| 16 Apr 2025 |
 @aloisw:julia0815.de | In reply to @emilazy:matrix.org
when are we getting a licensing room? I guess a lawyer would be more helpful | 14:53:26 |
 emily | what I meant was that it talks about being "made available under these Terms and Conditions" and then the competition clause says "as of the date we make the Software available", so it seems like "making the Software available" clearly refers to publication of a specific version | 14:54:25 |
| emily | (yes please. the Foundation really needs one.) | 14:54:26 |
 vaw | Redacted or Malformed Event | 17:27:16 |
| 17 Apr 2025 |
 hexa | three steps further and | 03:56:39 |
| hexa | sentry-relay> Compiling minidump v0.22.2
sentry-relay> error[E0599]: no method named `blocking_queue_depth` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:76:20
sentry-relay> |
sentry-relay> 76 | self.tokio.blocking_queue_depth()
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^
sentry-relay> |
sentry-relay> help: there is a method `global_queue_depth` with a similar name
sentry-relay> |
sentry-relay> 76 - self.tokio.blocking_queue_depth()
sentry-relay> 76 + self.tokio.global_queue_depth()
sentry-relay> |
sentry-relay>
sentry-relay> error[E0599]: no method named `budget_forced_yield_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:82:9
sentry-relay> |
sentry-relay> 82 | budget_forced_yield_count
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `num_blocking_threads` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:89:20
sentry-relay> |
sentry-relay> 89 | self.tokio.num_blocking_threads()
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `num_idle_blocking_threads` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:97:20
sentry-relay> |
sentry-relay> 97 | self.tokio.num_idle_blocking_threads()
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_local_queue_depth` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:112:20
sentry-relay> |
sentry-relay> 112 | self.tokio.worker_local_queue_depth(worker)
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^
sentry-relay> |
sentry-relay> help: there is a method `global_queue_depth` with a similar name, but with different arguments
sentry-relay> --> /build/cargo-deps-vendor/tokio-1.42.0/src/runtime/metrics/runtime.rs:95:5
sentry-relay> |
sentry-relay> 95 | pub fn global_queue_depth(&self) -> usize {
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_mean_poll_time` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:119:20
sentry-relay> |
sentry-relay> 119 | self.tokio.worker_mean_poll_time(worker)
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_local_schedule_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:126:9
sentry-relay> |
sentry-relay> 126 | worker_local_schedule_count
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_noop_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:132:9
sentry-relay> |
sentry-relay> 132 | worker_noop_count
sentry-relay> | ^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_overflow_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:138:9
sentry-relay> |
sentry-relay> 138 | worker_overflow_count
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_park_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:143:9
sentry-relay> |
sentry-relay> 143 | worker_park_count
sentry-relay> | ^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_poll_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:148:9
sentry-relay> |
sentry-relay> 148 | worker_poll_count
sentry-relay> | ^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_steal_count` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:154:9
sentry-relay> |
sentry-relay> 154 | worker_steal_count
sentry-relay> | ^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_steal_operations` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:160:9
sentry-relay> |
sentry-relay> 160 | worker_steal_operations
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> error[E0599]: no method named `worker_total_busy_duration` found for struct `tokio::runtime::RuntimeMetrics` in the current scope
sentry-relay> --> relay-system/src/runtime/metrics.rs:169:31
sentry-relay> |
sentry-relay> 169 | let stat = self.tokio.worker_total_busy_duration(worker).as_secs_f64();
sentry-relay> | ^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `RuntimeMetrics`
sentry-relay>
sentry-relay> For more information about this error, try `rustc --explain E0599`.
sentry-relay> error: could not compile `relay-system` (lib) due to 14 previous errors
| 03:57:06 |
| hexa | (╯°□°）╯︵ ┻━┻ | 03:57:23 |
| hexa | can't reproduce with nix-shell -p cargo python3.pkgs.build --run "python3 -m buiild py" | 04:22:07 |
| hexa | * can't reproduce with nix-shell -p cargo python3.pkgs.build --run "python3 -m build py" | 04:23:18 |
| hexa |
cargo-deps-vendor-staging> Fetching https://crates.io/api/v1/crates/tokio/1.42.0/download -> tarballs/tokio-1.42.0.tar.gz
| 04:25:07 |
| hexa | same version of tokio | 04:25:23 |
| hexa | because of course it is locked | 04:29:40 |
| hexa | a fun bit is that the tag on the repo is not the version of the python package in the repo 🤪 | 04:30:01 |
| hexa | https://github.com/getsentry/relay/blob/master/py/setup.py#L23 | 04:30:43 |
| hexa | and instead of 25.4.0 we get 0.9.8 | 04:30:49 |
| hexa | reminds me of good ol' openssl | 04:30:54 |
| hexa | * reminds me of good ol' openssl | 04:30:59 |
| hexa | latest version pushed to https://github.com/mweinelt/nixpkgs/blob/sentry/pkgs/development/python-modules/sentry-relay/default.nix | 04:33:05 |
 K900 | We don't have a prefetch-cargo-vendor or anything, right? | 09:56:47 |
| emily | nix-update can do it | 10:06:47 |
| emily | if you tell it not to bump the version | 10:06:52 |
| K900 | Hm OK this helps | 10:09:49 |
 Gaétan Lepage | How can I pass --target wasm32-wasip1 to buildRustPackage? Is it really falling in the scope of cross-compiling? | 11:07:55 |
| Gaétan Lepage | Source: https://github.com/bytecodealliance/wasmtime-py/blob/main/ci/build-rust.py#L22 | 11:08:24 |
 Alyssa Ross | You should be able to do it without cross compiling | 11:17:34 |
| Alyssa Ross | (in the Nixpkgs sense) | 11:17:39 |
| Gaétan Lepage | Ok great! How though? If I add --target wasm32-wasip1 to cargoBuildFlags, it just appends it and I have two --target flags in the final command. | 11:41:31 |
| Gaétan Lepage | Is there a way to simply "override" the --target flag? | 11:41:47 |
| @aloisw:julia0815.de | There does not appear to, but you can work around by calling cargo with the right flags in stdenv.mkDerivation. | 12:39:16 |
| Gaétan Lepage | Ok I see, thanks :) | 13:26:14 |
