[DVC]DevCoin - Official Thread - Moderated - page 358.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Unthinkingbit on October 13, 2013, 07:47:19 PM

Quote from: twobits on October 13, 2013, 07:17:59 PM

..
I told him I would work with him to try and find and fix the issue back in July. Ideally I would set up a similar build environment with the exact compiler and libraries he is using. My understanding is that the devcoin trade is not high enough to be worth putting the work in from his end to help track down the issue.

This is the big problem. A few days ago the devcoin volume was 9 btc, the lowest of all the coins, today it is 4 btc, also the lowest of all the coins:
https://mcxnow.com/exchange/DVC

Twobits and I both asked him to send a bug report, or even just say which version he's using, and haven't received a reply yet. Fixing this requires at least some more information from his end.

I'll make an account on Mcxnow and place some devcoin orders, and ask others to trade more. Hopefully that'll encourage him to provide some info.

Quote

There are also no other reports of crashing to work with.

Devcoin is running at the vircurex, cryptsy and cryptostock exchanges, along with several pools. I haven't received any crash reports from anyone and haven't seen any on this thread.

Quote

..
If you do not know the cause of the crashes you can not have any idea what would fix them. For all we know they could be from the curl version used or the way it was linked even. The rebase would be a different project then fixing a crash/bug report. To jump to that as the answer without even knowing the problem is not a wise reaction.

I agree, it's hard enough to fix problems when you have good bug reports. Without any bug report, and without even knowing what version is running, it's impossible.

It has no volume because everyone knows its going to be delisted... before it had many consecutive days of 100 million dvc traded in a row.

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: twobits on October 13, 2013, 07:17:59 PM

..
I told him I would work with him to try and find and fix the issue back in July. Ideally I would set up a similar build environment with the exact compiler and libraries he is using. My understanding is that the devcoin trade is not high enough to be worth putting the work in from his end to help track down the issue.

This is the big problem. A few days ago the devcoin volume was 9 btc, the lowest of all the coins, today it is 4 btc, also the lowest of all the coins:
https://mcxnow.com/exchange/DVC

Twobits and I both asked him to send a bug report, or even just say which version he's using, and haven't received a reply yet. Fixing this requires at least some more information from his end.

I'll make an account on Mcxnow and place some devcoin orders, and ask others to trade more. Hopefully that'll encourage him to provide some info.

Edit: The volume is usually low, but there was a big flurry of trades when delisting was announced.

Quote

There are also no other reports of crashing to work with.

Devcoin is running at the vircurex, cryptsy and cryptostock exchanges, along with several pools. I haven't received any crash reports from anyone and haven't seen any on this thread.

Quote

..
If you do not know the cause of the crashes you can not have any idea what would fix them. For all we know they could be from the curl version used or the way it was linked even. The rebase would be a different project then fixing a crash/bug report. To jump to that as the answer without even knowing the problem is not a wise reaction.

I agree, it's hard enough to fix problems when you have good bug reports. Without any bug report, and without even knowing what version is running, it's impossible.

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: Unthinkingbit on October 12, 2013, 06:28:35 PM

..
I'm sorry for not checking the warning log. The warning log is experimental, I just added it last round, and it brings up many false positives so I ended up ignoring it because I was in a hurry. In the next couple of hours I'll make it more informative so I can see which are real warnings then I'll rerun devtome for everyone.

I finished running devtome again, and edited the devtome earnings post at:
https://bitcointalksearch.org/topic/m.3322732

I also reran marketing and edited that post to be sure, but very little if anything changed there:
https://bitcointalksearch.org/topic/m.3325644

twobits

sr. member

Activity: 574

Merit: 250

Quote from: markm on October 13, 2013, 07:05:35 PM

From the start the GUI would never mine because of some kind of problem with multithreading, maybe because the libcurl or whatever we use to go get the receiver files is not thread-safe or something, we never did figure out exactly why mining would not work, instead we simply disabled mining in the GUI version, you have to use the daemon to mine.

That is the only multithreading "issue" I know of; could it be that RS has been hacking at it trying to get mining to work in the GUI or something?

I have no problem with devcoind crashing, some other coins I have made wrappers for to fire them up again when they crash, I have never bothered with devcoind because it never crashes. So I don't know what version he is running, from where, but it sounds like it isn't the version I have been running.

-MarkM-

I do know he does his own builds. He also makes and runs a 32 bit windows build. I am pretty sure using devcoin[d] as long running server is not as well tested as it is under linux. I assume he runs the daemon, but really don't know for sure. libcurl is thread safe, but the flags you use on windows vary depending on if you are statically linking it or not if I remember right. We just dont know enough to fix the issue without help from RS.

twobits

sr. member

Activity: 574

Merit: 250

Quote from: sidhujag on October 13, 2013, 06:58:05 PM

