Dart Analysis server crashing repeatedly, but not always producing reports.

The analysis server is crashing repeatedly under IntelliJ.
It doesn't always generate a crash report, but it is constantly (about every 20 seconds while I edit the code) restarting, re-analyzing the tree, and flashing the dartdoc links, disabling symbol lookup, etc.
I've filed a couple of other bugs, but I'm going to close those and put the information here, because I think they are probably related crashes.
This is on the bleeding edge Flutter repo, since the last Dart roll.
I'm just editing dartdoc comments in the code while this happens.
I've tried opening the analyzer diagnostics page, and when the server is restarted by IntelliJ after the crash, the diagnostic page just stops being served, and when I open it again after the restart, there are no exceptions reported.
Version information

IDEA IC-191.6183.87
2.2.1-edge.896f1c4bb94a390c2969953626980d9de320cd84
IC-191.6183.87, JRE 1.8.0_202-release-1483-b39x64 JetBrains s.r.o, OS Linux(amd64) v4.19.20-1rodete1-amd64, screens 3840x2160, 3840x2160

Exception number 1
This stack appears in more than one report:
Dart analysis server, SDK version 2.2.1-edge.896f1c4bb94a390c2969953626980d9de320cd84, server version 1.25.0, FATAL error: Bad state: Attempt to modify immutable list
#0      Driver._captureExceptions.errorFunction (package:analysis_server/src/server/driver.dart:579:7)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:1003:19)
#2      _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#3      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#4      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#5      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#6      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:391:30)
#7      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:416:5)
#8      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:171:12)

1554479682649 => {"id":"34","method":"analysis.updateContent","params":{"files":{"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart":{"type":"add","conte
1554479682650 <= {"id":"34","result":{}}
1554479682650 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":true}}}
1554479682660 => {"id":"35","method":"edit.getAssists","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","offset":699,"length":0},"cli
1554479682682 <= {"event":"analysis.errors","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","errors":[]}}
1554479682683 <= {"id":"35","result":{"assists":[{"message":"Convert to block documentation comment","edits":[{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/foc
1554479682686 <= {"event":"analysis.highlights","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"type":"DIRECTIVE","offs
1554479682689 <= {"event":"analysis.navigation","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"offset":173,"length":12
1554479682689 <= {"event":"analysis.closingLabels","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","labels":[]}}
1554479682690 <= {"event":"analysis.outline","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","kind":"LIBRARY","outline":{"element":{
1554479682690 <= {"event":"analysis.overrides","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","overrides":[{"offset":17716,"length"
1554479682829 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":858,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kin
1554479682850 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":false}}}
1554479683008 <= {"event":"analysis.implemented","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","classes":[{"offset":5574,"length":
1554479683330 => {"id":"36","method":"analysis.updateContent","params":{"files":{"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart":{"type":"add","conte
1554479683330 => {"id":"37","method":"completion.getSuggestions","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","offset":701},"clie
1554479683332 <= {"id":"36","result":{}}
1554479683333 <= {"event":"server.status","params":{"analysis":{"isAnalyzing":true}}}
1554479683371 <= {"id":"37","result":{"id":"3"}}
1554479683372 <= {"event":"analysis.errors","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","errors":[]}}
1554479683374 <= {"event":"completion.results","params":{"id":"3","replacementOffset":701,"replacementLength":0,"results":[],"isLast":true,"includedSuggestionSets":[{"id":904,"relevance":5},{"id":966,
1554479683377 <= {"event":"analysis.highlights","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"type":"DIRECTIVE","offs
1554479683380 <= {"event":"analysis.navigation","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"offset":173,"length":12
1554479683380 <= {"event":"analysis.closingLabels","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","labels":[]}}
1554479683381 <= {"event":"analysis.outline","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","kind":"LIBRARY","outline":{"element":{
1554479683381 <= {"event":"analysis.overrides","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","overrides":[{"offset":17718,"length"
1554479683597 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      _FbList.length= (package:analyzer/s
1554479683597 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      _FbList.length= (package:analyzer/s
1554479683597 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      Driver._captureExceptions.errorFunc
1554479683597 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      Driver._captureExceptions.errorFunc

Exception number 2
This stack also appears in more than one report:
Dart analysis server, SDK version 2.2.1-edge.896f1c4bb94a390c2969953626980d9de320cd84, server version 1.25.0, FATAL error: Bad state: Attempt to modify immutable list
#0      Driver._captureExceptions.errorFunction (package:analysis_server/src/server/driver.dart:579:7)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:1003:19)
#2      _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#3      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#4      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#5      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#6      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:391:30)
#7      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:416:5)
#8      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:171:12)

1554480733004 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733005 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733005 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733006 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733092 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733093 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733093 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733094 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733094 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733128 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733128 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733129 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733129 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733130 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733130 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":0,"uri":"package:flutter/src/widgets/focus_manager.dart","items":[{"label":"FocusNode","element":{"kind"
1554480733131 => {"id":"129","method":"analysis.updateContent","params":{"files":{"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart":{"type":"add","cont
1554480733131 => {"id":"130","method":"completion.getSuggestions","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","offset":1068},"cl
1554480733132 <= {"id":"129","result":{}}
1554480733202 <= {"id":"130","result":{"id":"46"}}
1554480733203 <= {"event":"analysis.errors","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","errors":[]}}
1554480733204 <= {"event":"completion.results","params":{"id":"46","replacementOffset":1068,"replacementLength":0,"results":[],"isLast":true,"includedSuggestionSets":[],"includedElementKinds":[],"incl
1554480733208 <= {"event":"analysis.highlights","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"type":"DIRECTIVE","offs
1554480733225 <= {"event":"analysis.navigation","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","regions":[{"offset":173,"length":12
1554480733225 <= {"event":"analysis.closingLabels","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","labels":[]}}
1554480733226 <= {"event":"analysis.outline","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","kind":"LIBRARY","outline":{"element":{
1554480733226 <= {"event":"analysis.overrides","params":{"file":"/usr/local/google/home/gspencer/code/flutter/packages/flutter/lib/src/widgets/focus_manager.dart","overrides":[{"offset":17873,"length"
1554480733226 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      _FbList.length= (package:analyzer/s
1554480733226 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      _FbList.length= (package:analyzer/s
1554480733226 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      Driver._captureExceptions.errorFunc
1554480733226 <= {"event":"server.error","params":{"isFatal":false,"message":"Captured exception","stackTrace":"Bad state: Attempt to modify immutable list\n#0      Driver._captureExceptions.errorFunc

This error has not been reported since this report; please re-open if you see this again.

This error has not been reported since this report; please re-open if you see this again.


fix: add INCAR to ft example

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@devel dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


docs: correct comments in examples

When I run the command commented in examples, an error occurred.
❯ cargo run --example tcp_server --features="os-poll tcp"
error: Package `mio v0.8.0 (/home/pvon/Documents/mio)` does not have the feature `tcp`

This pull request is to fix them.

@persevereVon can you rebase on master? It should fix the CI.

@Thomasdezeeuw ok, thank you, this time it should be fine.

Thanks @persevereVon.


Inadequate Content Validation in Private and Public Key Normalization

Both normalizePrivateKey and normalizePublicKey functions in the code validate the length of input strings to determine their format (hex or base64) but do not adequately validate the content. This can lead to accepting strings with the correct length but invalid content.
An attacker could provide strings with the correct length but malformed content for both private and public keys, causing unexpected behavior or security vulnerabilities.
Recommendation
Implement content validation for both private and public keys using regular expressions to ensure strings match the proper hex or base64 format. Update both normalizePrivateKey and normalizePublicKey functions to include these checks. For example:
function isValidHex(input) {
return /^[0-9a-fA-F]*$/.test(input);
}
function isValidBase64(input) {
return /^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$/.test(input);
}
// Update the normalizePrivateKey and normalizePublicKey functions
// to include these validation checks before processing the input.
Certik finding: GDP-01

Done here https://github.com/GalaChain/sdk/pull/148


Vulnerability Assessment  using a private endpoint storage account hangs  deployment

https://github.com/Azure/ResourceModules/blob/2bba6013e392cf7ebb1b52f4b8b1cea6002df0aa/arm/Microsoft.Sql/managedInstances/vulnerabilityAssessments/deploy.bicep#L43
Configuring Vulnerability Assessment on  SQL Managed instance.    When storage account keys are not used and deploying to Storage account connected with a private endpoint this line causes the deploy to hang.   Commenting it out  allows the deploy to succeed.

Hey @kprotsko, thanks for the issue. We'll make sure to check it out. Will flag the issue as a bug.

Closing if favor of #1210


DeadLetterPublishingRecoverer should respect onlyLogRecordMatadata listener property

Expected Behavior
Currently the org.springframework.kafka.listener.KafkaMessageListenerContainer class has onlyLogRecordMatadata property that governs how ConsumerRecord is logged on processing failure. Same onlyLogRecordMatadata property should be respected by the org.springframework.kafka.listener.DeadLetterPublishingRecoverer class for ProducerRecord.
Current Behavior
DeadLetterPublishingRecoverer currently logs the whole ProducerRecord when publication fails with no option to switch to just the metadata.
Context
We already have set onlyLogRecordMatadata = true because we don't want the message payload to appear in the logs when something fails. Since DeadLetterPublishingRecoverer copies the payload from the failed message into a ProducerRecord we still see the original message payload in the logs when publication fails.

Which version are you using? And which log message specifically?
It looks like all logs in 2.8.x properly log the record; in 2.7.x, I see one debug and 2 exceptions that log the full record.

That flag only controls logging of the consumer record.
The DLPR does log the producer record; in 2.8 we added a new feature to format the logs for producer record.
https://github.com/spring-projects/spring-kafka/blob/f94620aea7e7b43416b67cf9a46dce0acf46aa95/spring-kafka/src/main/java/org/springframework/kafka/support/KafkaUtils.java#L168-L176
The default formatter logs the full record.

Although it was back-ported to 2.7.x, the DLPR doesn't use it.

Good point @garyrussell. I'm on 2.7.12, inherited from Spring Boot 2.5.13. I don't see DeadLetterPublishingRecoverer using KafkaUtils formatting in these lines:
https://github.com/spring-projects/spring-kafka/blob/85cbbed1a28aca28a2c4c9e5dfc698d25cec7d9b/spring-kafka/src/main/java/org/springframework/kafka/listener/DeadLetterPublishingRecoverer.java#L501
https://github.com/spring-projects/spring-kafka/blob/85cbbed1a28aca28a2c4c9e5dfc698d25cec7d9b/spring-kafka/src/main/java/org/springframework/kafka/listener/DeadLetterPublishingRecoverer.java#L525

It might be useful if failIfSendResultIsError field and verifySendResult method are changed from private to protected just like publish method is already protected. That way when when someone wants to override publish they can still reuse failIfSendResultIsError + verifySendResult functionality.

Yes, I will do some polishing around that at the same time; we don't allow protected fields (except loggers), but I can add a getter for it.

Closed by https://github.com/spring-projects/spring-kafka/commit/56b7756206462bcd2b9dd8aaad0e64d27efce4d5
(Not sure why this didn't auto-close).


MeSH:C538339 is not a recognised xref for Nasopharyngeal Carcinoma (MONDO:0015459)

Nasopharyngeal Carcinoma (MONDO:0015459) it has a exactMatch to MeSH:C538339
But that ID is not found/does not exist : https://www.ncbi.nlm.nih.gov/mesh/?term=C538339
For Nasopharyngeal Carcinoma (MONDO:0015459) should the MeSH ID be:
https://www.ncbi.nlm.nih.gov/mesh/?term=D000077274
I think this might be another one for Orphanet? as the MeSH xref comes from them (cc @ana-rath-orphanet and @Orphanet). The MeSH id seems to have been retired and replaced with D000077274.
Although it is not always the case I have found a number of these on this list https://www.nlm.nih.gov/mesh/2019/download/TermsMovingFrom2018SCRsto2019Descriptors.pdf
Could this be check/cross referenced somehow within MONDO to see if there are any more cases like this or should this list be checked with each of the xref databases used for the MeSH terms?
I haven't found a more recent pdf listing the retired MeSH terms and their new equivalent descriptors but hoping you might know @nicolevasilevsky
Thank you!

https://www.nlm.nih.gov/databases/download/mesh.html

@lcdaugherty I updated the xref to MESH - thanks for catching that.
We do not have a process to check for deprecated terms that are xref'd in Mondo. The list you attached is super helpful, but too long for me to look through manually. I'll create a new ticket to see if we could automate this process somehow.

@nicolevasilevsky as you know, updating xrefs is the known ongoing cat and mouse chase!
I agree it super useful if that deprecated list could be used to do a mass update (and a task that no curator should do manually).  PDF is an awful format for relaying info but even with open source converters you should be able to get in into something that can be used computationally.
As  I continue to check our dataset I have come across a few not that list (we are after-all now in 2020!),  shall I create new tickets for each one, a single ticket with them all with an attached list or will Mondo be able to do a review of the new download features/data now available direct at MeSH (as linked by @maglott)


Remove CLI from the readme

someone want to do the wiki, too?

Done: deleted the page and https://github.com/lightbend/migration-manager/wiki/Home/_compare/e6dbb68b2d90375da30121395dcb8e2395135331...f953911c994604ceadd742eec7db55282c31e95a.

Thanks for cleaning up the Wiki!


systemd.services..path and buildInput hooks?

Today, it can be a bit jarring for people to add something like pythonPackages.foo to systemd.services.<foo>.path, expecting it to behave like buildInputs in a build. Perhaps it'd be nice to have a systemd.services.<foo>.inputs option that works like buildInputs and triggers hooks that would make packages with hooks that modify the environment work properly?

That's a bit strange. Why would anyone want to have a build environment (setup.sh and stuff) in a systemd service?

I'm not saying they would, but we often merge build and "actually work"
functionality in there. Before we added python.withPackages a little while
ago, how would you add a python package to the scope of a systemd service?
The hook adds to the PYTHONPATH.
On Tue, Feb 7, 2017 at 07:22 Nikolay Amiantov<EMAIL_ADDRESS>wrote:

That's a bit strange. Why would anyone want to have a build environment (
setup.sh and stuff) in a systemd service?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/22498#issuecomment-277983161,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAKP2ISlBra0zuzFGS3p1JpL3iPntQgks5raGHvgaJpZM4L4Up3
.

Hm, seems that we do the wrong thing :D I'm not sure how to do better though; in this particular case I'd set systemd.services.foo.environment.PYTHONPATH but that's non-ideal too...

Yeah, this feels like part of the broader build vs. run question. It also arises when we talk about the uses for nix-shell as a general-purpose dev environment vs. as a mechanism for debugging nix builds. It feels like we should start talking about how to separate things like PYTHONPATH which are useful for execution and other things like autoreconf buildhooks that are only used for building.
cc @edolstra since there was a lot of talk about the new Nix command-line interface and the various uses for nix-shell.

Another example here is JAVA_HOME. I had someone get quite confused that java was in the PATH, but JAVA_HOME was unset. If you just use nix-shell -p jre you get a proper JAVA_HOME in your environment.

I don't think this is a good idea. It conflates the build- and run-time environment. For example, do you really want to pull in stdenv and PKG_CONFIG_DIRS and your runtime environment for services? That feels wrong to me.
I believe that there are better, different solutions for these problems. For python packages for example, you should not need to explictly set PYTHONPATH. Instead, use either pythonWithPackages or package your app as a full derivation and then use it in your service. The python builder will make sure that all binaries of your app are wrapped such that PYTHONPATH gets set before running them. A similar solution should be possible for JAVA_HOME.

@bennofs I'm not too opinionated on the specific mechanism, but requiring withPackages-like solutions further forks the behavior between a build (well tested, every time we run builds) and what people actually use, so I'm hesitant. In other words, why should buildInputs be special? Why not use python.withPackages there too?
Anyway, as I said I don't care about the specifics, but I am wary of using completely separate mechanisms for the two different use cases.

@copumpkin This is a valid concern. It definitely applies to development environments: it would be nice if we could use the same mechanisms as we use for building the packages. However, there's multiple issues with this:

a systemd service hould not run a in a "development environment", in my opinion. Services are a runtime construction. This is a lot more clear in the case of compiled languages: you don't need headers or pkgconfig files to run a c-based service, so you shouldn't run the build hooks for this stuff.
sometimes, the mechanisms for finding dependencies etc used at build time are not really convenient to use if you don't use a script, so they would not be fit for interactive use or even just for use outside of the builder for this language (case in point: haskell at least used to pass explictly flags for every dependency in it's builder)
using withPackage-like wrappers in the build has a cost, it results in more derivations or at least requires time to build the wrappers. These are not such a problem for usage in runtime environments.

But I don't think that a runtime-environment should be the same as a development/build-environment. For example, the issue you described does not only affect systemd units. There's lot's of other places where this would fail as well:

you cannot place such a package in systemPackages and have it "just work"
you cannot install such a package with nix-env easily.

I believe just running systemd services inside a build environment is not the solution here. It will perhaps fix this particular issue, but it leaves those other issues unsolved and also is kind of ugly because build environments are often not meant to exists for extended amounts of time (for example, they might create lots of temporary files etc)

a systemd service hould not run a in a "development environment", in my opinion.

Oh, I fully agree. I just want things to work reliably 😄

you don't need headers or pkgconfig files to run a c-based service, so you shouldn't run the build hooks for this stuff.

No but sometimes I need (DY)LD_LIBRARY_PATH. I get that in almost all cases that sort of thing should be handled by a wrapper, but I want to make sure that it's hard to screw up too.

But I don't think that a runtime-environment should be the same as a development/build-environment.

100% agree 😄
My point in this ticket is just that there are some things you might want in both contexts, both at runtime and at development/build time. Definitely not proposing bringing in all sorts of annoying build-time dependencies in at runtime; I just don't think we maintain enough information to do this sensibly right now.

Are there any updates to this issue, please?


enable support for change in aggregates

Right now it is evaluated if “aggregate” is a boolean value but since version 24. of Sensu, it should be a string and not a bool anymore

+1


Add failure tests for noms-merge

Tests command line validation for noms-merge
Toward #2445

ptal

Ping?

lgtm with comments


Interface description language (IDL) for ReactiveSocket

Has there been any discussions about an IDL for ReactiveSockets yet?
Once the protocol spec is frozen I'd be down for hacking something up. Been looking at both thrift and grpc IDLs to refresh my memory, and compare their IDLs and features available to each.

There have definitely been internal discussions at both Netflix and Facebook. @robertroeser and @rdegnan I think have explored this space. And Thrift-based ones at Facebook.
It's not a goal of ReactiveSocket to standardize this behavior though, so I would expect that to be a layer on top.

Cool, thanks for clarifying.
At some point I might still try it though, and I'm sure others will do too.


Get newly registered users in last 30 days

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe how to intend to go about adding this feature
Describe the approach you will take in adding this feature.
Additional context
Add any other context or screenshots about the feature request here.

can  i take this?

i already sent a pr


Fix coreclr binlog: corrupted patch

Recreate the patch adding the dotnet/runtime build-source-build.sh: it wasn't adding the last line. This ends up overwriting the coreclr binlog in the portable build.
Fixes https://github.com/dotnet/source-build/issues/1943.

It looks like with https://github.com/dotnet/source-build/commit/26c298f8acd841a8cc9e495c1fdcf6c437541018#diff-c72afe4ad8f6530dfdc0d7bb0a852e671bd0e57d4bf2dda5af448d9a1e38aebe, the patch was changed without updating the line count.
Within the commits of the PR that was squashed to make that commit, I see this tighter diff which only adds one line and makes the patch wrong: https://github.com/dotnet/source-build/commit/d0caaeace71ba5da8b6f6f2a94f295f2d93d1aff#diff-c72afe4ad8f6530dfdc0d7bb0a852e671bd0e57d4bf2dda5af448d9a1e38aebe.
Maybe the patch text was manually modified without updating the rest of the patch properly? Seems like the simplest answer to me.

Merging past https://github.com/dotnet/source-build/issues/1937.


patch

Let's update patch with:

Data (typed)
Variables (or nothing and will reset the all cache)

I'll remove the xPath thing for now and think about fragment update later.

I'll close this version of patch for now.
And will open a new issue for the next evolution of it. (with fragments!)


Implement message stores

I have replicated and renamed NewConnection function to have constructors for connections from account database as well as messages database. The return type of GetFromGroup from MerkleStore has been changed to single from an array. This was done as id is a primary key for the table. The store functions are implemented and the tests are also added.

Very nice! Thank you for adding this.


Views clickable functionality not working

Bug Description
B1: "Forget Password?" view not working on Login page.
B2: "Already Have an account? Login" view not working on Sign up page.
To Reproduce
B1:-
Go to Login page. (automatically opens after splash screen)
Click on "Forget password?"
ERROR: Nothing happens
B2:-
Go to Sign up page. (by clicking sign up button below)
Click on "Already Have an account? Login"
ERROR: Nothing happens
Expected behavior
B1:  The view should be renamed to "Forgot Password?" and it must intent to the browser where firebase will handle the change password procedure. User has to enter their registered email and will get a password reset mail.
B2: The click must intent back to login page.
Smartphone

Device: Redmi 7
OS: Android 10

Additional context
Code for B1 must be entered and synced with loginActivity.java
Code for B2 must be fixed under signupActivity.java

Hi @aakash232!
In order to use the login and sign-up function, one must connect the project with Firebase. Please try to connect this project with firebase and then share whether it was working or not.
Thanks for sharing your interest in this project.

@VikasPandey121 after connecting project to firebase, there are many duplicate classes which exits. What should we do in that case? I am not able to find the location of these classes.


 These contributions should be local to their feature area and register to a shared registry somewhere, as opposed to being implemented directly in workbench/contrib/accessibility.

Duplicate of https://github.com/microsoft/vscode/issues/210397


Integrate Finished Consumable Transactions

This issue is meant to be a good first issue to get into coding, and into open source contribution over all, as it will require to touch few existing files, is a small change and is documented extensively. If you are new to coding, I encourage you to try this issue.
Please read our contribution guidelines before picking this up, it will also lead you through the process of setting up the repository.
Feature description
With iOS 18, finished consumable transactions are now included in the transaction history APIs. This issue requires to update the documentation about this change.
Describe the solution you'd like
Write an article how to support this change in an application using a new property list key, SKIncludeConsumableInAppPurchaseHistory.

Hi @nik3212, I would like to take a look at this issue 🔨

Hi @nssina, sure! Feel free to take a look. Let me know if you have any questions.

Sure, Thanks!

@nssina how's it going? Do you want to continue on this?

@nssina there is only a need to update the documentation


Changelog links to the wrong PR

Common: #1610 Added Typescript Definitions
under
0.17.0 (October 11, 2017)
https://github.com/airbnb/react-native-maps/blob/9fd1055c2b1321ed1b830cd5de6434a5a06f773a/CHANGELOG.md
Should probably be https://github.com/airbnb/react-native-maps/pull/1601

Did a PR, not sure if the changelog is generated or not.


STAR determinism

Description
After a lot of testing I have determined that STAR produces outputs in a non-deterministic order, but the reads themselves remain consistent over time. This non-determinism can have downstream effects on other steps of the pipeline, which is why the results can be different despite the files containing the same information. I have made this deterministic by sorting the resulting fastq files with a subsequent sort command after STAR.
Version

[X] I have increased the appropriate version number in https://github.com/chanzuckerberg/idseq-dag/blob/master/idseq_dag/init.py. Guidelines here: https://github.com/chanzuckerberg/idseq-dag/blob/pr-template/README.md#release-notes
[X] I have added release notes for my new version to https://github.com/chanzuckerberg/idseq-dag/blob/master/README.md#release-notes
[X] I will push a git tag after merging in the form vX.Y.Z

Tests

[ ] I have verified that the pipeline still completes successfully:

[ ] for single-end inputs
[ ] for paired-end inputs
[ ] for FASTQ inputs
[ ] for FASTA inputs.

[ ] I have validated that my change does not introduce any correctness bugs to existing output types.
[ ] I have validated that my change does not introduce significant performance regressions or I have discussed with the team that the benefits of the change are substantial enough that we're comfortable accepting the size of the measured performance penalty.

In the process of running tests but I wrote unit tests for the function itself.

Identified an issue will resolve soon.


WindowedLimit with configurable percentile in addition to average

I've been thinking how a perfect installation of concurrency-limits might look like for my needs. I walked along the path Vegas -> Gradient2 -> AIMD -> AIMD wrapped with Windowed. And it gave me an idea that calculating average response times usually less representative for real-time services, even if average would've been a perfect p50, I'd like to have my limits reduced earlier than the time when half of my users are out of acceptable timings. What people usually monitor is percentiles like p90, p95, p99, p999, and that's the metric I would prefer to have for my AIMDLimit, because it's a better representation for users experience. So I think concurrency-limits would be a better tool, if it has a percentile-window support.
I've made some research according to moving percentile algorithms and it seems like the only O(1) algorithm described here and it requires some knowledge about time distribution and it might be less accurate in some cases (check out the plot at the bottom of the article), also it's less straightforward, therefore it's more error-prone and harder to trust in.
I'd like to help with that, if team doesn't mind and I think that O(N) space, O(logN) insert time, O(1) percentile calculation implementation might be an appropriate solution here. My idea for now looks like this:

Allow WindowedLimit to work with abstractions other than ImmutableSampleWindow.
Write some sort of PercentileSampleWindow class which is mutable (I think copying N observations on each sample is too much) which will be backed with PriorityBlockingQueue
When window is ready - fetch queue-backing array with reflection (to avoid extra copies), get size()*percentile value, call onSample() and update the WindowedLimit's field with a brand new instance of PercentileSampleWindow.

What do you think so far?

@elandau Would you mind providing any advises?

@IgorPerikov Glad to see people jumping in with suggestions for improvement. I'm big fan of percentiles as they are definitely better than averages for analyzing system performance. However, traditional congestion control algorithms are really more interested in jut identifying latency trends.  In fact, most algorithms prefer to use minimum latency measurements and not averages.  I chose averages as they are very easy to calculate, both space and time, and are less prone to random low latency measurements (think things like heartbeats) resulting in a non-realistic minimum (no load) RTT.  With that said, I definitely think percentiles give a much better representation of a system's latency profile and eliminate the impact of outliers.  50th percentile is probably ideal as there are some clever optimizations for tracking it using little memory or cpu and can even be made lock free.  I can also see percentiles feeding into the timeout latency used in AIMD thereby eliminating the need for any configuration.
My recommendation for moving forward would be to simplify SampleWindow so it tracks a single value as input to the different limiter algorithms (aimd, gradient, ...).  sum can be eliminated as it is a metric implementation concern (average, percentile, min) and of no real interest to the limit algorithm.  At first, I'd just recommend doing a naive implementation for PercentileSampleWindow to gauge the efficacy of the approach.  We can optimize the implementation once the use of percentiles have been validated.

My recommendation for moving forward would be to simplify SampleWindow so it tracks a single value as input to the different limiter algorithms (aimd, gradient, ...). sum can be eliminated as it is a metric implementation concern (average, percentile, min) and of no real interest to the limit algorithm. At first, I'd just recommend doing a naive implementation for PercentileSampleWindow to gauge the efficacy of the approach. We can optimize the implementation once the use of percentiles have been validated.

Thanks, it all makes sense. I'll get back with something to show, maybe something intermediate, so we can discuss details in-progress :man_technologist:

I am closing the issue since non-naive implementation https://github.com/Netflix/concurrency-limits/pull/119 is on master, thanks for the support


Using an array as custom transformations doesn't work as expected

Hi guys,
Two problems:

it considers the array as an object and replace number with the value at the index of the array;
it mutates the array and starts adding properties to it.

Here is a test case:
var getSlug = require('speakingurl');
const custom = ['b'];

const slug = getSlug('0', { custom });
console.log(slug); // => 'b', '0' has been replaced with the custom char at index 0

console.log(custom); // => [ 'b', b: 'b' ] the array has been mutated and now have a `b` property

There are more examples of this issue:

const slug = getSlug('top 100 waterfalls', { custom: ["."] })
console.log(slug); // => top-1..-waterfalls`


Cards - Multiple bottom attached buttons

Hi, trying to create multiple bottom attached buttons in the card view.  Is there any way for the bottom attached buttons to display horizontally instead of stacking on top of one another?  Thanks!

Closing due to lack of test case

Sorry about that.  Please see the jsfiddle below:
http://jsfiddle.net/jaypanares/Loatezun/1/


testing/sensortest: Fix printf format warning

Summary
sensortest.c: In function 'print_gps':
Error: sensortest.c:169:29: error: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type 'uint64_t' {aka 'long unsigned int'} [-Werror=format=]
  169 |   printf("%s: timestamp: %llu time_utc: %llu latitude: %f longitude: %f "
      |                          ~~~^
      |                             |
      |                             long long unsigned int
      |                          %lu
......
  172 |          " %u\n", name, event->timestamp, event->time_utc, event->latitude,
      |                         ~~~~~~~~~~~~~~~~
      |                              |
      |                              uint64_t {aka long unsigned int}
Error: sensortest.c:169:44: error: format '%llu' expects argument of type 'long long unsigned int', but argument 4 has type 'uint64_t' {aka 'long unsigned int'} [-Werror=format=]
  169 |   printf("%s: timestamp: %llu time_utc: %llu latitude: %f longitude: %f "
      |                                         ~~~^
      |                                            |
      |                                            long long unsigned int
      |                                         %lu
......
  172 |          " %u\n", name, event->timestamp, event->time_utc, event->latitude,
      |                                           ~~~~~~~~~~~~~~~
      |                                                |
      |                                                uint64_t {aka long unsigned int}
sensortest.c: In function 'print_gps_satellite':
Error: sensortest.c:183:29: error: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type 'uint64_t' {aka 'long unsigned int'} [-Werror=format=]
  183 |   printf("%s: timestamp: %llu count: %u satellites: %u", name,
      |                          ~~~^
      |                             |
      |                             long long unsigned int
      |                          %lu
  184 |          event->timestamp, event->count, event->satellites);
      |          ~~~~~~~~~~~~~~~~
      |               |
      |               uint64_t {aka long unsigned int}

Impact
Fix the warning by PR https://github.com/apache/incubator-nuttx-apps/pull/893
Testing
Pass CI

Note both PR https://github.com/apache/incubator-nuttx-apps/pull/894 and https://github.com/apache/incubator-nuttx/pull/4846 need merge to fix the CI break.

Note both PR https://github.com/apache/incubator-nuttx-apps/pull/894 and https://github.com/apache/incubator-nuttx/pull/4846 need merge to fix the CI break.


Can not install with laravel-helpers 3

We should be able to install package with any version of LaravelHelpers greater than 2.1

Fixed


Navigation bar overlap the tableview content after adding the UIRefreshControl?

Hi
I'm getting the issue that when I scroll up, the navigation bar is moved up, the tableview is sticked under the status bar. The I scroll down, the tableview is still with the status bar, the navigation bar overlap a part of the uitableview.
I disabled adjust scroll view inset and set 'hasCustomRefreshControl = YES'. The navigation controller is inside a tabbar.
Anyone know how to fix this?

#99
szweier's comment may helpful.
if you have extensionView, try set that "-64" more smaller.

Fix that by making the refresh control as an extension view:
[self.shyNavBarManager setExtensionView:refreshControl];
That's weird. It supposed to be
self.shyNavBarManager.hasCustomRefreshControl = YES;
I still dont know why?!

Fix that by making the refresh control as an extension view:
[self.shyNavBarManager setExtensionView:refreshControl];

I didn't see that and I didn't do it.
I have a custom refreshcontrol and an extensionView.
here is my part of code in TLYShyScrollViewController.m
- (CGFloat)updateLayoutIfNeeded
{
    CGFloat magicFloat = self.hasCustomRefreshControl ? -217 : 0;

    if ((self.scrollView.contentSize.height < FLT_EPSILON &&
        ([self.scrollView isKindOfClass:[UITableView class]] || [self.scrollView isKindOfClass:[UICollectionView class]])) ||
    (self.scrollView.contentOffset.y <= magicFloat)) {
        return 0.f;
    }
    //...


Magento convert Compass to Bourbon

Hello,
Magento 1.9 comes with a compass install which uses ruby and is slow (esp with magento's huge scss files).
Do you know of a way I can convert the compass inside Magento to bourbon instead.

Hey!
I don’t know of an automated way, unfortunately. But some of the mixins between Bourbon and Compass are quite similar in syntax and function, so it may not take too much effort.
Also: no need to post the same question to GitHub, Twitter and Gitter. We’ll see it in any one of those places. :smiley:


Empty View remove.

How can I remove Empty View (No Content) using a button click event?

The return value of the hasContent method determines which view is going to be shown on screen. If you'd like to remove the empty view, you may return false from hasContent and reload the UI by invoking endLoading().


Optional find dependency in installed cmake config.

Following up https://github.com/dmlc/xgboost/pull/6159 .  This PR removes find_dependency in CMake config and make sure dependencies are private if xgboost is built as shared library (the default).
An issue was found during writing another C demo for external memory, where I have to set the project with CXX language to get CMake working (but I'm writing a demo for C).  Also FindNccl is a custom script in xgboost which is not available as part of CMake, adding it to dependency will break users' code.
After the PR we simply include gputreeshap header instead of linking it due to a CMake error saying it's not in the export set when built as a static library.
Other than these, I added a simple script using readelf to show that the C demo is not linking anything from the dependency set of xgboost.

Codecov Report

Merging #7099 (756a953) into master (77f6cf2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7099   +/-   ##
=======================================
  Coverage   81.59%   81.59%
=======================================
  Files          13       13
  Lines        3901     3901
=======================================
  Hits         3183     3183
  Misses        718      718

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 77f6cf2...756a953. Read the comment docs.


Updates appveyor and travis for newer node versions.

Wow AppVeyer takes forever. I'm sitting on the edge of my seat here!

Yeah, it'd be nice to have more concurrent builds.


Per request scopes in e.g. Autofac will eat resources

Sample here: https://gist.github.com/danielwertheim/887868c17ab8cd67be44
Kind of followed your sample code... Probably have missed something. And yes, I know I could inject Func<SomeDependency> instead and have the handler resolve and dispose....
But how do I acomplish per-routed message scoped handlers? If not possible with MediatR, perhaps state that clearly in the sample?

See http://binarysculpting.com/2012/08/19/using-idisposable-with-autofac/. You need to make sure you resolve from a lifetime scope, and that the scope is disposed. Otherwise, Autofac will hold on to your transient instances and you'll have a leak.

I know. And that's why the sample is misleading as it will consume new resources for each message routed as the gist will show.
So the Q is how to achieve this with MediatR in e.g. something like a long running windows service?
Can it? As you would need to get hooked into before and after the func for resolving the handler....
Just raising my voice as this easily could lead to people getting more and more handler resources that in turn has resources on ... ...

So the Q is how to achieve this with MediatR in e.g. something like a long running windows service?

Just resolve the stuff you need from a lifetime scope (as shown in the blog post mentioned)? Make sure you dispose it when you're finished.

As you would need to get hooked into before and after the func for resolving the handler....

I'm not sure what you're talking about here. What func?

Just raising my voice as this easily could lead to people getting more and more handler resources that in turn has resources on ... ...

I don't think anyone here are experts on all the containers in the samples that have been contributed to this repo, and by all means, they could absolutely have bugs. I guess it's generally expected to know how the container you're using works. That should probably be a requirement anyway, using MediatR or not :wink: If you're having trouble wiring up the container properly, maybe it's best to just go "pure DI"-style? :smile:

You want to be able to create the lifetime scope before the ....what you call "instance factories" are called and then be able to release the scope after a message has has been routed. Not the same lib, but you get the point: Something like this: http://danielwertheim.se/routemeister-and-autofac/
But MediatR probably has another lifecycle of the closure (call to the instance factories) giving you the actual instance of the handler. Or? Because I hope you aren't saying that if you want "per-request style resourced routing", you have to rebuild all the routes and the factory again for each request?

You want to be able to create the lifetime scope before the ....what you call "instance factories" are called and then be able to release the scope after a message has has been routed.

Basically, you do what you want. MediatR doesn't dictate how you want to wire up your container, and I don't think it should. The sample is just that -- a sample, and it works fine.

MediatR probably has another lifecycle of the closure (call to the instance factories) giving you the actual instance of the handler.

I'm not sure what you're talking about here. MediatR doesn't care about lifetime. It just calls one of the delegates passed to it when you send a request or notification, that's it! The rest is up to the user/container. It's open source, go look for yourself. The code base is a couple hundred lines of code, max :grin:

Because I hope you aren't saying that if you want "per-request style resourced routing", you have to rebuild all the routes and the factory again for each request?

Again, I'm not sure what you mean with "routing" and "rebuild all the routes". Is this something in your application. It doesn't seem related to MediatR.

Let me try again then... There seem to be no way to accomplish this, without recreating an instance of Mediator. Let me elaborate:
You inject the InstanceFactories "resolvers" in the constructor to `Mediator:
https://github.com/jbogard/MediatR/blob/master/src/MediatR/Mediator.cs#L29 and these resolvers would need access to the child scope, hence they need to be able to extract one tied to a certain message.
Suppose we do a Publish of two notifications: Notification1 and Notification2 using: https://github.com/jbogard/MediatR/blob/master/src/MediatR/Mediator.cs#L64
During this, an InstanceFactory is called to resolve the "handler" for each message. Now. To get the resolver to actually use a child scope, you would need to pass that e.g. as state with the message, so that the InstanceFactory could extract that and use it. Sure, you could potentially allow two hooks: OnBeforeRoute which could use CallContext and stash away arbitrary data (e.g. the scope); then extract that in the injected InstanceFactory, then release it in something like OnAfterRoute.
But given your answers there seem to be now way to accomplish this in MediatR. Hence you are either left to:

Recreate Mediator for each message routed (guessing more penalty hits)
Not expect to get a working solution for Handler per message, and use service locator pattern in your handlers.

And no, MediatR should not be tied to a IoC or something, but if there's no design decisions taken to provide tooling for the above scenario; you should clearly state: Either recreate Mediator instances or use some service locator inspired pattern in your handlers and keep them as singletons. So easy for people to think they are "safe" in setting the handlers as transient, but because how MediatR integrates with what ever you hook in, it can not be cleaned properly unless you use transient Mediator instances....

What penalty hits for resolving per request?
On Sunday, March 20, 2016, Daniel Wertheim<EMAIL_ADDRESS>wrote:

Let me try again then... There seem to be no way to accomplish this,
without recreating an instance of Mediator. Let me elaborate:
You inject the InstanceFactories "resolvers" in the constructor to
`Mediator:
https://github.com/jbogard/MediatR/blob/master/src/MediatR/Mediator.cs#L29
and these resolvers would need access to the child scope, hence they need
to be able to extract one tied to a certain message.
Suppose we do a Publish of two notifications: Notification1 and
Notification2 using:
https://github.com/jbogard/MediatR/blob/master/src/MediatR/Mediator.cs#L64
During this, an InstanceFactory is called to resolve the "handler" for
each message. Now. To get the resolver to actually use a child scope, you
would need to pass that e.g. as state with the message, so that the
InstanceFactory could extract that and use it. Sure, you could
potentially allow two hooks: OnBeforeRoute which could use CallContext
and stash away arbitrary data (e.g. the scope); then extract that in the
injected InstanceFactory, then release it in something like OnAfterRoute.
But given your answers there seem to be now way to accomplish this in
MediatR. Hence you are either left to:

Recreate Mediator for each message routed (guessing more penalty
hits)
Not expect to get a working solution for Handler per message, and
use service locator pattern in your handlers.

And no, MediatR should not be tied to a IoC or something, but if there's
no design decisions taken to provide tooling for the above scenario; you
should clearly state: Either recreate Mediator instances or use some
service locator inspired pattern in your handlers and keep them as
singletons. So easy for people to think they are "safe" in setting the
handlers as transient, but because how MediatR integrates with what ever
you hook in, it can not be cleaned properly unless you use transient
Mediator instances....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jbogard/MediatR/issues/71#issuecomment-198946942

To clarify. This is not a bug and I'm not saying it will have a hit. It was a guess ("Guessing more penalty hits"). This cause you have handler caches etc in there that in that case would be set aside right? But I haven't looked closely. And yes, even if, it's most likely negligible, seen to all bits and pieces involved where MediatR would be used.
If this is the recommendation, to have the MediatR instance created on each request and thereby being able to manage the scope. I'm happy to have gotten this clarified for me.
Assuming usage of MediatR in conjunction with an IoC-container is a rather normal use-case, I still think you should emphasise this a bit more. Help people to use it right. But I can have missed that part trying it out.

There's really not much of a recommendation here. I guess I do assume people use a container because otherwise it'd be a pain to build out the handler factories.
If the usage isn't clear, I'm happy to accept PRs for the readme or just edit the wikis directly. This is code I was copy-pasting amongst a dozen projects, so there might be a bit in my head about how I use it.

What if the Mediator's caches were changed to static fields? This way they would persist across instances, thus creating a new instance of the Mediator for each request would not cause any performance hit.

@leddt Yeah, I have no clue why they weren't static in the first place :smile:

Just to spite you @khellang

Shouldn't it be the concern of how to configure the IMediator on the IoC (single instance vs instance per request) instead of without any usage choice, have the Dictionaries always on memory due their static nature?

@kappy The dictionaries are internal implementation details to cache types created using the reflection APIs. I don't think that's something the user needs to know or care about :smile:

@khellang Indeed, but then, on the other side, by making them static, you're limiting the their lifetime to be always in memory despite the lifetime configuration of the Mediator.
I didn't find any Thread-safety issues on the Mediator itself (I also didn't look too hard) so I don't see any issues on configure the Mediator as a Single Instance, something that Ioc containers already do

@kappy the problem with configuring it as a singleton is that the factory methods it receives as constructor parameter cannot use a per-request container, which is a very common pattern in web apps.

Also, note that the caches in question are simple type caches, not instance caches. Memory usage should be pretty small for that.
I guess we could make the caches be another constructor dependency of the Mediator, which would enable users to configure the caches lifetime as they want, but then that would expose an implementation detail to the outside world, which is better kept hidden.

@leddt aren't the factory method just delegates? So all you're doing is querying the Ioc for the instances of the type, based on the scope it currently is.
Even if the Mediator is configured as Singleton, it could resolve the handler instances based on the current scope.

@kappy I'm only familiar with StructureMap, so maybe it's different with other containers. In the StructureMap sample for Mediator, the delegate's configuration looks like this:
cfg.For<SingleInstanceFactory>().Use<SingleInstanceFactory>(ctx => t => ctx.GetInstance(t));
cfg.For<MultiInstanceFactory>().Use<MultiInstanceFactory>(ctx => t => ctx.GetAllInstances(t));

If Mediator is a singleton, these delegates will be created only once, using the same container (the ctx variable in this code) as the Mediator itself.
But in StructureMap you create a nested container to handle lifetime scopes. The nested container holds all of it's own instances, and refers to it's parent container to resolve longer lived objects (I'm probably explaining this terribly, I'm sorry).
So it is my understanding that, with StructureMap, using a singleton Mediator it would not be able to resolve request-scoped services. However it is possible that I am completely wrong about this. If that's the case then I guess the caches should indeed stay as instance fields.

@leddt You're not wrong. but then again, you can configure the delegates not form the context you're registering the Mediator, but from the actual Mvc (in this case) DependencyResolver. This way, the delegates will use the nested container that is created to handle the Request.
For<SingleInstanceFactory>().Use<SingleInstanceFactory>(ctx => t => DependencyResolver.Current.GetService(t));
For<MultiInstanceFactory>().Use<MultiInstanceFactory>(ctx => t => DependencyResolver.Current.GetServices(t));

I've written 2 samples, one using Autofac and another using StructureMap using exactly this configuration in here.

@kappy I see!
I wonder if this can work with Owin? The challenge with Owin is that there is not really a static way of getting the current request context. I'll have to think about it :smile:

The challenge with Owin is that there is not really a static way of getting the current request context.

Some would argue that accessing a service locator in a static way like this is an anti-pattern :wink:

@leddt at least with Autofac, you can reach the scope with Owin using the owinContext.GetAutofacLifetimeScope();
But I think we're getting a bit off topic. For me, the real question is if we sacrifice the Configuration easiness against keep a cache of types.

The only disadvantage I see is if we change in runtime the container types registry (a bit like a plugin system for handlers). But this is clearly an edgy case.
I would say, go for this approach.


Assignment1 done

Great! Now complete the last steps from instructions:
git checkout main
git pull upstream main
git push origin main


Issues don't fully deofuscate

Platform
Dart
Obfuscation
Enabled
Debug Info
Enabled
Doctor
[✓] Flutter (Channel stable, 3.16.9, on macOS 14.4 23E214 darwin-arm64, locale en-AU)
• Flutter version 3.16.9 on channel stable at /Users/user/.puro/envs/stable/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 41456452f2 (9 weeks ago), 2024-01-25 10:06:23 -0800
• Engine revision f40e976bed
• Dart version 3.2.6
• DevTools version 2.28.5
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/user/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• ANDROID_HOME = /Users/user/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15E204a
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2023.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
[✓] IntelliJ IDEA Community Edition (version 2023.2.5)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 76.3.4
• Dart plugin version 232.10248
[✓] VS Code (version 1.85.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.80.0
[✓] Connected device (3 available)
• iPhone 15 Pro (mobile) • E37C05EC-694C-4EDF-928A-4D162D46673E • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)
• macOS (desktop)        • macos                                • darwin-arm64   • macOS 14.4 23E214 darwin-arm64
• Chrome (web)           • chrome                               • web-javascript • Google Chrome 123.0.6312.86
[✓] Network resources
• All expected network resources are available.
• No issues found!
Version
7.16.1
Steps to Reproduce

Obfuscate your app and compile it with these flags:

--obfuscate --split-debug-info=build/app/outputs/symbols \
--extra-gen-snapshot-options=--save-obfuscation-map=build/app/outputs/obfuscation_map.json \

Upload the symbols
Generate an exception
Open the Sentry Issues Screen
See something like this:

Expected Result
All symbols will be deofuscated, regardless of where they are shown in the Sentry UI.
Actual Result
I keep seeing weird names like dw in many of my Sentry issues. I imagine Sentry is not deofuscating some symbols, or the tool is not uploading them correctly, or it's not finding the folder where my symbols where stored.
Are you willing to submit a PR?
None

This is already tracked by https://github.com/getsentry/sentry/issues/48334
This is a known issue and we have to plan how to fix it, at least for AOT apps.


HappyPack does not notices the cache?

I am not sure why, but when using webpack-dev-server, happypack is writing .happypack directory but on the same time, it is not able to detect the cache and regenerates the entire build on subsequent runs.
Any suggestion?

Hmmm, that's strange. I personally don't use the devserver but I'll take a look.

Looks like it does not work even if using the command line tool:
./node_modules/.bin/webpack --config Webpackfile.js
leads to:

Every time.

Hmm, curious. What does the .happypack/ folder contain? Is there a cache--[something].json file?

Yes, I have one file per loader id

Size of the file? Is it possible to paste the contents of it somewhere?

$ ls -la | grep cache

-rw-r--r--    1 vchianese  staff  66262 Jan 13 14:56 cache--coffee.json
-rw-r--r--    1 vchianese  staff  21430 Jan 13 14:56 cache--ect.json

I'll try to do something to post its content.

Thanks. The relevant bit in the cache contents will be an object with the key context; this controls whether the cache contents are valid or not between different runs.

The context object itself is empty
{"context":{},"mtimes":...

And then I have a mtimes object with path: mtime {}

@amireh Is that enough or - would you still want to have a look at files?

I know that the context should not be empty, at the very least it should contain a "loaders" attribute. I will take a look tonight if possible.
No need for the rest of the file contents, this is enough :) thanks
Which OS do you use btw? Is this on node 0.10 ?

$ uname -a
Darwin Vincenzos-MacBook-Pro.local 15.2.0 Darwin Kernel Version 15.2.0: Fri Nov 13 19:56:56 PST 2015; root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64
$ node -v
v0.10.37
$ npm -v
2.14.14

Ok, because the other similar report I got was also from OS X, but using node 0.12. Thanks, will update when I find something.

@XVincentX I just pushed 1.1.3 with a possible fix, please confirm when you can test it!

@amireh
So, now the context key is populated, but I am still getting no cache:
{
  "context": {
    "loaders": [
      {
        "path": "/somePath/lib/webpack/ect-loader.js"
      }
    ],
    "external": {}
  }
}

This is the second run:
$ ./node_modules/.bin/webpack --config Webpackfile.js
Happy[coffee]: Firing up! Version: 1.1.3. Using cache? yes. Threads: 3
Happy[coffee]: No cache was found, starting fresh.
Happy[coffee]: All set; signalling webpack to proceed.
Happy[ect]: Firing up! Version: 1.1.3. Using cache? yes. Threads: 3
Happy[ect]: No cache was found, starting fresh.
Happy[ect]: All set; signalling webpack to proceed.

So the examples seem to work if I run them using:
./node_modules/.bin/webpack-dev-server --config examples/single-loader/webpack.config.js

And they seem to be picking up the cache. Is there a special way you're running the devserver? Can i see the webpack config file please?

Can you verify whether this was fixed in 1.1.4 (see #17 for more information)?

This looks great. I'll let you know

@amireh Unfortunately no. I'll make other tests but at first glance it seems still broken.

@amireh
Ok I was tired of this problem and decided to investigate. Basically node 0.10 does not have fs.accessSync, but bs.existsSync.
Would that be possible to create a fallback for that?


Update package-lock.json

What kind of PR is this?:
/kind feature
/kind
What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:

/kind feature


Unclear whether to set HTTP Custom Header

Custom domain overview - Step 4, states request to AAD B2C endpoint includes a custom HTTP header that contains the original custom domain name. Yet Create a new Azure Front Door instance, shows a backend host header matching the b2clogin.com domain.
Should the backend host header be the custom domain name? Or the original {tenantname}.b2bclogin.com?

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

ID: 9c4a65cd-dae6-898a-514b-5bb9238f58a3
Version Independent ID: 9c2f7824-efed-7108-7c1e-eb2b57f3c0d6
Content: Enable Azure AD B2C custom domains - Azure AD B2C
Content Source: articles/active-directory-b2c/custom-domain.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@TheUniquePaulSmith
Thanks for your feedback! We will investigate and update as appropriate.

The document is correct. Both the Backend host name and the Backend host header  should be the same. This is the default behavior. The default value for the host header field is the host name of the backend.
The header that is mentioned in the overview is not the HOST header. It's a custom one X-Forwarded-Host.
I'm updating the article and close this issue.


actions.xml

Why isnt there an actions.xml

I am working on opening a feature in my app and I built an actions xml file.


Fix/272 set json as default type

Status

WIP
Description
A few sentences describing the overall goals of the pull request's commits.
Related PRs
List related PRs against other branches:

branch
PR

other_pr_production
link

other_pr_master
link

Todos

[x] Tests
[ ] Documentation
[ ] Changelog Entry (unreleased)

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
> git pull --prune
> git checkout <branch>
> grunt jasmine

Hi,
i not sure how the test are working so some hints would be nice :)

Hey @zerocity, thanks for the pr! For the test, seems good like that.


support avsc files

are there any plans to support avsc files?

It's something I'd like to support in the future, but not something I really have any free time to work on.
Ideally, .avsc, .avpr and .avdl files would all be parsed by different parsers (an actual parser for .avdl and walking over the existing JSON AST for .avsc and .avpr), into the same Avro AST. This would then allow things like go-to-definition and quick documentation lookup to work in a completely uniform manner across files.
If anybody wants to work on this, I'd happily review it.

+1

+1 (as a temporary relief is to associate .avsc with json, so reformatting works).

+1

+1

I take it this has never been done?

No, it hasn't.

+1

I've just deleted all the '+1' comments. GitHub has a reactions feature built in.
I'm archiving this repository as I don't have any time or inclination to work on it.


Fixed typo; Pressets -> Presets

Hey! 👋
Since the other guy finished the feature you wanted already, I fixed the typo.
It's "Presets" and not "Pressets".
Hope I changed it everywhere, so nothing breaks.
Regards,
Zentreax

@Zentreax Thanks for your contribution


[3.0] fix MergeableClusterInvoker NPE

issue #8890

Codecov Report

Merging #8891 (cada6ca) into 3.0 (4d42765) will decrease coverage by 0.10%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                3.0    #8891      +/-   ##
============================================
- Coverage     63.78%   63.67%   -0.11%
  Complexity      313      313
============================================
  Files          1170     1170
  Lines         49330    49294      -36
  Branches       7351     7345       -6
============================================
- Hits          31467    31390      -77
- Misses        14420    14456      +36
- Partials       3443     3448       +5

Impacted Files
Coverage Δ

...o/rpc/cluster/support/MergeableClusterInvoker.java
38.88% <0.00%> (ø)

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...ava/org/apache/dubbo/config/DubboShutdownHook.java
59.25% <0.00%> (-14.82%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...moting/transport/netty4/NettyEventLoopFactory.java
22.22% <0.00%> (-7.78%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
77.58% <0.00%> (-6.90%)
:arrow_down:

...ache/dubbo/remoting/api/NettyEventLoopFactory.java
30.00% <0.00%> (-6.37%)
:arrow_down:

.../threadpool/support/limited/LimitedThreadPool.java
83.33% <0.00%> (-5.56%)
:arrow_down:

... and 39 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 4d42765...cada6ca. Read the comment docs.


Implement encrypted path backend

I'd like to provide an encrypted path backend, like encFS. The general idea would be to encrypt each filename with a stream chipher based on a password.
This wouldn't work very well for teams (they'd have to share the same path-encryption-password), but for individuals wanting to protect their secret names this would be a nice feature.

I wonder if there would be any way to make this work for teams.
Would a map file possibly be a solution? It would simply contain the mapping between the random names and the plaintext names, this file would then be encrypted in the same way as the secrets themselves. You would need one map file next to each .gpg-id file. This would make gopass pretty incompatible with pass but would stick with the principle of storing the data in such a way that it can be read without (go)pass.

Would support for Keybase's encrypted git repos serve the same purpose?

This was partly fixed with #1366 already.


Add benches for raw multiproof and IPA

This PR adds extra benchmarks for the cryptography lowest layer, particularly multiproofs and IPA.
I'm currently digging into go-ipa applying some missing or new optimizations, and I wanted to have a reference on the performance of the Rust implementation, thus creating these benchmarks.
This has been fruitful since looking at some numbers made me realize the Rust implementation has some extra trick missing in the Go one, which I'll apply soon.
Eventually, I'll reference these PR benchmark results in the Benchmark section of the summary document.

I'll fix the lints soon.

@kevaundray, done.

Definitely I've to adjust my linters in Vim! I'll take care of clippy now. :P

Clippy is failing that I didn't change in this PR, probably because the version isn't fixed.
The lint is quite basic, so not sure.
In any case, fixed now!
cc @kevaundray

I realized that the ipa multipoint is a different crate, which already has some similar benchmarks.
I'll close this PR and look at https://github.com/crate-crypto/ipa_multipoint .
I see some benchs there that are probably quite similar to these ones (and if not, I can create a PR there).

See https://github.com/crate-crypto/ipa_multipoint/pull/11


Add galaxy s21 to supported devices

Could you please post your device information (can be copied from inside the app) so I can take a look?

App Version: 2.3.3 (25)
App Build Type: release
App Installer: dev.imranr.obtainium
Software: Android 14 (34)
Light Levels: 5
Manufacturer: samsung
Brand: samsung
Model: SM-G991B
Device: o1s
Board: samsung
Supported ABIs: arm64-v8a,armeabi-v7a,armeabi

Sorry I thought this was a list of supported devices I just realized it was for unsupported.  This device works with the app.


[Diagnostics] Improve never-returning call diagnostic

This patch just improves the wording and provides a little more clarity about why this code is unreachable.

@swift-ci please smoke test


feature 555 master 3.0 simplify dependencies

Verified that all use case tests run with this environment in master_v3.0 (georgemccabe fork), the installed pytest locally and verified that all unit tests run successfully.

Replaced by PR #559


consider storing optional client identity meta data

 Issue by sym3tri
Thursday Dec 11, 2014 at 18:41 GMT
Originally opened as https://github.com/coreos-inc/auth/issues/146

There are many more OPTIONAL fields beyond just id and secret. For instance name and contacts seem like good ones for us to consider given that we'll provide a listing of all registered clients in the admin UI and client ids are not very user-friendly.
http://openid.net/specs/openid-connect-registration-1_0.html#ClientMetadata

All fields in client metadata is stored in the DB.


Instant paste Permission

Hi!
Your application is really nice, thanks for the work on it!
One thing that is unclear to me is the following. When I'm in the Clipboard overview

I would expect that there is a key combination, which lets me instantly paste. I tried alt+enter, which brings me to the macOS permissions popup:

Following that, I cannot see Maccy in the list (Security & Privacy > Privacy > Accessibility), thus I cannot grant it permission.
Am I on the right path to "paste from the list"?
Am I doing something wrong? Or is this feature only available from the paid version in the App Store? Currently I installed via brew install --cask maccy).
Cheers!

Oops, I missed the "+" bottom of the list. Problem solved, things are working :)


use rubygems.org for gem artifacts

this will remove the remaining problems in #1669
CLA will come once you decided to pull in this patch

ok - travis would need to use mvn-3.3.x
let's see how to achieve this

Don't worry too much, in the longer run we are wondering about switching to a native maven scss compiler.

The way to have this work, it to have a maven profile in library that activates the local maven extension is the maven version is greater than 3.3.1 and otherwise uses torquebox proxy. But I'm not sure the complexity is worth it.

with jruby itself we use: https://github.com/jruby/jruby/tree/master/.mvn/wrapper and https://github.com/jruby/jruby/blob/master/mvnw
and tell travis to use those mvnw

but it also needs to enforce maven-3.3.x somewhere.

Switched to using libsass for compilation https://jira.sakaiproject.org/browse/SAK-30439 so this is no longer applicable. Thanks!


feat(sdk): support for claim metadata as jsonpath value

Codecov Report
Attention: Patch coverage is 87.50000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 89.06%. Comparing base (97a0fe4) to head (b8f1b21).

Files
Patch %
Lines

pkg/credentialschema/credentialdisplay.go
87.50%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #760      +/-   ##
==========================================
- Coverage   89.08%   89.06%   -0.02%
==========================================
  Files         104      104
  Lines        4582     4592      +10
==========================================
+ Hits         4082     4090       +8
- Misses        324      325       +1
- Partials      176      177       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[6.0][Distributed] Adjust whenLocal impl to avoid potential ABI issues

Description: This is a follow up to https://github.com/swiftlang/swift/pull/74324 resolving rdar://129651474 where we added a missing @AEIC to the whenLocal function which adopted typed throws. This caused Distributed breakage in Beta 1. This PR here is a follow up to make the transition even safer, by introducing the "accidentally exposed symbol" (by not having made the new method AEIC from the beginning), such that applications which build against that we don't "remove" this symbol without replacement -- i.e. this patch doesn't "add" an API, but "keeps it" for ABI reasons, even if no new code against the new SDK should ever be touching that old symbol.
Scope/Impact: Distributed module users are impacted if they happened to build against an SDK with the non-@AEIC declaration of the whenLocal function.
Risk: Low, this only adds an "old" abi entrypoint which may have been used by someone in the brief beta 1 period.
Testing: CI testing and we verified manually with @xedin in a real reproducer project the AEIC approach is correct overall, and this only adds an "old" abi entrypoint.
Reviewed by: @xedin
Original PR: https://github.com/swiftlang/swift/pull/74606
Radar: rdar://130610949

@swift-ci please test


KOGITO-3948 Redis persistence

Jira: https://issues.redhat.com/browse/KOGITO-3948
Goal: Add redis modules to bom + redis test resource.
Main PR on kogito-apps: https://github.com/kiegroup/kogito-apps/pull/574
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

Jenkins retest this please

Jenkins retest this please

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

jenkins retest this please

The Linux check is successful.


RFP - kite

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://www.kite.com
Direct download URL for the software / installer : https://alpha.kite.com/release/dls/windows/current
Software summary / short description: AI-Powered code completion

kite doesn't exist anymore: https://www.kite.com/blog/product/kite-is-saying-farewell/


Implement dual certificate support (RSA/EC on same domain)

What does this PR do?
This allows loading multiple certificates for the same domains as long as they aren't of the same type (RSA vs. EC, with EC including ECDSA and Ed25519) and also enables generation of default certificates for RSA and ECDSA.
Fixes #3483.
Motivation

Allowing both RSA and EC certificates for a domain allows using a wider range of cipher suites, since some only work based on an RSA certificate and some only work with an EC certificate. Newer clients could then be served the EC certificate and use newer cipher suites for better and faster encryption while older clients can fall back to RSA.
More

[x] Added/updated tests
[x] Added/updated documentation

Additional Notes
This merge request does not implement nor enable any capabilities for certificate providers to request certificates for both RSA and EC, instead it currently relies on the configuration either being set up with usage of default certificates or existing certificates (for example by providing them from another ACME client). I see this is as a separate follow-up issue. See #4993 for a previous PR that attempted to change the default key type for the built-in ACME client.
This PR tries to implement support as transparently as possible, but it includes a deprecation of the defaultCertificate TLS store configuration key and replaces it with the defaultCertificates array while still keeping support. This should probably be discussed on before merging this.

etcd-related integration testing is failing for reasons that are unknown to me, the results also seem inconsistent as the testing fails with different configuration entries missing on my local run compared to the run on Semaphore CI.
Local run:
----------------------------------------------------------------------
FAIL: etcd_test.go:59: EtcdSuite.TestSimpleConfiguration

etcd_test.go:157:
    c.Error(text)
... Error: --- Expected
+++ Got
@@ -27,7 +27,6 @@
       "tls": {
         "domains": [
           {
-            "main": "aaa.localhost",
             "sans": [
               "aaa.aaa.localhost",
               "bbb.aaa.localhost"
@@ -36,8 +35,7 @@
           {
             "main": "bbb.localhost",
             "sans": [
-              "aaa.bbb.localhost",
-              "bbb.bbb.localhost"
+              "aaa.bbb.localhost"
             ]
           }
         ]
@@ -110,8 +108,7 @@
     "striper@etcd": {
       "stripPrefix": {
         "prefixes": [
-          "foo",
-          "bar"
+          "foo"
         ],
         "forceSlash": true
       },
@@ -154,8 +151,7 @@
         "service": "simplesvc",
         "mirrors": [
           {
-            "name": "srvcA",
-            "percent": 42
+            "name": "srvcA"
           },
           {
             "name": "srvcB",

Would be really happy to see this added!

Hello @icedream,
We have upgraded Traefik to be using golang 1.14, and with that brought some TLS changes that affect this PR.

Do you think that this PR is still needed with the changes to Golang 1.14 TLS certificate handling?
Do you think that you could use the 1.14 features to implement this feature while reducing the complexity?

Please let us know!

Hello,
while I didn't check through the changes in Go 1.14 in detail for this PR yet, here are a few points from the changelog that will become highly relevant for this PR:

When multiple certificate chains are provided through the Config.Certificates field, the first one compatible with the peer is now automatically selected. This allows for example providing an ECDSA and an RSA certificate, and letting the package automatically select the best one. Note that the performance of this selection is going to be poor unless the Certificate.Leaf field is set.

This means if we fully want to off-load certificate selection to Golang itself, we would need to completely rewrite how Traefik manages certificates internally. Right now Traefik handles that logic itself and I don't know how much time I would need to pour into this PR to make the code work around what Go now offers. I am a bit limited in how much I can work at this PR at the moment but creating a second PR to replace this one seems like the thing to do here.

The new (*ClientHelloInfo).SupportsCertificate and (*CertificateRequestInfo).SupportsCertificate methods expose whether a peer supports a certain certificate.

This would be the thing to use if we are going to keep how Traefik currently implements TLS logic.
If anyone else checked through the changes and has concrete suggestions for reworking this PR, I will definitely take these suggestions into account!

This means if we fully want to off-load certificate selection to Golang itself, we would need to completely rewrite how Traefik manages certificates internally.

The team agrees with your assessment, but are limited in the ability to scope or commit to building a proposal for this change.

creating a second PR to replace this one seems like the thing to do here

Given the capabilities introduced in 1.14 this makes the most sense. For now, I propose closing this PR and updating the original issue (https://github.com/containous/traefik/issues/3483) with a summary of what may be required to exploit the capabilities of most recent updates to the tls package.


ci(rustdoc): lint all crates for rustdoc errors

cargo rustdoc only generates docs for the root crate, not its dependencies, cargo doc does.

Unless we can have a --all-features that actually works, there will be broken links in some feature configurations. If we merge this, our options are to

just have no links in some places where there could be some
#[cfgattr(feature = "...", doc("Some doc with [link]"))] / #[cfgattr(not(feature = "...", doc("Some doc without link))] all links (and that doesn't even work everywhere, esp. not in feature documentation)

I suggest we either delay that, or tell it to accept broken links, or ensure that --all-features works and apply that.

(Manually moving a comment from @ROMemories over from https://github.com/future-proof-iot/RIOT-rs/pull/251#issuecomment-2051951335)

I'd say it makes sense to enable all features that are not mutually exclusive, it's just annoying because it's not factored out, but we can live with that for now. Also they do also need to be enabled when actually building the docs (not just when checking for broken links), otherwise the links will actually be broken in the rendered docs.

It's Rust features, they are supposed to not be mutually exclusive :-)
They don't have to typecheck and build without warnings, but they can doc without warnings. This example is not pretty (wouldn't want to do it precisely like that), but it shows that not all warnings that happen at check time with --all-features also trigger the rustdoc checks:
#[cfg(feature = "a")]
mod af {
    pub fn f() {}
}

#[cfg(feature = "b")]
mod bf {
    pub fn f() {}
}

// At check time, these warn.
pub use af::*;
pub use bf::*;

So our policy regarding links in rustdoc is to always add links when items are in scope, enable the relevant features when
generating the documentation to have as many items in scope as possible, and, when it is not possible, to not link to
items.

Sounds reasonable to me.
LGTM.


Admin role clarification

This page states, "You must have admin permissions to do this."  Can you clarify the minimum permissions role needed for adding an alias?  Surely they don't have to be a global admin.  Do they have to be an Exchange admin?  Is it possible to add an alias with less?

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

ID: 50963b73-8563-f99a-72f7-bf4037965cde
Version Independent ID: 5daa29ed-8092-3a79-c011-8bcbe0225b2c
Content: Add another email alias for a user
Content Source: Office365-Admin/email/add-another-email-alias-for-a-user.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@MidSpeck  - Thank you for submitting feedback.
I will get this issue over to the O365ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@MidSpeck  Thank you for your feedback. You are correct, There are more than one role which you could use to add an alias. I have made the change to the doc via PR # https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/pull/832
Thanks
Sri

@MidSpeck  - From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/commit/18b2b3432fbf1c65320977256db8ab7f62f6cdec but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!


Use sell time when there's not exit_tick_time

Coverage increased (+0.1%) to 35.958% when pulling 0ad637a91efb5e8fd426f37ce20198e8eefca317 on qingweibinary:qingwei/workaround_broken_api into 7b450a2eeb855de1786061e3de42294fdafe0e1f on binary-com:master.


Fixed The Overlapping Chatbot and Scroll to Top Button

Description
Hey @sk66641

issue closes #492

I have fixed the overlapping chatbot and scroll to top button

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

@RadhikaMalpani1702
Now, it's overlapping with the sidebar

@sk66641 Then I will just remove the scroll to top button from the home page as it is not needed there? as the home page is short

@RadhikaMalpani1702 dont remove the scroll to top button instead put it above the chatbot in the main page

@RadhikaMalpani1702 dont remove the scroll to top button instead put it above the chatbot in the main page like in between the social icons and the chatbot

@RadhikaMalpani1702 yes it can be

@aditya-bhaumik and @sk66641 Okay i will do it

Hey @sk66641 and @aditya-bhaumik Made the changes

@RadhikaMalpani1702 there still many bugs like in small screen it is not visible and why is the back to top button is always visible but it should only be visible when the screen is scrolled down
@sk66641 can you please check this as i think this is introducting new bugs

@sk66641  @aditya-bhaumik If you can see the code changes what I have done then those are only CSS adjustments, the scroll to top button was like this already, please review the code changes

I have only done CSS changes
For small screens it is not visible because whoever made this button he did not add media properties
The button is always visible because its JavaScript code has that logic (I didn't even touched it)
lastly I raised the issue/bug for solving the overlapping of scroll to top button because of Chatbot

I hope I was able to explain it to you! If you want it then I will fix it.

@RadhikaMalpani1702 yes for smaller screens you need to make css changes only check the website it is visible before you made the changes as for the other bug i checked it was already there so you dont need to fix that fix for the smaller screens as it was the css change which is caused it to disappear from the smaller screens

@aditya-bhaumik Sure, I will make the changes!

@RadhikaMalpani1702 okay you can try making changes to the javascript logic so that the button is visible only when we sroll down and when we press on it it should go back up and also the smaller screen fix
I will update the issue level to 3 after these changes

@aditya-bhaumik Done the changes the scroll to top button is now appears only when scroll down a bit (Except home page as before) and on click it smoothly scrolls up to the page

can you send a recording showing it please


ssl_transport_security.cc: Make it compile with libressl

Compiling grpc latest master [1] on Windows 10 Pro using MSVC 2019 and using LibreSSL 3.8.2 as SSL provider (package) does currently not work, as the functions X509_STORE_set_get_crl/X509_STORE_set_check_crl and the define SSL_OP_NO_RENEGOTIATION are not present.
Employ a workaround seen in the surrounding code by making the code block only for openssl available.
[1]: 24f89637 ([Test] Removed obsolete node test from run_tests.py (#35525), 2024-01-19)

@markdroth this seems fine to me, can you take a look. We don't explicitly support LibreSSL nor make any guarantees about it's behavior, but I don't mind doing little things to let it compile.
I think the test failures are unrelated flakes


no deadzones

there are no dead zones to the controler and so it dosent alow me to control without getting a stuck input

Hello, please tell me if this help : https://github.com/getItemFromBlock/Create-Tweaked-Controllers/wiki/Tutorials-on-the-advanced-mode#configuring-a-deadzone

You might have to enable the advanced input mode for that however


ellipses appears/disappears every time codefile is edited

Issue Type: Bug
create typescript file
focus cursor in open file
type anything
result:
line is inserted momentarily at top of file with '...'
all file contents shift down one line
line disappears
all file contents shift up one line

This becomes tedious and distracting, causing my eye to chase the cursor and the area I'm actively editing
Thanks

VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:29.527Z)
OS version: Linux x64 5.13.0-30-generic
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz (8 x 2000)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 1

Memory (System)
62.46GB (36.31GB free)

Process Argv
/home/subatai/Documents/code/clubforce/app --crash-reporter-id e0ed23cd-195f-4cf0-a266-26d0b87e72fc

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (45)

Extension
Author (truncated)
Version

cucumberautocomplete
ale
2.15.1

laravel-extra-intellisense
ami
0.6.2

ng-template
Ang
13.2.4

docs-view
bie
0.0.9

vscode-intelephense-client
bme
1.8.2

npm-intellisense
chr
1.4.1

vscode-postgres
cko
1.4.0

vscode-database-client2
cwe
4.7.3

vscode-eslint
dba
2.2.2

githistory
don
0.6.19

gitlens
eam
12.0.0

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.24

prettier-vscode
esb
9.3.0

vscode-jest-runner
fir
0.4.47

gitkraken-authentication
git
1.0.3

gc-excelviewer
Gra
4.0.50

todo-tree
Gru
0.0.215

vscode-test-explorer
hbe
2.21.1

rest-client
hum
0.24.6

open-in-browser
igo
1.0.2

angular-essentials
joh
12.0.0

vscode-peacock
joh
4.0.0

eml
lei
0.4.0

template-string-converter
meg
0.6.0

vscode-docker
ms-
1.20.0

csharp
ms-
1.24.1

vscode-dotnet-runtime
ms-
1.5.0

remote-containers
ms-
0.217.4

test-adapter-converter
ms-
0.1.5

debugger-for-chrome
msj
4.13.0

angular-console
nrw
17.14.1

autolaunch
phi
2.0.9

material-icon-theme
PKi
4.13.0

fabric8-analytics
red
0.3.5

vscode-commons
red
0.0.6

vscode-xml
red
0.19.1

vscode-yaml
red
1.4.0

code-settings-sync
Sha
3.4.3

vscode-scss-formatter
sib
2.3.3

sass-indented
syl
1.8.19

ayu
tea
1.0.5

lorem-ipsum
Tyr
1.3.1

JavaScriptSnippets
xab
1.8.0

php-debug
xde
1.24.3

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstartedc:30433508
vsclayoutctrc:30437038
vsrem710cf:30416617
dsvsc008:30440022
pythonvsnew555cf:30442237
vsbas813:30436447
vscscmwlcmc:30438804
helix:30440343
vsnot107cf:30443615

/gifPlease

Same problem as reported here on StackOverflow ~ 3 dots above first line while I write code in react in Visual Studio Code, it moves the code and its very annoying

Restarting with extensions disabled prevents it so most likely not a core issue

Encountering the same issue:

I believe this is related to GitLens, try disabling it and see if it helps with your issue.

Already reported here ~ https://github.com/gitkraken/vscode-gitlens/issues/1742

I this issue fixed???

/causedByExtension
As mentioned above - issue is caused by extension. Thanks for the link to gitlens issue.
Everybody who has this issue should wait for extension update or switch to preview version of extension.