{"push_id":1014446118,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b49322b568725c8c92c0732b14cc726748ec57d3","before":"f0c6a0315df752dddc21a8daa5282e91b5e499cc","commits":[{"sha":"b49322b568725c8c92c0732b14cc726748ec57d3","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"logging: use non-fatal logging level for glib backend\n\nIn our usage of glib logging, every g_critical()/g_return*()/g_warning()\nis considered a bug. They must not occur in a regular program run,\nso that we can run NetworkManager with G_DEBUG=fatal-warnings.\n\nOn the other hand, all nm_log() statements (even with severity <error>)\nare valid conditions that can occur at runtime.\n\nAs a consequence, when nm-logging uses glib as backend, we must not use\nG_LOG_LEVEL_WARNING level. Otherwise\n\n  $ /usr/sbin/NetworkManager --debug --g-fatal-warnings\n\nwill dump core on the message\n\n  \"<warn> glib-version: cannot handle SIGUSR1 and SIGUSR2 signals. Consider upgrading glib to 2.36.0 or newer\"\n\nThereby, downgrade the glib level for \"<info>\" to G_LOG_LEVEL_INFO.","distinct":true,"url":"https://api.github.com/repos/NetworkManager/NetworkManager/commits/b49322b568725c8c92c0732b14cc726748ec57d3"}]}