Skip to content

Conversation

@Guardiola31337
Copy link
Contributor

  • Returns the actual error coming back from NN when fetching an offline route fails, adding something which has more information to help which will definitely help diagnose potential fetching issues

cc @kevinkreiser

Copy link
Contributor

@danesfeder danesfeder left a comment

Choose a reason for hiding this comment

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

Thanks @Guardiola31337 🚢

@codecov-io
Copy link

codecov-io commented Jan 10, 2019

Codecov Report

Merging #1660 into master will increase coverage by 0.24%.
The diff coverage is 80%.

@@             Coverage Diff             @@
##             master   #1660      +/-   ##
===========================================
+ Coverage     26.25%   26.5%   +0.24%     
- Complexity      787     795       +8     
===========================================
  Files           197     197              
  Lines          8384    8392       +8     
  Branches        602     602              
===========================================
+ Hits           2201    2224      +23     
+ Misses         5983    5968      -15     
  Partials        200     200

@Guardiola31337 Guardiola31337 force-pushed the pg-return-offline-error-from-nn branch from 092f0cb to c83b45e Compare January 10, 2019 15:52
@Guardiola31337 Guardiola31337 force-pushed the pg-return-offline-error-from-nn branch from c83b45e to 124f6ec Compare January 10, 2019 15:54
@Guardiola31337 Guardiola31337 merged commit 5cc556e into master Jan 10, 2019
@Guardiola31337 Guardiola31337 deleted the pg-return-offline-error-from-nn branch January 10, 2019 16:13
@danesfeder danesfeder mentioned this pull request Jan 16, 2019
12 tasks
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.

3 participants