You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when runnign cargo nextest run, I get errors like these:
thread 'db::test::index_invalidate_cache' panicked at 'called `Result::unwrap()` on an `Err` value: AtomicError { message: "Failed setting propval for 'https://localhost/agents/w0ppEskueRjKC6S9tAawjtFJYtTWsndcHpQ96OlHq6Q=' because property 'https://atomicdata.dev/properties/publicKey' could not be found. Failed getting property https://atomicdata.dev/properties/publicKey. Error when fetching https://atomicdata.dev/properties/publicKey : https://atomicdata.dev/properties/publicKey: Network Error: Network Error: Error encountered in the status line: timed out reading response", error_type: OtherError }', lib/src/db/test.rs:436:52
thread 'parse::test::serialize_parse_roundtrip' panicked at 'called `Result::unwrap()` on an `Err` value: AtomicError { message: "Unable to import JSON-AD. Unable to parse resource. Failed getting property https://atomicdata.dev/properties/name. Error when fetching https://atomicdata.dev/properties/name : https://atomicdata.dev/properties/name: Network Error: Network Error: Error encountered in a header: timed out reading response", error_type: OtherError }', lib/src/parse.rs:246:36
Edit: seems like the issue is that create_agent fetches properties, because they aren't loaded yet. This should not be needed, because we know the datatypes are valid.
I should find a way to make tests fail when they do a network call
The text was updated successfully, but these errors were encountered:
Sometimes when runnign
cargo nextest run
, I get errors like these:Edit: seems like the issue is that
create_agent
fetches properties, because they aren't loaded yet. This should not be needed, because we know the datatypes are valid.I should find a way to make tests fail when they do a network call
The text was updated successfully, but these errors were encountered: