Added wave spread animation

Hello,
this is my very first trial on Sass and one of the first for front-end stuff, so, any feedback would be helpful.
From what I see, the implemented animation is not as rapidly evolved as the rest of the existing ones, but I thought of having an overall feedback, as a first step.
TB

Feel free to rework this into the new structure as of #143 🙏


python -m pip install -e GroundingDINO 安装报错

ERROR: GroundingDINO is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

Sry, we will further refine this project later~ you can directly install GroundingDINO follow the official guide:
conda activate <your_env>
git clone https://github.com/IDEA-Research/GroundingDINO.git
cd GroundingDINO
pip install -e .

If you are using colab, make sure to use correct syntax (! or %) like so:
!git clone https://github.com/IDEA-Research/GroundingDINO.git
%cd GroundingDINO
!pip install -e .
%cd ..

more on ! VS %

ERROR: GroundingDINO is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

I also encountered  this error...

If you try to mount your drive on colab notebook, you can try to edit the %cd command to
%cd /content/drive/MyDrive/Colab/Grounded-Segment-Anything/GroundingDINO
!pip install -q -e /content/drive/MyDrive/Colab/Grounded-Segment-Anything/GroundingDINO

instead of  %cd /content/. This works for me

I met this in Docker(Ubuntu) with "Error:segment_anything is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file)",how to solve it


what's up my dudes

hi

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

This contains potentially hazardous tags that need manual review.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

226e1e9d46bb58a04937a99c58d970df42555c52

Looks good to me! Lets get this in!

Also just realized this is #100, Two days and 100 prs, this better be a record or something

def didn't time it


[TRIVIAL] Rename parameter to prevent shadowing.

Reviewers: @rec, @mtrippled

:+1:

Suggested:
Fix shadowing


sneakers work Should run all workers in app/workers

Major nitpick, but it'd be nice if the base command:
sneakers work
Looked up workers in app/workers or lib/workers and ran the ones that are Sneakers workers. That way, when I add a worker, I don't have to remember to update that command.

Hey @shaqq - would you be willing to sketch out how this might happen? I was thinking about a sneakers-rails gem maybe? what do you think?

+1 for this. Although I'm not sure why rails would come into this? As for how this could work, you could do something like Hutch does - https://github.com/gocardless/hutch/blob/master/lib/hutch/consumer.rb#L10..L13
It would be good to simplify it further and just have to run sneakers


Add a reusable exporter function (Entity to Map).

This relies and compliments pr #203.

Anyone wanting to have this feature can use my fork which I'll maintain to always sync with upstream:develop: https://github.com/noordawod/floor/tree/develop-noordawod

Too bad this wasn't merged in, it'd have made my life much easier rather than having duplicates of the same fields that already exist in the db schema.


Changes for apns ws extension

Just a minor change to make WsExtensionValidation.STATUS public.

Coverage remained the same at 46.43% when pulling dc05a4b1c9ee83f45c2bdb7199d961920993f667 on cmebarrow:changes_for_apns_ws_extension into be4773022c21e2e84067002b3d09e6a60cbf5dae on kaazing:develop.

Coverage decreased (-0.08%) to 46.34% when pulling 780381f9a063b1987a5e9c1ba6abf9ff9efddab8 on cmebarrow:changes_for_apns_ws_extension into be4773022c21e2e84067002b3d09e6a60cbf5dae on kaazing:develop.


Fix existing name map creating

An error occurred when there were names along the lines of "James" and "James I" if the first one was read in first. Since we were adding a " " to the end of "James" without a map attached to it, and "James I" has a " " in it and then more. It would try and access the map after " " but get an error because there was no map.
Since we have added an alphabet generator that could have " " as a valid character, I have make the end of a name in the map be "end" to clear up some of the confusion as to when a name has a valid ending.
Make generated names font a bit bigger so its easier to see against the mountains.
Change some naming of html elements to be more consistent. Both on the user side and just on the code side.

Excellent catch


script: Set noninteractive env var in install script

This ensures that our apt-get installs don’t get stuck waiting for input.
Closes #1665

LGTM


Exempt one type declaration from the redeclared export check - Fix #6043

:1+:

Close enough to :+1:!

It's the Common Lisp variant. You have to (apply :1+ ...


Search results for an Owncast instance shows only template tags

I'm guessing some HTML metadata tag should resolve this?

@gingervitis Want to put this on your radar in case you have an easy fix.

