You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "geido (via GitHub)" <gi...@apache.org> on 2025/01/30 16:50:28 UTC
[I] RLS "Last modified" field is not updated [superset]
geido opened a new issue, #32050:
URL: https://github.com/apache/superset/issues/32050
### Bug description
Updating a RLS won't update the "Last modified" time.
## How to reproduce the bug
1. Visit Row Level Security under Settings
2. Create a RLS rule
3. Wait a few minutes and observe the Last modified time
4. Change the rule
## Expected results
The Last modified time should update
## Actual results
The Last modified time hasn't updated
### Screenshots/recordings
<img width="1202" alt="Image" src="https://github.com/user-attachments/assets/b768530e-4855-474e-a3e0-76aa7044d148" />
### Superset version
master / latest-dev
### Python version
3.9
### Node version
18 or greater
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] RLS "Last modified" field is not updated [superset]
Posted by "geido (via GitHub)" <gi...@apache.org>.
geido commented on issue #32050:
URL: https://github.com/apache/superset/issues/32050#issuecomment-2625348179
---
### 🎉 **Preset Bounty Available: $150 USD** 🎉
To claim this bounty, please carefully follow the steps below.
---
#### 📋 **Steps to Participate**
1. **Review Guidelines:**
Read through the [Preset Bounty Program Contribution Guide](https://preset.notion.site/preset-bounty-program-apache-superset) for complete details on bounty requirements.
2. **Show Your Interest:**
Complete the [Preset Bounty Program Survey](https://docs.google.com/forms/d/e/1FAIpQLSeDsR1iWvPxFydUIXs2agsUg3kMDaAooeD4P9P1L5sI0Yu5QQ/viewform?usp=sharing) and comment this issue to express your interest.
3. **Join the Slack Channel:**
After completing the survey, you’ll receive an invitation to the dedicated [Apache Superset Slack](https://join.slack.com/t/apache-superset/shared_invite/zt-2be0drwz8-bxPfkdz28ozzk1Iox29ufg) channel.
4. **Get Assigned:**
To officially start, ensure a **Bounty Program Manager** has assigned you to this issue.
5. **Submit Your Solution:**
When ready, submit your solution with the `Fixes #{issue_number}` notation in your Pull Request description.
6. **Claim Your Bounty:**
Sign up at [GitPay.me](https://gitpay.me/) and submit your solution via: [https://gitpay.me/#/task/1057](https://gitpay.me/#/task/1057)
---
#### 💡 **Additional Notes**
- Only developers assigned by a **Bounty Program Manager** should start working on this issue to win the bounty.
- Be sure to follow the guide closely to avoid any delays in payment. Please, allow a few days after your PR has been merged for the bounty to be released.
Good luck, and happy coding! 🎉
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] RLS "Last modified" field is not updated [superset]
Posted by "LevisNgigi (via GitHub)" <gi...@apache.org>.
LevisNgigi commented on issue #32050:
URL: https://github.com/apache/superset/issues/32050#issuecomment-2625389655
I can take this as well.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] RLS "Last modified" field is not updated [superset]
Posted by "villebro (via GitHub)" <gi...@apache.org>.
villebro closed issue #32050: RLS "Last modified" field is not updated
URL: https://github.com/apache/superset/issues/32050
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] RLS "Last modified" field is not updated [superset]
Posted by "fardin-developer (via GitHub)" <gi...@apache.org>.
fardin-developer commented on issue #32050:
URL: https://github.com/apache/superset/issues/32050#issuecomment-2625375845
I would love to work on this
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org