-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
```
What steps will reproduce the problem?
1. trace( JSON.encode( ) );
What is the expected output? What do you see instead?
Like Date instance (see issue #2), there is no standard XML encoding syn…
-
Problem statement
---
As ZetaChain connects more blockchains the `addresses.json` is at risk of becoming bloated and useless. The current design is good enough for maintaining a small set of blockch…
-
It will make it possible to define parameters in one place and then use them throughout the package. This can be useful for kip offsets. When updating the kip, it will be possible to change only the v…
-
This is the current implementation of writing metadata in JSON format for ingest into HuBMAP infrastructure:
```python
def extract_metadata_write_json(mdata: mudata.MuData, output_json: Path):
…
-
In the `stream` endpoint, the optional `bitrate` parameter does not specify the units. I assume based on the code base it is in **kbps**? In the docs the complete description is `max bitrate for trans…