Ok cool, so do we just send him the new binaries to try to get him to replace it and see if its fixed? He was complaining about the crashing and multithreading issues so im guessing RAM consumption which MarkM was talking about... I think we can ask him as a first step to try the new binary?

Ofcourse the rebase would fix the crashes because of the bigger community testing and debugging @ BTC. However the bounty is pretty sizeable and will need to be tested by the dev to ensure no crashes... so he/she would be on it if there were any issues. Either way its a headache for RS.

He does his own builds. I told him I would work with him to try and find and fix the issue back in July. Ideally I would set up a similar build environment with the exact compiler and libraries he is using. My understanding is that the devcoin trade is not high enough to be worth putting the work in from his end to help track down the issue. There are also no other reports of crashing to work with.

The ram issue, that I had a hard time convincing anyone for months was not a memory leak is not the issue here. It comes into play only on p2pool mm blocks. The ram usage of devcoin at this time is not yet that large. As I said back in May when everyone else still thought this was an i0coin only memory leak it will eventually bite all the mm coins though. It is not a fire though.

No, it is not an 'of course' the rebase would fix the crashes. If you do not know the cause of the crashes you can not have any idea what would fix them. For all we know they could be from the curl version used or the way it was linked even. The rebase would be a different project then fixing a crash/bug report. To jump to that as the answer without even knowing the problem is not a wise reaction.

markm

legendary

Activity: 2940

Merit: 1090

From the start the GUI would never mine because of some kind of problem with multithreading, maybe because the libcurl or whatever we use to go get the receiver files is not thread-safe or something, we never did figure out exactly why mining would not work, instead we simply disabled mining in the GUI version, you have to use the daemon to mine.

That is the only multithreading "issue" I know of; could it be that RS has been hacking at it trying to get mining to work in the GUI or something?

I have no problem with devcoind crashing, some other coins I have made wrappers for to fire them up again when they crash, I have never bothered with devcoind because it never crashes. So I don't know what version he is running, from where, but it sounds like it isn't the version I have been running.

-MarkM-

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: twobits on October 13, 2013, 06:43:13 PM

Quote from: sidhujag on October 13, 2013, 08:27:57 AM

So according to RS we have 7 days to either fix dvc code or come up with a plan with timeline. Most likely have to fix otherwise it will be replaced.

