Canalplan Bug Tracker



Anonymous Login
2018-04-27 06:28 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000406Canalplan Route Planningpublic2018-04-07 09:30
Reportercanalplan_14892 
Assigned ToNick Atty 
PriorityhighSeveritycrashReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformPCOSwindows 7OS Version
Product VersionProduct Build 
Target VersionFixed in Version 
Summary0000406: No longer able to use the planner which I have used for years
DescriptionERROR
Canal - an error has occurred:
A Signal was trapped
canerr.c:375::The signal alarm was trapped
This happened at Sun Mar 4 12:13:25 2018 in line 273 of "../modules/load_ring.can"
pi = placeinfo('$'+k.place1)
Steps To Reproducelogin
enter route info for start at braunston chandlers and finish at braunston chandlers use warwick ring
Tagsroute planning
Attached Files

-Relationships
has duplicate 0000410closed Furthest Route not possible 
related to 0000407closedNick Atty Route planner not working since late morning. 
related to 0000408closedNick Atty Route Planning error message 
+Relationships

-Notes

~0001591

Stephen Atty (administrator)

Can you tell us which ring you were trying to load.

The rest of route planning seems to be working OK.

~0001592

canalplan_14892 (reporter)

Warwickshire ring

~0001593

Stephen Atty (administrator)

I can reproduce it.

We're also getting errors in the server error log:

Sun Mar 4 11:09:14 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:11:36 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:24:41 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:25:15 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:27:30 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:27:56 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:28:09 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:28:26 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:31:05 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:37:18 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 11:38:30 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/furthest_place.can, line 123
Sun Mar 4 11:39:06 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/furthest_place.can, line 123
Sun Mar 4 11:39:29 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/furthest_place.can, line 123
Sun Mar 4 11:59:37 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/furthest_place.can, line 180
Sun Mar 4 12:00:03 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/furthest_place.can, line 180
Sun Mar 4 12:13:25 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273
Sun Mar 4 12:32:35 2018 ./canal /webstuff/canalplan/cgi-bin/../cgi-bin/canal.can: A Signal was trapped - canerr.c:375::The signal alarm was trapped - file ../modules/load_ring.can, line 273

~0001594

Stephen Atty (administrator)

The code hasn't changed since last year so it must be something to do with the variant route code change

~0001596

Nick Atty (administrator)

Thanks for providing an example as my first tests from other reports all worked. The variant route changes should all have been walled off as they weren't perfect - I suspect a data problem, but am investigating.

~0001597

Nick Atty (administrator)

Something obscure has gone wrong when I changed the route calculation code to - supposedly - work better. It's very hard to work out exactly what and only affects a subset of routes. I've reverted to the older version of the code until I can get it working properly - and at least I have a good test case now!

~0001610

Nick Atty (administrator)

As this is the main bug for this - a few more details:
a) I over-reverted the source, meaning some other functions stopped working. Fixed that 6pmish yesterday.
b) I believe I have tracked the bug down and fixed it - a very trivial typo in the route planning code - but will wait until I am in close supervision before releasing it. Certainly the example route here now works perfectly with the development code (which is much better in several ways than that currently live - at least, it is when it works!).

~0001688

Autoclose (administrator)

Closing automatically, stayed too long in feedback state. Feel free to re-open with additional information if you think the issue is not resolved.
+Notes

-Issue History
Date Modified Username Field Change
2018-03-04 12:22 canalplan_14892 New Issue
2018-03-04 12:22 canalplan_14892 Tag Attached: route planning
2018-03-04 12:26 Stephen Atty Assigned To => Nick Atty
2018-03-04 12:26 Stephen Atty Status new => assigned
2018-03-04 12:27 Stephen Atty Note Added: 0001591
2018-03-04 12:30 canalplan_14892 Note Added: 0001592
2018-03-04 12:33 Stephen Atty Note Added: 0001593
2018-03-04 13:42 Stephen Atty Note Added: 0001594
2018-03-04 19:51 Stephen Atty Relationship added related to 0000407
2018-03-05 06:55 Stephen Atty Relationship added related to 0000408
2018-03-07 08:08 Nick Atty Note Added: 0001596
2018-03-07 09:56 Nick Atty Relationship added has duplicate 0000410
2018-03-07 09:58 Nick Atty Note Added: 0001597
2018-03-07 09:58 Nick Atty Status assigned => resolved
2018-03-07 09:58 Nick Atty Resolution open => fixed
2018-03-08 07:36 Nick Atty Note Added: 0001610
2018-04-07 09:30 Autoclose Note Added: 0001688
2018-04-07 09:30 Autoclose Status resolved => closed
+Issue History