Support Interrupt in RawKernel

Interrupt should just be sending a SIGINT or something directly to the kernel process. Or changing the kernel spec and passing an interrupt message as noted below.

If you change the kernel_spec, you can use a message to interrupt:
https://jupyter-client.readthedocs.io/en/stable/messaging.html#kernel-interrupt
https://jupyter-client.readthedocs.io/en/stable/kernels.html#kernel-specs

I grouped these together, but restart should actually be pretty similar to the changeKernel work item, so those should probably be handled together.

Moving this item to just interrupt and putting restart in with change kernel.

Validated.


Implement Component trait for Size and Rect

Currently existing Bevy Bundles that use Size or Rect as components stopped working after 07ed1d053e7946a116ce3eef273fc93dd246f49d, so implementing the Component trait for these two structs should fix that.
Objective
Make it so that Entities that use Size as a component can work.
Solution
By deriving the Component trait for Size and Rect, it can be used as components for Entities.

@mockersf Yea, I was using it as part of a WIP game and when updating to the latest Git commit, I realized that part of the reason it wouldn't build was this.

Hmm, alright. Should I close this?

Yep, let's close this out. If we have a change of heart later, we can redo this more comprehensively.


Bump Guardian dependency version number

Sorry, made a PR on the wrong branch. Just bumping the version number will cause errors.


Snapshot is missing LICENSE file

LICENSE file should be included in all jars, releases and snapshots.  It is currently missing from the SNAPSHOT jars.  The change should place the LICENSE in ALL snapshot jars as well a the release jars when they are bult.

@Claudenw can you tell us which jar. We have tooling to include LICENSE in jars but maybe this is missing from some places

@Claudenw can you look at https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26660-7809c783-SNAPSHOT/ - last night's pekko-actor jars?

Download pekko-actor_2.13-0.0.0+26660-7809c783-SNAPSHOT.jar
It has these files in the jar

      551  01-01-2000 00:00   META-INF/DISCLAIMER
    12128  01-01-2000 00:00   META-INF/LICENSE
     1732  01-01-2000 00:00   META-INF/NOTICE

@mdedetrich we don't include LICENSE, NOTICE, DISCLAIMER in the -sources and -javadoc jars. Is that something that can be changed in sbt-apache-sonatype?

Can we clarify if we need to add them into the -sources and -javadoc jars as well? Both are highly suspicious because they are only meant to contain either Java/Scala sources or generated documentation.

I checked some random Apache -sources and -javadoc jars and found that they had LICENSE and NOTICE files. I doubt whether it's universal but it does seem like something that many teams try to support.

https://repo1.maven.org/maven2/org/apache/spark/spark-core_2.13/
https://repo1.maven.org/maven2/org/apache/streampark/streampark-common_2.12/

I'm not guaranteeing that sbt makes this easy - the sources and javadoc jars are basically generated using black box code and there doesn't appear to straightforward ways to manipulate them to add extra files.

I checked some random Apache -sources and -javadoc jars and found that they had LICENSE and NOTICE files. I doubt whether it's universal but it does seem like something that many teams try to support.

I checked some other projects like Apache Daffodil and indeed it does seem to be the case. Do we also have to include DISCLAIMER as well?

I'm not guaranteeing that sbt makes this easy - the sources and javadoc jars are basically generated using black box code and there doesn't appear to be straightforward ways to manipulate them to add extra files.

This shouldn't be that difficult. Apache Daffodil uses sbt so I can just check their code

Actually I just checked -javadoc for Apache daffodil and it doesn't contain any license files, -sources is a lot more clear.

with the DISCLAIMER file, I'm not 100% sure we need that in our jars at all - but since it's easy to extend what we have for adding LICENSE/NOTICE to also add DISCLAIMER - it just seems to be simpler to include it.
We will get dragged over coals for missing files but if we add extra ones, we are less likely to get in trouble.

Release for v1.0.8 of sbt-apache-sonatype has been triggered. It should be available/downloadable on Maven in around half an hour. Bumping the version is enough for it to include the files in the -sources package.

https://nightlies.apache.org/pekko/snapshots/org/apache/pekko/pekko-cluster_3/0.0.0+26660-7809c783-SNAPSHOT/pekko-cluster_3-0.0.0+26660-7809c783-SNAPSHOT-sources.jar
A snapshot from May 23.  Does not have the License file included.

https://nightlies.apache.org/pekko/snapshots/org/apache/pekko/pekko-cluster_3/0.0.0+26660-7809c783-SNAPSHOT/pekko-cluster_3-0.0.0+26660-7809c783-SNAPSHOT-sources.jar
A snapshot from May 23. Does not have the License file included.

Snapshots are published nightly and the fix for this has only been published recently (see https://github.com/apache/incubator-pekko/issues/328#issuecomment-1559262610)

I was simply providing a reference to one that was broken.

No worries, I will create a PR to fix this now (the sbt-apache-sonatype fix should be available in maven now).

@Claudenw this is partially done now - the sources jars now have LICENSE/NOTICE (the runtime jars already had them).
We don't yet support them on javadoc jars. It's not clear how hard it is to make this change. From checking other Apache projects, javadoc jars do not always contain the LICENSE/NOTICE. Is that going to be an issue? Should we take this to Legal team?

@mdedetrich there is https://issues.apache.org/jira/browse/LEGAL-28 and it seems to indicate that we should put LICENSE/NOTICE in javadoc jar. Even if it is ambiguous whether this is the case - it is going to cost time to discuss the issue. is there any chance that sbt-apache-sonatype could just be changed to add LICENSE/NOTICE to the javadoc jars?

No worries, ill add it into sbt-apache-sonatype. Will also use this ticket as a reference.

@pjfanning PR created at https://github.com/mdedetrich/sbt-apache-sonatype/pull/16, can you review it

@pjfanning Release of v0.1.9 was just triggered, should be on Maven in ~30 min, see https://github.com/mdedetrich/sbt-apache-sonatype/actions/runs/5094036357

Closing this as I have updated all pekko projects with sbt-apache-sonatype that makes sure these files are put into source and javadoc jars.
If there is something missing/wrong, feel free to re-open issue.


error: var packageName = /^packages/(.+).js$/.exec(pckge.path)[1];

Hey. Cool library. I'm getting this error on npm run client
var packageName = /^packages/(.+).js$/.exec(pckge.path)[1];
^
TypeError: Cannot read property '1' of null

I got it to work like this (meteor 1.3.2):
on entry.js:
import 'meteor-imports'
const { Mongo } = Package.mongo
const { Tracker } = Package.tracker
const { Meteor } = Package.meteor

@rickmed I am glad this is useful.
If you find the fix make a PR and I will accept it.

I just want to add another reason for this error is when it tries to package css files!
merged-stylesheets.css
C:\repo\ReactJS_seedProject\node_modules\meteor-imports-webpack-plugin\index.js:92
var packageName = /^packages/(.+).js$/.exec(pckge.path)[1];
The regex fails,
The solution is to delete all the CSS files in the meteor directory, or to fix code so it ignores css bundles?

I think it could be possible to ignore css files. Could you please do a PR?

I find it problematically with both CSS and the main app file. Those are not inside /packages/ and therefore the execreturnsnull`. I am working in a fix for it.

fixed by #11
Okay, the fix is published as 1.1.1!


More granular achievements

It would be nice to have more granular achievements for lower level players before 99. They could be every 10 levels starting at 40 or so for individual skills or important milestones (e.g. 85 slayer).
Longer term it would be nice to be able to verify an account and set custom achievements.
Use Case: With the release of group ironman I would like to have the discord bot announcing my group's achievements as we progress even early-mid game.

The only thing stopping us from adding more achievements is database size, you can imagine how quickly it would fill up if every 10 levels of every skill had an achievement, multiplied by 350k players, and it would only increase everyday.
Could be done, but some thought would have to go into managing that

As an example, let's say the average player has level 50 in all skills, that's 5 achievements per skill, for 23 skills, for 350k players, that's a quick 40M database entries.
And if you get bosses involved, that's 40+ bosses, it's a lot, unfortunately.

So we did some maths on the Discord, and there are a lot of savings to be had with how the data is stored.
Currently, the achievement table stores the name of the achievement, the metric it needs to look up, and the value it's checking against. All of this is static data, so it could be moved over to its own static table. This would drastically reduce the amount of space each row takes up (up to 97% if postgres bad, 83% if postgres sensible). It could be replaced with a smallint FK, as 32.7k total unique achievements seems relatively reasonable (and the negative numbers could probably be used too for another 32.7k)
Postgres docs aren't exactly clear about how much space a varchar takes up when empty, so there are a couple of guesses.
As an example, the worst achievement for space is the 100 Chambers of Xeric Challenge Mode one, due to the sheer width of the metric and display names.
Current (Best Case, postgres doesn't allocate extra space): 84 bytes per achievement row
Current (Worst Case, postgres allocates all varchar space): 530 bytes per achievement row
With a static table and smallint FK: 14 bytes per achievement row
This 14 bytes would also be consistent across all types of achievements, as no matter what the text for the achievement is it'll be in another static table (again, assuming allocation stuff)


e2e,migrations: Quarantine very flaky paused VMI migration tests

What this PR does
The failure rate of the compute migrations presubmit lane is higher than 50% mainly due to these tests[1]
Quarantine to give time to get a fix in place
[1] https://testgrid.kubernetes.io/kubevirt-presubmits#pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations&width=20

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
/cc @xpivarc @dhiller

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

NONE

/priority critical-urgent

Could have been more productive to review #13474 instead of breaking it 😅

Does #13474 cover these? I am not seeing direct correlation. See https://github.com/kubevirt/kubevirt/pull/13463

Could have been more productive to review #13474 instead of breaking it 😅

Does #13474 cover these? I am not seeing direct correlation. See #13463

Yes, just lowering the bandwidth appears to do the trick

Could have been more productive to review #13474 instead of breaking it 😅

Does #13474 cover these? I am not seeing direct correlation. See #13463

Yes, just lowering the bandwidth appears to do the trick

Very well I see. @vladikr #13463 might be redundant but we still need to review if the speed up, caused by the bw limit being not aggregating, is not producing false positives. @jean-edouard Thank you for the work on #13474 and I am sorry for the conflict. Sometimes we prioritize quick fix(especially if the problems persists for many days and fix is not apparent ) to keep the impact low.


ReferenceError: crypto is not defined for 0.1.64

after upgrading to 0.1.64 I get the following error on deploy (only in github/console builds)
Running program '/tmp/repo/.sst/platform/sst.config.1722392645972.mjs' failed with an unhandled exception:
ReferenceError: crypto is not defined
    at file:///tmp/repo/.sst/platform/src/components/aws/cdn.ts:404:16
    at /tmp/repo/.sst/platform/node_modules/@pulumi/output.ts:402:31
    at Generator.next (<anonymous>)
    at /tmp/repo/.sst/platform/node_modules/@pulumi/pulumi/output.js:21:71
    at new Promise (<anonymous>)
    at __awaiter (/tmp/repo/.sst/platform/node_modules/@pulumi/pulumi/output.js:17:12)
    at applyHelperAsync (/tmp/repo/.sst/platform/node_modules/@pulumi/pulumi/output.js:244:12)
    at /tmp/repo/.sst/platform/node_modules/@pulumi/output.ts:316:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

I think regression was added here https://github.com/sst/ion/commit/0b21b1ee29014b5c87ada2893af6eec79d56b1b2

I don't know if it is related but I get:
Getting an error on the latest version of sst with nextjs:
./node_modules/.pnpm/sst@3.3.26/node_modules/sst/dist/resource.js:3:1

Module not found: Can't resolve 'crypto'
  1 | import { env } from "process";
  2 | import { readFileSync } from "fs";
> 3 | import crypto from "crypto";
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^


Update Puppet lexer

(Original issue 919 created by semente on 2013-10-19T02:46:10.593415+00:00)
I'm using Pygments==1.6 and looks like it have to update its Puppet lexer. Give a look on  the Puppet code on this page: http://semente.io/3-caching-packages-downloaded-pip/
Thanks!

(Original issue 919 last updated on 2014-01-10T09:28:45.989989+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2014-01-09T19:34:57.915355+00:00)
Hmm, where is that code? :)

(Original comment by semente on 2014-01-09T21:48:17.912757+00:00)
oh, sorry... I just removed. :-P
But I think you can reproduce it by using this code:
#!puppet

package { 'puppet':
    ensure      => installed,
    testquotes => 'test',
    anothertest => "test",
}

(Original comment by semente on 2014-01-09T21:49:08.505466+00:00)
The main problem was with the single quotes, that was showing as syntax error...

(Original comment by birkenfeld on 2014-01-10T09:28:46.010839+00:00)
That seems to be fine now...


 I tried to do the same for all our ESLint config stuff and it was a complete nightmare and therefore I bailed. So... someone should go do this at some point.

Notably if we upgrade to ESLint 7 we'll have to drop Node 8 support but Node.js core already did that last December 31st so I'm inclined to say who cares


Sync eng/common directory with azure-sdk-tools for PR 5991

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/5991  See eng/common workflow

Manually queued core test run: https://dev.azure.com/azure-sdk/public/_build/results?buildId=2707735&view=results
@billwert I just used the default selection for which packages are actually tested. That includes azure-core-test so I figure it's g2g.


Error: "Unable to parse color from string:" with Vanilla Example

I tried this tool in a simple example derived from the HTML Vanilla Example:
<!doctype html>
<html>
<head>
    <script type="module" src="https://cdn.skypack.dev/openapi-explorer"></script>
    <!-- Or use a local deployed copy -->
    <!--script type="module" src="node_modules/openapi-explorer/dist/openapi-explorer.min.js"></script-->
</head>
<body>
<openapi-explorer
        spec-url="./api-docs-token.json"
        disable-default-colors="true"
        bg-color="#FFF"
        primary-color="#006C69"
        secondary-color="#CCC"
        text-color="#333"
        nav-bg-color="#FFF"
        nav-hover-text-color ="#555"
        nav-text-color ="#333"
> </openapi-explorer>
</body>
</html>

I served the html along side with the api-docs-token.json from a local folder with npx serve.
What is the Problem?
Nice tool btw :)

No idea but we've been able to reproduce it. We're looking into it.

This is fixed with release 0.1.100, there was an issue with our dynamic resolution of colors, when they weren't set by a UX framework, the fallback wasn't correctly being applied. It should work as you would expect now:


Cpan dependencies

Hi,
I can install this app with no errors, but when i create a short link, i have an error.
Can't locate Image/PNG/QRCode.pm
My debian need the package libpng-dev to install Image/PNG/QRCode.pm during the install of Carton with cpan.
Best regards.

@frju365 Please have a look at https://framagit.org/luc/lstu/wikis/dependencies. Also, you can choose to not install some dependencies, making the installation faster: https://framagit.org/luc/lstu/wikis/installation#installation-of-lstu

Thanks for your answer.
Or just add libpng-dev at line 50 in the file scripts/install ?
ynh_package_install build-essential libssl-dev libpq-dev libpng-dev
Best regards

My comment was for @frju365, for him to fix properly the package. Yes, adding libpng-dev to the packages installation is enough, but I was pointing him the doc to make a cleaner app.

Oh, i was sleeping i think ;)

Seems to be better for this point.


where is the vlmeval/utils/data_util.py

Excellent work:)
But I can`t fine the data_util file in the lasted version..
And  I would like to ask when the Internlm2 7b model will be supported.Thanks!

# When running with `python`, only one VLM instance is instantiated, and it might use multiple GPUs (depending on its default behavior).
# That is recommended for evaluating very large VLMs (like IDEFICS-80B-Instruct).

# IDEFICS-80B-Instruct on MMBench_DEV_EN, MME, and SEEDBench_IMG, Inference and Evalution
python run.py --data MMBench_DEV_EN MME SEEDBench_IMG --model idefics_80b_instruct --verbose
# IDEFICS-80B-Instruct on MMBench_DEV_EN, MME, and SEEDBench_IMG, Inference only
python run.py --data MMBench_DEV_EN MME SEEDBench_IMG --model idefics_80b_instruct --verbose --mode infer

# When running with `torchrun`, one VLM instance is instantiated on each GPU. It can speed up the inference.
# However, that is only suitable for VLMs that consume small amounts of GPU memory.

# IDEFICS-9B-Instruct, Qwen-VL-Chat, mPLUG-Owl2 on MMBench_DEV_EN, MME, and SEEDBench_IMG. On a node with 8 GPU. Inference and Evaluation.
torchrun --nproc-per-node=8 run.py --data MMBench_DEV_EN MME SEEDBench_IMG --model idefics_80b_instruct qwen_chat mPLUG-Owl2 --verbose
# Qwen-VL-Chat on MME. On a node with 2 GPU. Inference and Evaluation.
torchrun --nproc-per-node=2 run.py --data MME --model qwen_chat --verbose

Hi, @TousenKaname ,
For now, please refer to the dataset_config.py. The document has been updated accordingly.

Thanks!


Tensor RT Python API for Inference on Jetson Nano/Orin Nano in realtime

I have a requirement for Tensorrt implementation of this lane detection in my Jetson Nano/ Jetson Orin nano device. I can see that there is Tensrort C++ API for it and steps are given on how to do the same, But I need a Python implementation with TensorRt for the same and it is needed for deployment so that the model can reason in real-time on my edge device with the CSI camera on board.
I have tested the code on a non-ARM-based architecture device(laptop) but I want to deploy the code on my edge device with Python implementation.
Can you help me by providing code/resources for the same or steps on how to do it?

天 我们能交流一下部署的问题吗 我现在刚拿到AXG 一点都不会部署 ，我现在的问题是把原始文件的onnx删了 但是pt转不成onnx 这一步你完成看了吗