Bug? /usr/bin/bitcoind ""

[mizerydearia]

When I execute

Code:

/usr/bin/bitcoind

bitcoin daemon starts as expected.

When I execute

Code:

/usr/bin/bitcoind ""

error: couldn't connect to server

How come?  Is this a bug?

Satoshi: May we have a bug tracking system please? (size reduced since it was noticed by satoshi and is no longer necessary to stand out, which was meant as a bit humorous anyhow.)

Workaround for my gentoo linux init script:

Code:

BITCOIN_OPTS="-min"

which will then execute as `bitcoind "-min"`

[1713881685]

1713881685

[1713881685]

1713881685

[1713881685]

1713881685

[1713881685]

1713881685

[1713881685]

1713881685

[1713881685]

1713881685

[LZ]

So we have to choose something. May be Mantis?

[mizerydearia]

I sent sourceforge-based message to Satoshi suggesting enabling MantisBT or Trac.  Perhaps he will notice it.

[nelisky]

When I execute

Code:

/usr/bin/bitcoind

bitcoin daemon starts as expected.

When I execute

Code:

/usr/bin/bitcoind ""

error: couldn't connect to server

How come?  Is this a bug?

Satoshi: May we have a bug tracking system please?

Workaround for my gentoo linux init script:

Code:

BITCOIN_OPTS="-min"

which will then execute as `bitcoind "-min"`

How is this a bug? I may be reading it completely wrong but:

Code:

/usr/bin/bitcoind

starts the daemon whereas

Code:

/usr/bin/bitcoind ""

calls the rpc method "" in the running daemon which is not there, so you get the can't connect. If it were there you'd get:

Code:

error: {"code":-32601,"message":"Method not found"}

[Gavin Andresen]

I agree with nelisky-- not a bug.  Here's what the unix cat command has to say about "":

Code:

> cat ""
cat: : No such file or directory

[satoshi]

I don't know anything about any of the bug trackers.  If we were to have one, we would have to make a thoroughly researched choice.

We're managing pretty well just using the forum.  I'm more likely to see bugs posted in the forum, and I think other users are much more likely to help resolve and ask follow up questions here than if they were in a bug tracker.  A key step is other users helping resolve the simple stuff that's not really a bug but some misunderstanding or confusion.

I keep a list of all unresolved bugs I've seen on the forum.  In some cases, I'm still thinking about the best design for the fix.  This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them.

[BioMike]

Maybe, they could be made sticky?

[nelisky]

I don't know anything about any of the bug trackers.  If we were to have one, we would have to make a thoroughly researched choice.

We're managing pretty well just using the forum.  I'm more likely to see bugs posted in the forum, and I think other users are much more likely to help resolve and ask follow up questions here than if they were in a bug tracker.  A key step is other users helping resolve the simple stuff that's not really a bug but some misunderstanding or confusion.

I keep a list of all unresolved bugs I've seen on the forum.  In some cases, I'm still thinking about the best design for the fix.  This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them.

There are many, many bug trackers out there, and I've worked with a good bunch of them. The good thing about any of these is organization, and preventing other users from posting duplicate bug reports (well, to the point where the user looks for them first ).

But what I would really see improving things as we go on is git (or bazaar, or another decentralized source tracking system) and a door to give satoshi patches for consideration. This goes for both bugs and enhancements. In the end, as long as the sole keeper or the bitcoin key is satoshi, we just need whatever means of communication he feels better with. Forums, you say? Well, good enough, I guess.

But something like trac (http://trac.edgewall.org/) would really help keeping things organized, and I'm sure everyone would appreciate it.

[mizerydearia]

I agree with using something like trac or mantisbt.  I suggest we try one of those two and if it helps improve things, then continue using it.  Otherwise it it doesn't seem to work, we still have the forum and nothing is lost.

Also, since `bitcoind ""` is not a bug, then for my gentoo linux ebuild init script to exec as that (dependent on /etc/conf.d/bitcoin containing BITCOIN_OPTS="") is the bug and I will fix that.
Fixed!

[LZ]

As I know Trac is not so multilingual as MantisBT.
So I prefer MantisBT, moreover, I already used it.
But if Satoshi prefer forum - we will use forum.

[nimnul]

I vote for Trac.

[mizerydearia]

As long as Bitcoin community doesn't contain 10,000+ developers, trac seems suitable.
Trac can communicate directly with the SVN repository and track live changesets that are linked to ticket IDs.
http://retrospectiva.org/ looks interesting and it is based on ror, therefore it is obviously a serious bug tracker for adults

[nelisky]

As I know Trac is not so multilingual as MantisBT.
So I prefer MantisBT, moreover, I already used it.
But if Satoshi prefer forum - we will use forum.

You mean multilingual as in programming languages or spoken languages? Because for the latter I think it's in everyone's benefit we stick to English, and as for the former, I don't see how that can be an issue.

I never used MantisBT, but I'm always up for learning something new. Having said that, the one most people are comfortable with would be my first choice.

[LZ]

I am about interface languages. Yes, most reports should be in English.
But an interface in the native language - it is very nice. Do you agree?

[nelisky]

I am about interface languages. Yes, most reports should be in English.
But an interface in the native language - it is very nice. Do you agree?

Well, I don't know what your native language is, but most tech terms don't have real translations to Portuguese, and instead translators use some sound-alike replacement that is usually both lame and wrong. I'll take english for any multi-lingual computer related project, thank you

But I understand that often people's grasp of the English language is less than perfect, and makes their life easier to have native language interfaces, so yeah, I agree, but my interface will remain in English, regardless.

[LZ]

We use English, not because it is a certain standard, so it is not. But because it is more common.