Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Path names used to create manifest resource tags are not being normalized

Description

Cause appears to be a change in the behaviour of makeAbsolutePath. Suggest reverting to prior behaviour.

Conclusion

None

Activity

Show:

Dan Camper May 21, 2020 at 2:12 PM

Good to hear. I have Senthil re-running his profile job with an earlier version of client tools (7.2.x in his case – it's what he had handy).

I've just confirmed that the PR fixed the problem as well, on my dev cluster.

Jim DeFabia May 21, 2020 at 2:01 PM

I hit the same issue using Visualizer and so I switched to using 7.6.x compiler in the ECL IDE's compiler overrides.  

Dan Camper May 21, 2020 at 1:26 PM
Edited

The WU archive does not seem to contain that information. However, the Variables in the WU show two interesting items:

QueryBuilder version: community_7.8.4-1
Debug eclcc_compiler_version: 7.8.0

I thought both of those were supposed to be server-side values. Are they client-side?

Richard Chapman May 21, 2020 at 1:16 PM

It could be, if the job was submitted from a 7.8.x clienttools

Dan Camper May 21, 2020 at 1:00 PM

http://alpha_dev_thor_esp.risk.regn.net:8010/?Wuid=W20200518-104553&Widget=WUDetailsWidget

That is a 7.6.40 cluster, running a DataPatterns.Profile job (from the bundle version of DataPatterns, so there is a manifest). Going to the Resources WU tab displays an error (Exception: 5502 Cannot open resource) rather than the visualizations. Is that a manifestation of this problem?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/13768
https://github.com/hpcc-systems/HPCC-Platform/pull/13768

Created May 21, 2020 at 12:05 PM
Updated May 26, 2020 at 12:37 PM
Resolved May 21, 2020 at 1:57 PM

Flag notifications