Implement Jest Tests for Conversion Calculator

The Conversion Calculator currently lacks Jest tests. We need to add tests to ensure its functionality and reliability.
Tasks:

Identify the key functionalities of Conversion Calculator.
Write unit tests for:

Component rendering
User interactions
Props and state management

Write integration tests for:

Any significant workflows (if applicable)

Ensure all tests pass in the local environment and CI/CD pipeline.
Update the documentation to include instructions on running the tests.

Acceptance Criteria:

Jest tests for Conversion Calculator are created and passing.

Additional Information:

Any known issues or specific areas of concern related to Conversion Calculator can be added here.

@TobyDS Can you comment here, so i can assign the issue to you?

@Bashamega Absolutely, feel free.


refactor(translation): minor nl changes

Some minor modifications in the NL translation file.

Thanks a million @RolfKoenders :)


How to Install ?

I'm sorry i'm new with git & phyton.
Does anyone know how to install this? maybe some video about installing this bot? or exe release may be?
thanks in advance

Instructions are on the WIKI
https://github.com/PokemonGoF/PokemonGo-Bot/wiki
Issues are not a place to post support requests, but for reporting bugs.

@brantje another noop that is not able to use his gray mass ;)


Husky

Description
Add Husky library
Related Issue

Close #26
Motivation and Context

How Has This Been Tested?
git commit -S -m "#26 : Add husky"

The script have launched.
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Problem with the signed commit, abording


Phantom Forces not working

Anyone got  a suggested config or does it just not work?

Anyone got a suggested config or does it just not work?

Try to use different Aim Mode


Add hidden content body field for SEO purposes when gated

This is being implemented the same was as RR. @brandonbk hoping you can give me your opinion on possibly adding this logic to this component.  Maybe with some sort of  <if(!canAccess || (isLoggedIn && requiresUserInput))> to display this at the bottom of the gating component.

 Adding HTML code of entire article to gated Identity X campaigns


Directional light does not disappear after removing the DirectionalLight component

Removing the DirectionalLight component does not remove the directional light from the render world
Caused by #15320
Noticed in the clearcoat example

This seems like a general issue we need to solve with the retained render world that the PR/docs doesn't answer, who is responsible for removing components from the render world? Should that be done by the extract step, a separate system/plugin, or is it the users responsibility? A workaround is to remove SyncToRenderWorld and RenderEntity together with the component, but that seems like a footgun.
In any case we really need to fix and/or document it before 0.15.

[4:24 PM]kristoff3r: The OIT example is broken with the retained render world in the same way as https://github.com/bevyengine/bevy/issues/15560. How do we plan to support removing components like this?
[4:29 PM]IceSentry: 😦 oh no
[4:30 PM]IceSentry: @Bird! @Alice 🌹 ^
[4:32 PM]Alice 🌹: Hmm. This is more common than I expected
[4:33 PM]Alice 🌹: My medium-term plan was to do a ref-counting style design, where you have a "number of components that are causing this to be retained" tracked
[4:33 PM]Alice 🌹: And then hooks to incremenet and decrement it
[4:33 PM]Alice 🌹: I think we probably need to prioritize getting that in
From Discord.


Appears there is an unnecessary loop in check_Q_spd

https://github.com/locuslab/qpth/blob/0ccf2d73a299eda00f597406e2dd00bf97ba728a/qpth/qp.py#L82

       if check_Q_spd:
           for i in range(nBatch):
               try:
                   torch.linalg.cholesky(Q)
               except:
                   raise RuntimeError('Q is not SPD.')`

The Q variable is not updated in the loop, so loop over nBatch will produce same result every time

Thanks, good spot. I just pushed in a fix to this


form_(in|out) -> first_line_format

This PR replaces all (already deprecated) occurences of Request.form_(in|out) with Request.first_line_format.

I'm not sure if the name first_line_format is a good fit - might be confusing for HTTP/2 use cases.


dependency updates

Updates a few outdated npm dependencies.
tween.js is not updated yet, pending resolution of #11324.

Thanks for the pull request @jjhembd!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @jjhembd! I've tested the updates, and everything is looking good.
Just that one comment, and this should be good to go.

Looks great, thanks @jjhembd!


Brings GH pages up to date

As it says on the tin.
The Github Pages are rather outdated in terms of referencing the supported Rails version numbers. I also noted the gemspec is rather outdated (I'll open a separate PR) and the Github repository description is also referring to older, unsupported (?) Rails versions.
Question: are you using the Google Analytics tracking code at all? Otherwise, I'd advise simply removing it (which can be done in a separate PR).

@stefanvermaas Thanks for taking the time to open this PR, the changes looks good!


add spatie/menu to navigation section

Used this library in a project recently and found it very nice to work with. Definitely recommended 👍 https://github.com/spatie/menu

Thanks!


BUG : TITLE IS FLICKRING ON SERVICE PAGE

https://github.com/khushi-joshi-05/Food-ordering-website/assets/162811933/3ccd8bcc-6d69-4f00-94e4-a305ccee0124

@khushi-joshi-05 Please assign me this issue.


Module not found: Can't resolve imported dependency "async_hooks"

App •  ERROR  •  UI  in<EMAIL_ADDRESS>
Module not found: Can't resolve imported dependency "async_hooks"
Did you forget to install it? You can run: npm install --save async_hooks

App •  COMPILATION FAILED  • Please check the log above for details.

Is this useable in a Javascript project?
Tried installing in a Quasar js app and get the above error on compile, after successful install of import * as Langtrace from '@langtrase/typescript-sdk'

Hey @sonicviz , thanks for reaching out and apologies for the delay in response. Let me take a look and get back to you

Hi @sonicviz thanks for trying out Langtrace. Currently the SDK is only supported on Node.js and won't work on browser side code. If you are using Node.js for your backend try installing the SDK there and it should work. If you face any issues let us know and we would be more than happy to help.


Add GitHub Readme YouTube Cards

65 . GitHub Readme YouTube Cards
GitHub action to show your latest YouTube videos on your GitHub profile or project readme automatically as dynamic SVG cards

📍 For example :

65 . GitHub Readme YouTube Cards
GitHub action to show your latest YouTube videos on your GitHub profile or project readme automatically as dynamic SVG cards

📍 For example :

This is a very good tool 👌
Thank you for adding it 🙏


Improve notifications summary

Discussed in https://github.com/jocmp/capyreader/discussions/554

Originally posted by flameshikari November 23, 2024
I'm suggesting a feature that will notify about a number of new articles in a single notification instead a notification per article grouped by feeds.
Suggested behavior:

I came to make this suggestion, this possibility would be great. By the way, thanks for this application!

This change is live as of 2024.12.1088-dev. I wasn't able to make it exactly like the suggestion, but the elements are all there like the total count.

Summary
Expanded view


Fixup Flags

Mark hidden all references to signature-policy
Default all uses of --authfile
Add --authfile support to podman run and podman create.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

I'm curious, why are we hiding --signature-policy?  I know it's not used often, but in weird corner cases might be useful.  I'm just a little concerned that we're starting to get a handful of options that might be useful on rare occasions and we won't have a secret decoder ring anywhere for them.
Other than that, the code LGTM.

Multiple reasons:

It was not fully used in all situations
It is security related, I would like to eventually move to a discussion about whether or not users can override SYS Admins decisions.    If admin says only run containers signed by this signature, we should make it more difficult to override (--registries-conf) should be similar situation.  I don't want signature-policy allowed in general right now until we make some decisions on it.
3 Signature-policy was not fully implemented/documented for all commands that could/would use it.
4.I don't think we should carry technical dept for an options that was added mainly for CI/CD testing.

Need to hit varlink stuff then too:
io.podman.varlink:417:    signaturePolicyPath: string,
io.podman.varlink:475:    signaturePolicyPath: string,
io.podman.varlink:766:method PushImage(name: string, tag: string, tlsverify: ?bool, signaturePolicy: string, creds: string, certDir: string, compress: bool, format: string, removeSignatures: bool, signBy: string) -> (reply: MoreResponse)
io.podman.varlink:828:method PullImage(name: string, certDir: string, creds: string, signaturePolicy: string, tlsVerify: ?bool) -> (reply: MoreResponse)

@rhatdan I'm generally in favor of this flag clean up.  For signature, would you consider removing it completely from our CLI and only support it in libpod.conf (undocumented maybe?) ?  I'd like to propose this because:

i dont think it is used. for those that might be using it, we provide a conf way to override it.
the above would allow it to be "global" in the sense it isn't just command to command but could be applied to the runtime.
it isnt needed for parity with other runtimes
now is the time to do it; just looking at the PR makes me think about the technical debt incurred by keeping it around as a "silent" option.

@rhatdan thanks for the explanations.

Baude lets discuss signature-policy at standup,  the main use case for this is CI/CD System and I don't see removing this and moving it to libpod.conf, as an easy thing to do.

@baude Went back to not enabling these in remote commands.
Also removed cert-dir from remote commands.  Updated man pages to reflect what is not available in remote commands.
@TomSweeneyRedHat @giuseppe @baude @mheon PTAL

Tests aren't hip @rhatdan, IDK if it's related to the changes or not.

These aren't the tests that were blowing up on master, so I'm leaning towards not flakes

Tests are passing
@mheon @baude @giuseppe @vrothberg @TomSweeneyRedHat PTAL

LGTM, happy green test buttons.
One question for future consideration.

LGTM, but I won't merge until @jwhonce and @baude can take another look and say they're satisfied - a lot of changes deep in Varlink code here

/lgtm


Add Deepspeed zero3 configuration to run bloom-7b on Gaudi1

What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Is this supposed to work with SynapseAI 1.13? I just tried with 1.12 and I got a memory allocation error.

Yes, we will have a fix for 1.13. I tested the code with the candidate fix so it works for 1.12 yet. I'm sorry to forget to mention it.
I think we should hold to merge this until 1.13 out? @libinta What do you think of it?

Sounds good to me, let's wait for the release of 1.13 to merge this PR :slightly_smiling_face:

@yeonsily @libinta Could you run this example with 1.13 and let me know the following metrics please so that I had it to the set of regression tests?

Throughput
Train runtime
Perplexity

@yeonsily @libinta Could you run this example with 1.13 and let me know the following metrics please so that I had it to the set of regression tests?

Throughput
Train runtime
Perplexity

@regisss  This the batch 8 result.
train_runtime               = 0:25:53.70
train_samples_per_second    =      4.755


gnome3.gnome-power-manager: 3.30.0 -> 3.32.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-power-manager/versions.
meta.description for gnome3.gnome-power-manager is: '"View battery and power statistics provided by UPower"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0/bin/gnome-power-statistics had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0/bin/.gnome-power-statistics-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 3.32.0 with grep in /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0
directory tree listing: https://gist.github.com/93272546d7db395d1a7c916e24114d02
du listing: https://gist.github.com/597ebde3e67ef0f5f88537eb2d0e53b4

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

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gnome3.gnome-power-manager

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnome3.gnome-power-manager https://github.com/r-ryantm/nixpkgs/archive/4e9c0bd8027ee00879da5326f749106a35b878dd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0
ls -la /nix/store/p4p4gzr8a9s602wsnlkhf0m37xdkxxy1-gnome-power-manager-3.32.0/bin

cc @lethalman @jtojnar @hedning @worldofpeace for testing.

new release, see #57027


Enhancement Request: Custom Builds using Typescript Compiler

I created a custom openlayers 4 build using typescript and amd (https://github.com/ca0v/ol4-lab) but had to tweak rbush/quickselect because, unlike ol, it cannot support es6 syntax.  This was the only thing preventing a basic custom build using nothing but tsc.

Very interesting!

Agreed, I also find this interesting. But I don't understand the size comparison i.e the reference to a 91k ol-debug.js doesn't seem right to me?

@bjornharrtell Those were line counts so roughly 1.4MB vs 2.5MB uncompressing.

@ca0v I have not tried, and I don't know how Rollup would fit into your stack. But https://github.com/rollup/rollup-plugin-commonjs should help here. Just so you know, rbush is a normal dependency of ol.

@ahocevar rollup might do it because the rbush project cannot use es6 syntax due to a browserify limitation (see https://github.com/mourner/rbush/pull/66#issuecomment-279824375).  @morner might consider use tsc instead although I'm not sure how that would work.
Maybe: tsc --allowJs rbush.js --outDir ./out --module umd

what exactly is the 'enhancement request' here? OL uses 5 external 'modules': the 4 in ol.ext, and proj4js. It uses proj4js global, and tasks/build-ext.js hacks the ol.ext ones so they can be used with GCC. The ol ES-module package simply imports the ol.ext ones as CJS modules. This however only works with server-side tools that can import CJS, so isn't usable directly in the browser, and from what you say can't be used with TS either.
I'm currently exploring using the ES-module OL version directly in the browser, and as part of this have created a custom version of proj4js and rbush replacing the UMD wrapper with an ES one. I could make these available for use in other environments, such as TS if that can't handle the current CJS import. Alternatively, there are tools like https://github.com/nolanlawson/cjs-to-es6 which enable you to convert CJS modules to ES (with various caveats, as it's not a simple 1-to-1). I view these though as short-term fixes. ISTM the long-term solution is for the upstream packages to provide the code in ES module form. I don't see much that OL can do ATM other than provide short-term hacks.

@probins The 'enhancement' is to allow TSC to build OL projects without modifying the dependencies.  The implications of using TSC to build the transpiled code instead of browserify means asking multiple project owners to experiment with something that might not work.  I can only say it worked for a very simple demo using 4.0.1 and if it works in the larger picture would simplify the build process (tsc will transpile and concatenate) for typescript developers.  As an aside, typescript delivers freedom through constraint that ol developers might come to love nearly as much as their unit tests.

The es6 module migration is now complete, closing


fix: adjust startup, liveness and readiness probes settings

Description of the change
Startup probe settings seem to have been added in the upstream Backstage Chart
in [1], but the current settings do not allow the RHDH Chart for the
liveness probe to be triggered sufficiently enough for the app to be
considered live.
This adjust such settings by accounting for the worst case scenario
where the application might take a bit long to start.
This also aligns the probe endpoints with the upstream chart.
[1] backstage/charts#216
Existing or Associated Issue(s)

Fixes https://issues.redhat.com/browse/RHIDP-5106
Relates to https://issues.redhat.com/browse/RHIDP-4968

Additional Information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[ ] Variables are documented in the values.yaml and added to the README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes.
[ ] JSON Schema template updated and re-generated the raw schema via pre-commit hook.
[ ] List tests pass for Chart using the Chart Testing tool and the ct lint command.

/uncc @kadel
/cc @PatAKnight @gustavolira

/cherry-pick release-1.4

This fixes the problem that we have, but why not just remove the probe definitions from the RHDH sub-chart and rely on the inherited values from the upstream RHDH chart? I've tested them and it should work

when cherrypicking this to the release-1.4 branch we can safely update that chart from 2.23.0 to 2.23.1 as the 2.24.z version was created when we branched for the 1.4.0 release.
so the same patch has to be applied to https://github.com/redhat-developer/rhdh-chart/blob/release-1.4/charts/backstage/Chart.yaml 2.23.0 -> 2.23.1
https://artifacthub.io/packages/helm/rhdh-chart/backstage

This fixes the problem that we have, but why not just remove the probe definitions from the RHDH sub-chart and rely on the inherited values from the upstream RHDH chart? I've tested them and it should work

That was exactly the issue. The upstream chart defines the probes (including the startup probe) here, but the default thresholds and periods do not seem sufficient to cover the RHDH application.
Also note that this was also not always reproducible. On some clusters, it worked, but in some others, the startup probe didn't and the pod got restarted until it failed.


Previous pages not being refetched with correct locale when user changes the locale on current page and goes back to those previous pages

Description
When going back to the previous browser's history pages, those pages are not being refetched with the correct locale once the user has changed the locale of the website on the current page.
Maybe this is is the intended behavior, but it shouldn't: Why in the world an user that changes the language on my website and go back to the previous pages would want those pages to display on the previous language and not the language that he actually wants?
Verifications

[x] I've verified that the problem I'm experiencing isn't covered in the docs.
[x] I've searched for similar, existing issues on GitHub and Stack Overflow.
[x] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://www.ramzeis.com
Reproduction description
I'm following all of the steps on the navigation section docs.
I'm navigating between my pages using both the <Link/> component and the useRouter() router extracted from the object returned by the createSharedPathnamesNavigation function. After navigating FORWARD to any page, either by clicking on  components or changing the url using the browser's search bar, everything works as expected:

The new locale is succesfully being inyected onto the target url when the user chooses the new language he wants
The NEXT_LOCALE cookie is succesfully changing to the new locale.
The pages are picking the correct locale and are being rendered with the correct translations

But when navigating BACKWARDS, when clicking on the browser's back button, every page of the history will completely ignore the NEXT_LOCALE cookie and will render it's content on the previous locale language and not the new one. No new requests are being made when going back to those pages.
Expected behaviour
When navigating backwards the pages must be refetched if the NEXT_LOCALE cookie has changed an use that locale.

I appreciate the report, but this has been discussed before and works as intended: https://github.com/amannn/next-intl/issues/700.


Added piping support, updated some deps

Fixed #1
I happened to use it, saw the issue and thought to add it 😛

@sindresorhus what do you think?

Instead of an option, couldn't we just check if process.stdout.isTTY is false?

I didn't think of that, should I change it?

Yup. If you can avoid introducing a new option, it's good :).

I'm not sure how to use execa to test for the default option(return icons location) now.

I'm not sure how to use execa to test for the default option (return icon's location) now.

You could just set process.stdout.isTTY to true manually in the test and then reset it to whatever it was before.

You could just set process.stdout.isTTY to true manually in the test and then reset it to whatever it was before.

Inside the test it's already true, the problem is inside the child process that is created.

Oh right, you could pass stdio: 'inherit' to execa and it should work.

It does, but I can't capture the output 😕

The process.stdout.isTTY is undefined. No? 😕

I think we can skip this test after all.

Friendly ping @kevva :relaxed:

Friendly ping @kevva @sindresorhus :relaxed: (I think we can skip this test, after all)

The trick to make it work in execa is to not check process.stdout.isTTY, but rather to just assume piping when there are no arguments.

but even when piping, there will be arguments. No?

Ah yeah, that's true... I guess we can just pass down an environment variable in the test and check for it in the code. Just for testing. Like __FILE_ICON_SHOULD_PIPE__. It's ugly, but at least then we can test it.

Hmm. The problem is that execa runs the command in a child process, and in that child process process.stdout.isTTY is always false. So maybe you meant an env variable __FILE_ICON_SHOULD_NOT_PIPE__? If so, I think that an option like --no-pipe would be better: we can test it and lets someone pipe the location of the image as well.

So maybe you meant an env variable FILE_ICON_SHOULD_NOT_PIPE?

Yes, I said environment variable.

If so, I think that an option like --no-pipe would be better: we can test it and lets someone pipe the location of the image as well.

I don't want to expose it as a flag to users. We only need this workaround for testing.

Thanks for your patience, @iamnapo. It looks good now :)


Exception calling "AddFromFile"

From VS Feedback:
I just upgraded my solution to .net core 2.0 and also find Entity Framework migrations to be working very inconsistently in the package manager.
I tend to get the following error on "add-migrations"
"add-migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character."

See also:

scaffold-dbcontext basepath exception on EntityFrameworkCore
Add-Migration : Exception calling “AddFromFile” with “1” argument(s): “'basePath' cannot be an empty string (”")

This made me curious. We would throw above exception when the generated file is essentially null coming out of reveng or add-migration. I am trying different things to achieve that but so far all I got is VS crash. :trollface:

I can't repro this. If anyone has a solution that consistently fails with this error, please let us know so we can investigate further.


Error on Android device version 4.4.2

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Got the following error when run the app on Android Device Samsung S4
Ionic Native: deviceready event fired after 15027 ms vendor.js:114769
accepted session main.js:1079
you are authenticated! main.js:853
ERROR
Error {rejection: TypeError, promise: t, zone: r, task: e}
vendor.js:1377
defaultErrorLogger vendor.js:1377
ErrorHandler.handleError vendor.js:1437
IonicErrorHandler.handleError vendor.js:113943
onError.subscribe.next vendor.js:4860
schedulerFn vendor.js:3992
SafeSubscriber.__tryOrUnsub vendor.js:32731
SafeSubscriber.next vendor.js:32678
Subscriber._next vendor.js:32618
Subscriber.next vendor.js:32582
Subject.next vendor.js:37568
EventEmitter.emit vendor.js:3978
(anonymous function) vendor.js:4269
t.invoke polyfills.js:3
r.run polyfills.js:3
NgZone.runOutsideAngular vendor.js:4201
zone._inner.zone._inner.fork.onHandleError vendor.js:4269
t.handleError polyfills.js:3
r.runGuarded polyfills.js:3
(anonymous function) polyfills.js:3
n.microtaskDrainDone polyfills.js:3
o polyfills.js:3
e.invokeTask polyfills.js:3
i.isUsingGlobalCallback.invoke polyfills.js:3
n
Expected behavior:

Steps to reproduce:

Get started with the following Ionic AWS Starter
$ ionic start myApp aws
$ ionic cordova platform add android
$ ionic cordova build android
Related code:

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here
cli packages: (/home/develop/.npm-packages/lib/node_modules)

    @ionic/cli-utils  : 1.13.1
    ionic (Ionic CLI) : 3.13.1

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 3.0.0
    Cordova Platforms  : android 6.2.3
    Ionic Framework    : ionic-angular 3.7.1

System:

    Node : v8.7.0
    npm  : 5.4.2
    OS   : Linux 3.10

Misc:

    backend : pro

Hello! Thank you for opening an issue with us!
Does this only happen when using the AWS starter? Or does it also happen when using other starters (blank, tabs, etc)? If only with the AWS starter, I will move this issue over to its repo.
Thank you for using Ionic

Hello,
Thanks a lot for your quick response.
Just when using the AWS starter. Please move this issue to its repo.
Best regards

This issue was moved to ionic-team/ionic2-starter-aws#43


RadioButtons ValueType of SetEnvUIConfig.xsd is limited to only 5

We are in need of having more than 5 environments, and we would like to have RadioButton instead of Fileselect.
We are using Deployment framework V5.5
is it possible to achieve this?

You could create a custom version of SetEnvUI.exe.  The code that sets up the radio button controls and the overall UI is here.

Thank you...


Don't send additional 500 email if no useful information in it.

After the implementation if #1485 we get an additional email for all 500 errors, even if there is no supplied information. Let's not send an email if there's no useful information in it.

Closed as of #1498 I think


Bugfix: Use singular point when score is 1 or -1

When reasonScore is 1 or -1 and score is 1 or -1, use singular "point" instead of "points" and remove unnecessary phrasing.
So if ajacksified has 0 points then ajacksified++ for reviewing this pull request, the phrasing was:
"ajacksified has 1 points, one of which is for reviewing this pull request."
Now it is:
"ajacksified has 1 point for reviewing this pull request."

Thanks for contributing!

@ajacksified please publish? I no longer have publish access.

@ajacksified disregard, it's working now.

Published v1.2.6


Doubletap problem [BUG]

Config used:
https://www.mediafire.com/file/yvln55q1uzxpz8h/scout_hvh.fw/file
Description:
My doubletap forces it to load all the time, so when I shoot or click the dash key it just doesn't work as it was supposed to, this makes it impossible for me to use doubletap
Steps to reproduce:
try using doubletap

I've noticed that this bug only happens when i die, and the only way to fix it is reinjecting the cheat. Sadly, i couldn't find what causes it, but its definitely some peace of code just constantly running the recharge function

I've no idea what this issue post is about, please record a video of the issue you're trying to describe.

I've no idea what this issue post is about, please record a video of the issue you're trying to describe.

Whenever I respawn the recharge breaks
https://imgur.com/a/L4dkQdd

same problem.


VeloKey_V1 locks up

VeloKey_V1 locks up.  Seems to software as vk_display test can run for hours without locking up.

have you performed a static analysis of RAM usage? or perhaps periodically
printing free_ram() periodically?
On Mon, Feb 15, 2016 at 10:45 PM, Justin Shaw<EMAIL_ADDRESS>wrote:

VeloKey_V1 locks up. Seems to software as vk_display test can run for
hours without locking up.
—
Reply to this email directly or view it on GitHub
https://github.com/wyolum/VeloKey/issues/4.

On the hardware side, try adding a large (10uF  ~ 47uF) cap across the M0 power supply pins to take care of the occasional supply brownout, or a 100nF cap to take care of noise.

Hard to test when it is intermittent.  Right now it seems to be working fine.

Figured it out.  When there is no bluetooth link it locks up.  Need to check bt before writing to EZKey

Looks like we need to monitor L2 on the EZLink for a 4 Hz sq wave.  This is the signal that a link is made.
https://learn.adafruit.com/introducing-bluefruit-ez-key-diy-bluetooth-hid-keyboard/pinouts

Successful testing connecting EZ-Key L2 --> A4.  Please update schematic @Anool

Connected EZKey L2 to M0 Pin A4

Connected EZKey L2 to M0 Pin A4

Fixed in SW.  Lock up occurs when trying to use BlueFruit when there is no link.   We now wait for link before starting BF serial.


Incompatibility between keras and tf.keras for layer.build

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Google Colab
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): 1.13.0rc1
Python version: 3.6
Bazel version (if compiling from source): No
GCC/Compiler version (if compiling from source): No
CUDA/cuDNN version: No
GPU model and memory: No

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
Here is the code below which should work (it works with keras-team/keras).
Describe the expected behavior
The code should run as expected, instead, we get the error message below. Note that changing the flag at the begining of the script makes the code work.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
use_tf_keras = True
if use_tf_keras:
    from tensorflow.keras.layers import Layer, Dense
    from tensorflow.keras import backend as K
    from tensorflow.keras import Sequential
else:
    from keras.layers import Layer, Dense
    from keras import backend as K
    from keras import Sequential

class MyLayer(Layer):

  def build(self, input_shape):
    print(type(input_shape))
    input_dim = input_shape[-1]
    output_dim = input_shape[-1] / 2

    self.kernel = self.add_weight(shape=(input_dim, output_dim),
                                  name='kernel',
                                  initializer='ones')
    super().build(input_shape)

  def call(self, inputs):
    return K.dot(inputs, self.kernel)

  def compute_output_shape(self, input_shape):
    input_shape = list(input_shape)
    input_shape[-1] = input_shape[-1] // 2
    return input_shape

model = Sequential()
model.add(Dense(8, input_shape=(20, 20)))
model.add(MyLayer())

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/resource_variable_ops.py:435: colocate_with (from tensorflow.python.framework.ops) is deprecated and will be removed in a future version.
Instructions for updating:
Colocations handled automatically by placer.
<class 'tensorflow.python.framework.tensor_shape.TensorShapeV1'>
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-2-255eda5c5005> in <module>()
     32 model = Sequential()
     33 model.add(Dense(8, input_shape=(20, 20)))
---> 34 model.add(MyLayer())

/usr/local/lib/python3.6/dist-packages/tensorflow/python/training/checkpointable/base.py in _method_wrapper(self, *args, **kwargs)
    440     self._setattr_tracking = False  # pylint: disable=protected-access
    441     try:
--> 442       method(self, *args, **kwargs)
    443     finally:
    444       self._setattr_tracking = previous_value  # pylint: disable=protected-access

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/sequential.py in add(self, layer)
    178       # If the model is being built continuously on top of an input layer:
    179       # refresh its output.
--> 180       output_tensor = layer(self.outputs[0])
    181       if isinstance(output_tensor, list):
    182         raise TypeError('All layers in a Sequential model '

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py in __call__(self, inputs, *args, **kwargs)
    536       if not self.built:
    537         # Build layer if applicable (if the `build` method has been overridden).
--> 538         self._maybe_build(inputs)
    539         # We must set self.built since user defined build functions are not
    540         # constrained to set self.built.

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py in _maybe_build(self, inputs)
   1601     # Only call `build` if the user has manually overridden the build method.
   1602     if not hasattr(self.build, '_is_default'):
-> 1603       self.build(input_shapes)
   1604
   1605   def __setattr__(self, name, value):

<ipython-input-2-255eda5c5005> in build(self, input_shape)
     15     print(type(input_shape))
     16     input_dim = input_shape[-1]
---> 17     output_dim = input_shape[-1] / 2
     18
     19     self.kernel = self.add_weight(shape=(input_dim, output_dim),

TypeError: unsupported operand type(s) for /: 'Dimension' and 'int'

if using keras-team/keras, we get:
<class 'tuple'>

The issue is that Dimension only defines a __div__, not __rdiv__ (or __truediv__/__rtruediv__):
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/framework/tensor_shape.py#L455
I think adding __rdiv__ will fix the issue of TypeError: unsupported operand type(s) for /.
However, in the above code in tensorflow, it also mentioned that __div__ is deprecated (in favor of __floordiv__ or //). Actually, changing:
output_dim = input_shape[-1] / 2 to output_dim = input_shape[-1] // 2 works.
I think it probably makes sense to change / to //?
Or, maybe it also makes sense to explicitly thrown out a better error message in __div__/__rdiv__?

Created a PR #25821 to print a better error message in case the operation is not supported.

Closing this issue since the associated PR has been merged.
Also can see clear error message with latest TF (tested with tf-nightly 1.15.0-dev201907250)
Thanks!


Alert admins when item has been depositing for more than 48 hrs.

For when there is time.....
Some items are completing accessioning, but H2 doesn't know about it so they remain "Depositing..." and are not editable.
Conversation from slack:
Andrew Berger
https://stanfordlib.slack.com/archives/C69UZCJ8M/p1693501538236339?thread_ts=1693402344.675239&cid=C69UZCJ8M
I wonder if it would be useful to have an alert that lists items that have been “depositing” for over a certain number of days. The big globus deposits so far have been 1-2 days, probably if something is depositing for more than 2 days it’s worth a look.
We have an alert like this based on workflow status but we can’t use that here because the workflows show all the steps complete, it’s just H2 doesn’t hear about it.
Mike Giarlo
https://stanfordlib.slack.com/archives/C69UZCJ8M/p1693502179780759?thread_ts=1693402344.675239&cid=C69UZCJ8M
That might be the sweet spot? We'd need to record when an item entered the depositing state, which isn't a huge change.

this is meant as a tool for helping to debug https://github.com/sul-dlss/happy-heron/issues/3297 (and to automatically find occurrences of it for remediation, since we currently only find them when people notice things stuck in the Depositing state)

#3391 adds an audit job that runs hourly.  it looks for any depositing work that's actually done accessioning, and automatically corrects the state in H2, as well as sending a honeybadger alert to let us know about the issue.
we might be able to close this ticket since #3297 is about investigation/tracking?  PR #3391 doesn't do exactly what this ticket asks for, but it might actually be slightly more useful, since it sends more timely alerts and auto-fixes the bad states it finds?

Agreed @jmartin-sul . I'm closing this ticket.


Doesn't handle autocompleted content elegantly on chrome

When a user selects a given option from an autocomplete menu in chrome, it doesn't validate the result, just the text up to the point at which the user selected the autocomplete option (using the tab key, this does not happen when the enter key is used to select the content). The user must then type to get validation.

This actually seems to be impossible. I can't figure out how to listen for that tab keypress in such a way that the input in focus receives the event.


go get with triple dot  doesn't work with 1.10.6 and 1.11.3

What version of Go are you using (go version)?

$ go version
go version go1.10.6 linux/amd64

Does this issue reproduce with the latest release?
Yeah, it only happens on latest versions, 1.10.6 and 1.11.3.

What did you expect to see?
The command should succeed.
It succeeds with previous versions, e.g. go 1.11.2.
What did you see instead?
package github.com/kubernetes-sigs/cri-tools/...: github.com/kubernetes-sigs/cri-tools/...: invalid import path: malformed import path "github.com/kubernetes-sigs/cri-tools/...": double dot

Thanks for the report.
This is #29241, so I'm closing this in favour of the older thread.

@ALTree Thanks for the pointer!


Insert index property on array processing

Is there a way to get index of inserted item when we work with array? As I saw in the code you just run over array with for each without index referencing.
The index property could be useful e.g. in add distinct dynamic id (div0, div1, div2...)

I'm not sure how this will work, without making major changes to the plugin (I'd have to add a property you could bind to, only if it was an array. Confusing). Simplest way to do this, add the index to each item yourself before you call the templating plugin.


feat: add user vat id

What are the relevant tickets?

Closes https://github.com/mitodl/mitxpro/issues/2762
Description (What does it do?)

Adds user vat id.
How can this be tested?

Will add once we get this Field to QA

I am not able to refresh the schema. Also, getting an error when I try to test the models locally. Is there anything that I am missing?


Support multiple ip addresses per host name

A common case for operations is to use DNS for load balancing and failover, mapping a single host name to multiple ips.
Currently, CassandraHost uses InetAddress.getByName(), which gets only on of the ips.
I suggest using InetAddress.getAllByName() (apparently it should be called outside of CassandraHost constructor) so that every host name in a connection string passed to CassandraHostConfigurator potentially gives rise to multiple instances of CassandraHost.
A nice-to-have is to continue calling InetAddress.getAllByName() periodically in order to detect removed/added ips (this is important for applications running 24/7 for weeks).

DNS LB is a legitimate approach (as is dedicated hardware/software LB). In this case - some general external load balancing - you would want to balance the initial request of a 'seed node' (different from cassandra's concept of such) in order to deduce the ring topology for the cluster.
I have no interest in supporting general-purpose multi-homing at the host level as that would involve a whole sale re-write of existing LB and failover plumbing for not a lot of gain (if I am reading this correctly?). We make a lot of assumptions on take-down and failover that rely on this one-to-one idiom.
What would be interesting is something that did this upstream and just pushed through the discovered list into CHC in the normal flow of events. Not quite sure how this would be called in configuration hook order, but there would be more room to manuever there. Thoughts?

Turned out I can use Hector auto-discovery instead of getAllByName() - it does not provide exactly the same level of faut-tolerance, but is good enough.


Cloud ML Serving issue - input and filter must have the same depth: 1 vs 3

When following the instructions under "Cloud ML Serving" on this page (server path), the upload-model.py call works, but the second command (call to process-cloud.py) fails.
The response returned from request.execute()  is a key "error" with value:
Prediction failed: Exception during model execution: AbortionError(code=StatusCode.INVALID_ARGUMENT, details="input and filter must have the same depth: 1 vs 3 [[Node: generator/encoder_1/conv/Conv2D = Conv2D[T=DT_FLOAT, _output_shapes=[[1,128,128,64]], data_format="NHWC", padding="VALID", strides=[1, 2, 2, 1], use_cudnn_on_gpu=true, _device="/job:localhost/replica:0/task:0/cpu:0"](generator/encoder_1/conv/Pad, generator/encoder_1/conv/filter/read)]]
Wondering if anyone has insights what may be going wrong here.

Resolved: Was passing a grayscale image. Ensure images being passed to the service are PNGs with 3 channels.

passing a PNG with 3 channels did not help me. What else could be the reason? Any help appreciated!

Hi R-Miner! Have you resolved your error already? Been experiencing the same error right now. :)


C# code unusable after merge of #18 and #20

Changes introduced by @scholtz and merged by @ph4r05 in PRs #18 and #20 turned C# sample code unusable. IMO these changes should be reverted and any further changes to C# codebase should be reviewed by someone familiar with .NET tooling.
Problems in PR #18

as @darinkes correctly pointed out this change has broken validation of certificate files from data directory
introduces dependency on AGPL licensed iTextSharp which IMO should not be used in MIT licensed project
does not correctly set project references and makes it impossible to build the project without manual tweaking
information printed to the console cannot be easily understood without reading the code first

Problems in PR #20

does not correctly set project references and makes it impossible to build the project without manual tweaking
information printed to the console cannot be easily understood without reading the code first

I first wanted to open new PR and fix problems mentioned above but then gave up because of lack of free time and lack of will to deal with introduced code formatting.

Hmm this is unfortunate. I don't have time for managing C# branch and ideally it should be in the separate repository. I will revert #18 and #20 for now.


"helm secrets clean ."  does not work

After decrypting and then cleaning with '.' as directory does not work.
➜  helm-secret git:(master) ✗ ls -l
total 8
drwxr-xr-x  7 abdul  staff   224 Jun  3 15:27 nginx
-rw-r--r--  1 abdul  staff  2439 Jun  3 17:41 secret.yaml
➜  helm-secret git:(master) ✗ helm secrets dec secret.yaml
Decrypting secret.yaml
➜  helm-secret git:(master) ✗
➜  helm-secret git:(master) ✗ ls -l
total 16
drwxr-xr-x  7 abdul  staff   224 Jun  3 15:27 nginx
-rw-r--r--  1 abdul  staff  2439 Jun  3 17:41 secret.yaml
-rw-r--r--  1 abdul  staff   118 Jun  3 17:57 secret.yaml.dec
➜  helm-secret git:(master) ✗
➜  helm-secret git:(master) ✗ helm secrets clean .
➜  helm-secret git:(master) ✗
➜  helm-secret git:(master) ✗ ls -l
total 16
drwxr-xr-x  7 abdul  staff   224 Jun  3 15:27 nginx
-rw-r--r--  1 abdul  staff  2439 Jun  3 17:41 secret.yaml
-rw-r--r--  1 abdul  staff   118 Jun  3 17:57 secret.yaml.dec
➜  helm-secret git:(master) ✗

@raufkk I found the issue. Current release approach that all secret files have to meet pattern: https://github.com/zendesk/helm-secrets/blob/master/secrets.sh#L441. Unfortunately, we do not check this constrains during decryption but when we removed files we search for file secrets*.yaml https://github.com/zendesk/helm-secrets/blob/master/secrets.sh#L441 I will correct it this week.


CMakeUserPresets regression

Brief Issue Summary
CMakeUserPresets is no longer working when extending an existing configure preset.
Let's take this very short example:
CMakePresets.json file:
{
	"version": 6,
	"configurePresets": [
		{
			"name": "project",
			"binaryDir": "${sourceDir}/_build_${presetName}"
		}
	]
}

and this CMakeUserPresets.json file:
{
	"version": 6,
	"configurePresets": [
		{
			"name": "user project",
			"inherits": [
				"project"
			]
		}
	]
}

When I run cmake --list-presets I correctly get:
Available configure presets:

  "user project"
  "project"

Since a recent update of vccode-cmake-tools, I don't get my user project anymore.
As a reminder, this is taken from cmake documentation:
If CMakePresets.json and CMakeUserPresets.json are both present, CMakeUserPresets.json implicitly includes CMakePresets.json, even with no include field, in all versions of the format.
Although I did try to add an include of CMakePresets in my CMakeUserPresets file, it doesn't help.
Additional Information
I'm on v1.19.35

Could you test this vsix?
cmake-tools.zip
This should (I believe), fix the regression.

It doesn't look like a vsix file, how should I install it?

@christophe-calmejane Ah, my apologies, some people I've already given the instructions and some I haven't.
Steps:

Download the file.
Change the extension from .zip to .vsix (Github doesn't allow dropping of .vsix)
Install manually in VSCode extensions pane:

Oh yes sorry I didn't know that. (But I just dropped the vsix file to the extension panel and it correctly replaced my version with yours).
I can confirm it both fixes this issue, and that #3522 is also working fine.


zh-hans and zh-hant cannot take effect

Found a bug? Please fill out the sections below.
Issue Summary
I found that there is a problem with localization in our project. The "-" in the two folders of zh-hans and zh-hant should be changed to "_", otherwise it will not take effect, such as "zh-hans" -> "zh_hans "
Steps to Reproduce
Included in the sandbox example, also appears not to use zh-hans
Technical details
Python 3.8.6

Django version: 3.2.12

Oscar version: 3.1

Yes, I found the same problem.


Scheduled job to send message to web socket broker will cause incorrect warning about "try to close but not current span"

A simple scheduled job sending message to the web socket message broker will trigger an incorrect warning telling: "Tried to close span but it is not the current span: ..."
I see the inner interceptor already clear the span but the outer still compare the created one with null and think they are different and warn.
Should the check skips if the current span is null?

I setup a test case:
https://github.com/jiangzhe/spring-cloud-tracing-test-case
You can run it and check the console logging:
2018-02-01 11:31:12.954  WARN [tracingtest,,,] 12351 --- [MessageBroker-1] o.s.cloud.sleuth.util.ExceptionUtils     : Tried to close span but it is not the current span: [Trace: d5649fc3efb15397, Span: d5649fc3efb15397, Parent: null, exportable:false].  You may have forgotten to close or detach null


[feature request] .so stager for linux

it would be incredibly useful when deploying bootkits/rootkits if a .so stager was available for the Linux/python payload, would it be possible to create one?

Could you give some more details on how this would look to facilitate .so to work with rootkits? deployment method etc?

some rootkits (EvilAbigail) takes payloads in .so format which is easy
to do with metasploit, but it would be nice to do the same thing with
Empire.
On 01/16/2017 10:35 AM, Alexander Rymdeko-Harvey wrote:

Could you give some more details on how this would look to facilitate
.so to work with rootkits? deployment method etc?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adaptivethreat/Empire/issues/434#issuecomment-272893474,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIqhyJNKuCFFjraSi58fSqYZk9nGgRvqks5rS45EgaJpZM4LkBvN.

@thesle3p i will see what the guys think. Your looking for a Shared Object that is injectable? Never played with that tool set, let me do some research on this.

Not needed figured out a way to get it to work, just had to modify the make
file.
On Feb 1, 2017 9:27 AM, "Alexander Rymdeko-Harvey"<EMAIL_ADDRESS>wrote:

@thesle3p https://github.com/thesle3p i will see what the guys think.
Your looking for a Shared Object that is injectable? Never played with that
tool set, let me do some research on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adaptivethreat/Empire/issues/434#issuecomment-276670410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIqhyDwW4wia7P7fyQpzxereqCbyqQ5hks5rYJZdgaJpZM4LkBvN
.


Improve the ReportImage parsing

Attempt to parse the unique image details using a few more fields in the pod object along with some regexes.
Also added an ignore-not-running option so the end user can configure whether they want to capture image details from pods that are not running yet.

You bet!


feat(import): Remove ReadMore import from guides/deploy/deno.mdx cause usage got removed in #9949

Description (required)
Remove ReadMore import from guides/deploy/deno.mdx cause usage got removed in #9949
I'm not sure if it's really necessary. I guess that Astro builds the site without the import, idk...

Related issues & labels (optional)

#9949
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

en/guides/deploy/deno.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Store binary data as-is for PostgreSQL

Use the "E" prefix to mark the input as escaped binary data, and do not unescape when reading the data back from the DB.
Fixes #675

heh, najs trick from your pocket! ... 'E' is a Postgre's thing, I guess? :green_heart:  :cupid: :green_heart:

Yes, 'E' is connected to 'bytea' for PostgreSQL.  Old fashioned escaping with octal escape sequences did not require any prefix, but HEX encoded escape sequence requires the 'E' prefix.  Without the 'E' prefix, the string is stored directly without being unescaped as a hex sequence.
This was introduced in PG 8.2.  How old versions of PG do we support?  The README does not say anything about that.

we sure supported older than AR itself ... there's semi-support for Amazon's Redhift, but I mostly "blind" fixed some reported requests (without running against Redshift), which is based on PostgreSQL 8.0.2 ...


Improved logging in python

Reworked the way developer logging happens when using the openweave wrappers for python. With this change, all WeaveLog...() calls in C++ code result in a callback to a logging function in python.  The default implementation of this function directs log messages to a standard python logger object associated with the python WeaveStack object.  By default, the python logger is configured to output messages to stdout, in a format identical to that used by the C++ code.  However, developers are free to reconfigure the logger object, or replace it altogether, giving them complete control over the handling of C++ generated logs in python applications.

Added support for dynamic logging behavior.  Modified the standard implementation of nl::Weave::Logging::Log() so that the default logging behavior can be overridden at runtime. Applications can now use the SetLogFunct() function to specify a pointer to a function to be called for every logged message.  Setting the function pointer to NULL (the default value) results in the original behavior of logging to stdout via printf().

Latest version has some minor changes to make it easier for applications to setup customize logging.

Overall it looks perfect!!
Currently during CI validation, we use make -f Makefile-Standalone TIMESTAMP=1, then weave c++ log with timestamp would automatically go to stdout
the test case is openweave-core/src/test-apps/happy/tests/standalone/pairing/test_weave_pairing_01.py, the log is in /tmp/xxxxxWEAVE-PAIRING-MOBILEnode02.out
With your change, the weave c++ log message has piped to python, but at default, timestamp is disabled. Could you enable timestamp at default,
def init(self, datefmt=None, logModule=True, logLevel=False, logTimestamp=True, logMSecs=True)
https://github.com/openweave/openweave-core/pull/556/commits/540be9be4452ba108f22860656d761c71b4c473c#diff-870dcb3a4097be4f5a8c1d196c0db469R119
Or add
logFormatter = WeaveLogFormatter(logLevel=True, logTimestamp=True) in
https://github.com/openweave/openweave-core/blob/master/src/test-apps/happy/lib/WeaveDeviceManager.py
Thanks

Could you enable timestamp at default

@yunhanw-google I cannot do that, as that would enable timestamps everywhere, including in the device manager shell.
I have pushed another commit that enables timestamps for the pairing tests.

Codecov Report

Merging #556 into master will decrease coverage by 0.01%.
The diff coverage is 30.76%.

@@            Coverage Diff             @@
##           master     #556      +/-   ##
==========================================
- Coverage   54.17%   54.15%   -0.02%
==========================================
  Files         331      331
  Lines       57637    57657      +20
==========================================
+ Hits        31223    31227       +4
- Misses      26414    26430      +16

Impacted Files
Coverage Δ

src/lib/support/logging/WeaveLogging.cpp
43.90% <30.76%> (-32.29%)
:arrow_down:

src/lib/profiles/security/WeaveCert.cpp
88.96% <0.00%> (+0.45%)
:arrow_up:

Continue to review full report at Codecov.

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

Could you enable timestamp at default

@yunhanw-google I cannot do that, as that would enable timestamps everywhere, including in the device manager shell.
I have pushed another commit that enables timestamps for the pairing tests.

Yep, fully agree on this. Just review and validate the code, all looks good, thank you!


UI of Fevicon Fetcher Website

Hey @TusharKesarwani  , an SSOC'23 contributor here.
UI of Fevicon Fetcher project is too boring as shown below So,
I would like to improve the UI of Fevicon Fetcher Website if you assign it to me.

@TusharKesarwani Kindly assign me this issue under SSOC 2.O


Remote option

Looks good, thanks. Merge away and redeploy!

Pushed to production - requiring a bit of jiggery pokery

Great job

Cheers. Great job on the remote icon @testbrian I like how it looks.


Does this support Linux?

Looks like this is possibly unsupported on Linux?
Looking in the bin directory, I do see sdcli, however it looks like it's just a luncher for sql developer:
# cat sdcli
#!/bin/bash

#=============================================================================
#  Launcher for Oracle SQL Developer
#  Copyright (c) 2005, Oracle. All rights reserved.
#=============================================================================

. "sqldeveloper"

#-----------------------------------------------------------------------------
#  product-specific function overrides
#-----------------------------------------------------------------------------
GetFullProductName()
{
    echo "Oracle SQL Developer"
}

GetShortProductName()
{
    echo "SQL Developer"
}

Only tested on Windows 7 with Oracle SQL Developer v4.0.3.
I don't have any Linux box with SQL Developer installed so I can't check it but I made a quick research and everything should be OK in Linux, just add sdcli with the full path to the settings section
If that fails, run sdcliwith the full path from the console to check if its available and working


Result from serialized json

Hi! I watched your talk on nordicjs, it was inspiring. I've been using it for some of my vue projects.
I'm currently using it both on the server and client through tRPC. When tRPC serializes the result, which from what I've understood is a class with specific methods, it creates a json struct which it sends down to the client.
Therefore, I would need to turn something like {"tag": "Ok", "value: "[...]"} into a Result class on the client, if that makes sense. Do you think there's a valid use case for this?

Hi! Isn't https://swan-io.github.io/boxed/serializer what you are looking for?

Thanks, missed that!


Soul Readme update

Feature Request

Is your feature request related to a problem? Please describe
A clear and concise description of what the problem is. Ex. I have an issue when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context

closed by https://github.com/dromara/soul/pull/425


chore: update dependencies with security issues

There's a security issue with handlebars. I've tried updating the packages that depend on handlebars:

lerna
jest
rollup

I think ta bad version is still getting included.
No tests or docs updates will be required.

Closing. There's a bug with the new version of jest that's causing the tests to hang.


Remove need for static_visitor class

It seems the only reason for the static_visitor class is the result_type typedef for its derived classes. I have just created a branch 'result_of' that has some changes that remove the need for the static_visitor class.

landed in 3cc2d708e0552ba4ebce11d4d67f798813f15aa2, followup in #35


(DevX) Create lock file to manage asset list image cache

What is the purpose of the change:
Previously, we disabled caching to avoid token image conflicts when switching environments. However, since waiting for image downloads to start the server is time-consuming and tedious, we propose creating a lock file inside the generated folder. This lock file will store the current asset list hash and override the cache if the hash changes.
Linear Task
https://linear.app/osmosis/issue/FE-1228/create-lock-file-to-manage-asset-list-images-cache
Testing and Verifying

[ ] Asset list is generated correctly

How are token images persisted across builds with a lockfile? They're still downloaded each time, just from the locked asset list?

In the production build, images will always be downloaded. In the development environment, images will only be downloaded if the asset list commit has changed or if the file is missing


z80 vs "gbz80"

http://www.z80.info/z80gboy.txt
Mention the author, too (references)

@avivace Is this ticket resolved, then?

Yes! Thanks for pinging me on this


Update to Creek 0.4.1-SNAPSHOT

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 98.238%. Remained the same when pulling c3c2f948adcb49a1cbe7d19a514d012ac26dac9a on 0.4.1-SNAPHOT into 34eaa1c060f9124010f6828d0ffff306640f28f5 on main.


Fix for incorrect limit with remote

Hey guys, here's a fix for #43. We've continued @mlissner's great work, and fixed the tests.

Simple enough change. Thanks @DanielApt. Merge it, merge it!

Merge, please :shipit:

@sheeley Could this be merged?

@jharding, @vskarich, @timtrueman, I've got a project that's waiting on this fix. Without it, the Limit feature is totally broken. Considering this is "corejavascript" I'm pretty concerned to see this PR languish.
Can we get a merge and a release, please? I don't know about other people, but this is a major bug for my organization.

@mlissner: I haven't been keeping up with the releases, but AFAIK the other folks (who actually started this fork) have a couple of outstanding issues they want to solve before creating corejs releases of this fork: #9. Tagging folks like @jharding who aren't involved here won't really help, unfortunately, and that won't update the original typeahead package regardless.
@corejavascript/collaborators as I was added after you'd already started this, I don't feel comfortable speaking about the plans/etc. Can you help respond to @mlissner's concerns?

@mlissner There's nothing stopping you from monkey-patching or even committing it. Truth be told, at my organization our typeaheadjs library is fairly hacked up (not  by me).
We don't have end-to-end tests running right now, so it would be helpful if people would identify if they have actually tested the code by running it. If we have 3 people who can say they've done that, it would allay concerns.
This looks good to me but I haven't actually run it.

@sheeley I've fixed the whitespace diffs.
In the future it might be useful to add an editorconfig file, which should make most code editors use the same whitespace rules.

@jcrben we have been running this PR in our codebase since last week, as well as the test suite in our CI, without any problems

@jcrben We have released this feature to our beta users and they aren't reporting any issues. It's also on Twitter's typeahead.js issue tracker where several people say it's working properly: https://github.com/twitter/typeahead.js/issues/1435

If some of you want to be committers, let us know so we can ping the owner. I'm juggling too many things right now to spend too much time on it...

Thanks @jcrben!

Tracking this for release soon. See #55


pure-fb-openmetrics deployment k8s example error

--host is now --address the example needs to be updated. https://github.com/PureStorage-OpenConnect/pure-fb-openmetrics-exporter/blob/main/examples/config/k8s/pure-fb-exporter-deployment.yaml

This has been fixed


Upgrade 0.9.8.

Pull Request Template
Description

Upgrade to 0.9.8.
ORML submodule update to latest master.
Remove template pallet folder.
Run cargo +nightly fmt --all in directory.

Type of change
Please delete options that are not relevant.

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

Checklist:
Make sure these boxes are checked!

[x] You have the latest version of rustfmt installed

$ rustup component add rustfmt

[x] You ran cargo fmt on the code base before submitting.
[x] fmt is styled according to rustfmt.toml file.
[ ] Documentation is updated.
[ ] Tests have been written/updated.
[ ] All CI jobs completed successfully - can be closed off after submitting a PR.

Thank you for your contribution to Standard Protocol! 🎉

Subwasm diff output attached, large output of changes because of the removal of Template and RandomnessCollectiveFlip pallets. Transaction version has been adjusted to reflect pallet removals. Diff also includes changes from 0.9.7 upgrade - #45.
subwasm-diff-output.txt
Local run output with fork-off-substrate tool:
2021-08-05 14:14:18 🙌 Starting consensus session on top of parent 0x39eaa948424c46166cb6d2d1da0f01a7b088cd4375cfb126568d9e78a38b16bd
2021-08-05 14:14:18 ⚠ System declares internal migrations (which *might* execute), setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Vault, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Oracle, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Market, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for AssetRegistry, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Currencies, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Tokens, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Tips, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Bounties, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Treasury, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Identity, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Elections, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for TechnicalMembership, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for TechnicalCommittee, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Council, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Democracy, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Scheduler, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Historical, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Session, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Indices, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for AuthorityDiscovery, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Authorship, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ⚠ Staking declares internal migrations (which *might* execute), setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ⚠ Offences declares internal migrations (which *might* execute), setting storage version to <wasm:stripped>
2021-08-05 14:14:18 have 0 deferred offences, applying.
2021-08-05 14:14:18 ✅ no migration for ImOnline, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Grandpa, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Babe, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Sudo, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for TransactionPayment, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Balances, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 ✅ no migration for Timestamp, setting storage version to <wasm:stripped>
2021-08-05 14:14:18 🎁 Prepared block for proposing at 31 [hash: 0xfecdc5700161f6127f8e3c5936e08442099e8d174f594579f952069623179d91; parent_hash: 0x39ea…16bd; extrinsics (1): [0x02c1…3a29]]
2021-08-05 14:14:18 🔖 Pre-sealed block for proposal at 31. Hash now 0x88d31589f769029c9238cde543ce128372e5df146023aca0738ce23d42fececa, previously 0xfecdc5700161f6127f8e3c5936e08442099e8d174f594579f952069623179d91.
2021-08-05 14:14:18 ✨ Imported #31 (0x88d3…ceca)


Find package for table like printout

Current output with tabs not really working

Using tabulate and colorama

https://github.com/elsewhat/nft-crypto-taxes/commit/3a55d57de950cc2f5ad7860f61d086dc3a4f7645


Broken FAQ link shown when function deploy fails

I could not consistently repro this, but the error did repeat a few times on May 13.
Log below.
The link shown at the end seems broken, and redirects to the general azure blog.
Link: https://blogs.msdn.microsoft.com/appserviceteam/2017/08/08/faq-app-service-domain-preview-and-custom-domains
11:26:45 PM psapmdemo: Creating zip package...
11:26:47 PM psapmdemo: Starting deployment...
Error:  404 Web Site not found.
You may be seeing this error due to one of the reasons listed below :

 * Custom domain has not been configured inside Azure. See how to map an existing domain [https://docs.microsoft.com/en-us/azure/app-service-web/app-service-web-tutorial-custom-domain] to resolve this.
 * Client cache is still pointing the domain to old IP address. Clear the cache by running the command ipconfig/flushdns.

Checkout App Service Domain FAQ [https://blogs.msdn.microsoft.com/appserviceteam/2017/08/08/faq-app-service-domain-preview-and-custom-domains/] for more questions.
11:41:55 PM psapmdemo: Creating zip package...
11:41:57 PM psapmdemo: Starting deployment...
Error:  404 Web Site not found.
You may be seeing this error due to one of the reasons listed below :

 * Custom domain has not been configured inside Azure. See how to map an existing domain [https://docs.microsoft.com/en-us/azure/app-service-web/app-service-web-tutorial-custom-domain] to resolve this.
 * Client cache is still pointing the domain to old IP address. Clear the cache by running the command ipconfig/flushdns.

Checkout App Service Domain FAQ [https://blogs.msdn.microsoft.com/appserviceteam/2017/08/08/faq-app-service-domain-preview-and-custom-domains/] for more questions.

The error (and link) is coming directly from Azure. Closing as won't-fix since it doesn't seem consistent and I haven't heard other users report it. Feel free to re-open if you get consistent repro steps.


Update preact.mdx

fix doc typo: use pnpm exec astro add preact to run astro cli, instead of pnpm astro add preact

Description (required)
Indeed, if you run pnpm astro add preact, you get the following error :
$ pnpm astro add preact

><EMAIL_ADDRESS>astro C:\Users\Utilisateur\radio_jaune_2024
> astro "add" "preact"

'astro' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
 ELIFECYCLE  Command failed with exit code 1.

Related issues & labels (optional)

Closes #
Suggested label:

Environment

Git bash for windows,
astro 4.2.4
pnpm 8.14.1

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Important update. an important issue
Hello, as I was setting up a new astro project, I had to execute pnpm dlx to execute astro add preact.
But after successfully adding preact astro integration using pnpm dlx, I experienced an issue:

I then tried to add another package, lucide-preact
to do that,  I executed pnpm add --save lucide-preact
I ended up with the following error :

$ pnpm add --save lucide-preact
 WARN  Moving astro that was installed by a different package manager to "node_modules/.ignored"
 WARN  Moving preact that was installed by a different package manager to "node_modules/.ignored"
 EPERM  EPERM: operation not permitted, rename 'C:\Users\Utilisateur\my_project_here\node_modules\astro' -> 'C:\Users\Utilisateur\my_project_here\node_modules\.ignored\astro'

Now, to solve that, I had to roll back the astro preact integration installation, by :

running  :

rm -fr ./node_modules/
pnpm remove @astrojs/preact preact

I di not change my astro.config.mjs :

import tailwind from "@astrojs/tailwind";
import icon from "astro-icon";
import { defineConfig } from "astro/config";

import preact from "@astrojs/preact";

// https://astro.build/config
export default defineConfig({
  site: "https://astro-moon-landing.netlify.app/",
  integrations: [tailwind(), icon(), preact({ compat: true })]
});

to :

import tailwind from "@astrojs/tailwind";
import icon from "astro-icon";
import { defineConfig } from "astro/config";

// https://astro.build/config
export default defineConfig({
  site: "https://astro-moon-landing.netlify.app/",
  integrations: [tailwind(), icon()]
});

Then I manually installed the astro preact integration, and the lucide-preact package :

pnpm add @astrojs/preact preact
pnpm add @preact/compat
pnpm add lucide-preact

Note that after that, I tested creating a bare new astro project, to try and use pnpm exec instead of pnpm dlx, and that confirmed to se astro cli with pnpm, one should use pnpm exec astro:
Utilisateur@Utilisateur-PC MINGW64 ~/pr_test/retrograde-ring
$ pnpm exec astro add preact
- Resolving packages...
√ Resolving packages...
05:03:04
  Astro will run the following command:
  If you skip this step, you can always run it yourself later

 ╭──────────────────────────────────────────────────╮
 │ pnpm add<EMAIL_ADDRESS><EMAIL_ADDRESS>│
 ╰──────────────────────────────────────────────────╯

? Continue? » (Y/n)Y
√ Continue? ... yes
- Installing dependencies...
√ Installing dependencies...
05:03:25
  Astro will make the following changes to your config file:

 ╭ astro.config.mjs ─────────────────────────────╮
 │ import { defineConfig } from 'astro/config';  │
 │                                               │
 │ import preact from "@astrojs/preact";         │
 │                                               │
 │ // https://astro.build/config                 │
 │ export default defineConfig({                 │
 │   integrations: [preact()]                    │
 │ });                                           │
 ╰───────────────────────────────────────────────╯

? Continue? » (Y/n)Y
√ Continue? ... yes
05:03:32
   success  Added the following integration to your project:
  - @astrojs/preact
05:03:32
  Astro will make the following changes to your tsconfig.json:

 ╭ tsconfig.json ─────────────────────────────╮
 │ {                                          │
 │   "extends": "astro/tsconfigs/strictest",  │
 │   "compilerOptions": {                     │
 │     "jsx": "react-jsx",                    │
 │     "jsxImportSource": "preact"            │
 │   }                                        │
 │ }                                          │
 ╰────────────────────────────────────────────╯

? Continue? » (Y/n)Y
√ Continue? ... yes
05:03:34
   success  Successfully updated TypeScript settings

Utilisateur@Utilisateur-PC MINGW64 ~/pr_test/retrograde-ring
$ pnpm add --save preact @preact/compat lucide-preact
Progress: resolved 0, reused 1, downloaded 0, added 0
Progress: resolved 3, reused 3, downloaded 0, added 0
Progress: resolved 209, reused 185, downloaded 0, added 0
Packages: +2
++
Progress: resolved 479, reused 444, downloaded 0, added 1
Progress: resolved 479, reused 444, downloaded 0, added 2
Progress: resolved 479, reused 444, downloaded 0, added 2, done

dependencies:
+ @preact/compat 17.1.2
+ lucide-preact 0.314.0

Done in 6.9s

The astro version I used at the time of my test is ^4.2.4,  :
$ cat package.json
{
  "name": "retrograde-ring",
  "type": "module",
  "version": "0.0.1",
  "scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "build": "astro check && astro build",
    "preview": "astro preview",
    "astro": "astro"
  },
  "dependencies": {
    "astro": "^4.2.4"
  }
}

My guessed explanation is that using pnpm dlx invokes npm ( npx ), while we want to use pnpm, and that's why one should use pnpm exec.
So I think it would be useful to add a warning about that point in the astro docs, for the pnpm astro projects. I would say this warning should appear at least for every astro integration commands for frameworks, like here for preact in this PR.

just squashed my 2 commits

Hi! Can you please file a docs Issue about this instead, so that others can examine what's happening here? This is not something reported by anyone else, so I'd like others to be able to verify and figure out what is happening so we can decide what, if anything, needs to change in docs.

what's

Thank you for your quick reply! I will do that with pleasure :) , thank you all astro team for that awesome project! :)

@sarah11918 there you go : https://github.com/withastro/astro/issues/9844


[BUG] rollout with non-uniform tensors no longer supported

Describe the bug
There seems to be a bug with performing a rollout when the tensordicts produced do not have the same shape. The rollout used to produce LazyStackedTensorDict, but it currently fails to stack them. It's possible to fix this issue by using the context manager: python with set_lazy_legacy(True):
When I was using the version below:
TorchRL:
git+ssh://git@github.com/pytorch/rl.git@7cd6a181020ba2d0ec420d7c3a92c8d689be6bd1#egg=torchrl
TensorDict:
tensordict-nightly==2024.3.20
To Reproduce
Steps to reproduce the behavior.
Please try to provide a minimal example to reproduce the bug. Error messages and stack traces are also helpful.
Please use the markdown code blocks for both code and stack traces.
import torchrl

env = make_env() # some env that produces sequential data

# this raises a stacking error (It works in older versions)
env.rollout()

# this works
with tensordict.utils.set_lazy_legacy(True):
    env.rollout()

Traceback (most recent call last):
  File "/Users/dtsaras/Documents/CS/circuit_gen/src/rl/mcts_policy.py", line 502, in simulate
    rollout = self.env.rollout(
  File "/opt/homebrew/Caskroom/miniconda/base/envs/c_gen/lib/python3.10/site-packages/torchrl/envs/common.py", line 2567, in rollout
    out_td = torch.stack(tensordicts, len(batch_size), out=out)
  File "/opt/homebrew/Caskroom/miniconda/base/envs/c_gen/lib/python3.10/site-packages/tensordict/base.py", line 388, in __torch_function__
    return TD_HANDLED_FUNCTIONS[func](*args, **kwargs)
  File "/opt/homebrew/Caskroom/miniconda/base/envs/c_gen/lib/python3.10/site-packages/tensordict/_torch_func.py", line 490, in _stack
    raise RuntimeError(
RuntimeError: The shapes of the tensors to stack is incompatible.

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

Expected behavior
It's expected to return a LazyStackedTensorDict
System info
Describe the characteristic of your environment:

Describe how the library was installed (pip, source, ...)
Python version 3.10
Versions of any other relevant libraries

import torchrl, numpy, sys
print(torchrl.__version__, numpy.__version__, sys.version, sys.platform)

Additional context
Add any other context about the problem here.
Reason and Possible fixes
If you know or suspect the reason for this bug, paste the code lines and suggest modifications.
Checklist

[x] I have checked that there is no similar issue in the repo (required)
[x] I have read the documentation (required)
[ ] I have provided a minimal working example to reproduce the bug (required) [there is no such environment to provide one]

Missed to include the versions:
0.4.0 1.26.2 3.10.13 (main, Sep 11 2023, 08:16:02) [Clang 14.0.6 ] darwin

Ok thanks that's helpful! Also, I wonder if we could create dense stacks by batching them as nested tensors instead?

Yes we can do that, I don't think we have the util to stack things as nested tensors yet though
The main issue we'll be facing is that nested tensors can only be stacked along dim 0 and rollout stacks along the last+1 dim, so it will only work for non-batched envs

I wonder if we encounter such data maybe we can automatically pad the data and return a padding mask along the dynamic dimensions. This can be the fallback when the contained tensors are nested tensors. If you think that's an option, I can look into implementing something like this after the NeurIPS deadline.

Another option is to create the nested tensor along dim 0 but "lie" with tensordict and present it as a transposed version
we'll need to patch the get set etc

Closing this as now contiguous=False will do a best intention attempt to stack what can be stacked and return non-contiguous stacks everywhere else


DBeaver: Execute SQL text generate error if the ";" delimiter together with "GO" separator is used with BEGIN/END

DBeaver - Version 21.0.2 CE
DBeaver driver: MS SQL Server  / Microsoft Driver (the new Microsoft Driver)
Operating System: Windows 7 / Windows 8.1 / Windows 10
Database Server: Microsoft SQL Express 2014, 2016, 2017
When I execute SQL Text containing both ";", "GO" and BEGIN/END, I get an error.
Seems that DBeaver do not consider BEGIN/END statements that contain statement(s) that each contain a trailing ";" charater. See TEST 6 below for an example (also read comment for TEST 3 in the importance of seperate batches when "GO" is used).
PS. The practise to place a trailing ";" character to mark end-of-statement is now something that Microsoft recommends.
My DBeaver settings (Editors -> SQL Editor -> SQL Processing -> Delimiters)
Statement delimiter: ;
  Ignore native delimiter
X Blank line i statement delimiter
X Remove Trailing query delimiter

TEST SETUP - OK (if run as script)
IF OBJECT_ID('dbo.TestTableOne', 'U') IS NOT NULL
  DROP TABLE dbo.TestTableOne;
IF OBJECT_ID('dbo.TestTableTwo', 'U') IS NOT NULL
  DROP TABLE dbo.TestTableTwo;
GO
CREATE TABLE TestTableOne(Id INTEGER, Value VARCHAR(40));
GO
INSERT INTO TestTableOne VALUES (1, 'A');
GO
CREATE TABLE TestTableTwo(Id INTEGER, Value VARCHAR(40));
GO
INSERT INTO TestTableTwo VALUES (2, 'B');
GO

TEST 1 - OK (if executed as script or statement)
Here DBeaver work ok in noticing the ";" character as statement separator. So if I place the cursor on the first line and execute, only the first line is executed. If I select all lines and execute I also correctly get two tabs (ie two result sets).
SELECT * FROM TestTableOne;
SELECT * FROM TestTableTwo;

TEST 2 - OK (if executed as script or statement)
Here DBeaver work ok in noticing the empty line as statement separator. So if I place the cursor on the first line and execute, only the first line is executed. If I select all lines and execute I also correctly get two tabs (ie two result sets).
SELECT * FROM TestTableOne

SELECT * FROM TestTableTwo

TEST 3 - OK (if executed as script), SQL ERROR (if executed as statement)
That I get an error if I try to execute these lines as a statement,  is ok I guess, since this is more like a script.
Here DBeaver should first send "SELECT * FROM TestTableOne;" to the SQL Server as one batch, then send the "SELECT * FROM TestTableTwo;" as the second batch to the SQL Server.
It is important that DBeaver don't send all the text to the SQL Server in one batch. This have no effect here, but if I have script with batch 1 creating a table and batch 2 inserting values into the table the two batches must be sent as two different batches.
SELECT * FROM TestTableOne;
GO
SELECT * FROM TestTableTwo;
GO

TEST 4 - OK (if executed as statement), SQL ERROR (if executed as script),
That I get an error if I try to execute these lines as a script,  is ok I guess, since this is more like a statement.
DECLARE @TestVal INTEGER = 1;

IF @TestVal = 1
BEGIN
  SELECT * FROM TestTableOne;
END;

TEST 5 - OK (if executed as script)
Here I have not put any ";" training characters on the statements in the BEGIN/END section.

END;
GO

TEST 6 - SQL ERROR [102] [S0001]: Incorrect syntax near 'ON' (if executed as script)
Here only differens with test (5) above, is that I have placed a trailing ";" on the SET NOCOUNT ON line.
IF OBJECT_ID('dbo.OnTestTableOneUpdate', 'TR') IS NOT NULL
  DROP TRIGGER dbo.OnTestTableOneUpdate;
GO
CREATE TRIGGER dbo.OnTestTableOneUpdate
  ON dbo.TestTableOne
  AFTER UPDATE
AS
BEGIN
  -- The use of a ";" to mark end of statement below generate an error
  SET NOCOUNT ON;

  -- TODO Do something...
END;
GO

Hello @pdanie
Yep, this is bug. A can execute the last example in mssql management studio, but not as script in DBeaver.
But I could execute this script рighlighting all the text and using ctrl+enter
CREATE TRIGGER dbo.OnTestTableOneUpdate
  ON dbo.TestTableOne
  AFTER UPDATE
AS
BEGIN
  -- The use of a ";" to mark end of statement below generate an error
  SET NOCOUNT ON;

  -- TODO Do something...
END;
GO

And I have a question about point 3.
As I can see in Query Manager DBeaver send SELECT TOP 100 * FROM TestTableOne and SELECT TOP 100 * FROM TestTableTwo after.
He combined
SELECT * FROM TestTableOne

SELECT * FROM TestTableTwo

yes.
Why do you think, that point 3 is sent as a batch?

1) You should execute the whole TEST 6 SQL text.
In real life we have SQL files that contain many batches separated with "GO" (mostly drops followed by creates). Its  really irritating to have to select and execute each batch "by hand".
2) When I execute TEST 3 (ie select all 4 rows and choose Execute SQL Script) in DBeaver I got this in the Execution Log:
Time             Type             Text                        Duration (ms) Rows
Apr-12 17:45:00  SQL/User script  SELECT * FROM TestTableOne  2             1
Apr-12 17:45:01  SQL/User script  SELECT * FROM TestTableTwo  2             1

To me it looks like it have generated 2 batches that it sent to the SQL Server.
The thing about the "GO" is that is nothing that the SQL server understand nor anything that is supported by the SQL language. It is a directive to the SQL IDE (like DBeaver, Microsoft SSMS, etc.) to chop down a SQL text in smaller chunks/batches and send each chunk/batch one after another to the SQL server.
Summary
For SQL Server the ";" is a SQL statement terminator and "GO" is a SQL batch separator. Both are needed to be handled by DBeaver and none could be ignored. Since SQL Server support the use of BEGIN/END that is something that DBeaver need to take into consideration when it decide where a statement ends.
PS. I have never seen the use of "GO" in other IDE:s than for SQL Server and Sybase ASE (nowdays I think it is named SAP ASE), but it could be used for all database brands since the "GO" is never sent to the database server.

And again, you said:

Here DBeaver should first send "SELECT * FROM TestTableOne;" to the SQL Server as one batch, then send the "SELECT * FROM TestTableTwo;" as the second batch to the SQL Server.

And we do it. DBeaver recognize GO as batch separator. As you can see in Query Manager.
Do we close the discussion on test case 3? Or tell me, please, more about how it should look like.

Sorry if I have been unclear.
The ONLY thing that is something bad, is for TEST 6 use case above. ALL other test cases are OK.
The reason I have written TEST 1 .. 6 is that I wanted to have all use cases using ";" and "GO" separators for SQL Server in one and the same support issue. So that if you adjust DBeaver for TEST 6, that all the other test cases still work ok.

@pdanie : FYI - if you change the SQL Processing Delimiters such that

Statements delimiter = "go"
Ignore native delimiter is checked

then your Test 6 runs successfully

Apparently, as of release 21.0.0, DBeaver considers the semicolon to be a "native delimiter" for MSSQL (in addition to go), which is different from past behavior.
I've found that for MSSQL connections on the most recent DBeaver versions, I need the settings configured as above:

If you don't Ignore native delimiter, it will send everything between semicolons as separate batches.  So, you can't do things such as declare variables and then reference them later.
If you ignore native delimiter but don't set the Statements delimiter to "go", you'll get "incorrect syntax near 'go'" errors.

seems the issue is fixed.
Test 6 is successfully executed as a script in 21.2.1


where are the actions set

related to https://github.com/CMSCompOps/WmAgentScripts/issues/339
the actions might be set committed somewhere in mongodb, can someone surface what collection is that ?

If you open the MongoDB, you can do the following:
> show dbs
> use <some db>
> show collections

It looks like there's a database wtc-console, but there might be no collection of "actions" yet. @vined can correct me.

related to CMSCompOps/WmAgentScripts#339
the actions might be set committed somewhere in mongodb, can someone surface what collection is that ?

Here: https://github.com/CMSCompOps/wtc-console/issues/11#issue-402870938

@vlimant What's the plan for updating the production server with the latest console? I don't have sudo access to vocms0276, and @vargasa likely doesn't either.

please ask the voc for the proper rights

Daniel left, right? Who's the new VOC?

<EMAIL_ADDRESS>;-)


mTLS in STRICT mode block additional init containers

Hi
When STRICT mode is enabled for the mTLS Istio mesh policy all traffic between Pods covered by the policy must use mTLS. This means that the Istio sidecars (istio-proxy Envoy container) must be ready before Pods can successfully communicate with each other over the network. See the Istio Security docs for much information all of this.
The issue with our app right now is that it is using an init container to run database migrations. This init container runs before the regular istio-proxy container on the Pod is ready so there is no client sidecar in place to mediate the mTLS connection with the sidecar running on the database Pod1.
Are there some configuration options within Istio that would help here?
Thanks!

This is not currently supported today

hi

This is not currently supported today
are there any plans for the implementation of such functionality?
or maybe you can suggest some workaround ?
Thanks!

https://github.com/istio/istio/issues/11130 tracks long term and has some workarounds. But k8s doesn't allow us to do much here unfortunately.

@elkh510 do you need to use init containers for that? Can you not put the db-migration container as the first container in the list and then use postStart lifecycle hook to wait until migration is done?

@howardjohn why do you say it is not supported? Is the user sets holdApplicationUntilProxyStarts then we will ensure istio-proxy get read first, followed by dm-migrate container, which should now have full access to MTLS etc.
If dm-migrate container also uses postStart then this is supported today.
The only reason to not do it would be if the privileges needed by dm-migrate are more, and they don't want those to be present in running containers.

It sounds like you are describing a normal container, not an initContainer. Perhaps you can hack around it with undocumented implementation details of kubernetes pod startup with postStart hooks, but its not an init container.

I am asking why does the container have to be init container.
If it does not, then they can just make it a normal
Container with the above changes and it will work.  It is not an api, but the behaviour is unlikely to change without explicit notification.

@howardjohn it seems like https://github.com/istio/istio/issues/11130 tracks the race between application and envoy and somehow making one start only after the other one is ready. However, this issue is specifically about init container's network connection, meaning there is no sidecar running to race or depend on.

Just want to point out that the lack of mTLS for init container traffic also inhibits the use of Istio authorization policies.

i am trying to do some setup by connecting to external service from init-container but i am unable connect to external service in ISTIO strict mode.
i found out about ISTIO CNI so i want to know whether ISTIO CNI will help to resolve the issue?
https://istio.io/latest/docs/setup/additional-setup/cni/#compatibility-with-application-init-containers
in above document it says there are 3 ways we can do it
i want to know whether those 3 ways actually work to resolve the issue?

This will work in a permissive MTLS context, not a strict one.
I've found a way to keep the initContainer pattern in a Strict MTLS context tho.
I use a K8s job to make the database migration while the initcontainer is simply waiting for this job to complete.
Since the job will be created with a istio-proxy sidecar in the same pod, the TLS connexion on both side (job and database) will be valid.
The tricky part is to wait for istio-proxy sidecar to be ready on the job pod and wait for the job to finish from the initContainer.
the job
apiVersion: batch/v1
kind: Job
metadata:
  name: <name-job>
spec:
  template:
    metadata:
      name: <name-job>
      annotations:
        proxy.istio.io/config: '{ "holdApplicationUntilProxyStarts": true }' <=== wait for the istio-proxy to be ready
    spec:
      containers:
        - image: <image-job>
          name: <name-job>
          command:
            - "/bin/sh"
            - "-c"
          args:
            - >-
              you-command-to-db-migration
       restartPolicy: OnFailure <==== This will retry the migration if the db is not ready yet for example

in the deployment
initContainers:
  - name: wait-for-db-migration
    image: ghcr.io/groundnuty/k8s-wait-for:v1.6
    imagePullPolicy: Always
    args:
      - "job"
      - "<name-job>"

An addtional cluster role / cluster role binding is necessary to check the state of the job from the initContainer.