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

fix: Exceptions are not catched in query over ws #18

Merged
merged 1 commit into from
Jul 7, 2021
Merged

Conversation

ciscorn
Copy link
Owner

@ciscorn ciscorn commented Jul 7, 2021

No description provided.

@codecov
Copy link

codecov bot commented Jul 7, 2021

Codecov Report

Merging #18 (e398e28) into master (fb3b46b) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   99.09%   99.10%   +0.01%     
==========================================
  Files           1        1              
  Lines         221      224       +3     
==========================================
+ Hits          219      222       +3     
  Misses          2        2              
Flag Coverage Δ
unittests 99.10% <100.00%> (+0.01%) ⬆️

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

Impacted Files Coverage Δ
starlette_graphene3.py 99.10% <100.00%> (+0.01%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb3b46b...e398e28. Read the comment docs.

@ciscorn ciscorn linked an issue Jul 7, 2021 that may be closed by this pull request
@ciscorn ciscorn merged commit afadd2a into master Jul 7, 2021
@ciscorn ciscorn deleted the fix-exc-wsquery branch July 7, 2021 02:40
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.

Exceptions are not catched when using a websocket
1 participant