Custom Query (23726 matches)


Show under each result:

Results (40 - 42 of 23726)

Ticket Resolution Summary Owner Reporter
#31362 wontfix please delete the branch 'orfox-stringsxml' tor-gitadm emmapeel

Hash: SHA512

i need to delete the translation.git branch orfox-stringsxml cause it is wrong, has the wrong .po files. i will recreate it then.

iQIzBAEBCgAdFiEEuIXY3OAXO0KkAgIfNk4d6ixPiDUFAl1KuQUACgkQNk4d6ixP iDWguBAAnW7V/74YXLWGmi3wwDC7xZkSXhLfCwQ0/F1TVjMvTkHQEFzhqo2yj4Kh L06V5SAIq+FzfgECAq04B9OXc1kpZeHPzD9Tzw28QdblNF8uKalEnCXQNXhElcuW YjnbrSeHOeA59T7vV9aN5x1zP4ERr/CrC/8ylYbi491mhgD19fThtoATpOteGc4R PsXGs/wwXjtDw+MoFKSW/3RsNI9XE8VVwOUkNLg3kLzD/dVH1cKcAJgsE5ZHA0nN bc2LF86VUMXiiYpnhHbjT8bmjptFFBN+F6Mgbnbjpku7YGOLCGLTtnL7wIQ7kUN9 RhSRMyQFjuQTLfyhhc6bdA+V2IBkmqoKN/qLG3pvEz10iIzgTzPYVZ4obP9oEHR0 NSZ9dVHAVwYTduIN4kBCPPfEGfSzRUHLsXZYipckUapqsreena06W2wKIqqeRyYT 6JNOV386dsWg+dW7qyx9Cei4Qw6xqDirElad7bqQXevGFGBeY1oguHbfLqbqApIa W7I/yJEW1y2agFmBmyKGPcxwS/vHyGZN4N7705N6FzF2paqd0WOGRDayqw/HPYWB dTv8WIqAcidplENpIiDOTmQBuJflRp8kvMUHibEwK2rm43xHFeUfjqgztDU8J2JV T4pwEXbydijBr5nx2pTj+eO7Hu4H2iLp2SS+Y5J/O/awlD3EXzM= =qGDo

#31361 implemented Remove Cobertura from our build process karsten karsten

We're having trouble with Cobertura, and we noticed that we're not really using it that much: One issue is an UnsupportedClassVersionError (#31233), another issue is a CI fail due to line coverage rate of 91.6% being below 92.0% on the CI host which doesn't show on my dev machine.

Without having hard evidence, I suspect that these issues are in one way or another related to Cobertura not being maintained anymore with its last release being from February 2015.

Let's remove Cobertura from our build process. We can later switch to using something else that GitLab can actually interpret the output of.

I didn't work on these changes yet, but I think this mainly requires changes to metrics-base and a subsequent update in all depending code bases. I'll work on this later today or tomorrow.

#31359 wontfix Split a control_event module out of control, and make it use control safe logging teor teor

Currently, control events can log messages through the standard logging module, which can send those logs as control events. This means that some configurations, future code, or errors might cause an infinite loop.

We should split off a control_event or control_log_event module, and make it use control safe logging. All it's dependencies should also use control safe or signal safe logging.

I think we need to make this change after catalyst's control refactor, to avoid merge conflicts.

Note: See TracQuery for help on using queries.