Add listnames RPC command for dotNav#937
Conversation
|
A new build of 763fb6f has completed succesfully! |
mxaddict
force-pushed
the
add-listnames-rpc-command
branch
from
763fb6f to
868977e
Compare
|
@aguycalled should I just create an index for the dotNav names like I did for nftindex? |
sounds good |
|
Should I maybe add the name to the |
|
I'd say modifying the current index would make current clients crash when they try to read it with a different structure, unless some kind of versioning is implemented. Might be better to have a different index. |
|
Alright, makes sense.
…On Sun, Feb 27, 2022, 01:03 alex v. ***@***.***> wrote:
I'd say modifying the current index would make current clients crash when
they try to read it with a different structure, unless some kind of
versioning is implemented. Might be better to have a different index.
—
Reply to this email directly, view it on GitHub
<#937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIDAKOXJ7UDOWBGWHZJEY3U5EBVBANCNFSM5OM247TA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
A new build of 4e587d3 has completed succesfully! |
|
A new build of e32d689 has completed succesfully! |
|
A new build of 2927669 has completed succesfully! |
|
A new build of d9ba894 has completed succesfully! |
Conflicts: src/coins.cpp src/coins.h src/rpc/client.cpp src/txdb.cpp src/txdb.h src/wallet/rpcwallet.cpp
|
A new build of 455710a has completed succesfully! |
|
A new build of 61fa02a has completed succesfully! |
|
A new build of 7644855 has completed succesfully! |
|
A new build of b1f4384 has completed succesfully! |
|
after i got this error and pressed ok after starting with -nameindex=0 and then switched to -nameindex=1 further more, after i set -reindex-chainstate=1, i still get the same errors as above |
It should have rebuild the index, what does the debug.log say? |
|
@chasingkirkjufell I think I know what happened
Do you think this might have been the case? |
|
@mxaddict once i set index to true, i cannot start the wallet no matter what. |
|
Is this on windows?
…On Wed, Mar 16, 2022, 09:16 chasingkirkjufell ***@***.***> wrote:
@mxaddict <https://github.com/mxaddict> once i set index to true, i
cannot start the wallet no matter what.
2022-03-16 01:13:58 InitBlockIndex: nft index disabled
2022-03-16 01:13:58 InitBlockIndex: name index enabled
2022-03-16 01:13:58 InitBlockIndex: address index disabled
2022-03-16 01:13:58 InitBlockIndex: timestamp index disabled
2022-03-16 01:13:58 InitBlockIndex: spent index disabled
2022-03-16 01:13:58 Initializing databases...
2022-03-16 01:13:59 GUI: initializeResult : Initialization result: 0
2022-03-16 01:13:59 GUI: requestShutdown : Requesting shutdown
2022-03-16 01:13:59 GUI: shutdown : Running Shutdown in thread
2022-03-16 01:13:59 Interrupting HTTP server
2022-03-16 01:13:59 Interrupting HTTP RPC server
2022-03-16 01:13:59 Interrupting RPC
2022-03-16 01:13:59 scheduler thread interrupt
2022-03-16 01:13:59 PrepareShutdown: In progress...
2022-03-16 01:13:59 Stopping HTTP RPC server
2022-03-16 01:13:59 Stopping RPC
2022-03-16 01:13:59 Stopping HTTP server
2022-03-16 01:13:59 Stopped HTTP server
2022-03-16 01:13:59 StopNode()
2022-03-16 01:13:59 Committing 0 changed transactions (out of 0) to coin database...
2022-03-16 01:13:59 Shutdown: done
2022-03-16 01:13:59 GUI: shutdown : Shutdown finished
2022-03-16 01:13:59 GUI: shutdownResult : Shutdown result: 1
2022-03-16 01:13:59 GUI: ~NavcoinApplication : Stopping thread
2022-03-16 01:13:59 GUI: ~NavcoinApplication : Stopped thread```
—
Reply to this email directly, view it on GitHub
<#937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIDAKI72QLWPUZNAXN7XGTVAEY53ANCNFSM5OM247TA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
yep |
|
A new build of 1cf3fcf has completed succesfully! |
|
@mxaddict still the same error |
|
I see, will test it out |
|
A new build of 33fb611 has completed succesfully! |
|
A new build of 14dc474 has completed succesfully! |
|
A new build of 6cd2b4d has completed succesfully! |
|
A new build of 5e7370a has completed succesfully! |
|
A new build of 5e7370a has completed succesfully! |
4 participants
closes #924