| Summary: | org.eclipse.orion.server.tests/testData/importTest/あ.txt causes egit problems on a mac | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Anton McConville <antonm> |
| Component: | Client | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, mamacdon.bugs, mamacdon |
| Version: | unspecified | ||
| Target Milestone: | 6.0 RC3 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Anton McConville
This is still causing me problems. Please point me at the code, and I'll work to generate the file. Since the file was added to test a file name defect rather than a file contents defect, I have wiped out the unicode characters from the file with commit: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=212cc228331e24cc8db861680f99335ff04180b6 Give it another try. Anton is still experiencing this bug, so reopening. The problem seems to be "あ" in the filename, not the file contents. I will try the latest eGit at home on my Mac and see if I can duplicate the issue. I released a change that generates the test file on-the-fly instead of storing it in the repo. Hopefully this will prevent EGit from choking on the あ.txt file. http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=055bc4e http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=8f4d66c http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=89a44e1 Anthony: if you want to try to reproduce the issue, do a hard reset on your server repo to commit 5be1f06, and the problematic file should appear again. I appreciate all the work you've put in, but I have a workaround now, which is to avoid using egit, and to clone from the command line and import the projects from there. It makes a huge difference not to see the error any more when working with eclipse. (In reply to Mark Macdonald from comment #5) > Anthony: if you want to try to reproduce the issue, do a hard reset on your > server repo to commit 5be1f06, and the problematic file should appear again. No need to look further, problem solved. |