Is this because Vue is in development mode? (I've never used Vue before so this is a shot in the dark)

I think it's because it's client-rendered, so unless the search engine runs the Javascript and scrapes the output, I guess all it has is the raw templates.  I've run into the same thing with React.

Hmm, you'll need to do some server side rendering. If we're reading a config with JS on the client side for the entire thing, this is what we'll get. We could have a blurb somewhere about Owncast, the service itself hardcoded somewhere on the page. Let me know what copy you'd like to put it.

Actually now that the config file is shared spitting out a server-rendered page with just a blurb in it, so search engines/opengraph have metadata would be really straightforward.  I'll do that at some point.

Ok I threw something together.

FYI you'll also need to consider the document title, other this will happen.

That should be ok with this, https://github.com/gabek/owncast/commit/ea9a1a3afda467a83848d387e85ee6acbfb9b5ec#diff-54d8f3681bfad6fcfe4117bbdf73697bR7, right?

Oh interesting, so how does it get replaced by index.html?

The main index.html will get swapped out with the server-rendered version if the backend detects that the client requesting it is a web crawler/bot here: https://github.com/gabek/owncast/commit/b4c9654dacda0318145af7f13deb096db182e399#diff-67de5c415112a3133605aca0859176cfR34

Aside from the separate server-rendered page, currently the title tag is not a part of the Vue app, right?  Should we move app-container to be the id of the html tag instead?  Is that even allowed?  Or should we just getElementsByTagName the title tag and set it outside of Vue?

Actually I still need to set the  tag in javascript with the config data right after getting it. (document.title)

Oh that's way easier then the mess I was talking about.

Oh and btw the app version is now in /config, and I pushed up an update to app.js to use it.


update logs

till 12-07-2015 (sunday) #DryTask

duplicate is https://github.com/WindowsGeekPro/workaholic-meow/issues/67

moved to https://github.com/WindowsGeekPro/workaholic-meow/issues/71


New package: Stellantis.OpelUpdate version 1.5.2

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/136904#issuecomment-1915574193

Refer to https://github.com/microsoft/winget-pkgs/pull/136908#issuecomment-1915879279

Refer to https://github.com/microsoft/winget-pkgs/pull/136908#issuecomment-1924911142


[OPPRO-292] Fallback to vanilla Spark on unsupported data source

What changes were proposed in this pull request?
This patch adds more checks on data source and fallback to vanilla Spark if not supported
Signed-off-by: Yuan Zhou<EMAIL_ADDRESS>How was this patch tested?
manually tested

With this patch, S3 read will fallback to use vanilla Spark's impl, below is one example run with local minio setup

It occurs to me that in future we may be able to move more stuffs to doValidate() probably including "enableColumnarXXX" too.

Yes, it's a better way

does that mean we can use gluten with s3 even without gluten s3 connector implementation (just use the spark one)?

It should be. Slack channel reports some issues

@CodingCat  we have a Spark slack channel in Velox where I update our status and talked about issues. Would you like to join? You may send mail to Pedro Eugenio Rocha Pedreira<EMAIL_ADDRESS>to join in

does that mean we can use gluten with s3 even without gluten s3 connector implementation (just use the spark one)?

@CodingCat correct, this patch should be able to use the S3 connector in Vanilla/EMR, however you may need to disable the vectorized reader(which may hurt the performance) - just a work around for now
We are working on adding the S3 support in Gluten and it seems not that difficult - should be ready soon.

thanks @FelixYBW and @zhouyuan ,
and sure I'd love to join the channel, will email soon


[Bug]: Authentication redirection flow

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
ZITADEL Cloud
Version
1.0.2
Database
None
Database Version
No response
Describe the problem caused by this bug
I cloned the following repo: https://github.com/zitadel/zitadel-react
I filled the necessary information for configuration and run the project. I clicked on login button and clicked on register button to register a new user. I was asked to verify the email, expected the user to be logged once my email verification code was verified and redirected to default redirect uri. But, I was redirect to default uri but the user was not logged in
To reproduce

Register for a new user.
Enter necessary information for registration.
A code is sent to user's email, there is a Finish initialization button, right click on button and click open in a new tab option.
Verify the code.
Click on Next button.
I am redirected to user activated page.
Then, I click Next button and I am redirected to homepage rather than redirect_uri page.

Screenshots
https://github.com/zitadel/zitadel/assets/97692845/68b69bcb-5e6d-4579-9284-a8e095a24510
Expected behavior
I expected the user to be logged in but it was not the case.
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

Hei @aeghprs
Can you test what happens if you are coping the code from the email and put it directly into the code input? Instead of clicking the verify link in the email?
I am not sure where the problem is, but it might be that you loose the context of the authorization request.
You can also test this, if you now try to login with the user you have already created. Does that work?

Hi @hifabienne , thanks for response.
Currently I have only tested for register button.
Yes it works if I copy and pasted the code, in code input field and once the code is verified I am redirected to redirect uri, and the newly registered user is logged in too.
But, if I follow the same steps but with minor change in steps where I copy the link address from Finish initialization button and open in new tab, I am redirected to default uri but the user is not logged in.
I expected the user to be logged in both cases as the user behavior is unpredictable.
Also, can I ask if there is plan for feature to hide or show the Finish Initialization button in email verification message ?

Hi @hifabienne , thanks for response. Currently I have only tested for register button.
Yes it works if I copy and pasted the code, in code input field and once the code is verified I am redirected to redirect uri, and the newly registered user is logged in too.
But, if I follow the same steps but with minor change in steps where I copy the link address from Finish initialization button and open in new tab, I am redirected to default uri but the user is not logged in.
I expected the user to be logged in both cases as the user behavior is unpredictable. Also, can I ask if there is plan for feature to hide or show the Finish Initialization button in email verification message ?

The problem is, that in case of the email the user looses the context of the authrequest, so ZITADEL does not know who did start the authentication process.
If you configure the default redirect url to your application, this is the url where ZITADEL does redirect if there is not existing auth request, then the user should be redirected to your app when no authrequest is existing and your app will then start one again: https://zitadel.com/docs/guides/manage/console/instance-settings#default-redirect-uri

+1 for the additional possibility to hide the button "Finish initialization".
When registering a new user in an app (phone) and then clicking "Finish Initialization" in an e-mail client (computer) the app (phone) gets "stuck" on the enter code page. For this scenario it would thus be helpful to just hide the button in the mail altogether.

@livio-a What does "Done" mean? Does it mean it is available in production instances?

@akaegi As soon as we have implemented it and it is merged to our main branch it is marked as done.
As soon as it is built into a version you can see the following on the pullreaquest:

(this screenshot is from another issue)

Just a small addition: feature releases are deployed to zitadel.cloud within a week after their release

Just a small addition: feature releases are deployed to zitadel.cloud within a week after their release

Where do I see the used version in the cloud portal, is it the same for all instances?

Just a small addition: feature releases are deployed to zitadel.cloud within a week after their release

Where do I see the used version in the cloud portal, is it the same for all instances?

You can see it when you login to your instance, on the instance detail page. Yes at the moment it is the same for all instances

Seems to be fixed on Android but not on iOS.
I filed another issue with a request to provide a more general solution: https://github.com/zitadel/zitadel/issues/7954.


Build a Modern Analytics Dashboard with Next.js 14, React, Tailwind - 2024

For the URL to this one, see the title in the list found in this https://github.com/JamieBort/Personal-Dashboard/issues/13#issuecomment-1986638169 comment that matches the title of this Issue.
Build a Modern Analytics Dashboard with Next.js 14, React, Tailwind - 2024 85 minute YouTube video by Josh tried coding.
Finished product repo
https://github.com/joschan21/next-analytics

Notes following along
was
create-next-app@latest analytics-dashboard
I used
create-next-app@latest personal-dashboard


Unauthorised 401

All of a sudden today it's started to 401 Unauthorised. Any idea what might suddenly cause this issue ?

I'm using Nuget so 0.9.x trying the Bot prefix now and closing if that's the issue. It more then likely is

Same here, trying that Bot prefix.

Works fine thanks


multiple sms request issue

HI Team,
Thanks in advanced, Can anybody help, how we send multiple sms, while doing bulk request, its proccessing one by one, and while every request its taking more then 40sec ,

Your request is taking too long to complete, ideally it shall not take more than 100 millies, have you tried submitting multiple messages using one session and multiple threads?


fix indentaion in hpa deployment

Fix indentation in example deployment for HPA to avoid confusion.

Ready for review.

@kubernetes/sig-autoscaling-pr-reviews 👋 Would you please review for accuracy?

/lgtm

(from the content perspective)

/lgtm
/approve


Allow sending messages prior to closing the connection

Related to https://github.com/phoenixframework/websock/issues/11

Great! I'll let this stand for comments for a day or so and then get the other PRs ready to actually implement this

Implementations for Bandit and Cowboy (the latter via websock_adapter) are linked above; I'll give those a day or so to soak up reviews (feel free to add your own!) and then I'll get all this merged


DOC: add RawKernel example using complex-valued arrays

This adds an example to the custom kernels tutorial showing how to define a RawKernel for complex-valued arrays.  The appropriate include file and notation took me some reading of the cupy sources and some trial & error to figure out.  Perhaps there are also other ways, but this was what I got working.
Notably, it seems one should use the C++-style complex<float> notation from Thrust and not the C-style cuFloatComplex, etc.
The example also demonstrates casting of a constant to the appropriate dtype.

Thank you for PR!
We don't want to recommend this solution (because of https://github.com/cupy/cupy/pull/1398#issuecomment-400226515), but we agree with you that we need to provide a way to handle complex arrays.  We'll discuss it and reply soon.

Thanks. I understand if you want to implement and recommend a different approach.
Is my proposed approach here likely to continue to work in the future?  If so, I can use it for now until/unless something better comes along.

Signatures like complex<float> can be considered stable.
The header filename <cupy/complex.cuh> is considered as a kind of private API, but currently there's no plan to change it.

I am closing this based on the feedback above. Thanks

@leofang Thanks for the comment!
I discussed again with @okuta and concluded that documenting cupy/complex.cuh is better in this case.

@grlee77 Can I takeover your PR?

Yes, feel free to update it.

Apparently the fact that complex numbers are treated specially in CuPy starts to cause issues (ex: #2111). I'd suggest @kmaehashi to merge this PR for the time being, and polish it later since it's not as critical but does present somehow as an obstacle for advanced users.

Hi @kmaehashi @asi1024, any chance get this PR merged? Just ping you folks again in case the ball is dropped. Thanks.

I have rebased to fix the merge conflict and made the change suggested by @leofang

LGTM! Thanks for revisiting this PR, @grlee77.
@kmaehashi @asi1024 any chance you could take a look at this before the weekend? Thanks.

Note: This PR is merged into #2551.


Incorporate package updates and also add onSave/onLoad

As mentioned in #21

the native module is not loading properly in a version of this branch. Looking into why. I think it's a require/default/import problem.

@djMax Let me know if/when this is ready to merge and I'll get a release cut.

I don't know as much as I'd like about configuring metro, but maybe playing with the transform inlineRequires would solve the issue.


chore: remove usage of fixed function pipline methods

this removes usage of the fixed function pipeline methods from Chunk. the chunk only renders its own local position but maybe there are ways to address the transforms. glMatrixMod/glLoadIdentity/glpushMatrix etc . some of the active state stuff is called for every chunk draw so were adding a lot of additional state changes to chunk rendering. some of this is pretty limited to opengl so maybe moving these to utilities of some kind. I would imagine vulkan spec is a lot different but I think opengl is can be emulated from vulkan. some things to consider for more work in this regards.
https://www.khronos.org/opengl/wiki/Legacy_OpenGL
PR: https://github.com/Terasology/CoreRendering/pull/35

This shaders should be in CoreRendering... isn't it?
Yeah vulkan not use fttransform. GLSL3-4 too.

that's what I thought to @DarkWeird but apparently it lives int he engine instead :?.

@pollend
Someone forgot to move it. seems.

@pollend
Someone forgot to move it. seems.

lets start here and then migrate the shaders later. I think I'll get rid of the fttransform stuff first then slowly replace things as I go.


Confusion around 2022.25.1 documentation

Hi,
Can someone help clarify the following documentation:

Configure your USB LTE stick using your computer. No other setup then saving your PIN is required. Verify if Internet is accessible after unpluging and pluging your device back into your computer. Then, connect your USB LTE stick to your Pi that will be used for the Linux system.
Connect the HDMI capture interface to the camera header on your Pi.
Connect the capture interface with a second Pi using an microHDMI to HDMI cable.
Using an Ethernet cable connect both your boards together.
Plug your Linux Pi to a power source.
Wait a few minutes for the Linux Pi to boot up for the first time.
Connect your computer to Tesla Android Wi-Fi network. The default password is: “changeit”
Using a Terminal of your choice connect to your Linux Pi using SSH:
ssh<EMAIL_ADDRESS>
Questions:
For item 4, is it a special cable or just regular cable?
For item 8, how does the pi connect to ethernet? AFAIK, the LinuxPi and AndroidPi are connected via Ethernet, but how does the LinuxPi get an IP? Doe LinuxPi boot up and broadcast this network name?
Lastly, do I need to connect LinuxPi to any external display for the setup?

self closing:
For item 4, is it a special cable or just regular cable?
Yes, regular cable.
For item 8, how does the pi connect to ethernet? AFAIK, the LinuxPi and AndroidPi are connected via Ethernet, but how does the LinuxPi get an IP? Doe LinuxPi boot up and broadcast this network name?
LinuxPi boots up and broadcasts this network.
Lastly, do I need to connect LinuxPi to any external display for the setup?
Not needed.

Did you RTFD?


Build a Rake task for building Apple Packages

The goal is to have our release managers build all Facter packages
within Rake, and so this commit adds a rake task (apple_package) that
will build a DMG-encapsulated package for OS X and put it into the
pkg/apple directory off of the Facter Root.
To accomplish this goal, a folder structure is created in
/tmp/facter/facter-#{version} that mirrors the structure needed for
Apple's Packagemaker CLI tool to build a package for OS X. Next, the
necessary files are copied from the Puppet source into the structure in
/tmp/facter/facter-#{version} and then packagemaker is run
(targeting that folder structure) to build an initial package. Hdiutil
then encapsulates that package into a DMG, and the file is finally
copied into the pkg/apple directory.

Is there a ticket for this in redmine Gary? You need to include the ticket number in the commit message as is standard.

Thanks for the reminder.  The ticket number is here --> http://projects.puppetlabs.com/issues/11201

Updated the commit so it falls in line with the Puppet pull requests (and thus won't/shouldn't break the build).  Let me know if this looks good or should have any changes?

Per Mike, closing this pull request and creating a new one based on 1.6.x versus Master.


Updating README.md of Javascript Projects Folder

The Javascript folder under Projects needs an update to the README.md as new projects have been added.

The Javascript folder under Projects needs an update to the README.md as new projects have been added.

Please add the README.md file for each project of Javascript in their respective folder. Go through each project understand it then drop README.md file to it. Procced if you can.

@risingstar-bit yes sure, please assign me the issue.


German Shortcut for Clear Cache wrong

Description

In platform/src/Administration/Resources/app/administration/src/app/snippet/de-DE.json line 882 reads:
    "keyboardShortcutSpecialShortcutClearCacheMac": "control s",
Possible Solution
Line 882 should read:
    "keyboardShortcutSpecialShortcutClearCacheMac": "control c",
Additional context
English version is OK

hey @aagd
thanks for the hint.
sounds like an easy pick for a PR 😉

Yes, that was an easy one :-)
Thanks @aagd !
Hope you didn't want to make the PR yourself!

@ThomasChr  No, thank you for helping out. Would have taken me too long. Next time, I'll try it myself.


Untracked files not added to staged files after build step

I have noticed that release-it does not stage untracked files. Ones the files have been manually committed it does stage them as expected. I have seen this when release-it is runs in a project for the first time that files are generated by a build command as part of the release proces. The CHANGELOG.md is also missing after the first run of release-it.
Here is an example of git status after release-it has run for the first time after I changed the output formats of the build command.
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        dist/vue-build-helper.es.js
        dist/vue-build-helper.js
        dist/vue-build-helper.min.js
        dist/vue-build-helper.min.js.map

nothing added to commit but untracked files present (use "git add" to track)

Here is the output of the Show staged files? prompt:
√  Built in 8.51s.
┌──────────────────────────────────────────────────┐
│file                          size       gzip size│
│dist\vue-build-helper.cjs.js  12.41 KB   3.8 KB   │
│dist\vue-build-helper.es.js   12.17 KB   3.73 KB  │
│dist\vue-build-helper.js      192.31 KB  55.7 KB  │
│dist\vue-build-helper.min.js  144.82 KB  44.97 KB │
└──────────────────────────────────────────────────┘
? Show staged files? Yes
M  CHANGELOG.md
M  dist/vue-build-helper.cjs.js
M  package.json
? Commit (chore: release 0.1.1)? Yes
? Tag (v0.1.1)? Yes
? Push? Yes
? Create a release on GitHub (🚀 Release 0.1.1)? Yes
? Publish vue-build-helper to npm? Yes

You can checkout releases 0.1.1 and 0.1.2 here to see the above example.
How to recreate:

New project.
Run release-it for the first time.
When prompted Show staged files? select Yes and you will only see a subset of the files that were generated.
After completion run git status  and you should see one or more untracked files generated by release-it.

release-it version: 8.3.0

Hi, @nidkil!

I have noticed that release-it does not stage untracked files.

This behavior is intended. So either they should indeed be added manually, or use src.addUntrackedFiles: true. The latter is usually not recommended, as unexpected/unwanted files may get included in the release.
Or are you saying that release-it behaves unexpectedly by staging a (random) subset of files?

Hi Lars,
First of all: great project! Really like what you have done. A real time saver!
I understand that files that are untracked/staged when the release it process start should not be touched by release-it. Except if addUntrackedFiles is enabled. But these are files that are generated during the release process. Even the intial version of the CHANGELOG.md file is not picked up and committed.
I feel release-it should distinguish between files that exist before the release process starts and files that are generated during the release process. This last category should be committed by release-it, even if they do not yet exist in the repository (untracked). That is actually how release-it behaves ones they have been initially committed to the repository.
Hope you can follow my thinking.

I feel release-it should distinguish between files that exist before the release process starts and files that are generated during the release process.

This is virtually impossible, because release-it doesn't know what the results of the user's commands are (e.g. npm run build or generating CHANGELOG.md).

Okay, but I do not understand why it does work after the files have been committed manually to the repo after the first time.
Take for example the CHANGELOG.md which is generated by conventional-changelog. The first time it is generated it is not part of the release. On subsequent releases it is picked up and committed. How come this happening automagically?

Well, that is weird indeed. You can see what release-it itself is doing with the --verbose argument. Let me know if you think release-it has a bug or could improve here. Closing this for now, but feel free to discuss.

Hi Lars,
I'm a little lost now. Does release-it expect the build command and conventional-changelog to commit their own changes when they are called in the release-it hooks?

It depends. But generally speaking, "yes".
I do understand this might be unexpected for some people using release-it for the first time. However, it is often considered bad practice to include build artifacts in version control (as they can be generated from source).
This is also the reason I don't put the changelog in https://github.com/webpro/release-it/blob/master/CHANGELOG.md (besides a few remarks re. breaking changes), but in releases.
In your case, you might want to add e.g. git add CHANGELOG.md to the command, or use --src. addUntrackedFiles for the first time only.
One more thing: publishing build artifacts to npm is of course fine. This can be managed using .npmignore and .gitignore (and/or publishing from a directory, e.g. --npm.publishPath dist).

I do understand this might be unexpected for some people using release-it for the first time. However, it is often considered bad practice to include build artifacts in version control (as they can be generated from source).

Good point, I initially did have the dist directory in .gitignore, but thought it was needed for NPM. So it is not. Cool I can change that. One problem less :-)

