Looks great, thanks for the heads-up!
Are you absolutely sure the feature is not on mainnet? The proposal #127461 contains the feature:
Execution,Runtime: Add fetch_canister_logs stub to the management canister API
itās not available on application subnets, even if the feature has been merged. Also, my fix is merged and will be in the next release.
1 Like
Thanks for the feedback and, looking forward to next release!
Tried with last version of agent-js, the error message has been improved, which is clear now.
Cannot fetch logs. | Call failed: Canister: aaaaa-aa Method: fetch_canister_logs (query) āStatusā: ārejectedā āCodeā: āCanisterErrorā āMessageā: āIC0504: fetch_canister_logs API is not enabled on this subnetā
1 Like
this feature is not enabled for mainnet, see flag and is going to be available in DFX local run first.
I assumed it was live on mainnet because the related proposal didnāt specify that it wasnāt active, and I also naively assumed it had little value being deployed only locally therefore assumed that it should had been proposed for mainnet.
Thanks for pointing the flag; I should enable it in my Docker image.
I guess no but, do we already have an ETA for proposing to activate this on mainnet?
I guess no but, do we already have an ETA for proposing to activate this on mainnet?
thereās no specific ETA at the moment, some implementation work still have to be done and DFX integration.
we may also want to hear some dev feedback from local dfx usage experience and only then decide on enabling it on mainnet.
It would be cool not only to tailor this for dfx users but also for developers on the IC in general. For example, I donāt use dfx.
However, I have implemented the feature in Juno. Iām happy to provide feedback or quickly implement any features if interested. Let me know.
1 Like
How does dfx obtain the logs if this feature is not available on mainnet? Because dfx canister --ic logs <canister id> definitely works on mainnet.
Ummm the logs feature is available on mainnet.
1 Like