Resolve parent packageInfo when using with monorepos

When resolving styles from a different package in a monorepo, the cwd package info was being used instead of the package info relative to the styles being imported.
Below is just a simple structure example of the setup I am having issues with. When changing the packageInfo to resolve to the parent package.json relative to the styles being imported, this fixes the issue since. The id being passed to the resolveId and the load functions are now the same (in the Vite plugin).
packages
	@package/styles
		sprinkles.css.ts
site
	pages
		index.tsx
	vite.config.ts

Hey 👋,
This was a conscience trade-off to prevent needing to resolve the packageInfo for every file in the project. I'm not sure it causes any issues in practice. Have you found any issues related to this?

I see now, yeah performing this for every file does seems very excessive (and expensive).
I am experiencing an issue trying to load .css.ts files across workspace packages. I have a monorepo setup with a Vite site and then a separate sibling packages directory. I want to be able to link the packages and load the files from outside website package during development. Vite seems to be handing the dep-scan step of finding the packages locally.
Currently, when the style files (.css.ts) are resolving, the path from the resoveId and load functions are different, causing the virtual transformed file to not return properly.
Open to alternative ideas or configurations if you suggestions on a better approach 😅

@samrose3 Interesting. Happy to take a look into this but I'll really need a reproduction of the issue. Would you be able to open an issue with a reproduction and we can work out next steps there?

Certainly, I'll setup a test repo to reproduce and demo 👍 Thanks Matt!


feat: data augmentation while training models

Adds function which augments data during training.

Hello @hasibzunair! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file decavision/model_training/tfrecords_image_classifier.py:

Line 437:9: E722 do not use bare 'except'

Not sure how to fix the PEP8 issue. I've formatted the script using autopep8 filename.py --in-place.

Not sure how to fix the PEP8 issue. I've formatted the script using autopep8 filename.py --in-place.

This message is because there is a try/except where the except doesn't specify what error types to look for. This is not favored but we can leave it like that.

Can you please add a parameter in the class to decide if we augment the data? It can be set to True by default but it's good to have it for people who want to use the offline augmentation feature of the library for reproducability purposes for example.

Added.

Yay!


Make tsserver.js a library

VS Code (and probably others) currently consumes both tsserver.js and
typescript.js, even though they have essentially the same content.  This
change makes it possible to use tsserver.js for both purposes, by
suppressing the server startup code (including requires) and adding a
declaration file (stripped of internals).

I bet there's a cleverer way to skip the body of server.ts and I'd be happy to hear it.

FYI @mjbvz, hopefully, this will save VS Code 8MB or so.

Do I need to hook the new .d.ts file up to some sort of baseline/validation system?

If we're considering this, the tsserverlibrary build is already this minus the startup code - perhaps we should just merge them?

@weswigham What does "merge them" mean in this context?  Drop tsserverlibrary?

tsserverlibrary's build tasks already have the declaration files and API baselining set up - so copying the conditional startup code into the tsserverlibrary entrypoint, then renaming it to tsserver, I imagine.

I've done my best to port the functionality of tsserverlibrary to tsserver, but they had slightly different watch functionality, so it might not be exact.

Force update was just a rebase.  No manual merging required.

There's a weird quirk there actually - unless we manually delete it next time we update the LKG, we'll continue to ship the old one.  (See also https://github.com/microsoft/TypeScript/pull/39330)

AFAIK when we rewrote the LKG script, the only reason it doesn't automatically delete dead files was because there was some .json document or something which seemed dead but was also potentially consumed by VS (and may even be gone by now - or I could be thinking of typesMap.json, don't know), IIRC from a conversation from years ago.

This would be a hack, so we're not going to pursue it.


NEOSserver

This adds a way of solving jsLPSolver problems with CPLEX hosted at the NEOS Servers.
However, it isn’t a stable solution for Problems having spaces and special characters in their variable names as GAMS does not allow them.
I was thinking about translating the jsLPSolve model object into a separate object featuring safe variable names, but as I’m just programming as a hobby I don’t know whether this would be the best way to deal with this issue.

This is interesting but I think that it is outside the scope of the solver. You should make a new repository with the solver as a dependency.

Alright that makes sense! Will do that


Docs and build version hosted on builds.dockyard.com out of sync?

I have no ember cli project, so I would like to consume ember-validations from here http://builds.dockyard.com/
Can it be, that the current documentation do not match the version build on the server?
For example, the property "dependentValidationKeys" mentioned in the docs (https://github.com/dockyard/ember-validations#creating) in not present in the build version, its only "_dependentValidationKeys".
Now I have the feeling, that the build version is not up to date.
By the way it makes no difference if I choose
http://builds.dockyard.com.s3.amazonaws.com/ember-validations/ember-validations-latest.js or
http://builds.dockyard.com.s3.amazonaws.com/ember-validations/release/ember-validations.js
Thank you

I am going to close this issue for now, feel free to reopen this issue if you feel like it's still relevant and we should take a look at it.


Upload land-use raster database to GeoServer (2)

Check metadata is clean and CF conformant.

Did you have a specific project in mind? NRCan and USGS have country-specific data. Most of the popular projects date back a few years (< 2010) and those with global coverage don't typically have high-resolution (~0.5 Km for MODIS).
Also, GeoTIFFs don't have fields for integrated metadata and GeoServer metadata doesn't allow fields for categories like facet, simulation, history, etc. I'm not sure what you mean here.

@richardarsenault ?

@richardarsenault
I'm also curious to see if we could clarify this matter. I can manually create NetCDF containers from GeoTIFFs but it is relatively labour-intensive. If this is data must be searchable within the facet list, we need to propose a few conventions/practices. Is there a land use raster project you already have in mind?

As we discussed at the kick-off meeting, we are likely best to go forward with the Landsat-based CEC Land Cover 2010 land use raster. This can be integrated into the CRIM infra as soon as Thursday.

Well that's beautiful, because CEC and NRCan!

I've managed to upload the CEC LandCover 2010 dataset to one of the crim testing servers (starts with a 'c') but the data is in a custom projection so I had to add a new custom CRS definition (100004) to the geoserver's epsg.properties. In order for it to load, the geoserver instance needs to be restarted. If someone could restart the geoserver, I can confirm that the land use data is working and we can close this issue.
@ldperron could you restart the geoserver?

Excellent, thanks Trevor!
Have a great weekend!
Richard
Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Trevor James Smith<EMAIL_ADDRESS>Date: 2018-11-09  15:50  (GMT-05:00) To: Ouranosinc/raven<EMAIL_ADDRESS>Cc: richardarsenault<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Ouranosinc/raven] Upload land-use raster database to GeoServer (2) (#3)
I've managed to upload the CEC LandCover 2010 dataset to one of the crim testing servers (starts with a 'c') but the data is in a custom projection so I had to add a new custom CRS definition (100004) to the geoserver's epsg.properties. In order for it to load, the geoserver instance needs to be restarted. If someone could restart the geoserver, I can confirm that the land use data is working and we can close this issue.
@ldperron could you restart the geoserver?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Ouranosinc/raven","title":"Ouranosinc/raven","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/Ouranosinc/raven"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Zeitsperre in #3: I've managed to upload the CEC LandCover 2010 dataset to one of the crim testing servers (starts with a 'c') but the data is in a custom projection so I had to add a new custom CRS definition (100004) to the geoserver's epsg.properties. In order for it to load, the geoserver instance needs to be restarted. If someone could restart the geoserver, I can confirm that the land use data is working and we can close this issue.\r\n\r\n@ldperron could you restart the geoserver?"}],"action":{"name":"View Issue","url":"https://github.com/Ouranosinc/raven/issues/3#issuecomment-437490951"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/Ouranosinc/raven/issues/3#issuecomment-437490951",
"url": "https://github.com/Ouranosinc/raven/issues/3#issuecomment-437490951",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [Ouranosinc/raven] Upload land-use raster database to GeoServer (2) (#3)",
"sections": [
{
"text": "",
"activityTitle": "Trevor James Smith",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@Zeitsperre",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "Ouranosinc/raven",\n"issueId": 3,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "Ouranosinc/raven",\n"issueId": 3\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/Ouranosinc/raven/issues/3#issuecomment-437490951"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 340848294\n}"
}
],
"themeColor": "26292E"
}
]