This is also the reason I don't put the changelog in CHANGELOG.md (besides a few remarks re. breaking changes), but in releases.

I don't understand what you mean. If I look at the GitHub repo the CHANGELOG.md is in the project root like mine.

In your case, you might want to add e.g. git add CHANGELOG.md to the command, or use --src. addUntrackedFiles for the first time only.

 I still do not understand why this is only needed on the first call. Why isn't it possible to determine which files are untracked & unstaged when release-it starts. Then using this informatin release-it could check after the postbuild hook if there are any files that were not their on startup and stage and commit them. Is their a reason for not doing it this way?

One more thing: publishing build artifacts to npm is of course fine. This can be managed using .npmignore and .gitignore (and/or publishing from a directory, e.g. --npm.publishPath dist).

Doesn't release-it look at the files property in the package.json file to determine what to publish to NPM?

If I look at the GitHub repo the CHANGELOG.md is in the project root like mine.

I do have a CHANGELOG.md, but it is not generated. I store the changelog in the "Releases" page of my GitHub projects. See https://github.com/webpro/release-it#github-releases

I still do not understand why this is only needed on the first call.

Once you git add-ed a file, you don't need to do it again, since release-it does this for you:
git add package.json
git add . --update      # This (default), or:
git add . --all         # with `src.addUntrackedFiles: true`

You can see this with the --verbose argument.

release-it, after the post build hook, could check if there are any files that were not their on startup and stage and commit them. No risk of adding anything that is not generated during the release process and predictable for the user. Is their a reason for not doing it this way?

Lots of files could be generated during any script, and everything within reach would get included in the release. This can lead to unexpected results. I think it's better to opt-in/whitelist, than to opt-out/blacklist.

Doesn't release-it look at the files property in the package.json file to determine what to publish to NPM?

No, release-it delegates this to npm publish. No tricks here, it's like you would npm publish from the command line yourself. Again, you can see happening with the --verbose argument.

No, release-it delegates this to npm publish. No tricks here, it's like you would npm publish from the command line yourself. Again, you can see happening with the --verbose argument.

NPM does look at this property, right?
The rest is clear. Thx for your time!

NPM does look at this property, right?

It does: https://docs.npmjs.com/misc/developers

The rest is clear. Thx for your time!

 Thanks for your feedback.


Make sure RunOnlyOnPlatforms works as expected with sparse matrix testing updates

The sparse matrix test updates allow the Core CI pipeline to be split amongst several sub pipelines. Each pipeline runs a subset of the tests on a specific platform, i.e. we don't run the full set of tests on each platform like we did previously or like we still do for individual library pipelines. When you combine this behavior with the RunOnlyOnPlatform attribute, you have the potential for a given test to not be run at all in a Core CI run. This is mitigated by the fact that the test should still be run as part of the library CI pipeline. However, it would be good to determine whether there is a way that the test splitting can take into account this attribute and ensure that tests using this attribute are assigned to a platform that they can actually run on.
/cc @weshaggard @m-nash

This was split off from https://github.com/Azure/azure-sdk-for-net/issues/34264

@JoshLove-msft just so it is clear the Core tests should be running on the entire matrix. The tests for the tests projects that depend on core are running sparse. For this RunOnlyOnPlatforms options is it about the core tests themselves? If so I think we are good here.


Update FastRoute

The functions \FastRoute\cachedDispatcher and \FastRoute\simpleDispatcher
are deprecated since V2 of FastRoute
and will bee removed soon.
The 2 functions are used in Dispatcher

That's interesting. Could you please provide a link to that information?

https://github.com/nikic/FastRoute/blob/d3ada013d0f683ad2a8d0614fc97917a6ab72ce9/src/functions.php#L14
https://github.com/nikic/FastRoute/blob/d3ada013d0f683ad2a8d0614fc97917a6ab72ce9/src/functions.php#L31


Stratagem GUI should be hidden if not available

Stratagem info: "Scan Filesystem Now", "Top inode Users", "File Size Distribution",  ... is all shown in filesystem detail page, but there's no stratagem profiles or components installed on servers.
To Reproduce
Steps to reproduce the behavior:

Create filesystem in managed mode.
See Stratagem components

Expected behavior
No stratagem components

Here is json of /api/host/
api-hosts.json.log
Json of /api/target/
api-target.json.log

The problem is within this code:
https://github.com/whamcloud/integrated-manager-for-lustre/blob/51e958665efdbdcf1d2abb982cee82bf668a8acf/iml-wasm-components/iml-fs/src/fs_detail_page.rs#L92-L96
A filter checking mdt.active_host_name == x.address is used, however in this case active_host_name is fqdn and address is shortname so no filters match.
After this filter, all remaining items are checked to be stratagem_server. Since there are no items, this returns true.

The active_host_name property comes from here:
https://github.com/whamcloud/integrated-manager-for-lustre/blob/51e958665efdbdcf1d2abb982cee82bf668a8acf/chroma_api/target.py#L374-L378
It uses the label so, it seems that's how we should do comparisions.

In addition, we should be checking there are still some hosts left before checking that all remaining items in the collection have the expected server_profile, given that an empty iterator returns true for .all https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.all.


feat: update auth documentation for app router

Closes #1882
✅ Checklist

[x] I have followed every step in the contributing guide (updated 2022-10-06).
[x] The PR title follows the convention we established conventional-commit
[x] I performed a functional test on my final commit

Changelog
Update sections about server-side fetching and use of tRPC + add warning about Client Provider section to highlight that it is relevant only to the use of the /pages router. Change one outdated hyperlink and add additional context in few areas for user clarity.

Screenshots
[Screenshots]
💯

i could add an additional commit to this pr to fix #1889 too maybe?

did not see that PR before! seems like an easy enough change, I'll do that by tomorrow! Should I also add another commit into this same pr to fix #1889 because it's a similar sort of issue or would you prefer I open a different pr for that after this is closed?

Should I also add another commit into this same pr to fix https://github.com/t3-oss/create-t3-app/issues/1889 because it's a similar sort of issue or would you prefer I open a different pr for that after this is closed?

Sure!

I think I'd have to add an additional dependency in the form @mdx-js/react and @mdx-js/runtime since unlike #1900 where there is only one edit at the top of the page, there's both a continuous series of edits for this specific page and a few of them include code snippets so I'd have to pass down some .mdx from the component to the mark down file.

you can make a react component that conditionally renders children based on some condition
so
<PagesOnly>
  Use gSSP...
</PagesOnly>
<AppOnly>
  Await in an RSC...
</AppOnly>

The trpc stuff was fixed in ff32e083970357a64ddf53e2e0469f9170c06412
Feel free to reopen for the auth changes if you get the time for it in the future


use Submit-PullRequest.ps1 to replace curl cmd

use Submit-PullRequest.ps1 to replace curl cmd when creating PR.

want to get pr number directly in Submit-PullRequest.ps1's response, so I can use it in a for loop. Thanks
CC @benbp

Hi @weshaggard  , I use parameters to pass Boolean type to power shell script but it didn't work.  (https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2034856&view=logs&j=22c482a4-5c29-5536-e3f4-9bc4a870126f&t=77f8a040-4539-5ea0-f035-44975cc40c0b&l=80)  Throw out the error again “Submit-PullRequest.ps1: Missing an argument for parameter 'OpenAsDraft'. Specify a parameter of type 'System.Boolean' and try again.”
I also try it in my local wsl environment:

Could you please give me an example of passing boolean parameter to power shell script in bash? Thanks.

@zzvswxy see bash escaping rules at https://wiki.bash-hackers.org/syntax/quoting. I think what you want is pwsh -NoProfile -Command " ./testps.ps1 -OpenAsDraft /$False"

@zzvswxy we also might want to consider not going in and out of bash and pwsh we could do it all the same logic in a single step in a single language.

Agreed on consolidating new scripts to powershell and not using bash.


unable to locate device

I installed traccar both client and server..Registered a mobile device on the server but cant show location of the device on the map

Please follow instructions here:
https://www.traccar.org/troubleshooting/

i think thats why i cant see my device on the map on the server

That's definitely a problem. Are you sure port is visible? What port are you using?

5055

What about the second question?

its is visible on my mobile phone on traccar mobile app thats server port....and server address is <IP_ADDRESS>

OK, so it's on the same local network, right? What do you see in the logs?

This what i see on the tracker server.log
2016-07-26 07:18:18  INFO: Operating system name: Windows 7 version: 6.1 architecture: amd64
2016-07-26 07:18:18  INFO: Java runtime name: Java HotSpot(TM) 64-Bit Server VM vendor: Oracle Corporation version: 25.5-b02
2016-07-26 07:18:18  INFO: Memory limit heap: 1812mb non-heap: 0mb
2016-07-26 07:18:18  INFO: Character encoding: UTF-8 charset: UTF-8
2016-07-26 07:18:18  INFO: Version: 3.5-SNAPSHOT
2016-07-26 07:19:15  INFO: Starting server...
2016-07-26 08:56:22  INFO: Shutting down server...
2016-07-26 09:03:26  INFO: Operating system name: Windows 7 version: 6.1 architecture: amd64
2016-07-26 09:03:26  INFO: Java runtime name: Java HotSpot(TM) 64-Bit Server VM vendor: Oracle Corporation version: 25.5-b02
2016-07-26 09:03:26  INFO: Memory limit heap: 1812mb non-heap: 0mb
2016-07-26 09:03:26  INFO: Character encoding: UTF-8 charset: UTF-8
2016-07-26 09:03:26  INFO: Version: 3.5-SNAPSHOT
2016-07-26 09:03:51  INFO: Starting server...

