Correction for raw affiliation UMR MoISA (Montpellier Interdisciplinary centre on Sustainable Agri-food systems), Univ Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro Montpellier, IRD, Montpellier, France

Correction needed for raw affiliation UMR MoISA (Montpellier Interdisciplinary centre on Sustainable Agri-food systems), Univ Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro Montpellier, IRD, Montpellier, France
raw_affiliation_name: UMR MoISA (Montpellier Interdisciplinary centre on Sustainable Agri-food systems), Univ Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro Montpellier, IRD, Montpellier, France
new_rors: 05kpkpg04;04abkkz03;051escj72;05q3vnk25;03rnk6m14;0005r2j17;003vg9w96;011xg1225
previous_rors: 05kpkpg04;04abkkz03;051escj72;05q3vnk25;03rnk6m14;0005r2j17;003vg9w96
works_examples: W4399049632;W4402901640
contact: da1d3277f7229e58c231498d8595d99a:fa556b6f7ff38789 @ supagro.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Error with "npm run test"

Not able to run npm run test successfully.
I have installed the following:
npm install -g browserify
npm install -g testling

Result:

The error is: No headless browser found.
Anyone else experiencing this?
Update: my co-worker just tried on his machine and is getting the same error.
Update 2: This could be related to the issue https://github.com/substack/testling/issues/111

Hmmm I might have one clue but will investigate tonight.

Temporary quick fix
After installing phantomjs via homebrew...
rm -rf ~/.config/browser-launcher

For some reason, this works.
 I've fixed and improved this and made a PR #20.
Please let me know if something has to be modified in order for the PR to be accepted/valid. I'm in a hurry right now.
Thanks!

@rafaelrinaldi
I manually made the updates from your PR, and the tests ran successfully, but only after installing phantomjs.
Seems that phantomjs is a dependency. Might be worth making a note of that.
:beers:

@peduarte Hum, that doesn't make much sense. I have quite a few libraries that rely on tape-run for CI and I have never pointed PhantomJS as a dependency. You know that you can specify a browser via -b. Maybe the default behavior is to look up for a local PhantomJS binary, but I'm not sure.
I'm going to dig deeper into this later, will update you guys when I find something useful.
In the meantime @henriquea can :rocket: because CI will work.

So, yeah tape-run does rely on a local copy of PhantomJS. It uses browser-run in the background which points this out on the docs:

Defaults to phantom. Available if installed (...)

I think that the simplest way of fixing this is to specify PhantomJS as a dev dependency. I just sent a commit which locks on version 1.9.2-6.
I've removed my local PhantomJS binary, installed the dependencies, ran the test suite and everything went smooth. Thanks @peduarte @henriquea :+1:

@rafaelrinaldi @henriquea happy days! :tada: :balloon:

Good stuff guys! Thanks @rafaelrinaldi and @peduarte I'll look into this when I get home later 👌🏼


WebAuthenticatorPage not working with OAuth1Authenticator in UWP

https://github.com/xamarin/Xamarin.Auth/blob/c584e5395f598b98b82bd22cfe079f135b0ffeda/source/Xamarin.Auth.UniversalWindowsPlatform/WebAuthenticatorPage.Events.xaml.cs#L28

Why is there a cast here?
Don't OAuth1Authenticator and OAuth2Authenticator have a base class that exposes all necessary functions?
I tried implemented Twitter Oauth1 in UWP with with a cast exception...

var twitterAuthenticator = new OAuth1Authenticator(                 "blabla",                 "blabla",                 new Uri("https://api.twitter.com/oauth/request_token"),                 new Uri("https://api.twitter.com/oauth/authorize"),                 new Uri("https://api.twitter.com/oauth/access_token"),                 new Uri("https://auth.heapshow.com/signin-google"),                 isUsingNativeUI: true             )             {                 AllowCancel = false,             }; Windows.UI.Xaml.Controls.Frame x = (Windows.UI.Xaml.Controls.Frame) Window.Current.Content; x.Navigate(twitterAuthenticator .GetUI(), twitterAuthenticator );

@KoenkookpotPlasmans

Why is there a cast here?
https://github.com/xamarin/Xamarin.Auth/blob/c584e5395f598b98b82bd22cfe079f135b0ffeda/source/Xamarin.Auth.UniversalWindowsPlatform/WebAuthenticatorPage.Events.xaml.cs#L28

Because "Parameter" object passed to the target page for the navigation in UWP and its type is System.Object. And I passed OAuthXAuthenticator, so System.Object is casted on that line to OAuthXAuthenticator.

Don't OAuth1Authenticator and OAuth2Authenticator have a base class that exposes all necessary functions?

So, I inherited this project almost accidentally and do dig through the code to understand it and refactor some things. Unfortunately most of developers that started this project are not with Xamarin anymore or are on other teams (Xamarin.Forms) and have not too much time to dive into newer version and explain some design and/or implementation decisions.
The answer would be NO few weeks ago, because since day 1 2012-10-24 both had common base class WebAuthenticator:
https://github.com/xamarin/Xamarin.Auth/tree/75b17c15c78fc19a6de2f33a47e58a26b459a7ab/Xamarin.Auth
Later on WebRedirectAuthenticator came into play and it became base class only for OAuth2Authenticator:
https://github.com/xamarin/Xamarin.Auth/commit/23b820e364a82f7e6f8eaf80ab340e158d9806cd#diff-2dd716c77da664c7a7ecc3c6dc3b0864
Today the answer is YES again, because I'm refactoring this parts, but I must be careful not to break too much.
This is bug. I must add cast and test for OAuth1Authenticator and OAuth2Authenticator.

@moljac
Thanks for the elaborate answer.
I knew there was some technical baggage build-up throughout the years.
But I'm glad you're getting on top of things! Seems like a frustrating job when there is no information available ;-).
My apologies if my ticket seemed a bit 'short' and quite direct.
Keep up the good work!

no futher action on this


refactor(ra_syntax.validation): removed code duplication from validate_literal()

Hi! This is my first ever contribution to this project.
I've taken some dirty job from issue #223
This is a simple atomic PR to remove code duplication according to FIXME comment in the function that is the main focus of the further development.
I just didn't want to mix refactoring with the implementation of new features...
I am not sure whether you prefer such atomic PRs here or you'd rather have a single PR that contains all atomic commits inside of it?
So if you want me to add all that validation in one PR I'll mark this one as WIP and update it when the work is finished, otherwise, I'll go with the option of creating separate PRs per each feature of validation of strings, numbers, and comments respectively.
Comments about refactoring
Yeah, reducing the duplication is quite hard here, extracting into stateless functions could be another option but the number of their arguments would be very big and repeated across char and string implementations so that just writing their types and names would become cumbersome.
I tried the option of having everything captured implicitly in the closure but failed since rust doesn't have templated (or generic) closures as C++ does, this is needed because unescape_byte*() and unescape_char|str() have different return types...
Maybe I am missing something here? I may be wrong because I am not enough experienced in Rust...
Well, I am awaiting any kind of feedback!

bors r=@kiljacken
Thanks @Veetaha and @kiljacken !

@matklad Looks like bors was happy to see you!
@Veetaha if you'd create a new PR with the remaining changes, that would be nice :)

@kiljacken, Sorry I was taking some time to study this project codebase and architecture. I didn't expect that this will be merged so soon, though I will create a new pr with amendments according to the review soon as you suggested

I guess I needed to make this one as [WIP], didn't I?

No need to apologize, I just think bors mis-parsed Aleksey's command, so it got merged instead of allowing me to merge it (which wasn't really necessary as he already gave me r+ rights haha)


Fix maskable icon.

Add extra space around icon so "L" is visible with any masking.

Resolved with commit 25f2d8c711.


Map missing selectors to roles

So it's entirely possible that I'm doing this Entirely Wrong, buuut I noticed that (the apparently deprecated) selectors, used only on OS X, don't map completely to their replacements in role. Specifically, pasteAndMatchStyle and delete don't seem to map to anything. There may be other mappings we're missing here too, which I'd be happy to add. :smile:

:+1:


kakoune: fix build

@riteo kakoune needs a patch to fix constexpr usage: http://0x0.st/oSLn.patch

Oh right, I procrastinated on it and forgot it completely. I didn't know anybody except me used Kakoune here lol. That got fixed upstream long ago, it got caused by a new compiler release or something like that IIRC, but mawww hasn't released a new version in months. I applied the patch but I think that we should switch to a later commit or to a git version completely as we're missing quite a lot of work (eg. a hare syntax highlighter) and while reading the issue tracker it looks like that the more "advanced" users should just compile the head of the main branch. Thanks a lot for the patch!


Node API OCR3 support

I think we need to be very careful with the naming here. I don't like the idea of OCR2 being implicit but OCR3 being explicit, and we should avoid the extra baggage of repeated prefixes/suffixes whenever possible. Is it time to start thinking about multiple proto packages?

@jmank88 I agree -- I think we could move the OCR2 bits into internal/ocr2 and the OCR3 bits into an internal/OCR3. However, I want to avoid scope creep on this PR, since we need this for the first Keystone demo: would it be OK to move the OCR3 bits into their separate package and follow up on the OCR2 migration separately?
@george-dorin , I'd expect each OCRX package to contain:

the GRPC server implementation for that flavour of OCR
the loop constructor
then the reporting plugin client/servers for that flavour of OCR as well.


Add an option to support TLS session ticket resumption

From some manual testing (by connecting to a local server run with openssl s_server -key key.pem -cert cert.pem -accept 44330 -tlsextdebug -www -state), it looks like there are two requirements here:

Call either SSLSetSessionTicketsEnabled or SSLSetSessionOption with kSSLSessionOptionEnableSessionTickets, which will cause the client to send the SessionTicket extension in its initial ClientHello.
Call SSLSetPeerID with something that uniquely identifies the remote (maybe domain + port?).
Both of these are required, as with just the first, the client will just send an empty SessionTicket extension in its ClientHello every time. It seems like setting a peer ID is required so that Security Framework knows what to key the session ticket against.

In the openssl s_server output, a normal TLS handshake looks like:
SSL_accept:before/accept initialization
TLS client extension "session ticket" (id=35), len=0
...

SSL_accept:SSLv3 read client hello A
SSL_accept:SSLv3 write server hello A
SSL_accept:SSLv3 write change cipher spec A
SSL_accept:SSLv3 write finished A
SSL_accept:SSLv3 flush data
SSL_accept:SSLv3 read finished A

I'm happy to accept pull requests implementing this functionality.


Update typescript eslint plugins to v4

Should be backwards compatible, but adding support for TypeScript 4 in projects using CRA

Fixes https://github.com/facebook/create-react-app/issues/9583

This is going to be fixed by https://github.com/facebook/create-react-app/pull/9434

Closing as duplicate of  9434


New command: planner plan remove

Usage
m365 planner plan remove [options]
Description
Removes the Microsoft Planner plan
Options

