g$SrSSKJr SSKJr SSKJr SSKrSSKrSSKrSSKJ r SSKJ r SSK J r SS K Jr SSKr"S S \5rg) aThis module implements update checking and notification to the user. It provides a context manager around the cache file that stores information about the last update check. The general process is as follows: 1) This stores the last time an update check occurred, so the check will only be done if the update check frequency has expired. 2) When an update check is done, all notifications in the latest snapshot are queried to see if their condition matches the current state of the SDK. Any notifications that match are "activated" and cached. 3) Every time a command is run, Notify() is called to notify the user of available updates. It loops over the activated notifications and determines if any of the triggers match the current command invocation. If there is a match, the notification is printed and the last nag time is recorded for that particular notification. At most one notification is printed per command. The priority is determined by the order the notifications are registered in the component snapshot. )absolute_import)division)unicode_literalsN)config)log)schemas)filesct\rSrSrSrSrSrSrSrSr Sr S r S r S r S rS rSSjrSrSrSrSrg)UpdateCheckData3zBA class to hold update checking data and to perform notifications.iQc[R"5RUlSUlUR 5Ulg)NF)rPathsupdate_check_cache_path_last_update_check_file_dirty _LoadData_dataselfs /lib/googlecloudsdk/core/updater/update_check.py__init__UpdateCheckData.__init__8s+#)<<>#I#ID DK!DJc[RRUR5(d[R R 05$[R"UR5n[R"U5n[R R U5$![a8 [R"S5 [R R 05s$f=f)z%Deserializes data from the json file.zDFailed to parse update check cache file. Using empty cache instead.)ospathisfilerrLastUpdateCheckFromDictionaryr ReadFileContentsjsonloads ValueErrorrdebug)rraw_datadatas rrUpdateCheckData._LoadData=s 77>>$66 7 7  $ $ 3 3B 77%%d&B&BCH8 ZZ !d  $ $ 3 3D 99 8 ii!"  $ $ 3 3B 778s/4B$$?C&%C&cUR(dg[R"UR[R "UR R555 SUlg)z!Serializes data to the json file.NF)rr WriteFileContentsrr!dumpsr ToDictionaryrs r _SaveDataUpdateCheckData._SaveDataKsC ;;  D88 JJtzz'>'>'@ACDKrcU$Nrs r __enter__UpdateCheckData.__enter__Ss Krc$UR5 gr/)r,)rargss r__exit__UpdateCheckData.__exit__Vs NNrc.URR$)zGets the revision of the snapshot from the last update check. Returns: long, The revision of the last checked snapshot. This is a long int but formatted as an actual date in seconds (i.e 20151009132504). It is *NOT* seconds since the epoch. )rlast_update_check_revisionrs rLastUpdateCheckRevision'UpdateCheckData.LastUpdateCheckRevisionYs :: 0 00rc.URR$)zGets the time of the last update check as seconds since the epoch. Returns: int, The time of the last update check in seconds since the epoch. )rlast_update_check_timers rLastUpdateCheckTime#UpdateCheckData.LastUpdateCheckTimecs :: , ,,rcZ[R"5URR- $)znGets the number of seconds since we last did an update check. Returns: int, The amount of time in seconds. )timerr<rs rSecondsSinceLastUpdateCheck+UpdateCheckData.SecondsSinceLastUpdateCheckks 99;:: ::rcDUR5[R:$)zChecks if it is time to do an update check. Returns: True, if enough time has elapsed and we should perform another update check. False otherwise. )rAr !UPDATE_CHECK_FREQUENCY_IN_SECONDSrs rShouldDoUpdateCheck#UpdateCheckData.ShouldDoUpdateCheckss#  , , .  = = >?rc[URRVs/sH"nURR(dM UPM$ sn5$s snf)zReturns whether we already know about updates that are available. Returns: bool, True if we know about updates, False otherwise. )boolr notifications conditioncheck_components)r notifications rUpdatesAvailable UpdateCheckData.UpdatesAvailable}sJ )-)A)A)A  ! ! 2 2 )A s AAcU(dUR5UR:wa[R"S5 [R R n[R Rn/nURRnUHXnURRXEU5(dM&[R"SUR5 URU5 MZ X`RlUR5 [R"5URlURURlSUlg)aSets that we just did an update check and found the given snapshot. If the given snapshot is different than the last one we saw, refresh the set of activated notifications for available updates for any notifications with matching conditions. You must call Save() to persist these changes or use this as a context manager. Args: snapshot: snapshots.ComponentSnapshot, The latest snapshot available. component_updates_available: bool, True if there are updates to components we have installed. False otherwise. force: bool, True to force a recalculation of whether there are available updates, even if the snapshot revision has not changed. zUpdating notification cache...zActivating notification: [%s]TN)r9revisionrr$rINSTALLATION_CONFIGversionsdk_definitionrIrJMatchesidappendr_CleanUpLastNagTimesr@r<r8r) rsnapshotcomponent_updates_availableforcecurrent_versioncurrent_revision activatedpossible_notificationsrLs rSetFromSnapshotUpdateCheckData.SetFromSnapshots" ,,.(2C2CC ii0122::o33<<i'66DD0,  ! ! ) ) /J L L ))3\__ E   < ( 1 "+jj !(, DJJ%,4,=,=DJJ)DKrc [R"S5 [R"S[R"SSSSS5[R "SSS9[R "SSS5S9nU/URlUR5 [R"5URl SURl S Ul g) amSets that we just did an update check and found a new schema version. An incompatible schema version means there are definitely updates available but we can't read the notifications to correctly notify the user. This will install a default notification for the incompatible schema. You must call Save() to persist these changes or use this as a context manager. z># UHupUT;dM X4v M g7fr/r0).0namevalue activated_idss r 7UpdateCheckData._CleanUpLastNagTimes..s& &G }$ TMGs  N)rrIrUdictsix iteritemslast_nag_times)rnrrs @rrW$UpdateCheckData._CleanUpLastNagTimess` $(::#;#;<#;aTT#;>  3::#4#4#6#6  00 __djj//33D!rs; &'' &#/* AfAr