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 generating supergraph #1443

Closed
rmarku opened this issue Dec 2, 2022 · 1 comment
Closed

bug: crashed while generating supergraph #1443

rmarku opened this issue Dec 2, 2022 · 1 comment
Labels
bug 🐞 duplicate 🧑‍🤝‍🧑 issue or pull request already exists triage issues and PRs that need to be triaged

Comments

@rmarku
Copy link

rmarku commented Dec 2, 2022

Description

just running rover

rover supergraph compose --config supergraphql.yaml > supergraph.graphql

Crash Report

name = 'rover'
operating_system = 'unix:Unknown'
crate_version = '0.10.0'
explanation = '''
Panic occurred in file 'src/utils/telemetry.rs' at line 121
'''
cause = '''
could not get request client: RoverError { error: builder error: error reading DNS system conf: Error parsing resolv.conf: ProtoError { kind: Msg("Malformed label: --") }

Caused by:
    error reading DNS system conf: Error parsing resolv.conf: ProtoError { kind: Msg("Malformed label: --") }, metadata: RoverErrorMetadata { suggestion: None, code: None, skip_printing_cause: false, json_version: One } }'''
method = 'Panic'
backtrace = '''

   0: 0x560e21f7b743 - core::result::unwrap_failed::hfaddf24b248137d3
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/result.rs:1785
   1: 0x560e2200b1b5 - sputnik::session::Session::new::h5022b872ed8d5bbd
   2: 0x560e21f88d9b - rover::cli::Rover::run::h625bff5fd5c53de9
   3: 0x560e21f88c12 - rover::cli::Rover::run_from_args::h54f84c361f7a6e4f
   4: 0x560e21f7c3b3 - rover::main::h9665f97a284ca5bc
   5: 0x560e21f7c6e3 - std::sys_common::backtrace::__rust_begin_short_backtrace::he6c7811e36f6c513
   6: 0x560e21f7c0c9 - std::rt::lang_start::{{closure}}::ha175893b1326791c
   7: 0x560e2283280f - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hb69be6e0857c6cfb
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/ops/function.rs:283
                 - std::panicking::try::do_call::h396dfc441ee9c786
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:492
                 - std::panicking::try::h6cdda972d28b3a4f
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:456
                 - std::panic::catch_unwind::h376039ec264e8ef9
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::{{closure}}::hc94720ca3d4cb727
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/rt.rs:148
                 - std::panicking::try::do_call::h2422fb95933fa2d5
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:492
                 - std::panicking::try::h488286b5ec8333ff
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:456
                 - std::panic::catch_unwind::h81636549836d2a25
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panic.rs:137
                 - std::rt::lang_start_internal::h6ba1bb743c1e9df9
                at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/rt.rs:148
   8: 0x560e21f7c6d8 - main
   9: 0x7f3846a6b30a - <unresolved>
  10: 0x7f3846a6b3c5 - __libc_start_main
  11: 0x560e21f7bd97 - <unresolved>
  12:        0x0 - <unresolved>'''
@rmarku rmarku added bug 🐞 triage issues and PRs that need to be triaged labels Dec 2, 2022
@EverlastingBugstopper
Copy link
Contributor

Hi @rmarku - sorry that you've encountered this issue. This seems to be a problem with parsing your system's DNS resolv.conf configuration file. This panic occurs in an upstream dependency called resolv-conf. You might try inspecting that file and removing the offending entry. I'm going to close this issue as a duplicate of #1471.

@EverlastingBugstopper EverlastingBugstopper added the duplicate 🧑‍🤝‍🧑 issue or pull request already exists label Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 duplicate 🧑‍🤝‍🧑 issue or pull request already exists triage issues and PRs that need to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants