File Line column identification going to wrong file.

[Justin Julicher]

• Improved file line/column identification for deployment errors where the line and column numbers are encoded into the error message instead of being reported in a first-class manner.

In the latest you mention the above update however it’s going to the wrong file. E.g:

The error line:

‌

‌

C:\Users\justinj\GRE Salesforce Phase One\force-app\main\default\classes\AmendmentsToBeApprovedController.cls
     Error:(34, 58) Dependent class is invalid and needs recompilation:     Class ApprovalProcessTrackedChangeManager : Method does not exist or incorrect signature: void      getSObjectsByRelationshipIds(Schema.SObjectType, String, Set<Id>, Set<String>) from the type DynamicSObjectSelector

‌

would go to AmendmentsToBeApprovedController and not the ApprovalProcessTrackedChangeManager which has the error.

Let me know if you need anything else.

[Scott Wells]

Can you provide the raw error output from a debug log? Basically what IC2 now does is if it finds an error message of the form "line XXX, column YYY: errorMessage" when no explicit line/column information is provided, it uses the line/column information from the message. I'd like to see this reported error to see what's going on.

[Justin Julicher]

What debug setting do I need to for that log?

[Scott Wells]

Enable debug logging for metadata deployment, reproduce the deployment failure, and shoot over the resulting log. I'll be looking for the raw error as reported by the server, and IC2 should also log when it extracts the line/column/message components from that raw error.

[Scott Wells]

Issue tracker grooming. Deployment error reporting has changed quite a bit with the change to sf and similar. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.