Kamil Skalski
Kamil Skalski
### Describe the bug I'm getting error ``` > error: Invalid define value (must be valid JSON syntax or a single identifier): process.env > error: Invalid define value (must be...
Private registry push reports "blob upload unknown" in client even though data gets pushed correctly
My setup is following: - registry from upstream 2.6 image - single replica running on kubernetes - storage is backed by NFS - access to registry is handled by haproxy...
When grpc-js calls are made, it's possible to set [``Metadata``](https://grpc.github.io/grpc/node/grpc.Metadata.html), which besides key-value pairs, also contains a few pre-defined options set in constructor with [``MetadataOptions`` object](https://github.com/grpc/grpc-node/blob/7239c0e2a234db7e8226394c4ad84cd6059a6639/packages/grpc-js/src/metadata.ts#L71) ). Currently the generated...
When grpc-js calls are made, it's possible to set [``Metadata``](https://grpc.github.io/grpc/node/grpc.Metadata.html), which besides key-value pairs, also contains a few pre-defined options set in constructor with [``MetadataOptions`` object](https://github.com/grpc/grpc-node/blob/7239c0e2a234db7e8226394c4ad84cd6059a6639/packages/grpc-js/src/metadata.ts#L71) ). Currently the generated...
When grpc-js calls are made, it's possible to set [``Metadata``](https://grpc.github.io/grpc/node/grpc.Metadata.html), which besides key-value pairs, also contains a few pre-defined options set in constructor with [``MetadataOptions`` object](https://github.com/grpc/grpc-node/blob/7239c0e2a234db7e8226394c4ad84cd6059a6639/packages/grpc-js/src/metadata.ts#L71) ). Currently the generated...
Sometimes the output of 'svn info' contains non-English labels, so there is no 'Revision' Solution is to use 'svn info --xml'
```rust #[derive(Debug, Deserialize)] struct RpcResponse { jsonrpc: MustBe!("2.0"), id: usize, result: RS, } ``` generates error: `derive` cannot be used on items with type macros
I spent some time debugging why rate limiter allowed total `n` larger than `max_burst` within first minute when using `Quota::per_minute(max_burst)`. It seems this is actually an allowed and correct behavior...
Looks like Tardis is using old `futures.order_book` channel for `gate-io-futures`, e.g. [2023-09-01 feed](https://api.tardis.dev/v1/data-feeds/gate-io-futures?from=2023-09-1) According to [this article](https://www.gate.io/article/19776) it should be possible to switch into `futures.order_book_update`, similarly as is already used...
Looks like the proper way to ensure single-pod access to volume is using a new `ReadWriteOncePod` [access mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) introduced [here](https://kubernetes.io/blog/2021/09/13/read-write-once-pod-access-mode-alpha/) in Kubernetes 1.22 It would be nice to have this...