The rpc hangs mentioned should have been fixed ( https://gitorious.org/devcoin/devcoin/commit/a7aad74030c36da201d526477a47693a8d1cbeeb )

One thing that is unclear to me is just what version/build is mcxnow even running? I know last I talked to RS about it, end of July, he was running a version that did not have that patch among others in it. I am not sure he ever updated.

To fix the code we really should know more exactly what is wrong with it. A bug report with the rpc commands sent and the very head and tail of the debug log would help a lot. Perhaps someone could write some code to exercise the rpc interface to see if they can get it to crash for them?

Quote from: smeagol on October 13, 2013, 12:20:21 PM

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Just a rebase of the code is not how you fix a crash. In fact at first a new rebase would be more likely to crash. We need actionable bug reports.

Ok cool, so do we just send him the new binaries to try to get him to replace it and see if its fixed? He was complaining about the crashing and multithreading issues so im guessing RAM consumption which MarkM was talking about... I think we can ask him as a first step to try the new binary?

Ofcourse the rebase would fix the crashes because of the bigger community testing and debugging @ BTC. However the bounty is pretty sizeable and will need to be tested by the dev to ensure no crashes... so he/she would be on it if there were any issues. Either way its a headache for RS.

eeh

full member

Activity: 185

Merit: 100

I'll give 500K DVC also from the next round. I'm pretty sure I'll make that much, if not, I'll buy it off an exchange and send it to the bounty winner or to whoever is collecting the payout.

twobits

sr. member

Activity: 574

Merit: 250

Quote from: sidhujag on October 13, 2013, 08:27:57 AM

So according to RS we have 7 days to either fix dvc code or come up with a plan with timeline. Most likely have to fix otherwise it will be replaced.

The rpc hangs mentioned should have been fixed ( https://gitorious.org/devcoin/devcoin/commit/a7aad74030c36da201d526477a47693a8d1cbeeb )

One thing that is unclear to me is just what version/build is mcxnow even running? I know last I talked to RS about it, end of July, he was running a version that did not have that patch among others in it. I am not sure he ever updated.

To fix the code we really should know more exactly what is wrong with it. A bug report with the rpc commands sent and the very head and tail of the debug log would help a lot. Perhaps someone could write some code to exercise the rpc interface to see if they can get it to crash for them?

Quote from: smeagol on October 13, 2013, 12:20:21 PM

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Just a rebase of the code is not how you fix a crash. In fact at first a new rebase would be more likely to crash. We need actionable bug reports.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: FinShaggy on October 13, 2013, 05:35:08 PM

Quote from: sidhujag on October 13, 2013, 03:46:14 PM

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

I'll put down at least 500,000 DVC from round 28 payout.

Updated thanks.

FinShaggy

full member

Activity: 196

Merit: 100

Google/YouTube

Quote from: sidhujag on October 13, 2013, 03:46:14 PM

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

I'll put down at least 500,000 DVC from round 28 payout.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: sidhujag on October 13, 2013, 04:00:52 PM

Quote from: smeagol on October 13, 2013, 03:51:10 PM

Quote from: sidhujag on October 13, 2013, 03:46:14 PM

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

So far for the bounty we have:
Shakezula, 1.000.000 DVC (1,000,000)
...

Great, how about you? You putting anything in? Cmon guys we need to get this done within 7 days!

SO far I got this:

sidhujag 1 million dvc
weisoq 1 million dvc
matt608 (dont know) assume 1 million dvc
shakezula 1 million dvc
notabot 1 million dvc

3-shares also next round.

Who else is going to step up to the plate here? I have a dev who's interested and knows the source. I also messaged MarkM and maybe the dev he was talking to will be interested to work right away if the bounty is big enough! if it get delisted we all probably lose half the value of our dvc's anyway just off the bat!

Please see https://bitcointalksearch.org/topic/m.3332344 for the DVC update bounty.

Can someone also add it to the bounty now page: http://www.devtome.com/doku.php?id=devcoin_bounty_now

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: smeagol on October 13, 2013, 03:51:10 PM

Quote from: sidhujag on October 13, 2013, 03:46:14 PM

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

So far for the bounty we have:
Shakezula, 1.000.000 DVC (1,000,000)
...

Great, how about you? You putting anything in? Cmon guys we need to get this done within 7 days!

SO far I got this:

sidhujag 1 million dvc
weisoq 1 million dvc
matt608 (dont know) assume 1 million dvc
shakezula 1 million dvc
notabot 1 million dvc

3-shares also next round.

Who else is going to step up to the plate here? I have a dev who's interested and knows the source. I also messaged MarkM and maybe the dev he was talking to will be interested to work right away if the bounty is big enough! if it get delisted we all probably lose half the value of our dvc's anyway just off the bat!

notabot

member

Activity: 99

Merit: 10

I will match Shakezula's 1 million dvc to update the code.

smeagol

legendary

Activity: 1008

Merit: 1005

Quote from: sidhujag on October 13, 2013, 03:46:14 PM

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

So far for the bounty we have:
Shakezula, 1.000.000 DVC (1,000,000)
...

sidhujag

legendary

Activity: 2044

Merit: 1005

Please lets get this done. I need to know who is willing to add to the bounty. I have to know what the bounty is to tell people.

smeagol

legendary

Activity: 1008

Merit: 1005

Quote from: sidhujag on October 13, 2013, 03:16:01 PM

Quote from: shakezula on October 13, 2013, 12:59:47 PM

Quote from: smeagol on October 13, 2013, 12:20:21 PM

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Ugh, that sounds like fun. Ok, I too will put in some DVC, 1 million of them, towards this bounty of updating the code.

I need some guidance I'm beginning to look at the src. Can I not just look at maybe taking a new snapshot from the latest say Namecoin which is also merge mined, or just take the latest bitcoin and add merge mining capabilities and change the settings to match devcoin settings instead of going in adding patches? Are there other specific devcoin patches (and or what reason)?

Does it make sense to essentially start the codebase from the fresh fork(either from nmc or btc), match the settings up and be done?

Jag

I recommend forking the latest i0coin code, which was newly resurrected. As for the settings, ask unthinkingbit about that. It is a bit complex.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: shakezula on October 13, 2013, 12:59:47 PM

Quote from: smeagol on October 13, 2013, 12:20:21 PM

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Ugh, that sounds like fun. Ok, I too will put in some DVC, 1 million of them, towards this bounty of updating the code.

I need some guidance I'm beginning to look at the src. Can I not just look at maybe taking a new snapshot from the latest say Namecoin which is also merge mined, or just take the latest bitcoin and add merge mining capabilities and change the settings to match devcoin settings instead of going in adding patches? Are there other specific devcoin patches (and or what reason)?

Does it make sense to essentially start the codebase from the fresh fork(either from nmc or btc), match the settings up and be done?

Jag

shakezula

sr. member

Activity: 308

Merit: 250

Quote from: smeagol on October 13, 2013, 12:20:21 PM

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Ugh, that sounds like fun. Ok, I too will put in some DVC, 1 million of them, towards this bounty of updating the code.

smeagol

legendary

Activity: 1008

Merit: 1005

Quote from: matt608 on October 13, 2013, 12:14:58 PM

I'd be up for offering some DVC towards a bounty to get the code fixed. However, I don't really know what is wrong with it and I'm not a coder. Who can help?

The code is based on bitcoin 0.3. Right now, we are at bitcoin 0.8. We need to catch up the code so it does not crash.

Topic: [DVC]DevCoin - Official Thread - Moderated - page 358. (Read 1058949 times)