Closed Jean-Paul76 closed 2 years ago
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
Thanks for this. I started looking at it and will run some tests. Hit a wall, there must be some file encoding or path corruption around that blocks me from checking out the branch or PR branch.
Looks like a known issue when checking out repos in windows. Will spend sometime to read how this can be resolved :/ https://stackoverflow.com/questions/63727594/github-git-checkout-returns-error-invalid-path-on-windows
Thx, not sure what happened there. I'll have a look today or tomorrow.
Kind regards
Jean-Paul Malherbe 082 3099 609 On 1 May 2022, 01:39 +0200, Rodel E. Dagumampan @.***>, wrote:
Thanks for this. I started looking at it and will run some tests. Hit a wall, there must be some file encoding or path corruption around that blocks me from checking out the branch or PR branch. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Since I checked in from Linux this seems relevant.
https://brendanforster.com/notes/fixing-invalid-git-paths-on-windows/
I'm planning on redoing that branch on a Windows machine. Should be quicker than trying to resolve the problem in the broken branch.
Kind regards
Jean-Paul Malherbe 082 3099 609 On 1 May 2022, 01:39 +0200, Rodel E. Dagumampan @.***>, wrote:
Thanks for this. I started looking at it and will run some tests. Hit a wall, there must be some file encoding or path corruption around that blocks me from checking out the branch or PR branch. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Closing this Pull Request because of the file-path issue. Replaced by https://github.com/rdagumampan/yuniql/pull/266
Upgrade to .Net 6.0 and bump referenced assemblies to their latest stable versions.
I'm running on POP_OS 22.04, and as such added bash files for kicking off the tests. Only the SQL Server version was tested thus far however.
The project builds, and running the MSSQL Server suit of tests had only 7 failures. I'm not sure if this is due to my environment or something else. If someone could check for me that would be much appreciated.