Added submit_and_await endpoint to not miss the notifications
#1192
Conversation
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
# Conflicts: # Cargo.lock # tests/Cargo.toml
…freesig/test-submit-await
Voxelot
reviewed
May 26, 2023
crates/client/assets/schema.sdl
Outdated
| """ | ||
| submit(tx: HexString!): Transaction! | ||
| """ | ||
| Submits transaction to the `TxPool` and await either confirmation or failure. | ||
| """ | ||
| submitAndAwait(tx: HexString!): TransactionStatus! |
There was a problem hiding this comment.
This should probably be a stream/subscription, as the connection is more likely to just timeout if the transaction is waiting in the transaction pool too long.
There was a problem hiding this comment.
I wrote a test and checked that I didn't get a timeout with a 10-minute production interval. Maybe it works for me because of OS keeps alive default behavior.
But I changed to use a subscription model. Maybe we can get a timeout in the production in some other place like ingress nginx.
Voxelot
approved these changes
May 29, 2023
Merged
xgreenx
added a commit
that referenced
this pull request
Jun 14, 2023
## What's Changed * version compatibility cleanup by @Voxelot in #1171 * Added example with custom query around the `fuel-core-client` by @xgreenx in #1175 * Update to fuel-vm 0.32 (including wideint gas profiling) by @Dentosal in #1173 * feat: Client primitives by @bvrooman in #1144 * Improve executor config by @Voxelot in #1185 * Added `contract_id` to the `ContractConfig` by @xgreenx in #1184 * fix windows file name error by @firedpeanut in #1176 * Make transaction status stream work by @freesig in #1108 * Added `submit_and_await` endpoint to not miss the notifications by @xgreenx in #1192 * feat: Use ID types in client api by @bvrooman in #1191 * Use `fuel-vm 0.33` with predicate estimation by @xgreenx in #1195 * Add transaction lifecycle diagram to the docs by @digorithm in #1201 * sync with peers before producing blocks by @leviathanbeak in #1169 * SMT storage key hashing by @xgreenx in #1207 ## New Contributors * @firedpeanut made their first contribution in #1176 **Full Changelog**: v0.18.1...v0.19.0 --------- Co-authored-by: Brandon Kite <brandonkite92@gmail.com>
crypto523
pushed a commit
to crypto523/fuel-core
that referenced
this pull request
Oct 7, 2024
## What's Changed * version compatibility cleanup by @Voxelot in FuelLabs/fuel-core#1171 * Added example with custom query around the `fuel-core-client` by @xgreenx in FuelLabs/fuel-core#1175 * Update to fuel-vm 0.32 (including wideint gas profiling) by @Dentosal in FuelLabs/fuel-core#1173 * feat: Client primitives by @bvrooman in FuelLabs/fuel-core#1144 * Improve executor config by @Voxelot in FuelLabs/fuel-core#1185 * Added `contract_id` to the `ContractConfig` by @xgreenx in FuelLabs/fuel-core#1184 * fix windows file name error by @firedpeanut in FuelLabs/fuel-core#1176 * Make transaction status stream work by @freesig in FuelLabs/fuel-core#1108 * Added `submit_and_await` endpoint to not miss the notifications by @xgreenx in FuelLabs/fuel-core#1192 * feat: Use ID types in client api by @bvrooman in FuelLabs/fuel-core#1191 * Use `fuel-vm 0.33` with predicate estimation by @xgreenx in FuelLabs/fuel-core#1195 * Add transaction lifecycle diagram to the docs by @digorithm in FuelLabs/fuel-core#1201 * sync with peers before producing blocks by @leviathanbeak in FuelLabs/fuel-core#1169 * SMT storage key hashing by @xgreenx in FuelLabs/fuel-core#1207 ## New Contributors * @firedpeanut made their first contribution in FuelLabs/fuel-core#1176 **Full Changelog**: FuelLabs/fuel-core@v0.18.1...v0.19.0 --------- Co-authored-by: Brandon Kite <brandonkite92@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.