Skip to content
This repository has been archived by the owner on Dec 15, 2023. It is now read-only.

Wrap badrequest error when forking #462

Merged

Conversation

tonypony220
Copy link
Contributor

@tonypony220 tonypony220 commented May 8, 2023

Usage related changes

Not wrapped functions in Forked state seems to have no errors and not have to be suppressed.

  • none

Development related changes

  • redirect stderr replaced with muting only logger (not redirects in origin for some reason).

Checklist:

  • Applied formatting - ./scripts/format.sh
  • No linter errors - ./scripts/lint.sh
  • Performed code self-review
  • Rebased to the last commit of the target branch (or merged it into my branch)
  • Documented the changes
  • Linked the issues which this PR resolves
  • Updated the tests
  • All tests are passing - ./scripts/test.sh

@FabijanC FabijanC self-requested a review May 9, 2023 07:31
starknet_devnet/util.py Outdated Show resolved Hide resolved
test/test_endpoints.py Outdated Show resolved Hide resolved
@tonypony220 tonypony220 force-pushed the wrap_badrequest_error_when_forking branch from bd08bc5 to 3882b36 Compare May 9, 2023 14:16
starknet_devnet/util.py Outdated Show resolved Hide resolved
starknet_devnet/util.py Outdated Show resolved Hide resolved
starknet_devnet/util.py Outdated Show resolved Hide resolved
@tonypony220 tonypony220 force-pushed the wrap_badrequest_error_when_forking branch from 298ad19 to 83fe306 Compare May 9, 2023 15:57
@FabijanC FabijanC merged commit c7ddd4c into 0xSpaceShard:master May 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrap BadRequest error logs when forking
2 participants