Paul Liu
Paul Liu
**Problem** One application often has more than one canisters, so it makes sense to donate from a single allocation to a group of canisters when any one of them runs...
If we change `gcc` in [this line of pilicl](https://github.com/IntelLabs/flrc-lib/blob/master/scripts/linux/pilicl.in#L89) to `icc`, then `pillar2c` would fail due to a parsing error like this: ``` Program failed to parse at line 3419....
When compiling benchmarks in [flrc-benchmarks], if we enable vectorization (by doing `VEC=y make`), then there are two problems with `pillar2c` (assuming we still use `gcc` for the macro expansion): 1....
If some asset is uploaded to the asset canister under name `api/xyz`, then requesting it through icx-proxy will result in 400 error, which happens on both local dfx deployment and...
The python oneliner in README computes CRC, but if the result contains lower-case letter, it will not be recognized as a valid CanisterId, which leads to the following error when...
Looks like identity.ic0.app is using ed25519 and its seed phrase is not recognized by keysmith. Any plan to support this kind of interoperability?
At the moment, in building sdk and dfx, we fetch pre-built canister binaries just as the official sdk build does. Ideally they should all be built from source.
Here is a laundry list. Welcome suggestions! - [x] Include vessel - [x] Include ic-repl - [ ] Include ic-ref - [ ] Build wallet and asset canisters from source...