Re: Floating point exception on future entry

[John Wiegley]

> "A" == Alexis   writes:

A> Of course, I welcome the change. How do we best move forward with this?

So, I have Docker build that will create the Bugzilla on your local machine,
which you can then load the SQL into. That can then be used as the basis for
the conversion process.

I won't have time to try this until mid-March, but I'm happy to do it then. I
ask for help only in case someone has the time to do it sooner.

John

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Floating point exception on future entry

[Alexis]

Hello John Wiegley on Tuesday, 2018-01-23 at 15:17:08-0800, you wrote:
> Is anyone willing to help me set this up?

Of course, I welcome the change. How do we best move forward with this?


Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Floating point exception on future entry

[Jostein Berntsen]

On 23.01.18,19:15, Jostein Berntsen wrote:
> On 22.01.18,18: 15, John Wiegley wrote:
> > > "JB" == Jostein Berntsen  writes:
> 
> > 
> > JB> It seems like bugs.ledger-cli.org is not working. Would it be useful to
> > JB> activate the issues feature at the ledger github site so bugs can be
> > JB> reported and tracked? Now it seems it's only active for pull requests.
> > 
> > OK, issues are enabled.
> > 
> > We have over a 1,000 issues still stuck in the MySQL dump from
> > bugs.ledger-cli.org. I wonder if anyone would be willing to help extract
> > details from the important ones? I'm fine with ditching Bugzilla.
> > 
> 
> Thanks. One possible way could be to create an XLM dump of the most 
> actual bugs from the bugzilla DB and use this script to import all 
> issues to github?
> 
> https://github.com/rowanj/BugzillaMigrate
> 
> 

Another recent article:

Notes on successfully migrating 4900 bug reports from Bugzilla to GitHub 
issues - Théo Zimmermann

https://www.theozimmermann.net/2017/10/bugzilla-to-github/


Jostein


-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Floating point exception on future entry

[John Wiegley]

> "JB" == Jostein Berntsen  writes:

JB> It seems like bugs.ledger-cli.org is not working. Would it be useful to
JB> activate the issues feature at the ledger github site so bugs can be
JB> reported and tracked? Now it seems it's only active for pull requests.

OK, issues are enabled.

We have over a 1,000 issues still stuck in the MySQL dump from
bugs.ledger-cli.org. I wonder if anyone would be willing to help extract
details from the important ones? I'm fine with ditching Bugzilla.

John

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Floating point exception on future entry

[Jostein Berntsen]

On 22.01.18,07:00, Rob Napier wrote:
> The following ledger file generates a floating point exception on the 
> following command:
> 
> *x.ledger*
> 
> 2018/01/19 * Transfer to X  ; Date in the past
> Transfer:X   $1000
> Assets:Checking
> 
> 
> 2018/01/23 Transfer to Y  ; Date in the future
> Transfer:Y   $1000
> Assets:Checking
> 
> 
> *command*
> ledger -f x.ledger --no-pager -X $ reg assets
> Floating point exception: 8
> 
> This crash occurs when the final transaction is in the future (so this 
> is run on Jan 22).
> 
> * Adding --current will avoid the crash.
> * Removing "assets" will avoid the crash.
> * Removing -X $ will avoid the crash
> * Removing the first entry will avoid the crash
> 
> I can't find http://bugs.ledger-cli.org. Has it been taken down?
> 

It seems like bugs.ledger-cli.org is not working. Would it be useful to 
activate the issues feature at the ledger github site so bugs can be 
reported and tracked? Now it seems it's only active for pull requests.


Jostein

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.