Thomas Haller 2582694b46 cloud-setup: cleanup error handling in GCP provider ... - drop GCPData.success field. It is redundant to have GCPData.error set. Also, it's meaningless to indicate failure, if we don't have an error at hand. - ensure that we keep the first error passed during _get_config_maybe_task_return(). Once we set an error, that error gets returned. There is a twist here, that we prefer cancellation errors over other error reasons. - in _get_config_fip_cb(), ensure to call _get_config_maybe_task_return() even if we are not yet ready. That is useful to record a potential error.		2020-07-30 09:18:40 +02:00
..
cli	all: add trailing semicolon to NM_UTILS_LOOKUP_DEFINE()/NM_GOBJECT_PROPERTIES_DEFINE*()	2020-07-19 12:12:58 +02:00
cloud-setup	cloud-setup: cleanup error handling in GCP provider	2020-07-30 09:18:40 +02:00
common	all: add trailing semicolon to NM_UTILS_LOOKUP_DEFINE()/NM_GOBJECT_PROPERTIES_DEFINE*()	2020-07-19 12:12:58 +02:00
tests	all: add ap-isolation property to wifi setting	2020-07-01 17:36:20 +02:00
tui	tui: fix default values for bond options in nmtui	2020-07-11 15:06:28 +02:00
meson.build	docs: generate nm-settings-docs-nmcli.xml based on nmcli meta data	2020-06-11 10:53:50 +02:00
nm-online.c	nm-online: allow configuring timeout via NM_ONLINE_TIMEOUT environment	2020-04-30 21:46:59 +02:00