fedora-copr / logdetective

Analyze logs using Language Model (LLM) and Drain template miner.
Apache License 2.0
5 stars 8 forks source link

polish readme & inform user about downloading model #12

Closed TomasTomecek closed 4 months ago

TomasTomecek commented 4 months ago

I tried current HEAD logdetective on some funky code from a friend: waku (blockchain p2p networking stack), this is what I got:

$ logdetective https://gist.githubusercontent.com/TomasTomecek/2397bb4d7382c4aea7a536e2a25ebafb/raw/9205ba71573a016b5d46a2397e2786207edfaf22/gistfile1.txt

Explanation:
[2024-01-24T15:38:25.0354050Z 2024-01-24T15:38:25.033Z waku:error:connection-manager Error dialing peer 16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L - The dial request has no valid addresses]: This error message indicates that there is a problem with dialing a peer (identified by the address '16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L') using the connection manager, because there are no valid addresses for that peer. This can occur if the peer information is not correctly configured or if the network is not reachable for that peer.

[2024-01-24T15:38:25.0355562Z 2024-01-24T15:38:25.033Z waku:info:connection-manager Dialing peer 16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L on attempt 3]: This message indicates that the connection manager is attempting to dial the peer '16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L' for the third time. This suggests that previous attempts to dial that peer have failed, which is consistent with the error message from the previous log entry.

[2024-01-24T15:38:25.0362094Z 2024-01-24T15:38:25.033Z waku:info:connection-manager Deleting undialable peer 16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L from peer store. Reason: The dial request has no valid addresses]: This message indicates that the connection manager is deleting the peer '16Uiu2HAm4ogtjMF567go92sEsWcVtqHtoaxdytxqcC4v75cWDk9L' from the peer store because there are no valid addresses for that peer, and the dial request has failed. This means that the connection manager will not attempt to connect to that peer again unless the peer information is updated with valid addresses.

[2024-01-24T15:38:25.1121866Z 2024-01-24T15:38:25.106Z waku:info:test:docker 2c5c7d120f9343048661238ba09fb8c4c11cb95cc586276e7c214103110250d1 started at 3:38:25 PM]: This message indicates that a test Docker container with the ID '2c5c7d120f9343048661238ba09fb8c4c11cb95cc586276e7c214103110250d1' has been started. This container appears to be running the Waku test suite, based on the 'waku' prefix in the log messages.

[2024-01-24T15:38:25.1124138Z 2024-01-24T15:38:25.106Z waku:info:test:node Waiting to see 'Node setup complete' in type() {...}]: This message indicates that the test suite is waiting for the 'Node setup complete' message from the Waku node before continuing with the tests. This suggests that the test suite is attempting to interact with a running Waku node.

[2024-01-24T15:38:25.1243187Z 2024-01-24T15:38:25.121Z waku:info:test:node TypeError: Cannot read properties of undefined (reading 'catch')]: This error message indicates that there is a JavaScript error in the Waku test suite with the message 'TypeError: Cannot read properties of undefined (reading "catch")'. This suggests that there is a problem with a Promise or an asynchronous function call in the test suite that is returning undefined where a Promise or a catch block is expected. This could be due to a coding error or a configuration issue in the test suite.

Based on the available information, it appears that the Waku test suite is unable to connect to a peer due to invalid or missing addresses in the peer information, which is preventing the connection manager from dialing that peer. This issue may be causing the test suite to fail with a JavaScript error related to Promise or asynchronous function calls. It is recommended to check the peer information and ensure that it contains valid addresses that the connection manager can use to dial the peer. Additionally, it may be helpful to review the JavaScript error message to determine the exact cause of the error and address any coding or configuration issues in the test suite.

not bad though I'm sure the devs would explain the error better, but as a clue it's great