Hi @pooms_7365 , Thanks, I found where the error is in the code; it was in displaying the "code has not been synced" message. Easy fix (BM-3845) and it will ship in next maintenance release :) And wow... 15gb! Cheers, Alana

I installed ProGet 3.1.2 today and the errors I experienced with 3.1.1 are gone. Thanks for the quick turn-around on the fix, you guys are great. Riko

hi, I had in the proxy configuration both allowed, ssl and non ssl. The Web.BaseUrl must be make empty. All self connector using http://localhost as base url.

I'm pretty sure it's just due to Microsoft SQL's CLI cutting off the XML output @atripp, as the XML object would just be unfinished when viewing in my terminal. I'm gonna whip together a quick CLI to try to pull it out programmatically later today, and then I can let you know if it all works. I'm quite confident that's what's been causing my issue though.

@atripp said in [Otter 3] Upgrade Inedo Agent failed: m here, I recommend to just reinstall v49 on the serve Reinstall the v49 directly is working but as the config file move and its format change I have to modify my autoregistration deployment script Thanks for the reply

Hi David, I came across your post and noticed that you're experiencing an issue with Git source providers in BuildMaster. I understand that you're trying to use the "Get Git Source" command but can only get the source from the master branch. Based on the command you provided, it looks like you have the syntax partially correct. However, it seems that the code is being picked up from the master branch instead of the production branch that you specified. Have you tried specifying the branch name with the "refs/heads/" prefix? For example: bash Copy code Branch: refs/heads/PRODUCTION This may help in correctly identifying the production branch. Additionally, you mentioned that you have deleted the repo details from C:\BuildMaster_WEBTMP\SrcRepos, but are still facing the same issue. Have you tried clearing your Git credentials and re-entering them? It's possible that the issue may be related to authentication. Plus I was researching on Elmedia Player for Mac, and As someone who's been using Elmedia Player for Mac for quite some time, I can definitely say that it's a great media player that offers a lot of useful features. One thing I particularly appreciate about Elmedia Player is its ability to play virtually any video or audio format that you throw at it.

Which older version of nuget works correctly?

Alana- looks like this one is actually on me, the reverse proxy was stopping the single quotes. But, the extra trailing slash is what causes the issue with Packages(), same as it does with the earlier problem. I have it sorted out now.

thanks!! Very interesting to see.

@wsah_6160 @pluskal_4199 assuming this is related to 5.3, then there should be a fix coming soon!

Hi @pfeigl, Thanks for letting us know. It looks like this is related to how HEAD requests were handled. I went and added that header to head requests also. This will be tracked in PG-2300 and will be released in ProGet 2022.25. Thanks, Rich

John, while on the subject of execution ID's and such, during the logging of a psensure, can we add the psensure key to the log so it always outputs what it is checking and validating? How it is now: INFO : 2018-12-11 20:31:07Z - Configuration drift detected. DEBUG: 2018-12-11 20:31:07Z - Adding to execution plan. DEBUG: 2018-12-11 20:31:11Z - Collecting configuration... DEBUG: 2018-12-11 20:31:11Z - Comparing configuration... INFO : 2018-12-11 20:31:11Z - Configuration matches template. DEBUG: 2018-12-11 20:31:14Z - Collecting configuration... DEBUG: 2018-12-11 20:31:14Z - Comparing configuration... INFO : 2018-12-11 20:31:14Z - Configuration matches template. and so on. Maybe it could log something like "Collecting configuration <key>" and "<key> matches template". That way it would make each line meaningful and bring more value into keeping the logs. Eventually I would like to have a way to save a copy of the txt execution into servicenow so we have a record of it in change management system as well. The url you shared previously will help in doing that I think. This improvement would help as documentation for each change. Thanks!

Alright, after messing around with that information, I was able to get it to work. I am able to update the variables. Interesting thing is that it doesn't appear I can change just one variable, I have to change all of them, or at least enter all of them as they are? Thanks for your help!

Thanks for the additional debugging information; we now see why this doesn't work. It would appear that NuGet stopped streaming all versions of the packages at some point, and now appends the following at the end of its package search XML... <link rel="next" href="http://www.nuget.org/api/v2/Packages? $filter=tolower(Id)%20eq% 20'ravendb.client'&$orderby=Id& $skiptoken='RavenDB.Clie nt','RavenDB.Client','1.2.2005-Unstable'" /> So, we will need to add support for this as well... I've added this as PG-140, but it's not scheduled for a release yet. If an enterprise (i.e. paying) user requests this, we can expedite it of course.

Hello Jonathan, We use Proget to deploy our PSModules. The deployement is driven with an Otter PSEnsure fonction- check if module exist with a specific version, if not deploy - Each new server is linked to an Otter role and after remediation, the module is installed. To update the module, we change version number in a otter variable. Otter remediation make the job We call PS function from local script or from Otter plan directly or from module. Don't know if this your need but it is working fine for us.

Hi Paraig, Replication between two different versions will likely work, though it would be a good idea to verify correctness when complete. We try to maintain backwards compatibility though we don't officially support this scenario (by this I mean we don't routinely test replication with older versions). In the event of a problem, another possibility is to replicate to another 4.6.7 instance, and then upgrade it to the latest version.

Please review KB#1161 for instructions on how to update this.

Hi @gurdip-sira_1271, Yes, this will be released with Otter later today. Thanks, Rich

We haven't heard any other complaints, so it leads me to think it's either your end (proxy?) or npm's end (blocking). We have no idea what their blocking mechanism could look like. For all we know, they could be doing agent-string filtering, and blocking requests from ProGet software, but not your web browser or npm client. Best bet is to run ProGet through a proxy (like fiddler or wireshark), by going to Admin > Proxy. Then you can see exact traffic.

Hi @aries66_2180, I just set up a clean ProGet 6.0.16 docker instance and tested this and it seems to be working for me. Can you send me an example image you are trying to push that fails? Also, would you be able to use a tool like WireShark or Fiddler to record your requests when trying to push an image and email it over to us at support@inedo.com with a subject of [QA-878] Docker push error? Thanks, Rich