@Zeitsperre Hi, any news on this front?

@richardarsenault I'm still waiting to hear back from CRIM. I just asked on slack if someone could perform the last step to verify that it works. I'll let you know by tomorrow.

It's been updated and it seems to be working. The data simply needs to be synced between servers at CRIM and we should be able to cross this off.

@Zeitsperre Status ?

@Zeitsperre Status ?

@huard The raster is present on a CRIM testing server. I'm blocked at the moment on the Ouranos production server as the layer uses a custom projection that needs to be configured within the GeoServer files. I need to wait on @moulab88 to create a user_projections folder within /data/geoserver folder that I have write access to before I can get the layer online.

Fixed with #112


Plot.text, when rotated, interprets dx and dy differently from other marks

When you rotate Plot.text, the x and y attributes is correctly interpreted as horizontal and vertical positions, but the dx and dy seems to be switched.
Plot.plot({
  x: {domain: [-10,10], grid:true},
  y: {domain: [-10,10], grid:true},
  marks: [
    Plot.frame(),
    Plot.text([1], { x: 5, y: 0, dx: -50, dy: 0, rotate: -90, text: ["test"]}),
    Plot.dot([1], { x: 5, y: 0, dx: -50, dy: 0})
  ]
})

I would expect the dot and the text to be in the same position.

This is the expected/intended behavior.

Interesting. Fair enough, but it felt strange that x and y are not affected by the rotation, but dx and dy are...
But if that is intentional and/or intuitive to others, I will adapt :-)

It's not intuitive, but it's the SVG spec. Very useful when your text follows a text-path and needs to be a little above the path:


Where is the WSL2 Version?

I couldn't find a WSL2 version of ArchWSL
After downloading the latest release (appx) and installed it, it is still wsl1.

ArchWSL also works with WSL2.
run wsl --set-version Arch 2 in shell

