Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InfoRequest level censor rule was not applied #8387

Open
laurentS opened this issue Sep 19, 2024 · 0 comments
Open

InfoRequest level censor rule was not applied #8387

laurentS opened this issue Sep 19, 2024 · 0 comments
Labels
bug Breaks expected functionality f:redaction x:france

Comments

@laurentS
Copy link
Contributor

We received a message from a user requesting to hide their name from an incoming message. I added a censor rule on the info request, but it never was applied on the public page (I could see it in effect for admins), even several weeks later, which we found out after receiving a second request from the same person.

After running IncomingMessage.find(xxx)._cache_main_body_text in the console, the problem was fixed.
However, I wonder how this could happen. We are running sidekiq for background job queues, my understanding is that jobs should not be lost because of a server reboot or similar situations. What scenarii could lead to the job being skipped? Are there counter measures we can put in place to ensure this does not happen again?
We were running alaveteli 0.44.0.0 at the time of the bug. I came across #3959 which suggests that this was fixed several years ago.

@github-staff github-staff deleted a comment from nhatlaso1 Sep 23, 2024
@garethrees garethrees added bug Breaks expected functionality f:redaction x:france labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Breaks expected functionality f:redaction x:france
Projects
None yet
Development

No branches or pull requests

2 participants