-
Notifications
You must be signed in to change notification settings - Fork 0
[fix] DVC-6373: use address pinning in Local Bucketing #52
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
Conversation
| WasmFunctions.Consumer3<Integer, Integer, Integer> fn = WasmFunctions.consumer(store, queueEventPtr, I32, I32, I32); | ||
| fn.accept(tokenAddress, userAddress, eventAddress); | ||
| fn.accept(sdkKeyAddress, userAddress, eventAddress); | ||
| unpinParameter(userAddress); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens in case of errors thrown above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all errors are surfaced in the DVCLocalClient, with try / catch blocks around each call to Local Bucketing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah but the values wont be unpinned until the next time one of the two methods that triggers unpin is called.
the approach I went with for c# was just to unpin at the beginning of every method so that you'd only have at most one method call's worth of pinned resources left behind by some error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, will do the same here :) thanks
b1c8093 to
d826b5c
Compare
f778b1f to
cf1118f
Compare
src/main/java/com/devcycle/sdk/server/local/bucketing/LocalBucketing.java
Show resolved
Hide resolved
cf1118f to
657179e
Compare
657179e to
a188be1
Compare
…4.2 to address a vulunerability finding
0.14and jackson2.14.2