Интересно видео за АЕЦ-овете, сигурността на електрическата мрежа, COVID, Фаучи, как “студенти” на които не е преподавал и не познава го принуждават да напусне университета, в който работи (а полицията се крие и не взема мерки), и още много неща в интервюто с Dr Bret Weinstein в DOAC (The Diary Of A CEO):
Вариант да си спестите чакането пред бариерите за плащане на таксите е ако използвате чип за преминаване, който предварително се зарежда със сума, от която се тегли таксата на всяко преминаване.
I had to check recently what is the storage capacity of an Apple TV 3rd generation device identified as model Apple TV A1469. Strangely NOWHERE in the About and Settings is shown the capacity. It seems that officially for this device there is no storage available and stated!!!
Apple TV (3rd Generation, Early 2013) Specs Identifiers: 3rd Gen – MD199LL/A – AppleTV3,2 – A1469 – 2633
Apple TV (3rd Generation) has 512 MB of RAM and is capable of supporting 1080p video.
Processor Speed: 1 GHz* Processor Type: Apple A5
Apple does not specify the amount of RAM onboard. However, by third-parties it was confirmed that it has 512 MB of RAM.
Standard Storage: 8 GB SSD Storage. Officially, the third generation Apple TV models have no internal storage. However, third-parties have determined that they actually have 8 GB of flash memory to cache content, just like the second generation Apple TV.
With QR code (also to older version and Android phones) or directly to another iPhone (you have to turn off personal hotspot and to have each others email in contacts). Here is a video from Apple Support:
Below the code make sure to switch ON in Settings“Run this query on application load?”
Now you can use the created value in the variable “dt” in any Date picker component by simply putting the following text in “Default value” property: “{{variables.dt}}“
If you have a BigQuery external table which uses for example a Google Sheets file as source, AND you try to read / join this table in BigQuery SQL you may get the error in BigQuery job failure log:
EricSeastrand commented on May 27, 2024•
For anyone else facing this, here's the exact code that worked for me:
from google.cloud import bigquery
client = bigquery.Client(client_options={
"scopes": ['https://www.googleapis.com/auth/drive', 'https://www.googleapis.com/auth/cloud-platform']
})
results = client.query_and_wait(sql)
During the bigquery.Client connection I had to pass the above scopes and there is no problem with authorizations in Sheets/Drive access anymore.
I used to run some functions developed and deployed on Google Cloud Run Functions.
Some of them are scheduled to run via Cloud Scheduler.
Last time I decided to copy the definition of the Cloud Scheduler job from bot 2 to my new bot3 function. And I started to get 401 unauthenticated errors for bot3, but the same definition was working fine for bot2.
The error looks like below:
debugInfo: "URL_ERROR-ERROR_AUTHENTICATION. Original HTTP response code number = 401"
jobName: "projects/....../locations/europe-west6/jobs/......"
status: "UNAUTHENTICATED"
targetType: "HTTP"
and in the Cloud Function log is the misleading:
The request was not authorized to invoke this service. Read more at https://cloud.google.com/run/docs/securing/authenticating Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#401
BUT – actually the problem is that during the copy of the scheduler job definition, the “Audience” value IS NOT updated with the new function URL (in my case bot3), but the old function URL is kept. It seems like it was autofilled in bot2 definition though and I didn’t noticed it. So be sure that URL and Audience are properly set!
If you fix this the 401 error is solved and gone!!!
I hope I saved you some time. Post one thanks in comments if so …
При преподписване на договор с A1 (2024 година) започнаха да пращат на потърпевшите абонати реклами за гледане на мачове, резултати и т.н.
За да се спре този тормоз трябва да се изпрати на номер 1516 SMS със съдържание: СТОП
И при успешно изпълнена заявка би трябвало до няколко минути да върне, че е спряна услугата. Както практиката показва може да получите още 1-2 съобщения в следващите минути и след това спират.