ABCDEFGHIJKL
1
IDContextOSTest #Telegram reporting linkPriorityType DescriptionAddressed it?ActionLast time reviewedNotes
2
I1wallet713Windows-https://t.me/c/1679402521/1235MediumBUGwallet is not reading properly balances after migration from v2/v3 CLI < this one is worrying most.NoDebug Wallet713 to output logs2022-02-08We need to ask the logs from people in order to debug this efficiently. Walet713 is not producing logs
- wallet713 has an outdated header version than v3. That is probably causing the problems
- Related to I22
3
I2wallet713Windows-https://t.me/c/1679402521/1235Warningdefault config file requires manual steps to connect to local nodeYes-2022-01-20- We can add update the instructions so the users know that they need to update the configuration file
- We can automatically generate new configuration files for the users
4
I3wallet713Windows-https://t.me/c/1679402521/1235Warningdefault config file is not listening on foreign/owner API while listening on epic-box only (user should be able to turn on and off listeners in UI, it is possible to listen on epic-box and standard API at the same time)Yes-2022-01-20- We can add update the instructions so the users know that they need to update the configuration file
- We can automatically generate new configuration files for the users
5
I4Epic-box
(wallet 713)		Windows-https://t.me/c/1679402521/1235MediumCommentepic-box service* is now turned off and we can't test transactions using this service (really important part of the whole v3 update)NoWe need to clarifiy first who will build and run the server for the epic box.2022-02-08- Epic disabled the server since they haven't released v3 yet
- BA will talk to Epic to define who will run the server for the epic box. While this is not defined this issue wil remain on the backlog
- Blacktyger asked Epic to use their AWS account and Max approved it. Blacktyger is returning today (2022-01-31)
6
I5wallet713Windows-https://t.me/c/1679402521/1235Commentwallet713 toml file is completely different than CLI, even same options have different variables - this could be worth to consider to merge those files or produce more readable wallet713.toml file after installation.Yes-2022-01-20- We can add update the instructions so the users know that they need to update the configuration file
- We can automatically generate new configuration files for the users
7
I6node v3Windows-https://t.me/c/1679402521/1236CommentUpdating process from v2 to v3 on floonet requires changes in foundation.json file name, .bat relevant for MainnetYes-2022-01-25- We can add update the instructions so the users know that they need to update the configuration file
- Eric updated the instructions on Drive
8
I7node v3Windows-https://t.me/c/1679402521/1236MediumCommentUpdating process from v2 to v3 may require changes in logging level naming in epic-server.tomlWIPBuild Windows Wallet binaries
Test Windows and Linux binaries		2022-02-08- We added instruction on the test instructions
- We are working on making v3 also accept v2 values
9
I8node v3Windows-https://t.me/c/1679402521/1236MediumCommentNodes are having small number of peers (1-2) for the first hours of connection, worth to monitor further.WIPBuild Windows Wallet binaries
Test Windows and Linux binaries		2022-02-08- This is a problem with the nodes. Needs further investigation
- Eric is keeping track of the testers' reports
- Might be related to I10
- Whenever a connection between v3 nodes and peers fails, the time it takes for it to try again is too long. We can decrease this time and this might fix this problem
10
I9wallet713Windows 10Test #05 Common Step 3https://t.me/c/1679402521/1141CommentWallet713 reports a listener was "started" but when I do "netstat -ano | find "13415" in command prompt it doesn't find the application using port 13415. The same command ran after starting the V3 CLI does find the V3 CLI wallet app using port 13415
The attached wallet log is only for the V3 CLI wallet, not the 713 wallet. I think we are still waiting to see how the 713 wallet produces a log.		Yes-2022-01-20- We just need some additional configuration in the toml file
- We need to update the instructions.
11
I10node v3Windows Server 2019-https://t.me/c/1679402521/1087HighBUGHIGH IMPORTANCE
endless 'waiting for peers' status, 0-2 peers connected at most, having problem to sync again after gentle reboot.
closing server, removing peer directory from chain_data and starting again helps. This is old hack that is often used till today on our Mainnet.
Although in our case it will help sync, I still can get 1 max 2 peers at most (before update was stable 9 to 11) - but this may be caused by our floonet network condition at the momentedited 10:44		Yes---2022-02-02- I can see the following error message in the logs: "an established connection was aborted by the software in your host machine"
- Related to I8
- We were able to replicate the issue using docker containers and emulating network issues (bad handshaking, delay and package loss)
- Mapped mos of connection issues and started adddressing them
- Connection issue
- This problem happens when v2 nodes and the v3 server talk to eachother. This doesn't happen when v3 nodes are connected to the v3 server
- The problem only happens with v2 nodes in the v3 server.
12
I11nodeWindows--BugOn Windows nodes stop syncing at some point and have a total of 0 peersYes-2022-01-17- V3 code had an expected hard fork at 5800 (floonet), increased to 25800
13
I12node (v2, v3)Windows / Linux--HighBUGServer is randomly crashing due to 'ILLEGAL INSTRUCTIONS`.WIPBuild Windows Wallet binaries
Test Windows and Linux binaries		2022-02-08- 'ILLEGAL INSTRUCTIONS` happens when the targeted CPU Micro-architecture (or CPU family) doesn't support an instruction from that the binary program is using
- Apparently the problem happens when calling external dinamically linked libraries. Needs further investigation
- The problem happens on external libs. The code might not be the problem but we need to double check
- Check RandomX config files and try to recompile it
- Eric was not able to reproduce the issue on the stage server. We're testing and getting testers help to debug this one
14
I13wallet713Windows / Linux-https://t.me/c/1679402521/977WarningOn the `wallet713` REPL, using the `exit` command hangs up the programYes2022-01-24- We need to ask the logs from people in order to debug this efficiently. Walet713 is not producing logs Workaround: Ctrl + C when it happens
- User said that he is not having this problem anymore
- The bug happens if something is wrong in the config file
- We updated the instructions regarding the configuration that needs to be done
15
I14wallet713Windows / Linux--BugWallet713 is not producing logsYes2022-01-21- Related to I1
16
I15wallet713Windows / Linux--BugOne can't mine using the wallet713 instead of the default V2/V3Yes-2022-01-20- wallet 713 is using an older version of the Blockfeed with missing serialization configs
17
I16WalletWindows 10https://t.me/c/1679402521/1437LowCommentWallet v3 recovery function on already existing wallet is different than in v2

