Dart2JS collection compiler error

Sadly, I don't have a small case to reproduce this & the codebase is private, but I can summarize the change that resulted in this error.
This started occurring after removing the _dtoList.removeWhere line of code below, but I found that it would continue to happen even if this _replaceDto function & its callsites were removed.
class DtoCache {
  List<Dto> _dtoList = [];

  // ...

  // Gets called as part of a code path that is listening to a stream event.
  void _replaceDto(Dto dto) {
    // If either of these lines, or the function itself are removed, I get the compiler error below.
   _dtoList.removeWhere((d) => dto.id == d.id);
   _cacheDto(dto);
  }
}

Edit: I realize it's probably useful if I include that our pubspec.lock is using collection: 1.16.0.

Name & Version of OS:

macOS 10.15.7
We also have CI running a container based on the official dart-docker image that fails with the same error. On our side we're using FROM dart:2.13.4.

Dart SDK Build Number:

2.13.4

Command run: pub global run webdev build --output build -- --delete-conflicting-outputs
Error:
[SEVERE] build_web_compilers:entrypoint on web/main.dart: ExitCode:255
StdOut:
org-dartlang-app:///packages/collection/src/algorithms.dart@2303+1:
Internal Error: Runtime type information not available for type_variable_local(j:type_variable(lowerBound.E)) in (SyntheticLocal(result), local(lowerBound#sortedList), local(lowerBound#value), local(lowerBound#compare)) for j:method(lowerBound).
The compiler is broken.

When compiling the above element, the compiler crashed. It is not
possible to tell if this is caused by a problem in your program or
not. Regardless, the compiler should not crash.

The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.

Please include the following information:

* the name and version of your operating system,

* the Dart SDK build number (2.13.4), and

* the entire message you see here (including the full stack trace
  below as well as the source location above).

StdErr:
Unhandled exception:
Assertion failure: Runtime type information not available for type_variable_local(j:type_variable(lowerBound.E)) in (SyntheticLocal(result), local(lowerBound#sortedList), local(lowerBound#value), local(lowerBound#compare)) for j:method(lowerBound).
#0      failedAt (package:compiler/src/diagnostics/invariant.dart:49:3)
#1      LocalsHandler.readLocal (package:compiler/src/ssa/locals_handler.dart:354:11)
#2      TypeBuilder._buildEnvironmentForType (package:compiler/src/ssa/type_builder.dart:289:12)
#3      TypeBuilder.analyzeTypeArgumentNewRti (package:compiler/src/ssa/type_builder.dart:207:9)
#4      TypeBuilder.analyzeTypeArgument (package:compiler/src/ssa/type_builder.dart:191:12)
#5      KernelSsaGraphBuilder.visitInstantiation (package:compiler/src/ssa/builder_kernel.dart:5212:24)
#6      Instantiation.accept (package:kernel/ast.dart:6291:44)
#7      KernelSsaGraphBuilder._visitPositionalArguments (package:compiler/src/ssa/builder_kernel.dart:3616:16)
#8      KernelSsaGraphBuilder._visitArgumentsForStaticTarget (package:compiler/src/ssa/builder_kernel.dart:3736:33)
#9      KernelSsaGraphBuilder.visitStaticInvocation (package:compiler/src/ssa/builder_kernel.dart:3820:11)
#10     StaticInvocation.accept (package:kernel/ast.dart:6120:44)
#11     KernelSsaGraphBuilder.visitReturnStatement (package:compiler/src/ssa/builder_kernel.dart:1797:23)
#12     ReturnStatement.accept (package:kernel/ast.dart:9497:43)
#13     KernelSsaGraphBuilder.visitBlock (package:compiler/src/ssa/builder_kernel.dart:1731:17)
#14     Block.accept (package:kernel/ast.dart:8518:43)
#15     KernelSsaGraphBuilder._visitInlinedFunction (package:compiler/src/ssa/builder_kernel.dart:6325:30)
#16     KernelSsaGraphBuilder._doInline (package:compiler/src/ssa/builder_kernel.dart:6303:5)
#17     KernelSsaGraphBuilder._tryInlineMethod.doInlining.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:5984:11)
#18     KernelSsaGraphBuilder._inlinedFrom.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:926:21)
#19     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#20     KernelSsaGraphBuilder._inlinedFrom (package:compiler/src/ssa/builder_kernel.dart:924:14)
#21     KernelSsaGraphBuilder._tryInlineMethod.doInlining (package:compiler/src/ssa/builder_kernel.dart:5979:7)
#22     KernelSsaGraphBuilder._tryInlineMethod (package:compiler/src/ssa/builder_kernel.dart:5991:17)
#23     KernelSsaGraphBuilder._pushStaticInvocation (package:compiler/src/ssa/builder_kernel.dart:4939:9)
#24     KernelSsaGraphBuilder.visitStaticInvocation (package:compiler/src/ssa/builder_kernel.dart:3841:5)
#25     StaticInvocation.accept (package:kernel/ast.dart:6120:44)
#26     KernelSsaGraphBuilder.visitVariableDeclaration (package:compiler/src/ssa/builder_kernel.dart:3562:24)
#27     VariableDeclaration.accept (package:kernel/ast.dart:10058:43)
#28     KernelSsaGraphBuilder.visitBlock (package:compiler/src/ssa/builder_kernel.dart:1731:17)
#29     Block.accept (package:kernel/ast.dart:8518:43)
#30     KernelSsaGraphBuilder._visitInlinedFunction (package:compiler/src/ssa/builder_kernel.dart:6325:30)
#31     KernelSsaGraphBuilder._doInline (package:compiler/src/ssa/builder_kernel.dart:6303:5)
#32     KernelSsaGraphBuilder._tryInlineMethod.doInlining.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:5984:11)
#33     KernelSsaGraphBuilder._inlinedFrom.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:926:21)
#34     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#35     KernelSsaGraphBuilder._inlinedFrom (package:compiler/src/ssa/builder_kernel.dart:924:14)
#36     KernelSsaGraphBuilder._tryInlineMethod.doInlining (package:compiler/src/ssa/builder_kernel.dart:5979:7)
#37     KernelSsaGraphBuilder._tryInlineMethod (package:compiler/src/ssa/builder_kernel.dart:5991:17)
#38     KernelSsaGraphBuilder._pushDynamicInvocation (package:compiler/src/ssa/builder_kernel.dart:5020:11)
#39     KernelSsaGraphBuilder._handleMethodInvocation (package:compiler/src/ssa/builder_kernel.dart:5245:5)
#40     KernelSsaGraphBuilder.visitInstanceInvocation (package:compiler/src/ssa/builder_kernel.dart:5259:5)
#41     InstanceInvocation.accept (package:kernel/ast.dart:5178:44)
#42     KernelSsaGraphBuilder.visitExpressionStatement (package:compiler/src/ssa/builder_kernel.dart:1765:18)
#43     ExpressionStatement.accept (package:kernel/ast.dart:8462:43)
#44     KernelSsaGraphBuilder.visitBlock (package:compiler/src/ssa/builder_kernel.dart:1731:17)
#45     Block.accept (package:kernel/ast.dart:8518:43)
#46     KernelSsaGraphBuilder._visitInlinedFunction (package:compiler/src/ssa/builder_kernel.dart:6325:30)
#47     KernelSsaGraphBuilder._doInline (package:compiler/src/ssa/builder_kernel.dart:6303:5)
#48     KernelSsaGraphBuilder._tryInlineMethod.doInlining.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:5984:11)
#49     KernelSsaGraphBuilder._inlinedFrom.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:926:21)
#50     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#51     KernelSsaGraphBuilder._inlinedFrom (package:compiler/src/ssa/builder_kernel.dart:924:14)
#52     KernelSsaGraphBuilder._tryInlineMethod.doInlining (package:compiler/src/ssa/builder_kernel.dart:5979:7)
#53     KernelSsaGraphBuilder._tryInlineMethod (package:compiler/src/ssa/builder_kernel.dart:5991:17)
#54     KernelSsaGraphBuilder._pushDynamicInvocation (package:compiler/src/ssa/builder_kernel.dart:5020:11)
#55     KernelSsaGraphBuilder._handleMethodInvocation (package:compiler/src/ssa/builder_kernel.dart:5245:5)
#56     KernelSsaGraphBuilder.visitInstanceInvocation (package:compiler/src/ssa/builder_kernel.dart:5259:5)
#57     InstanceInvocation.accept (package:kernel/ast.dart:5178:44)
#58     KernelSsaGraphBuilder.visitExpressionStatement (package:compiler/src/ssa/builder_kernel.dart:1765:18)
#59     ExpressionStatement.accept (package:kernel/ast.dart:8462:43)
#60     KernelSsaGraphBuilder.visitBlock (package:compiler/src/ssa/builder_kernel.dart:1731:17)
#61     Block.accept (package:kernel/ast.dart:8518:43)
#62     KernelSsaGraphBuilder._buildForInIterator.buildBody (package:compiler/src/ssa/builder_kernel.dart:2088:17)
#63     LoopHandler.handleLoop (package:compiler/src/ssa/loop_handler.dart:85:9)
#64     KernelSsaGraphBuilder._buildForInIterator (package:compiler/src/ssa/builder_kernel.dart:2091:18)
#65     KernelSsaGraphBuilder.visitForInStatement (package:compiler/src/ssa/builder_kernel.dart:1882:7)
#66     ForInStatement.accept (package:kernel/ast.dart:9058:43)
#67     KernelSsaGraphBuilder.visitBlock (package:compiler/src/ssa/builder_kernel.dart:1731:17)
#68     Block.accept (package:kernel/ast.dart:8518:43)
#69     KernelSsaGraphBuilder._buildGeneratorBody (package:compiler/src/ssa/builder_kernel.dart:1359:23)
#70     KernelSsaGraphBuilder.build.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:516:11)
#71     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#72     KernelSsaGraphBuilder.build (package:compiler/src/ssa/builder_kernel.dart:429:21)
#73     KernelSsaBuilder.build.<anonymous closure> (package:compiler/src/js_model/js_strategy.dart:502:22)
#74     CompilerTask.measure (package:compiler/src/common/tasks.dart:66:51)
#75     KernelSsaBuilder.build (package:compiler/src/js_model/js_strategy.dart:485:18)
#76     SsaBuilderTask.build (package:compiler/src/ssa/ssa.dart:346:21)
#77     SsaFunctionCompiler.compile (package:compiler/src/ssa/ssa.dart:80:29)
#78     OnDemandCodegenResults.getCodegenResults (package:compiler/src/common/codegen.dart:454:30)
#79     JsBackendStrategy.generateCode (package:compiler/src/js_model/js_strategy.dart:318:43)
#80     KernelCodegenWorkItem.run (package:compiler/src/js_model/js_strategy.dart:452:29)
#81     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:530:70)
#82     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#83     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:530:32)
#84     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#85     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:528:28)
#86     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#87     Compiler.emptyQueue.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:526:18)
#88     CodegenEnqueuer._forEach (package:compiler/src/js_backend/enqueuer.dart:269:12)
#89     CodegenEnqueuer.forEach (package:compiler/src/js_backend/enqueuer.dart:285:5)
#90     Compiler.emptyQueue.<anonymous closure> (package:compiler/src/compiler.dart:522:16)
#91     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#92     Compiler.emptyQueue (package:compiler/src/compiler.dart:521:14)
#93     Compiler.processQueue.<anonymous closure> (package:compiler/src/compiler.dart:547:7)
#94     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#95     Compiler.processQueue (package:compiler/src/compiler.dart:540:14)
#96     Compiler.runCodegenEnqueuer (package:compiler/src/compiler.dart:428:5)
#97     Compiler.generateJavaScriptCode (package:compiler/src/compiler.dart:331:9)
#98     Compiler.compileFromKernel.<anonymous closure> (package:compiler/src/compiler.dart:503:7)
#99     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#100    Compiler.compileFromKernel (package:compiler/src/compiler.dart:469:14)
#101    Compiler.runInternal (package:compiler/src/compiler.dart:304:13)
<asynchronous suspension>

Thanks for the bug report @danielszopa-wk
We've seen this kind of error in the past, and the cause was either a bug in our rti optimization (an optimization that removes type variables if it can determine that the type variable is not used for anything meaningful) or a bug in how data from this optimization was consumed.
There are a few things that would help us isolate this issue:

To confirm this is related to such optimizations, can you try adding --disable-rti-optimization as a dart2js flag? When that's provided I'd expect this crash will no longer occur, is that correct?
The issue may already be fixed, could you help us verify that this is not the case? We have fixed both kinds of bugs in the last year, and you may be hitting one of those fixed bugs. Is it possible for you to try a one-off compilation with the latest dev or beta version of dart2js? (we have had fixes very recently that are not in 2.16.2, but are available in 2.17.0-182.2.beta or 2.17.0-266.0.dev).
If the issue is still there in the latest dart2js, it would help to get more context about the function causing the crash and how it's used. It appears that the crash happens when compiling  lowerBound form package:collect. Could describe or show how that function is used elsewhere in your app? Is it torn off and stored somewhere and later called indirectly? Other odd patterns you can notice? This may help us isolate the issue further.

Thanks!
FYI @fishythefish

Testing with a newer version of dart2js would be great, but AFAIK all the fixes I landed for similar issues were in 2.10 or earlier, so this may be something new. It's hard to diagnose without a repro because many of the RTI optimizations are affected by the state of the whole program - things like which types all of the closures have, whether certain type tests occur anywhere in the code, etc.

To confirm this is related to such optimizations, can you try adding --disable-rti-optimization as a dart2js flag? When that's provided I'd expect this crash will no longer occur, is that correct?

I can confirm this is correct. I do not hit the error when using that flag.

Is it possible for you to try a one-off compilation with the latest dev or beta version of dart2js?

Since our codebase hasn't fully migrated to support null safety and apparently there are some breaking changes affecting analyzer and build_runner preventing us from using more recent versions of the SDK. @alanknight-wk would be able to elaborate better than I if you'd like more of an explanation.

It appears that the crash happens when compiling lowerBound form package:collect. Could describe or show how that function is used elsewhere in your app?

Ah I didn't even know that function existed. It appears we use lowerBound in two locations. The first is for the implementation of _cacheDto() which I omitted earlier:
    var n = lowerBound(_dtoList, dto, compare: _compareDtos);
    _dtoList.insert(n, dto);

The second callsite is essentially the same, just for a different object type.
From testing, it appears the two callsites are both being considered by the compiler as removing both appears to result in a successful build, but leaving one results in a failure.
I tried removing the callsites and attempted to reproduce this on a smaller scale but had no luck.
I noticed that lowerBound internally calls lowerBoundBy so I experimented and imported lowerBoundBy with import 'package:collection/src/algorithms.dart' as algo (don't do this in actual production code) and I was able to get a successful build by replacing both the lowerBound calls with:
    final n = algo.lowerBoundBy<Dto, Dto>(_dtoList, (value) => value, _compareDtos, dto);

Additionally, I think it's worth calling out that we're passing the --no-minify & -O3 flags to dart2js.

Thanks for the updates!
@fishythefish for reference this is the definition of lowerBound:
int lowerBound<E>(List<E> sortedList, E value, {int Function(E, E)? compare}) {
  compare ??= defaultCompare;
  return lowerBoundBy<E, E>(sortedList, identity, compare, value);
}

Nothing stands out to me at the moment unforutnately.

Alright one more update. I poked at this some more and I found that if I updated lowerBound locally to use (value) => value instead of identity, the error went away.
int lowerBound<E>(List<E> sortedList, E value, {int Function(E, E)? compare}) {
  compare ??= defaultCompare;
  return lowerBoundBy<E, E>(sortedList, (value) => value, compare, value);
}

@sigmundch: Yup, I was playing around with some small programs using lowerBound earlier and didn't see an obvious issue.
@danielszopa-wk: I wouldn't expect --no-minify to affect the result. I also don't expect -O3 to affect anything since --disable-rti-optimization is only set at -O0, but please let us know if you discover other optimization levels affecting the build.
My initial hunch is that this is related to closures, as was the case with similar issues in the past. removeWhere is passed the closure (d) => dto.id == d.id, but it would be great if you're able to also provide the implementation of _compareDtos. You also mentioned that lowerBound is called on a different type. Is the type essentially the same as Dto, or does it have e.g. a type argument? Is the comparison function for that type similar to _compareDtos?

I wouldn't expect --no-minify to affect the result. I also don't expect -O3 to affect anything since --disable-rti-optimization is only set at -O0, but please let us know if you discover other optimization levels affecting the build.

I actually found that -O0, -01, & -O2 all passed the build.
--no-minify didn't appear to have any impact.

it would be great if you're able to also provide the implementation of _compareDtos

Here's the two implementations:
  static int _compareDto1s(Dto1 left, Dto1 right) {
    var result = right.stringVar1.compareTo(left.stringVar1);
    if (result == 0) {
      result = left.stringVar2.compareTo(right.stringVar2);
    }
    return result;

  static int _compareDto2s(Dto2 left, Dto2 right) {
    return left.stringVar.compareTo(right.stringVar);
  }

I did think it was slightly odd that we were declaring these as static but I found that removing the static declaration didn't cause the build to pass.

You also mentioned that lowerBound is called on a different type. Is the type essentially the same as Dto, or does it have e.g. a type argument? Is the comparison function for that type similar to _compareDtos?

Neither calls specify the type argument on lowerBound (ex: lowerBound<Dto1>(...)) I tried adding them and the build still failed.

Thanks for the additional information! I'll try playing around with this some more to see if I can distill a repro.

Neither calls specify the type argument...

Sorry, what I meant was: are the two (implicit) type arguments similar types, or do they have some distinguishing features (e.g. one is generic) or major differences in how they're used?

Sorry, what I meant was: are the two (implicit) type arguments similar types, or do they have some distinguishing features (e.g. one is generic) or major differences in how they're used?

Yeah the two callsites are similar, no use of generics, they look like this:
  // Call site 1
  // _dtoList1 is a List<Dto1>
  // dto1 is a Dto1 object, no parent type like TBase is referenced / used.
  var n = lowerBound(_dto1List, dto1, compare: _compareDto1s); // See _compareDto1s in previous comment

  // Call site 2
  // _dtoList2 is a List<Dto2>
  // dto2 is a Dto2 object, no parent type like TBase is referenced / used.
  var n = lowerBound(_dto2List, dto2, compare: _compareDto2s) // See _compareDto2s in previous comment

So the fact that the breakage starts at -O3 is interesting - --omit-implicit-checks is the only flag we enable going from -O2 to -O3. This could make sense - an implicit typecheck elsewhere in the program may have been causing us to collect the missing type variable information; when those checks get omitted, the compiler crashes.
Unfortunately, I haven't yet been able to repro the crash itself, so I'm not sure why this might fix it.

@danielszopa-wk The locals which are in scope when the crash occurs look like we're setting up state for inlining. Does the problem persist if you pass --disable-inlining?

@fishythefish I can confirm the build passes if I add the --disable-inlining flag.

@danielszopa-wk Okay, great, that helps. I'll keep trying to get a repro and I may have some follow-up questions, but just a heads up that this will likely be a slow, intermittent process without direct access to an existing failure.

We just hit another instance of this issue, where quickSort from package:collection (source) was failing to compile:
org-dartlang-app:///packages/collection/src/algorithms.dart@14383+1:
Internal Error: Runtime type information not available for type_variable_local(j:type_variable(quickSort.E)) in (SyntheticLocal(result), local(quickSort#elements), local(quickSort#compare), local(quickSort#start), local(quickSort#end)) for j:method(quickSort).
…

The full error:
org-dartlang-app:///packages/collection/src/algorithms.dart@14383+1:
Internal Error: Runtime type information not available for type_variable_local(j:type_variable(quickSort.E)) in (SyntheticLocal(result), local(quickSort#elements), local(quickSort#compare), local(quickSort#start), local(quickSort#end)) for j:method(quickSort).
The compiler is broken.

When compiling the above element, the compiler crashed. It is not
possible to tell if this is caused by a problem in your program or
not. Regardless, the compiler should not crash.

The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.

Please include the following information:

* the name and version of your operating system,

* the Dart SDK build number (2.13.4), and

* the entire message you see here (including the full stack trace
  below as well as the source location above).

 Removing those usages of .slice in this package worked around the issue: https://github.com/Workiva/json_schema/pull/145/files
This specific instance only started happening when we removed code in an unrelated package (which is unfortunately private). I tried reproducing the issue in a smaller test case with the version of that package before the code was removed, but didn't have any luck.

Thanks, @greglittlefield-wf, that's helpful! Notably, both lowerBound and quickSort take a compare function with similar types (involving E), and they both delegate to other functions like lowerBoundBy/quickSortBy. Closures have been involved in similar issues in the past, so I'm curious if any of the code deleted from the unrelated package also indirectly invoked quickSort or if it involved closures with a similar type to the compare function.

@fishythefish It seems like that's still the only usage of quickSort 😕.
I tried looking for other usages of sort or compare functions and couldn't really find anything, but the deleted code apparently referenced quite a bit of code from other packages transitively, so it's possible I missed something in there.
I also diffed the dart2js output between a build with dependencies that failed unless --disable-inlining was provided, and a build that reverted those code deletions and thus didn't fail (but was also built with --disable-inlining).
I couldn't find any different calls to sort or referencing a compare function, but I did notice that ListSlice.sort and quickSort were compiled a little differently:

(note that deletion lines represent the build that exhibits this bug, and addition lines the build that does not exhibit this bug)

Thanks, @greglittlefield-wf! Between that info and what @danielszopa-wk provided, I think I might have a rough idea of what's going wrong. What's the best way to provide you with a fix to test?

@fishythefish You're welcome! Thank you for looking into it!
Oh, awesome!! If there's a branch with a fix, we should be able to compile the Dart SDK locally and give it a whirl.

Would just a change on Gerrit work? (I think @robbecker-wf might know how to patch this in.)
https://dart-review.googlesource.com/c/sdk/+/247609
If this doesn't fix the issue, we may have to do a bit of back-and-forth print debugging.

That sounds perfect—we'll give that a try!

We ended up not being able to compile that test case in the latest Dart SDK, but @alanknight-wk was able to apply the patch locally to Dart 2.13.4's builder_kernel.dart, and that appears to have fixed the issue!! 🎉

Wow, that's great to hear! As a software engineer, I'm already stunned when any of my code actually works, and this was a shot in the almost-dark. :P
Ironically, an actual repro remains the most elusive part of this fix, but I'll try to land this ASAP once I get one.

That feeling when shot in the almost-dark solutions actually work is the best 😁.
Awesome, thank you! Please let us know if we can help provide more clues around how to repro the issue.

@danielszopa-wk @greglittlefield-wf I'm starting to suspect that there's another latent bug related to instantiations which is making this tricky to reproduce. Could you uncomment the following code and share what it prints for a successful build and for a failing build? Ideally, this is with a minimal change to the code, like replacing identity with (x) => x in Daniel's example.
https://github.com/dart-lang/sdk/blob/e157e59cf8987475915369be38309fd2d19db795/pkg/compiler/lib/src/js_backend/runtime_types_resolution.dart#L1367-L1387
Depending on the size of the application, this might dump a lot of info - hopefully it isn't too sensitive.

Hmm. It is indeed a lot of data, about 1.1MB in each case. I'll have to ask about the sensitivity. However, the difference between the two is extremely slight. The passing version is created by adding the line
    _contextList.removeWhere((dto) => dto.id == context.id);
in the method
  void _replaceContext(ContextDTO context) {
In the passing version, there is an extra line for that method
k:local_function(_replaceContext.<anonymous>)

and in the failing version at the end there is
instantiationsNeedingTypeArguments: {1}
org-dartlang-app:///packages/collection/src/algorithms.dart@2303+1:
Internal Error: ...

where in the passing version it still lists
instantiationsNeedingTypeArguments: {1}

but then succeeds.

Thanks for looking into it, @alanknight-wk. I'm going to mark this issue closed for now since it sounds like the CL fixes the issue and we don't have a repro to investigate further. There have been some minor changes to the way we handle generic instantiations since 2.13.4 as well, so that might make it difficult to isolate a repro as well. Please feel free to reopen or file a new issue if you run into this again.


Correct target for FC

Please help me with my FC target choice
My FC - Mamba F722 mini MK2
is it the same as the target into qicksilver app - Mamba F722_i2C ?
Thanks for your help
Id love to try this configurator

yes, we try to match the betaflight targets wherever it makes sense.
So MAMBAF722_I2C is the correct target.
General questions like this are best asked on discord


< and > should not appear as it is

ℹ Computer information

PowerToys version: 0.25.0

PowerToy utility: FancyZones, Keybaord Manager

Language: Korean

📝 Provide where the issue is / 📷 Screenshots

❌ Actual phrase(s)

< should be shown as "<" in my quess
> should be shown as ">" in my quess

✔ Expected phrase(s)
The string should express Shift key, not showing character incoding string.

odd, the english doesn't have the quotes, lemme look at why this is happening

Looks like only the KO lcl does this.
https://ceapex.visualstudio.com/CEINTL/_workitems/edit/334958

Great news!  This was resolved in the newly released 0.33 version of PowerToys!  Head to https://aka.ms/installpowertoys to grab latest.


event bind name not support chinese characters

Version
2.6.11
Reproduction link
https://stackblitz.com/edit/js-bafxzt
Steps to reproduce
<a @click="点击">btn1
<a @click="点击($event)">btn2
<a @click="onClick">btn3
methods:{
点击:function(e){
},
onClick:function(e){

}

}
What is expected?
btn1 event not work
What is actually happening?
write $event in console

Duplicate of https://github.com/vuejs/vue/issues/6975


Does the find method use multiple images for same identity of person or not?

What does the following statement mean the readme doc
Even though face recognition is based on one-shot learning, you can use multiple face pictures of a person as well.
Will the multiple images does not add any value/benefit in  recognition task here?
Here it was mentioned that it does not use multiple images.

One image for one identity is enough, still you can have many.


Feature: Randomly assign reviewers for dependabot PRs

To handle the volume of dependabot PRs, setup a rule/workflow such that incoming dependabot PRs will be randomly assigned a reviewer. It will be the assigned reviewer's responsibility to make sure the PR is safely merged into main.
Not sure if this is easy to setup. I found this tool which claims to do the exact thing though - https://mergify.io/.

Would a potential solution be to create a team, add that team as a CODEOWNER, and then specify the team name in a "reviewers" section in the dependabot.yml, as described here: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers?

Closing as we already use a team in our CODEOWNER file and recently turned on the review auto-assignment feature.


request: recurring $50/month to fund experimental project for container distribution

Description:
SIG k8s Infra is currently looking at options that will help reduce the cost burden of container distribution. We want to test 2 approaches:

synchronize blobs of the Kubernetes container images to a AWS S3 bucket and make them available to AWS customers
distribute container images using a Lambda function. The lambda function will act as a proxy in front of k8s.gcr.io.
A funded AWS account is needed to do some tests.

Requesting SIG: sig-k8s-infra
Cost:

Frequency: monthly
Scale function:
cost increase is not expected here. It could be the result of hidden costs associated with using AWS services.

SIG approval list archive URL: https://github.com/kubernetes/k8s.io/issues/1834
Owners for renewal: sig-k8s-infra
Cancellation criteria: Unable to properly distribute Kubernetes container images from k8s.gcr.io

/committee steering

/sig k8s-infra
cc @dims

+1 from me.

+1

As a test of the pipeline can someone from steering make a request for this $50 via CNCF.io/credits?

+1

@hh CNCFSD-1060 is the service desk request.

+1 for Steering + @kubernetes/release-engineering!

@ameukam +1 from the credits side of the house, do you need any assistance with setting the account up?

@ameukam +1 from the credits side of the house, do you need any assistance with setting the account up?

@idvoretskyi I can set up an account and give you the account id for Org invitation or give you an e-mail address. WDYT ?

I think @hh will take case of everything needed here.

+1

The creation of the google group, to grant access to the account / OU is here:
https://github.com/kubernetes/k8s.io/pull/3301

thanks for the update @hh

The account is created and I confirm we have access to it.
/close


Apim 312 migrate plan p4

Issue
https://gravitee.atlassian.net/browse/APIM-312
Description

finish migration of plan list page
finish migration of plan create/edit page
small improvement

/!\ No support for api v1 is made. because is removed in next 3.21.x
Additional context

🚀 CI was able to deploy the build of this PR, so you can now try it directly here
Notes: The deployed app is linked to the management API of APIM master. (Same login and password as APIM master)

📚  View the storybook of this branch here

ok i merge this one and open a new one to add next sruff to disabled plan when origin is k8s


Add "breadcrumb-nopointer" and "breadcrumb-nodivider" classes to hide the breadcrumb pointer shape and divider at the end a breadcrumb item.

Completed.


Remove JsonSerializeOptions QuoteKeys for NLog 5.0

For NLog 5.0 then we should remove the option to generate invalid Json.

Also consider to remove JsonSerializeOptions.Format since it doesn't make sense for a Json-Serializer to format all properties with the same Format.
If needing special formatting of a single value, then one should format before calling SerializeObject

For NLog 5.0 then we should remove the option to generate invalid Json.

Unquoted keys are accepted by almost every library? Yet it's not in the specs, but the specs are to conservative (comments aren't either in the JSON specs, or trailing commas...)

NLog is still a logging-library, so not a big fan of supporting special Json-options that are never used.

This is how appsettings.json editor looks like:

Like that the fallback solution to exotic features is just to override the Json-serializer.

Unquoted keys is far from exotic.

This is how appsettings.json editor looks like:

Yes, I know it's not technical correct. (unfortunate!).
Libs and platforms that support unquoted keys:

ASP.NET MVC modelbinders (from Microsoft self)
JSON.NET

consider to remove JsonSerializeOptions.Format since it doesn't make sense for a Json-Serializer to format all properties with the same Format.

Agree on that, but we need support for SerializeObject(2, format) I guess

but we need support for SerializeObject(2, format) I guess

When does that happen?

JSON.NET is like the mother of all exotic Json-quirks. It has been down every ditch, and have implemented settings to support those ditches. But their default value is to avoid the ditch.
Cannot see it as being a recommendation for NLog to support the QuoteKeys=false ditch.

When does that happen? Think Json is by default culture invariant (xml-style)

Good one.

PS there a many other who like unquoted keys (including me, I could quote when I need so). Also see this: https://json5.org/

PS2, performance wise, quote=false is much faster probably ;)

PS2, performance wise, quote=false is much faster probably ;)

Think the performance is the same. But all those if-conditions whether to include quotes or not, are hurting performance :)

How much does the complexity suffer for quotekey =false?

How much does the complexity suffer for quotekey =false?

Probably gives a complexity point for every method that makes decision based on it.

Also see this: https://json5.org/

Didn't know of this religion. Then I guess all arguments are futile :)
So change the issue to remove the Format-parameter?


libav: libvpx >= 1.8 drops some formats

Motivation for this change
The recent upgrade of libvpx to 1.8/1.9 broke libav_12.
nix build nixpkgs.libav_12

...
  libavcodec/libvpx.c:66:42: error: 'VPX_IMG_FMT_RGB555_LE' undeclared (first use in this function); did you mean 'AV_PIX_FMT_RGB555LE'?
     66 |     case AV_PIX_FMT_RGB555LE:     return VPX_IMG_FMT_RGB555_LE;
        |                                          ^~~~~~~~~~~~~~~~~~~~~
        |                                          AV_PIX_FMT_RGB555LE
  libavcodec/libvpx.c:70:42: error: 'VPX_IMG_FMT_444A' undeclared (first use in this function); did you mean 'VPX_IMG_FMT_I440'?
     70 |     case AV_PIX_FMT_YUVA444P:     return VPX_IMG_FMT_444A;
        |                                          ^~~~~~~~~~~~~~~~
        |                                          VPX_IMG_FMT_I440
  make: *** [Makefile:48: libavcodec/libvpx.o] Error 1
  make: *** Waiting for unfinished jobs....

The issue, as can seen above, is that some libvpx has dropped some of its previously supported formats. The effected code just converts VPX image format constants to AV image format constants, and the solution, as found in this patch here is to simply #if out the conversion lines for the dropped formats when building against the newer libvpx.
This simply results in the case falling through to the default none format constants and follows the existing #if statements found in the code for differences in various other versions of libvpx.
This pull request adds the referenced patch for libav_12. It is applied unconditionally to libav_12 as libvpx <= 1.7 (the ones that had the dropped formats) were removed with the libvpx upgrade that causes this issue.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 111172 run on x86_64-darwin 1

1 package marked as broken and skipped:

libav_12

Result of nixpkgs-review pr 111172 run on x86_64-darwin 1

1 package marked as broken and skipped:

libav_12

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111172 run on x86_64-linux 1

2 packages built:

libav_12
untrunc

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111172 run on x86_64-linux 1

2 packages built:

libav_12
untrunc

CCing @Ericson2314 @vcunat as recent commiters from the git log as this simple fix will probably go nowhere without some actual people.

CCing @Ericson2314 @vcunat as recent commiters from the git log as this simple fix will probably go nowhere without some actual people.

without some actual people.

I am a real person and already took a look at the diff but I can't really tell if the patch is good or not.

without some actual people.

I am a real person and already took a look at the diff but I can't really tell if the patch is good or not.

Thank @SuperSandro2000. Sorry for having thought you were a bot. :grinning:

Thank @SuperSandro2000. Sorry for having thought you were a bot. :grinning:

Thanks. I was using it because it was listed as a requirement of ovito a couple of years ago when I first packaged it (I filed this bug in order to submit the ovito package). After your message, I looked into it, and I see it was switched to ffmpeg last year. I'll update and switch it over. :+1:

Thanks. I was using it because it was listed as a requirement of ovito a couple of years ago when I first packaged it (I filed this bug in order to submit the ovito package). After your message, I looked into it, and I see it was switched to ffmpeg last year. I'll update and switch it over. :+1:


add pictures for DLP for RPA

@lanlanlee2008  I believe we got these changes already so am closing this PR. Please reopen if you think we need it.


collection iterator

What do we think about turning FeatureCollection and GeometryCollection into iterators?
I think this:
for feat in fc:
    ...

is nicer than this:
for feat in fc.features:
    ...

@geospatial-jeff seems pretty nice; are there any examples of similar libraries having this sort of API (shapely, pygeos, etc)?

Yeah all shapely multipart geometries have this feature (https://github.com/Toblerity/Shapely/blob/master/shapely/geometry/base.py#L892-L908)

https://github.com/developmentseed/geojson-pydantic/pull/12 work or need something fancier?


Security enhancements

Security fixes based on ansible-lint scan
Improve monitor and logging deployment consistency
Update dependencies

Watching this one


[ ERROR ] Taking listener 'MyListener' into use failed:  Listener 'MyListener' does not have mandatory 'ROBOT_LISTENER_API_VERSION' attribute

Getting an error while running a listener example from RF Userguide (Version 3.0)
Content of MyListener.py:
import os.path
import tempfile

class PythonListener:
	ROBOT_LISTENER_API_VERSION = 2
	def __init__(self, filename='listen.txt'):
		outpath = os.path.join(tempfile.gettempdir(), filename)
		self.outfile = open(outpath, 'w')

	def start_suite(self, name, attrs):
		self.outfile.write("%s '%s'\n" % (name, attrs['doc']))

	def start_test(self, name, attrs):
		tags = ' '.join(attrs['tags'])
		self.outfile.write("- %s '%s' [ %s ] :: " % (name, attrs['doc'], tags))

	def end_test(self, name, attrs):
		if attrs['status'] == 'PASS':
			self.outfile.write('PASS\n')
		else:
			self.outfile.write('FAIL: %s\n' % attrs['message'])

	def end_suite(self, name, attrs):
		self.outfile.write('%s\n%s\n' % (attrs['status'], attrs['message']))

	def close(self):
		self.outfile.close()

Command to start test in TESTS folder:
robot --listener MyListener TESTS

Output:
$ robot --listener MyListener TESTS
[ ERROR ] Taking listener 'MyListener' into use failed: Listener 'MyListener' does not have mandatory 'ROBOT_LISTENER_API_VERSION' attribute.
==============================================================================
TESTS
...

The reason is that you take the module to use as a listener, not the class. Change the module (i.e. file) name to match the class name and Robot ought to realize that you want to use the class as a listener. Alternatively you could import the listener by including both the module and class name in the listener name. Please let us know if you see that related docs could be enhanced somehow.

@pekkaklarck Thank you so much. Once again you brought me back on the right track. Did PR #2388 to enhance related docs.

Cool, thanks for the doc PR. I comment it separately.


Payment - web - stats?

2017-03-11 15:42:21 [Payments]  [zdash] Could not update zcash stats to redis {"command":"EXEC","code":"EXECABORT","errors":[{"command":"HSET","args":["zdash:stats","networkSols"],"code":"ERR","position":2}]}

flushall did not work

update z-nomp and set zdash's coin to zdash, https://github.com/z-classic/z-nomp/commit/017731bbe71f08ae14a901f4932f762000155f33

No, its not working, did fresh install/compile/etc

yep, couldn't get it to refresh statics on rpc/web (just in Zdash) (Zec, Zcl are working ok) (Komodo won't run with this line // generate the fees and coinbase tx var blockReward = (this.rpcData.miner + this.rpcData.founders) * 100000000;)


[DOC] Point users to UCX 1.11.2

UCX 1.11.2 is fixing two bugs we have seen:

When running on a machine that has a non-RDMA NIC (i.e. an ethernet-only device used as a the primary NIC for the executor), and a secondary RDMA NIC, we see failures since UCX would skip a step to register memory against the non-RDMA NIC and fail when attempting to use it later after realizing it exists: https://github.com/openucx/ucx/pull/7436.

Seen in the DGX-2, an error where when we have so many GPUs (16) and nics (8) and the various transports that UCX supports, that an internal datastructure in UCX could not hold all of this: https://github.com/openucx/ucx/pull/7398

UCX 1.11.2 is in RC state, with the first RC out: https://github.com/openucx/ucx/releases/tag/v1.11.2-rc1. This issue is to change the docs to point to UCX 1.11.2, at least to the RC.

We decided to move this to 21.12, because there is no official version of UCX 1.11.2 out there (just an RC).

The 1.11.2 version is going to be moved earlier, so we think this fits 21.10.


hi my html file suddenly became , unknown encoding format. What is the solution to retrieve my file. I have lot of contents in my html file.

I worked a lot in my html file and it suddenly give this error all of the sudden. How to retrive my file back. need assistance.

jobPosted.html.txt
I tried opening my html in notepad, still its empty. Need assistance

can you tell me how you fix this problem i had the same in css file

I have the same problem, did you guys ever hear back? @sunithaanilkumar @ghaithdiab Thanks!

Hi
i am sorry i did not find solution for this issue i write again my file

من: Nathan F Wade<EMAIL_ADDRESS>تم الإرسال: 24 نوفمبر, 2018 02:01 ص
إلى: adobe/brackets
نسخة: ghaithdiab; Mention
الموضوع: Re: [adobe/brackets] hi my html file suddenly became , unknown encoding format. What is the solution to retrieve my file. I have lot of contents in my html file. (#14347)
I have the same problem, did you guys ever hear back? @sunithaanilkumarhttps://github.com/sunithaanilkumar @ghaithdiabhttps://github.com/ghaithdiab Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/adobe/brackets/issues/14347#issuecomment-441334462, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AprQNnmSP2pr_RRqyE2rqiM6JKgT1N3Fks5uyJpkgaJpZM4UG5h1.

I faced the same issue while trying to open html file using brackets

I had same problem! Just click uninstall brackets )

Same problem

Same problem here Brackets really needs to do something I worked a lot on the project! :(


improve example for using iterators

user report:
in https://lancedb.github.io/lancedb/guides/tables/#using-iterators-writing-large-datasets, we show the following example:
import pyarrow as pa

def make_batches():
    for i in range(5):
        yield pa.RecordBatch.from_arrays(
            [
                pa.array([[3.1, 4.1], [5.9, 26.5]],
                        pa.list_(pa.float32(), 2)),
                pa.array(["foo", "bar"]),
                pa.array([10.0, 20.0]),
            ],
            ["vector", "item", "price"],
        )

schema = pa.schema([
    pa.field("vector", pa.list_(pa.float32(), 2)),
    pa.field("item", pa.utf8()),
    pa.field("price", pa.float32()),
])

db.create_table("table4", make_batches(), schema=schema)

It was unclear whether the value 2 in pa.list_ refers to the number of vectors or the number of dimensions since it's 2x2.
Solution: make the shape rectangular instead of a square to disambiguate.

Hi @changhiskhan, just addressed this issue in this PR: https://github.com/lancedb/lancedb/pull/533.


Feature: Replace OG image

Overview

Replaced the OG image with the one provided by the designers' team.
Assignee Checklist:

[x] The naming convention of the PR title is correct (See the comment at the top of this template)
[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[x] Double-check the "Assignee Checklist"
[x] The code follows the generic best practices and our Coding Style Guide
[x] The code is well-commented and easy to understand
[x] The UI changes accurately reflect the provided design

@kanta1207 Thank your for your prompt review!


[Enhancement] add more trace for mv preprocess

Why I'm doing:
What I'm doing:

Add more traces to the preprocessMvs step

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[x] 3.1
[ ] 2.5

@Mergifyio backport branch-3.3


:rocket: update: upgrade python and depends

Changes:

Min python version 3.8.1
Upgrade all dev dependencies
Fix main ForwardRef
Fix test tutorial with fastapi

Now with mkdocs 1.4.2 and mkdocs-material 8.5.11 the docs site is created ok without some bugs.

Should update workflows to install poetry instead of doing the workaround for installing a specific version of poetry and poetry-core for 3.6.
publish.yml was not updated 3.7 -> 3.8.
Dockerfiles were not updated 3.7 -> 3.8.
Check for != '3.6.15' in test.yml not removed.
TODO regarding python 3.6 removal in lint.sh should be fixed.
There are still dependencies for python 3.6 in pyproject.toml, async_generator and async-exit-stack.
expression.py.jinja2 should be updated to remove the version check.

All changes are resolved. Thanks for the observations.


[KNI][release-4.15][manual] cmd: dump version on startup

log the component version first time as startup to make the troubleshooting (a bit) easier.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>(cherry picked from commit 37426d9020a3bd19e6e3abb605e96f2e9addbeb7)
manual cherry pick of #225

/cc @shajmakh

/lgtm


Read Arguments from STDIN

When calling QPDF from an external process it would be useful to push arguments via standard input. This would help with automated merges that are called on a set of files with unpredictable length and unpredictable file names.

I'd like to second this feature request. I'm using qpdf in PHP via the CLI and would love to be able to use STDIN instead of creating a temporary file.
Similar to many other command line utilities, I'd like to propose the ability to simply supply a dash (-) to tell qpdf to read the input from STDIN, e.g. to read from STDIN and write to STDOUT:
cat foo.pdf | qpdf --linearize - -

qpdf can already take - as an output file to write to stdout, but the PDF file format fundamentally can't work with a non-seekable input, so reading from stdin is not possible. Any program that is able to read PDF files from stdin is doing something internally like writing it to a temporary file or loading it into memory.
However, reading arguments from stdin is certainly doable.

I see, thanks for the explanation!

I think adding the ability to read arguments from a file or from stdin would be a good enhancement. I'm thinking about the more-or-less standard convention of @file or perhaps @- to read from STDIN.

Version 7.0.0, to be released later this summer, will allow @filename and @- as arguments to mean reading args from a file and stdin respectively. We don't look for @ recursively. In these files, each line is taken to be a separate option. This allows an arbitrary number of arbitrarily long lines, and the lines can contain spaces, etc. No interpolation is done on the lines. I think it should satisfy this requirement. I will be pushing the change to master momentarily.

Sorry it took soooo long.

I have been trying to use the @filename as a command line argument.
However I could not use it for --encrypt. Could you give me a guidance, please?
Here what I tried:
bash-3.2$ cat encrypt_params.txt
--encrypt helloworld12345 helloworld12345 40 --
qpdf @encrypt_params.txt test_input.pdf test_passwd.pdf
qpdf: unknown option --encrypt helloworld12345 helloworld12345 40 --

Usage: qpdf [options] infile outfile
For detailed help, run qpdf --help

Thanks in advance. Look forward to hearing from you.

You need to put each command line argument on a separate line. This is in the docs. Sorry if it's unclear. So your file should contain
--encrypt
helloworld12345
helloworld12345
40
--

This makes it possible to specify arguments that contain spaces.

Aha..Thanks for the example 🤓


libmariadb build failure - Applying patch failed!!

Environment

OS: Windows 7 Ultimate SP1 (OS Build 7601) x64
Compiler: VC 2017 v15.9.18 Toolset v141

To Reproduce
Steps to reproduce the behavior:

./vcpkg install libmariadb
See error
Error: Building package libmariadb:x86-windows failed with: BUILD_FAILED

Failure logs
failure.log

Duplicated to https://github.com/microsoft/vcpkg/issues/10024.

-- Extracting source C:/Users/Adorius Black/vcpkg/downloads/MariaDB-mariadb-connector-c-8e9c3116105d9a998a60991b7f4ba910d454d4b1.tar.gz
-- Applying patch md.patch
CMake Error at scripts/cmake/vcpkg_apply_patches.cmake:50 (message):
Applying patch failed.  Patch needs to be updated to work with source being
used by vcpkg!
Call Stack (most recent call first):
scripts/cmake/vcpkg_extract_source_archive_ex.cmake:134 (vcpkg_apply_patches)
scripts/cmake/vcpkg_from_github.cmake:139 (vcpkg_extract_source_archive_ex)
ports/libmariadb/portfile.cmake:8 (vcpkg_from_github)
scripts/ports.cmake:90 (include)
Error: Building package libmariadb:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: libmariadb:x64-windows
Vcpkg version: 2020.02.04-nohash


Create DIY coverage checking class

There should be a class for convenient and possibly consistent coverage testing. It could, for example, write branches taken to a specified file.

The resulting file can be checked for the number of unique lines using sort ips.txt | uniq -c (bash command, there is probably something similar for Windows). See https://stackoverflow.com/questions/15984414/bash-script-count-unique-lines-in-file


Non-default types cannot be safely serialized by default

When settings contains types that are not covered with to_django it is passes as-is to underlying variables. So if settings contains any of these types (and much more, any custom):

Url
NameEmail
Emailstr
IPv4Address
IPv6Address

it will lead to unexpected behaviour since Django code and apps knows nothing about these types. This can be easily solved by calling settings.model_dump(mode="json") instead of settings.model_dump() (which targets mode="python" by default), however I have no idea how to force lazy gettext strings to pass this call. Or if that's even possible.
pydantic_core._pydantic_core.PydanticSerializationError: Unable to serialize unknown type: <class 'django.utils.functional.lazy.<locals>.__proxy__'>

Nah. That's not a good idea to use mode="json" since we may want to use callable(s) in settings. So probably the only viable solution is to include all known types from pydantic_core and modify to_django so it can handle additional types conversions.

So probably the only viable solution is to include all known types from pydantic_core and modify to_django so it can handle additional types conversions.

Do I understand correctly that you're suggesting adding custom handlers for non-standard Pydantic types (like Url, NameEmail, etc.), similar to how we handle SecretStr and SecretBytes here?
https://github.com/erhosen-libs/pydjantic/blob/0a981396572909b40b1e278b4020a7560c741c93/pydjantic/pydjantic.py#L55-L56
If that's the case, I have no objections. It seems like a logical development for the library, and I'd be grateful if you could create the appropriate patch to address your issue.
In turn, I’ll promptly review it and release a new version to PyPI!

Yeah. Unfortunately I haven't found any better solution other than handling custom types manually within 'to_django' function. It's not nice but there is no better way to do it at the moment.


Monitor for clients

The monitor (middleware) concept could be extended to clients.
c := restful.NewClient()
c.Monitor(pre0, post0).Monitor(nil, post1) // Similar function types as for the server.

// One could add data to ctx, if monitor needs that.
c.Get(ctx, ...)
// Internally Do() could just call pre and post, if not nil.

Done in v1.5.0.


Voice input and output.py

Script Title -voice input output.py
Hi guys I had created "voice input output.py" for you repo please review the code and add if you liked it .
Thank You happy coding guys.

Mention this issue number in your Pull request.

Issue #294


Rust crate updates

Closes #189.

Thanks, we literally just made a issue for this thinking we'd have to figure it out! :laughing:
We can probably close that now and merge this! :tada:

@str4d I'm having troubles to compile this on rustc 1.40.0, is the assertion issue fixed on with this pr as well?

try cargo clean and  then cargo update, I suspect that might fix that issue.

@str4d I got it to build by upgrading the rust compiler to 1.46.0, but then I got into the assertion issue #177


ctzpos-cups: init at 1.2.4

Motivation for this change
This pull request adds the package ctzpos-cups, which provides CUPS PPDs and filters compiled from source for CITIZEN-brand POS printers. Tested with a CITIZEN CT-S310II.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Closing due to inactivity from author.


Fix overnight staking flow tests

Recent token FE rework checks are failing for some tests, need to look into waiting for elements to appear before peroforming checks


Duplicate area+collision shape causes a bug

Godot version:
3.2 beta3
OS/device including version:
ubutu 18.04
Issue description:
When you duplicate a area with a child of collision shape, and then modify the shape of the copy, the original one modify too.

That's because Shape is a resource and when you duplicate the Area, both copies will share the same shape. To avoid this, make the shape unique by right-clicking it and using "Make Unique".
This is intended behavior.


Add Discover Table Tests

Description
This adds functional tests for the issues described in https://github.com/opensearch-project/OpenSearch-Dashboards/issues/6280.
Issues Resolved
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/5713
Issues Still Pending (Sub Issues within the Test Suite are mentioned within brackets)

Function Test Suite 2: Copy data without extra data: No easy way to test copying data to clipboard in cypress
Function Test Suite 5: Left Navigation Display (Should display Unknown type field properly in left navigation): Niche scenario
Function Test Suite 6: Saved Search Embeddable in Dashboard (When load a saved search in dashboard, sort should be loaded properly Issue: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/5933) : Issue still open hence couldn't be tested
Function Test Suite 10: Saved query (From index manage page (saved object), click a saved query object created from Discover/Dashboard/Vis can load Discover with proper query and filter Issue: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/5942) : Issue Still open hence can't be tested

The test suites are divided across two files discover_table and discover_advanced_settings. All the functional tests related to the Advanced Settings are grouped in discover_advanced_setting while the rest are part of discover_table settings.
Tests when run without security
https://github.com/opensearch-project/opensearch-dashboards-functional-test/assets/38322563/b7d4ead2-99e2-45e0-a7eb-79d545a01e8a
https://github.com/opensearch-project/opensearch-dashboards-functional-test/assets/38322563/8a636136-6473-4c46-ada7-0ef06a67ad51
Tests when run with security
https://github.com/opensearch-project/opensearch-dashboards-functional-test/assets/38322563/35cae8a4-70b8-4d97-8154-252f44c2e9ce
https://github.com/opensearch-project/opensearch-dashboards-functional-test/assets/38322563/1eded379-9e6c-4cb9-9074-9cd02493e4a1
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@SuZhou-Joe I have updated the tests to fix the failures. The newly added tests are now passing for both with and without security enabled.

@LDrago27 Thanks for addressing all the failed cases.


doc: Update README With Link To Manual Test Cases

updating README manual test cases link

Resolves: docs/readme-manual-test-link-fix

current link seems to 404, but perhaps it shouldn't? I'm kinda figuring perhaps the github.io link would be more preferred but - open to iterate / change or update this pr in any way :smile:

@noahgildersleeve - oh! I didn't know there was #192 open, I should of audited the issues prior to opening up the PR but you're right, at least in the meantime this link-fix can act as a bandaid


QUESTION: is this properly maintained?

Hi, i want to say i love the this lib and I would really love to use it longterm but amount of the PRs and issues is worrying for a project like this.
Is it actively maintained? Do you need help? i wouldn't mind sponsoring you if you choose to do so.

There's little chance of Ramda switching implementation to TS.  See the reasons and discussions in #2976.  But we are looking at how to improve the TS support.
I'd suggest that most of the Ramda tutorials (at least those since 2015) are probably still fairly accurate.  And, as a library, it will never have the sort of documentation that framework have and need.  There is room -- plenty of room! -- to improve the documentation.  And tutorials are among the best ways to do that.  That is one way that you could easily help.  Write a tutorial about some part of Ramda that interests you but you don't think is well-documented.  Tell us about it and we'll add it to the wiki.  Or simply add a wiki page with it if you don't want to host your tutorial somewhere else.


Connect front-end to R&R server

Updated server port from 3000 to 8000 because 3000 needs to be used for other component's API endpoints
Updated a few returning data types in order for front-end to be loaded the same
Trello: https://trello.com/c/PZp7uOUQ

 Connect front-end to R&R server


Add changes for upgraded help command to developer guide

Updated section looks like the above image. Will remove code blocks in future commits if deemed too verbose.

It is highly discouraged to put code blocks in developer guide, because it can get outdated quickly. It is better to use a class or object diagram to show this instead.


onFail()

No execution of added code within onFail() method. Even the Toast "Wrong password" does not appear...

No execution of added code within onFail() method. Even the Toast "Wrong password" does not appear...


Version in the user-agent header should be generated automatically

We should use https://github.com/aspnet/SignalR/blob/7b0be52c545bc20f7402ed1b58c5ff8f99c2030f/version.xml#L6 to generate the User-Agent header. Currently the version is hardcoded - it is fragile and will very likely be missed when we move to a newer version/version suffix.
(We already use this to generate version for the npm module for the client: https://github.com/aspnet/SignalR/blob/cdbb13de66b068015d068e5fab67e4e6ab42d3da/client-ts/Microsoft.AspNetCore.SignalR.Client.TS/Microsoft.AspNetCore.SignalR.Client.TS.csproj#L42)

All we need to do here is make sure the AssemblyInformationalVersion ends up in the User Agent from the client.


Create Tom and Jerry.py

Please read the new Contributing.md and make changes in your PR accordingly. Thank you


refactor: replace manual async IPLD recursion with a stream

Summary of changes

Changes introduced in this pull request:

Replace recurse_links_hash with stream_chain as it is much nicer.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

I changed the progress log message. Need re-review.


508: Update Focus in the Create/Edit/View Method

Issue:
MP Workspace - Create/Edit Modal - Making a parameter select shifts focus to the close button instead of keeping focus where it is.
Stepps to Recreate:

Login to ECMPS, navigate to MP an Select, checkout and open a Configuration
From the Section dropdown, Select Method
Click on View/Edit or Create Method to open the modal
Make a selection in the Parameter dropdown
Observe that the focus immediately goes to X. It should stay on the selection made for Parameter

Testing complete, focus is now staying on the parameter dropdown


Remove the settings for the coverage column in the dashboard view set…

I have reviewed this codes.


Form input :number used wrong

fixed
see material-components/#!/forms/showcase
use it with type="number"
<md-input :value.sync="age" :number="true" type="number">
    Age
</md-input>


merge for  v0.3.1rc

Codecov Report

Merging #22 (ff2a77a) into master (8d7afb7) will increase coverage by 1.08%.
The diff coverage is 99.58%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   97.72%   98.81%   +1.08%
==========================================
  Files          40       40
  Lines        4401     4710     +309
==========================================
+ Hits         4301     4654     +353
+ Misses        100       56      -44

Flag
Coverage Δ

unittests
98.81% <99.58%> (+1.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pDESy/model/base_workflow.py
97.00% <ø> (+2.00%)
:arrow_up:

setup.py
0.00% <ø> (ø)

tests/model/test_project.py
97.34% <ø> (-0.10%)
:arrow_down:

pDESy/model/base_project.py
98.61% <97.22%> (+8.24%)
:arrow_up:

pDESy/__init__.py
100.00% <100.00%> (ø)

pDESy/model/base_component.py
100.00% <100.00%> (ø)

pDESy/model/base_facility.py
100.00% <100.00%> (ø)

pDESy/model/base_factory.py
100.00% <100.00%> (ø)

pDESy/model/base_organization.py
100.00% <100.00%> (ø)

pDESy/model/base_product.py
100.00% <100.00%> (ø)

... and 23 more

Continue to review full report at Codecov.

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


INT B 18889 remove prime ability to update destination address for approved shipment outside correct endpoint

Agility ticket
Summary
When a shipment is in an APPROVED status, we do not want the Prime to have the freedom to update the destination address of a shipment without the TOO approving the change first.
Right now there are two endpoints where the destination address can be updated without the respective logic checks that are in the updateShipmentDestinationAddress endpoint. This PR does the following:

when calling the updateMTOShipment and updateMTOShipmentAddress endpoints, implemented logic to check the shipment status and if the shipment's destination address is provided in the payload
handled error return to inform the user to use the updateMTOShipmentDestinationAddress endpoint instead when trying to update the destination address
updated tests to reflect changes in logic

How to test

Access MM as prime
Find a move with an approved shipment
Try to edit the destination address for the shipment by clicking the Edit and submitting the form
You should get back an error

Screenshots

Update Shipment Destination Address should be functional on an approved shipment right?

Should Udate Shipment Destination Addressbe functional on an approved shipment?

Yessir


chore: legacy babel build for cjs and esm

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.02 :tada:

Comparison is base (cb76da3) 88.37% compared to head (c82be07) 88.39%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##            alpha    #5139      +/-   ##
==========================================
+ Coverage   88.37%   88.39%   +0.02%
==========================================
  Files          78       78
  Lines        2865     2870       +5
  Branches      811      812       +1
==========================================
+ Hits         2532     2537       +5
  Misses        282      282
  Partials       51       51

Impacted Files
Coverage Δ

.../src/rules/exhaustive-deps/exhaustive-deps.rule.ts
100.00% <100.00%> (ø)

...ackages/eslint-plugin-query/src/utils/ast-utils.ts
66.14% <100.00%> (+1.10%)
:arrow_up:

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

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


Discrepant results between similar Salamae genomes

Hello,
We've isolated some subsp salamaes for one of our projects. I have a few questions about the SISTR output for these isolates:

sample
cgmlst_found_loci
cgmlst_matching_alleles
cgmlst_subspecies
o_antigen
serogroup
serovar
serovar_antigen
serovar_cgmlst
O antigen prediction
H1 antigen prediction(fliC)
H2 antigen prediction(fljB)
Predicted identification
Predicted antigenic profile
Predicted serotype
average_depth
snp_count
indel_count
N_count
reads_cov
Reference
Organism from Esmie
Salmonella genus

CQJ13L
330
129
salamae
-
B
II 1,4,12,[27]:a:z39|II 4:a:z39
II 1,4,12,[27]:a:z39|II 4:a:z39
II 1,4,[5],12,[27]:b:[e,n,x]
4
a
z39
Salmonella enterica subspecies salamae (subspecies II)
4:a:z39
II [1],4,12,[27]:a:z39
70.3072
40928
0
0
89.86
GCF_019339485.1

Salmonella species

CQJ127
330
134
salamae
-
B
II B:-:e,n,x
II B:-:e,n,x
II 1,4,[5],12,[27]:b:[e,n,x]
4
z
e,n,x
Salmonella enterica subspecies salamae (subspecies II)
4:z:e,n,x
II [1],4,12,27:z:e,n,x
62.4964
40202
0
0
89.21
GCF_019339485.1
Salmonella Typhimurium
Salmonella typhimurium

Neither of these samples have a prediction in the o_antigen column, but when I blast them against your database, they have quite a good match (97% similarity, >99% coverage) to "304|584|1,4,12,27|B" from the wzx database. Is this match not good enough to call the O antigen? Or is there uncertainty about record 304?
They  are quite similar results across most fields (and for my blast results against the wxy and wxz databases), but they have different results in the output. How come?

Here are the fasta files, in case you want to dig in.
https://www.dropbox.com/scl/fi/ppkiflqyvtwrn28nah9s6/CQJ127_S25_L001.fna?rlkey=t19wktth1uguutnmqkuej3jq7&dl=0
https://www.dropbox.com/scl/fi/k4yg4iwo1k0mjdinyahx0/CQJ13L_S23_L001.fna?rlkey=woawgupve273z3b7y7tx2xipi&dl=0
Thanks,
Phil

Thanks very much, apologies for the slow response!

Partially addressed in new release v1.1.3

Great, thanks.
On Tue, 26 Nov 2024 at 20:33, Kirill Bessonov @.***>
wrote:

Closed #57 https://github.com/phac-nml/sistr_cmd/issues/57 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/phac-nml/sistr_cmd/issues/57#event-15440731418, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAT6FEQN7JNTNZCBRWRX6RT2CS5IZAVCNFSM6AAAAABNSXCQQ2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGQ2DANZTGE2DCOA
.
You are receiving this because you authored the thread.Message ID:
@.***>


On Get started page, the point 4 is still "Run your app"

I opened https://github.com/phonegap/phonegap-docs/issues/153 where I said that "Step 4: Run Your App" should be "Step 4: Preview Your App"
It was fixed on the docs section, but the Get started page (http://phonegap.com/getstarted/) still shows "Run your new app on your device".
I think it should be changed there too.

It says preview now, closing...
But I still see a lot of people confused because 3rd party plugins don't work on the developer app.

Agreed. I'm going to stub out the more complete docs that would help clear this up.


add spenc and test_spenc

Could you please help me check why the solution got by checks is different from what I got from my local machine? I used the same code and have specified random seed. @jGaboardi

i think you need to use the random_seed= argument rather than setting numpy.random.seed, since SPENC builds on a scikit-learn estimator with that option.

i think you need to use the random_seed= argument rather than setting numpy.random.seed, since SPENC builds on a scikit-learn estimator with that option.

I have the same thought.

i think you need to use the random_seed= argument rather than setting numpy.random.seed, since SPENC builds on a scikit-learn estimator with that option.

Thanks Levi!

@jGaboardi  Could you please check this error? It seems we need to update any usage of the set-env and add-path workflow commands, while I do not know where to start.
Add "/usr/share/miniconda3/condabin" to PATH Error: Unable to process command '::add-path::/usr/share/miniconda3/condabin' successfully. Error: The add-pathcommand is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting theACTIONS_ALLOW_UNSECURE_COMMANDSenvironment variable totrue. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ Set 'CONDA="/usr/share/miniconda3"' Error: Unable to process command '::set-env name=CONDA::/usr/share/miniconda3' successfully. Error: The set-envcommand is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting theACTIONS_ALLOW_UNSECURE_COMMANDSenvironment variable totrue. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ /usr/share/miniconda3/condabin/conda config --add pkgs_dirs /home/runner/conda_pkgs_dir Error: Unable to process command '::set-env name=CONDA_PKGS_DIR::/home/runner/conda_pkgs_dir' successfully. Error: The set-envcommand is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting theACTIONS_ALLOW_UNSECURE_COMMANDSenvironment variable totrue. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@xf37 I am having trouble pushing to this branch for some reason. Try swapping out - uses: conda-incubator/setup-miniconda@v2 for - uses: goanpeca/setup-miniconda@v1 on line 20 in spopt/.github/workflows/unittests.yml. Last week the GHA syntax got updated and the previous version of setup-miniconda that we were using switched repos. See pysal/spaghetti#555, pysal/libpysal#359  for background.

@xf37 We have two problems here, (1) is an easy fix and the other (2) is more involved.

We are moving away from Python 3.6 with the initial phase of dropping support for Windows. This is due directly to failures upstream with fiona, which easily remedied by excluding Python 3.6/Windows tests.
To my knowledge, we have still not verified the result from testing (here) is correct. Verifying this is critical prior to merge. Maybe we can reach out to Serge, Ran, Levi, etc. to confirm this testing result?

@xf37 We have two problems here, (1) is an easy fix and the other (2) is more involved.

We are moving away from Python 3.6 with the initial phase of dropping support for Windows. This is due directly to failures upstream with fiona, which easily remedied by excluding Python 3.6/Windows tests.
To my knowledge, we have still not verified the result from testing (here) is correct. Verifying this is critical prior to merge. Maybe we can reach out to Serge, Ran, Levi, etc. to confirm this testing result?

Thanks @jGaboardi! I would like to solve the first problem and leave the second problem as it is for now. I just talked about it with Serge and Eli. They are okay with this test file which has the same idea as it is in geosnap for now.


It's better to add azure key vault secret springboot starter dependencies in the document

If user starts from an existing spring boot project, it's not clear which dependency should be added in the project.
https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-key-vault#add-key-vault-integration-to-the-app, step 3, The Key Vault integration provides a Spring PropertySource that is populated from the values of the Key Vault. Some more implementation details are available in the reference documentation.
it goes to this link: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/spring/azure-spring-boot-starter-keyvault-secrets/README.md,
the dependency (this one is correct, same as when I use spring initializer https://start.spring.io/ to add the dependencies) shows it's
<dependency>
<groupId>com.azure.spring</groupId>
<artifactId>azure-spring-boot-starter-keyvault-secrets</artifactId>
<version>3.2.0-beta.1</version>
</dependency>
but if I click Package(Maven) on the same page, it shows another dependency:

<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-keyvault-secrets-spring-boot-starter</artifactId>
<version>2.3.5</version>
<scope>runtime</scope>
</dependency>
this causes a misunderstanding if I start from an existing project, which would be a lot of people's choice.
So please add pom settings as well in the document
<properties>
<azure.version>3.1.0</azure.version>
 </properties>
<dependencies>
 <dependency>
<groupId>com.azure.spring</groupId>
<artifactId>azure-spring-boot-starter-keyvault-secrets</artifactId>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.azure.spring</groupId>
<artifactId>azure-spring-boot-bom</artifactId>
<version>${azure.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 43e25b58-811b-ec83-0251-7a641d4a7670
Version Independent ID: 55deb14a-7feb-fcf3-95e7-5e947f5fb061
Content: Tutorial on reading a secret from Azure Key Vault in a Spring Boot application
Content Source: articles/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-key-vault.md
Service: key-vault
GitHub Login: @bmitchell287
Microsoft Alias: brendm

@KarlErickson could you please add @chenrujun as an assignee?

@chenrujun please coordinate with @lastnameholiu who has also been looking at these issues. Thanks!

I'll create PR soon

#512


Update nf-wdm-exallocatepoolwithtag.md

The change is mentioned in #442. However, I got the failed allocation with zero pool tag on Windows 10 1903 (not 1909 as stated in the issue).

Thanks for the feedback @MartinDrab.  I'd like to look into it, will circle back once I've had a chance to do that.

Sorry for the delay @MartinDrab.  I just updated the doc to read "Specify the pool tag as a non-zero character literal of one to to four characters".  The change should be live within the hour.

For reference, the doc page is https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/nf-wdm-exallocatepoolwithtag


Add PHP7.1 support

Current coverage is 100% (diff: 100%)

No coverage report found for master at eba49c0.

Powered by Codecov. Last update eba49c0...00fb4f3


Avatar reaction to Critical Fumble/Success as World Settings

Hey, I would like to request an option to disable the avatar reactions to every player, so they don't know the outcome, mainly for Hero Point uses.

That already exists?

At the moment, it is a user setting, meaning the players can leave it on.

Making it a world setting is not going to happen, as people have different preferences for style, so it must be possible to disable it on a client bases.
I do however appreciate that it can leak information in a way that GMs might not want at their table.
I think the best option is to use one of those modules that can sync/push client settings to players and then lock the setting.
Ironically the split to submenus has made those not work perfectly right now, but I'm working on that.

Module Management+ and Force Client Settings will allow you to pick a client-setting and force it upon your players.


Add support for com.google.protobuf.AbstractMessageLite

j2objc's protobuf runtime doesn't define AbstractMessageLite.

Fixed in current source.


Wallet changes the default name by himself

After the payment transaction, the name in the account was changed by itself, although by default I set a different name.
Originally posted by @Liubov-crypto in https://github.com/aeternity/superhero-wallet/issues/1016#issuecomment-822399009

Tested, I can't reproduce this error on develop branch  68a2ffe / v.0.6.0

fixed by #1023


Transparent background regression in 1.10 and new

Here's a simple Sandcastle example that uses the scene.backgroundColor property to make a transparent background (with the underlying yellow div showing through).  It works in 1.9 but not in 1.10 or 1.11.  Multiple users have ran into this problem: forum post.
JS
javascript
var viewer = new Cesium.Viewer('cesiumContainer', {
skyBox : false,
skyAtmosphere : false,
contextOptions : {
webgl: {
alpha: true
}
}
});
viewer.scene.backgroundColor = Cesium.Color.TRANSPARENT;
**HTML**
```html

Loading...

Hi! Seeing there was not much activity here and i wanted to use a bit newer versions then 1.9 on our services i have been looking for the change that removed this functionality. After quite some looking around i found it! :smile:
It seems it got in in around the commit 6413fbe1a578f2ae0bb3f378a1f3068de8f5a88e in the file Source/Scene/Scene.js this was changed:
this.fxaa = true; (line 482 in release 1.12)
from false to true.
Changing it back resolves the problem, not sure what else it could do though that is why i am pointing it out and not creating a pull request, maybe it has some use that i don't know of.
Would really be happy to see this in the next release because i will be solving this really hacky for our deployment strategy.
If you want to change this directly in the minified build Cesium.js file, you can replace "this.fxaa=!0" with "this.fxaa=0".
Kind regards!

@santilland There's no need to hack Cesium.js for a workaround so simple, just set the value after you construct the widget.
viewer.scene.fxaa = false;

(Also, if you were to hack the minified file, !1 is the correct minified version of false, not the number zero.)

Hi! Well that happens for over thinking :D that is a far easier approach of course, thanks for that.

@bagnell since we know it's the fxaa pass, could the problem be that we are not checking if the webGL context was created with alpha:true and creating the framebuffer with the correct options to match?  I took a quick look at the code, but it's an area I'm not familiar with so nothing jumped out at me.

Once this issue is resolved, check to see if #1921 is fixed.

I can't get a transparent background with 1.52. Even fix FXAA disabled. There has to be another effect that forces alpha drawing.
`	//Create the Cesium viewer
var viewer = new Cesium.Viewer('cesiumContainer', {
skyBox : false,
skyAtmosphere : false,
baseLayerPicker : false,
homeButton: false,
sceneModePicker: false,
navigationHelpButton: false,
animation: false,
creditsDisplay: false,
timeline: false,
scene3DOnly: true,

contextOptions : {
webgl: {
alpha: true
}
}
});
//Set the background of the scene to transparent
viewer.scene.backgroundColor = Cesium.Color.TRANSPARENT;
viewer.scene.fxaa = false;
`

@Pheater thanks for brining this up.  I took a quick look at the good news is FXAA is no longer the culprit (plus the way to disable it changed a while ago).  Now it's HDR that needs to be disabled.  Here's a minimum snippet to get things working:
//Create the Cesium viewer
var viewer = new Cesium.Viewer('cesiumContainer', {
    skyBox : false,
    skyAtmosphere: false,
    contextOptions : {
        webgl: {
            alpha: true
        }
    }
});
//Set the background of the scene to transparent
viewer.scene.backgroundColor = Cesium.Color.TRANSPARENT;

//HDR needs to be disable for transparent backgrounds
viewer.scene.highDynamicRange = false;

And here's a working example with a yellow background: https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=ZVHLbsIwEPyVVS5QidrqlQZUCpV6qKAC1FMujrNJLBw7sh0grfj32oHy6l7sfcyOZ0zp1CBzCK5EmKIVTQVbgTs0idoyc7rDCBTuTn3y1dX6Pd6lU60cEwpNbwA/iQIfdtO+6j0MIWfS4uBcnLhK27pEg7ct7lfg3i1qJ7SyHnfaE2KHaSFvKiGYrEs2BGcavDQOx6s/Dg/PiaJ0ha7TlTK+KYxuVAY67yqWo/Katd/AlK2ZQeW84E4Y6ZrkAppqqYMFJ/ldStbLyXz1OVm+zdeeK7C9z5beJcxs2JsiZMKyVCLkHnxFc/Uae0dZiqKctYpVgi+ZKtBzdjZ5gmgQxda1EsdHkS+iqrVx0BjZJ4Q6rGrpv9HStOEbdIRbGzwIo6nO2mv/LvyPPEgZQotS6t3ZvZj+McWZ2ILIRkl099dJBFwya30nb6RciW9MonFM/fwNTGqWCVUstmgka8NI+TT+OBYJITH16X+U01qmzFxt/AU

Fantastic. Works great.

Thanks for pointing this out.  Do you think the docs where alpha is explained (I think at the top of Scene) could be updated to mention this?  Alternately (and/or?), maybe a brief mention in the release notes -- helpful to know why my transparent background suddenly wasn't.
Another thought: it wouldn't hurt if viewer.scene.backgroundColor = Cesium.Color.TRANSPARENT automatically turned off any options that would otherwise keep it from actually being transparent.

I opened an issue for the recent regression: https://github.com/AnalyticalGraphicsInc/cesium/issues/7427.

@Pheater @thw0rted this was fixed in https://github.com/AnalyticalGraphicsInc/cesium/pull/7431 and will be in the 1.53 release. It seems like the original issue with FXAA has since been solved too.


About face masking

Can you tell me how to get a face mask? The article cited doesn't give me code and pre-trained models, can you give me a little advice, or alternatives?

Hi, the cited article has not released the code and pre-trained models yet. We provide the segment_face.pb in https://github.com/youngLBW/HRN/blob/main/assets/README.md, which is implemented based on the cited article and can be applied to obtain the face mask.


Migrate the datamapper code from visualizer of the rewrite branch to main branch ballerina extension

Description:
Currently the code is located in the visualiser of the rewrite branch of VSCode extension. This has to be moved to the main branch, ballerina extension(backend).

The fix is merged. Hence closing the issue.


Update ResourceContainerFactory packaging parameters

This pull request resolves #5

Ah, I didn't realize setVolume was an external volume. That makes sense. I will make changes.


Implement absolute_import in Scrapers w/ tests

Fixes #226 (with tests included)
This should help the codebase to achieve Python 3 compatibility.
Checklist

[X] I have read the Contribution & Best practices Guide and my PR follows them.
[X] My branch is up-to-date with the Upstream master branch.
[X] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

Adds from __future__ import absolute_import and .imports within a module
Used isort to sort imports
Remove unused read_in()
Remove unused imports
Added <search engine name> parsed:  to the output to aid testing #271 -like issues.
Added two test to app/test_server.py to ensure we do not have regressions
Some code was processed by yapf to improve #265

Please provide heroku deployment for this PR to be reviewed. Thanks !

I used Bluemix, not Heroku but #270

Heroku will not fail. Try heroku easy and free.

https://scrapers-use-absolute-imports.herokuapp.com/

Travis refuses to engage

@niranjan94 This was the PR where Travis refused to engage.

@cclauss looks like travis had some issues on their side. That coincides with the day this PR was created. Could be related. https://www.traviscistatus.com/incidents/v4jnp6nkgzqx


Proxies

Hi.
Thank you for your hard work!
Is it possible to know the anonymity of these proxies?
How frequently do you refresh the entire list with new ones?
Thank you
Daniel

Hi Daniel.
The update itself and proxies are pulled every 10 minutes, but due to the way github actions work, it is not guaranteed that updates will occur every 10 minutes. Fresh proxies appear here as soon as they appear on a paid service source.
You can take information about the anonymity of the proxy from the csv file, there is a separate column there.


⚠ Bofrost.lu has degraded performance

In 92e4d41, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2220 ms

Resolved: Bofrost.lu performance has improved in 7219e45 after 9 minutes.


Groundwork for sphinx docs

This PR adds the boilerplate for getting auto-generated sphinx documentation for the source code and re-words the introduction to the root README.md to capture the value proposition of the plinder project.


Call Jenkins.EnhanceClient to replace http.DefaultClient

Allows for custom time-out, disable TLS , etc.
fixes #42

Looks good.  But I think straightforward name like SetHTTPClient instead of EnhanceClient would be nice.

Sounds reasonable, done.

merged.  Thank you for your contributing!


PairPhone doesn't not trigger the on connected handler

@krypton-byte any method to disconnect and then connect again after PairPhone is called?

Trying
@client.event.qr
async def on_qr(client: NewAClient, qr_data: bytes):
    await client.PairPhone(…

Broke the client on first run after pair (Two same clients running simultaneously )

Not necessarily solved
Realized I didn't need to actually call connect (the on connected handler I wanted to use was broken anyways, had to create another one )


Initial setup of terraform-config-validator

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/di-graph/terraform-config-validator?version=dev:8ca8961ce9f346ee6616a5990bb6ac965ca251c1

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/di-graph/terraform-config-validator?version=dev:8ca8961ce9f346ee6616a5990bb6ac965ca251c1


TypeError [ERR_INVALID_ARG_TYPE]: The "name" argument must be of type string. Received null

Hi,
When first running npm run dev, I was seeing the following error:

TypeError [ERR_INVALID_ARG_TYPE]: The "name" argument must be of type string. Received null
    at validateString (internal/validators.js:120:11)
    at Resolver.queryA [as resolve4] (dns.js:216:5)
    at D:\demos\commerce\node_modules\@zeit\dns-cached-resolve\lib\resolve4.js:5:18
    at new Promise (<anonymous>)
    at resolve4 (D:\demos\commerce\node_modules\@zeit\dns-cached-resolve\lib\resolve4.js:4:12)
    at D:\demos\commerce\node_modules\@zeit\dns-cached-resolve\lib\dns-resolve.js:29:55
    at RetryOperation.runAttempt [as _fn] (D:\demos\commerce\node_modules\async-retry\lib\index.js:35:15)
    at Timeout._onTimeout (D:\demos\commerce\node_modules\retry\lib\retry_operation.js:81:10)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7) {
  code: 'ERR_INVALID_ARG_TYPE',
  url: '321',
  opts: {
    method: 'POST',
    headers: Headers { [Symbol(map)]: [Object: null prototype] },
    body: '{"query":"\\n  query getAllProducts(\\n    $hasLocale: Boolean = false\\n    $locale: String = \\"null\\"\\n    $entityIds: [Int!]\\n    $first: Int = 10\\n    $products: Boolean = false\\n    $featuredProducts: Boolean = false\\n    $bestSellingProducts: Boolean = false\\n    $newestProducts: Boolean = false\\n  ) {\\n    site {\\n      products(first: $first, entityIds: $entityIds) @include(if: $products) {\\n        ...productConnnection\\n      }\\n      featuredProducts(first: $first) @include(if: $featuredProducts) {\\n        ...productConnnection\\n      }\\n      bestSellingProducts(first: $first) @include(if: $bestSellingProducts) {\\n        ...productConnnection\\n      }\\n      newestProducts(first: $first) @include(if: $newestProducts) {\\n        ...productConnnection\\n      }\\n    }\\n  }\\n\\n  \\n  fragment productConnnection on ProductConnection {\\n    pageInfo {\\n      startCursor\\n      endCursor\\n    }\\n    edges {\\n      cursor\\n      node {\\n        ...productInfo\\n      }\\n    }\\n  }\\n\\n  \\n  fragment productInfo on Product {\\n    entityId\\n    name\\n    path\\n    brand {\\n      entityId\\n    }\\n    description\\n    prices {\\n      ...productPrices\\n    }\\n    images {\\n      edges {\\n        node {\\n          urlOriginal\\n          altText\\n          isDefault\\n        }\\n      }\\n    }\\n    variants {\\n      edges {\\n        node {\\n          entityId\\n          defaultImage {\\n            urlOriginal\\n            altText\\n            isDefault\\n          }\\n        }\\n      }\\n    }\\n    productOptions {\\n      edges {\\n        node {\\n          __typename\\n          entityId\\n          displayName\\n          ...multipleChoiceOption\\n        }\\n      }\\n    }\\n    localeMeta: metafields(namespace: $locale, keys: [\\"name\\", \\"description\\"])\\n      @include(if: $hasLocale) {\\n      edges {\\n        node {\\n          key\\n          value\\n        }\\n      }\\n    }\\n  }\\n\\n  \\n  fragment
productPrices on Prices {\\n    price {\\n      value\\n      currencyCode\\n    }\\n    salePrice {\\n      value\\n      currencyCode\\n    }\\n    retailPrice {\\n      value\\n      currencyCode\\n    }\\n  }\\n\\n  \\n  fragment multipleChoiceOption on MultipleChoiceOption {\\n    values {\\n      edges {\\n        node {\\n          label\\n          ...swatchOption\\n
    }\\n      }\\n    }\\n  }\\n\\n  \\n  fragment swatchOption on SwatchOptionValue {\\n    isDefault\\n    hexColors\\n  }\\n\\n\\n\\n\\n","variables":{"first":6,"locale":"en-US","hasLocale":true,"featuredProducts":true}}',
    agent: Agent {
      _events: [Object: null prototype],
      _eventsCount: 4,
      _maxListeners: undefined,
      defaultPort: 80,
      protocol: 'http:',
      options: [Object],
      requests: {},
      sockets: {},
      freeSockets: {},
      keepAliveMsecs: 1000,
      keepAlive: true,
      maxSockets: Infinity,
      maxFreeSockets: 256,
      freeSocketKeepAliveTimeout: 15000,
      timeout: 30000,
      socketActiveTTL: null,
      createSocketCount: 0,
      createSocketCountLastCheck: 0,
      createSocketErrorCount: 0,
      createSocketErrorCountLastCheck: 0,
      closeSocketCount: 0,
      closeSocketCountLastCheck: 0,
      errorSocketCount: 0,
      errorSocketCountLastCheck: 0,
      requestCount: 0,
      requestCountLastCheck: 0,
      timeoutSocketCount: 0,
      timeoutSocketCountLastCheck: 0,
      [Symbol(kCapture)]: false
    },
    redirect: 'manual',
    onRedirect: [Function]
  }
}

Is anyone here can help me to solve this problem? Thanks !!!

For more information I have this problem on my windows machine and not on my macbook.

For more information I have this problem on my windows machine and not on my macbook.

Hey, there @bbeldame did you use the proper .env.local  variables?

Hey, there @bbeldame did you use the proper .env.local  variables?

@Itsaadarsh  emm.. I haven't change the .env.template to .env.local.. And which value can  I assign them?

@Itsaadarsh  emm.. I haven't change the .env.template to .env.local.. And which value can  I assign them?

Hey @blanklong28 tbh I'm also having the same doubt I'm unclear of the .env.local variables and their value. I thought you were past all of that so I thought I'd ask you.

Hey @blanklong28 tbh I'm also having the same doubt I'm unclear of the .env.local variables and their value. I thought you were past all of that so I thought I'd ask you.

I fixed my issue and it had nothing to do with macbook/windows. Only that when I copy pasted the .env that I wanted, it added some formatting (I copied from Notion). I didn't see that it changed the formatting so the error was just that the BIGCOMMERCE_STORE_API_URL and BIGCOMMERCE_STOREFRONT_API_URL were badly typed.

Hey there! Thank you for your contribution. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: #966


Unexpected keyword argument 'log_level'

The log_level argument passed to pyrouge.Rouge155 is denied as unexpected argument:
Preparing documents...
Running ROUGE...
Traceback (most recent call last):
  File "/usr/local/bin/files2rouge", line 11, in <module>
    load_entry_point('files2rouge==2.0.0', 'console_scripts', 'files2rouge')()
  File "/usr/local/lib/python3.6/site-packages/files2rouge-2.0.0-py3.6.egg/files2rouge/files2rouge.py", line 65, in main
    log_level=log_level)
TypeError: __init__() got an unexpected keyword argument 'log_level'

Python: Version 3.6

The problem with log_level is not how to dodge it, but why it happens. I mean, current pyrouge code has such a parameter (see: https://github.com/bheinzerling/pyrouge/blob/master/pyrouge/Rouge155.py#L74) therefore it must not be a problem.
I do not care that much about this param, it just shows that you are not running the expected pyrouge code.

59ad4b0c1c1c0ce9bbf7ee5a757a733940816898