Profile parsing problem
See original GitHub issueIn profile.py, the env doesn’t work if the value contains a ‘=’, the code is using simple split which does not cover this case.
for env in doc.env.split("\n"):
if env:
varname, value = env.split("=")
obj.env[varname] = value
Also when an error happens when parsing the profile file, it reports error as cannot find this profile, and the message looks like
RROR: Specified profile 'gcc62' doesn't exist.
Existing profiles: gcc62, gcc4.8.3
which is confusing.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Debugging a plugin with Profiler Tool : Profile Parsing Error
Hi guys,. I had the same issue, it turned out the profiler was running while I was trying to Debug. Stop the profiler...
Read more >Import Profile fails with error "Failed during Parsing record"
An Import Profile worked before, but new files fail to load with error : "Failed during Parsing record". Cause 1: Import Profiles are...
Read more >An error occurred while parsing the plugin profile from file
1 Answer 1 · Unregister the Plugin assembly & Profiler · Download latest 365 SDK · Register the assembly freshly using new PRT...
Read more >Import error "failed to parse profile" new update 3.2.7
While we importing ovpn config on new version we encountered withe issue of failed to parse profile and it list our files.
Read more >Resume Parsing Not Filling the Information in Candidate Profile
When the CV is being uploaded, the Resume Parsing is not filling the information in the Candidate Profile section Image/data in this KBA...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@memsharded The case is
Fixed in #608, will be released in next 0.15