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

Segfault/ENFORCE hit when indexing hashicorp/vagrant #162

Open
varungandhi-src opened this issue Nov 17, 2022 · 0 comments
Open

Segfault/ENFORCE hit when indexing hashicorp/vagrant #162

varungandhi-src opened this issue Nov 17, 2022 · 0 comments

Comments

@varungandhi-src
Copy link
Contributor

varungandhi-src commented Nov 17, 2022

Input

See https://sourcegraph.com/github.com/hashicorp/vagrant/-/code-graph/indexes/TFNJRkluZGV4OjQwOTEwMjk=

Repo: https://github.com/hashicorp/vagrant.git
Commit tested: 8a1e285689226e12023716eed6a6878a821d65a3

Sorbet type-checking output

I ran bundle exec srb tc and got this output:

<suppressed>
Errors: 3269

There is no crash.

scip-ruby indexing output

n/a

scip-ruby-debug indexing output

I ran:

❯ PATH="$HOME/Code/scip-ruby/bazel-bin/main:$PATH" ~/Code/scip-ruby/scip_indexer/autoindex.sh

and got:

Exception::raise(): namer/namer.cc:703 enforced condition kind != Kind::ClassOrModule has failed: ClassOrModule symbols should always be entered first, so they should never need to mangle something else

The stack trace isn't showing up for me for some reason.

Configuration

n/a

Additional info

No response

@varungandhi-src varungandhi-src added the bug Something isn't working label Nov 17, 2022
@varungandhi-src varungandhi-src changed the title Segfault when indexing hashicorp/vagrant ENFORCE hit when indexing hashicorp/vagrant Nov 17, 2022
@varungandhi-src varungandhi-src changed the title ENFORCE hit when indexing hashicorp/vagrant Segfault/ENFORCE hit when indexing hashicorp/vagrant Nov 17, 2022
@mmanela mmanela added the Migrated label May 6, 2024 — with Linear
@linear linear bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants