You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Wallet and Walrus config paths are printed to the console in case of error.
Example:
#...
Caused by:
running the command exited with error: 2024-08-21T12:41:29.735851Z INFO walrus: running in JSON mode
2024-08-21T12:41:29.735925Z INFO walrus_service::client::cli_utils: using Walrus configuration from '/home/kos/.walrus/client_config.yaml'
2024-08-21T12:41:29.735979Z INFO walrus_service::client::cli_utils: Using wallet configuration from /home/kos/suibase/workdirs/testnet/config/client.yaml
2024-08-21T12:41:29.737098Z INFO walrus_service::client::cli_utils: using RPC URL setin wallet configuration
Error: the specified Walrus system object 0x0e37ebae146052248fef02853b39e05b75e8c6d22a074db170aad053429618ba does not exist; make sure you have the latest configuration and you are using the correct Sui network
It would be good to have the Walrus Site Builder config path there as well, for example:
(time) INFO walrus_service::client::cli_utils: Using site-builder configuration from ./site-builder.yaml
The motivation here is that with this number of config files, it's easy to accidentally mix up the paths, and this change can help to investigate the issue.
Component
site-builder
Code of Conduct
I agree to follow this project's Code of Conduct.
The text was updated successfully, but these errors were encountered:
Tzal3x
changed the title
[Feature]: Add Walrus Site Builder config path to the error output
Add Walrus Site Builder config path to the error output
Nov 14, 2024
Description
Currently Wallet and Walrus config paths are printed to the console in case of error.
Example:
It would be good to have the Walrus Site Builder config path there as well, for example:
The motivation here is that with this number of config files, it's easy to accidentally mix up the paths, and this change can help to investigate the issue.
Component
site-builder
Code of Conduct
The text was updated successfully, but these errors were encountered: