YAML pipeline - Cannot select '*' to link all work items to all branches

If you use the 'Automatically link work items included in this run' option for a YAML pipeline, once you have selected any particular branch you cannot revert to linking to all branches. The drop down control only opens a filter option and if you put '*' in there nothing shows up to select.
There is no way to clear your selections either. If you try to unselect 'Automatically link work items included in this run', save and then re-open settings, when you tick 'Automatically link work items included in this run' again the filter is pre-populated with your previous branch selection and not the '*' 'default'.
There is no way to specify '*' as mentioned in the documentation if you have ever selected a more specific branch.

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

ID: 521b594c-dbb9-54d5-f56f-00e2f5fa1d92
Version Independent ID: 509d3e4e-23db-8493-e1a6-acb67ec47e81
Content: Customize your pipeline - Azure Pipelines
Content Source: docs/pipelines/customize-pipeline.md
Product: devops
Technology: devops-cicd
GitHub Login: @vijayma
Microsoft Alias: vijayma

@mbeets - Thanks for your question. While we look into it, consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow

I would like to add that it appears even when you attempt to enable this feature for the first time the "*" is not defaulted or available. In the pic below I cut off the bottom of the window, but I am not able to click "Save" if I just tick the enable checkbox as shown below. Thanks!


[DevOps] Snyk Integration

Scan results can be found here.
requirements.txt is scanned for vulnerabilities & license issues.
Following requirements are removed from scan.
https://github.com/h2oai/h2ogpt/blob/2ccf687ea3f3f3775a501838e81c1a0066430455/requirements.txt#L42-L51

Parent Issue: https://github.com/h2oai/h2o-ops/issues/323

How do I evaluate the goodness of this PR? Does it hook-up to our internal devops scans? Can those be made public with some link in the readme?

If there are any issues with PR the checks will fail. You can check the logs for GitHub action workflows. Those are publicly available.

You can check the logs for GitHub action workflows. Those are publicly available.

They are not afaik. The logs can (and do, I believe) contain secret tokens printed to stdout. It makes sense to keep those logs private to the repo maintainers.

You can check the logs for GitHub action workflows. Those are publicly available.

They are not afaik. The logs can (and do, I believe) contain secret tokens printed to stdout. It makes sense to keep those logs private to the repo maintainers.

sure


emacsPackages.lspce: 1.1.0-unstable-2024-07-14 -> 1.1.0-unstable-2024-07-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for emacsPackages.lspce is: LSP Client for Emacs implemented as a module using Rust
meta.homepage for emacsPackages.lspce is: https://github.com/zbelial/lspce
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.0-unstable-2024-07-29 with grep in /nix/store/zbw94ppxl22ycb3f8c49xcgf46cxlgdd-emacs-lspce-1.1.0-unstable-2024-07-29
found 1.1.0-unstable-2024-07-29 in filename of file in /nix/store/zbw94ppxl22ycb3f8c49xcgf46cxlgdd-emacs-lspce-1.1.0-unstable-2024-07-29

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

emacsPackages.lspce

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zbw94ppxl22ycb3f8c49xcgf46cxlgdd-emacs-lspce-1.1.0-unstable-2024-07-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A emacsPackages.lspce https://github.com/r-ryantm/nixpkgs/archive/ebbc481ff5664533e7f0a6e9ef58851a1d2a4891.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ebbc481ff5664533e7f0a6e9ef58851a1d2a4891#emacsPackages.lspce

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zbw94ppxl22ycb3f8c49xcgf46cxlgdd-emacs-lspce-1.1.0-unstable-2024-07-29
ls -la /nix/store/zbw94ppxl22ycb3f8c49xcgf46cxlgdd-emacs-lspce-1.1.0-unstable-2024-07-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

emacsPackages.lspce

Maintainer pings
cc @AndersonTorres for testing.

Lemme rework it a bit


⚠ Bofrost.de has degraded performance

In eb46547, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1093 ms

Resolved: Bofrost.de performance has improved in 14da728.


Fix new index.html path for deluge

Theme was broken, now it is fixed :)

[x] I have read the contributing guideline and understand that I have made the correct modifications

Description:
Path to index.html file must have changed recently in the linuxserver.io deluge container, so the theme would never be applied. This fixes the path so the theme works again.
Benefits of this PR and context:
Otherwise, deluge theme will not work
How Has This Been Tested?
Made the change locally in my container and restarted. It worked
Source / References:

Thanks!


build(all): update dep version and use aliyun mirrors

Not all developers or users who want to build themselves are in China, so do not just replace maven central to the mirror of Alibaba.
Maven central should always be first, the mirrors are not always in sync with upstream.
So I think it should be a local property instead of the general solution.

And there are several unsafe dependencies upgrades, so we need to test and adapt for API changes. I recommend you read SemVer 2.0 to learn about best practices for dependency control.
Based on the reasons above, I'll close this PR as refuse.


usage for pin

Lovely work you gave to the community..
Though i haven't installed the keyboard, and the reason was because i am not sure if this can be used as a pin entry.
I am currently developing an ionic 4 app, and i was hoping i could use this numeric keyboard to achieve pin entry such that, number pad is displayed and the characters would be in password type.
I would like to confirm if this is possible this piece.
Thanks in adv.

Sorry cannot catch your point. Do you mean the effect of password panel?  I update the snapshot to gif in README. Check the demo code if it is the right effect.

Yeah, the gif reflects my questions.
How would i achieve the pin effect?

Yeah, the gif reflects my questions.
How would i achieve the pin effect?

Code for gif is in demo directory


Breaks in the table rows in Tab2

These breaks should be fixed.

I observed that this is fixed. Just make sure this is not by accident.

This is the issue with recent version of the code on the website.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit e2d71ff:
:clock10: Pending: waiting for processors (26 builds ahead of you)
:warning: Docs Build is busy, currently there are 26 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit e2d71ff:
:clock10: Full build: the average full build time is 12 min(s) 33 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit e2d71ff:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[FEATURE REQUEST] Supports for trace block indexing

In essence, I want to be able to have a block listener handler that uses debug_traceBlockByNumber or something else so I can track in / outs of balances. I'm happy to help sponsor the work.
For reference, this implements this and account listeners: https://github.com/ponder-sh/ponder/pull/1210/files
I woulndt go that far, as long as it indexes blocks using debug_traceBlockByNumber and send it to a handler, on the handler a logic to track in / out of ETH native balance changes in the block can be written
The reasoning is that would allow rindexer to fully index tokens and native transfers, a feature it is lacking at the moment.

This is a great idea something I would love to add alongside as if executed well you can in turn track tons of stuff this way. I also want to add factory contract monitoring.
The first thing I would like to define here is the rindexer.yaml and how it would look this allows us to see how people will set it up! Is your pure usecase just doing native transactions or have you other thoughts? Asking as I can imagine this being useful for address filtering, gas based filtering, internal transactions, contract creations, state variable updates and well tons more but I defo don’t to add the most important things first.
The core thing rindexer does well is do everything for you so do want to make sure we get the interface spot on. In your case thought you want to write the handler yourself using the rindexer rust project right?


python312Packages.pgpy: fix build

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-reviewd workflow started
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12493805060

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12493805060
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-darwin

:x: 2 packages failed to build:

python313Packages.pgpy
python313Packages.pgpy.dist

:white_check_mark: 2 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

aarch64-darwin

:x: 2 packages failed to build:

python313Packages.pgpy
python313Packages.pgpy.dist

:white_check_mark: 2 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-linux

:x: 2 packages failed to build:

python313Packages.pgpy
python313Packages.pgpy.dist

:white_check_mark: 2 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist

nixpkgs-reviewd workflow started
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12499805297

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12499805297
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-darwin

:white_check_mark: 8 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python312Packages.standard-imghdr
python312Packages.standard-imghdr.dist
python313Packages.pgpy
python313Packages.pgpy.dist
python313Packages.standard-imghdr
python313Packages.standard-imghdr.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

aarch64-darwin

:white_check_mark: 8 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python312Packages.standard-imghdr
python312Packages.standard-imghdr.dist
python313Packages.pgpy
python313Packages.pgpy.dist
python313Packages.standard-imghdr
python313Packages.standard-imghdr.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-linux

:white_check_mark: 8 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python312Packages.standard-imghdr
python312Packages.standard-imghdr.dist
python313Packages.pgpy
python313Packages.pgpy.dist
python313Packages.standard-imghdr
python313Packages.standard-imghdr.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/5009

nixpkgs-reviewd workflow started
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12514460061
Extra args: ``

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/Bot-wxt1221/nixpkgs-reviewd/actions/runs/12514460061
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-darwin

:white_check_mark: 4 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python313Packages.pgpy
python313Packages.pgpy.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

aarch64-darwin

:white_check_mark: 4 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python313Packages.pgpy
python313Packages.pgpy.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368110

x86_64-linux

:white_check_mark: 4 packages built:

python312Packages.pgpy
python312Packages.pgpy.dist
python313Packages.pgpy
python313Packages.pgpy.dist

@kirillrdy Done.


It's easyer to get an Response instead of an StreamedResponse

Hey could you change the response type from StreamedResponse to Response. It is much easyer to work with.

Review the latest update and respond here: New Comment
This is critical—take action now.
Stay secure!


Retrieve tensor values

I have a pre-trained model which I want to use to calculate the value of a middle layer. The question is how I can get the value of the tensors (middle features). What function should I look into? How can I pass the value back outside the wrapped functions?
Thanks very much!

See this http://tensorpack.readthedocs.io/en/latest/modules/callbacks.html#tensorpack.callbacks.ProcessTensors


STORE LENGTH OF vector

In action:
DATA:
count IS NUMBER
names IS TEXT VECTOR
ages IS NUMBER VECTOR

PROCEDURE:
STORE 81 IN ages:0
STORE 75 IN ages:1
STORE 102 IN ages:2

STORE "Marilyn" IN names:0
STORE "Dillsworth" IN names:1
STORE "Rogert" IN names:2
STORE "Pepperberry" IN names:3

STORE LENGTH OF ages IN count
DISPLAY count " ages"
DISPLAY " & "
STORE LENGTH OF names IN count
DISPLAY count " names" CRLF

Woah, neat! Thank you very much for your contribution! Much appreciated!

Hello! We've found a problem with STORE LENGTH OF. The thing is, when you look at a vector position and the value has not been initialized, it is initialized implicitly so the length of the vector grows by one. This, obviously, is very counter-intuitive and the solution to that issue is something that escapes this compiler, so I have two possible solutions:
One would be "COUNT INITIALIZED POSITIONS OF", that's just a rename of this funcion.
I'd rather just remove it for now. It's quite counter-intuitive and that goes against the philosophy of the language 😔
I'm sorry for not having realized this before.

Ahh whoops! I didn't realize that.
Is your plan to keep that behavior for vectors?  Because I'd think you could change the [] operators to return a default value if the key doesn't exist in the vector, if you wanted.

I can look into that, but I believe it's not that easy for you cannot forsee on which side of the assignment operator the map will be.

I see! I have been poking around and see what you mean, right now it's nice how flexible get_c_variable is in the compiler. You'd maybe have to check for the vector type and do an insert/push or something special in all the STORE code.
I am :+1: on removing this until there's a less confusing solution :+1:

Great, thank you! I'll check the code later and see what I can do, but checking the length of an LDPL VECTOR was not something I ever had in mind. Given that they aren't lineal, a size parameter may not be as expressive or useful as in other languages. Awk took the same decision. I'd rather keep and update a myvector.length variable, separately.
Thank you very much!

:+1: makes sense, I like this way of thinking, yes! I was originally reaching for STORE LENGTH OF vector to iterate over a list (and because the syntax was no addition) but I can track all that separately.

Yay! That's the idea. In AWK you can't get the length of a vector and you end up using tracking variables. It's not the most comfortable thing in the world, but I find it to be consistent with the data structures used.


[plugin] add option to compile with the Static Linux SDK instead of docker

Expected behavior
Now that the Static Linux SDK has been released, it open the doors to cross-platform compilation from Mac that doesn't require Docker or depend on Amazon Linux.
The binaries created with the Static Linux SDK work "as is" on AWS Lambda.
I propose to add an option to the Archiver plugin to compile the binary with the Static Linux SDK instead of Docker.
When this option is enabled (it might become the default at some stage):

the plugin would check if the Linux Static SDK is installed, and install the correct version automatically when it's not installed.
the plugin will check the current platform architecture (or a command line flag to force a specific architecture)
the plugin will then compile the Lambda functions with swift build -c release --swift-sdk aarch64-swift-linux-musl (or x64_86)
the plugin will create a bootstrap sym link to the executable and package the sym link and the executable in a ZIP file

However, some pre-requisites are necessary before to release this enhancement