Option
Description

-i, --id [id]
ID of the plan to remove. Specify either id or title but not both.

-t, --title [title]
Title of the plan to remove. Specify either id or title but not both.

--ownerGroupId [ownerGroupId]
ID of the Group that owns the plan. Specify either ownerGroupId or ownerGroupName when using title.

--ownerGroupName [ownerGroupName]
Name of the Group that owns the plan. Specify either ownerGroupId or ownerGroupName when using title.

--confirm
Don't prompt for confirmation

Examples
Removes the Microsoft Planner plan by ID
m365 planner plan remove --id gndWOTSK60GfPQfiDDj43JgACDCb

Removes the Microsoft Planner plan with title My Plan in group with specific ID
m365 planner plan remove --title "My Plan" --ownerGroupId 00000000-0000-0000-0000-000000000000

Removes the Microsoft Planner plan with title My Plan in group with name My Planner Group
m365 planner plan remove --title "My Plan" --ownerGroupName "My Planner Group"

Additional Info
Graph docs: https://docs.microsoft.com/en-us/graph/api/plannerplan-delete?view=graph-rest-1.0&tabs=http

Great spec, looks to be ready to be picked up 🚀

I'm willing to work on it.

It might be useful if you specify at the options ownerGroupId and ownerGroupName that they are only needed if they make use of the option title

It might be useful if you specify at the options ownerGroupId and ownerGroupName that they are only needed if they make use of the option title

Was thinking about that too. I copied this description from other plan commands where this is not mentioned either. But I'll update the specs, thx @Jwaegebaert.

@Jwaegebaert great point!  @milanholemans would you mind creating an issue to update the docs of the other commands that as well then? That way we can keep it consistent as I assume the same implication goes for those commands?

@Jwaegebaert great point! @milanholemans would you mind creating an issue to update the docs of the other commands that as well then? That way we can keep it consistent as I assume the same implication goes for those commands?

Will do!


Update TDTM Table UI

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-030029

Tracking W-030029

@rponti-sforg this item is ready for testing. Thanks!


Mac download broken

On this page https://dbeaver.io/download/ when I click on Mac OS X (dmg) I get the following error:
<Error>
AccessDenied
<BucketName>dbeaver</BucketName>
<RequestId>tx000000000000020a83e82-0060172002-868307d-nyc3b</RequestId>
<HostId>868307d-nyc3b-nyc-zg02</HostId>
</Error>

I downloaded the zip file but when I unzipped it and tried dragging it into my Applications I got a warning saying the file is corrupt and should be deleted.

Thank you for the bug report.
Something went wrong during release publishing.
Fiuxed.

Verified


rav1e ffmpeg 4.3 support

Currently, FFmpeg 4.3 supports Rav1e video encoding. Can you enable it on the Dockerfile on ubuntu docker file?

It is 4.3 specific, in that case we can add it to all 4.3 variants (alpine, centos, ubuntu, etc), if you are interested the change itself seems very similar to https://github.com/jrottenberg/ffmpeg/blob/master/update.py#L195 but with  --enable-librav1e


cli: Relax stake split destination check

This is a copy of https://github.com/solana-labs/solana/issues/32735
Problem
In the CLI, process_stake_split checks that the destination stake account doesn't exist, and errors if it does. In most cases, this saves from getting an on-chain error from trying to split into some other account.
https://github.com/solana-labs/solana/blob/849525735f784f8e2e0fca19ba5699aea6b1724e/cli/src/stake.rs#L1884-L1893
However, it's possible to pre-seed some lamports into a system account before splitting into it, to keep the full amount delegated, so this check is needlessly strict.
Proposed Solution
Relax the check by allowing the destination split account to be owned by the system program, with some lamports, and no data. It can error in every other case still.

Closed by #162


User may overwrite observations with special symbols

Due to the implementation of internal storage, it is possible to overwrite existing observations if they have two or more labels:
tarantool> c = metrics.gauge('coll')
---
...

tarantool> c:set(3, {lab = 'val', lab2 = 'val2'})
---
...

tarantool> c:collect()
---
- - label_pairs:
      lab2: val2
      lab: val
    timestamp:<PHONE_NUMBER>982881
    value: 3
    metric_name: coll
...

tarantool> c:set(4, {['lab\tval\tlab2'] = 'val2'})
---
...

tarantool> c:collect()
---
- - label_pairs:
      "lab\tval\tlab2": val2
    timestamp:<PHONE_NUMBER>647270
    value: 4
    metric_name: coll
...

It is highly unlikely that someone would become a victim of this bug unintentionally, but this behavior still seems a bit problematic.
Moreover, using special symbols breaks prometheus export:
# HELP coll
# TYPE coll gauge
coll{lab	val	lab2="val2"} 4

error while linting: text format parsing error in line 3: expected '=' after label name, found 'v'

The metric counter is code hot path. Be careful it seems that new if can decrease a little.


Added Helwan University

Faculty of Computer Science Helwan University

@LechTheMitch lib/domains/eg/edu/helwan: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


[FEATURE] Lock camera on selected track

Is your feature request related to a problem? If so, Please describe.
Matt and I talked about implementing the locked camera view from the WAMI viewer version in this.  It allows the camera to center the track through multiple frames and when selecting new tracks it will move the camera to center it on the new track.
The main problem is that in large datasets it is sometimes difficult to determine where tracks are located, this will enable this to work.
Describe the solution you'd like
Toggle for locking the camera next to the reset camera button.  It will allow the user to toggle the lock on to automatically jump to tracks instead of hunting for them.  I think I may want to indicate it is locked a little more than just the standard unlock/locked icon.  A color change will probably help make it a little more noticeable.
Describe alternatives you've considered
Keyboard shortcut to center the camera on the selected track could be added as well that way the user could quickly center it without remaining locked.
Additional context
Example of it working in the wami viewer:

This sounds like it would involve changes in much of the guts of the annotation viewer.
What VIAME Web customer wants this?  Can we form a user story about them?  Any example dataset where this would apply?  WAMI viewer is useful for demonstrating the concept, but not relevant here.

This was a request from Matt.  Specific to Seal or large image datasets with small tracks.  Mostly people having difficulties identifying where tracks are in these 5k or larger images.  I'll ask Matt for the dataset he was using where he was having this specific issue.
The change would require hooking into the annotator.js from inside the LayerManager, a selectedTrack knows it's bounds and center point so you just forward that to the annotator.js and if the setting is on it moves the camera.  Similar to how we already do this for the  icons in the editing modes and the editHandles.

this was done a long time ago.


Added auto rotate functionality

Actually I just wanted to answer the question asked in #8. But it would be great to have that functionality directly in the project if someone wants to tinker around so im creating this PR. It's just trivial but why not.

@thexmanxyz Hi! Thanks for adding this feature. If you could fix the error on line 85 pointed out by parasm0802 I would be more than happy to merge this PR in. Thanks for your contribution.

@parasm0802 Strangely I did not get a notification email for your comment I completely missed that compile error. Will add a commit in the next minutes to fix that compilation error. Just wrote it without checking syntax I guess. @VectStudio. Sorry for that. You can merge it in the next minutes.

 Sorry for adding a compilation error. I now verified the sketch and added another commit which adds the missing ) bracket. I'm curious why I did not get a notification mail on August 16th for the comment from @parasm0802 not even in my mail history. But whatever it is fixed now. Thanks in advance for merging!


ARROW-10287: [C++] Avoid std::random_device

std::random_device may block on some systems, even for long times.

@kszucs

@github-actions crossbow submit conda-cpp-valgring

@github-actions crossbow submit conda-cpp-valgrind

@crossbow submit conda-cpp-valgrind

This PR now also fixes the Valgrind failures.

Thanks Antoine!


feat: added multiclusteringress hub feature for use by multiclustergateway

added multiclusteringress hub feature for use by multiclustergateway

/lgtm pending the response from @gtsorbo


Add a script to check models in the model zoo

This patch adds a script that can automatically download models from the model zoo (https://github.com/onnx/models), compile, run the models and verify inference outputs.
By default, the script runs for all models in the model zoo. To run with specific models, please directly change models_to_run in the script, e.g. models_to_run = ['mnist-8', 'yolov4', 'resnet50-v2-7']
Signed-off-by: Tung D. Le<EMAIL_ADDRESS>

Could we put the script into onnx-mlir/test/choose-a-name? It is part of our test, and it is very likely that we will start the test with a cmake target.

@chentong319 @etiotto thanks, I addressed your comments and find a new home for the script.

Please add a section in docs/Testing.md on how to use this, thanks

Done. Thanks!

Jenkins Linux s390x Build #5648 [push] Add a script to check mo... started at 02:56

Jenkins Linux ppc64le Build #4770 [push] Add a script to check mo... started at 02:59

Jenkins Linux amd64 Build #5633 [push] Add a script to check mo... started at 01:56

Jenkins Linux s390x Build #5648 [push] Add a script to check mo... failed after 35 min

Jenkins Linux amd64 Build #5633 [push] Add a script to check mo... passed after 1 hr 11 min

Jenkins Linux ppc64le Build #4770 [push] Add a script to check mo... passed after 1 hr 19 min


fix: ensure HMR requests can be streamed

addresses https://github.com/netlify/cli/issues/4569

tested this locally with a fresh Nuxt app. can confirm that HMR is broken on main, but works with this change.

@eduardoboucas thanks for the review! could I get another ✅? I had to update a snapshot (see https://github.com/netlify/cli/pull/5194#issuecomment-1300648933).

Can confirm the change to proxy.cjs fixes hot reload for netlify dev in our Nuxt 2 app.


fix popover support check

on my browsers (firefox, chrome, chromium and chrome based edge) the popover detection didn't work anymore since #170. So i changed back to the old variant of checking.

Thanks for contribution. I was on vacation. I'll look inside and reflect on the next update.


Rename "api upgrade" to "api upgrade-access"

User story
I find it confusing to call this an "API upgrade" as it really just copies/upgrades app+org access from one API to another. An API upgrade includes much more: upgrade access, upgrade quotas, replace the previous API proxy, etc. So basically the entire process that the CLI performs today when publishing an API on the same URL. Would it be clearer to call it upgrade-access (same as in the UI)?
Additional context
See issue: https://github.com/Axway-API-Management-Plus/apim-cli/issues/120#issuecomment-735751744

Hi @cwiechmann, are there any plans to support and command like "api upgrade", which does the steps like upgrade access, upgrade quotas, replace the previous API proxy ...?

@jschaefer77, is this what you are looking for not what the api import command does?


[FEAT] : Add Conribution Section in README.md

✏ Description
To do:

[ ] use the github api
[ ] list all the contribution in the readme below this section :point_down:

Note: make sure you check the Contribution Guidline

📸 Screenshots
No response

i would like to work on this

Great !! , go for it :heart_eyes:


Remove "~" references to home-directory in SettingsParams

Fixes #2657 by removing "~" references to the user's home directory, and adding error checking for file-writes in MainForm.
The ofstream method is picky about the file path its given.   While it writes to existing files with "~" in its path, it will not create them.
Note: You may need to "restore defaults" to overwrite an existing .vapor3_prefs file in your home directory, which still may refer to "home" as "~"

@stasj If you check out SettingsParams, the ~ is still handled in the getters and setters, so the user can still use a ~.  But this is moot because your file selectors do not allow for manual path entry.

Also I think the proper solution would be to resolve the tilde when accessing the file rather than replacing the default with a hard path:

a user may manually enter a path relative to their home directory
A user may share a session file with someone else and vapor will try to use the original user’s config which may be undesirable, if it is even accessible.

@stasj please suggest the code changes to support this suggestion.

Also I think the proper solution would be to resolve the tilde when accessing the file rather than replacing the default with a hard path:

a user may manually enter a path relative to their home directory
A user may share a session file with someone else and vapor will try to use the original user’s config which may be undesirable, if it is even accessible.

@StasJ please suggest the code changes to support this suggestion.

Doing the above would require refactoring either the getters to replace tildes or refactoring our IO calls to handle them. That is assuming that our current IO calls cannot handle them, however, I still cannot reproduce #2657.

Also I think the proper solution would be to resolve the tilde when accessing the file rather than replacing the default with a hard path:

a user may manually enter a path relative to their home directory
A user may share a session file with someone else and vapor will try to use the original user’s config which may be undesirable, if it is even accessible.

@StasJ please suggest the code changes to support this suggestion.

Doing the above would require refactoring either the getters to replace tildes or refactoring our IO calls to handle them. That is assuming that our current IO calls cannot handle them, however, I still cannot reproduce #2657.

@stasj I can no longer reproduce this either, but the branch has been updated with a fix that is SettingsParams::Init(). Wasn't your argument that a more robust fix would be to handle the "~" in the getter? With the changes currently proposed don't we still have the problem that if a "~" finds its way into the database it may not be handled by whoever is doing I/O?

@stasj, the bug can still be reproduced if you have an existing .vapor3_settings file that has the old AutoSaveFileLocation default value of "~/VaporAutoSave.vs3".
However, in looking into this I noted that every single getter in SettingsParams that returns a path contains:
if (dir == "~") { dir = QDir::homePath().toStdString(); }
except for GetAutoSaveSessionFile(). I suggest we change GetAutoSaveSessionFile() to be consistent with the other getters and be done with this.

I suggest we change GetAutoSaveSessionFile() to be consistent with the other getters and be done with this.

@clyne I've added added logic that does this, but the way it was being done previously (shown below) was problematic.
if (dir == "~") { dir = QDir::homePath().toStdString(); }
This misses the case where dir=="~/foo".  Instead, I'm replacing all occurrences of ~ with the home directory.  For consistency, this logic has been given its own function, and is now being used by all Getters in SettingsParams instead of the code shown above.

@clyne this should be all set.


Enable TagHelper attributes to render in the order they were originally.

This was accomplished by changing when/how TagHelper attributes are rendered. Previously they were rendered: Bound => Unbound. Now they're rendered inthe order that they exist on the TagHelperChunk.
Regenerated test files to account for new re-ordering of TagHelper attributes.
Did not add additional tests since the current tests seem to be heavily impacted by the re-organization of code rendering; effectively showcasing the fix.

#225

/cc @dougbu

Did not add additional tests since the current tests seem to be heavily impacted by the re-organization of code rendering; effectively showcasing the fix.

Disagree with this choice.  The vast majority of the existing tests only saw AddTagHelperAttribute() calls move relative to CreateTagHelper() calls, as the CreateTagHelper() calls moved into a group.  Need a few more cases (besides PrefixedAttributeTagHelpers.cshtml and a couple of others):

mixing bound and unbound attributes
involving unbound attributes with duplicate names (this currently isn't tested at all)

Ideally would test whether TagHelperExecutionContext.AllAttributes and ...HtmlAttributes additions end up in the correct order more directly.  Unfortunately, that can be done only in a MVC test and Razor confirmations don't really belong there.  Good news is my spot checks, especially of generation for PrefixedAttributeTagHelpers.cshtml, indicate what's tested is working correctly.

:watch:

@dougbu Multiple tests cover those scenarios. Heck even just MinimizedTagHelpers covers both of the scenarios you mentioned and then some.

Updated.

even just MinimizedTagHelpers covers both of the scenarios you mentioned and then some by itself.

Minimized tag helper attributes are a special case. More generally we have very little coverage of code generation with multiple bound and unbound attributes in various source orders. And we have just one test (PrefixedAttributeTagHelpers.cshtml) involving attributes with duplicate names; that one covers only bound attributes.

@dougbu The MinimizedTagHelpers test has mixes of unbound/bound/required minimized/notminimized all mixed together. In addition to this TagHelpersInSection, BasicTagHelpers, ComplexTagHelpers, AttributeTargetingTagHelpers, SingleTagHelper all have  mixes of bound/unbound (multiples, not multiples etc.).
As for duplicate name-unbound attributes. We do only have 1 test covering that which is the MinimizedTagHelpers test and as you said it is a minimized attribute. I'll add a duplicate same name, unbound, unminimized to ComplexTagHelpers.

Added update to ComplexTagHelpers

:watch:

Updated.

:shipit: after addressing remaining few comments.


Fix TableScreen searchable

Also add search text to the example table screen in the app so that there are results when searching.
This should be merged asap and a minor version released since PM::TableScreen searching is broken in v1.4.0
Closes #134

Bacon::Error: not #<UIImage:0x1117c6550>.==(#<UIImage:0x1117cd040>) failed
	spec.rb:769:in `satisfy:': RubyMotionQuery styler: UIImageView - should set a remote image URL string
	spec.rb:783:in `method_missing:'
	spec.rb:459:in `execute_block'
	spec.rb:421:in `run_postponed_block:'
Bacon::Error: not #<UIImage:0x1117fb990>.==(#<UIImage:0x1117d99a0>) failed
	spec.rb:769:in `satisfy:': RubyMotionQuery styler: UIImageView - should set a remote image with a NSURL instance
	spec.rb:783:in `method_missing:'
	spec.rb:459:in `execute_block'
	spec.rb:421:in `run_postponed_block:'
Bacon::Error: not nil.==(nil) failed
	spec.rb:769:in `satisfy:': RubyMotionQuery styler: UIImageView - should set a remote image and no placeholder
	spec.rb:783:in `method_missing:'
	spec.rb:459:in `execute_block'
	spec.rb:421:in `run_postponed_block:'
Bacon::Error: #<UIImage:0x113201830>.==(#<UIImage:0x113201c70>) failed
	spec.rb:769:in `satisfy:': RubyMotionQuery styler: UIImageView - should fetch the image from memory
	spec.rb:783:in `method_missing:'
	spec.rb:316:in `block in run_spec_block'
	spec.rb:459:in `execute_block'
	spec.rb:316:in `run_spec_block'
	spec.rb:331:in `run'
118 tests, 154 assertions, 4 failures, 0 errors

OK, this should be ready to go. I even added a new test :)

@jamonholmgren
Locally:
bundle exec rake spec files='spec/ruby_motion_query/stylers/ui_image_view_spec.rb'

RubyMotionQuery styler: UIImageView
  - should set a placeholder image
  - should set a remote image URL string
  - should set a remote image with a NSURL instance
  - should keep the placeholder image when the remote image fails
  - should set a remote image and no placeholder
  - should fetch the image from memory

6 specifications (13 requirements), 0 failures, 0 errors

Nice. :shipit:

that remote image test i have seen fail on travis quite a bit actually...

Yeah, it fails all the time. And usually we can just restart it and it'll pass, but not this time. I've restarted it like 4 times. :cry:
It passes locally.

@twerth Can we release a new version with this fix in it?

Please release it, my search is broken :/

gem 'redpotion', github: 'infinitered/redpotion'

should do it for you till we get the next release out. Sorry for the delay!

We will be releasing a new version of ProMotion shortly, too.

Ok, thanks for the gem hint.

No problem. that basically uses the most recent version of the gem from github instead of the version released on rubygems. You can also specify branches if you want, but if you reference github and don't supply a branch parameter, it'll use master.

I was actually going to ask just that in this moment but then saw that you already answered the question :smile: Thanks!

I had the same issue, thanks for fix it.
Another thing is that "Cancel" button is not showing "Cancel" label, it is actually showing "...".
:(


Optimize ManagedConnection

This is just about eliminating some object allocations for performance.

[ ] Eliminate all methods that accept a nested closure to modify a command
[ ] Watch the Polly retry methods to avoid passing in closed variables to the lambdas being executed
[ ] Let's also streamline it so it's dumber so that it's only data execution. Execute() returns a DbDataReader, and not a T.

This was a duplicate.


merge: dev to stage

:tada: This PR is included in version 0.57.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add new WebUI.prototype functions to the list of array operations.

Add the following prototype functions:
at: [].at,
includes: [].includes,
toReversed: [].toReversed,
toSorted: [].toSorted,
toSpliced: [].toSpliced,

Completed.


Solves #3 : Adds Some description and screenshot to readme

Improves the readme description and adds a screenshot of the logged-in user screen to the README.md.
@kyzn
I've added the necessary links to the README.md as well.
Cheers!

Hi,
Unfortunately I'm going to close this Pull Request, as I ended up doing some rework on README.md.
Thanks for your help!


chore(launch): Launch hardening for next release

Fixes WB-NNNN
Fixes #NNNN
Description

Freezes kaniko version to one that works
Updates to the current good launch agent version

Testing
How was this PR tested?
Checklist

Include reference to internal ticket "Fixes WB-NNNN" (and github issue "Fixes #NNNN" if applicable)

@KyleGoyette do you want this in the upcoming release? if yes, please add to the *09.1 milestone and merge :)


[ROCm] Update to use ROCm 4.1 (when building TF with --config=rocm)

/cc @cheshire @chsigg @sanjoy

@cheshire @chsigg @sanjoy gentle ping

@cheshire @chsigg @sanjoy gentle ping

@gbaned this PR seems to have failed the internal review/check....anything I can do to move this PR forward?
thanks

I did the fixes, it is merged now.

Thank you @akuegel , really appreciate your help.


SSL connection to CLN fails using a custom certificate

After following the instructions in the CLN documentation here to install a custom certificate into CLN (in order to run CLN under SSL over Tor), the boltzd service is failing to connect to CLN with the error:
2024-07-20 15:31:08.930 [WARN ] Could not connect to lightning node: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate is not valid for any names, but wanted to match cln"

The ServerName for certificate validation is hardcoded here. One option is to regenerate my custom certificates with cln included as a SAN, but it sounds like boltzd shouldn't make such particular assumptions regarding the certificate settings, especially with custom certificates supported by CLN.

Yep, we'll fix this on our end

Fix is on master as you can see, we plan to include this in an official release towards end of the week

Release with the fix is finally out, sorry for the wait: https://github.com/BoltzExchange/boltz-client/releases/tag/v2.1.1


add stop word

github , for, this

Maybe you could find more to add together ? Now, the general stop words is few.

the

It should be filtered. I don't why. Let me figure it out.

nice job

I think adding the repo name to the corresponding stopword list is reasonable.


[Identity] Add the SharedTokenCacheCredential

.Net has this SharedTokenCacheCredential. We should have it too. .Net's API: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/api/Azure.Identity.netstandard2.0.cs#L214
Also use this credential from DefaultAzureCredential, and add these options to DefaultAzureCredential's constructor: excludeSharedTokenCacheCredential, sharedTokenCacheTenantId and sharedTokenCacheUsername.

We don't plan to add this to JS, the SharedTokenCacheCredential actually has some fairly fundamental issues which is why we have removed it from the DefaultAzureCredential authentication flow by default, and we're not recommending it's use.

@schaabs Thank you for the update!


Website crashing after installing paystack

Problem/Motivation
I tried to install the paystack plugin on my site and it keeps crashing. I tried using the magento connect and tried uploading the plugin manually through FileZilla.
Proposed resolution
(Description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch.)
I have a theme which carries its own package.xml file. Is there a way I can go around this or add to the previous package.xml file because I think the issue could be from there.
Repeatable
Always|Sometimes|Specific conditions|Specific times
(If it is a bug, you are reporting lease specify:)
Steps to repeat: (Describe how the issue can be repeated by someone who is to work on it)

Step 1
Step 2
...

Expected Results:
(What you expected steps 1, 2 and 3 to give)
Actual Results:
(What is gave including any error messages, memory dump etc that can help)

Hi @dolispy, follow the installation steps on the README file (the direct upload method) and let me know how it goes

Hi @steveamaza , i followed the steps and i got this error when clearing the cache
Package installed:
community Paystack_Inline <IP_ADDRESS>
Cleaning cache
....
Exception during cache and session cleaning

Hello @ibrahimlawal, I missed this response. Any idea what could be happening here? @dolispy, sincere apologies. Were you able to resolve?

When is the release for Magento 2 version.
I need to install on m2 server

@Dscnlag please see https://paystack.helpscoutdocs.com/article/88-how-to-setup-paystack-on-magento-2


adds design-system-provider component

Pull Request
📖 Description
This PR implements a Blazor component for the <fluent-design-system-provider> custom element.

🎫 Issues

👩💻 Reviewer Notes

📑 Test Plan

✅ Checklist
General

[ ] I have added tests for my changes.
[x] I have tested my changes.
[ ] I have updated the project documentation to reflect my changes.
[x] I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

[x] I have added a new component
[ ] I have modified an existing component

⏭ Next Steps

Nice! Do we not need to provide 'sensible' defaults for the properties (like the FillColor, etc.)? Or is that taken care of by the underlying fast web component?

The DesignToken infrastructure in the web component library handles the default case, so I don't think we need to assign any default values here.


Add embed for gvid.tv

The embed is there if you want to use it, for gvid.

Could you resubmit this against:
https://github.com/notabugio/notabug/tree/master/packages/notabug


openresty: disable perl module by default

Motivation for this change
This creates consistency with the other nginx packages.
Additionally, I have been receiving intermittent segfaults during config loading caused by the perl module (albeit on 20.03), despite there being no reference to perl in my configs:
#0  0x00007f03deb51a63 in Perl__invlist_intersection_maybe_complement_2nd () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#1  0x00007f03deb520a5 in S_populate_ANYOF_from_invlist.part.0 () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#2  0x00007f03deb61adf in S_regclass () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#3  0x00007f03deb683bf in S_regpiece () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#4  0x00007f03deb6ce13 in S_regbranch () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#5  0x00007f03deb6d3b4 in S_reg () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#6  0x00007f03deb722fc in Perl_re_op_compile () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#7  0x00007f03deb0731d in Perl_pmruntime () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#8  0x00007f03deb4371b in Perl_yyparse () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#9  0x00007f03debe4347 in S_doeval_compile () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#10 0x00007f03debe9cad in Perl_pp_require () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#11 0x00007f03deb9f336 in Perl_runops_standard () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#12 0x00007f03deb0d33c in Perl_call_sv () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#13 0x00007f03deb0ff38 in Perl_call_list () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#14 0x00007f03deaed720 in S_process_special_blocks.isra.0 () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#15 0x00007f03deb060ef in Perl_newATTRSUB_x () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#16 0x00007f03deb0967e in Perl_utilize () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#17 0x00007f03deb43bb9 in Perl_yyparse () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#18 0x00007f03debe4347 in S_doeval_compile () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#19 0x00007f03debe9cad in Perl_pp_require () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#20 0x00007f03deb9f336 in Perl_runops_standard () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#21 0x00007f03deb0d33c in Perl_call_sv () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#22 0x00007f03deb0ff38 in Perl_call_list () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#23 0x00007f03deaed720 in S_process_special_blocks.isra.0 () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#24 0x00007f03deb060ef in Perl_newATTRSUB_x () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#25 0x00007f03deb0967e in Perl_utilize () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#26 0x00007f03deb43bb9 in Perl_yyparse () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#27 0x00007f03deb14053 in perl_parse () from /nix/nix/store/...-perl-5.30.1/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE/libperl.so
#28 0x0000562f8df614ed in ngx_http_perl_create_interpreter (pmcf=0x562f8f4f3920, pmcf=0x562f8f4f3920, cf=0x7ffed953fa50) at src/http/modules/perl/ngx_http_perl_module.c:605
#29 ngx_http_perl_init_interpreter (cf=0x7ffed953fa50, pmcf=0x562f8f4f3920) at src/http/modules/perl/ngx_http_perl_module.c:524
#30 0x0000562f8df61d49 in ngx_http_perl_init_main_conf (conf=<optimized out>, cf=<optimized out>) at src/http/modules/perl/ngx_http_perl_module.c:819
#31 ngx_http_perl_init_main_conf (cf=<optimized out>, conf=<optimized out>) at src/http/modules/perl/ngx_http_perl_module.c:814
#32 0x0000562f8def8729 in ngx_http_block (cmd=<optimized out>, conf=<optimized out>, cf=<optimized out>) at src/http/ngx_http.c:263
#33 ngx_http_block (cf=0x7ffed953fa50, cmd=<optimized out>, conf=<optimized out>) at src/http/ngx_http.c:121
#34 0x0000562f8ded8109 in ngx_conf_handler (last=1, cf=0x7ffed953fa50) at src/core/ngx_conf_file.c:463
#35 ngx_conf_parse (cf=cf@entry=0x7ffed953fa50, filename=filename@entry=0x562f8f4efda0) at src/core/ngx_conf_file.c:319
#36 0x0000562f8ded5959 in ngx_init_cycle (old_cycle=old_cycle@entry=0x562f8f7bfe00) at src/core/ngx_cycle.c:275
#37 0x0000562f8deec25d in ngx_master_process_cycle (cycle=<optimized out>) at src/os/unix/ngx_process_cycle.c:242
#38 0x0000562f8dec31de in main (argc=<optimized out>, argv=<optimized out>) at src/core/nginx.c:382

The change from specifying perl = null to withPerl is necessary due to openresty's use of perl in its configure script.
I have tested nginxStable, nginxUnstable, nginxShibboleth, and openresty using my unmerged nginx-variant tests from #89342.
Things done

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

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

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

Hmm, if it was about openresty, wouldn't passing it perl=null; make more sense? The segfault might indeed motivate making the most frequent no-Perl mode the default, but then the description should be talking about this point of view and not just about openresty

@7c6f434c sure, will do if you want.

@7c6f434c done.

I think even this version should still mention switching to the withPerl flag in the commit message (and then you can add one line about segfaults and make withPerl false by default, no problem)

@7c6f434c done

Apparently I fail to express what I am actually annoyed by.
You replace perl=null with withPerl globally (for Nginx), not just for openresty (and that's what I asked to mention in the first commit message). The predefined packages stay the same, but the override interface changes.
(In principle, openresty could just check for perl == null instead of the flag, but I can see the motivation to have things in a cleaner way, especially when half of the versions already disable Perl)

@7c6f434c I'm still confused sorry. The motivation for all of this is that I can't check for perl==null, because openresty depends on perl at build time (./configure is written in perl).

That means that in the status quo it is impossible for a user to turn off perl in openresty (except by overriding to delete some configure flags)

I still don't understand what you want at this point. Is the issue that the commit message is not explicit that the change affects all nginx packages>

Yes — as I said, I agree with the changes themselves.

@7c6f434c I split this into two commits that are more clear about what they apply to -- hope that seems right to you.

Thanks!


AQL result is not as expected when the same archetype is used in two different templates

Environment information
EHRbase version:0.23.0
openEHR_SDK version:1.19.0
Archie version:2.0.1
PostgreSQL version: PostgreSQL 13.7, compiled by Visual C++ build 1914, 64-bit
Java Runtime version: Oracle Corporation 17.0.4.v20221004
Steps to reproduce
Sample Template-1(encounter-signsymptom-3.en.v0) has composition(encounter) > observation(story)
Sample Template-2(encounter-signsymptom-5.en.v0) has composition(encounter) > observation(story) > cluster(sign-symptom)
Input Eg:->
Sample FLAT- for template 1 only observation is entered, since  template has only observation
"encounter-signsymptom-3.en.v0/story_history/any_event:0/story:0": "Test-Story-1"
Sample FLAT- for template 2 observation and cluster details is entered, template has both observation and cluster as archetypes
"encounter-signsymptom-5.en.v0/story_history/any_event:0/story:0": "Test-Story-2",
"encounter-signsymptom-5.en.v0/story_history/any_event:0/symptom_sign/symptom_sign_name": "Test-sign-symptom-2",
Below is the AQL used :
{
"q" : "SELECT  e/ehr_id/value as ehrId, c/uid/value as composition_id, c1/items[at0001]/value/value as name, o1/data[at0001]/events[at0002]/data[at0003]/items[at0004]/value/value as story, c/archetype_details/template_id/value as template FROM ehr e[ehr_id/value='{{ehrId}}'] CONTAINS COMPOSITION c[openEHR-EHR-COMPOSITION.encounter.v1] contains (observation o1[openEHR-EHR-OBSERVATION.story.v1] or cluster c1[openEHR-EHR-CLUSTER.symptom_sign.v1]) where (o1/data[at0001]/events[at0002]/data[at0003]/items[at0004]/value/value='Test-Story-1' and c/archetype_details/template_id/value ='encounter-signsymptom-3.en.v0') or (c1/items[at0001]/value/value ='Test-sign-symptom-2' and c/archetype_details/template_id/value ='encounter-signsymptom-5.en.v0')"
}
Attached is the  zip file which has  sample templates , composition and aql
sign-syptom-AQL-issue.zip
Actual result
"rows": [
    [
        "47441ec1-8d2d-40d6-b4ca-9053327747ff",
        "9136e5c4-5bca-4566-832e-ab2a41a2031b::local.ehrbase.org::1",
        "Test-sign-symptom-2",
        "Test-Story-2",
        "encounter-signsymptom-5.en.v0"
    ]
]

AQL result is not as expected, since its filtering out with template ID which has all the archetypes mentioned in the containment , if any template that does not contain that archetype its not taken into consideration.
As soon as we query for signsymptom name in select clause or in where clause, its taking only (template2) into consideration, template1 is not considered at all
Further Debugging in code we got this below SQL query against which it return the results
select ehr_join.id as ehrId, jsonb_extract_path_text(cast(ehr.js_composition(
cast(composition_join.id as uuid),
'local.ehrbase.org'
) as jsonb),'uid','value') as composition_id, (array_509096368_57.var_509096368_58#>>'{/data[at0003],/items[openEHR-EHR-CLUSTER.symptom_sign.v1],0,/items[at0001],0,/value,value}')::TEXT as name, (array_1197837163_59.var_1197837163_60#>>'{/value,value}')::TEXT as story, ehr.entry.template_id as template from ehr.entry right outer join ehr.composition as composition_join on composition_join.id = ehr.entry.composition_id right outer join ehr.ehr as ehr_join on ehr_join.id = composition_join.ehr_id join lateral (
select (ehr.xjsonb_array_elements((ehr.entry.entry#>>'{/composition[openEHR-EHR-COMPOSITION.encounter.v1],/content[openEHR-EHR-OBSERVATION.story.v1],0,/data[at0001],/events,/events[at0002]}')::jsonb))
AS var_509096368_58) as array_509096368_57 on true join lateral (
select (ehr.xjsonb_array_elements((ehr.xjsonb_array_elements((ehr.entry.entry#>>'{/composition[openEHR-EHR-COMPOSITION.encounter.v1],/content[openEHR-EHR-OBSERVATION.story.v1],0,/data[at0001],/events,/events[at0002]}')::jsonb)#>>'{/data[at0003],/items[at0004]}')::jsonb))
AS var_1197837163_60) as array_1197837163_59 on true where (ehr.entry.template_id = 'encounter-signsymptom-5.en.v0' and ( ( (array_1197837163_59.var_1197837163_60#>>'{/value,value}')::TEXT  = 'Test-Story-1' and ehr.entry.template_id  = 'encounter-signsymptom-3.en.v0' )  or  ( (array_509096368_57.var_509096368_58#>>'{/data[at0003],/items[openEHR-EHR-CLUSTER.symptom_sign.v1],0,/items[at0001],0,/value,value}')::TEXT  = 'Test-sign-symptom-2' and ehr.entry.template_id  = 'encounter-signsymptom-5.en.v0' )  and ehr_join.id  = '47441ec1-8d2d-40d6-b4ca-9053327747ff'))
As we can see in where clause its considering only template2
Expected result
"rows": [
[
"47441ec1-8d2d-40d6-b4ca-9053327747ff",
"9136e5c4-5bca-4566-832e-ab2a41a2031b::local.ehrbase.org::1",
"Test-sign-symptom-2",
"Test-Story-2",
"encounter-signsymptom-5.en.v0"
],
[
"47441ec1-8d2d-40d6-b4ca-9053327747ff",
"88367g5c4-3rca-8966-821e-sd2a41w3031b::local.ehrbase.org::1",
null,
"Test-Story-1",
"encounter-signsymptom-3.en.v0"
]
]
AQL should have returned results across any templates which has archetype openEHR-EHR-OBSERVATION.story.v1 for given ehrId.

Hello @manci22lc,
Thank you for detailed bug description.
Issue was analyzed and reproduced at my side as well.
Defect ticket reported in our internal JIRA: https://jira.vitagroup.ag/browse/CDR-722
Will let you know, when it is fixed.
CC: @vidi42 , @HolgerReiseVSys

please recheck  with https://github.com/ehrbase/ehrbase/releases/tag/v2.0.0


SCSM SDK Missing Documentation

Describe the bug
SCSM SDK 2012 and 2016 are missing documentation
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/dotnet/api/?view=sc-sm-dotnet-2012
Click on no namespaces or documentation available
Same goes for 2016

@rloutlaw Can you please take a look at this issue?


Add Feature Light/Dark Mode toggle

Hello Sir,
After visiting your website i found that there was no dark/light mode toggle button.
I can add this which will enhance the beauty of your website.
Please assign this issue to me under GSSOC 2024

Hello Sir,
I found that there was no dark/light mode toggle button.
I can add this which will enhance the beauty of your website.
Please assign this issue to me under GSSOC 2024 @ashutoshgithubs

@mdrehan369 Can you please assign this issue to me..?

please assign me this issue


Improve Prettification of JSON

The default prettification we're using creates a lot of redundant whitespace. The Vega folks use `'json-stringify-pretty-compact', which does a really nice job of balancing readability with compactness.

Resolved in build 121.


Do not insert newline when there are no sub-Commands

@aaronjheng I went ahead and implemented this across all of the Argument Help Groups.


Missing statements/read/mine scope

I wonder why LRSQL is missing statements/read/mine scope.
It's critical for us to separate xapi access by customer.
Is there any other way we can achieve this behaviour?

Hello @DmitriyKabanov!
We did not implement statements/read/mine in SQL LRS since at that time none of our LRS customers has had a need for that feature, so we decided to deprioritize it during development. Now that we have people like you who do have a need, implementing it is back on our roadmap.
Are you using the recently-added OIDC authentication for SQL LRS? We are curious if the statements/read/mine scope would be more popular now that we have added support for OIDC.

Hi @kelvinqian00!
No, we're using api key/secret pairs per customer.

Do you have a timeline when this feature will be implemented?
Could you please confirm, that we can continue using LRS SQL with api key/secret pairs and assume that access control via statements/read/mine will just work as soon as you release it?

Hey @milt!
It's been a while since out last catchup.
Is there any updates?

We currently have a PR up that will implement this feature (#245). However, as Milt said previously we are also busy with several other projects at the moment, so it may be a while before the update is officially released.

Hey @kelvinqian00!
Thank you for the update.
Do you have an ETA when this PR will go live?
It's been a month this PR is open.

Our team is currently working on releasing an open beta for a separate project, and we are aiming to release that either end of this week or beginning of next week. Once that is done we can refocus and return to SQL LRS tasks such as this.

Apologies for the delay, but the statements/read/mine scope has been implemented in the latest release of SQL LRS v0.3.6.

Closed as the statements/read/mine scope feature has been implemented with no issue for over a month.


Display running average of day/night scores

HI @mbokinala, thanks for the PR, I like the idea but I want to keep it simple. Feel free to create your own version though. I'll add a MIT license so you can do whatever you like with my code.


wifi/cloud integration?

I know this is a BT integration, but maybe you can point me in a correct direction
I have a BT Eglo lamp and an Eglo smart plug which acts as a wifi <-> mesh bridge. From my phone app, I'm able to operate the lamp even when I'm not within its range - so it works via wifi
unfortunately, my HA server is far enough from the lamp that I can't make a BT-only connection: either the plug doesn't reach the lamp or the server (which is Rpi with built-on bt) can't reach the plug
so he question is is there an Eglo integration that would work similarly to their app, i.e. via wifi?

No sorry, I don't know any integratie that can use the wifi features of Awox.
But maybe you can build a small BT hub based on  https://github.com/fsaris/EspHome-AwoX-BLE-mesh-hub that you could position in reach of your plug

I'm trying to build something myself by reading your cloud connection code. is the awox.cloud api you're using a public one? is there any documentation? thx in advance :)

I reversed engineered it by using Wireshark and the app on a old android device ;)
There is no real public API
Maybe this can help you to get started https://github.com/fsaris/EspHome-AwoX-BLE-mesh-hub/issues/27#issuecomment-1681117854 I created a little jsfiddle to get the mesh credentials


fix range input number not show on firefox

fix the range input number not showing on firefox #233

I want to contribute as well and want to merge pull requests


Raise error upon construction of out-of-bounds datetime?

In pydata/xarray#1252 I am working on a NetCDFTimeIndex that is intended to bring some of the features of pandas's DatetimeIndex (for now namely field accessors and partial datetime string indexing) to time indexes that use netcdftime._netcdftime.datetime objects.
Currently one can construct non-sensical datetimes using netcdftime._netcdftime.datetime objects:
In [1]: from netcdftime import DatetimeNoLeap

In [2]: DatetimeNoLeap(1, 45, 45)
Out[2]: netcdftime._netcdftime.DatetimeNoLeap(1, 45, 45, 0, 0, 0, 0, -1, 1)

Would it be possible for this kind of expression to raise an error?  This would be nice, because that way if one tries to index with a slice involving an out-of-bounds datetime, it would automatically cause an error, rather than behave in the fashion below:
In [1]: import xarray as xr

In [2]: from xarray.conventions.netcdftimeindex import NetCDFTimeIndex

In [3]: from netcdftime import DatetimeNoLeap

In [4]: dates = [DatetimeNoLeap(1, 1, 1), DatetimeNoLeap(1, 2, 1), DatetimeNoLeap(2, 1, 1), DatetimeNoLeap(2, 2, 1)]

In [5]: da = xr.DataArray([1, 2, 3, 4], coords=[NetCDFTimeIndex(dates)], dims=['time'])

In [6]: da.sel(time=slice(DatetimeNoLeap(1, 1, 1), DatetimeNoLeap(1, 45, 45)))
Out[6]:
<xarray.DataArray (time: 2)>
array([1, 2])
Coordinates:
  * time     (time) object    1-01-01 00:00:00    1-02-01 00:00:00

cc @shoyer

This should absolutely be done. We should be able to provide similar checks to what is provided in the datetime module.
In [1]: import datetime

In [2]: datetime.datetime(2000, 1, 45, -4)
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-2-2492d881556f> in <module>()
----> 1 datetime.datetime(2000, 1, 45, -4)

ValueError: day is out of range for month```


Flesh out the base layer test suite

Currently the base interface test suite (grpc_test.framework.interfaces.base) is little more than a smoke test and nowhere near as comprehensive as I'd like it to be. After Beta would be a good time to try to complete it.

This is not going to happen and it is not going to need to happen.


upgrade check: upgrade to same version is a noop

We actually had a test that was "upgrading" from one version to the very same
version. This commit adds a check for that case.
Signed-off-by: Nathan Cutler<EMAIL_ADDRESS>

I thought this would address the following:
2017-07-03T16:12:30.234 INFO:teuthology.task.install:Ceph rpm upgrade from 10.2.7-430.g53a3be7.el7 to 10.2.7-430.g53a3be7

But now I see there's a .el7 on the end of the first version, which is missing in the second, and that causes the second one to be "less" than the first.
Not sure if we can reasonably check for that, though.

Maybe just strip off any .el\d+ at the end of the version number, before doing any comparisons?

@gregsfortytwo In general our upgrade testing seems like it could be improved. Your take on the comments above?

@gregsfortytwo This fix is based on two hypotheses:
Hypothesis #1: The code in upgrade_common only runs when the install.upgrade task is specified in the test yaml.
Hypothesis #2: install.upgrade is currently used only to upgrade packages from the Ceph monolith.
Now, if someone constructs test yaml that ends up instructing install.upgrade to either (a) downgrade Ceph packages or (b) keep them at the same version, then that would indicate the test is not doing what was intended.
The idea here is to help discover semantic issues in the upgrade tests - i.e. cases when install.upgrade was intended to upgrade Ceph, but in reality that's not happening.
I already landed a patch that fails the test if install.upgrade ends up downgrading, but I would like (and maintain that it makes sense) to fail the test if it ends up installing the same version on top of the existing packages, as well.
Can you think of a case when install.upgrade would be intentionally used to just reinstall the same version of the Ceph packages?

Marking DNM until I can figure out what can be done (if anything) about https://github.com/ceph/teuthology/pull/1090#issuecomment-312738217

Ugh, I'm sorry. I merged without refreshing this browser tab, which I opened this morning...


Remove reliance on Sprockets

Cherry-picked a few commits from #2419.
Sprockets can be fully replaced by Webpacker, so there's no reason to continue using it. This changes all usages of static images to use Webpacker instead of Sprockets. Rails 7 removes Sprockets as a hard dependency, and there's no harm backporting this change for Rails 6.1 to make Sprockets' removal easier in the Rails 7 upgrade. So here we are. Goodbye, Sprockets.

This caused a production failure when deployed, which I fixed with 1deecd44d8143927b4efc2f1e242cf45dd3b1507. Turns out you also need to remove the config.assets.* options or things will catch on fire.


React vs Vue vs Solid

In the following, Bati's offical recommendation.
The recommendation follows an open discussion: everyone (especially UI framework maintainers) can engage in a conversation with us if they believe our recommendation to not be accurate.

All three are great choices and there are plenty of companies proving that you can build a successful business with each.
A lot of the choice is about personal preference: we recommend reading the offical website and documentation of React, Vue, and Solid and see what resonates most with you. (If all three seem just fine to you and none of them sticks out, then you can fallback with the conservative choice of picking the most widespread one which currently is React.)
Vike works with any UI framework, which means that you can use several UI frameworks for the same website. For example, you can use Vue or Solid while using this one React library that only works with React. (That's why we say that "Vike has the largest ecossystem" as you can cherry-pick from the ecosystem of any UI framework.)
Instead of getting stuck with decision paralysis, we recommend to decide and get started quickly and, as you scale, see for yourself whether you like your initial choice, and progressively switch UI frameworks if you change your mind.
React:

Pro: Largest ecosystem.
Pro: JSX templates (personal preference: it's a "con" for some people).
Pro: Innovative.

React introduced many novelties, most notably unidirectional UIs, JSX, Hooks, and Server Components.

Con: Sometimes difficult to use.

Its reactivity system is based on immutable objects which makes React inherently difficult to use (for example, you'll need to use memo to keep your app performant).
Sometimes complex, for example UI tearing is complex in a leaky way: libraries cannot always fully abtract that complexity away.
It has to be shown whether RSC will manage to provide an easy DX. Today, using RSC is difficult to use.
It has a lot of paper cuts, such as unhelpful error messages, no built-in TypeScript types, or libraries with broken ESM which need manual fixing.

Vue:

Pro: Large ecosystem.
Pro: Simple.
Pro: HTML-like templates (personal preference: it's a "con" for some people).
Pro: Cohesive ecosystem of basic tools.

Solid:

Pro: Simple.

Its reactivity system is based on observable objects, which makes it considerably simpler to use and more performant.

Pro: Highly performant.
Pro: JSX templates (personal preference: it's a "con" for some people).
Pro: Responsive maintainers and bugs are fixed promptly.
Con: Its ecosystem is growing but still not as large as React/Vue's ecosystem.

Really good points. The next task on my todo list was to explain the recommendations, so thanks for that 😃
I still need to find a proper way to show them in the interface (could be difficult for the embed/widget UI)

You're welcome 😀 Although it's a rough draft that needs polishing.

needs polishing

Speaking of which:

~Beyond personal preference, there is one aspect we recommend to be careful about: the ecosystem. We recommend to think about what tools your business will need and to double check whether the UI framework's ecosystem has what you need.~
Vike works with any UI framework, which means that you can use several UI frameworks for the same website. For example, you can use Vue or Solid while using this one React library that only works with React. (That's why we say that "Vike has the largest ecossystem" as you can cherry-pick from the ecosystem of any UI framework.)
Instead of getting stuck with decision paralysis, we recommend to decide and get started quickly and, as you scale, see for yourself whether you like your initial choice, and progressively switch UI frameworks if you change your mind.


Can report presence active even after in background

This is potentially one of the causes of #3659: which would mean it's causing people not to get notifications when they should.
It hasn't been confirmed empirically -- that'll be an important step in addressing the issue.
Found from studying the source. As I wrote there:

[@ray-kraesig] Or at least that the mobile app should be better about declaring its lack of presence. (We could possibly put something appropriate in handleAppStateChange... but there's a reportPresence call in there that looks like it's supposed to handle exactly this. )

Hmm. There is indeed that:
  handleAppStateChange = (state: 'active' | 'background' | 'inactive') => {
    const { dispatch, unreadCount } = this.props;
    dispatch(reportPresence(state === 'active'));

But then there's also this:
export const doInitialFetch = () => async (dispatch: Dispatch, getState: GetState) => {
  dispatch(reportPresence());
  setInterval(() => dispatch(reportPresence()), 60 * 1000);

That doesn't know anything about being in the background or not. And the hasFocus argument to reportPresence defaults to true. So one thing that may be happening is

app is put in background

handleAppStateChange gets called; calls reportPresence(false)

sometime in the next 60 seconds, the timer set up by doInitialFetch fires

... and the OS hasn't yet totally put us on ice. So it runs, and does effectively reportPresence(true), which tells the server we're active after all.

So that, at least, seems like straightforwardly a bug.

(If empirically it turns out this doesn't seem to happen, then that'll be interesting and it'd be good to understand why. Also that fact may be a fragile one, dependent on facts about the platforms that aren't evident in our code, and might not be stable over time -- in which case it'd be good to adjust the code so that it definitely behaves right even if those external facts change.)

At least on my Android test setup, it's both worse and better than that: the setInterval()-triggered reportPresence doesn't seem to be firing while the app is inactive... but handleAppStateChange isn't kicking off a presence report at all.
Looking at the code suggests this is due to the throttling in the middle of usersActions#reportPresence. Since it's almost always been less than a minute since the last heartbeat, the user will never be reported as idle.

Looking at the code suggests this is due to the throttling in the middle of usersActions#reportPresence. Since it's almost always been less than a minute since the last heartbeat, the user will never be reported as idle.

Oh gosh, indeed. That logic basically doesn't make sense at all in a world where this function has parameters.
A local fix might be to remember the last value we sent for hasFocus (and eliminate the other parameter, which is never passed), and bypass the throttling if the new value is different. But this code probably deserves bigger changes than that, too.

From discussion in chat and on #3704 , having unpacked more clearly how the Zulip presence subsystem works and what the various states of it mean, we reached the conclusion that it doesn't actually make sense to send an inactive report!
So really the root bug here is that we have code that attempts to send such a thing. Then that bug is sort of masked by the other bugs we have in this logic, which cause us that code not to work as intended.
Anyway, #3704 should fix this whole cluster of bugs, notably by introducing a clearly-demarcated state machine.


Slide-toggle theme color does not follow app theme definition, but is fixed at 500 level default

Bug:
slide toggle does not match app theme definition when base is set (to a value other than the default 500 'level')
What is the expected behavior?
That Slide-toggle @Input() color: ThemePalette matches app theme definition when base is defined so that slide-toggle will match other themed components
What is the current behavior?
Slide toggle is fixed at the 500 level for each theme color: e.g., primary, accent and warn.
What are the steps to reproduce?

) set app theme to values other than default; e.g.,

@import '~@angular/material/theming';
@include mat-core();

$primary: mat-palette($mat-teal, 700, 300, 900);
$accent: mat-palette($mat-blue, 900, 300, 900);
$warn: mat-palette($mat-red, 900, 300, 800);

$my-theme: mat-light-theme($primary, $accent, $warn);
@include angular-material-theme($my-theme);

Compare Switch (slide-toggle) to other theme-able components

Inspect hex value; e.g.,: version with 'accent' (mat-blue palette) theme color applied:
button: #0d47a1 = 700 (accent, base from mat-blue-palette)
chip:  #0d47a1 = 700
slide toggle: #2196f3 = 500

[](StackBlitz example: https://stackblitz.com/edit/angular-theme-test)
What is the use-case or motivation for changing an existing behavior?
The switch does not match my other themed components, it is lighter
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6+, Angular Material 6+, mac os, all browsers
Is there anything else we should know?
issues seems to be in setting the thumb-checked-hue to 'default' in light theme in the slide-toggle theme
...
$thumb-checked-hue: if($is-dark, 200, default);

This is a duplicate of 12698 and https://github.com/angular/material2/issues/11854


Fix freeze in TextEdit with scroll_past_end_of_file and fit_content_height

fixes https://github.com/godotengine/godot/issues/84742

scroll_past_end_of_file and fit_content_height don't make sense together so scroll_past_end_of_file now needs fit_content_height to be false.

This should probably be mentioned in the description of fit_content_height.

The description for scroll_fit_content_height says '[TextEdit] will disable vertical scroll', so it should be clear that scroll_past_end_of_file, scroll_v_scroll_speed, set_line_as_first_visible(), adjust_viewport_to_caret(), and other things related to vertical scrolling won't do anything, right?

Makes sense.

Thanks!

Thanks, this bug was driving me nuts when I was trying to fix it. Glad you sorted it out!


Would you develop  a  uv  plugin for pycharm   ,  ask      entreatly .

Would you develop  a  uv  plugin for pycharm   ,  ask      entreatly .

They're going to natively support uv, refer https://youtrack.jetbrains.com/issue/PY-75985/Allow-extending-PythonAddNewEnvironmentPanel#focus=Comments-27-10763817.0-0 and the tracking issue is https://youtrack.jetbrains.com/issue/PY-70533.

@dhruvmanila
Good new for everyone!!
I appreciate your help!


Publishing / Marketing

General ideas here - break out into issues as they are finalized.
The hacker's bookmarks
Quixer -
Denotes speed & universal searchability
Refine logo

Alfred, Quicksilver or spotlight but web-focused
"Quicker Search"
Hacker's bookmarks
Custom search engines - enhanced

Small bit of SEO?
reach out to anyone directly?

Make it really clear - 10-sec pitch, 3-sec. video/gif demo - show the magic moment
Who's it for?
Who's it NOT for?

Why is it better than Alfred (has some web integration)? What else exists that's similar?

Harness the raw power of your browser's URL bar


removed einsum causing error when use_atten_result is enabled

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #659
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

Screenshots
Please attach before and after screenshots of the change if applicable.

Before
After

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I have not rewritten tests relating to key interfaces which would affect backward compatibility

@bryce13950 should I close this, or should we merge the test?

Sorry @oliveradk! The last month has been pretty busy, and this one slipped through the cracks. Looks perfect, and it will be in the next release.


Learning rate scheduler

Hello,
I have a question regarding the learning rate. Is there a special reason why you use triangular cycle as learning rate scheduler?
Thanks in advance.

No special reason, in fact, we just simply try it and find that it works well for training our unified framework for segmentation and pose estimation.


[AZ Linux Pipeline] Changes needed to get the project running on Linux

Description
Changes in the project and code to get them running on a Linux pipeline in Azure DevOps
Changes

Several instances of changing backslashes by forward slashes
Capitalization disparities fixed

Details
We got a pipeline deploying a TestBot to Linux running in Azure DevOps.

For this, we took as a starting base the TestBot pipeline Nightly-Build-Test which is deploying a bot on Windows, but made some modifications to get it running under Linux.
Changes done to the pipeline
New tasks:
•	We had to remove the Visual Studio Build solution step because It wasn't compatible with the Linux platform and replace it by the MSBuild Build solution step. Due to this change, we had to…
•	Replace both the Use NuGet 4.9.1 and the NuGet restore by a dotnet restore step.
•      We added a PowerShell step to add the section RuntimeIdentifiers to three projects that required it
Existing tasks:
•	We had to change the zip filename in the az webapp deployment command at the Create Resources step, leaving the line as:
az webapp deployment source config-zip --resource-group "$(BotGroup)" --name "$(BotName)" --src "$(System.DefaultWorkingDirectory)/tests/Microsoft.Bot.Builder.TestBot/PublishedBot/Microsoft.Bot.Builder.TestBot.zip"

•	We had to change the PowerShell script that was running on the task Get Bot Keys to the following:
$json = Get-Content '$(System.DefaultWorkingDirectory)/DirectLineCreate.json' | Out-String | ConvertFrom-Json

$key = $json.properties.properties.sites.key

echo "##vso[task.setvariable variable=DIRECTLINE;]$key"
echo "##vso[task.setvariable variable=BOTID;]$(BotName)"

Changes done to the code
•	We had to change backslashes hardcoded in several parts of the code since they need to be forward slashes in Unix. For this, we will use System.IO.Path.Combine in the final PR.
•	We had to change some oversight capitalization in filenames and paths that were running well on Windows but didn't on Unix, due to the latter being case-sensitive.

Pull Request Test Coverage Report for Build 59699

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.008%

Totals

Change from base Build 59695:
0.0%

Covered Lines:
4008

Relevant Lines:
6072

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll

This looks good. Merging in so we can get the Linux tests working tomorrow.


Update reconciliation requeu and status update logic

@vbnrh and @umangachapagain Was running some tests in the QE setup and came across a few issues, posting this PR for a look at the issues and potentially a better PR for actual fixes.

Stale...


Switch the build to using Maven 4 and the 4.1.0 model

This PR obviously needs a CI change to build with 4.0.0-beta-5, but it serves as a testing for https://github.com/apache/maven/pull/1818

BOM GA's changed, this PR will now fail with beta-5 unless updated


[Request]: Side Bar Guide

What feature would you like to add?
Hi Developers. I tried looking for the left side bar guide however, I can't find it anywhere.
Notes
No response

Hi, I'm not sure what you mean.
The left sidebar (panel navigation) is created automatically from all your docs. The right sidebar is the table of contents, which is created also automatically based on the headings from your markdown file.

Hi Lukas.
I am referring to this:

Ah, I see. I've described it in the issue here https://github.com/GuavaCZ/filament-knowledge-base/issues/30#issuecomment-2194223523
I need to add some more info in the docs about the front matter.

I've added some info to the readme about the different front matter options.

To clarify the process of creating a parent-child relationship in the left-side navigation panel, please follow these steps:

Create a parent document: Execute the command docs:make test.main.
Update your data: Ensure to set the title, for instance, title: Main.
Create a child document: Execute the command docs:make test.child1.
Update your data: Add a title and specify the parent. For example, parent: Main. Note that this is case-sensitive, so ensure the data matches precisely.

Hi,
When I follow the steps given by @markwillow , I get an error:
Guava\FilamentKnowledgeBase\KnowledgeBase::documentable(): Argument #1 ($documentable) must be of type
Guava\FilamentKnowledgeBase\Contracts\Documentable|string, null given, called in /Users/charlie/Herd/test-
filament/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 358

My files:
/docs/fr/test/main.md
/docs/fr/test/child1.md

/docs/fr/test/main.md
---
title: Main
---

# Main

Lorem ipsum dolor sit amet

/docs/fr/test/child1.md
---
title: Child 1
parent: Main
---

# Child 1

Lorem ipsum dolor sit amet


7.3.0

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #37.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #37

@Tobias-Fischer do you need this in fast? I would like to use this to report the issue of the missing update in cf-scripts, but if you need this fast we can wait for another update.

We eventually need it for https://github.com/conda-forge/gz-sim-feedstock/pull/64 but I’m in no rush at all

We eventually need it for conda-forge/gz-sim-feedstock#64 but I’m in no rush at all

Great, thanks.

I know how to reproduce the issue without waiting for an actual update, so for me we can go forward on this, thanks!

Output:
21/84 Test #21: COMMON_TEST_collisions_bullet-featherstone ..........................***Exception: SegFault 11.03 sec
[==========] Running 4 tests from 3 test suites.
[----------] Global test environment set-up.
[----------] 1 test from CollisionTest/0, where TypeParam = struct CollisionFeaturesList
[ RUN      ] CollisionTest/0.MeshAndPlane
No plugins with required features found in D:/bld/gz-physics7_1727157569951/work/build/bin/gz-physics7-bullet-featherstone-plugin.dll
D:\bld\gz-physics7_1727157569951\work\test\common_test\collisions.cc(66): Skipped

[  SKIPPED ] CollisionTest/0.MeshAndPlane (1 ms)
[----------] 1 test from CollisionTest/0 (1 ms total)

[----------] 2 tests from CollisionMeshTestFeaturesList
[ RUN      ] CollisionMeshTestFeaturesList.MeshOptimization
Testing plugin: gz::physics::bullet_featherstone::Plugin
[Dbg] [D:\bld\gz-physics7_1727157569951\work\bullet-featherstone\src\SDFFeatures.cc:1096] Optimizing mesh (convex_decomposition): D:\bld\gz-physics7_1727157569951\work\test\resources\chassis.dae
[Dbg] [D:\bld\gz-physics7_1727157569951\work\bullet-featherstone\src\SDFFeatures.cc:1096] Optimizing mesh (convex_hull): D:\bld\gz-physics7_1727157569951\work\test\resources\chassis.dae
[       OK ] CollisionMeshTestFeaturesList.MeshOptimization (6619 ms)
[ RUN      ] CollisionMeshTestFeaturesList.MeshDecomposition
Testing plugin: gz::physics::bullet_featherstone::Plugin
[Wrn] [D:\bld\gz-common5_1724573723174\work\graphics\src\OBJLoader.cc:202] Missing material for shape[V_shape] in OBJ file[D:\bld\gz-physics7_1727157569951\work\test\resources\v_shape.obj]
[Wrn] [D:\bld\gz-common5_1724573723174\work\graphics\src\OBJLoader.cc:202] Missing material for shape[base] in OBJ file[D:\bld\gz-physics7_1727157569951\work\test\resources\v_shape.obj]
[Dbg] [D:\bld\gz-physics7_1727157569951\work\bullet-featherstone\src\SDFFeatures.cc:1096] Optimizing mesh (convex_decomposition): D:\bld\gz-physics7_1727157569951\work\test\resources\v_shape.obj
[       OK ] CollisionMeshTestFeaturesList.MeshDecomposition (4070 ms)
[----------] 2 tests from CollisionMeshTestFeaturesList (10690 ms total)

[----------] 1 test from CollisionStaticTestFeaturesList
[ RUN      ] CollisionStaticTestFeaturesList.StaticCollisions
Testing plugin: gz::physics::bullet_featherstone::Plugin
[       OK ] CollisionStaticTestFeaturesList.StaticCollisions (299 ms)
[----------] 1 test from CollisionStaticTestFeaturesList (299 ms total)

[----------] Global test environment tear-down

As bullet-featherstone is not the default physics engine and is still in progress, I think we can just skip the test for now, also to avoid blocking everything.

By the way, apparently also the same test for dartsim was failing: https://github.com/conda-forge/gz-physics-feedstock/pull/7#issuecomment-1582053175 .


build: upgrade azure-cloud-node-manager versions

Signed-off-by: Zhecheng Li<EMAIL_ADDRESS>

Can you update the version to 1.23.5? It contains an important fix for AAD Pod Identity.
https://github.com/kubernetes-sigs/cloud-provider-azure/pull/1205
https://github.com/kubernetes-sigs/cloud-provider-azure/issues/1155
https://github.com/Azure/aad-pod-identity/issues/1246

/retest

@feiskyer @zhiweiv I have updated the code. PTAL
Keep for RP:
0.6.0
0.7.12
1.0.9
1.1.5
1.23.2

Latest:
0.7.15
1.0.12
1.1.8
1.23.5

Check validate-image-version fails because the site is unstable right now.
http://mcr.microsoft.com/v2/oss/kubernetes/azure-cloud-node-manager/tags/list


-maxVAFValid?

Hi,
I don't really understand why you put this option. Why are you filtering SSNVs where at least one sample has a VAF>0.6? I cannot find any explanations in the paper and I also looked at the supplementary about the datasets and you didn't put anything about filtering VAF>0.6. Maybe I missed it?
Thank you,
Laurence

The VAF of the root node (max expected VAF) is set to 0.5 in the network, since a VAF of 0.5 implies that the SSNV is present in 100% of the cells, with the assumption that the SSNVs are heterozygous. Of course many sources of error are possible (in addition to the effects of LOH, CNVs etc) and as a result mutations can have higher VAFs. The user can control what VAFs should be tolerated. Switching to CP values (if available) will mediate many such issues. The default of 0.6 comes from the default error margin of 0.1 (added on top of the 0.5).

Ok thank you, I think it would remove too much in my case. I estimated the purity of my sample using ABSOLUTE so I think I will use this value+0.1 for the maxVAFvalid.
Thank you so much for you answers, it's helping a lot!


Typescript warnings when defining params and using context

Hello,
Looks like one of the recent releases brought issues when using params in the route that are passed to a handler function:

Taking a closer look at what typescript is complaining about:
Argument of type '{ body: unknown; query: Record<string, string | null>; params: Record<"base" | "term", string>; headers: Record<string, string | null>; cookie: Record<string, Cookie<any>>; set: { ...; }; path: string; request: Request; store: {}; }' is not assignable to parameter of type '{ body: unknown; query: Record<string, string | null>; params: never; headers: Record<string, string | null>; cookie: Record<string, Cookie<any>>; set: { ...; }; path: string; request: Request; store: {}; }'.
  Types of property 'params' are incompatible.
    **Type 'Record<"base" | "term", string>' is not assignable to type 'never'.ts(2345)**

Basically, the type for the params defined for that route (Record<"base" | "term", string>) are not compatible to never, which is the type defined in Context.
@SaltyAom , curiously, if I remove the params from the route, the TS error disappears:

Dep versions:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
The getSearch handler function is defined as:
export const getSearch = async (context: Context) => {
  console.log(context.query);
  console.log(context.params);

  return "Search handler returned";
};

Thank you!

Have something similar.
Same case, I've contracted out the handler but the return type and arguments types aren't working if I assign them Handler or Context.
The context becomes incompatible if I specify the type with parameters or try to de-structure the context to get params or body.

I've contracted out the handler

That does look cleaner ;)

This continues to be an issue. I've tried separating the handler from the route and keeping it included, as seen here:

This is a major blocker to using Elysia at the moment.

Closing as unable to reproduce in previous subsequent version of Elysia.
Either this was fixed or I'm unable to reproduce on my end.
As for passing context, it's recommended to handle Context type as document in MVC pattern


How to download

Hey, I want to get this, But How do I download it. I want to start hosting cpanel hosting.

Hi @Neutrideo,
currently, there is no downloadable available.
We're currently working on a stable and working version (Have a look at our development branch).
You can get and install that version (But please not that it's not stable):
git clone https://github.com/CircleBilling/CircleBilling --branch develop
Then change to the main directory and run:
composer install
Maybe you need to install composer first:

apt install composer,
yum install composer,
yast install composer

After that you can install CircleBilling with the web installer.
Maybe you can use php7.2 and please report any issue, you can find. We're very active in development and would be happy to get some feedback!
Thank you!

Thank you, But I am currently on shared reseller hosting

@Neutrideo then you can install php7 and composer on your PC, checkout the git and install the dependencies locally. Then simply upload the files via ftp. I think that should work.
Otherwise you can use our vagrant vm:

Clone git
Run vagrant up
Connect via ssh to vagrant vm (vagrant ssh)
"apt install composer"
goto "/var/www/circlebilling.local" and run "composer install"

Because of the synced folder, you should be able to uplode the files via FTP.
A other option is, that you wait about 1 week. I hope we can release our first version then.

Don't use the support tickets for that, thanks!

Any news about stable?


Node _t1_conform0 failed to run

_t1_conform0 and _t1_conform1 throw errors that don't seem to be fatal. qsiprep continues, running eddy.
The offending assert checks orig_img.affine.dot(transform) is np.allcose to  target_affine.
For those two we have the matrices:
(array([[   1.        ,    0.        ,    0.        ,  -87.5       ],
       [   0.        ,   -1.        ,    0.        ,<PHONE_NUMBER> ],
       [   0.        ,    0.        ,    1.        , -156.40016174],
       [   0.        ,    0.        ,    0.        ,    1.        ]]), array([[  -1.        ,    0.        ,    0.        ,   87.5       ],
       [   0.        ,   -1.        ,    0.        ,<PHONE_NUMBER> ],
       [   0.        ,    0.        ,    1.        , -156.40016174],
       [   0.        ,    0.        ,    0.        ,    1.        ]]))

(array([[   1.        ,    0.        ,    0.        ,  -85.32082367],
       [   0.        ,   -1.        ,    0.        ,<PHONE_NUMBER>3],
       [   0.        ,    0.        ,    1.        , -125.54721069],
       [   0.        ,    0.        ,    0.        ,    1.        ]]), array([[  -1.        ,    0.        ,    0.        ,   89.67917633],
       [   0.        ,   -1.        ,    0.        ,<PHONE_NUMBER>3],
       [   0.        ,    0.        ,    1.        , -125.54721069],
       [   0.        ,    0.        ,    0.        ,    1.        ]]))

But I'm not sure what these are, how bad it is they are not close, or how we'd better align them.
 out/qsiprep/sub-11550/log/20191024-201223_a65f2775-c6ef-4ed5-8de5-6a0e4df8ef53/crash-20191024-201310-root-_t1_conform0-3ad0eb2e-6400-45cf-a238-baad0d2048b3.txt

Node: _t1_conform0
Working directory: /work/qsiprep_wf/single_subject_11550_wf/anat_preproc_wf/anat_template_wf/t1_conform/mapflow/_t1_conform0
Node inputs:
in_file = /data/sub-11550/ses-20160617/anat/sub-11550_ses-20160617_acq-1ADNIG2_run-2_T1w.nii.gz
target_shape = (176, 240, 256)
target_zooms = (1.0, 1.0, 1.0)
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/multiproc.py", line 69, in run_node
result['result'] = node.run(updatehash=updatehash)
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 473, in run
result = self._run_interface(execute=True)
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 557, in _run_interface
return self._run_command(execute)
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 637, in _run_command
result = self._interface.run(cwd=outdir)
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 375, in run
runtime = self._run_interface(runtime)
File "/usr/local/miniconda/lib/python3.7/site-packages/qsiprep/interfaces/images.py", line 330, in _run_interface
assert np.allclose(orig_img.affine.dot(transform), target_affine)
AssertionError

The command
docker run --rm -it \
   -v $FREESURFER_HOME:$FREESURFER_HOME:ro \
   -v /Volumes:/Volumes:ro \
   -v /Volumes/Hera/Projects/mMR_PETDA/qsi/BIDS:/data:ro \
   -v /Volumes/Hera/Projects/mMR_PETDA/qsi/out:/out \
   -v /Volumes/Hera/Projects/mMR_PETDA/qsi/work:/work \
   pennbbl/qsiprep:0.6.1 \
     --bids-dir /data --output-dir /out -w /work \
     --analysis-level participant \
     --fs-license-file  $FREESURFER_HOME/license.txt \
     --output-resolution 2.3

mentions the error like

191024-20:12:57,848 nipype.workflow INFO:
[Node] Finished "qsiprep_wf.single_subject_11550_wf.bidssrc".
191024-20:13:00,990 nipype.workflow INFO:
[Node] Setting-up "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_template_wf.t1_template_dimensions" in "/work/qsiprep_wf/single_subject_11550_wf/anat_preproc_wf/anat_template_wf/t1_template_dimensions".
191024-20:13:00,991 nipype.workflow INFO:
[Node] Outdated cache found for "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_template_wf.t1_template_dimensions".
191024-20:13:01,220 nipype.workflow INFO:
[Node] Running "t1_template_dimensions" ("qsiprep.niworkflows.interfaces.images.TemplateDimensions")
191024-20:13:01,829 nipype.workflow INFO:
[Node] Finished "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_template_wf.t1_template_dimensions".
191024-20:13:04,672 nipype.workflow INFO:
[Node] Setting-up "_t1_conform0" in "/work/qsiprep_wf/single_subject_11605_wf/anat_preproc_wf/anat_template_wf/t1_conform/mapflow/_t1_conform0".
191024-20:13:04,687 nipype.workflow INFO:
[Node] Setting-up "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_derivatives_wf.t1_name" in "/work/qsiprep_wf/single_subject_11550_wf/anat_preproc_wf/anat_derivatives_wf/t1_name".
191024-20:13:04,687 nipype.workflow INFO:
[Node] Outdated cache found for "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_derivatives_wf.t1_name".
191024-20:13:06,60 nipype.workflow INFO:
[Node] Running "_t1_conform0" ("qsiprep.interfaces.images.Conform")
191024-20:13:06,81 nipype.workflow INFO:
[Node] Running "t1_name" ("nipype.interfaces.utility.wrappers.Function")
191024-20:13:06,214 nipype.workflow INFO:
[Node] Finished "qsiprep_wf.single_subject_11550_wf.anat_preproc_wf.anat_derivatives_wf.t1_name".
191024-20:13:07,151 nipype.workflow WARNING:
[Node] Error on "_t1_conform0" (/work/qsiprep_wf/single_subject_11605_wf/anat_preproc_wf/anat_template_wf/t1_conform/mapflow/_t1_conform0)
191024-20:13:08,354 nipype.workflow ERROR:
Node _t1_conform0 failed to run on host b817b64e3492.
191024-20:13:08,359 nipype.workflow ERROR:
Saving crash info to /out/qsiprep/sub-11605/log/20191024-201223_a65f2775-c6ef-4ed5-8de5-6a0e4df8ef53/crash-20191024-201308-root-_t1_conform0-a47a2103-a57f-4c98-88f0-6bfd0e65d8b2.txt

There was also a bug like this in fmriprep that I believe they solved. I'll see if I can find it and fix here too. This isn't a critical problem with your data, though.

Do you know if the T1s you're processing have the same number of voxels in each dimension?

Thanks for the quick reply!
The T1 matrix shape is 176	240	256 (of 1mm^3 voxels)
Here's a session folder (anat, dwi, fm -- but without intendedFor json) for one throwing errors
https://pitt.box.com/s/zmz0x0hlsd6fur1l40qu9cdpmgymmkir

Thanks! Downloaded and debugging now.

I got this working and there will be a patch later tonight. This is a DSI dataset, so you definitely don't want to be using eddy for motion correction. I'd recommend using --hmc-model 3dSHORE. The bvals also look like they're incorrectly scaled in 2 directions:

Is this expected?

No conform errors! But breaking out of docker put focus on outdated packages (namely ANTs), so I haven't yet run a full pass.
I don't know much (anything) about what the bvecs should look like! Thank you for drawing attention to it!
They were likely generated with a 2016 version of dcm2niix. using v1.0.20190410 they're are now half as many significant digits. Though it doesn't seem like that was the problem.

The digits in the bvecs shouldn't matter here, it would be the bvals that are off in the L/R direction. Can you confirm with the MR operator that these are correct? If so you won't be able to do traditional DSI reconstruction on it. Closing this issue since the main problem is fixed (closed by #46)