Home → Problems →

Publication to symbolsource.org

• Edit

pascal

30 Jul, 2015 11:00 AM

Since yesterday, the publication to symbolsource.org fails with a connection error (for example my latest builds in https://ci.appveyor.com/project/picrap/mradvice). The symbolsource.org on the other side says that an assembly with the same hash was already published. This is true but was no problem before (it was simply rejected, the same way it was with publication to nuget).
Can something be done for this?

1. Support Staff 1 Posted by Feodor Fitsner on 30 Jul, 2015 02:26 PM

   

   Will take a look.

   - Feodor

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 30 Jul, 2015 07:03 PM

   

   Looks like it's working: https://ci.appveyor.com/project/FeodorFitsner/nuget-test/build/1.0.144

   When I do republish the same build via environments I don't get an error on pushing symbols - see attached screenshot. There are intermittent issues sometimes on symbolsource side so maybe that was the case.

   • nuget-symbols-redeploy.png 29 KB
   • Edit

3. 3 Posted by pascal on 30 Jul, 2015 08:15 PM

   

   It still does not work for me. In your snapshot, the symbol package appears to be new. What if you do another build with different code and same version number?

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 30 Jul, 2015 09:52 PM

   

   It worked: https://ci.appveyor.com/project/FeodorFitsner/nuget-test/build/1.0.145

   How many times do you have to publish the same package to catch the error? Is it sporadic or permanent? Is your package changing between builds (but version stays the same)?

   • Edit

5. 5 Posted by pascal on 30 Jul, 2015 09:55 PM

   

   I get the error when my build produces a different package with different code. And since two days it happens everytime I do this. Until now, I haven't tested with a new version number (since I'm refactoring my code).
   So yes, the package changes between builds, but the version is the same. This means that I don't wan't to release a new package, but still want the package to be validated.

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 30 Jul, 2015 09:57 PM

   

   Looks like there is something on symbolsource side rejecting it - maybe it's checking SHA or there is other way to check integrity. Have you tried publishing symbols package using nuget push command?

   • Edit

7. 7 Posted by pascal on 30 Jul, 2015 10:00 PM

   

   SymbolSource shows my packages in the failed section with "Image file MrAdvice.Dll exists in compilation with different binary hash."
   So yes, this is a deny from SymbolSource, but I don't understand why it is seen as a connection exception from Appveyor.
   And no, I haven't tried nuget push.

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 30 Jul, 2015 10:06 PM

   

   While publishing to nuget source AppVeyor recognizes these response code:

   • 500 - error publishing; retry one time in 10 seconds
   • 409 - package already exists; skip publishing

   That works well with nuget.org.

   In your case with symbolsource it looks like they just drop the connection without any response at all. We could wrap everything in a big try-catch of course, but dropped connection could mean everything like the site unavailable or networking issues...

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 30 Jul, 2015 10:06 PM

   

   Anyway, let me know what it says when pushing with nuget.exe

   • Edit

10. 10 Posted by pascal on 31 Jul, 2015 07:34 AM

    

    Which package shall I push? The release or package with symbols? Also, shall I push it to nuget or to symbolsource?

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 31 Jul, 2015 07:38 AM

    

    Package with symbols to symbolsource.

    • Edit

12. 12 Posted by pascal on 31 Jul, 2015 08:30 AM

    

    I get the same connexion error (see attached file, it's in french, but you got the idea :)).
    I wanted to see what's up with symbolsource, but the status page appears to be down this morning.

    • Developer_Command_Prompt_for_VS2013.jpg 47.1 KB
    • Edit

13. Support Staff 13 Posted by Feodor Fitsner on 31 Jul, 2015 02:29 PM

    

    Write them a message - they usually respond pretty fast.

    - Feodor

    • Edit

14. 14 Posted by pascal on 02 Aug, 2015 01:37 AM

    

    I did, but the problem seems to have been solved "spontaneously" before I got an answer :)
    Thanks.

    • Edit

15. Support Staff 15 Posted by Feodor Fitsner on 02 Aug, 2015 02:23 AM

    

    Ah, OK then :)

    - Feodor

    • Edit

16. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.