[go_router] Named GoRoutes cause exception when dynamically updating routing table

Is there an existing issue for this?

[X] I have searched the existing package issues
[X] I have read the guide to filing a bug

What package does this bug report belong to?
go_router
What target platforms are you seeing this bug on?
Android, iOS
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  clock:
    dependency: transitive
    description:
      name: clock
      sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  collection:
    dependency: transitive
    description:
      name: collection
      sha256: f092b211a4319e98e5ff58223576de6c2803db36221657b46c82574721240687
      url: "https://pub.dev"
    source: hosted
    version: "1.17.2"
  cupertino_icons:
    dependency: "direct main"
    description:
      name: cupertino_icons
      sha256: d57953e10f9f8327ce64a508a355f0b1ec902193f66288e8cb5070e7c47eeb2d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.6"
  fake_async:
    dependency: transitive
    description:
      name: fake_async
      sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.1"
  flutter:
    dependency: "direct main"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_lints:
    dependency: "direct dev"
    description:
      name: flutter_lints
      sha256: a25a15ebbdfc33ab1cd26c63a6ee519df92338a9c10f122adda92938253bef04
      url: "https://pub.dev"
    source: hosted
    version: "2.0.3"
  flutter_test:
    dependency: "direct dev"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_web_plugins:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  go_router:
    dependency: "direct main"
    description:
      name: go_router
      sha256: a206cc4621a644531a2e05e7774616ab4d9d85eab1f3b0e255f3102937fccab1
      url: "https://pub.dev"
    source: hosted
    version: "12.0.0"
  lints:
    dependency: transitive
    description:
      name: lints
      sha256: "0a217c6c989d21039f1498c3ed9f3ed71b354e69873f13a8dfc3c9fe76f1b452"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  logging:
    dependency: transitive
    description:
      name: logging
      sha256: "623a88c9594aa774443aa3eb2d41807a48486b5613e67599fb4c41c0ad47c340"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  matcher:
    dependency: transitive
    description:
      name: matcher
      sha256: "1803e76e6653768d64ed8ff2e1e67bea3ad4b923eb5c56a295c3e634bad5960e"
      url: "https://pub.dev"
    source: hosted
    version: "0.12.16"
  material_color_utilities:
    dependency: transitive
    description:
      name: material_color_utilities
      sha256: "9528f2f296073ff54cb9fee677df673ace1218163c3bc7628093e7eed5203d41"
      url: "https://pub.dev"
    source: hosted
    version: "0.5.0"
  meta:
    dependency: transitive
    description:
      name: meta
      sha256: "3c74dbf8763d36539f114c799d8a2d87343b5067e9d796ca22b5eb8437090ee3"
      url: "https://pub.dev"
    source: hosted
    version: "1.9.1"
  path:
    dependency: transitive
    description:
      name: path
      sha256: "8829d8a55c13fc0e37127c29fedf290c102f4e40ae94ada574091fe0ff96c917"
      url: "https://pub.dev"
    source: hosted
    version: "1.8.3"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_span:
    dependency: transitive
    description:
      name: source_span
      sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  stack_trace:
    dependency: transitive
    description:
      name: stack_trace
      sha256: c3c7d8edb15bee7f0f74debd4b9c5f3c2ea86766fe4178eb2a18eb30a0bdaed5
      url: "https://pub.dev"
    source: hosted
    version: "1.11.0"
  stream_channel:
    dependency: transitive
    description:
      name: stream_channel
      sha256: "83615bee9045c1d322bbbd1ba209b7a749c2cbcdcb3fdd1df8eb488b3279c1c8"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  term_glyph:
    dependency: transitive
    description:
      name: term_glyph
      sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"
  test_api:
    dependency: transitive
    description:
      name: test_api
      sha256: "75760ffd7786fffdfb9597c35c5b27eaeec82be8edfb6d71d32651128ed7aab8"
      url: "https://pub.dev"
    source: hosted
    version: "0.6.0"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  web:
    dependency: transitive
    description:
      name: web
      sha256: dc8ccd225a2005c1be616fe02951e2e342092edf968cf0844220383757ef8f10
      url: "https://pub.dev"
    source: hosted
    version: "0.1.4-beta"
sdks:
  dart: ">=3.1.3 <4.0.0"
  flutter: ">=3.7.0"

Steps to reproduce

Launch the provided code sample.
Tap the 'Add a new route' button.

I wanted to use the new dynamic RoutingConfig feature in GoRouter 12, using the GoRouter.routingConfig() constructor. However, I'm finding that using named GoRoutes (i.e. passing a value for the name parameter) is incompatible with this feature. If I try to update the RoutingConfig, the following exception is raised:
Failed assertion: line 622 pos 15: '!_nameToPath.containsKey(name)'
The provided code sample is based on go_router/example/lib/routing_config.dart, with the only change being that I added a name to the GoRoutes on lines 46 and 83 as follows:
  RoutingConfig _generateRoutingConfig() {
    return RoutingConfig(
      routes: <RouteBase>[
        GoRoute(
          name: 'home', // <-- Added this line
          path: '/',
          builder: (_, __) {
            // ...
          },
        ),

Expected results
Expected no exception to be thrown.
Actual results
The following exception is printed to the console:
======== Exception caught by foundation library ====================================================
The following assertion was thrown while dispatching notifications for ValueNotifier<RoutingConfig>:
duplication fullpaths for name "home":/, /
'package:go_router/src/configuration.dart':
Failed assertion: line 622 pos 15: '!_nameToPath.containsKey(name)'

When the exception was thrown, this was the stack:
#2      RouteConfiguration._cacheNameToPath (package:go_router/src/configuration.dart:622:15)
#3      RouteConfiguration._onRoutingTableChanged (package:go_router/src/configuration.dart:199:5)
#4      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:403:24)
#5      ValueNotifier.value= (package:flutter/src/foundation/change_notifier.dart:530:5)
#6      _MyAppState._generateRoutingConfig.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:go_router_bug/main.dart:62:36)
#7      State.setState (package:flutter/src/widgets/framework.dart:1138:30)
#8      _MyAppState._generateRoutingConfig.<anonymous closure>.<anonymous closure> (package:go_router_bug/main.dart:59:25)
#9      _InkResponseState.handleTap (package:flutter/src/material/ink_well.dart:1154:21)
#10     GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:275:24)
#11     TapGestureRecognizer.handleTapUp (package:flutter/src/gestures/tap.dart:654:11)
#12     BaseTapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:311:5)
#13     BaseTapGestureRecognizer.handlePrimaryPointer (package:flutter/src/gestures/tap.dart:244:7)
#14     PrimaryPointerGestureRecognizer.handleEvent (package:flutter/src/gestures/recognizer.dart:630:9)
#15     PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:98:12)
#16     PointerRouter._dispatchEventToRoutes.<anonymous closure> (package:flutter/src/gestures/pointer_router.dart:143:9)
#17     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:625:13)
#18     PointerRouter._dispatchEventToRoutes (package:flutter/src/gestures/pointer_router.dart:141:18)
#19     PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:127:7)
#20     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:488:19)
#21     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:468:22)
#22     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:333:11)
#23     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:413:7)
#24     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:376:5)
#25     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:323:7)
#26     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:292:9)
#27     _invoke1 (dart:ui/hooks.dart:186:13)
#28     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:424:7)
#29     _dispatchPointerDataPacket (dart:ui/hooks.dart:119:31)
(elided 2 frames from class _AssertionError)
The ValueNotifier<RoutingConfig> sending notification was: ValueNotifier<RoutingConfig>#57e04(Instance of 'RoutingConfig')
====================================================================================================

Code sample
Code sample
// Copyright 2013 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

/// This app shows how to dynamically add more route into routing config
void main() => runApp(const MyApp());

/// The main app.
class MyApp extends StatefulWidget {
  /// Constructs a [MyApp]
  const MyApp({super.key});

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  bool isNewRouteAdded = false;

  late final ValueNotifier<RoutingConfig> myConfig =
  ValueNotifier<RoutingConfig>(_generateRoutingConfig());

  late final GoRouter router = GoRouter.routingConfig(
      routingConfig: myConfig,
      errorBuilder: (_, GoRouterState state) => Scaffold(
        appBar: AppBar(title: const Text('Page not found')),
        body: Center(
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              children: <Widget>[
                Text('${state.uri} does not exist'),
                ElevatedButton(
                    onPressed: () => router.go('/'),
                    child: const Text('Go to home')),
              ],
            )),
      ));

  RoutingConfig _generateRoutingConfig() {
    return RoutingConfig(
      routes: <RouteBase>[
        GoRoute(
          name: 'home',
          path: '/',
          builder: (_, __) {
            return Scaffold(
              appBar: AppBar(title: const Text('Home')),
              body: Center(
                child: Row(
                  mainAxisAlignment: MainAxisAlignment.center,
                  children: <Widget>[
                    ElevatedButton(
                      onPressed: isNewRouteAdded
                          ? null
                          : () {
                        setState(() {
                          isNewRouteAdded = true;
                          // Modify the routing config.
                          myConfig.value = _generateRoutingConfig();
                        });
                      },
                      child: isNewRouteAdded
                          ? const Text('A route has been added')
                          : const Text('Add a new route'),
                    ),
                    ElevatedButton(
                      onPressed: () {
                        router.go('/new-route');
                      },
                      child: const Text('Try going to /new-route'),
                    )
                  ],
                ),
              ),
            );
          },
        ),
        if (isNewRouteAdded)
          GoRoute(
            name: 'new',
            path: '/new-route',
            builder: (_, __) {
              return Scaffold(
                appBar: AppBar(title: const Text('A new Route')),
                body: Center(
                    child: Column(
                      mainAxisAlignment: MainAxisAlignment.center,
                      children: <Widget>[
                        ElevatedButton(
                            onPressed: () => router.go('/'),
                            child: const Text('Go to home')),
                      ],
                    )),
              );
            },
          ),
      ],
    );
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      routerConfig: router,
    );
  }
}

Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Launching lib/main.dart on macOS in debug mode...
Building macOS application...
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006021-0002295C1447401E }
{ platform:macOS, arch:x86_64, id:00006021-0002295C1447401E }
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.072 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.073 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.073 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.073 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.081 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
2023-10-24 09:44:48.082 xcodebuild[58060:5961273] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
Details:  createItemModels creation requirements should not create capability item model for a capability item model that already exists.
Function: createItemModels(for:itemModelSource:)
Thread:   <_NSMainThread: 0x600003d10240>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
Debug service listening on ws://<IP_ADDRESS>:62672/IxmgW4ZZk-o=/ws
Syncing files to device macOS...

======== Exception caught by foundation library ====================================================
The following assertion was thrown while dispatching notifications for ValueNotifier<RoutingConfig>:
duplication fullpaths for name "home":/, /
'package:go_router/src/configuration.dart':
Failed assertion: line 622 pos 15: '!_nameToPath.containsKey(name)'

When the exception was thrown, this was the stack:
#2      RouteConfiguration._cacheNameToPath (package:go_router/src/configuration.dart:622:15)
#3      RouteConfiguration._onRoutingTableChanged (package:go_router/src/configuration.dart:199:5)
#4      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:403:24)
#5      ValueNotifier.value= (package:flutter/src/foundation/change_notifier.dart:530:5)
#6      _MyAppState._generateRoutingConfig.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:go_router_bug/main.dart:62:36)
#7      State.setState (package:flutter/src/widgets/framework.dart:1138:30)
#8      _MyAppState._generateRoutingConfig.<anonymous closure>.<anonymous closure> (package:go_router_bug/main.dart:59:25)
#9      _InkResponseState.handleTap (package:flutter/src/material/ink_well.dart:1154:21)
#10     GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:275:24)
#11     TapGestureRecognizer.handleTapUp (package:flutter/src/gestures/tap.dart:654:11)
#12     BaseTapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:311:5)
#13     BaseTapGestureRecognizer.handlePrimaryPointer (package:flutter/src/gestures/tap.dart:244:7)
#14     PrimaryPointerGestureRecognizer.handleEvent (package:flutter/src/gestures/recognizer.dart:630:9)
#15     PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:98:12)
#16     PointerRouter._dispatchEventToRoutes.<anonymous closure> (package:flutter/src/gestures/pointer_router.dart:143:9)
#17     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:625:13)
#18     PointerRouter._dispatchEventToRoutes (package:flutter/src/gestures/pointer_router.dart:141:18)
#19     PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:127:7)
#20     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:488:19)
#21     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:468:22)
#22     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:333:11)
#23     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:413:7)
#24     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:376:5)
#25     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:323:7)
#26     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:292:9)
#27     _invoke1 (dart:ui/hooks.dart:186:13)
#28     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:424:7)
#29     _dispatchPointerDataPacket (dart:ui/hooks.dart:119:31)
(elided 2 frames from class _AssertionError)
The ValueNotifier<RoutingConfig> sending notification was: ValueNotifier<RoutingConfig>#57e04(Instance of 'RoutingConfig')
====================================================================================================

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @hakonber. Thanks for filing this issue. From the logs, I see there is an open issue similar/related to this #117449, can you check this out to confirm it is? If not, the code sample has some complex codes that might be unrelated in reproducing this issue, can you please provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code?
Thank you!

Hi @dam-ease. Issue #117449 doesn't seem to be related. The issue I've posted above is related to the new dynamic routing table capability (GoRouter.routingConfig()) that was added in the recently released v12.0.0 of go_router.
Regarding the code sample I provided, I'm not sure if it can be made much smaller. It's based on one of go_router's included examples. There's no 3rd party code. The only change I made to the example code was to give the GoRoutes names (line 46 and 83), which is what causes an exception to be raised. I believe not supporting named GoRoutes when using dynamic routing must be a bug.

Thanks a lot for your detailed response, I see the issue I was facing in running this earlier.  I can reproduce the issue on my end running on the latest versions of go_router and flutter.
Details

[✓] Flutter (Channel stable, 3.13.8, on macOS 13.0 22A380 darwin-arm64, locale
    en-NG)
    • Flutter version 3.13.8 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio
      Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build
      17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        •
      android-arm64  • Android 14 (API 34) (emulator)
    • iPhone XS (mobile)          • 3CFD1268-0D52-486E-A12E-6E136E972D94 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                •
      darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)                • chrome                               •
      web-javascript • Google Chrome 118.0.5993.88

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[✓] Flutter (Channel stable, 3.13.8, on macOS 13.0 22A380 darwin-arm64, locale en-NG)
    • Flutter version 3.13.8 on channel stable at /Users/damilolaalimi/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 14 (API
      34) (emulator)
    • iPhone 14 Pro (mobile)      • 6548B0D1-7674-4306-9852-198C465F1104 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.0 22A380
      darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome
      118.0.5993.88

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.


Request: Add happyaccidents.ai to filter list

https://www.happyaccidents.ai
It's another AI image generator. Need I say more?

done


WL-4521 Two Sakai fixes for roster/site members.

It's easier if you can just do plain cherry-picks and not touch/sqaush the commits as then when coming to merge it's obvious that they should be skipped because they are in Sakai. Did you have todo much manual merging for this one?

As agreed have amended the commit message.


Cockpit Modules

I've been using 45drives cockpit modules on my current server (not coreOS) and they have been quite helpful to make file server operations easier.
It would be nice to have these (at least for zfs builds) available. These help bridge some of the UI gap for getting sharing up and running.
Cockpit client will also incorporate these modules.

potential fix:
https://github.com/45Drives/cockpit-zfs-manager/issues/15#issuecomment-1698850989

This commit fixed it for me: https://github.com/bketelsen/homer/commit/23303b522c76ecddb303bc319708649458447226


Chinese: parse numerals

This can be done by reverse-engineering @tventimi 's processNumbers() Parallelogram function:
https://github.com/pulibrary/parallelogram/blob/main/cloudapp/src/app/pinyin.service.ts#L160
From earlier correspondence:

The number conversion depends on the table only in the sense that certain entries are marked with a # if they represent > numbers or are part of the context in which a number would appear.  This is a fairly short list, which I paste below:
〇,ling#0
零,ling#0
一,yi#1
二,er#2
兩,liang#2
两,liang#2
三,san#3
四,si#4
五,wu#5
六,liu#6
七,qi#7
八,ba#8
九,jiu#9
十,shi#10
廾,gong#20
廿,nian#20
卅,sa#30
卌,xi#40
百,bai#100
千,qian#1000
万,wan#10000
萬,wan#10000
亿,yi#100000000
億,yi#100000000
及,ji#
至,zhi#
年,nian#
月,yue#
日,ri#
第,di#
When the "#" is followed by a number, that represents the numeric value of the character.  The other entries are: 及 and 至 ("to" when used in a date range), 年 (year), 月(month), 日 (day), and 第 (ordinal marker, used before a number to indicate 1st, 2nd, 3rd, etc).
As far as the format for date ranges, the code looks for any sequence of characters containing only numbers and/or the 5 date-related characters 及至 年 月 日.  As long as that sequence contains both (年 and 月) or (月 and 日), then it considered a date and any numerical characters in that entire sequence are converted to numbers.  This covers a variety of different formats that a date range could be in.

Fixed by #96.


Show dates in notes on calendar

Would it be possible to have the calendar scan a note, or set of notes, for dates and show all of them? Ideally this wouldn't be a "copy", it would use the notes as the source of truth.
I'm asking because I currently have a campaign timeline note where I bullet-point everything like:

1420-01-01

A cult of Orcus sets up on a island 20 miles west of Saltmarsh.

1504-02-20

The party arrives in Saltmarsh

1504-02-21

The party hears that a corpse of an adventurer was found on the beach, and start to investigate
The hear rumours that the dead adventurer was last seen in the [[Haunted Mansion]]

And it would be really great to render that as a calendar sometimes.

I think this is possible, let me think about how to implement it.


[User Story-Resource Explorer] Button to start the client generation

As a user, when I click on the generate button on the collection view ,
my collection will be used to generate an API client

Removing from milestone as spec might change

Closing this issue as it's not part of the scope anymore. New scope includes generating an API manifest which is covered in a different epic. @thewahome do you agree?

agreed


pkg/operator/targetconfigcontroller: block rollout and report on missing external resource

The current code reports the invalid resource but does not block a new revision from being created. In the case that configmap openshift-config-managed/csr-controller-ca is not managed by cluster-kube-controller-manager-operator block if SNO.

/retest
cc @soltysh

error: unable to read image registry.build02.ci.openshift.org/ci-op-g6h0r2i8/stable-initial@sha256:6c05d74eb1fa37a77ed9215d83933265564d661dd96fa765a3e6799340c6fae5: received unexpected HTTP status: 504 Gateway Time-out

/test e2e-upgrade

/hold


[FixBug][seatunnel-web]Fix delete job task

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
Fixed an issue where the jobdefinition was deleted but the job task was not deleted

Please add a screenshot of the test passing

LGTM


CodeQL migration: C# topics - change titles & add intros (2174)

product-documentation issue #2174
Summary
This changes the titles of the C# topics in the "Learning" section, and adds intros as the first paragraph.
I've also made some small editorial changes to bring the style a little more in line with GitHub's writing style. However, I haven't made any larger content changes or structural changes.
Changes in this PR

Article preview
Source
Notes

"CodeQL for C#"
Source

"CodeQL library for C#"
Source

"Analyzing data flow in C#"
Source

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Merging this - as discussed at this week's DSP docs meeting.

Ah, I see. A user could doing an analysis with the CodeQL CLI, CodeQL for VS Code, or the query console, so we probably don't want to mention a specific product here. Suggest changing to:
When you're analyzing a C# program, you can make use of the large collection of classes in the CodeQL libraries for C#.


API directory issue

when i run this command "ts-node --pretty utils/create-entities-index.ts"
then it throw me below error in my cmd
node:internal/modules/cjs/loader:988
throw err;
^
Error: Cannot find module './create-entities-index.ts'
Require stack:

C:\new_wamp64\www\multivendor-marketplace-master\api\utils\imaginaryUncacheableRequireResolveScript
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15)
    at Function.resolve (node:internal/modules/cjs/helpers:109:19)
at requireResolveNonCached (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:549:16)
at getProjectSearchDir (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:519:40)
at phase3 (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:267:27)
at bootstrap (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:47:30)
at main (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:33:12)
at Object. (C:\Users\vatsa\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js:579:5)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\new_wamp64\www\multivendor-marketplace-master\api\utils\imaginaryUncacheableRequireResolveScript'
]
}

Hi @Rajan417
In Spurtcommerce multivendor-marketplace build, you do NOT have access to the source code of utils/create-entities-index.ts file and hence its impractical for you to execute direct commands like  "ts-node --pretty utils/create-entities-index.ts".
However you can run the whole API build.
Navigate to api/ folder then execute -> node dist/src/app.js
Please let us know if you need further assistance.


fix: externalize dependencies

Why are these changes introduced?
Fixes ENG-8711

Nuxt 2 throws webpack warnings and errors when using the sdk v2 transpiled

The ticket describes a webpack warning in Nuxt 2 projects using<EMAIL_ADDRESS>
WARNING in [file] [line]:[column-range]
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

When we inspect the Storefront SDK's bundled code, we can find the new Function("require") that the warning refers to:

This code is from @urql/exchange-persisted-fetch: https://github.com/urql-graphql/urql/blob/34f83b14af9531f0335cd1c9d9fa3bfc8a6835a1/exchanges/persisted-fetch/src/sha256.ts#L19
Recognizing this made it clear that @urql/exchange-persisted-fetch was being unexpectedly bundled in the @nacelle/storefront-sdk code. This was also the case for @urql/exchange-retry.
What is this pull request doing?

This PR externalizes some dependencies that were being included in the @nacelle/storefront-sdk bundle. This fixes the issue described above.
How to Test

Check out the test-storefront-sdk-v2-with-nuxt-2 project's main branch.
npm i && npm run dev - you should see the error message described in the ticket (in the console).
Check out the ENG-8711-externalize-dependencies branch of nacelle-js.
Navigate to packages/storefront-sdk.
npm run build.
Use npm link/npm link -S @nacelle/storefront-sdk to link packages/storefront-sdk to the test-storefront-sdk-v2-with-nuxt-2 project.
When running npm run dev again, there should be no "Critical dependency" warnings.

Checklist

[x] This Pull Request aligns with nacelle-js' Code of Conduct.
[x] You can follow your own "How to Test" instructions and get the expected result.

Hey @NWRichmond, I'm not seeing the error on npm run dev but I still get one on npm run generate

@KrisQ that's strange, I'm not getting any errors with npm run generate after building @nacelle/storefront-sdk and linking it to the project:

Let's do a screen share to get to the bottom of the discrepency between our setups.


:sparkles: Adding aws-cli to docker image

Summary
This image will be use as initContainer to copy the aws-cli to klusterlet-agent when initialized with awsirsa auth type.
This will allow us to keep registration-operator docker image clean.
Related issue(s)
Fixes # https://github.com/open-cluster-management-io/ocm/issues/514

also would you help to remind me on why we do not use aws go sdk? https://pkg.go.dev/github.com/aws/aws-sdk-go-v2. I remember we discussed this before. It will be good to leave some comments so we do not miss the reason.

also would you help to remind me on why we do not use aws go sdk? https://pkg.go.dev/github.com/aws/aws-sdk-go-v2. I remember we discussed this before. It will be good to leave some comments so we do not miss the reason.

Yes, that is because the eks kubeconfig uses aws cli. We discussed about it and @deads2k suggested an option to copy aws cli from init container to klusterlet agent container. With this we do not have to maintain 2 copies of registration operator docker image, one for csr and other for aws auth.
https://github.com/open-cluster-management-io/enhancements/pull/125#discussion_r1678003208
With

/approve
@mikeshng I think we also need to create a repo in quay for this image.

/approve
@mikeshng I think we also need to create a repo in quay for this image.

Ok. I have submitted the repo creation request. Thank you all for your patience.


Improve screen reader support for  comment reactions

Microsoft/vscode#69321
Tested using VoiceOver on MacOS
Issues

The add reaction button on the right side is currently read out at Menu (8 items)

When focusing on a reaction in the context menu, it is read as just the emoji name. Github instead reads each option as React with smily face

The existing reactions do not have helpful voice text. They should be read as the reaction name and number of reactions

The add reaction button the right of existing reactions also does not have helpful voice over labels

The add reaction button on the right side is currently read out at Menu (8 items)

This is now read as "Toggle Reaction"

When focusing on a reaction in the context menu, it is read as just the emoji name. Github instead reads each option as React with smily face

Since this uses a context menu, this is intentional. Menus don't have special aria labels.

The existing reactions do not have helpful voice text. They should be read as the reaction name and number of reactions

This now reads a more useful "Toggle reaction, x reactions with y" message.

The add reaction button the right of existing reactions also does not have helpful voice over labels

Same as above since this is a menu.

This seems improved but I can't get it to read the menu when I tab from the comment to the react menu button. It doesn't read anything when I use the arrow keys to move focus between menu buttons. If I expand the menu with space, then it reads the menu name. It looks like this, so I guess voiceover is stuck on the full comment context even though focus has moved. Not a voiceover expert though, is that an issue or should I be using other nav keys anyway?


Fill submaps slices

This implements a frequently used function (twice in cartographer_ros).
Also, it corrects a wrong repeated proto field access,
so we can fix cartographer_ros/issues/944.

Merge requested by authorized user gaschler. Merge queue now has a length of 1.

Refusing to merge, since the combined checks state is failure


Please update the readme with newer ROCM instructions

the readme tells me to install rocm 5.4.2 but rocm  5.4.2 is no longer working rocm 5.7 works. it would be super helpful to AMD GPU users if the rocm instructions were updated in the readme thank you

I put a pretty  thorough guide in https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/272#issuecomment-2071131203


test: run tests on AWS with Flatcar edge too

There were no tests being run with Flatcar edge.

Oops:

Each term consists of letters, digits, underscores, and dots.

https://golang.org/pkg/go/build/#hdr-Build_Constraints

I've tested the edge pipeline here and it seems to work: https://yard.lokomotive-k8s.net/teams/main/pipelines/lokomotive-oss-aws-edge-master/jobs/test-lokomotive-aws-deployment/builds/42

I'd leave it like this. If a certain release breaks we can disable the pipeline until the next release is out.

The bare metal pipeline passed but didn't notify GitHub: https://yard.lokomotive-k8s.net/teams/main/pipelines/lokomotive-oss-bare-metal-pr/jobs/test-lokomotive-deployment/builds/306
I'll merge.


List input files in history metadata attribute

At present, Zarrs produced by nc2zarr don't contain any indication of the source files from which they were generated. nc2zarr should optionally include a list of source files in the value of the Zarr's history attribute on first generation, and update this value with the additional input files when appending to an existing Zarr.

Several metadata attributes may be updated in a CF-compliant way, see section Description of File Contents in the CF conventions.

Should be resolved together with #20.

Implementing this will also help with implementation of a related feature request from CloudFerro: the ability to ignore an input file when appending if it has already been ingested into the target Zarr. nc2zarr could check the input pathname or filename against the list in the history attribute before appending.

@pont-us Please note:

[ ] Append to the history attribute when what has been done: "\n: converted to Zarr using nc2zarr ".
[ ] Use the sources attribute to list the sources.
[ ] Resolve  #20

Implementing this will also help with implementation of a related feature request from CloudFerro: the ability to ignore an input file when appending if it has already been ingested into the target Zarr. nc2zarr could check the input pathname or filename against the list in the history attribute before appending.

We should not use metadata to make decisions about the data in the dataset. Whether a timeslice has already been processed or not should be detected by looking into the data: time coordinates. Once it is detected there are two options: ignore new data or replace existing. To replace an existing timeslice by a more up-to-date one is a valid use case we have in other scenarios. (Example: Same Sentinel 3 Level-2 data is beeing processed in a fast lane and another one that takes much more time but has higher data quality. When the second data arrives, the first is replaced.)

We should not use metadata to make decisions about the data in the dataset. Whether a timeslice has already been processed or not should be detected by looking into the data: time coordinates.

Agreed -- I've opened Issue #41 to discuss and implement this functionality.


Upgrade version of semver used

The most recent version of the semver repository has fixed a few bugs in version requirements that it rejects. If we update to it, however, it causes breakage, so we had to revert the recent update.
Looks like the semver crate has fixed bugs recently to support new version requirements with build metadata.
I think what we'll need to do is to add a strategy like this where we continue to parse old version requirements, but warn about them.
@steveklabnik, could you add a feature to the semver crate to support old version requirements like 0.2*? Once we do that we can update Cargo to using that, warn about old broken requirements, and start picking up bug fixes.

Yes, I have planned to, I just have not had the time. It's going to be a big pain, but it's manageable.

I think I'm going to try to tackle this thursday or friday, depending on how the release goes.

Ok, thanks @steveklabnik! If it's too onerous we could also just vendor something locally in Cargo like an old regex or something like that.

That's precisely the issue: the version of semver we're using in Cargo currently has nom for Versions, and a hand-rolled parser for VersionReqs, so it's going from one parser (semver-parser, which is regex based) to three.
I have a plan (shove the older parser under an old module), it's just that it's not super simple, and tedious, so I haven't made it happen. But I also really want to get Cargo on the new semver; if I hadn't been travelling the last three weeks, I probably could have found the time. Now this week is the release...

I think it's probably ok to not literally use the same parser, we can probably just scrape all Cargo.toml files on crates.io and parse them to learn about all "invalid" specs.
Would that be helpful to generate such a list?

Oh yeah, is there an easy way to get all Cargo.toml files? I would love that for my own regression testing.

My plan was to just download all *.crate files, extract all files named Cargo.toml, and then parse them. So I guess not exactly easy :)

hehe.
well, yeah, if we can get that data set, I can maybe make it work more easily. If you can do it, that'd be good. Primarily, it would mean not bringing back the nom dependency, which would be nice. Not because nom isn't nice, but to keep cargo lighter.

Ok, here's the list: https://gist.github.com/alexcrichton/97d3fa76b90e232eb61af37a59da91ad
I downloaded every crate file from crates.io, parse all files that looked like Cargo.toml, and then looked at all TOML strings in that file. If it succeeded with the previous semver parser and failed with the most recent one, I printed it out.
The panic there is presumably an older bug in semver, so can be ignored, and word-like ones like "x-smtpapi" I think are false positives (but are odd to be accepted by the old parser!).
In short it looks like the complete list of versions we need to keep accepting are:
.*
*.0
0.1.0.
0.2*
<IP_ADDRESS>

Those are spread across a whole mess of crates though

So, on Friday I tried to run the script to reproduce the list, but got bad results. I'm guessing something is wrong. Regardless, looking at those examples:

.* should be *.
*.0 is a bug, imho. Apparently npm parses it as *: https://github.com/npm/node-semver/issues/171
0.1.0. should be 0.1.0.
0.2* should be 0.2
<IP_ADDRESS> actually used to parse as 0.3.13! https://github.com/lensvol/strfile-rs/pull/1

Given that these are such a small number of cases, I think we can just handle them individually.
I've implemented a fix here: https://github.com/steveklabnik/semver/tree/deprecation One commit: https://github.com/steveklabnik/semver/commit/aae8a4530639d28557c329a6eefc11d21d77c1c0
This will stop us from having to bring back in the entire old parser.
What do you think? @alexcrichton could you try to run your script again against that branch? If so, I will prepare a real PR against semver and Cargo. We can't print out the warning in semver, since you want to respect cargo's settings; the idea is that i'll add a new error case, Deprecated, that still gives you the fixed version, and we can handle that logic similarly to TOML.

@steveklabnik sounds reasonable to me, but perhaps this behavior could be disabled by default? I doubt anyone actually wants to publish something with 0.2* as a version requirement, so Cargo will at least want to warn about invalid version requirements even if it parses them.

What would "disabled by default" mean? You mean in the Cargo side of the patch? I'm certainly open to it.

Oh imagine that Cargo would actively go out of its way to parse these version requirements. General users of the semver crate shouldn't automatically opt-in to these cases.
I'd be fine adding this specific logic to Cargo itself as opposed to semver.

Ah yes. let me prepare the real patch, I think this will work as you want it to.

#3154 was just merged. Closing!


Twitter Metadata field support

This PR Addresses #191 by adding additional Metadata Fields.  The Card type can be selected by dropdown.

Looks great! I'll take a better look & test it in the following days and let you know if I have any feedback. But really appreciate this PR and the other one that you did!

Thanks @patrickdemooij9  - let me know if I can be of assistance; really itching to get this released so we can use it on a couple of projects :)

Hi @robertjf
Great PR! Just spotted a few small things. If you want, I can also pick these up but I'll let that decision up to you. Really appreciate the work you do here!

hey @patrickdemooij9 let me know what they are, and I'll jump on them straight away :)

hey @patrickdemooij9 let me know what they are, and I'll jump on them straight away :)

You should be able to see them above our messages :)

hm.  Not seeing them at all..

@patrickdemooij9 are they marked as private by any chance?

Hmm, I don't see anything related to private in the mobile app. I'll take a look at it tomorrow in the browser. The feedback was:

I think the open graph URL should probably belong in the open graph group.
Let's put all the Twitter related meta fields in their own group between open graph and extra information.
Are you sure that product is a valid Twitter card type? I didn't see it listed in their documentation.
The Twitter card type dropdown should probably have an empty option. Currently, there is no way to "empty" your field and use the fallback value.

Hopefully I'll be able to get review points showing for you tomorrow.

great - I'll get to work on those in the meantime.

@patrickdemooij9 I'm about to push up some changes for you - I'm not 100% convinced that the twitter specific fields should be in their own group though; the twitter preview widget is still in the Open Graph group so it's a little disjointed.
Still, I do like the separation.  For Facebook I've also added  facebook app_id field as well, also in it's own group.
Perhaps we should call the group "Social Media" instead of "Open Graph" and keep it all together?

@robertjf You're right, the preview doesn't really fit then. I think a Social Media Group would be a great idea to do then!

ok, so if we rename the group from Open Graph to Social Media, would that work?  and consolidate the fields into that?

Yes, I think that is the way to go about it

all done :)

PR looks great! I've merged it and I will try to release it somewhere next week. Trying to get a few more changes added for the next version


Bugfix: Syntax incompatible with older versions of Matlab

Reported on the Brainstorm user forum (example file included):
https://neuroimage.usc.edu/forums/t/error-importing-reviewing-raw-meg-fif-files/26029/3
Fix on the Brainstorm repo:
https://github.com/brainstorm-tools/brainstorm3/commit/dfd4a6b7cf66a76d9ed09549947f3340156d77a9
I haven't tested with all versions of Matlab to see when this syntax was accepted. I only tried with 2009b and got the same error reported by our user.

thx @ftadel


WIP Minimal implementation of the LLC data manager

Mostly so that Subbu can review this

lgtm after changes suggested, unit tests can be separate.

Current coverage is 44.48% (diff: 0.00%)

Merging #361 into master will decrease coverage by 1.37%

@@             master       #361   diff @@
==========================================
  Files           709        658     -51
  Lines         33387      30610   -2777
  Methods           0          0
  Messages          0          0
  Branches       4995       4604    -391
==========================================
- Hits          15312      13618   -1694
+ Misses        16860      15902    -958
+ Partials       1215       1090    -125

Powered by Codecov. Last update e0824eb...48fb30c


(maint) Ensure projects can handle fedora without the f prefix

This commit removes the 'fedora-prefix' from the filename in acceptance tests.

CLA signed by all contributors.

Is this going to break testing puppet-agent on fedora, e.g. a recent build still has ...fedora-f25-x86_64.repo in the URL

@joshcooper The beaker updates to consume the .yaml for finding artifacts should make this not a problem, right?

@mwaggett I think methods were added to beaker-puppet, e.g. install_from_build_data_url, but puppet and related components haven't been modified to call the new methods. For example, puppet is still curling the repo directly:
01:37:06 * Install puppet-agent...
01:37:06   Fetching: http://builds.delivery.puppetlabs.net/puppet-agent/497793fff6251da6385f3758708c0f4e967e3bf8/repo_configs/rpm/pl-puppet-agent-497793fff6251da6385f3758708c0f4e967e3bf8-fedora-f26-x86_64.repo
01:37:06     and saving to tmp/repo_configs/fedora/pl-puppet-agent-497793fff6251da6385f3758708c0f4e967e3bf8-fedora-f26-x86_64.repo

Are those updates that could happen now?

We are working on an epic for beaker acceptance test workflow improvements. We'll need to switch over to using the puppet5 installation methods in beaker before we can merge this.

This will also break module pipelines (if we test against fedora?). See https://github.com/puppetlabs/beaker-puppet_install_helper/blob/master/lib/beaker/puppet_install_helper.rb#L95-L104, which ends up calling into beaker in https://github.com/puppetlabs/beaker/blob/7439f35a4e24fc910502f32a2d3bbd9f98f07278/lib/beaker/host/unix/file.rb#L77. The beaker-puppet_install_helper should be modified to call https://github.com/puppetlabs/beaker-puppet/blob/master/lib/beaker-puppet/install_utils/puppet5.rb#L148 as well. /cc @tphoney @DavidS

@joshcooper @pmcmaw @willmeek @DavidS  it doesnt look like we are testing against fedora in our modules pipelines at the minute. @pmcmaw is starting to look at using the metadata.json as the source of truth for modules testing. Currently he have a cherry picked list of OSes here https://github.com/puppetlabs/ci-job-configs/blob/master/resources/defaults/modules.yaml#L277-L426

@mwaggett all of puppet (component) CI should be using build data to install puppet agent and server packages. We'll also be moving all of the CI logic into beaker-puppet in @melissa's PR #6602. So I think this PR can be closed.


Add whackamole game

Thanks for this fantastic list! I would like to add a game I developed some time ago.

Thanks @tomicapretto!


Regarding queries on Aspera Connect SDK

Hi Team, I am trying Folder Upload using Aspera Connect SDK(using asperaweb-4.js) and have below queries, please help with them:
1- Does asperasdk create separate objects for each file during folder upload?
2- How do we do folder upload with exception to skip few files (folder path specified in paths property of transfer spec of starttransfer)?
For example, uploading folder D:/Test/abc, and want to skip uploading few files from the folder like /Test/abc/test1.jpg, /Test/abc/test2.jpg. We have file names or extensions of files to be skipped.
3- Is there any threshold in Folder upload for number of files that can be transferred within folder?
4- If we do upload, using multiple source paths mentioned in 'paths' property of TransferSpec for startTransfer (transfer multiple files in single transfer session), is there any threshold for number of paths that will be allowed for transfer?
ex of transfer spec:
{
"authentication": "password",
"cipher": "none",
"cookie": "...",
"create_dir": "False",
"destination_root": null,
"direction": "send",
"http_fallback": false,
"http_fallback_port": 0,
"lock_min_rate": false,
"lock_target_rate": false,
"min_rate_kbps": 5000,
"paths": [
{
"destination": "xyz.mov",
"source": "C:\\Users\\abc\\Downloads\\abc.mov"
},
{
"destination": "\\POC\\abc.mp3",
"source": "C:\\Users\\abc\\Downloads\\abc.mp3"
}],
"remote_host": "asperaHost",
"remote_user": "userAspera",
"resume_check": "full_checksum",
"ssh_port": 33001,
"tags": {
"aspera": {
"xfer_id": "...",
"xfer_retry": 90
}
},
"target_rate_kbps": 10000,
"uuid": "......"
}
5- What are the reasons for getting below error during multiple file upload in single transfer session:
"error_code": 63,
"error_desc": "Source path stat failed"
6- Is there a way to know from aspera transfer progress events, that which files failed to upload upfront? or we can know it by checking which files are not part of 'files' property in TransferInfo or bytes_written is not equal to bytes_expected, those would be failed?
TransferInfo:
"files": [
{
"bytes_expected": 1998617,
"bytes_written": 1998617,
"fasp_file_id": "..",
"file": "D:\Test files\flower.jpg"
},
{
"bytes_expected": 5518662,
"bytes_written": 5518662,
"fasp_file_id": "...",
"file": "D:\Test files\notification.pdf"
}]
7- In TransferInfo json, file_counts has 'failed' property. In which scenario does this property gets populated?
Would be grateful to receive any inputs on these. Thanks in advance.

Hi @AakankshaBhatia,

I'm not sure what you mean by separate objects for each file. When uploading a folder, each file within the folder will be uploaded as expected. If you are referring to the files array in the TransferInfo response then yes each file within the folder will be a separate object.
For example, if I'm uploading a folder named aspera-test-dir-tiny that has 2 files named 200KB.1 and 200KB.2 then at the end of the transfer I will have two elements in the files array - one for each file. Note that files that have not been active yet in this session will not be reported in files.

It's not documented, but you can try using TransferSpec.exclude_patterns to skip files from within the directory when uploading. exclude_patterns should be an array of strings where each pattern can be a file or directory name, or a set of names expressed with UNIX glob patterns.
For example, if I'm uploading a directory and I set exclude_patterns = ['*.jpg'] then Aspera Connect will upload the directory but skip all the files with jpg as the file extension from within that directory.

I am not aware of any threshold.

I am not aware of any threshold.

That error seems to indicate that one of the source paths you specified does not exist. More detailed information can probably be found in the transfer logs (i.e. aspera-scp-transfer.log).

Yes, I believe the file that failed should contain an error object field with code and description fields.

The failed field in file_counts just reflects the number of files that had errors during the transfer - it's fairly generic it seems.

Hi @dwosk ,
Thanks a lot for the reply. Answer to point (2) helped me. I am able to exclude files when I do folder upload. But wanted to enquire if there is any limit on the number of filenames that can be mentioned in this array?
Also, please find below clarification for other points:
1- By separate objects I meant, during folder upload, internally in aspera code, are separate objects created for each file? I am asking this question because I saw a point in this link (https://www.ibm.com/support/pages/how-identify-root-cause-slow-transfer) "It is expected to see low Transfer Speed for many(thousands) small files(less than 1Mb). In such cases, it takes more time to initiate a transfer of each file, create a file object and close it, rather than the actual transfer of the data. "

5- Below are some type of errors/Info I got in transfer logs:

User aborted session
ERR Unhandled OS error code 10022
ERR Unrecognized fasp error 656801859 - generate management ERR_UNDEFINED
ERR fasp_sock_send() failed, err:10022, len:46
ERR FASP sender had error, errcode 656801859 errstr []
Sender has not received a packet for 3 seconds!
LOG Receiver has not received a packet for 2 seconds!
If there is no UDP traffic for 60 seconds the transfer fails and must be restarted.
DBG source_work: Out of while loop!

Some were due to connection issue but some errors came even when connection was fine at my end during testing upload of large number of files, in single session. If you have any more information on these errors, then please share.
6- I Agree, this will happen if any 1 file fails, and error object with code and description will come for that. But we cant know which all files are not transferred without checking Files Property, I think. Is that right?
And is this true that , if 1 file transfer fails and is not retry able by aspera, then aspera transfer wont proceed further for non-transferred files?
Sample transfer info:
[
{
"add_time": "2023-05-25T17:37:26",
"aspera_connect_settings": {..},
"bytes_expected":<PHONE_NUMBER>,
"bytes_written":<PHONE_NUMBER>,
"calculated_rate_kbps": 7220,
"current_file": "D:/Test Assets/abc.mov",
"elapsed_usec":<PHONE_NUMBER>,
"end_time": "2023-05-25T19:12:28",
"error_code": 63,
"error_desc": "Source path stat failed",
"explorer_path": "D:\Test Assets\xyz.mp4",
"file_counts": {
"attempted": 264,
"completed": 264,
"failed": 0,
"skipped": 0
},
"files": [
{
"bytes_expected": 7476442,
"bytes_written": 7476442,
"fasp_file_id": "26b9.......",
"file": "D:\Test Assets\aaa.m4v"
},....
],
"lock_min_rate": false,
"lock_rate_policy": false,
"lock_target_rate": false,
"min_rate_kbps": 0,
"modify_time": "2023-05-25T19:12:28",
"percentage": 0.97333,
"previous_status": "running",
"rate_policy": "fair",
"rate_policy_allowed": "fixed",
"remaining_usec": 155000000,
"start_time": "2023-05-25T17:37:26",
"status": "failed",
"target_rate_cap_kbps": 0,
"target_rate_kbps": 10000,
"title": "xyz.mp4 (+283)",
"transfer_iteration_token": 6379,
"transfer_spec": {
"destination_root": "upload_folder",
"direction": "send",
"paths": [
{
"destination": "xyz.mp4",
"source": "D:\Test Assets\xyz.mp4"
},
{
"destination": "abc.mov",
"source": "D:\Test Assets\abc.mov"
},..........
],
"remote_host": "asperahost",
"remote_user": "asperauser",
"tags": {
"aspera": {
"xfer_id": "26b9...",
"xfer_retry": 90
}
},
"uuid": "26b9..."
},
"transport": "fasp",
"uuid": "26b9..."
}
]
7- The failed field in file_counts never updated when I tried multiple file uploads and there were failures. So, I am thinking in what scenarios will this property 'failed' get updated.

I'm not aware of any limit to the number of paths specified.

In that case, yes, uploading a folder with many small file sizes would encounter this transfer speed issue.

Those errors seem like connection related errors - doesn't necessarily seem related to the source stat failed error.

Yes, if you want this granularity of details about the transfer error, you'll need to inspect the files property of the TransferInfo response. On the app side, if Connect determines the error renders the transfer non-retryable then the transfer will not be retried and the remaining files will not be transferred.

Connect populates the file_counts field from the responses it gets from the ascp executable that actually does the transfer. Hard to say in what scenarios Connect would not get a failed field increment even though the transfer failed.

Thanks for the answers