Consider adding spell checking to CI

Description of the new feature/enhancement

https://github.com/microsoft/terminal/pull/4295#issuecomment-582022434 asked if it was possible to have automated spell checking in the same way that clang-tidy rules are run by CI
Proposed technical implementation details (optional)
I have a live opensource integration running w/ Travis in the checkstyle project:
https://github.com/checkstyle/checkstyle/blob/master/.ci/test-spelling-unknown-words.sh
And yesterday I finally wrote a version that we're going to use internally w/ Jenkins:
https://github.com/jsoref/spelling-ci/tree/jenkins-ci-gsutil
That branch includes the dependencies. I'm not sure whether Windows Server CI is Perl friendly. If it is, then migrating the Bash bits to Perl is manageable. If it isn't, then it probably means porting the entire thing.
The code isn't particularly complicated, so I may end up just hosting it in a bunch of languages (Perl/Python/JavaScript). (This general task has been on my todo list for a number of years.)

As noted in https://github.com/microsoft/terminal/pull/4295#issuecomment-582035079, one has to select a Dictionary. It looks like Visual Studio is using Hunspell. I've worked w/ it in the past. http://wordlist.aspell.net/dicts/ -- the format for its wordlist isn't quite flat, so it would take a bit of code to properly handle, but not a whole lot (basically each line has an optional suffix that is essentially a way to compress acceptable variations of a word).

This would definitely be good. Thanks for doing a first pass on our code, as well!
Taking Triage off, leaving on backlog.

So, I've finally packaged things up nicely enough that they might be usable for others.
Overview
It's available as an action.
Configuration is basically ~4 things:

the workflow that uses the action
references for how to get the whitelist+exclusions
excluded paths
whitelisted tokens

Output
Output comes in a couple of flavors:

Visual Studio matcher (adopted by GitHub) output

