Skip to content

Sync to prepare for 0.74.2 #4182

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

Merged
merged 22 commits into from
Apr 17, 2025
Merged

Sync to prepare for 0.74.2 #4182

merged 22 commits into from
Apr 17, 2025

Conversation

scudette
Copy link
Contributor

No description provided.

dependabot bot and others added 22 commits April 17, 2025 00:53
This would deadlock a client's profile flow.
In rare situations the periodic update mechanism. This resulted in
notebook cell state going backwards preventing proper updates.
In some situations it is possible for result sets to be retransmitted
(for example when there is a load balancer in front). This PR detects
when a result set upload is replayed and ignores it. Without this
detection, the result set will append a repeated set of data which may
corrupt the uploaded query results.
When artifacts are modified we need to recompile the client event tables
- this takes time. If the user modifies a lot of artifacts very quickly
(e.g. with a VQL query) this can overwhelm the server as it will try to
recompile the event table for each artifact.

This PR adds debouncing via the notification service to limit the rate
of event table compilation.
This happened when the file store memory limit exceeded and it tried to
flush aggresively.
I'm using Velociraptor with SSO, and the lack of the IdP-initiated SAML
flow was annoying me, so I decided to contribute it! It's fairly simple
change as we only need to pass that option to `samlsp.Options` and
`samlsp` takes care of everything afterwards.
This field can add additional enrichment to events only after they
already matched. This removes the need to calculate expensive operations
for all events, instead we only do this for some events.
Pst parser introduced a dependency that does not build on this platform.
Previously we added the token in the cookie which would make the cookie
too large. This PR sets the user avatar in the datastore during the
oauth step so it can be retrieved from there instead of the cookie each
time. This keeps the cookie smaller.

Fixes: #4177
@CLAassistant
Copy link

CLAassistant commented Apr 16, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ predictiple
✅ seqre
✅ scudette
❌ dependabot[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@scudette scudette merged commit 107e07b into v0.74-release Apr 17, 2025
2 of 3 checks passed
@scudette scudette deleted the 0.74-2-sync branch April 17, 2025 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants