Quantcast

No public bug tracker?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

No public bug tracker?

Yuri
Your bug tracker http://www.sqlite.org/src/rptview?rn=1 doesn't accept
public submissions.
A few weeks ago I reported (in this ML) the bug with blob handle being
invalidated by the writes into unrelated tables.
fossil timeline doesn't  show this bug as fixed, and the above bug site
doesn't show it too.

Is there anything to assure that this bug isn't forgotten?

A few days ago I reported the problem with configure script and thread
safety options. configure option --enable-threadsafe only supports two
values for SQLITE_THREADSAFE, 0 and 1, while documentation says that the
allowed values are 0,1,2. There was no answer, while this appears to be
a valid problem.

Isn't it better to have a separate bug report for every issue?

Yuri

_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Simon Slavin-3

On 21 Mar 2017, at 12:00am, Yuri <[hidden email]> wrote:

> Isn't it better to have a separate bug report for every issue?

You can report bugs by posting here.  The development team will see them.

It sometimes takes a little time to get a reaction while they discuss things between themselves to figure out what to do.

Simon.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Joshua J. Kugler
In reply to this post by Yuri
On Monday, March 20, 2017 5:00:21 PM AKDT Yuri wrote:

> Your bug tracker http://www.sqlite.org/src/rptview?rn=1 doesn't accept
> public submissions.
> A few weeks ago I reported (in this ML) the bug with blob handle being
> invalidated by the writes into unrelated tables.
> fossil timeline doesn't  show this bug as fixed, and the above bug site
> doesn't show it too.
>
> Is there anything to assure that this bug isn't forgotten?
>
> A few days ago I reported the problem with configure script and thread
> safety options. configure option --enable-threadsafe only supports two
> values for SQLITE_THREADSAFE, 0 and 1, while documentation says that the
> allowed values are 0,1,2. There was no answer, while this appears to be
> a valid problem.
>
> Isn't it better to have a separate bug report for every issue?

If you go here:

https://www.sqlite.org/src/login

You can see you can log in (if you have an account), or:

"Visitors may enter anonymous as the user-ID with the 8-character hexadecimal
password shown below."

j

--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
[hidden email] - Jabber: [hidden email]
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Yuri
On 03/20/2017 17:20, Joshua J. Kugler wrote:
> If you go here:
>
> https://www.sqlite.org/src/login
>
> You can see you can log in (if you have an account), or:
>
> "Visitors may enter anonymous as the user-ID with the 8-character hexadecimal
> password shown below."


sqlite.org/src/login  shows that I am logged in, but the bug site says I am not logged in. I am not sure if this is intentional. I assumed it was.

Yuri

_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Yuri
In reply to this post by Simon Slavin-3
On 03/20/2017 17:11, Simon Slavin wrote:
> You can report bugs by posting here.  The development team will see them.
>
> It sometimes takes a little time to get a reaction while they discuss things between themselves to figure out what to do.

Does this mean that this issue will be fixed:

 > A few days ago I reported the problem with configure script and
thread safety options. configure option --enable-threadsafe only
supports two values for SQLITE_THREADSAFE, 0 and 1, while documentation
says that the allowed values are 0,1,2. There was no answer, while this
appears to be a valid problem.


?


Yuri

_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Simon Slavin-3

On 21 Mar 2017, at 2:25am, Yuri <[hidden email]> wrote:

> Does this mean that this issue will be fixed:

Not necessarily.  It does mean that the development team will know about it.  They may decide it’s not a bug, or that it’ll take a long time to fix, or have to decide whether to change the documentation or the program.  Or have something better to do.

Whichever it is, there’s no need to report the issue again.

Simon.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No public bug tracker?

Dominique Devienne
In reply to this post by Yuri
On Tue, Mar 21, 2017 at 1:23 AM, Yuri <[hidden email]> wrote:

> On 03/20/2017 17:20, Joshua J. Kugler wrote:
>
>>
>> sqlite.org/src/login  shows that I am logged in, but the bug site says I
> am not logged in. I am not sure if this is intentional. I assumed it was.


It is intentional indeed. SQLite is public domain, but not really OSS in
the traditional sense.

You report issues on this mailing list, and the SQLite dev will create bugs
report in the tracker,
but only for those real bugs which are not user-error, or on older versions
of SQLite and already fixed, etc...

But you'll see that the SQLite dev-team, with Dr Richard Hipp at its head,
are very good are picking up real bugs, and fix them in record time most
time. FWIW. --DD
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Loading...