Annotations (based on the matcher output, but it seems like you're limited to about 10...), e.g. https://github.com/jsoref/terminal/commit/c8e60639dd8f70c89065f37eaeb220e605343b73#annotation_123330796123330796

A comment, e.g. https://github.com/jsoref/terminal/commit/c8e60639dd8f70c89065f37eaeb220e605343b73#commitcomment-37449411 which lists new misspellings and offers a rough idea of how to manage the whitelist.

Configuration
The whitelist can live in the same repo & branch as the code, I'm not a huge fan of this as it means that other random spelling tools have to learn to ignore it as well. If you want to do this, it's pretty easy, you'd just add the two files to the excludes.txt file and configure the bucket to be ./path/to/parent/of/project (you can use project=. to flatten things as well).
The version I've prototyped here checks out a distinct branch from the same repository and then provides that directory to the engine. -- I plan to add better support for this format (probably by supporting bucket='git:' to mean "use this repository, just get the files from branch=$project". The whitelist/excludes can also live in other repositories or be retrieved from https:/gs: urls -- in these cases, the tool will give correct instructions for updating.
Warnings/Caveats
Note: while the tool suggests how to whitelist, you're really supposed to check to see if the word is misspelled first (someone sheepishly came to me and said something like "oh ... your tool caught an actual error, but instead of paying attention, I just whitelisted it").
Caveats: forks of repositories don't run Actions out of the box, and when they come back as pull requests, their token is basically a read-only token, which is not terribly helpful for reviewing a PR. To address that, there's a third mode (beyond pull_request and push) for schedule which will try to iterate over open PRs, identify foreign ones and review them.
Disclaimers
This code is in its early stages, and I haven't yet deployed it into a large repository. "You could be the early adopter."

@miniksa, @DHowett-MSFT: If you're interested, I'm happy to make a PR for this -- at this point, I'd need input about how you'd want things structured (mostly: where would you want things to live).
I'd expect you'd want to pin the action by a hash as opposed to using a tagged release.
Since GitHub runs the code in Docker, I'd hope you'd be ok w/ that, as opposed to waiting for me to port the code.

I'm alright with a PR for this.
I'm OK if it runs in Docker with GitHub Actions as long as that doesn't mind that most of our CI will run in Azure DevOps while this will run in parallel in a GitHub Action. It just shows up as another check on PR, right?
I'd rather the configuration be included in this repository along with everything else. I think it could go in a subdirectory of ./build. Maybe ./build/config? The YML file could go into ./build/pipelines like the rest of 'em.
I don't mind if it is completely unrunnable on developer desktops and only has shows up during PRs. By your caveat, I would want to use whatever scheduling thing was required to make sure that it hit PRs coming back in.
I also don't mind if we're an early adopter of something. You're very on top of this and very engaged. I trust that you'll be able to work out whatever issues might arise and evolve it as GitHub Actions improves. And if it causes some catastrophic problem... it's Git. We'll just revert it/pull it out until we can turn it back on again. Can't be any worse than our flaky tests that have been decimating PRs for weeks.

Oh, if this has to go into the .github folder, that's fine too.

Yes, it shows up as just another check on the PR.
To have GitHub do the running, workflow file itself needs to live in the .github/workflows folder.
The whitelist+exclusions can live anywhere. I think that having them in the repository (as opposed to on a distinct branch) is the right approach (I'm slowly becoming convinced of this) -- although I really don't like the idea of merge conflicts for the whitelist -- thankfully, in theory the script should be able to talk people through resolving it in the worst case, but...).
And thanks for being open to being an early adopter. I'll probably update this on the weekend.


"Create convex static body/collision sibling" freezes the editor if used on sphere mesh (regression)

Godot version:
c93888a
OS/device including version:
Windows 10
Issue description:
If you use these options when MeshInstance with sphere geometry is selected

the editor will freeze for a long time(or maybe crash) with the following error spam in console

Update: It also have same behavior if you use it on Capsule mesh

@hpvb i think you did some changes in quickhull, maybe its related?

This happens to me also, every time with a sphere. Godot 3.1 Beta 4 , Windows 10 64 bit.

Is this going to be ignored until 3.2? It crashes the entire program and happens every time when using one of the few basic shapes, this is going to happen very frequently, surely you can't just leave it.

This does not seem to work very well. I will give it a check in 3.2 and implement proper convex decomposition.

I don't understand what could be more important than this bug, a complete crash on one of the most frequent tasks.

Leaving this issue as is guarantees countless crashes. I have not come across anything else like it in Godot, a common task that causes a total crash.
I submit that the "Create Convex Static Body" and "Create Convex Collision Sibling" are removed from the menu until it's fixed.
Users can still use "Create Trimesh Static Body" and "Create Trimesh Collision Sibling". No functionality is truly lost.

Leaving this issue as is guarantees countless crashes. I have not come across anything else like it in Godot, a common task that causes a total crash.
I submit that the "Create Convex Static Body" and "Create Convex Collision Sibling" are removed from the menu until it's fixed.
Users can still use "Create Trimesh Static Body" and "Create Trimesh Collision Sibling". No functionality is truly lost.

I submit that the "Create Convex Static Body" and "Create Convex Collision Sibling" are removed from the menu until it's fixed.
Users can still use "Create Trimesh Static Body" and "Create Trimesh Collision Sibling". No functionality is truly lost.

No, trimesh collision shapes are buggy. They have no volume and they don't collide with each other.

No, trimesh collision shapes are buggy. They have no volume and they don't collide with each other.

I didn't realize they couldn't be used as collision shapes until after I posted that.
In the interim is it possible to disallow converting shapes that cause a crash. Trigger a  little pop up that says "It is not possible to convert this shape into a convex body." Even just doing that to the sphere would cut down on crashes.

A proper fix would definitely be implementing a convex decompositing library like HACD:
https://github.com/kmammou/v-hacd
instead of using quickhull, as this option as it currently is, is really sub-optimal.

Kicking to 3.2 as no clear way of fixing this exists..

Is there no way to restore the functionality from 3.0 in the meantime? There was no problem generating a collision shape from a sphere or capsule there (except for warnings in the console output).
That would prevent quite a lot of frustration in using this functionality - as it is impossible to save the scene after having clicked on the button, therefore leading to losing some work.

I don't mean to be an annoyance but this does seem to be a "critical" bug. Although I don't know the exact definition. There's not a way to revert the code for just the convex creation portion of the current code? I also think disabling convex creation on affected meshes is a much better option than allowing lock ups/crashes.

Moving back to 3.1 milestone, as this is a regression.
The feature works well in 3.0.6, so there's no reason it can't be made to work again in 3.1.
Test project: convex_crash.zip
(Select MeshInstance, pick one of the "Create convex" options.

I tested 3.1 alpha 1 and it reproduces the bug too.
If someone is willing to bisect what caused the regression between 3.0-stable and 3.1 alpha 1 (don't have the exact commit reference anymore, but should be around 3304e6ce or a day or two earlier, so this one can be used as git bisect bad).

I tested 3.1 alpha 1 and it reproduces the bug too.
If someone is willing to bisect what caused the regression between 3.0-stable and 3.1 alpha 1 (don't have the exact commit reference anymore, but should be around 3304e6ce or a day or two earlier, so this one can be used as git bisect bad).

@akien-mga I will try to find it..

@Chaosus sorry, I just saw your comment right now, I searched for it during the day. If I bisected right, the first bad commit is e179bf0726868fbf2c6216a6c6a715c4a2f99419. Hope this helps!
e179bf0726868fbf2c6216a6c6a715c4a2f99419 is the first bad commit
commit e179bf0726868fbf2c6216a6c6a715c4a2f99419
Author: Juan Linietsky<EMAIL_ADDRESS>Date:   Tue Jul 3 10:55:50 2018 -0300

    Ensure, if a texture meant for a normal map is imported and size limit exists, that it's renormalized after resize.

:040000<PHONE_NUMBER>c3142ae7fb86da5e18dbf790443cffd1a292 44578e251f21d54e217c0580761e9c21380383e0 M	core
:040000 040000 f9d307110e2f06d73f76e18b86e1050e0cfe1bcf cd18305297ba36ff22e655afd7bd50be216b5a22 M	editor
:040000<PHONE_NUMBER>8b79e7494716723fc12986bdf49e0395dfc5 fbb843714fe87f758faf8c9eb5ff149947e262f9 M	scene
:040000 040000 588e4422da2a86d6f06849bd1b92460f592a8e41 3d73b700a069c96df9da0c024edb945ff5d3f5ac M	servers

The crash is caused because of the default settings on the mesh being changed. Particularly ARRAY_COMPRESS_VERTEX appears to be necessary for quickhull to function. I'll try to fix quickhull to be able to work with different mesh formats.

What ever came of this? What is one to use while this feature is not there? It's on version 3.4 now so surely people are using another workaround by now?

Use a CollisionShape node with a SphereShape instead of generating a convex collision shape from a SphereMesh primitive.


Fix Windows Dynamic Linking

Hello,
Linking against the symbol definitions explicitly instead of using /force:unresolved fixes the segfaults. The examples work as expected. Note that the lib definitions, taken from a 0.9 source build, haven't been tested on a nightly NeoVim.
Fixes #125

Could you remove the first 2 commits and cherry-pick 6c8c54a6c2e57d871bb6f211b0bc78945d892f73 to see if this fixes CI on Windows?
Also, what about this?

I removed the first two commits, I can't cherry-pick the commit you sent. I'll add the Windows CI to the build script and commit again.

Thanks I used the libs from an earlier version of this PR for echo, would this new refactoring do it at build time? I'm still trying to figure out how to properly bundle it. For now, I think I'll build all platforms in GH actions and use a build step in lazy to fetch the releases from Github, I'm not sure that's very common...

Closed by #149.


[RoleManagement] Suggestion | Roleset

Describe the solution you'd like
When setting roles exclusive to each other it would be nice to have the bot remove the reaction your first chose if you react with something else later. So that if you need/want to go back to the initial reaction you don't have to unreact before reacting again. Plus it also shows the correct number of reactions compared to roles added to members.

Won't be added

As there's new attention on this  since supporting again...
The "won't be added" bit was a glib quick response that didn't deal with explaining why this change is not easily compatible with the cog.
Discord does not send information about who removed the reaction in the same payload as the reaction events (it is inconsistently available from the audit log) This also increases the rate limit consumption, the number of reactions matching is also not something this achieves, as discord does not send the full reaction info to the desktop or mobile clients.
This could lead to conditions that are messy to deal with properly and I cannot suggest this, despite agreeing that in a perfect scenario, if the roles were set as exclusive, this would be done.


Support OpenShift certificate serving used with TLS registry

Summary
Adding support for certificate serving so that we can test this section of TLS registry reference: https://quarkus.io/guides/tls-registry-reference#utilizing-openshift-serving-certificates
I have only implemented it for template-based builder. I think it should be technically possible to test this with extension-based builder, but probably need to configure OpenShift extension specific properties inside of the test. It is not really relevant as I care about TLS registry reference verification ATM.
Regarding limitation to Quarkus runtime inside of this PR. I have added it so that I avoid (not necessarily) possible side-effects. I am just implementing what I need and if someone needs more, they need to extend functionality.
Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Release (follows conventions described in the RELEASE.md)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

run tests

run tests


M. Tech result

Include M. Tech result also. Make UI for that and also change the backend for it.

@shubham12541 is IIIT Una and 5 yr integrated also there?

@Akarshit Yes


Add isForced argument, which forces respawn even without node flags

This pr adds isForced argument to this module. isForced is to force respawn even if forcedFlags is empty or is not specified.
I will modify Liftoff to respawn itself when cwd or configPath is specified explicitly, in order to add node_modules in cwd to environment variable NODE_PATH. (process.env.NODE_PATH is not allowed to change in a program).
By this, for example, gulp can load modules in node_modules in both gulpfile directory and cwd. (And this will solve the issues gulpjs/gulp#2126 and  js-cli/js-liftoff#55.)

@sttk I didn't get a chance to respond in full to your suggestion but I don't like the idea of introducing this sort of magic into the CLI.  If we do this, we're basically warping the way node's require works.  Maybe we just need to better document this edge case and suggest the consumer add NODE_PATH before their command?

@phated You're right. This way is certainly odd, and I agree to placing that suggestion on document.
I'll close this pr.


About the deformable convolution in YOLACT++?

In table 5, is the deformable conv for yolact-resnet50 also 'interval=3'?

If so, I noticed that the AP gain for yolact-resnet101 after doing DCN is 1.6, but for yolact-resnet50, it's 2.8. Then, it can be supposed that DCN can help to improve the weights utilization rate. That is, DCN made the network use weights more efficiently.  For deeper resnet101, it can just use more weights to compensate the inflexibility of traditional conv, so the AP gain brought from DCN is not so obvious. Do you agree with this?

The resnet version uses an interval of 1, so I'm not sure if they're directly comparable like that.


Workaround for the Blazor (client-side) template not visible

As there seems to be a known issue, https://github.com/aspnet/AspNetCore.Docs/issues/13531 which has a known root cause https://github.com/aspnet/AspNetCore/pull/11707
I'd propose either to create the blazor client project from command line with "dotnet new blazor" or either select the "ASP.NET Core Web Application" template and on the third step we will be asked the ASP.NET Core project template to use. One of them is "Blazor (client-side)", so go and use it.

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

ID: c07e57dc-526f-9479-4695-de7d8f06eb9a
Version Independent ID: 8226ed72-69b2-3c93-a931-218bd11cf9c8
Content: Get started with ASP.NET Core Blazor
Content Source: aspnetcore/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Those seem closed/merged ... we'll see when this issue is triaged if the fix is in for Pre8 (or VS's new preview release); and if so, if we'll need to cover anything in the meantime. Exact date for Pre8 release isn't publicly announced (I know what it is but I'm sworn to 🙊 secrecy), but the Pre8 engineering issues on the roadmap are all worked/closed/merged and the milestone for Pre8 shows 197 issues closed and 0 issues open. I'll let you guess what that means. :smile:

Sounds like great work! :)

I like this

I just installed VS 2019 Community Version (Version 16.3.0 Preview 2.0) with .NET Core 3.0 Preview 8. I also ran the command "dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview8.19405.7", which I copied from Get started with ASP.NET Core Blazor page. I'm able to see the Blazor App project type when creating a new project but don't see the Blazor (Client-Side) template even after selecting Asp.NET Core Web App.

@jerryzjw It should be called Blazor WebAssembly App now. If you don't see it (and try restarting VS if you haven't done that already), open an engineering issue https://github.com/aspnet/AspNetCore/issues ... but search the closed issues there with the area-Blazor label first to see if others reported this and the team already responded.
I'm going to close this issue now because their work for Pre8 and the latest VS preview should have resolved most of the issues.


Properly paginate pkg-github-fix-permissions

cc @ntkme

I suggest to make it more verbose and print link of each archive that is patched for tracking purpose.


Update install-unifi.sh

bumps to Unifi version 6.0.22
OPNsense 20.7.2-amd64
FreeBSD 12.1-RELEASE-p8-HBSD
no problems encountered, dashboard seem functional

no problems encountered, dashboard seem functional

Don't Upgrade to UniFi Controller 6.0.20!
Broadcast storm after Unifi controller upgrade to 6.0.20

Given the wide range of network-breaking early issues, this can probably wait. Let it settle and watch for things to not be so FUBAR. Seems 6.0.22 isn't exactly perfect either.

I concur. 6.x seems like it might not be what everyone wants just yet. Going to let this wait a bit. In the meantime, those wanting to try it can use the @tong2x branch. Thank you


[DO NOT MERGE] - Test for creating orphan files

--- Releases ---
Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/6dhj65ol9e798
iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/5cbjc52qo487o

Tested. Closing this one.


started refactoring

composition structure for the lighting settings
File structure is not finalised
please let me know if these changes lead in the desired direction

Looking much better than it was. The only consideration at the moment is that some of the button lists should probably be radio lists to aid in accessibility. I've been slowly making this change in various places (Faders.vue is a good example) where it uses a role="radiogroup" and the RadioItem buttons.
The main reason is that a radio button list is clearer in indicating to screen readers and visually impaired users that only one item can be selected at a time, where as the historical buttons imply otherwise.
Other than that, loving the direction :)

added role="radiogroup" to container
added type="radio" to button
is this what you meant?

As context, the Radio implementation is available at:
https://github.com/GoXLR-on-Linux/goxlr-ui/blob/main/src/components/button_list/RadioItem.vue
And an example of a button list implementing them:
https://github.com/GoXLR-on-Linux/goxlr-ui/blob/main/src/components/sections/Faders.vue

Looking good, the only comment is that the group= parameter needs to be unique across all radio groups (I see the group 'Button' defined twice), it also, oddly, doesn't need to be human readable, it's just a general group identifier, so something like (for example) lighting_cough_buttons would be generally acceptable.
Otherwise, it's looking great. I'm taking a couple of days off general work on the util, but will keep an eye on this PR, feel free to continue down this path, and let me know when you're in a position that everything is ready for a merge :)
Thanks!

Code looks good so I'll accept this as-is, I'll do some testing post merge just in case there are other problems.
Thanks!

I may end up reverting this, the entire effects section was non-functional..
Respectfully, could you make PRs once the work and changes are complete? Rather than in a progressive state?
I'm always happy to accept good quality code, which you've obviously put the time in here to provide (It's a lot better than what was there previously!), but stuff becomes tricky when I have to start running through it correcting some unfortnunately major issues with it..
The improvements you're making are good, I wouldn't have merged them if they weren't.. I do understand that there's a bit of difficulty spending time making changes that could be rejected, but I promise you, for this level of change, I'll always be open to completed PRs,
I'll happily admit that the original code was, and is, a mess that needs improvements which you've clearly provided here, but preemptive PRs make it a little difficult to determine what's complete and what's not, which can leave things in an unfortunate state when I accept the merge, and various things are broken!
Thanks.

I'm sorry for the inconvenience the pr caused.
I only own the goxlr mini and couldn't test the sampler and effects tabs properly.
Since last week my schedule is quite tight again, so I don't have time to continue refactoring at the moment.
I hope the fixes weren't too time consuming for you.

Thanks for the work you've done. While it was a bit of a problem initially, I kept the code in because it was well developed, and after making a few tweaks and changes to bring it inline with the rest of the code, I've been migrating everything across to your new containers, and deprecating the old ones.

Thanks again.


release process

documenting the release process.

This repository is no longer maintained. Please visit Aurora CLI for latest release of Aurora CLI. Feel free to submit your issues/proposals there.


ytt: 0.40.1 -> 0.41.0

Description of changes
https://github.com/vmware-tanzu/carvel-ytt/releases/tag/v0.41.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

0.41.1 was just released with minor bug fix, pushing update now

@ofborg eval


[Payment due October 4]Remove any code that references or was used only for free workspaces (policies)

Problem
There was a project this summer to deprecate and remove all of the free workspaces in Expensiy and migrate them over to team workspaces. Now that there are no free workspaces in the database or in the backend, there is a lot of leftover code that is no longer necessary.
Why is this important to solve?
Keeping the code up-to-date reduces technical debt and allows it to be more easily maintained.
Solution
Find any code that references or was used only for the free plan in E/App and remove it.
Issue OwnerCurrent Issue Owner: @situchan

Should we also remove the Personal Policy?

Nope, that one needs to stay there.
While you are looking for the code that can be removed, I've heard reports that there are pages or routes that are still referencing the free plan somehow, so please try to track down any pages or URL routes of that nature too. They might not be references that constant, so they might be a little tricky to find.

Just a heads up - I'm going to be ooo 9/4-9/11. I'll add a BZ teammate to watch this while I'm away!
@anmurali - we are reviewing/discussing this proposal. So I think you'll just need to monitor this but I don't expect anything will be needed while I'm away.

bump @situchan Can you please give the proposals a look?

We can go with @cretadn22's proposal.
Please add screenshots of all pages to be removed from route in PR. (opened from deep link)
🎀👀🎀 C+ reviewed

@tgolen, when you have a moment, can you please check out this proposal review? TY! https://github.com/Expensify/App/issues/48345#issuecomment-2329855079

@Christinadobrzyn Yeah, I had a look at it and assigned them a couple of weeks ago. It looks like they have a PR that is ready for review which I'm going to be taking a look at today.

Thanks for the update @tgolen!
It looks like this PR was just merged to staging.
heads up - I'm going to be ooo until 9/30. Since we're reviewing PRs I'm not going to assign a BZ teammate to monitor this while I'm gone. If you need someone while I'm gone please feel free to reach out in Slack for a volunteer. TY!

PR in production! Adding payment date to the title.
Payouts due:

[ ] Contributor: $250 @cretadn22 (upwork offer - https://www.upwork.com/nx/wm/offer/104189664)
[ ] Contributor+: $250 @situchan (are you paid via NewDot?)

Do we need a regression test (I assume not?)

No need regression test. I am paid via upwork

Thanks @situchan can you accept this offer - https://github.com/Expensify/App/issues/48345#issuecomment-2382150454
TY!

Moving to daily to pay this out.

waiting on @situchan to accept the offer - https://www.upwork.com/nx/wm/offer/104260166

This is paid out! Based on this payment summary https://github.com/Expensify/App/issues/48345#issuecomment-2382150454
Closing as complete


OCI_SubscriptionRegister() returns always NULL since v4.7.0

OCI_SubscriptionRegister() returns always NULL since v4.7.0 due a removed return value assignment :(
Test suite does not include test for database notifications.
This will be fixed and a test suite added for database notifications and this issue.

yes now in 4.7.3. first call OCI_SubscriptionRegister return not NULL. (same as in 4.7.2)


HTTP/L7 metrics for TLS-terminated downstream requests in a Gateway

Describe the feature request
We are currently using the Egress Gateway to terminate HTTPS/TLS requests originating from our workloads to external domains that we control as well and whose traffic we want to observe on L7. We do have an own self-signed CA and a server certificate with a PKI that we distribute securely to the Istio Egress Gateway. The role of that Egress Gateway should then be to terminate the HTTPS/TLS connections, make the HTTP requests visible for L7 metrics gathering, and then optionally send these HTTP requests further to an egress cache (Varnish) which is used to cache egress requests and whose Istio sidecar will then do TLS origination to the actual external domains; or the Egress Gateway will TLS-originate those requests again and send them off to the actual destination domain.
That all works splendidly, however no HTTP/L7 metrics are gathered by Istio/Envoy for downstream HTTPS/TLS requests to the Egress Gateway that are ultimately TLS-terminated by the Egress Gateway, so should be available to Istio/Envoy there.
I am assuming that, when you have a HTTPS/443 listener on a Gateway CRD with downstream tls configured, then the Envoy listener this is configured for, is still a HTTPS/TLS listener which "thinks" that it cannot inspect HTTP/L7 metrics, even though we are doing TLS-termination here.
Describe alternatives you've considered
Observing HTTP/L7 metrics for outbound/upstream requests in the Egress Gateway works, though. So, we currently do not have L7 metrics for downstream requests to the Egress Gateway (which are originally HTTPS/TLS requests, but TLS-terminate by the Egress Gateway), but we have HTTP/L7 metrics for upstream requests done by the Egress Gateway.
However, that means, we lose the correlation between the source service where the HTTPS/TLS connections/requests originate from and the Egress Gateway where those requests are received (and TLS-terminated) and then sent further upstream.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[X] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

Can you share a config dump (istioctl pc all PODNAME)? Istio knows when its HTTPS and does HTTP metrics, so this means either:

Its not actually doing what you think (terminating HTTPS)
Stats are not configured correctly
A new bug

The Egress Gateway is definitely terminating the TLS connection. I see the Common Name of the certificate when I do e.g. curl https://httpbin.org/status/200 in a source workload/pod. And the certificate is only ever mounted to the Egress Gateway's Gateway CRD, which looks like this:
spec:
  selector:
    app: istio-egressgateway
    istio: egressgateway
  servers:
  - hosts:
    - '*'
    port:
      name: https-port
      number: 443
      protocol: HTTPS
    tls:
      credentialName: egress-server-cert-secret
      mode: SIMPLE

I think, it is much like with an Ingress Gateway which terminates HTTPS/TLS connections for our own server domain (with a public Let's Encrypt certificate). There, I also do not see (via Prometheus stats endpoint) the incoming/downstream requests from clients towards the Ingress Gateway. So, no istio_requests_total metrics here when the reporter="destination" on that Ingress Gateway pod. However, upstream requests are visible as Prometheus metrics when the HTTPS/TLS-terminated requests go upstream from the Ingress Gateway to the upstream services/backends. There, I do see the HTTP requests e.g. via istio_requests_total{reporter="source", source_app="istio-ingressgateway"}.
But no downstream HTTP metrics with istio_requests_total{reporter="destination", destination_app="istio-ingressgateway"}.
The exact same scenario is with the Egress Gateway: Terminating the downstream HTTPS/TLS connections, but no HTTP/L7 metrics over the Prometheus stats endpoint for incoming/downstream requests. Though, outgoing/upstream requests, the metrics are fine.
I am going to assemble a sensible istioctl pc all egress-gateway-... output, because it contains many sensitive information at many places and is many tens of thousands of lines long.

1 request to a gateway generates 1 single metric, not a distinct one for upstream and downstream.
Sidecars generate 2 because there are two distinct sidecars (each generates 1)

1 request to a gateway generates 1 single metric, not a distinct one for upstream and downstream.
Oh, that makes total sense, since there is only one listener filter chain and single http connection manager processed.
So, is there no way to correlate requests through a gateway between the downstream and upstream?
What I really am after is to know in the metrics which downstream service was sending a request through a gateway, which ultimately sent this very request upstream to another service.
I cannot track the HTTPS request in the originating workload's outgoing sidecar, because it cannot inspect the HTTPS/TLS traffic. Only the gateway could do that, but since, as you said, there is only a single metric generated, and that metrics seems to look like "outgoing/upstream" metrics (so the source_app is the gateway and the destination_app is the service this request is destined for).
What I would like to have is a single metric point with the originating service being the source_app and the eventual destination upstream being the destination_app.

Basically no. You can use tracing to do this, but its of course not quite the same as metrics.
Interestingly, part of ambient mesh we decided to make the waypoint component work exactly how you want it to work: https://github.com/istio/istio/issues/42320#issuecomment-1977262417. While we haven't talked about it much yet, there are plans to be able to use waypoints like egress gateways, which would ultimately fulfill that use case. Its a ways off to get the egress part though.

Thank you for your answers and insights. Much appreciated!
Actually, the reason why we opted for an egress gateway was that there does not seem to be an easy way for the outbound listener of a workload's sidecar to do the TLS-termination, because whenever a ServiceEntry was configured with a HTTPS port, it would not configure a Http connection manager on it, but only make TLS metrics visible. Terminating the application-side HTTPS/TLS connection on the outbound listener would also suit us here.
Using the downstream tls config on a gateway was just the next best thing, since there currently is no such thing as a tls config on a sidecar's outbound/upstream listener.
While researching this topic I came across at least these following Istio GitHub issues tackling the same problem, I think:

https://github.com/istio/istio/issues/21368
https://github.com/istio/istio/issues/37160
https://github.com/istio/istio/issues/39490

I think the current state is:

This can work with a waypoint instead. Not well documented, but I plan to in a couple weeks hopefully
Could be done with sidecar termination, but its not implemented. See above for reference issues
Could be done with traces, but not quite the same

Overall I think this is the expected state, and while there isn't a great solution to this right now there isn't anything directly to do on this issue

hi @kaiburjack, I am trying to achive the same setup app originates tls nad to terminates on egress so I can modify traffic and send to teh destination and I have some issues when I am not using PASSTHROUGH so I was wondering how did you achive it, especially the terminating TLS part?


[Airbrake] [Production] Network Error

Airbrake error: #7528
Airbrake project: datanator_frontend
Error type: Error
Error message: Network Error
Where: <no information>
Occurred at: Jun 12, 2020 17:08:47 UTC
First seen at: Jun 12, 2020 17:08:47 UTC
Occurrences: 0 (0 since last deploy on <no information>)
Severity: error
URL: https://datanator.info/stats
File: https://d33wubrfki0l68.cloudfront.net/bundles/fc6f517048dfaefbd790678d19c5d39a8b3682de.js
Backtrace:
https://d33wubrfki0l68.cloudfront.net/bundles/fc6f517048dfaefbd790678d19c5d39a8b3682de.js:1:in e.exports
https://d33wubrfki0l68.cloudfront.net/bundles/fc6f517048dfaefbd790678d19c5d39a8b3682de.js:1:in e.exports/</h.onerror

This was a HTTP vs HTTPS error. This appears to be fixed in the REST API.


search should not be considered in navigation stack when moving back

go to a work, tap artist name, land on artist page A, use search for different artist, land on artist page B, hit back button, see search again....
i should actually go back to artist page A, not see search again

We did this before with search and this ^ ended up feeling a bit off. So what we went with was if you pushed through two things then the search would go away. Otherwise you could easily get back and revise search, or try other results (say if there were multiple artists with similar sounding names).
So, Artwork -> Artist -> Search -> Artist tapping back would show search. Whereas Artwork -> Artist -> Search -> Artist -> Artwork Would remove the Search from the history.

@orta why not retain search results instead? so that when the user enacts the button again their old search is still there (lets say for a period of time)

I like the simplicity of retaining the search results.

There is only one issue, namely that a single view controller can only be shown in one place at a time. Thus, if you open search in one tab, then move to another tab and also open search there, they cannot show the same single search view controller. Things we can do:

only maintain search results per tab (simple to implement)
persist search results to disk and load those for each search view controller we show, thus always showing the last search results, regardless of tab (harder to implement)

only maintain search results per tab (simple to implement)

I think this is acceptable, there is a context change in switching between tabs. It's very unlikely you're going to want to go back to same results after switching from home to notifications for example

remove presented search view controller from other tabs when it’s shown (simple to implement)

I added this one after the fact.
@orta While what you say makes sense, I’d just like to be sure that you wouldn’t prefer this one instead.

I do prefer

remove presented search view controller from other tabs when it’s shown (simple to implement)

Okidoki :+1:

:+1:


torch-opencv version compatible with CUDA 7.0?

Hello,
I was wondering if there is a branch of torch-opencv compatible with CUDA 7.0 (or a previous version of master available). When I try to install, it explicitly asks for CUDA 7.5. I am asking this because the machine I want to install it on is used by more than one users and most of us are using CUDA 7.0, so I don't want to open any dependancy issues by upgrading to 7.5.
Thank you!

Hi @Leftetris ,
I'm sorry for so late reply. It's unexpected that it asks for 7.5. What error message do you get?

Hello @shrubb , my bad. There were conflicting types of CUDA in the machine (one pointing to 7.0 and one to 7.5). Fixed it, but forgot to close the issue. Sorry, thanks anyway!


fix: pixiv-icon waitUntilVisible condition

やったこと

fix waitUntilVisible to contain the fix in https://github.com/vueuse/vueuse/pull/3365
In Chromium based browsers, multiple entries can be returned in a single callback even only called observe() once.

Found this is more likely to happen if the element's parent has css transform somehow? e.g. Modal/Sidebar
Related implementation but not found so mush useful info. https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/intersection_observer/intersection_observation.cc;l=36

動作確認環境
チェックリスト
不要なチェック項目は消して構いません

[ ] 破壊的変更がある場合には、対象のパッケージのメジャーバージョンが上がっていることを確認した
[ ] 追加したコンポーネントが index.ts から再 export されている
[ ] README やドキュメントに影響があることを確認した

@yue4u Thank you for the PR!
We apologize for the inconvenience, but could you please add a Checkbox to the BottomSheet story of this Storybook to check the operation?
packages/react/src/components/Modal/index.story.tsx

@yue4u Thank you for the PR! We apologize for the inconvenience, but could you please add a Checkbox to the BottomSheet story of this Storybook to check the operation? packages/react/src/components/Modal/index.story.tsx

Is https://github.com/pixiv/charcoal/pull/557/commits/d306866edb14b1746ae6e8754b505d55d32a6296 the change you want? It's tricky to reproduce this issue and I don't see it happening on storybook.

@yue4u Thank you for the PR! We apologize for the inconvenience, but could you please add a Checkbox to the BottomSheet story of this Storybook to check the operation? packages/react/src/components/Modal/index.story.tsx

Is d306866 the change you want? It's tricky to reproduce this issue and I don't see it happening on storybook.

thank you! Sometimes I can confirm a problem with the image snapshot test, so I'm glad to have it.


explore stdlib over testify/suite

This is just a bit of a refactor to enable running a bunch of tests without using the testify/suite pacakge.
The way I currently have it projected would still do a setup for each of func TestXXX, but if you really wanted to make sure the setup only happened once per execution, you could turn those into their own nested calls to t.Run(...) instead.

What's the benefit over just "not using the standard library"? suite provides some helpful naming and categorization, and I'm a big fan of not having to rewrite what it provides. I'm not sure I love the multi argument returns of setup vs having a shared struct.

I'm not sure what "naming and categorization" you're referencing, but I'd like to understand that.
Also to note, I did keep the testify/assert functionality, as I recognize rewriting that stuff is very tedious. I'm just not convinced the incremental functionality suite added over assert buys a lot.
I feel like the hierarchy in the Suite is already very handily supported by t.Run(...). Also the SetupTest feels a little bit like hidden magic to me, whereas I'd prefer that kind of thing to be explicitly declared inline in the test.
And on a more theoretical layer, I tend to try to reduce external packages due to the Go Proverb:

A little copying is better than a little dependency.


Multiselect Picklist options are rendered wrong when there is an error message

Pull Request will come soon.

@up2go-sschwarz Thank you for the pull request. We'll merge it to the master branch and it'll be part of the new release. We appreciate your contribution.


Set filetype

Tiny addition to set filetype in addition to buffer name, so that it can be used for conditional user settings. I use it with galaxyline (statusline) short_line_list config.

https://github.com/simrat39/symbols-outline.nvim/commit/9c3299bef81122fd02b72993870bf2eff4b8fcfd actually looks like i messed up something

Thanks for the PR !


Table gets corrupted while editing in WYSIWYG mode

Azure Data Studio Version:

Steps to Reproduce:

edit the table
Save, Close the file
Open the file again

@rajeshka @chlafreniere could you start a thread in the Shiproom teams channel to provide context and get this approved?

Some more context:

This affects tables that don't have headings. Tables with headings work as expected.
This is not a regression

@chlafreniere - can you please confirm that this is the workaround?

@chlafreniere - can you please confirm that this is the workaround?

@MsSQLGirl - that's correct 😄 Tables with a header do not get corrupted.

This has been checked into main. Closing as it will make the next release.


cmake: add version number in csg/tools check

csg builds only with exactly the same of tools, e.g.
1.2.0 with 1.2.0 and 1.3-dev with 1.3-dev.

We need to a an extra check for that to FindVOTCA_Tools.cmake

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 20 Jun 2011 at 8:41

Super project has been start: votca/buildutil@f42ec0a66c04ee4a97cec7dc3546903d18bbb48d, see the global branch for further development!

cmake-3.0 has library interface, which might make that very easy.
https://cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#interface-libraries

We switched to imported targets everywhere, so now CMake should provide the ability to check version, too.


[operations] Implement process_deposit

https://github.com/lambdaclass/lambda_ethereum_consensus/blob/dd0a0523e6be2a21fa3f6a96d4466926307d236c/docs/specs/beacon-chain.md?plain=1#L2874-L2895
See Spec tests format: https://github.com/ethereum/consensus-specs/tree/dev/tests/formats/operations
Acceptance criteria:

Run corresponding spec tests

I can take this

Yes


rename loopy

cc https://github.com/illinois-ceesd/mirgecom/pull/136

I saw this too, but:

It'll keep working in the presence of the rename.
Removing it now will break the workflow of folks who run a new emirge with an old mirgecom.

So I think removing this is premature.

I saw this too, but:

It'll keep working in the presence of the rename.
Removing it now will break the workflow of folks who run a new emirge with an old mirgecom.

So I think removing this is premature.

Ok, but I'll document this at least.

Ok, but I'll document this at least.

Fair point.

ready for review.


Logs don't show HTTP ports when HTTPS is enabled

Due to a bug in Phoenix the HTTPS endpoint is mentioned twice in the logs, while the HTTP port is not mentioned at all:
09:02:14.451 [info]  Running RigInboundGatewayWeb.Endpoint with cowboy 2.6.1 at https://localhost:4001

09:02:14.484 [info]  Running RigInboundGatewayWeb.Endpoint with cowboy 2.6.1 at https://localhost:4001

To be fixed upstream, see https://github.com/phoenixframework/phoenix/issues/3149

fixed upstream


Copy/Paste error in cell

Expected behavior and actual behavior.
expected: the correct behavior of data when paste data in cell
actual: when paste data into the cell, an error is displayed  Cannot read property 'name' of undefined
Steps to reproduce the problem.

open link https://tonygermaneri.github.io/canvas-datagrid/tutorials/demo.html
copy data from cell
paste in cell
error Cannot read property 'name' of undefined

Specifications like the version of the project, operating system, or hardware.
MacOs High Sierra, Chrome 67.0.3396.99

Thanks, looks like a bug that was introduced recently in 0.21.x.  I have no proper automated tests for clipboard so it's fallen through the crack before.  I'll get it fixed.


Mistake in sample JSON file

Hi
I think there is a mistake in the sample config.json file
"id": "<service_id>," is correct
and "id": <service_id>,  isn't correct (quotes are missing)

All the sample values in <> brackets are meant to be replaced and set to proper values. Service's "id" attribute is number and doesn't need quotes


SIP: Clock Trigger

Rendered
Signed-off-by: Brian H<EMAIL_ADDRESS>

#365

I want something to execute on start, and never again (0 0 5 31 2 ?)
Would this be a supported feature? Some schedulers error out on runaway dates.

@ecumene

I want something to execute on start, and never again

Could you expound on what you want to do here? It seems like you could basically get this effect with e.g.
interval = "infinity" # or... "999 years"
on_start = true

...but the specific point of time "on start" is sort of a weird concept for Spin.

interval = "infinity" works!

I want "on start" to run some code that registers callbacks with another service before starting my app.

This is an interesting one - sounds like you're basically doing a sort of service discovery registration. Would you mind giving a little more detail here?

I also want to do some template rendering before running the services

Depending on exactly what you need, you might be interested in wizer. I think we'll probably bake it (or something equivalent) into spin eventually.

service discovery registration

I'm actually registering a discord command. Right now, it does it on the event that's meant for ping (😬)

Depending on exactly what you need, you might be interested in wizer.

Thanks! I'll look into that

service discovery registration

I'm actually registering a discord command. Right now, it does it on the event that's meant for ping (grimacing)

Makes sense. I'm mostly just trying to get a sense of whether there is a more general use for an "on start" entrypoint, independent of this clock trigger. This seems like a pretty good example.


Merge master into develop

Automatically created PR for merging master to develop.
No merge conflicts were found.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.289%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
253

Relevant Lines:
254

💛  - Coveralls


5.x Cannot change tag for CardActionIcon to "a"

Looks like the tag is being forced to "button" here. Or maybe I'm doing something else wrong...
https://github.com/jamesmfriedman/rmwc/blob/b63aa1417f79cae49a775205bdfd234c50a21439/src/icon-button/index.tsx#L175

Nope, good catch. I'll get a fix in and add a test.

Fixed, publishing now. Should be live in a few


Handle the version attribute setup in a more intelligent fashion

Having to hard code a version of squid based on the distro version is not a sustainable setup.  We need to discover it post install

👍 It's pretty bad how it currently is. Right now it's defaulting to 3.1 and only has Ubuntu specified for up to 14.10, so it's missing 3 releases.
The Debian version doesn't seem to gracefully handle 'testing' or 'sid'
Ubuntu:
15.04 -> 3.3
15.10 -> 3.3
16.04 -> 3.5

Closing this out since the logic behind this has been reworked. We have a helper now for some of this which we can use to add logic if necessary.


replace references to master branch with release branch

I think all of these could refer to develop so that when we make changes in develop, they are instantly visible.


Add support for chatgpt-4o-latest

Thanks for the PR. This LGTM after addressing my comments

I've updated the PR and also added a test.


standardize client-side validation

Story:  As a developer, I want the validation code for client-side form submissions to utilize a standard pattern so that it will be easy to maintain and to clearly implement.
Add a library for input validation or implement a standard form validation pattern.

I moved the client side validation code to it's own file and broke it into smaller functions for re-usability. I did not go with an existing js library because our validation needs are somewhat unique.
PR #122


Update to Varnish 4.0

Since Varnish 4.0 the directors has been moved into VMODs, and with that their invocation syntax has been changed.

:skull_and_crossbones:


How to migrate amplify setup to client's AWS account

Amplify CLI Version
10.4.1
Question
Hello,
I have a working Amplify backend with some data set up within it. Everything works in our mobile app as we would expect.
The client has recently asked us to move this whole amplify setup into their aws account.
Is there a guide on how to do this? I found one page with a very non-detailed 3 step process on how to do it.
When I try to run amplify init, as suggested in the guide, it just seemingly re-creates my existing setup in our own AWS account. I have already created a new project for this app in the client's aws account and I tired to run amplify init --appId  but that also does not work. I get an access denied error.
Is there some kind of guide I can follow to do this ?

Hey @Tom-Sziler :wave: thanks for raising this! If you are looking to simply create the same infrastructure in another AWS account, you can run amplify add env which will prompt for the target account's credentials. When running amplify init are you getting the prompt for the target AWS account you'd like to use for the new environment?

Hi @josefaidt,
here's my process currently:
Pull fresh clone of repo
Option 1:

Run amplify init Result:

Option 2:

Run amplify add env Result:

One more update - I tried using the existing staging env with amplify init, but got the same error:

It looks like I can no longer even use my app as is with my old account, I am not able to do any amplify init to get the project running. I keep getting the 'access denied' error

Hey @Tom-Sziler when you originally pulled this backend did you choose "No" to "Do you plan on modifying this backend?"

@josefaidt I chose yes

I'm wondering if it would be easier at this point to just re-create the entire backend setup on the client amplify account?

Ok so I was able to revert everything to work with my original AWS account and use the existing env that we started with.
I logged out of my aws account and logged into the client's aws account for which I have full admin access.
I ran amplify add env in my terminal and it worked, but the problem is that it adds this env to my existing account/appId, NOT the intended client aws account.

I ran the command again and used AWS profile as the authentication method and it looks like it succeeded again, but this time it added to an appId I have not seen. This is not the appId of my account nor the client aws account:

Using "Amplify Studio" as the auth mechanism will deploy the environment to your current account

@josefaidt where would I find that amplify/.config/local-aws-info.json file? I don't see it in my project in the amplify directory

Hey @Tom-Sziler thanks for clarifying! Is your default AWS profile pointing to the client's AWS account?

@josefaidt How would I check that?

Hey just wanted to reach back out - I did figure out how to change the profile to point at the client and got everything correctly moved over. After this whole experience, I can say that I wish the process was more clearly outlined in the docs because this was pretty tough to do

Hey @Tom-Sziler apologies for the delay here!! I'm glad to hear you were able to get things set up and moved over despite the experience. Do you have any particular callouts on the difficulties of setting this up? I'd like to use this information to improve the documentation 🙂

Hi @josefaidt Yes, I got this all figured out. No specific callout, but the docs were pretty unclear. If I recall, it's a single page with a 3 step instruction list and not much context.


[FEATURE] Store paths as well as names

From what I understand (please correct me if I'm wrong) it is currently only possible for client-zip to generate a "flat" zip file. I.e. no folder paths in the zip file. Would it be very difficult to add this?
Why is your feature relevant to client-zip?
There are definitely a use cases where this would be useful. On top of my head.

Avoids having to mangle the filename itself if there are duplicate filenames in the files/requests to be stored in the zip. (Just use different folders)
Keep folder structure if user needs to download files from a system that actually stores files in folders (plenty). Duplicate filenames are often not that rare in those cases.

Describe the solution you'd like
Make it possible to not only specify name for a entry in the zip package but also folder path (relative is probably enough).

Please see #6

Doh! I should have seen that. My bad. Thank you for the prompt response


chain/ethereum,graph,node: moved BlockIngestor to chain/ethereum and removed IngestorAdapter

The IngestorAdapter was actually protocol specific and having the abstraction in the Blockchain trait was not used expect for Ethereum chain.
Removed IngestorAdapter from block chain and moved the chain agnostic BlockIngestor to graph-chain-ethereum crate.

I'd like @lutter's opinion before merging since he originally introduced this in https://github.com/graphprotocol/graph-node/pull/2411.

I agree that a generic IngestorAdaptor has been overtaken by events, and making it ethereum specific is the right move.
How does this mesh with the ingestor we need for NEAR to have black hash/number mappings in the database though?

Right now, they are completely separated. There is a BlockIngestor (in chain/ethereum) specific for NEAR and a more generic for Firehose ready chain in general called FirehoseBlockIngestor (in graph/blockchain).
In main entrypoint of graph-node, the logic remain the same, just the location of BlockIngestor changed.


Soroban Improvement

changes in this PR:

add getLatestLedger
fix Pagination Options
fix Topic Filter & add example

Hi @hasToDev, this is great! Thank you for fixing and improving it.


Sub Folder resizing

Description of the new feature / enhancement
Ability to select a folder and the images in that or subfolders with images to be resized
Scenario when this would be used?
Bulk resizing any pictures in many folders
Supporting information
No response

/dup #7741


Container performs constructor injection on discovered services

@JoeHegarty This fix should be compatible with the current version, but adds the ability to use constructor injection in services and singletons.

Loks good. Thanks Adam!


Use df's algorithm to calculate the disk used ratio

related issue #3245 Make sure set the target branch to develop
What is the purpose of the change
#3245
Brief changelog
Use df's algorithm to calculate the disk used ratio
Verifying this change
#3245
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.2%) to 54.264% when pulling c8144b2b4f3fcc06f3c583187d0e21e7727ebdb8 on aaron-ai:pr into 44bdeedad2d0e28717f5012d375d12af76305bb5 on apache:develop.

Codecov Report

Merging #3246 (e4298bb) into develop (44bdeed) will increase coverage by 1.61%.
The diff coverage is 87.50%.

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

@@              Coverage Diff              @@
##             develop    #3246      +/-   ##
=============================================
+ Coverage      48.08%   49.69%   +1.61%
- Complexity      4575     5012     +437
=============================================
  Files            552      552
  Lines          36521    40174    +3653
  Branches        4818     5814     +996
=============================================
+ Hits           17561    19966    +2405
- Misses         16747    17830    +1083
- Partials        2213     2378     +165

Impacted Files
Coverage Δ

.../main/java/org/apache/rocketmq/common/UtilAll.java
40.89% <87.50%> (+0.63%)
:arrow_up:

...ava/org/apache/rocketmq/test/util/VerifyUtils.java
46.26% <0.00%> (-2.99%)
:arrow_down:

...g/apache/rocketmq/store/MessageExtBrokerInner.java
75.00% <0.00%> (-1.93%)
:arrow_down:

.../rocketmq/broker/filter/ConsumerFilterManager.java
72.19% <0.00%> (-1.80%)
:arrow_down:

.../rocketmq/broker/pagecache/OneMessageTransfer.java
22.58% <0.00%> (-1.42%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
54.16% <0.00%> (-0.84%)
:arrow_down:

...e/rocketmq/client/impl/consumer/RebalanceImpl.java
39.45% <0.00%> (-0.79%)
:arrow_down:

...org/apache/rocketmq/store/AppendMessageResult.java
59.45% <0.00%> (-0.55%)
:arrow_down:

...java/org/apache/rocketmq/logging/inner/Logger.java
52.15% <0.00%> (-0.48%)
:arrow_down:

...he/rocketmq/client/impl/consumer/ProcessQueue.java
58.60% <0.00%> (-0.47%)
:arrow_down:

... and 38 more

Continue to review full report at Codecov.

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

nice work.

LGTM

Sorry! There is no issue with the code, but some errors occurred when we released the version, which led to the introduction of commits that should not be introduced. Could you resubmit a pull request with the latest develop branch code?

another


[Event Request] Page 256 "Payment Journal" - protected var

Please add the following Variable CurrentJnlBatchName to protected var in Page 256 "Payment Journal"
    protected var
        <...>
        CurrentJnlBatchName: Code[10];

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


Force a timeout of the healthcheck in 45s

Until https://issues.apache.org/jira/browse/MESOS-3479 is resolved we
must never timeout.  There are cases where we still exceed the 60s
timeout
I got lucky testing this.  I ran into the scenario which usually has a health check exceed it's 60s timeout, but the timeout enforced here (Ctrl+f timeout 45s) caused the health-check to fail on time.  The next health-check succeeded as usual, but this time we converged to a healthy state.  Defect mitigated!

LGTM


refactor: use generic function sliceContains

This PR refactors the code to utilize the generic function sliceContains from the pkg/codegen package.
Upon migration to Go 1.21, sliceContains can be substituted with slices.Contains.

Hi, appreciate you've worked on this and it's not yet in - please bear with, we're over-stretched and are trying to prioritise higher priority pieces (when we get time to work on the project).
Once we get through the backlog for the next release we'll revisit this


Entity disappear in the evaluation and  playground

Describe the bug
suddenly entity labeling is not working in the evaluation panel  and playground .although it works correctly in the API section
To Reproduce
Steps to reproduce the behavior:

Go to 'NLU'
Click on 'Evaluation'
Scroll down to 'Report'
See error

Expected behavior
The entity report should provide the predicted labeling for entities.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

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

Smartphone (please complete the following information):

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

Additional context
Botfront Version : 25.3
Rasa for Botfront Version: 1.10.3-bf.2

@GuillaumeTech can add a fix for this in #692 ?

Hello @znat . Any time frame for this bug . Thanks in advance

We can't commit to a precise date right now, but it's being addressed. We will let you know as soon as it's done


add sign up page

@Anjuli08 Kindly review my PR.

size of the card it too large as it shouldn't have scrolling for just one card


Would you please post a new release?

https://github.com/sqrthree/vuepress-theme-api/commit/6bb64386ec94719a1c49f2861ec5c97af2740796
this commit is not release, I'm having this BUG happening.
thx.

Thank you, a new version v0.2.1 is available here.


package not found

Hi Team,
I got below error while building iso.
Downloading toolchain RPM: kernel-headers-<IP_ADDRESS>-1.cm1.noarch.rpm
--2021-07-30 15:55:16--  https://packages.microsoft.com/cbl-mariner/1.0/prod/base/x86_64/rpms/kernel-headers-<IP_ADDRESS>-1.cm1.noarch.rpm
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-07-30 15:55:17 ERROR 404: Not Found.
I also validated by looking into below path and package is not there.
https://packages.microsoft.com/cbl-mariner/1.0/prod/update/x86_64/rpms/
Regards,
Rajnish Soni

Hi Rajnish, can you confirm which branch/tag you're building from? Currently, we can only guarantee that the package versions from the 1.0-stable tag are retrievable from our repository on packages.microsoft.com.

Duplicate of #1191 . If the linked issue did not resolve your problem, feel free to reopen this with more information. Thank you!


mgmt, aks, minor NPE protection

Get some NPE protection from https://github.com/Azure/azure-sdk-for-java/pull/30073
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Fixed event trigger twice when dragging then changing progress

You can simulate this error by changing the progress bar of an event and then attempting to drag it(change start and end date). It will trigger the on_progress_change event needlessly. Furthermore, clicking anywhere else on the svg triggers a random on_progress_change event(after changing the progress), which this takes care of too.


Handle group join password when logged out (or remove)

At the moment when you are logged out you can join a group with a password, you get redirected through the signup flow, but if you got the password wrong this isn't really handled well.
This is quite complicated state stuff to keep around, and is fragile without tests, so one option would be to remove this possibility. Alternatively to implement it so it works :)

I think the best option is to go back to the groupInfo page and show an error in the password form.


Add convenience function to return the size of an encrypted segment

in the datastream the header is from.

Codecov Report
Attention: Patch coverage is 69.23077% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 71.21%. Comparing base (adf6e1f) to head (6d57f37).

Files
Patch %
Lines

model/headers/headers.go
69.23%
2 Missing and 2 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #127      +/-   ##
==========================================
+ Coverage   69.75%   71.21%   +1.45%
==========================================
  Files           6        6
  Lines         873      886      +13
==========================================
+ Hits          609      631      +22
+ Misses        141      135       -6
+ Partials      123      120       -3

Flag
Coverage Δ

unittests
71.21% <69.23%> (+1.45%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


fix overline size

It should be 0.88.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Meta boxes

Start of pull request, will edit this

Need to put in readme a brief summary of how to add more standards (with optional edits and views), and how these can be automatically picked up and displayed in the tag editor


Add CONTRIBUTING.md

Provide contributing guidelines for new contributions
to mpiFileUtils.
Signed-off-by: Giuseppe Di Natale<EMAIL_ADDRESS>

@dinatale2, thanks for putting this together.  Looks great.

@adammoody I went ahead and updated it. Do we have a logo or other resources we should provide?

Is this ok to merge? We can always make additions if the current version is acceptable.

@dinatale2 Yes, looks good.  Let's merge.


The release download zip file isn't there

Hey, I think you forgot to add the zip file for the download under releases :)

Please add it, I really need this awesome tool!

you need to build it. no clue why the author didn't include the zip


add cedr dataset

Hi ! Thanks a lot for adding this one :)
Good job with the dataset card and the dataset script !
I left a few suggestions

Thank you very much for your helpful suggestions. I have tried to carry them all out.


Live Mode

Ok.  It can be very, very slow...
I tested the live mode here adding the following code in the bottom of the file tipuesearch_content.js.
var tipuesearch_pages = [];
$.each(tipuesearch.pages, function (k,v){
  tipuesearch_pages[k] = v.url;
});

Personally, I am not using it now. But, when I changed the mode to live my page breaks. Then I added this callback.
My question is: Is it useful to be included by default or would be best to add an option var in _config.yml to use the live mode, then we do not generate the content for the static mode, but only the var with the pages urls. What do you think about?

No, I don't think it is useful to be included by default. The Tipue Search documentation states "Live mode uses the DOM extensively, so doesn't work well with some sites, and is particularly unforgiving with malformed pages. At present, Live mode is only suitable for smaller sites with less than thirty or so pages." -- So I don't want to support it by default.  Each user can decide to use Live mode or not.


New import location at the top of the file is not what expected.

Good extension! But...

I expect that new imports are added at the top of the file but after "use strict" directive and
possibly preserving alphabetic order.
It is also helpful to leave header comments adove import location.
Yet the comment like //imports may help to determine preferrable position for them.
Ability to use three common groups of imports delineated by blank lines: provided by node (fs, path, http etc.), provided by npm (express, angular, chalk etc.) and project specific (defined with path)
Abilities, reflected to this linting rule

At least some of this features would be greatly appreciated!

Hey @DiamondeX
Thanks for your thoughts :-)

good point! but why do you even use "use strict" as I'm aware of, typescript does not need use strict anymore
It actually does sort the imports when you use "organize imports" and since workspace files are preceeded by a dot, they are sorted at the top.

6 counts to the sorting thingy :-)
For the fifth point, it would be nice, but it's kinda hard to achieve this

About "use strict" consider this answer at stackoverflow

Yea you are right, but I just checked, "use strict" is emitted by the typescript compiler. Or am I wrong?
Well anyway, since "use strict" has to be on the top of a file, I'll prevent the organizer to add imports before the use strict ;-)
On the other thoughts I'll have a look at when I got time for enhancements

@buehler, Should I open new issues for some of the above features except one with use strict?

@DiamondeX yea, if you don't mind, it would be nice!
Some of them should be covered with the other issue #80
A possible plan would be to introduce special comments (like // TSH:) or so, that allow grouping of imports


Major changes so far from the API branch.

I moved all the files from the app directory up one level to the root of the project to match how Neurovault, expfatory-docker, and open_fmri are setup.
The core query functions have been left in place and my tests(looking and clicking) show the views working as expected.
Extended some of the node subclasses to have a custom function called get_full for their api views. This name should probably be changed to something more descriptive, its similar in function to the Node.get but collects information in a dictionary to match the old api endpoints more closely.
Also updated the import script in /scripts to pull in a few more relations.

Let me know when this is working and I'll try again. Right now I get 502 bad gateway and the error is
  No such command /code/uwsgi.sh

I just merged most of these changes into master - if you want to rebase we can look at the differences and make tweaks if necessary.


Failure when training with tf.GradientTape() for regression problems

System information

OS Platform and Distribution: Windows 10 (the same thing happens on Linux)
TensorFlow version: 2.1.0 (the same thing happens on 2.5.0)
Python version: 3.6.6

Describe the current behavior
For the exactly the same model, training via tf.GradientTape() either: (a) does not converge, or (b) converges with worse score than model training via tf.keras.Model.fit method.
Describe the expected behavior
Similar training outcome when using tf.GradinetTape() and tf.keras.Model.fit.
Standalone code to reproduce the issue
import numpy as np
from sklearn.datasets import load_boston
import tensorflow as tf

tf.random.set_seed(0)

def make_model():
    input_layer = tf.keras.layers.Input(shape=(np.shape(x)[1]))
    inner_layer_1 = tf.keras.layers.Dense(
        units=10,
        activation='selu',
        kernel_initializer=tf.keras.initializers.lecun_normal()
    )(input_layer)
    inner_layer_2 = tf.keras.layers.Dense(
        units=10,
        activation='selu',
        kernel_initializer=tf.keras.initializers.lecun_normal()
    )(inner_layer_1)
    output_layer = tf.keras.layers.Dense(
        units=1,
        activation='linear'
    )(inner_layer_2)
    return tf.keras.Model(
        input_layer,
        output_layer
    )

# Get raw data.
raw_features, y = load_boston(return_X_y=True)

# Standardize features.
x = (raw_features-raw_features.mean(axis=0)) / raw_features.std(axis=0)
print(np.std(x, axis=0))

# Reshape targets.
y = np.array(np.reshape(y, newshape=(-1, 1)), dtype=np.float32)

# Training parameters.
optimizer = tf.keras.optimizers.Adam()
objective = tf.keras.losses.MeanSquaredError()
batch_size = 4
epochs = 5

# Fit via fit method.
train_fit = make_model()
train_fit.summary()
train_fit.compile(optimizer, objective)
train_fit.fit(x=x, y=y, batch_size=batch_size, epochs=epochs)

# Fit via gradient tape.
gradient_tape_fit = make_model()
gradient_tape_fit.summary()
dataset = tf.data.Dataset.from_tensor_slices((x, y)).batch(batch_size)
for epoch in range(0, epochs):
    for step, (x_batch, y_batch) in enumerate(dataset):
        with tf.GradientTape() as tape:
            predictions = gradient_tape_fit(x_batch, training=True)
            loss = objective(y_batch, predictions)
        gradients = tape.gradient(
            loss,
            gradient_tape_fit.trainable_weights
        )
        optimizer.apply_gradients(zip(
            gradients, gradient_tape_fit.trainable_weights
        ))
    predictions_via_tape = gradient_tape_fit.predict(x)
    print(
        'Tape MSE: %s' % np.mean(np.power(y-predictions_via_tape, 2))
    )

predictions_via_train = train_fit.predict(x)
print(
    'Fit MSE: %s' % np.mean(np.power(y-predictions_via_train, 2))
)

@markodjordjic the reason could be with way how losses are calculated. Since losses calculated using fit() are scaled during training so it is not exactly the mse but mse with some scaling.

@tusharvickey1999 Thank you for your reply. I have updated the implementation, so now there is an optimizer which can retrieve both scaled and unscaled loss. However the issue still remains. There is a significant decline in model quality when trained via tf.GradientTape() in comparison to the training wit the  tf.keras.Model.fit() method.

@markodjordjic
Please refer similar issue and let us know if it helps.Thanks

@UsharaniPagadala Hi. Thank you for referring to the issue #33898. The issue deals with the problem in a slightly different way, but it was still possible to serve as an insight in what is the root cause of the problem. And the final conclusion is that the tf.keras.Model.fit() method does the shuffling of the data by default and then if you wish to replicate the outcome of the training process via tf.GradientTape() data also needs to be shuffled before consumed by the training process. This of course refers to training processes where shuffling of the data is needed. If shuffling of the data is not needed it must be disabled in the tf.keras.Model.fit() as well; otherwise the trainings will still have different outcomes.

@jvishnuvardhan
I was able to replicate the issue reported here.Please find the gist here.Thanks


[Bug]: Card padding broken with HA 2024.8

Requirements

[X] I checked the troubleshooting section in the README to verify that I have the latest Mushroom version.
[X] I did a search to see if there is a similar issue or if a pull request is open.
[X] I have read the state of card mod support (in pin issues) and understand card mod support is not provided in this repository.

Current Behavior
The padding on Mushroom cards (between the elements and the edge of the card) has roughly halved after upgrading to Home Assistant 2024.8. It looks quite bad. How can we get the previous level of padding back?
Expected Behavior
Padding as per HA 2024.7
Steps To Reproduce
No response
Context
YAML state

Environment
- Browser: Firefox
- HA Version: 2024.8
- Mushroom: 4.0.2

Anything else?
No response

The latest update made my stack-in-cards misaligned. The number controls on this used to be centered:

For me the same issues with stack-in-cards.
Temporarily downgraded to v3.6.4 solves my problem.

The same problem also exists with the "Restriction Card" after the update.

This is probably related:

Since the last update, the small cards are not showing the icons centered anymore.

Here's the issue on my side.

Mine is mainly wonky if I tell it not to display the name in the card. It looks fine if I set the name to a single space though.


Fix lookup of ptr to slice

type Inner struct {
	Value string
}
type Outer struct {
	Values *[]Inner
}
// ...
LookupStringI(data, "Values[0].Value")

see tests for more details

@mcuadros can you please have a look at this PR? Thank you!


fix module path

Fix #475

Thanks for the PR! Looks like linting failed here
logspout.go:3: File is not `goimports`-ed (goimports)


About update

What would you like to discuss?

Hello, really cool stuff here, but since the cloudflare updated their method, this cant work anymore,
Is there any chance you will update in the near future??? thx a lot man, u have a good day.

Checklist

[x] I have read the hooman and got documentation.

Yes soon! I plan to fix it within the next weeks :) Atm I'm very busy with other internal projects.

Awesome man, looking forward to it.

Some time ago, about two months ago, it works perfect in a website (protected by cloudflare), but now days it's not working, i hope a update that fix it soon, this is a amazing tool, congratulations!

ye, looking around of node libraries to bypass these stupid cloudflare screens. Hopefully the creator picks back up the project soon :)

Yes soon! I plan to fix it within the next weeks :) Atm I'm very busy with other internal projects.

U will still offer updates for this lib? im checking and can't bypass v1 challenge (iuam)

I’m really very sorry for not updating as promised. I got really busy with big private projects that I cannot make any time for working on my active open-source projects.

By reading the code and testing the body response, the new version never gets inside the 503 status code statement (hooman.js file, line: 56 - response.body.includes('var s') ), it doesn't find a 'var s' in the body. Also inside core.js which solves the challenge, it's looking for a 'var s' in the script string... I'm new with this cloudflare stuff, but this is not making sense to me, is the body response different than before?
anyways... the library is amazing, never seen something like this before.


Update the 'combine' rules to also work against gatekeeper

Gatekeeper supports looking at cached data, should explore that with conftest combine

https://github.com/open-policy-agent/gatekeeper/blob/1c99315f63f1f7529378b66e2244c0e1171aa8ed/README.md#replicating-data

[ ] remove konstraint ignore

[ ] remove skip in gatekeeper tests, and check they work

Looking into this...


Keyboard lag on Mac OS?

Has anyone faced keyboard input lag while using the cheapino on a Mac OS (only at the login screen)? It works fine once I've logged in, but otherwise there is an input lag (have to hit a key (random) multiple times for it to register any sort of keystroke and I'm not sure if they're even correct because it always says the password is wrong. All of my other keyboards work just fine at the login screen (keebio iris, nico & steph arisu) except for the cheapino (v2) I built.
I'm using a 2018 macbook pro on Sonoma 14.7

Hi. Im on macs exclusively, and havent noticed. Could you test with another cable(maybe cheaper)? Or if you Are running it through a docking station, try directly?
Not sure what this could be...

Sorry for the late update! With your suggestions for debugging, I've tried:

Rebooting
connecting a USB-c to usb-c cable directly to my macbook
using a USB-A (plugged into an adapter for my macbook) to usb-c

Unfortunately, neither of these solved my issue.

Yep! The iris is qmk as well (uses via not vial though, not sure if that matters).
The led of the cheapino does the initial color loop when first plugged but stays green afterwards and does not change.

Just tried it on my kbdcraft Adam which also runs on vial but did not have any input lag so that debunks my suspicion. It's very strange, I'm not sure why it only behaves this way on the cantor remix and cheapino

Im wondering if this might be related to nkro somehow...
Could you test attached firmware for lag(its just a build stripped of nkro and some other suspects...)
cheapino_tompi.uf2.zip

the firmware you gave me seems to flash, but then never boots and is not recognized by my computer (tried unplugging and replugging the mcu after the flash). Also, now when the keyboard is connected, the mcu led color is now purple instead of green -- is this usually just random based on a flash?

Did you unzip it? Btw, you have version 2 of the cheap ion?

Yep! Unzipped, put the mcu into dfu, then dragged the uf2 file into the folder. And yes I'm on v2

Ooof, I probably messed up somehow... I tried again with attached firmware, tried to turn off some options.
Is it better?
cheapino_vial.uf2.zip

Sorry for the late reply! I just haven't had the chance to flash the firmware, I will report back soon.

Just tried it again this morning, it works fantastically! What did you change? I want to try something similar on my cantor remix.

Hey, I turned off mouse keys and nkro and changed usb pid:

Well I tinkered with the cantor and flashed the firmware but it still has the same issue. However it's definitely fixed for the cheapino. Thanks again!


[FEATURE] Split file naming

Is your feature request related to a problem? Please describe.
Files generated when --fileSize argument is set can not be easily sorted:
activity.data.split-0.json.gz
activity.data.split-1.json.gz
activity.data.split-10.json.gz
activity.data.split-11.json.gz

Describe the solution you'd like
I would like left padding in split numbering
activity.data.split-00000.json.gz
activity.data.split-00001.json.gz
activity.data.split-00002.json.gz
activity.data.split-00003.json.gz

Moreover, let's say I am running elasticdump with following options:
elasticdump (...) --type data --output s3://mybucket/myfolder/activity.data.json.gz --s3Compress --limit 1000

As expected, I get a file named  activity.data.json.gz
Then I enable file splitting
elasticdump (...) --type data --output s3://mybucket/myfolder/activity.data.json.gz --s3Compress --limit 1000 --fileSize 1gb

Then I get files named
activity.data.json.split-0.gz.gz

So I have to remove the .gz to get what I want:
elasticdump (...) --type data --output s3://mybucket/myfolder/activity.data.json --s3Compress --limit 1000 --fileSize 1gb

Personnally, when compress is enabled, I would remove the trailing .gz here in order to get the .json extension, and then I would add it back here.
Another option would be to add the .gz extension when compression is enabled but file splitting is disabled.

All good ideas, but not that useful for this library. Feel free to fork.
Left padding limits to 4 digits, which means you have a max of 9999, I have seen more splits been done, this logic can work for you. i have no problem sort using bash ls -1 | sort ....
You don't need to include the extension at the end since it will be added at the library. Yes I can detect and strip, but this is really just nit-picking.
elasticdump (...) --type data --output s3://mybucket/myfolder/activity.data.json --s3Compress --limit 1000 --fileSize 1gb


Again keyboard focus doesn't return to putty tab when switching to SP window

What steps will reproduce the problem?
1. Switch to a different program via Alt-Tab or the mouse
2. Alt-Tab or mouse click back to SuperPuTTY
3. I can't to type into the current Putty tab (see screenshot)

What is the expected output? What do you see instead?
Expected output is the results of whatever you tried to type into the Putty tab.
Instead, nothing happens until I click in the Putty tab to give it keyboard
focus.

What version of the product are you using? On what operating system?
<IP_ADDRESS>

Please provide any additional information below.
It is not duplicate of Issue 152

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 11 Oct 2012 at 3:19
Attachments:

No_Focus_After_Swithing_Back_To_SP_Window_.png

Closing this issue but all hope is not lost! We still want to help.
See: https://github.com/jimradford/superputty/wiki/Legacy-Imported-Issues on how to help us to help you!


ci: remove docker needs

Codecov Report

Merging #12 (5c828da) into main (fe92e8e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   46.70%   46.70%
=======================================
  Files          24       24
  Lines         379      379
=======================================
  Hits          177      177
  Misses        202      202

Continue to review full report at Codecov.

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


Revert back to DeepSpeed FP16 defaults to prevent underflow

Our custom defaults are causing convergence problems with DS+FP16 -- removing these yields proper convergence. I spoke to @abhi-mosaic about it and we should be able to remove it entirely.

Another comment: we might need to think about the external users on our cluster who are saving checkpoint using the old loss values. Does changing this default affect them?

Another comment: we might need to think about the external users on our cluster who are saving checkpoint using the old loss values. Does changing this default affect them?

Good thinking, but I'd argue that compatibility of checkpoints across Composer versions isn't something we need to worry about until we hit 1.0.

I think checkpoints don't currently cache the DeepSpeed loss scaler right? I guess that's its own issue...

Wait, do we not cache the entire DeepSpeed config in order to reinitialize it from that config later on? I haven't dug into the DS code too much.


Failed to convert page to image. convert: symbol lookup error: /usr/lib/libraqm.so.0: undefined symbol: fribidi_get_bracket_types

I've installed Imagemagick, Ghostscript and poppel on Arch linux on a Aarch64 hardware (Odroid C2 like system). Arch kernel is 3.14.29 , I cannot upgrade the kernel and must stay on this.
I've also installed pdf-image module to use with node. When I try to convert a PDF file to jpg image I get the following error message:
`[test@test ~]$ node convertPdf2Jpg.js
Error occured: { message: 'Failed to convert page to image',
error:
{ Error: Command failed: convert -colorspace RGB -density 300 -interlace none -quality 100 "./scan_000864.pdf[0]" "/home/test/Extras/images/scan_000864-0.jpg"
convert: symbol lookup error: /usr/lib/libraqm.so.0: undefined symbol: fribidi_get_bracket_types
at ChildProcess.exithandler (child_process.js:272:12)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:927:16)
at Socket.stream.socket.on (internal/child_process.js:348:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
 killed: false,
 code: 127,
 signal: null,
 cmd: 'convert -colorspace RGB -density 300 -interlace none -quality 100 "./scan_000864.pdf[0]" "/home/test/Extras/images/scan_000864-0.jpg"' },

stdout: '',
stderr: 'convert: symbol lookup error: /usr/lib/libraqm.so.0: undefined symbol: fribidi_get_bracket_types\n' }`
Here is the code that I have. (FYI, this code works perfectly on another Intel based Ubuntu machine with latest kernel).
`
var PDFImage = require("pdf-image").PDFImage;
var path = require('path');
var util = require('util');
function convertPDFTOJPG(pathToPdf) {
const pdfImageOpts = {
outputDirectory: path.join(__dirname, './images'),
convertExtension: 'jpg',
convertOptions: {
'-colorspace': 'RGB',
'-interlace': 'none',
'-density': '300',
'-quality': '100'
}
};
var pdfImage = new PDFImage(pathToPdf, pdfImageOpts);
pdfImage.convertPage(0).then(function (imagePath) {
// 0-th page (first page) of the slide.pdf is available as slide-0.png
console.log("Converted.");
fs.existsSync("./scan_000864.jpg") // => true
}, function (err) {
console.log("Error occured: " + util.inspect(err));
});
}
process.on('uncaughtException', function (err) {
console.log('Caught exception: ' + err);
});
convertPDFTOJPG("./scan_000864.pdf");
`
In fact on this Armv8 machine if I enter the command "convert" with or without any arguments, I immediately get the following error:
convert: symbol lookup error: /usr/lib/libraqm.so.0: undefined symbol: fribidi_get_bracket_types
I suspect the problem is due to old Kernel or the Armv8 / Aarch64 Architecture. Unfortunately I am married to both these elements (Kernel version as well as the Architecture) so I cannot upgrade or change either one. Please advice what can I do to fix this.

You need to update fribidi to version 1.0 or higher.


Enhancement: Hit error bar

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
my suggestion is adding a hit error bar (the one in the bottom of the screen while playing osu) to visualize timing errors

Renamed: Enhancement: Hit error bar


auto switch to latest stable release in production

Mike do you know if there is a way to auto switch back from dev branch to latest stable release. I am currently testing some features that modify tracks and midi quite drastically and I don't want to forget to switch bach to master when working on big projects and accidentally crush all tracks and midi. I'm gonna ask this in cockos forum also.

https://forum.cockos.com/showthread.php?p=2371664#post2371664


slow gui resizing Editor window

Godot version
4.0.1 (also 4.0)
System information
Ubuntu 20.04, GLES and Forward, Gtx 1050
Issue description
Gui is slower than with Godot 3.5 especially when resizing editor window.
There is no difference, wether you have scenes loaded or not.
https://user-images.githubusercontent.com/49408918/226658479-32ae0533-5d3e-4929-9972-172ed80aad9a.mp4
Steps to reproduce

Open Godot 4 editor
tear window down to get smaller window
grab window in the corner to resize
watch window artifacts show up while resizing (sometimes visible for seconds)

Minimal reproduction project
"N/A"

Duplicate of https://github.com/godotengine/godot/issues/39222.


[WIP] golangci-lint

Not for merging. This is so I can manually go through everything.

Submitted to opa repository for review.


Projection Shard Work Distribution in the Async Daemon

This is probably going to be prime for not making the 4.0 cut, but let's still talk about it.
This is dependent first on #1718 and #1715.
If we know all the possible running nodes active in the system, plus all the known projection shards running asynchronously, the leader process should be extended to try to distribute different shards across different running nodes. We'd need a system to detect new nodes coming up and old nodes going offline. Each node should be listening for assignment changes by effectively just polling a table.

@xeromorph We have most certainly not forgotten about this, but other ongoing work has to go first. I won't even attempt top give a date when this would start, but at least after Wolverine goes 1.0 (plus the assumption to me is that we'd use Wolverine to coordinate the distributed work).

Good news! This is going to be worked on and hopefully completed in the next couple weeks. Maybe not the best news, it'll be going into the shortly forthcoming "Critter Stack Pro" paid model through JasperFx Software.
Marten 7 will have some ability to distribute daemon work across nodes though.