Nedim Salkić
Nedim Salkić
@Dhaiwat10 You can mock `execSync` and have two tests: 1. Have `execSync('fuelup --version')` fail, verify that it was called later on with `curl https://install.fuel.network | sh` 2. Have `execSync('fuelup --version')`...
[Related comment](https://github.com/FuelLabs/fuels-ts/pull/1356/files#r1530301679). That PR has implementation for how the infrastructure part of this issue would be handled.
> but I bet we can find some external articles on the topic. Here's a great one from the SRE book: https://sre.google/sre-book/handling-overload/. The section of most interest for us would...
> especially if we have more information about the fuel-core rate-limiting (not sure if we have these details yet). Could somebody from @FuelLabs/client chime in on this?
Closing this issue as not planned because it's not in the domain of the SDK. Referencing the @FuelLabs/devrel team because they might want to evolve this topic further from the...
This makes sense. The "usage" examples shouldn't be showing something that's not representative of actual real-world usage.
@danielbate While you're at it, you can look into removing it totally based on #1592.
@arboleya > The only way to ship these files to the browser is if we generate types for everything using Typegen. The JSON and hexlified bytecode would be included in...
Blocked by merge #1615 and #1495.
This was first an issue, but you wanted it turned it into a discussion because some things were unclear and I couldn't properly formulate how to introduce it into the...