App wants to use your confidential info stored in firebase_auth with macos flutter

Description
As the title suggests, when I first submitted my app to testflight I noticed the dialog below. I found this issue on the firebase ios sdk repo. It should have been fixed. What I've done:

Updated to the latest firebase flutter libs. Specifically 4.1.5 firebase auth.
Enabled keychain sharing as described by the fix. I confirmed in the archive that the "keychain-access-groups" entitlement is present.

My observations.

When the firebase_auth keychain is not present, I can build the app in debug locally and it works fine.
With the keychain item now present, if I open a testflight build the dialog will always pop up until "Always Allow" is selected.
 But now pops up for my debug builds.
If I update the app through testflight the keychain dialog comes back.

I was hestitant to post this here. But since a previously opened issue is also happening to me I figured it makes sense.

Any help avoiding this keychain issue on update? My fear is every time a user updates the app in production they will be prompted to enter their keychain info. Currently I am testing with testflight, which should be a final build anyways.
Reproducing the issue

Use firebase auth 4.2.1.
Flutter 3.0.2
Need to be able to release on testflight using xcode archive.
Make sure a keychain was created in debug.
Opening in testflight build you will notice the popup.

Firebase SDK Version
10.0.0
Xcode Version
13.4.1
Installation Method
CocoaPods
Firebase Product(s)
Authentication
Targeted Platforms
macOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
No response
If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

PODS:
  - abseil/algorithm (1.20211102.0):
    - abseil/algorithm/algorithm (= 1.20211102.0)
    - abseil/algorithm/container (= 1.20211102.0)
  - abseil/algorithm/algorithm (1.20211102.0):
    - abseil/base/config
  - abseil/algorithm/container (1.20211102.0):
    - abseil/algorithm/algorithm
    - abseil/base/core_headers
    - abseil/meta/type_traits
  - abseil/base (1.20211102.0):
    - abseil/base/atomic_hook (= 1.20211102.0)
    - abseil/base/base (= 1.20211102.0)
    - abseil/base/base_internal (= 1.20211102.0)
    - abseil/base/config (= 1.20211102.0)
    - abseil/base/core_headers (= 1.20211102.0)
    - abseil/base/dynamic_annotations (= 1.20211102.0)
    - abseil/base/endian (= 1.20211102.0)
    - abseil/base/errno_saver (= 1.20211102.0)
    - abseil/base/fast_type_id (= 1.20211102.0)
    - abseil/base/log_severity (= 1.20211102.0)
    - abseil/base/malloc_internal (= 1.20211102.0)
    - abseil/base/pretty_function (= 1.20211102.0)
    - abseil/base/raw_logging_internal (= 1.20211102.0)
    - abseil/base/spinlock_wait (= 1.20211102.0)
    - abseil/base/strerror (= 1.20211102.0)
    - abseil/base/throw_delegate (= 1.20211102.0)
  - abseil/base/atomic_hook (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/base/base (1.20211102.0):
    - abseil/base/atomic_hook
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/log_severity
    - abseil/base/raw_logging_internal
    - abseil/base/spinlock_wait
    - abseil/meta/type_traits
  - abseil/base/base_internal (1.20211102.0):
    - abseil/base/config
    - abseil/meta/type_traits
  - abseil/base/config (1.20211102.0)
  - abseil/base/core_headers (1.20211102.0):
    - abseil/base/config
  - abseil/base/dynamic_annotations (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/base/endian (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/base/errno_saver (1.20211102.0):
    - abseil/base/config
  - abseil/base/fast_type_id (1.20211102.0):
    - abseil/base/config
  - abseil/base/log_severity (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/base/malloc_internal (1.20211102.0):
    - abseil/base/base
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/raw_logging_internal
  - abseil/base/pretty_function (1.20211102.0)
  - abseil/base/raw_logging_internal (1.20211102.0):
    - abseil/base/atomic_hook
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/log_severity
  - abseil/base/spinlock_wait (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/core_headers
    - abseil/base/errno_saver
  - abseil/base/strerror (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/errno_saver
  - abseil/base/throw_delegate (1.20211102.0):
    - abseil/base/config
    - abseil/base/raw_logging_internal
  - abseil/container/common (1.20211102.0):
    - abseil/meta/type_traits
    - abseil/types/optional
  - abseil/container/compressed_tuple (1.20211102.0):
    - abseil/utility/utility
  - abseil/container/container_memory (1.20211102.0):
    - abseil/base/config
    - abseil/memory/memory
    - abseil/meta/type_traits
    - abseil/utility/utility
  - abseil/container/fixed_array (1.20211102.0):
    - abseil/algorithm/algorithm
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/throw_delegate
    - abseil/container/compressed_tuple
    - abseil/memory/memory
  - abseil/container/flat_hash_map (1.20211102.0):
    - abseil/algorithm/container
    - abseil/container/container_memory
    - abseil/container/hash_function_defaults
    - abseil/container/raw_hash_map
    - abseil/memory/memory
  - abseil/container/hash_function_defaults (1.20211102.0):
    - abseil/base/config
    - abseil/hash/hash
    - abseil/strings/cord
    - abseil/strings/strings
  - abseil/container/hash_policy_traits (1.20211102.0):
    - abseil/meta/type_traits
  - abseil/container/hashtable_debug_hooks (1.20211102.0):
    - abseil/base/config
  - abseil/container/hashtablez_sampler (1.20211102.0):
    - abseil/base/base
    - abseil/base/core_headers
    - abseil/container/have_sse
    - abseil/debugging/stacktrace
    - abseil/memory/memory
    - abseil/profiling/exponential_biased
    - abseil/profiling/sample_recorder
    - abseil/synchronization/synchronization
    - abseil/utility/utility
  - abseil/container/have_sse (1.20211102.0)
  - abseil/container/inlined_vector (1.20211102.0):
    - abseil/algorithm/algorithm
    - abseil/base/core_headers
    - abseil/base/throw_delegate
    - abseil/container/inlined_vector_internal
    - abseil/memory/memory
  - abseil/container/inlined_vector_internal (1.20211102.0):
    - abseil/base/core_headers
    - abseil/container/compressed_tuple
    - abseil/memory/memory
    - abseil/meta/type_traits
    - abseil/types/span
  - abseil/container/layout (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/meta/type_traits
    - abseil/strings/strings
    - abseil/types/span
    - abseil/utility/utility
  - abseil/container/raw_hash_map (1.20211102.0):
    - abseil/base/throw_delegate
    - abseil/container/container_memory
    - abseil/container/raw_hash_set
  - abseil/container/raw_hash_set (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/container/common
    - abseil/container/compressed_tuple
    - abseil/container/container_memory
    - abseil/container/hash_policy_traits
    - abseil/container/hashtable_debug_hooks
    - abseil/container/hashtablez_sampler
    - abseil/container/have_sse
    - abseil/memory/memory
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/utility/utility
  - abseil/debugging/debugging_internal (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/errno_saver
    - abseil/base/raw_logging_internal
  - abseil/debugging/demangle_internal (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/debugging/stacktrace (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/debugging/debugging_internal
  - abseil/debugging/symbolize (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/malloc_internal
    - abseil/base/raw_logging_internal
    - abseil/debugging/debugging_internal
    - abseil/debugging/demangle_internal
    - abseil/strings/strings
  - abseil/functional/bind_front (1.20211102.0):
    - abseil/base/base_internal
    - abseil/container/compressed_tuple
    - abseil/meta/type_traits
    - abseil/utility/utility
  - abseil/functional/function_ref (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/core_headers
    - abseil/meta/type_traits
  - abseil/hash/city (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
  - abseil/hash/hash (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/container/fixed_array
    - abseil/hash/city
    - abseil/hash/low_level_hash
    - abseil/meta/type_traits
    - abseil/numeric/int128
    - abseil/strings/strings
    - abseil/types/optional
    - abseil/types/variant
    - abseil/utility/utility
  - abseil/hash/low_level_hash (1.20211102.0):
    - abseil/base/config
    - abseil/base/endian
    - abseil/numeric/bits
    - abseil/numeric/int128
  - abseil/memory (1.20211102.0):
    - abseil/memory/memory (= 1.20211102.0)
  - abseil/memory/memory (1.20211102.0):
    - abseil/base/core_headers
    - abseil/meta/type_traits
  - abseil/meta (1.20211102.0):
    - abseil/meta/type_traits (= 1.20211102.0)
  - abseil/meta/type_traits (1.20211102.0):
    - abseil/base/config
  - abseil/numeric/bits (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/numeric/int128 (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/numeric/bits
  - abseil/numeric/representation (1.20211102.0):
    - abseil/base/config
  - abseil/profiling/exponential_biased (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
  - abseil/profiling/sample_recorder (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/synchronization/synchronization
    - abseil/time/time
  - abseil/random/distributions (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/random/internal/distribution_caller
    - abseil/random/internal/fast_uniform_bits
    - abseil/random/internal/fastmath
    - abseil/random/internal/generate_real
    - abseil/random/internal/iostream_state_saver
    - abseil/random/internal/traits
    - abseil/random/internal/uniform_helper
    - abseil/random/internal/wide_multiply
    - abseil/strings/strings
  - abseil/random/internal/distribution_caller (1.20211102.0):
    - abseil/base/config
    - abseil/base/fast_type_id
    - abseil/utility/utility
  - abseil/random/internal/fast_uniform_bits (1.20211102.0):
    - abseil/base/config
    - abseil/meta/type_traits
  - abseil/random/internal/fastmath (1.20211102.0):
    - abseil/numeric/bits
  - abseil/random/internal/generate_real (1.20211102.0):
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/random/internal/fastmath
    - abseil/random/internal/traits
  - abseil/random/internal/iostream_state_saver (1.20211102.0):
    - abseil/meta/type_traits
    - abseil/numeric/int128
  - abseil/random/internal/nonsecure_base (1.20211102.0):
    - abseil/base/core_headers
    - abseil/meta/type_traits
    - abseil/random/internal/pool_urbg
    - abseil/random/internal/salted_seed_seq
    - abseil/random/internal/seed_material
    - abseil/types/optional
    - abseil/types/span
  - abseil/random/internal/pcg_engine (1.20211102.0):
    - abseil/base/config
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/numeric/int128
    - abseil/random/internal/fastmath
    - abseil/random/internal/iostream_state_saver
  - abseil/random/internal/platform (1.20211102.0):
    - abseil/base/config
  - abseil/random/internal/pool_urbg (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/base/raw_logging_internal
    - abseil/random/internal/randen
    - abseil/random/internal/seed_material
    - abseil/random/internal/traits
    - abseil/random/seed_gen_exception
    - abseil/types/span
  - abseil/random/internal/randen (1.20211102.0):
    - abseil/base/raw_logging_internal
    - abseil/random/internal/platform
    - abseil/random/internal/randen_hwaes
    - abseil/random/internal/randen_slow
  - abseil/random/internal/randen_engine (1.20211102.0):
    - abseil/base/endian
    - abseil/meta/type_traits
    - abseil/random/internal/iostream_state_saver
    - abseil/random/internal/randen
  - abseil/random/internal/randen_hwaes (1.20211102.0):
    - abseil/base/config
    - abseil/random/internal/platform
    - abseil/random/internal/randen_hwaes_impl
  - abseil/random/internal/randen_hwaes_impl (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/numeric/int128
    - abseil/random/internal/platform
  - abseil/random/internal/randen_slow (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/numeric/int128
    - abseil/random/internal/platform
  - abseil/random/internal/salted_seed_seq (1.20211102.0):
    - abseil/container/inlined_vector
    - abseil/meta/type_traits
    - abseil/random/internal/seed_material
    - abseil/types/optional
    - abseil/types/span
  - abseil/random/internal/seed_material (1.20211102.0):
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/raw_logging_internal
    - abseil/random/internal/fast_uniform_bits
    - abseil/strings/strings
    - abseil/types/optional
    - abseil/types/span
  - abseil/random/internal/traits (1.20211102.0):
    - abseil/base/config
  - abseil/random/internal/uniform_helper (1.20211102.0):
    - abseil/base/config
    - abseil/meta/type_traits
    - abseil/random/internal/traits
  - abseil/random/internal/wide_multiply (1.20211102.0):
    - abseil/base/config
    - abseil/numeric/bits
    - abseil/numeric/int128
    - abseil/random/internal/traits
  - abseil/random/random (1.20211102.0):
    - abseil/random/distributions
    - abseil/random/internal/nonsecure_base
    - abseil/random/internal/pcg_engine
    - abseil/random/internal/pool_urbg
    - abseil/random/internal/randen_engine
    - abseil/random/seed_sequences
  - abseil/random/seed_gen_exception (1.20211102.0):
    - abseil/base/config
  - abseil/random/seed_sequences (1.20211102.0):
    - abseil/container/inlined_vector
    - abseil/random/internal/nonsecure_base
    - abseil/random/internal/pool_urbg
    - abseil/random/internal/salted_seed_seq
    - abseil/random/internal/seed_material
    - abseil/random/seed_gen_exception
    - abseil/types/span
  - abseil/status/status (1.20211102.0):
    - abseil/base/atomic_hook
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/container/inlined_vector
    - abseil/debugging/stacktrace
    - abseil/debugging/symbolize
    - abseil/functional/function_ref
    - abseil/strings/cord
    - abseil/strings/str_format
    - abseil/strings/strings
    - abseil/types/optional
  - abseil/status/statusor (1.20211102.0):
    - abseil/base/base
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/meta/type_traits
    - abseil/status/status
    - abseil/strings/strings
    - abseil/types/variant
    - abseil/utility/utility
  - abseil/strings/cord (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/base/raw_logging_internal
    - abseil/container/fixed_array
    - abseil/container/inlined_vector
    - abseil/functional/function_ref
    - abseil/meta/type_traits
    - abseil/strings/cord_internal
    - abseil/strings/cordz_functions
    - abseil/strings/cordz_info
    - abseil/strings/cordz_statistics
    - abseil/strings/cordz_update_scope
    - abseil/strings/cordz_update_tracker
    - abseil/strings/internal
    - abseil/strings/str_format
    - abseil/strings/strings
    - abseil/types/optional
  - abseil/strings/cord_internal (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/base/raw_logging_internal
    - abseil/base/throw_delegate
    - abseil/container/compressed_tuple
    - abseil/container/inlined_vector
    - abseil/container/layout
    - abseil/functional/function_ref
    - abseil/meta/type_traits
    - abseil/strings/strings
    - abseil/types/span
  - abseil/strings/cordz_functions (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/profiling/exponential_biased
  - abseil/strings/cordz_handle (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/raw_logging_internal
    - abseil/synchronization/synchronization
  - abseil/strings/cordz_info (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/container/inlined_vector
    - abseil/debugging/stacktrace
    - abseil/strings/cord_internal
    - abseil/strings/cordz_functions
    - abseil/strings/cordz_handle
    - abseil/strings/cordz_statistics
    - abseil/strings/cordz_update_tracker
    - abseil/synchronization/synchronization
    - abseil/types/span
  - abseil/strings/cordz_statistics (1.20211102.0):
    - abseil/base/config
    - abseil/strings/cordz_update_tracker
  - abseil/strings/cordz_update_scope (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/strings/cord_internal
    - abseil/strings/cordz_info
    - abseil/strings/cordz_update_tracker
  - abseil/strings/cordz_update_tracker (1.20211102.0):
    - abseil/base/config
  - abseil/strings/internal (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/base/raw_logging_internal
    - abseil/meta/type_traits
  - abseil/strings/str_format (1.20211102.0):
    - abseil/strings/str_format_internal
  - abseil/strings/str_format_internal (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/functional/function_ref
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/numeric/int128
    - abseil/numeric/representation
    - abseil/strings/strings
    - abseil/types/optional
    - abseil/types/span
  - abseil/strings/strings (1.20211102.0):
    - abseil/base/base
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/endian
    - abseil/base/raw_logging_internal
    - abseil/base/throw_delegate
    - abseil/memory/memory
    - abseil/meta/type_traits
    - abseil/numeric/bits
    - abseil/numeric/int128
    - abseil/strings/internal
  - abseil/synchronization/graphcycles_internal (1.20211102.0):
    - abseil/base/base
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/malloc_internal
    - abseil/base/raw_logging_internal
  - abseil/synchronization/kernel_timeout_internal (1.20211102.0):
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/time/time
  - abseil/synchronization/synchronization (1.20211102.0):
    - abseil/base/atomic_hook
    - abseil/base/base
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/dynamic_annotations
    - abseil/base/malloc_internal
    - abseil/base/raw_logging_internal
    - abseil/debugging/stacktrace
    - abseil/debugging/symbolize
    - abseil/synchronization/graphcycles_internal
    - abseil/synchronization/kernel_timeout_internal
    - abseil/time/time
  - abseil/time (1.20211102.0):
    - abseil/time/internal (= 1.20211102.0)
    - abseil/time/time (= 1.20211102.0)
  - abseil/time/internal (1.20211102.0):
    - abseil/time/internal/cctz (= 1.20211102.0)
  - abseil/time/internal/cctz (1.20211102.0):
    - abseil/time/internal/cctz/civil_time (= 1.20211102.0)
    - abseil/time/internal/cctz/time_zone (= 1.20211102.0)
  - abseil/time/internal/cctz/civil_time (1.20211102.0):
    - abseil/base/config
  - abseil/time/internal/cctz/time_zone (1.20211102.0):
    - abseil/base/config
    - abseil/time/internal/cctz/civil_time
  - abseil/time/time (1.20211102.0):
    - abseil/base/base
    - abseil/base/core_headers
    - abseil/base/raw_logging_internal
    - abseil/numeric/int128
    - abseil/strings/strings
    - abseil/time/internal/cctz/civil_time
    - abseil/time/internal/cctz/time_zone
  - abseil/types (1.20211102.0):
    - abseil/types/any (= 1.20211102.0)
    - abseil/types/bad_any_cast (= 1.20211102.0)
    - abseil/types/bad_any_cast_impl (= 1.20211102.0)
    - abseil/types/bad_optional_access (= 1.20211102.0)
    - abseil/types/bad_variant_access (= 1.20211102.0)
    - abseil/types/compare (= 1.20211102.0)
    - abseil/types/optional (= 1.20211102.0)
    - abseil/types/span (= 1.20211102.0)
    - abseil/types/variant (= 1.20211102.0)
  - abseil/types/any (1.20211102.0):
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/base/fast_type_id
    - abseil/meta/type_traits
    - abseil/types/bad_any_cast
    - abseil/utility/utility
  - abseil/types/bad_any_cast (1.20211102.0):
    - abseil/base/config
    - abseil/types/bad_any_cast_impl
  - abseil/types/bad_any_cast_impl (1.20211102.0):
    - abseil/base/config
    - abseil/base/raw_logging_internal
  - abseil/types/bad_optional_access (1.20211102.0):
    - abseil/base/config
    - abseil/base/raw_logging_internal
  - abseil/types/bad_variant_access (1.20211102.0):
    - abseil/base/config
    - abseil/base/raw_logging_internal
  - abseil/types/compare (1.20211102.0):
    - abseil/base/core_headers
    - abseil/meta/type_traits
  - abseil/types/optional (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/memory/memory
    - abseil/meta/type_traits
    - abseil/types/bad_optional_access
    - abseil/utility/utility
  - abseil/types/span (1.20211102.0):
    - abseil/algorithm/algorithm
    - abseil/base/core_headers
    - abseil/base/throw_delegate
    - abseil/meta/type_traits
  - abseil/types/variant (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/base/core_headers
    - abseil/meta/type_traits
    - abseil/types/bad_variant_access
    - abseil/utility/utility
  - abseil/utility/utility (1.20211102.0):
    - abseil/base/base_internal
    - abseil/base/config
    - abseil/meta/type_traits
  - BoringSSL-GRPC (0.0.24):
    - BoringSSL-GRPC/Implementation (= 0.0.24)
    - BoringSSL-GRPC/Interface (= 0.0.24)
  - BoringSSL-GRPC/Implementation (0.0.24):
    - BoringSSL-GRPC/Interface (= 0.0.24)
  - BoringSSL-GRPC/Interface (0.0.24)
  - cloud_firestore (4.1.0):
    - Firebase/CoreOnly (~> 10.2.0)
    - Firebase/Firestore (~> 10.2.0)
    - firebase_core
    - FlutterMacOS
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - cloud_functions (4.0.5):
    - Firebase/CoreOnly (~> 10.2.0)
    - Firebase/Functions (~> 10.2.0)
    - firebase_core
    - FlutterMacOS
  - Firebase/Auth (10.2.0):
    - Firebase/CoreOnly
    - FirebaseAuth (~> 10.2.0)
  - Firebase/CoreOnly (10.2.0):
    - FirebaseCore (= 10.2.0)
  - Firebase/Firestore (10.2.0):
    - Firebase/CoreOnly
    - FirebaseFirestore (~> 10.2.0)
  - Firebase/Functions (10.2.0):
    - Firebase/CoreOnly
    - FirebaseFunctions (~> 10.2.0)
  - firebase_auth (4.1.5):
    - Firebase/Auth (~> 10.2.0)
    - Firebase/CoreOnly (~> 10.2.0)
    - firebase_core
    - FlutterMacOS
  - firebase_core (2.3.0):
    - Firebase/CoreOnly (~> 10.2.0)
    - FlutterMacOS
  - FirebaseAppCheckInterop (10.2.0)
  - FirebaseAuth (10.2.0):
    - FirebaseCore (~> 10.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.8)
    - GoogleUtilities/Environment (~> 7.8)
    - GTMSessionFetcher/Core (< 4.0, >= 2.1)
  - FirebaseAuthInterop (10.2.0)
  - FirebaseCore (10.2.0):
    - FirebaseCoreInternal (~> 10.0)
    - GoogleUtilities/Environment (~> 7.8)
    - GoogleUtilities/Logger (~> 7.8)
  - FirebaseCoreExtension (10.2.0):
    - FirebaseCore (~> 10.0)
  - FirebaseCoreInternal (10.2.0):
    - "GoogleUtilities/NSData+zlib (~> 7.8)"
  - FirebaseFirestore (10.2.0):
    - abseil/algorithm (~> 1.20211102.0)
    - abseil/base (~> 1.20211102.0)
    - abseil/container/flat_hash_map (~> 1.20211102.0)
    - abseil/memory (~> 1.20211102.0)
    - abseil/meta (~> 1.20211102.0)
    - abseil/strings/strings (~> 1.20211102.0)
    - abseil/time (~> 1.20211102.0)
    - abseil/types (~> 1.20211102.0)
    - FirebaseCore (~> 10.0)
    - "gRPC-C++ (~> 1.44.0)"
    - leveldb-library (~> 1.22)
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - FirebaseFunctions (10.2.0):
    - FirebaseAppCheckInterop (~> 10.0)
    - FirebaseAuthInterop (~> 10.0)
    - FirebaseCore (~> 10.0)
    - FirebaseCoreExtension (~> 10.0)
    - FirebaseMessagingInterop (~> 10.0)
    - FirebaseSharedSwift (~> 10.0)
    - GTMSessionFetcher/Core (< 4.0, >= 2.1)
  - FirebaseMessagingInterop (10.2.0)
  - FirebaseSharedSwift (10.2.0)
  - FlutterMacOS (1.0.0)
  - FMDB (2.7.5):
    - FMDB/standard (= 2.7.5)
  - FMDB/standard (2.7.5)
  - GoogleUtilities/AppDelegateSwizzler (7.10.0):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
  - GoogleUtilities/Environment (7.10.0):
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/Logger (7.10.0):
    - GoogleUtilities/Environment
  - GoogleUtilities/Network (7.10.0):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.10.0)"
  - GoogleUtilities/Reachability (7.10.0):
    - GoogleUtilities/Logger
  - "gRPC-C++ (1.44.0)":
    - "gRPC-C++/Implementation (= 1.44.0)"
    - "gRPC-C++/Interface (= 1.44.0)"
  - "gRPC-C++/Implementation (1.44.0)":
    - abseil/base/base (= 1.20211102.0)
    - abseil/base/core_headers (= 1.20211102.0)
    - abseil/container/flat_hash_map (= 1.20211102.0)
    - abseil/container/inlined_vector (= 1.20211102.0)
    - abseil/functional/bind_front (= 1.20211102.0)
    - abseil/hash/hash (= 1.20211102.0)
    - abseil/memory/memory (= 1.20211102.0)
    - abseil/random/random (= 1.20211102.0)
    - abseil/status/status (= 1.20211102.0)
    - abseil/status/statusor (= 1.20211102.0)
    - abseil/strings/cord (= 1.20211102.0)
    - abseil/strings/str_format (= 1.20211102.0)
    - abseil/strings/strings (= 1.20211102.0)
    - abseil/synchronization/synchronization (= 1.20211102.0)
    - abseil/time/time (= 1.20211102.0)
    - abseil/types/optional (= 1.20211102.0)
    - abseil/types/variant (= 1.20211102.0)
    - abseil/utility/utility (= 1.20211102.0)
    - "gRPC-C++/Interface (= 1.44.0)"
    - gRPC-Core (= 1.44.0)
  - "gRPC-C++/Interface (1.44.0)"
  - gRPC-Core (1.44.0):
    - gRPC-Core/Implementation (= 1.44.0)
    - gRPC-Core/Interface (= 1.44.0)
  - gRPC-Core/Implementation (1.44.0):
    - abseil/base/base (= 1.20211102.0)
    - abseil/base/core_headers (= 1.20211102.0)
    - abseil/container/flat_hash_map (= 1.20211102.0)
    - abseil/container/inlined_vector (= 1.20211102.0)
    - abseil/functional/bind_front (= 1.20211102.0)
    - abseil/hash/hash (= 1.20211102.0)
    - abseil/memory/memory (= 1.20211102.0)
    - abseil/random/random (= 1.20211102.0)
    - abseil/status/status (= 1.20211102.0)
    - abseil/status/statusor (= 1.20211102.0)
    - abseil/strings/cord (= 1.20211102.0)
    - abseil/strings/str_format (= 1.20211102.0)
    - abseil/strings/strings (= 1.20211102.0)
    - abseil/synchronization/synchronization (= 1.20211102.0)
    - abseil/time/time (= 1.20211102.0)
    - abseil/types/optional (= 1.20211102.0)
    - abseil/types/variant (= 1.20211102.0)
    - abseil/utility/utility (= 1.20211102.0)
    - BoringSSL-GRPC (= 0.0.24)
    - gRPC-Core/Interface (= 1.44.0)
    - Libuv-gRPC (= 0.0.10)
  - gRPC-Core/Interface (1.44.0)
  - GTMSessionFetcher/Core (3.0.0)
  - leveldb-library (1.22.1)
  - Libuv-gRPC (0.0.10):
    - Libuv-gRPC/Implementation (= 0.0.10)
    - Libuv-gRPC/Interface (= 0.0.10)
  - Libuv-gRPC/Implementation (0.0.10):
    - Libuv-gRPC/Interface (= 0.0.10)
  - Libuv-gRPC/Interface (0.0.10)
  - nanopb (2.30909.0):
    - nanopb/decode (= 2.30909.0)
    - nanopb/encode (= 2.30909.0)
  - nanopb/decode (2.30909.0)
  - nanopb/encode (2.30909.0)
  - package_info_plus_macos (0.0.1):
    - FlutterMacOS
  - path_provider_macos (0.0.1):
    - FlutterMacOS
  - PromisesObjC (2.1.1)
  - Purchases (3.13.2):
    - PurchasesCoreSwift (= 3.13.2)
  - purchases_flutter (3.10.0):
    - FlutterMacOS
    - PurchasesHybridCommon (= 1.11.2)
  - PurchasesCoreSwift (3.13.2)
  - PurchasesHybridCommon (1.11.2):
    - Purchases (= 3.13.2)
  - screen_retriever (0.0.1):
    - FlutterMacOS
  - shared_preferences_macos (0.0.1):
    - FlutterMacOS
  - sqflite (0.0.2):
    - FlutterMacOS
    - FMDB (>= 2.7.5)
  - url_launcher_macos (0.0.1):
    - FlutterMacOS
  - window_manager (0.2.0):
    - FlutterMacOS

DEPENDENCIES:
  - cloud_firestore (from `Flutter/ephemeral/.symlinks/plugins/cloud_firestore/macos`)
  - cloud_functions (from `Flutter/ephemeral/.symlinks/plugins/cloud_functions/macos`)
  - firebase_auth (from `Flutter/ephemeral/.symlinks/plugins/firebase_auth/macos`)
  - firebase_core (from `Flutter/ephemeral/.symlinks/plugins/firebase_core/macos`)
  - FlutterMacOS (from `Flutter/ephemeral`)
  - package_info_plus_macos (from `Flutter/ephemeral/.symlinks/plugins/package_info_plus_macos/macos`)
  - path_provider_macos (from `Flutter/ephemeral/.symlinks/plugins/path_provider_macos/macos`)
  - purchases_flutter (from `Flutter/ephemeral/.symlinks/plugins/purchases_flutter/macos`)
  - screen_retriever (from `Flutter/ephemeral/.symlinks/plugins/screen_retriever/macos`)
  - shared_preferences_macos (from `Flutter/ephemeral/.symlinks/plugins/shared_preferences_macos/macos`)
  - sqflite (from `Flutter/ephemeral/.symlinks/plugins/sqflite/macos`)
  - url_launcher_macos (from `Flutter/ephemeral/.symlinks/plugins/url_launcher_macos/macos`)
  - window_manager (from `Flutter/ephemeral/.symlinks/plugins/window_manager/macos`)

SPEC REPOS:
  trunk:
    - abseil
    - BoringSSL-GRPC
    - Firebase
    - FirebaseAppCheckInterop
    - FirebaseAuth
    - FirebaseAuthInterop
    - FirebaseCore
    - FirebaseCoreExtension
    - FirebaseCoreInternal
    - FirebaseFirestore
    - FirebaseFunctions
    - FirebaseMessagingInterop
    - FirebaseSharedSwift
    - FMDB
    - GoogleUtilities
    - "gRPC-C++"
    - gRPC-Core
    - GTMSessionFetcher
    - leveldb-library
    - Libuv-gRPC
    - nanopb
    - PromisesObjC
    - Purchases
    - PurchasesCoreSwift
    - PurchasesHybridCommon

EXTERNAL SOURCES:
  cloud_firestore:
    :path: Flutter/ephemeral/.symlinks/plugins/cloud_firestore/macos
  cloud_functions:
    :path: Flutter/ephemeral/.symlinks/plugins/cloud_functions/macos
  firebase_auth:
    :path: Flutter/ephemeral/.symlinks/plugins/firebase_auth/macos
  firebase_core:
    :path: Flutter/ephemeral/.symlinks/plugins/firebase_core/macos
  FlutterMacOS:
    :path: Flutter/ephemeral
  package_info_plus_macos:
    :path: Flutter/ephemeral/.symlinks/plugins/package_info_plus_macos/macos
  path_provider_macos:
    :path: Flutter/ephemeral/.symlinks/plugins/path_provider_macos/macos
  purchases_flutter:
    :path: Flutter/ephemeral/.symlinks/plugins/purchases_flutter/macos
  screen_retriever:
    :path: Flutter/ephemeral/.symlinks/plugins/screen_retriever/macos
  shared_preferences_macos:
    :path: Flutter/ephemeral/.symlinks/plugins/shared_preferences_macos/macos
  sqflite:
    :path: Flutter/ephemeral/.symlinks/plugins/sqflite/macos
  url_launcher_macos:
    :path: Flutter/ephemeral/.symlinks/plugins/url_launcher_macos/macos
  window_manager:
    :path: Flutter/ephemeral/.symlinks/plugins/window_manager/macos

SPEC CHECKSUMS:
  abseil: ebe5b5529fb05d93a8bdb7951607be08b7fa71bc
  BoringSSL-GRPC: 3175b25143e648463a56daeaaa499c6cb86dad33
  cloud_firestore: 5bfd8f92a2f11f9d25a0ee69303ca069cadc7637
  cloud_functions: b74c3e431668d5a99088638954bb202d6b1b0686
  Firebase: a3ea7eba4382afd83808376edb99acdaff078dcf
  firebase_auth: 89ed93a8d1d8f657fec8fe149bdeeb02e55c92d4
  firebase_core: f6f75d92dcdd5ef1b43876017affde02b7b402ec
  FirebaseAppCheckInterop: af164d9c623f82174e3ffa54394dee189587c601
  FirebaseAuth: 08e7739244eeae5216d0a3f8d9f16a76be9c252e
  FirebaseAuthInterop: 027d42ca8fec84dc6151566479af05095a0bd5c0
  FirebaseCore: 813838072b797b64f529f3c2ee35e696e5641dd1
  FirebaseCoreExtension: d08b424832917cf13612021574399afbbedffeef
  FirebaseCoreInternal: 091bde13e47bb1c5e9fe397634f3593dc390430f
  FirebaseFirestore: bda7a1ca8c19319a2acd2761cd4b962022c1d5ea
  FirebaseFunctions: eaa208f64f2f179f0ab9b775fecdec07fdd74d90
  FirebaseMessagingInterop: b46e7fcf39c0e9b16841e258645a320a154af240
  FirebaseSharedSwift: a160b39d4ce77be922b3d6ff009099c7294e36e5
  FlutterMacOS: 57701585bf7de1b3fc2bb61f6378d73bbdea8424
  FMDB: 2ce00b547f966261cd18927a3ddb07cb6f3db82a
  GoogleUtilities: bad72cb363809015b1f7f19beb1f1cd23c589f95
  "gRPC-C++": 9675f953ace2b3de7c506039d77be1f2e77a8db2
  gRPC-Core: 943e491cb0d45598b0b0eb9e910c88080369290b
  GTMSessionFetcher: c1edebe64e9fb4e8f6415d018edf1fd3eac074a1
  leveldb-library: 50c7b45cbd7bf543c81a468fe557a16ae3db8729
  Libuv-gRPC: 55e51798e14ef436ad9bc45d12d43b77b49df378
  nanopb: b552cce312b6c8484180ef47159bc0f65a1f0431
  package_info_plus_macos: f010621b07802a241d96d01876d6705f15e77c1c
  path_provider_macos: 3c0c3b4b0d4a76d2bf989a913c2de869c5641a19
  PromisesObjC: ab77feca74fa2823e7af4249b8326368e61014cb
  Purchases: 03200de9288724e77de435000d1828601e6b8e00
  purchases_flutter: ec56bb806ae9076a2edced385860f1fea4b30639
  PurchasesCoreSwift: 2ea4b33e5cece5c8a0751594ef7c6cbfcbd747a9
  PurchasesHybridCommon: 56ef42d85c3e930d49aff4ac5fa027373d2e1bb8
  screen_retriever: 59634572a57080243dd1bf715e55b6c54f241a38
  shared_preferences_macos: a64dc611287ed6cbe28fd1297898db1336975727
  sqflite: a5789cceda41d54d23f31d6de539d65bb14100ea
  url_launcher_macos: 597e05b8e514239626bcf4a850fcf9ef5c856ec3
  window_manager: 3a1844359a6295ab1e47659b1a777e36773cd6e8

PODFILE CHECKSUM: a884f6dd3f7494f3892ee6c81feea3a3abbf9153

COCOAPODS: 1.11.3

@ncooke3 no rush. But just curious if you are able to reproduce? Or if you have an ETA on when you can get to this?

Hi @notandyvee, so if you build and run the app in release mode, does the issue also reproduce?

Also, what is your macOS version?

Hi @notandyvee, so if you build and run the app in release mode, does the issue also reproduce?

Just tried it. Interestingly it does not happen when running it in release mode with the firebase auth keychain created in the development mode.

Also, what is your macOS version?

MacOS 12.6

Hmm interesting... Question, is your project configured in such a way that you can edit the source code in Firebase Auth? Specifically, FirebaseAuth/Sources/Storage/FIRAuthKeychainServices.m?

 I don't really fully understand the setup. Left it mostly as the flutter default. But I can see the file you are talking about. Just not in the same path as what you posted. So not sure if I can edit it. Do you have a specific root folder I can search in to look?

No worries–– and that looks right. It should let you edit it (you might have to "unlock" it in a dialog box that pops up when you try to do so). If it does, locate the genericPasswordQueryWithKey method on line 228.
Replace it with the following:
- (NSDictionary *)genericPasswordQueryWithKey:(NSString *)key {
  NSMutableDictionary *query = @{
    (__bridge id)kSecClass : (__bridge id)kSecClassGenericPassword,
    (__bridge id)kSecAttrAccount : [kAccountPrefix stringByAppendingString:key],
    (__bridge id)kSecAttrService : _service,
  }.mutableCopy;

  if (@available(iOS 13.0, macOS 10.15, macCatalyst 13.0, tvOS 13.0, watchOS 6.0, *)) {
    query[(__bridge id)kSecUseDataProtectionKeychain] = (__bridge id)kCFBooleanTrue;
  }

  return [query copy];
}

And then try reproducing the issue again.

Sorry for the delay @ncooke3 . Pushed a new testflight build. The pop up is gone, but because now the existing keychain wasn't recognized. I verified that firebase_auth keychain exists. But had to re-login. When logging in the resulting keychain looks like this.

Sorry, what exactly do you mean by "but because now the existing keychain wasn't recognized."? I'm trying to determine if this helped or not. Did successive calls to the new keychain yield a pop up?

Edit: How do I undo the change when doing things like this? After xcode is closed and re-open I mean.

You can copy and paste the implementation here: https://github.com/firebase/firebase-ios-sdk/blob/c24031ad9410c746c49deddc739fdf311a386fc7/FirebaseAuth/Sources/Storage/FIRAuthKeychainServices.m#L228-L234. This is the corresponding implementation for Firebase Auth 10.2.0, which your Podfile.lock shows is being used.

Damn. Apologies for the wasted cycles here. It was not clear what was happening. So to be clear, the change you made should stop using the old keychain row, which will be of type "login" and my app should now be using the "iCloud" keychain? In essence a re-auth is expected? When I noticed that I stopped testing thinking it was not expected since it "appeared" wrong.
Assuming my assumption above is correct, I tested a few scenarios with your test change on genericPasswordQueryWithKey:

Pushed a testflight build and logged in. This created the new keychain.
Run app in development. No pop up.
Increment build to push for testflight. Updated and no pop up.

Did successive calls to the new keychain yield a pop up?

Your method change did not yield pop ups when using builds in development and testflight. When updating a testflight build no popups occur either. It's like they are now sharing the same keychain properly. This is great news. Thank you.
Now whats the next steps here for this fix? Is it safe to use this code temporarily to avoid the popups? Or should I wait for a proper prod fix?
Again, extremely appreciative in such quick turn around here 🙏🏻 .

No worries– macOS keychain debugging is pretty confusing!

So to be clear, the change you made should stop using the old keychain row, which will be of type "login" and my app should now be using the "iCloud" keychain? In essence a re-auth is expected?

Yes, the new flag will use the data protection keychain rather than the traditional file based keychain. This is the only way that I know of to make the macOS keychain behave like the iOS one. Apple released a good tech note on this recently that helped fill in the gaps of my keychain knowledge so check it out if you're interested. There are two inevitable drawbacks worth calling out with the updated implementation:

macOS devices running under 10.15 will still see the pop-ups (might not be an issue if your targeting >= 10.15)

as you saw, updating the implementation meant using a new keychain for storing Auth credentials. You mentioned:

In essence a re-auth is expected?

Were you logged out the first launch after the update? I'll have to double check with the Auth team as I'm not 100% sure the effect of switching keychains but I would expect there to be a one-time cost where users would have to re-auth so the credentials can be safely stored in the new, pop-up free keychain.

I'll check with the Auth team after the holidays and move to getting this out in a release!
In the meantime, I think it's safe to use this local edit to unblock yourself–– all of Firebase's other keychain usage now use this new attribute (I must have missed this particular API surface). I would just do some extra manual testing with the test flight builds to ensure auth is functioning as expected after updating (apart from the need to re-auth). Let me know if you notice any interesting behavior!

Apple released a good tech note on this recently that helped fill in the gaps of my keychain knowledge so check it out if you're interested.

Thanks for the link. Does actually help in understanding why this was a problem.

Were you logged out the first launch after the update?

That's a great question. The setup I have should automatically respond to auth changes. I don't log users out automatically, so it would have to be in response to the auth SDK callback. Definitely confirm with the auth team. I can take the one time hit as I'm waiting to release so it doesn't bother me at the moment.

In the meantime, I think it's safe to use this local edit to unblock yourself

Question about that. So I'm cool doing that. What happens when I update the firebase libs before this fix is included? Would those files be deleted and a fresh copy from the release be used? Meaning, would I need to manually edit genericPasswordQueryWithKey every update until a fix is included? Or would the local change persist updates?
Coming from the Android world, editing libraries like that is magical haha. Have no idea what to expect.

What happens when I update the firebase libs before this fix is included? Would those files be deleted and a fresh copy from the release be used? Meaning, would I need to manually edit genericPasswordQueryWithKey every update until a fix is included?

Yep– if you update the Firebase libs before the fix is scheduled, those files will be deleted and a fresh copy from the release will be cached for your app's xcworkspace. So, you're correct that you will have to manually edit genericPasswordQueryWithKey every update.

Or would the local change persist updates?
For reasoning above, no – the local change would not persist.

We've been seeing this issue in a TestFlight downloaded Flutter iOS app to an M1 MacOS.
Can see in Podfile.lock that we're on 10.3.0.
The error exposed is:
An error occurred when accessing the keychain. The NSLocalizedFailureReasonErrorKey field in the NSError.userInfo dictionary will contain more information about the error encountered.
Just wanted to give a heads up.

This thread solved it for us: https://github.com/google/GoogleSignIn-iOS/issues/165
Specifically, adding a capability of "Keychain Sharing", and then a key with com.google.GIDSignIn.

@larssn the issue you are referencing seems similar but unrelated at first glance. I had also turned on keychain sharing but my issue is not a google sign in issue. Does this mean if I use google sign in I need to add the keychain sharing capability with com.google.GIDSignIn?

Tbh I haven't looked into in detail. We're two people who need TestFlight access on iOS to our app, and all I concluded was that the above fixed it.
You might be right that it's an entirely different issue.

Hi @notandyvee, checking in to see if the original solution is working as expected?

Sorry for the late response @ncooke3 .

Hi @notandyvee, checking in to see if the original solution is working as expected?

Yes. Your solution fixed the issue I was having when updating the method as you instructed.

Hi @notandyvee, apologies for the delay. I have since staged this fix in the next release, which should release sometime during the week of February 7th.
Thanks for reporting the issue and don't hesitate to reach out on this thread if you run into anymore trouble!


[Bug] Sum has default parseInt()

Why do you use parseInt() inside Array.sum() if no callback is provided? To use it with doubles it is required now to do .sum(v => v). Also everything that uses .sum (like .average) also needs explicit (v => v).

This is really unexpected behaviour. And even if you know about it, it spoils the joy of using the lib.

@s-soltys Could you merge the PR, #2 ?

Merged PR #2 and republished the package. Thank you for contributing!


Remove --ci flag from install_ptvsd.py

For #7698

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: lightme16 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #7814 into master will decrease coverage by 0.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7814      +/-   ##
==========================================
- Coverage   59.16%   58.41%   -0.75%
==========================================
  Files         498      498
  Lines       22254    21893     -361
  Branches     3578     3573       -5
==========================================
- Hits        13166    12789     -377
- Misses       8264     8271       +7
- Partials      824      833       +9

Impacted Files
Coverage Δ

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-50%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:

src/client/language/characters.ts
12% <0%> (-21.34%)
:arrow_down:

src/client/testing/codeLenses/main.ts
60% <0%> (-17.78%)
:arrow_down:

src/client/datascience/cellFactory.ts
72.34% <0%> (-17.32%)
:arrow_down:

src/client/common/platform/pathUtils.ts
66.66% <0%> (-5.56%)
:arrow_down:

src/client/linters/pydocstyle.ts
84.61% <0%> (-5.13%)
:arrow_down:

... and 33 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1536d8b...a58b979. Read the comment docs.

I can see that one test is failed due to

The agent: Azure Pipelines 21 lost communication with the server. Verify the machine is running and has a healthy network connection. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

Looks unrelated to this PR, it seems we need to restart the tests


Error when router.on() (Client-side routing)

using: director-1.0.7.min.js
In chrome v16:
var router = new Router().init();
router.on('/:some', function () {...}); //=> TypeError: Cannot call method 'concat' of undefined

In FF v9
var router = new Router().init();
router.on('/:some', function () {...}); //=> TypeError: this.scope is undefined

In IE v9 does not work.

I have this same issue on the client. Is there any other way to do scoped routing on the client to avoid this error.

Yes.
use
router.mount();

var router = new Router();

 router.mount({
           '/': function () {

            }
  });


Outer constructor

A small fix on the constructor, apologies @charlesknipp for the confusion on the alias

No problem. Tim fixed it on the GPU branch as well. Not sure why I decided on an inner constructor.

Implemented in #4


Tactical Medical Pouch

https://cm-ss13.com/wiki/Marine_Equipment#Tactical_Medical_Pouch

I'm assuming this is just called "medical pouch" internally, so
https://github.com/CM-14/CM-14/pull/762

It was not.

It was not.

it was, #762 it has id CMPouchMedicalSoc

#762
in Resources/Prototypes/_CM14/Entities/Objects/Clothing/pouches.yml on line 353 with id CMPouchMedicalSoc


Implement testcases for Progress Command

[x] ProgressCommandParserTest
[ ] ProgressCommandTest

Codecov Report

Merging #194 (ddcbb31) into master (284ed12) will increase coverage by 0.90%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #194      +/-   ##
============================================
+ Coverage     55.45%   56.36%   +0.90%
- Complexity      571      580       +9
============================================
  Files           105      105
  Lines          2420     2420
  Branches        318      318
============================================
+ Hits           1342     1364      +22
+ Misses          968      942      -26
- Partials        110      114       +4

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
97.29% <0.00%> (+13.51%)
:arrow_up:

.../seedu/address/logic/commands/ProgressCommand.java
24.13% <0.00%> (+24.13%)
:arrow_up:

...du/address/logic/parser/ProgressCommandParser.java
90.90% <0.00%> (+90.90%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 284ed12...ddcbb31. Read the comment docs.

Closing this PR cos idk why its failing on macos


Fix readme colors in example

The colors in the readme aren't showing up on GitHub

Not possible atm - https://github.com/github/markup/issues/1440
Use gif for example instead


Fix to allow plugin to correctly capture performance navigation event…

Modified NavigationPlugin to capture PerformanceNavigationEvents when the plugin loads after the page does.

Removed PerformanceObserver from eventListener.
Added two new unit test cases and modified existing one case with respect to the new implementation change.
Created a new app called delayed_page.html that loads the script after the page finishes loading.
Created a new integ test case using the delayed_page app to verify that PerformanceNavigationEvents are captured.

To test the change, do the following:

Create a temporary app (delayed_page.html) in your local repository without any other implementation changes
Run server and either use Chrome debugger or open up local host, compare the output between index.html and delayed_page.html.
index.html should have the navigation events, while the delayed_page.html does not.
This indicates that with the original implementation, delayed_page properly simulates a web page loading prior to plugin
Once this is verified, pull in the NavigationPlugin changes, and rerun the server/debugger to see that now PerformanceNavigationEvents are captured in the delayed_page app.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.


Trying to ping the build

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 32.81%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
251

Relevant Lines:
765

💛  - Coveralls


Bump golang and further dependency versions

Bumps building golang 1.17 -> 1.20
Bumps commons-lang and guava
Adds back dependabot

Thanks @zabil and @haroon-sheikh 👋


Process persistence?

I am running an interactive console application, whose process needs to run for a long time. But when I close the browser window, the process is killed by ttyd too. In other words, I want to share my console with other team members. Would you consider this enhancement?

Nope, you can use terminal multiplexers like tmux as a workaround which is documented in README.


Apache error after uploading my previous Wordpress and DB folders, w/o using Apache

Description
I was working for months with Docker version 1.11.2, build b9f10c9 and Docker Compose version 1.8.0-rc1, build 9bf6bc6, everything was working fine. You will find below my docker-compose.yml, which was working without any problems.
I decided to change my server provider. First I had a lot of problems with Ubuntu 16.04 so I decided to build my new server with 14.04 like my previous one.
My DataBase folder and my Wordpress folder are copied in a directory (read conf file). I used to download them in ftp and then upload them on other servers running the same configuration, I was able to move my website super quickly.
I have installed the latest versions of Docker and Docker Compose.
My Problem :
After uploading my folders, the website isn't working and I'm getting an Apache error, whereas... I'm not using Apache ? And, Apache Debian Server ? I'm on Ubuntu ?  : )
"You don't have permission to access / on this server.
Apache/2.4.10 (Debian) Server at mywebsite.com Port 80"
Steps to reproduce the issue:

Install Ubuntu 14.04, update, upgrade
Install Docker & Compose
Build containers with my compose .yml file (see below)
Wordpress installation is displayed on the website - Working
Upload my database folder and wordpress folder via ftp (well, can't really give you this :( )
Website not working anymore, Apache error.

docker-compose.yml :
version: '2'

services:
  https-portal:
    image: steveltn/https-portal
    restart: always
    ports:
      - 80:80
      - 443:443
    links:
      - giwordpress
    environment:
      DOMAINS: "mywebsite.com -> http://giwordpress"
      STAGE: 'production'
      FORCE_RENEW: 'true'

  gidb:
    image: mysql:5.7
    volumes:
      - "./.data/gidb:/var/lib/mysql"
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: password
      MYSQL_DATABASE: giwpdb

  giwordpress:
    depends_on:
      - gidb
    image: wordpress:latest
    links:
      - gidb
    working_dir: "/var/www/html/"
    volumes:
      - "./.data/wordpress:/var/www/html/"
    restart: always
    environment:
      WORDPRESS_DB_HOST: gidb:3306
      WORDPRESS_DB_PASSWORD: password

Describe the results you received:
Forbidden
You don't have permission to access / on this server.
Apache/2.4.10 (Debian) Server at gamers-industry.com Port 80
Output of docker version:
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 3
 Running: 2
 Paused: 0
 Stopped: 1
Images: 3
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 44
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null bridge host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-45-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.822 GiB
Name: GamersIndustry
ID: GCOK:3GO4:YCW7:NOOY:N6LK:3HHD:IPZ6:A6HO:BWTR:OWHZ:L4OL:3TV2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):

It's not the error I got but I had an issue with Ubuntu having apache running by default and preventing some conatiners to bind to port 80. Can you try running sudo service apache2 stop?

Hi Laurent, yes I forgot to mention that I looked if apache2 was installed, it isn't :/. Still,  I tried it stop stop it. "Unrecognized service" . So, it's not Apache... .
I just contacted my server provider, since I'm not using Debian or Apache and having those errors, but they don't see what could be the problem.
I'm going to reinstall everything and to set a chmod 777 on all my folders just to try..

@ScottBu I'm going to close this issue, because this does not look like a bug in docker, feel free to continue the conversation, or open a topic on https://forums.docker.com, which may be more suitable for this kind of questions


[DS-2220] Always use SSL to fetch Google Analytics

We benefit from fetching ga.js over SSL regardless of whether the current page is using SSL itself.

For the record, @peterdietz and @bram-atmire, see the recent man-on-the-side attack against GitHub which hijacked plaintext requests for Baidu analytics and replaced them with malicious code, creating a massive DDoS against GitHub:
http://www.netresec.com/?page=Blog&month=2015-03&post=China's-Man-on-the-Side-Attack-on-GitHub
HTTPS always better! Of course, the CAs will be the next nail in the current TLS ecosystem's coffin. Just sayin'. ;)


ZMNHUD Temperature issue

Hi all,
I use your fantastic ZwaveJS2MQQT with my Home Assistant instance.
i m a French user and I use a Qubino ZMNHUD for my climate.
With this ZMNHUD, I have a Wired Temperature Sensor and it s work with ZwaveJS2MQTT but it s not the good temperature value remote to Home Assistant (Two température value in config panel but  it s not the correct send to HA :()
edit more detail :

24-49-3-Air temperature] Air temperature -> Value send to HA
24-49-1-Air temperature] Air temperature -> Correct value needed :)

Can you help me ?
thank a lot :)

@Balooforever I think your climate has multiple endpoints, by default when I auto discover climates I use the first endpoint (0 or 1). You can try to manually edit the discovery template to fix this

Hum, i agree with you.
The debug info for this 2 values :
{
"id": "24-49-3-Air temperature",
"nodeId": 24,
"commandClass": 49,
"commandClassName": "Multilevel Sensor",
"endpoint": 3,
"property": "Air temperature",
"propertyName": "Air temperature",
"type": "number",
"readable": true,
"writeable": false,
"label": "Air temperature",
"stateless": false,
"ccSpecific": {
"sensorType": 1,
"scale": 0
},
"unit": "°C",
"list": false,
"value": 20.5,
"lastUpdate":<PHONE_NUMBER>469,
"newValue": 20.5
},
{
"id": "24-49-1-Air temperature",
"nodeId": 24,
"commandClass": 49,
"commandClassName": "Multilevel Sensor",
"endpoint": 1,
"property": "Air temperature",
"propertyName": "Air temperature",
"type": "number",
"readable": true,
"writeable": false,
"label": "Air temperature",
"stateless": false,
"ccSpecific": {
"sensorType": 1,
"scale": 0
},
"unit": "°C",
"list": false,
"value": 21.1,
"lastUpdate":<PHONE_NUMBER>559,
"newValue": 21.1
},
The endpoint "3" is used, not the endpoint "1".
How i can edit and fix the discovery template ?
It's really a nice work, thank again :)

Go to control panel, expand the node that controls the climate, go to home hasssistant tab of the expanded node, in the table of the discovered hass devices select the climate and then on the right you will be able to edit the discover template. IN poor words you need to only change the number of the endpoint in all the Air Temperature values you find there. If you want paste it here so I can showe you

Sorry, but in "Control panel", i expand the node but no "home assistant tab", i have : "Node" / "Group" / "Debug Info"
I use ZwaveJS2mqtt without mqtt broker, only has control panel.

Oooh ok so you are using the zwavejs server with zweavejs hass integration right? If so I need to move the issue there


CVSS 4.0: compute score (T and E)

For CVSS 4.0, only the overall score is provided - the threatScore and the environmentalScore that the JSON schema lists, are not presented.

Thank you for your input; I must admit that during research and implementation, I have not seen a "threat" or "environmental" score being defined anywhere in the CVSS 4.0 specification or the official implementation, which both only define and provide the base score.
The same goes for this go implementation that only returns one base score.
This also does not conform with my understanding of the "CVSS-BTE" nomenclature, where only one score is calculated and interpreted in a different way depending on the metrics used to calculate it.

The only way these scores would make sense to me right now would be to leave away the threat metrics on the environmental score and the other way around, leave away the environmental metrics on the threat score.
But I wouldn't find that too useful, so I'm not sure what the actual way of calculating these are.
Or do they represent an intermediate result on the way to calculating the base score?

If you would be as kind as to point me in the right direction for this? I would be very interested, as I've been looking for a way to calculate these myself, but was unable to find anything.

If you would be as kind as to point me in the right direction for this? I would be very interested, as I've been looking for a way to calculate these myself, but was unable to find anything.

I'm not sure whether I'm able to do that. According to the JSON schema, those values exist... Maybe, you could reach out to the CVSS SIG to ask them about this?

All right, I will be doing that next week. Thank you also for your other issues, we will be addressing them as soon as possible.


Add cross-compilation for arm

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] 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)
[X] Ensured the license file is being packaged.

Add cross-compilation for arm.

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.

@conda-forge-admin, please rerender

@patricksnape This is ready for review/merge.


FP16 datatype support for chromium DML prototype

We plan to support FP16 datatype especially for VPU acceleration on DML. After investigation, I found the https://learn.microsoft.com/en-us/windows/win32/dxcore/dxcore-source-code gives an example using dxcore  to enumerate the devices (including GPUs and VPU), and it works. All of the available devices will be in the list:
 // From the factory, retrieve a list of all the Direct3D 12 Core Compute adapters.     winrt::com_ptr<IDXCoreAdapterList> d3D12CoreComputeAdapters;
But how to select the correct device VPU from the list is not clear. Do you know any flags/preferrence/properties that can indicate which device is VPU?
Any suggestions? Thanks a lot! @fdwr

Sorry to bother you too early, please ignore this question temporarily, I will try FP16 on GPU firstly. @fdwr . We can discuss for VPU in WebNN-DirectML Teams Channel in the future.


fixes: #596 Design readme

fixes #596
Please provide enough information so that others can review your pull request:
Added links and contact information to design readme
Explain the details for making this change. What existing problem does the pull request solve?
More guiding information to readme
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.

Final Checklist

[x] Have you bumped the version in package.json?

Second decimal for major change, third decimal for minor change. This can go past 10 i.e. 1.0.9 !=> 1.1.0, 1.0.9 => 1.0.10
Read here for more info

[x] Have you added any new tests necessary?
[x] Is your PR rebased off the most current master?
[x] Have you squashed all commits, or if you will merge will you squash all commits?
[x] Did you use yarn, not npm?
[x] Did you use Material-UI wherever possible?
[x] Did you format according to Prettier?
[x] Did you run all of your most recent changes locally to make sure everything is working?

LGTM. AWESOME STUFF @crispinamuriel ! GREAT PR!

Looks good.. I would suggest trimming the contact info quite a bit and just include design-related people.


"Directory not empty" error after upgrading 0.41 → 0.42:

After upgrading overcommit from 0.41.0 to 0.42.0, the first time I attempt to use git commit on an overcommit-enabled project I get this crash:
$ git commit
Directory not empty @ dir_s_rmdir - /Users/mbrictson/Code/myapp/.git/hooks/old-hooks
/Users/mbrictson/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `rmdir'
/Users/mbrictson/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `block in rmdir'
/Users/mbrictson/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `each'
/Users/mbrictson/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `rmdir'
/Users/mbrictson/Code/overcommit/lib/overcommit/installer.rb:142:in `preserve_old_hooks'
/Users/mbrictson/Code/overcommit/lib/overcommit/installer.rb:58:in `update'
/Users/mbrictson/Code/overcommit/lib/overcommit/installer.rb:20:in `run'
.git/hooks/pre-commit:67:in `<main>'
Report this bug at https://github.com/brigade/overcommit/issues

Digging in a bit further, I found that 3c37254 in 0.42.0 made a trivial change to the git hooks. Thus, the first time overcommit 0.42 is used on a existing overcommit-enabled project, it will attempt to upgrade to the new version of the git hooks.
It backs up any existing hooks to old_hooks_path, and then reaches this line:
# Remove old-hooks directory if empty
FileUtils.rmdir(old_hooks_path)

For me, this fails with a "Directory not empty" error. Seems like there should be a guard clause here that skips the rmdir if the directory is not empty?
https://github.com/brigade/overcommit/blob/838a571852ac43e782dba58264f542c9a8a9d913/lib/overcommit/installer.rb#L129-L143

Hey @mattbrictson, thanks for discovering this. This is really weird, as our tests should have picked this up.
Running the tests on my local Mac, I found that they did indeed fail. This tells me that there is some sort of platform difference between TravisCI and macOS which I don't have bandwidth to dig into right now. What's more frustrating is that there's not an easy way to tell when the breakage started (this code is pretty old, which suggests to me this issue started happening recently).
Thanks again for the report!

The fix in https://github.com/brigade/overcommit/commit/7c85c6651b7249cecf92f2cfa848bbd16a488f03 doesn't seem to work for me. I'm on macOS 10.12.6 with Ruby 2.5.0. I updated my Gemfile to point to the master branch of overcommit, and when I run overcommit --install, it still fails. It looks like it's trying to move the hooks into my home folder, not the current project's directory:
Installing hooks into /Users/monfresh/projects/my_app
Hook '/Users/monfresh/projects/my_app/pre-commit' already exists and was not installed by Overcommit. Moving to '/Users/monfresh/.git-support/hooks/old-hooks'
Traceback (most recent call last):
  13: from /Users/monfresh/.gem/ruby/2.5.0/bin/overcommit:23:in `<main>'
  12: from /Users/monfresh/.gem/ruby/2.5.0/bin/overcommit:23:in `load'
  11: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/bin/overcommit:49:in `<top (required)>'
  10: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/cli.rb:24:in `run'
   9: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/cli.rb:125:in `install_or_uninstall'
   8: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/cli.rb:125:in `each'
   7: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/cli.rb:127:in `block in install_or_uninstall'
   6: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/installer.rb:22:in `run'
   5: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/installer.rb:34:in `install'
   4: from /Users/monfresh/.gem/ruby/2.5.0/gems/overcommit-0.42.0/lib/overcommit/installer.rb:142:in `preserve_old_hooks'
   3: from /Users/monfresh/.rubies/ruby-2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `rmdir'
   2: from /Users/monfresh/.rubies/ruby-2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `each'
   1: from /Users/monfresh/.rubies/ruby-2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `block in rmdir'
/Users/monfresh/.rubies/ruby-2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `rmdir': Directory not empty @ dir_s_rmdir - /Users/monfresh/.git-support/hooks/old-hooks (Errno::ENOTEMPTY)
command failed (pid 36350 exit 1): overcommit --install

I figured it out. I had to run bundle exec overcommit --install. For some reason, it was not using the correct version of the gem without the bundle exec.

Thanks for following up, @monfresh. The behavior your observed seems surprising, as Overcommit should automatically respect the Bundler context defined by the gemfile option in your .overcommit.yml: https://github.com/brigade/overcommit/blob/master/bin/overcommit#L5-L31


Create Tuple archives

See #36
The 0.1-tuple files were downloaded using
curl -O -L https://github.com/carbynestack/base-images/raw/3595c5427915b2f9e1f22804e3f742cda9e72312/fake-crypto-material.zip

The 0.2-Tuple files were manually generated used the steps outlined in the README.md
Still a draft since I haven't tested uploading and running a calculation with the Tuples yet (though when creating it showed the proper MAC values so I assume they work ^^')
Signed-off-by: Timo Klenk<EMAIL_ADDRESS>

So, the Deployment works fine with the new Tuples:
Differences from Stack Deployment:

Used kindest/node:v1.21.1 instead of kindest/node:v1.18.19
Latter did not boot up on my workspace..?

Used newly built CLI instead of the one from the deployment
cp target/cli-0.2-SNAPSHOT-jar-with-dependencies.jar ${DEPLOY_FOLDER}/cs.jar

Used Newly built Crypto-Material instead of the one from the deployment
curl -O -L https://github.com/carbynestack/carbynestack/raw/e4946ba3cfdab9507805c4c69d2c5caa7983ba08/tuples/fake-crypto-material-0.2.zip
unzip -d crypto-material fake-crypto-material-0.2.zip
rm fake-crypto-material-0.2.zip

Updated Upload-Tuples Script to new Location
-> change to TUPLE_FOLDER=${SCRIPT_PATH}/crypto-material/2-p-128 instead of 2-128-40 as we only upload the GFP Triples
-> Result:
cat << 'EOF' > upload-tuples.sh
#!/bin/bash
SCRIPT_PATH="$( cd "$(dirname "$0")" ; pwd -P )"
TUPLE_FOLDER=${SCRIPT_PATH}/crypto-material/2-p-128
CLI_PATH=${SCRIPT_PATH}
NUMBER_OF_CHUNKS=1

function uploadTuples {
   echo ${NUMBER_OF_CHUNKS}
   for type in INPUT_MASK_GFP MULTIPLICATION_TRIPLE_GFP; do
      for (( i=0; i<${NUMBER_OF_CHUNKS}; i++ )); do
         local chunkId=$(uuidgen)
         echo "Uploading ${type} to http://${APOLLO_FQDN}/castor (Apollo)"
         java -jar ${CLI_PATH}/cs.jar castor upload-tuple -f ${TUPLE_FOLDER}/Triples-p-P0 -t ${type} -i ${chunkId} 1
         local statusMaster=$?
         echo "Uploading ${type} to http://${STARBUCK_FQDN}/castor (Starbuck)"
         java -jar ${CLI_PATH}/cs.jar castor upload-tuple -f ${TUPLE_FOLDER}/Triples-p-P1 -t ${type} -i ${chunkId} 2
         local statusSlave=$?
         if [[ "${statusMaster}" -eq 0 && "${statusSlave}" -eq 0 ]]; then
            java -jar ${CLI_PATH}/cs.jar castor activate-chunk -i ${chunkId} 1
            java -jar ${CLI_PATH}/cs.jar castor activate-chunk -i ${chunkId} 2
         else
            echo "ERROR: Failed to upload one tuple chunk - not activated"
         fi
      done
   done
}

uploadTuples
EOF
chmod 755 upload-tuples.sh
./upload-tuples.sh

Result Telemetry:
java -jar cs.jar castor get-telemetry 1
Initializing ExecutorService
bit_gfp
        available:      0
        consumption/s:  0

bit_gf2n
        available:      0
        consumption/s:  0

inputmask_gfp
        available:      30000
        consumption/s:  0

inputmask_gf2n
        available:      0
        consumption/s:  0

inversetuple_gfp
        available:      0
        consumption/s:  0

inversetuple_gf2n
        available:      0
        consumption/s:  0

squaretuple_gfp
        available:      0
        consumption/s:  0

squaretuple_gf2n
        available:      0
        consumption/s:  0

multiplicationtriple_gfp
        available:      10000
        consumption/s:  0

multiplicationtriple_gf2n
        available:      0
        consumption/s:  0

interval: 60000

Millionaires Problem - Ran fine.
Log:
$ # Create a secret representing Jeff's net worth (note that we work with
# billion USD here)
export JEFFS_NET_WORTH_ID=$(java -jar cs.jar amphora create-secret 177 -t billionaire=Jeff)

# And another one for Elon
export ELONS_NET_WORTH_ID=$(java -jar cs.jar amphora create-secret 151 -t billionaire=Elon)

$ cat << 'EOF' > billionaires.mpc
# Prologue to read in the inputs
port=regint(10000)
listen(port)
socket_id = regint()
acceptclientconnection(socket_id, port)
v = sint.read_from_socket(socket_id, 2)

# The logic
first_billionaires_net_worth = v[0]
second_billionaires_net_worth= v[1]
result = first_billionaires_net_worth < second_billionaires_net_worth

# Epilogue to return the outputs
resp = Array(1, sint)
resp[0] = result
sint.write_to_socket(socket_id, resp)
EOF

$ export RESULT_ID=$(cat billionaires.mpc | java -jar cs.jar ephemeral execute \
  -i $JEFFS_NET_WORTH_ID \
  -i $ELONS_NET_WORTH_ID \
  ephemeral-generic.default \
  | tail -n +2 \
  | sed 's/[][]//g')

$ java -jar cs.jar amphora get-secret $RESULT_ID
[0]
        gameID -> 62e6cd56-e489-4341-8854-9cc70d5a379c
        creation-date -><PHONE_NUMBER>888

$ java -jar cs.jar amphora delete-secrets $ELONS_NET_WORTH_ID
export ELONS_NET_WORTH_ID=$(java -jar cs.jar amphora create-secret 179 -t billionaire=Elon)
export RESULT_ID=$(cat billionaires.mpc | java -jar cs.jar ephemeral execute \
  -i $JEFFS_NET_WORTH_ID \
  -i $ELONS_NET_WORTH_ID \
  ephemeral-generic.default \
  | tail -n +2 \
  | sed 's/[][]//g')
java -jar cs.jar amphora get-secret $RESULT_ID
Success - Deleted secret with id 722e1a82-07fc-43d3-8649-7084a135933a
All Secrets deleted
[1]
        gameID -> 06496553-3724-45e8-8c11-3f4700234e3a
        creation-date -><PHONE_NUMBER>073

Should be Ready for Review now.
Can we ignore the Codacy [list-item-indent] Incorrect list-item indent: add 2 spaces again?

Can we ignore the Codacy [list-item-indent] Incorrect list-item indent: add 2 spaces again?

Yes that can be ignored.

As I assume tuples/fake-crypto-material-0.1.zip to be identical to the tuple file used so far, is it required to re-upload the file again instead of referencing the file from an old commit?
Would it be more convenient to have both side by side?

Can we ignore the Codacy [list-item-indent] Incorrect list-item indent: add 2 spaces again?

There are a lot of findings from Codacy in this commit. Have you tried to resolve them? Seems mostly related to indention and newlines which seems resolvable.

Rewrote the file using remark README.md -o
Codacy seems fine with the changes now?
Maybe someone could add some information on remark to the Contribution Guide 😛

As written in the PR note, tuples/fake-crypto-material-0.1.zip is identical to the tuple file used so far, is it required to re-upload the file again instead of referencing the file from an old commit?
Would it be more convenient to have both side by side?

That's your call 😛
I can remove it from here, but I thought it may be easier to just have them next to each other.
Though we could also just put links in the README that is added by this PR, with the old tuple file being referenced there?

Can we ignore the Codacy [list-item-indent] Incorrect list-item indent: add 2 spaces again?

There are a lot of findings from Codacy in this commit. Have you tried to resolve them? Seems mostly related to indention and newlines which seems resolvable.

Rewrote the file using remark README.md -o Codacy seems fine with the changes now?
Maybe someone could add some information on remark to the Contribution Guide 😛

I would have to look into it first, but it seems legit at first glance. 😅

As written in the PR note, tuples/fake-crypto-material-0.1.zip is identical to the tuple file used so far, is it required to re-upload the file again instead of referencing the file from an old commit?
Would it be more convenient to have both side by side?

That's your call 😛 I can remove it from here, but I thought it may be easier to just have them next to each other. Though we could also just put links in the README that is added by this PR, with the old tuple file being referenced there?

Honestly, I'm fine with both. I think even once Klyshko is available for automated tuple generation, pre-generated tuples are still required to allow users to test Carbyne Stack easily and fast. Still I am not sure about keeping a version of deprecated files for kind of backwards compatibility. @strieflin any opinion on that?

Honestly, I'm fine with both. I think even once Klyshko is available for automated tuple generation, pre-generated tuples are still required to allow users to test Carbyne Stack easily and fast. Still I am not sure about keeping a version of deprecated files for kind of backwards compatibility. @strieflin any opinion on that?

At this stage I wouldn't care to much about backwards compatibility. From that point of view, I think even omitting the old tuples archive would be OK. Nevertheless, PR is already prepared and I think, we don't loose much just taking it as it is and use our time for improving more essential things.
For the time Klyshko will be available, this will be legacy. Klyshko will come with the ability to generate fake tuples easily, so no need anymore for pregenerated ones. However, it will still take some time to get to that point.

Regarding remark: We have mdformat in place as a precommit hook. Have you enabled that @kindlich? We should not add an additional tool, if what we have is sufficient already.

Regarding remark: We have mdformat in place as a precommit hook. Have you enabled that @kindlich? We should not add an additional tool, if what we have is sufficient already.

I can check for the next PR again, but I think it formatted the files in a way that Codacy complained about.
@strieflin Is there anything remaining in the PR?
From what I inferred it was mostly about the question whether the "old" tuple files should remain in there, which seems to be okay?

I can check for the next PR again, but I think it formatted the files in a way that Codacy complained about.

@kindlich Using pre-commit is not optional. If we are not happy with the results of running it, we have to fix the pre-commit configuration or configure Codacy in a way that it doesn't complain any more. I am open for both.
For this PR, I have revised the README to adhere to current pre-commit settings and fixed some other minor issues. As this PR is external, I can unfortunately not directly push my changes (or at least I don't know how). Please find the revised README file attached.
README.md


Can't remap shortcut to output multiple characters

Microsoft PowerToys version
0.75.1
Installation method
GitHub
Running as admin
None
Area(s) with issue?
Keyboard Manager
Steps to reproduce
Go into keyboard manager and select remap shortcut, choose a shortcut to be remapped (I chose Winkey + F12), then on the right hand side type the text you want it to map to (e.g. "Hello World"). My goal is that every time I press Winkey + F12 it autotypes Hello World for me.
✔ Expected Behavior
My actual goal is to have a handful of names, locations or whatever that I have to type a handful of times a day and it'd make life easier if I could have them typed for me via a shortcut key. That's what I thought this tool did, but it doesn't seem to.
❌ Actual Behavior
As I typed the test string "Hello World" it thought that each key press I was making was me changing my mind on what I wanted and at the end of the sequence it had mapped Winkey + F12 to the letter 'd'.
Other Software
No response

AutoHotkey or PowerAutomate could do this without breaking a sweat!

I don't know if I can trust AutoHotkey on the machine I use for online banking and work. As for PowerAutomate, that seems like using a nuclear weapon to kill a fly when you already have a fly-zapper but don't know how to turn it on. In my super stretched analogy here, the PowerToy "Remap Shortcut" is the fly-zapper and all I'm trying to get it to do is output more than one character. I would have thought that it was in the top 3 requirements of such a program. #1 remap existing shortcut to something else, #2 remap a new shortcut key combo to a different key combo, #3 map a new shortcut key to a string of characters.

@Jay-o-Way I think this is a duplicate of https://github.com/microsoft/PowerToys/issues/14120
This is planned for the next release of PowerToys 😃

It's a duplicate, but not of that issue. AutoHotkay is safe and practically built for this. It's lightweight and still powerful.

/dup #5668


[TRI-1642] Add Stripe invoice triggers

How to add a new trigger

Add an event specification for each: https://github.com/triggerdotdev/trigger.dev/blob/main/integrations/stripe/src/events.ts
Add a function for each, referencing the event: https://github.com/triggerdotdev/trigger.dev/blob/131d0dbea420b3174f6a6ea11de1fbb844853d91/integrations/stripe/src/index.ts#L848
Test the trigger works by adding it to the job-catalog, running it and triggering a webhook using Stripe's CLI: https://github.com/triggerdotdev/trigger.dev/blob/131d0dbea420b3174f6a6ea11de1fbb844853d91/references/job-catalog/src/stripe.ts#L165

List of events to add:
invoice.created
data.object is an invoice
Occurs whenever a new invoice is created. To learn how webhooks can be used with this event, and how they can affect it, see Using Webhooks with Subscriptions.
invoice.deleted
data.object is an invoice
Occurs whenever a draft invoice is deleted.
invoice.finalization_failed
data.object is an invoice
Occurs whenever a draft invoice cannot be finalized. See the invoice’s last finalization error for details.
invoice.finalized
data.object is an invoice
Occurs whenever a draft invoice is finalized and updated to be an open invoice.
invoice.marked_uncollectible
data.object is an invoice
Occurs whenever an invoice is marked uncollectible.
invoice.paid
data.object is an invoice
Occurs whenever an invoice payment attempt succeeds or an invoice is marked as paid out-of-band.
invoice.payment_action_required
data.object is an invoice
Occurs whenever an invoice payment attempt requires further user action to complete.
invoice.payment_failed
data.object is an invoice
Occurs whenever an invoice payment attempt fails, due either to a declined payment or to the lack of a stored payment method.
invoice.payment_succeeded
data.object is an invoice
Occurs whenever an invoice payment attempt succeeds.
invoice.sent
data.object is an invoice
Occurs whenever an invoice email is sent out.
invoice.upcoming
data.object is an invoice
Occurs X number of days before a subscription is scheduled to create an invoice that is automatically charged—where X is determined by your subscriptions settings. Note: The received Invoice object will not have an invoice ID.
invoice.updated
data.object is an invoice
Occurs whenever an invoice changes (e.g., the invoice amount).
invoice.voided
data.object is an invoice
Occurs whenever an invoice is voided.
invoiceitem.created
data.object is an invoiceitem
Occurs whenever an invoice item is created.
invoiceitem.deleted
data.object is an invoiceitem
Occurs whenever an invoice item is deleted.
TRI-1642

Assigned @rishi-raj-jain

This was completed by @ericallam


Update railtie to work with Rails 3.1.

This removes deprecation warnings with the ActionView template.

Nice, thanks. FWIW bldr doesn't really work with rails 3, so hopefully this is a step in the right direction.


Finish methods should has bitrate support but not finished in #1439

Please describe the changes this PR makes and why it should be merged:
Bitrate support was added in previus pull reqeset #1439, but not implemented in all methods and VoiceBroadcast.
This PR implement bitrate option in VoiceBroadcast, VoiceBroadcast#playOpusStream and VoiceConnection#playOpusStream, and also add a test purpose bot to evaluate above methods works correctly
This PR fix the bug that the opus option in AudioPlayer#playOpusStream didn't pass to StreamDispatcher correctly.
Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

All of this will be handled in the voice rewrite branch.
Thanks for the contribution though!


remove unneeded async fns, remove esModuleInterop, upgrade output to es6, bump package.json version to v2

Closes https://github.com/ProjectOpenSea/seaport-js/pull/128

Codecov Report
Patch coverage: 95.52% and project coverage change: +0.57 :tada:

Comparison is base (ecd0213) 93.13% compared to head (686861c) 93.71%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #246      +/-   ##
==========================================
+ Coverage   93.13%   93.71%   +0.57%
==========================================
  Files          16       16
  Lines        3790     3773      -17
  Branches      334      296      -38
==========================================
+ Hits         3530     3536       +6
+ Misses        250      232      -18
+ Partials       10        5       -5

Impacted Files
Coverage Δ

src/utils/approval.ts
93.20% <94.00%> (-4.05%)
:arrow_down:

src/seaport.ts
96.12% <100.00%> (+1.58%)
:arrow_up:

src/utils/fulfill.ts
94.92% <100.00%> (+0.40%)
:arrow_up:

... and 4 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

actually the initial reason was changing the async signatures on some fns:

fulfillBasicOrder in src/utils/fulfill.ts
fulfillStandardOrder in src/utils/fulfill.ts
getApprovalActions in src/utils/approval.ts


Created initial abstract renderers

Overview: What does this pull request change?

The purpose of this PR is an initial refactor of the renderer and scene. The main goals were to remove circular dependencies between scene, renderer and scene_file_writer, and to make scene agnostic to the type of renderer used. There is still a lot more refactoring and improvements to still do beyond this, but those first few goals already created quite a large PR so anything else now related to these I think should be outside the scope of this PR.

Created initial abstract Renderer class
Made scene agnostic to the type of renderer
Untangled circular dependencies between scene, renderer and scene_file_writer

Motivation and Explanation: Why and how do your changes improve the library?

The goals of this PR are

To make scene agnostic to the renderers. Currently scene needs to know if the renderer is opengl or cairo. This PR allows scene to treat both renderers (and any future renderers) the same.

To untangle the dependencies between scene <-> renderer and renderer <-> scene_file_writer. This avoids circular dependencies that adds complexity, makes the flow more difficult to follow and improves the decoupling of components. The scene now has access to a renderer and a scene_file_writer. The renderer does not need to be aware of the scene or the file_writer. The few cases where the renderer uses a file_writer it is passed as a parameter from the scene.

To create an initial abstract renderer that can be applied to cairo and opengl. This is not meant to be what the final abstract renderer will look like, it was simply to extract what the common methods currently are. Finding the final abstract renderers will involve making improvements to the renderers themselves and this is outside the scope of this PR.

Things that are outside the scope of this PR:

To make any improvements to the logic or functionality of the renderers, scene etc.
To try and find a final abstract renderer for the long-term. This will likely materialize after we merge the Mobjects and OpenGLMObjects to a united mobject. So you can think of the current Renderer class as a placeholder for now

In doing this a lot has moved about, such as renderer-specific logic to the renderers, and common logic to the scene, but the goal was to try and not change any behaviour.
Links to added or changed documentation pages

Further Information and Comments

This likely will not be merged to the main branch but will be targetting a new branch as part of the refactor.
It is a bit behind main, I will rebase to main once we are ready to start merging these kind of changes, but I thought I would open a draft for people to begin looking at it.
Most of the tests are passing. There are a four graphical unit tests not passing, I am not sure if this is due to an error in this PR, but I didn't think that it was. They are failing because the last frame in this PR is showing the scene, however in the stored test data the last frame is an empty scene. An example of one of the tests that fail is
@frames_comparison(last_frame=False)
def test_ZIndex(scene):
    circle = Circle().set_fill(RED, opacity=1)
    square = Square(side_length=1.7).set_fill(BLUE, opacity=1)
    triangle = Triangle().set_fill(GREEN, opacity=1)
    square.z_index = 0
    triangle.z_index = 1
    circle.z_index = 2

    scene.play(FadeIn(VGroup(circle, square, triangle)))
    scene.play(ApplyMethod(circle.shift, UP))
    scene.play(ApplyMethod(triangle.shift, 2 * UP))

I don't see from this scene why the last frame should be an empty scene?
The below tests fail:
FAILED tests/test_graphical_units/test_opengl.py::test_Circle - AssertionError:
FAILED tests/test_graphical_units/test_geometry.py::test_ZIndex - AssertionError:
FAILED tests/test_graphical_units/test_indication.py::test_FocusOn - AssertionError:
FAILED tests/test_graphical_units/test_indication.py::test_Flash - AssertionError:
FAILED tests/test_graphical_units/test_indication.py::test_ShowPassingFlash - AssertionError:

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

I put this on the list of relevant PRs on the Architecture discussion

https://github.com/ManimCommunity/manim/discussions/2836
Closing this for now till we have decided what to do


Pipes don't survive scope-app restarting

Sending KILL to the scope-app should have it back up and running with pipes intact. At the moment the pipes become unusable.

I realised there is a bug in pkill scope-app
in that the app id changes across restarts
so the pipe is torn down
-Tom

Actually I'm not sure this is going to be (easily) possible.  Even if we make the app id survive app restart, the probe is still going to kill the app client when the app goes away and it can't read the id, and currently the pipe is tied to the app client.  We could change that, but I don't think its worth the effort.


Mocha separate steps

@albertjan So finally here is the PR that implements #33! :)
I tried to implement the same separated steps thing for QUnit, but that failed because of:

it would have required QUnit 2, because only then the required before and after hooks were introduced, but to use QUnit2 this would require using ember-cli-qunit 3, which has some requirement on some more recent ember-cli version (2.4 IIRC)

there does not seem a way to tell QUnit during runtime that a test should be regarded as pending, as it is the case with the Mocha implementation. You can only statically declare a step as pending (Skip API: https://api.qunitjs.com/QUnit.skip/). But this would be required to mark all following steps (which are then separate tests) as pending in the case that during runtime the preceding test/step would fail.

Therefor this feature is missing for QUnit. To make this not behave differently for QUnit and Mocha by default and to still allow the "old" way, I added the new behaviour as an option. So without using the separateSteps option described in the Readme, this should be fully backwards compatible.
I refactored the index.js a little bit, as it would have become quit large and cluttered. And writing the generated test runners as code within strings also felt a bit awkward. Should look better now!

Thanks for merging!

this looks so much better 😄 thanks for the PR


Does instagram4j support to post stories

Does this api supports to publish stories?

I have the same problem, it is possible?

#165


IFormFile vs byte[]

#19535 Issue description
I'm designing a REST API controller with .NET CORE so I can upload a file, should I use IFormFile or  byte[] in my request ?
It's  better to this :
public class AttachmentModel
    {
        public string FileName { get; set; }
        public byte[] FileContent { get; set; }
   }

or this :

public class AttachmentModel
    {
        public string FileName { get; set; }
        public IFormFile  FileContent { get; set; }
   }

Software versions

[ ] .NET Core 3.1

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

Potential bugs in the ASP.NET Core framework and product feedback can be reported at dotnet/aspnetcore issues (include full repro steps and cross-link to a repro project in GH when appropriate). For Visual Studio, use the Report a Problem gesture or Suggest a Feature gesture within VS, which open internal issues for the VS team. For Visual Studio Code, you can open an issue at microsoft/vscode issues.

Ok, thanks.


No matching distribution found for stt==1.0.0

When I install the package, I'm getting
> pip install -r requirements.txt
Collecting cycler==0.10.0
  Using cached cycler-0.10.0-py2.py3-none-any.whl (6.5 kB)
Collecting numpy
  Using cached numpy-1.22.2.zip (11.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
ERROR: Could not find a version that satisfies the requirement stt==1.0.0 (from versions: none)
ERROR: No matching distribution found for stt==1.0.0

UPDATE
Looks like an issue with stt
> pip install stt==1.2.0
ERROR: Could not find a version that satisfies the requirement stt==1.2.0 (from versions: none)
ERROR: No matching distribution found for stt==1.2.0

https://github.com/coqui-ai/STT/issues/2115

Not an AutoSub issue. Closing.


Fix name in CI exclude

I noticed I forgot to change the name for ruby: in the exclude line added in https://github.com/CanCanCommunity/cancancan/pull/682.
Now it should be good :)

Tackled in #707 . Thanks!


squid:S1118 - Utility classes should not have public constructors

This pull request is focused on resolving occurrences of Sonar rule
squid:S1118 - Utility classes should not have public constructors.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1118
Please let me know if you have any questions.
George Kankava

Thanks @georgekankava!


Image Similarity Scoring with SAPUI5

Hi,
submit answer button does not accept answer :
"Process completed!
Target URL: /ml-dest/imagefeatureextraction/feature-extraction"
what can the answer be?
Best regards,

Closing due to inactivity. Please feel free to reopen if needed.


RESTORE DB on Managed Instance doesn't work

Issue Type: Bug
Connect to managed instance and restore database - restore flow doesn't work.
GENERAL tab

MI doesn't supports restore from the database/file - please put URL as source.
Cannot choose the file path. It selects path for automated backups https://wasd2prodwcus1abakmi55.blob.core.windows.net/managedserverbac-b48544e2-eaa6-4280-a837-05400712d912/backup and then returns "An error occurred while loading the file browser." error.
2.1 Wishlist 1- could backup file path be somehow pre-populated the list with URL from credentials that start with https: because these are credentials for blob storages that will be used for restore.
When I return back from select file path dialog I'm getting some Database dropdown that is not loaded - probably bug.
Target database cannot  be dropdown with existing databases because MI don't support restore into existing database. User must enter new database name in text box.
Not sure what is Restore to and Restore plan - they are empty.
FILES tab
Remove it because we are not supporting relocation of files. in restore syntax you cannot specify file names because we are automatically relocating files on internal paths.
OPTIONS tab
Remove because RESTORE WITH options are not supported.

SQL Operations Studio version: sqlops 0.31.4 (e026ab85a72c190cc4ccc834503aa9fe36dd6407, 2018-07-18T02:14:21.826Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz (4 x 2904)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.84GB (4.97GB free)

Process Argv
C:\Program Files\SQL Operations Studio\sqlops.exe

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

agent
Mic
0.31.4

profiler
Mic
0.1.2

+1

This should be fixed with https://github.com/microsoft/azuredatastudio/pull/19244, the latest insiders builds have this improvement and it will be included in the next stable release (1.37)


Update ug

added sscreenshots

Codecov Report

Merging #180 (8d49e17) into master (d329a84) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #180   +/-   ##
=========================================
  Coverage     58.39%   58.39%
  Complexity      671      671
=========================================
  Files           135      135
  Lines          2723     2723
  Branches        358      358
=========================================
  Hits           1590     1590
  Misses         1061     1061
  Partials         72       72

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.