Nothing from the device. It means that server doesn't receive anything.

So it means maybe its a problem with server address??

I can only guess where the problem is, but you must be missing something somewhere.

how should i tackle this because i tried reinstalling but still the same

Well, I would recommend to follow troubleshooting guide. Make sure the port is visible from your device.

port is visible from my device because it is stated there....but i tried this link https://www.traccar.org/port-check/ to check the port it said the port is closed

What do you mean by "is stated there"? Link won't work because you are using local IP address.

traccar client app at server port.And which IP address am I supposed to use??

You need to use your server IP address and port 5055.

How can i find the IP address i am using??

Do you want to use public or local address. Local you can check in network settings. For public you can ask your ISP.

I just tried with a local IP address,same responses

Try to open following URL in browser on your mobile device:
http://your.ip.address:5055

Its does not show..it says the webpage is not available

It means that port is closed.

So what should i do to fix these

@josephphale if your are running the server behind a router, you should probably port forward. google or go to http://portforward.com/
recommend closing this issue.


Map's x and y values not updated on each click

First of all, many thanks for this plugin as it has made my life sure easy!
I was exploring useCallback to see if I needed to use that function as when areas values are changes, it's not being reflected on map; I have a double click to see the "dot" moves. Is this a bug?
See demo.

Sorted. See #32


Webpack with SAM?

Hi. Is there any way to use SAM with webpack? If not, can you provide this possibility?
Somewhere, I saw something for Typecript, but I need for JavaScript.

It's definitely possible. I wrote a blog post about building SAM with Webpack for TypeScript. The webpack config supports both TypeScript and Babel (for JavaScript). You just need to modify the webpack script inside the package.json so it builds src/index.js instead of src/index.ts.
There's also an issue for adding a Webpack builder to SAM. I've been trialing some updates to the blog post I wrote that will hopefully go into this.

I recently added an example here https://github.com/awslabs/aws-serverless-express/tree/v4/examples/lambda-edge which uses Webpack to bundle a Lambda Function. If you're asking for SAM CLI support, please open an issue in that repo https://github.com/awslabs/aws-sam-cli.

Issue was created with AWS SAM CLI at https://github.com/awslabs/aws-sam-cli/issues/1277


Add ESPHome Cover position/tilt support

Description:
Add ESPHome cover position and tilt support.
The aioesphomeapi also received a small refactor for these changes and those are part of this PR (constants were refactored into enums and optimistic was renamed to assumed_state). If possible, I'd like to include those in this PR because:

