Skip to content
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

[Access] Add endpoints to Execution nodes to support getting Transaction Result error messages #5042

Conversation

AndriiDiachuk
Copy link
Contributor

#4754

In this pull request are Introduced new endpoints on the Execution node grpc API, that return transaction result error messages.

Related PR:
onflow/flow#1398

@codecov-commenter
Copy link

codecov-commenter commented Nov 21, 2023

Codecov Report

Attention: 43 lines in your changes are missing coverage. Please review.

Comparison is base (538e72e) 56.20% compared to head (3071d24) 56.19%.
Report is 8 commits behind head on master.

Files Patch % Lines
engine/execution/rpc/engine.go 63.20% 33 Missing and 6 partials ⚠️
engine/access/apiproxy/access_api_proxy.go 0.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5042      +/-   ##
==========================================
- Coverage   56.20%   56.19%   -0.02%     
==========================================
  Files         975      975              
  Lines       90714    90833     +119     
==========================================
+ Hits        50990    51047      +57     
- Misses      35913    35970      +57     
- Partials     3811     3816       +5     
Flag Coverage Δ
unittests 56.19% <60.90%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

engine/execution/rpc/engine.go Outdated Show resolved Hide resolved
engine/execution/rpc/engine_test.go Outdated Show resolved Hide resolved
engine/execution/rpc/engine_test.go Outdated Show resolved Hide resolved
engine/execution/rpc/engine_test.go Outdated Show resolved Hide resolved
@AndriiDiachuk
Copy link
Contributor Author

I've accidentally pushed a version which wasn't properly structured while I was trying some tests refactoring. I've fixed everything and there is a clean diff with only additions.

@AndriiDiachuk
Copy link
Contributor Author

@peterargue Thanks for comments. Added missing parts and now it's ready for review again.

Copy link
Contributor

@peterargue peterargue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple small comments, but otherwise this looks good. Great work!

engine/execution/rpc/engine.go Outdated Show resolved Hide resolved
engine/execution/rpc/engine_test.go Show resolved Hide resolved
Copy link
Member

@durkmurder durkmurder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job. 🎸

@durkmurder durkmurder enabled auto-merge November 22, 2023 09:08
@durkmurder durkmurder added this pull request to the merge queue Nov 22, 2023
Merged via the queue into onflow:master with commit 583f9f8 Nov 22, 2023
54 checks passed
peterargue pushed a commit that referenced this pull request Dec 12, 2023
…dpoints-to-execution-nods-to-support-tx-result-err-msgs

[Access] Add endpoints to Execution nodes to support getting Transaction Result error messages
peterargue pushed a commit that referenced this pull request Dec 12, 2023
…dpoints-to-execution-nods-to-support-tx-result-err-msgs

[Access] Add endpoints to Execution nodes to support getting Transaction Result error messages
peterargue pushed a commit that referenced this pull request Dec 13, 2023
…dpoints-to-execution-nods-to-support-tx-result-err-msgs

[Access] Add endpoints to Execution nodes to support getting Transaction Result error messages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants