Parsing 837D Dental Claims

Hello,
I'm using stupidedi to parse some incoming medical/dental claims, put them into a sane format, and save them to a database. It's working great for Professional and Institutional claims, but I'm running into a wall with Dental.
It looks like there's currently no guide built for dental (005010X224A2). I'm more than willing to take a stab at it, but It'd also be great if there was a quicker way to get up and running with dental claims for the time being. Is there a generic config I can use (not hipaa) that will allow me to navigate 005010X224A2 files until I can build out the guide for 005010X224A2?
Something like:
config = Stupidedi::Config.generic
parser = Stupidedi::Builder::StateMachine.build(config)

Thanks!

Hi, you can try adding an entry to a config similar to the ones for 837P in hipaa, but you can use the generic grammar for 837 (these are called TransactionSetDef instead of Guide).
config = Stupidedi::Config.hipaa
config.customize do |c|
  c.transaction_set.customize do |c|
    x.register("005010X???", "HC", "837") { Stupidedi::Versions::FunctionalGroups::FiftyTen::TransactionSetDefs::HC837 }
  end
end

Try putting this in bin/edi-pp and printing an example file with ./bin/edi-pp <path-to-file>. Since 837D hasn't been implemented, there's a chance some of the segments or elements are missing and you'll need to add definitions for them to be parsed (otherwise you'll see InvalidSegmentVal).
Beware that this will limit how much information the API has about the structure of the file. For instance there's probably a single NM1 loop to describe all of patients, providers, guarantors, etc, rather than each having a distinct loop. You can still access all the data, but the API has less information to help.

Perfect! That worked like a charm. Thanks for the help - as soon as I get some time I'm going to give defining the dental spec a try, but this is super helpful for the time being!


[Bugfix] remove post_layernorm in siglip

No issues have been raised at present,  but it is a known bug.

What is the bug

When siglip acts as a multimodal vision encoder, there is no need for a post layer norm, which would otherwise result in unexpected output.

What is the fix

comment post_layer_norm

Why was the original implementation wrong?

In the LLaVA-Next code implementation, post_layernorm is not used.
It just used encoder_outputs.
https://github.com/LLaVA-VL/LLaVA-NeXT/blob/48890b0cb5da882ab584689244e74802ddbd4f75/llava/model/multimodal_encoder/siglip_encoder.py#L576-L587

Can you add a test or modify the existing tests to be stricter so that this behaviour is checked? Thanks!

Sorry, I have no clue about adding relevant test cases.
I think this is a small modification, and the tensor shape is the same before and after the modification.
I don't know how to add test examples for this change, can you give me some specific tips?

How did you discover this bug? You can add a test for the model that triggered it.

How did you discover this bug? You can add a test for the model that triggered it by updating the corresponding file under tests/models.

Thanks for your reply, I found this problem on a model I trained myself. There is no model for siglip as a vision encoder in huggingface. As a result, I couldn't test directly with llava/ llava-next.
Another way is to test the siglip model directly, but testing the vision model alone is not currently supported. Maybe I should write a new test case that supports visual encoder testing?

Ah I see, I thought it was a problem with one of our existing models. In that case there is no need to add the test, thanks for fixing!

Ah I see, I thought it was a problem with one of our existing models. In that case there is no need to add the test, thanks for fixing!

Thank you very much!🙏

This is because PaliGemma uses the last hidden state, whereas LLaVA models use the second-last hidden state. The last hidden state in transformers library is subject to the post_layernorm.

Hmm actually, I tried this locally and it broke the tests. The existing vision models expect post_layernorm to be used. I think you'll have to add an optional argument to the forward method so that post_layernorm can be skipped specifically in your case.

In the current llava based siglip model, post_layernorm is not used. It's like not using the head.
https://github.com/LLaVA-VL/LLaVA-NeXT/blob/48890b0cb5da882ab584689244e74802ddbd4f75/llava/model/multimodal_encoder/siglip_encoder.py#L576-L587
If necessary, I can add a parameter for selection.

We have to fix both CLIP and Siglip:

CLIP should load post_layernorm if the last feature layer is selected.
Siglip should omit post_layernorm if the last feature layer is selected

But post_layernorm  does not appear in ClipVisionTransformer. if necessary, I could make similar modifications to clip.

Tests are failing. You need to update the weight loading logic as well.

Tests are failing. You need to update the weight loading logic as well.

thx!  I have fixed the problem.
I added need_post_layernorm to control whether post_layernorm weights are initialized and loaded

Thank you for your patient guidance!

This is because PaliGemma uses the last hidden state, whereas LLaVA models use the second-last hidden state. Only the last hidden state in transformers library is subject to post_layernorm. Therefore, the current implementation of CLIP in vLLM will also break if the last feature layer is selected (since post_layernorm isn't implemented).
So, the real fix would be to apply post_layernorm for each visual encoder in vLLM only if all of the encoder layers are used.

Thank you for your patient response. I have revised my submission.
Now determine whether the last layer is used by self.num_hidden_layers_override.
If the last layer is used, self_num_hidden_layers_override is None, it will use post_layer_norm; Otherwise, post_layer_norm will be skipped.

@wnma3mz @DarkLight1337  "post_layer_norm" is not used in LLaVA model. But the changes in this issue may not solve this problem.  Because "self_num_hidden_layers_override" is used to determine the layers of encoder,  not for the "post_layer_norm".

This is because PaliGemma uses the last hidden state, whereas LLaVA models use the second-last hidden state. Only the last hidden state in transformers library is subject to post_layernorm. Therefore, the current implementation of CLIP in vLLM will also break if the last feature layer is selected (since post_layernorm isn't implemented).
So, the real fix would be to apply post_layernorm for each visual encoder in vLLM only if all of the encoder layers are used.

Thank you for your patient response. I have revised my submission.
Now determine whether the last layer is used by self.num_hidden_layers_override.
If the last layer is used, self_num_hidden_layers_override is None, it will use post_layer_norm; Otherwise, post_layer_norm will be skipped.

@wnma3mz @DarkLight1337 "post_layer_norm" is not used in LLaVA model. But the changes in this issue may not solve this problem. Because "self_num_hidden_layers_override" is used to determine the layers of encoder, not for the "post_layer_norm".

Please see #8155


Add ubuntu docker image

We still refer to an ubuntu docker image in https://buildkite.com/docs/agent/v3/docker. I think it makes sense to offer an ubuntu variant as well as alpine.
This will have a -ubuntu suffix, so buildkite/agent:3.0-ubuntu and will use the latest LTS.

We deprecated the Ubuntu image quite a while ago… we just forgot to update the docs. I wonder if it's a good idea to bring it back? Then we'd add jessie too I guess? We initially deprecated it to reduce the support footprint.
We could instead have some instructions for building your own Ubuntu + Jessie images?

It seems like it's pretty standard to have a default alpine build but also an ubuntu or debian build for things @toolmantim. I'm ok with adding it to the build process, enough people have asked and the size of the ubuntu image has come right down over time. Feels?

Cool cool, sounds worth it?
The only other thing maybe to consider is keeping our OS base up-to-date with security vulns too? Alpine base tends to have much less vulns, and at the moment we only update our images on agent release at the moment.
https://hub.docker.com/r/buildkite/agent/tags/

How do other people handle that I wonder? With Docker Hub auto-build you can have it trigger based on other dependent images. We could use a daily scheduled build? So package updates would be picked up max 24h after the OS packages are updated.

Yeah, it's a tricky problem. We basically need to monitor upstream images somehow and trigger agent builds, but we also need a way to notify us so we can cut new releases.


[image_picker] Implemented 2860 and added Unit Test to test functionality

Fixes an issue where videos could be wrongly picked with .jpg extension.
Description
When picking videos on Android devices, it will return file names ended with .jpg extension, regardless of the file being actually a video. This requires a workaround implementation, such as opening a File descriptor on Flutter side and rename it to .mp4 again.
The issue happens because some URI paths doesn't have an extension and it was being extracted just by splitting the file name from . and getting the last part, which make it not quite reliable for some scenarios. Right now, I've updated the source to retrieve the extension based on the URI content.
As a note, this doesn't happen with all Android devices, but I can see it easily replicable with Samsung phones.
Related issues
Fixes #52419
Same implementation as #2860, but with the requested unit test
Pre-launch Checklist

[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I signed the CLA.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@cyanglaz : can you please review and publish the new version?


Template vars have type map[interface {}]interface {} instead of map[string]interface {}

https://github.com/go-vela/compiler/blob/ef890ebd54b82cfff886631e5818ce9ea4c20ebe/template/native/render.go#L16-L47

⚠ I'm a JavaScript dev with pretty low knowledge of GoLang. Anything and everything I say is probably wrong.

I'm unsure if this is occurring at the root level, or only in deeper properties, but I'm unable to call the spring function toJson (or mustToJson) to wholesale take an object from vars and render it out into my template.
Given a .vela.yml like...

ℹ It doesn't have to be this absurdly deep, this was a test I wrote while trying to fix.

steps:
  - name: praxis-pipeline
    template:
      name: praxis
      vars:
        build_environments:
          - name: foo
            ruleset:
              some:
                deep:
                  property:
                    tree:
                      - foo
                      - bar
                      - baz

And content within a template such as...
{{- range $buildEnv := .build_environments -}}
  {{- $reactAppEnv := $buildEnv.name -}}
  {{- $buildRuleset := $buildEnv.ruleset }}
  # Build the app for the {{ $reactAppEnv }} environment
  - name: {{ $reactAppEnv }}_build
    <<: *node-image
    environment:
      REACT_APP_ENV: {{ $reactAppEnv }}
    commands:
      - npm run build
  {{- if $buildRuleset }}
    ruleset: {{ mustToJson $buildRuleset }}
  {{- end }}
{{- end }}

It breaks with an error like...
unable to execute template: template: praxis-pipeline:84:16: executing "praxis-pipeline" at <mustToJson $buildRuleset>: error calling mustToJson: json: unsupported type: map[interface {}]interface {}

This may have to do with the default typings of go-yaml - defaultMapType = reflect.TypeOf(map[interface{}]interface{}{}) (see https://github.com/go-yaml/yaml/issues/139).

I believe I may have overcome this by injecting this block into the beginning of my template:
{{- $vars := dict -}}
{{- block "castInterfaceMapToStringMap" list . $vars -}}
  {{- $in := index . 0 -}}
  {{- $out := index . 1 -}}
  {{- range $key, $inValue := $in -}}
    {{- if kindIs "map" $inValue -}}
      {{- $outValue := dict -}}
      {{- template "cleanJson" list $inValue $outValue -}}
      {{- $_ := set $out $key $outValue -}}
    {{- else if kindIs "slice" $inValue -}}
      {{- $_ := set $out $key (list) -}}
      {{- range $inItem := $inValue -}}
        {{- $outItem := ternary (dict) $inItem (kindIs "map" $inItem) -}}
        {{- if kindIs "map" $inItem -}}
          {{- template "castInterfaceMapToStringMap" list $inItem $outItem -}}
        {{- end -}}
        {{- $_ := set $out $key (append (get $out $key) $outItem) -}}
      {{- end -}}
    {{- else -}}
      {{- $outValue := $inValue -}}
      {{- $_ := set $out $key $outValue -}}
    {{- end -}}
  {{- end -}}
{{- end -}}

Declare a new object, $vars
Declare and execute a template, castInterfaceMapToStringMap. Supply it with an array of 1) input values (.); and 2) output values ($vars).
Iterate over the key/value pairs in the input object.

For objects, recurse into the castInterfaceMapToStringMap template.
For arrays, iterate over the array and either inject values directly or recurse into the castItnerfaceMapToStringMap template.
All other values are injected as is.


big cleanup-phase after restructuring

Cleanup-request
Description
The last big restructure was done, because the parser and the language should be also used in other projects. So it should be not limited only to the SakuraTree tool anymore and should be more generic. There is a post-processing necessary to cleanup the code, add comments and make some parts more generic.

changes:

reduce interface of libKitsunemimiSakuraLang to an absolute minimum
cleanup and massive reduction of the code-base
add comments
fix output
update blossom-output (#62)
remove mulit-node prototype


Add a dedicated page for customization

Related: https://github.com/Microsoft/vscode/issues/26893, https://github.com/Microsoft/vscode/issues/26892
What is we could augmented the welcome page to add a dedicated customize page. This could be the first thing users saw on first launch:

Basically a bunch of tiles with images/gifs that make it really easy to see what a setting does. The order of the settings/extensions could be based on the amount we feel the setting could be a deal breaker for the user.
After first launch it could revert to the regular welcome page. These three welcome page buttons could also be combined into one to open this "customize page":

/cc @Microsoft/vscode

Then we would have two different settings UIs, which I think would be confusing. It would set users up to expect a full traditional settings GUI.

The interesting thing here is that this is exactly the approach of the keyboard editor (two experiences) one for the power user JSON and one for the other users asking for a UI.
If we don't try to solve both problems at once for both classes of users then I think we get a cleaner experience and it will not be confusing - assuming we can make switching modes work well.
I'm also working on a few mock-ups in this area and will post them once they are a little cleaner.  One thing for instance we want to preserve is a focused settings experience but we also have a lot of scopes [User, Workspace, Extension], relationships [detect indentation, tab size, ...]  and overrides [language specific] to deal with.

This is a little different to a UI for settings https://github.com/Microsoft/vscode/issues/3355, it's more to help the welcome page get users up and running in their ideal preferences ASAP by giving some visual and easy to understand examples of the top 10-15 or so settings.
You wouldn't want to send users to a traditional settings UI as the first thing they see.

Maybe this in combination with asking the user from which other editor or IDE he/she is coming and then proposing a set of settings and extensions to install?

I recently had to install Eclipse for a project and on the welcome page it had a link to a wizard for reviewing the most fiercely contested preferences. It didn't have the settings that turned out to annoy me the most, but I like the idea.
I have seen several extensions that have settings to disable some feature that was turned on by default, where I thought why would anybody turn that off, but when I then checked the issues in the extension repository, I found out that there were some very good reasons for why you may want to turn it off.
A solution could be to add an extra field to the setting in the configuration properties that indicates the user should be asked to review the default value the first time the extension is activated or for system settings, on first launch.
If it also keeps track of new settings that should be reviewed, then it is also less "dangerous" to be bold in #26893 :smirk:

To me the current Welcome UX serves as a signpost showing users where to go from there and they can choose to ignore that. Showing only settings on first startup seems much more one-sided and might serve less users than the current mixed approach.
I like the idea of having a simplified settings UX augmenting the full settings JSON. At the same time I'd prefer the Welcome page to stay lean.
@bpasero We already link to keymaps for other editors from the Welcome page. We could look into extending these extensions to also change some of the defaults for settings.
@dymo The release notes might be a simpler way to inform users about one-offs like the default settings in #26893.


Resource to get container volume path?

Question: is there an existing resource to get the location of a container volume path (i.e. /var/lib/docker/volumes/xxxxx/_data)?
I would like to use Chef to write some canned template data into a container volume.  I would normally bind a host directory (path which I would prescribe) to a container volume, but that does not seem to be working with the container I am working with (artifactory).

Sorry.. there is no native mechanism in the resource for getting this information through the resource...
You can get the path from docker inspect, but I wouldn't recommend manually dropping files into /var/lib/docker like you're trying to do
-s


Compile the files into a neat executable

I'm pretty sure there's a way to do it. Make it so that it looks just like any other game

I found this tutorial on how to 'compile' it, although it's more like installing it? Idk. Anyway, here's the link to that video

It would be great to package it https://packaging.python.org/en/latest/tutorials/packaging-projects/ and make it installable with pip. (Which then could provide an executable)

I've made an executable before with pygame and had to format the file directory like this project so that it compiles neatly. Also, the executable should be called Number-Game.exe. And this will mean a lot of refactoring is gonna be required.

Is there any progress or wish for this issue to retain relevance? @R0merol
I may be able to help with this!

Yes, I'd like this issue to be completed. But first, I'll have to refactor the code to make it easier to compile


verifyTime is not used nor documented

Hello,
I thought this lib would check the notBefore and notOnOrAfter fields. There's a function called verifyTime that does this. Though this function is never used anywhere. Neither is there documentation about how to use it yourself.
I have done the following (which seems to work):
// simplified example
sp.parseLoginResponse(idp, 'post', req, parseResult => {
    const {conditions} = parseResult.extract;
    const notBefore = conditions.notbefore;
    const notOnOrAfter = conditions.notonorafter;
    const validTimeframe = sp.verifyTime(notBefore, notOnOrAfter);

    if (!validTimeframe) {
      console.warn(`SAML message has expired. notBefore: ${notBefore} notOnOrAfter: ${notOnOrAfter}`);
      res.sendStatus(500);
    } else {
      res.send(parseResult.extract.nameid);
    }
  });

@Guuz This function is exposed to both idp and sp instance (in fact, the time conditions are optional in document P.21, the parseLoginResponse is a helper function to handle the xml document, and leave this option to developers.
I think it would be good to include before the callback is invoked, once the message has time conditions, it should be checked.
I am welcome to any pull request. Since we are working on v2 right now, so new features and enhancements would not be updated in v1, v1 only updates when bug is discovered.

I don't see this function on the types for ServiceProvider  in types/index.d.ts and I get Property 'verifyTime' does not exist on type 'ServiceProvider'. Am I missing something?

@tngan What is the recommended approach to use verifyTime with TypeScript?


Edit PPP, improve test cases and code quality for FindCommand

Codecov Report

Merging #169 (be40843) into master (a9018f3) will increase coverage by 0.50%.
The diff coverage is 98.03%.

@@             Coverage Diff              @@
##             master     #169      +/-   ##
============================================
+ Coverage     67.25%   67.76%   +0.50%
- Complexity      706      718      +12
============================================
  Files           114      116       +2
  Lines          2446     2469      +23
  Branches        287      289       +2
============================================
+ Hits           1645     1673      +28
+ Misses          713      707       -6
- Partials         88       89       +1

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/FindCommandParser.java
85.00% <87.50%> (-7.50%)
:arrow_down:

...java/seedu/address/logic/commands/FindCommand.java
100.00% <100.00%> (ø)

...a/seedu/address/logic/parser/ArgumentMultimap.java
100.00% <100.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
93.04% <100.00%> (+2.56%)
:arrow_up:

...gic/parser/exceptions/ParseNoKeywordException.java
100.00% <100.00%> (ø)

...ogic/parser/exceptions/ParseNoPrefixException.java
100.00% <100.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
92.06% <0.00%> (+4.76%)
:arrow_up:

...rson/predicates/TagsContainsKeywordsPredicate.java
87.50% <0.00%> (+25.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix session reuse plugin shutdown crashes and cleanups

Remove pthread_cancel, use atomic flags to ensure cross thread safety, and some other cleanups.

Cherry-picked to v9.0.x branch.


Tweak makefile

This pull request tweaks the followings:

Fix Makefile pattern rules order (fix %-test-image never be used)
Add "-gke-zone=$(GCP_ZONE)" command line option to "just-the-integration-test" make task

Since I sent PR to upstream, I'm closing this.
https://github.com/grafeas/kritis/pull/331


Comprehend

Issue #, if available:
Description of changes:
added a new helper file in lambda layer to fetch and process Comprehend and ComprehendMedical data from Textract results.  Modified to 2 lambda functions syncprocessor and jobresultprocessor to call it
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

ADDENDUM:  the lambda syncprocessor and jobresultprocessor have been packaged with a more recent version of boto3 since the current lambda runtime boto3 is missing needed calls to Comprehend and ComprehendMedical.

ADDENDUM: the lambda syncprocessor and jobresultprocessor have been packaged with a more recent version of boto3 since the current lambda runtime boto3 is missing needed calls to Comprehend and ComprehendMedical.

Can we use the similar (adding a layer) approach as the previous version of the demo used?
Here is how it works=  Creating the layer. Adding the layer to the lambdas

On the subject of packaging the newer version of boto3 as a layer, yes it would be best to put that boto code in one place only,  I had some discussions with Curtis earlier.  But first, it would have to be tried and tested first to make sure the lambda functions do default to that boto3 in their execution.  Secondly,  if it works, all other lambda functions needing boto will also default to that new version in the layer.  There is a very small chance that there might be some change and conflict,  but testing again will tell.

On the subject of packaging the newer version of boto3 as a layer, yes it would be best to put that boto code in one place only, I had some discussions with Curtis earlier. But first, it would have to be tried and tested first to make sure the lambda functions do default to that boto3 in their execution. Secondly, if it works, all other lambda functions needing boto will also default to that new version in the layer. There is a very small chance that there might be some change and conflict, but testing again will tell.

I believe we can get it tested before the demo. Given that its not a major version upgrade I believe all changes would be backward compatible. Also, I'd like it be a layer and a zipped folder so as to keep the dependecies packed together and avoid redundancy


apiversion for pdb is behind

It has been noticed that PDB for both operator and metrics server is at policy/v1beta1. Since we see that rest all components are at apiversion v1. Could you please let us know when can we expect v1 apiversion for pdb.
Specifications

KEDA Version: 2.7.2
Platform & Version:
Kubernetes Version: v1.22.4 AKS
Scaler(s):

Are you willing to send a PR?

v1beta deprecated in 1.21, will be removed in 1.25
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#poddisruptionbudget-v125
If KEDA min k8s version is 1.21+, then this can just be changed to v1.
Otherwise, a capabilities check will be needed:
{{- if .Capabilities.APIVersions.Has "policy/v1/PodDisruptionBudget" }}
apiVersion: policy/v1
{{- else }}
apiVersion: policy/v1beta1
{{- end }}


feat: use webworker to keep main thread free

Try out this version of the Hiro Wallet - download extension builds.

In both wallets we use Argon2 to stretch the user's password, deriving the encryption key. By design, it's hugely resource intensive, to make brute force attacks as infeasible as possible.
The downside to this is the the wallet can seem unresponsive as the thread is busy deriving the key. This is noticeable in that the animation lags, and everything else becomes temporarily inaccessible. In the video below, I've added buttons with hover colours and a text input that demonstrates this. I'm frantically clicking the input to no avail. Only at the end does it become accessible before navigating to the homepage.
https://user-images.githubusercontent.com/1618764/133125583-70e2e9e5-ab0e-42f4-abcb-19833ad57ae4.mp4
In this example, the function has been modified so that the msg is sent to a WebWorker, which does the key stretching on a different thread, and returns a postMessage with the same response.
https://user-images.githubusercontent.com/1618764/133125590-b3e504af-b1f7-4c3a-b539-50c47547d02a.mp4

I don't know if I'm seeing what is different b/w the two videos?

in the first video, the UI thread is frozen, meaning the buttons don't animate, you can't type, etc. This is not the case in the second

I don't know if I'm seeing what is different b/w the two videos?

in the first video, the UI thread is frozen, meaning the buttons don't animate, you can't type, etc. This is not the case in the second

Thx, I see it now. 👍

@fbwoolf here's another demo https://afshinm.github.io/50k/
There's more that could be done:

Creating an abstraction around workers themselves to handle generation/termination
Use a webpack loader to auto-detect *.worker.ts files and bundle them accordingly

These would be good improvements, but as we're only using a single worker, reckon the simpler approach is better.

Password testing and Unlocking passed.
Moving it to QA Done


Go Back and Go Forward don't work sometimes

Does this issue occur when all extensions are disabled?: Yes

Version: 1.87.0-insider (user setup)
Commit: ec291c126878742ad640055ce604a58129cd088c
Date: 2024-02-05T05:46:55.122Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

Steps to Reproduce:
https://github.com/microsoft/vscode/assets/68118705/7059fa79-bcda-4e26-a29d-efa4ea2bf481

@bpasero, is this something that falls into your area of ownership?

Does it work from the "Go" top level menu?

No, it's the same, and the shortcuts don't work either

I cannot reproduce at least in this case:

Is this always reproducible for you or only in specific cases?

 This will ensure Code is starting with a fresh data directory, e.g. no specific settings and without any extensions running.

https://github.com/microsoft/vscode/assets/68118705/38fd24ad-b2d3-476d-aeea-464228443fc9

Very strange, I can really not reproduce, not even on Windows...

Just tried to debug this, seem to be the history stack index got reset by a file removal event triggered by git fsmonitor

Wow, I appreciate you going the full mile to debug this and I can reproduce now. Interestingly this code has been around for years. I cannot fully understand why I would reset the history here even if no element was removed from the stack:
https://github.com/microsoft/vscode/blob/56c54e7fef7f168e9d6eab921301fc91479b5b19/src/vs/workbench/services/history/browser/historyService.ts#L1708-L1724

This bug has been fixed in the latest release of VS Code Insiders!
@Legend-Master, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version b2598b92d18ea1132e9cd35df776c8c22a7f9730 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

/verified


check into error message for indexing like [a+1:4] in BUGS model

I'll flesh this out when I have more time, but basically we had a user try to have code like this
x[(i-1)*L+1:L]

and that errored out in model building.  x[((i-1)*L+1):((i-1)*L+L)] does work.

Fixed by PR #783


Watch when using the module

Is there any way to combine watch with module usage?

Hi @kurtextrem,
Not right now, but it's something I'm considering.
As a workaround, I think you can do it using nodemon:
nodemon index.js --watch db.json

or
// db.js
module.exports = {
  posts: []
}

// index.js
const db = require('./db')

// The router can accept an object but the side effect is that data won't be persisted
jsonServer.router(db)

nodemon index.js

I've solved it using your code:
chokidar
.watch(config.db)
.on('change', function (file) {
	if (file === config.db) {
		var obj = JSON.parse(fs.readFileSync(file))
		console.info('Setting new DB state')
		router.db.setState(obj)
	}
})


Testing for dupe tags

Re: #59, that's not really something that should be discovered in the wild. A CI-based test to make sure there aren't duplicate tags in the help docs would be useful to keep that from happening again.

Done; part of 4.0.0, though, but the current production release doesn't have any dupes


Suggestion for hw 1, pb 1 next time course is taught: use of Zotero shared group folder and shared annotations for literature extraction

To help with making the literature data extraction FAIR, going with a Zotero group library where PDF files, annotations, etc. are shared between group members can help out by:

keeping all the references in one place
highlights/annotations are shared and are easily made searchable, plus "click link to go directly to annotation" (makes curation easier)
easy to make the list of references public, and the copyrighted files along with the annotations can be easily shared upon request

(planning to update later with some examples/images)

great suggestion.


Update build scripts

This pull request aims to update the build scripts process discussed in: https://github.com/BrainJS/brain.js/issues/223

Description
Analyzing the code base and scripts, I believe following things needed to be done:

[x] Update Read-me to include CDN link
[x] Update package JSON to include Browser field
[x] Replace browserify/uglify with Parcel-Bundler
[x] Add Dev & Build scripts
[x] Reduce files distributed with the npm package install.
[x] Update brain.js imports in examples
[x] Validate that all tests run fine

This will make sure:

When using npm we don't need to load minified or build version and index.js will be the entry point for the script. This will also ensure that brain.js is built using the developer environment (babel etc)
For direct usage in Browser

a CDN link will be available.
a build/minified will be available in dist directory.

existing browser.js & browser.min.js files will be removed from the root directory.

Please let me know if you have any questions about these tasks.
Motivation and Context
issue
How Has This Been Tested?
Running the tests and examples in the repo.
Types of changes

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

Author's Checklist:

[x] My code focuses on the main motivation and avoids scope creep.
[x] My code passes current tests and adds new tests where possible.
[x] My code is SOLID and DRY.
[x] I have updated the documentation as needed.

Reviewer's Checklist:

[ ] I kept my comments to the author positive, specific, and productive.
[ ] I tested the code and didn't find any new problems.
[ ] I think the motivation is good for the project.
[ ] I think the code works to satisfies the motivation.

[ ] Make all test run on Windows

By the Way, is there any plan to build a dedicated homepage for brain.js introduction?Currently landing page is example.

Added new directory structure for tests written using jest. Next step is to write tests for each module from the src directory.

Are you going to possibly add code coverage as well?

Yes, that is the plan.

How much work would it take to apply your work here to another branch, like nn-gpu-layers for example?  Shortly after we close this issue, we'll want to merge that branch into master.

Not, much. I am not touching any of the source code inside src folder. All you have to do will be copy new src to this branch and done.

What needs to happen next with this branch for it to be ready?

I am writing tests now for each module in the source code. Which might take a week (maybe less, depends on how much test code can I use form previous version). This is because I am using jest now for all tests. Some of the tests will be ready today, then I will ping you to take a look.
In the next step, I will pull latest code from you dev branch and test again. If all goes well, then you can merge into your dev branch. Then test again for some time and then merge into master and release.
DONOT think of merging this into dev/master yet.

ok, just let me know.  Ty for your hard work.

Also: I forgot to mention: please do not go ahead and unit test and fix or even change too much anything in the recurrent folder.  This will all go away in v2, so lets spend our time on the nn-gpu-layers branch after this branch is done.  Most everything in the nn-gpu-layers refactors what is in the recurrent folder, so that it'll run on GPU.

Thanks, I just started writing tests for this folder. matrix directory should also be skipped?

Merged nn-gpu-layer branch into this. If you can take a look and test it to your likings then you can merge it into develop branch. Then we can continue working on adding tests for each and every modules.

Yes, skip it for the time being.
On Sat, Jun 30, 2018, 1:38 AM Muhammad Ubaid Raza<EMAIL_ADDRESS>wrote:

Thanks, I just started writing tests for this folder. matrix directory
should also be skipped?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BrainJS/brain.js/pull/225#issuecomment-401519008, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AApcu-CVIek_Ha3x7KV2mRwJirz7wwtIks5uBw7hgaJpZM4U58xb
.

Merged nn-gpu-layer branch into this

Huzzah!
You'll see that the layer folder more or less replaces the recurrent/matrix folder.

@robertleeplummerjr Please clean the src folder in nn-gpu-layers branch

Do you still need me to fix this branch?  I'm actively working on it, fyi.

Now that I have merged it into this branch, lets work on this branch now. These are things needed to be done now:

Cleanup the src folder. (Only you can do it better)
Add tests (I can do part of this, easier ones which I can understand :p)
Test all the build scripts (easy task)
Test examples (easy task)
Prepare for release (build, tests, coverage report publish)

What do you say?

I say lets just merge it into develop, and I can give you write access.
Once it is ready we can merge it into master.
If fixes for 1.x need to be made, we can make them on the https://github.com/BrainJS/brain.js/tree/v1.x branch.
This will do two things: force us to be serious about v2, and force us to get super serious about tests and stability.
Thoughts?


add possibility of custom tex template

added new command line parameter --tex_template in order to allow a custom tex template
if not specified, default file is used. if specified but not available (file not found or file not readable), an error message is shown and the default is used.
This pull request would at least close issues https://github.com/3b1b/manim/pull/745 and https://github.com/3b1b/manim/issues/525 .

I have completely rewritten the code for managing the TeX template:

Full backwards compatibility: if you do nothing, everything will work as before, the old default template will be used for LaTeX or XeLaTeX
New command line option --tex_template allows for a custom tex file
New class TeXTemplatestarting with the current default values for maximum backwards compatibility.
New class has methods to append or prepend custom packages and/or custom preamble commands.
Added method register_tex_template allows to register a new or modified template

Example
class ExampleScene(Scene):
    def construct(self):
        tpl=TeXTemplate()
        tpl.append_package(["esvect",["f"]])
        register_tex_template(tpl)

        text=TextMobject(r"$\vv{vb}$")
        self.play(Write(text))

As you may have guessed, the syntax for packages is

append_package("package") if you do not have any options
append_package(["package",["option1","option2=value2"]]) if you do have options to give

Got an error after making all the changes. Can you please help?
AttributeError: 'NoneType' object has no attribute 'get_text_for_tex_mode'

@Ammar34 I am happy to help, but I need more information:

What is your input?
What is the exact error message? (preferably with the stack trace)

With the information you provide, there is absolutely no way for me to help.

@PhilippImhof yeah okay. Prior to changes suggested by your commit, I was getting no error. After the changes I am getting the following in the terminal:
PS E:\VisualStudioCode\manim> python -m manim graphingFile.py firstPlot -pm
Traceback (most recent call last):
File "C:\Users\Khan-\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 193, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\Khan-\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "E:\VisualStudioCode\manim\manim.py", line 5, in
manimlib.main()
File "E:\VisualStudioCode\manim\manimlib_init.py", line 11, in main
config = manimlib.config.get_configuration(args)
File "E:\VisualStudioCode\manim\manimlib\config.py", line 189, in get_configuration
module = get_module(args.file)
File "E:\VisualStudioCode\manim\manimlib\config.py", line 184, in get_module
spec.loader.exec_module(module)
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "graphingFile.py", line 1, in
from manimlib.imports import *
File "E:\VisualStudioCode\manim\manimlib\imports.py", line 104, in
from manimlib.new_packages.new_classes import *
File "E:\VisualStudioCode\manim\manimlib\new_packages\new_classes.py", line 82, in
class CheckFormulaByTXT(Scene):
File "E:\VisualStudioCode\manim\manimlib\new_packages\new_classes.py", line 86, in CheckFormulaByTXT
"text": TexMobject(""),
File "E:\VisualStudioCode\manim\manimlib\mobject\svg\tex_mobject.py", line 149, in init
SingleStringTexMobject.init(
File "E:\VisualStudioCode\manim\manimlib\mobject\svg\tex_mobject.py", line 43, in init
file_name = tex_to_svg_file(
File "E:\VisualStudioCode\manim\manimlib\utils\tex_file_writing.py", line 20, in tex_to_svg_file
tex_file = generate_tex_file(expression, tex_template, source_type)
File "E:\VisualStudioCode\manim\manimlib\utils\tex_file_writing.py", line 36, in generate_tex_file
output = tex_template.get_text_for_tex_mode(expression)
AttributeError: 'NoneType' object has no attribute 'get_text_for_tex_mode'
PS E:\VisualStudioCode\manim>

What is manim\manimlib\new_packages\new_classes.py ? This does not exist in my code and I cannot find it in the main repository either.

@PhilippImhof Ah! That was the problem. It was an old classes file that I forgot to delete. Thanks. Now its working.
P.S Can you please explain how can I change the tex template to any custom template I want? A code example would be deary of you!

@Ammar34 I'm glad I could help.
In order to use a custom tex template, you basically have two possibilities
Template file
You prepare a template file (complete LaTeX file starting with \documentclass[preview]{standalone} plus your preamble containing all desired packages followed by
\begin{document}
   YourTextHere
\end{document}

The template can then be used by invoking manim with the new '--tex-template ' command line option.
Template object
You create a new TeXTemplate object within your scene's constructor. The template will be initialized with the default packages for best compatibility, check manimlib/tex_template.tex for reference. The object then offers you to add custom packages directly in your code. After everything is done, you have to "register" your template object:
class ExampleScene(Scene):
    def construct(self):
        tpl=TeXTemplate()
        tpl.append_package("siunitx") # add package without options
        tpl.append_package(["esvect",["f"]]) # add package with one option
        tpl.append_package(["spalign",["systelims=||","delims=()"]]) # add package with multiple options and keyval syntax
        tpl.append_to_preamble(r"\newcommand{\tr}{\operatorname{tr}}") # add definition to preamble
        register_tex_template(tpl)

        text=TextMobject(r"$\vv{vb}$")
        self.play(Write(text))

There is also a method clear_preamble if you do not want to have all the default packages in your template. I do not think there is a need for this, as those packages normally should not make any problems, but I decided to include it nevertheless, for maximum flexibility.


Add "-Wconversion" to more closely align to MSVC

This will make GCC builds warn on the same things that Windows does.  Unfortunately, it will also warn on more things, so I'm going to open this as a draft until the whole stack builds cleanly.

ign-utils: https://github.com/ignitionrobotics/ign-utils/pull/46

The level of strictness and the level of warnings that we want to enable by default that we want to have with ign-cmake is open to debate however I have some thoughts about this PR:

We need to define clearly what are we trying to get with the change: try to unify compiler warnings behaviour? improve the QA of the code using ign-cmake by increasing the level of strictness?
Enabling the warning flag by default on ign-cmake2 branch is probably a no-go since it is going to alter many builds out there by introducing new warnings.

Depending on the first point, we can try to generalize the measure into new features. Seems to me like we are going to need to control new behavior using a CMake parameter (or similar) no matter what options we choose.

We need to define clearly what are we trying to get with the change: try to unify compiler warnings behaviour?

I was mainly trying to bring our linux gcc warnings in line with what MSVC produces in terms of numeric conversions.  Unfortunately, after working up the stack a little bit, GCC is far more strict (to the tune of dozens of warnings on ign-math itself).  I think this is probably a non-starter as default flag for the reason you said.
I'm going to leave this as a draft just so that I can track progress towards being able to enable it, but I agree it will need to be changed to an opt-in mechanism rather than opt-out.


ensure in cluster challenging and browser clients reconciled

/test e2e-aws

solves:
https://github.com/openshift/hypershift/issues/316

/test e2e-aws

/test e2e-aws

/test e2e-aws

/lgtm
/approve


Connection issue with select clients - M_NOT_FOUND: Not found

I am new to conduwuit and matrix in general, and I tried to get a basic server running yesterday. No federation, just a private server to familiarize myself with conduwuit. So the issue may be in my config.
As far as I can say, the server runs fine using docker compose and traefik. I can connect to the server using webapps https://app.schildi.chat and the like, as well as desktop apps (https://fluffychat.im). However, trying Element and SchildiChat for Android I get the error message 'M_NOT_FOUND: Not found' right after entering the server URL.
Using the FluffyChat Android app works fine.
Is this a configuration issue?
My docker compose:
---
networks:
  proxy:
    external: true

volumes:
  database:

services:
  conduwuit:
    image: girlbossceo/conduwuit:latest
    restart: always
    volumes:
      - database:/var/lib/conduwuit
    container_name: conduwuit
    environment:
      CONDUWUIT_SERVER_NAME: sub.domain.tld
      CONDUWUIT_DATABASE_PATH: /var/lib/conduwuit
      CONDUWUIT_DATABASE_BACKEND: rocksdb
      CONDUWUIT_PORT: 6167
      CONDUWUIT_MAX_REQUEST_SIZE: 20_000_000
      CONDUWUIT_ALLOW_REGISTRATION: 'true'
      CONDUWUIT_REGISTRATION_TOKEN: redacted
      CONDUWUIT_ALLOW_FEDERATION: 'false'
      CONDUWUIT_ALLOW_CHECK_FOR_UPDATES: 'false'
      CONDUWUIT_TRUSTED_SERVERS: '["matrix.org"]'
      CONDUWUIT_ADDRESS: <IP_ADDRESS>
    networks:
      - proxy
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.conduwuit.rule=Host(`sub.domain.tld`)"
      - "traefik.http.services.conduwuit.loadbalancer.server.port=6167"
      - "traefik.http.routers.conduwuit.tls=true"
      - "traefik.http.routers.conduwuit.tls.certresolver=production"
      - "traefik.http.routers.conduwuit.middlewares=cors-headers@docker"
      - "traefik.http.middlewares.cors-headers.headers.accessControlAllowOriginList=*"
      - "traefik.http.middlewares.cors-headers.headers.accessControlAllowHeaders=Origin, X-Requested-With, Content-Type, Accept, Authorization"
      - "traefik.http.middlewares.cors-headers.headers.accessControlAllowMethods=GET, POST, PUT, DELETE, OPTIONS"

Maybe they require a well known file? e.g.
   CONDUIT_WELL_KNOWN: |
   {
     client=https://<delegated>,
     server=<delegated>:443,
     support_page=https://<domain>,
     support_role=m.role.admin,
     support_email=<email>,
     support_mxid=<mxid>
   }

I also had this issue, but I fixed it by adding .well-known/matrix/client delegation to my web server. You would use a reverse proxy for something like that, but you can also tell conduwuit to serve its own .well-known/matrix files. I don't really know how to do this in a Docker setup, I only found this example config on the documentation (relevant configuration lines are at the bottom): https://conduwuit.puppyirl.gay/configuration.html
I hope that I could clear up some things!

Indeed, serving a .well-known/matrix/client file did the trick. Thank you!


invalid_request

Suddently I started to get this right out of nowhere.
{
  "error": "invalid_request",
  "error_description": "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Check the \"access token\" parameter."
}

Sometimes it works, sometimes not...
I just created a token using the method with grant_type = password.
return \Response::json(\Authorizer::issueAccessToken());

My configurations are the following:
<?php
return [
    'database' => 'default',
    'grant_types' => [
	    'password' => [
	        'class' => League\OAuth2\Server\Grant\PasswordGrant::class,
	        'callback' => '\Puzzible\OAuth2\Verifier@verify',
	        'access_token_ttl' => 3600
	    ],
	    'facebook' => [
	        'class' => Puzzible\OAuth2\Grants\FacebookTokenGrant::class,
	        'callback' => '\Puzzible\OAuth2\Verifier@verifyFacebook',
	        'access_token_ttl' => 3600
	    ],
	    'twitter' => [
	        'class' => Puzzible\OAuth2\Grants\TwitterTokenGrant::class,
	        'callback' => '\Puzzible\OAuth2\Verifier@verifyTwitter',
	        'access_token_ttl' => 3600
	    ],
    ],
    'token_type' => League\OAuth2\Server\TokenType\Bearer::class,
    'state_param' => false,
    'scope_param' => false,
    'scope_delimiter' => ',',
    'default_scope' => null,
    'access_token_ttl' => 3600,
    'limit_clients_to_grants' => false,
    'limit_clients_to_scopes' => false,
    'limit_scopes_to_grants' => false,
    'http_headers_only' => false,
];

Any ideas how to fix this issue?

I tried to change composer.json to use the following package versions:
league/oauth2-server (4.1.3) instead of league/oauth2-server (4.1.4)
lucadegasperi/oauth2-server-laravel (5.0.2) instead of lucadegasperi/oauth2-server-laravel (5.0.3)

Now it works on one of my two web servers, any ideas why this can be?
They have the exact same code deployed...

I had this exact issue, it is in the league package, the authorization header gets completely converted to lowercase while the token verifier looks for "Authorization" which it cannot find for obvious reasons.
This was not yet the case in the old version (4.1.3) so requiring that version in your composer.json should solve the issue for now.

This only happened with the latest version?

From what I know, yes @vinkla.

I'm using the latest version of this package with the latest version of Laravel without any problems.

Lets close this for now and if anyone else have this problem we will take it from there. Thanks for reporting!

Now this is also reported in #612. @alexbilbie do you know why this could happened?

I am also getting the same issue.

I am having the same problem, I can solve it temporarily?

Now this is also reported in #612. @alexbilbie @lucadegasperi do you guys know why this could happened?

@marktopper @vinkla @lucadegasperi I found this same problem and the solution to this issue I added the following line in the .htaccess file, I think that is an Apache problem.
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization},last]

@marktopper @tuupke does the comment by @guilhermesoratto above solve your issue?

@vinkla Well, I'm running nginx, but even with its version of that command, it will not be fixed; Somewhere the headers were converted to lowercase while it checked for the "Authorization" header which it could not find since the capitol A got converted to lowercase. But as I said, the problem was not caused by this package, but by the league's package. So reverting that back to 4.1.3 was the easiest fix.

@vinkla, I am running nginx as well. So can't help with checking that.

I'm also running NGINX without any issues at all. Closing this for now.

@tuupke Thank's.. it works after downgrading the league's package to 4.1.3

I'm using nginx 1.8 and am having the same issue with the Authorization Header getting stripped out of the request.


Konflux update test-component-pac-ibxdor

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-ibxdor-on-pull-request has successfully validated your commit.
Namespace: build-e2e-jrzi-tenant
PipelineRun: test-component-pac-ibxdor-on-pull-request-r8pn2

Task Statuses:

StatusDurationName

✅ Succeeded
22 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
sast-snyk-check

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
1 minute
ecosystem-cert-preflight-checks

✅ Succeeded
2 minutes
clamav-scan

✅ Succeeded
1 minute
sbom-json-check

✅ Succeeded
1 minute
apply-tags

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-ibxdor-on-pull-request has successfully validated your commit.


[WIP] Enable auto installation ID lookup

Fix #46 . Do you even want to go this route before I have to worry about updating the rest of tests?

[ ] Fix test failures
[ ] Add change log

I think this looks fine to me.
This doesn't stop us from creating a repo handler for a non-installed repo and doing things that aren't authenticated right?

I don't even remember this one anymore... 😬  Let me know if I should revisit this, or we can just close this...


10 metrofication

Heeey @shiftkey? @andrewtobin? Beuller?

There is a slight lag when creating the first document - will raise as a separate issue. Rest is good.

Side effect of loading in WebKit, unfortunately.


Adding a way to make "volumes" from chapters

Here's the reasoning, I can get Chapters off MangaDex (or else). But chapters are very annoying on an ereader because of the time needed to read the next one.
So I've been using Calibre to do -> CBZ -> EPUB -> EPUB Merge into Volumes -> PDF
Then take the PDF and finally run it through KCC to get a MOBI file.
It would be reallllllyy nice if we could get a small UI or one more level to the file list to group chapters into volumes.

This workaround is redundant and not needed - pulling all chapter files into a single folder and dropping that folder into KCC with the split output option disabled will result in a merging of all chapters into a single file.

Ohh I did not know this, it might be worth it to write it in the documentation or the GitHubreadme ?

I actually am unable to add zip files (or folders) to KCC. I receive an error saying that the source directory is empty. Are there any workarounds for this error? Thanks!

TatianaC's comment has been solved in another issue.
@Xqua
ghost's proposition is correct.
The simplest way is to use a directory with sub directories inside for each chapter
everything is already there:
https://github.com/ciromattia/kcc/wiki/Automatic-output-splitting


[Local] Fix config != None vs. 'None'

Quick bug-fix. The if statement checks if the config value is None, but this will never be the case. Though refactoring the config options so we could use None instead of 'None' is probably worthwhile.

Thanks for the PR, but if possible I'd rather not add in workarounds for the optional config parameters issue.  I'll see if I can create a quick fix for #181 instead.

@ericzinnikas : Ok, I fixed #181 with #301, so I think that should also fix this issue.  I'm going to close this for now, but feel free to re-open it if there is still an issue.  Thanks!


Fix out of memory (and permitting support of checkin policies)

Another attempt to fix #1117 following solution described in
https://github.com/git-tfs/git-tfs/pull/1118#issuecomment-347305811
Run as x64 by default and added a script to run as x86 if needed for checkin policies.
Perhaps need some docs and a script to revert the "prefered 32bit" flag...

I have added the documentation...
If those having the OutOfMemory error and those using checkin policies could test this version....

Sorry for the delay. It works for me, @JensNordenbro  can you try it as well?

I would have liked that this PR was tested by users that use check-in policies because that's the ones that will be heavily impacted (it should work without problems for those having the out of memory exception...) but it's not likely that one is aware of this thread.
That will break once released :-(

I have started a conversion, it will take some time to complete.
The process at least start as 64-bit so there is hope :)


Dots between words

Attach (recommended) or Link to PDF file here:
Lentini.pdf
ss-copy-spec.pdf
Configuration:

Web browser and its version: firefox flatpak version 111.0.1
Operating system and its version: openSUSE Tumbleweed
PDF.js version:
Is a browser extension: no

Steps to reproduce the problem:

Open the pdfs
See the dots and background changes

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
I tested the pdf.js from Firefox 111.0.1 (flatpak) against Evince (GNOME PDF reader)

Let's dup this to https://bugzilla.mozilla.org/show_bug.cgi?id=1825293, since the problems look (more or less) identical.


Support API Version in URL Generation

Add support to resolve the current API version as an ambient value during URL generation via the IUrlHelper. Today, URL generation works exactly has it is supposed, but often confuses those that version by URL segment and do not include the API version route parameter as an input value. The default IUrlHelper implementations provided by ASP.NET only consider well-known route parameters (ex: [controller], [action], etc) as a possible ambient value.

Hello, Chris.
I have an issue even when I do not use version in url.
Here's the repo to reproduce the problem.
When I run POST, I get:

System.InvalidOperationException: No route matches the supplied values.
at Microsoft.AspNetCore.Mvc.CreatedAtActionResult.OnFormatting(ActionContext context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.ExecuteAsyncCore(ActionContext context, ObjectResult result, Type objectType, Object value)
at Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.ExecuteAsync(ActionContext context, ObjectResult result)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeNextResultFilterAsyncTFilter,TFilterAsync
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
HEADERS
=======
Accept: /
Connection: keep-alive
Host: localhost:5084
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9,ru;q=0.8
Cookie: .AspNetCore.Antiforgery._qyHzYA0nYs=CfDJ8L6H2Ao5KRNOqEdd0Szk4ky1IHlDMHIOBjVn9eU2S15AZ2zcAW2hegOp8DUfyiWTkparHfXkVkVGEy7v9W2FzlNOleMu0j8qqiUvaU0ILZfpcQBBIaRh8et9783kcc7PbB7jDdsEHOKYHFkPM6vJHMM; .AspNetCore.Antiforgery.N1usb0hhv5Y=CfDJ8L6H2Ao5KRNOqEdd0Szk4kzXNo9YEuLaHQyvbXKtkcMXTJqt132QyOaHKRKk_XyULGuqWp1gxHwf9ci6OR3lxqbcYb8On0hSgoCb0iFP_I-ZmtofuMp3YrW1NWfX-2mRMU30PAJK2ZQd0l942kKsLTs
Origin: http://localhost:5084
Referer: http://localhost:5084/swagger/index.html
Content-Length: 0
sec-ch-ua: "Google Chrome";v="125", "Chromium";v="125", "Not.A/Brand";v="24"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty

Am I missing something here?

From the looks of it, this is simply because you are missing the route parameter in the template.  The correct signature should be:
[HttpGet("{id}")]
public async Task<string> Get(int id) => $"Hello, {id}!";

It's also worth nothing that the issue with URL generation only exists if you are versioning by URL segment, which you are not (currently) doing and I don't recommend. 😉

Unfortunately, even with "{id}" I have the same error.

Using the BasicExample as the baseline project, I added your example controller as follows:
[ApiController]
[Route( "[controller]" )]
public sealed class HomeController : ControllerBase
{
    [HttpGet( "{id}" )]
    public IActionResult Get( int id ) => Ok( $"Hello, {id}!" );

    [HttpPost]
    public IActionResult Post() => CreatedAtAction( nameof( Get ), new { id = 42 }, null );
}

Request
POST /home?api-version=1.0 HTTP/2

Response
HTTP/2 201
Location: http://localhost/home/42
api-supported-versions: 1.0

Hopefully that helps you figure out the difference from your setup.

Ofc there are differences =)
public static void ConfigureApiVersioning(this IServiceCollection services)
{
    var headerApiVersionReader = new HeaderApiVersionReader("Accept-Version");

    services.AddSingleton<IConfigureOptions<SwaggerGenOptions>, ApiVersioning.SwaggerGenOptionsConfigurer>();
    services.AddSingleton<IConfigureOptions<SwaggerUIOptions>, ApiVersioning.SwaggerUIOptionsConfigurer>();

    services.AddApiVersioning(cfg =>
    {
        cfg.ApiVersionSelector = new CurrentImplementationApiVersionSelector(cfg);
        cfg.AssumeDefaultVersionWhenUnspecified = true;
        cfg.ReportApiVersions = true;

        cfg.ApiVersionReader = ApiVersionReader.Combine(
            new MediaTypeApiVersionReader(),
            headerApiVersionReader,
            new QueryStringApiVersionReader());
    })
    .AddMvc() // This is not the same AddMvc method you might have thought about.
    .AddApiExplorer(opt =>
    {
        opt.GroupNameFormat = "VV"; // Shows version as Major.Minor
        opt.ApiVersionParameterSource = headerApiVersionReader;
    });
}

Get method works fine.
If I explicitly specify not supported version 2.0 I get 400 for both Get and Post.
But if I omit it or specify 1.0 for Post, it fails with 500.

SwaggerUIOptionsConfigurer causes the issue. Without it, Postman requests work

You can inject IApiVersionDescriptionProvider directly. There's almost no reason to ever use the factory. I don't see anything else obvious that would cause that problem. 🤔

Yes, injecting IEnumerable<EndpointDataSource> dataSources somehow leaves them empty.


Video_Player unable to play the asset video, Video Player error

Only the sample video downloaded from the website can be played and all the other videos cant be played.
The error mentioned source error but I have added the path in pubspec.yaml file and also have the key in the correct path.
VideoPlayerController.network is working, only the VideoPlayerController.asset having problem
here is the link to the sample video which is working
Here is the video that is not working
Steps to Reproduce

Logs

Logs

Flutter doctor -v output

I solved the issue by uploading the video to Youtube and download the video by using the youtube downloader website, I know its weird but it solve the problem


cvxgrp conda : no 1.0.x deployments on python 3 since 1.0.25.

On conda, all python 3 releases of 1.0.x stop with 1.0.25, compare to 1.0.26. This is almost certainly because of version_getter.py thinking that versions 1.0.x are out-of-date, after 1.1.a0 was released.
We could fix version_getter.py, or we could use this as a time to drop cvxpy distribution on the cvxgrp conda channel. @akshayka @SteveDiamond.

My vote is for dropping the cvxgrp conda and switching to conda forge.

We switched to conda-forge a while ago. Thanks, @h-vetinari!


Add config options to DNS Resolver that mitigate a bug w/ Unifi (and maybe others)

This PR adds some configuration options to Unbound (DNS Resolver) that mitigate a bug with Unifi gear failing to reach the controller due to unqualified DNS lookups to 'unifi.' post 2.3.3+/2.4 master.

adds ability to specify on a host-by-host basis whether to create both qualified and unqualified DNS entries
adds option to auto-track 'domain' according to System > General - can be nice time saver / safety net when you have a lot of overrides within the default domain
Unbound overview page displays these as checkmarks/additional columns, domain will be shown in green if it is set to 'track'
fixes a bug (seemingly caused by commit 13541a81e1173fc02af9af8ab7fe46df2a51007d) that caused a 'host/domain already exists' error to print when trying to edit & then save an existing Host Override
minimal testing done - "it works for me!"

references:
reddit thread
2.3.3 changes - DNS
redmine 6064

There is no such bug with UniFi. You need to fix your DHCP to pass a search domain to the UniFi gear. That's all. Working on 5 sites with pfSense and UniFi.

Has something changed recently about the way search domain works in DHCP? I usually leave it "blank" which has always caused DHCP to send the domain from System>General as option 15.
The reason I created this patch is because something definitely seems to have changed -- Search Domain was definitely still being handed out, but somehow the Unifi stuff was ignoring it and sending unqualified queries. This might be better discussed on the forums, but this patch is working well for me at 2 locations.

SSH into the UniFi client and do cat /etc/resolv.conf. Yeah, better discussed in the forums.  I always configure things explicitly for the DHCP server, never liked this stuff happening behind the scenes, it's just an endless source of user confusion. (Ditto with the DNS servers.)

Opened a topic on the forums to continue discussion until we know what is going on. I will also be working on some Wireshark captures later to dig deeper.

There is a feature that got removed. The dns lookup will now only work with full domain or configured search-domain on the client. The /var/etc/hosts on pfsense server has changed.

I created a new unified commit 25c163d6c973737beb449864f0a7f5dc6ee7f488 that has the fixes here in one patch so it can be used in System Patches.
I have been doing extensive testing on this issue -- lots of tcpdump'ing and setting up different test scenarios, and I am going to update the forum topic shortly with some new (surprising) findings as to why I believe everything in this PR should remain in for now.

Can you rebase your fork? It has conflicts now.
Also, Ubiquity published a firmware update recently that fixed some issues with DHCP search domains, can the problem behavior be reproduced with a unit on current firmware?

The busybox applet bug is fixed in current stable firmware as far as UBNT is concerned. (Not sure how desirable is this feature otherwise, seems kinda confusing to me.)

@jim-p sure, I will rebase and fix the conflicts. There were originally 2 features + 1 bugfix in here.  The bugfix related to pconfig[$id] was fixed by Phil in https://github.com/pfsense/pfsense/pull/3679, so I will remove that part. Even though Ubnt has fixed their busybox bug, there are still cases where creating the unqualified host entries in DNS could be useful. The other feature (to track the system domain) I think is useful as well. @doktornotor not sure if that was the one you were confused about? It's pretty straightforward, although I could add some additional helptext if you think it would help.

Conflicts still unresolved

Hello,
In an effort to improve the tracking of changes and bug/feature requests, we have decided to require an entry on the pfSense Redmine issue tracker associated with every pull request, and likewise the Redmine entry should also have a link back to the pull request.
If you could, please associate this PR to an open Redmine issue either by locating an existing issue at https://redmine.pfsense.org or by creating a new issue. Add a link to the Redmine issue that points to this PR, and also add a link on the PR to the Redmine issue.
For more information, see https://doc.pfsense.org/index.php/Submitting_a_Pull_Request_via_Github
Thanks!


Difference between the version 0 and 1 of the datasets

Hello,
I read the README, and found that there were two versions of the datasets, namely version 0 and 1.
But when I clicked the links, they led me to the same google drive file.
(e.g., Harm-P for version 0 and 1 both direct to https://drive.google.com/file/d/1fw850yxKNqzpRpQKH88D13yfrwX1MLde/view)
Is it that they are the same?
Thank you

Hi,
The readme and links are now updated. Please check again.


Testing issue

I am using set01/video_0002 to run the train_test.py 2 (after changing the the pie_data.py file / line 92). Howver, I am encountering an issue for running the code as  following :
"FileNotFoundError: [Errno 2] No such file or directory: '/home/marouene/PIEPredict/PIE_dataset/images/set01/video_0002/05051.png"
That being said, even for testing would the concerned video images shall be extracted !!
Many hanks for your quick reply

Hi @Marouene-Oueslati,
Try adding the line
imdb.extract_and_save_images(extract_frame_type='annotated')

after line 56 (imdb = PIE(data_path=pie_path)) in train_test.py. This should extract the images. You will need 1.1 Tb of space to hold all images from the dataset with annotations. If you are not planning to use training and validation data, you can modify the function pie_data.py:extract_and_save_images() to extract images only from set03 (test data).

Hi @ykotseruba ,
Thanks a lot for your answer. I have configured the right set of video clips.
That being said, do we need to use sh function "split_clips_to_frames.sh" to extract the needed images for the desired Set-XX beforehand as I still have the same issue.
Furthermore, I am wondering if the model could tested for any type of raw video without being linked to annotated images (I mean in Real Time application)
Thanks a lot for your valuable feedback

Hi @Marouene-Oueslati,
split_clips_to_frames.sh extracts all frames, whereas the line of code I suggested extracts only the annotated frames (1/3 of all frames). If nothing else works, you may try using the bash script but it will require 3 times more memory.
To answer your second question, the model needs bounding boxes for pedestrians to work. In order to apply it to videos that are not part of dataset you will either have to annotate them manually or implement object detection/tracking. For evaluation you will also need other ground truth: intention scores, vehicle information, etc.

Hi @ykotseruba ,
your feedback is highly appreciated. Indeed I do understand your feedback as the code as well as the paper was part of a deep research topic with in-house validation.
The line of code till now seems not working, perhaps I will try to extract it accordingly using the split_clips_to_frames.sh.
Just wondering if you have any idea regarding the use of yolo / ss to extract the bounding boxes & reshaping the BB convention.
My last question concerns the possibility of only training the intention model without linking it to trajectory prediction nor vehicle speed; if so, could you please share some rules or approach.
My apologies for the long message.

Hi @Marouene-Oueslati,
Could you please be more specific? What error do you get when running the extract_and_save_images()?
Regarding two other questions, I didn't run object detectors on PIE so I can't help you with this. If you need annotations in YOLO or any other format you can use CVAT to convert them.
It is possible to train only the intent model. train_intent()' function has code for both training and testing. Try commenting out train_predict()intrain_test.py:173`, that should probably do it.

Hello @ykotseruba; this is a screen shot of the error that I am getting when running the "python train_test.py 2". FYI, as you can see, I am only testing for video 0002 from the set01 and have added imdb.extract_and_save_images(extract_frame_type='annotated')

Hi @Marouene-Oueslati,
Based on the error, the images aren't extracted. Do you get any output or errors from extract_and_save_images?

Closing due to inactivity.


Can't install Nerdtree, it shows: Plugclean required

I tried to install the plugin, but it doesn;t seem to be working, it says plugclean required, can someone please help me with this please~
thank you!!

have you tried running :PlugClean it uninstalls plugins if they are not in your config file you just have to type y and hit enter to remove them after running the command

have you tried running :PlugClean it uninstalls plugins if they are not in your config file you just have to type y and hit enter to remove them after running the :PlugClean command you should then be able to run :PlugInstall

OMG this works perfectly, thank you so much!!!


Error on npm

Describe the bug

Version

Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

@ambuj64 I'm sorry you faced with the issue. Could you provide additional details? Please fill-in the template from above.

Closing due to inactivity. Feel free to reopen


Teach IN FL62 actors

Hi their,
first of all many thanks to all your great work!
I mainly use our tool to control my FSR14 devices ...
in order to get rid of my bad little Homee device with the enocean add-on I would like to control al of my FL62 actors with your add-on.
I can already see the status change of the FL62-actor.
I´m going to set the actor in learning mode (by 4 short and 1 long push of the local button)
2024-11-10 17:34:13.952 DEBUG (Thread-4) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 04 23 c1 18, db0 = 70, status = 0x30 (T2, N, 0 repetitions)>
2024-11-10 17:34:13.997 DEBUG (Thread-2) [eltako] [Gateway] [Id: 2] Received message: <RPSMessage from 04 23 c1 18, db0 = 70, status = 0x30 (T2, N, 0 repetitions)>
2024-11-10 17:34:16.202 DEBUG (Thread-4) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 04 23 c1 18, db0 = 70, status = 0x30 (T2, N, 0 repetitions)>
2024-11-10 17:34:16.248 DEBUG (Thread-2) [eltako] [Gateway] [Id: 2] Received message: <RPSMessage from 04 23 c1 18, db0 = 70, status = 0x30 (T2, N, 0 repetitions)>
But I´ve been running into several problems: Seems like the teach in Button don't work.
2024-11-10 17:34:18.815 WARNING (Thread-2) [enocean.communicators.SerialCommunicator] [ESP3SerialCommunicator] Cannot convert to esp2 message (04:23:C1:18->FF:FF:FF:FF (-68 dBm): 0x01 ['0xd1', '0x0', '0xd0', '0xff', '0x0', '0x0', '0x4', '0xb7', '0x4', '0x23', '0xc1', '0x18', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()).
2024-11-10 17:34:18.943 WARNING (Thread-2) [enocean.communicators.SerialCommunicator] [ESP3SerialCommunicator] Cannot convert to esp2 message (04:23:C1:18->FF:FF:FF:FF (-68 dBm): 0x01 ['0xd1', '0x0', '0xd0', '0xfe', '0x3', '0x3', '0x1', '0x0', '0x77', '0x4', '0x23', '0xc1', '0x18', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()).
2024-11-10 17:34:26.023 DEBUG (SyncWorker_0) [eltako] [Gateway] [Id: 2] Send message: <Regular4BSMessage from ff 93 c1 18, data e0 40 0d 80, status = 0x80> - Serialized: a55a6b07e0400d80ff93c118800a
2024-11-10 17:34:26.211 ERROR (Thread-2) [enocean.communicators.SerialCommunicator] Received ESP3 response with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict()
can you provide me some advice ?

Hello @FloCodeRian,
I definitely tested FSR61 and checked FSR62 work the same regarding teach-in functionality and telegrams. I assume you are using USB300 or similar!? I'm not really sure if I did test with USB300. I assume tests were made with FAM-USB.
I should have a 62 device and can test when time allows it.


Create reverse.py

This Pull Request resolves Issue #
Description:
printing the string in reverse in python

Are there any updates here or should we close the PR and label it as spam?


Guests don't receive intellisense on trigger characters

Describe what happened:
When typing, guests are not able to open intellisense on trigger characters (e.g. -> in our case). When a single letter is typed then the popup appears.
What was your system configuration?
Product and Version [VS/VSCode]: VSCode
OS Version[macOS/Windows]: Windows
Live Share Extension Version: v1.0.5892
Target Platform or Language [e.g. Node.js]: PHP
Steps to Reproduce / Scenario:

Type $this->
No intellisense popup appears
Type a single letter
Intellisense popup appers
Remove the letter
Intellisense disappears

Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Screenshots
If applicable, add screenshots to help explain your problem.

Thanks for taking the time to file this issue. We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it is for you.


any way to see which features were selected for each tree, level, split?

Thanks for participating in the XGBoost community! We use https://discuss.xgboost.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :)
Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
For bug reports, to help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
For feature proposals, list clear, small actionable items so we can track the progress of the change.

@h17 Try using dump_model() function.
Example:
bst = xgboost.train(...)
bst.dump_model('./model_dump.txt')

Hello Philip,
This is not what I was asking: I used dump_model but one crucial piece of
information that is missing is which features were chosen via colsample_by*
On Wed, Dec 18, 2019, 4:29 PM Philip Hyunsu Cho<EMAIL_ADDRESS>wrote:

Closed #5132 https://github.com/dmlc/xgboost/issues/5132.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/xgboost/issues/5132?email_source=notifications&email_token=AC7TBLAVLBKTT5IJ5DQMOYTQZKI4NA5CNFSM4J4ODPV2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVSH5GHY#event-2895106847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7TBLG4SRBWAMINCUUTOT3QZKI4NANCNFSM4J4ODPVQ
.

@h17 You can't do that.  It's really internal to XGBoost.  You can see ColumnSampler in src/common/random.h.  It's used all tree method except approx.

@trivialfis We could potentially add an Observer to ColumnSampler?

@hcho3 It will take some efforts to extend the observer for enabling customization via user parameters.  I incline to keep it internal, curious users can look into the code for internal data.

@trivialfis For now, it should be sufficient to dump everything and let the (expert) user filter the dumped output. Let me put together something this weekend.

That would be ideal to have everything, might also help zooming in on other phenomena later. For what I was looking right now I just need to sum gain for each feature over all instances where it participated after ColumnSampler selection, lets call this gain_opportunity. Then you use this to divide total_gain obtaining another feature importance, i.e. competitiveness=total_gain/gain_opportunity which is in my opinion better than the 5 you have at the moment. I can back this up with many simple examples, but I think the simplest to think about is the following: first tree almost always has highest gain because it gets first cut so to say, so if the feature is not there for that first cut neither of the metrics will capture this.  This can be reduced by ensemble of xgb and other techniques but still measuring competitiveness will reduce noise from the start.


Rollback to Java 11

Is your feature request related to a problem? Please describe.
The latest versions of Ksoup appear to be compiled with Java 17 compatibility, which prevents the library from being used in projects targeting Android 13 and below. Android 13 and earlier only support JVM targets up to Java 11.
Describe the solution you'd like
Please consider compiling Ksoup with Java 11 compatibility (i.e., set sourceCompatibility and targetCompatibility to Java 11) to allow projects supporting Android 13 and below to use this library without compatibility issues.
Describe alternatives you've considered
Recompiling Ksoup from source with Java 11 compatibility, though this adds maintenance overhead and may not be feasible for all developers.
Additional context
Providing Java 11 compatibility would enable developers who need to support Android 13 and below to continue using Ksoup without modification. This is important for many Android projects where backward compatibility is crucial.

Sorry, something was wrong with my build.gradle.kts configs
please delete this issue

Yes, my bad, it was a build config problem on my end
I was getting an error
caused by: java.lang.UnsupportedClassVersionError: com/fleeksoft/ksoup/Ksoup has been compiled by a more recent version of the Java runtime (class file version 61.0), this version of the Java runtime only recognizes class file versions up to 55.0

I was using jvmToolChain targetting Java 11 but Ksoup is compiled for Java 17 targets
Kindly, please delete this issue


Fixing conflicts

Resolved conflicts in https://github.com/Azure/azure-content/pull/5333

@steved0x - Steve, see the bright green highlighting in the diff...can these updates from @m-gagne be merged?

@tysonn - yes please merge them.
@m-gagne Thank you for your contribution to the Azure docs!


Support for Rancher RKE2 distribution

Hi there
I installed the Trivi operator and encountered many cluster-level misconfiguration issues:

Rancher RKE2 is compliance with cis https://docs.rke2.io/security/cis_self_assessment123 so should pass the scans.
The main problem I gest is scanned directories. RKE2 configurations are stored  in /etc/rancher and /var/lib/rancher/, witch are not supported in node collector.

@intonet thanks for this input I'll have a look


rust 1.75.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge/rust-activation this is ready for review.

@h-vetinari I would value your insight on this PR. This changes the minimal OSX version for rust to 10.12. Do you know how to correctly handle this?

The CBC looks alright, you just need:
        - __osx >={{ MACOSX_DEPLOYMENT_TARGET }}  # [osx and x86_64]

under run: (or run_constrained:), so that the outputs themselves have the correct metadata as well.

Ah, I hadn't gotten the detail that this is also about binaries produced by rust >=1.75. Thanks Isuru. :)

Ah, I hadn't gotten the detail that this is also about binaries produced by rust >=1.75. Thanks Isuru. :)

Yes, that's why I was hesitant to merge here.

@conda-forge-admin please rerender


Fix the appxbundle version to be the appx version

The store did not like when I uploaded two Windows Terminal packages
built on the same date, because the appxbundle version defaulted to
YYYY.MMDD.something.
There is a risk that using this version number will fail because it is
thousands of numbers less than "2022". We'll have to see if the store
rolls it out properly. I cannot find any documentation on how the store
rolls out bundle versions (it is very aware of .appx versions...).
A local test with 1.14.72x (Preview) published via the store seems to
have worked.

@msftbot merge this in 1 minute


eq matcher produces confusing Diff message for a trailing new line

RSpec's built-in eq matcher is very useful for comparing two strings.
The Diff message for failing test allows developers to quickly find bugs especially for large size text.
However, I have found a confusing message when the diff is a trailing new line.
It says:
<The diff is empty, are your objects producing identical `#inspect` output?>

Here are the related issues.

https://github.com/rspec/rspec-support/issues/70
https://github.com/rspec/rspec-expectations/issues/570

Your environment

Ruby version: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin19]
rspec-expectations version: rspec-expectations (3.12.2)

Steps to reproduce
Following is the test code to reproduce this.
require 'rspec'

def lines_to_text(*args)
  args.join("\n")
end

RSpec.describe '#lines_to_text' do
  subject { lines_to_text('foo', 'bar', 'baz') }

  context 'when there is diff inside string' do
    it 'shows diff elegantly' do
      expect(subject).to eq "foo\n\nbar\nbaz"
    end
  end

  context 'when there is a diff after the string' do
    it 'shows somewhat confusing message' do
      expect(subject).to eq <<~EXPECTED
        foo
        bar
        baz
      EXPECTED
    end
  end
end

Expected behavior
For the second test:
  2) #lines_to_text when there is a diff after the string shows somewhat confusing message
     Failure/Error:
       expect(subject).to eq <<~EXPECTED
         foo
         bar
         baz
       EXPECTED

       expected: "foo\nbar\nbaz\n"
            got: "foo\nbar\nbaz"

       (compared using ==)

       Diff:
       @@ -1,3 +1,4 @@
        foo
        bar
        baz
       +

     # ./spec/sample_spec.rb:19:in `block (3 levels) in <top (required)>'

Actual behavior
For the second test:
  2) #lines_to_text when there is a diff after the string shows somewhat confusing message
     Failure/Error:
       expect(subject).to eq <<~EXPECTED
         foo
         bar
         baz
       EXPECTED

       expected: "foo\nbar\nbaz\n"
            got: "foo\nbar\nbaz"

       (compared using ==)

       Diff:
         <The diff is empty, are your objects producing identical `#inspect` output?>
     # ./spec/sample_spec.rb:19:in `block (3 levels) in <top (required)>'

Thanks, this is a duplicate of #570 as you linked to, as the trailing new line produces no diff you get this output.


Is org.k2fsa.sherpa.onnx v1.10.17 supporting Android Xamarin?

Hi there!
I'm trying to embed sherpa in an android application using c# xamarin.  org.k2fsa.sherpa.onnx v1.10.17 package works well on windows and linux. On Android there is a problem with creating OnlineRecognizer. While importing libsherpa-onnx-c-api.so I am getting DllNotFoundException. Using dlimport and dlerror, I found out that the error was in importing the transitive dependency libpthread.so.0. As far as I know there is no libpthread.so.0 in android, hence this libsherpa-onnx-c-api.so is not android oriented.
dlerror output - "dlopen failed: library "libpthread.so.0" not found: needed by /data/app/~~roWPFky3a7zFKDoAAw0VVA==/Dictation.Client-m1pLIjGpo753L8FT3uZF5Q==/lib/x86_64/libsherpa-onnx-c-api .so in namespace clns-6"
I tried to write a minimal application in flutter - it works. I took libsherpa-onnx-c-api.so from this build and linked it to my project, but it didn't work.
Will org.k2fsa.sherpa.onnx package support xamarin in the future?
Can you give instructions on how to link the required libsherpa-onnx-c-api.so assembly when building the nuget-package for xamarin from sources?

please find our sherpa_onnx package on pub.dev for flutter.

I tried to write a minimal application in flutter - it works. I took libsherpa-onnx-c-api.so from this build and linked it to my project, but it didn't work.

Please describe this step in detail
Also, please post all of the error logs

hello! here steps:

Build working flutter example from your repo and extract libsherpa-onnx-c-api.so from the build
Link extracted libsherpa-onnx-c-api.so to c# xamarin app and call OnlineRecognizer's constructor
OnlineRecognizer's constructor throws managed c# exception DllNotFoundEception.

But real error examined via dlimport/dlerror is "dlopen failed: library "libpthread.so.0" not found: needed by /data/app/~~roWPFky3a7zFKDoAAw0VVA==/Dictation.Client-m1pLIjGpo753L8FT3uZF5Q==/lib/x86_64/libsherpa-onnx-c-api .so in namespace clns-6". So it can't import libsherpa-onnx-c-api .so because of importing transitive dependency "libpthread.so.0". dlerror output and c# exception stacktrace are all my error logs (:
"libpthread.so.0" is not present in android OS. I think step 2 doesn't work and it links "libsherpa-onnx-c-api.so" from nuget package but not from flutter build.
So my main question is how to link "libsherpa-onnx-c-api.so" from flutter build to nuget package for c# if i wanna build package from source via your scripts?
Today I got the idea to link "libsherpa-onnx-c-api.so" from flutter build with a different name and imort via custom import resolver, but dunno if that works.


picat: 1.9 -> 2.7

Motivation for this change
Version bump.
Haven't tested on darwin, though.
Things done

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

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

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

Notify maintainers
cc @earldouglas

@GrahamcOfBorg build picat

Picat is now at 2.8-2 in master. Closing as OBE.


Issue 327 raw statsd with refactor metrics

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

Please see https://github.com/fabiolb/fabio/issues/211#issuecomment-375880738


Is Useragent ratio correct?

Hi! Awesome project!
I noticed on various, common browsers on common OS's, User agent ratio always reported < 0.1%. Is that correct? Seems unlikely but could be true so I'd like to verify.
Some examples from three recent (but unique ;) machines:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.46 Safari/537.36
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36

Hi! Thanks for your interest in our project!
These ratios seem correct to me because they take our full history of fingerprints since the website was launched in November.
For example, Version 44.0.2403.157 was released last week. If you take a look at our stats page, we collected 1030 fingerprints in the past week. This means that if all devices that connected to AmIUnique.org in the past week were all Macs with the same browser, the ratio could be at most 1.2% (=1030*100/88346). Since not everyone is on Mac with the same browser and the same browser version, it does not surprise me that the ratio is under 0.1%.
What our website does not reflect is the browser market share at a specific time. If we were to collect 80 000 fingerprints on a single day, you would see that this ratio is clearly above 1% and maybe a lot more than that. If you take a look at the stats for the past week, you can see that Chrome 44 (the current stable version of Chrome) represents two thirds of the collected Chrome fingerprints. But, since we take all the fingerprints that we collected on a large time span to calculate our ratios, you get these results that may be surprising.
If I was not clear and if you want more clarifications, don't hesitate to ask! :)

I see. Very cool -- I'd mention that the fingerprint uniqueness is only a
snapshot in time and not relevant over a period, but regardless I think
it's cool what you're doing! Good work.
On Wed, Aug 26, 2015 at 1:00 AM, Pierre Laperdrix<EMAIL_ADDRESS>wrote:

Hi! Thanks for your interest in our project!
These ratios seem correct to me because they take our full history of
fingerprints since the website was launched in November.
For example, Version 44.0.2403.157 was released last week
http://googlechromereleases.blogspot.fr/2015/08/stable-channel-update_20.html.
If you take a look at our stats page https://amiunique.org/stats, we
collected 1030 fingerprints in the past week. This means that if all
devices that connected to AmIUnique.org in the past week were all Macs with
the same browser, the ratio could be at most 1.2% (=1030*100/88346). Since
not everyone is on Mac with the same browser and the same browser version,
it does not surprise me that the ratio is under 0.1%.
What our website does not reflect is the browser market share at a
specific time. If we were to collect 80 000 fingerprints on a single day,
you would see that this ratio is clearly above 1% and maybe a lot more than
that. If you take a look at the stats for the past week, you can see that
Chrome 44 (the current stable version of Chrome) represents two thirds of
the collected Chrome fingerprints. But, since we take all the fingerprints
that we collected on a large time span to calculate our ratios, you get
these results that may be surprising.
If I was not clear and if you want more clarifications, don't hesitate to
ask! :)
—
Reply to this email directly or view it on GitHub
https://github.com/DIVERSIFY-project/amiunique/issues/16#issuecomment-134889520
.

--
@SamyKamkar https://twitter.com/samykamkar
http://samy.pl