@yuk7 I ran this command and here comes an error :(

Error: 0x80041002

Make sure the Windows virtualization platform and Intel-VT/AMD-V are enabled.

It's already enabled @yuk7

hmm...
Could you run msinfo32.exe and show me the related items of Hyper-V in System Summary?

@yuk7 sure thing
processor: intel core i7 9700
summary:
名称	Hyper-V RAW
无连接服务	否
保证送达	是
保证顺序	是
最大地址大小	36 字节
最大消息大小	0 字节
面向消息	否
最小地址大小	36 字节
面向虚拟流	否
支持广播	否
支持连接数据	否
支持断开连接数据	否
支持加密	否
支持加速数据	否
支持特权关闭	是
支持保证的带宽	否
支持多播	否
(do i need to set my system to english so that it can display terms in english?)

Don't worry.
Changing the settings is troublesome, so you can leave it as it is.
I'm Japanese and can read a little Chinese characters.

Probably,It's another page.
The System Summary is at the top of the left sidebar.

@yuk7 do you mean these terms?
基于虚拟化的安全性	正在运行
安全属性要求基于虚拟化的安全性
安全属性可使用基于虚拟化的安全性	基本的虚拟化支持, DMA 保护, UEFI 代码只读, SMM Security Mitigations 1.0, 基于模式的执行控制
已配置基于虚拟化的安全服务
正在运行基于虚拟化的安全服务
设备加密支持	设备自动加密失败的原因: TPM 不可用, 不支持 PCR7 绑定, 硬件安全测试界面失败，设备未处于现代待机模式, 检测到不允许使用的具有 DMA 功能的总线/设备, TPM 不可用
已检测到虚拟机监控程序。将不显示 Hyper-V 所需的功能。

yes.
It seems that those items are hidden...
I couldn't see the information I wanted.

@yuk7 what information do you want? I can find it for ya

@Asiimoviet please look at this issue.
And please try to avoid communicate using Chinese on GitHub... Maybe you should consider switch your Windows display language to English for English troubleshooting info.
既然您再用WSL，相信也是有此实力的！❤

I'm running a ArchWSL on WSL2 and this is what I get from msinfo32.exe, just for your infomation:
Virtualization-based security	Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, Mode Based Execution Control
Virtualization-based security Services Configured
Virtualization-based security Services Running
Device Encryption Support	Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

yep.
I thought I could see the status of Hyper-V&Virtualization from there, but it was my mistake.

@escape0707 I tried and did not work. I completely shut down windows defender and firewall. Quitted all my proxy.
@yuk7 btw i enabled the virtualmachineplatform feature through this command
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

and tried that again. Unfortunately that did not work. Still getting the same 0x80041002 error.

 Like check whether port 53 is free and backup you WSL 1 Arch - uninstall - completely disable WSL feature and re-enable - reinstall and recover from backup?

@escape0707 I set the default version of wsl to 2 and uninstalled arch. after then, re installing it using arch.exe and the same error popped out.

https://github.com/microsoft/WSL/issues/5329#issuecomment-638982097
https://github.com/microsoft/WSL/issues/5329#issuecomment-639146874

@escape0707 I have read through that issue page and found out that most of them are having problem with that COMODO firewall. Unfortunately I don't have that installed. Interestingly, one of the post mentioned that the comodo firewall is having problem with something called the loopback problem. I am using clash for windows as my proxy and it has that problem as well (that makes my UWP apps unable to connect to the internet). I tried shutting down and completely uninstalled clash but that didn't work even after a reboot of my system.
About the 2 comment you posted:

I tried running that command but it turns out that there is nothing occupying my 53 port:

Get-NetUDPEndpoint: No MSFT_NetUDPEndpoint objects found with property 'LocalPort' equal to '53'.  Verify the value of the property and retry.
Get-Process: Cannot bind argument to parameter 'Id' because it is null.

I took the WSL log from Windows Feedback, hoping that might help:
https://aka.ms/AAaf293

@Asiimoviet Well, I'm not a Microsoft employee so I don't have the authority to view your feedback, you should check " Save a local copy of xxxx"

and attach that log file here.
By the way, there should be 3 .etl file in it and you can download Windows Performance Analyzer to inspect it.
Talking about Clash For Windows, I have it on my device, too and it seems not causing any WSL problem. But you can try to remove all app's loopback restriction anyway since you also experienced UWP app proxy failure. The CFW proxy software has already included a utility to do this.

@escape0707 appx

I used scoop and zip. Maybe you want to give zip installation a try?

omg, just encountered a situation which neither of wsl and arch.exe is responsive.

There are so many of those folders. I reran the capture and took the folder that is closest to the time i was doing the test.
See if this could help @escape0707
Critical_{1B96BCC2-1B1B-4_ce5eb7b0111624146853d1dedaaa1f66bf82b7ea_00000000_cab_d3331430-10c8-4b0d-8b81-841ffd9d92e1.zip

I just tried the zip install and it doesn't work as well

Oof, sorry, completely my bad: WSL team updated their CONTRIBUTION.md so that the original instruction to capture a shorter .etl log has been removed and they're recommending people to use the Feedback Hub app... I didn't realize that...
The original method to capture a log and some people identify the source of their problem is in the older version of the CONTRIBUTION.md. Sorry for not checking that by myself first and the waste of your time.
See if we can find something suspicious following the original way they tried.

Turns out other distro has the same issue. Imma go open a new issue in their wsl repo. thx for your help 👍
@escape0707 @yuk7

@Asiimoviet you should send these info into the issue I first referred before.

WSL 2 requires an update to its kernel component I get when I try to update, both using the
wsl --set-version Arch 2

wsl --set-default-version 2

Both gives same error. Have turned on everything. I just dont get it.

Never mind, had to man download kernel update. Working now wsl2

What is the difference between WSL2 version in this repository and original ArchWSL2 in  yuk7/container-systemd-init-tool

What is the difference between WSL2 version in this repository and original ArchWSL2 in  yuk7/container-systemd-init-tool


Cleanup for session tables doesn't run

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When a user deletes the browser local storage session, new sessions are created in auth.sessions table for that users even if one already exists.
This PR #875 was added to cleanup the session tables.
I can see the cleanup SQL runs on every request. This is the SQL for the session table (there is similar SQL for the other tables) cleanup in this code
fmt.Sprintf("delete from %q where id in (select id from %q where not_after < now() - interval '72 hours' limit 10 for update skip locked);", tableSessions, tableSessions)
However the column not_after allows nulls and has nulls for the session data in the session table and I can't see in the code where it ever gets a value? So the cleanup will never happens?
This is where the column not_after was added which also said its not used PR #810
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Login using Supabase auth
Check session is created in auth.sessions table
Delete session data from browser local storage. This forces browser logout
Login again using same user
Check auth.sessions. There is 2 sessions for the same user.

Expected behavior
All related unused session/token data to be cleaned up/deleted from supabase. This also counts towards database storage.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: Mac
Browser: Safari
Version of supabase-js: 2.25.0
Version of Node.js: 18.16.0

Additional context
I came across this because I was looking into how you could see what active sessions there is. Is there another way to do this?

The not_after column is used only when using SSO and the identity provider has specified an absolute time.
Please enable the new single session per user or inactivity timeout / timeboxing features to get the cleanup of sessions.
https://supabase.com/docs/guides/auth/sessions#limiting-session-lifetime-and-number-of-allowed-sessions-per-user


wchar_t is 32 bits for Windows targets.

The wchar_t type is 4 bytes wide when building for Windows on Linux platforms. My understanding is that wchar_t is supposed to be 16 bits / 2 bytes on Windows platforms, as a simple C program shows:
david@pc1:/tmp$ cat size.c
#include <stddef.h>
#include <stdio.h>

int main() {
	printf("%lu\n", sizeof(wchar_t));
	return 0;
}
david@pc1:/tmp$ gcc size.c -o size && ./size
4
david@pc1:/tmp$ x86_64-w64-mingw32-gcc size.c -o size.exe && wine ./size.exe
2

Trying to run the tests with cargo test --target x86_64-pc-windows-gnu confirms something is wrong as I get this:
error[E0308]: mismatched types
 --> tests/wchar_t.rs:4:45
  |
4 | const _: fn(wchar_t) -> libc::wchar_t = |x| x;
  |                                             ^ expected `u16`, found `i32`
  |

That's interesting, the wchar_t in the procedural macro implementation comes from libc. It simply uses a trait to determine the type based on the one in the libc crate.
There is probably an issue occurring related to the separate build stages of the library. I don't have a Windows machine on hand so I'll need to set up a VM to investigate.

What I'm guessing is happening is that the macro is built for Linux platforms and hence gets a ì32 as wchar_t type regardless of the target platform of the library/executable being built.


internal/worker/server: return an error on depsolve timeout (HMS-2989)

Fixes the special case that if no worker is available and we generate an internal timeout and cancel the depsolve, including all followup jobs, no error was propagated.
For details, see https://issues.redhat.com/browse/HMS-2989
Now all jobs (in the DB) are set to "failed":

All jobs entries get a "job_error" in the result as well as
started_at and failed_at are set to "now" and
token is set to a random UUID to comply with the DB schema

This pull request includes:

[x] adequate testing for the new functionality or fixed issue
[x] adequate documentation informing people about the change such as

[x] submit a PR for the READMEs listed here
[x] submit a PR for the osbuild.org website repository if this PR changed any behavior not covered by the automatically updated READMEs

This is set to draft for now until:

I get feedback that this approach is ok
tests are implemented
we decided on if we should "create a separate metrics" (see comment in the code)

On the frontend this looks like this:

@croissanne last question for me is:
should we create separate metrics? maybe in a followup PR?
func (s *Server) SetFailed(id uuid.UUID, error *clienterrors.Error) error {
	/* create a separate metrics?
…

@croissanne last question for me is: should we create separate metrics? maybe in a followup PR?
func (s *Server) SetFailed(id uuid.UUID, error *clienterrors.Error) error {
	/* create a separate metrics?
…

I don't think that's necessary, the jobs will be marked as failed like any other job. As long as the job isn't marked as "userinputerror" it should trigger alerts and all that. Plus at that point presumable the depsolve job duration alert would also fire.
https://github.com/osbuild/osbuild-composer/blob/6ccfc7f81884eedbf3290bb2118d0c6e31c676d5/internal/worker/clienterrors/errors.go#L73-L111

…rebased


How to build elan on windows

I figured out that I needed a windows friendly version of perl from https://strawberryperl.com/ because the one in "c:\Program Files\Git\usr\bin\perl.exe" doesn't work for some reason. So the openssl configure steps now works.
But the build still fails with this:
error: failed to run custom build command for `elan-dist v1.11.0 (D:\git\leanprover\elan\src\elan-dist)`

Caused by:
  process didn't exit successfully: `d:\git\leanprover\elan\target\debug\build\elan-dist-6a05c90498e27db7\build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NotPresent', src\elan-dist\build.rs:8:50
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

Possibly because these environment variables are not defined?
    let out_dir = PathBuf::from(env::var_os("OUT_DIR").unwrap());
    let target = env::var("RELEASE_TARGET_NAME").unwrap();

If so, what  should these be set to and why do I need to set them, and we need a readme to explain what to set them to, etc.

I tried the vcpkg route to build openssl but it doesn't solve the problem.


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^17.1.2 remove ^17.1.1 (devDependencies.semantic-release)

:tada: This PR is included in version 1.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add ident description

Hi,
In this PR we add a new attribute called "description" to identifier for better user experience. For example, we will return something like following in resource leak message.

The highlighted message is the description of the resource leaked identifier.
We think the whole Infer community could benefit from it. Please let us know your feedbacks! We can do proper changes accordingly.
Thanks!

I'm a bit worried about the performance implications of such a change. Moreover, except in C#, every ident created will get a "None" description added to it. I think this is more the job of individual analyses to keep track of where values came from to report sensible messages. For example, in Pulse we solve this issue by introducing a "decompiler" that keeps track of where values came from. I would prefer a similar solution here too: you could add an element to your abstract domain that records this kind of information for each ident.

We can remove this PR; we switched over to Pulse resource leak.

Closing as per @matjin comment


bump up the default runtime to "io.containerd.runc.v2"

The former default runtime "io.containerd.runc.v1" won't support new features
like support for cgroup v2: containerd/containerd#3726
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

/test pull-cri-containerd-windows-cri

/test pull-cri-containerd-node-e2e

@jterry75 @Random-Liu thoughts on PRs that hit _unix isms. As a general rule, should we try to shadow/pair another PR to do the windows equivalent changes or make suggestions for the windows equivalent in the PR if amenable/doable.

We need to make sure the Docker and containerd packages on OS distributions contain the new shim binary.

We need to make sure the Docker and containerd packages on OS distributions contain the new shim binary.

Would be nice if we had an official line of communication for the distributions, where we could get feedback / verification.

I think we can just mention that in v1.4 release note.

@mikebrow Windows stuff is unrelated to this PR. Windows doesn't use io.containerd.runc.v%d.

@mikebrow Windows stuff is unrelated to this PR. Windows doesn't use io.containerd.runc.v%d.

ok

I think we can just mention that in v1.4 release note.

true...still would be nice to give them a heads up if they are not watching master changes.

updated docs

We need to make sure the Docker and containerd packages on OS distributions contain the new shim binary.

cc @thaJeztah Who is managing Docker containerd.io package?

cc @thaJeztah Who is maintaining Docker containerd.io package?

I can have a look at that one; plan was to open-source the repo soon (think there's one remaining PR for that)

/lgtm


Use progress bars to indicate docker operation progress

After #89 is done, deisrel will do multiple docker operations at once. Instead of just printing the raw event stream out to stdout, this issue is for using a progress bar like github.com/cheggaaa/pb.
Note that the number of steps each operation will require is not known a priori, so we may have to use a different type of progress bar - one that indicates the name of each operation, but not a definitive endpoint, for example.

deisrel no longer uses docker, so this is no longer needed.


issue about “element_bits,int_bits,additional_bits"

您好,作者!
很抱歉又一次打扰到您.
在您的代码中:https://github.com/SamuelGong/FLASHE/blob/master/encrypt_test/final_big_table.ipynb 请问element_bits,int_bits,additional_bits分别代表什么?  对这些位数的设置有要求吗?
以及在https://github.com/SamuelGong/FLASHE/blob/master/federatedml/secureprotol/jzf_quantize.py 中 关于  batch_size = int_bits // element_bits 这个又是怎么去理解呢?
期待您的回复!

Hi there,
Sorry for the confusion and ambiguity caused.
Meaning of the Variables in final_big_table
Specifically, element_bits is a configurable parameter which means how many bits do you wish to use for representing a floating-point number, whenever quantization is needed for encryption (i.e., FLASHE/Paillier/BFV). For example, setting it as 16 means that when using the above-mentioned encryption scheme, a floating-point number will be quantized into a 16-bit integer.
In the original final_big_table, both additional_bits and int_bits are defined dynamically, i.e., a user is not expected to configure them. First, additional_bits means how many should we additionally preserve for the sum to avoid overflowing. As a concrete example, suppose that you have two 3-bit quantized integers: 4 (whose binary representation is 100) and 5 (whose binary representation is 101). Adding them up we obtain 9, whose binary representation is 1001 and cannot be represented using only 3 bits. In this case, we need to expect 1 additional bit to the two operands, i.e., we need to take the two operands as two 4-bit integers (0100 and 0101). 4 is thus the conceptual number of bits each quantized integers have, and we call it int_bits, i.e., element_bits + additional_bits.
Meaning of the Variables in jzf_quantize
As for the int_bits and element_bits in jzf_quantize.py, they actually have totally different meanings from those mentioned above. To be exact, int_bits actually means how many bits are there in a batch of encrypted integer, while element_bits is a bit complicated:
(i) at first (when it serves as the argument of the function), it is the same as what we mentioned above, e.g., at https://github.com/SamuelGong/FLASHE/blob/d18303bbb088bf416c9d81aa1c8a13857867758a/federatedml/secureprotol/jzf_quantize.py#L136
(ii) it then accepts in-place modification with its meaning changed to the conceptual number of bits each encrypted integer in the batch have, e.g., at https://github.com/SamuelGong/FLASHE/blob/d18303bbb088bf416c9d81aa1c8a13857867758a/federatedml/secureprotol/jzf_quantize.py#L137
Conclusion
I hope that these explanations help you better follow the logic of our code and facilitate your experiments. To improve the readability of final_big_table.ipynb, we have just conducted code reframing, please check it out and see if it helps, too.


Schema rename suppress types

First part of the implementation described in pull request #828 and issue #810, covering just 1-0 renaming for types (aka suppressing types). I'm going to read over the changes here first and then when it's ready, I'll mark it as ready for review

Summary:

Implement type suppressions (so no field renamings, 1-many, suppressions etc just yet)

Checking for any illegal schema state that can arise just from suppressing types (see the new Visitor class I wrote)

Tests for both successful type suppression & illegal schema state errors

Small adjustments to test input strings and other tests that use these input strings to make sure the tests say what we think they say (e.g. confirming that suppressing all types in a union is why it raised an error, and not because we suppressed every type in the schema, all of which happen to be a member of that union).

Type hinting rename_schema

Not sure what's going on with the failing CI tests-- is this a known issue? Doesn't seem like anything in this PR would prevent them from running and the internet hasn't brought up much yet.

That makes sense-- since this'll break it into several smaller PRs, I'll also be able to incorporate some of the comments that I hadn't touched previously.
Here's how I plan to split it up:

[ ] type-hints for existing code, no functionality changes. Also removes type-hints from Args section in comments) as Selene mentioned.

[ ] Replace return None with return IDLE in the visitor functions because the GraphQL-core library defines that constant for us. Also would involve creating the VisitorReturnType which we'll need later anyways. No functionality changes.

[ ] Actually implement type suppression: possibly including the helper function mentioned here if it's not too long and plays nice with the existing tests here. Functionality change

[ ] Tests for type suppression will probably be in a separate PR opened at the same time as the type-suppression implementation.

Sounds great!

Now that PR 858 and 859 are out in draft form, all the significant changes described here have either already been merged or exist in one of those two PRs so I'll close this PR and delete this branch when we're done. For the time being, though, I'll keep this open until those two get merged jus tin case there's something here that I've missed by mistake.

Converting to draft because PRs 858 and 859 (plus a bit more work with enums and interfaces) will supersede the work here.


Create dependabot.yml

Let's try enabling dependabot!

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (d9a387f) to head (2325163).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #24   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines         1932      1932
=========================================
  Hits          1932      1932

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


Allow channel exceptions to be rescuable

Feature
Description
Exceptions in reflexes are currently logged and swallowed. This will give reflexes the ability to handle the exceptions via rescue_from in much the same manner as you would with ActionController.
Why should this be added
We'd like to track reflex errors via an external exception tracker, but the errors are currently swallowed with no chance to handle them.
This PR allows you to use rescue_from in reflexes thusly:
class MyTestReflex < StimulusReflex::Reflex
  rescue_from StandardError do |exception|
    ExceptionTrackingService.error(exception)
  end

  # ...
end

Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

Thank you for making StimulusReflex a better library, @dark-panda. This PR is excellent.


feat: Add text area counter

Allows users to toggle counter

They are responsible for passing in the counter & maximum counter.

There are ways to automate this process but I don't recommend since the checks are going to happen VERY frequently.

closes #2292


Dismissable Modal/Dialog is dismissed when clicking on other portals

Provide a general summary of the issue here
When using react-aria-component's Modal with a custom ModalOverlay and its contents include an element that also portals, the dialog is dismissed when the OTHER portals are clicked. I'm guessing this is because those 3rd party tools don't stop propogation of their click events, but I don't have control over that...
🤔 Expected Behavior?
I'd expect that the Dialog/Modal will only dismiss if the click event starts on the ModalOverlay.
😯 Current Behavior
Any click event on a portal above ModalOverlay in context causes the dismissal of the opened modal.
💁 Possible Solution
No response
🔦 Context
I'm attempting to improve accessibility in the codebase by introducing react-aria; however, it's been a frustrating experience because it feels like it's all or nothing. For example, unrelated to this issue, onPress vs. onClick makes types a pain in the neck and I basically need to use usePress or useButton all over the codebase. In this scenario, there are multiple form elements which portal from MUI and any interaction causes them to get dismissed 😭
🖥 Steps to Reproduce
https://stackblitz.com/edit/react-ts-rewjnk?file=Modal.tsx
Version
latest
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Going to close as dupe of https://github.com/adobe/react-spectrum/issues/5916
Please continue the discussion in that issue.


Mandatory Calculation?

Hello
Do we still HAVE to do a calculation request on or after the end of the obligation date so that HMRC knows that we have complied?  Or has that been resolved?

Yes, you must provide the financial data for the whole obligation period and request a calculation to meet your Obligation.

OK, thanks
I would really really really recommend when you release the API, you also release a standard workflow to navigate through it.
Even though you are refining the structure and content of the Developer Hub, it still doesn't have anything useful in there about actual usage of the APIs.  All it would take is a Behaviour section that says POSTing of the tax calculation is a mandatory step for obligations to be met due to the HMRC implementation.
I can't emphasise enough how this is NOT what we would have done had you not mandated it, and it's not obvious from the API that this is indeed mandatory.

I agree 100%

Even though you are refining the structure and content of the Developer Hub, it still doesn't have anything useful in there about actual usage of the APIs. All it would take is a Behaviour section that says POSTing of the tax calculation is a mandatory step for obligations to be met due to the HMRC implementation.

I can't emphasise enough how this is NOT what we would have done had you not mandated it, and it's not obvious from the API that this is indeed mandatory.

Thanks for your feedback. I understand your concern with regards to combining obligation check with triggering of calculation. We would take this feedback to business.

Thanks @saurabharora80  - I have moaned about that unfortunate coupling so much I think HMRC have tuned me out now !  :o)
But the point I was making was more to make sure you over-inform in the API documentation.  At the moment it reads as if you've all forgotten we have to build something from it.  Large pieces of critical workflow and transaction requirements are not clear or obvious or written down.
It makes my life really really difficult and tiresome - when someone, somewhere in HMRC knows this and all they have to do it write it down and we'd all get that insight.

We have added a paragraph about meeting the Obligations in our latest documentation which talks about the (unfortunate) coupling between calculation trigger and meeting obligation.
I have included that snippet below.
"
To meet their obligations, taxpayers are required to submit regular financial updates for each of their businesses. Typically these updates cover four 3-month obligation periods, with one set of obligation periods per business per accounting period. To meet the taxpayer's obligation for a particular obligation period for a business:

Supply summarised transactions for income and expenditure for the the whole of the obligation period for that specific business
Request a tax calculation
"

Please advice what you think is missing from it?

That text would help matters, but can I ask where you got that text?    I'm looking at the developer hub and I can't find that anywhere.

Given the following:

To meet their obligations, taxpayers are required to submit regular financial updates for each of their businesses. Typically these updates cover four 3-month obligation periods, with one set of obligation periods per business per accounting period. To meet the taxpayer's obligation for a particular obligation period for a business:

Supply summarised transactions for income and expenditure for the the whole of the obligation period for that specific business
Request a tax calculation

Would you please clarify whether triggering a first calculation in a 24 hour period will prevent a subsequent recalculation within the 24 hour period?

@P-Tracy The text can be found in the 'Overview' section of our currently LIVE Documentation here

@andyws I have raise a separate issue for this, as it goes beyond the scope of the original query.

Thanks @saurabharora80
I'm sure you hate me by now .... but that's really not where I would look to find that information, but that may just be me!

feel free to close!

@P-Tracy Interesting. Where would you like to see it?

My automatic point of reference was the 'met' attribute on the Obligation response.  I expected it to describe what the behaviour of it was, and how it was switched from true to false.
I do keep moaning about the same things, but when an API has a boolean of 'word' = true/false, it is less than helpful for the description to say this:
"True if this obligation period has been met; false otherwise" as this is just a combination of the same words again - I can get that from the raw API and payload.
What I would look for here is what triggers is from one to other, and the associated behaviour.
I also have an outstanding question relating to the transition and how the consumer is made aware of the success/failure and the reason for the failure, but hopefully that would be answered separately (and then added to the 'met' description as a bonus) ......

@P-Tracy your last question is linked to #343. It has been raised to TDG. Please watch #343 for updates.

Yes, thanks!

Feel free to close this one!


Difficulties with pypi_attestations verify

Hi,
I'm looking to use PEP 740 attestations in Sphinx, using the pypi_attestations CLI. The signing and inspection steps seem to work, but I've had some trouble with verify. Hopefully there's an opportunity to improve documenation or guidance:

Running verify dist/*.publish.attestation fails with an unhelpful error. This was my first approach, as I wanted to run sign-inspect-verify consecutively in GHA, and the inspect command runs on .publish.attestation files. Similarly, running verify dist/* fails with the same error -- perhaps the tool could check if the extension is already .publish.attestation, and if so skip that file?
$ python -m pypi_attestations verify dist/*.publish.attestation --identity ...
dist/sphinx-8.1.0-py3-none-any.whl.publish.attestation.publish.attestation is not a file.
$ python -m pypi_attestations verify dist/* --identity ...
dist/sphinx-8.1.0-py3-none-any.whl.publish.attestation.publish.attestation is not a file.

pypi_attestations inspect doesn't tell me what value I should be using with --identity (I don't know if this is possible, though). The example on README uses an email, so I tried the email I use for commits, which failed.

The failure for an incorrect --identity key is obscure and confusing ("Certificate's SANs do not match"):
$ python -m pypi_attestations verify dist/*.whl --identity<EMAIL_ADDRESS>Verification failed for dist/sphinx-8.1.0-py3-none-any.whl: Verification failed: Certificate's SANs do not match<EMAIL_ADDRESS>actual SANs: {'https://github.com/AA-Turner/sphinx/.github/workflows/create-release.yml@refs/heads/attestations'}
Verification failed for dist/sphinx-8.1.0.tar.gz: Verification failed: Certificate's SANs do not match<EMAIL_ADDRESS>actual SANs: {'https://github.com/AA-Turner/sphinx/.github/workflows/create-release.yml@refs/heads/attestations'}

At the least expanding the initialism so that I can look up what a SAN is would be helpful. The key for "actual SANs" is a hyperlink, which doesn't look like the example of the verify command on the README.

Failures to verify in CI don't exit with a non-zero status code, so GHA reports all is well -- this seems wrong.

Using the "actual SAN" hyperlink as the value for --identity works, but it is unclear how to auto-generate this for verification purposes. Is it always <address of fork>/<path to workflow>@refs/heads/<branch name>? Is there a difference if annotated or lightweight git tags are used? I can find many of these things by trial-and-error, but the documentation of pypi_attestations verify in README doesn't mention it.

Sorry for the laundry list of problems, but I thought it would be helpful to list my experience here as attestations are still fairly new. If I've missed a very obvious source of documentation please forgive me -- I tried looking in e.g. https://docs.pypi.org/attestations/publish/v1 as listed in pypi_attestations inspect, but every part of that path is a 404.
Thanks,
Adam
P.S. For context, the Sphinx PR that lead to this is at https://github.com/sphinx-doc/sphinx/pull/12981

Hi @AA-Turner, no problem at all! I appreciate the detailed issue.
I'll respond to each of your items below, but as a high-level point: the pypi_attestations CLI was built primarily for early experimentation, and we didn't expect anybody to use it directly for CI integrations 😅. Instead, we encourage most people to use the attestations functionality we've built directly into pypa/gh-action-pypi-publish, or to use actions/attest and convert its format (a Sigstore bundle) into a PyPI attestation via this package's Python APIs (not CLI).
With that being said, I agree that all of these are defects.

perhaps the tool could check if the extension is already .publish.attestation, and if so skip that file?

The reason we do this is because we need both files to perform verification (both the dist and the attestation), and so we infer the attestation's name from the file it's attesting for. With that said we could definitely improve the error message here, and emphasize that people should pass in verify dist/*.{whl,tar.gz} or similar.
(We should also make it so that verify dist/* itself just works.)

2. pypi_attestations inspect doesn't tell me what value I should be using with --identity (I don't know if this is possible, though). The example on README uses an email, so I tried the email I use for commits, which failed.

Yep, that's possible -- the identity to use is embedded as the certificate's SAN (Subject Alternative Name), so we can present that if it isn't already.

3. At the least expanding the initialism so that I can look up what a SAN is would be helpful. The key for "actual SANs" is a hyperlink, which doesn't look like the example of the verify command on the README

Agreed, we'll expand it. The reason it's a URL instead of an email like in the README is because it's produced by GitHub Actions, meaning the signing identity is the workflow identity that produced the attestation rather than the user identity that owns the repo. This is intended behavior, and it's what PyPI itself currently expects when uploading with attestations (attestations must currently match the Trusted Publisher workflow identity that's configured on PyPI).

Failures to verify in CI don't exit with a non-zero status code, so GHA reports all is well -- this seems wrong.

Yep, that's a bug.
(This goes back to the point about this CLI not being an intended public interface, but it's a bug regardless.)

5. Using the "actual SAN" hyperlink as the value for --identity works, but it is unclear how to auto-generate this for verification purposes. Is it always <address of fork>/<path to workflow>@refs/heads/<branch name>?

The identity/SAN will always be the "job workflow ref" for the workflow identity, which will always be https://github.com/<owner>/<repo>/.gjithub/workflows/<workflow>@<ref>, where ref can be either a symbolic ref (branch/tag) or a concrete commit ref. This corresponds with the Trusted Publisher configuration on PyPI, so if you register a Trusted Publisher like this:
Owner: foo
Repo: bar
Workflow: publish.yml

then your attestation identity will look like:
https://github.com/foo/bar/.github/workflows/publish.yml@<ref>

...where ref varies depending on how publish.yml was invoked.
This variance is one of the reasons the pypi_attestations CLI is mostly just intended for experimentation -- the way we handle it during verification on PyPI itself is by using the APIs, which can take a VerificationPolicy that matches individual identity components (e.g. owner/repo) without having to futz around with strings.

If I've missed a very obvious source of documentation please forgive me -- I tried looking in e.g. https://docs.pypi.org/attestations/publish/v1 as listed in pypi_attestations inspect, but every part of that path is a 404.

It's understandable that you missed it, since it's still in a PR! You can find the documentation for much of this in https://github.com/pypi/warehouse/pull/16398; please let me know if you have any questions about it.

As a bottom line: if possible, it'd be ideal for the Sphinx CI/CD to use gh-action-pypi-publish, since it intentionally encapsulates all of these details and represents the intended public interface for the signing/attesting side. If using that action isn't desirable for whatever reason, my follow-on recommendation would be to use this package's Python APIs directly, since those are intended to be the public interface that people rely on.
(The README doesn't say that, which is our fault. I'll also update it to nudge people towards the APIs, with a note that the CLI is principally for experimentation only.)

Yep, that's possible -- the identity to use is embedded as the certificate's SAN (Subject Alternative Name), so we can present that if it isn't already.

I just checked, and it looks like we do indeed print the identity. For example:
$ python -m pypi_attestations inspect test/assets/rfc8785-0.1.2-py3-none-any.whl.publish.attestation
Warning: The information displayed below are not verified, they are only displayed. Use the verify command to verify them.
File: test/assets/rfc8785-0.1.2-py3-none-any.whl.publish.attestation
Version: 1
Statement:
        Type: https://in-toto.io/Statement/v1
        Subject:
                rfc8785-0.1.2-py3-none-any.whl (digest: c4e92e9ecc828bef2aa7dba1de8ac983511f7532a0df11c770d39099a25cf201)
        Predicate type: https://docs.pypi.org/attestations/publish/v1
        Predicate: None
Certificate:
        Subjects<EMAIL_ADDRESS>        Issuer: CN=sigstore-intermediate,O=sigstore.dev
        Validity: 2024-06-06 18:49:05+00:00
Transparency Log (1 entries):
        Log Index: 28175749

The list under Subject: is the set of identities bound to the attestation. We could make that clearer by removing the confusing language around SANs vs. subjects vs. identities, though.

Thanks Will,
I've switched to the actions/attest approach in the Sphinx PR as that records commit metadata in the attestation (at least in the one uploaded to GitHub), which was requested by a contributor.
I appreciate that you want to keep the CLI as experimental/non-stable, but it is awfully useful. Hyrum's law and all that, I suppose. Nevertheless, the only part of the CLI we now use is inspect, as it's non critical and we don't do anything with the output, so we don't care if it changes.
If your position changes and you become open to making use of the command-line interface more official, it would be very welcome -- I try to keep my use of non-first-party (GitHub) actions to a minimum, even though I do trust the developers of the PyPA action.
One thing I did discover is that the "Transparency Log" entries actually mean something and go somewhere -- I thought originally it was just some internal logging. The GitHub action outputs "Attestation signature uploaded to Rekor transparency log: https://search.sigstore.dev/?logIndex=137921341", which might be a useful thing to point people towards both in documentation and in the tool's output.
Thank you for suffering my ignorance, and for being so prompt in updating things.
Thanks,
Adam

If your position changes and you become open to making use of the command-line interface more official, it would be very welcome -- I try to keep my use of non-first-party (GitHub) actions to a minimum, even though I do trust the developers of the PyPA action.

Makes sense! We'll keep this in mind as we continue to stabilize the package here -- one possibility is that we collapse the CLI here into the sigstore CLI, since the latter is already mature/stable and intended as an integration point.

Thank you for suffering my ignorance, and for being so prompt in updating things.

Thank you for your detailed issue and responses! I greatly appreciate that you've gone and dove straight into the internals of PEP 740.

As an update, Sphinx 8.1 has been released with PEP 740 attestations.
I tried to validate using the materials from PyPI, but failed. I appreciate that this may be too early, though (I got the provenance URL from the docs PR you linked earlier):
PS> curl https://pypi.io/packages/py3/s/sphinx/sphinx-8.1.0-py3-none-any.whl --remote-name --silent
PS> curl -H"Accept: application/vnd.pypi.integrity.v1+json" https://pypi.org/integrity/Sphinx/8.1.0/sphinx-8.1.0-py3-none-any.whl/provenance -o sphinx-8.1.0-py3-none-any.whl.bundle --silent
PS> sigstore verify github --repository sphinx-doc/sphinx --name create-release.yml --sha 2f1d775dfda9e4f81dfff6cfbe9edf7731e32a97 --bundle sphinx-8.1.0-py3-none-any.whl.bundle sphinx-8.1.0-py3-none-any.whl
[18:08:14] ERROR    An issue occurred while parsing the Sigstore bundle.                                                                                errors.py:41

                    The provided bundle is malformed and may have been modified maliciously.

                    Additional context:

                    unsupported bundle format:

                    For detailed error information, run sigstore with the `--verbose` flag.

A
xref: GitHub attestations summary

I tried to validate using the materials from PyPI, but failed. I appreciate that this may be too early, though (I got the provenance URL from the docs PR you linked earlier):

You're not too early, but there's unfortunately an extra step that isn't documented yet: that API returns a provenance object (per PEP 740), which contains bundles of (identity, [attestation]). To verify its contents, you need to unpack the attestations, convert them into Sigstore bundles, and verify them against their supplied identities.
The top-level API is Provenance, which you can then pull attestations from. I'm now realizing we don't provide convenience APIs for converting identities into Sigstore verification policies, though, so I'll look at adding those now.

The docs for this have fully landed: https://docs.pypi.org/attestations/, so I'm closing here! Please ping me anytime if you have any follow-on questions or problems with the docs 🙂


npm bundling for Texture

We should think what should go into a texture npm release too. Should we make the same structure as with Substance? I mean I guess we only need a browser bundle here, but a transpiled one, and tests are not relevant.

Done.


Unable to play non-chroma maps with heck.dll loaded into Beat Saber

I'm having an issue where if heck.dll is loaded to get chroma working standard non chroma/noodle maps aren't loading their stages and are unplayable but work fine if heck.dll is removed.

Heck just Doesnt Let you play Dont worry about it It might be fixed

I'm having an issue where if heck.dll is loaded to get chroma working standard non chroma/noodle maps aren't loading their stages and are unplayable but work fine if heck.dll is removed.

Can't reproduce. Please provide the _latest log if that ever happens again to you

I am apparently not allowed to press play, and can't play any maps at all when heck.dll is there. But for me too it works if i remove heck.dll.

I am apparently not allowed to press play, and can't play any maps at all when heck.dll is there. But for me too it works if i remove heck.dll. Like the maps load in i'm just not allowed to press play.

Please provide _latest.log found in the UserData/Logs

Here this might Help
[WARNING @ 10:47:22 | [Plugins/IniParser.manifest] Failed to find info
[WARNING @ 10:47:22 | [Plugins/Heck.dll] Failed to find info
I found this In my logs Folder And Only put that

Here this might Help
[WARNING @ 10:47:22 | [Plugins/IniParser.manifest] Failed to find info
[WARNING @ 10:47:22 | [Plugins/Heck.dll] Failed to find info
I found this In my logs Folder And Only put that

This tells nothing - it's just the warning that comes up because those files are not posted on BeatMods.
The only thing that is helpful is the _latest.log found in UserData/Logs, after experiencing a behavior that you would think is a bug.
ONLY that. Nothing else.
You won't find ANY help unless you provide this file

latest.log
This log should have the relevant information to this behavior

latest.log
This log should have the relevant information to this behavior

I see you don't have Chroma installed
You Noodle Extensions are outdated

Closed for inactivity from original poster


Are there plans to implement drop-in replacements for parts of sklearn.feature_selection?

Some (like VarianceThreshold) may be pretty easy to do, others can be a little more complex and may require more thought.
I'm wondering if there's a plan to cover that as part of dask-ml?

Yes, some of those would definitely be in scope. Looking through the list, the Recursive ones probably can't be parallelized.
The various Select*  ones should be doable, assuming the score functions can be implemented.
Do you have any interest in working on these? It can be done in bits and pieces. I suspect that you're correct that VarianceThreashold is the most straightforward.

I expect to be needing some soon, at least VarianceThreshold to get us started. I was going to implement it directly in our source code but if its in-scope I would definitely prefer putting it here.
We're also using a slightly naive DT implementation on top of Dask, let me know if you will be interested that as well and I'll open a PR and we can continue discussing the details there.

Great!
What's DT stand for?

sorry, I meant implementing a random forest based on parallelizing decision trees using dask.


Getting this error

fastrpc.Server: error on connection "<IP_ADDRESS>:80"<->"234.324.234.324:43202": error in handshake: error in TLS handshake: remote error: tls: bad certificate
i've tried many self signed cert and always get this issue.
can u provide the instructions to create self signed cert to /usr/local/src/
not sure if i need to link it to the right directory or not.
Server Frontend
./httptp -inType=http -inTLSCert=/usr/local/src/alice.crt -inTLSKey=/usr/local/src/alice.key -in=<IP_ADDRESS>:866 -outType=teleports -out=<IP_ADDRESS>:866 &
Server Backend
./httptp -inType=teleports -inTLSCert=/usr/local/src/alice.crt -inTLSKey=/usr/local/src/alice.key -in=:80 -outType=http -out=<IP_ADDRESS>:88
what is the problem?
appreciate this.

certificates.zip
using the certficates from downloaded free from the internet. i did generate them myself with
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /usr/local/src/ssssl.key -out /usr/local/src/ssssl.crt
but it's not working too

just realised because i'm running the server behind aws so the ip address cannot be detected http server side. any ways to use teleportS without domain name verification?


ADT 3D Object Detection Challenges Evaluation Blank

I have made a few submissions to phase 3 (few-shot validation) of the challenge, but the "result file" and "stdout file" (visible from the "my submissions" tab) are both blank.
When I make my submission public and check on the leaderboard, I see that all metrics are 0.
However, I'm unsure whether the metrics are 0 because not a single prediction matched the annotation or because the evaluation script is just not spitting out any results (as seen in the blank "result file").
I would like to think that I at least retrieved and matched the pose from the initial 5 seconds properly, but there's still some room for error I guess.
I am doing something along the lines of
for img_timestamp_ns in provider.get_aria_device_capture_timestamp_ns(stream_id):
    image_with_dt = provider.get_aria_image_by_timestamp_ns(img_timestamp_ns, stream_id)
    bbox2d_with_dt = provider.get_object_2d_boundingboxes_by_timestamp_ns(img_timestamp_ns, stream_id)
    bbox3d_with_dt = provider.get_object_3d_boundingboxes_by_timestamp_ns(img_timestamp_ns)
    aria3d_with_dt = provider.get_aria_3d_pose_by_timestamp_ns(img_timestamp_ns)
    assert image_with_dt.is_valid(), "Image not valid!"
    assert bbox2d_with_dt.is_valid(), "2D bounding box is not available"
    assert bbox3d_with_dt.is_valid(), "3D bounding box is not available"
    assert aria3d_with_dt.is_valid(), "3D pose is not available"

    image_path = os.path.join(sequence_cache_dir, f'imgs/{img_timestamp_ns}.png')
    # if image and bbox2d are close in time
    if (
            abs(bbox2d_with_dt.dt_ns()) < 200000 and
            abs(bbox3d_with_dt.dt_ns()) < 200000 and
            abs(aria3d_with_dt.dt_ns()) < 200000
    ):

to match and save the annotations in the frame's (image's) timestamp, but maybe this logic is critically off?
My method (https://github.com/facebookresearch/projectaria_tools/assets/8120297/cf5e0b00-0cfd-499c-88ae-fd9916dd89b6) is barely working, so I'll be happy if I can just get one legit submission in before it's due for experience's sake :)
Thanks for the awesome dataset, challenge, and any help in advance!

Also, did the challenge finish early?
It seems like it's inactive on eval AI because it finishes 12AM 03/22 (Fri) instead of 11:59PM 03/22 (Fri).

Hey, just a friendly ping, because it's nearing the end of the day here.
There should still be about 9 hours left according to the announced official due date, but the eval AI challenge is still inactive and won't let me submit...
I know it's the last day, but it'd be super helpful if you could help me with this :)

Hi @chahyon-ku, I am looking into extending the deadline now. In the mean time, I think you may have used the wrong prototype names. They should be WorkoutDumbbell_Proto and WaterPitcher_Proto

Ah makes sense, thank you so much!
I assumed no "_Proto" because Apartment_release_challenge_example contained prototypes like "ChoppingBoard" and "WhiteUtensilTray" in "submissions_example/Apartment_release_challenge_example.csv", but that example must have been for phase 1/2.

@chahyon-ku are you able to submit now?

Same issue with same end datetime I believe.

I see.. I'm not the maintainer of this so it seems I can't update it. I have contacted the maintainers, hopefully they get back to me soon. But I'm sure we can extend it so that you can submit, please don't stress about the time! Sorry for the inconvenience.

That's awesome :) Thank you so much for the help and have a great weekend!

It should be updated now. Please let me know if you have any other issues, otherwise, please close the issue. Thank you for participating in our challenge!

Thanks for that! I ended up submitting later that night, but the submission seems to be stuck at the "submitted" stage and neither "finished" or "failed." Is this also likely some formatting issue of the submission?
It's so unforunate that the competition finished so early :/ I only found out about the competition through the EgoVis Workshop posting and there's still so much time until the workshop...

Glad to hear you were able to submit! We confirmed that we did receive your submission. The server gets shut down after the deadline so maybe it didn't have time to complete the evaluation before it was shut down.
Sorry to hear you only found out about the challenge recently. We do try to announce these challenges at the major conferences (e.g., ECCV, ICCV, CVPR), but it is still hard to get the reach that we would like. Please keep an eye out for future challenges at projectaria.com, or sign up for our newsletter on the home page to make sure you don't miss anything!
Thanks again for participating! Closing this issue, but please feel free to add more comments or reopen if you have anything else you'd like to discuss.


Support Memory Hotplug with Hugepages

What this PR does
Before this PR:
A VM configured with memory hotplug and hugepages does not start
After this PR:
A VM configured with memory hotplug and hugepages starts correctly

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Support Memory Hotplug with Hugepages

/cherry-pick release-1.2


1.8.4启动后，经常报这个，有影响吗，怎么让它不报

[2022-05-10 09:44:20 +0800] [30] [INFO] Starting gunicorn 20.0.4
[2022-05-10 09:44:20 +0800] [30] [INFO] Listening at: http://<IP_ADDRESS>:8888 (30)
[2022-05-10 09:44:20 +0800] [30] [INFO] Using worker: sync
[2022-05-10 09:44:20 +0800] [31] [INFO] Booting worker with pid: 31
[2022-05-10 09:44:20 +0800] [32] [INFO] Booting worker with pid: 32
[2022-05-10 09:44:20 +0800] [33] [INFO] Booting worker with pid: 33
[2022-05-10 09:44:20 +0800] [34] [INFO] Booting worker with pid: 34
/opt/venv4archery/lib/python3.9/site-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
/opt/venv4archery/lib/python3.9/site-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
/opt/venv4archery/lib/python3.9/site-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
/opt/venv4archery/lib/python3.9/site-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,

不影响archery功能；看下cryptography版本，如果>36.0.2，可以重新安装36.0.2版本来消除警告
pip freeze|grep -i cryptography
pip install cryptography==36.0.2

pip freeze|grep -i cryptography
pip install cryptography==36.0.2   完美解决了 感谢


[Bug]: Issue with the droppable area when we increase the size of the widget

https://www.loom.com/share/5c3681e317c4440988c09b0cfa1240c3

Working fine now, moving to done.


Support 0.11.x build API and unify tag components

build.zig changes:

build.zig now detects whether the new build system is available and handles it appropriately: the new build system has breaking API changes; most notably in the removal of std.build.Pkg and breaking changes to how executable artifacts are created. For backwards compatibility with projects pinned to an old Zig version, the pkg field is still provided (lazy evaluation means that in new projects it won't cause any errors).

The flecs module should be exposed when using the package due to the use of b.addModule, but without exposing the functionality provided by link it's probably not possible to use zig-flecs with the package manager yet. Therefore, end users should probably still vendor or submodule this project and use the module() function provided in the updated build.zig file.

The build process works in both 0.11.x and 0.10.1 and the example executes successfully.

ecs_component changes:

Following a discussion with Sander in the Flecs discord, the special casing for zero-sized types in ecs_component has been removed: the Flecs C++ binding lacks this special-casing (zero-sized types are registered as ordinary components), and Sander thinks that the ECS_TAG macro in the C API should probably set the use_low_id option as well.

Hm, I accidentally removed setOutputDir, guess I'll re-add that.

Thank you so much for this PR, life has been busy for me lately and I didn't have a chance to get around to this yet. Note also that now Michal has been adding his own flecs bindings to zig-gamedev which to be honest will likely end up much nicer than these, though more work to update.

Actually I couldn't test 0.10.x properly, turns out it was a no-op. Probably issues with my kernel version, Zig didn't support 6.1 until recently. Anyway, it should work but I can't confirm, oof.
I noticed the zig-gamedev one, I'll use that once it's viable. Not like I've gotten around my chronic procrastination to do anything useful with this one.


PHPStorm support for ActiveRecord methods

Since 2.0.3 I have problem with type hint at the PHPStorm 8. It considers the return type of method findOne() is 'null|static' (real @return static|null but PHPStorm detects null|static) and hence don't hint real model type. In previous versions the return type was just 'static' and all works fine. It is strange the return type static|null because of for empty of object null is the normal case.
I know that Yii core team use different IDEs and PHPStorm also. How you solve this problem? Thanks.

dublicate https://github.com/yiisoft/yii2/issues/7404


Add network Address class

Header: core/net/address.hpp
Source files:

core/net/posix/address.cpp
core/net/windows/address.cpp

Class name: cubos::core::net::Address
It should provide:

default constructor (initially <IP_ADDRESS>).
copy constructor.
constructor which takes the four ipv4 octets (x.y.z.w).
constructor which takes a ipv4 32-bit integer (octets together basically).
static Opt<Address> from(const std::string& address), can receive any IP or URL. Returns none on error.
static const Address Any - <IP_ADDRESS>.
static const Address LocalHost - <IP_ADDRESS>.
it should implement reflection and contain the StringConversionTrait.

What is the main purpose, will this store as state just a 32 bit value, or should it hold the socket implementation (WSADATA for windows and int for linux) ?

Just a 32 bit value, I think, to avoid exposing the headers

So whats the point of having posix and windows address.hpp ? The implementation should be similar, or actually, the same

We won't have two headers, only two different source files. Only one of them is used in each platform

We won't have two headers, only two different source files. Only one of them is used in each platform

Yes but why? What would differ in storing a simple 32bit value

I meant having a single address.hpp, which stores a single 32 bit value. Then, there are two .cpp files, one used in windows, another one used in posix. The implementation of the functions is what differs on the two .cpp files, but the interface is the same, and thats why there is only a single .hpp file.

See my PR implementation above. It will make a bit more sense why I am asking I think. The major implementation is similar, only some functions differ (such as from). But if the major is similar, can't we just use ifdef for those specific functions?

See my PR implementation above. It will make a bit more sense why I am asking I think. The major implementation is similar, only some functions differ (such as from). But if the major is similar, can't we just use ifdef for those specific functions?

Ahhh, I understand. Indeed, in this class the functions are mostly same, it's better to use #ifdef yeah. For consistency we should do the same for the socket and listener classes too then. Ty!


Full hash-routing using preact-router

Let me say first that the current routing implementation works beautifully and I've had no issues, but I have a specific use case where I want to use hashes instead of routes to avoid polluting the javascript history object.
Currently, my main app is setup like this
<Router>
  <Index default />
  <UserContainer path='/users' />
</Router>

This basic implementation gives me 2 routes:
www.example.com -> which loads my Index component
www.example.com/users -> which loads my UserContainer component
The issue I'm seeing is that once I go from / to /users, calling javascript:history.back() will take me back to / since /users is a new route.
I was trying to avoid pushing a new route into my history object, so I thought I could achieve this using hashes for routing instead of full routes.
What I want is
www.example.com -> which loads Index
www.example.com#users -> which loads UserContainer
That way, when i go from / to /users and call  javascript:history.back(), it will take me to what I had before i was on / (which is my desired behavior).
Is this possible with preact-router?

Also I did take a look at #88 and #151 but I don't think its the same use case. Let me know if you feel otherwise

Mutating location.hash actually still adds a history entry.  Perhaps you could use the replace option on route():
route('/users', true);   // replaces the current history entry with /users & routes to it

Thanks @developit that is pretty useful.
Another followup question, is there any way to mutate the javascript history hash using preact-router? I'm asking because my specific use-case involves multiple nested screens, but when an action in the deeply nested screen is successful, I want to return the user to the default page and clear all previous history so that clicking the back button takes you back to where you were before you entered the default page.

Ah that's a tricky one. I'm not really sure how you'd do that in a way that didn't just involve remembering the history states:
// go back 3 views:
history.go(-3);

// overwrite the original entry with some destination URL:
route('/results', true);


Slot reverts to initial value when SlotSet event is forgotten by AugmentedMemoizationPolicy

Rasa Open Source version
2.6.2
Rasa SDK version
No response
Rasa X version
No response
Python version
Other
What operating system are you using?
Other
What happened?
The AugmentedMemoizationPolicy seems  to modify a state:
Before calling the delorean, the value of a slot is (0.0, 0.0, 0.0, 1.0, 0.0, 0.0).
After calling the delorean, the value of a slot is (1.0, 0.0, 0.0, 0.0, 0.0, 0.0).
A similar bug was seen before and it might be fixed in the current version. Customer is checking if its fixed with 2.7.1.
Discussion: https://rasa-hq.slack.com/archives/C021ZTVSY77/p1629720593324400
Command / Request
No response
Relevant log output
No response

Shukri confirmed they're seeing the issue with 2.7.1 as well

This actually isn't a matter of sorting. It seems that the "SlotSet" event is forgotten by the policy, and the slot returns to its initial state.
slots:
   thing:
    type: rasa.shared.core.slots.CategoricalSlot
    initial_value: abc
    auto_fill: true
    influence_conversation: true
    values:
    - abc
    - def
    - ghi

Before calling the delorean, the value of a slot is "ghi" (0.0, 0.0, 1.0).
After calling the delorean, the value of a slot is "abc" (1.0, 0.0, 0.0).
See tests demonstrating this here

@hsm207 am I good to close this as not a bug? You're planning on clarifying this in the docs, right?

@koernerfelicia yes, we can close this and i will clarify in the docs


rye run -l prints to stderr

Steps to Reproduce

create a script in the [project.scripts] section, or rye add a package with entry points.
run rye run -l (or rye run) to see the list of available entry points
grep for specific entry point rye run -l | grep "my-entrypoint"

Expected Result
I would expect in step 3 to be able to grep against the list of available entry points. If not from rye run, then at least from rye run -l/rye run --list.
Actual Result
rye run -l output to stderr, so all entry points are printed and then a non-zero exit code occur due to no grep matches.
rye run -l 2>&1 | grep "my-entrypoint" will give the desired result.
Version Info
rye 0.34.0
commit: 0.34.0 (d31340178 2024-05-20)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true
Stacktrace
No response

https://github.com/astral-sh/rye/pull/342
pub fn execute(cmd: Args) -> Result<(), Error> {
let _guard = redirect_to_stderr(true);
I'm not sure if this issue should be fixed, because it seems to be intentional by the developers, or maybe it's a mistake.

Aha, I see! It was opposite to the behaviour I expected so I figured it was just overlooked, but feel free to close if it isn't really an issue.

I would probably expect this to be written to stdout, personally.

I would probably expect this to be written to stdout, personally.
I think so, I will try to submit a PR, but still have to see the administrator to accept or not.

This is definitely a very opinionated topic. Personally I prefer STDERR to keep it separate from STDOUT. This is standard for a lot of applications, like strace as a fine example. 2&>1 |  is not too hard write to enable you grepping through the output from my POV.

@Woovie what's to be kept separate from STDOUT though? The entire output of rye run -l is a list of commands which is meaningful data that could be piped to another tool as is the intent of STDOUT. Think about if there were some log messages output by Rye while determining what the list of commands is — that'd go to STDERR and should not be piped to another program. If you just combine STDERR / STDOUT you're unable to discern which information is relevant.