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

bug: crashed while publishing first federated service to graph #548

Closed
dragonfriend0013 opened this issue May 17, 2021 · 2 comments · Fixed by #549
Closed

bug: crashed while publishing first federated service to graph #548

dragonfriend0013 opened this issue May 17, 2021 · 2 comments · Fixed by #549
Labels

Comments

@dragonfriend0013
Copy link

dragonfriend0013 commented May 17, 2021

MacOS Catalina, rover installed locally (non-npm)
command run:
APOLLO_KEY set to default key when graph created

rover graph introspect http://127.0.0.1:8080/graphql --header "introspect: apollo" > schema.graphql
rover subgraph publish Mercury-COF@test
--schema schema.graphql
--name am-service
--routing-url http://localhost:8001/graphql

Did receive in console:
Publishing SDL to Mercury-COF:test (subgraph: am-service) using credentials from the default profile.

Crash Report

name = 'rover'
operating_system = 'unix:OSX'
crate_version = '0.1.0'
explanation = '''
Panic occurred in file 'crates/rover-client/src/query/config/is_federated.rs' at line 30
'''
cause = 'called `Option::unwrap()` on a `None` value'
method = 'Panic'
backtrace = '''

  0: 0x105ac81fa - _rust_begin_unwind
  1: 0x105b04ccf - core::panicking::panic_fmt::h84e4b5f5d5160f07
  2: 0x105b04c27 - core::panicking::panic::hc8ddd2371b27d6e7
  3: 0x10575b924 - rover_client::query::config::is_federated::run::hfd743f26599a7624
  4: 0x104833aec - rover::command::subgraph::publish::Publish::run::h64ed21acc8947ced
  5: 0x104818b8f - rover::command::subgraph::Subgraph::run::h0f9a07e978cd5631
  6: 0x10484b18e - rover::cli::Rover::run::h6dc6b2a8071a1ad8
  7: 0x1047e5497 - rover::main::hf2dbbe5aede58229
  8: 0x1047e390a - std::sys_common::backtrace::__rust_begin_short_backtrace::hffb16c902375a64f
  9: 0x1047e392c - std::rt::lang_start::{{closure}}::h188f24c2d46d090b
 10: 0x105ac8ba4 - std::rt::lang_start_internal::h0c37a46739a0311d
 11: 0x1047e5c19 - _main'''
@dragonfriend0013
Copy link
Author

solved, typo in the graph name, did not see the extra characters provided after my named graph.

@EverlastingBugstopper
Copy link
Contributor

Hey @dragonfriend0013! We'll still classify this as a bug since we'd like you to receive a more actionable error message instead of an unrecoverable panic. Thanks for opening this issue 😄

@EverlastingBugstopper EverlastingBugstopper added bug 🐞 triage issues and PRs that need to be triaged labels May 17, 2021
@abernix abernix removed the triage issues and PRs that need to be triaged label Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants