Code examples

Hi,
Thanks for this great library!
Your code examples 'https://github.com/noaa-ocs-hydrography/kluster/tree/master/examples' have been to great help. Would it be possible to add the following options to it:
-svp export
-track export
-cube cleaning example
Kind regards
Kurt

Hi Kurt,
I'm glad you are finding it useful!  Are these tasks that you have accomplished already?   Or that you need help accomplishing?  Id certainly welcome a PR for examples that you have come up with.
Eric

Hi Erik, no I have not accomplished that already. It would be great if you have the possibility to add some examples for that. Text files, ala the ones that the 'fq.export_variable' function is making would be great. Also I noticed in one of the old issues tickets that you mentionned cube cleaning. It would be great if you could show an example of how you would run that on a fq object.

Not sure that I have time to put together more examples, but I can link some of the code that I think is fairly straightforward.
For SVP, you can basically just use this - https://github.com/noaa-ocs-hydrography/kluster/blob/master/HSTB/kluster/fqpr_generation.py#L868
So 'fq.return_all_profiles' gets you the svp profiles and metadata.
Trackline export is here - https://github.com/noaa-ocs-hydrography/kluster/blob/master/HSTB/kluster/fqpr_generation.py#L3129
So 'fq.export_tracklines_to_file', with the trackline names you are interested in.  I think if you do not specify individual tracklines, you get them all.  It's been a while, but I think that is true.
For cleaning, we really don't have anything you can script, just because it relies so heavily on the mouse inputs.  You can see in the filter example, that there is a way to write a filter to do cleaning, say within a depth range.  That might be interesting to you.
https://kluster.readthedocs.io/en/latest/cleaning/index.html#writing-a-custom-filter

Thanks Eric, that worked :-)

Hi Erik and Barry,
you don't happen to have a s7k to kmall converter in your library, do you? If not, would you happen to know if there are any tools under the stars that does that?
Kind regards
Kurt


Feature request: Notification center to conform to ActiveSupport notifications API

I have a couple concerns with the instrumentation implementation presently in use.

Currently, the Project's notification_center is being type-checked against Optimizely::Notificiation center. This anti-pattern violates one of ruby's core idioms of duck typing. A notification center should only need to conform to the expected API. In particular, as long as the given object responds to send_notifications, then it should be considered a valid notification center.

Secondly, the existing NotificationCenter api does not conform to semi-standard notification APIs in Rails land. A de-facto standard API in Rails land is ActiveSupport::Notifications, of which there are many implementations. Conforming to this API would allow existing instrumentation objects within a codebase to be passed to the Optimizely project to handle the new optimizely events.