Swift 6 must be generally available. At the moment, installing the toolchain requires manual steps that we don't want to include in the archive plugin code
The Swift runtime for AWS Lambda must compile with musl (see #331)
The segmentation fault problem must be fixed, to avoid further ceremony to get the toolchain working.

Actual behavior
The archiver plugin requires Docker and an Amazon Linux 2 image with the Swift toolchain installed
Steps to reproduce
n/a
If possible, minimal yet complete reproducer code (or URL to code)
Here is the script I use to test this on macOS Sonoma
export TOOLCHAINS=org.swift.600202406131a
PATH_TO_TOOLCHAIN=/Library/Developer/Toolchains/swift-6.0-DEVELOPMENT-SNAPSHOT-2024-06-13-a.xctoolchain

LAMBDA_USE_LOCAL_DEPS=true DYLD_LIBRARY_PATH=$PATH_TO_TOOLCHAIN/usr/lib/swift/macosx $PATH_TO_TOOLCHAIN/usr/bin/swift build -c release --swift-sdk aarch64-swift-linux-musl

pushd .build/aarch64-swift-linux-musl/release
cp UrlLambda bootstrap
zip UrlLambda.zip bootstrap
cp SQSLambda bootstrap
zip SQSLambda.zip bootstrap
cp HttpApiLambda bootstrap
zip HttpApiLambda.zip bootstrap
rm bootstrap
popd

What version of this project (swift-aws-lambda-runtime) are you using?
1.0.0-alpha1
Swift version
 ✗ swift --version && uname -a
Apple Swift version 6.0-dev (LLVM 6e13b8be259f20f, Swift 372de4670b9cd55)
Target: arm64-apple-macosx14.0
Darwin bcd07458a91c 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 arm64

Amazon Linux 2 docker image version
No response

Discussion thread on the Swift forums : https://forums.swift.org/t/aws-lambda-functions-and-the-linux-static-sdk-works/72604

Are we aware that this will increase code size significantly?

I am. I want to first measure the impact on code size and cold startup time. I want to share result with the community and - if it makes sense - propose it as an optional flag.
Unfortunately, I don't expect having time to work on this this year


Move the sklearn maintainer model notebook to katalog

fix #58

@Tomcli -- I can take care of (2) since it will require a separate PR. Number (3) could be done in this PR or in a follow up.


Mention "enabling the realtime feature on each table" in docs for liveQuery feature

It is a very small thing, but it would be great if the docs mention in the live query section to enable realtime for the table on Mission Control. Websockets do not listen to changes in DB if the realtime option isn't enabled.

Done. Will be published along with the v0.17.0 release. Thanks for bringing this up! @AmeyaDaddikar


[$500] [Form Provider Refactor] AddressPage

Coming from https://github.com/Expensify/App/issues/25397#issuecomment-1743272245, we created a new Form provider that works with functional components and we need to refactor all usages of the old Form component.
This issue is specific to refactoring src/pages/settings/Profile/PersonalDetails/AddressPage.js
cc @kowczarz
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012aba0c7431d96aff
Upwork Job ID:<PHONE_NUMBER>695823360
Last Price Increase: 2023-10-05

Issue OwnerCurrent Issue Owner: @kowczarz

Hello! I'm Kamil Owczarz from Software Mansion, the expert agency and I would like to work on this task.

@kowczarz -- any update on the proposal for this GitHub?

Similar to the hook refactor, I don't think we need a proposal for this one since the refactors are straightforward and follow the same pattern. @kowczarz authored the original refactor PR, so I think they are best suited to work on this as well :)

Thanks @luacmartins, sounds like a plan!

Update: Waiting for the PR to fix this issue

We're still working on other forms. Will get to this one soon!

Still working on other forms.

As soon as https://github.com/Expensify/App/pull/29983 will be merged I will start working on this issue.

Perfect, thanks @kowczarz for the update!

Daily Update: It looks like the PR mentioned above has some feedback that needs review.

Daily update: The PR is moving forward now.

Holding PR is merged. We're good to work on this

@kowczarz - all set, the blocker should be clear now. Thanks for reviewing again.

@luacmartins should we make this external again? Thanks for the update!

@luacmartins bumping again, should we make this external?

It seems to be external already and we got SWM working on it

@kowczarz is still working on related issues

Thank you @kowczarz for the update!

Daily Update: PR is moving forward!

Catching up from being OOO, it looks like the PR was reverted due to deploy concerns. @cdOut and @kowczarz - can you please share the next steps here and how we can keep moving forward? Thanks!

@cdOut and @kowczarz - any update here?

There was a little bit of confusion due to multiple pages being named similarly. This issue will be done alongside this one, since they both address the same component, AddressForm: https://github.com/Expensify/App/issues/32064. After that one is merged, this one will also be refactored.

Thank you @cdOut for the update!

Daily Update: The PR is in draft mode.

Daily Update: The PR is ready for review!

Ok, now we will need to wait for automation here.

@luacmartins and @thesahindia it looks like automation didn't kick in here. Is this one complete? If yes, I'll need to start the manual payment process. Thanks!

It is merged and completed.

Here is the payment summary:

External issue reporter - N/A
Contributor that fixed the issue - @cdOut Software Mansion
Contributor+ that helped on the issue and/or PR - @thesahindia $500

Upwork Job: N/A

Heads up, I will be offline from Friday, December 22, to Thursday, January 4, 2024. I will not be actively watching over this GitHub during that period. If anything urgent is needed here, please ask for help in the #expensify-open-source Slack Room-- thanks!

No update, waiting for confirmation that @thesahindia has submitted a payment request in Chat.

@thesahindia can you please confirm if you submitted a payment request? After, I can close this GH - thanks!

Awesome, thank you for the update!

$500 payment approved for @thesahindia based on this comment.


Custom events

In progress, but haven't decided on syntax yet

Almost done, will push soon probably

Committed in https://github.com/TPGamesNL/skript-mirror/commit/ac18b44cc25ea81eb5347af328065602f4d59261, but will probably have some bugs, so feel free to test and send anything wrong with it here.
Download: https://github.com/TPGamesNL/skript-mirror/actions (currently, the latest is https://github.com/TPGamesNL/skript-mirror/actions/runs/127750321)
Example (actual documentation coming soon, hopefully):
command /call:
	trigger:
		set {_ev::player} to player
		# effect for calling custom events, the given list variable has entries in the form {list::%type%} = %value%
		# the with {_ev::*} part can be left out, but it won't have any event-values of course
		# the name (hack_evt) is defined in the custom event
		call custom event "hack_evt" with {_ev::*}

# patterns work like rest of skript-mirror, multiple can be defined with a patterns: section
# patterns can also contain literals (for example, on hack %-string%, use expr-1 to get the value for %-string%)
custom event hack:
	name: hack_evt
	event-values: player # optional
	parse: # optional
		# code
		continue
	check: # optional
		# code
		event.getEventValue("player") is set # let me know I should also make this one a normal event-value (so just event-player / player)
		continue

on hack:
	message "Don't do that!"
	send "%player% hacks" to console

Please let me know any suggestions here (or somewhere else, I don't really care tbh)
Also let me know what things should be given priority.
For custom events, some things I still want to do include:
make them work async
add better support for extra data (it's already here, but not rly document, look at the source code for now)

Todo for custom events:

Make calling work async
Better support for custom data
Event-values in check section

Todo for custom events:

Make calling work async
Better support for custom data
Event-values in check section

These are now done, let me know if you want anything else

Closing at it's done, feel free to open a new issue / comment here if you have a bug / suggestion for custom events


Lambda create

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days


Incorrect IBAN Info?

[Hi please can you check the published IBAN and confirm if this is correct?
IBAN: GB31CITI18500812510049  is stated here but we believe that it is meant to be GB95CITI18500812510049 - please can you verify this as soon as possible?
]

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

ID: afea22ca-c974-f0ef-07f1-4a44a390c058
Version Independent ID: a1f02905-3ac6-be64-a400-23287f7e2879
Content: Payment information for Saudi Arabia
Content Source: microsoft-365/commerce/pay/saudi-arabia.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@SDkempf94, please download your invoice from the Microsoft 365 admin center, and check the payment instructions shown on the PDF.

It says GB95CITI18500812510049 and it seems to be the same for other Saudi Arabia tenants too - if this is the case, will you update this public facing documentation?


No botocore required

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This change is

thank you for your contribution!


Using openapi-typescript-codegen to generate TypeScript types from our APIs

###Description of the Tech Debt###
I believe this package could be a valuable addition for us. This tool allows us to automatically generate TypeScript types from our APIs, saving us the effort of creating them manually. You can check out a practical example of its usage in this commit:
https://github.com/bcgov/cas-registration/pull/180/commits/d4cf8e83f778b290a504063f032fcf1fac428fa3
###Tech Debt Triage#
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring:

Level
Value

High
3

Medium
2

Low
1

Technical Debt - Risk Types
Level
Value

Business Area Risk - Risk of business area visibility / damage to user experience

Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it

System Fault Risk - Risk of system errors or application downtime

Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?

Time Sink Risk - How much will this tech debt slow the development process down

TOTAL SCORE:

The package is no longer being maintained and has been replaced with this one: https://heyapi.vercel.app/openapi-ts/get-started.html


feedback: Make it easier to add a section of the code to the open chat

Version
Version: 1.88.1
Areas for Improvement

[X] UI/UX
[ ] Onboarding
[ ] Docs
[X] Chat
[ ] Commands
[ ] Context
[ ] Response Quality
[ ] Other

What needs to be improved? Please describe how this affects the user experience and include a screenshot.
It would be nice to have a straightforward way to add current selected code to the chat without needing to do @fileName:5-10. For people that use relative line numbers for example, it's a chore
Describe the solution you'd like to see
It'd be nice if the current selection can be automatically referenced in the open chat instead of needing a new chat on its own
Describe any alternatives that could be considered
No response
Additional context
No response

@abeatrix Can we close this now? With your work to include the selection by default

pardon, does this mean that now, in an already opened chat, the current selection is automatically added as context? I didn't try this again so if you addressed it then yes of course we can close it

@mcheviron Thank you so much for the feedback!

In today's Cody for VS Code release, there is a new feature that allows you to add code from your editor to open chat with the right-click menu: https://github.com/sourcegraph/cody/pull/3713

We also have an existing feature where your current selection will be included automatically when you submit the question when enhanced context is enabled (the button next to your chat input box).
There is also an experimental feature that allows you to start a new chat or add current selection to chat on hover!

I hope this helps!
(@umpox thanks for the ping!)


What's the best way to deal with variable episode length?

A solution provided in Acme pads all episodes to the maximum episode length, but I'm afraid that this will drastically reduce the performance if the episode length has a high variance. For example, if the maximum episode length is 300, while most episodes end at 15 steps, this could be a 20 folds decrease in data throughout. For my tasks, it's ok to always have a batch size of one (sampling one episode at a time), would this change the requirement of all items must have the same shape?
What are the best ways to deal with this situation?
Here are some ideas that came to my mind but I'm not sure if they can solve the problem:

create multiple tables corresponds to various padding length, and insert to different tables based the actual episode lengths
used delta-encoding

Related: #19  #47

You can create one table which contains variable lengths.  Both the old Writer/Sampler and the new Trajectory Writer/Sampler allow it (if you provide a signature to the dataset, simply set the outer/time dimension to None in Python).
But now you additionally have the problem of batching and training from a stream of variable episode lengths.
You have roughly 3 options from a tf.data perspective:

padded-batch (what you're using)
bucket-by-sequence-length (what you're suggesting except move the bucketing into tf.data streams and out of tables; but using multiple tables works too!)
chunk-and-shuffle (chop all episodes into fixed sized pieces and shuffle those, not bothering to train on full eps)

Chunk-and-shuffle often works well in dense reward scenarios.  Here's an example:
  stream = dataset.unbatch()
  # Since we're generally reading from a never-ending replay buffer, we
  # can drop remainder here and get the benefit of usually having known
  # episode lengths and batch sizes.
  chunks = stream.batch(chunk_size, drop_remainder=True)
  # reshuffle_each_iteration will probably never be used since replay
  # buffers are based on never-ending datasets, but we add it just in case.
  shuffled = chunks.shuffle(
      shuffle_buffer_size, reshuffle_each_iteration=True, seed=seed)
  batched = shuffled.batch(batch_size, drop_remainder=True)
  return batched

The bucket-by-sequence-length approach can be combined with padding-up-to-fixed-lengths-per-bucket (allowing fixed shaped graphs, which is useful if you're training with TPUs).  The tf.data function that helps you do this is bucket_by_sequence_length.
In all cases, you can accelerate by creating multiple reverb datasets (flexible_batch_size=1 in each) and using tf.data's interleave (ACME's reverb dataset code does this).


Simplified "Create Issue" Flow

Description
This PR simplifies the issue creation flow when interacting with the <ContributingGuidelines /> component. Rather than sending the user to a page to choose what issue type, they are placed on the new issue page with some fields filled out.
Reviewer Notes
Example Link
This includes some refactoring of the <SimpleFeedback /> component by abstracting the link-creation logic to a helper file (tests = easy refactoring).
Related Issues

Closes #170

qq: Should the GlobalFooter also have this behavior?

Oh good point, I totally forgot we had buttons down there too!

Awesome! I'd be happy to do a full review after thats in place 😄

@jerelmiller added it to <GlobalFooter /> thanks for catching that!

@zstix nice! I noticed this isn't in place yet, but I assume each site property will need to update to the newest theme version to use this change?

@jpvajda Yeah, we'll need to publish the theme (if it hasn't already been) and then bump the theme for each site that uses it. I can do that today.

@zstix ok I had a few questions on the workflow, so I'll send you a slack message


[stdlib] BidirectionalCollection cleanup

Do not restate Collection requirements

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - bec81c99d389c249631227cab3c2934b12266283
Test requested by - @dabrahams

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - bec81c99d389c249631227cab3c2934b12266283
Test requested by - @dabrahams

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - bec81c99d389c249631227cab3c2934b12266283
Test requested by - @dabrahams

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - bec81c99d389c249631227cab3c2934b12266283
Test requested by - @dabrahams

Not going to work until the compiler gets smarter, apparently.


Python scripts Browser(run_on_failure=..) & register_keyword_to_run_on_failure both not working

Describe the bug
Python scripts Browser(run_on_failure=..) & register_keyword_to_run_on_failure both not working
To Reproduce
test.py
from robot.api.deco import keyword
from Browser import Browser

@keyword
def test_keyword():
    lib = Browser()
    lib.new_browser()
    lib.new_page(url='http://www.google.com')
    lib.click("//img[@alt='Fake']")    <---  Expecting failure and take screenshot here

@keyword
def test_keyword2():
    lib = Browser()
    lib.register_keyword_to_run_on_failure('Take Screenshot')  <---  Expecting screenshot to be taken when failure occurs
    lib.new_browser()
    lib.new_page(url='http://www.google.com')
    lib.click("//img[@alt='Fake']")    <---  Expecting failure and take screenshot here

test.robot
*** Settings ***
Library  test.py

*** Test Cases ***
Test
    Test Keyword

Test Register Keyword On Failure
    Test Keyword2

output report
No screenshot being taken even if the register_keyword_to_run_on_failure is defined!

Expected behavior
Take screenshot on failure.
Desktop (please complete the following information):

OS: Windows 10
Browser: chrome
Version: robotframework-browser==11.1.1

Additional context
Use the same test keyword on robot level, and the screenshot is taken properly.
*** Settings ***
Library  Browser

*** Test Cases ***
Test
    New Browser
    New Page    url=http://www.google.com
    Click  //img[@alt='Fake']

output report:

Yes this is true and correct. The run on failure only works when library methods are run as keyword from Robot Framework. If methods are executed directly from Python, run on failure functionality does not work. Luckily implementing such functionality in your library should not be hard to do.
But because this is not documented anywhere, we could improve the docs.


[Bug] [Server] UT failed in LoggerServer

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
UT failed in LoggerServer LoggerServerTest.
What you expected to happen
UT success.
How to reproduce
fix the UT code.
Anything else
No response
Version
2.0.5
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have checked this issue and found the 'testRemoveTaskLog' UT method throw an exception but UT is successful on my local machine.
The method has the following functions:

Create a file '\tmp\remove.log'.
Call method 'logClientService.removeTaskLog' to delete the log.
Read the file and view the log.
The question is the 3rd step, the file has already been deleted so that throw a 'FileNotFoundException' and cause a logger print 'ERROR' log. I think this one is fine, it is reasonable and the UT result is successful.

have checked this issue and found the 'testRemoveTaskLog' UT method throw an exception but UT is successful on my local machine. The method has the following functions:

Create a file '\tmp\remove.log'.
Call method 'logClientService.removeTaskLog' to delete the log.
Read the file and view the log.
The question is the 3rd step, the file has already been deleted so that throw a 'FileNotFoundException' and cause a logger print 'ERROR' log. I think this one is fine, it is reasonable and the UT result is successful.

So, Is there a problem here? Do I need to modify it ？


Add atom node feature

It would be nice if we have atom_type as a feature (we can obtain them from the node information from the hdf5 file).

Could you copy-paste here the code you use to obtain this info? @DTRademaker
Please list here all possible values that the feature can have.

`
def extractAtoms(fileName):
return [[float(line[30:38]),
float(line[38:46]),float(line[46:54]), line[17:20], line[77], line[13:15], line[21]]
for line in open(fileName).read().replace(' OX', ' O ' ).split('\n')
if line.startswith('ATOM ') and line[77]!='H']
Extract coordinates, chainID, atom, element and aminoacid information from pdb
def raw2proc(pdbFile):
pdb 		= extractAtoms(pdbFile)
xyz 		= torch.tensor([i[:3] for i in pdb])
chain 		= [i[-1] for i in pdb]
atom  		= [i[-2].strip() for i in pdb]

element  	= [i[-3] for i in pdb]
amino_acids = [i[-4] for i in pdb]
return xyz, chain, atom, element, amino_acids
return atom

All possible values
atoms = ['OX', 'CZ', 'NE', 'SG', 'N ', 'O ', 'OH', 'CE', 'C ', 'NZ', 'OE', 'OD', 'OG', 'NH', 'CG', 'CD', 'CA', 'SD', 'CH', 'CB', 'ND']`

It would be handy to have #147 resolved first, which explains what is required for a new feature module

@gcroci2 ,
did you mean an entire module for atom graphs, including the element (atom type), atomic charge, etc? Or did you just mean a single feature for the element?

did you mean an entire module for atom graphs, including the element (atom type), atomic charge, etc? Or did you just mean a single feature for the element?

note to self:

if single feature --> use amino_acid.py
if feature module --> use atom.py

@gcroci2 ,
did you mean an entire module for atom graphs, including the element (atom type), atomic charge, etc? Or did you just mean a single feature for the element?

I mean a single feature for the element, which is the atomic type. It could be placed in deeprankcore.feature.amino_acid

@DaniBodor Additional context: right now, FEATURENAME_AMINOACID refers to the feature called type in the hdf5 file (see deeprankcore.domain.feature). It indicates the type of residue (amino acid), and it is represented with a one-hot encoding of the residue, assuming that there are 20 possible residues. Thus, this feature should be called res_type or something similar to indicate that the type refers to the residue. Then, I think we should have two different cases:

If node.id is a Residue (see deeprankcore.feature.amino_acid), then we only have res_type. It is already like this, except for the name type instead of res_type.
If node.id is an Atom, then we should have both res_type and atom_type, the latter not implemented at the moment. We could to the same thing that we do for residues, which is one-hot encoding the string that represents the type.

I checked the code and I don't think we have a module for specific atomic features right now, right? @cbaakman If this is the case, I would create a new module called like atom.py in which for now we only calculate the atomic type (so only a single feature there). We may add other features in the future.

The information for those is actually present. Basically generic features of the different elements. It is used for example to calculate some of the edge features already. So, I will create a small module to get all of these, I guess

I also still need to move the atom features into domain/feature once that branch is merged


Allow context in named templates

Fixes issue https://github.com/expath/xspec/issues/66
XSpec schema updated to allow context element in named-scenario (just as it is already allowed in matching-scenario)
generate-xspec-tests.xsl had code to deal with context in this position, but written with incorrect $context - now changed to $impl:context

Looks good to me, thank you!  Any objection on this one?  @tgraham-antenna ?

Are there any updates on this issue? @tgraham-antenna


Fix the not failing on pytest error workflow bug

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.44%. Comparing base (3d8667d) to head (bee85df).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #907   +/-   ##
=======================================
  Coverage   78.44%   78.44%
=======================================
  Files          10       10
  Lines        1786     1786
=======================================
  Hits         1401     1401
  Misses        385      385

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


SyntaxError: Unexpected end of input

Hi
I've followed the instructions, but when run the chat I've got the following error:
joe@MBP-von-Jose chatbot-ui % npm run chat

><EMAIL_ADDRESS>chat
> supabase start && npm run db-types && npm run dev

supabase start is already running.
Run supabase status to show status of local Supabase containers.

><EMAIL_ADDRESS>db-types
> supabase gen types typescript --local > supabase/types.ts

(node:1) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time

><EMAIL_ADDRESS>dev
> next dev

/Users/joe/Documents/GitHub/chatbot-ui/node_modules/array-uniq/index.js:56
		module

SyntaxError: Unexpected end of input
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1178:20)
    at Module._compile (node:internal/modules/cjs/loader:1220:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at mod.require (/Users/joe/Documents/GitHub/chatbot-ui/node_modules/next/dist/server/require-hook.js:65:28)
    at require (node:internal/modules/cjs/helpers:121:18)
    at Object.<anonymous> (/Users/joe/Documents/GitHub/chatbot-ui/node_modules/del/node_modules/array-union/index.js:2:17)

Node.js v18.17.1

MacOS Sonoma 14.3.1, MacBook Pro Intel
Thanks in advanced.

Sup, to fix such problem try to delete your node_module  and after clear cache using
 npm cache clean --force
yarn cache clean
pnpm store prune

after that install all your packages back , if it doesnt work try to install newwer version of node


175 domains and pools are global rather than per design recreating same design causes error

Hmm, looks like lots of unit tests need to be adjusted first. Converting to draft until that's done.


fix(collections): Add extra add / removal logs in case of failure

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


Half of the test suite fails because 'nats-server' process cannot be started on Mac and Windows (but works on Linux)

Observed behavior
When running 'gradle test' task, half of the tests fail with error:
SEVERE: %%% Failed to run [nats-server --config /var/folders/g0/j11s_mg529gfq10lyqnxsgl80000gn/T/nats_java_test7737451283960269566.conf -js]
SEVERE:     Cannot run program "nats-server": error=2, No such file or directory
SEVERE: %%% Make sure that the nats-server is installed and in your PATH.
SEVERE: %%% See https://github.com/nats-io/nats-server for information on installation
Expected behavior
Tests not failing.
Server and client version
Server (signed and notarized) 2.8.2 on macOS
Server (as downloaded) 2.10.21 on macOS, Windows and Linux
Client source from latest main branch (commit 27efeab5)
Host environment
macOS 13.10 (failing)
Windows 11 (failing)
PopOS 22.04 (working)
All with Java 11
Steps to reproduce

download nats-server
copy to location that is in $PATH
start nats-server once and accept all warning dialogs on Mac and Windows
start nats-server again to verify that no more interactive warning dialogs are shown
clone this repo
cd to repo folder
execute ./gradlew build and observe half the tests failing
set environment variable "nats_server_path" to point to correct location
execute ./gradlew build and observe half the tests failing again
modify source code and add line "NatsServerRunner.setPreferredServerPath("/usr/local/bin/nats");" to constructor of class NatsTestServer
execute ./gradlew build and observe the tests passing

Diagnosis: Your code fails to read environment variables on macOS and Windows.

@HenriNext I develop on Windows 11 and have no problem running the test suite multiple times daily. I also just double checked my ubuntu machine and no problem there either. I do not have access to a Mac.
It's strange that every test that requires a server doesn't fail. I set a bad nats-server_path on windows and got this:
Failed to run [\progams\bin --config C:\Users\<myuser>\AppData\Local\Temp\nats_java_test5603773406283295305.conf]

The code that runs the server is found in the jnats-server-runner project. The nats-server_path needs the entire path to the executable, not just the directory, so expects something like:
/usr/local/bin/nats/nats-server

This should not work since it does not point to an executable so I would expect all tests taht require a server to fail. (There are many that don't, for instance tests that check builders and objects. This could account for "half")
NatsServerRunner.setPreferredServerPath("/usr/local/bin/nats");

Here is excerpted code from the jnats-server-runner project:
public static final String NATS_SERVER_PATH_ENV = "nats_server_path";
public static final String DEFAULT_NATS_SERVER = "nats-server";

public static String getResolvedServerPath() {
    String serverPath = NatsServerRunner.getPreferredServerPath();
    if (serverPath == null) {
        serverPath = System.getenv(NATS_SERVER_PATH_ENV);
        if (serverPath == null) {
            serverPath = DEFAULT_NATS_SERVER;
        }
    }
    return serverPath;
}

This is my windows batch file that I use to run the tests:
taskkill /F /IM nats-server.exe

rd /S /Q C:\Users\<myuser>\AppData\Local\Temp\nats
rd /S /Q C:\Users\<myuser>\AppData\Local\Temp\jetstream

del C:\Users\<myuser>\AppData\Local\Temp\nats_java_test*.conf
del C:\Users\<myuser>\AppData\Local\Temp\nats_net_test*.conf

cd \nats\nats.java
call gradlew clean build
taskkill /F /IM nats-server.exe

Thanks for your fast response.

"half the test suite" meant exactly the (about) half that requires a nats-server, so nothing weird or non-deterministic.

I typo-ed, and the actual working solution was to call 'NatsServerRunner.setPreferredServerPath("/usr/local/bin/nats-server")', not just "/nats".

The surface problem seems to be that on macOS and Windows, the 'nats-server' was not found even when it is on PATH. So the advice from the readme section "Building from the source", and from the test suite error message when nats-server cannot be found, simply didn't work.

The underlying problem may be that when I traced the execution on macOS, the System.getenv(...) call returned null. I'm not sure of the reason, could it be related to running via Gradle? But this might break both the "nats-server from path" and the "nats-server from environment variable" cases, leaving "nats-server from preferredServerPath" as the only working option.

I run on windows with the server in my path. I have also tested using nats_server_path. Here is an interesting discussion about System.getEnv(...) failing, it has to do with the shell or the application without the proper path information in the environment.
Sorry for your difficulties, maybe there could be something of issue on a Mac since I don't have one to test, but it works on windows and linux (ubuntu, aws linux). Could be something with gradle, but I'm using two different gradle versions across a couple projects that use the jnats-server-runner, it works fine.
P.S. I'm having a friend check the build on a Mac, he's always worked on a Mac and been a contributor, so I'm pretty sure the Max issue would have surfaced by now.

Closing not reproducible.


fix race condition when trie generation thread may be invoked after storage has been closed

motivation: with trie genration now running on lower priority, a race was exposed where the operation may start after the storage already was closed
changes: guard on state before trying to execute a statement on the connection since it may be terminated

@swift-ci please smoke test

@swift-ci please smoke test


Remove unused source code in Code Coverage API

CoverageChangeTendency is also not used, expect for its unit test.
Some metric types are not used in ElementFormatter.


Cloudformation: Fix - validate template yml fixes

This change fixes:

Replace call to non-existent exception yaml.ParserError
Catches yaml scanner error for valid json with tabs
Supply yaml loader to ensure yaml loading throws exception validly for json with tabs and doesn't try to load the json incorrectly

Coverage decreased (-0.0006%) to 94.263% when pulling 0f062f68ff1f6a48e3768c0068d201277c49a83a on shano:fix-invalid-yaml-parsererror into 73813460b66119dd2491f286a01bf07e0b18d193 on spulec:master.

Thanks @bblommers !

Hi @shano, would you mind merging master into your branch? The ServerMode tests are now fixed, so Travis should be happy again if we pull the fix here as well

Cool, done @bblommers


[Event Request] codeunit 12 "Gen. Jnl.-Post Line"

Please add OnAfterUpdateTotalAmounts event in function UpdateTotalAmounts
procedure UpdateTotalAmounts(var TempDimPostingBuffer: Record "Dimension Posting Buffer" temporary; DimSetID: Integer; DtldCVLedgEntryBuf: Record "Detailed CV Ledg. Entry Buffer")
    var
#if not CLEAN19
        TempInvoicePostBuffer: Record "Invoice Post. Buffer" temporary;
#endif
        IsHandled: Boolean;
    begin
#if not CLEAN19
        CopyDimPostBufToInvPostBuf(TempDimPostingBuffer, TempInvoicePostBuffer);
        OnBeforeUpdateTotalAmounts(
          TempInvoicePostBuffer, DimSetID, DtldCVLedgEntryBuf."Amount (LCY)", DtldCVLedgEntryBuf."Additional-Currency Amount", IsHandled,
          DtldCVLedgEntryBuf);
        CopyInvPostBufToDimPostBuf(TempInvoicePostBuffer, TempDimPostingBuffer);
#endif
        OnBeforeUpdateTotalAmountsV19(
          TempDimPostingBuffer, DimSetID, DtldCVLedgEntryBuf."Amount (LCY)", DtldCVLedgEntryBuf."Additional-Currency Amount", IsHandled,
          DtldCVLedgEntryBuf);
        if IsHandled then
            exit;

        with TempDimPostingBuffer do begin
            SetRange("Dimension Set ID", DimSetID);
            if FindFirst() then begin
                Amount += DtldCVLedgEntryBuf."Amount (LCY)";
                "Amount (ACY)" += DtldCVLedgEntryBuf."Additional-Currency Amount";
                Modify();
            end else begin
                Init();
                "Dimension Set ID" := DimSetID;
                Amount := DtldCVLedgEntryBuf."Amount (LCY)";
                "Amount (ACY)" := DtldCVLedgEntryBuf."Additional-Currency Amount";
                Insert();
            end;
        end;
//NEW EVENT
        OnAfterUpdateTotalAmounts(TempDimPostingBuffer, DtldCVLedgEntryBuf);
//NEW EVENT
    end;

[IntegrationEvent(false, false)]
    local procedure OnAfterUpdateTotalAmounts(var TempDimPostingBuffer: Record "Dimension Posting Buffer"; DtldCVLedgEntryBuf: Record "Detailed CV Ledg. Entry Buffer")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


No analysis dir inside src dir

Describe the bug
A clear and concise description of what the bug is.
The main branch does not have the analysis directory and r scripts.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
As per the instructions in the document, the analysis script should be present here - src/analysis/. I cannot find the analysis dir in src.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Seems like this is in dev but not in main. I believe @desaibhargav is working on the analysis code as of now, so I will assign to him.

Hi @L-Pandey, thanks for reporting this. As @Zach-Attach mentions, I'm integrating the analysis as part of the library experience, so that the user only need call the .analyze() method after the .run() method and that will automatically produce the necessary benchmarking graphs.
This is part of the v0.2 release, expected to go live today.

This appears to have been fixed in dev so I am closing.


Add hydra parsing

Adds hydra parsing and also further cleanups of the repo structure

:books: Documentation preview :books:: https://metatensor-models--18.org.readthedocs.build/en/18/

Hmm. The splines should be computed once on calculator creation. Are you regenerating the calculator manually?

I have no clue with the splining.
And yes all docs are missing. I will add a page and introduction once we also have the evaluation script okay?
I think these two go hand in hand.


connectivitycheckcontroller: create check for localhost etcd conn.

We create a PodNetworkConnectivityCheck for each apiserver to etcd on a node, but we also have an etcd connection via localhost. This PR creates a PodNetworkConnectivityCheck for the localhost connection.

/test e2e-aws
/test e2e-aws-serial
/test e2e-aws-operator

/lgtm
/retest


ROX-17602, ROX-17603: Remove RocksDB reportconfigurations and integrationhealth

Description
Title
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI

/retest


Data caching not working if regular provider calls keep alive provider

This might be due to me having the wrong expectations but here it goes anyway. Minimal reproducible example attached.
I am reading daily data from a repository, if I am looking at the current day (today) then I do not want to use riverpod data caching because the data changes in realtime. However if the date selected is in the past, I want to use riverpod caching because that data is static and I benefit from the caching.
So, to solve this I have a Provider with a condition. It checks if the currently selected day is today and if then, it forwards the call to the Provider that just uses @riverpod while if the currently selected day is in the past, it forwards the call to a provider using @Riverpod(keepAlive: true).
The issue is that this does not work. Even if the Provider marked with @Riverpod(keepAlive: true) is called for a date I have already watched, the repository is called. If I mark the top level provider with @Riverpod(keepAlive: true) it does work as expected and the repository is only called the first time but I can't do that because I want the specific behaviour if we are looking at todays date.
I have created a minimal example that I attach. It reproduces what I was hoping to do.
My expectation is that if I start on 2023-04-26 and move two days back to 2023-04-24 and then one day forward again to 2023-04-25, then the repository should not be called for 2023-04-25 because I already fetched the data for that date when I moved two days back.
riverpod_test.zip

My expectation is that if I start on 2023-04-26 and move two days back to 2023-04-24 and then one day forward again to 2023-04-25, then the repository should not be called for 2023-04-25 because I already fetched the data for that date when I moved two days back.

Why would that be the behavior?
You're only keeping the state of the current day. So days other than today wouldn't be kept in memory if they aren't used anymore, and therefore re-visiting those pages would refetch them.
Am I missing something?

Thanks @rrousselGit
Much more likely that I am missing something. Let me see if I can add something to clarify.
In a simpler scenario similar to the attached example but without the extra steps, I can read directly from a repo like this:
@riverpod
Future<SomeData> fetchDataForDate(
    FetchDataForDateRef ref, DateTime date) async {
  return ref.watch(someRepositoryProvider).fetchData();
}

For each date, the repo is called. No caching and we get the 1 second delay
On the other hand if I use keepAlive: true:
@Riverpod(keepAlive: true)
Future<SomeData> fetchDataForDate(
    FetchDataForDateRef ref, DateTime date) async {
  return ref.watch(someRepositoryProvider).fetchData();
}

Then if I have previously fetched data for that date, it is already cached by riverpod, the repo is not called, there is no delay and the data is instantly available. This all works great.
In my sample code, I was trying to do a combination of these two behaviours depending on if it is today or a day in the past. So the widget always would use the same provider but internally that provider would decide if it should use _fetchDataForDateWithoutCache() or _fetchDataForDateWithCache().
It is completely possible that I am missing something fundamental here but it did not seem that unreasonable?
@riverpod
Future<SomeData> _fetchDataForDateWithoutCache(
    FutureProviderRef ref, DateTime date) async {
  return ref.watch(someRepositoryProvider).fetchData();
}

@Riverpod(keepAlive: true)
Future<SomeData> _fetchDataForDateWithCache(
    FutureProviderRef ref, DateTime date) async {
  return ref.watch(someRepositoryProvider).fetchData();
}

@riverpod
Future<SomeData> _dataForDate(FutureProviderRef ref, DateTime date) async {
  if (date.isToday()) {
    return _fetchDataForDateWithoutCache(ref, date);
  } else {
    return _fetchDataForDateWithCache(ref, date);
  }
}

@riverpod
Future<SomeData> fetchDataForDate(
    FetchDataForDateRef ref, DateTime date) async {
  return await ref.watch(_dataForDateProvider(date).future);
}

I was thinking that the _fetchDataForDateWithCacheProvider would always be kept alive for the lifetime of the application, internally caching all the repository responses but I might be completely off.

It should be. I'm pretty sure that if you put a print in it, it won't be re-executed for the same date.
Also do note that you don't need that many providers for this. You can do:
@riverpod
Future<SomeData> _fetchDataForDate(
    FutureProviderRef ref, DateTime date) async {
  if (data.isToday) ref.keepAlive();
  return ref.watch(someRepositoryProvider).fetchData();
}

and remove all the other providers.

Fantastic suggestion. Helped me understand a bit more about how things work behind the scenes. Lot's to learn still.
Lunch's on me and big thanks again for your support and hard work, it is highly appreciated.


Uncaught TypeError: Cannot read property '0' of undefined(anonymous function)

I got the error:
Uncaught TypeError: Cannot read property '0' of undefined
issue.txt
Could reproduce it in http://alasql.org/console/
CBke

create table data( id INTEGER PRIMARY KEY);
insert into data values (1);
insert into data values (2);

select a.id , ifNULL((select MIN(b.id) from data as b where a.id < b.id), 0) b_id from data as a;

create view view1 as select a.id , ifNULL((select MIN(b.id) from data as b where a.id < b.id), 0) b_id from data as a;

select * from view1;

I discovered this issue. The problem is that AlaSQL can not run SELECT subqueries from VIEW query. Probably we can not solve it in short-term. Sorry,

Closed as its put on The Long List - only to be reopend when its time has come.


Inherit from ScriptableObject

Shouldn't the dictionary inherit from ScriptableObject to avoid multiple references to the same dictionary becoming independent dictionaries upon deserialization?

Hey, that sounds good. Also serializeReference could work I'm guessing.
I'll have a look when I get the chance thanks!

Nevermind, trying to instantiate a generic ScriptableObject-derived class returns null, with no exception being thrown. Sneaky!


Missing access key in Next.js 13 route handlers

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[x] I have removed any sensitive information from my code snippets and submission.

App Id
d1e9ukt9805kdz
AWS Region
us-west-1
Amplify Hosting feature
Environment variables, Service role
Question
I am facing an issue when attempting to access AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY within a Next.js 13.4.12 with App Router. I'm trying to perform a server-side call to AWS SES inside of Route Handlers. Here's the sample code:
// src/app/api/route.ts

Amplify.configure({ ...awsmobile, ssr: true });

const ses = new aws.SES({
  credentials: {
    accessKeyId: process.env.AWS_ACCESS_KEY_ID,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  },
});

export async function POST(request: Request) {
// send email via ses
}

Both AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are undefined. I have attached the right SES permissions to the service role of the aws amplify app.
I expect that the Route Handlers assume the role of the service which will provide those credentials inside of env.
How can I obtain those credentials without setting them manually in the build step?

Hi @agazibaric 👋 , thanks for raising this!
Have you made the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables accessible to the server-side compute runtime: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-environment-variables.html?
Your build specification file amplify.yml should look something like:
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - env | grep -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY >> .env.production
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
      - .next/cache/**/*

Hi @Jay2113 , thank you for the answer!
I've tried adding those variables to the build step as you described, but unfortunately, they don't seem to be present there. I've cat the .env.production file and the secrets are missing.
As a potential workaround I could generate access keys and add them to the AWS Amplify Environment as ACCESS_KEY_ID  and SECRET_ACCESS_KEY (without the AWS_ prefix, as it's reserved by Amplify).
By exposing these keys in the build step, I can retrieve them on the server side using the following configuration:
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - env | grep -e ACCESS_KEY_ID -e SECRET_ACCESS_KEY >> .env.production
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
      - .next/cache/**/*

However, my goal is to find a solution that doesn't require manual setup of these secrets.

@agazibaric 👋 , currently we do not support the functionality of executing server side requests to other AWS services using IAM permissions. We are tracking this as a feature request here https://github.com/aws-amplify/amplify-hosting/issues/3205. I'll recommend subscribing to it to track updates. Thanks!


[T3A3][W13-A1] Conan Kian

Ready for review

@ckjr
Avoid accumulating unrelated changes into a single PR.
Tip: If you are currently on branch1 and want to create a new branch2, you need to switch back to master branch before creating branch2. If not, changes in branch1 will appear in the PR created from branch2 later.

@ckjr
Some comments added. Please ack & close the PR after reading comments.
This seems like an incomplete attempt to me.

Acknowledged.


Intercept Altitudes

Aircraft that are intercepting below the glideslope are penalized for high intercept angles. Realistically aircraft should be entering ILS approaches significantly below the glideslope to allow the pilot to fly the correct course before beginning descent.
"The vector shall also enable the aircraft to be established on the ILS localizer course in level flight for at
least 2NM (3.7km) prior to intercepting the ILS glide path." - https://www.ivao.aero/training/documentation/books/APC_parallel_runways.pdf
Therefore controller should be penalised for aircraft entering high or too far right/left but not for aircraft that are low.

@mooneybravo really? I double checked the code and don't believe they should be getting penalized for high intercept angles in relation to their altitude, the two seem to be unrelated in how the logic is implemented and shouldn't affect it. Relevant section in aircraft.js:2433.
As for the latter, unless there is a similar mandate in the 7110.65 (I'm not aware of one), no penalties will be implemented for that. IVAO/VATSIM have plenty of policies that are not 100% in alignment with real world practice, and it's the real-world practice that we're trying to simulate.

There is no policy I believe about intercept altitudes, but what could be
implemented is the maximum altitude the glidescope can be caught at, which
is seen on Navigraph ILS charts.

I thought (and was reasonably) I was observing this behavior. Just tried to replicate by vectoring an aircraft to the glide slope at 1000ft 20 miles from the runway and it established fine. Will see if I can replicate what I was seeing again, but basically I was observing that aircraft establishing on glidepath but not descending were being consistently penalised when intercept angle was 20° off nominal runway heading.
As for the information on IVAO this was just showing that ideally aircraft would be entering below glideslope as I believe would be best practice if not actually mandated in the real world. A common real world ATC transmission might include 'maintain 3000 until established' or similar.

Gotcha. You're right, it's definitely best practice to bring ac to the localizer well below the GS, and that is the phraseology indeed. I just don't personally think I'd want to add or subtract any points for that. Now something like whether or not they intercept a sufficient distance out from the approach gate (outside the FAF), THAT, I would support a penalty for. We'd just have to add in the location of all final approach fixes for each runway of all airports, and I don't feel like doing that! haha :smiley:

There is definitely some funny behavior with intercept angle penalisation. I was just penalised for this:

The trail shows direction assigned through the turn command before issuing clearance for ILS approach.

And... I think I've worked it out.

Vectoring and then using a fix along the ILS path triggers message because the last vector given to the aircraft may be significantly different to runway heading. Am I right that the logic is somehow using the heading command rather than the actual angle of interception?
If that is the case, why does flying aircraft fix-to-fix behave as expected regarding the actual angle of interception?

@mooneybravo Okay, yeah, that would be true, because it checks the runway's "nominal heading" (eg 270 for Runway "27L") and compares it against the heading assigned in the active "waypoint".
            if (!this.projected && (abs(angle_offset(this.fms.currentWaypoint().heading,
                  radians(parseInt(this.rwy_arr.substr(0,2))*10))) > radians(30))) {
              ui_log(true, this.getRadioCallsign() +
                      " approach course intercept angle was greater than 30 degrees");
              prop.game.score.violation += 1;
            }

Should probably be changed to accommodate sending a/c direct to a fix to join an approach.
As for your last question, it's simply because there's no rules requiring ATC to do anything specific with the routes the aircraft fly, only to give a 30-degrees-or-less angle when vectoring them to intercept the ILS's final approach course.
Side note: My understanding of the rules is that in the instance where we send an aircraft direct to a fix that is not a designated IAF on the approach plate, the same rules for interception apply under FAA JO 7110.65, 5-9-2-a, just as if we had vectored them onto the final. However, if we clear them to an IAF, then ATC is not expected to provide any sort of directionality, and the presence/absence of a procedure turn would be dictated by the approach plate. In the former, we need to do the 30-degree intercept check, and in the latter, we would not need to. To simplify the implementation (since it'll be nightmarish to track all the IAFs for all approaches), for now, we can just make the 30-degree check happen both on vectors to final and fixes to final. If/when GPS approaches are implemented (espeically the T-shaped ones), we'll have to revisit this, because 90>30. :wink:

Resolved by #702.


How to update to v1.0.0-rc2-16898

My UWP APP can goes well when I use below reference
Microsoft.EntityFrameworkCore.Commands v1.0.0-rc2-16811
Microsoft.EntityFrameworkCore.Sqlite v1.0.0-rc2-16811
Microsoft.NETCore.UniversalWindowsPlatform v5.0.0

But when I want to update the EF7 to the latest version (16898), there is some error in nuget output.
So, I try to update Microsoft.NETCore.UniversalWindowsPlatform to latest, but I also get below error:
Restoring packages for 'EFGetStarted.UWP'.
Restoring packages for C:\Users\lchao\Source\Repos\EntityFramework.Docs\docs\getting-started\uwp\sample\EFGetStarted.UWP\project.json...
All packages are compatible with UAP,Version=v10.0.
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm.
Some packages are not compatible with UAP,Version=v10.0 (win10-arm).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-arm-aot).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86.
Some packages are not compatible with UAP,Version=v10.0 (win10-x86).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-x86-aot).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64.
Some packages are not compatible with UAP,Version=v10.0 (win10-x64).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-x64-aot).
Package restore failed for 'EFGetStarted.UWP'.
Package restore failed. Rolling back package changes for 'EFGetStarted.UWP'.
========== Finished ==========

So I search System.AppContext and install runtime.any.System.AppContext v4.1.0-rc2-23818, then, I try to install System.AppContext  v4.1.0-rc2-23818, but also get the same error.
How can I update to the latest EF7?

Have you tried removed all package references from your project (.csproj/project.json/packages.config) ?

@ErikEJ I tried, but got the same error.

having the same issue, relevant output:
...
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm.
Some packages are not compatible with UAP,Version=v10.0 (win10-arm).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-arm-aot).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86.
Some packages are not compatible with UAP,Version=v10.0 (win10-x86).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-x86-aot).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64.
Some packages are not compatible with UAP,Version=v10.0 (win10-x64).
System.AppContext 4.1.0-rc2-23818 provides a compile-time reference assembly for System.AppContext on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64-aot.
Some packages are not compatible with UAP,Version=v10.0 (win10-x64-aot).
...

Use RC1 for now. RC2 will require updated Windows 10 Tools.

@bricelam  RC1 can't compile in Release. #4387
Now, I use 1.0.0-rc2-16811, this can work well. So, I hope 1.0.0-rc2-16811 won't be deleted on [https://www.myget.org/F/aspnetcidev]

I wonder if installing Visual Studio 2015 Update 2 CTP would help...

@ericstj Is System.AppContext supposed to install into UWP projects?

You need a NuGet update.  The latest packages require the latest version of NuGet because they use updated generation mappings.


Overlays does not display since 9.0.0

Describe the bug
Since version 9.0.0 overlay display. We can also see this on the documentation: https://vue3openlayers.netlify.app/componentsguide/overlay/#example-1-overlay-content
Example 1 is empty.
Affected version(s)
All version over 9.0.0
Expected behavior
Overlay items should be displayed.

Oh, it seems like the wrong default value is passed for className. Please set it to ol-overlay-container ol-selectable. I will fix this meanwhile and release the fix with the next version

Released with 9.0.2: https://github.com/MelihAltintas/vue3-openlayers/releases/tag/v9.0.2

Thank you very much !

There is another issue with the current update : events are not propagated when there is an overlay. If you do a scroll with your mousewheel on an overlay, the event does not propagate like it used to, and the zoom is not modified.

This could be because stopEvent is set to true by default which was a breaking change and introduced to align with the OpenLayers API.

Please raise new Issues if you find more. Thanks! :)


Ensuring that we have default options for source plugins.

Coverage decreased (-0.003%) to 60.535% when pulling a86636fe4e73fd2cce63cf61d3d640d714316cac on kevgliss:source-plugin into a6305a5cae67440c010ca77791e522daf48259ef on Netflix:master.

Coverage increased (+0.006%) to 60.535% when pulling cc4faa10d30c504308cc343aa83319313b71b9ab on kevgliss:source-plugin into e0d9443141884f13a2d4aa69deac1becd5ae3184 on Netflix:master.


Ahjorth/optional pcie address in eth tools

Add support for optional pcie_address in binary/hssi/ethernet/* tools.
Add command rejection in binaries/fpgadiag/opae/diag/* tools if more than one board is selected.

Please note that I have only changed the hssistats and fpgastats commands yet. If the changes are approved, they shall be replicated to all the other commands in the two folders.
In that case I also recommend changing the return data type from class FpgaFinder.find_eth_group() from dict to list since the data is used that way.

Coverage remained the same at 65.294% when pulling 2d67e14534562880e5329e9b98b0931b94db6717 on ahjorth/optional_pcie_address_in_eth_tools into a494f54a9f0356d0425edbff228f0254a4c70303 on master.


Our new study on lightweight high resolution networks: Dite-HRNet

Hi, thank you so much for your excellent work. Based on your research on lightweight high resolution networks, we have done some further exploratory studies. Our paper was accepted by IJCAI-ECAI2022. This is our repository: https://github.com/ZiyiZhang27/Dite-HRNet. And you are most welcome to give your valuable comments.

repository didn't include pretrained model,could you please sharing , thanks!


Feature request: cursive::theme::load_terminal_default()

Please implement a cursive::theme::load_terminal_default() function which works like the  cursive::theme::load_default() function but instead of loading and returning the default colors chosen by Cursive returns the local terminal defaults.
Rationale: loading terminal defaults is kinda tedious right now as demonstrated by the terminal_default.rs example. The example only sets the terminal background to the default color as a result, all other enums in PaletteColor remain unexplored .

I think I may have misunderstood how terminals handle color. Is there a standardized way in which terminals or applications can communicate color roles like TitlePrimary and TitleSecondary other than the background color?

Hi, and thanks for the report!
The terminal defines a handful of colors:

The basic 16-colors palette
A separate color for the background, and one for the text.

The first group is what you get with colors like "red" or "light blue". It's already usable: if you ask for a "blue" background (the default background color) it will use the definition from the terminal theme.
The "terminal default" is what we call the terminal background and text color. It's only 2 colors, so it's not quite enough to use everywhere; but it's available if you want to use the same background for instance.

Is there a standardized way in which terminals or applications can communicate color roles like TitlePrimary and TitleSecondary other than the background color?

Not really. A terminal doesn't have a notion of titles, windows, or anything beyond just text. So it's up to libraries like ncurses or cursive to define their own abstractions for that.

Thanks for the response. I will close this issue since there is nothing else we can do.


xSQLServerDatabaseOwner: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerDatabaseOwner resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.
The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a FCI.
xSQLServerDatabaseOwner Set_SqlDatabaseOwner_SQLAdmin
{
    Name                 = 'CONTOSO\SQLAdmin'
    Database             = 'AdventureWorks'
    SQLServer            = 'SQLServer'
    SQLInstanceName      = 'DSC'
    PsDscRunAsCredential = $SysAdminAccount
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it does not own the instance, and then silently exit.

To resolve this issue, a parameter called ProcessOnlyOnActiveNode should be created on the Set-TargetResource and Test-TargetResource functions.
The Get-TargetResource function will execute the helper function Test-ActiveNode to determine if the current node is actively hosting the SQL instance and return the result via the read-only property IsActiveNode.
The Test-TargetResource function will use the value of ProcessOnlyOnActiveNode and IsActiveNode to determine if it should continue. If ProcessOnlyOnActiveNode is $true and IsActiveNode is $false, Test-TargetResource will return $true.
I put together this gist as a guide to updating the resource.
Also, see the xSQLServerAlwaysOnAvailabilityGroup resource for a completed example.

Does this issue applies to AlwaysOn too?

It looks like AlwaysOn was already corrected according to the Resources should be cluster aware project.

Resource was deprecated


Add a docker-compose for development

This adds the ability to use docker-compose for development with hot reloading. Now one only has to type docker-compose -f docker-compose.dev.yml up -d to get started with development.

@adriankumpf I believe it provides a much more easy starting point. To get started developing one only has to spin up a container. The dependencies are cached on the host so, when running teslamate without the container it should still work.

I see. Once docker-compose -f docker-compose.dev.yml up -d  works on a fresh repo and (and conflicts are resolved) this can be merged :-)

For me it works perfectly fine on a new repo. You just have to set the environment variables UID and GID to the ids of your user to have it work correctly.
I will add documentation for this, once the PR is merged.

Something must have gone wrong during merging. The "Files changed" tab shows 5k changed lines 😱  Can you take a look?

I can attest that in my environment, this would make dev easier.

I can attest that in my environment, this would make dev easier.


htcondor python bindings currently pinned to 9.2.0

Due to condor versioning issue at LPC mentioned in #65

cc: @clundst

@mapsacosta do you still have a constraint that htcondor version should be == 9.2.0?

@oshadura let me ask the HTCondor team @3pm and get back to you, we may be able to upgrade now...

@oshadura @lgray the condor team at FNAL confirmed that we can upgrade to 10.0.1


Release 5.4 out of preview.

Updates include:

Handling paths with spaces
Improved error handling for older versions of Unity
Fixed bug when spaces were in Additional Arguments
Safe handling of large installers

We've been running on all these changes except the large installers for some time, which is a small change. Would like to move these into master so that default installs get support for Unity 2020.

This tool is very helpful.

This tool is very helpful.


[Bug] Table's DateTime data type does not work

Description
Appsmith sees DateTIme columns in MSFT SQL Server as int numbers. Even if I try to change the column's datatype in the table widget - it shows weird things (like "year 521234") or complains about invalid date
Steps to reproduce the behaviour:
Add steps to reproduce this behaviour, include console / network logs & screenshots

Add any SELECT data query that has a DateTime column in SQL Server
Run the query
See error

Important Details

Version: [Cloud]
Browser [chrome]

@alex-jitbit thank you for reporting this! Looks like an issue in our epoch date converter where we're using moment.unix for milliseconds.
To get around this today, you can format the data in the table by mapping over it
{{ Query1.data.map((row) => { return  { ...row, id: moment(row.id).format("DD-MM-YYYY") } })}}

Thanks for fixing this so quickly. Any news when this will be deployed?

@alex-jitbit This fix is already deployed on Appsmith Cloud ( https://app.appsmith.com ). For self-hosted instances, this will be available early next week.

I still see this issue on the latest version of the self-hosted app. When is getting fixed?

@tlawrence-TAG this was fixed awhile back. Where are you seeing this issue? Can you share step to reproduce it?

You're right... it does look to be working. What I'm seeing is that if you have more results that don't fit into the page size that's displayed, it doesn't sort the entire set of data even though it knows the total amount of records and is holding the entire dataset in memory!

Still seeing this issue. Any update on this bug?

@jbaker43 please file a new issue with a video describing the problem and some sample data of the table. It could simply be that the date format you selected is is epoc seconds and your data is in milliseconds but we'll need to investigate it


3d secure authentiction process not included in the card charge proceedure

Feature Request Type

[ ] Core functionality
[ ] Alteration (enhancement/optimization) of existing feature(s)
[ ] New behavior

Description

The same problem right now


move to netstandard 2.0

Configueé projects to use netstandard 2 instead of netcoreapp for better support across .net versions

thanks to @dotted


Crashing when importing VAE.py

Currently, I am using
Windows 10
Python 3.6
VTK 7.1.0
If i try to run GUI.py, I get Error from
config_module = imp.load.source('config', args.config_path)
saying "unmarshallable object"

This is due to discrepancies between python 2 and 3. Either install python 2.7 or replace the imp.load_source calls with import('config',args.config_path[:-3]) (the "[:-3]" will get rid of the .py , and is also an adorable kitty emoticon).
You'll also need to handle other python2-3 shenanigans like making sure any xrange calls are replaced with range, etc.


Use marshmallow for Serialization and deserialization in logic

Serialization and deserialization of sqlalchemy objects for use in the API and UI are being done in our own bespoke (custom) manner. There are standard libraries that do this like marshmallow and we should use them.
Tasks

[ ] Use marshmallow (and marshmallow-flask in logic / controller layer for serialization and deserialization) https://flask-marshmallow.readthedocs.io/en/latest/

[ ] Replaces hand-rolled current work spread around controllers and in site.models.Packaged
Why? Standard, well-developed library for doing this

Moving in next milestone as this is quite big refactor and did not fit in time

This one needs big refactor so moving to next milestone - Did not fit in time

FIXED


ChangeSet building for embedManyDocuments fails to detect removes

When removing a document from an embedMany PersistentCollection, the changeSet for the parent document does not contain the property/field as changed, even though the document is successfully removed.
It does work however, if the property has been initialised before, e.g. by adding another document to the collection.
For better understanding, I have attached a unit test, reproducing the issue:
<?php

namespace Adticket\Elvis\CoreBundle\Tests\EventListener\Doctrine;

use Doctrine\Common\Collections\ArrayCollection;

use Doctrine\ODM\MongoDB\Event\OnFlushEventArgs;
use Doctrine\ODM\MongoDB\Events;
use Doctrine\ODM\MongoDB\Mapping\Annotations as MongoDB;
use Doctrine\ODM\MongoDB\PersistentCollection;
use Doctrine\ODM\MongoDB\Tests\BaseTest;

/**
 * Class DoctrineTest
 *
 * This test uses:
 * doctrine/mongodb-odm 1.0.4  Doctrine MongoDB Object Document Mapper
 * phpunit/phpunit      4.8.23 The PHP Unit Testing framework.
 */
class DoctrineTest extends BaseTest
{
    public function testBug()
    {
        $listener = new SimpleListener();

        $this->dm->getEventManager()->addEventListener(Events::onFlush, $listener);

        $document     = new Document();
        $document->id = new \MongoId();

        $document->embeddedCollection = new ArrayCollection();
        $document->embeddedCollection->add(new Embed('A'));

        $listener->onFlushCallable = function (OnFlushEventArgs $eventArgs) {
            $unitOfWork = $eventArgs->getDocumentManager()->getUnitOfWork();

            foreach ($unitOfWork->getScheduledDocumentUpserts() as $document) {
                $changeSet = $unitOfWork->getDocumentChangeSet($document);

                /** @var PersistentCollection $persistentCollection */
                $persistentCollection = $changeSet['embeddedCollection'][0];

                $this->assertEquals(1, count($persistentCollection->getInsertDiff()));
                /** @var Embed $newEmbed */
                $newEmbed = $persistentCollection->getInsertDiff()[0];
                $this->assertInstanceOf(Embed::class, $newEmbed);
                $this->assertEquals('A', $newEmbed->value);

            }
        };

        $id = (string) $document->id;

        $this->dm->persist($document);
        $this->dm->flush();
        $this->dm->clear();

        $document = $this->dm->getRepository(Document::class)->find($id);

        $document->embeddedCollection->add(new Embed('B'));

        $listener->onFlushCallable = function (OnFlushEventArgs $eventArgs) {
            $unitOfWork = $eventArgs->getDocumentManager()->getUnitOfWork();

            foreach ($unitOfWork->getScheduledDocumentUpdates() as $document) {
                $changeSet = $unitOfWork->getDocumentChangeSet($document);

                /** @var PersistentCollection $persistentCollection */
                $persistentCollection = $changeSet['embeddedCollection'][0];

                $this->assertEquals(1, count($persistentCollection->getInsertDiff()));
                // Using "1" as index here, as apparently the index from the original PersistentCollection is used
                /** @var Embed $newEmbed */
                $newEmbed = $persistentCollection->getInsertDiff()[1];
                $this->assertInstanceOf(Embed::class, $newEmbed);
                $this->assertEquals('B', $newEmbed->value);
            }
        };

        $this->dm->flush();
        $this->dm->clear();

        $document = $this->dm->getRepository(Document::class)->find($id);

        $document->embeddedCollection->removeElement($document->embeddedCollection->first());

//        This line is required for doctrine do detect the removal in the change set correctly
        $document->embeddedCollection->add(new Embed('C'));

        $listener->onFlushCallable = function (OnFlushEventArgs $eventArgs) {
            $unitOfWork = $eventArgs->getDocumentManager()->getUnitOfWork();

            foreach ($unitOfWork->getScheduledDocumentUpdates() as $document) {
                $changeSet = $unitOfWork->getDocumentChangeSet($document);

                // This will fail if the above comment remains commented out
                // The change ( = removal of first element ) in the embeddedCollection property / Persistent Collection will not be detected
                // Thus the index 'embeddedCollection' will be missing from the array

                /** @var PersistentCollection $persistentCollection */
                $persistentCollection = $changeSet['embeddedCollection'][0];

                $this->assertEquals(1, count($persistentCollection->getDeletedDocuments()));

                // Using "0" as index here, as apparently the index from the original PersistentCollection is used
                /** @var Embed $removedEmbed */
                $removedEmbed = $persistentCollection->getDeletedDocuments()[0];

                $this->assertInstanceOf(Embed::class, $removedEmbed);
                $this->assertEquals('A', $removedEmbed->value);
            }
        };

        $this->dm->flush();
        $this->dm->clear();
    }
}

/**
 * Class SimpleListener
 */
class SimpleListener
{
    /**
     * @var callable|null
     */
    public $onFlushCallable;

    /**
     * @param OnFlushEventArgs $eventArgs
     */
    public function onFlush(OnFlushEventArgs $eventArgs)
    {
        if ($this->onFlushCallable) {
            call_user_func($this->onFlushCallable, $eventArgs);
        }
    }
}

/**
 * @MongoDB\Document()
 */
class Document
{
    /**
     * @MongoDB\Id()
     *
     * @var \MongoId
     */
    public $id;

    /**
     * @MongoDB\EmbedMany(targetDocument="Adticket\Elvis\CoreBundle\Tests\EventListener\Doctrine\Embed")
     *
     * @var ArrayCollection|Embed[]
     */
    public $embeddedCollection;
}

/**
 * @MongoDB\EmbeddedDocument()
 */
class Embed
{
    /**
     * @MongoDB\String()
     *
     * @var string
     */
    public $value;

    /**
     * @param $value
     */
    public function __construct($value)
    {
        $this->value = $value;
    }
}

@Jan0707 thanks for the test case! Is the error also reproducible on 1.1.x branch of ODM? Asking since 1.0.x is no longer supported

Using version ~1.1 solved the problem. Which is technically good news, but also sucks for us, as we cannot upgrade the version just yet in this specific project.
I will close this issue. Thanks for the help !

@Jan0707 looking through 1.1.x changelog I'd guess this was relevant PR: https://github.com/doctrine/mongodb-odm/pull/1437 if you'd like to backport it into fork of yours. Also the upgrade to 1.1.x is quite painless unless it's PHP version that is holding you back.


Wrong files names for fonts without defined unicode

Describe the bug
For all fonts that don't have unicode metadata defined, variant filenames are wrongly generated.
i.e. for material-icons currently the generated source is<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>Steps to Reproduce
Just include the mixin, i.e.:
@use '@fontsource/material-icons/scss/mixins' as material;

@include material.faces();

Expected behavior
No response
Version
5.0.0
OS
No response
Browser
No response
Additional context
I am able to workaround this issue by adding map with empty values for subsets, i.e:
@use '@fontsource/material-icons/scss/mixins' as material;
@use 'sass:map';

@include material.faces(
  $metadata:
    map.set(
      material.$metadata,
      unicode,
      (
        latin: null,
      )
    )
);

Fix has been added at 34c487c96cbf9eac4ba0182c3582ca3933a8269c (accidental commit to main oops), but we're just going to write some more tests that snapshot the CSS outputs of the SCSS files to reduce the chances of something like this happening in a separate PR.