It's mostly just very simple changes
Because of the new position change the dev branch would be in a non-working state for a while until the split PR is merged (unless I write some temporary glue logic, but I'd prefer to avoid that)

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly (example).
[x] New dependencies have been added to requirements in the manifest (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

@awarecan Yeah the problem with that is that it would require aioesphomeapi to be installed for the mypy checks. Also some of the lazy imports I need to use here because of the REQUIREMENTS don't work too well with mypy - so I'd need to change quite a bit to keep mypy from freaking out about that.
For now, I'll just use it for my IDE.


Performance fixes for longer videos and fmp4 streaming

This fixes a few problems that kept me from streaming fragmented mp4 HLS from PeerTube:

the byte ranges were not used, leading to overlarge requests and reads from the wrong place
hitting the recursion limit in buf2str on large playlists
don't reallocate the entire request buffer every time a block is received
add a very basic request abort mechanism

I'm trying this on the new bitsong player, it seems to perform better on long playlists

@vaultec81 Yep looks good to me! Please go ahead :)


feat: add external dependency software check command

Description

related: https://github.com/star-whale/starwhale/issues/761
Modules

[x] Client

Checklist

[x] run code format and lint check
[ ] add unit test
[ ] add necessary doc

LGTM


[MRG] Make the build pod clean up task run in the background

We need to create a task, not just convert it into a future for the
build pod clean up function to run in the background all the time.
Noticed this because some tests printed a warning that this coroutine wasn't being awaited. I don't remember why there was an ensure_future() here. IMHO that would be useful for converting things that aren't a coroutine but won't get them executed.
Instead we now create a task which runs in the background. I think this is the right thing to do and equivalent to IOLoop.current().add_callback() from Tornado (which we could also use if we wanted to?).
Two questions for reviewing:

do create_task and add_callback achieve the same thing?
if yes, should we prefer one over the other? For example for cleanup during shutdown or something like that?

Because Travis is paused right now "all checks passed" as a PR status doesn't mean all our tests passed. They are "green" because the unit tests are not being executed at all :D

This change will introduce a dependency on Py37 rather than just Py36 as we currently have according to the python documentation.
async def coro():
    ...

# In Python 3.7+
task = asyncio.create_task(coro())
...

# This works in all Python versions but is less readable
task = asyncio.ensure_future(coro())
...

The ensure_future part will schedule the coroutine to be executed, but exactly where is not something I'm sure of, or if it will keep executing if not awaited etc.

Ok, then this isn't needed. Super weird naming though :)


fix(sdk): enforce legacy transactions on Vanar mainnet

#3639  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite

lgtm


community change the trigger of github action

Proposed changes
Issue Number: close #xxx
Problem summary
Change to pull_request_target so that some pre check action can be run
before approving.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Support for building Sass

Would it be possible to add support for building Sass files?
https://esm.sh/vuetify@next

/* esm.sh - error */
throw new Error("[esm.sh] " + "esbuild: No loader is configured for ".sass" files: esm-build-18733500f98f2f68be0fd12fb31cbfc2c013325f/node_modules/vuetify/lib/components/VAlert/VAlert.sass");
export default null;

Maybe with something like https://github.com/glromeo/esbuild-sass-plugin/?

i have a plan to support this, but we can not use the plugin directly since the server is written in golang


Add Merin chapters 3-5

These three WoK Prime chapters were released under WoR deleted scenes, but follow the Merin chapters released under WoK deleted scenes.

I haven't been following WoK prime properly, so this is very helpful. Thanks :+1:


Refactor Teams Service for Improved Structure and Asynchronicity

Refactor TeamsService for Improved Structure and Asynchronicity
Description:
In line with our project-orion objectives, the following requirements should be addressed for the teams-service.js module. Please use the Matrices service and repository (services/matrices-service.js and repository/matrices-repository.js) as a frame of reference when making these changes.
Requirements:

Decoupling Database Logic:

Remove all direct database operations from the service module.
Migrate these operations to a new repository/DAO module.

Exceptions Handling:

Implement the new exceptions module to handle errors.
Replace traditional error handling with our standardized custom error classes.

Callbacks to Promises:

Transition all existing callback handlers to Promises.
Use try-catch blocks and async/await notation for cleaner, more readable asynchronous code.

Service Structure:

Refactor the service module to be a class-based structure.
This class should extend the BaseService for consistent behavior and structure across all services.

Repository Structure:

The newly created repository/DAO should also be class-based.
This class should extend the BaseRepository to ensure consistency in database operations across services.

Common Function Migration:

Migrate shared or common functions to BaseRepository and BaseService as necessary.
Avoid duplication and ensure that common functionalities are accessible to all services and repositories.

Service-Specific Functions:

Functions that are specific to a particular service and are not shared should be implemented directly on the corresponding service class. Do not add them to BaseRepository.

Testing:

Refactor the Mocha test suite spec file corresponding to this service.
Transition from callbacks to async/await notation.
Ensure all tests are passing before opening a pull request.

Notes:
Please reference any relevant documentation, discussions, or PRs as needed. Ensure that the refactoring remains consistent with the established practices from the Matrices service and repository as a reference.

NOTES

Recommend tackling UserAccount first as the teams service will need to import the UserAccountRepository
This one should be mostly standard:

Convert to class & extend BaseService
Migrate callbacks to async
Migrate DB calls to repository class
Create TeamsRespository


Documentation on Rigetti 19Q

This is a pull request to change the Pyquil Docs.
This document includes information about Rigetti 19Q.

@willzeng - can you go through this too?


[KYUUBI #5284] Support Hudi Alter Table Command in Authz

Why are the changes needed?
Hudi also is a common used data format, since kyuubi already support iceberg and delta, we should also support hudi.
In this pr we support hoodie sql about ALTER COMMAND in authz
In this PR we use default Hudi version 0.14.0.
We support from spark 3.1 to spark 3.4, since Hudi don't support spark 3.5 yet

[x] spark 3.1
[x] spark 3.2
[x] spark 3.3
[x] spark 3.4
[ ] spark 3.5

Also since Hudi only supports Scala 2.12, I also made Hudi as a separate profile to avoid importing Hudi when enable Scala 2.13
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?
No

Codecov Report

Merging #5287 (0557133) into master (dd2cd51) will not change coverage.
Report is 28 commits behind head on master.
The diff coverage is 0.00%.

:exclamation: Current head 0557133 differs from pull request most recent head b8173b8. Consider uploading reports for the commit b8173b8 to get more accurate results

@@          Coverage Diff           @@
##           master   #5287   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         590     590
  Lines       33368   33369    +1
  Branches     4413    4414    +1
======================================
- Misses      33368   33369    +1

Files
Coverage Δ

...ache/kyuubi/plugin/spark/authz/OperationType.scala
0.00% <0.00%> (ø)

...he/kyuubi/plugin/spark/authz/util/AuthZUtils.scala
0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

ping @yaooqinn , fix the GA issue and hudi for spark 3.4 is ok now, could you take a look?

ping @bowenliang123 Do you know why the UT failed? I miss some setting?

ping @bowenliang123 Do you know why the UT failed? I miss some setting?

Run tests locally with each spark version and debug all the problems. Maintaining the compatibility for Spark versions.

ping @bowenliang123 Do you know why the UT failed? I miss some setting?

Run tests locally with each spark version and debug all the problems. Maintaining the compatibility for Spark versions.

I know but I follow the UT case of iceberg, I don't know why it don't throw access control exception. I have check the inputs outputs is ok.

AND WHY DONT YOU SPEND SOME MORE TIME IN INVESTIGATION IN ALL THESE DIFFERENT EXCEPTION IN DEPENDENCIES AND RUNTIME ERRORS ?

PLEASE TRY NOT THROW EMPTY QUESTIONS TO NOWHERE ELSEBODY WOULD KNOW.
T H A N K S.

The very first problem, what's Hoodie in the title.
This is Apache Hudi:

And this is a Hoodie:

Hoodie is not even the official nickname for Apache Hudi.
 Value your contribution to Kyuubi's Authz does impacts on the Spark ecosystem, on datalakes, on authorization. Let's make a difference and carry on.

Hoodie is not even the official nickname for Apache Hudi.

@bowenliang123 I have talked with @AngersZhuuuu and we reached a consensus to use the term "Hudi" in the Kyuubi codebase because Hudi should be a formal name of the project. I'm not sure what the Hudi community thought about the term "Hoodie", but it definitely appears in the Hudi's codebase frequently.

Hoodie is not even the official nickname for Apache Hudi.

@bowenliang123 I have talked with @AngersZhuuuu and we reached a consensus to use the term "Hudi" in the Kyuubi codebase because Hudi should be the formal name of the project. I'm not sure what the Hudi community thought about the term "Hoodie", but it definitely appears in the Hudi's codebase frequently.
BTW, it's legal to use trademarks with the same name in different categories, for example, if there is only a clothing brand call "Kyuubi", we still could use this name for a Software, because there are in different categories.
PS: The above is the expression of my understanding of trademarks, not rigorous legal provisions.

What I asking is for the respect to the code of conduct. Such clarification of course should be done by the contributor, if we have to use specific term for any reason. No matter Hoodie or Apache Hudi.
And the description is unclear too. No even the range of cover commands of ALTER are covered are mentioned. As we have so many alter commands for Hive \ Iceberg tables, there's no essential hints for the coverage. Simply refer to "sweeping" concepts ALTER table commands are just not enough.

Please add a new PrivilegesBuilderSuite for Hudi as well. The IcebergCatalogPrivilegesBuilderSuite could be an example. New supported commands should be covered in both end-to-end tests in *RangerSparkExtensionSuite and the privilege object parsing tests in *PrivilegesBuilderSuite. The latter is important for maintaining compatibility and ensuring the intermediates.

Hudi is working on supporting v2 command. Currently, CREATE DATABASE does not support v2 command, so this place may not be able to test it yet.

Please add a new PrivilegesBuilderSuite for Hudi as well. The IcebergCatalogPrivilegesBuilderSuite could be an example. New supported commands should be covered in both end-to-end tests in *RangerSparkExtensionSuite and the privilege object parsing tests in *PrivilegesBuilderSuite. The latter is important for maintaining compatibility and ensuring the intermediates.

Hudi is working on supporting v2 command. Currently, CREATE DATABASE does not support v2 command, so this place may not be able to test it yet. Maybe we only can add some test for the command that support v2

Well notices. But the concern is we should have a PrivilegesBuilderSuite for Hudi. It doesn't matter if Hudi only works on V1 only as you discovered. WDYT?
Is it possible to create a Hudi's PrivilegesBuilderSuite or maybe there's other way to test the intermediates previlge objects?

Yea, currently we only can add UT for supported hudi v2command. But I want to do it later after implement all the v1 scope, then to see how to do this for all supported V2 command. WDYT?

I may have missed your points. @AngersZhuuuu
It's not about the v1 or v2 commands. It's for ensuring intermediate objects are aligned to the final output in e2e tests.
Is it possible to introduce a subclass of PrivilegesBuilderSuite for Hudit this time? If not why?

I may have missed your points. @AngersZhuuuu It's not about the v1 or v2 commands. It's for ensuring intermediate objects are aligned to the final output in e2e tests. Is it possible to introduce a subclass of PrivilegesBuilderSuite for Hudit this time? If not why?

Even can't run beforeAll's CREATE DATABASE command. So maybe we can't introduce a subclass of PrivilegesBuilderSuite for Hudit this time

Alright, it's acceptable to me, if there's an unresolved obstacle in introducing a PrivilegesBuilderSuite for  Hudi for now.

Any more suggestion? ping @yaooqinn @pan3793 @bowenliang123

Have your fiexed the failing tests for spark 3.1?

@bowenliang123 Failed UT should be not related.

An excellent feature to have. Thanks, @AngersZhuuuu, for the contribution, and thanks @bowenliang123 @pan3793 for the check.
Merged to master


Adding a single RepositoryAction to build.

Environment#buildEnvVars can be called multiple times in build which can lead to something like http://i.imgur.com/Vsxz4R9.png.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Charts[Gateway] Unable to install chart in a new namespace

Bill of Materials or CLI Version
No response
Execution Environment
JUnit Extensions
Slf4j Logging Implementation
None
To Reproduce

Deploy chart in namespace-1
Attempt to deploy helm chart in namespace-2

It errors with message:
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "pod-monitoring-role" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata;

Describe the bug
There are two issues as below:

We are currently creating "pod-monitoring-role" ClusterRole to be able to run helm chart test container with necessary access. However, we don't need to create the ClusterRole every time we deploy the chart.

Therefore, "pod-monitoring-role" ClusterRole needs to be deployed only once as shared resource. Ideally, we should also be able to remove after helm chart test is executed.

Besides the shared GatewayClass also exhibit the same issue and therefore needs to be installed as shared resource.

Describe the expected behavior
A user should be able to deploy the helm chart to multiple namespaces
Whole JUnit/CLI Logs
helm install fst-namespace-test2 -n fst-lenin2  hedera-network

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "pod-monitoring-role" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "fst-namespace-test2": current value is "fst-namespace-test"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "fst-lenin2": current value is "fst-lenin"

Additional Context
No response
### Tasks
- [ ] https://github.com/hashgraph/full-stack-testing/issues/358
- [ ] https://github.com/hashgraph/full-stack-testing/issues/359
- [ ] https://github.com/hashgraph/full-stack-testing/issues/361

:tada: This issue has been resolved in version 0.12.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Is there a way to get the "Live Preview" Pre-Release?

On the README it says there is a https://github.com/shabegom/buttons#next-version-not-released-yet that lets buttons render in Live Preview mode.
This would be really useful for me. Is there a way for me to get access to this before it is "released"?
I would be willing to beta test/contribute/donate if that would help in making this a reality.
Thank you!

you pull and build the cm6-preview branch. I've abandoned it, though.


how do I install it?

Do i just download the jad/jar file and open it in my blackberry or is there something else i must do?

Hi !
There is many ways to install the app. The two I personnaly use :
-You can compile it and deploy it trough Eclipse (with BlackBerry SDK configured).
-You can install by using Blackberry Desktop Software (You will need the .cod & the .alx file it the same directory)
Here a video which show you how to : https://www.youtube.com/watch?v=mmt735G1oo0
Of course there is a way to do it directly from the phone, but I don't remember : I use it only once.  Is this true?

I that's true since something like one month and half. But there certainly is a way to bypass the new safety procedure. That's just I'm too fool to do some reverse engineering again.
-----Original Message-----
From: ducklin5<EMAIL_ADDRESS>Date: Mon, 02 Feb 2015 08:28:20
To<EMAIL_ADDRESS>Reply-To: mamatheking/CrapSnap<EMAIL_ADDRESS>Cc: Mathieu<EMAIL_ADDRESS>Subject: Re: [CrapSnap] how do I install it?  Is this true?

Reply to this email directly or view it on GitHub:
https://github.com/mamatheking/CrapSnap/issues/1#issuecomment-72486976

In order to install this, you can transfer this folder to your Blackberry and open CrapSnap.jad in the web browser.


initialize default Gift Entry settings in post-install script

Critical Changes
Includes initial creation of gift-entry settings in the post-install script for NPSP. Without this update, Org Telemetry will fail on a mixed DML error and disrupt our ability to collect telemetry.
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

**lurch: attach W-039793

Tracking W-039793


FAIL: TestPackageRenames

Running tests @ https://github.com/derekparker/delve/commit/04c4b019f7557344910ade621f68e2695eabe2e5 on Windows 10 with Go 1.8.3 / Go 1.9 beta 1 gives this:
--- FAIL: TestPackageRenames (2.10s)
        support.go:129: enabling recording for github.com/derekparker/delve/service/test_test.TestPackageRenames
        variables_test.go:54: Expected "interface {}(*struct { github.com/derekparker/delve/_fixtures/vendor/dir1/pkg.SomeType; X int }) *{github.com/derekparker/delve/_fixtures/vendor/dir1/pkg.SomeType: github.com/derekparker/delve/_fixtures/vendor/dir1/pkg.SomeT
ype {X: 1, Y: 2}, X: 10}" got "(unreadable interface type \"*struct { SomeType github.com/derekparker/delve/_fixtures/vendor/dir1/pkg.SomeType; X int }\" not found for 0xc04206baa8: no type entry found, use 'types' for a list of valid types)" (for variable astruct
2)

Are you sure this happens with go1.8.3? With 1.9 it's normal (see https://github.com/derekparker/delve/pull/824) but we are running integration tests on windows with 1.8 and this doesn't show up.

Yes, my environment was messed up. Sorry for the noise.


lack of info cmake

It could be easier to inform that packet "cmake tools for c++" need to be installed in visual studio installer.

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

ID: c6b25c8d-63c4-e903-69cc-a90b88f7b13d
Version Independent ID: 113c6b83-1457-d4ac-93d0-4177abb3b993
Content: Walkthrough: Compiling a Native C++ Program on the Command Line
Content Source: docs/build/walkthrough-compiling-a-native-cpp-program-on-the-command-line.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

@Piekarnik

It could be easier to inform that packet "cmake tools for c++" need to be installed in visual studio installer.

I think the point of the questioned page and example is about command-line use of the compiler and how the single command line will compile and link without any need for knowledge of additional tools.
I do think the instructions are a bit gnarly around preparing the code.  That's a different problem and cmake will not improve it.  My impressions is that the page on "Hello World" is much better as a starter.
If we're talking about building outside of Visual Studio (but using the build tools from a command prompt), I think introduction of make and cmake is best deferred until a beginner encounters the situations that these different tools facilitate.   I have no idea how that is (or could be) handled at Microsoft Learn.


Should we support brms' centering transform?

See the center arg. of brmsformula.

@neerajprad Is this something we could support upstream with more generic transformations in Pyro, as in e.g. this paper?

While we don't automatically reparametrize a model, a user can easily do so in NumPyro (not Pyro though) using TransformedDistributions. See this example on Neal's funnel. i.e. instead of using dist.Normal(mu, sigma) they can use dist.TransformedDistribution(dist.Normal(0., 1.), AffineTransform(mu, sigma)).
I think that should be sufficient for brmp since all the latents are being generated by us.

I think we're talking about two different things here. The thing I had in mind (which I called "brms' centering transform") is a transform of the data (mean centering) which is enabled by default. I'm not sure whether this is important, but if we don't have it we might simply want to note it as a difference between the two systems.


Changes in fuguecli require greater access control

dynamodb:Query needs to be added otherwise
fugue status
[ ERROR ] There was a problem executing this command.
   Reason: An error occurred (AccessDeniedException) when calling the Query operation: User: arn:aws:iam::877453989326:user/rbac_user_0 is not authorized to perform: dynamodb:Query on resource: arn:aws:dynamodb:us-east-1:877453989326:table/fugue-cli-responses

for fuguecli versions 1.0.2-1936 and onwards

Yeah I hit this problem too. Can we reduce this to only allowing queries to the fugue-cli-responses table instead of *?

Fugue  fugue policy generate-secret, we also need:
    {
        "Sid": "Stmt1484850039000",
        "Effect": "Allow",
        "Action": [
            "kms:Decrypt"
        ],
        "Resource": [
            "*"
        ]
    }

These changes were included in https://github.com/fugue/fugue-user-iam-templates/pull/3
This can be closed.


NDArray.set() fails on linux with " Inplace update to inference tensor outside InferenceMode"

Description
The NDArray.set() fails when trying to update tensors in a post-processing stage with a message:

Inplace update to inference tensor outside InferenceMode is not allowed.You can make a clone to get a normal tensor before doing inplace update.See https://github.com/pytorch/rfcs/pull/17 for more details.

This behavior is observed when running the code with PyTorch engine on a linux machine, the same code runs without any errors on a Mac M1 Pro. The work-around is to first duplicate the tensor by calling a NDArray.duplicate() and performing the .set() on the new tensor.
Expected Behavior
The PyTorch implementation of the NDArray should either perform the tensor duplication when trying to modify the tensors outside of the InferenceMode, or these tensors should be made immutable.
Error Message

Exception in thread "main" ai.djl.translate.TranslateException: ai.djl.engine.EngineException: Inplace update to inference tensor outside InferenceMode is not allowed.You can make a clone to get a normal tensor before doing inplace update.See https://github.com/pytorch/rfcs/pull/17 for more details.
Caused by: ai.djl.engine.EngineException: Inplace update to inference tensor outside InferenceMode is not allowed.You can make a clone to get a normal tensor before doing inplace update.See https://github.com/pytorch/rfcs/pull/17 for more details.
at ai.djl.pytorch.jni.PyTorchLibrary.torchMaskedPut(Native Method)
at ai.djl.pytorch.jni.JniUtils.booleanMaskSet(JniUtils.java:416)
at ai.djl.pytorch.engine.PtNDArrayIndexer.set(PtNDArrayIndexer.java:82)
at ai.djl.ndarray.index.NDArrayIndexer.set(NDArrayIndexer.java:157)
at ai.djl.ndarray.NDArray.set(NDArray.java:469)
at ai.djl.ndarray.NDArray.set(NDArray.java:490)
at processOutput(PtBertQATranslator.java:116)

How to Reproduce?
Create a custom QATranslator, override the processOutput() method like
   public List<QAResult> processOutput(TranslatorContext ctx, NDList list) {
        NDManager manager = ctx.getNDManager();
        NDArray start_logits = list.get(0);
        boolean[] bad_tokens_mask = new boolean[128];
        NDArray nd_bad_tokens_mask = manager.create(bad_tokens_mask);
        start_logits.set(nd_bad_tokens_mask, -10000.);

Steps to reproduce
(Paste the commands you ran that produced the error.)
Create a QA predictor using a model based on the custom translator and using "PyTorch" engine. Run predictor.predict() on a linux machine.
What have you tried to solve it?
Making a duplicate of the "output" tensors resolves the issue:  NDArray startLogits = list.get(0).duplicate();
Environment Info
Please run the command ./gradlew debugEnv from the root directory of DJL (if necessary, clone DJL first). It will output information about your system, environment, and installation that can help us debug your issue. Paste the output of the command below:
./gradlew debugEnv
Starting a Gradle Daemon (subsequent builds will be faster)

> Task :integration:debugEnv
[DEBUG] - Registering EngineProvider: XGBoost
[DEBUG] - Registering EngineProvider: MXNet
[DEBUG] - Registering EngineProvider: PyTorch
[DEBUG] - Registering EngineProvider: TensorFlow
[DEBUG] - Found default engine: MXNet
----------- System Properties -----------
java.specification.version: 17
sun.jnu.encoding: UTF-8
java.class.path: /mnt/ssd4tb/user/Software/djl/integration/build/classes/java/main:/mnt/ssd4tb/user/Software/djl/integration/build/resources/main:/home/user/.gradle/caches/modules-2/files-2.1/commons-cli/commons-cli/1.5.0/dc98be5d5390230684a092589d70ea76a147925c/commons-cli-1.5.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-slf4j-impl/2.17.2/183f7c95fc981f3e97d008b363341343508848e/log4j-slf4j-impl-2.17.2.jar:/mnt/ssd4tb/user/Software/djl/basicdataset/build/libs/basicdataset-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/model-zoo/build/libs/model-zoo-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/testing/build/libs/testing-0.18.0-SNAPSHOT.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.testng/testng/7.5/1416a607fae667c14e390b484e8d02b5824c0674/testng-7.5.jar:/mnt/ssd4tb/user/Software/djl/engines/mxnet/mxnet-model-zoo/build/libs/mxnet-model-zoo-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/pytorch/pytorch-model-zoo/build/libs/pytorch-model-zoo-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/pytorch/pytorch-jni/build/libs/pytorch-jni-1.11.0-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/tensorflow/tensorflow-model-zoo/build/libs/tensorflow-model-zoo-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/ml/xgboost/build/libs/xgboost-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/mxnet/mxnet-engine/build/libs/mxnet-engine-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/pytorch/pytorch-engine/build/libs/pytorch-engine-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/engines/tensorflow/tensorflow-engine/build/libs/tensorflow-engine-0.18.0-SNAPSHOT.jar:/mnt/ssd4tb/user/Software/djl/api/build/libs/api-0.18.0-SNAPSHOT.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/1.7.36/6c62681a2f655b49963a5983b8b0950a6120ae14/slf4j-api-1.7.36.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.17.2/fa43ba4467f5300b16d1e0742934149bfc5ac564/log4j-core-2.17.2.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-api/2.17.2/f42d6afa111b4dec5d2aea0fe2197240749a4ea6/log4j-api-2.17.2.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-csv/1.9.0/b59d8f64cd0b83ee1c04ff1748de2504457018c1/commons-csv-1.9.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/com.google.code.findbugs/jsr305/3.0.1/f7be08ec23c21485b9b5a1cf1654c2ec8c58168d/jsr305-3.0.1.jar:/home/user/.gradle/caches/modules-2/files-2.1/com.beust/jcommander/1.78/a3927de9bd6f351429bcf763712c9890629d8f51/jcommander-1.78.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.webjars/jquery/3.5.1/2392938e374f561c27c53872bdc9b6b351b6ba34/jquery-3.5.1.jar:/home/user/.gradle/caches/modules-2/files-2.1/ml.dmlc/xgboost4j_2.12/1.6.0/4623e78f614c998b4600c1cc58441ce06d80ba49/xgboost4j_2.12-1.6.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/commons-logging/commons-logging/1.2/4bfc12adfe4842bf07b657f0369c4cb522955686/commons-logging-1.2.jar:/home/user/.gradle/caches/modules-2/files-2.1/com.google.code.gson/gson/2.9.0/8a1167e089096758b49f9b34066ef98b2f4b37aa/gson-2.9.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/net.java.dev.jna/jna/5.11.0/27770efb6329f092f895c7329662d1aa8ee8c0ac/jna-5.11.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.21/4ec95b60d4e86b5c95a0e919cb172a0af98011ef/commons-compress-1.21.jar:/mnt/ssd4tb/user/Software/djl/engines/tensorflow/tensorflow-api/build/libs/tensorflow-api-0.18.0-SNAPSHOT.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.tensorflow/tensorflow-core-api/0.4.0/2ac35ca087607cce0e5419953cc1ef0c3a5edaea/tensorflow-core-api-0.4.0.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.bytedeco/javacpp/1.5.6/1f18a820aadd943577b0b372554f9e35e1232e25/javacpp-1.5.6.jar:/home/user/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.19.2/e958ce38f96b612d3819ff1c753d4d70609aea74/protobuf-java-3.19.2.jar:/home/user/.gradle/caches/modules-2/files-2.1/org.tensorflow/ndarray/0.3.3/1b6d8cc3e3762f6e465b884580d9fc17ab7aeb4/ndarray-0.3.3.jar
java.vm.vendor: Red Hat, Inc.
sun.arch.data.model: 64
user.variant:
java.vendor.url: https://www.redhat.com/
java.vm.specification.version: 17
os.name: Linux
sun.java.launcher: SUN_STANDARD
sun.boot.library.path: /usr/lib/jvm/java-17-openjdk-<IP_ADDRESS>.7-1.fc36.x86_64/lib:/usr/lib/jvm/java-17-openjdk-<IP_ADDRESS>.7-1.fc36.x86_64/lib
sun.java.command: ai.djl.integration.util.DebugEnvironment
jdk.debug: release
sun.cpu.endian: little
org.gradle.appname: gradlew
user.language: en
java.specification.vendor: Oracle Corporation
java.version.date: 2022-04-19
java.home: /usr/lib/jvm/java-17-openjdk-<IP_ADDRESS>.7-1.fc36.x86_64
ai.djl.logging.level: debug
org.gradle.internal.http.connectionTimeout: 60000
file.separator: /
java.vm.compressedOopsMode: Zero based
line.separator:

java.vm.specification.vendor: Oracle Corporation
java.specification.name: Java Platform API Specification
sun.management.compiler: HotSpot 64-Bit Tiered Compilers
java.runtime.version: 17.0.3+7
path.separator: :
os.version: 5.17.12-300.fc36.x86_64
java.runtime.name: OpenJDK Runtime Environment
file.encoding: UTF-8
java.vm.name: OpenJDK 64-Bit Server VM
java.vendor.version: 21.9
java.vendor.url.bug: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=java-17-openjdk&version=36
java.io.tmpdir: /tmp
org.gradle.internal.http.socketTimeout: 120000
java.version: 17.0.3
user.dir: /mnt/ssd4tb/user/Software/djl/integration
os.arch: amd64
java.vm.specification.name: Java Virtual Machine Specification
native.encoding: UTF-8
java.library.path: /usr/local/cuda-10.2/lib64:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
java.vm.info: mixed mode, sharing
java.vendor: Red Hat, Inc.
java.vm.version: 17.0.3+7
sun.io.unicode.encoding: UnicodeLittle
library.jansi.path: /home/user/.gradle/native/jansi/1.18/linux64
java.class.version: 61.0
org.gradle.internal.publish.checksums.insecure: true

--------- Environment Variables ---------
PATH: /usr/local/cuda-10.2/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin
LD_LIBRARY_PATH: /usr/local/cuda-10.2/lib64
-------------- Directories --------------
temp directory: /tmp
DJL cache directory: /home/user/.djl.ai
Engine cache directory: /home/user/.djl.ai

------------------ CUDA -----------------
GPU Count: 1
CUDA: 102
ARCH: 52
GPU(0) memory used: 295370752 bytes

----------------- Engines ---------------
DJL version: 0.18.0
Default Engine: MXNet
[WARN ] - No matching cuda flavor for linux found: cu102mkl/sm_52.
[DEBUG] - Loading mxnet library from: /home/user/.djl.ai/mxnet/1.9.0-mkl-linux-x86_64/libmxnet.so
Default Device: cpu()
PyTorch: 2
MXNet: 0
XGBoost: 10
TensorFlow: 3

--------------- Hardware --------------
Available processors (cores): 48
Byte Order: LITTLE_ENDIAN
Free memory (bytes):<PHONE_NUMBER>
Maximum memory (bytes):<PHONE_NUMBER>8
Total memory available to JVM (bytes):<PHONE_NUMBER>
Heap committed:<PHONE_NUMBER>
Heap nonCommitted: 31391744
GCC:
gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

BUILD SUCCESSFUL in 8s
44 actionable tasks: 1 executed, 43 up-to-date

From the error message, it shows that you are using the old feature of setter.
at ai.djl.pytorch.jni.PyTorchLibrary.torchMaskedPut(Native Method)
at ai.djl.pytorch.jni.JniUtils.booleanMaskSet(JniUtils.java:416)
at ai.djl.pytorch.engine.PtNDArrayIndexer.set(PtNDArrayIndexer.java:82)
at ai.djl.ndarray.index.NDArrayIndexer.set(NDArrayIndexer.java:157)
at ai.djl.ndarray.NDArray.set(NDArray.java:469)
at ai.djl.ndarray.NDArray.set(NDArray.java:490)
at processOutput(PtBertQATranslator.java:116)

Could you try the setter with NDIndex? It will utilize the new feature.
start_logits.set(new NDIndex("{}", nd_bad_tokens_mask), -10000.);

This is in version 0.18.0, which is just released.

There is no change to this behavior when I use the NDArray.set(NDIndex, Number), the error is coming from the way PyTorch restricts the modification of the tensors after inference:
Caused by: ai.djl.engine.EngineException: Inplace update to inference tensor outside InferenceMode is not allowed.You can make a clone to get a normal tensor before doing inplace update.See https://github.com/pytorch/rfcs/pull/17 for more details.

I see. Ok, if this is a bug in Pytorch, can you file an issue to PyTorch to see if they can solve this from their side?

@demq
Are you able to reproduce the issue in python?

I need to clarify the reason I think this issue a bug.

Pytorch behaves as  expected, since the tensors created while in "c10:InferenceMode" are made immutable outside of "InferenceMode": https://pytorch.org/cppdocs/notes/inference_mode.html

DJL appears to be invoking the "InferenceMode" for the "newer" version of torch: https://github.com/deepjavalibrary/djl/blob/master/engines/pytorch/pytorch-native/src/main/native/ai_djl_pytorch_jni_PyTorchLibrary_inference.cc
struct JITCallGuard {
#ifdef V1_10_X
  torch::autograd::AutoGradMode no_autograd_guard{false};
  torch::NoGradGuard no_grad;
#else
  c10::InferenceMode guard;
  torch::jit::GraphOptimizerEnabledGuard no_optimizer_guard{false};
#endif
};

The V1_10_X is set if PT_OLD_VERSION is true, which  on its own is set in
https://github.com/deepjavalibrary/djl/blob/master/engines/pytorch/pytorch-native/build.cmd
if "%VERSION%" == "1.10.0" (
    set PT_OLD_VERSION=1
)
if "%VERSION%" == "1.9.1" (
    set PT_OLD_VERSION=1
)

I suppose the M1 version of the djl is compiled with the V1_10_X defined, so the c10::InferenceMode guard; is not defined, while the linux version has it.

DJL Needs to either Document this behavior, or ensure the tensors can be modified after the inference by either using the torch::NoGradGuard no_grad;, or returning the duplicates of the tensors created outside of the InfereceMode

@demq Thank you so much for this detailed investigation! The purpose of InferenceMode guard, is to free the array from being changed by autograd in the inference mode. We should try to keep consistent with this. But in your case, you need to modify the inference array, we need to think how to resolve it.
@frankfliu Which strategy should we choose?

I have just updated the document of processOutput to notify this behaviour. So when users try to implement postProcessor, they will see this link.


Require filename resolution breaks with suffixes that look like extensions

Steps to reproduce:
require 'something.stuff' # resembles a real file called something.stuff.rb or something.stuff.js

Expected results:
Path resolve works
Actual results:
.stuff is considered an extension and since the file can't be found, resolution stops and an error occurs

Fixed, waiting for https://github.com/cj/opal-webpack/pull/25 to be accepted first

Putting on hold because the branch of code that fixes this is obsolete if https://github.com/cj/opal-webpack/pull/28 is merged


Add an article of how to deploy the solution with ADFS.

Describe the issue
As a customer, I have my own ADFS and I'd like to use existing AD.
Links
https://awslabs.github.io/log-hub/en/implementation-guide/deployment/

completed. Here is the link https://awslabs.github.io/log-hub/en/implementation-guide/deployment/with-oidc/#option-4-adfs-openid-connect-client


Gruntfile working?

Please take a look at the grunfile config. Thanks guys, you're the best.

This looks good.


[libwebp] Do not enable SSE4 support with /arch:AVX

The library source, in file cmake/cpu.cmake:36 sets /arch:AVX compiler flag to enable SSE4 support. It even has a comment stating it is intentional.
This 'ofcause enables the AVX instruction-set, resulting in a executable that will not run on a CPU without AVX.
e.q. function WebPDecode will crash with exception 0xC000001d 'Illegal Instruction' on a Intel Atom x5 CPU (build details in my case: VS2019, Release, x86, Cross-Compiled, both Win10).
The library should be clear about which instruction-set it is using, SSE4 or AVX.
As a workaround I propose an addition to the vcpkg-patch file: '0007-fix-arm-build.patch' that removes the '/arch:AVX' option.
diff --git a/cmake/cpu.cmake b/cmake/cpu.cmake
index da9a42a4..cb7a050d 100644
--- a/cmake/cpu.cmake
+++ b/cmake/cpu.cmake
@@ -33,7 +33,7 @@ set(WEBP_SIMD_FILE_EXTENSIONS
     "_sse41.c;_sse2.c;_mips32.c;_mips_dsp_r2.c;_neon.c;_msa.c")
 if(MSVC)
   # MSVC does not have a SSE4 flag but AVX support implies SSE4 support.
-  set(SIMD_ENABLE_FLAGS "/arch:AVX;/arch:SSE2;;;;")
+  set(SIMD_ENABLE_FLAGS "/arch:SSE2;;;;;")
   set(SIMD_DISABLE_FLAGS)
 else()
   set(SIMD_ENABLE_FLAGS
@@ -73,7 +73,7 @@ foreach(I_SIMD RANGE ${WEBP_SIMD_FLAGS_RANGE})
     set(CMAKE_REQUIRED_FLAGS ${SIMD_COMPILE_FLAG})
     webp_check_compiler_flag(${WEBP_SIMD_FLAG} ${WEBP_ENABLE_SIMD})
   else()
-    if(MSVC)
+    if(MSVC AND NOT (CMAKE_GENERATOR_PLATFORM MATCHES "^ARM"))
       list(GET SIMD_ENABLE_FLAGS ${I_SIMD} SIMD_COMPILE_FLAG)
     else()
       set(SIMD_COMPILE_FLAG " ")

@0xECEAD ,Thanks for posting this issue，Have you tested your ideas? Is it feasible?

The proposed patch works.
It still uses the SSE4 instructions, because they are included as intrinsics, (no harm done).
The compiler no longer emits AVX instructions, for code-optimization, only SSE2.

@0xECEAD ,I tested your suggestion but there seems to be a problem
-- Performing Test WEBP_HAVE_FLAG_MSA
-- Performing Test WEBP_HAVE_FLAG_MSA - Failed
CMake Error at cmake/cpu.cmake:72 (list):
  list index: 5 out of range (-5, 4)
Call Stack (most recent call first):
  cmake/deps.cmake:138 (include)
  CMakeLists.txt:51 (include)

-- Performing Test WEBP_HAVE_FLAG_MSA
-- Performing Test WEBP_HAVE_FLAG_MSA - Failed
-- Configuring incomplete, errors occurred!

Hi JonLiu,
you are right, the patch file is not correct, sorry.
I attached a new version.
and 'successful' build log.
0007-fix-arm-build.patch.txt
stdout-x64-windows.log
Best regards,
Enceladus

Hi @0xECEAD ,Is your vcpkg the latest version? The patch 0007-fix-arm-build.patch already exists in the latest vcpkg, but in the patch, only if (MSVC) is changed to if (MSVC AND NOT (CMAKE_GENERATOR_PLATFORM MATCHES "^ARM")), I will follow the patch you provided I re-made the previous patch, but it still doesn't work, and the problem is the same. Can you check again? The following is the patch I remade and the architecture log Thanks
diff --git a/cmake/cpu.cmake b/cmake/cpu.cmake
index da9a42a..cb7a050 100644
--- a/cmake/cpu.cmake
+++ b/cmake/cpu.cmake
@@ -33,7 +33,7 @@ set(WEBP_SIMD_FILE_EXTENSIONS
     "_sse41.c;_sse2.c;_mips32.c;_mips_dsp_r2.c;_neon.c;_msa.c")
 if(MSVC)
   # MSVC does not have a SSE4 flag but AVX support implies SSE4 support.
-  set(SIMD_ENABLE_FLAGS "/arch:AVX;/arch:SSE2;;;;")
+  set(SIMD_ENABLE_FLAGS "/arch:SSE2;;;;")
   set(SIMD_DISABLE_FLAGS)
 else()
   set(SIMD_ENABLE_FLAGS
@@ -73,7 +73,7 @@ foreach(I_SIMD RANGE ${WEBP_SIMD_FLAGS_RANGE})
     set(CMAKE_REQUIRED_FLAGS ${SIMD_COMPILE_FLAG})
     webp_check_compiler_flag(${WEBP_SIMD_FLAG} ${WEBP_ENABLE_SIMD})
   else()
-    if(MSVC)
+    if(MSVC AND NOT (CMAKE_GENERATOR_PLATFORM MATCHES "^ARM"))
       list(GET SIMD_ENABLE_FLAGS ${I_SIMD} SIMD_COMPILE_FLAG)
     else()
       set(SIMD_COMPILE_FLAG " ")

config-x86-windows-out.log

Hi JonLiu, thank you for testing/trying.
I just did a clean checkout, bootstrap-build vcpkg. Then I overwrite the 0007-fix-arm-build.patch with my file 0007-fix-arm-build.patch.txt. And install the libwebp-library. That all works without errors on my machine. See console-my-patch.log.
When I do the same with your patch, it fails with error: corrupt patch at line 22. See console-your-patch.log.
I don't know why but it always seems complicated to patch a patch-file.. :-)
SideNote: I found that the number of items in the SIMD_ENABLE_FLAGS should stay the same, so you need to keep the number of ; separators (5x). Your patch misses one (although that is not the cause of this error).
Best Regards,
Enceladus

this fix seems to have broken the libwebp:x86-windows-static build
https://github.com/microsoft/vcpkg/issues/32940

Note https://github.com/microsoft/vcpkg/pull/21644#discussion_r1284053075.


AudioMate links are dead

Could update the README or figure out where AudioMate still exists, if it does...

Updated, thanks!


many users in system

hi
when you have many user the script go slowly.
for example i have 5000 user and for every user i have 1 secret the ping go very high (4000) and everything go slowly
i see the code in line 664 we have for loop for check secret. this loop Scrolling all secret key in config file for every connection. in this case we have 5000 secret this is why the script go slowly.
is there any way to fix this problem?

hello, I am afraid the telegram protocol doesn't support users. Now the proxy tries to decrypt the first packet with various secrets until it succeed.
To fix the problem it is possible to run several proxy servers on different ports with smaller amount of users each.

can we have threading for that?
for example for each secret we have we check it in different thread and when one of the thread found that, message to all other thread to stop working.
i not know python but i thing this work for it

the threading will not decrease the overall cpu time, the different ports approach with smaller number of users should do the better work


Refresh test dbdumps

As mentioned in this issue https://github.com/opencollective/frontend/issues/467, it looks like the dbdumps are outdated.
Is there a way to refresh them?

I don't think we have a working solution for seeding data into our dev database. We only have some tools for updating the schema of the binary dumps and some scripts to copy the production database to a local one and scramble sensitive data.
Although we have thought about keeping a binary dump to allow people to see some content when they setup open collective, I wonder if there's an easier way of doing it.

I'm going to try replacing the dbdumps with Sequelize seeder files to enable easier refreshing of local data and a reliable getting started experience.


"Sign your attempt" is too generic.

It's ok that it defaults to "sign your attempt" but for known actions like opening wallet or showing seed phrase. It should have a clear text what you're doing rather than "sign your attempt".
Screenshot is text shown after trying to show seed phrase.

Also see linked issue, same issue in a different place.


BREAKING CHANGE: remove -e in favor of NODE_ENV

Remove -e flag in favor of NODE_ENV which will behave the same way as the -e flag.
Dynamic config still works the same way and we default to development when running suites.

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.'}

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #318 opened

Start Time: 2021-06-24T15:18:56.563+0000

Duration: 27 min 1 sec

Commit: fc4fe01d79fb226b54542b0049a7bf83ad85a74e

Test stats :test_tube:

Test
Results

Failed
0

Passed
110

Skipped
0

Total
110

Trends :test_tube:

Log output
Expand to view the last 100 lines of log output

[2021-06-24T15:28:07.564Z]  > git rev-parse HEAD^{commit} # timeout=10
[2021-06-24T15:28:07.572Z]  > git config core.sparsecheckout # timeout=10
[2021-06-24T15:28:07.576Z]  > git checkout -f fc4fe01d79fb226b54542b0049a7bf83ad85a74e # timeout=15
[2021-06-24T15:28:11.105Z] Commit message: "BREAKING CHANGE: remove -e in favor of NODE_ENV"
[2021-06-24T15:28:11.105Z] Cleaning workspace
[2021-06-24T15:28:11.183Z]  > git --version # timeout=10
[2021-06-24T15:28:11.187Z]  > git --version # 'git version 2.17.1'
[2021-06-24T15:28:11.197Z] fatal: bad object bbed8ab717206e63fa6cc1cef7d35f4a13f717ab
[2021-06-24T15:28:11.107Z]  > git rev-parse --verify HEAD # timeout=10
[2021-06-24T15:28:11.126Z] Resetting working tree
[2021-06-24T15:28:11.126Z]  > git reset --hard # timeout=10
[2021-06-24T15:28:11.147Z]  > git clean -fdx # timeout=10
[2021-06-24T15:28:13.207Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/src/github.com/elastic/synthetics
[2021-06-24T15:28:26.999Z] + set +x
[2021-06-24T15:28:26.999Z] => Downloading nvm from git to '/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/.nvm'
[2021-06-24T15:28:26.999Z]
=> Initialized empty Git repository in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/.nvm/.git/
[2021-06-24T15:28:27.567Z] From https://github.com/nvm-sh/nvm
[2021-06-24T15:28:27.567Z]  * [new tag]         v0.37.1    -> v0.37.1
[2021-06-24T15:28:27.567Z] => Compressing and cleaning up git repository
[2021-06-24T15:28:27.567Z]
[2021-06-24T15:28:27.567Z] => Profile not found. Tried ~/.bashrc, ~/.bash_profile, ~/.zshrc, and ~/.profile.
[2021-06-24T15:28:27.567Z] => Create one of them and run this script again
[2021-06-24T15:28:27.567Z]    OR
[2021-06-24T15:28:27.567Z] => Append the following lines to the correct file yourself:
[2021-06-24T15:28:27.567Z]
[2021-06-24T15:28:27.567Z] export NVM_DIR="$HOME/.nvm"
[2021-06-24T15:28:27.567Z] [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[2021-06-24T15:28:27.567Z]
[2021-06-24T15:28:29.474Z] => Close and reopen your terminal to start using nvm or run the following to use it now:
[2021-06-24T15:28:29.474Z]
[2021-06-24T15:28:29.474Z] export NVM_DIR="$HOME/.nvm"
[2021-06-24T15:28:29.474Z] [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[2021-06-24T15:28:29.474Z] Installing latest LTS version.
[2021-06-24T15:28:29.474Z] v14.17.1 is already installed.
[2021-06-24T15:28:29.732Z] Now using node v14.17.1 (npm v6.14.13)
[2021-06-24T15:28:29.851Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/src/github.com/elastic/synthetics
[2021-06-24T15:28:30.164Z] + chmod -R ugo+rw examples
[2021-06-24T15:28:30.191Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/src/github.com/elastic/synthetics/__tests__/e2e
[2021-06-24T15:28:30.505Z] + npm run test
[2021-06-24T15:28:30.505Z]
[2021-06-24T15:28:30.505Z] > e2e-synthetics@ test /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/src/github.com/elastic/synthetics/__tests__/e2e
[2021-06-24T15:28:30.505Z] > npm i && npm run setup &&  bash scripts/test.sh
[2021-06-24T15:28:30.505Z]
[2021-06-24T15:28:33.794Z] added 3 packages from 4 contributors and audited 178 packages in 2.398s
[2021-06-24T15:28:35.700Z]
[2021-06-24T15:28:35.700Z] 66 packages are looking for funding
[2021-06-24T15:28:35.700Z]   run `npm fund` for details
[2021-06-24T15:28:35.700Z]
[2021-06-24T15:28:35.700Z] found 1 moderate severity vulnerability
[2021-06-24T15:28:35.700Z]   run `npm audit fix` to fix them, or `npm audit` for details
[2021-06-24T15:28:35.700Z]
[2021-06-24T15:28:35.700Z] > e2e-synthetics@ setup /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/src/github.com/elastic/synthetics/__tests__/e2e
[2021-06-24T15:28:35.700Z] > bash scripts/setup.sh
[2021-06-24T15:28:35.700Z]
[2021-06-24T15:28:35.958Z]
[2021-06-24T15:28:35.958Z] Temporary folder
[2021-06-24T15:28:35.958Z] Temporary files will be stored in: ./tmp
[2021-06-24T15:28:35.958Z]
[2021-06-24T15:28:35.958Z] Starting elasticsearch , kibana and synthetics docker
[2021-06-24T15:28:35.958Z]
[2021-06-24T15:28:35.958Z]
[2021-06-24T15:28:35.958Z] Waiting for synthetics docker to start...
[2021-06-24T15:28:35.958Z] Error: No such object: synthetics
[2021-06-24T15:28:45.945Z] Error: No such object: synthetics
[2021-06-24T15:28:58.152Z] Error: No such object: synthetics
[2021-06-24T15:29:06.269Z] Error: No such object: synthetics
[2021-06-24T15:29:16.255Z] Error: No such object: synthetics
[2021-06-24T15:29:26.233Z] Error: No such object: synthetics
[2021-06-24T15:29:38.442Z] ✅ Setup completed successfully. Running e2e tests...
[2021-06-24T15:29:38.442Z] Waiting for Elastic Search  to start
[2021-06-24T15:30:17.335Z] Waiting for Synthetics to send data to ES for test monitor
[2021-06-24T15:45:44.526Z] Cancelling nested steps due to timeout
[2021-06-24T15:45:44.534Z] Sending interrupt signal to process
[2021-06-24T15:45:54.584Z] scripts/test.sh: line 26:  5598 Terminated              SYNTHETICS_JUNIT_FILE='junit.xml' npx @elastic/synthetics uptime.journey.ts --reporter junit
[2021-06-24T15:45:54.585Z] npm ERR! code ELIFECYCLE
[2021-06-24T15:45:54.585Z] npm ERR! errno 143
[2021-06-24T15:45:54.585Z] npm ERR! e2e-synthetics@ test: `npm i && npm run setup &&  bash scripts/test.sh`
[2021-06-24T15:45:54.585Z] npm ERR! Exit status 143
[2021-06-24T15:45:54.585Z] npm ERR!
[2021-06-24T15:45:54.585Z] npm ERR! Failed at the e2e-synthetics@ test script.
[2021-06-24T15:45:54.585Z] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[2021-06-24T15:45:54.585Z]
[2021-06-24T15:45:54.585Z] npm ERR! A complete log of this run can be found in:
[2021-06-24T15:45:54.585Z] npm ERR!     /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318/.npm/_logs/2021-06-24T15_45_49_997Z-debug.log
[2021-06-24T15:45:54.594Z] script returned exit code 143
[2021-06-24T15:45:55.834Z] Post stage
[2021-06-24T15:45:55.869Z] Archiving artifacts
[2021-06-24T15:45:56.024Z] Recording test results
[2021-06-24T15:45:56.133Z] None of the test reports contained any result
[2021-06-24T15:45:56.143Z] [Checks API] No suitable checks publisher found.
[2021-06-24T15:45:56.400Z] Stage "Release" skipped due to earlier failure(s)
[2021-06-24T15:45:56.441Z] Stage "Release" skipped due to earlier failure(s)
[2021-06-24T15:45:56.519Z] Stage "Release" skipped due to earlier failure(s)
[2021-06-24T15:45:56.905Z] Running on Jenkins in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-318
[2021-06-24T15:45:56.990Z] [INFO] getVaultSecret: Getting secrets
[2021-06-24T15:45:57.036Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-06-24T15:45:57.985Z] + chmod 755 generate-build-data.sh
[2021-06-24T15:45:57.985Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-318/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-318/runs/1 ABORTED 1621150
[2021-06-24T15:45:57.985Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-318/runs/1/steps/?limit=10000 -o steps-info.json
[2021-06-24T15:45:57.985Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-318/runs/1/tests/?status=FAILED -o tests-errors.json


Navbar styling issue

Navbar buttons get pushed to end when user is logged in.

Also add testimonials and faq s to thenavbar


NomCom feedback - volunteer primary affiliation

Description
This is something of a procedural request, but a small tweak to the tool might go a long way to making the NomCom process more transparent.
The basic idea is to add a field to feedback forms so that people providing feedback can volunteer information about their own affiliation.  This would be voluntary, but it would help greatly in going through feedback to have this information.  Too often, positive feedback on a nominee is dominated by their colleagues and having affiliation, even voluntarily given, would help filter that feedback.
The concrete suggestion is to offer a blank text box on the form where people can type their affiliation.  Ideally, we'd save that for a short amount of time so that people don't have to type it repeatedly, but not keep it for any significant time (a session-bound cookie with a short-ish timer would be good).
Code of Conduct

[x] I agree to follow the IETF's Code of Conduct

How about using their datatracker login to point to their public page as well?

That is a separable, but reasonable, thing, I think.