Lastly, the existing NotificationCenter only allows registration of Method listeners. This is completely abnormal ruby, as a normal ruby listener could be a block, proc, or lambda. Even better, it should be anything that responds to call, but at the very least, accepting block/proc/lambdas is table-stakes. (addressed by #216 🎉 )

My apologies for the significant delay in response to this issue. The team is updating our processes and reviewing all open issues and PR's. If this Feature Request is still relevant, please add your suggestion to our idea portal here https://feedback.optimizely.com/ where it can be evaluated with the other ideas for the product.


reportMissingImports

selenium Keys are not imported

Screenshot? Error log?

You haven't filled out the template, so there isn't enough information to help you.
Consider looking at our troubleshooting page, which covers many ways you can diagnose unresolved imports. If the page doesn't help, instructions to file an issue are at the bottom.
https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md

Closed issue :
webdriver.exe X64 needs to be in the path in order to import Keys


disallowExtraProperties does not propagate down to reference models

disallowExtraProperties is not being passed to recursive validations. So validations on nested models pass if there are extra properties on reference models, despite the disallowExtraProperties setting.
I believe the PR to fix issue #59 missed this.
I'll submit a PR to fix this.

PR #69 submitted.


Colab: The host is online, but the API seems to be disabled

Describe the bug
I'm using automatic1111 on Colab and running the extension is prompting me with the following:
The host is online, but the API seems to be disabled. Have you run the webui with the flag --api?
I have set up the webui command argument with --api but still getting the same message.
Screenshots

Hi, can you try accessing "/docs"? Like, if you access the webui via http://<IP_ADDRESS>:7860, you need to be able to access http://<IP_ADDRESS>:7860/docs

You can also provide us the notebook you are using to run the webui, so we can test it there.

We just really need the general format of the URL you are using to access the webui. (Ex. https://<domain>/<folder>)

also, seems to be an issue in the extension only. Will transfer it there.


GDScript: Do not reset return value in release build

Fixes #59239
Reset return value on error only in debug builds. Right now there is no mechanism in release build to know if there was error or not.

Thanks!

If a function would return a Resource but does not have return value declared, it returns null instead of the Resource. Setting the return type to Resource has fixed the issue. I am seeing this in Beta4. Should I open an issue?


Calibration Error

I can’t calibrate the flow meter with the new devel firmware. I was able to successfully calibrate it in 1.0.0, however.
When I go to the calibrate page, Select Tap 9 (that’s the one and only I’m using since the 1-sided PCB made it easier), Config by volume, enter in some ounces measured, but don’t get a 0 to show up in the Pulses box until the flow starts. No pulses seen at all.
Originally posted by @rkhanso in https://github.com/lbussy/keg-cop/issues/51#issuecomment-1274170349

don’t get a 0 to show up in the Pulses box until the flow starts. No pulses seen at all.

@rkhanso I want to be sure I understand this.  Why would it matter if the 0 shows up or not if you have not started flow?  The process for "By Volume" is:

Select "by volume"

Draw a sample of a known volume (e.g. 12 ounces)

(at this point pulses should register)

Enter "12" as the volume dispensed

The calculated PPU should be displayed

Enter "12" in the

Keg Cop quit working for me again. I think I'm going to have to go back to use CraftbeerPi3 for now on the Kegerator. I may try Bru Control in the future for all aspects of my brewing process.
From my memory though...
the 0 didn't pre-populate in the pulses box after I chose to calibrate, which then made it impossible to calibrate the flow meter. I knew this right away, because when there was a 0 in that box, I could change the number in the box. No zero in the box, the calibration number could not be entered and calibration was not possible.

Keg Cop quit working for me again.

In what way?  Mine has been running (without actually pulling beer) for two weeks or so.  I need to ficx the me not getting any beer part.

From my memory though...

I'll have to try to set some time aside to work through that.  I'm still not sure if it's a documentation problem or a code problem.  Either way it's my problem I'm just not sure which.

It's been hit or miss whether I can get the web pages to load. It still seems to be rebooting randomly and losing configs. I have to go back in and reset the sensors, brewery name, etc.
Wouldn't you know.....right now it seems to be working.
Eventually it'll stop and the kegerator won't be told to turn on and it'll be 68F in it again.

But now it just went berzerk again.  I clicked to go to the settings page and everything was reset - the 3 temp probes went to disabled. Control was then lost since there are no temps to control.
The only thing that doesn't get reset is the Tap settings. They stick. Everything else is lost when "it" happens

One thing that I think would be helpful - some feedback after clicking the Update button on the settings page. I get no response that it accepted my changes. It just stays on that page and it looks like nothing happened until I leave it and go back (if it doesn't then reset itself again).

One thing that I think would be helpful - some feedback after clicking the Update button on the settings page. I get no response that it accepted my changes. It just stays on that page and it looks like nothing happened until I leave it and go back (if it doesn't then reset itself again).

There is - the button will disable and show a spinning icon while it is applied.  If it goes back to normal then it is applied.  If not, there will be an error banner.

I don't get a spinning circle. I get nothing confirming or denying the changes were saved or not.
I still keep getting the sensors and control resetting very frequently. Sometimes within 20 seconds after setting them up. The Tap settings are still there, but the temp sensors all go disabled and the temp control is disabled.
I'm going to stick with CraftbeerPi3 on the Kegerator.

Is there a big difference in v 1.1.1 and 1.2.0-alpha?
The 1.1.1 version runs way better for me than the 1.2.0 version.
1.2 is very slow between web pages or doesn’t load them at all. The ESP crashes.
1.1 is very stable and fast.
From: Lee Bussy @.>
Sent: Thursday, October 13, 2022 9:05 AM
To: lbussy/keg-cop @.>
Cc: Roger Hanson @.>; Mention @.>
Subject: Re: [lbussy/keg-cop] Calibration Error (Issue #150)
Keg Cop quit working for me again.
In what way? Mine has been running (without actually pulling beer) for two weeks or so. I need to ficx the me not getting any beer part.
From my memory though...
I'll have to try to set some time aside to work through that. I'm still not sure if it's a documentation problem or a code problem. Either way it's my problem I'm just not sure which.
—
Reply to this email directly, view it on GitHub https://github.com/lbussy/keg-cop/issues/150#issuecomment-1277668098 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AIIV7FX5KFATKGWRE4SG2BTWDAJJJANCNFSM6AAAAAARCFUBQE .
You are receiving this because you were mentioned.Message ID: @.***>

Is there a big difference in v 1.1.1 and 1.2.0-alpha?

Well, 1.2.0-Alpha is no longer supported; I released 1.2.0 officially, so if you are going to use a version, you should use that.
There are several changes between them, but the largest change is the core libraries from the manufacturer.  They are considerably larger and, by all accounts, do bring some additional quirks.

Are there big differences in the web server, web pages, file system or basic underlying systems?
I ask, because I can run v 1.1.1 perfectly with fast web page response, no trouble loading pages for weeks so far.
But when on any of the 1.2 versions, the only web page that almost always opens is the home or about page. Often the temperature page doesn’t even show up in the menu and the setup page almost never loads (gets spinning circle). It still crashes frequently and I lose temp sensor settings, sometimes within a minute of setting them.
The reason I wanted v1.2 was to get the tower temp sensor to control the solenoid GPIO for a tower fan. I’ll gladly forget about that feature and just run 1.1.1 if that’s what it takes for the whole thing to be stable.
From: Lee Bussy @.>
Sent: Saturday, October 29, 2022 9:56 AM
To: lbussy/keg-cop @.>
Cc: Roger Hanson @.>; Mention @.>
Subject: Re: [lbussy/keg-cop] Calibration Error (Issue #150)
Is there a big difference in v 1.1.1 and 1.2.0-alpha?
Well, 1.2.0-Alpha is no longer supported; I released 1.2.0 officially, so if you are going to use a version, you should use that.
There are several changes between them, but the largest change is the core libraries from the manufacturer. They are considerably larger and, by all accounts, do bring some additional quirks.
—
Reply to this email directly, view it on GitHub https://github.com/lbussy/keg-cop/issues/150#issuecomment-1295861188 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AIIV7FVKAB4XC5EQ7O5MP2DWFU3HZANCNFSM6AAAAAARCFUBQE .
You are receiving this because you were mentioned.Message ID: @.***>

Fix merged to devel, closing.


Fix animation-name check for old browsers

According to a bug tracker of a developing app, old browsers like Safari of IOS8 or Chrome of Android5 could return null instead of requested style property. This patch brings additional checks.
Screenshot from our bug tracer:

Thanks!


Issue with babel runtime regenerator

var wu = require('./dist/wu.js');
TypeError: Cannot read property 'regeneratorRuntime' of undefined
at wu.js/dist/wu.js:3427:24
at Object. (wu.js/dist/wu.js:4020:4)
at Object.module.exports (wu.js/dist/wu.js:4025:31)
at webpack_require (wu.js/dist/wu.js:30:30)
at Object. (wu.js/dist/wu.js:3377:19)
at Object. (wu.js/dist/wu.js:3393:31)
at webpack_require (wu.js/dist/wu.js:30:30)
at Object. (wu.js/dist/wu.js:67:28)
at webpack_require (wu.js/dist/wu.js:30:30)
at wu.js/dist/wu.js:50:18

Apologies, this only happens when running node in harmony mode.


Press and hold key in terminal

Issue Type: Feature Request
Pressing and holding a key in the integrated terminal should type the character multiple times, rather than just triggering key press once. This is the behavior in most other command prompts.
VS Code version: Code 1.30.1 (dea8705087adb1b5e5ae1d9123278e178656186a, 2018-12-18T18:05:00.654Z)
OS version: Darwin x64 17.7.0

This is likely caused by this? https://github.com/xtermjs/xterm.js/issues/265


🌱 test commit

What this PR does / why we need it:
test
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@kashifest it is running and failed: https://github.com/metal3-io/ip-address-manager/actions/runs/6729695242/job/18290998859?pr=371

@kashifest it is running and failed: https://github.com/metal3-io/ip-address-manager/actions/runs/6729695242/job/18290998859?pr=371

Yes perhaps it requires write permission after all. cc @tuminoid

Yes perhaps it requires write permission after all. cc @tuminoid

maybe, in capi they have added the permission. I will add it, lets see.

maybe, in capi they have added the permission. I will add it, lets see.

We added it already, its now working, I mean failing on PRs where we dont have correct titles, albeit we have to only see the failure reason on the logs of the workflow Run. Check #370

/close


[ownership] Implement Interior Pointer handling API for RAUWing addresses

This PR contains 4 commits all in service of one goal: allowing us to eliminate address_to_pointer, pointer_to_address round trips. This is an important problem to solve since the stdlib uses this pattern to reinterpret cast addresses that point into COW containers. Our emission strategy of small scopes generally makes it so that when we get the underlying address, we create a borrow scope, then address_to_pointer a pointer derived from a ref_element_addr. Later we then cast the pointer to the new address type and then use it for whatever purpose the author intended.
It is important that we be able to convert these to addresses for memory promotion/alias analysis/etc on the stdlib, so this PR introduces a new utility that if necessary will extend the lifetime of the base value that the interior pointer operand is derived from and produce a new access path into the base value that is valid over all uses of the new value. Later passes (CopyPropagation/SemanticARCOpts) will then clean up the ARC and intervening passes can now actually use these addresses without being stymied by the escaping nature of pointer_to_address.

Now in terms of the 4 commits themselves, lets go through each:

The first is hiding simplifyInstruction and changing all callers of it to use a simplifyAndReplace variant instead. Already there was a hidden assumption that simplifyInstruction's result would be passed to replaceAllUsesAndErase, this just eliminates that bug. It also prepares the
OwnershipFixupContext has grown a bit and I want to convert it back to a more context struct that various utilities use. So, I extracted the RAUW methods onto a new helper class called OwnershipRAUWHelper that composes with OwnershipFixupContext.
In this PR,  I implemented the actual RAUW API and got everything in place.
In this final API, I let InstSimplify fold identity address_to_pointer/pointer_to_address using this new utility. I also added a bunch of tests that exercise the new API with various CFG patterns (diamonds, loops, etc). Once this lands, I am going to use this to implement other optimizations like this (e.x.: non-identity reinterpret casts).

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - fb994e99da151c3bbcd6c11cf7f5b4b42c6b4ed2

Build failed
Swift Test OS X Platform
Git Sha - fb994e99da151c3bbcd6c11cf7f5b4b42c6b4ed2

Build failed
Swift Test Linux Platform
Git Sha - fb994e99da151c3bbcd6c11cf7f5b4b42c6b4ed2

Build failed
Swift Test Linux Platform
Git Sha - fb994e99da151c3bbcd6c11cf7f5b4b42c6b4ed2

@swift-ci test

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 70091cf0820d3454f99d8e975402d5ca467aa874

Build failed
Swift Test Linux Platform
Git Sha - 70091cf0820d3454f99d8e975402d5ca467aa874

Build failed
Swift Test OS X Platform
Git Sha - 70091cf0820d3454f99d8e975402d5ca467aa874

Build failed
Swift Test OS X Platform
Git Sha - 70091cf0820d3454f99d8e975402d5ca467aa874

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - d6928cd7a9a295fc02e763d0748a16b0ee2fe97b

Build failed
Swift Test OS X Platform
Git Sha - d6928cd7a9a295fc02e763d0748a16b0ee2fe97b

Build failed
Swift Test Linux Platform
Git Sha - d6928cd7a9a295fc02e763d0748a16b0ee2fe97b

Build failed
Swift Test Linux Platform
Git Sha - d6928cd7a9a295fc02e763d0748a16b0ee2fe97b

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@atrick I implemented InteriorPointerAddressRebaseUseDefChainCloner since I couldn't figure out how to extend the code in tree to handle this case. If you can show me how to do this, I would be happy to eliminate it.

@atrick I implemented InteriorPointerAddressRebaseUseDefChainCloner since I couldn't figure out how to extend the code in tree to handle this case. If you can show me how to do this, I would be happy to eliminate it.

I talked with @atrick, he is going to do the additional review he wanted post-commit.

I talked with @atrick, he is going to do the additional review he wanted post-commit.


fped: init at unstable-2017-05-11

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

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

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

@GrahamcOfBorg build fped

@worldofpeace I've made your corrections.

@GrahamcOfBorg build fped

@worldofpeace Thanks for the suggestions, done.

@GrahamcOfBorg build fped

Build failed with
ppmcolormask: can't open color names dictionary file from the path '/usr/local/netpbm/rgb.txt:/usr/share/netpbm/rgb.txt:/etc/X11/rgb.txt:/usr/lib/X11/rgb.txt:/usr/share/X11/rgb.txt:/usr/X11R6/lib/X11/rgb.txt' and Environment variable RGBDEF not set.  Set RGBDEF to the pathname of your rgb.txt file or don't use color names.
make: *** [Makefile:116: icons/point.xpm] Error 1

So I guess another environment variable to set?

Yay, that's what we just removed.
On Fri, 12 Apr 2019, 20:48 worldofpeace<EMAIL_ADDRESS>wrote:

Build failed with
ppmcolormask: can't open color names dictionary file from the path '/usr/local/netpbm/rgb.txt:/usr/share/netpbm/rgb.txt:/etc/X11/rgb.txt:/usr/lib/X11/rgb.txt:/usr/share/X11/rgb.txt:/usr/X11R6/lib/X11/rgb.txt' and Environment variable RGBDEF not set.  Set RGBDEF to the pathname of your rgb.txt file or don't use color names.
make: *** [Makefile:116: icons/point.xpm] Error 1
So I guess another environment variable to set?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/51285#issuecomment-482683277, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArCY9pme2k4erB7nnE4S-kry_x6W5cgks5vgNTmgaJpZM4Y746g
.

Yay, that's what we just removed.
…
On Fri, 12 Apr 2019, 20:48 worldofpeace, @.***> wrote: Build failed with ppmcolormask: can't open color names dictionary file from the path '/usr/local/netpbm/rgb.txt:/usr/share/netpbm/rgb.txt:/etc/X11/rgb.txt:/usr/lib/X11/rgb.txt:/usr/share/X11/rgb.txt:/usr/X11R6/lib/X11/rgb.txt' and Environment variable RGBDEF not set. Set RGBDEF to the pathname of your rgb.txt file or don't use color names. make: *** [Makefile:116: icons/point.xpm] Error 1 So I guess another environment variable to set? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#51285 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AArCY9pme2k4erB7nnE4S-kry_x6W5cgks5vgNTmgaJpZM4Y746g .

Yep it was https://github.com/NixOS/nixpkgs/pull/51285#discussion_r238277498
Yay?

Ah, good to know I wasn't crazy.
On Sat, 13 Apr 2019, 06:30 worldofpeace<EMAIL_ADDRESS>wrote:

@worldofpeace commented on this pull request.
In pkgs/applications/science/electronics/fped/default.nix
https://github.com/NixOS/nixpkgs/pull/51285#discussion_r275082186:

+, pkgconfig
+}:

+with lib;
+stdenv.mkDerivation rec {

name = "fped-${version}";
version = "unstable-2017-05-11";

src = fetchgit {
url = "git://projects.qi-hardware.com/fped.git";
rev = "fa98e58157b6f68396d302c32421e882ac87f45b";
sha256 = "0xv364a00zwxhd9kg1z9sch5y0cxnrhk546asspyb9bh58sdzfy7";
};

LEX="flex";
RGBDEF="${netpbm}/share/netpbm/misc/rgb.txt";

@expipiplus1 https://github.com/expipiplus1 This is needed #51285
(comment)
https://github.com/NixOS/nixpkgs/pull/51285#issuecomment-482683277.
Things still built because it was on a different linux distro and without
sandboxing.
Corrected in d571ec0
https://github.com/NixOS/nixpkgs/commit/d571ec0df025dfcc17196065e08c157b3b284ee9
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/51285#discussion_r275082186, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGRJXEYHAUHS74ONJGNA5DPQEEP3ANCNFSM4GHPR2QA
.

@expipiplus1 Can you squash the commits?

@worldofpeace done, thanks!


Visualize inertia is freezing the GUI

Environment

OS Version: e.g, Ubuntu 20.04
Source: Garden

Bug
I loaded a world in Gazebo and I try to see the inertia of the model but the GUI is getting freeze

I noticed that some times it takes a looong time, but it does unfreeze eventually. I think that the GUI plugin code can be optimized.


keep PCC public-comments open until they are updated

bring back into public-comment section, possibly indicating they are public-comment versions for which the comment period has closed.

Mobile Antepartum Summary (mAPS) Release 1.0.0-comment - Published 2024-06-04

USA Mobile Antepartum Summary (mAPS.us) Release 1.0.0-comment - Published 2024-06-04

Occupational Data for Health (ODH) Release 1.0.0-comment - Published 2024-03-08

@MaryLJ I created this to track the PCC old public-comment.


Handling of the time conditioning

Hi, thanks for the implementation.
I was trying to implement the RIN paper and was looking at this implementation for reference and i observed that the time conditioning was handled differently. In the paper, the say they just add it as one more latent token and here i see it's closer to other diffusion models handling of conditioning.
Is there some reason for this choice of implementation? Does it improve performances? Thanks!

@nicolas-dufour only that i was unaware of this! would be happy to make the correction, if you can point me to the relevant passage
do they discretize and select out an embedding, or construct it from an MLP?

From the paper they say the following:
"Conditioning variables, such as class labels and time step t of diffusion models, are mapped to embeddings; in our experiments, we simply concatenate them to the set of latents, since they only account for two tokens."
So i would say they map them with an MLP, and then concat to the rest of the tokens

@nicolas-dufour ok, should be in effect in 0.5.0! let me know if that looks ok to you or if you find any other issues :pray:

@nicolas-dufour are you planning on trying this out during your internship at Meta? would welcome you to share your experiments between adaptive layernorm vs latent token conditioning, if you are allowed to do so

I'm not at meta anymore, but I'm working on this for my PhD will try to do some experiment and I will post here if i find anything!

@nicolas-dufour yes please, i'm very curious what is the better approach!
if it turns out latent token conditioning is better, it would be another 'attention is all we need' moment :smile:

@nicolas-dufour also, there was a time when i implemented DDPM incorrectly a long time ago, forgot to time condition, and yet it still converged and sampled decent pictures. i never dug into that, but thought i'd share

Concatenating the time and class embeddings to the set of latents (i.e. along the seq axis) is the default used in the paper.
We've open-sourced the code, here is the architecture, in case it may be of help: https://github.com/google-research/pix2seq/blob/main/architectures/tape.py


Updated hmcollector to 2.16.5 to support paradise subscriptions

Summary and Scope
Updated hmcollector to 2.16.5 to support paradise subscriptions
Issues and Related PRs

Resolves CASMHMS-6127

Testing
Tested on:

tyr

Test description:

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)? Y
Were continuous integration tests run? If not, why? Y
Was upgrade tested? If not, why? Y
Was downgrade tested? If not, why? Y
Were new tests (or test issues/Jiras) created for this change? Y

Risks and Mitigations
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

@shunr-hpe Please provide JIRA ticket number in commit message and PR subject, it really helps to navigate over git history in csm repo.


enynes

Is it possible to provide IUPAC names and/or annotate the following entries to ChEBI standard:
Aethusin (CHEBI:2501)
I suppose it is (2E,8E,10E)-trideca-2,8,10-triene-4,6-diyne
https://de.wikipedia.org/wiki/Aethusin (in German)
//
3-Penten-1-yne (CHEBI:167062)
IUPAC name: (3E)-3-penten-1-yne
//
Tridec-1-ene-3,5,7,9,11-pentayne (CHEBI:9699)
IUPAC name: tridec-1-ene-3,5,7,9,11-pentayne
https://chem.nlm.nih.gov/chemidplus/rn/startswith/2060-59-5

All 3 entries have now been annotated.


Add package uriparser to SPECS-EXTENDED

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[X] The toolchain has been rebuilt successfully (or no changes were made to it)
[X] The toolchain/worker package manifests are up-to-date
[X] Any updated packages successfully build (or no packages were changed)
[X] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[X] All package sources are available
[X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[X] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[X] All source files have up-to-date hashes in the *.signatures.json files
[X] sudo make go-tidy-all and sudo make go-test-coverage pass
[X] Documentation has been updated to match any changes to the build system
[X] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Adds package uriparser to SPECS-EXTENDED
Does this affect the toolchain?

NO
Test Methodology

Pipeline build id:
AMD64 Buddy build with check
ARM64 Buddy build with check

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=416036&view=results

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=416036&view=results


Null sorting fix

See https://github.com/TriPSs/nestjs-query/issues/270

@abrenoch the linting errors now could be fixed by running the linter with --fix. (Bit weird that Nx no longer outputs it here in the CI)

Hey @TriPSs does your nx cloud run say what the lint errors are? I'm trying to work out what is failing, even pointed the nxCloudAccessToken to a workspace I can check, and I'm seeing these "Buildable libraries cannot import or export from non-buildable libraries" errors when running yarn nx run-many --target=lint --all (adding --fix didnt seem to help).
Could you provide some insight please? I have no idea what the issue here is.

@abrenoch reran the jobs and disabled that Nx does not output the logs here, bit weird that this was auto enabled.

Added a couple small changes the linter was complaining about - odd they were unrelated to the actual change I had made, but /shrug

Thanks for everything!


User can access emoji list and bug fix!

This PR makes us be able to access raw emoji list. Yay! :smile: (https://github.com/ta2gch/cl-emoji/pull/4#issuecomment-298235899)
...And two fixes:

A test fails by changing emoji list format
A bug: codepoint and name returns keyrword :characters, not correspond characters

I hope you favor this.

Thank you!


Option for relative positioning to parent

Great job on the library!
I've been playing around with it, and it's been really useful for notifications. One thing I've noticed is that the positioning seems to be based only on the active screen. Is there a way to make it position relative to its parent element? Maybe I'm missing something, but it would be awesome if you could point me in the right direction!

Thanks, I appreciate it!
Currently, you can only position the toasts relative to a screen (either the main screen, the screen the parent widget is on, or any other specific fixed screen).
I like the idea of being able to position them relative to the parent widget, though. That's definitely something I could implement.
Just to make sure I understood you correctly, you mean something like in this screenshot where the toasts would be shown in the bottom right corner of the parent widget and not in the bottom right corner of the screen, correct?

Yep, that is exactly what I was thinking about!

i use Toast.setOffset(x, y) instead , hope your implement 😄

i use Toast.setOffset(x, y) instead , hope your implement 😄

I will implement it, don't worry. I'm just really busy for the next two weeks, but after that, it should only take a few days until I release it.
I'll also make it possible for the notifications to move with the parent when it is resized or moved, so the toasts will always stay in the same position relative to the parent if enabled :)

This feature has now been released in v1.3.0.
After updating to the latest version, you can use the static method Toast.setPositionRelativeToWidget(widget), where the parameter is the widget that the toasts will be relatively positioned to.
Example:
class Window(QMainWindow):
    def __init__(self):
        super().__init__(parent=None)

        self.resize(600, 320)

        # Add button and connect click event
        self.button = QPushButton(self)
        self.button.setText('Show toast')
        self.button.clicked.connect(self.show_toast)

        # Relative to window
        Toast.setPositionRelativeToWidget(self)
        Toast.setOffset(10, 10)

    # Shows a toast notification every time the button is clicked
    def show_toast(self):
        toast = Toast(self)
        toast.setDuration(5000)  # Hide after 5 seconds
        toast.setTitle('Success! Confirmation email sent.')
        toast.setText('Check your email to complete signup.')
        toast.applyPreset(ToastPreset.SUCCESS)  # Apply style preset
        toast.show()


File hands.py, solution_base.py missing, but they exist in my file manager.

Please make sure that this is a bug and also refer to the troubleshooting, FAQ documentation before raising any issues.
System information (Please provide as much relevant information as possible)

Have I written custom code (as opposed to using a stock example script provided in MediaPipe): I did not, I used  freeCodeCamp.org's hand tracking code.
Programming Language and version ( e.g. C++, Python, Java): Python 3.9
MediaPipe version: <IP_ADDRESS>
Solution ( e.g. FaceMesh, Pose, Holistic ): Hand

Describe the current behavior:
When i launch it with pycharm, it gives me this error:
Traceback (most recent call last):   File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\HandTrackingMin.py", line 8, in <module>     hands = mpHands.Hands()   File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\venv\lib\site-packages\mediapipe\python\solutions\hands.py", line 109, in __init__     super().__init__(   File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\venv\lib\site-packages\mediapipe\python\solution_base.py", line 237, in __init__     validated_graph.initialize( FileNotFoundError: The path does not exist.
Describe the expected behavior:
Starts tracking my hand, and output coordinates
Standalone code to reproduce the issue:
Install opencv-python latest version using pip
Install mediapipe latest version using pip
Launch pycharm
Copy the code
Start the code
Get the error
Other info / Complete Logs :
The code that I'm using:
import cv2
import mediapipe as mp
import time

cap = cv2.VideoCapture(0, cv2.CAP_DSHOW)

mpHands = mp.solutions.hands
hands = mpHands.Hands()
mpDraw = mp.solutions.drawing_utils

pTime = 0
cTime = 0

while True:
    success, img = cap.read()
    imgRGB = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
    results = hands.process(imgRGB)
    # print(results.multi_hand_landmarks)

    if results.multi_hand_landmarks:
        for handLms in results.multi_hand_landmarks:
            for id, lm in enumerate(handLms.landmark):
                # print(id, lm)
                h, w, c = img.shape
                cx, cy = int(lm.x * w), int(lm.y * h)
                print(id, cx, cy)
                # if id == 4:
                cv2.circle(img, (cx, cy), 15, (255, 0, 255), cv2.FILLED)

            mpDraw.draw_landmarks(img, handLms, mpHands.HAND_CONNECTIONS)

    cTime = time.time()
    fps = 1 / (cTime - pTime)
    pTime = cTime

    cv2.putText(img, str(int(fps)), (10, 70), cv2.FONT_HERSHEY_PLAIN, 3,
                (255, 0, 255), 3)

    cv2.imshow("Image", img)
    cv2.waitKey(1)

Hi @Rego0116, Can you try installing the latest pip install mediapipe==0.8.7.

Still doesn't work, gives me the same problem sadly.
Traceback (most recent call last):
  File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\HandTrackingMin.py", line 8, in <module>
    hands = mpHands.Hands()
  File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\venv\lib\site-packages\mediapipe\python\solutions\hands.py", line 109, in __init__
    super().__init__(
  File "C:\Users\Reiner Regő\PycharmProjects\HandTrackingProject\venv\lib\site-packages\mediapipe\python\solution_base.py", line 237, in __init__
    validated_graph.initialize(
FileNotFoundError: The path does not exist.

It seems like the line   validated_graph.initialize(           binary_graph_path=os.path.join(root_path, binary_graph_path))
is causing problems, by the path doesn't exist


Bevel setup issues in local development

I tried setting up an initial test-network in Ubuntu 18.04
All the steps have been clearly followed as given in the doc: https://blockchain-automation-framework.readthedocs.io/en/v<IP_ADDRESS>/developer/baf_minikube_setup.html
I am facing the following error  when I run " docker run -it -v $(pwd):/home/blockchain-automation-framework/ hyperledgerlabs/baf-build
" and could not able to make progress.

Also, I have tried looking for help online no relevant issues were there. Post this I used Windows to set the cluster I found https://docs.docker.com/toolbox/ one of the packages required to set up is deprecated.
Please help by suggesting a way out.
Thank you

@Sayyad-Nayyaroddeen  have you checked https://hyperledger-bevel.readthedocs.io/en/latest/operations/bevel_verify.html before creating this issue?

@Sayyad-Nayyaroddeen hope the guide and docs in general are useful.
You can always put up questions & feedback on our Discord channel. Please join our Discord first.

@Sayyad-Nayyaroddeen are you able to fix this issue, pls help because I can not able find help in this doc
https://hyperledger-bevel.readthedocs.io/en/latest/operations/bevel_verify.html


Ruby 3

Ruby 3.0 was released and I'd like to kick its tires in CI to see if the performance gain will be as good as for some of the highlighted scenarios, but it seems setup-ruby does not support 3.0.0 or similar yet. Could this be added? Thank you for this action! ❤

This other action (the official Ruby org action, and the one recommended in starter-workflows) now has Ruby 3.0.0.

Works, thank you, happy holidays 🎄


[ComposedModal] does not overlay all other elements

Describe the bug
When the ComposedModal is used with the Header, the Header overlaps the top of the modal content at small display sizes
To Reproduce
Steps to reproduce the behavior:

Go to implementation with ComposedModal and Header
Open modal
Change screen size to mobile / tablet
See error

Expected behavior
Nothing should overlap modal content
Environment/versions:

OS: MacOS
Browser: chrome

Additional context

Specific timeline issues / requests
No timeline

Tried testing this with a Header and ComposedModal in Storybook and wasn't able to reproduce. Closing as I believe this is our own (Monitor)  implementation bug


confirm installation process

Document how users can install a version of parastell that is outside the source tree and findable in the path, and confirm that imports work as expected.

Closed by #69


Trans update for Chinese Simplified

deepl >> human trans
ref: https://steamcommunity.com/sharedfiles/filedetails/?id=2785892768   WikiRim简体中文汉化包

Thanks, should be published in c9af29d


[go_router] Transfer gorouter.dev ownership to Flutter

The readme of go_route https://pub.dev/packages/go_router points to https://gorouter.dev/ which is not owned by flutter. We should migrate these docs to flutter.dev
We also need to make sure all the migration doc is included

https://github.com/flutter/uxr/blob/master/nav2-usability/scenario_code/lib/sign-in-routing/sign_in_routing_go_router.dart is also outdated


Support transparent thematic gradient settings

Discussed in https://github.com/iTwin/itwinjs-core/discussions/6212
ThematicGradientSettings is used both for thematic display (colorizing based on implicit properties like elevation or normal) and scientific visualization (colorizing based on auxiliary polyface scalar data).
In both cases, the alpha channel of the gradient's color keys is ignored - the transparency is determined by the surface color's alpha channel alone.
Proposal: add a transparencyMode to ThematicGradientSettings of enum type with two initial options:

use the surface alpha, ignoring gradient alpha (default)
multiply gradient alpha by surface alpha

The latter will behave the same as material alpha does, and address the request. In future we may find a need for additional transparency modes.
We will have to handle the case in which between the surface alpha and the gradient colors we have a mix of opaque and translucent colors. That will require drawing in both passes and discarding in one based on the alpha computed in the shader. We do the same thing for textures that contain a mix of fully-opaque and semi-transparent pixels, keying off of the HasTexture surface bit flag.

ThematicGradientSettings is used both for thematic display (colorizing based on implicit properties like elevation or normal) and scientific visualization (colorizing based on auxiliary polyface scalar data).
In both cases, the alpha channel of the gradient's color keys is ignored - the transparency is determined by the surface color's alpha channel alone.
Proposal: add a transparencyMode to ThematicGradientSettings of enum type with two initial options:

use the surface alpha, ignoring gradient alpha (default)
multiply gradient alpha by surface alpha

The latter will behave the same as material alpha does, and address the request. In future we may find a need for additional transparency modes.
We will have to handle the case in which between the surface alpha and the gradient colors we have a mix of opaque and translucent colors. That will require drawing in both passes and discarding in one based on the alpha computed in the shader. We do the same thing for textures that contain a mix of fully-opaque and semi-transparent pixels, keying off of the HasTexture surface bit flag.

@markschlosseratbentley I modified your issue description with a proposed solution.


Add Fast Palm AI ChatBot 💬 in list

Website URL
https://fast-palm-ai-chatbot.vercel.app

Website Type

[x] Chatbot Ai site
[ ] Other

Website Description and Usage

Please provide a clear description to help others understand how to use it.

[x] 😄 Free to use (open and ready to use with no restrictions, uses your device threads)
[ ] 🔑 Free to use, but requires login or password
[ ] 🤑 Paid service
[ ] 🎁 Paid service with a trial period

Website Icon - Path (optional)

Square-shaped icon

For example: https://fast-palm-ai-chatbot.vercel.app/img/robot.png

Requires International Access (optional)

[x] No
[ ] Yes

PR welcome.


Update mixins.py

Make the json content a more robust to make it work in cases with content-type like 'application/json;charset=utf-8'

Hi @gusriobr
Can you please expose what's the goal of your PR? Are you trying to prevent that header contains also charset...or what's the goal?
thanks for the information, will be good that you create first issue with the explanation.
thanks in advance!

The condition to try to parse the content of the response as json is content-type == 'application/json', but in some cases the "Content Type" header can include the charset, so accessing the header with request will outcome values like
application/json;charset=utf-8.
That makes the client return the raw content (self.response.content).
https://developer.mozilla.org/es/docs/Web/HTTP/Headers/Content-Type
Thank you


[POC] feat: Add model-property type

[x] Added or updated tests
[x] Documented user facing changes
[ ] Updated CHANGELOG.md

Introduction
Laravel has a lot of methods that have string parameters that represent a property of a Model class. For example, the where() method on a query builder could receive a model property string as its first parameter:
// Here, we expect 'username' to be a property on the User model.
User::where('username', 'test')->get();

Similarly, when creating a new User:
User::create([
   'name' => 'Test',
   'email' =><EMAIL_ADDRESS>]);

we're expected both name and email to be a property on the User class.
This pull request attempts to provide a proof of concept for easily verifying that these strings actually exists as a property on a model by introducing a new type: model-property.
How does it work?
The model-property type is a generic type whose argument can be a subclass of \Illuminate\Database\Eloquent\Model. For example, the type model-property<User> only accepts strings that are properties on the User class.
The property uses the ModelPropertyExtension under the hood, so this type is very dependent on Larastan being able to analyze the migrations. I've currently disabled the type by default. It will just be seen as a string. To enable it, you have to set checkModelProperties: true in your configuration file.
Caveats
In the case of Builders methods, the current implementation can give false positives. E.g. the following examples are perfectly valid but are seen as invalid:
User::selectRaw('id as newid')->pluck('newid')
User::get('users.id')

I could remove the typehint from all Builder where methods and only put them on update(), create() and, for example, on model properties such as $fillable and $hidden.
The errors are not clear at all. If a property does not exist on your model the following error will be printed:
Parameter #1 $property of method TestClass::test() expects model-property<App\\User>, string given.

which most users probably won't understand unless they read through the documentation.
The current implementation is not entirely finished yet, but before I put more time in it, I'd like to know whether this is something you'd consider adding to Larastan. If you like the idea, I could brush it up and add some more extensive testing. Any suggestions would also be appreciated.
If this is something you'd see the potential in, then I think a similar model-relation property would also be of great value. This could verify the strings passed to whereHas(), with(), load() and many more.

E.g. the following examples are perfectly valid but are seen as invalid:
User::get('users.id')

Not sure I follow, as you also used ->where() at the beginning of the description of the PR.
Is this invalid because it's using ::get() or because it's using <table prefix>.<column>?
thanks!

I because it's using <table prefix>.<column>

It's because the prefix is infront of it, indeed. Given some simple User class, model-property<User> would accept only the following values: id, name, email, password.
For that reason it might not be worth checking the builder methods because prefixing a column name will result in a false positive.

Ah that's too bad.
In most private projects, the table prefix is a required code style.
Primary reason is that conditions coupled with joins and ambiguous column names require this and I've had one too many bug in the past where the same in select would break things later.

Ah that's too bad.

I could also create a db-column type, or however you want to call it, which would allow for prepending the table name. We could then use this type for all where() like methods, and we could use the current model-property type for methods such like update() and create().

Sounds good to me!
I sure have at least one big project to run this against with lots of variations, so I think I can help testing this.

Hey,
I was also working on this same thing 😅 But my approach is different. I didn't think model property as a type. It can be useful I think.
I can't do detailed review now. I'm on holiday until this weekend and next week.
But this is definitely something we want. So feel free to continue working on this. And when I'm back we can go through together if you want. Fixing false positives, edge cases etc.
Thank you!

Hi again,
I did some quick review. The idea is mostly fine. But as you mentioned there is one caveat:

The errors are not clear at all. If a property does not exist on your model the following error will be printed:
Parameter #1 $property of method TestClass::test() expects model-property<App\\User>, string given.
which most users probably won't understand unless they read through the documentation.

This is because of the new type we are using. And PHPStan checks the types of the arguments passed into the methods. And when we say this model doesn't have that property, it generates the error message above.
As far as I know, there is no real way to improve that message. One hack is to have more information in the describe method. But at best it'd be something like Parameter #1 $property of method TestClass::test() expects a property of App\User, string given. which is still confusing.
Another way to go about this is to write custom rules. Then we can write our own error messages. This is also how phpstan-doctrine extension does it. And I have a wip feature branch doing this.
I think, to sum up:

New type allows us to just type hint it anywhere we want, and PHPStan will automatically check it. But the error message is confusing.

Custom rules allows us to configure better error mesages, but requires us to write more rules for every usage of model property in Laravel code. Plus it's just bound to Laravel core. User can't typehint their code to just allow a certain model's properties. But on the other hand custom rules might give us more flexibility in some cases.

I'm open to disccusion about the issues. What you think?

@canvural
I'd like to add that using a Type also has the benefit of it being easier to check values that are stored in a variable. E.g.
$key = 'name';
$arr = [$key => 'Daan'];
User::create($arr);

In addition, Rules require a lot of logic to register them, in contrast to the declarative approach of using a Type in PHPDoc.
Maybe we can find another way to customize the error message that is printed.

Perhaps we could write a custom error formatter to transform the error in something that's easier to understand.
In the end, the error message is generated by a PHPStan rule. Maybe we could override the rule itself to change the error message.
Or maybe we can change something in PHPStan's codebase that would make it easier to override the text of a type mismatch error or just an error from a rule in general.

All of those solutions sound a lot like cheating or abusing the PHPStan 😀
I believe it's the CallMethodsRule in PHPStan that gives this error. Maybe we can do something to satisy this rule. But then write our own rule that is similar to that one, but outputs the correct error message.
But then writing a single rule instead of a new type feels more simpler. Less code compared to the new type approach.

All of those solutions sound a lot like cheating or abusing the PHPStan

True, it's not neat.

But then writing a single rule instead of a new type feels more simpler.

This will probably not just be a single rule when you want to apply this to several methods (e.g. where, whereColumn, create )  both in a static and non-static context right?
I could see the logic becoming really complex in the Rule because for each method you'd have to precisely define what is allowed. E.g.
whereColumn($first, $operator = null, $second = null, $boolean = 'and')

Accepts something like:
/**
 * @param model-property<TModel>|array<model-property<TModel>|int, model-property<TModel>|array{model-property<TModel>, string, ?model-property<TModel>}> $first
 * @param string|null $operator
 * @param model-property<TModel>|null $second
 * @param string|null $boolean
 */

Which would require quite a bit of code in a Rule, right?
But then again, when using a Type the error message would be even worse:
Parameter #1 $first of method Builder::whereColumn() expects array<int|model-property<App\\User>, array(model-property<App\\User>, string, model-property<App\\User>|null)|model-property<App\\User>>|model-property<App\\User>, 'test' given.

I do see the benefit that a Type allows you to easily specify in a declarative manner what a method should accept as its arguments. However, a Type alone is not enough to completely validate the correctness of the arguments. For example, you will still need a Rule if you want to specify that no other arguments should be passed to the Builder::where method if its first argument is of type array.
I'm not really sure what the best way is to go. If you feel like the Rule is the better way to go, then I understand and will close this PR.

I think we can make it work with a hybrid approach. Having a new type that will allow us to use it wherever needed, and the actual validation of model property will happen in a rule. I will try to change my POC from before to do that. Do you mind if I take some code from this PR? :)

@canvural
Sounds good.

Do you mind if I take some code from this PR?

Sure, no problem. 😄

@Daanra Do we need ModelPropertyType ? I think we just need the generic type with the model. Just a model-property would not make sense.

@canvural
Correct. I treated a regular ModelPropertyType just as a string. But it can be removed because without a generic type it doesn't add any benefit to be honest.


Support non-lvalue pointers in CloudIoTCoreMqtt constructor

The CloudIoTCoreMqtt constructor has three reference to pointer arguments:
CloudIoTCoreMqtt::CloudIoTCoreMqtt(
    MQTTClient *&_mqttClient, Client *&_netClient, CloudIoTCoreDevice *&_device){
  this->mqttClient = _mqttClient;
  this->netClient = _netClient;
  this->device = _device;
}

What's the rationale for declaring the arguments as references? This makes it impossible to pass non-lvalue pointers to the constructor.
What I would like to do in principle is to create a wrapper class like this:
class Wrapper {
private:
  CloudIoTCoreDevice device;
  CloudIoTCoreMqtt mqtt;
  MQTTClient mqttClient;
  WiFiClientSecure netClient;

public:
   Wrapper() : mqttClient(512),
    mqtt(&mqttClient, &netClient, &device) {}
}

But this is not possible because of the references.

It's been a while since I wrote the code encapsulating the MQTT clients. I am open to removing the reference arguments, I may have at one point been passing references to objects that were to be created by the client.

I don't see any benefit in the reference arguments. With the wrapper class that I outlined above I want to avoid unnecessary dynamic allocations. Removing the reference from the argument should be compatible with all existing code.

@smuehlst ack. Makes sense, happy to make the change in the next update. If you'd be interested in reviewing, let me know.

I think I made the request so far , this was to have control on the client on sketch side

@gguuss Thank you for accepting the proposal. I'll happy to review the change.

@Gior80 Sorry, it is not clear to me what you mean. Are you in favor or against the proposal?

hi @smuehlst I better explain. Actually in my sketch I initiate the connection outside the class as I need to verify connection status from main sketch (and manage reconnection), to use wifimanager to setup wifi and to use client for another library. I think this is useful . A solution btw could be to use both init method

PR is here

Fixed!


Allow to customize logger used for file reloader

[x] I was not able to find an open or closed issue matching what I'm seeing.
[x] This is not a question. (Questions should be asked on chat (Signup here) or our forums.)

I was recently digging into the code and discovered the hot code reloading feature.
I started to play with it and saw the Reloader was getting a logger injected, but I wasn't seeing the messages printed, until I realized it was printing them in a different place because I have a LoggerInterface service.
I was thinking that maybe it makes sense to provide something like what was implemented here, but for the Reloader.
In fact, what I was expecting at first was the Reloader to share the same logger defined for the swoole server, but from a config point of view, maybe that's confusing. What do you think?
Anyway, regardless the approach, I can provide a PR if you think this makes sense.

what I was expecting at first was the Reloader to share the same logger defined for the swoole server

I agree that this is a reasonable expectation!
Looking forward to the PR; please ping me when it is ready.

I have just provided the PR with a few comments there. I'll wait to hear from you.

Release with 2.4.0.


[Accelerator-4] Adding realtime notification implementation

Adding real time event notification

This PR adds Realtime Event Notification Implementation

Issue link: https://github.com/wso2-enterprise/solutions-bfsi/issues/20
Doc Issue: Optional, link issue from documentation repository
Applicable Labels: Spec, product, version, type (specify requested labels)

Development Checklist

[x] Build complete solution with pull request in place.
[x] Ran checkstyle plugin with pull request in place.
[x] Ran Findbugs plugin with pull request in place.
[x] Ran FindSecurityBugs plugin and verified report.
[x] Formatted code according to WSO2 code style.
[x] Have you verified the PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?
[ ] Migration scripts written (if applicable).
[x] Have you followed secure coding standards in WSO2 Secure Engineering Guidelines?

Testing Checklist

[ ] Written unit tests.
[ ] Verified tests in multiple database environments (if applicable).
[ ] Tested with BI enabled  (if applicable).

Adding this again because https://github.com/wso2/financial-services-accelerator/pull/193 has an issue with CLA.


Add linting step to CI

Codecov Report

Merging #11 into master will increase coverage by 1.11%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   82.22%   83.33%   +1.11%
==========================================
  Files           3        3
  Lines          45       48       +3
==========================================
+ Hits           37       40       +3
  Misses          8        8

Impacted Files
Coverage Δ

structoscope/__init__.py
100.00% <ø> (ø)

structoscope/lib.py
68.00% <80.00%> (+4.36%)
:arrow_up:

tests/test_lib.py
100.00% <100.00%> (ø)

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 8a707de...e2c48d1. Read the comment docs.


feat: EDA on pipeline Tables

Summary of Changes

MVP of EDA analysis through the VS Code extension
Working

Table viewing of pipeline extracted data
Column reodering
Column resizing
Window resizing with table adapting
Selecting Columns
Selecting Rows
Column header context menu to select, and unselect columns
Sidebar content: Table name and Row count
Sidebar resizing and table realigning
Profiling drop down with just sample text
Id/Row number column
Displaying of large data through dynamically loaded rows
Loading indications and proper presentation as a window of VS Code
Multiple exploration windows at same time and reordering them in vscode
returning to a running exploration if selecting same placeholder again

To start

Have a pipeline with an imported table, like having this stub in directory:

class Table {
    @Impure(
        [
            ImpurityReason.Other
        ]
    )
    static fun from_csv_file(name: String) -> table: Table
}

@Impure(
    [
        ImpurityReason.Other
    ]
)
@PythonCall("from safeds.data.tabular.containers import Table")
fun __import_Table()

and then this pipeline, while having the relevant CSVs stored in proper locations (can get from Kaggle, change paths accordingly):

pipeline mainpipeline {
    __import_Table();
    val i = 0;
    val i2 = i + i + 3;
    val i3 = "abc";
    val i4 = true;
    val i5 = -1.2491891891;
    val Titanic23 = Table.from_csv_file("/home/jonas/titanic.csv"); // pfad
    val Cerea25l = Table.from_csv_file("/home/jonas/cereal.csv"); // pfad
    val Netflix23 = Table.from_csv_file("/home/jonas/netflix_titles.csv"); // pfad
    val Tweets123 = Table.from_csv_file("/home/jonas/tweets.csv"); // pfad
}

Right click on table variable and select "Explore Table"
If the selected placeholder was valid the table will show in a new window after loading

Other way:

Press "ctrl + shift + p" (for vscode commands) and start the EDA command, the one from right click that works if your cursor is in right position is "EDA: Explore Table"

@lars-reimann it appears there is an issue with some CSS not being kebab-case in my vscode.css file, like --vscode-editor-groupHeaderBackground, but these are the CSS variables set by vscode that I am here getting, for using them as my default styles. That means I can hardly just go and rename them.

After scrolling, the border color changes unexpectedly:
I think this issue has to do with dark mode being enabled and thus could be fixed in a future PR.
The performance of the implementation is great, and the view feels really responsive!

Also fixed now by installing dark theme and testing around!

@lars-reimann it appears there is an issue with some CSS not being kebab-case in my vscode.css file, like --vscode-editor-groupHeaderBackground, but these are the CSS variables set by vscode that I am here getting, for using them as my default styles. That means I can hardly just go and rename them.

You can turn off that rule in https://github.com/Safe-DS/DSL/blob/main/.github/linters/.stylelintrc.json.

@lars-reimann am not able to successfully merge main into eda. When I do all the syntax highlighting and sds specific things for sds files is not working. Process was: merge into eda, accept all or most conflicts of package.json from main branch, run npm i, run npm run langium:generate

Can you push the version of the branch with main merged into it?

Don't bother with the linter issue, this was fixed for prettier v3.2.5.

Don't bother with the linter issue, this was fixed for prettier v3.2.5.

I see, was very confused.
Everything seems to be working for me now after merging main back into eda. Feel free to take a look and review again.

I see, was very confused. Everything seems to be working for me now after merging main back into eda. Feel free to take a look and review again.

Great, thanks.

@SmiteDeluxe ESLint and Prettier should now also work for svelte files. Kindly check whether the functionality of the application is unaffected by my changes and fix the two remaining ESLint errors (the marked code looks a buggy). Then this is good to go.

@SmiteDeluxe ESLint and Prettier should now also work for svelte files. Kindly check whether the functionality of the application is unaffected by my changes and fix the two remaining ESLint errors (the marked code looks buggy). Then this is good to go.

/github/workspace/packages/safe-ds-eda/src/components/TableView.svelte
21:13  error  'minTableWidth' is already declared in the upper scope on line 14 column 9  @typescript-eslint/no-shadow
30:13  error  'minTableWidth' is assigned a value but never used                          @typescript-eslint/no-unused-vars

Have fixed now. But now I seem to run into the issue again where the extension is not started properly on launch. There is no sds specific highlighting (as seen in screenshot) and under settings there is also no Safe-DS extension settings. This was caused for me by this commit/merge: https://github.com/Safe-DS/DSL/commit/703e27bdbc18616a108c730141cecffc57498ecc
I don't know by what specifically though. Let me know if it's the same for you. I just checked out the commit, ran "npm i" and then "npm run langium:generate"

Try updating your VS Code to version 1.86.0. Once we have a stable release, we won't continually upgrade the minimum VS Code engine anymore.

Try updating your VS Code to version 1.86.0. Once we have a stable release, we won't continually upgrade the minimum VS Code engine anymore.

That worked and makes a lot of sense. We are good to merge then.


How to open GIMP's dialog windows in floating mode?

I would like to have the main window inside the tiled layout and all remaining dialog windows in floating mode. The app name us GIMP-<version> and the main window's title is <filename> (<options>) <dimensions> – GIMP.
I first tried to use a negative lookahead. However, I found that yabai does not support negative lookaheads.
yabai -m rule --add app='^GIMP' title='(?!GIMP)$' manage=off

I then to use the negative syntax explained in this issue. However, this gives an unknown key 'title[!]' error in yabai v3.3.0.
yabai -m rule --add app='^GIMP' 'title[!]="GIMP$"' manage=off

How can I write a rule that disables the tiling window management for GIMP windows except for the main window?

[] means optional, so you should use title=xxx or title!=xxx.

As yanzhang mentioned, yabai -m rule --add app='^GIMP' 'title!="GIMP$"' manage=off should do it.

Perfect, thanks! I had to catch one more special case where the main window title would be different when no image is loaded. The complete rule is:
yabai -m rule --add app='^GIMP' title!='(^GNU|GIMP$)' manage=off

thank you, this was very helpful

I needed a $ at the end of the app name:
yabai -m rule --add app='^GIMP$' title!='(^GNU|GIMP$)' manage=off


DependencyResolutionException when running upgrade-assistant extensions

Describe the bug
Running command upgrade-assistant extensions immediately crashes with a stack trace.
To Reproduce
PM> upgrade-assistant extensions
-----------------------------------------------------------------------------------------------------------------
Microsoft .NET Upgrade Assistant v0.4.346202+66a923ad8212e008d71c1c232bed728c4c7982c1

We are interested in your feedback! Please use the following link to open a survey: https://aka.ms/DotNetUASurvey
-----------------------------------------------------------------------------------------------------------------

[12:32:31 INF] Loaded 9 extensions
[12:32:35 INF] Using MSBuild from C:\Program Files\dotnet\sdk\6.0.402\
[12:32:35 INF] Using Visual Studio install from C:\Program Files\Microsoft Visual Studio\2022\Community [v17]
[12:32:36 ERR] Unexpected error
Autofac.Core.DependencyResolutionException: An exception was thrown while activating Microsoft.DotNet.UpgradeAssistant.Cli.ConsoleAnalyze -> Microsoft.DotNet.UpgradeAssistant.Cli.FileUpgradeStateFactory.
 ---> Autofac.Core.DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(Microsoft.Extensions.Options.IOptions`1[Microsoft.DotNet.UpgradeAssistant.Cli.FileStateOptions], Microsoft.Extensions.Logging.ILogger`1[Microsoft.DotNet.UpgradeAssistant.Cli.FileUpgradeStateFactory])' on type 'FileUpgradeStateFactory'.
 ---> Microsoft.Extensions.Options.OptionsValidationException: DataAnnotation validation failed for members: 'Path' with the error: 'The Path field is required.'.
   at Microsoft.Extensions.Options.OptionsFactory`1.Create(String name)
   at Microsoft.Extensions.Options.UnnamedOptionsManager`1.get_Value()
   at Microsoft.DotNet.UpgradeAssistant.Cli.FileUpgradeStateFactory..ctor(IOptions`1 options, ILogger`1 logger) in /_/src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/FileUpgradeStateFactory.cs:line 31
   at lambda_method55(Closure , Object[] )
   at Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate()
   --- End of inner exception stack trace ---
   at Autofac.Core.Activators.Reflection.BoundConstructor.Instantiate()
   at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Activators.Reflection.ReflectionActivator.<ConfigurePipeline>b__11_0(ResolveRequestContext ctxt, Action`1 next)
   at Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   --- End of inner exception stack trace ---
   at Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Pipeline.ResolvePipeline.Invoke(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Middleware.RegistrationPipelineInvokeMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Middleware.SharingMiddleware.<>c__DisplayClass5_0.<Execute>b__0()
   at Autofac.Core.Lifetime.LifetimeScope.CreateSharedInstance(Guid id, Func`1 creator)
   at Autofac.Core.Lifetime.LifetimeScope.CreateSharedInstance(Guid primaryId, Nullable`1 qualifyingId, Func`1 creator)
   at Autofac.Core.Resolving.Middleware.SharingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.Middleware.CircularDependencyDetectorMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   at Autofac.Core.Pipeline.ResolvePipeline.Invoke(ResolveRequestContext ctxt)
   at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, ResolveRequest request)
   at Autofac.Core.Resolving.ResolveOperation.ExecuteOperation(ResolveRequest request)
   at Autofac.Core.Resolving.ResolveOperation.Execute(ResolveRequest request)
   at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(ResolveRequest request)
   at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
   at Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable`1 parameters)
   at Autofac.ResolutionExtensions.Resolve(IComponentContext context, Type serviceType, IEnumerable`1 parameters)
   at Autofac.ResolutionExtensions.Resolve[TService](IComponentContext context, IEnumerable`1 parameters)
   at Autofac.ResolutionExtensions.Resolve[TService](IComponentContext context)
   at Microsoft.DotNet.UpgradeAssistant.Cli.ConsoleRunner.StartAsync(CancellationToken token) in /_/src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/ConsoleRunner.cs:line 60

Sorry I can't share project files for commercial reasons. I'm happy to answer questions though.
Further technical details
Edition	Windows 10 Home
Version	21H1
Installed on	05/01/2022
OS build	19043.2130
Experience	Windows Feature Experience Pack 120.2212.4180.0

PM> dotnet --list-sdks
6.0.202 [C:\Program Files\dotnet\sdk]
6.0.203 [C:\Program Files\dotnet\sdk]
6.0.300 [C:\Program Files\dotnet\sdk]
6.0.305 [C:\Program Files\dotnet\sdk]
6.0.402 [C:\Program Files\dotnet\sdk]

PM> upgrade-assistant --version
0.4.346202+66a923ad8212e008d71c1c232bed728c4c7982c1

upgrade-assistant.clef.txt

Same issue here.


[SPARK-49361] Fix Dockerfile by removing unused ARG from builder and moving default value

What changes were proposed in this pull request?
This PR aims to fix Dockerfile by removing unused ARG from builder and moving default value.
Why are the changes needed?
To publish snapshot image correctly.

https://github.com/apache/spark-kubernetes-operator/actions/workflows/publish_snapshot_dockerhub.yml

Does this PR introduce any user-facing change?
No. This is not released yet.
How was this patch tested?
In build.gradle, we always use --build-arg.
https://github.com/apache/spark-kubernetes-operator/blob/5bdb8394e9383836d712cfb94364f742df01b1e8/build.gradle#L41
For testing, we need to test manually without --build-arg.
$ docker build -t spark-kubernetes-operator:main-snapshot -f build-tools/docker/Dockerfile  .

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

Could you review this PR, @viirya ?

Thank you, @viirya . Merged to main.


fix: Add Missing Release Script

Looks like the scripts/uploadToS3.js script is required in the
production image so that downstream scripts can copy the client assets
to s3.

The error on the test build is Cannot find module 's3', this suggests to me that we are missing a package from package.json rather than the script itself.


try and fix the lazy loading

try fix the lazy loading thing by adding another useeffect

still breaks on large screen because the observer doesn't get retriggered if it stays in view


IsReleaseBuild() returns incorrect info.

TL;DR
Ideally,  IsReleaseBuild returns true if this binary was built by goreleaser as part of
// the official release process (as opposed to a user just running "go build",
// or running in a CI environment, or something else). But somehow when I install abc cli via go install ./..., or https://github.com/abcxyz/abc/blob/23068d1417191358257a9663cc3bf10dffcffe1b/cmd/abc/abc_test.go#L66, IsReleaseBuild also returns true
Expected behavior
No response
Observed behavior
No response
Environment Details
N/A

Additional information
No response

I took a look at our v0.5.0 and go install ./... and https://github.com/abcxyz/abc/blob/23068d1417191358257a9663cc3bf10dffcffe1b/cmd/abc/abc_test.go#L66, the version is all devel and it is expected.  See https://github.com/golang/go/issues/29228. I think probably we need to change our mechanism to hide some api versions.

I took a look at our v0.5.0 and go install ./... and
https://github.com/abcxyz/abc/blob/23068d1417191358257a9663cc3bf10dffcffe1b/cmd/abc/abc_test.go#L66
, the version is all devel and it is expected. See golang/go#29228. I think probably we need to change our mechanism to hide some api versions.

https://github.com/abcxyz/abc/pull/439 probabbly fixed the bug that when we release abc cli, the version we saw is still devel

I took a look at our v0.5.0 and go install ./... and
https://github.com/abcxyz/abc/blob/23068d1417191358257a9663cc3bf10dffcffe1b/cmd/abc/abc_test.go#L66
, the version is all devel and it is expected. See golang/go#29228. I think probably we need to change our mechanism to hide some api versions.
I checked the v0.5.0 via go version -m xxx command (Edit: when I run abc templates -help on abc cli v0.5.0, it shows correct info, the mechanism is that the version of build info of v0.5.0 is devel but the abc templates -help shows the version according to the override version in goreleaser.

when I run abc templates -help on abc cli v0.5.0, it shows correct info, the mechanism is that the version of build info of v0.5.0 is devel but the abc templates -help  shows the version according to the override version in goreleaser.  https://github.com/abcxyz/abc/pull/439 made it more clear regarding how the override works.

I took a look at our v0.5.0 and go install ./... and
https://github.com/abcxyz/abc/blob/23068d1417191358257a9663cc3bf10dffcffe1b/cmd/abc/abc_test.go#L66
, the version is all devel and it is expected. See golang/go#29228. I think probably we need to change our mechanism to hide some api versions.
I checked the v0.5.0 via go version -m xxx command (Edit: when I run abc templates -help on abc cli v0.5.0, it shows correct info, the mechanism is that the version of build info of v0.5.0 is devel but the abc templates -help shows the version according to the override version in goreleaser.

For v0.5.0, the version is different if we are using different approaches to install it, see https://github.com/abcxyz/abc/issues/441


Cannot validate challenges - using DNS01

Not exactly sure what the issue is here.  I went to renew an expired certificate and cannot.  I updated to the latest jar.  I cleared the workdir and digests folder.  Order certificates runs fine.  I copied the values for each challenge to the TXT records ( I use GoDaddy).
I used LetsDebug,net to validate the challenge (at least I think that is what it does).  It says that all is OK.  So, what am I missing?  This has been working fine although it has been a while since I renewed the certificate.  Still looking for a solution.  Ideas?
2019-12-29 15:45:05 WARN  com.jblur.acme_client.command.certificate.VerifyDomainsCommand:74 - Cannot validate one of challenges for domain: *.ossgarden.org org.shredzone.acme4j.exception.AcmeException: Challenge invalid: https://acme-v02.api.letsencrypt.org/acme/chall-v3/1999273187/rBdjGA 	at com.jblur.acme_client.manager.ChallengeManager$1.failIfInvalid(ChallengeManager.java:81) 	at com.jblur.acme_client.manager.ValidationService.validate(ValidationService.java:59) 	at com.jblur.acme_client.manager.ValidationService.validate(ValidationService.java:21) 	at com.jblur.acme_client.manager.ChallengeManager.validateChallenge(ChallengeManager.java:57) 	at com.jblur.acme_client.command.certificate.VerifyDomainsCommand.commandExecution(VerifyDomainsCommand.java:72) 	at com.jblur.acme_client.command.ACMECommand.execute(ACMECommand.java:47) 	at com.jblur.acme_client.CommandExecutor.executeACMECommand(CommandExecutor.java:123) 	at com.jblur.acme_client.CommandExecutor.execute(CommandExecutor.java:74) 	at com.jblur.acme_client.Application.main(Application.java:65) 2019-12-29 15:45:10 WARN  com.jblur.acme_client.command.certificate.VerifyDomainsCommand:74 - Cannot validate one of challenges for domain: ossgarden.org org.shredzone.acme4j.exception.AcmeException: Challenge invalid: https://acme-v02.api.letsencrypt.org/acme/chall-v3/1999273188/4hndhw 	at com.jblur.acme_client.manager.ChallengeManager$1.failIfInvalid(ChallengeManager.java:81) 	at com.jblur.acme_client.manager.ValidationService.validate(ValidationService.java:59) 	at com.jblur.acme_client.manager.ValidationService.validate(ValidationService.java:21) 	at com.jblur.acme_client.manager.ChallengeManager.validateChallenge(ChallengeManager.java:57) 	at com.jblur.acme_client.command.certificate.VerifyDomainsCommand.commandExecution(VerifyDomainsCommand.java:72) 	at com.jblur.acme_client.command.ACMECommand.execute(ACMECommand.java:47) 	at com.jblur.acme_client.CommandExecutor.executeACMECommand(CommandExecutor.java:123) 	at com.jblur.acme_client.CommandExecutor.execute(CommandExecutor.java:74) 	at com.jblur.acme_client.Application.main(Application.java:65) 2019-12-29 15:45:10 ERROR com.jblur.acme_client.command.certificate.VerifyDomainsCommand:100 - Domain *.ossgarden.org is not verified. Please, check warnings. 2019-12-29 15:45:10 ERROR com.jblur.acme_client.command.certificate.VerifyDomainsCommand:100 - Domain ossgarden.org is not verified. Please, check warnings.

OK..Self-inflicted.  I have two domain combinations for ossgarden a .org and a .com  I was updating the digest in the .com DNS record so naturally, it didn't match what was generated.
Sorry for the noise.


feat(reload test environment): implement test environment reload

Add the ability for Stryker to restart a test runner in order to reload its test environment. This is used to test static mutants where the test runner is incapable of reloading the test environment by itself. This is a requirement to support es modules (ESM) since it is impossible to reload an ESM using something like delete require.cache['...']. Instead, Stryker will restart the entire test runner process for those mutants.
The way for the test runner to communicate to Stryker whether it is capable of reloading the environment is by implementing the new capabilities() method.
capabilities() {
  return { reloadEnvironment: true }
}

If you do this, you can expect the new reloadEnvironment boolean in your MutantRunOptions to be true when you need to reload the test environment after activating the mutant.
See #2413 and #2922
I also moved some code around (from the MutationTestProcess to a new class MutantTestPlanner).
BREAKING CHANGE: Test runner plugins must provide TestRunnerCapabilities by implementing the capabilities method.

@simondel do you think it is OK to make capabilities() required?

This change also contains a breaking change for the reporter API:
- export type MutantTestCoverage = Mutant &
-  Pick<schema.MutantResult, 'coveredBy' | 'static'> & {
-    estimatedNetTime: number;
-    hitCount?: number;
-    testFilter: string[] | undefined;
-  };
+ export type MutantTestCoverage = Mutant & Pick<schema.MutantResult, 'coveredBy' | 'static'>;

I've removed estimatedNetTime, hitCount, and testFilter. They weren't used by our reporters and they were only there to pass along state internally in core, between the find-mutant-test-coverage and mutation-test-executor. I found this very obfuscated and it frustrated me.
That's why I now choose to do all the work in the new MutantTestPlanner class. It is responsible for planning which mutant should be run with which options and which should be reported as an early result.
We can in a later PR replace the onAllMutantsMatchedWithTests with a new onMutantPlanDetermined, which can include the run options per test. That way we can improve the progess reporter. Instead of counting the same progress per mutant, it can count mutants that require a test env reload 3 times for example.


Download keyword is not working as expected

Please check the following issue. Just as a reproducible example, when I try to directly download a file with the given url, the keyword does not seem to be consistent or maybe also it is not clear how to use it:

If New Page does not have an url, the Download keyword fails with "Error: page.evaluate: Evaluation failed: TypeError: Failed to fetch"

    New Browser    headless=${FALSE}
    New Context    acceptDownloads=${TRUE}
    New Page

    ${res}  Download  https://www.gutenberg.org/ebooks/135.epub.noimages?session_id=5ae7d248d2d09dff3ebd65f8914dccd32b8ad9cd

If New Page does have as url the root url of the file to be downloaded, then the download succeeds but the returned suggestedFilename is wrong:

"${res} = {'saveAs': '...1ba1bf58-228b-4691-b788-3e29ee1625ad', 'suggestedFilename': 'https___www.gutenberg.org_ebooks_135.epub.noimages_session_id=5ae7d248d2d09dff3ebd65..."
    New Browser    headless=${FALSE}
    New Context    acceptDownloads=${TRUE}
    New Page  https://www.gutenberg.org

    ${res}  Download  https://www.gutenberg.org/ebooks/135.epub.noimages?session_id=5ae7d248d2d09dff3ebd65f8914dccd32b8ad9cd

Related also to #620 and #642

Download should also check acceptDownloads

I did try this one and there is an error, in PL logs I see
(node:6059) UnhandledPromiseRejectionWarning: Error: server must be bound in order to start
    at Server.start (/home/tatu/workspace/robotframework-playwright/Browser/wrapper/index.js:16666:19)
    at /home/tatu/workspace/robotframework-playwright/Browser/wrapper/index.js:67798:12
    at bindResultPromise.then.errorString (/home/tatu/workspace/robotframework-playwright/Browser/wrapper/index.js:16608:25)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:6059) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:6059) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I can think we have bug, but I lies on node side and I have leave it for someone else.

We did have discussion and how the keywords is correct. When using Download keyword, there must always page loaded. But we should document this feature.


Refactor and test legend code; show barplot legends

Closes #299 and closes #331. (Also counts as progress towards #142, since now legend.js is tested.) Also updates the barplots section of the README accordingly.
This PR adds a pretty large amount of documentation / tests, both to new and previously-existing code.

Various notes

This fixes a weird bug where it was possible for barplot layers' HTML elements' IDs to collide in certain circumstances. See this comment for an explanation.
The CSS changed a decent amount in this PR, but not that much -- the main reason the CSS file has a lot of diffs is I went ahead and added it to the collection of files run through prettier (so now it should be consistently styled).
For now, gradients match Emperor in that they go from high -> low. It would be nice to flip these around if/when https://github.com/biocore/emperor/issues/782 is addressed. (For now, I assume consistency is important. also i don't know enough SVG to do this myself right now lol)

The following artifacts were built for this PR: empire-biplot.qzv, empire.qzv, empress-tree.qzv


Add priority attribute to token superclass

The token superclass lacks the attribute priority which will be used by the shunting yard algoritm. numbers have a -1 value while operators have their values assigned based on their priority in the order of operations.

The attribute was added with commit db88857c81aae8c6fc3da2cc24787b9029aa2ccf


Docker image is failing to build

Bug description
After cloning the 3.x branch and running docker-compose up -d (or build) then the following error appears:
failed to solve: rpc error: code = Unknown desc = executor failed running [/bin/sh -c docker-php-ext-configure pgsql -with-pgsql=/usr/local/pgsql     && docker-php-ext-install -j$(nproc) gd pdo pdo_mysql pdo_pgsql pdo_sqlite pgsql zip gmp bcmath pcntl ldap sysvmsg exif     && pecl install redis-5.3.2     && docker-php-ext-enable redis     && pecl install pcov     && docker-php-ext-enable pcov     && echo "pcov.enabled = 1" > /usr/local/etc/php/conf.d/pcov.ini]: exit code: 1
Steps to reproduce
Clone 3.x repo (currently at 3.5.1) and then run docker-compose up -d
Expected behavior
That the docker image builds correctly and then I'd like to be able to run the tests
Laravel version
"illuminate/support": "^6.0|^7.0|^8.0"
stancl/tenancy version
3.5.1

Did you manage to fix this somehow?

No I didn't try much. But I did find something great I even implemented on my projects at work (also because I needed to upgrade to PHP8.1 and Laravel 9) : https://kool.dev
They have a repo of all their php images. I think that could be used here.
And for the db's then the official database images could be used. That would help a lot for the development and testing process. If you're open to the idea I could try making it run with an updated docker-compose.yml file.

I see. I first thought it's related to pcov, but after experimenting it seems like this fixed the issue for me: https://github.com/archtechx/tenancy/commit/5026f54a6d4482226951d3a8196218ea41434db4#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557
So I just changed phpredis 5.3.2 to 5.3.7


Error in prod build

When I make production build, I always get an error:
WARNING in<EMAIL_ADDRESS>134:63-70
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
<EMAIL_ADDRESS>@ ./node_modules/vue/server-renderer/index.mjs
@ ./node_modules/babel-loader/lib??ref--1!./node_modules/vue-loader/dist/templateLoader.js??ref--6!./node_modules/vue-loader/dist??ref--9-0!./src/App.vue?vue&type=template&id=ecf91598
@ ./src/App.vue?vue&type=template&id=ecf91598
@ ./src/App.vue
@ ./src/entry-server.js
Any ideas how to solve this?

You might try updating the dependencies.

It didn't help (I tried in cloned non modified project)
I found that the error appears only with target: "node" in ssr webpack config

I am sorry I don't have a capacity to help you with this issue since the reason is completely unclear to me. Please post a solution here in case you're able to resolve that yourself.


4090 support

Will this ever get 4090 support?

Sadly not yet supporting. GTX 1XXX and RTX 2XXX series supports

my 6x RTX 4090 AI workstation is desperately waiting for it

do you have deals by any chance ?

I think support is unlikely... Starting from Ampere (RTX30xx) vGPU implementation has become SR-IOV based instead time slicing. SR-IOV support should be enabled in GPU firmware for that to function properly (which is not for consumer grade GPUs). GPU firmware is signed nowadays making flashing modded firmware very hard.

Has anyone investigated options which Nvidia supports nowadays for those newer cards? Based on https://nvidia.custhelp.com/app/answers/detail/a_id/5173/~/geforce-gpu-passthrough-for-windows-virtual-machine-(beta) at least scenario where host system is Linux and guest Windows should be supported but is it also possible to have Windows+Hyper-V as host and Linux as guest?
Of course there is that single VM limitation so it is not solution for everyone.

Monday, August 21st 2023
NVIDIA BIOS Signature Lock Broken, vBIOS Modding and Crossflash Enabled by Groundbreaking New Tools. There is still hope i guess

Monday, August 21st 2023 NVIDIA BIOS Signature Lock Broken, vBIOS Modding and Crossflash Enabled by Groundbreaking New Tools. There is still hope i guess

yea, maybe a little hope is still present. Would be great to hear a feedback from the devs

Any updates on whether support for this is possible or not?

is any progress for Ampere architectures?


wrap geneNameSearch with generator

Codecov Report

Merging #19 into authz will increase coverage by 0.01%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##            authz      #19      +/-   ##
==========================================
+ Coverage   81.32%   81.34%   +0.01%
==========================================
  Files          36       36
  Lines       12390    12387       -3
  Branches     1305     1304       -1
==========================================
  Hits        10076    10076
+ Misses       1914     1911       -3
  Partials      400      400

Impacted Files
Coverage Δ

ga4gh/server/backend.py
62.48% <14.28%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


Canonical URL %CurrentUrl% breaks when custom URL provider is used

Hi Patrick,
Using a custom URL provider and '%CurrentUrl%' in the Canonical URL is throwing an exception. There are two symptons:

It breaks the SEO tab on affected nodes
Using the <meta-fields></meta-fields> tag breaks the front end

The exception I'm getting is below. I've tested this on two separate Umbraco 11 projects and it happens on both. I've not tested it on Umbraco 10.
I can get around it for now by leaving the Canonical URL empty, or by hard coding a different value. It's not a deal breaker but would be awesome to get a fix.
System.UriFormatException: Invalid URI: The format of the URI could not be determined.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind, UriCreationOptions& creationOptions)
   at System.Uri..ctor(String uriString)
   at SeoToolkit.Umbraco.MetaFields.Core.Common.Converters.SeoValueConverters.TextSeoValueConverter.Convert(Object value, IPublishedContent currentContent, String fieldAlias)
   at SeoToolkit.Umbraco.MetaFields.Core.Providers.DefaultMetaTagsProvider.<>c__DisplayClass12_0.<Get>b__2(ISeoField it)
   at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.ToArray()
   at SeoToolkit.Umbraco.MetaFields.Core.Providers.DefaultMetaTagsProvider.Get(IPublishedContent content, Boolean includeUserValues)
   at SeoToolkit.Umbraco.MetaFields.Core.Services.MetaFieldsService.MetaFieldsService.Get(IPublishedContent content, Boolean includeUserValues)
   at SeoToolkit.Umbraco.MetaFields.Core.Common.TagHelpers.MetaFieldsTagHelper.Process(TagHelperContext context, TagHelperOutput output)
.... lots more````

Hi @philipdanielhayton
Sorry to leave your issue hanging here for two weeks. Are you able to show some of the code that you have in your content finder? Would love to see what sort of URL you are returning from it.

Hi @patrickdemooij9,
Hey no problem brother. I've actually fixed the issue, turns out it was a gap in my understanding of how UrlProviders work. 🤦🏻♂ I thought they only handled relative URLs, but I noticed that sometimes they can be absolute too, so I've added some code to handle both scenarios and it now works as expected 🥳
Sorry if you wasted any time on this.


@segment/analytics-next export AnalyticsBuffered

I want a way to check if current analytics instance is buffered or an initialized / loaded instance. It seems like I need to do something like:
import { AnalyticsBuffered } from '@segment/analytics-next';

// ...

if (analytics instanceof AnalyticsBuffered) {}

However, AnalyticsBuffered is not exported.

We ended up checking for presence of ctx property.


Suggestion: using the eloquent model instead of query builder

Why not create references to your models rather than use config('roles.models.role')::find($roleId);
This enables us to use route model binding which is pretty handy in the controllers.
Route::post('user/{user}/role/{role}','UserController@setRole’);
use jeremykenedy\LaravelRoles\Models\Role as Role;

class UserController extends Controller

{

 public function setRole(User $user, Role $role)

 {

    $user->detachAllRoles();

    $user->detachAllPermissions();

    $user->attachRole($role);

    return Response::success(new RoleResource($user->getRoles()->first()));

 }

}

Flexibility for others to change the model to thier own.


charting state strums

Describe your bug here.
when there are hold notes and i think normal ones too
basically in a duet
the strums of the both sections don't light up correctly
https://user-images.githubusercontent.com/85742902/146037727-11056f1c-546e-4c1e-8861-7bc99d33e2d8.mp4
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
nothin

Why is this important tho? The game just doesn't know what data the sustain is, it isn't a note.

what about playstate?
this does not happen there

oh
ik what is doing that
its the hitsounds
when enabled they do the funny bug

https://user-images.githubusercontent.com/85742902/146041403-679e8f85-aeec-41c1-aed2-95b58f5ef463.mp4

I'll check it out l8r. thxx

I'll check it out l8r. thxx

👍

Update to 0.5

but it is

downloaded build

yay it got fixed


jpeg/gif image support

the rest of #109
this PR allows showing jpeg/gif images, but the animated gif is not supported.

Awesome, thanks @zigen!
I'm reading over the code here and thinking we can probably simplify some of this if we use juce's URL class: https://docs.juce.com/master/classURL.html. We can take that string from the source prop, construct a URL, check if it's valid, then branch our behavior based on getScheme(). Where scheme == data, we can split out the mime type and branch thereupon as well. This for example opens the door to using the getLocalFile() method (https://docs.juce.com/master/classURL.html#a2aa2e8a4033cf040c4c6273dbf3f6cdc) as well for supporting the file:// scheme quite easily. What do you think?

@nick-thompson thank you for reviewing!
using juce::URL class seems absolutely better than my implementation.
let me rebase and fix it!

I tried to use juce::URL to get the scheme from the given source property, but I couldn't to get the scheme because juce:URL.getScheme returns empty string for data url.
juce::URL.getScheme calls findEndOfScheme method. this method checks the index of ://, but data url's format is like this data:[mimeType],<data>, so data url doesn't contain ://.
https://github.com/juce-framework/JUCE/blob/master/modules/juce_core/network/juce_URL.cpp#L264
https://github.com/juce-framework/JUCE/blob/master/modules/juce_core/network/juce_URL.cpp#L360
finally juce:URL class cannot used for parsing data url (e.g. "data:image/png;base64,iVBORw0KG...)
so current my implementation seems fine and I just only rebased.

@zigen, @nick-thompson , I need to add png support with the file:// scheme for my project pretty soon. I was going to take a crack at this first thing tomorrow but want to check if you're planning on adding file:// support as part of this merge @zigen ? If not I'll take a stab at it tomorrow.
@nick-thompson given juce::URL doesn't support data URLs is this good to be merged so that I can continue on top and  support loading from the file system? Happy to look at fetching images over network as well but file support is the thing I need imminently.

@JoshMarler I'm not planning to support file:// scheme on this PR.
@nick-thompson could you review this again?

@zigen, OK thanks! I'll take a look at it in that case. Will hold out till this afternoon to see if Nick is going to merge this change down.


drivers: display: gc9x01x: fix correct mipi buffer size in gc9x01x_write

when the given buffer width is smaller than the display width the mipi buffer size was set incorrectly
fixes: https://github.com/zephyrproject-rtos/zephyr/issues/81572

commit message did not comply with zephyr standards, I will close the pull request and open a new one with a proper commit message

@Casales you can amend commits via git commit --amend changing your message. No need for a new PR


Minor grammar fix

@anwather : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.