Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Umlaut in contributor name of a Git commit makes it impossible to claim the commit
Umlauts in a Git username are not extracted or rendered correctly as can be seen in this example:
https://www.openhub.net/p/mmmcore/contributors/3085687042120039
The 'ö' between 'r' and 'h' in the last name is missing.
(Maybe as a consequence) it is impossible for me to claim this commit.
The error message is ''Contributor 'Manfred Krhnert' could not be found".
This error does also occur with other projects.
Is this a known issue and can it be fixed?
Thanks and best regards,
Manfred
Manfred,
I will let management know about this and hopefully, we can come up with a solution. (It shouldn't have become an issue, but hindsight is 20:20, they say...)
Thanks!
Thank you very much for the fast response!
Same problem here.
Same here too.
Hi Folks;
We apologize for this inconvenience. This is a growing pains issue as we perform long overdue upgrade issues.
As we talked about in our blog post, Upgrading Crawlers, we moved up to Ruby 1.9.3 from Ruby 1.8.7. Ruby 1.9.3 has a vastly different way of handling encoding from Ruby 1.8.7. When we couple this difference in behavior with the configuration of the database in SQL-ASCII, we have a series of confounding issues that makes consistent parsing of strings in conceivably nearly any possible encoding very complex.
To keep the site running, we decided to simply drop illegally encoded characters that were otherwise keeping the analysis from completing and blocking presentation on the web site.
This is a short term fix.
We are refactoring some back end code and will then focus on updating our web site to the latest versions of Ruby and Rails.
Thanks for shedding some light on this issue.
Looking forward to the final solution.
Hope it will get fixed soon, I have the same problem on two projects.
Umlaute are working now, but now it seems the repositories aren't get updated at all.
My first location is not analyzed since over 25 days, I added a second recentely and it even isn't scheduled. Both are at GitHub.
Heiko,
I'll check to see if there are any extraordinary problems in place or only the issues everybody is challenged by. Standby.
Thanks!
Heiko,
Nothing extraordinary. I pushed a little here and there to see if we can rush the electrons and get them to dance to our tune.
I'll let you know if I see any change.
Thanks!
Thanks, this have been only thoughts of me. As you know even in the best software even the smallest change can break the system in a totally unexpected place.
Happened several times to me and pushed me to write unit tests more and more ;-)
This wasn't meant as any criticism, just a note from my own experience.