In v2 recovery wallet from seed_phrase could be done in directory with already existing wallet - that would promt about backup of wallet.seed file and proceed.
In v3 it is imposible to recovery from seed_phrase like that, first wallet_data and config file have to be removed in order to continue

v2 version seem to be way better solution		NoNeeds invetigation2022-02-08
18
I17nodeWindows 10https://t.me/c/1679402521/1448MediumWarningLow number of connected peers in EU located servers v3 compared to USA basededited 13:19
although less peers server is syncing 3x faster oO		WIPNeeds testing (I8)2022-02-08- Connection issue
- Might be related to I8 (needs testing)
19
I18nodeWindows 10https://t.me/c/1679402521/1469Bugv3 not syncing from 0Yes2022-01-24- This problem is happening when we use v2 seeds
- We haven't seen this issue happening on v3 seeds- We won't update v2 since we are working on the v3 update, which fixes the problem
20
I19nodeWindows 10https://t.me/c/1679402521/1581Bugv2 and v3 instances stuck during synchronization - headers are fully downloaded but blocks only up to height 19682 and 19194 respectively. Restarts and clearing peer directory is not helping. Test was done during seed v2 periodedited 12:16Yes2022-01-24- This problem is happening when we use v2 seeds
- We haven't seen this issue happening on v3 seeds
- We won't update v2 since we are working on the v3 update, which fixes the problem
21
I20nodeWindows 10https://t.me/c/1679402521/1611HighBUGthe cleaning out peers has stopped working for me on mainnet. thats why i asked you long time ago if there was some kind of innate ip temporary bans that occur. the onlyway for me to solve it is to use an old peers folder i keep lying around13:37WIPNeeds testing of v3 binaries2022-02-08- A peer can be banned for 3 hours for several reasons. We need to find out if this is intended behavior
- Connection issue
- This problem might be related to the "failling connection" to the seed servers. Josias addressed this problem and we are testing the binaries
22
I21nodeWindowshttps://t.me/c/1679402521/1842MediumWarningjust replacing epic.exe and foundation.json from working v2.17 to v3 will most likely fail cause of different logging level names - can we prevent this in any way? Rewrite the code that will accept either names or go back to v2 style?WIPBuild Windows Wallet binaries
Test Windows and Linux binaries		2022-02-08- Requires update to the wallet
- Related to I7
- This would make it harder on the user to rollback from v3->v2 (which is good)
- We updated the codebase to accept either name conventions
23
I22WalletWindows/Linuxhttps://t.me/c/1679402521/1852HighBugat this point wallet v3 is not reading properly balance/transactions from v2Yes---2022-01-26- v3 transactions were not showing up on v2 wallets as well
- Related to I1
- v3 CLI is capable of reading v2 CLI transactions/balances
-
24
I23Wallet713Windows 10#4https://t.me/c/1679402521/1921Warningdid as instructed and confirmed it worked. However. now my wallet713 is unsynced by the missing value of (1.33EPIC that i transferred) due to not seeing the 2nd acount.Yes2022-01-21fixed- had to manually add the 2nd account in wallet713 with 'account create account213' i thought it would just add it automatically
25
I24TOR transactionsWindows 10https://t.me/c/1679402521/2047MediumWarningUnable to receive transaction via tor probably due to default setting:socks_proxy_addr = "127.0.0.1:59050"

Changing it to socks_proxy_addr = "0.0.0.0:59050" is making sending and receiving imposible due to The requested address is not valid in its context error.

Seem like Linux does not have this problem		NoWe need to improve the configuration2022-02-08- The out-of-the-box configuration is broken and we'll need to update it
26
I25wallet713Windows/LinuxBugWallet713 is ignorring the `--log-config-path` optionYes2022-01-21- Discovered while investigating the I14
27
I26wallet713Windows/LinuxBugWallet713 is overwriting the configuration file each time it runsYes2022-01-21- Discovered while investigating the I14
28
i25walletWindows 10https://t.me/c/1679402521/2211LowWarningi got a transaction on my v3 cli , that i dont remember processing ( i never put my wallet on listen the last week).
on the kernel , it says 'none' for said transaction.
and shared transaction id is none, as if it was mined, but its not.		NoNeeds invetigation2022-02-08- Keep an eye on that happening for other people
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100