Support

• J

  Changing server context in the middle of a script
  • jimbobmcgee  

  3
  0
  Votes
  3
  Posts
  7
  Views

  J

  Thanks @atripp -- I can't believe I missed VariableTemplateType in the SDK! Thansk for posting the BuildMaster equivalent -- I'll look to see if I can adapt. As you say, the lack of DB may make this more challenging. Out of interest, how resilient are extensions to mismatched versions of InedoSdk and/or Otter.Core? Would I have recompile/redistribute an extension each time Otter is updated? Regarding the security issue, I'm not entirely certain I agree – perhaps, as the sole administrator / runner, my use case is vastly different from others. Agree to disagree Maybe, in a multi-user scenario, a valid middle ground might be to consider allowing Job authors to limit the servers that can be for server'd into, i.e. as a property of the job, rather than cutting off all access to for server. Or maybe allowing defining a for server privilege on servers / roles / environments themselves, so that certain users are allowed to issue that command in jobs scripts, and resolving the permissions at runtime. (I'm sure you've considered this before.)
• L

  How to delete untagged Docker images digest (free tier)
  • lisama7982_5385  

  3
  0
  Votes
  3
  Posts
  8
  Views

  L

  @atripp Thanks for the quick reply, I'm stuck about how to retag already existing digests? Currently, the repository is entirely untagged, so I can’t pull from the image's digest and retag it. I believe the issue is that I’m not being provided with the full digest hash - as seen in my screenshot - which is preventing me from referencing or working with the images directly. Would there be a way to retrieve the complete digest hash or otherwise interact with these untagged images so I can retag them? Or is there another approach you’d recommend for cleaning them up?
• S

  Error logs with SQL connection
  • serveradmin_0226  

  5
  0
  Votes
  5
  Posts
  13
  Views

  S

  I don't agree with you. Sorry. Configuration is very simple and we are 100% sure that everything is ok with connection string. It was tested. So ok, we will buy a payment version and we will send a request to support. Thanks for help.
• J

  Otter server receives thousands of connections from agent after reboot
  otter agents bug • • jimbobmcgee  

  3
  0
  Votes
  3
  Posts
  8
  Views

  

  @jimbobmcgee thanks again for the detailed analysis & debugging, definitely not easy doing so "blind" like that :) Anyway we will investigate/patch via OT-516 - I haven't looked but what you're describing sounds like a reasonable conclusion, i.e. the incoming agent isn't getting matched up.
• J

  Improper output encoding in Execution Details page
  bug • • jimbobmcgee  

  2
  0
  Votes
  2
  Posts
  5
  Views

  

  @jimbobmcgee thank you again for the very detailed analysis; we will get this fixed via OT-515, it's most an easy encoding to add
• M

  SQL Execute Permissions Missing for LogMessages_PurgeOldMessages
  • MY_9476  

  2
  1
  Votes
  2
  Posts
  8
  Views

  

  Hi @MY_9476 , Thanks for the heads up! We will fix this via OT-514 in the next maintenance release. As an FYI, this is the code that should have been run at the end of the database upgrade, to ensure that all procs and table-value params have appropriate permission: DECLARE @SQL NVARCHAR(MAX) SET @SQL = '' SELECT @SQL = @SQL + 'GRANT EXECUTE ON TYPE::' + QUOTENAME(name) + ' TO [OtterUser_Role] ' FROM sys.table_types SELECT @SQL = @SQL + 'GRANT EXECUTE ON ' + QUOTENAME(name) + ' TO [OtterUser_Role] ' FROM sys.procedures EXEC sp_executesql @SQL The script you ran works too :)
• J

  Error getting npm package versions: The JSON value could not be converted to System.DateTime ...
  • jeff.peirson_4344  

  9
  0
  Votes
  9
  Posts
  17
  Views

  

  Hi @jeff-peirson_4344, I have been able to recreate the issue and created a ticket, PG-2870, to track the fix. We expect this to release in ProGet 2024.25 on January 24, 2025. This looks to be related to the package name existing on npmjs.org with all versions being unlisted. If you need a fix sooner, we can provide a pre-release version of ProGet 2024.25 that includes the fix. Thanks, Rich
• H

  ProGet 24.0.23: Maven (new) Feed no longer accepts our (in 24.0.22 accepted) pom files.
  • hammel_7023  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  hi @hammel_7023 , Thanks for letting us know, you are correct... this is indeed a regression from PG-2859. What's happening is the upload stream is getting prematurely closed during the POM validation logic, which is what's causing this error to occur. I've just patched it now via PG-2868, and it'll get in the next maintenance release. Cheers, Alana
• S

  Working Rafts_CreateOrUpdateRaftItem example for Otter
  otter • • scusson_9923  

  2
  0
  Votes
  2
  Posts
  7
  Views

  

  Hi @scusson_9923 , Here's a one-liner that should hopefully get you started. Invoke-WebRequest -Method Post -Uri "http://otter.localhost/api/json/Rafts_CreateOrUpdateRaftItem" -Body @{ API_Key = "abc123" Raft_Id = 1 RaftItemType_Code = 4 RaftItem_Name = "mypath/myscript.ps1" ModifiedOn_Date = Get-Date ModifiedBy_User_Name = "API" Content_Bytes = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("'hello world'")) } The RaftItemType_Code=4 is not documented, but it's a fixed value and means a script. I recommend creating the item manually first, then looking in the RaftItems table for the Raft_Id and RaftItemType_Code values. Cheers, Alana
• J

  HTTP/500 error when re-running a job from History which has a blank/empty template variables
  otter • • jimbobmcgee  

  6
  0
  Votes
  6
  Posts
  20
  Views

  

  @jimbobmcgee excellent thanks!! Release has been published then :)
• N

  Authentication not working anymore - Unable to retrieve NuGet Packages
  • nachtmahr  

  2
  0
  Votes
  2
  Posts
  8
  Views

  

  Hi @nachtmahr , It sounds like your Windows Integrated Authentication is broken. This is an operating-system level feature, and the only thing you can do in ProGet is turn it on, or turn it off. WIA is pretty buggy these days, and sometimes it just breaks. Here is more information: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-integrated-authentication Hopefully just doing a reboot of the server will fix the problem. If not, then you'll have to troubleshoot it, which kind of sucks: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-troubleshooting#integrated-authentication-not-working Note that you can disable WIA by using the Locked Out protocol: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-troubleshooting#locked-out-restoring-default-admin-account Hope that helps, Alana
• 

  Publishing ProGet to Chocolatey Community Repository
  • steviecoaster  

  6
  0
  Votes
  6
  Posts
  15
  Views

  

  Thanks @steviecoaster! All that sounds great, especially since it won't require changing anything on our end :) Much appreciateD!!
• G

  After upgrading ProGet, docker images cannot be pulled because missing configuration blob
  • ghollosy_9163  

  3
  0
  Votes
  3
  Posts
  9
  Views

  G

  Hi @dean-houston , Thanks for your response, at the end, we come to the same conclusion that something went wrong during the upgrade and some of the configuration blobs got deleted from the disk and also from the database table. Luckily, we have the backup, but we need to figure out which images are corrupted and need to be recovered. Gabor
• S

  Problem with SQL connection for Basic version
  • serveradmin_0226  

  4
  0
  Votes
  4
  Posts
  13
  Views

  

  Hi @monika-sadlok_5031, That error means that the ProGet application container cannot make a network connection to the the SQL Server container. I would try to restart the containers, start with SQL Server. Make sure it's running. If it's running, you can try connecting to it with another tool like SSMS if you'd like to verify.' Otherwise, on the ProGet side, you can only configure the connection string; upgrading or changing the license key has zero impact on this. If it worked in the past, then it means that the SSQL Server container is not running or your network/container configuration changed. This can be hard to discover exacgtly what changed, so I would recommend "starting from scratch" on a new server/environment, then compare/contrasting what changed. Sometimes it's as simple as a typo or an errant - (dash character) in the wrong place/script. Cheers, Alana
• S

  Support for Winget feed
  features • • sylvain.martel_3976  

  16
  0
  Votes
  16
  Posts
  82
  Views

  

  Hi @mikes_4196 , Per the discussion above... can you tell me a bit about "we" (i.e. the size/profile of your organization) and describe how you are using winget in your organization? And why did you use WinGet instead of Chocolatey? Per the discussion above, it does not look like a tool/ecosystem that is usable at scale. I get that it's built in to Windows, but I haven't seen a case study demonstrating a real deployment -- even within teams at Microsoft. The "central repository" is just a giant mess of files in a GitHub repository and can't reasonably be "proxied" via a connector like other feeds. They apparently have "private repositories", but there's no documentation/guidance on how to create/use private packages for end users, so I don't think many are doing this. But open to learning more. Cheers, Alex
• F

  Package delist and deprecated API
  • forbzie22_0253  

  3
  0
  Votes
  3
  Posts
  8
  Views

  

  Hi @forbzie22_0253 , Similar to the UI, packages are still returned in the API - they just have a flag set to indicate they are unlisted/deprecated. It's up to the client to determine what to do about that. I don't believe the Find-Package cmdlet works with these properties; I think only Visual Studio will hide/warn about them. Thanks, Alana
• J

  Question About Architecture Support in ProGet’s Container Registry
  • jaehyung.shin_8059  

  3
  0
  Votes
  3
  Posts
  6
  Views

  J

  Dear @dean-houston , Thanks for your guidance. Following the steps in the provided Docker guide, I was able to successfully build a multi-platform image, and the “Fat Manifest Image” information now appears correctly in ProGet. This resolves my question, and I really appreciate your help in clarifying the process.
• J

  How to Force Vulnerability Scan on “Not Scanned” Artifacts?
  • jaehyung.shin_8059  

  2
  0
  Votes
  2
  Posts
  7
  Views

  

  hi @jaehyung-shin_8059 , If you click on the latest tag, do you see any information about the packages in the container? Container images are scanned on upload if they are small or queued to be scanned in the background if they are large. There are sometimes errors scanning containers, and if so, these errors will be logged... typically under Admin > Executions. -- Dean
• P

  An unexpected error occurred while migrating artifact metadata: 'xsi' is an undeclared prefix
  • parthu.reddy  

  9
  0
  Votes
  9
  Posts
  12
  Views

  

  @parthu-reddy yes, but we do recommend migrating... There are some known bugs/quirks with Maven (Classic) feeds and we will not fix them. We will likely not migrate them to PostgresSQL, which means you won't be able to migrate to PostgreSQL in ProGet 2025+. So it's likely that ProGet 2027 will not support them.
• P

  Need suggestion during proget upgrade
  • parthu.reddy  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Hi @parthu-reddy, For a major upgrade, we recommend to schedule a maintenance window and then stop traffic from the load balancer. Then, upgrade the servers. For a maintenance release, it's fine to just upgrade them one at a time. It only take as few minutes to do that. There may be a few errors with the database/code being out of sync, but it likely will not cause any problems. -- Dean