Skip to content

[BUG] octocode index and clear commands panic! #12

@ossfellow

Description

@ossfellow

Thank you for fixing reported issues, and improving the Octocode capabilities.

Unfortunately, the new version 0.8.0 has introduced new issues, but the first and most important one which occurs with both octocode index and octocode clear is the following:

thread 'main' panicked at /Users/ossfellow/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.46.1/src/runtime/scheduler/multi_thread/mod.rs:86:9:
Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I should add that in the case of clear command, after multiple failures, I manually deleted everything, except the config file, and ran the command both from inside and outside a local git repository but the issue persisted.

So, because of this, I cannot test if any of the 3 issues, I had reported including the search and graphrag commands are now working or not.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions