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
It is not possible to get logs from js-waku retrospectively (env variable should be set and node re-run).
User Story
As a consumer of js-waku lib, I want to be able to get logs, so that I can read them or share with other people.
As Waku CC, I want to be able to easily navigate logs that are shared to me or that I retrieved from debugging.
Proposed Solution / Feature Design
Provide API to trigger during run time in Browser to download logs from js-waku in an application. optional - For NodeJS allow to save files into a file.
Example: waku.dumpLogs() -> triggers download of a file in browser.
Add configuration to js-waku that will allow to change verbosity level - add verbosity option to createLightNode:
env is set AND option provided - use verbosity and print logs;
env is set AND no option provided - print logs with default verbosity;
env is off AND no option - no logs;
env is off AND option provided - print logs;
The text was updated successfully, but these errors were encountered:
Description
It is not possible to get logs from
js-waku
retrospectively (env variable should be set and node re-run).User Story
Proposed Solution / Feature Design
Provide API to trigger during run time in
Browser
to download logs fromjs-waku
in an application.optional - For
NodeJS
allow to save files into a file.Example:
waku.dumpLogs()
-> triggers download of a file in browser.Add configuration to
js-waku
that will allow to change verbosity level - addverbosity
option tocreateLightNode
:env
is set AND option provided - use verbosity and print logs;env
is set AND no option provided - print logs with default verbosity;env
is off AND no option - no logs;env
is off AND option provided - print logs;The text was updated successfully, but these errors were encountered: