Intermittent preconditionFailure when building documentation for multiple modules in one docc convert call.

Description
I've been using the experimental --analyze feature for several months, and periodically it has been failing without any additional details - just a trap:
3430 Trace/BPT trap: 5       $(xcrun --find docc) convert Sources/SwiftVizScale/Documentation.docc --analyze --fallback-display-name SwiftVizScale --fallback-bundle-identifier com.github.swiftviz.SwiftVizScale --fallback-bundle-version 0.1.9 --additional-symbol-graph-dir .build/symbol-graphs --experimental-documentation-coverage --level brief

Checklist

[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
report brief synopsis of the state of coverage for the documentation catalog in the project.
Actual behavior
3430 Trace/BPT trap: 5       $(xcrun --find docc) convert Sources/SwiftVizScale/Documentation.docc --analyze --fallback-display-name SwiftVizScale --fallback-bundle-identifier com.github.swiftviz.SwiftVizScale --fallback-bundle-version 0.1.9 --additional-symbol-graph-dir .build/symbol-graphs --experimental-documentation-coverage --level brief

Steps To Reproduce

clone repo (public): git clone https://github.com/swiftviz/scale.git
cd scale
git checkout cc39b0a8becc14c471ebf857e825de4af997433c
./docreport.bash

Swift-DocC Version Information
d56e5a991991528c8396c0c6175ec8ee97e2bd6e
Swift Compiler Version Information
swift-driver version: 1.62.1 Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.7 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx12.0

I've compiled a local copy of docc from the main branch and run this under LLDB from the command line to get more details:
DOCC_HTML_DIR=/Applications/Xcode-beta4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/docc/render
# version is hardened, so I can't attach with the debugger to see what's happened
# DOCC=/Applications/Xcode-beta4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/docc

# built from source: d56e5a991991528c8396c0c6175ec8ee97e2bd6e (main branch)
DOCC=/Users/heckj/src/swift-project/swift-docc/.build/debug/docc

lldb $DOCC -- convert Sources/SwiftVizScale/Documentation.docc \
    --analyze \
    --fallback-display-name SwiftVizScale \
    --fallback-bundle-identifier com.github.swiftviz.SwiftVizScale \
    --fallback-bundle-version 0.1.9 \
    --additional-symbol-graph-dir .build/symbol-graphs \
    --experimental-documentation-coverage \
    --level brief

The error reported under LLDB was more informative:
SwiftDocC/DocumentationContext.swift:2236: Fatal error: Reference does not have an associated documentation node.
2022-07-30 10:30:21.533841-0700 docc[94104:3221654] SwiftDocC/DocumentationContext.swift:2236: Fatal error: Reference does not have an associated documentation node.
Process 94104 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = Fatal error: Reference does not have an associated documentation node.
    frame #0: 0x00000001b424132c libswiftCore.dylib`_swift_runtime_on_report
libswiftCore.dylib`:
->  0x1b424132c <+0>: ret

libswiftCore.dylib`:
    0x1b4241330 <+0>: b      0x1b424132c               ; _swift_runtime_on_report

libswiftCore.dylib`:
    0x1b4241334 <+0>: adrp   x8, 299488
    0x1b4241338 <+4>: ldrb   w0, [x8, #0x23c]
Target 0: (docc) stopped.

(referencing DocumentationContext.swift, line 2236)
I set a breakpoint to inspect the fragment:
breakpoint set --file DocumentationContext.swift --line 2233
run
fr v reference

And it's showing a fragment, with an available language, from a dependency of this library:
(SwiftDocC.ResolvedTopicReference) reference = {
  _storage = 0x0000600002cdb300 {
    bundleIdentifier = "com.github.swiftviz.SwiftVizScale"
    path = "/documentation/Numerics/AlgebraicField//(_:_:)-9bcy2"
    fragment = nil
    sourceLanguages = 1 value {
      [0] = {
        name = "Swift"
        id = "swift"
        idAliases = 0 values {}
        linkDisambiguationID = "swift"
      }
    }
    identifierPathAndFragment = "com.github.swiftviz.SwiftVizScale/documentation/Numerics/AlgebraicField//(_:_:)-9bcy2"
    url = "doc://com.github.swiftviz.SwiftVizScale/documentation/Numerics/AlgebraicField//(_:_:)-9bcy2"
    pathComponents = 5 values {
      [0] = "/"
      [1] = "documentation"
      [2] = "Numerics"
      [3] = "AlgebraicField"
      [4] = "(_:_:)-9bcy2"
    }
    absoluteString = "doc://com.github.swiftviz.SwiftVizScale/documentation/Numerics/AlgebraicField//(_:_:)-9bcy2"
  }
}

I looked briefly at what the error throwing method call (func entity(with reference: ResolvedTopicReference) throws -> DocumentationNode) does, and it looks like it's trying to look up a relevant DocumentationNode from a cache - only there's not going to be anything cached there for me (local build) since I don't have any external resolvers, and as far as I know - the dependency documentation isn't being built either.
I'm not sure of the context in the code of how we got here, or the overall flow of what's happening in these sources - but hoped this additional information would make it easier to highlight what could or should be resolved so that this experimental feature could be more stable.

git checkout cc39b0a8becc14c471ebf857e825de4af997433c

git checkout cc39b0a8becc14c471ebf857e825de4af997433c
fatal reference is not a tree：cc39b0a8becc14c471ebf857e825de4af997433c

@heckj  Could you please provide a branch for this commit?

Absolutely @Kyle-Ye - I made a branch analyze_error from that commit and pushed it up just now.
The command git clone https://github.com/swiftviz/scale -b analyze_error
should clone the repo and get you to that specific commit in one command.

I'm doing a bit more debugging on this, and realized I should have included the backtrace (bt) earlier in order to make sure of how we got to hitting the failed assertion:

* thread #1, queue = 'com.apple.main-thread', stop reason = Fatal error: Reference does not have an associated documentation node.
  * frame #0: 0x00000001b424132c libswiftCore.dylib`_swift_runtime_on_report
    frame #1: 0x00000001b42d68d8 libswiftCore.dylib`_swift_stdlib_reportFatalErrorInFile + 208
    frame #2: 0x00000001b3ef9424 libswiftCore.dylib`Swift._assertionFailure(_: Swift.StaticString, _: Swift.String, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never + 304
    frame #3: 0x00000001007951d0 docc`DocumentationContext.sourceLanguages(reference=SwiftDocC.ResolvedTopicReference @ 0x000000016fdf1838, self=0x0000000102705600) at DocumentationContext.swift:2236:13
    frame #4: 0x00000001007f735c docc`closure #1 in static GeneratedDocumentationTopics.createCollectionNode(identifier=SwiftDocC.ResolvedTopicReference @ 0x000000016fdf1888, context=0x0000000102705600) at GeneratedDocumentationTopics.swift:106:92
    frame #5: 0x00000001007f94e8 docc`partial apply for closure #1 in static GeneratedDocumentationTopics.createCollectionNode(parent:title:identifiers:context:bundle:) at <compiler-generated>:0
    frame #6: 0x00000001b4075d20 libswiftCore.dylib`Swift.Sequence.flatMap<τ_0_0 where τ_1_0: Swift.Sequence>((τ_0_0.Element) throws -> τ_1_0) throws -> Swift.Array<τ_1_0.Element> + 864
    frame #7: 0x00000001007f57dc docc`static GeneratedDocumentationTopics.createCollectionNode(parent=SwiftDocC.ResolvedTopicReference @ 0x000000016fdf32b0, title="Equatable Implementations", identifiers=3 values, context=0x0000000102705600, bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf8490, self=SwiftDocC.GeneratedDocumentationTopics) at GeneratedDocumentationTopics.swift:106:60
    frame #8: 0x00000001007f8bdc docc`static GeneratedDocumentationTopics.createInheritedSymbolsAPICollections(relationships=1603 values, context=0x0000000102705600, bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf8490, self=SwiftDocC.GeneratedDocumentationTopics) at GeneratedDocumentationTopics.swift:266:21
    frame #9: 0x00000001007817b4 docc`closure #1 in DocumentationContext.registerSymbols(bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf8490, documentationCacheBasedLinkResolver=0x0000600000c01830, symbolGraphLoader=SwiftDocC.SymbolGraphLoader @ 0x000000016fdf8550, self=0x0000000102705600) at DocumentationContext.swift:1272:46
    frame #10: 0x00000001007a0480 docc`partial apply for closure #1 in DocumentationContext.registerSymbols(from:symbolGraphLoader:) at <compiler-generated>:0
    frame #11: 0x00000001bb966ad4 libswiftObjectiveC.dylib`ObjectiveC.autoreleasepool<τ_0_0>(invoking: () throws -> τ_0_0) throws -> τ_0_0 + 64
    frame #12: 0x000000010077e5f8 docc`DocumentationContext.registerSymbols(bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf95d0, symbolGraphLoader=SwiftDocC.SymbolGraphLoader @ 0x000000016fdf8880, self=0x0000000102705600) at DocumentationContext.swift:1098:20
    frame #13: 0x000000010078c718 docc`DocumentationContext.register(bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf95d0, self=0x0000000102705600) at DocumentationContext.swift:1867:59
    frame #14: 0x000000010076c134 docc`closure #1 in DocumentationContext.dataProvider(bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf95d0, self=0x0000000102705600) at DocumentationContext.swift:315:22
    frame #15: 0x000000010078db50 docc`partial apply for closure #1 in DocumentationContext.dataProvider(_:didAddBundle:) at <compiler-generated>:0
    frame #16: 0x0000000100629a90 docc`benchmark<E, Result>(event=0x10076c01c, log=0x0000600002108640, body=0x10078db34) at Benchmark.swift:135:20
    frame #17: 0x000000010076bfa8 docc`DocumentationContext.dataProvider(dataProvider=0x0000600001705780, bundle=SwiftDocC.DocumentationBundle @ 0x000000016fdf9940, self=0x0000000102705600) at DocumentationContext.swift:311:13
    frame #18: 0x000000010079964c docc`protocol witness for DocumentationContextDataProviderDelegate.dataProvider(_:didAddBundle:) in conformance DocumentationContext at <compiler-generated>:0
    frame #19: 0x00000001008340d4 docc`DocumentationWorkspace.registerProvider(provider=SwiftDocC.LocalFileSystemDataProvider @ 0x0000600001700b90, options=SwiftDocC.BundleDiscoveryOptions @ 0x000000016fdf9dc0, self=0x0000600001705780) at DocumentationWorkspace.swift:123:27
    frame #20: 0x00000001007a99c8 docc`DocumentationConverter.convert<OutputConsumer>(outputConsumer=SwiftDocCUtilities.ConvertFileWritingConsumer @ 0x000000016fdfda10, self=SwiftDocC.DocumentationConverter @ 0x000000016fdfea18) at DocumentationConverter.swift:207:23
    frame #21: 0x0000000100af1754 docc`ConvertAction.perform(logHandle=standardOutput, self=SwiftDocCUtilities.ConvertAction @ 0x000000016fdfe910) at ConvertAction.swift:369:68
    frame #22: 0x0000000100af43bc docc`protocol witness for Action.perform(logHandle:) in conformance ConvertAction at <compiler-generated>:0
    frame #23: 0x0000000100b1e834 docc`Action.performAndHandleResult(self=SwiftDocCUtilities.ConvertAction @ 0x000000016fdfe910) at Action+performAndHandleResult.swift:25:26
    frame #24: 0x0000000100b4c230 docc`Docc.Convert.run(self=SwiftDocCUtilities.Docc.Convert @ 0x00000001026054b0) at Convert.swift:338:31
    frame #25: 0x0000000100b506e0 docc`protocol witness for ParsableCommand.run() in conformance Docc.Convert at <compiler-generated>:0
    frame #26: 0x0000000100042224 docc`static ParsableCommand.main(arguments=nil, self=SwiftDocCUtilities.Docc) at ParsableCommand.swift:97:19
    frame #27: 0x000000010004233c docc`static ParsableCommand.main(self=SwiftDocCUtilities.Docc) at ParsableCommand.swift:107:10
    frame #28: 0x0000000100c49c8c docc`docc_main at main.swift:14:6
    frame #29: 0x000000010238508c dyld`start + 520

On main I can reproduce the same preconditionFailure even if I remove the --analyze and --experimental-documentation-coverage --level brief flags, so we can rule those out.

I could not reproduce it under Swift 5.6 toolchain (The default toolchain bundled by Xcode 13.4)
Although the result is a little strange.
➜  scale git:(analyze_error) $(xcrun --find docc) convert Sources/SwiftVizScale/Documentation.docc --analyze --fallback-display-name SwiftVizScale --fallback-bundle-identifier com.github.swiftviz.SwiftVizScale --fallback-bundle-version 0.1.9 --additional-symbol-graph-dir .build/symbol-graphs --experimental-documentation-coverage --level brief
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Scale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/DomainDataTransform.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/NiceValue.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Tick.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorInterpolator.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/DiscreteScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/LCH.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ComputedRGBInterpolator.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_Cyclical.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/IndexedColorInterpolator.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/LCHColorInterpolator.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ConvertibleToDouble.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Band.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/SequentialScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ReversibleScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/BandScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_SequentialSingleHue.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/PointScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ContinuousScale.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_Diverging.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_SequentialMultiHue.md:1:1: note: This document does not have an abstract.
An abstract provides a short description of the document. Write a paragraph below the title of the document to use it as an abstract.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/PointScale.md:1:3: note: No symbol matched 'SwiftVizScale/PointScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ComputedRGBInterpolator.md:1:3: note: No symbol matched 'SwiftVizScale/ComputedRGBInterpolator'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/IndexedColorInterpolator.md:1:3: note: No symbol matched 'SwiftVizScale/IndexedColorInterpolator'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/NiceValue.md:1:3: note: No symbol matched 'SwiftVizScale/NiceValue'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/BandScale.md:1:3: note: No symbol matched 'SwiftVizScale/BandScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/SequentialScale.md:1:3: note: No symbol matched 'SwiftVizScale/SequentialScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_SequentialMultiHue.md:1:3: note: No symbol matched 'SwiftVizScale/ColorScheme/SequentialMultiHue'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme.md:1:3: note: No symbol matched 'SwiftVizScale/ColorScheme'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Tick.md:1:3: note: No symbol matched 'SwiftVizScale/Tick'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_Cyclical.md:1:3: note: No symbol matched 'SwiftVizScale/ColorScheme/Cyclical'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/LCHColorInterpolator.md:1:3: note: No symbol matched 'SwiftVizScale/LCHColorInterpolator'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ReversibleScale.md:1:3: note: No symbol matched 'SwiftVizScale/ReversibleScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/LCH.md:1:3: note: No symbol matched 'SwiftVizScale/LCH'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ConvertibleToDouble.md:1:3: note: No symbol matched 'SwiftVizScale/ConvertibleWithDouble'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Documentation.md:1:3: note: No symbol matched 'SwiftVizScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_SequentialSingleHue.md:1:3: note: No symbol matched 'SwiftVizScale/ColorScheme/SequentialSingleHue'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ContinuousScale.md:1:3: note: No symbol matched 'SwiftVizScale/ContinuousScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/DomainDataTransform.md:1:3: note: No symbol matched 'SwiftVizScale/DomainDataTransform'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorInterpolator.md:1:3: note: No symbol matched 'SwiftVizScale/ColorInterpolator'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/ColorScheme_Diverging.md:1:3: note: No symbol matched 'SwiftVizScale/ColorScheme/Diverging'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/DiscreteScale.md:1:3: note: No symbol matched 'SwiftVizScale/DiscreteScale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Band.md:1:3: note: No symbol matched 'SwiftVizScale/Band'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/Scale.md:1:3: note: No symbol matched 'SwiftVizScale/Scale'. This documentation will be ignored.
/Users/kyle/Workspace/Github/swift-docc-project/scale/Sources/SwiftVizScale/Documentation.docc/MakingAndUsingScales.md: note: You haven't curated 'doc://com.github.swiftviz.SwiftVizScale/documentation/SwiftVizScale/MakingAndUsingScales'
   --- Experimental coverage output enabled. ---
                | Abstract        | Curated         | Code Listing
Types           | (0/0)           | (0/0)           | (0/0)
Members         | (0/0)           | (0/0)           | (0/0)
Globals         | (0/0)           | (0/0)           | (0/0)

It's understandable that this wouldn't reproduce in the 5.6 toolchain. The sourceLanguages(for:) function that has this precondition is part of the multi-language feature that was added in the 5.7 release.
Like @franklinsch pointed out in the Forums topic this build setup is providing symbol graph files for multiple modules to DocC which isn't officially supported. This means that DocC is treats all 7 modules as a single unit and computes the documentation coverage for both SwiftVizScale and its dependencies (Collections, ComplexModule, DequeModule, Numerics, OrderedCollection, and RealModule) as one unit.
Passing only the SwiftVizScale symbol graph files produces the coverage information for only that module (see for example that there are 188 members instead of 1108):
   --- Experimental coverage output enabled. ---
                | Abstract        | Curated         | Code Listing
Types           | 100% (29/29)    | 100% (29/29)    | 0.0% (0/29)
Members         | 95% (178/188)   | 89% (167/188)   | 0.0% (0/188)
Globals         | 7.7% (1/13)     | 100% (13/13)    | 0.0% (0/13)

Building documentation for only SwiftVizScale will avoid this precondition failure and it will output the coverage information that I think you're looking for.
I'll update the title of this issue to reflect the cause of the crash.

@d-ronnqvist Thank you!! I was just following up and finding that the main branch also hit that precondition, and didn't know about (or understand) the constraint that I should only be providing the symbol graph files for the specific target I was after. I'd erroneously thought that it only grabbed what it needed, but in hind sight it becomes clear these older docc convert commands don't use --target which narrows it down to the specific symbol graph, and which I'd become used to seeing with the docc-plugin scripts.
Thank you, this gives me a much easier way to work around things and get reporting!

Since this was using the experimental coverage feature it's probably the same issue that was fixed by https://github.com/apple/swift-docc/issues/697.
Feel free to reopen this issue, or open a new one, if this crash continues to happen.


Remove playground

I believe it's no longer necessary to have it. We used to use this to experiment with micro API (Finch in Action).

Removed in #323.


[AutoPR compute/resource-manager] Added Examples and Updated Comments for SKU and Computer APIs in the swagger

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6294

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5044


error code 500 and error code langur

i get these errors after while and when im using multiple accounts at once

Hello,
The 500 error code is not a problem, it is coming from the shitty servers hosting the farm stats.
Also, I saw that 'Langur' error code but I don't know what error it does refer to. I'll do some research for a future update.
Hope this helps.

So after studying the update of the get-tickets page, it seems that the 'Langur' error code means that 'we can't add tickets because you haven't waited enough'. This is not a serious bug here, but i know these popups are kind of annoying, even more if you don't know what is the error.
I'll fix this in the next update.

thanks nice work by the way:)

If you want to, I could host your farm stats stuff on my dedicated server.

Hi shock2provide,
I'm interested into your proposition. All I need is a Web Server supporting HTTPS and PHP5. Feel free to contact me by email : Jordan.Demaison @gmail.com
Thanks.


feat: [TSI-2083] enable format_options argument for java-client

Assumptions
Some assumptions made while working on the PR:

format_options argument will be key-value based map with values mostly being of primitive types
Initially explored the possibility of using params with style deepObject and explode: true option as suggested here as a fix but subsquently wasn't able to find appropriate mustache directive to determine if the param has any of these attributes (deepObject, explode: true) which led to adding a fix by checking if input is of the type Map and if yes, manually convert it to key value based Pair objects.

Problem Statement
Phrase API accepts format_options argument on locales download endpoint.
For java-client the format_option argument was not being properly parsed and embedded in the query params resulting in a request url like below
https://api.phrase.com/v2/projects/e4c0450ccc8dcc087fac8351ecc89eb6/locales/01877decc84124a75fdd0a4fc147d8de/download?file_format=properties&tags=menu&format_options=%7B%22omit_separator_space%22%3Atrue%7D&encoding=UTF-8

Solution
This pull requests adds the ability to parse any query params of type map and embed them to the URL's query string as proper key value pairs resulting in request URLs like:
localhost:3000/api/v2/projects/:project_id/locales/:id/download?file_format=i18next_4&format_options%5Bnesting%5D=false

@hahmed-dev is this still valid?

@docstun yes, we initially were waiting to merge the open api version bump PR since its based out of that, but we discussed last week, there is no dependency and we can merge this independently as well. I will try and shortly open a new PR and if that gets merged close this one.


API section is out of screen

This is on my MacBook Pro 14":

Many thanks for the issue! I've fixed it now 🤓


fix(404): redirect to dashboard page

Issues
#102
Fixes #
add redirect to /
Changes
add vercel.json config file
How to test

Open some not existing pages, e.g. https://snapshot.org/sialala (use your own domain)
Vercel shouldn't show 404 and just show a dashboard (unfortunately the link will be https://snapshot.org/sialala/#/

To-Do

[ ]

Self-review checklist

[ ] I have performed a full self-review of my changes
[ ] I have tested my changes on a preview deployment
[ ] I have tested my changes on different screen sizes (sm, md)
[ ] I have tested my changes on a custom domain

Additional notes or considerations
(Include any other relevant information or context that may be helpful for the reviewer)

@Todmy nice one I needed this for Tune histoire too


404 On files through nginx reverse proxy running code-server in a docker container

Hello, I have installed code-server. It worked previously, but it has stopped working.
This is what I see in Firefox:

This is my nginx reverse proxy setup:
server {
    listen      <IP_ADDRESS>:80;
    server_name coder.diademiemi.me;

    location / {
        rewrite ^ https://$host$request_uri? permanent;
    }
}

server {
        server_name coder.diademiemi.me;
        listen <IP_ADDRESS>:443;
        ssl on;
        ssl_certificate /etc/letsencrypt/live/diademiemi.me-0005/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/diademiemi.me-0005/privkey.pem;

        location / {
        proxy_pass http://<IP_ADDRESS>:8080;

        proxy_set_header Host $host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection upgrade;
        proxy_set_header Accept-Encoding gzip;
        }
}

This is what I use to start code-server:
docker run -d -it --name code-server --restart always --ip <IP_ADDRESS> -p 8080:8080 --env-file coder.env -v "/srv/coder:/home/coder/host" -v "/home/coder/:/home/coder/" codercom/code-server \
 --disable-telemetry \
docker exec -it code-server sudo /usr/bin/apt -y update
docker exec -it code-server sudo /usr/bin/apt -y update --fix-missing
docker exec -it code-server sudo /usr/bin/apt -y install cmake default-jre python3 python3-pip nodejs zsh git

Is this a bug? How can I fix this? it used to work

Hm weird. It worked on previous versions?
Can you try clearing your cache?

I don't think I updated anything in this time. Maybe I did and forgot though.
I have cleared cache, tried other devices as well. Didn't help. I just tried and it also does not work on Chromium

Also, this happens after I log in, the login page loads fine.

I'm no expert with nginx (so bear with me), but it seems maybe nested paths are failing to load?

That's odd; those files don't exist in the production build (they get
bundled into the larger workbench files).

It loads fine when just accessing it normally, but once I try to access it via a nginx as a reverse proxy (which would be preferred greatly because of easy HTTPS and a subdomain) it does this. Is there anything I can try to fix this?

It might be worth trying out the 3.0.0 Docker tag to see if that helps at all. I'm not sure what it could be if it works directly but not through the proxy except for the browser cache, but you mentioned you already cleared that.

Following on #1428, I tried v3.0.1 and I'm having the same issue. For some reason, code-server will add parent dir to path which I suspect to be the issue. For instance if I access http://localhost/my-project/, I get:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <meta
      name="viewport"
      content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no"
    />
    <meta http-equiv="Content-Security-Policy" content="style-src 'self'; manifest-src 'self'; img-src 'self' data:;" />
    <title>404 - code-server</title>
    <link rel="icon" href="./../static/0b9a478289e6f15c2ab1f9345e3ece7b2eb29180/src/browser/media/favicon.ico" type="image/x-icon" />
    <link
      rel="manifest"
      href="./../static/0b9a478289e6f15c2ab1f9345e3ece7b2eb29180/src/browser/media/manifest.json"
      crossorigin="use-credentials"
    />
    <link rel="apple-touch-icon" href="./../static/0b9a478289e6f15c2ab1f9345e3ece7b2eb29180/src/browser/media/code-server.png" />
    <link href="./../static/0b9a478289e6f15c2ab1f9345e3ece7b2eb29180/dist/pages/app.css" rel="stylesheet" />
    <meta id="coder-options" data-settings='{"base":"./..","commit":"0b9a478289e6f15c2ab1f9345e3ece7b2eb29180","logLevel":2}' />

404

          Not found

          go home

Ohhh, I think I see what's going on. code-server makes all requests
against the base, so if you need the requests to go against some other
path then you'll need to rewrite the URL.
For nginx I think adding a trailing slash on proxy_pass should do it.
For example: proxy_pass http://localhost:8080/;.

@code-asher, yup! I can confirm this works. And, I thought I have tested all the possible combinations reverse proxy settings in nginx. Thanks a lot!

🎉

I have the trailing slash already within my NGINX config file
proxy_pass http://<IP_ADDRESS>:8080/;
But I'm having the same issue with vscode-remote-resource
https://dev.mydomain.com/vscode-remote-resource?path=%5Cusr%5Clib%5Ccode-server%5Clib%5Cvscode%5Cextensions%5Ctheme-seti%5Cicons%5Cseti.woff&tkn=

Everything was working fine on version 3.2.0.
This is on 3.3.0.

See #1642


Acrolinx quality improvements: Walkthrough-Guide--Manage-Risk-with-Ad…

…ditional-Multi-Factor-Authentication-for-Sensitive-Applications.md

@robinharwood, @Xelu86
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


left sidebar: "Compose" in stream actions popover prefills topic.

To replicate:

Narrow to a topic T in stream X
Go to stream actions popover for stream Y, and click "Compose a message to stream Y"

It will prefill the topic of the new message with T.

@zulipbot  claim


Constant 404's related to minting/annual-provisions

I see repeated ongoing attempts to access the following on the console:
http://...:1317/minting/annual-provisions
I suspect this is because I do not have minting turned on. But I should not have to have it on.
Maybe a config parameter, or something? Would be nice to have this removed from the console output so it is "cleaner"?

I think this is the same issue as #319 ?

Close as duplicates


Update AppVeyor configuration.

Use yarn
Use Node 6 (we test node 4, 6, and 7 in Travis so just using 6 here for AppVeyor)

superseded by #10


External 2D Engine

Dear Staff,
what about if i import .a lib for a 2D engine? ...
Do you think it could work if the lib has all framework it need to run inside iOS?
I think there must be no error.
Anyway i will test much and i will update you all if interested in this question.
Not a real issue, but is very important for me as game developer.

@xGEKKOx since winobjc is a source code solution, the lib you are including must be compiled for windows.  If it is an OBJC library, it needs to be recompiled with winobjc. Closing this issue as this is more of a question.


Restore finish scope in hclib_future_wait

Closes #27.

Good catch. Interesting that we haven't had a test catch this yet.


VIZ/MINOR: use bootstrap for GFP CI for plot_compare_evokeds

plot_compare_evokeds will calculate an analytic CI for channels, but as the GFP isn't normally distributed, I decided against calculating the CI. (Actually, isn't grad RMS also not normally distributed at all ..?)
@dengemann just contributed a helper function for bootstrapped CIs for GFP, which should be added to the plot_compare_evokeds code.
Maybe it should always be used? Or maybe just for GFP and RMS.

Jona can you play with it a bit? We might want to generalize it and add it
to mne.stats.
On Tue, Apr 4, 2017 at 2:13 AM jona-sassenhagen<EMAIL_ADDRESS>wrote:

plot_compare_evokeds will calculate an analytic CI for channels, but as
the GFP isn't normally distributed, I decided against calculating the CI.
(Actually, isn't grad RMS also not normally distributed at all ..?)
@dengemann https://github.com/dengemann just contributed a helper
function for bootstrapped CIs for GFP, which should be added to the
plot_compare_evokeds code.
Maybe it should always be used? Or maybe just for GFP and RMS.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/4159, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fihKKf1U5rHo9662q79J0QMWgDj28ks5rsd-hgaJpZM4MybUq
.

For highly skewed distributions one way would be to fit gamma distribution and estimate ci from gamma. A simpler approach is to calculate one-sided sd's (this is what is being done in ica's plot_properties here. But bootstrapping is also good if it's fast - it would be good to have it in stats.

Hm. I'm okay with either. @dengemann , opinions?
I guess the bootstrap is more robust, the gamma might be more effective and efficient.
We could easily give the option to pass a function to ci, but it should default to something sensible otherwise. (The question is, should it pick gamma/bootstrap only for RMS/GFP, or should it do some basic check (are all values positive?), or should it always bootstrap, ..?)

Bootstrap or one-sided std are safer, scipys gamma sometimes does bad fits unless loc is frozen or good starting parameters are given. And while bootstrap and one-sided sd will work both on gaussian and skewed, gamma requires the distribution to be skewed (although it approaches gaussian with increasing shape param).

Ok you convince me to write tests and open a pr for a generalized bootstrap
function. Bootstrap is cool as it makes almost no assumptions and can be
used with any statistic.
On Thu, Apr 6, 2017 at 8:30 AM Mikolaj Magnuski<EMAIL_ADDRESS>wrote:

Bootstrap or one-sided std are safer, scipys gamma sometimes does bad fits
unless loc is frozen or good starting parameters are given. And while
bootstrap and one-sided sd will work both on gaussian and skewed, gamma
requires the distribution to be skewed (although it approaches gaussian
with increasing shape param).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/4159#issuecomment-292158831,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fin-TBIGmzR1d2pN2ahmbPeylGJe_ks5rtNrXgaJpZM4MybUq
.

Do we have any synergy with the other stats functions? (Which also use resampling.) Maybe we can keep actual overhead low.

I think this is pretty independent and adds no overhead.
On Thu, Apr 6, 2017 at 8:50 AM jona-sassenhagen<EMAIL_ADDRESS>wrote:

Do we have any synergy with the other stats functions? (Which also use
resampling.) Maybe we can keep actual overhead low.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/4159#issuecomment-292164250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fikFABYZ_7p4kJd399PzBbRmNjgvqks5rtN-bgaJpZM4MybUq
.

That's why you find it in an example :)
On Thu, Apr 6, 2017 at 9:01 AM Denis-Alexander Engemann <
<EMAIL_ADDRESS>wrote:

I think this is pretty independent and adds no overhead.
On Thu, Apr 6, 2017 at 8:50 AM jona-sassenhagen<EMAIL_ADDRESS>wrote:
Do we have any synergy with the other stats functions? (Which also use
resampling.) Maybe we can keep actual overhead low.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/4159#issuecomment-292164250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fikFABYZ_7p4kJd399PzBbRmNjgvqks5rtN-bgaJpZM4MybUq
.

Done in #4289


Word Scrabble Game Extension

Word Scrabble Game Browser Extension is a sleek and interactive tool that brings the fun of word scrabble directly to your web browser. Perfect for casual play or enhancing your vocabulary, this extension offers a seamless and customizable gaming experience.
Features:
User-Friendly Interface: Clean, visually appealing design with an easy-to-navigate scrabble board and tile set.
Responsive Design: Adapts to all screen sizes, ensuring a consistent experience on any device.
Offline Mode: Enjoy scrabble games without needing an internet connection.

Already added to my repository #240. Closing this


docker-compose spaces

Sail Version: any
Laravel Version: any
PHP Version: any
OS: any

Description:
In .editorconfig file of laravel/sail and laravel/laravel exists line:
[*.{yml,yaml}]
indent_size = 2

But sail's yaml stubs has 4 spaces.
Suggest fix spaces in stubs or append to laravel/laravel .editorconfig line:
[docker-compose.yml]
indent_size = 4

Steps To Reproduce:
Not relevant

Feel free to attempt a PR, thanks.

@driesvints, it's suggest with two way to resolve and I want discuss them before create PR to sail or laravel skeleton

We use two spaces everywhere normally.


For a 2.1.0 release

#143

Codecov Report

Merging #144 (3f83bd7) into master (e72b6c8) will decrease coverage by 2.65%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #144      +/-   ##
==========================================
- Coverage   96.85%   94.19%   -2.66%
==========================================
  Files           7        7
  Lines         286      293       +7
==========================================
- Hits          277      276       -1
- Misses          9       17       +8

Impacted Files
Coverage Δ

src/ScientificTypes.jl
100.00% <ø> (ø)

src/convention/scitype.jl
78.37% <0.00%> (-18.29%)
:arrow_down:

src/schema.jl
97.14% <0.00%> (-2.86%)
:arrow_down:

Continue to review full report at Codecov.

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

Here's the doc fail log:

I cannot make sense of this, as ScienticTypesBase v2.1 was release 3 days ago, and is found by the other parts of CI.
Merging this now anyway and opening separate issue.


Apple iPhone 5s, iOS 12.5.7, cannot open OpenLayers V8 examples.

Apple iPhone 5s, iOS 12.5.7, cannot open OpenLayers V8 examples.

IOS:12.5.7
safari:605.1.15
openlayers:v8
Expected behavior
Can be used normally

Could reproduce on an iphone 7 with iOS 12, this error shows up:

This apparently comes the optional chaining operator ?. from this line:
https://github.com/colorjs/color-parse/blob/6d0f7c1009f451948aa92c055371805174a7e381/index.js#L146
Indeed this operator is only supported from iOS 13+, see: https://caniuse.com/mdn-javascript_operators_optional_chaining

Nonetheless, if you're using OpenLayers in your own application, you can transpile your code if you need to target older browsers.
For the examples on openlayers.org, I think we'll stick with untranspiled code. The iOS/Safari version in question has a market share of 0.27 %, according to browsersl.ist.

Can't find variable: ResizeObserver at Map.js
npm install resize-observer
import { install } from 'resize-observer';
if (!window.ResizeObserver) install();
fix


InRelease should be generated by default

Hi,
The debian repository format states that the InRelease should be present, and the Release file should be present for older client.
At the moment, it's generated only for the codenames "xenial", "jessie" and "stretch". Shouldn't this be the default behavior?
Thanks for this gem :)

@krobertson Any input on this? thanks :)

+1 on this, this should be nice to be applied

He merged a PR made after this one, not sure why this one got no attention so far. Let's be patient ^^


PR for #51 - Added fix for issue with PackageVersion reported version number

This pull request contains a fix for issue #51 where the PackageVersion would parse a string such as '1.0' and would determine the value as '1.0.65535.65535' on Android devices.
This change includes a new parsing method which will take the string value and determine the correct major, minor, build and revision numbers, replacing those which don't exist with the default 0 value.

Happy for these changes to be merged in.


Mesh.volume() and Mesh.is_closed() don't work with Boxes and Cylinders

Calculating the volume of a Box or a Cylinder seems to always return zero for Box and Cylinder objects, even though they plot just fine and seem overall well-formed.  Similarly, is_closed() seems to always return False.  Pyramids and Spheres work fine.  I'm thinking it may be related to the fact that Boxes and Cylinders are wholly composed of non-triangular cells, since calling triangulate() causes them to give nonzero volumes (but they still don't register as closed).
import vedo

box = vedo.Box()
print("Box:", box.volume(), box.is_closed())

box = box.triangulate()
print("Triangulated box:", box.volume(), box.is_closed())

cylinder = vedo.Cylinder()
print("Cylinder:", cylinder.volume(), cylinder.is_closed())

cylinder = cylinder.triangulate()
print("Triangulated cylinder:", cylinder.volume(), cylinder.is_closed())

pyramid = vedo.Pyramid()
print("Pyramid:", pyramid.volume(), pyramid.is_closed())

sphere = vedo.Sphere()
print("Sphere:", sphere.volume(), sphere.is_closed())

# expected result: all volumes are nonzero and all booleans are True
# actual result:
# Box: 0.0 False
# Triangulated box: 6.000000000000002 False
# Cylinder: 0.0 False
# Triangulated cylinder: 6.211656935437641 False
# Pyramid: 0.43333333333333357 True
# Sphere: 4.157386497443854 True

Thanks for reporting.
I've added documentation for this behavior in both is_closed() and volume() methods, but also in Box and Cylinder.
Checking whether the mesh is triangular in volume() might be computationally expensive if these methods are called in loops or for large meshes.
import vedo

box = vedo.Box().triangulate().clean()
print("Box     :", box.volume(), box.is_closed(), box.is_manifold())

cylinder = vedo.Cylinder().triangulate().clean()
print("Cylinder:", cylinder.volume(), cylinder.is_closed(), cylinder.is_manifold())

pyramid = vedo.Pyramid() # not necessary, already triangulated
print("Pyramid :", pyramid.volume(), pyramid.is_closed(), pyramid.is_manifold())

sphere = vedo.Sphere()
print("Sphere  :", sphere.volume(), sphere.is_closed(), sphere.is_manifold())


1.8

Is 1.8 still "supported"?  ie, if there's a problem discovered with 1.8.2, will there be a 1.8.3?
If it is still supported, is there some documentation somewhere pointing to supported versions (especially with EOL dates)?

Yes, io.js v1.x is still supported; nodejs/io.js#1736 is a work in progress backport of changes from v2.
The process of long term support is being discussed by the @nodejs/lts working group and will probably be finalised before the next major release of Node.JS is ready.

Nice, thanks for clarifying! :heart:


useScrollToTop  from '@react-navigation/native' error

Hello Marco,
Thank you for all the hard work.
I am trying to implement useScrollToTop with BigList and i'm getting the following error
'undefined is not an object (evaluating '_ref7.animated')
Im following the instructions from the react navigation docs
Here is my code
import { useScrollToTop } from '@react-navigation/native'

const MyScreen = () => {

       const bigListRef = useRef()
       useScrollToTop(bigListRef)

              return (
                  <BigList
                    ref={bigListRef}
                   ....
                   />
                   )
}

Hi @haibert
try this
import { useScrollToTop } from '@react-navigation/native'

const MyScreen = () => {

const bigListRef = useRef()
useScrollToTop(React.useRef({
    scrollToTop: () => bigListRef.current?.scrollToTop({ animated = true }),
  }));

  return (
      <BigList
  ref={bigListRef}
  ....
  />
  )
}

I fixed this problem with PR #61
Please upgrade to the latest version 1.4.2

Thank you so much! worked like a charm. didn't need to specify the animation though. This was good enough:
 useScrollToTop(
        React.useRef({
            scrollToTop: () => {
                bigListRef.current.scrollToTop()
            },
        })
    )

that's right, need to pass parameters if using version 1.4.1 or below.


custom synonyms list not saved

Hi,
I created  custom synonyms list (Tools > create custom synonyms), gave a name, input about 200 positions and clicked on 'save'. However, when trying to filter ('search this file') the name doesn't autocomplete, and going back to Tools > create custom synonyms, you see that the synonym that was just created/saved, is not there.
thanks,
Pankaj

So, after a few attempts, it did save.....maybe I reached my account quota and it couldn't save? But might still be worth looking into....

Hi, I think you must have meant to open an issue for a different project! Bistro is a distributed job scheduler, it doesn't have a Tools menu or synonyms.


chore[definitions-parser]: whitelist @types/react

Refer to New types definition for next-pwa - PR for an overview of why the @types/react package is needed and should be added.

Not needed anymore! DT maintainer revised his decision to not include the triple-dash reference, which would mean that a package.json reference to @types/react would be needed. By using the triple-dash reference, no explicit addition to this file is needed.


Checkmark in ContextMenu MenuItem not rendering

What steps will reproduce this issue?
To reproduce this issue, I created a simple project containing a window with a button and a context menu. For each menu item in the context menu, I set the IsCheckable property to true. The properties are properly set with MenuItem clicks, however, the check mark is not rendered when IsChecked is set to true. I've attached the project where I reproduced the issue.
ContextMenuCheckmarkIssue.zip
Expected outcome
The checkmark simply needs to render properly. There is a Geometry object in Styles/Controls.ContextMenu.xaml that supposedly defines the checkmark. It seems as though that is the issue, but I'm not very familiar with the Geometry object to determine with certainty
--
Environment

MahApps.Metro v1.3.0
Windows 10
Visual Studio 2015 Community Edition
.NET Framework 4.5.2

I was able to get the check mark to show up by changing the Fill Property of the GlyphPanel to Black from UnsetValue using Snoop. I am unsure why, but the CheckMarkFill DynamicResource is not being set properly.

I was able to work around this issue by manually setting the application scope resource to a brush that I desired. A possible production ready solution until this is fixed would be to create a static class that edited resources wherever the application entry point was.
Application.Current.Resources["CheckmarkFill"] = Brushes.Black;

@chrism00ch You forgot to add the complete MahApps resources. https://github.com/MahApps/MahApps.Metro#a-short-how-to
Maybe you not followed the quick start guide http://mahapps.com/guides/quick-start.html
So with these resources your problem should be fixed.
<Application x:Class="WpfApplication.App"
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             StartupUri="MainWindow.xaml">
  <Application.Resources>
    <ResourceDictionary>
      <ResourceDictionary.MergedDictionaries>
        <ResourceDictionary Source="pack://application:,,,/MahApps.Metro;component/Styles/Controls.xaml" />
        <ResourceDictionary Source="pack://application:,,,/MahApps.Metro;component/Styles/Fonts.xaml" />
        <ResourceDictionary Source="pack://application:,,,/MahApps.Metro;component/Styles/Colors.xaml" />
        <ResourceDictionary Source="pack://application:,,,/MahApps.Metro;component/Styles/Accents/Blue.xaml" />
        <ResourceDictionary Source="pack://application:,,,/MahApps.Metro;component/Styles/Accents/BaseLight.xaml" />
      </ResourceDictionary.MergedDictionaries>
    </ResourceDictionary>
  </Application.Resources>
</Application>


Allow biospyder_dbs and biospyder_manifest_file to be null in config schema

Change schema to allow these params to be null when analyzing RNA-seq projects. This is an easy change, I just don't want to forget.
Setting these to null shouldn't affect the check-if-files-exist part of module 1, but it's work testing to be sure.

Closed with merge https://github.com/R-ODAF/R-ODAF_Health_Canada/pull/244


test-branch/execute-job/quoted-authorization/485b50c2-107b-4b21-897d-17bdbd2f535f

PR for testing d7344511cf733e3b3f0dd028736caac0e555a173

/canonical/self-hosted-runners/run-workflows d7344511cf733e3b3f0dd028736caac0e555a173


Mock 丢失responseType，导致文件下载乱码

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

What is expected?
https://github.com/PanJiaChen/vue-element-admin/pull/1779

@Nash-x9 mock就是模拟数据。可以去调用真实接口进行下载。


Docs: duplicate 'this'

Summary
before: this [this egghead video]
after: this [egghead video]

Codecov Report

Merging #3999 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3999   +/-   ##
=======================================
  Coverage   60.26%   60.26%
=======================================
  Files         196      196
  Lines        6765     6765
  Branches        6        6
=======================================
  Hits         4077     4077
  Misses       2685     2685
  Partials        3        3

Continue to review full report at Codecov.

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


Parallel queries support

https://github.com/AlexTatiyants/pev/issues/26
https://github.com/AlexTatiyants/pev/issues/29

Aha, yes, I came here because I was seeing over 100% time spent on some nodes. I found https://explain.dalibo.com/plan instead, which works.


Make PyGlow compatible with Python 3.

Make PyGlow compatible with Python 2.7 and 3.X.

thanks bjornt, nice work!


Editor drag n drop: unable to duplicate selection sometimes

Refs: #25338
os x, insiders

Enable drag and drop in editor and select something
Move the cursor one line up or down and hold the option key and drop
Notice the whole selection is moved one line down, it is not duplicated as I would expect since I am holding the option key

Please note that his is not happening 100% time but I get it seldomly to happen. Notice in this gif I had to do it 2 times in order to catch it.

Let's track this issue in https://github.com/Microsoft/vscode/issues/24000 which is younger. The way we monitor Ctrl key down is somewhat buggy.


Unable to install koalas on lubuntu--segmentation fault

On ubuntu, I have no problem in installing koalas and invoking the library as:
import databricks.koalas as ks
But, on lubuntu (version 18, 64bit), lightweight brother of ubuntu, conda installation is successful. But when I open ipython and call koalas as above, ipython breaks and I get a message of 'Segmentation fault'. I have tried to install koalas through pip also but to no avail.  I have tried this installation process on three different Virtual Machines (of lubuntu 64bit) but same result appears each time.

Could you share the error detail or the screen shot which shows the whole error message?
Also, what if import pandas or pyarrow or pyspark?

I am attaching three screen shots. Segmentation fault occurs when I call pyarrow. The first screen shot is the successful installation of koalas. IInd screenshot is regarding segmentation fault in ipython and IIIRd when I call pyarrow in pyspark.  Thanks.

Could you try with the higher version of pyarrow, like 0.14.1 if the underlying Spark <3.0 or 0.15 or higher if Spark >=3.0 ?

This time I created a virtual environment for koalas as mentioned in the installation. pyarrow version installed was 1.0.0. Other software installed are:
Downloading and Extracting Packages
readline-8.0         | 281 KB    |
libutf8proc-2.5.0    | 85 KB     |
pyparsing-2.4.7      | 60 KB     |
libgcc-ng-9.3.0      | 8.2 MB    |
gflags-2.2.2         | 114 KB    |
libev-4.33           | 105 KB    |
cycler-0.10.0        | 9 KB      |
_libgcc_mutex-0.1    | 3 KB      |
libblas-3.8.0        | 11 KB     |
libwebp-base-1.1.0   | 845 KB    |
boost-cpp-1.72.0     | 16.3 MB   |
libstdcxx-ng-9.3.0   | 4.5 MB    |
grpc-cpp-1.30.2      | 3.2 MB    |
pillow-7.2.0         | 676 KB    |
matplotlib-base-3.3. | 6.7 MB    |
icu-67.1             | 12.9 MB   |
openssl-1.1.1g       | 2.1 MB    |
libgfortran-ng-7.5.0 | 1.7 MB    |
libopenblas-0.3.10   | 7.8 MB    |
abseil-cpp-20200225. | 915 KB    |
bzip2-1.0.8          | 396 KB    |
libssh2-1.9.0        | 225 KB    |
pytz-2020.1          | 227 KB    |
tornado-6.0.4        | 642 KB    |
lcms2-2.11           | 431 KB    |
arrow-cpp-1.0.0      | 20.6 MB   |
libffi-3.2.1         | 47 KB     |
parquet-cpp-1.5.1    | 3 KB      |
thrift-cpp-0.13.0    | 18.6 MB   |
libevent-2.1.10      | 1.3 MB    |
six-1.15.0           | 14 KB     |
pandas-1.1.0         | 10.8 MB   |
setuptools-49.2.0    | 949 KB    |
lz4-c-1.9.2          | 226 KB    |
pip-20.2             | 1.1 MB    |
pyarrow-1.0.0        | 3.0 MB    |
python-3.8.5         | 71.0 MB   |
xz-5.2.5             | 343 KB    |
matplotlib-3.3.0     | 6 KB      |
libgomp-9.3.0        | 820 KB    |
tk-8.6.10            | 3.2 MB    |
libcblas-3.8.0       | 11 KB     |
freetype-2.10.2      | 905 KB    |
libcurl-7.71.1       | 312 KB    |
snappy-1.1.8         | 32 KB     |
libedit-3.1.20191231 | 122 KB    |
libpng-1.6.37        | 308 KB    |
re2-2020.08.01       | 226 KB    |
libtiff-4.1.0        | 668 KB    |
kiwisolver-1.2.0     | 87 KB     |
ncurses-6.2          | 993 KB    |
glog-0.4.0           | 104 KB    |
python-dateutil-2.8. | 220 KB    |
libnghttp2-1.41.0    | 709 KB    |
python_abi-3.8       | 4 KB      |
curl-7.71.1          | 139 KB    |
zlib-1.2.11          | 105 KB    |
_openmp_mutex-4.5    | 435 KB    |
ca-certificates-2020 | 145 KB    |
zstd-1.4.5           | 712 KB    |
olefile-0.46         | 31 KB     |
c-ares-1.16.1        | 108 KB    |
krb5-1.17.1          | 1.5 MB    |
brotli-1.0.7         | 386 KB    |
libprotobuf-3.12.3   | 2.3 MB    |
liblapack-3.8.0      | 11 KB     |
certifi-2020.6.20    | 151 KB    |
numpy-1.19.1         | 5.3 MB    |
sqlite-3.32.3        | 1.4 MB    |
aws-sdk-cpp-1.7.164  | 1.8 MB    |
jpeg-9d              | 266 KB    |
ld_impl_linux-64-2.3 | 612 KB    |
wheel-0.34.2         | 24 KB     |
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
But exactly the same segmentation fault persists. As soon as I call pyarrow library, pyspark (or rather ipython) breaks with  a Segmentation fault (Core dumped) message as before.

Looks like an issue in PyArrow. It might be best to report in their repo.

The problem is solved at this link.

Thanks for the sharing, @harnalashok


Web UX: Browser default scrollbars

Include browser default scrollbars for persistent indication of scrollable pages and their length.
Currently, touch style indicators only appear when already scrolling.
This would affect:

Wonder home
Collection view
Artifact search
Timeline

@jaredbell Just landed this in main. One note:

ArtifactSearch had this intentionally turned off because

it's a dynamic list and the scrollbacr "knob" size is always fluctuating.
performance is pretty poor when trying to drag the scroll bar quickly.

I've left it off for this view for now, but LMK if you think it's worth turning on.


Publish to Windows update

Our company is rarely publishing drivers to Windows update and every time the procedure is a little bit different.
This time there are three required fields that we don`t know how to fill.
We opened a ticket at Microsoft but didn`t get all answers.
These are the questions.

Provide the email address of the Microsoft sponsor working with you on this request.

From Microsoft support we got an answer that the current workaround where you put<EMAIL_ADDRESS>as that field is being removed in the next portal update. What should we put here after the workaround is removed?

Describe how you validated the quality of this driver.

What to write here? We ran HCK and HLK tests on 13 different OS. Is this good enough?

The following OEMs are affected by this publication.

What to write here?
Regards

Hi @UrosDakskobler
I'm so sorry that you have had trouble publishing your driver. Here are the answers to your three questions:

"Provide the email address of the Microsoft sponsor working with you on this request."
If you aren’t working with someone at Microsoft, then entering<EMAIL_ADDRESS>is perfectly fine. If you have worked with someone at Microsoft, it is helpful if you provide the contact.

"Describe how you validated the quality of this driver."
Briefly describe the validation you performed. Your example is perfectly fine. This information is collected to help us understand what partners are--and are not--doing. Ultimately the health, and performance telemetry and associated measures guide us.

"The following OEMs are affected by this publication."
If an OEM is affected please list which ones. If no OEM is affected enter None.

I hope that this helps.
All the best,
Eliot


Robotic implementation

Hi,
I have carefully followed your work and your cooperation with AMZ Driverless team. I managed to implement the Udacity MPC algorithm on my robot but i found conversion of MPCC from matlab to C++ very difficult especially the theta function.
I was wondering how did you manage to implement the MPCC algorithm on RC car and driverless car without having the C++ version code.

I assume with theta function you mean the spline. For the RC cars we used matlab to generate the spline and exported the parameters, and in C++ only had to perform the evaluation.
Generally, I do have a C and a C++ version of the controller and AMZ Driverless has their own implementation which is based on ForcesPro. Until now I just did not open source the C++ version, however, this is something a constantly evaluate.

I, for one, would really appreciate a C++ version ;)

I am also looking forward to the c++ version.


bundle.js.map returns a copy of bundle.js

/bundle.js.map currently has exactly the same content as /bundle.js on version 0.4.0.

Ouch! Would you like to send a PR?


CmdK Menu Doesn't Search Snippets Properly (no results when searching)

I've reproduced this several times, the react-query setup is likely wrong, it needs to keep searching with a queryKey that is unique for the search string

CC @mrudulpatil18


[firebase_crashlytics]Firebase Crashlytics plugin

Add plugin to FlutterFire that will report Dart side errors as non-fatal errors to the Firebase console.
Fixes: https://github.com/flutter/flutter/issues/14765

I got a bit eager waiting for this to get merged, so I migrating a project from flutter_crashlytics to this plugin by including the git branch, and stumbled on a few things.. hope you don't mind a bit very early feedback (feel free to ignore):

Imho there should be a way to cause a "real" crash, ie. calling [Crashlytics crash] because if I understand it correctly, crashlytics only ever sends crashes/logs/etc. when the app actually crashes and is subsequently restarted? (or even provide a isFatal flag in the onError method)
It would be nice if logs are also sent periodically, because otherwise if a native part of my application crashes, all "context" logging from the dart side is lost (although i guess i could simply do this manually as a user of the plugin)
api nitpicking .. I imagine user identifier, email, name would be usually set from the same location. how about providing one method with named parameters and only one native roundtrip :)

Consider updating FlutterFire.md while we're at it? https://github.com/flutter/plugins/blob/master/FlutterFire.md

@hpoul thanks for the feedback:

Non fatal crashes are the best we can do without changes to the underlying SDKs. We considered causing a fatal crash but decided that non fatals would be better till we have better native SDK support.

Good point, thanks for the suggestion.

It would be nice, but our current approach is to stay as close to the native SDK interfaces as possible. Still a good point and something we can consider later on.

Cirrus is all green, PR has stale CI status. See finished builds here:
https://cirrus-ci.com/build/5687774492491776


Dev

Support for lifespan ASGI messages
Improved logging

See https://github.com/encode/uvicorn/issues/225 for an explanation why its good to add exc_info to error logs.

(CI is green except for Hypercorn tests (hypercorn is still broken))


[BUG] Lama-cleaner: error: torch.cuda.is_available() is False

Model
Which model are you using?
lama-cleaner: 1.2.0
Describe the bug
Aftert I update Lama Cleaner I got an Error:

Platform: Windows-10-10.0.19045-SP0
Python version: 3.10.6
torch: 2.0.1
torchvision: 0.15.2
Pillow: 9.4.0
diffusers: 0.16.1
transformers: 4.27.4
opencv-python: <IP_ADDRESS>
xformers: N/A
accelerate: 0.17.1
lama-cleaner: 1.2.0
rembg: N/A
realesrgan: N/A
gfpgan: N/A

2023-06-07 11:09:03.954 | INFO     | lama_cleaner.parse_args:parse_args:193 - Loading installer config from D:\Lama Cleaner\lama-cleaner\win_start.bat..\installer_config.json
usage: lama-cleaner [-h] [--host HOST] [--port PORT] [--config-installer] [--load-installer-config]
[--installer-config INSTALLER_CONFIG]
[--model {lama,ldm,zits,mat,fcf,sd1.5,anything4,realisticVision1.4,cv2,manga,sd2,paint_by_example,instruct_pix2pix}]
[--no-half] [--cpu-offload] [--disable-nsfw] [--sd-cpu-textencoder] [--sd-controlnet]
[--sd-controlnet-method {control_v11p_sd15_canny,control_v11p_sd15_openpose,control_v11p_sd15_inpaint,control_v11f1p_sd15_depth}]
[--sd-local-model-path SD_LOCAL_MODEL_PATH] [--local-files-only] [--enable-xformers]
[--device {cuda,cpu,mps}] [--gui] [--no-gui-auto-close] [--gui-size GUI_SIZE GUI_SIZE]
[--input INPUT] [--output-dir OUTPUT_DIR] [--model-dir MODEL_DIR] [--disable-model-switch]
[--quality QUALITY] [--enable-interactive-seg] [--interactive-seg-model {vit_b,vit_l,vit_h}]
[--interactive-seg-device {cuda,cpu,mps}] [--enable-remove-bg] [--enable-anime-seg]
[--enable-realesrgan] [--realesrgan-device {cpu,cuda,mps}]
[--realesrgan-model {realesr-general-x4v3,RealESRGAN_x4plus,RealESRGAN_x4plus_anime_6B}]
[--realesrgan-no-half] [--enable-gfpgan] [--gfpgan-device {cpu,cuda,mps}]
[--enable-restoreformer] [--restoreformer-device {cpu,cuda,mps}] [--enable-gif]
[--install-plugins-package]
lama-cleaner: error: torch.cuda.is_available() is False, please use --device cpu or check your pytorch installation
Press any key to continue . . .
In CMD I got this:
Microsoft Windows [Version 10.0.19045.2965]
(c) Microsoft Corporation. All rights reserved.
C:\Users\derec>python
Python 3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import torch
print(torch.version)
1.12.1+cu113
print(torch.cuda.is_available())
True

I update Cuda and Torech but tje error continue
Successfully installed torch-2.0.1+cu117
C:\Users\derec\OneDrive\Desktop\Deep_Fack>python
Python 3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import torch
print(torch.version)
2.0.1+cu117
print(torch.cuda.is_available())
True

It seems that the Python environment where you installed torch 2.0.1+cu117 and launched lama-cleaner are not the same. Lama detected an environment with torch 2.0.1.

This is not the main Installation it's a second one for vlad/automatic

i get this error too.... after i install Xformers... reinstall still get the problems...

after i install Xformers...i get this error too...., reinstall still get the problems...

Different versions of xformers require different versions of PyTorch. Below are the tested version combinations that can be used. Perhaps it can solve your problem.
pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 --extra-index-url https://download.pytorch.org/whl/cu117
pip install xformers==0.0.16

pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 --extra-index-url https://download.pytorch.org/whl/cu117
pip install xformers==0.0.16
In what version of Python?

pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 --extra-index-url https://download.pytorch.org/whl/cu117 pip install xformers==0.0.16
In what version of Python?

python 3.10 should work


Angular 2 team has approached RC2

Angular 2 Team has approached RC2.

@aftab10662  Thanks!
:shipit:


Connection lost to XMPP Server on Incoming File Accept Request if not accepted within certain time

Hello,
There is a serious issue in File Transfer , as OnStreamInitiationRequest(Jid from, XmlElement si) is blocking all the communication to server and server close connection after certain time.

You are using the default SOCKS5 proxy method? You are reffering to the file tranfer itself, or to the Stream INitiation process?

Dear sir,
I have used Sharp.Xmpp in Client Xamarin.forms and Xamarin.Android and also Configured an Openfire server. I can send messages with others. While sending any file to JID, it is not streaming after accepting the request. but If i get any request, It is downloaded after accepting it. I Could not figured out.  How to resolve it?.


apollo.config.js and graphql-config

Hello!
Apollo has their own config file (apollo.config.js)
and https://graphql-config.com/ has a number of filenames it supports
It would be swell to see those supported here.
Thanks again for the great work!

Sorry, I completely missed this.
Added!


The "Market size" referenced in Venus.io only contains the BNBchain network.

Hello,
The current “Market size” & "Total Borrowed" displayed in Venus.io front end does not include all networks such as Ethereum, Arbitrum, opBNB, and zkSync. It is only BNBchain. It could be nice to include all markets with API call, as well as referencing the number of networks etc.

Thanks,

Hi @Frayst2
You're correct yes, this layout is out-of-date given we're now a multi chain dApp. We have it in our pipeline to do exactly what you described (show the total market size across all networks, show the amount of networks/assets), so you can expect the landing page to be updated in the coming weeks.
Thank you!


feature request: move document easily

The traditional approach would be to Drag and Drop onto the tree. However, drag & drop is tricky. I like the approach that Google Docs currently takes of selecting the folder separately. I think though we could make it visually nicer by instead of displaying one folder at a time displaying the active tree being navigated.

The current workflow is to open the folder in gdrive (click on breadcrumb if viewing a file) and then move it there. Alternatively, open the file itself and use the move functionality there. Note that edit mode for the doc (embed) appears to not support the file move operation.


App crash during shutdown

Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10325,Native,Thread*=0xb88d1920,peer=0x2334a100,"allenges - 8539 - 10325"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10343,Native,Thread*=0xb890a4f0,peer=0x2334a160,"allenges - 8539 - 10343"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10349,Native,Thread*=0xb88d1920,peer=0x2334a1c0,"allenges - 8539 - 10349"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10355,Native,Thread*=0xb890a4f0,peer=0x2334a220,"allenges - 8539 - 10355"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10358,Native,Thread*=0xb88d1920,peer=0x2334a280,"allenges - 8539 - 10358"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10360,Native,Thread*=0xb890a4f0,peer=0x2334a2e0,"allenges - 8539 - 10360"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10361,Native,Thread*=0xb88d1920,peer=0x2334a340,"allenges - 8539 - 10361"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10369,Native,Thread*=0xb890a4f0,peer=0x2334a3a0,"allenges - 8539 - 10369"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10377,Native,Thread*=0xb890a4f0,peer=0x2334a400,"allenges - 8539 - 10377"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10391,Native,Thread*=0xb890a4f0,peer=0x2334a460,"allenges - 8539 - 10391"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10394,Native,Thread*=0xb887e050,peer=0x2334a4c0,"allenges - 8539 - 10394"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10408,Native,Thread*=0xb84dd608,peer=0x23351100,"allenges - 8539 - 10408"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[65,tid=10412,Native,Thread*=0xb890a4f0,peer=0x2334a520,"allenges - 8539 - 10412"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10419,Native,Thread*=0xb84dd608,peer=0x23351160,"allenges - 8539 - 10419"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10415,Native,Thread*=0xb887e050,peer=0x2334a580,"allenges - 8539 - 10415"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[65,tid=10424,Native,Thread*=0xb890a4f0,peer=0x233511c0,"allenges - 8539 - 10424"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[62,tid=10425,Native,Thread*=0xb84dd608,peer=0x2334a5e0,"allenges - 8539 - 10425"]
Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[64,tid=10426,Native,Thread*=0xb887e050,peer=0x23351220,"allenges - 8539 - 10426"]

These messages are harmless, is there an actual crash backtrace? Logs?

oh, i am sorry. I did not understand your manual for report correctly
11-01 16:47:03.708 7196-7196/ E/AndroidRuntime: FATAL EXCEPTION: main
Process: PID: 7196
java.lang.RuntimeException: Unable to destroy activity {/com.outdoo.ui.direct.chat.ChatActivity}: java.lang.IllegalStateException: Attempt to use disposed object in ChatClient#shutdown
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3812)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3830)
at android.app.ActivityThread.access$1400(ActivityThread.java:156)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:211)
at android.app.ActivityThread.main(ActivityThread.java:5371)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:945)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:740)
Caused by: java.lang.IllegalStateException: Attempt to use disposed object in ChatClient#shutdown
at com.twilio.chat.ChatClient.checkDisposed(ChatClient.java:553)
at com.twilio.chat.ChatClient.shutdown(ChatClient.java:441)
at com.outdoo.data.chat.twillio.TwillioMessagingClient.disconnect(TwillioMessagingClient.java:70)
at com.outdoo.ui.direct.chat.ChatPresenter.detachFromView(ChatPresenter.kt:30)
at com.outdoo.ui.base.inject.BaseInjectActivity.onDestroy(BaseInjectActivity.kt:26)
at android.app.Activity.performDestroy(Activity.java:6169)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1141)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3799)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3830)
at android.app.ActivityThread.access$1400(ActivityThread.java:156)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:211)
at android.app.ActivityThread.main(ActivityThread.java:5371)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:945)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:740)

Attempt to use disposed object in ChatClient#shutdown

You have shut down ChatClient and then try to shutdown it again.

I can send all logs, when app is crashing

Just don't reuse ChatClient after shutdown.

Closing, please reopen if you have further questions.


Suspected orchestrator issue

Hi,
gulp.task('lint', function() {
   return gulp.src('src/ngCacheService.js')
        .pipe(jshint('.jshintrc'))
        .pipe(jshint.reporter('jshint-stylish'))
        .pipe(jshint.reporter('fail'));
});

above lint task breaks with following error
TypeError: undefined is not a function
    at Gulp.<anonymous> (c:\Workspaces\gulpfile.js:36:50)
    at module.exports (c:\Workspaces\node_modules\gulp\node_modules\orchestrator\lib\runTask.js:34:7)
    at Gulp.Orchestrator._runTask (c:\Workspaces\node_modules\gulp\node_modules\orchestrator\index.js:273:3)
    at Gulp.Orchestrator._runStep (c:\Workspaces\node_modules\gulp\node_modules\orchestrator\index.js:214:10)
    at Gulp.Orchestrator.start (c:\Workspaces\node_modules\gulp\node_modules\orchestrator\index.js:134:8)
    at C:\ProgramData\nodejs\node_modules\gulp\bin\gulp.js:129:20
    at process._tickCallback (node.js:355:11)

modules
"gulp": "^3.8.11"
"gulp-jshint": "~1.11.1"
"jshint-stylish": "^2.0.1"

Did you figure this out? If you provide the rest of your gulpfile I may be able to help more but closing this as it's definitely not a gulp-jshint issue.

The problem occurs only within jshint, as the rest of my tasks works as normal.
Please see below : my gulpfile
taskvar gulp = require('gulp');
var bump = require('gulp-bump');
var gutil = require('gulp-util');
var uglify = require('gulp-uglify');
var sourcemaps = require('gulp-sourcemaps');
var rename = require("gulp-rename");
var fs = require('fs');
var karmaServer = require('karma').Server;
var jshint = require('gulp-jshint').Server;
var karmaConfig = '/test/resources/karma.conf.js';
var cwd = process.cwd();

var getPackageJson = function() {
   return JSON.parse(fs.readFileSync('./package.json', 'utf8'));
};

gulp.task('version-bump', function() {
   return gulp.src([ cwd + '/package.json' ]).pipe(bump()).pipe(gulp.dest('./'));
});

gulp.task('lint', function() {
   return gulp.src('src/ngCacheService.js').pipe(jshint('.jshintrc')).pipe(jshint.reporter('jshint-stylish')).pipe(jshint.reporter('fail'));
})

Could you reopen the issue

The error above says that it happened on line 36 of your gulpfile, but the one you put here only has ~20 lines


Multiple EventViews get's created

New Issue Checklist

[x] Use the latest version of CalendarKit
[x] I've read the Contribution Guidelines
[x] I've searched for existing GitHub issues

Issue Description
When ever i try to create a event there'll be multiple events that is getting created for the same time and date. I think the startDate and EndDate gets called multiple times..
Probably im doing something wrong here.I'm just not able to see it where :/
Code I'm using with CalendarKit

//Event for date
    var events = [Event]()
    override func eventsForDate(_ date: Date) -> [EventDescriptor]
    {
                let dateFormatter = DateFormatter()
                dateFormatter.dateFormat = "yyyy-MM-dd HH:mm:ss"
                dateFormatter.timeZone = TimeZone(abbreviation: "GMT+5:5")
                let event = Event()
                event.startDate = dateFormatter.date(from: "2018-09-05 3:30:00")!
                event.endDate = dateFormatter.date(from: "2018-09-05 6:30:00")!
                 event.text = "test"
                 self.events.append(event)
                return events
}

this is what im getting

Can you please give me an example ?

@mahanthesh0r I think the issue you're having is because of a for loop which creates multiple events. Is there a for loop in your code?
for i in 0...4 {
let events = Event()
}

If so...remove the for loop and change it to the code below
let events = Event()
//etc...

this should fix the issue, and only give you one event

@johnnyperdomo, @mahanthesh0r or this;
//Event for date
    var events = [Event]() // Outer scope variable
    override func eventsForDate(_ date: Date) -> [EventDescriptor]
    {
                let dateFormatter = DateFormatter()
                dateFormatter.dateFormat = "yyyy-MM-dd HH:mm:ss"
                dateFormatter.timeZone = TimeZone(abbreviation: "GMT+5:5")
                let event = Event()
                event.startDate = dateFormatter.date(from: "2018-09-05 3:30:00")!
                event.endDate = dateFormatter.date(from: "2018-09-05 6:30:00")!
                 event.text = "test"
                 self.events.append(event) // Events just get appended over and over again
                return events // The outer array is returned
}

@richardtop You were right.  It works now!! Thank You


Mention how to run all tests interactively

The guide fails to mention that users can run all test interactively with this incantation:
M-x ert RET t

It might be good to mention (some of) the other test selectors too.

+1 that's very handy!

+1 Yeah, I gave a very basic overview of ert, I have some other docs to write this week, I'll try to do an update.

:tada:


TPL - SEACAS/exodus building issues

There are some build issues with SEACAS/ExodusII that have emerged:

Requires netcdf < 4.9.0 currently
Possible gcc issues. Was able to build on M1 with gcc/g++ wrappers of Apple clang 14.0.3, but may be issues with other gcc versions.

Explicit netcdf version added at 13355a5e83f98b0a35dc0b4a2059ad565a2b30b8.


Add backgroundColor and border options to writeTextToCanvas background

There has been multiple requests for this. Its not currently used in labels, but this can be used to create a canvas and add it as a billboard.
Tests were added and CHANGES.md was updated.

LGTM.  @mramato do you want to test and merge?

@mramato I've updated the parameter name like we discussed.

That's my only comment.

@mramato Not sure what happened there. Updated changes.md


IP may leak after agent restart

Describe the bug

In the existing reconcile logic (), antrea-agent remove OVS ports/ OpenFlow entries / items in the memory interface store if the Pod is deleted when agent is down. But the logic does not call IPAM to recycle the allocated IP. So this may lead to a leak on the IP resources.
To Reproduce

Expected

Actual behavior

Versions:

Antrea: main branch
Additional context

I was taking a look at this old issue and I tried to reproduce the IP leakage.
Based on my tests and based on the kubelet code, it seems very difficult to reproduce this situation.
Even with the following steps:

schedule a workload Pod on nodeX
remove the antrea-agent Pod from nodeX by editing the DaemonSet's affinity
force delete the workload Pod with kubectl
wait for a few minutes
kill the kubelet service (it will restart immediately)
revert the change to the antrea-agent DaemonSet

After a few seconds (less than a minute), the new antrea-agent Pod receives a CmdDel command for the old workload Pod, and the IP is released.
It seems that the kubelet garbage collector is taking care of removing the old sandbox. When I increase kubelet log verbosity, I see:
Oct 30 22:20:02 kind-worker kubelet[37935]: I1030 22:20:02.300464   37935 kuberuntime_gc.go:175] "Removing sandbox" sandboxID="4eb3e402b4d2342278fdf12e5d3b33a206363f4ec93af271020a8736604a8442"
Oct 30 22:20:02 kind-worker kubelet[37935]: E1030 22:20:02.322027   37935 kuberuntime_gc.go:180] "Failed to stop sandbox before removing" err="rpc error: code = Unknown desc = failed to destroy network for sandbox \"4eb3e402b4d2342278fdf12e5d3b33a206363f4ec93af271020a8736604a8442\": plugin type=\"antrea\" failed (delete): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial unix /var/run/antrea/cni.sock: connect: connection refused\"" sandboxID="4eb3e402b4d2342278fdf12e5d3b33a206363f4ec93af271020a8736604a8442"

kubelet is able to list all sandboxes from the container runtime, and the container runtime I am using (containerd v1.7.1) will not remove the sandbox until the network has been deleted:
root@kind-worker:/# crictl pods
POD ID              CREATED             STATE               NAME                NAMESPACE           ATTEMPT             RUNTIME
5a64643d69ed8       32 minutes ago      NotReady            toolbox-rhc2g       default             0                   (default)
4eb3e402b4d23       34 minutes ago      NotReady            toolbox-qfnfr       default             1                   (default)
b49dac301f1fe       2 hours ago         Ready               kube-proxy-kz7zx    kube-system         0                   (default)

It is possible that some older versions of containerd were not that robust.
@tnqn do you think we should have a more defensive posture in Antrea and add logic to proactively release IPs on agent (re)start?

@antoninbas I have tried the following K8s versions deployed via kind and haven't managed to reproduce IP leak with the steps you described:

v1.26.6
v1.24.15
v1.23.17
v1.22.17
v1.21.14

So I feel this case may have been taken care of in normal workflow, but it's hard to say it's handled correctly in abnormal case, for example, containerd previously had this issue: https://github.com/containerd/containerd/pull/5569, and I remember you were investigating another leak with newer container versions in the last few weeks which we don't know the root cause yet? And there could be other CRIs which implement the cleanup differently. Therefore, I tend to agree that, instead of relying on kubelet/container runtime to be bug free regarding CNI cleanup, it's more robust to perform a conservative garbage collection on agent start. We should log such cleanup explicitly as we don't actually expect it unless there is a bug in container runtime or antrea.

I remember you were investigating another leak with newer container versions in the last few weeks which we don't know the root cause yet?

The person who reported the issue confirmed that when using a more recent version of containerd, the issue cannot be reproduced anymore (perhaps because of this fix: https://github.com/containerd/containerd/pull/5904). With an older containerd version, they were able to reproduce the issue consistently.

Therefore, I tend to agree that, instead of relying on kubelet/container runtime to be bug free regarding CNI cleanup, it's more robust to perform a conservative garbage collection on agent start.

Sounds good to me. I can take a stab at it.
It probably won't be possible to validate that code with e2e testing, but we can have a unit test.

@tnqn I wrote some PoC code so see if I could come up with a viable approach: https://github.com/antrea-io/antrea/commit/fbfa402ce5d7138880b37cc6de3903f6baf9ce39
However, it feels very much like an anti-pattern: we have to craft the CNI arguments from "scratch" in order to invoke the IPAM plugin. It can work (both when delegating to host-local IPAM or when using AntreaIPAM), but it feels like a hack.
The code I wrote uses the interfaceStore (populated from the persisted OVSDB) to determine for which containers we should do "IPAM garbage collection". An alternative approach would be to maintain and persist a CNI result cache, which would be updated whenever we invoke the IPAM plugin (ideally, AntreaIPAM too). We can use libcni for this. With this approach, we can use the cached results to easily generate DEL commands for Pods that no longer exist. This may be a cleaner approach (I need to check if it works), but it's probably a bit more disruptive.
Going back to the relevance of this issue, it does feel inconsistent to treat interfaces and IP addresses differently. Either we assume that the container runtime (+ kubelet) will always eventually invoke CNI DEL, in which case that part of the reconciliation logic is not really needed at all. Or we assume that resource leak is possible under some conditions, and we have to take care of all resources consistently.

I remember you were investigating another leak with newer container versions in the last few weeks which we don't know the root cause yet?

The person who reported the issue confirmed that when using a more recent version of containerd, the issue cannot be reproduced anymore (perhaps because of this fix: containerd/containerd#5904). With an older containerd version, they were able to reproduce the issue consistently.

I took a look at the issue and the PR, they seem ensuring CNI will be called repeatedly until it returns success. But I remember in our case there was no CNI invocation, so looks different. Do you know which version the issue can be reproduced and which can not? According to the enhancements that have been made in containerd, it does seem CNI cleanup is ensured now.

However, it feels very much like an anti-pattern: we have to craft the CNI arguments from "scratch" in order to invoke the IPAM plugin. It can work (both when delegating to host-local IPAM or when using AntreaIPAM), but it feels like a hack.

I was thinking something more hacky, accessing the IPAM dir and deleting IPs that shouldn't exist.. I remember we offered a script for users to do the cleanup when they encounted the IP leak: https://github.com/antrea-io/antrea/blob/main/hack/gc-host-local.sh.

Going back to the relevance of this issue, it does feel inconsistent to treat interfaces and IP addresses differently. Either we assume that the container runtime (+ kubelet) will always eventually invoke CNI DEL, in which case that part of the reconciliation logic is not really needed at all. Or we assume that resource leak is possible under some conditions, and we have to take care of all resources consistently.

Agree. When we added this logic, kubelet and container runtime were not that robust, notwithstanding the logic is not complete. But looking at the related issues in containerd and its fixes, I'm also wondering if it's still worth making it more complex to cover this case.
If we want to keep the logic for now, how about just using the simple (but hacky) approach to release known leaked IPs bypassing the IPAM plugin, without adding more cache/storage? It will be very specific to host-local plugin and could be broken if host-local changes its implementation, but it's the only case we have encountered in production, and this is a workaround anway. If IP leak still happens, right direction is still patching and upgrading container runtime.

I took a look at the issue and the PR, they seem ensuring CNI will be called repeatedly until it returns success. But I remember in our case there was no CNI invocation, so looks different. Do you know which version the issue can be reproduced and which can not? According to the enhancements that have been made in containerd, it does seem CNI cleanup is ensured now.

Yes that PR seemed like a bit of a stretch, so maybe it was some other patch.
The issue could be reproduced consistently with containerd 1.6.6, but could not be reproduced with containerd 1.6.18.
One it became apparent that the issue was because of containerd, not Antrea, and that it could not be reproduced with a more recent version of containerd, I didn't try to identify the exact patch.
We also have this in Antrea now, which avoids that issue as well: https://github.com/antrea-io/antrea/pull/5548

If we want to keep the logic for now, how about just using the simple (but hacky) approach to release known leaked IPs bypassing the IPAM plugin, without adding more cache/storage?

Hmm, I was thinking it would be nice to have a unified approach which also works with AntreaIPAM. Don't you think the same issue can happen there if there is a missing CNI DEL? I.e., the IPPool CR has leaked IPs.

If we want to keep the logic for now, how about just using the simple (but hacky) approach to release known leaked IPs bypassing the IPAM plugin, without adding more cache/storage?

Hmm, I was thinking it would be nice to have a unified approach which also works with AntreaIPAM. Don't you think the same issue can happen there if there is a missing CNI DEL? I.e., the IPPool CR has leaked IPs.

I remember it has been taken care of by antrea-controller: https://github.com/antrea-io/antrea/blob/e8f5d93c1a63722922f3d5549e8787369304d420/pkg/controller/ipam/antrea_ipam_controller.go#L162-L165.

OK, thanks for the link. If AntreaIIPAM has its own GC, then I think it's acceptable to have a solution which is specific to host-local.


Release Version 0.2.1

This version fixes a bug where the identity matrix was undefined.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/82224
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 53c9dbc2f90be89a5cfaccb327aa1ce5cdac9db6
git push origin v0.2.1

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/82224
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 53c9dbc2f90be89a5cfaccb327aa1ce5cdac9db6
git push origin v0.2.1


display on the map

Hello @hkgnp,
I have just displayed some places and I have noticed what I'm personally missing, maybe you could add these functions to your plugin, I think it would be useful not only for me..

An option to show different places on the map with different icons and/or colours.
A button to show the names of all places on the map at the same time and to turn them off.

No? No-one?

I'm currently overseas. Will take a look when I am back.

Hi @hkgnp ,
I don't want to rush you, just to ask if and when we can expect the improvements mentioned above?

Avaiable in the latest version.


Updated imodel.js version to 2.7.0

Looked over each sample and did not find any issues caused by the new updates. I'll leave this open for a little while to give time for people to double check their own samples/code for issues caused by 2.7.0

I deleted node-modules and started over.  The app-ui problem did not reproduce.


Update hosts after SetHostname is called.

This happens before provisioning. Which is useful for cases such as Ansible if the hostname is used in a playbook. See #31. I don't know if there is a better place that this can be hooked in but this works for me.

This PR worked for me in Arch linux. I then tried it on my OS X host which had a working vagrant machine and it also continued to work, so it looks like this small change wouldn't introduce a regression.

Merged in develop