-
Notifications
You must be signed in to change notification settings - Fork 22
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
feat: integrate agent store for idempotence & invocation/receipt persistence #1444
Merged
Merged
Changes from all commits
Commits
Show all changes
49 commits
Select commit
Hold shift + click to select a range
9aee035
feat: add blob add to upload-cli
joaosa 48cde40
feat: use blob add on upload-cli
joaosa d5672c8
feat: modify tests to cover blob add on upload-client
joaosa 0f1e592
chore: cleanup code and add current status
joaosa 1ccb3c4
feat: revamp implementation
joaosa dc40432
chore: cleanup blob/add implementation
joaosa 48a641e
chore: fix typo
joaosa 99c1878
feat: expose blob add result types
joaosa 8ae5f69
fix: have all test return types match the blob add response
joaosa 2ff3748
fix: pass upload CAR and file tests
joaosa 8fb6720
fix: pass upload-client tests
joaosa 5642e01
feat: add client upload progress
joaosa 1f600c3
chore: relock deps
joaosa 2c73702
fix: blob add upload progress implementation
joaosa 50929e6
chore: address linter errors
joaosa 9391a86
fix: test blob upload on w3up-client tests
joaosa 45507f2
chore: cleanup upload-client test code
joaosa 0896614
fix: pass w3up-client upload tests
joaosa 7552e9b
fix: missing import
joaosa 4eee857
chore: appease prettier
joaosa 24a99e9
fix: address w3up upload test expectations
joaosa c6aaa04
feat: implement blob/remove
joaosa 65dfee1
feat: implement blob/list
joaosa 21e2973
fix: pass blob protocol upload-client tests
joaosa f9c4043
chore: address coverage for upload-client blob
joaosa 5196f9c
feat: add w3up-client upload-client blob boilerplate
joaosa fb21b1a
fix: error classes that called recursion
Gozala 87915a9
fix: digest encoding
Gozala 1c886f1
fix: invalid test assertion
Gozala c4c941a
fix: failing tests
Gozala e0b8619
feat: implement task & receipt store
Gozala c10ca5f
fix: address remaining issues
Gozala 93faab5
chore: remove receipt storing logic
Gozala 0afa904
Apply suggestions from code review
Gozala f5a960b
Merge remote-tracking branch 'origin/main' into feat/agent-store
Gozala cf7e1f7
chore: put comments about temp hack back in
Gozala c89e9ce
fix post-merge errors
Gozala 49f275e
fix: enable all tests
Gozala b67bb83
fix: type check
Gozala 8d4a484
chore: undo accidental changes
Gozala c8e0088
chore: disable failing test
Gozala a3382e4
fix: upload-client api misalignment
Gozala 23c795f
fix: failing tests
Gozala 6d513de
fix: failing test
Gozala 4b196c6
fix: remove unused dep
Gozala 98889fb
feat: add agent store tests
Gozala 3c403f1
Apply suggestions from code review
Gozala 1d6e557
Merge remote-tracking branch 'origin/main' into feat/agent-store
Gozala c8a83d3
fix: workaround c8 bug
Gozala File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
nit: would be great to send this into a DLQ where we could be alerted. Probably an issue for now would be good, as we would also need to do the setup for DLQ monitoring
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.
We could probably set this up as capability handler and dispatch to it, that way we would be able to throw here which will end up triggering
catch
handler of the server and get logged instead.Does that sound like a better option ?