python2: backport fix for pyc race condition, part 2

Motivation for this change
Turns out fixing this only in importlib is not sufficient and we
need to backport CPython part of the fix too.
This patch is based on https://hg.python.org/cpython/rev/c16063765d3a
but because the code around is different there are some changes (C-strings
instead of Python objects etc.)
With this patch Tensorflow builds successfully on many-core machine.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I'd appreciate review of the patch given that I basically rewrote it.

I should also mention https://github.com/NixOS/nixpkgs/pull/64067 where the first part was introduced, but contrary to it this one isn't backported by any upstream distributions, reason unknown.

I'd appreciate review of the patch given that I basically rewrote it.

I can't give a comprehensive review due to a lack of time and I'm far from a C-developer myself anyway. But out of interest, why didn't you use my patch at https://github.com/NixOS/nixpkgs/pull/63616/files#diff-7af205fc79201d40af30ad4983bcc777?

Huh, I guess I... missed it? I'll compare them, thanks!

Well I did tell you that I pushed it, but its easy to miss :woman_shrugging:
Anyway, we definitely have to be a little more careful here than with https://github.com/NixOS/nixpkgs/pull/64067, since its's C, malloc/free is involved and there is no other-distro precedent.

Could we apply this patch only when building tensorflow?

@FRidh We could do that but it's a bug nevertheless, I feel it could show up in other massively parallel builds too. If there are any we'll have until the EOL that is ;)

I minimized the patch, also bringing it as close to the spirit of original patch as possible. Hopefully this helps with the review.

@FRIdh Thinking more about it, could be problematic because Tensorflow will then link to its custom Python 2 library and then we'll have a conflicting Python library loaded into our usual interpreter.

Reading more into the original patch: unless I'm mistaken there is actually a race condition in it too! Namely, in C (but not in Python) file is opened exclusively to prevent concurrent writes but then fclose()d before rename(), so another Python process can open .tmp file in this short period of time and begin writing while the file has already been renamed. This code isn't in final Python 3.4 release AFAICS so I suppose it has been replaced with something else.
Did I overlook something there? The fix is quite easy (move fclose() a bit further down) so I propose to do just that.

Could very well be a bug, probably wouldn't happen much in practice and the exclusive open was added as an afterthought.

Hehe, actually the bug that I described is present in Python right now but in a very light form - because id() is used the chance of this actually happening is pretty slim. Because rename() works differently on POSIX and Windows simply moving rename into with block wouldn't work for Windows here I think, so it's not that simple to fix. I'll report it but don't think it's nearly serious enough to fix it by ourselves given id() is 64-bit address of an object so the chances of a clash actually happening in such conditions are pretty slim.

Patch updated, tested this one through the night running Tensorflow compilations.

could be problematic because Tensorflow will then link to its custom Python 2 library and then we'll have a conflicting Python library loaded into our usual interpreter.

EDIT: Fixable via patchelf though.

Yes, did the same with tkinter. Well, let's just see how it turns out. If we get trouble that may be the way forward.

Checked out tkinter - nice hack! I wonder if something similar could be done for things like Java (headless + GUI libraries as modules of some kind)...


