History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RUBY-1432
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Roman Chernyatchik
Reporter: Randy Puro
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Ruby

console log filter doesn't recognize stack trace with relative file paths

Created: 25 Feb 08 23:14   Updated: 29 Feb 08 19:07
Component/s: Rails
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File development.log (7 kb)
2. Text File test.log (2 kb)

Image Attachments:

1. screenshot-1.jpg
(107 kb)

2. screenshot-2.jpg
(320 kb)
Environment: osx

Build: 14,330


 Description  « Hide
The rails server produces stack traces with file paths relative to the rails root for those files within the rails project. The console log filter does not recognize these relative file paths, and therefore does not autolink you to the file source as it should (and as would be the most likely files you'd want to jump to).

 All   Comments   Work Log   Change History      Sort Order:
Randy Puro - 25 Feb 08 23:16
oops - using plugin version 1.0.14330 (which I mistakenly put in the build number).

Oleg Shpynov - 27 Feb 08 15:47
Hello, Randy!
Could you please attach stacktrace where you experience such a problem?

Randy Puro - 27 Feb 08 19:22
Sample log file from running the regular ruby script/server Run Configuration. The second 2 lines of the stack trace aren't autolinked (and they're the relevant lines since they're the files in the project). See attached screenshot. I see similar behavior for unit tests.

Randy Puro - 27 Feb 08 19:24
Missing autolinking for files in the project

Randy Puro - 27 Feb 08 19:29
Similar behavior in for a test run. Note, some test runs report full file names, while others report some project relative file names.

Randy Puro - 27 Feb 08 19:30
screen shot for test run