You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since the last changes to source updates, it looks like manual triggering an update doesn't work any more. I suspect it just keeps the cached version, what I wouldn't expect when manually triggering an update. I don't have any logs to confirm my suspicion at the moment.
To Reproduce
Steps to reproduce the behavior:
Have a source (e.g. YARA rules) that you control and that has been updated in AL some time ago.
Change something in the source.
Wait a few minutes to ensure no caching happens in between.
Go to the update sources page and manually trigger updating your selected source.
Observe quick "Skipped" result. You can also find signatures and confirm there was nothing updated.
To confirm that there was something to update, you can change something in the source configuration. Then you will see that it updates.
Expected behavior
When manually triggering an update, I would expect to ignore any cache.
Screenshots
Environment (please complete the following information if pertinent):
Assemblyline Version: 4.5.0.67
I've observed the same behaviour in newest YARA as well as custom services.
Additional context
The text was updated successfully, but these errors were encountered:
kam193
added
assess
We still haven't decided if this will be worked on or not
bug
Something isn't working
labels
Jan 4, 2025
Describe the bug
Since the last changes to source updates, it looks like manual triggering an update doesn't work any more. I suspect it just keeps the cached version, what I wouldn't expect when manually triggering an update. I don't have any logs to confirm my suspicion at the moment.
To Reproduce
Steps to reproduce the behavior:
To confirm that there was something to update, you can change something in the source configuration. Then you will see that it updates.
Expected behavior
When manually triggering an update, I would expect to ignore any cache.
Screenshots
Environment (please complete the following information if pertinent):
Additional context
The text was updated successfully, but these errors were encountered: