Closed donnybell closed 2 years ago
From the original slack conversation it looks like it affects 2022.1.2584
and 2022.2.5111
and potentially all versions from there.
I have reverted https://github.com/OctopusDeploy/OctopusDeploy/pull/11894, which is related to escaping / and % in the URL. The problem persists, so is not related to this change.
Turns out this is caused by the 11894 change - I wasn't testing it properly.
Any timeframe on a fix for this issue?
Another customer experiencing this issue (Internal Ticket) - https://octopus.zendesk.com/agent/tickets/91016
Sorry - missed the messages. I'm working on a fix for this issue this week. It is really getting into the depths of React's routing and proving to be 'difficult'.
Sorry this has taken a while to get sorted. We have decided to revert the original change that caused the Unicode project names to break. The original change was done to allow % symbols in Git branch names, but that will be very rare compared to Unicode project names. The fix is in this PR.
Release Note: Fixed issue with Unicode in project names
When will this fix become available in the on-premise version?
@gh-ttgo The 2022.3 release is currently scheduled for General Availability release on 5 September.
Heads up! If any other project properties contain non-ASCII characters, the workaround script needs to be adjusted:
# Save project changes
$body = [Text.Encoding]::UTF8.GetBytes(($project | ConvertTo-Json -Depth 10))
Invoke-RestMethod -Method Put -Uri "$octopusURL/api/$($space.Id)/projects/$($project.Id)" -Headers $header -Body $body
Otherwise those properties will be garbled. The server (v2022.2.7457) doesn't seem to validate the received project configuration entirely, because it accepted the update. It broke both the project view and the API GET .../projects/
: Octopus.Core.Model.Exceptions.DomainException: The package step provided could not be found in the project's deployment process (see Automatic Release Creation settings, via Project > Triggers). (I fixed it by updating the project with a new handcrafted JSON configuration.)
The error is stil present in 2022.3.7782 (onprem)
:tada: The fix for this issue has been released in:
Release stream | Release |
---|---|
2022.1 | 2022.1.3180 |
2022.2 | 2022.2.7965 |
2022.3 | 2022.3.9953 |
2022.4+ | all releases |
Team
Severity
Blocking
Version
Reproduced in 2022.1.2584
Latest Version
No response
What happened?
Project names with certain special characters may fail to load with an Octopus.Core.Model.Exceptions.EntityNotFoundException error.
Examples include:
It appears that there's something going on with the URL encode/decode. For example, a project with the name åååååå in 2022.1.2584 results in the following:
http://octopus_url/app#/Spaces-1/projects/åååååå
turns into:http://octopus_url/api/Spaces-1/projects/%25C3%25A5%25C3%25A5%25C3%25A5%25C3%25A5%25C3%25A5%25C3%25A5
when viewing the console in my browserThe correct URL should be:
http://octopus_url/api/Spaces-1/projects/%C3%A5%C3%A5%C3%A5%C3%A5%C3%A5%C3%A5
Reproduction
Create a project with the name of
åååååå
in2022.1.2584
, then try to access it.Error and Stacktrace
More Information
Internal Conversation - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1652374468520679
Workaround
You can manually change the project name via the API.