{"push_id":1818005706,"size":5,"distinct_size":5,"ref":"refs/heads/master","head":"53ec2a3226012374e6efce6c0a82cecd6149f52b","before":"7be1420f44465a96d098a33c12c5a61dcefb14aa","commits":[{"sha":"f2bfc6ba452d1389b703960969a341c8883c4211","author":{"name":"Lennart Poettering","email":"2baa8fca698523d252842633f852b9ab3cfeddbc@poettering.net"},"message":"sd-bus: make sure propagate all errors with vtable callbacks back to clients\n\nPreviously we'd propagate errors returned by user callbacks configured\nin vtables back to the users only for method handlers and property\nget/set handlers. This does the same for child enumeration and when we\ncheck whether a fallback unit exists.\n\nWithout this the failure will be treated as a non-recoverable connection\nerror and result in connection termination.\n\nFixes: #6059","distinct":true,"url":"https://api.github.com/repos/systemd-mailing-devs/systemd-mailing-list/commits/f2bfc6ba452d1389b703960969a341c8883c4211"},{"sha":"b007626897e73603dd57d31f83b53eaafd89f13e","author":{"name":"Michal Koutný","email":"aa995ee576eacf43ed0620db13e7a00cd61d603f@users.noreply.github.com"},"message":"core: dbus: Interpret released names properly (#6175)\n\nWhen a DBus name is released, NameOwnerChanged signal contains an empty string\r\nas new_owner. Commit bbc2908 changed interpretation of the empty string to a\r\nvalid name, which is not consistent with values that are sent by dbus-daemon.\r\n\r\nAs a side effect, this masks symptoms of systemd-logind dbus disconnections\r\n(#2925) by completely restarting it so it can freshly reconnect to dbus.","distinct":true,"url":"https://api.github.com/repos/systemd-mailing-devs/systemd-mailing-list/commits/b007626897e73603dd57d31f83b53eaafd89f13e"},{"sha":"05e33aa1d5c074df863d9de4bf236dd676347a4c","author":{"name":"Michal Sekletar","email":"154b5930e65ccb85bea4d3d1b954dc92e501c95d@users.noreply.github.com"},"message":"core: unset sysfs path after transition to dead state (#6174)\n\nDevice is gone and most likely it will get garbage collected. However in\r\ncases when it doesn't get gc'ed (because it is referenced by some\r\nother unit, e.g. mount from fstab) we need to unset sysfs. This is\r\nbecause when device appears next time, possibly, with different sysfs\r\npath we need to update the sysfs path. Current code could end up caching\r\nstale sysfs path forever.\r\n\r\nIn reality this is not a problem for normal disks (unless you swap them\r\nduring system runtime). However this issue causes failures to mount\r\nfilesystems on LVM where sysfs path depends on activation\r\norder (i.e. logical volumes from volume group that is activated first\r\nget assigned lower dm-X numbers and corresponding syspaths).\r\n\r\nFixes #6126.","distinct":true,"url":"https://api.github.com/repos/systemd-mailing-devs/systemd-mailing-list/commits/05e33aa1d5c074df863d9de4bf236dd676347a4c"},{"sha":"00c83b430020914499bebf22be6b258f518ae291","author":{"name":"Lennart Poettering","email":"2baa8fca698523d252842633f852b9ab3cfeddbc@poettering.net"},"message":"core: return a friendlier error for a dbus path referring to a non-existent unit\n\nSee: #6059","distinct":true,"url":"https://api.github.com/repos/systemd-mailing-devs/systemd-mailing-list/commits/00c83b430020914499bebf22be6b258f518ae291"},{"sha":"53ec2a3226012374e6efce6c0a82cecd6149f52b","author":{"name":"Zbigniew Jędrzejewski-Szmek","email":"77dc704bc81310147658033dcc63fa6fb3a4d704@in.waw.pl"},"message":"Merge pull request #6164 from poettering/bus-non-existant-object\n\nsd-bus: don't treat requests for non-existent objects as connection errors","distinct":true,"url":"https://api.github.com/repos/systemd-mailing-devs/systemd-mailing-list/commits/53ec2a3226012374e6efce6c0a82cecd6149f52b"}]}
{"actor":{"display_login":"surfsite-github-bot"}}