#964
  • Created on
    2011-11-18 10:15
  • Reported by
    Vlad Dumitrescu
  • Status
    Fixed
  • Priority
    High (2)
  • Assigned to
    Vlad Dumitrescu
  • Milestone
    sprint #33
  • Plan Level
    -
  • Permission type
    Private
  • Estimate
    None/Small/Medium/Large Small
  • Due Date
    -

Attachments

Problem markers show up in the wrong place in the editor

Some of the problems listed in the Problems view will when opened in the editor show up in the wrong place ( or rather, the warning lists the wrong file)

Steps to reproduce:
1. Set clearcase view based upon CXS101289_LLVPTB_91_P21A10_110524095051
2. Start "shade --release R2C05"
3. Import and build project ups_erl.
4. In the Problems view, sort on location so that the errors on line 0 is at the top.
5. Scroll down until the first Erlang problem, that will show one file in the Resource column, and another one in the Path column.
6. Double click on the problem, this will open the file specified in the resource column, and mark the problem in it. This is however in the wrong file and the location of the error is not relevant, see attached screenshot.
User picture
  on 2011-12-13 13:12 *
By Vlad Dumitrescu
Milestone set to sprint #27 - 0.14
Milestone set to sprint #27 - 0.14
Updating tickets (#964, #969, #976, #977, #978, #979)
User picture
  on 2012-01-06 10:47 *
By Vlad Dumitrescu
Milestone changed from sprint #27 - 0.14 to sprint #28 - 0.15
Milestone changed from sprint #27 - 0.14 to sprint #28 - 0.15
Updating tickets (#917, #831, #972, #983, #978, #957, #964, #834, #935, #943, #955, #956, #916)
User picture
  on 2012-01-30 09:39 *
By Vlad Dumitrescu
Milestone changed from sprint #28 - 0.15 to sprint #29 - 0.16
Milestone changed from sprint #28 - 0.15 to sprint #29 - 0.16
Updating tickets (#937, #831, #972, #978, #957, #991, #967, #847, #858, #966, #917, #965, #964)
User picture
  on 2012-02-13 09:28 *
By Vlad Dumitrescu
Milestone changed from sprint #29 - 0.16 to backlog
Milestone changed from sprint #29 - 0.16 to backlog
Updating tickets (#859, #831, #972, #996, #995, #978, #957, #991, #847, #964, #917)
User picture
  on 2012-04-27 14:20 *
By jakobc
Cannot reproduce this in latest builds, is this fixed?
User picture
  on 2012-04-27 15:57 *
By Vlad Dumitrescu
I didn't do anything special about it, so it's possible that it's just not easy to reproduce....
User picture
  on 2012-04-27 17:37 *
By Vlad Dumitrescu
Did you check in Shade environment?

I believe the problem is that errors that occur in hrl files are assigned to the erl file that includes them.
User picture
  on 2012-06-06 21:02 *
By Vlad Dumitrescu
Priority changed from Normal (3) to High (2)
Priority changed from Normal (3) to High (2)
User picture
  on 2012-07-23 13:03 *
By Vlad Dumitrescu
Shade ticket changed from 2095.0 to 5740.0
Shade ticket changed from 2095.0 to 5740.0
User picture
  on 2012-07-24 08:50 *
By Vlad Dumitrescu
Shade set to 5740
Shade set to 5740
User picture
  on 2012-07-30 11:36 *
By Vlad Dumitrescu
Assigned to set to Vlad Dumitrescu
Milestone changed from backlog to sprint #33
Status changed from New to Ongoing
Assigned to set to Vlad Dumitrescu
Milestone changed from backlog to sprint #33
Status changed from New to Ongoing
User picture
  on 2012-07-31 09:55 *
By Vlad Dumitrescu
Status changed from Ongoing to Test
Status changed from Ongoing to Test
Can't reproduce anymore. Seems to have been fixed together with #909.

When we have hrl files included indirectly (from other hrl files) and from external libs, then we are losing track of the source (we could search for any external resource with the given path, but it can be very slow for large projects like sgsn).
User picture
  on 2012-09-13 11:49 *
By Vlad Dumitrescu
Status changed from Test to Fixed
Status changed from Test to Fixed
Updating tickets (#272, #964, #965, #1051, #1056, #1057, #1060, #1066)