-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'push' of undefined #69
Comments
0.8.3 is not the recommended stable release? 1.1.3 is latest stable. |
I'll try with that one. The README.md indicates 0.8.3 so I assumed I should stick to that.
|
Oh I added that while 1.0 was still in it's infancy. I'll remove it today :) |
Cool. I'll close this one off then and re-do my testing with the current version. Thanks so much for the quick response. |
Based on the discussion in atlassian#69 it sounds like the latest 1.x release is the recommended version to use. This diff removes those outdated instructions from the README.
Based on the discussion in #69 it sounds like the latest 1.x release is the recommended version to use. This diff removes those outdated instructions from the README.
Hi there,
I'm testing the recommended stable version (0.8.3) on a Mac, running the server with yarn dev and Node 8.12.0.
If I publish an Electron project using electron-forge it, as expected, shows up as a draft version in Nucleus.
Both of those files exist in the .files/My-Project/temp/0394528b26599a344ed6fe471d1343b2/ directory and both are the correct file size.
When I publish the pre-release I get the following error:
This leaves things in a weird state. In the UI the release exists both in the "Released" tab (just listing the .exe) and in the Drafts tab (listing both files). In .files/PROJECT/CHANNEL/win32/x64/ nothing has been copied over yet.
Were I to go and press "Release" a second time, both files are removed from the temp folder and the logging looks a little less alarming, but the .exe file is never copied to the folder with the .nupkg. The Draft tab is empty afterwards and the Releaes tab reflects the new version (not that it can be downloaded as the .exe doesn't acutally exist on disk).
I tried adding some debug logging in and around line 315 of SequelizeDriver.js. The error apperas to be throwing from dbVersion.files.push(newFile) but all the component parts of that statement seem to exist as expected.
Any thoughts?
The text was updated successfully, but these errors were encountered: