Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
error on the first run
See original GitHub issueHi there,
I’m getting an UnhandledPromiseRejectionWarning: TypeError: tslib_1.__spreadArray is not a function error after the Conversion successful message when I run portman --cliOptionsFile portman/portman-cli.json on a basic openapi spec file with the default portman-cli.json generated by portman --init
Any hints?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11
Top Results From Across the Web
How to Fix Second Run /lang en-us /FirstRun ThreadId 6224 ...
How to Fix Second Run /lang en-us / FirstRun ThreadId 6224 error for any Autodesk productIf you are installing or uninstalling any Autodesk ......
Read more >Error on the first run on vagrant laravel - Stack Overflow
Im trying to run vagrant laravel but im getting an error on my first run on the VM, did i do something wrong...
Read more >SAP message F5316 First run is in the past
Message type: E = Error. Message class: F5 - Document Editing. Message number: 316. Message text: First run is in the past ...
Read more >Error on first run - Veeam R&D Forums
Re: Error on first run Hello, I've received a message from the Support Team, that the ticket is closed due to high Support...
Read more >Error on first run · Issue #40 · cloudflare/flan - GitHub
Hi, I ran make build withour any error. Then i tested make start and got this error : docker run --name flan_1574936755 -v ......
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
Looks like it works. Thanks guys.
@clonq The changes have been merged into the 1.5.1 release.
I’m going to leave this item open, and hope you can validate if the 1.5.1 release have fixed this unwanted error. If the error is solved, would you be so kind to close the item. If the error remains, could you let us know the error stack trace and share any additional info that could help us to reproduce the problem.