Point to providers in fiberplane-rs

[emschwartz]

No description provided.

[emschwartz]

@arendjr the test where it invokes the providers is failing with this error. Any idea what that's about?

Provider log: prometheus provider invoked with request: Status, config: Array([String(Utf8String { s: Ok("http://127.0.0.1:57175") })])
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Link(Import("__wbindgen_placeholder__", "__wbindgen_describe", UnknownImport(Function(FunctionType { params: [I32], results: [] }))))', /Users/emschwartz/.cargo/git/checkouts/fiberplane-rs-5049e26e67ac1a68/e2f20ae/provider-protocol/generated/fp-provider-runtime/src/spec/bindings.rs:186:68
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Provider log: prometheus provider invoked with request: Status, config: Array([String(Utf8String { s: Ok("http://127.0.0.1:57158") })])
thread 'tests::sends_data_sources_on_connect' panicked at 'assertion failed: `(left == right)`
  left: `Details(DataSourceDetails { ty: Elasticsearch, status: Error("Did not receive a status response from the provider") })`,
 right: `Details(DataSourceDetails { ty: Elasticsearch, status: Connected })`', proxy/src/tests.rs:199:17

[arendjr]

Oh, @sagacity and I ran into this the other day. You need to make sure time is pinned to the previous version, because the latest one assumes that anyone targeting wasm is using wasm-bindgen, which triggers these unresolved symbols during linking. I think Roy made an issue for it.

[emschwartz]

@arendjr I updated the time dep to the latest version which says it contains a fix for that issue but the test is still failing. https://github.com/time-rs/time/blob/main/CHANGELOG.md#0313-2022-08-09

[arendjr]

Did you try 0.3.11 as well? I haven't tried that fix yet, so cannot vouch for it...

[arendjr]

In any case, looking at the lock file, there's a whole bunch of wasm-bindgen stuff included. If you track down why they are included, you should find the culprit :)

[emschwartz]

@arendjr same error with time@0.3.11