-
Notifications
You must be signed in to change notification settings - Fork 15
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
Errors when uploading packages #73
Comments
Hmmm...I reverted the line in |
Mmmh can you give me the nuspec file of the package you are trying to upload? |
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
<metadata>
<id>EPG.CommonLibrary</id>
<version>1.1.21.7096</version>
<title></title>
<authors>EPG Internal Development</authors>
<owners>EPG Internal Development</owners>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<description>Common code library for EPG applications.</description>
<copyright>Copyright © 2016 EPG Insurance, Inc.</copyright>
</metadata>
</package> The packages were uploading fine up to the last couple of commits. |
I think this could result from the absence of the field on the nuspec, i think that a call to if(is_array( on the else could do the work ... this was generated by another guy having an array for the release notes (i always like the clarity and precision of the nuspec specifications :P ) |
hmmm...let me try adding the field and see if it works. |
So, adding the field |
This is the command I am using:
|
http://sandbox.onlinephpfunctions.com/ with htmlspecialchars(implode(" ",null)); it explode! |
Sounds good, but as I said, I don't think that is the main problem. Because even after putting in the release notes field, the push operation still fails with:
|
I can tell that the problem started with the wave of commits after (42cd592). (the ones with |
I can confirm commit 5f86b49 is what is breaking the push uploads. I am not sure which specific one of the changes in the commit does, but all the commits before that one work fine. |
@kendarorg Quick question. I notice that this commit introduces an IsLatestVersion field to the database. Am I missing a schema upgrade, and could this be the problem (I have mySQL backend)? And if so, UPDATE: Nevermind, the field exists in my |
…ls.php+Wrong handling of missing title
Added package \nuget_exes\NoRelease.1.0.0 to test |
This is still not resolved. Still getting the error:
|
I recognized now that you are treating Symbols packages!! |
The size is 199KB. The max is 50MB. And yes, I do both (with symbols and without symbols). As mentioned, this worked fine until after commit 5f86b49 . |
Tried to reduce the variations... (sorry for the dumb questions, but i am really trying to understand this thing) |
if u can give it a try! |
I did. Command returns:
PHP returns:
|
I was having a similar error with this, then upgraded to phpnuget 4.1.0.0 with php7.4.3:
|
@adrift42 You just need to install php-zip package, and php-curl while you're at it -- and php-mysql if you're using that. But uploads are still broken. |
I am getting an
Got error 'PHP message: PHP Warning: implode(): Invalid arguments passed in /app/src/inc/api_nuget.php on line 128\nPHP message: PHP Warning: implode(): Invalid arguments passed in /app/src/inc/api_nuget.php on line 128\n'
when trying to upload packages. As a result the push operation fails.This started happening after the last set of changes (092f2c1) where this was introduced:
Other subsequent errors are:
However, this one is possible just a result of the original failure.
The text was updated successfully, but these errors were encountered: