🐛 [FirestoreFirebase] FireStore Error

Performing hot restart...
Syncing files to device SM A260G...
Restarted application in 4 166ms.

======== Exception caught by widgets library =======================================================
The following _CastError was thrown building StreamBuilder<QuerySnapshot<Map<String, dynamic>>>(dirty, state: _StreamBuilderBaseState<QuerySnapshot<Map<String, dynamic>>, AsyncSnapshot<QuerySnapshot<Map<String, dynamic>>>>#dbd11):
Null check operator used on a null value

The relevant error-causing widget was:
  StreamBuilder<QuerySnapshot<Map<String, dynamic>>> file:///Users/ppo/AndroidStudioProjects/monapp/lib/main.dart:30:18
When the exception was thrown, this was the stack:
#0      _MonAppState.build.<anonymous closure> (package:monapp/main.dart:34:40)
#1      StreamBuilder.build (package:flutter/src/widgets/async.dart:546:81)
#2      _StreamBuilderBaseState.build (package:flutter/src/widgets/async.dart:124:48)
#3      StatefulElement.build (package:flutter/src/widgets/framework.dart:4691:27)
#4      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4574:15)
...
====================================================================================================
W/DynamiteModule(25778): Local module descriptor class for providerinstaller not found.
I/DynamiteModule(25778): Considering local module providerinstaller:0 and remote module providerinstaller:0
W/ProviderInstaller(25778): Failed to load providerinstaller module: No acceptable module found. Local version is 0 and remote version is 0.
W/ResourceType(25778): ResTable_typeSpec entry count inconsistent: given 62, previously 64
D/ConnectivityManager(25778): requestNetwork; CallingUid : 10135, CallingPid : 25778
I/zygote  (25778): The ClassLoaderContext is a special shared library.
I/zygote  (25778): The ClassLoaderContext is a special shared library.
V/NativeCrypto(25778): Registering com/google/android/gms/org/conscrypt/NativeCrypto's 294 native methods...

======== Exception caught by widgets library =======================================================
The following _CastError was thrown building StreamBuilder<QuerySnapshot<Map<String, dynamic>>>(dirty, state: _StreamBuilderBaseState<QuerySnapshot<Map<String, dynamic>>, AsyncSnapshot<QuerySnapshot<Map<String, dynamic>>>>#dbd11):
Null check operator used on a null value

The relevant error-causing widget was:
  StreamBuilder<QuerySnapshot<Map<String, dynamic>>> file:///Users/ppo/AndroidStudioProjects/monapp/lib/main.dart:30:18
When the exception was thrown, this was the stack:
#0      _MonAppState.build.<anonymous closure> (package:monapp/main.dart:34:40)
#1      StreamBuilder.build (package:flutter/src/widgets/async.dart:546:81)
#2      _StreamBuilderBaseState.build (package:flutter/src/widgets/async.dart:124:48)
#3      StatefulElement.build (package:flutter/src/widgets/framework.dart:4691:27)
#4      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4574:15)
...
====================================================================================================
I/ProviderInstaller(25778): Installed default security provider GmsCore_OpenSSL
D/ConnectivityManager(25778): requestNetwork; CallingUid : 10135, CallingPid : 25778
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/Firestore(25778): (23.0.1) [OnlineStateTracker]: Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }
W/Firestore(25778): This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:111)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/libEGL  (25778): EGLNativeWindowType 0xd2c7f008 disconnect failed
W/libEGL  (25778): EGLNativeWindowType 0xd2c43808 disconnect failed
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}
W/Firestore(25778): (23.0.1) [WatchStream]: (cbed553) Stream closed with status: Status{code=UNAVAILABLE, description=Unable to resolve host firestore.googleapis.com, cause=java.lang.RuntimeException: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
W/Firestore(25778): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
W/Firestore(25778): 	at java.lang.Thread.run(Thread.java:764)
W/Firestore(25778): Caused by: java.net.UnknownHostException: Unable to resolve host "firestore.googleapis.com": No address associated with hostname
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:141)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:90)
W/Firestore(25778): 	at java.net.InetAddress.getAllByName(InetAddress.java:787)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
W/Firestore(25778): 	at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404)
W/Firestore(25778): 	... 5 more
W/Firestore(25778): Caused by: android.system.GaiException: android_getaddrinfo failed: EAI_NODATA (No address associated with hostname)
W/Firestore(25778): 	at libcore.io.Linux.android_getaddrinfo(Native Method)
W/Firestore(25778): 	at libcore.io.ForwardingOs.android_getaddrinfo(ForwardingOs.java:59)
W/Firestore(25778): 	at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:122)
W/Firestore(25778): 	... 9 more
W/Firestore(25778): }.
W/ManagedChannelImpl(25778): [{0}] Failed to resolve name. status={1}

i am trying to retreive data fron firestore but it doesn't work. it gives me le message below can someone help fix the issue.

Hi @makecrepin
Could you please provide your flutter doctor -v and flutter pub deps -- --style=compact?
Can you provide a minimal complete reproducible code sample?
Thank you

It was all about the network, my emmulator was too slow. now that i'm using a real phone every thing is fine

Thank you

Closing this as not a Flutterfire issue based on above comment.


chore(deps): bump bulk import backend plugin to 1.5.2

Description
Changelog:

https://github.com/janus-idp/backstage-plugins/pull/2163

Which issue(s) does this PR fix
—
PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer
/cc @subhashkhileri

/cherry-pick 1.3.x

/lgtm
/approve

@rm3l: #1618 failed to apply on top of branch "1.3.x":
Applying: chore(deps): bump bulk import backend plugin to 1.5.2
Using index info to reconstruct a base tree...
M	dynamic-plugins/imports/package.json
Falling back to patching base and 3-way merge...
Auto-merging dynamic-plugins/imports/package.json
CONFLICT (content): Merge conflict in dynamic-plugins/imports/package.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore(deps): bump bulk import backend plugin to 1.5.2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Manually bumped in this PR: https://github.com/janus-idp/backstage-showcase/pull/1612


Feature idea: Cache the csv data to minimize traffic and load for the raw csv data source

At the moment with every page load on covidtrends the according raw csv data is pulled. I don't know the page impressions for covidtrend but it could sum up in api requests for the csv data source as well. How about to pull the csv data once a day around the announced times and then utilize those pulled and cached csv data instead of loading the data again from the source on each load?

Would have also the positive side effect that the graph could still show while Github is down ;) Cuz current state for covidtrends is:


x/crypto/acme/autocert: new certificate rejected by Chrome client for 1h if client's clock is behind.

What version of Go are you using (go version)?

$ go version
go version go1.14.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="off"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/h8liu/Library/Caches/go-build"
GOENV="/Users/h8liu/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/h8liu/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4l/dcqzjhqn65gggmw9qrlnksx00000gn/T/go-build462787337=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

use autocert to host a new site
change client's system clock to 3 second behind UTC. (1 second would also work).
visit the site with Google Chrome, the site will be rejected due to SCT timestamp was in the past.
in fact, even 5 seconds later, when the certificate is valid again, the site will still get rejected.

Chrome version: 83.0.4103.97
What did you expect to see?
Certificate won't get rejected, at least not for one hour.
I think the rejection can also happen when the visit is on a new renewal, but renewals often happen in the background, so it is slightly harder to hit the particular time window in a debug session.
What did you see instead?
Certificate got rejected for 1 hour.

to be fair, I think the root cause is on chrome browser side. I also filed the issue to chrome, and chrome marked it as won't fix:
https://bugs.chromium.org/p/chromium/issues/detail?id=1093183
so one mitigation autocert can have, is to have an config to optionally insert a sleeping delay after a certificate is issued and before the certificate can be returned to a GetCertificate() call.

Thank you for raising this issue. Given that Chrome have decided they will not address the certificate caching in the browser, I'm not sure what can or should be fixed on the Go side. The server running autocert should try to keep its clock in sync -- although I appreciate how hard accurate time keeping is these days.
Sleeping for an amount of time greater than the system's clock drift is an answer to the problem, but I don't think it is a good answer to the problem because this is fundamentally a caching problem on the browser. Any delaying returning from the certificate generation call is always a guess against unknown clock skew on the client.

Given the update on side of the chrome bug, it seems that the invalid result caching issue (invalid for 30+ minutes) will go away eventually.
The client clock skew/drift issue will still be there though: 1st time visit has a chance that the cert will be rejected for a short time (which also can happen in background refreshing scenarios when the client hits the exact time window), and you are right that it is a guess on the client side's system time error.
Based on my understanding, letsencrypt already had a guess (in the old days), which is 1 hour. That is a certificate issued at say 3pm will have NotValidBefore set to 2pm.
Assuming that nowadays most clients (that check SCTs) sync system time from the Internet, I think adding even just a 1-second sleep would greatly mitigate the issue in practice. I was hoping that this can be an config option where default is 0, but the server hosting user can set to a small time duration.
I am not sure what will be a better solution either.. maybe the client should compare the SCT timestamp with a queried time from the SCT's signing server (rather than local system time)?

Related: https://community.letsencrypt.org/t/possible-race-condition-observed-with-autocert/137271


clang v3.6.2 supported?

the Clang.jl README says >=3.1 is supported.  is there an upper limit?  i ask because  on OS X El Capitan with Julia 0.4.0 distributed and Homebrew LLVM 3.6.2, i get a 'clang-c/Index.h' file not found error.  (3.4.2 kinda works, but see https://github.com/ihnorton/Clang.jl/issues/147.)
julia> ENV["LLVM_CONFIG"]="/usr/local/Cellar/llvm/3.6.2/bin/llvm-config"
"/usr/local/Cellar/llvm/3.6.2/bin/llvm-config"

julia> Pkg.add("Clang")
INFO: Initializing package repository /Users/arthurb/.julia/v0.4
INFO: Cloning METADATA from git://github.com/JuliaLang/METADATA.jl
INFO: Installing Clang v0.1.0
INFO: Installing Compat v0.7.7
INFO: Installing DataStructures v0.3.13
INFO: Installing Docile v0.5.19
INFO: Building Clang
g++ wrapclang.cpp -fPIC -c -o wrapclang.cpp.o -I/usr/local/Cellar/llvm/3.6.2/include -g -Wall -Wno-strict-aliasing -fno-omit-frame-pointer -fPIC
wrapclang.cpp:7:10: fatal error: 'clang-c/Index.h' file not found
#include "clang-c/Index.h"
         ^
1 error generated.
make: *** [wrapclang.cpp.o] Error 1
================================[ ERROR: Clang ]================================

LoadError: failed process: Process(`make`, ProcessExited(2)) [2]
while loading /Users/arthurb/.julia/v0.4/Clang/deps/build.jl, in expression starting on line 19

================================================================================

================================[ BUILD ERRORS ]================================

WARNING: Clang had build errors.

 - packages with build errors remain installed in /Users/arthurb/.julia/v0.4
 - build the package(s) and all dependencies with `Pkg.build("Clang")`
 - build a single package by running its `deps/build.jl` script

================================================================================
INFO: Package database updated

julia>

Do you have the libclang headers installed? See https://github.com/Gnurou/kdevelop/issues/10 for example.

i did a search on the error msg too, and found that very same page.  notice that to fix it they had to downgrade from clang 3.3 to 3.2.
i do have headers installed, but there is no clang-c directory.  there is an llvm-c directory, but it doesn not contain an Index.h file:
$ ls /usr/local/Cellar/llvm/3.6.2/include/llvm-c/
Analysis.h		Disassembler.h		LinkTimeOptimizer.h	Target.h
BitReader.h		ExecutionEngine.h	Linker.h		TargetMachine.h
BitWriter.h		IRReader.h		Object.h		Transforms/
Core.h			Initialization.h	Support.h		lto.h

That still sounds like a installation problem.
The file certainly exist on my ArchLinux clang 3.7.0 and also on ubuntu libclang-3.6-dev and is also in the pre-built tarball for ubuntu 15.04 from llvm's site (I didn't check other binaries there but I imagine they all have this file).

Yes, I've used this up to llvm 3.8.
On Mon, Nov 9, 2015 at 1:25 PM, Yichao Yu<EMAIL_ADDRESS>wrote:

That still sounds like a installation problem.
The file certainly exist on my ArchLinux clang 3.7.0 and also on ubuntu
libclang-3.6-dev and is also in the pre-built tarball for ubuntu 15.04 from
llvm's site (I didn't check other binaries there but I imagine they all
have this file).
—
Reply to this email directly or view it on GitHub
https://github.com/ihnorton/Clang.jl/issues/148#issuecomment-155146801.

it was indeed an install problem.  please consider https://github.com/ihnorton/Clang.jl/pull/149 to make it easier for others.


Expose tmt version as an environment variable

Fixes: #2267

@idorax please, add the variable to README.rst as well, there's a list of variables exposed by tmt, this one should be documented there.

@idorax please, add the variable to README.rst as well, there's a list of variables exposed by tmt, this one should be documented there.

Just added TMT_VERSION to Step Variables, not sure it should be added to Command Variables. @happz, please correct me if it's incorrect, thanks!

Correct, no command variable as those are accepted by tmt - not the case of TMT_VERSION :)

Hi @happz, looks the test failures from testing-farm:fedora-39-x86_64 are not relevant to this patch. e.g.

/tests/execute/upgrade/simple      no package provides beakerlib
      Fedora 37 - x86_64                              535  B/s | 3.3 kB     00:06
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      stderr (4 lines)
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      Errors during downloading metadata for repository 'fedora':
        - Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64&countme=1 (IP: <IP_ADDRESS>)
        - Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64 (IP: <IP_ADDRESS>)
      Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64 (IP: <IP_ADDRESS>)

 /tests/prepare/install      Downloading Packages:
      The downloaded packages were saved in cache until the next successful transaction.
      You can remove cached packages by executing 'dnf clean packages'.
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      stderr (2 lines)
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      Error: Error downloading packages:
        Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f38&arch=x86_64 (IP: <IP_ADDRESS>)
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      :: [ 02:14:16 ] :: [   FAIL   ] :: Command 'tmt run -adddvvvr plan --name exclude' (Expected 0, got 2)

/packit retest-failed


Clean up dependency installation in stf-run-ci

Clean up the dependency installation when not using index images (which
installs dependencies via dependencies.yaml). Adjust installation of
cert-manager for versions of OCP 4.10 vs 4.12 and later.

Deployment was successful using following command:
ansible-playbook -e __local_build_enabled=true build/run-ci.yaml

TASK [stf-run-ci : Create ServiceTelemetry instance] **********************************************************************************************************************************************************
changed: [localhost]

TASK [stf-run-ci : Validate system is operational] ************************************************************************************************************************************************************
changed: [localhost]

TASK [stf-run-ci : debug] *************************************************************************************************************************************************************************************
ok: [localhost] => {
    "validate_deployment.stdout_lines": [
        "Already on project \"service-telemetry\" on server \"https://console-openshift-console.apps.stf15comm.rhos-d.infra.prod.upshift.rdu2.redhat.com:6443\".",
        "",
        "* [info] Waiting for QDR deployment to complete",
        "",
        "Waiting for deployment \"default-interconnect\" rollout to finish: 0 of 1 updated replicas are available...",
        "deployment \"default-interconnect\" successfully rolled out",
        "",
        "* [info] Waiting for prometheus deployment to complete",
        "",
        "Waiting for 1 pods to be ready...",
        "statefulset rolling update complete 1 pods at revision prometheus-default-8547b66858...",
        "",
        "* [info] Waiting for alertmanager deployment to complete",
        "",
        "statefulset rolling update complete 1 pods at revision alertmanager-default-56cd4b979...",
        "",
        "* [info] Waiting for smart-gateway deployment to complete",
        "",
        "Waiting for deployment \"default-cloud1-coll-meter-smartgateway\" rollout to finish: 0 of 1 updated replicas are available...",
        "deployment \"default-cloud1-coll-meter-smartgateway\" successfully rolled out",
        "deployment \"default-cloud1-ceil-meter-smartgateway\" successfully rolled out",
        "deployment \"default-cloud1-sens-meter-smartgateway\" successfully rolled out",
        "",
        "* [info] Waiting for all pods to show Ready/Complete",
        "",
        "",
        "* [info] CI Build complete. You can now run tests."
    ]
}

PLAY RECAP ****************************************************************************************************************************************************************************************************
localhost                  : ok=124  changed=43   unreachable=0    failed=0    skipped=15   rescued=0    ignored=0

oc get sub,csv,pod
NAME                                                                                PACKAGE                                SOURCE                CHANNEL
subscription.operators.coreos.com/amq7-interconnect-operator                                                         amq7-interconnect-operator             redhat-operators      1.10.x
subscription.operators.coreos.com/elasticsearch-eck-operator-certified                                               elasticsearch-eck-operator-certified   certified-operators   stable
subscription.operators.coreos.com/openshift-cert-manager-operator-stable-v1-redhat-operators-openshift-marketplace   openshift-cert-manager-operator        redhat-operators      stable-v1

NAME                                                                                DISPLAY                                       VERSION          REPLACES                                      PHASE
clusterserviceversion.operators.coreos.com/amq7-interconnect-operator.v1.10.17           Red Hat Integration - AMQ Interconnect        1.10.17          amq7-interconnect-operator.v1.10.4            Succeeded
clusterserviceversion.operators.coreos.com/cert-manager-operator.v1.11.4                 cert-manager Operator for Red Hat OpenShift   1.11.4                                                         Succeeded
clusterserviceversion.operators.coreos.com/elasticsearch-eck-operator-certified.v2.9.0   Elasticsearch (ECK) Operator                  2.9.0            elasticsearch-eck-operator-certified.v2.8.0   Succeeded
clusterserviceversion.operators.coreos.com/observability-operator.v0.0.25                Observability Operator                        0.0.25                                                         Succeeded
clusterserviceversion.operators.coreos.com/service-telemetry-operator.v1.5.1694550744    Service Telemetry Operator                    1.5.1694550744                                                 Succeeded
clusterserviceversion.operators.coreos.com/smart-gateway-operator.v5.0.1694550736        Smart Gateway Operator                        5.0.1694550736                                                 Succeeded

NAME                                                           READY   STATUS      RESTARTS       AGE
pod/alertmanager-default-0                                     3/3     Running     0              172m
pod/cert-manager-operator-controller-manager-bc5697c44-wplm9   2/2     Running     0              3h5m
pod/default-cloud1-ceil-event-smartgateway-c64889859-qrwpd     2/2     Running     0              172m
pod/default-cloud1-ceil-meter-smartgateway-7d54b48686-7gnzx    3/3     Running     0              172m
pod/default-cloud1-coll-event-smartgateway-95978bf8c-qltns     2/2     Running     0              172m
pod/default-cloud1-coll-meter-smartgateway-59bb9fc985-wx9dh    3/3     Running     0              172m
pod/default-cloud1-sens-meter-smartgateway-6d56f55bf4-nc8qr    3/3     Running     0              172m
pod/default-interconnect-7cc45b86c5-phtf8                      1/1     Running     0              173m
pod/default-snmp-webhook-5c7c44d97c-62r49                      1/1     Running     0              172m
pod/elastic-operator-77cdc8754c-s89rf                          1/1     Running     4 (107m ago)   3h5m
pod/elasticsearch-es-default-0                                 1/1     Running     0              3h5m
pod/interconnect-operator-7bb99c5ff4-5xv4x                     1/1     Running     0              3h5m
pod/prometheus-default-0                                       3/3     Running     0              172m
pod/prometheus-webhook-snmp-2-build                            0/1     Completed   0              175m
pod/service-telemetry-operator-2-build                         0/1     Completed   0              3h4m
pod/service-telemetry-operator-7fc6c94bb8-kb2gf                1/1     Running     0              173m
pod/sg-bridge-2-build                                          0/1     Completed   0              179m
pod/sg-core-2-build                                            0/1     Completed   0              3h2m
pod/smart-gateway-operator-2-build                             0/1     Completed   0              3h3m
pod/smart-gateway-operator-dbdb9fb94-gssdv                     1/1     Running     0              173m

oc get sub,csv -nopenshift-operators
NAME                                                       PACKAGE                  SOURCE                CHANNEL
subscription.operators.coreos.com/observability-operator   observability-operator   community-operators   stable

NAME                                                                        DISPLAY                  VERSION   REPLACES   PHASE
clusterserviceversion.operators.coreos.com/observability-operator.v0.0.25   Observability Operator   0.0.25               Succeeded


Pinguin2001.PenguinTo-Do version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

How can I add it to my manifest?

If you're talking about your WinGet package, it's not possible.
If you're talking about your AppX package, it's already listed.
Add-AppxPackage which is what WinGet uses, doesn't install any dependencies, even if you've listed them in AppxManifest.xml.

Also, is there any way to specify that an certificate should be installed alongside?

At the moment, no.
Your PR will not pass without a certificate from Microsoft Partner Center or from Code Signing because it's compulsory for all MSIX/APPX packages.

Also, is there any way to specify that an certificate should be installed alongside?

No.
Your pull request will not pass without a certificate signed from Microsoft or other publishers that do code signing because it's compulsory for all MSIX/APPX packages.

Then I will write my own installer for it so people can install my app more easily without me needing to pay for an certificate, thank you for your time ItzLevvie!


Update to 4.1

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Closes #21

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

This is ready for review. I've updated the build to use cmake, updated the dependencies for building and removed the two patches which are now obsolete.

@conda-forge-admin , please rerender

Thanks for your contribution! :)


Update state store in bulk in compaction job creation Lambda

Background
We've seen a lot of flakiness in the MultipleTablesIT system test, and some of that is coming from the compaction job creation Lambda taking a very long time to update the state store. This slowness also makes that test impractically slow, so we can't easily re-run it to solve the problems we're having.
Description
We'd like the compaction job creation Lambda to be able to update the state store as a single operation. This should happen across all tables, for all compaction jobs that were created.
Analysis
The lambda uses the class CreateJobs to create the compaction jobs and update the state store. We can refactor that to separate the state store update from the creation of compaction jobs.

I've tried this, and it seems to complicate the logic quite a lot. It also could detach the state store update considerably from when the job is put on the SQS queue. That makes the compaction job will start before the state store update finishes. It also seems more likely for the state store update to fail.
It seems much simpler to parallelise it, as in https://github.com/gchq/sleeper/issues/1385. I'm closing this one, we can do that instead.


keyListToProtobuf() does not handle KeyList with a threshold

Heh, I should of closed this issue because I fixed it soon after I made this issue: https://github.com/hashgraph/hedera-sdk-js/commit/8314a8371835cbee14135d30ba0ab5bd7958dbff
However, there are other issues that can be worked on; if you'd like to take some issue please let me know and I will assign it to you.


Adding an initContainer for the git cache

To, hopefully, help thwart the thundering herd problem we have if/when the git cache gets wiped, I'm adding an InitContainer that will perform either of the following operations based on the contents of the mounted PVC volume:

Prime a newly created PVC with an initial changelog from the latest 4-stable and 4-dev-preview releases (takes roughly 12 minutes)
Perform git maintenance on all the existing repositories that are present on the PVC (takes roughly 8 minutes)

/hold


Remove fetch and Promise polyfills

See #57.
I feel like there must be a more elegant way to patch fetch in node, but maybe this is fine?

Sorry, this was silly. Will reopen when I have this figured out.


Fix illegal atomic initialization

See https://stackoverflow.com/a/21710850 for an extensive discussion.

Friendly ping :kiss:

Merged internally, you should see it propagated here in a few weeks.


test PR

Change description
test PR
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Created for simple test, now closing


Superset + Impala get error:'NoneType' object has no attribute 'get'

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.18.5
Expected results
{"error": "Connection failed!\n\nThe error message returned was:\n'NoneType' object has no attribute 'get'"}
Actual results
Steps to reproduce

That's a very generic error, please share the full stack trace.


Extract forward declaration of stan::math::var_value into its own header

See #2430 for context.
This pull request would enable external code to also take advantage of forward declarations of the templated var_value by extracting the relevant forward declaration lines from vari.hpp into their own header, var_values_fwd_declare.hpp.  It then #includes this new header in vari.hpp.
It may make sense to do something similar with other forward declarations (I saw another for vari_value in that same file, and a few others when grepping around in other places).  But I don't know how externally-facing those other instances are meant to be, whereas var (==var_value<double>) is definitely user-facing.
I don't expect this to have any side effects.

@SteveBronder @rok-cesnovar this all look good? Seems fine to me.

Looks good, not sure of the name stan/math/rev/core/var_value_fwd_declare.hpp but I dont have a better suggestion...

Alright since we got two looks goods let's just merge away. If there's another change we need, our tests are down to 4 hours now!

Alright @rybern you should be free to do the free stuff!

Thanks everybody!


Defocus iframe on blur or mouseout (#22153)

Fixes #22153

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damondouglas

Please hold this PR. It uses my personal package. We have decided to re-publish it at Akvelon's pub.dev account. We are busy doing this now.

Before:

After:

(Note that we lose selection when moving mouse pointer out from the iframe.)

I also took this chance to rename enabled param to editable. enabled was vague, it gives an impression that disabled playground is unable to run the code. editable is more precise.
I did it in this branch because it is likely the fastest way to deploy it, and we want this change before URLs start to spread.


onnxruntime training

I am wondering whether it would be possible to add support for onnxruntime training to onnruntime_go. It would be particularly interesting to be able to train models on user feedback on device. Would it be something you would consider as an addition? I believe it could be done with bindings to onnxruntime training, see https://onnxruntime.ai/docs/install/#training-phase---on-device-training

It looks like you're correct in that there's a C API so it should be possible to add Go bindings (C API example in docs).  However, it looks like it would be a significant addition, since I would need to add another header, another Session type, and bindings for every function in the training C API header.  On top of that, for the training API to be easy to test, the .shared libraries in test_data/ would need to be swapped out for the versions that include training support.  This, of course, is doable, but I'm already not happy with how large the test_data directory has become.  So, some thought would need to be given to how to make the tests work OK.  (Though on the other hand, the test_data/ libraries already don't support CUDA, so I suppose there's precedent for skipping tests here.)
Honestly, that all seems doable enough---though the other issue is that I am unlikely to use it personally.  So, I suppose my stance is that I'd be happy to review a PR if someone else is willing to do a lot of the work!  Here are the things that I would want to see in a potential PR:

A new .go file for the bindings, say training_api.go.

This would contain a TrainingSession type that would follow the style of AdvancedSession
This would also invoke all of the C API functions.
We'd want something like func TrainingSupported() error that returns an error if the training API is not supported in the shared library.

onnxruntime_wrapper.c and onnxruntime_wrapper.h would need to expose pure C functions.

A static const OrtTrainingApi *training_api; would need to be added to onnxruntime_wrapper.c similar to the current static const OrtApi.
SetApiFromBase (in onnxruntime_wrapper.c) could be modified to attempt to call ort_api->GetTrainingApi(ORT_API_VERSION).  This returns NULL if training isn't supported.
Every function that uses the training API must check that training_api is not NULL---I want to make it completely impossible to cause a segfault from attempting to use the training API in Go.  (It's probably better to just use the TrainingSupported go function I mentioned above.)

A new test file for the bindings, like training_api_test.go

These unit tests should skipped if the training API isn't supported in the version of onnxruntime.so in test_data/ or indicated by the ONNXRUNTIME_SHARED_LIBRARY_PATH environment variable used by the other tests.
A minimal test case that would be easy to validate.  For example, I'd want to have a unit test that would train a small network to add two inputs.  The test would need to use the training API to create and train the network, then test it on a bunch of outputs to make sure it's fairly close to the expected behavior.
A basic benchmark test (run via go test -v -bench=.), similar to what I have with BenchmarkCUDASession in onnxruntime_test.go.  I'd want a benchmark for training using both CUDA and plain CPU.

Adding the onnxruntime_training_c_api.h header---but nothing else.  I don't want to start copying entire include/ directories from onnxruntime.  (And no C++ anywhere.)
Being a larger change, I'd be more picky that the code matches my personal style---so religiously following gofmt, plus 80-character lines.

Ok, clear. I am interested in using this capability from go, so I might give it a try to implement this bit.


MAINT: support for new "actions" API Results type

The results tuple type-check was too specific.

Looks good @jairideout, 👍 !
Merge pending qiime2/qiime2/pull/118


helper-cli: Add a command to export curations from package configs

This enables a workflow similar to what we already have for repository configurations.

Please note that this conflicts with https://github.com/oss-review-toolkit/ort/pull/3874, but I can rebase my PR (yet again).


Official example out of date

Not 100% sure, but it appears the "Official Example" linked in the README is out of date:
https://github.com/nuxt/nuxt.js/tree/dev/examples/vue-apollo

@leveloid can you open an issue on the https://github.com/nuxt/nuxt.js repo as the code example there is out of date. Thanks!


Fix jenkins after specialist-publisher rename

This will make the tests run properly.

👍
Do we need to update the jenkins job that triggers all schema tests?

No, that'll keep working.


dtrace user stacks not generating

Hi,
I'm identify some useful metrics to use with powermetrics, dtrace, rust, and tokio. I've found tokio-metrics and other utilities, but I can't seem to get dtrace to work with mini-redis. Here is the interesting part about it, I can run the following command on another project using tokio for the PID[12345] selected.
$ sudo dtrace -x ustackframes=100 -n "profile-97 /pid == 12345 / { @[ustack()] = count(); } tick-60s { exit(0); }" -o user.stacks

Why am I opening this ticket here when the issue is with dtrace? I'd like to know, is this project doing anything sparsely different from the norm of writing rust code? If so, where is that sparsely different thing?

Oie, so I managed to figure out the answer. Turns out when the server is idle. There are no stack traces to capture.
$ RUST_LOG=debug cargo run --bin mini-redis-server --release

The moment information starts being sent to the server via a client, stack traces are generated/captured


Materials count rise w hot reload

When running a preview, every time you do a hot reload, the materials in the scene get re-counted. This leads to the warnings about materials limit appearing for scenes that aren't really over the limits
Try this scene out, check the materials count with by opening the tab with the key Y
dclTest.zip
every time you do a change to game.ts to trigger a hot reload, notice that the materials count rises by 1
Try instead commenting out lines 41 & 42, and uncomment lines 22 & 23 (exactly the same content, but outside a function)
Once you do this and do a manual reload on the browser tab, the materials count will stop rising.
Somehow, the material creation happening outside the function is being properly cleared up from memory, but when it's part of a function it's not getting purged by hot reload

Looks like this problem is happening with creating/destroying entities with Materials. It's ignoring the destruction at least on the counter.
Scene to test: https://github.com/decentraland-scenes/conway-game-of-life


Transferring datasets

Three of the sports datasets have been transferred to the new format, however an error in subreddits.py appears to be preventing the test from running. I thought I would push what I have done so far anyway...

@aidanscienz, try running git pull against the aorist repo - that error should be fixed in the latest version.

All of the Sports datasets are now in the correct format as well as two of the Covid datasets. The init.py file still needs to be adjusted so that the conda build runs correctly.

For quick testing:
PYTHONPATH=aorist:aorist_recipes:scienz python

And then: import scienz

The subreddits files are still preventing the conda build from running successfully.
text_template = DatumTemplate(Text(name="corpus"))
NameError: name 'Text' is not defined
When the subreddits files are commented out (not imported) the conda build runs successfully, implying that the sports and covid files are fine.


Env based maintenance windows

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Plan Result (sbox-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:sbox",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in sbox environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for sbox environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:sbox",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for sbox"
          + disable_synthetic = false
          + name              = "Planned Blackout in sbox"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Plan Result (ptlsbox-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:ptlsbox",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in ptlsbox environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for ptlsbox environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:ptlsbox",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for ptlsbox"
          + disable_synthetic = false
          + name              = "Planned Blackout in ptlsbox"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Plan Result (test-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:perftest",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in perftest environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for perftest environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:perftest",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for perftest"
          + disable_synthetic = false
          + name              = "Planned Blackout in perftest"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Plan Result (ithc-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:ithc",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in ithc environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for ithc environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:ithc",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for ithc"
          + disable_synthetic = false
          + name              = "Planned Blackout in ithc"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Plan Result (stg-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:aat",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in aat environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for aat environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:aat",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for aat"
          + disable_synthetic = false
          + name              = "Planned Blackout in aat"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Plan Result (demo-dt-availability-dashboards)
Plan: 2 to add, 0 to change, 0 to destroy.

Create

dynatrace_maintenance.auto_shutdown_blackout
dynatrace_maintenance.planned_blackout

Change Result (Click me)

  # dynatrace_maintenance.auto_shutdown_blackout will be created
  + resource "dynatrace_maintenance" "auto_shutdown_blackout" {
      + enabled = true
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:demo",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "All nonprod envs besides AAT are shutdown out of hours. This maintenance window stops alerting and HTTP monitors for all HTTP monitors in demo environment. The maintenance window starts after this as the clusters take some time to build."
          + disable_synthetic = true
          + name              = "Auto-Shutdown Blackout for demo environment."
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "DAILY"

          + daily_recurrence {
              + recurrence_range {
                  + end_date   = "2023-01-31"
                  + start_date = "2030-01-01"
                }

              + time_window {
                  + end_time   = "08:30:00"
                  + start_time = "20:00:00"
                  + time_zone  = "UTC"
                }
            }
        }
    }

  # dynatrace_maintenance.planned_blackout will be created
  + resource "dynatrace_maintenance" "planned_blackout" {
      + enabled = false
      + id      = (known after apply)

      + filters {
          + filter {
              + entity_tags = [
                  + "ENVIRONMENT:demo",
                ]
              + entity_type = "HTTP_CHECK"
            }
        }

      + general_properties {
          + description       = "Temporary planned Maintenance Window to stop alerting on likely failing HTTP checks for demo"
          + disable_synthetic = false
          + name              = "Planned Blackout in demo"
          + suppression       = "DONT_DETECT_PROBLEMS"
          + type              = "PLANNED"
        }

      + schedule {
          + type = "ONCE"

          + once_recurrence {
              + end_time   = "2023-01-30T20:00:00"
              + start_time = "2023-01-30T19:00:00"
              + time_zone  = "UTC"
            }
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.


pio command not found

[X ] I have reset Atom to defaults prior to submitting report.
[ ] I have not reset Atom to defaults prior to submitting report.

Description

Pio command not found on terminal when i want to use serial monitor
Steps to reproduce

Open serial monitor and terminal can't find pio command

Expected behavior:
Serial monitor show serial messages
Actual behavior:
Terminal can't find pio command
Reproduces how often:
Versions

> atom --version
Atom    : 1.34.0
Electron: 2.0.16
Chrome  : 61.0.3163.100
Node    : 8.9.3

> apm --version
apm  2.1.3
npm  6.2.0
node 8.9.3 x64
atom 1.34.0
python 2.7.16
git 2.20.1

OS name and version:
Distributor ID:	Debian
Description:	Debian GNU/Linux buster/sid
Release:	unstable
Codename:	sid
Platformio-ide-terminal version:
2.9.1
Additional Information

PATH enviroment variable of the terminal don't have the path for my pio command (on my home dir). Don't know how to set it.

echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

But my pio command is here:
/home/holic/bin/pio

Hello @holic-cl! Thank you for reaching out with this query.
You should probably symlink to the expected path in usr, alternatively try to export your home path.
To export, add a modified version of this (that suits your particular needs) to your .bashrc
export PATH="$HOME/bin:$PATH"
Without either a symlink or exporting the path its unlikely any terminal/shell will magically know where your own bins are stored.

Hi @ the-j0k3r thanks for your answer.
My .bashrc file already have my home path, this is the content of PATH var on my bash-terminal:

echo $ PATH
/home/holic/bin:/home/holic/.local/bin/:/home/holic/app/node-v11.10.0-linux-x64/bin:/usr/local/bin:/usr/bin:/ bin: / usr / local / games: / usr / games: /home/holic/.platformio/penv/bin: /home/holic/app/node_modules/.bin

Seems to be problem on the terminal where PATH var is not being exported from .bashrc file, do not know why, maybe i am missing a specific setting or reassigning the PATH in some place

@holic-cl does your setup work on a terminal besides platformio-ide-terminal or not?
Try to export the path once on the terminal and see if that does it.
Try on terminal.

export PATH="$PATH:/home/holic/bin/pio
Confirm that does it.

Else try.

echo export PATH="$PATH:/home/holic/bin/pio  >> ~/.bash_profile"

You can also export that path into .bashrc
The orther solution is symlinking
cd /usr/bin sudo ln -s /home/holic/bin pio
However if you are still getting issues you may want to relocate your binaries into their expected path rather than your home folders.

@the-j0k3r my problem is with atom terminal, which does not seem to read the .bashrc file, but i just tried with .bash_profile file as you suggest and it is working. I don't know if is normal to not read the .bashrc.
I was looking for a solution that did not involve the symbolic link, but i had it in mind.
Thank you a lot!

@the-j0k3r my problem is with atom terminal, which does not seem to read the .bashrc file, but i just tried with .bash_profile file as you suggest and it is working.

The problem here is that platformio-ide-terminal is using term.js to interact with system shells, etc, that library has been abandoned for years and its buggy. In order to improve these types issue, we would need to implement xterm.js  same as vscode uses, its currently developed, more compatible with different OS/shells terminals etc.
This project has no official developers anymore either (the main dev is just merging PR's and doing releases and Im sort of managing the bug tracker), anything like fixes/and switching to other libraries has to come from users, except this project doesnt have enough skilled users that want/can or have time to implement this much needed change. SO iunless someone comes along willing and able, this is it.
Glad my suggestion worked out for you in the end though =)


Make DBCamera compatible with framework

Load assets from bundle in current framework. This fixes #163.

Thanks @xhacker ! :+1:


English version of page with imperial units, contributors link, and a…

… few formatting fixes
English version of page with imperial units, contributors link that links to everyone who contributed, and a few formatting fixes to make the site look nicer

Hello my friend there are some conflictig files .
index.html | index_ES.html | index_it.html
We are setting locales, please fix it so I could maybe the merge. Thanks

done!


Fix Citadel using in-memory cert without writing to secret issue.

:thinking: :bug: You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

:thinking: :bug: You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: myidpt
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [myidpt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@myidpt: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@myidpt: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-mixer-no_auth

@myidpt: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-mixer-no_auth

@myidpt: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
4f1e54371133da8d1160c2c79c063542c47b3db6
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

prow/e2e-mixer-no_auth.sh is a known failure unrelated to this change

I agree this is the safest change for now while fixing this issue.
Oliver, could you file a github issue for feature improvement to add retry on network timeout? and assign an owner and make sure we keep track of that


[Runtime Security]Fix Techniques to Audits table

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--prisma-cloud-docs--hlxsites.hlx.page/
After: https://main--prisma-cloud-docs--hlxsites.hlx.page/
Worker: https://prisma-cloud-docs-production.adobeaem.workers.dev/?branch=attack-techniques

@rcaballeromx made a small fix. The sheet had spaces in the name, replaced it to have hyphens as separators.
I do not see the update in the preview here though. @iansk please take a look

@rcaballeromx The issue is not resolved. I've created a Jira issue to track the progress: CWP-57292.


大佬好，dataintegration.sql数据库脚本不全运行不起来

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.

你用的数据库版本是

5.7

打开dataintegration.sql文件就可以看到脚本不全，就只新建了一个表，执行到后面就报错了

你可以尝试通过dump 命令导入或者使用工具导入选择sql文件。这个sql其他拉取代码的人员是可以导入成功的