Re: Missing context for Ruby errors

2017-09-07 Thread Sam Ruby
On Sat, Jun 10, 2017 at 10:57 AM, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: >> On 10 June 2017 at 15:20, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: Hard to trace entry in error.log: App 11526 stderr: _ERROR TypeError: Cannot read proper

Re: Missing context for Ruby errors

2017-06-12 Thread sebb
On 12 June 2017 at 11:28, Sam Ruby wrote: > On Mon, Jun 12, 2017 at 5:29 AM, sebb wrote: >> On 12 June 2017 at 03:36, Sam Ruby wrote: >>> On Sun, Jun 11, 2017 at 7:16 PM, sebb wrote: On 11 June 2017 at 00:14, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: >> On 10

Re: Missing context for Ruby errors

2017-06-12 Thread Sam Ruby
On Mon, Jun 12, 2017 at 5:29 AM, sebb wrote: > On 12 June 2017 at 03:36, Sam Ruby wrote: >> On Sun, Jun 11, 2017 at 7:16 PM, sebb wrote: >>> On 11 June 2017 at 00:14, Sam Ruby wrote: On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: > On 10 June 2017 at 23:20, Sam Ruby wrote: >> On Sa

Re: Missing context for Ruby errors

2017-06-12 Thread sebb
On 12 June 2017 at 03:36, Sam Ruby wrote: > On Sun, Jun 11, 2017 at 7:16 PM, sebb wrote: >> On 11 June 2017 at 00:14, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: On 10 June 2017 at 23:20, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: >> On 10

Re: Missing context for Ruby errors

2017-06-11 Thread Sam Ruby
On Sun, Jun 11, 2017 at 7:16 PM, sebb wrote: > On 11 June 2017 at 00:14, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: >>> On 10 June 2017 at 23:20, Sam Ruby wrote: On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: > On 10 June 2017 at 17:22, Sam Ruby wrote: >> On Sa

Re: Missing context for Ruby errors

2017-06-11 Thread sebb
On 11 June 2017 at 00:14, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: >> On 10 June 2017 at 23:20, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: On 10 June 2017 at 17:22, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: >> On 1

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 6:39 PM, sebb wrote: > On 10 June 2017 at 23:20, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: >>> On 10 June 2017 at 17:22, Sam Ruby wrote: On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: > On 10 June 2017 at 16:58, Sam Ruby wrote: >> On S

Re: Missing context for Ruby errors

2017-06-10 Thread sebb
On 10 June 2017 at 23:20, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: >> On 10 June 2017 at 17:22, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: On 10 June 2017 at 16:58, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: >> On

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 6:15 PM, sebb wrote: > On 10 June 2017 at 17:22, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: >>> On 10 June 2017 at 16:58, Sam Ruby wrote: On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: > On 10 June 2017 at 15:57, Sam Ruby wrote: >> On

Re: Missing context for Ruby errors

2017-06-10 Thread sebb
On 10 June 2017 at 17:22, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: >> On 10 June 2017 at 16:58, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: On 10 June 2017 at 15:57, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: >> On

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 12:05 PM, sebb wrote: > On 10 June 2017 at 16:58, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: >>> On 10 June 2017 at 15:57, Sam Ruby wrote: On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: > On 10 June 2017 at 15:20, Sam Ruby wrote: >> On

Re: Missing context for Ruby errors

2017-06-10 Thread sebb
On 10 June 2017 at 16:58, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: >> On 10 June 2017 at 15:57, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: On 10 June 2017 at 15:20, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: >> Har

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 11:48 AM, sebb wrote: > On 10 June 2017 at 15:57, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: >>> On 10 June 2017 at 15:20, Sam Ruby wrote: On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: > Hard to trace entry in error.log: > > App 115

Re: Missing context for Ruby errors

2017-06-10 Thread sebb
On 10 June 2017 at 15:57, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: >> On 10 June 2017 at 15:20, Sam Ruby wrote: >>> On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: Hard to trace entry in error.log: App 11526 stderr: _ERROR TypeError: Cannot read property 'prop

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 10:27 AM, sebb wrote: > On 10 June 2017 at 15:20, Sam Ruby wrote: >> On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: >>> Hard to trace entry in error.log: >>> >>> App 11526 stderr: _ERROR TypeError: Cannot read property 'proposal' of null >>> >>> The above error was fixed by

Re: Missing context for Ruby errors

2017-06-10 Thread sebb
On 10 June 2017 at 15:20, Sam Ruby wrote: > On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: >> Hard to trace entry in error.log: >> >> App 11526 stderr: _ERROR TypeError: Cannot read property 'proposal' of null >> >> The above error was fixed by cf054fd >> >> However finding the location of the erro

Re: Missing context for Ruby errors

2017-06-10 Thread Sam Ruby
On Sat, Jun 10, 2017 at 9:43 AM, sebb wrote: > Hard to trace entry in error.log: > > App 11526 stderr: _ERROR TypeError: Cannot read property 'proposal' of null > > The above error was fixed by cf054fd > > However finding the location of the error is not trivial, as there is > no obvious context.

Missing context for Ruby errors

2017-06-10 Thread sebb
Hard to trace entry in error.log: App 11526 stderr: _ERROR TypeError: Cannot read property 'proposal' of null The above error was fixed by cf054fd However finding the location of the error is not trivial, as there is no obvious context. Most other Ruby errors are reported with a stack trace and