Replace bin/* with proc-flake module

Ref: https://github.com/EmaApps/ema-template/pull/40

See https://github.com/numtide/devshell/issues/238 for alternative approach. Arguably better, because not everything needs a Procfile.

Going with https://github.com/srid/haskell-template/pull/72 instead


Tiles still shown after zooming out of minZoom/maxZoom

This is best explained with a fiddle: http://jsfiddle.net/ryy8abzt/2/
In there, the Toner layer is visible only at zoom levels 17 and 18. When zooming out from 17 to 16, is is still seen.
I don't really care about the visibility of the tile layer during the zoom animation. But (obviously) the layer has to be hidden at some point.
Reproducible on 0.7.x with a variety of browers. Gotta check with 1.0-beta1.Reproducible only on 0.7.x with a variety of browsers.

Wait, I think this might be a duplicate of #3506


rsa/rsa_ossl.c: implement variant of "Smooth CRT-RSA."

In [most common] case of p and q being of same width, it's possible to
replace CRT modulo operations with Montgomery reductions. And those are
even fixed-length Montgomery reductions...
1.0.2 and 1.1.0 labels are speculative in sense that they indicated intention to back-port this [as it won't cherry-pick]...

Red cross from travis was unrelated, it was failure to pull a package.

Ready.

On general note. There are few bn_correct_top-s on the path. Generally speaking probability that top would actually be corrected is rather low. One has to keep in mind that attacks are customarily about gathering statistics. And since we are operating on blinded values that periodically change, question would be if attack can be actually mounted fulfill in that window. There is sensitive point outside blinded operation, and that is unblinding in private_decrypt when it deduces plaintext. Variations are bn_correct_top itself, and then possible variation in BN_bn2pinpad. It would take ability to track access pattern with limb granularity to capture relevant variations. Well, that's what cachebleed was doing (on specific processors), but in that case the window of opportunity was much larger, attacker had hundreds and hundreds of cycles to catch it the act.

Another open question is what happens if |I| argument to rsa_ossl_mod_exp is not fully reduced. In normal case, even more specifically when called from libssl it just can't happen, because value will be reject by caller. Otherwise it would take specially crafted program. Should we care? I mean about specially crafter program failing and resorting to I^d? On side note verify pass could use a cleanup, some time later...

BN_bn2pinpad conceals memory access pattern for corrected tops, so that only possible variations are bn_correct_top themselves. Unlike as they all are, there is only one actually sensitive, at exit from unblinding.

Red cross seems to be unrelated. It's not clear to me what's going on, 1st red cross at https://travis-ci.org/openssl/openssl/branches is for commit that I don't have in this request...

Ping.

P-p-p-i-n-n-n-g-g-g-g-g...

P-i-i-i-i-i-i-i-i-i-i-n-g then?


Correction for raw affiliation LIP6, CNRS, Sorbonne Université, Paris 75005, France

Correction needed for raw affiliation LIP6, CNRS, Sorbonne Université, Paris 75005, France
raw_affiliation_name: LIP6, CNRS, Sorbonne Université, Paris 75005, France
new_rors: 02en5vm52;02feahw73;05krcen59
previous_rors: 02en5vm52;02feahw73
works_examples: W4315568115
contact: e3f2afc127df23a741fe0f79227aeca0:a514225aa5032d992b5ad33182 @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Fix suggested link from the first exercise

Fix suggested link from the first exercise of the 'Transfer Learning with Tensorflow' Colab.
Currently, the suggested link for getting a MobileNet v2 module is redirecting to the general page from where you can see all available modules.
Maybe the first suggested link should be fixed too, as it is not redirecting to only image modules, but to all modules.

I signed it!

Thanks Adina for pointing this out.
I did a change to fix the links in all the document and switch from "alpha.tfhub.dev" to "tfhub.dev". It should go live when the next repo sync is done.


Add Sharc Integration Examples to Chatter

Add Sharc Integration Examples to Chatter

Removed .idea directory and added .idea/ to the gitignore


[SPARK-27649][SS]Unify the way use 'spark.network.timeout'

What changes were proposed in this pull request?
For historical reasons, structured streaming still has some old way of use
spark.network.timeout
, even though
org.apache.spark.internal.config.Network.NETWORK_TIMEOUT
is now available.
How was this patch tested?
Exists UT.

Test build #105212 has started for PR 24545 at commit 77ad2b0.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10496/
Test PASSed.

Test build #105212 has finished for PR 24545 at commit 77ad2b0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105212/
Test PASSed.

cc @cloud-fan @zsxwing @maropu

This is OK. It overlaps with https://github.com/apache/spark/pull/24270

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10522/
Test PASSed.

Test build #105241 has started for PR 24545 at commit 0f1718d.

This is OK. It overlaps with #24270

Thanks for reminding. How should I do?

Test build #105241 has finished for PR 24545 at commit 0f1718d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105241/
Test PASSed.

It's OK, we can rebase that PR

thanks, merging to master!

thanks, merging to master!

Thank you, wenchen.

@cloud-fan @srowen Thanks for your help!


Add support for macOS

This PR adds support for macOS. It uses statically linked GLFW as I didn't want to learn Objective C and Cocoa.

Thanks for submitting this! I will have a look through the code and get back to you.

Nice submission.
If anyone is interested in an alternative that doesn't use GLFW, a few days ago I've been able to come up with a macOS platform layer that makes use of Objective C and Cocoa that is as rudimental as the ones introduced in #004 and #005, I'd gladly share my code if wanted.
I'll need more time to learn how to implement input and then Vulkan specific things like surface creation.

I'm going to merge this, but with the caveat that it isn't yet officially supported. Thank you for submitting this.


Ethereum Provider Potential Issue with SubscriptionStream

Hi,
I was auditing this code for a project I'm doing and saw that you use the ethers SubscriptionStream which uses eth_subscribe. I was looking at the geth docs and saw that If geth receives multiple blocks simultaneously, e.g. catching up after being out of sync, only the last block is emitted so its possible to miss blocks. Does apibara handle cases like this?

Hi, yes I believe we handle this case. The head tracker tracks the current/canonical chain and so it can detect if any block was skipped. This looks similar to the jump ahead test case, where the block stream sends block 102 and head tracker successfully backfills the missing blocks 100-101.

ahh I see, yeah looks good


Change directory permission instructions

1. Why is this change necessary?
The directory custom/plugins must also be writable.
Please also be aware that this change should be applied to all branches >= 5.2
2. What does this change do, exactly?

Add custom/plugins to directory permissions
Sort directories alphabetically

3. Describe each step to reproduce the issue or behaviour.
:heavy_minus_sign:
4. Please link to the relevant issues (if any).
:heavy_minus_sign:
5. Which documentation changes (if any) need to be made because of this PR?
:heavy_minus_sign:
6. Checklist

[X] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[X] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21872
Please use this issue to track the state of your pull request.

thanks for your contribution @Crease29  :+1: :tada: :blue_heart:


[FR] Default maximum image size (non-destructive)

Hello,
Great plugin. Thank you for refreshing the previous plugin by musug.
I would like to propose a feature, where the images have a maximum image size (horizontal) of X. In a non-destructive way.
My use case:
I tend to copy and paste lots of images into my Obsidian.
I don't want to reduce the size of the images.
But I don't want the images to take all the note space.
My proposal:
Instead of having to resize (non-destructive) each image individually, the plugin could check the image size and if it's bigger than X, apply an image size.
Using ![[Pasted image<PHONE_NUMBER>1352.jpg|1000]] the |.
Like "Image resize mode", but non-destructive.
Thank you for your consideration.

hey, thanks for checking it out!
that's a great idea, going to try to push it out with the next update

Thank you @xRyul for implementing this FR.
I think could be better if the "custom" setup value is a maximum size. Because as it is now, small images are expanded to match whatever I set as "custom" value.
I think this "Custom" should work like max(custom, actual.image.dimension).
Where actual.image.dimension is checking -as you are doing now- the resizeMode.

Hey, thanks for getting back to me 🙏
That's correct, currently it simply adds the desired size to the end of image link.   Although, as you and suggest this is not great when pasting too small images. Especially considering that Obsidian doesn't resample low-res images when we use "| size". Without resampling - low-res images will look crap, as they are simply being stretched.
Nevertheless, this might simply need a toggle, to simply enable/disable small image upscale. I am planning to implement a few other options, hence why currently the option appears as a dropdown. Following are just a few options I was looking at:

Upscale {upscale if image is too small}
Downscale {downscale if image is too big}
Modify only width { |widthxheight }
Modify only height { |widthxheight }
Fit image inside Line Max Width { auto read editors width and fit the image accordingly e.g. based on pixels or %}

Thank you for considering this idea.
Regarding the proposed options, just a few considerations:
Custom limit (here is an input box):

Pixels
% of Line Max Width << Great idea but, can you do it dynamic?. How about if I had it to "no limit in Obsidian", and I resize the Obsidian window?

Allow (dropdown):

Upscale {upscale if image is too small}
Downscale {downscale if image is too big}

Set limit based on (dropdown):

Width { |widthxheight }
Height { |widthxheight }
Longest dimension
Width proportional to Line Max Width { auto read editors width and fit the image accordingly e.g. based on pixels or %, as defined before} << Same question I made before, about how possible is to make it happen

For sure this is too much optionality, but for you to consider and limit to what you consider reasonable and doable.

Maybe, just having the option to set a maximum size will be great :)
I mean,
If the original (pre-conversion or pre-pasting) size is more than the "Setting > Non-destructive resize > Custom size":
     Apply the "|100"
else:
     Keep the original image size (no need to add the "|100")

In this way, the small images are not enlarged when the "|100" is applied.
This could be an option, not the default behavior.
Thank you for your consideration

Thank you! Works great!


./scripts/docker_build_jetpack.sh fail

Hi, when I'm running ./scripts/docker_build_jetpack.sh on my Jetson Xavier it fails during the execution of this part of Dockerfile.jetpack:
#
# install CUDA Toolkit
#
RUN apt-get update && \
    apt-get install -y --no-install-recommends \
		  cuda-toolkit-* \
    && rm -rf /var/lib/apt/lists/* \
    && apt-get clean

The error message that I'm getting is:
Unpacking cuda-nvrtc-10-2 (10.2.89-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-HjrbFB/62-cuda-nvrtc-10-2_10.2.89-1_arm64.deb (--unpack):
 unable to create '/usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89.dpkg-new' (while processing './usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89'): Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89': Read-only file system
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package cuda-nvrtc-dev-10-2.
Preparing to unpack .../63-cuda-nvrtc-dev-10-2_10.2.89-1_arm64.deb ...
Unpacking cuda-nvrtc-dev-10-2 (10.2.89-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-HjrbFB/63-cuda-nvrtc-dev-10-2_10.2.89-1_arm64.deb (--unpack):
 unable to create '/usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h.dpkg-new' (while processing './usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h'): Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h': Read-only file system
...

@dusty-nv or anybody else, do you maybe happen to know why is that?

Hi, you shouldn't need this anymore, instead please use l4t-jetpack container from NGC.  I should remove it from this repo.

From: Piotr Skalski @.>
Sent: Tuesday, August 30, 2022 2:00:56 PM
To: dusty-nv/jetson-containers @.>
Cc: Dustin Franklin @.>; Mention @.>
Subject: [dusty-nv/jetson-containers] ./scripts/docker_build_jetpack.sh fail (Issue #190)
Hi, when I'm running ./scripts/docker_build_jetpack.sh on my Jetson Xavier it fails during the execution of this part of Dockerfile.jetpack:

install CUDA Toolkit

RUN apt-get update &&
apt-get install -y --no-install-recommends
cuda-toolkit-*
&& rm -rf /var/lib/apt/lists/*
&& apt-get clean
The error message that I'm getting is:
Unpacking cuda-nvrtc-10-2 (10.2.89-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-HjrbFB/62-cuda-nvrtc-10-2_10.2.89-1_arm64.deb (--unpack):
unable to create '/usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89.dpkg-new' (while processing './usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89'): Read-only file system
dpkg: error while cleaning up:
unable to remove newly-extracted version of '/usr/local/cuda-10.2/targets/aarch64-linux/lib/libnvrtc.so.10.2.89': Read-only file system
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package cuda-nvrtc-dev-10-2.
Preparing to unpack .../63-cuda-nvrtc-dev-10-2_10.2.89-1_arm64.deb ...
Unpacking cuda-nvrtc-dev-10-2 (10.2.89-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-HjrbFB/63-cuda-nvrtc-dev-10-2_10.2.89-1_arm64.deb (--unpack):
unable to create '/usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h.dpkg-new' (while processing './usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h'): Read-only file system
dpkg: error while cleaning up:
unable to remove newly-extracted version of '/usr/local/cuda-10.2/targets/aarch64-linux/include/nvrtc.h': Read-only file system
...
@dusty-nvhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv&data=05|01|dustinf%40nvidia.com|937b9411e20442fe1d3608da8ab19691|43083d15727340c1b7db39efd9ccc17a|0|0|637974792587162012|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=vtft5dK2ZoCnk1XTVGFZASvLIwsOmLlIlPrfgt%2Bxyr4%3D&reserved=0 or anybody else, do you maybe happen to know why is that?
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-containers%2Fissues%2F190&data=05|01|dustinf%40nvidia.com|937b9411e20442fe1d3608da8ab19691|43083d15727340c1b7db39efd9ccc17a|0|0|637974792587318256|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Fmmbb29U3EUO9D2iEiy4csXHKJ%2B2%2FN7AxNxVuj1zo4A%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK5B2V6FZOYTTTCDOGDV3ZD5RANCNFSM6AAAAAAQAUPLDI&data=05|01|dustinf%40nvidia.com|937b9411e20442fe1d3608da8ab19691|43083d15727340c1b7db39efd9ccc17a|0|0|637974792587318256|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=aDxk4TSP9utde9g5IFa0%2FCAZl6R2MmdBZ2GA%2BRoZJgY%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@dusty-nv do you mean this container: https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-jetpack? It only supports JetPack 5.x, at least judging by available tags. I'm looking for a base image containing TensorRT that I could use with JetPack 4.5.0.

I'm looking for a base image containing TensorRT that I could use with JetPack 4.5.0.

You should use l4t-base container with --runtime nvidia and TensorRT will automatically be mounted in from the host device.
The "fat containers" which have CUDA/cuDNN/TensorRT installed inside the containers themselves only started with JetPack 5.x
BTW I've removed the jetpack.dockerfile from jetson-containers repo in commit https://github.com/dusty-nv/jetson-containers/commit/39496f8eba51ababb0cfb625fc70410163e4fe43

Okay, I'll definitely try. I have a question, however. My goal is to make TensorRT accessible through python 3.8 installed in virtual env inside docker image. IS that possible?

I think you would have to rebuilt the TensorRT Python bindings for Python 3.8 - i haven't tried this.  I think they are on the TensorRT github though

Is that what you mean https://github.com/NVIDIA/TensorRT/tree/main/python?

Yes, I believe that's it

Thanks I'll give it a try!


Added blacklist for non-integratable rigs

It was possible to add higgs anchor rigs (which can't be integrated) into integrated rigs. There is now a blacklist of item ids that have the Cannot be integrated attribute (id 193) that gets loaded on startup (thanks @SilkyPantsDan for the guide). For more details refer to the issue sweet-org/sweet#5.
Fixes sweet-org/sweet#5

There are two different cases for this rig selection list. The first case is, if the integrated rig is empty. In that case, all rigs may be fitted and the initialItems list is empty. This list only gets used in the second case, when there is already a rig inside the integraded rig. In that case, only the rigs with the same market group id and a different main cal code get filtered into the initialItems list which then will be displayed.
So I moved the filtering for the first case to the MarketGroupTile. Another option would probably to (recursively) search and clone the MarketGroups and pass the cloned top Market Group as the topGroup. I'll take a look into how difficult this is, this would probably be a more clean version as it does not require the blacklist to get passed through all these objects/classes into the MarketGroupTile.
And the chaining of course works/is better, I did not want to mess around with the original filter and didn't thought about just joining them.

Ah of course - forgot about that initial case as well. I'll make a note for the data model work I've slowly been working on (and currently trying to make rigs and integrated rigs better) so that we can pick this up sooner and filter it out for the cases of integrators
Thanks again @Blaumeise03!

I'm also close to reworking in the release pipeline so it should be able to work better with the open source repository - so we can get this fix out ASAP


feat: add option for version prefix

Hi,
I am a follower of your Youtube channel and user of this tool. I am seeing myself needing the option for v prefixes while releasing golang library packages.
Unfortunately, my sed/awk workflow does not look very pretty.
Kind regards
Florian

Sure, I have applied the changes you suggested and added tests for cases with version prefix.


TDD project

Created a class called Solver.
Created a methods called factorial, reverse and fizzbuzz
Used TDD Approach. Commit history proves that we have used TDD.
Following Gitflow
Add Linters

😄

Hi @rloterh,
Thanks for Approval. :smile:


Read upstream descriptions from sources

resolves #153
This is a:

[x] bug fix with no breaking changes

All pull requests from community contributors should target the main branch (default).
Description & motivation
generate_model_yaml now reads upstream description from sources, as well as models.
Checklist

[ ] This code is associated with an issue which has been triaged and accepted for development.
[x] I have verified that these changes work locally
[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

Also thank you for patience, truly appreciated @esegal!


How to use it in PlatformIO?

It works fine in ArduionoIDE.
This time, we want to use it in PlatformIO.
I'm worried because I don't know how to use it.
Please inquire how to do it.
Thank you.

Hi, have you found a way to use it in platformio?
This might be helpful : https://docs.platformio.org/en/stable/platforms/creating_platform.html
We'd probably need to create a package (example: framework-arduino-nullab ) with files from this repo and then write custom platform settings for PlatformIO.

加油！我也是在platform IO上开发的。能用上1.08版就更好啦！


Duplicated result appear in both of web platform and download data when seaching disease=cancer, gens=7SK

Duplicated result appear in both of web platform and download data when seaching disease=cancer, gens=7SK.
recreation the issue:

web platform
step1.  Access  cancer page (https://platform.opentargets.org/disease/EFO_0000311/associations)
step2.  Then search -> 7SK

download data:
step1.  Call overallDatasourceHarmonicScore of cancer
step2.  Search 7SK

In reviewing this cancer associations page (filtered by 7SK), it appears that 7SK is RNA found on different chromosomes and has different Ensembl IDs. And so each Ensembl ID has its own evidence page.

https://platform.opentargets.org/evidence/ENSG00000277313/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000275933/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000276626/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000202198/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000273591/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000271394/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000274303/EFO_0000311

All 7 evidence pages listed above have the same 3 rows in the Europe PMC section, referring to two PubMed IDs — 27752877 (2 x duplicated) and 22377309.

However, 2 of the evidence pages also have RNA expression evidence:
https://platform.opentargets.org/evidence/ENSG00000271394/EFO_0000311
https://platform.opentargets.org/evidence/ENSG00000274303/EFO_0000311

Flagging this for our data team to review and comment if the "duplication" is valid.
@ireneisdoomed, @DSuveges, @tskir, @d0choa

Ticket closed as 7SK has multiple Ensembl IDs (as noted above) and the text mining pipeline is unable to distinguish which Ensembl ID to use for the occurrence of 7SK in the literature.


wrong param with GetParams function

// 获取小程序前点调用支付接口所需参数     params, err := payment.GetParams(res.AppID, res.MchID, res.NonceStr, res.PrePayID, time.Now())     if err != nil {         // handle error         return     }
the paySign should use apikey not MchID, and here is the wechat app pay document

You are right, I've fixed it, thanks for that.


Make history prettier on PC

The current direction is "mobile first" which makes sense.
But the app and UI needs to be optimized for PC as well.

Marking this issue as invalid. This release will be mobile first


Not work with angular material v15

After update angular material to v15, mat-table-exporter doesn't work.

are you getting a custom exporter error too???


feat: OpenAI compatible API

The PR adds support for OpenLLM to be compatible with the legacy completions API of OpenAI for both stream & non-stream responses.
Notes:

The 'usage' (# of tokens) and 'finish_reason' are not currently supported due to the fact that a lot of implementations in _llm.py only take the 'text' of the output as the response. Changing them would raise inconsistency with other API endpoints, so I will have a discussion on how to proceed on the next step.
There is inconsistency in the implementation of vllm with pytorch. Probably need to discuss with Aaron on how to make everything consistent. With his guidance, I can make those changes.
Still need to do the chat completion API and embedding API, but should be much easier after completing this.

pre-commit.ci autofix


create github actions for commit

before we merge we need to setup some tests.

Yes the ci/cd failed for this commit of ci/cd... :/ that’s just an issue with “pub get”


Reset ordering part of orderSequence

It would be nice if sorting could easily be reset, showing the rows in their original order.
What I imagine, is to extend the columns.orderSequence option to support a third value, for example null or "" (the empty string), which means to disable sorting.
"orderSequence": [ "asc", "desc", null ] would mean that, by clicking on a column header, the rows will be ordered first ascending, then descending, and lastly be shown in their original order.
Such an ordering sequence is used for example by Spotify. When sorting a playlist by clicking on a column, the tracks are shown ascending, descending and then in their playlist order.

Thanks for the suggestion. However, this is a duplicate of #526.


Migrate CodebaseResource and DiscoveredPackage pk from id to uuid

DiscoveredPackage already has a uuid field but it's not the pk
CodebaseResource has only a id
Note: we want to keep the id as pk, simply add the uuid for the URLs and reference the object.

We do not rely on id PK in URLs anymore, https://github.com/nexB/scancode.io/commit/92d9c3543e6fbcfd6f0ca063068e1df8489a240a


Headline: make size a responsive property

In the design, we often have different font sizes defined for mobile and desktop versions of the UI. At the moment, there is no easy way to make it without explicit checks in the component. It would be great if we can provide a list or an object of sizes based on breakpoints to the size prop of the Headline component in a similar fashion we do with p and m props:
<Headline as='h2' size={['m', 'l']}>Text</Headline>
<Headline as='h2' size={{_: 'l', small: 'm'}}>Text</Headline>

@nlopin this would be great. We just need to document this in a clear way so everyone will understand how a particular Headline will look on different screens.
By design we do not have, for now, any definition on how a we transform headlines for mobile. Do you have on your side something already so we can bring this to the design group for discussion?

As an example, the web registration's thank you screen uses different headline in different viewports

@nlopin Ok, thanks. I will bring this to a discussion with other designers.

relates to #55

I will copy my question from #55 here (with a small correction, because I noticed a mistake 😅):
In code we have fontSizes: ['0.75rem', '0.875rem', '1rem', '1.25rem', '1.5rem', '2rem', '2.5rem', '3rem'],
and later
theme.fontSizes.small = theme.fontSizes[1];
theme.fontSizes.medium = theme.fontSizes[2];
theme.fontSizes.large = '1.125rem';

Did I get it right that we have?:

x-small : 0.75rem
small : 0.875rem
medium : 1rem
large : 1.25rem
x-large : 1.5rem
xx-large : 2rem
xxx-large : 2.5rem
xxxx-large : 3rem

If so, do we have an idea for how to improve the name for xxx-large and xxxx-large?

@nlopin , @nlopin Here I made some explorations
https://www.figma.com/file/pTAzbj6iuSFFWTPKvmEJOA/Wave-setup?node-id=0%3A1
On the right side I also collected some examples for how others are managing the names for different text sizes. We can discuss this in a dedicated session.


Fix a bug that a new model replica couldn't be registerd with the Clipper's RPCService

related issue : https://github.com/ucbrise/clipper/issues/636

LGTM!

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1934/
Test FAILed.

jenkins test this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1935/
Test PASSed.

@rkooo567 : Thank you! Don't you have the permission to review?

@withsmilo thanks for the patch! @rkooo567 i just gave you access to review and merge PR.


refactor: change the way dependencies are wired

might be a problem here with logs not being written to nginx's error log


adding attributes per surface

Semantic surfaces can have attributes, it would be nice if they were added

https://3d.bk.tudelft.nl/opendata/cityjson/3dcities/v1.1/DenHaag_01.city.json
is the file I showed btw, for testing purposes


Disable default-features for http-types

http-client doesn't use any of the default features.

That isn't true, we re-export some things (e.g. Body) which as additional functions based on features, unfortunately.
I suspect we could change this without anyone noticing but we should probably be careful.

That isn't true, we re-export some things (e.g. Body) which as additional functions based on features, unfortunately.
I suspect we could change this without anyone noticing but we should probably be careful.

It looks like the main issue there would be things like Body::from_file, which needs the fs feature. Making http-client depend on the fs feature of http-types shouldn't be a problem; that only causes http-types to depend on async-std, which will often be a dependency of http-client anyway. So, I'll change this PR to enable the fs feature, which should then avoid breakage.
(In theory, someone could rely on http_client::http_types::cookie or similar, but that seems much less likely compared to just using http_types directly.)

It looks like the main issue there would be things like Body::from_file, which needs the fs feature. Making http-client depend on the fs feature of http-types shouldn't be a problem; that only causes http-types to depend on async-std, which will often be a dependency of http-client anyway. So, I'll change this PR to enable the fs feature, which should then avoid breakage.
(In theory, someone could rely on http_client::http_types::cookie or similar, but that seems much less likely compared to just using http_types directly.)

@Fishrock123 Does this seem more reasonable? I think we can make this change without a semver-major bump.

@Fishrock123 Does this seem more reasonable? I think we can make this change without a semver-major bump.

Not sure what's causing the test failure. It looks like it happens on latest main, without this change; perhaps something changed elsewhere in the ecosystem that broke the http-client build.

Not sure what's causing the test failure. It looks like it happens on latest main, without this change; perhaps something changed elsewhere in the ecosystem that broke the http-client build.

@joshtriplett Could you rebase?

@Fishrock123

@joshtriplett If we release this, is cargo smart enough to not upgrade someone to this version if they are pinning to a previous http-types for some reason?

@Fishrock123 Cargo doesn't allow multiple compatible versions of the same crate in one dependency tree. If you're pinning an older http-types, you can't end up with a newer http-client that needs a newer http-types. (I don't know to what degree cargo's version resolution will decide to use an older http-client and to what degree it'll throw up its hands and say "nope, incompatible".)

Bumping a major here likely means bumping a major in surf, which I don't want to do until I have to for http-types 3.0 if possible.

Is there a major milestone waiting to get to http-types 3.0? Similarly I'm trying to get rid of dependencies keeping things as light as possible and the latest http-types helps a bit changing the rand dependency that I wont be needing

@Fishrock123 As far as I can tell, now that this change no longer omits the fs feature, it shouldn't require bumping any major versions. Given that, would you consider this change for http-client?


Remove support for using equals() to determine whether a task input property has changed

We now use the serialized binary form for values of custom types to determine whether a value has changed. However, for backwards compatibility we also fall back to using equals() when the binary forms are different. Using equals() has performance and robustness implications, as the previous value needs to be deserialized in order to do this, which means we need to retain and persist enough state to do this rather than, say, retaining only a hash of the binary form. This behaviour is also inconsistent with how the build cache makes its decision, which uses only the binary form.
In 4.0, we should remove support for equals() to address these issues.

@wolfs commented on Wed Dec 30 2020
I think we still want to do this. Though it seems like we don't use equals any more for change detection, though we try to use equals when we we snapshot a value and we have a pre-existing value: https://github.com/gradle/gradle/blob/e61192cf1c410b2d74d032a4c93514aef61e8b32/subprojects/model-core/src/main/java/org/gradle/internal/snapshot/impl/SerializedValueSnapshot.java#L73-L78
We should probably remove this behaviour in Gradle 7.0.

The deprecation has been added in 7.2: https://github.com/gradle/gradle/issues/17325


PLT-8215 Channel Switcher also checks member full name, nickname for …

…GM and DM channels
Summary

factors the channel filtering logic out of formatChannelsAndDispatch
resolves user profiles for GMs and DMs and includes their current username, nickname, and full name with the channel display name for matching against
replaces usage of String.prototype.indexOf with String.prototype.includes for readability
removed extraneous variable declaration

Ticket Link
resolves https://github.com/mattermost/mattermost-server/issues/7912
@enahum, thanks for your guidance today.
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-0fbf7d80d9101dfa6.spinmint.com
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-0fbf7d80d9101dfa6

Spinmint test server destroyed


Deletion of test cases

Hi
Can Piranha also delete unit test and integration tests corresponding to the code ?

Yes. Assuming this question is for Java, see discussion in https://github.com/uber/piranha/issues/123.


Cycle lists with keyboard shortcuts

Closes #1450
Replaces and closes #1501

I can no longer go backwards in the list with ArrowUp when using this PR.

Well, look at that. GitHub did it first


pre-commit: PR115988

Link: https://github.com/llvm/llvm-project/pull/115988
Requested by: @dtcxzyw

/add-label reviewed
/close


Onboarding link does not work

Summary
in our new tab "ecosystem", the onboarding tutoral link issues a 503 error
Current Behavior
503 error
Expected Behavior
onboarding tutorial appers
Steps to Reproduce

open mvg portal
select tab Ecosystem
select onboarding tutorial
see error 503

The link is working as expected, the problem is that the onboarding service is not available at the moment, nothing we can do from the portal except remove the link until the service is back up again.

okay then I close the issue for now

I would leave it open until we decide if we want to remove the link from the menu or not

I think we should remove the link for now, as this will not be resolved in the near future.


Dependency versions

Our minimum version requirements include numpy 1.5.0 and scipy 0.9.0.  However, our Ubuntu tests only test the latest version of all packages, and the miniconda tests only support numpy >= 1.6.2 and scipy >= 0.11.0.
I am a bit uncomfortable listing dependencies that our tests cannot verify work properly.  Installing either numpy or scipy (not to mention both) manually in travis takes forever, so that is not a feasible approach.
Even someone tests manually before official releases, a lot of small and subtle bugs sneak through that can be very hard to track to a specific change.
So I am thinking it might be best to set our minimum dependencies versions to be the versions supported by travis or greater.  What does everyone else think?

@apdavison perhaps Numpy 1.9 is downloaded because in the requirements it is stated that the version should be higher than 1.6.2. So if Elephant is installed per pip e.g. in a virtualenv numpy 1.9 will be automatically downloaded and installed.

@alperyeg That's not how I interpreted the message. He stated that he "needed" to install 1.9, which suggests to me that he already had an earlier version installed, and it didn't work. I guess I should follow up to find out which earlier version he tried and what the error message was.

set our minimum dependencies

We provide the versions as scipy>=X.Y.Z but this does not mean all X.Y.Z will work because it might clash with the requirement of another package. Therefore, the solution to this issue requires building a dependency tree, which, of course, is something we as the developers won't do.


Deserialization with custom ClassLoader

Our custom transformers live outside of the main project's class path, particularly in database. How to deserialize using a custom ClassLoader?
The code below loads transformers using the default ClassLoader and assumes transformers live with the main project. Ideally we should be able to deserialize as below by providing a custom ClassLoader as a parameter. Is it possible using the current API?
// load the Spark pipeline we saved in the previous section
val bundle = (for(bundleFile <- managed(BundleFile("jar:file:/tmp/simple-spark-pipeline.zip"))) yield {
  bundleFile.loadMleapBundle().get
}).opt.get

This appears to work (doing more tests before closing the issue)
implicit lazy val context: MleapContext = MleapContext(Some(your-class-loader))
val bundle = (for(bundleFile <- managed(BundleFile("jar:file:/tmp/simple-spark-pipeline.zip"))) yield {
  bundleFile.loadMleapBundle()(context).get
}).opt.get

@htdawoud The classloader you provided may have sun.misc.Launcher$AppClassLoader as the parent class loader is the only thing I can think of. Let me know if you find something in MLeap itself that is causing it to fallback to the app class loader.
Closing for now.


Chokidar causes VS Code extensions crashes on VS Code Insiders v1.31

Describe the bug
All VS Code extensions that are using Chokidar in their dependencies crashes on new VS Code Insiders version, that to be release approximately in February.
Versions (please complete the following information):

Chokidar version 2.0.4
Node version 10.2.0
OS version: macOS Mojave 10.14.2

To Reproduce

Install latest VS Code Insiders(1.31-insiders)
Install any of VS Code extensions that are using Chokidar (for example vscode-cordova)
Try to use any of extension functionality, that calls the extension code (accordingly to the example described above, try to debug Apache Cordova application)

Expected behavior
VS Code extensions that are using Chokidar is not crashes with new VS Code Insiders(1.31-insiders) version.
Additional context
This issue was investigated already and the problems is in fsevents package, that have some issues with Electron 3 (Node.js 10.2.0) that VS Code 1.31 is using under the hood. As described in this issue<EMAIL_ADDRESS>have no such problems.
So it looks like Chokidar is needed to be bumped fsevents to 1.2.4 version to be able to work with new Electron and VS Code versions without any errors.

The fsevents dependency was updated in v.2.1.0.

Hi, I am using v2.1.0 with fsevents 1.2.7 in my VSCode extension and this still causes the extension to crash in VSCode 1.32.3 on OSX.
See https://github.com/christianvoigt/argdown/issues/104
How far away is the release of 3.0.0?

I just checked again and there seems to be an issue with the update process in VSCode. Even though VSCode shows me I have installed the new version of my extension, the fsevents error thrown shows it is still trying to run the old version. So this is not an issue of Chokidar 2.1.0. Sorry for bothering you.

Still not work with<EMAIL_ADDRESS>

Try 3.0-master.

@paulmillr chokidar 3.0.0 works fine, thanks a lot!

Great!


RFC: Attributes

Rendered link
First draft of attribute RFC. This is very similar to how decorators were handled in JavaScript. This is marked as a draft until scope, desired features and feasibility is better understood.
TODO:

Do we want to allow annotating types? How would this be handled by the runtime? Would this be reserved only for the typechecker?
Do we want to trade any dynamic properties of attributes for constants/compile-times to increase performance or debugability?
Can attribute-laden code be feasibly debugged?

I am very interested in hearing your thoughts, use cases, and criticisms for this proposal. Thanks!
Note: This RFC collides with #807 so do not merge without resolving that first.

Hi @alexmccord, I saw you added the RFC tag to the other PR. Would you mind also adding it to this one? Thanks.


can't add childViewControllers with loop

override func viewControllers(for pagerTabStripController: PagerTabStripViewController) -> [UIViewController] {
var controllers = UIViewController
for item in self.sportsPrematch {
let chid = SportsViewController(itemInfo: IndicatorInfo(title: item.name, image: UIImage(named: "topi_futsal_w")))
controllers.append(chid)
    }
    return controllers

}
and this message is shown:
fatalError("viewControllersForPagerTabStrip should provide at least one child view controller")

You should append the child to your controllers before you called super.viewDidLoad()
In my case that's working


Update the token counting functions when library supports tool_calls

Feature Request
upgraded OpenAI 3.x to 4.19 where function_calls is depreciated and replaced with tool_calls (which takes functions as input).
The openai-chat-tokens library we use to count prompt tokens does not have the tool update supported yet so we have used a workaround to convert the tools to functions to pass to the token counter.
See https://github.com/ScottLogic/prompt-injection/pull/590
Description
When openai-chat-tokens is updated, change the function estimateMessageTokens function in openai.ts to pass tool_call in as itself instead of a converting to function as workaround.
If applicable, add screenshots to help explain your request.
Additional context
There may be changes to the number of tokens used by a tool vs. a function - may need to investigate when change is released.
Acceptance criteria
GIVEN openai-chat-tokens has been updated to use tool_calls
WHEN a function is called
THEN the correct tokens are counted & unit tests pass

Adding the blocked label until the library supports tool_calls.


Make autogenerated BlazorComponent views partial class

I would like to split the Razor c # + html template from the purely functional code of the view and I tried to make every generated class contained in "BlazorRazorComponents.g.cs" with the partial modifier (simply adding it in "Microsoft.AspNetCore.Blazor.Razor. Extensions \ BlazorRazorEngine.cs ").
So my views are composed in
nomeview.cshtml       <- html layout
nomeview.cshtml.cs   <- functional code
The compilation works without problems.
The problem is Visual Studio is unable to "read" the contents of the code in cshtml.cs, showing the error CS1061 'Class' does not contain a definition for 'Method'.
Now, adding the directive
@inherits <name of the same class>
instead Visual Studio works correctly, while, obviously, the compilation is not successful because the autogenerated code becomes
public partial class <classname>: <classname> <- the same
But if the code remain
public partial class <classname>: BlazorComponent
both the compilation and Visual Studio would work.
Is it possible to make that if implements the same class, BlazorComponent is kept as a base class?

Depends on #4065

@ajaybhargavb  should this be resolved as Done ?

Yeah. I'll file a new issue to track addressing feedback and fixing bugs.

Filed https://github.com/aspnet/AspNetCore/issues/14646


[usecase-wrt] Add test for handling SSL certificates

Impacted tests(approved): new 1, update 0, delete 0
Unit test platform: Crosswalk for Android 21.51.546.0
Unit test result summary: pass 1, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/CTS-1799

@Honry

LGTM


Unbreak CI config

Build with Node 14 installed through orbs.
Fixes #1275

Error is unrelated. Build failure is:
ERROR in ./src/sass/theme.sass
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):

  :not(kbd) > kbd,
 ^
      Property "not" must be followed by a ':'

I won't fix that in this PR.


features_cols param requires enabling use_gpu in pyspark

hi, I am using xgboost 1.7.4 in pyspark distributional training.
Here is the code:
df_assemble_dense_train_, df_assemble_dense_test = df_ix_oht_l_train.randomSplit([0.8, 0.2])

training_valid_data = df_assemble_dense_train_.withColumn("validationIndicatorCol", rand(1) >= 0.9)
xgbm = SparkXGBClassifier(
          features_col= [x.name for x in training_valid_data .schema if x.name != "label"]
          label_col= "label",
          n_estimators = 3000,
          max_depth = 7,
          max_bin  = 256,
          learning_rate = 0.1,
          min_child_weight = 0.2,
          subsample = 0.7,
          colsample_bytree = 0.7,
          # reg_alpha  = 0,
          # reg_lambda =0,
          num_workers = 15,
          max_cat_to_onehot = 10,
          max_cat_threshold = 1000,
          eval_metric="auc",
          early_stopping_rounds = 50,
          # missing=None,

          maximize_evaluation_metrics = True,
          validation_indicator_col="validationIndicatorCol"
)

# train and return the model
model = xgbm.fit(training_valid_data)

ERROR:

ValueError                                Traceback (most recent call last)
 in
27
28     # train and return the model
---> 29     model = xgbm.fit(training_valid_data)
30
31     predictions_test = model.transform(df_assemble_dense_test)
/databricks/python_shell/dbruntime/MLWorkloadsInstrumentation/_pyspark.py in patched_method(self, *args, **kwargs)
28             call_succeeded = False
29             try:
---> 30                 result = original_method(self, *args, **kwargs)
31                 call_succeeded = True
32                 return result
/databricks/spark/python/pyspark/ml/base.py in fit(self, dataset, params)
159                 return self.copy(params)._fit(dataset)
160             else:
--> 161                 return self._fit(dataset)
162         else:
163             raise TypeError("Params must be either a param map or a list/tuple of param maps, "
/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.8/site-packages/xgboost/spark/core.py in _fit(self, dataset)
645     def _fit(self, dataset):
646         # pylint: disable=too-many-statements, too-many-locals
--> 647         self._validate_params()
648         label_col = col(self.getOrDefault(self.labelCol)).alias(alias.label)
649
/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.8/site-packages/xgboost/spark/estimator.py in _validate_params(self)
228
229     def _validate_params(self):
--> 230         super()._validate_params()
231         if self.isDefined(self.qid_col):
232             raise ValueError(
/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.8/site-packages/xgboost/spark/core.py in _validate_params(self)
287         if self.getOrDefault(self.features_cols):
288             if not self.getOrDefault(self.use_gpu):
--> 289                 raise ValueError("features_cols param requires enabling use_gpu.")
290
291             get_logger(self.class.name).warning(
ValueError: features_cols param requires enabling use_gpu.

It seems that for param : features_col, I can not pass in with a list of feature columns names.
It works only when I assemble the feature columns into dense vector.
However, I find that in the doc https://github.com/dmlc/xgboost/blob/master/doc/tutorials/spark_estimator.rst
saying that

the "features" column(s) must be pyspark.ml.linalg.Vector type or spark array type or a list of feature column names.

Am I miss something ? Thanks.

This is an XGBoost extension for GPU acceleration. On CPU, the convention established by the spark-ml library is used, where all features are stored in a single dataframe column

thanks.

@trivialfis @yananchen1989  so wait how do you actually solve the problem? How does the code need to change. I'm getting the same error and I pass in a spark DataFrame into fit, specifying which column is the class (a string) and which columns are features with a list. See my code:
import pyspark.sql as psql
import xgboost.spark
spark = psql.SparkSession.builder.getOrCreate()
df = spark.read.parquet('dataset.parquet')
train, test = df.randomSplit([0.9, 0.1], seed=0)
label_name = 'label'
feature_names = [x.name for x in df.schema if x.name != label_name]

classifier = xgboost.spark.SparkXGBClassifier(
  features_col=feature_names,
  label_col=label_name,
  num_workers=2,
  device="cuda",
)
classifier.fit(train)

@erikhuck, If your node has only 1 GPU, you need to set num_workers=1.  I just tried your code to train a model on the iris dataset, it can work.

@wbo4958 I really appreciate your help!


comparisons: add RestrictedAny family of classes, analogous to mock.ANY

Need I say more?
I need to use these in more tests I'm writing, so would like to get this in soon.

Although the more I think about this, "malleable" may not be the right word here because actually this class is more restricted than mock.ANY. I wonder if RestrictedAny would be a better name?

Moved this to comparisons.py, renamed to RestrictedAny.

Why override __repr__ in these?

Oh don't worry, I get it...
... I think these just need something in the name (or in the module name) showing that they are mocks. Maybe we could have dmutils.mock.comparisons?

Well, they're not really mocks, are they? mock.ANY happens to live in mock because it has a use there (presumably originally matching recorded arguments of calls).

Yep ok point taken.
Are we expecting tests for these? Tests would probably be enough the make the expected usage/use cases clear.

(If not tests, then example usage in the docstrings, maybe?)

Tests? Perhaps if they got more complicated. Would be the first tests for this repo and would probably involve giving it a requirements-dev.txt and all that faff. Which also raises the question - all these undeclared dependencies we have because of the decision to try and avoid diamond dependencies - do we now have to declare them all in requirements-dev.txt...? Luckily this feature itself doesn't have any dependencies.
Might add something to the docstring?

Yep, docstring fine too, I'm not gonna be precious about that.
(Yes if I see the logic, all the dependencies we'd avoided adding to requirements.txt would indeed have to go into a possible requirements-dev - let's not go there for now I suppose :-) )


Unblock-File fails silently

In Windows PowerShell 5.1 this command will unblock files as expected:
gci C:\Users\myUser\OneDrive\Documents\foodir -Recurse -File | unblock-file
However, on the same machine, PowerShell 6.2.1 does not perform the unblock or give any indication of a problem.

I try :

download a blocked file ( https://notepad-plus-plus.org/repository/7.x/7.7/npp.7.7.Installer.x64.exe )
create a subfolder foodir in my OneDrive directory
move the blocked file to 'foodir'
verify the file is blocked => True
Enter the same command 'gci C:\Users\XXX\OneDrive\Documents\foodir -Recurse -File | unblock-file'
verify the file is unblocked => True

I can't reproduce your issue. ( Windows 10 1809/17763.475 + PS 6.2.1)
Please provide more informations to reproduce your issue.

Could you check that
gci C:\Users\myUser\OneDrive\Documents\foodir -Recurse -File
has any output?

My apologies, the silent failure is only when not elevated, which I think is the same (unfortunate) behavior as 5.1.
Name                           Value

PSVersion                      6.2.1
PSEdition                      Core
GitCommitId                    6.2.1
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@lanatmwan Feel free to contribute.


Get installed version with docker latest tag

I am using portainer installed with docker with portainer/portainer-ce:latest. Is it possible to get the installed version programmatically? (I mean without logging into the web). Some other containers use docker labels so it can be retrieved with the docker inspect command or some form of docker exec command. Is it possible to get it for portainer?
Thanks,

Hi @jrhbcn - Thanks for the question. As you have proabably already discovered, this information is not currently available in labels. I will investigate whether it is available elsewhere - or whether it can be made available elsewhere.
In the meantime, if you absolutely must get it programmatically, the version is reported in Portainer's container logs upon startup. The message looks like this: time="2022-05-22T20:14:32Z" level=info msg="[INFO] [cmd,main] Starting Portainer version 2.13.1\n". It's not a solution, but the data is there.

@jrhbcn
curl <portainer_url>/api/status will give you the version info.

Just what I was looking for, thanks @samdulam and @goatatwork.


Add dependency on non-tests classifier version of workflow-cps and incrementalify

Although the plugin has an explicit dependency on the <classifier>tests</classifier> version of workflow-cps, the regular test-scope dependency is pulled in transitively through workflow-multibranch.
This works fine for now since the 2 current versions seem to be compatible, but in the PCT, there can be failures because SnippitizerTester (which comes from the <classifier>tests</classifier> version of workflow-cps) from workflow-cps 2.56+ is not compatible with regular workflow-cps 2.55-, and the PCT isn't smart enough to update the non-classifier version unless it is specified explicitly here (it updates the workflow-multibranch version, but that is not enough).
I also incrementalified the plugin while I was here and fixed the access-modifier issue.

Sorry @casz I didn't see your PRs before submitting this or I would have based it off of them. This should subsume #50 and #51.

Ok now I could really use the incrementals on this repo so I can continue work on JENKINS-21336.

https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/matrix-auth/2.4-rc198.ac6c813a7ee8/ does that help? at least this PR is incremental 🤭

I suppose I could try forking from this PR. Good point!

Thanks @dwnusbaum and @casz for these changes, and I apologize for the delay. I've been very busy recently, so this plugin got a bit neglected.


systemd: Disable atd & cron

Those services can be used to run programs outside a user's slice, bypassing resources limits.

@KellerFuchs this PR still has the weird duplication in file names.

@daurnimator Thanks for the reminder.
Also, I just realised that this will break all the maintainance scripts under cron.*.
I will add some systemd units that run them.

@daurnimator I added some systemd units to periodically run /etc/cron.*, but I didn't try them yet.

@daurnimator I added some systemd units to periodically run /etc/cron.*, but I didn't try them yet.

I'd prefer we convert out crontab scripts to systemd timers.
I guess I'm okay with this as a temporary fix though if you want to merge as-is.


Skip show_bad_app_version Marathon test

Marathon changed the error message for invalid versions.
A ticket has been opened : https://jira.mesosphere.com/browse/MARATHON-7954
Until this is resolved that test should be skipped.

run linux integration tests


semantic kernel first version

first version on SK v1.0 lib version.
I will add a bit more changes and will update the readme, where are the differences lies with LC (as far as my knowledge)

Thanks @sohamda!


[chiptool.py] Failed to run test case [TC-ACE-1.5]. Test Step 4 : Waiting after opening commissioning window

Failure
I tried to run TC-ACE-1.5 using develop branch of Matter TH.
But this test step crashed chiptool.py :

Test Step 4 : Waiting after opening commissioning window

Error:
  File "/root/scripts/py_matter_yamltests/matter_yamltests/pseudo_clusters/clusters/delay_commands.py", line 61, in WaitForMs
    time.sleep(duration_in_ms / 1000)
TypeError: unsupported operand type(s) for /: 'str' and 'int'

Reproduction steps

commission device using chiptool.py
run chiptool.py command with arguments:

./scripts/tests/yaml/chiptool.py tests Test_TC_ACE_1_5 --nodeId 0xf8f838e26badee7d --delayInMs 250 --timeout 900 --continueOnFailure 1 --trace_file "/logs/trace_log_2023-05-09_22.33.36_0xf8f838e26badee7d_TEST_Test_TC_ACE_1_5.log" --trace_decode 1 --endpoint 0 --payload MT:-24J0AFN00KA0648G00 --discriminator 3840 --waitAfterCommissioning 5000 --PakeVerifier hex:b96170aae803346884724fe9a3b287c30330c2a660375d17bb205a8cf1aecb350457f8ab79ee253ab6a8e46bb09e543ae422736de501e3db37d441fe344920d09548e4c18240630c4ff4913c53513839b7c07fcc0627a1b8573a149fcd1fa466cf

Expect this log output:

WARNING:root:TAG configurator::cluster::description was not handled/recognized at src/app/zap-templates/zcl/data-model/chip/diagnostic-logs-cluster.xml:41:146
WARNING:root:TAG configurator::cluster::command::description was not handled/recognized at src/app/zap-templates/zcl/data-model/chip/diagnostic-logs-cluster.xml:47:63
WARNING:root:TAG configurator::clusterExtension::command::description was not handled/recognized at src/app/zap-templates/zcl/data-model/chip/color-control-cluster.xml:373:6
Parsing 1 files.
		Parsing: src/app/tests/suites/certification/Test_TC_ACE_1_5.yaml
✓ 7.0ms
		Connecting: ws://localhost:9002

⚠ 12.0ms
		  Retrying in 1 seconds.
		Connecting: ws://localhost:9002

✓ 1.0ms
Running: "42.1.5. [TC-ACE-1.5] Multi-fabric" with 17 steps.
		***** Test Start : Test_TC_ACE_1_5
		***** Test Step 1 : Wait for the commissioned device to be retrieved for TH1
		1. Running Wait for the commissioned device to be retrieved for TH1
✓ 216.42ms
		    [PostProcessCheckType.IM_STATUS check] The test expects no error and no error occurred.
		**** Test Setup: Device Connected
		***** Test Step 2 : TH1 reads the fabric index
		2. Running TH1 reads the fabric index
✓ 2.22ms
		    [PostProcessCheckType.IM_STATUS check] The test expects no error and no error occurred.
		    [PostProcessCheckType.SAVE_AS_VARIABLE check] The test save the value "1" as th1FabricIndex.
		***** Test Step 3 : Open Commissioning Window from alpha
		3. Running Open Commissioning Window from alpha
✓ 12.7ms
		    [PostProcessCheckType.IM_STATUS check] The test expects no error and no error occurred.
		***** Test Step 4 : Waiting after opening commissioning window
		4. Running Waiting after opening commissioning window
Traceback (most recent call last):
  File "/root/./scripts/tests/yaml/chiptool.py", line 141, in <module>
chiptool_py()
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/root/./scripts/tests/yaml/chiptool.py", line 130, in chiptool_py
success = send_yaml_command(commands[1], server_path, server_arguments, pics, commands[2:])
  File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/root/./scripts/tests/yaml/chiptool.py", line 44, in send_yaml_command
    return ctx.forward(chiptool)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 781, in forward
    return __self.invoke(__cmd, *args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/root/scripts/tests/yaml/runner.py", line 323, in chiptool
    return ctx.forward(websocket)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 781, in forward
    return __self.invoke(__cmd, *args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/root/scripts/tests/yaml/runner.py", line 299, in websocket
    return runner.run(parser_group.builder_config, runner_config)
  File "/root/scripts/py_matter_yamltests/matter_yamltests/runner.py", line 150, in run
    raise (result)
  File "/root/scripts/py_matter_yamltests/matter_yamltests/runner.py", line 182, in _run
    responses, logs = await config.pseudo_clusters.execute(request)
  File "/root/scripts/py_matter_yamltests/matter_yamltests/pseudo_clusters/pseudo_clusters.py", line 35, in execute
    status = await command(request)
  File "/root/scripts/py_matter_yamltests/matter_yamltests/pseudo_clusters/clusters/delay_commands.py", line 61, in WaitForMs
    time.sleep(duration_in_ms / 1000)
TypeError: unsupported operand type(s) for /: 'str' and 'int'

Test_TC_ACE_1_5.yaml
# Copyright (c) 2021 Project CHIP Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default

name: 42.1.5. [TC-ACE-1.5] Multi-fabric

PICS:
    - MCORE.ROLE.COMMISSIONEE
    - APPDEVICE.S

config:
    nodeId: 0x12344321
    cluster: "Access Control"
    endpoint: 0
    payload:
        type: char_string
        defaultValue: "MT:-24J0AFN00KA0648G00"
    discriminator:
        type: int16u
        defaultValue: 3840
    waitAfterCommissioning:
        type: int16u
        defaultValue: 5000
    PakeVerifier:
        type: octet_string
        defaultValue: "hex:b96170aae803346884724fe9a3b287c30330c2a660375d17bb205a8cf1aecb350457f8ab79ee253ab6a8e46bb09e543ae422736de501e3db37d441fe344920d09548e4c18240630c4ff4913c53513839b7c07fcc0627a1b8573a149fcd1fa466cf"

tests:
    - label: "Wait for the commissioned device to be retrieved for TH1"
      cluster: "DelayCommands"
      command: "WaitForCommissionee"
      arguments:
          values:
              - name: "nodeId"
                value: nodeId

    - label: "TH1 reads the fabric index"
      cluster: "Operational Credentials"
      command: "readAttribute"
      attribute: "CurrentFabricIndex"
      response:
          saveAs: th1FabricIndex

    - label: "Open Commissioning Window from alpha"
      cluster: "Administrator Commissioning"
      command: "OpenCommissioningWindow"
      timedInteractionTimeoutMs: 10000
      arguments:
          values:
              - name: "CommissioningTimeout"
                value: 180
              - name: "PAKEPasscodeVerifier"
                value: PakeVerifier
              - name: "Discriminator"
                value: discriminator
              - name: "Iterations"
                value: 1000
              - name: "Salt"
                value: "SPAKE2P Key Salt"

    - label: "Waiting after opening commissioning window"
      cluster: "DelayCommands"
      command: "WaitForMs"
      arguments:
          values:
              - name: "ms"
                value: waitAfterCommissioning

    - label: "Commission from TH2"
      identity: "beta"
      cluster: "CommissionerCommands"
      command: "PairWithCode"
      arguments:
          values:
              - name: "nodeId"
                value: nodeId
              - name: "payload"
                value: payload

    - label: "Wait for the commissioned device to be retrieved for TH2"
      identity: beta
      cluster: "DelayCommands"
      command: "WaitForCommissionee"
      arguments:
          values:
              - name: "nodeId"
                value: nodeId

    - label: "TH2 reads the fabric index"
      identity: "beta"
      cluster: "Operational Credentials"
      command: "readAttribute"
      attribute: "CurrentFabricIndex"
      response:
          saveAs: th2FabricIndex

    - label: "Read the commissioner node ID from the alpha fabric"
      identity: "alpha"
      cluster: "CommissionerCommands"
      command: "GetCommissionerNodeId"
      response:
          values:
              - name: "nodeId"
                saveAs: commissionerNodeIdAlpha

    - label: "TH1 writes ACL giving view privilege for descriptor cluster"
      command: "writeAttribute"
      attribute: "ACL"
      arguments:
          value: [
                  {
                      FabricIndex: th1FabricIndex,
                      Privilege: 5, # administer
                      AuthMode: 2, # case
                      Subjects: [commissionerNodeIdAlpha],
                      Targets:
                          [{ Cluster: 0x001f, Endpoint: 0, DeviceType: null }],
                  },
                  {
                      FabricIndex: th1FabricIndex,
                      Privilege: 1, # view
                      AuthMode: 2, # case
                      Subjects: null,
                      Targets:
                          [{ Cluster: 0x001d, Endpoint: 0, DeviceType: null }],
                  },
              ]

    - label: "Read the commissioner node ID from the beta fabric"
      identity: "beta"
      cluster: "CommissionerCommands"
      command: "GetCommissionerNodeId"
      response:
          values:
              - name: "nodeId"
                saveAs: commissionerNodeIdBeta

    - label: "TH2 writes ACL giving view privilge for basic cluster"
      identity: beta
      command: "writeAttribute"
      attribute: "ACL"
      arguments:
          value: [
                  {
                      FabricIndex: th2FabricIndex,
                      Privilege: 5, # administer
                      AuthMode: 2, # case
                      Subjects: [commissionerNodeIdBeta],
                      Targets:
                          [{ Cluster: 0x001f, Endpoint: 0, DeviceType: null }],
                  },
                  {
                      FabricIndex: th2FabricIndex,
                      Privilege: 1, # view
                      AuthMode: 2, # case
                      Subjects: null,
                      Targets:
                          [{ Cluster: 0x0028, Endpoint: 0, DeviceType: null }],
                  },
              ]

    - label: "TH1 reads descriptor cluster - expect SUCCESS"
      command: "readAttribute"
      cluster: "Descriptor"
      attribute: "DeviceTypeList"

    - label: "TH1 reads basic cluster - expect UNSUPPORTED_ACCESS"
      command: "readAttribute"
      cluster: "Basic Information"
      attribute: "VendorID"
      response:
          error: UNSUPPORTED_ACCESS

    - label: "TH2 reads descriptor cluster - expect UNSUPPORTED_ACCESS"
      identity: "beta"
      command: "readAttribute"
      cluster: "Descriptor"
      attribute: "DeviceTypeList"
      response:
          error: UNSUPPORTED_ACCESS

    - label: "TH2 reads basic cluster - expect SUCCESS"
      identity: "beta"
      command: "readAttribute"
      cluster: "Basic Information"
      attribute: "VendorID"

    - label: "TH1 resets ACL to default"
      command: "writeAttribute"
      attribute: "ACL"
      arguments:
          value: [
                  {
                      FabricIndex: 1,
                      Privilege: 5, # administer
                      AuthMode: 2, # case
                      Subjects: [commissionerNodeIdAlpha],
                      Targets: null,
                  },
              ]

    - label: "TH1 sends RemoveFabric command for TH2"
      cluster: "Operational Credentials"
      command: "RemoveFabric"
      arguments:
          values:
              - name: "FabricIndex"
                value: th2FabricIndex

Platform
other
Platform Version(s)
No response
Type
YAML tested, Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response

I suspect the problem here is that chiptool.py is not handling the --waitAfterCommissioning 5000 parameter as an integer, and passing it as a string to the lower layer.

CC: @vivien-apple


NIFI-4023, NIFI-4077: Addressed issue where repository was aging off …

…the wrong index. When it should age off Index 1, it was removing Index 2. As a result, the earliest index is never aged off, and the newest index could potentially be aged off before it is ready to be. Also addressed issue where a query that attempts to read an event that has aged off throws FileNotFoundException (NIFI-4077) instead of skipping over the event. The JavaDocs indicate that the EventIterator should skip records that it cannot find, but SelectiveRecordReaderEventIterator throw FileNotFoundException instead
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

on it.  Will let it run for a while.

seeing far better behavior on the flow i could cause these issues on.  Such as the one i posted in NIFI-3329.  Will monitor a bit more and if still good then merge

+1 will merge to master


support php8.1 ?

This bundle seams not maintained ?
Could you please add support for php8.1 in the composer file ?

nice, thanks


How to request the HPKS dataset?

Thank you for your work, Please ask how do I request the HPKS dataset from Johns Hopkins Hospital？

Hi, you may send an email to Prof. Shanshan Jiang (sjiang21@jhmi.edu). Currently, we are still working on obtaining the permission from JHH, which is the hardest part.

I I'm sorry I didn't get it. Is there a link or detailed description of the application related to this dataset, please? You have used the HPKS dataset in your article, why you are still working on obtaining the permission?

This is an in-house dataset. The data was acquired between 2010 and 2018 in Johns Hopkins Hospital. More information can be found at this paper (https://aacrjournals.org/clincancerres/article/25/2/552/125805/Identifying-Recurrent-Malignant-Glioma-after). We obtained consent from each subject to conduct research in JHH but releasing their information to public need additional permission.


dune_3: 3.16.0 -> 3.16.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ocaml/dune/releases.
meta.description for dune_3 is: Composable build system
meta.homepage for dune_3 is: https://dune.build/
meta.changelog for dune_3 is: https://github.com/ocaml/dune/raw/3.16.1/CHANGES.md
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.16.1 with grep in /nix/store/7aaxw9fdwbchkcag9c42fg2np8p8xmkl-dune-3.16.1
found 3.16.1 in filename of file in /nix/store/7aaxw9fdwbchkcag9c42fg2np8p8xmkl-dune-3.16.1

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

237 total rebuild path(s)

237 package rebuild(s)

First fifty rebuilds by attrpath

abella
acgtk
advi
alt-ergo
anders
beluga
cmdstan
coccinelle
comby
compcert
coq
coqPackages.Cheerios
coqPackages.CoLoR
coqPackages.ElmExtraction
coqPackages.HoTT
coqPackages.ITree
coqPackages.InfSeqExt
coqPackages.LibHyps
coqPackages.MenhirLib
coqPackages.QuickChick
coqPackages.StructTact
coqPackages.aac-tactics
coqPackages.atbr
coqPackages.autosubst
coqPackages.bignums
coqPackages.ceres
coqPackages.compcert
coqPackages.coq
coqPackages.coq-elpi
coqPackages.coq-ext-lib
coqPackages.coq-lsp
coqPackages.coq-record-update
coqPackages.coqeal
coqPackages.coqide
coqPackages.coqprime
coqPackages.coquelicot
coqPackages.coqutil
coqPackages.corn
coqPackages.deriving
coqPackages.equations
coqPackages.extructures
coqPackages.flocq
coqPackages.fourcolor
coqPackages.gaia
coqPackages.gappalib
coqPackages.hierarchy-builder
coqPackages.high-school-geometry
coqPackages.interval
coqPackages.itauto

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7aaxw9fdwbchkcag9c42fg2np8p8xmkl-dune-3.16.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/e6293a07ba7c38bac8537709ef84373b8fb8be2b#dune_3

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7aaxw9fdwbchkcag9c42fg2np8p8xmkl-dune-3.16.1
ls -la /nix/store/7aaxw9fdwbchkcag9c42fg2np8p8xmkl-dune-3.16.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @vbgl for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Could you please create a PR for 3.17.0? @r-ryantm


Exception thrown while trying to calculate math.log(0)

Bug Report
Current Behavior
math.log(0) raises ValueError: math domain error
Expected behavior/code
No exceptions raised while trying to calculate the log of a number too close to zero.
Environment

Python(s): Any I guess

Possible Solution
low = math.log(low) if low > 5e-324 else -750

Additional context/Screenshots
https://app.circleci.com/pipelines/github/DataDog/dd-trace-py/52341/workflows/776c836a-ea10-4af8-8154-236971fa72fc/jobs/3333537

Done in #103


[core] Why isn't there any window decoration under wayland?

Please, before submitting a new issue verify and check:

[X] I tested it on latest raylib version from master branch
[X] I checked there is no similar issue already reported
[X] My code has no errors or misuse of raylib

Issue description
When I run my application in X11 it works properly, but under Wayland I get this weird white border which is really weird. I did add -DUSE_WAYLAND=ON. When I read the logs, I cannot find anything related to that other then some random GLFW warnings that I cannot find anything on online. I even tried using the latest GLFW and latest Raylib and it didn't work either.
Warning: 'set target-async', an alias for the command 'set mi-async', is deprecated.
Use 'set mi-async'.
Running executable
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
INFO: Initializing raylib 4.6-dev
INFO: Supported raylib modules:
INFO:     > rcore:..... loaded (mandatory)
INFO:     > rlgl:...... loaded (mandatory)
INFO:     > rshapes:... loaded (optional)
INFO:     > rtextures:. loaded (optional)
INFO:     > rtext:..... loaded (optional)
INFO:     > rmodels:... loaded (optional)
INFO:     > raudio:.... loaded (optional)
[New Thread 0x7ffff0fff640 (LWP 23)]
[New Thread 0x7ffff07fe640 (LWP 24)]
[New Thread 0x7fffefffd640 (LWP 25)]
INFO: DISPLAY: Device initialized successfully
INFO:     > Display size: 2560 x 1440
INFO:     > Screen size:  850 x 500
INFO:     > Render size:  850 x 500
INFO:     > Viewport offsets: 0, 0
INFO: GLAD: OpenGL extensions loaded successfully
INFO: GL: Supported extensions count: 393
INFO: GL: OpenGL device information:
INFO:     > Vendor:   NVIDIA Corporation
INFO:     > Renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
INFO:     > Version:  3.3.0 NVIDIA 535.54.03
INFO:     > GLSL:     3.30 NVIDIA via Cg compiler
INFO: GL: VAO extension detected, VAO functions loaded successfully
INFO: GL: NPOT textures extension detected, full NPOT textures supported
INFO: GL: DXT compressed textures supported
INFO: GL: ETC2/EAC compressed textures supported
INFO: TEXTURE: [ID 1] Texture loaded successfully (1x1 | R8G8B8A8 | 1 mipmaps)
INFO: TEXTURE: [ID 1] Default texture loaded successfully
INFO: SHADER: [ID 1] Vertex shader compiled successfully
INFO: SHADER: [ID 2] Fragment shader compiled successfully
INFO: SHADER: [ID 3] Program shader loaded successfully
INFO: SHADER: [ID 3] Default shader loaded successfully
INFO: RLGL: Render batch vertex buffers loaded successfully in RAM (CPU)
INFO: RLGL: Render batch vertex buffers loaded successfully in VRAM (GPU)
INFO: RLGL: Default OpenGL state initialized successfully
WARNING: GLFW: Error: 65548 Description: Wayland: The platform does not provide the window position
WARNING: GLFW: Error: 65548 Description: Wayland: The platform does not provide the window position
WARNING: GLFW: Error: 65548 Description: Wayland: The platform does not support setting the window position
INFO: TEXTURE: [ID 2] Texture loaded successfully (128x128 | GRAY_ALPHA | 1 mipmaps)
INFO: FONT: Default font loaded successfully (224 glyphs)
WARNING: GLFW: Error: 65549 Description: Wayland: Window attribute setting not implemented yet
WARNING: GLFW: Error: 65548 Description: Wayland: The platform does not provide the window position
INFO: TIMER: Target time per frame: 6.944 milliseconds
INFO: FILEIO: [assets/Montserrat-Bold.ttf] File loaded successfully
INFO: TEXTURE: [ID 3] Texture loaded successfully (1024x1024 | GRAY_ALPHA | 1 mipmaps)
INFO: FONT: Data loaded successfully (60 pixel size | 95 glyphs)
INFO: FILEIO: [assets/Montserrat-Bold.ttf] File loaded successfully
INFO: TEXTURE: [ID 4] Texture loaded successfully (1024x1024 | GRAY_ALPHA | 1 mipmaps)
INFO: FONT: Data loaded successfully (60 pixel size | 95 glyphs)
INFO: FILEIO: [assets/user-circle.png] File loaded successfully
INFO: IMAGE: Data loaded successfully (48x48 | R8G8B8A8 | 1 mipmaps)
INFO: TEXTURE: [ID 5] Texture loaded successfully (48x48 | R8G8B8A8 | 1 mipmaps)
INFO: FILEIO: [assets/settings.png] File loaded successfully
INFO: IMAGE: Data loaded successfully (48x48 | R8G8B8A8 | 1 mipmaps)
INFO: TEXTURE: [ID 6] Texture loaded successfully (48x48 | R8G8B8A8 | 1 mipmaps)
[New Thread 0x7fffeda6a640 (LWP 26)]
[Thread 0x7fffefffd640 (LWP 25) exited]
[Thread 0x7ffff0fff640 (LWP 23) exited]
[New Thread 0x7fffefffd640 (LWP 27)]
[New Thread 0x7fffed269640 (LWP 28)]
WARNING: GLFW: Error: 65547 Description: Wayland: Standard cursor shape unavailable
WARNING: GLFW: Error: 65547 Description: Wayland: Standard cursor shape unavailable
WARNING: GLFW: Error: 65547 Description: Wayland: Standard cursor shape unavailable
WARNING: GLFW: Error: 65547 Description: Wayland: Standard cursor shape unavailable
WARNING: GLFW: Error: 65547 Description: Wayland: Standard cursor shape unavailable

Environment
Platform: Linux
OS: Fedora 38
OpenGL: No idea
GPU: NVIDIA 2080 Ti (535.54.03)
Issue Screenshot

Code Example
There's no point in sharing my code, it does it for any code I run even the simple one from the README.

I tested on my Steam Deck and it works.
I will test to see if it's GNOME  that's causing the problem, because the Deck is using KDE instead so that might be the cause of the problem.

After some research on my side I found that the problem was with Flatpak and not with Raylib itself.
In my flatpak config I was using --socket=fallback-x11 along side --socket=wayland . Sadly this was causing problems and one of my friend told me to try and replace --socket=fallback-x11 with --socket=x11 and keep --socket=wayland .
Without me really understanding why, it now works.

@Vysp3r Thanks for reporting the issue! Glad that now works as expected! 👍🙂


feat: add label operation metrics and improve test structure

Add new metrics for tracking label operations and annotations

pod_label_webhook_label_operations_total counter (success/skipped/error)
pod_label_webhook_annotation_validation_total counter (valid/invalid/missing)

Update webhook code to record new metrics during pod mutation
Add unit tests for new metrics
Improve integration test structure:

Extract common test utilities to test/integration/utils.sh
Add retries and better error handling for metric checks
Fix label ordering in metric queries to match Prometheus output

The new metrics provide better visibility into webhook operations and the test improvements make the integration tests more reliable and maintainable.
run-integ-test
Summary by Sourcery
Add metrics for label operations and annotation validation. Update the webhook to record these metrics. Improve integration tests by extracting common utilities, adding retries for metric checks, and fixing label ordering in metric queries.
New Features:

Added metrics for tracking label operations (success, skipped, error) and annotation validation (valid, invalid, missing).

Tests:

Improved integration test reliability and maintainability by extracting common utilities, adding retries to metric checks, and ensuring consistent label ordering in Prometheus queries.

@sourcery-ai review


Expose individual interventional outcomes from RegressionEstimator _do operator (#1011)

Original implementation of _do for RegressionEstimators calculated individual outcomes for all dataframe rows, and then returned the mean(). However, for many use-cases it is helpful to have the individual outcomes for further analysis. This commit moves the existing implementation (without changes) to a new function interventional_outcomes() which returns all outcomes. The implementation of _do() now only calls mean() on the returned values. The behaviour of _do() is unchanged.

@all-contributors please add @drawlinson as a contributor for code.


New theme for iSH

New Theme
Dracula for iSH

Hey, very cool! ✨
I just sent you an invitation to join the organization.
I also cloned your repository for Dracula's organization, so you can go ahead and delete or archive yours:

Your repository.
New repository.

Thanks for building this! 🎉

🧟 It's alive: https://draculatheme.com/ish


Error less often when native certificates fail to load on UNIX

In #24 when webpki-roots was refactored out, https://github.com/rustls/rustls-platform-verifier/commit/5351caaf0f9bf94fb7c3fdea4ffd9ac86dc24c93 changed how errors from rustls-native-certs were handled. Prior to the change, we logged any errors and continued onward. But today we return an error and fail out of verifier initialization when certificates from the system's CA bundle fail to parse. Combined with issues such as https://github.com/rustls/rustls-native-certs/issues/48, this can lead to more failure cases.
This PR proposes changing the behavior to do two things differently:

Load extra CA certificates before any from the system (will this be problematic? Which will take priority if they have the same key ID?)
If any extra certificates have been loaded, log an error like before. If no extra roots are available, return an error since no verification will be possible because the combined root store will be empty.

(will this be problematic? Which will take priority if they have the same key ID?)

Neither Rustls nor Webpki will do any de-duplication of trust anchors (by subject, or by subject public key information). The TrustAnchors are tried in the order they're added to the RootCertStore, so the extra CA certificates would be tried before the system provided copies. We don't presently parse or consider authority or subject key identifiers.
I don't believe this would cause any issues. Each CA certificate's subject and subject public key information will be processed independently until a valid path is found, budget for path building is expended, or all candidate CA certificates have been considered.


iOBC rootfs size increase

The iOBC's rootfs is currently limited to 20MB. This is exactly enough for everything when building the OS image, but leaves no extra room. Both monit and dropbear need to create temporary files in the rootfs as part of their initialization process, but that is now failing.
The U-Boot recovery/upgrade process currently limits the rootfs on the iOBC to just under 21MB (21,987,768 bytes). I'm bumping the rootfs max size to come closer to this limit.
"Why are you doing 21000K instead of 21MB?" - because they're not actually the same number.
21MB =><PHONE_NUMBER> => 22020096 (over limit)
21000K =><PHONE_NUMBER> => 21504000 (under limit)
"Why not 20.5MB?" - Because the arg parser doesn't allow decimal places
Other change in this PR: Fixing the default SLIP port for the iOBC.
The SLIP port is documented as /dev/ttyS1. Additionally, /dev/ttyS0 is the debug UART port, which we don't want to mess with

 iOBC rootFS free space too small for monit

 iOBC SLIP issues