v1: Optimize calls

This PR heavily refactors the v1 wasmi engine.
Greatly reorganizes the engine codebase and cleans up some older parts.
This results in up to 16% performance wins for call intense workloads.
Also the call stack now demands less memory for the same amount of nested calls.
Caching of instance related data now works across function call boundaries.

Codecov Report

Merging #412 (c618767) into master (71a913f) will increase coverage by 0.23%.
The diff coverage is 83.92%.

@@            Coverage Diff             @@
##           master     #412      +/-   ##
==========================================
+ Coverage   76.79%   77.02%   +0.23%
==========================================
  Files          68       71       +3
  Lines        6765     6800      +35
==========================================
+ Hits         5195     5238      +43
+ Misses       1570     1562       -8

Impacted Files
Coverage Δ

wasmi_v1/src/engine/bytecode/mod.rs
100.00% <ø> (ø)

wasmi_v1/src/instance.rs
73.52% <ø> (ø)

wasmi_v1/src/engine/config.rs
70.83% <70.83%> (ø)

wasmi_v1/src/engine/stack/mod.rs
77.14% <77.14%> (ø)

wasmi_v1/src/engine/cache.rs
79.16% <79.16%> (ø)

wasmi_v1/src/engine/stack/values.rs
93.75% <85.71%> (ø)

wasmi_v1/src/engine/mod.rs
85.10% <89.28%> (+0.43%)
:arrow_up:

wasmi_v1/src/engine/exec_context.rs
98.31% <90.90%> (+0.67%)
:arrow_up:

wasmi_v1/src/engine/stack/frames.rs
93.10% <93.10%> (ø)

wasmi_v1/src/engine/code_map.rs
82.75% <100.00%> (+25.13%)
:arrow_up:

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


update only payload of specific point

Hi 👋
Does Qdrant support the ability to specify a point as an id of the point and then modify only the payload of that point?
In my case, I would like to add a new key and value or modify the value of the existing key while keeping the other elements of payload.
I think it's done through upsert, but is it only possible to search and input all existing elements such as vector?
Thanks.

qdrant_client.overwrite_payload(
    collection_name="asan",
    # in my case, points=["9fad...(id)"]
    points=[Union[List[Union[int, str, PointId]], Filter, PointsSelector]],
    payload = {other elements of payload, new_key: new_value, ..},
)

This method is valid if choose to import and insert information from other existing payloads.
It is good that selecting a target point is strong through Filter.
Maybe it's looking for convenience, but it's not just for "=" and it would be nice to have a more flexible ability to modify payloads in the code, such as "append(extend)".

Hi @hwk06023
overwrite_payload as in the name, overwrites payload completely
there is another method, with which you can modify payload, it is called set_payload link


Remove unnecessary methods

We implement a bunch of traits for getting at the inner field. Also, the inner field is public. The into_inner and as_inner methods are just clutter - remove them.
Don't bother doing a deprecation cycle because this change (and crate) is so trivial.

cc @apoelstra just flagging for transparency - I was slack here.

Yeah, if the inner field is public I think it's fine to drop these.


Scaffolder : Passing login identity information from frontend to backend

It appears that we cannot pass the loggedin user identity information from scaffolder frontend to scaffolder backend plugins?
Or am I missing something here, tried various different options with vain.
Any pointers would be helpful

Duplicate of #5441

Thanks I will follow this up in another thread.


window - can't be used with window

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

What page(s) or areas on docs.getdbt.com are affected?
https://docs.getdbt.com/docs/build/metrics-overview
What changes are you suggesting?
"The accumulation window, such as 1 month, 7 days, 1 year. This can't be used with window."
I think this is not correct, window can't be used with window? Or please explain, thanks!
Additional information
No response

Thanks for catching this typo @wanalytics8 ! Fix propose din https://github.com/dbt-labs/docs.getdbt.com/pull/3982


Feature request: chronos distributed job scheduling

@bbaassssiiee thanks for the request! We currently have Chronos on the roadmap for the 0.5 release. You can follow the progress at #43.


Add a Developer Certificate of Origin

The Matrix.org Foundation is rolling out this DCO across all public repositories in its namespace. Of note, this DCO does not require the use of "real" or "legally identifiable" names.

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

Project coverage is 90.55%. Comparing base (9d90ff0) to head (69a7740).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
- Coverage   90.57%   90.55%   -0.02%
==========================================
  Files          34       34
  Lines        1909     1905       -4
==========================================
- Hits         1729     1725       -4
  Misses        180      180

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

I wonder if we should enforce this with a GitHub action https://github.com/apps/dco organization-wide.


wip: new(rules): add rule for detecting fileless execution via memfd_create

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

What this PR does / why we need it:
This PR takes advantage of a new incoming Falco feature for detecting fileless execution via memfd_create. This is a very well known defense evasion technique that threat actors might use to execute malware on victim machines. It has been used in the past, but also pretty recently as reported by these two articles:

https://cybersecurity.att.com/blogs/labs-research/malware-using-new-ezuri-memory-loader
https://www.wiz.io/blog/pyloose-first-python-based-fileless-attack-on-cloud-workloads
Putting this on wip until the feature lands in Falco.

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@loresuso we can soon start with merging rules that make the rules file incompatible with the current Falco as the next release is planned for end of Sep.

After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr

After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr

:+1:
Rules files have been split. @loresuso could you rebase this PR and address the above suggestions, please? :pray:

IMO it makes sense to uniformly bump the engine version. In this way, when we graduate rules, we don't need to bother or remember how the version should be bumped, and just move the rule between files, but I'm open to discuss!

/hold
We need to bump the required engine version. @leogr @LucaGuerra do we bump the rules engine uniformly in all rules files? I would vote for that!

What's the benefit of having the same required_engine_version?
The only two consequences I see

We will have to bump the minor version in all rules files https://github.com/falcosecurity/rules/blob/main/RELEASE.md#versioning-a-ruleset
We will make all files not compatible with a previous Falco engine (even if they are)

Moreover, the CI should already be able to check (and inform us) when an engine version bump is required. Indeed, this jobs matrix indicates that falco-incubating_rules.yaml is no longer compatible with 0.35.0 because the missing field

In the end, I don't have a strong opinion and am open to any solution. I just don't see the benefit of doing this (perhaps am I missing something? :thinking: )
In case we decide to bump all files, I still would avoid bumping falco-deprecated_rules.yaml, since it does not make much sense to me.

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.

@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?

The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.

ok then let's just bump it in the respective file for now, thanks!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 01650113bdbe0bb5383a3ee06151604fd4526b6b

/unhold


Trev8939/feature layer geo package

Adds a sample for FeatureLayer GeoPackage.
Also updates version.gradle to handle java language 1.8.

Thanks @shellygill. Fixes in!

Thanks @TADraeseke - changes look good to merge.


configure nginx to be proxy for app

instructions here >> https://vapor.github.io/documentation/deploy/nginx.html

that wasn't too bad


feature: Allow image tags to be used in place of digest (PROJQUAY-1890)

This PR will allow the images to be referenced by tag name OR by digest.

i think this area needs updating https://github.com/quay/quay-operator/blob/2d9adf38c5092f826051497b707a5dc1ce2a8db2/pkg/kustomize/kustomize.go#L323


typo: recommneded -> recommended

@nschonni : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

Merging typo fixes.

@ktoliver : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.


VSCode leaves text file without line terminator

Is this a feature?
Xcode editor always appends line terminator at the end of file.
$ cat Textfile.txt
hello$
$
$ file Textfile.txt
Textfile.txt: ASCII text, with no line terminators
$
VSCode Version: 1.38.1
macOS Mojave: 10.14.6

Please use the following user setting:
"files.insertFinalNewline": true


Asset Library causes Project Manager UI to extend beyond visible window

Godot version
4.1.1.stable.official
System information
Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz (4 Threads)
Issue description
What doesn't work:
When viewing community asset library projects, the UI can extend off the visible window to the right, it appears to be caused by projects with long names combined with the action of resizing the window.
The full UI only becomes visible at an extremely wide window size.
How it should work:
The entire UI should be visible regardless of window size or shape.

Steps to reproduce

open Godot project manager
click Asset Library Projects tab
Click support
check "community"
if the problem is not immediately present, resize window

Minimal reproduction project
N/A

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/80507 (this is fixed in 4.2.dev6).


Update Google site verification code

Our access to Google Webmaster Tools is no longer working. After speaking with Ash we have decided to replacing the verification code.
We are reducing the TTL to 5 minutes in case there is any problem with replacing the old verification code.
See:

https://github.com/alphagov/digitalmarketplace-aws/pull/163
https://github.com/alphagov/digitalmarketplace-buyer-frontend/pull/189

:+1:


chore: improve class hierarchy or sdk protocols vs core protocols

This is a change request
Problem
As of now we have convoluted class structure when:
FilterSDK.super -> BaseSDK.core -> FilterCore.super -> BaseProtocol
Proposed Solutions
Let's revisit it and try to remove extra steps in that chain.
Notes
Original threads: https://github.com/waku-org/js-waku/pull/2003#discussion_r1603014495 and https://github.com/waku-org/js-waku/pull/2003#discussion_r1603047083

ping @danisharora099 to share his experience with this and thoughts


Add ci2go under new Development -> CI/CD section

Project URL
https://github.com/ngs/ci2go
Category
Development -> CI/CD
Description
Add ci2go, macOS client for CircleCI
Why it should be included to Awesome macOS open source applications  (optional)
Because it's awesome. It works even for Apple Watch.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Appropriate language icon(s) added if applicable
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

  Generated by :no_entry_sign: Danger

@kimh Thanks for your contribution, but it is iOS application.


feat(cert): Support for extra TLS options

Support for extra SSL parameters for mqtt and http sources. Fixes #2241

LGTM. Just need to pass markdown check. Additionally, it'll be better to increase ut coverage to pass the condecov check. Thanks.

The markdown check fails in a file that I did not touch. Actually it is failing due to #2272 committed by @Yisaer  two days ago (see https://github.com/lf-edge/ekuiper/actions/runs/6269824039/job/17026819627).
Run markdownlint -c .github/workflows/markdown_config.json ./docs/
  markdownlint -c .github/workflows/markdown_config.json ./docs/
  shell: /usr/bin/bash -e {0}
docs/en_US/configuration/global_configurations.md:[2](https://github.com/lf-edge/ekuiper/actions/runs/6287798441/job/17072623952?pr=2258#step:4:2)[5](https://github.com/lf-edge/ekuiper/actions/runs/6287798441/job/17072623952?pr=2258#step:4:6)9 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

Locally, the markdown test passes so "it's not me, it's you" :)
❯ markdownlint -c .github/workflows/markdown_config.json docs
❯ echo $?
0

For tests, sure, I can add tests for those lines.

LGTM. Just need to pass markdown check. Additionally, it'll be better to increase ut coverage to pass the condecov check. Thanks.

The markdown check fails in a file that I did not touch. Actually it is failing due to #2272 committed by @Yisaer two days ago (see https://github.com/lf-edge/ekuiper/actions/runs/6269824039/job/17026819627).
Run markdownlint -c .github/workflows/markdown_config.json ./docs/
  markdownlint -c .github/workflows/markdown_config.json ./docs/
  shell: /usr/bin/bash -e {0}
docs/en_US/configuration/global_configurations.md:[2](https://github.com/lf-edge/ekuiper/actions/runs/6287798441/job/17072623952?pr=2258#step:4:2)[5](https://github.com/lf-edge/ekuiper/actions/runs/6287798441/job/17072623952?pr=2258#step:4:6)9 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

Locally, the markdown test passes so "it's not me, it's you" :)
❯ markdownlint -c .github/workflows/markdown_config.json docs
❯ echo $?
0

For tests, sure, I can add tests for those lines.

Ah, it's weird. The markdown check should have run in that PR. Never mind, we'll fix that. Appreciate your patience.

plz update the base master branch as we have fixed the markdown lint error


'RuntimeException' with message 'Function has already been defined'

I have humbug installed as a global dependency on my computer using composer global require humbug/humbug. Now if I execute humbug in a repo where it was also installed as a dependency, I get a RuntimeException saying 'Function has already been defined'.
I can execute the local humbug just fine with ./vendor/bin/humbug.
PHP Fatal error:  Uncaught exception 'RuntimeException' with message 'Function has already been defined' in /home/foo/project/vendor/padraic/humbug_get_contents/src/function.php:35

@marcaube It's an issue with humbug_get_contents throwing an Exception because two files are clashing over the same function. Easy fix - I'll remove the exception ;).

A new 1.0.3 tag for that dependency is pushed - do a composer update and that should resolve the issue.

The error is back since this commit in phar-updater yesterday.
PHP Fatal error:  Uncaught exception 'RuntimeException' with message 'Function has already been defined' in /home/foo/project/vendor/padraic/humbug_get_contents/src/function.php:25

Noted. I'm doing some work on phar-updater. Once that's done, the dependency will revert most likely to a new 1.0.4. I'll reopen here for tracking.

@marcaube This should now be fixed after a composer update ;)


[ColorPicker] Crash when typing color name that already exists

Microsoft PowerToys version
0.73.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
ColorPicker
Steps to reproduce

Go to Color Picker Settings
Add new color format
Save new color format, perhaps as "TEST"
Edit color format
Select name contents, delete them
Start typing an existing color name that already exists, perhaps "RGB"
As soon as you type the 'B', it crashes.

✔ Expected Behavior
No crash
❌ Actual Behavior
Crash
Other Software
No response

@ForbiddenEra
Please update to the latest PT version. It should be fixed in 0.74.0!

@ForbiddenEra Please update to the latest PT version. It should be fixed in 0.74.0!

I literally just did an update inside the app which is why I was toying around with it in the first place :)

@ForbiddenEra Please update to the latest PT version. It should be fixed in 0.74.0!

Yep; now that it's updated it seems to behave as expected, disabling the update button until the name collision is solved.
I probably should have searched this one before posting since I guess it was already known; my bad - but I figured 0.73.0 was reasonably new since it just updated to that like 20 minutes ago..not sure why it didn't just go straight to 0.74.0 but maybe it hadn't propagated to all the distribution servers or something (just pulling that out of my a$$ as I have no idea how UWP apps really work)


Update CONTRIBUTING.md

spelling of only corrected at line no 9

spelling of only corrected at line no 9


Can't locate Pod/Parser.pm in @INC

The test suite fails on some of my smoker systems because of a missing dependency. Just for info: according to corelist Pod::Parser was removed from core perl with version v5.31.1.
#   Failed test 'Pod/AsciiDoctor.pm loaded ok'
#   at t/00-compile.t line 43.
#          got: '512'
#     expected: '0'
Can't locate Pod/Parser.pm in @INC (you may need to install the Pod::Parser module) (@INC contains:  .) at /usr/local/lib/perl5/5.32/parent.pm line 16.
BEGIN failed--compilation aborted at /usr/home/cpansand/.cpan/build/2023020204/Pod-AsciiDoctor-0.101000-0/blib/lib/Pod/AsciiDoctor.pm line 6.
Compilation failed in require at -e line 1.
# Looks like you failed 1 test of 1.
t/00-compile.t .....
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
... etc ...

Happens also with Pod-AsciiDoctor-0.101001

@eserte : hi. is it ok now?

@eserte : closing for now.


v2.0-rc

NEXT MAJOR release
The following items are to be included with the next MAJOR release of the Auro WC-Generator, all PRs are to be from the feature branch to v2.0-rc branch.

[ ] https://github.com/AlaskaAirlines/auro-table/issues/14

Closing the rc in favor in individual issues and the milestone.


clockTolerance allows passing string

Please do not report security vulnerabilities here. The Responsible Disclosure Program details the procedure for disclosing security issues.
Thank you in advance for helping us to improve this library! Please read through the template below and answer all relevant questions. Your additional work here is greatly appreciated and will help us respond as quickly as possible. For general support or usage questions, use the Auth0 Community or Auth0 Support. Finally, to avoid duplicates, please search existing Issues before submitting one here.
By submitting an Issue to this repository, you agree to the terms within the Auth0 Code of Conduct.
Description
The documentation says:
clockTolerance: number of seconds to tolerate when checking the nbf and exp claims, to deal with small clock differences among different servers

However, it is possible to pass a number in a string format. It causes unexpected behavior but typical for JavaScript. For example, if we have timestamp<PHONE_NUMBER> and set clockTolerance to "30" the following code (used to e.g. check expiration):
console.log('expiration', payload.exp + (options.clockTolerance || 0))

will print "158589663330" ( like 4 + "9" == "49" ). There should be an additional check like in the clockTimestamp property:
if (options.clockTimestamp && typeof options.clockTimestamp !== 'number') {
    return done(new JsonWebTokenError('clockTimestamp must be a number'));
  }

Reproduction
Just run:
jwt.verify( token, { clockTolerance: "30" } )

Environment

Please provide the following:

Version of this library used: 8.5.1
Version of the platform or framework used, if applicable: Node.js v12.16.1
Other relevant versions (language, server software, OS, browser): MacOS Catalina
Other modules/plugins/libraries that might be involved: none

I'm closing it - duplicate of https://github.com/auth0/node-jsonwebtoken/issues/606


Flutter: What is Flutter?

A README file to understand what is Flutter.
The reference you may take:
Flutter Docs: https://flutter.dev/
https://github.com/dwyl/learn-flutter
https://github.com/Asabeneh/30-Days-Of-JavaScript/blob/master/04_Day_Conditionals/04_day_conditionals.md
(This is JS repository, ours should also look like this only)

Can I work on this issue.I'm a contributor on GWoC'21

Can I be assigned this issue?

@SurabhiMishra Assigned you another topic

can I work on this?

I'm a contributor in GWOC'21 can I work on this issue?

May I work on this issue as I have already wriiten blog on this topic..


Feature Request: Allow list[str] for stubPath setting

Currently the stubPath setting takes a string (indicating which directory contains stubs).
I'd like to pass a list of strings (indicating which directories contain stubs).
Motivation:
Some of my stubs are automatically generated by computers, and some of my stubs are coded by hand. I'd like to keep these sets of stubs in separate directories.
Describe the solution you'd like
It would be nice to be able to set stubPath = ["generated", "stubs"] in my pyproject.toml file.
Additional context
$PYTHONPATH and $MYPYPATH, which are comparable to stubPath, allow multiple directories.

Moving this issue to discussion as an enhancement request for comments and upvotes.


Do you provide a model checkpoint

Hi. I will like to ask if you provide a model checkpoint for the architecture.
Many thanks.

I would like to do so, yet, I haven't got a reliable source for storing the weights. The weights might come in few weeks.


ImportError for jwt.algorithms on Linux armv7l

Using Nuitka <IP_ADDRESS>, Python 3.8, I have the following ImportError on Linux armv7l. Using the same code and Nuitka version, I don't have the issue on x86_64 or aarch64 (armv8).
Traceback (most recent call last):
  File "/opt/app/main.dist/main.py", line 2, in <module>
ImportError: cannot import name 'RSAAlgorithm' from 'jwt.algorithms' (/opt/app/main.dist/jwt/algorithms.py)

The code is:
import jwt
from jwt.algorithms import RSAAlgorithm
from jwt.api_jws import _jws_global_obj

if "RS256" in _jws_global_obj._algorithms:
    jwt.unregister_algorithm("RS256")
jwt.register_algorithm("RS256", RSAAlgorithm(RSAAlgorithm.SHA256))

print("It's working,")

Easy to reproduce using Docker (see https://github.com/levesquejf/nuitka-jwt-algorithms-not-imported) on a Linux x86_64 machine. The second script is configured for cross-compilation. It is slow but it's normal.
./run-nuitka.sh is building on x86_64 and it's working
./run-nuitka-armv7l.sh is building on armv7l and it's failing

This works on my native armv7l just fine. The cross compiling setup is not supported as you know. Get in touch privately if you are willing to provide funding for me researching why it's happening, otherwise I can't really look at this.

So, this is on raspberrypi3-python:3.8.3-stretch-build which is relatively old, but well-supported by Nuitka. I am trying to reproduce it without docker, but since I fail to understand the dockerfile, I am running them with podman now.
What puzzles me is the cross-build-start RUN for which I don't see the file anywhere.

I have to assume it's contained in the images, and as such is something that these images provide, would that be correct?

@kayhayen Take a look at this: https://www.balena.io/docs/reference/base-images/base-images/#building-arm-containers-on-x86-machines.

Just to keep this on my mind: One approach, we could use, is to cross-compile a Python in there, and then convince pip to install wheels into there. Alternatively, we could use qemu/kvm to install a debian. I have used qemu images of various arches of stretch in the past to test Nuitka. But that approach was not aging well. I recall bootstraping ARM machines with qemu in the past too.
We only need the files from in there, so even if that's slow to create, it would be fine. What I think we need is some sort of "remote" access, where Nuitka scans remote Python code, and would use the ".so" and do its ldd lookups.

Judging by the speed of the installation however, and it's installing armhf packages, I might be on the wrong track, and this image is being actually executed in emulation already, in which case, this wouldn't be about cross compiling all that much.

Still catching up on my ignorance, but I found this for the cross scripts: https://www.balena.io/blog/building-arm-containers-on-any-x86-machine-even-dockerhub/

That's pretty neat technology I have to say, but it's making life a bit harder for debug logins, but I guess I only have to remove the "end" of that cross scripts.

Ok, I think I found a problem with your code:
STEP 10: RUN pipenv run python main.py
Traceback (most recent call last):
  File "main.py", line 2, in <module>
    from jwt.algorithms import RSAAlgorithm
ImportError: cannot import name 'RSAAlgorithm' from 'jwt.algorithms' (/root/.local/share/virtualenvs/app-ueEJiAOq/lib/python3.8/site-packages/jwt/algorithms.py)

It's not actually a difference, pure Python does not work! Nuitka will not be able to change that.
Now the question is, does armhf on Debian stretch have the support for this? It may not use wheels for each platform, esp. not the unusual ones, I think armhf is a dead end that Debian once had, but generally fell out of favor. I was doing my test on armv7l and regarding i386, that's also fallen out of favor. They may no longer support those with binary wheels which make it easy to use.
So I think you may either find an older version that still had those wheels, but seeing you use want to use 3.8 that is not going to happen.
Or you need to compile the wheels more properly from source with their development header packages dependencies installed. I am having the build of the pipenv cached, not sure if it would output what's missing. I also couldn't immediately find their CI config with how they build their wheels.
I hope this helps!

Of course, I don't expect Nuitka to work if native Python is not... Let me take a closer look on that code and if it's really needed and I will get back to you. Thanks for your help today.

You will be very welcome.


doc : Support build ARM CloudImage in AMD environment

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Using ImageSave, so needn't qemu anymore


refactor(ci): Update assets server pipeline to support new naming schema.

Before we can implement the new naming convention in cloudoperators/juno, we need to modify the assets server pipeline to no longer depend on specific directories like apps or libs. Instead, it should accept arbitrary directories, allowing us to designate the packages directory as a future source.
Additionally, we should adjust the shared task for uploading third-party assets accordingly.

related to #620


Block xDS REST endpoint access from outside

Hi
We have configured envoy using xDS with REST-JSON URL. The problem we have is if we send external request (from postman) to envoy gateway for xDS REST endpoints like v2/discovery:routes it return the envoy DiscoveryResponse from the service.
How can we block this external request for xDS REST Endpoints? I tried adding a route for these REST URL but it doesn’t work.

This question needs some more information to answer. What is "postman"? Why are you routing to your xDS API server external requests through the Envoy gateway? I think this is almost certainly a configuration error.

Hi @htuch
Postman is an application to make HTTP requests : https://www.postman.com/
The xDS API server accept a post request from envoy that returns the route and cluster information, right? However, what we found was that any client can make request to the API server and fetch those information, so we are asking how can we block that access by anyone other than envoy itself?

Adding http redirect filter to xDS urls did the trick!


Completion gets distorted when output is larger than window size

In a proper sized terminal window the output of (e.g.) cloudctl ip <tab> looks like this:
% c ip
allocate  (allocate a static IP address for your project that can be used for your cluster's service type load balancer)
delete    (delete an ip)
list      (list ips)
static    (make an ephemeral ip static such that it won't be deleted if not used anymore)

However, if the window does not fit the text lines without breaking anymore (that is, if one increases font size or decreases the window size) then the output of cloudctl ip <tab> looks like this:
% c ip
$allocate  (allocate a static IP address for your project that can be used for your cluster\s
service
type342200246) delete\ \ \ \ \(delete\ an\ ip\) list\ \ \ \ \ \ \(list\ ips\) static\ \ \ \ \(make\ an\ ephemeral\ ip\ static\ such\ that\ it\ won\t be deleted if not used anymore)

The behavior is the same with all completions which contain help texts.
So it seems cloudctl is aware of the window size and tries to adapt somehow, but this fails. I'd suggest not to adapt at all.
Env:
bash 5.1.4(1)-release

% c version
client: v0.10.19 (72d20d71), tags/v0.10.19-0-g72d20d7, 2022-06-21T07:45:10Z, go1.18.3
server:
    builddate: "2022-06-20T13:47:20Z"
    gitsha1: 4897315c
    name: cloud-api
    revision: tags/v0.18.23-0-g4897315
    version: v0.18.23

Pretty sure this depends on your terminal implementation, cannot reproduce with neither gnome-shell nor console (the successor of the former)

My default console is xfce-term and I can reproduce it in konsole (the kde one) and xterm.

code completion is not implemented by us, we simply use the completion framework provided by the cobra cli framework, which is used by almost all go based cli tools, including kubectl, helm and others.

Ok so you think I shall open an issue at the cobra project?

First you could try completion debugging as described here: https://github.com/spf13/cobra/blob/master/shell_completions.md#debugging

All right, now it's getting weird.
I tried as suggested, but the debugging output was identical to the expected (not actual) output.
Then - in order to submit an issue - I created a minimal completion app based on the example in the docs. Running this example's completion in a too small window worked fine, no distortions.
But then I tried cloudctl and - believe it or not - now it worked here as well!
And even today a couple of days later after updating cloudctl, the issue seems to be fixed. Other than installing the golang environment nothing changed on my system. However, the issue persists with other tools like kubectl.
While I don't really understand whats going on here, from my point of view it's fixed and the issue could be closed anyway.

Is it possible that this is related to the cobra update to v1.5.0 we made in the last release ?
We don't close issues someone raised, this should be done by the person who raised the issue.

Sounds reasonable, since with my own test I used the latest version as well.


GDNative C example not working on Windows

Godot version: 3.0.5 (64 bit)
OS: Windows 10 (64 bit)
Issue description:
Working through the GDNative C example here, I made it to the last step, where I build the project. Unfortunately, I get the following error:
Attempt to call function 'new' in base 'NativeScript' on a null instance.

Other Godot users experienced this issue and brought it up here. None of the suggestions in that thread helped in my case.
Steps to reproduce:
Download the attached project archive (also contains the godot_headers I used) and attempt to build. You may need Windows 10 to do this since it is using .dlls.
Minimal reproduction project:
GDNative.zip

That might be a problem in the documentation (so more fit to https://github.com/godotengine/godot-docs)

Closing in favor of https://github.com/godotengine/godot-docs/issues/2921.


make the labels clickable.

Now the onPress function only triggered when pressed on the circle button, let's make it possible when press on the label also.

Please, merge this asap!

Hi, Would love this feature too. Could you merge it ? Please

Thanks @troyz


Non-intuitive experiment name and tag

I have subdirectories for each experiment run in my logdir but when I convert it to Neptune, the name of the experiment is not the name of the run (which I would expect):
run_2770230158384141070/events.out.tfevents.1553086648.pascal01.intra.codilime.com
The tag is also a bit confusing to me since it is the same as the experiment name.
I would expect to have the run directory, event file, and computer name as separate entities, preferably as an experiment property even.

Hi,
Let's do the following:

experiment name is the name of the TB run
"computer name" is "host name" in neptune. It is system column. Is it correct @lukasz-walkiewicz ?
logdir (this path), is logged as neptune property. Key: logdir, value: absolute path
events file is logged as neptune property: key: events-file, value: name of this file

Do you agree @jakubczakon . If so, let's discuss ETA with @pitercl
Best,
Kamil

Hi,

Yes, it is. We can save computer name inside host name property.
What do you mean by absolute path? Do you mean the path to the run file starting from the root element or do you mean the path from the logdir to the run file? IMHO the second option makes more sense.

@jakubczakon This tag is used when we are trying to find out if the event file was converted to a Neptune experiment before, so you should consider it as an implementation detail.

@lukasz-walkiewicz I see, cool.

@kamil-kaczmarek I like it, thanks!

Hi,
Good! So the requirements are:

experiment name is the name of the TB run. Note, that is might be run_2770230158384141070 like in Kuba's example at the top on this issue, or mnist/test. We handle both cases.
add host name to the system column, extracted from this long string: run_2770230158384141070/events.out.tfevents.1553086648.pascal01.intra.codilime.com
logdir (this path), is logged as neptune property. Key: logdir, value: path from logdir, with logdir included.
events file is logged as neptune property: key: events-file, value: name of this file

@jakubczakon @lukasz-walkiewicz please confirm that it it Ok.
Best,
Kamil
:smiley:

ok

implemented better experiment name and hostname: #10

thanks @hubertjaworskineptune
let me know once merged.

Released in https://github.com/neptune-ml/neptune-tensorboard/releases/tag/0.2.0


Use dep to manage external imports, fix imports and run goimport

This is a first level clean up and will be followed by lint fixes.

https://github.com/Grarak/GoYTFetcher/commit/1653c4dc90fdb5d7ea1b0612bf0582f92fa12bff
Left out your other commits, because I don't really want the vendor folder in the repo


Missing support for erf (and related I guess) again

same as #364
MWE:
using Enzyme, Test, SpecialFunctions

f1(x) = erf(x)*x
@show first(autodiff(Reverse, f1, Active(1.0))[1])

and I get:
ERROR: Enzyme execution failed.
Enzyme compilation failed.
Current scope:
; Function Attrs: mustprogress willreturn
define "enzyme_type"="{[-1]:Float@double}" double @preprocess_julia_f1_1412(double "enzyme_type"="{[-1]:Float@double}" "enzymejl_parmtype"="140718177488032" "enzymejl_parmtype_ref"="0" %0) local_unnamed_addr #3 !dbg !23 {
top:
  %1 = call {}*** @julia.get_pgcstack() #4
  %ptls_field3 = getelementptr inbounds {}**, {}*** %1, i64 2
  %2 = bitcast {}*** %ptls_field3 to i64***
  %ptls_load45 = load i64**, i64*** %2, align 8, !tbaa !8
  %3 = getelementptr inbounds i64*, i64** %ptls_load45, i64 2
  %safepoint = load i64*, i64** %3, align 8, !tbaa !12
  fence syncscope("singlethread") seq_cst
  call void @julia.safepoint(i64* %safepoint) #4, !dbg !24
  fence syncscope("singlethread") seq_cst
  %4 = call double @.text(double %0) #4, !dbg !25
  %5 = fmul double %4, %0, !dbg !27
  ret double %5, !dbg !27
}

No augmented forward pass found for .text
 at context:   %4 = call double @.text(double %0) #4, !dbg !15

Stacktrace:
 [1] _erf
   @ C:\Users\Nicola\.julia\packages\SpecialFunctions\npKKV\src\erf.jl:15
 [2] erf
   @ C:\Users\Nicola\.julia\packages\SpecialFunctions\npKKV\src\erf.jl:13
 [3] f1
   @ .\REPL[2]:1

Stacktrace:
 [1] throwerr(cstr::Cstring)
   @ Enzyme.Compiler C:\Users\Nicola\.julia\packages\Enzyme\F71IJ\src\compiler.jl:1338

What is your Julia version, operating system, Enzyme version, and the result of st?

Enzyme v0.12.9, julia 1.10.2, windows.

Hm i think we'll need a call or something to debug this, since I have been able to reproduce this and our windows CI passes for this.
Are you available next week some time?


Added support for slice.indices

Fixes #1349
(unless full support would now involve being able to pass slices back to python?)
This PR adds support for the slice.indices method in compiled code. This was discussed a bit on gitter. It was my first time working with any of the extending code, so this could definitely use a looking over 🤞.

@ivirshup thanks for this, we appreciate you submitting this PR! I have now queued it for review.

it looks like CI is failing due to the type hints causing a SyntaxError on Python 2.7. It will be removing those to see if that fixes all the issues.

@esc, I think I've addressed the issues you raised. Let me know what you think.
I also caught a few bugs related to exceptions not being thrown by the numba function. I think I've handled this right...
A slightly more general question, how can I benchmark this kind of function without including slice construction/ conversion time? I'm worried if I declare the slice in a numba function llvm might figure out it's a constant and optimize for it. Do I just have to measure conversion/ construction separately and subtract it?

A slightly more general question, how can I benchmark this kind of function without including slice construction/ conversion time? I'm worried if I declare the slice in a numba function llvm might figure out it's a constant and optimize for it. Do I just have to measure conversion/ construction separately and subtract it?

@stuartarchibald probably has an answer for this.

@ivirshup thanks for addressing the review remarks. I have left a few more comments for your consideration. The PR is definitely going in the right direction, good job!

@esc, I'm having some difficulty with this python2 stuff. I'll lay out where I'm at, and then what I'm thinking.
In python2, slice(...).indices({negative_integer}) doesn't throw an error. It does, (based on the python change log) return nonsense results, since a negative length isn't really a valid case. In the spirit of compatibility I've tried to replicate those nonsense results, but there's a case where I'm not sure I can replicate without a lot of effort. When slice.stop is None, slice.step < 0, and length < 0, python2 returns maxint + length for the stop value from slice.indices. Here's an example:
>>> slice(None, None, -2).indices(-1)
(-2,<PHONE_NUMBER>854775807, -2)

Since numba slices don't store None,  just integer values which give equivalent slicing results, I can't think of how to tell when this case occurs without modifying the constructor and kinds of values numba slices hold.
To me, this seems like probably too much work to replicate what's pretty seems like a bug (or at least undefined behaviour) in python2, especially since python2 won't even be supported in a few months. As an alternative, I'm thinking I'll just not test the equivalency of results for slice.indices in python2 when length is negative, and keeping it a ValueError (like in python3) instead of returning nonsense.
Thoughts?

@ivirshup Given Python 2 has about 2-3 months of support left with Numba I'm inclined to not worry about it too much either. I don't think it's worth trying to accurately reproduce this result as I doubt code is going to be relying on it. As suggested, perhaps just make this work on Python 3 correctly and then skip the unusual result case in the unit tests on Python 2 and leave a note about why? Thanks.

@stuartarchibald, @esc, thanks for the feedback! I've updated the comment in the test to give more background on why those cases are disabled.
Is there anything else I should change here?

@ivirshup thanks for the inquiry, I'll queue it for the next round of inspection.

I tried to run the code with the disable_leak_check commented out and the tests don't seem to be leaking anything. @stuartarchibald is this to be expected?

@ivirshup o.k. so, since the function you are testing doesn't allocate anything that could leak, raising the exceptions during testing doesn't leak either. Sorry for the confusion. My  recommendation would be to remove the disable_leak_check but leave in the MemoryLeakMixin to protect agains any regressions.

@esc, no problem. I've pushed those changes.

@ivirshup thanks for your persistence, I think this is now almost ready for merge. I'd like to request a final review from @stuartarchibald or @sklam and it is good to go.

Thanks for the feedback!


In some cases Run button doesn't work

open charting tutorial
expand code cell for Custom Plot Example
set cursor to the 1st line
scroll down so Run button becomes visible
click Run

result:
cursor was set to the last line
the code wasn't executed

i get the cursor going to the last line which is a bug, but the code is executed fine.
clicking in the bkg of the code cell below the cm should move the cursor to the end.
i think this is misfiring if user clicks on run button.


All function definitions don't follow the style guide of the t_ prefix.

Either the style guide or the code should be refactored. Most likely this will be solved using a poll.

Has already been voted for.
Conclusion: t_ must be removed from the style guide.

Created a new pull request in the website repository. I have removed all t_'s from the function arguments in the project.


I am getting a 429 error

I am getting a 429 error, this I know is a rate limit error. Is there anyway to get around this with the YouTube "kookie" section in the .json file? Is there anyway to run this with proxies?

Try changing VPS host
Or Try different API Key

watch this
https://www.youtube.com/watch?v=9bZGT9frKLw


Fix wrong inject_yum_repo plugin name in prebuild task definition

CLOUDBLD-8243

Signed-off-by: Chenxiong Qi<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

Didn't we agree that the plugin would be renamed to "inject_yum_repos" after the plugins get merged?

I am working on merging the plugins to inject repos. Those plugins, once merged, are renamed to inject_yum_repos so this change will need to be changed back. I'd say rather than changing it back we just leave it as is.

Hi, sorry for confusion. I'll close this PR and please go ahead with what you are doing now. I made this change to unblock my test.


add proxy from UI to backend service

Description
This PR completes the previous PR on console plugin, by adding a proxy to the OLS application service.
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[x] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/assign @vbelouso

/lgtm
/approve


Error: No Project. in 'Object.ThrowNoProject' during 'signatureHelp'

This issue comes from crash dumps in telemetry. We've tried to de-duplicate issues on a best-effort basis, comparing the sequence of methods called and the command requested while ignoring line numbers.
TypeScript Version Prefix: 2.7.1
VSCode Version 1.20.0-insider
command requested: signatureHelp
hitting sessions: 652
proportion of all sessions: 0.002433989241170256
stack
Error: No Project.
    at Object.ThrowNoProject (tsserver.js:84217:23)
    at ProjectService.getDefaultProjectForFile (tsserver.js:87395:46)
    at IOSession.Session.getFileAndProjectWorker (tsserver.js:89772:87)
    at IOSession.Session.getFileAndProject (tsserver.js:89757:29)
    at IOSession.Session.getSignatureHelpItems (tsserver.js:89977:31)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:89035:61)
    at unknown (tsserver.js:90393:88)
    at IOSession.Session.executeWithRequestId (tsserver.js:90384:28)
    at IOSession.Session.executeCommand (tsserver.js:90393:33)
    at IOSession.Session.onMessage (tsserver.js:90413:35)
    at Interface.<anonymous> (tsserver.js:91614:27)
    at emitOne (events.js:96:13)
    at Interface.emit (events.js:191:7)
    at Interface._onLine (readline.js:241:10)
    at Interface._normalWrite (readline.js:384:12)
    at Socket.ondata (readline.js:101:10)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)

looks like a duplicate of https://github.com/Microsoft/TypeScript/issues/20629


[DR] Multi-block moments App (and also pattern for other Apps)

Prototype/Production Branches
Please see the branch multib-app for work on moments App. I consider this to be a production branch and other Apps, including GK, will be modified here to support multi-blocks.
Introduction
Extensions to multi-block (MB) geometry will allow us to do far more complex geometry simulations. However, manually specifying the inputs to setup can be tedious and potentially error-prone. In this DR I propose a few design principles and a proposed input driver for moments App.
Principles

The changes to the existing (single-block) App should be minimal or even zero. No API changes should be done unless absolutely needed
The MB App should become the default: to avoid changes to the existing drivers and Lua wrappers we should eventually replace the single-block App new() method to actually call the MB App new() with a single block and other data constructed manually (but hidden from user)
The MB App should minimize (ideally, avoid all together) input duplication
The MP App API names should be identical to the single-block API names, except of course a prefix change (for example, we need to add multib to the API names).
Bespoke changes to the core infra should not be done. Thought should be given to properly extending the infra to increase general capabilities, and not merely implement in haste a collection of one-off functions just for MB.

Running Example for this DR
I am using a 3 block Euler simulation with the following block layout.
  /* Block layout and coordinates

   Y
   ^
   |
   2  +------+
   |  |b0    |
   |  |      |
   1  +------+-----+
   |  |b1    |b2   |
   |  |      |     |
   0  +------+-----+

      0 -----1-----2 -> X
  */

Geometry Specification
I propose introducing a new geometry object that will hold the geometric information (cells, lower, upper bounds and mapc2p, etc) and the topology. This object is mostly App agnostic, but could contain App specific features as needed. For example, the API for this is:
// Geometry info a single config-space block
struct gkyl_block_info {
  // lower and upper extents of blocks
  double lower[GKYL_MAX_CDIM], upper[GKYL_MAX_CDIM];
  int cells[GKYL_MAX_CDIM]; // cells extents in each direction
  int cuts[GKYL_MAX_CDIM];  // domain split to use

  struct gkyl_target_edge connections[GKYL_MAX_CDIM][2]; // block connections
};

This is then used to populate the geometry object, for example, for a block:
  // block 0
  gkyl_block_geom_set_block(bgeom, 0, &(struct gkyl_block_info) {
      .lower = { 0, 1 },
      .upper = { 1, 2 },
      .cells = { 128, 128 },

      .connections[0] = { // x-direction connections
        { .bid = 0, .dir = 0, .edge = GKYL_PHYSICAL }, // physical boundary
        { .bid = 0, .dir = 0, .edge = GKYL_PHYSICAL }  // physical boundary
      },
      .connections[1] = { // y-direction connections
        { .bid = 1, .dir = 1, .edge = GKYL_UPPER_POSITIVE },
        { .bid = 0, .dir = 1, .edge = GKYL_PHYSICAL } // physical boundary
      }
    }
  );

Species and Field Inputs
I propose splitting inputs for species and fields into two parts: a part that is block independent, a part that is per-block. The per-block data need not be repeated if it is common to all block.
For example, the moment species data for an Euler solver would be:
  // all data is common across blocks
  struct gkyl_moment_multib_species_pb euler_blocks[1];
  euler_blocks[0] = (struct gkyl_moment_multib_species_pb) {
    .init = initFluidSod,
  };

  struct gkyl_moment_multib_species euler = {
    .name = "euler",
    .charge = 0.0, .mass = 1.0,
    .equation = euler_eqn,

    .are_all_blocks_same = true,
    .blocks = euler_blocks,
    .bcs = euler_phys_bcs,
  };

Note the use of the flag are_all_blocks_same to indicate that the blocks array has only 1 element in it.
To specify the BCs for each block I propose we introduce another input list that specifies the BCs as follows. The struct would be:
// BC for blocks
struct gkyl_block_physical_bcs {
  int bidx; // block index
  int dir;  // direction in which BC is specified
  enum gkyl_edge_loc edge; // which edge this BC is for
  int bc_type; // BC code
};

This seems different than our usual way to specifying BCs in single-block Apps, but it reduces the potential for setting inconsistent BCs, and reduces duplication. For the Euler simulation this list would be specified as:
  struct gkyl_block_physical_bcs euler_phys_bcs[] = {
    // block 0 BCs
    { .bidx = 0, .dir = 0, .edge = GKYL_LOWER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
    { .bidx = 0, .dir = 0, .edge = GKYL_UPPER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
    { .bidx = 0, .dir = 1, .edge = GKYL_UPPER_EDGE, .bc_type = GKYL_SPECIES_COPY },
    // block 1 BCs
    { .bidx = 1, .dir = 0, .edge = GKYL_LOWER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
    { .bidx = 1, .dir = 1, .edge = GKYL_LOWER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
    // block 2 BCs
    { .bidx = 2, .dir = 0, .edge = GKYL_UPPER_EDGE, .bc_type = GKYL_SPECIES_COPY },
    { .bidx = 2, .dir = 1, .edge = GKYL_LOWER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
    { .bidx = 2, .dir = 1, .edge = GKYL_UPPER_EDGE, .bc_type = GKYL_SPECIES_REFLECT },
  };

On Running Multi-Blocks in Parallel
This is a major unknown. We want to support N blocks with M communicators, with M<=N. This means, a communicator could have any number of blocks it handles. We could hide this by duplicating communicators so that M=N. For example, a 3 block serial simulation would have 3 null_comm, effectively updating each block sequentially. Even for MPI or nccl we could make M=N, but where some communicators are duplicates. Then, the update loop would be merely a loop over all blocks on all ranks, with the actual update only occurring on the ranks where the block is "valid".

I have updated the DR based on further work on July 5th 2024. At this point this DR is ready for review.

Some random notes on how to split ranks across communicator. Will clean up later.
Case where num_ranks >= num_blocks
global: [ 0 1 2 3 4 5]
color:   [ 0 0 1 1 2 2]
split:    [ 0 1 0 1 0 1]

MPI_COMM_WORLD
MY_COMM_COLOR
my_color
my_decomp
my_app (my_decomp, MY_COMM_COLOR)
In this case each rank only holds a pointer to ONE App
Case where num_ranks = 1
In this case the rank must hold num_block App pointers
General case: num_ranks <= num_blocks
Each rank holds pointers to [1 ... num_blocks] App. This means we must allow overlapping decomp!

The work proposed in this DR is completed and merged into the gk-g0-app branch.


Advent of code 5

--- Day 5: Print Queue ---
Satisfied with their search on Ceres, the squadron of scholars suggests subsequently scanning the stationery stacks of sub-basement 17.
The North Pole printing department is busier than ever this close to Christmas, and while The Historians continue their search of this historically significant facility, an Elf operating a very familiar printer beckons you over.
The Elf must recognize you, because they waste no time explaining that the new sleigh launch safety manual updates won't print correctly. Failure to update the safety manuals would be dire indeed, so you offer your services.
Safety protocols clearly indicate that new pages for the safety manuals must be printed in a very specific order. The notation X|Y means that if both page number X and page number Y are to be produced as part of an update, page number X must be printed at some point before page number Y.
The Elf has for you both the page ordering rules and the pages to produce in each update (your puzzle input), but can't figure out whether each update has the pages in the right order.
For example:
47|53
97|13
97|61
97|47
75|29
61|13
75|53
29|13
97|29
53|29
61|53
97|53
61|29
47|13
75|47
97|75
47|61
75|61
47|29
75|13
53|13
75,47,61,53,29
97,61,53,29,13
75,29,13
75,97,47,61,53
61,13,29
97,13,75,29,47
The first section specifies the page ordering rules, one per line. The first rule, 47|53, means that if an update includes both page number 47 and page number 53, then page number 47 must be printed at some point before page number 53. (47 doesn't necessarily need to be immediately before 53; other pages are allowed to be between them.)
The second section specifies the page numbers of each update. Because most safety manuals are different, the pages needed in the updates are different too. The first update, 75,47,61,53,29, means that the update consists of page numbers 75, 47, 61, 53, and 29.
To get the printers going as soon as possible, start by identifying which updates are already in the right order.
In the above example, the first update (75,47,61,53,29) is in the right order:
75 is correctly first because there are rules that put each other page after it: 75|47, 75|61, 75|53, and 75|29.
47 is correctly second because 75 must be before it (75|47) and every other page must be after it according to 47|61, 47|53, and 47|29.
61 is correctly in the middle because 75 and 47 are before it (75|61 and 47|61) and 53 and 29 are after it (61|53 and 61|29).
53 is correctly fourth because it is before page number 29 (53|29).
29 is the only page left and so is correctly last.
Because the first update does not include some page numbers, the ordering rules involving those missing page numbers are ignored.
The second and third updates are also in the correct order according to the rules. Like the first update, they also do not include every page number, and so only some of the ordering rules apply - within each update, the ordering rules that involve missing page numbers are not used.
The fourth update, 75,97,47,61,53, is not in the correct order: it would print 75 before 97, which violates the rule 97|75.
The fifth update, 61,13,29, is also not in the correct order, since it breaks the rule 29|13.
The last update, 97,13,75,29,47, is not in the correct order due to breaking several rules.
For some reason, the Elves also need to know the middle page number of each update being printed. Because you are currently only printing the correctly-ordered updates, you will need to find the middle page number of each correctly-ordered update. In the above example, the correctly-ordered updates are:
75,47,61,53,29
97,61,53,29,13
75,29,13
These have middle page numbers of 61, 53, and 29 respectively. Adding these page numbers together gives 143.
Of course, you'll need to be careful: the actual list of page ordering rules is bigger and more complicated than the above example.
Determine which updates are already in the correct order. What do you get if you add up the middle page number from those correctly-ordered updates?
The data is located in aoc5.txt
git-bob try to implement this.

--- Part Two ---
While the Elves get to work printing the correctly-ordered updates, you have a little time to fix the rest of them.
For each of the incorrectly-ordered updates, use the page ordering rules to put the page numbers in the right order. For the above example, here are the three incorrectly-ordered updates and their correct orderings:
75,97,47,61,53 becomes 97,75,47,61,53.
61,13,29 becomes 61,29,13.
97,13,75,29,47 becomes 97,75,47,29,13.
After taking only the incorrectly-ordered updates and ordering them correctly, their middle page numbers are 47, 29, and 47. Adding these together produces 123.
Find the updates which are not in the correct order. What do you get if you add up the middle page numbers after correctly ordering just those updates?
git-bob try to implement this.


prometheus names prefixed with argo_*

Summary
When running argo with potentially tens if not hundreds of other services all with prometheus scrapers
It is difficult to find the argo labels.
Ideally grouping of the prometheus labels should be together
currently they are scattered and not central to find without the docs
https://github.com/argoproj/argo/blob/25f12441f94dfb8e8b7ade5f20c79687e4ac1471/docs/metrics.md
Use Cases
when searching for argo stats they are clearly grouped
instead of:
workflows_processed_count
count
operation_duration_seconds
error_count
queue_depth_count
queue_adds_count
queue_latency

they present and group as
argo_workflows_processed_count
argo_count
argo_operation_duration_seconds
argo_error_count
argo_queue_depth_count
argo_queue_adds_count
argo_queue_latency

especially with regards to things like "count"

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I'm sorry, I'm not sure I understand what the request is. Currently all Argo Workflows metrics are indeed grouped:

Are you asking that they do not be grouped?

apologies if this is the case! Thanks for the prompt response..


core: add StructBase and StructDef for custom struct values

Custom struct value can be added like so:
import {StructBase, StructDef, Int} from "dotjs/types/index.js";
class MyStruct extends StructBase {
    constructor(field1, ....) {
      ...
    }
    static structDef() {
      return new StructDef("golang_struct_name", MyStruct)
        .withField("field1", Int);
    }
}

Codecov Report

Merging #58 into master will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
+ Coverage   86.15%   86.29%   +0.13%
==========================================
  Files          27       27
  Lines         744      744
==========================================
+ Hits          641      642       +1
+ Misses        103      102       -1

Impacted Files
Coverage Δ

core/map.js
90.62% <ø> (ø)
:arrow_up:

core/null.js
100% <ø> (ø)
:arrow_up:

core/decode.js
85.18% <0%> (+3.7%)
:arrow_up:

Continue to review full report at Codecov.

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


Add sentence to open_dataset docstring

This adds a sentence (below) under "chunks" in doctoring of open_dataset() to clarify current usage for those who want the same behavior as open_zarr() used to provide:
In order to reproduce the default behavior of xr.open_zarr(...) use `xr.open_dataset(..., engine='zarr', chunks={})`.

[ ] Closes #7293

Just a small newline addition. Thanks @paigem


flutter upgrade failed

every time I run flutter upgrade, it turned out this:
Downloading Dart SDK from Flutter engine 54ad777fd29b031b87c7a68a6637fb48c0932862...
dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
Referenced from: /Users/XXX/anaconda3/lib/libssh2.1.dylib
Reason: image not found
/Users/XXX/flutter/bin/internal/update_dart_sdk.sh: line 100:  7529 Abort trap: 6           curl --continue-at - --location --output "$DART_SDK_ZIP" "$DART_SDK_URL" 2>&1
Failed to retrieve the Dart SDK from: https://storage.flutter-io.cn/flutter_infra/flutter/54ad777fd29b031b87c7a68a6637fb48c0932862/dart-sdk-darwin-x64.zip
If you're located in China, please see this page:
https://flutter.dev/community/china

@hujianhang2996 can you add the output of flutter doctor -v please?

I got the same issue and when I run flutter doctor -v, it just returned:
flutter doctor -v
Downloading Dart SDK from Flutter engine fee001c93f25a1e7258e762781a7361f122d29f5...
dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
  Referenced from: /Users/binggan/anaconda3/lib/libssh2.1.dylib
  Reason: image not found
/Users/binggan/Desktop/flutter/bin/internal/update_dart_sdk.sh: line 100: 39230 Abort trap: 6           curl --continue-at - --location --output "$DART_SDK_ZIP" "$DART_SDK_URL" 2>&1

Failed to retrieve the Dart SDK from: https://storage.googleapis.com/flutter_infra/flutter/fee001c93f25a1e7258e762781a7361f122d29f5/dart-sdk-darwin-x64.zip
If you're located in China, please see this page:
  https://flutter.dev/community/china

@hujianhang2996 Could you check if this helps you solving the issue?
https://stackoverflow.com/questions/38670295/homebrew-refusing-to-link-openssl

This looks to me like anaconda overriding the system libssl with its own, of a different version. Assuming anaconda is configured in your shell config, could you try opening a new, default config bash shell like: bash --noprofile --norc and then try flutter doctor to see if that is indeed the issue?

Closing this because of lack of user response.

Did someone find any workarounds? I am trying to upgraded flutter and not able to proceed.

@microJ @BharathRavi27 you can test if your issue is the same as the OP (a conflict with anaconda overriding defaults) by doing:
env -i bash --norc --noprofile # invokes a new shell ignoring your config files
<path_to_flutter_repo>/bin/flutter doctor -v

And see if that is successful. If that works, then your issue is that your anaconda install is overriding libssl. Else, you are having a different issue and you should file a new issue with full logs and the output of flutter doctor -v.

I figured that my issue was related to permission. I has to give proper permissions to the flutter direcrory and also, had deleted the downloads/cache directory inside flutter/bin.


Detector Improvements

General restructuring of code for consistent style and conventions ("private" member protection)
Class names now generally indicate which "subcomponent" of Detector they belong to: Camera, Marker, Calibration
Detector configuration now has distinct sections for each of the "subcomponents"
Camera, Marker detection, and Calibration classes no longer deal with API data structures (that is instead handled in Detector)
Simpler communications between controller/GUI and Detector. Try to avoid roundtrips of data
Calibration images shall now be saved in lossless format (.png), fixes #18
Consolidate API classes into one api.py file, toward #49
User can now specify which calibration to use (the "active" one) in the GUI.
Remove unused fields from various classes

I'm not sure whether to squash or not. Although I generally tested after each commit, I'm leaning toward squashing simply because this represents a general overhaul of Detector.

Looks and works good for me.

Squashed and merged.


How to open the file system directory, select the directory?

How to open the file system directory, select the directory?
webview.h ---> 1404 (wins)
if (flags ==1 ){
        add_opts |= FOS_PICKFOLDERS;
      }

can I do this ？

It's a needed feature :+1: , will webview support this?


Version three compat

some changes to support python 3

hey sorry i had copied that experiment to as a template of sorts for my own experiment, i just pushed up a new commit with the original, this doesnt have #3 done yet if you dont mind im going to leave it open so I remember to do it but you can ignore until i make another commit with a message confirm 2 compat is safu

Hi again Nick,
You still seem to be modifying files which shouldn't be modified.
Furthermore, please refrain from doing stuff like os.environ["PATH"] += os.pathsep + 'D:/Program Files (x86)/Graphviz2.38/bin/' as it is only valid on your machine.
Kind regards

Hey yeah sorry about that, just trying to get my external experiment to work, I am going to close my pr and branch off main into a fresh branch to do the version3 compatibility update, i think changing print to print() will be version 2 compatible still, but the changes of xrange to range dropping the cPickle import and wrapping ranges with list() will be done conditionally on new branch.


feat: interactive project initialization

PR for #493.
All the functionality should be there. However, when it came to writing tests, I noticed that the current integration test setup can't really test stdin/stdout. I think we'd have to call it as a standalone program to do so. Does anyone have any thoughts on that? ~I'm happy to try and change it to such a setup tomorrow.~ Edit: I've added some tests with that sort of setup now.
cc @oddgrd @brokad

I've written some tests for the interactive route that interact with cargo-shuttle as an executable now.

(Rebased.)

Hmmm, the test run::actix_web_hello_world seems to be failing, but I can't immediately see how it would be related to these changes. Could it be that it was already failing before?

Thanks for the thoughtful review, @chesedo! I'll have a look at it tomorrow :)

Thanks for all the good suggestions, @chesedo! I've incorporated them now. Any thoughts on this question?

Everything's good to go on my end 👍

Good idea! Done!


Paolo/backend configuration

Created the S3 resource (already launched) and the common backend.

Now it should be ok :)


Action execution failed Error calling startBuild: Cannot have more than 0 builds using brand new account/org

Required Basic Info

Accelerator Version: v1.5.1-a

clean run

Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)
Failed at the Pipeline stage before State Machine is ready

config.json based on reference-artifacts/SAMPLE_CONFIGS/config.lite-CTNFW-example.json
see config-redacted.json.log attached

Describe the bug
ASEA-InstallerPipeline fails stating account limit exceeded - cannot have more than 0 builds in queue
Failure Info
Action execution failed
Error calling startBuild: Cannot have more than 0 builds in queue for the account (Service: AWSCodeBuild; Status Code: 400; Error Code: AccountLimitExceededException; Request ID: f0d98e36-8ac5-4668-abab-2108afa3251e; Proxy: null)
Required files

If a CodeBuild step failed- please provide the full CodeBuild Log

Could not find

Steps To Reproduce

Create a brand new account. Make it an Org. Follow all the steps in https://catalog.us-east-1.prod.workshops.aws/workshops/f3ed5d0f-d2f1-47e8-a305-168da9179aaa/en-US/sea-administrators
to setup the org and root account.
Upload the attached file to an S3 bucket
Launch the AWSA CF template using latest release

Expected behavior
Expected it runs to completion
Screenshots

config-redacted.json.log

Hi,

On quick review of the config file, it is not valid json (run it through any json validator or parser, one example) and needs to be fixed as a first step (you can't break lines the way you did).
I also noticed you started with the Control Tower + NFW based config file, yet disabled the primary Control Tower compatibility settings.  Are you installing on top on Control Tower or standalone?

If doing a standalone install, I do not think you will get the desired outcome and you should use config.lite-NFW-example.json as your starting point (identical but without all the Control Tower settings).
if deploying with control Tower you cannot set "ct-baseline": false, and "control-tower-supported-regions" must have at least one region

Finally, while the above are concerns, likely not the cause of this initial failure - "account limit exceeded"
-I'm guessing you have a very new AWS account, as it appears to have unusually low initial limits established

Can you start by running an small EC2 instance in the account (i.e. t2.micro) in your home or installation region for 15minutes.  This should force the account to establish some basic limits.
Before you rerun the ASEA, you will need to delete the EC2 instance and all associated sub-objects like security groups or the state machine will purposely fail attempting to delete the default VPC.  To ensure you properly cleaned up, recommend you manually delete the default VPC in that region.
if you still have trouble with errors associated to limits - you'll likely need to reach out to your local AWS account team to help you get your limits increased.

Hope this helps!

Thanks for the speedy reply @Brian969 !
The config problem was due to copy/paste from github - the file was too large and caused format problems.
I switched to NFW and tried to launch a t2.mediium.
I skipped over that part in the docs cause i assumed it was just for lab purposes. It would be great to add an explainer that it's to "activate" the account and you will hit limit issues on a new account for 2-3 days.
It actually took 60 hrs from my first activity in the account to get the t2 to launch. I opened 3 support tickets and the SLA said 48 hours for bumping limits, so I might have been unlucky.
Anyway, once that was cleared up, the pipeline ran to completion and I'm now debugging state-machine errors.
  "cause": {
    "errorType": "Error",
    "errorMessage": "This execition requires Accelerator execution with scope: \"FULL\"",
    "trace": [
      "Error: This execition requires Accelerator execution with scope: \"FULL\"",
      "    at I2e (/var/task/index.js:1392:22966)",
      "    at processTicksAndRejections (internal/process/task_queues.js:95:5)",
      "    at async Runtime.dT0 [as handler] (/var/task/index.js:1392:17569)"
    ]
  }

I'll close this out and open a new one on that topic
thanks again

The issue was a 60 hour delay in the new account being activated.
Unfortunately, the limits displayed when an account is first launched are not accurate until some extra activation takes place.


Overhaul state and backends documentation

In some recent online discussions, I noticed some factual errors in
the current state and backends documentation. In addition, the layout
was very difficult to follow, with a fair bit of redundant information,
and an ordering that didn't seem to make much sense. I've done an
editorial pass over the content. There isn't anything "majorly new"
here although I did also fill in some gaps I found as I rearranged
the content. Hopefully this is much easier to read/understand now.
Related to https://github.com/pulumi/docs/issues/3104.

Thanks @davidwrede, excellent suggestions, I will be sure to apply all of them tomorrow.

Thanks @davidwrede, excellent suggestions, I will be sure to apply all of them tomorrow.


tour: gotour download link is not working

Context: https://tour.golang.org/welcome/3
When I tried to download gotour. it's not working.

Can you explain what exactly did you try and what is not working?


Changing translation key as suggested in PR #3336

Summary
Changing translation key as suggested in PR #3336
Ticket Link
MM-17199
Related Pull Requests
PR #3336

Looks good. Does not requires QA to perform testing since these are used in unit tests only. Removing the QA Review label.


README Updates

Update README with helpful edits recommended by @cmarshak
Add pinned jupyter lab dependencies to environment yamls

Thank you for taking the time, Alex!

Thank you for the review, Charlie! I don't see the comment I made related to your suggested change anymore, so in case it vanished here it is:
You don't have to explicitly install the kernel but it makes sense to here. If you don't, and you start jlab from your activated env, you'll end up with the correct kernel but it will be generically named Python3. Installing it will provide the expected name. I think installing it was a good call.


Scroll to bottom after adding local closed event

Version 1.10.0 (1612)
Device: iPhone 7 Plus (iOS 10.3.3)

Actually scroll to bottom when already at the bottom. If at the top don't do anything since the status cell changes.

dupe


Libertarian Socialist should be Democratic Socialist in many cases

I received Socialist-Internationalist-Liberal-Very Progressive, and 8values gave me Libertarian Socialist. When I looked this up, it seems like that Libertarian Socialists are against the existence of the state (anti-statist). Given that someone who scores Liberal on the authority axis probably does not advocate for the destruction of the state, I would recommend that the match for Socialist-Internationalist-Liberal-Very Progressive should be changed to Democratic Socialism.

Would you share your results? I'd like to see the precise values as they would be useful to determine what tweaks might need to be made to the ideology matcher.

Something like this: https://8values.github.io/results.html?e=81&d=73.9&g=67.2&s=84


cvat sdk (low and high level apis) loses tasks

Library version: cvat_sdk==2.3.0
Used High-level API code to retrieve list of project tasks:
from cvat_sdk import make_client
client = make_client(
    host=cvat_host,
    credentials=cvat_creds,
)
project = client.projects.retrieve(project_num)
tasks_list = project.get_tasks()

In this case, i got 10 tasks of 16. But the most interesting thing is that on the project page with a list of tasks in cvat itself, the tasks are divided into 2 pages and the first contains 10 tasks, and the second 6. Accordingly, I just get a list from the first page of 10 tasks.
The same happens with Low-level API - I get 10 tasks of 16:
from cvat_sdk.api_client import Configuration, ApiClient, models, apis, exceptions

configuration = Configuration(
    host=cvat_host,
    username=cvat_username
    password=cvat_password,
)
api_client = ApiClient(configuration)
print(len(api_client.projects_api.list_tasks(project_num)[0]["results"]))

The last raw prints the length of results dictionary that contains tasks.

Hi, this problem was fixed in https://github.com/opencv/cvat/pull/5557 (v2.4.0+). Prior this change, only the first page (up to 10 entries) had been requested in this function. If you want to retrieve all the list, please use the low-level API and the get_paginated_collection() function:
from cvat_sdk.core.helpers import get_paginated_collection
from cvat_sdk.core.proxies.tasks import Task
from cvat_sdk import make_client

format_name = "CVAT for images 1.1"

with make_client("localhost", port=8080, credentials=("admin", "pass")) as client:
    tasks = [
        Task(client, m)
        for m in get_paginated_collection(
            client.api_client.projects_api.list_tasks_endpoint, id=project_id
        )
    ]

    for task in tasks:
        task.export_dataset(format_name, f"{task.id}-{task.name}-{format_name}.zip")

Hi, this problem was fixed in #5557 (v2.4.0+). Prior this change, only the first page (up to 10 entries) had been requested in this function. If you want to retrieve all the list, please use the low-level API and the get_paginated_collection() function:
from cvat_sdk.core.helpers import get_paginated_collection
from cvat_sdk.core.proxies.tasks import Task
from cvat_sdk import make_client

format_name = "CVAT for images 1.1"

with make_client("localhost", port=8080, credentials=("admin", "pass")) as client:
    tasks = [
        Task(client, m)
        for m in get_paginated_collection(
            client.api_client.projects_api.list_tasks_endpoint, id=project_id
        )
    ]

    for task in tasks:
        task.export_dataset(format_name, f"{task.id}-{task.name}-{format_name}.zip")

Hi! I tried the way you suggested but for me it doesn't work. I got the error below:

When I create client object:
 client = make_client(host=host, credentials=("admin", "pass"))

I get the warning message:
Server version '2.3' is not compatible with SDK version '2.7.2'. Some SDK functions may not work properly with this server. You can continue using this SDK, or you can try to update with 'pip install cvat-sdk'.
I guess there may be some version inconsistencies.

I guess there may be some version inconsistencies.

Yes, you should try to install the matching SDK version with pip install 'cvat-sdk==2.3.0' 'cvat-cli==2.3.0'.

I guess there may be some version inconsistencies.

Yes, you should try to install the matching SDK version with pip install 'cvat-sdk==2.3.0' 'cvat-cli==2.3.0'.

Thanks for the answer! But it seems I’m talking about something a little different: the inconsistency between the UI CVAT Server version and the cvat-sdk, cvat-cli versions. And that's why updating libraries versions will not fix the problem.

P.S: upgraded both cvat-sdk and cvat-cli libraries to 2.7.2 versions and it still doesn't work.

If you're using SDK or CLI, you need their versions to match the server version. From the conversation above, your server has version 2.3, so your SDK and CLI should both be 2.3.0.

Hello,
I am using cvat-sdk version v2.11 (more recent than v2.4.0) and I have found the same exact issue with the tasks low level API. See:
from cvat_sdk.api_client import Configuration, ApiClient
configuration = Configuration(host=host, username=username,  password=password)
with ApiClient(configuration) as api_client:
tasks = api_client.tasks_api.list()[0].results
for task in tasks:
print(task.id)
Surprinsingly enough, api_client.tasks_api.list()[0] has 'count' = 12 (I have 10 tasks in page 1, and 2 in page 2)
How can

Hi, this problem was fixed in #5557 (v2.4.0+). Prior this change, only the first page (up to 10 entries) had been requested in this function. If you want to retrieve all the list, please use the low-level API and the get_paginated_collection() function:
from cvat_sdk.core.helpers import get_paginated_collection
from cvat_sdk.core.proxies.tasks import Task
from cvat_sdk import make_client

format_name = "CVAT for images 1.1"

with make_client("localhost", port=8080, credentials=("admin", "pass")) as client:
    tasks = [
        Task(client, m)
        for m in get_paginated_collection(
            client.api_client.projects_api.list_tasks_endpoint, id=project_id
        )
    ]

    for task in tasks:
        task.export_dataset(format_name, f"{task.id}-{task.name}-{format_name}.zip")

Hello,
I am using cvat-sdk version v2.11 (more recent than v2.4.0) and I have found the same exact issue with the tasks low level API. See:
from cvat_sdk.api_client import Configuration, ApiClient
configuration = Configuration(host=host, username=username,  password=password)
with ApiClient(configuration) as api_client:
tasks = api_client.tasks_api.list()[0].results
for task in tasks:
print(task.id)
This will only print the ids of the first 10 tasks. Surprinsingly enough, api_client.tasks_api.list()[0] has 'count' = 12 (I have 10 tasks in page 1, and 2 in page 2)
Using the projects low level api proposed here raises an error at this line client.api_client.projects_api.list_tasks_endpoint, id=project_id saying there is no such method. Any help would be really appreciated.


Complement of TODO list in "how-to guide"

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
I'm going to prepare docs about "Create an Autoware package" in "how to guide". However, I'm not sure if I understand this part correctly. Is this section to guide new user how to customize his own project based on Autoware (msgs, tools, etc..)  or instruct people how to become an Autoware code contributor?
Purpose
Get clear of the scope.
Possible approaches
TBD
Definition of done
completion of docs

@JianKangEgon Thank you for opening this.

instruct people how to become an Autoware code contributor

I meant this by "Create an Autoware package".

guide new user how to customize his own project based on Autoware (msgs, tools, etc..)

I feel it's like an extension of https://autowarefoundation.github.io/autoware-documentation/main/how-to-guides/integrating-autoware-with-your-vehicle/. It's also worth writing a document.

@kenji-miyake oh thanks for the reply, got it.


How to generate a file with only those atomic classes that are used?

Hello! How to generate a file with only those atomic classes that are used in my project?

Okay, duplicate
https://github.com/tailwindcss/discuss/issues/18


Build and push

There is just one proble with the The composer.lock is not up to date. should be ok after merge to master.

@romaricp will there be any progress on merging this helpful feature? :)


.net build fails on windows-latest 20230620 but works on 20230612

Description
I've a project which has suddenly stopped building when deployed to a Azure DevOps Hosted Build Agent with version 20230620 of the image.
The changes in this image are listed here: https://github.com/actions/runner-images/releases/tag/win22%2F20230620.1
2023-06-26T03:54:24.3217964Z (ResolveRuntimePackAssets target) ->
2023-06-26T03:54:24.3219208Z   C:\hostedtoolcache\windows\dotnet\sdk\6.0.411\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(430,5): error NETSDK1112: The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'. [D:\a\1\s\proj\proj.csproj]
2023-06-26T03:54:24.3220136Z   C:\hostedtoolcache\windows\dotnet\sdk\6.0.411\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(430,5): error NETSDK1112: The runtime pack for Microsoft.WindowsDesktop.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'. [D:\a\1\s\proj\proj.csproj]
2023-06-26T03:54:24.3220371Z

I had originally thought it was a bug with the .net SDK but it was just the older version was running on a different host. Multiple runs see a correlation between the Windows image version and failure/success.
https://learn.microsoft.com/en-us/dotnet/core/tools/sdk-errors/netsdk1112
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Agent name: 'Hosted Agent'
Current agent version: '3.220.2'
Operating System: Microsoft Windows Server 2022 10.0.20348 Datacenter
Runner Image Image: windows-2022
Version: 20230508.3
Included Software: https://github.com/actions/runner-images/blob/win22/20230508.3/images/win/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20230508.3
Is it regression?
20230612
Expected behavior
No error.
Actual behavior
2023-06-26T03:54:24.3217964Z (ResolveRuntimePackAssets target) ->
2023-06-26T03:54:24.3219208Z   C:\hostedtoolcache\windows\dotnet\sdk\6.0.411\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(430,5): error NETSDK1112: The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'. [D:\a\1\s\proj\proj.csproj]
2023-06-26T03:54:24.3220136Z   C:\hostedtoolcache\windows\dotnet\sdk\6.0.411\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(430,5): error NETSDK1112: The runtime pack for Microsoft.WindowsDesktop.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'. [D:\a\1\s\proj\proj.csproj]
2023-06-26T03:54:24.3220371Z

Repro steps

dotnet restore
msbuild

Okay, so it's actually both issues at play. 20230620.1.0 has .NET core SDK v6.0.411 which causes the build to fail.
I can get it to succeed if both the OS image is 20230612.1.0 and the .NET Core SDK version is v6.0.408. I'm unsure who's the cause here. I'll try create a demo project.

hello, @ShadowXVII ,
as a workaround you can install certain .net core by using the following task https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/use-dotnet-v2?view=azure-pipelines

@ilia-shipitsin , That's what I did, however it still fails if runs on the newer image. I need to use the older image and have it forced to the older version. I'm playing around with a test project to see if I can discovery any more.

I'd suggest adding /bl switch to msbuild, it enables so called "binary log" named msbuild.binlog, which can be viewed by https://msbuildlog.com/
(I suspect that msbuild picks wrong SDK)

It seems to be using 6.0.408... It's only failing when using the 20230620 image...
20230620 Image

20230612 Image

it might be breaking change in msbuild behaviour

"obj" is not persissted (unless commited in repo).
is <RuntimeIdentifier> specified in project ?

No, just
<RuntimeIdentifiers>win10-x64</RuntimeIdentifiers>

a naive guess would be to try win-x64 (no idea what's wrong with win10-x64)
The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'

Tried that, but no luck :(

I ran out of ideas.
maybe we can find something if you provide minimal repro

@ShadowXVII Hello! As we have not had repro we could work on to reproduce the problem, I am going to close the issue. Feel free to re-open and reach us out again if you have something new to add.

Hi @mikhailkoliada , @ilia-shipitsin , I've created a new repo here with a code sample: https://github.com/ShadowXVII/WapProjCompile

I was able to build locally, also I cannot build in ADO. Thank you for repro.

meanwhile, I added restore step suggested by dotnet, build became green
https://github.com/ilia-shipitsin/WapProjCompile/commit/f032610c94c773b2fbc576cc789af76ac803e4ff
I'll try to figure out why (locally) it works without that restore step.

Oh right, I naively thought the DotNetCoreCli restore was the "equivalent" though I guess dotnet build doesn't work.

dotnet restore under the hood uses msbuild restore, it also sets properties (including RuntimeIdentifier), I suspect that something in ADO makes it set RuntimeIdentifier in different way

Ahk. That's interesting. I ran into the same problem originally with dotnet build vs. vsbuild also -- I think because of the WAP project. Not sure if there's similar subtle differences there.

I tend to think that dotnet restore is only supposed to restore SDK style project, WAP is not SDK style.
why it worked before, most probably image was shipped with proper Microsoft.NETCore.App.Runtime version, but I see only 6.0.408 for "working" image. Also, we do not install Microsoft.NETCore.App.Runtime explicitly , this package is marked Internal implementation package.
I beleive that proper approach will be use "msbuild restore" and not depend on presence of that package.

@ShadowXVII , I'm going to close this issue

I'm closing this issue. Feel free to reopen if the problem still exists. Thank you.


Remove old HMCTS TLS client certificate from ingress allow list

⚠  Merge only when it is confirmed that HMCTS Common Platform has switched over to the new TLS client certificate.

HMCTS have now told us that they are using the new certificate. This can be merged.


Added fix for running on Raspberry PI 5

The Raspberry PI uses a kernel with a 16K page size rather than the standard 4K page size.
This pull request changes the allocated block size to 16K and merges the heap and stack memory.
Fixed #4

@Vbitz Thanks! ✌


Bump inmanta-dev-dependencies[async,core,pytest,sphinx] from 2.59.0 to 2.62.0 (#5692)

Pull request opened by the merge tool on behalf of #5692

Merged in 6e5f116c1b50ba97810b9e4ac5935f73cb33f9b1


[gperftools] Add new port

Fix #3536 .

Hi @myd7349 thanks for your pull request.
I noticed that this port failed on x64-uwp , arm64-windowsand arm-uwp. Are these expected?
If this port doesn't currently support uwp, arm and arm64, please add the message to portfile.cmake.
vcpkg_fail_port_install(ON_ARCH "arm" "arm64" ON_TARGET "uwp")

/azp run

/azp run

/azp run

/azp run

Since this port doesn't support arm, arm64 and uwp.
Could you update baseline with the following?
gperftools:arm64-windows=fail
gperftools:x64-uwp=fail
gperftools:arm-uwp=fail

/azp run

/azp run

/azp run

I also noticed the regressions on Linux and osx.
Could you please try to look into them?

The new regressions on linux and osx:
There should be no bin\ directory in a static build, but /Volumes/data/work/1/s/packages/gperftools_x64-osx/bin is present.
There should be no debug\bin\ directory in a static build, but /Volumes/data/work/1/s/packages/gperftools_x64-osx/debug/bin is present.
If the creation of bin\ and/or debug\bin\ cannot be disabled, use this in the portfile to remove them

    if(VCPKG_LIBRARY_LINKAGE STREQUAL "static")
        file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/bin" "${CURRENT_PACKAGES_DIR}/debug/bin")
    endif()

Found 1 error(s). Please correct the portfile:
    /Volumes/data/work/1/s/ports/gperftools/portfile.cmake

All features have passed on x64-windows-static triplet.
Feature tools  have passed on the x86-windows and x64-windows triplets.
Note: Feature override only supports static build.

LGTM! Thanks y'all :)


Paths set in pathOptions are not applied to generated SCSS

It seems like the settings from pathOptions are not correctly applied to the generated SCSS file.
Sample configuration:
module.exports = {
    name: 'FontName',
    inputDir: './src',
    outputDir: './dist',
    fontTypes: ['ttf', 'woff', 'woff2', 'eot'],
    assetTypes: ['ts', 'css', 'json', 'html', 'scss'],
    pathOptions: {
        ttf: './dist/font-path.ttf',
        // ...
    }
};

This is how the SCSS looks like:
$FontName-font: "FontName";

@font-face {
    font-family: $FontName-font;
    src: url("./FontName.ttf?844d80a3a20d138df75d79cb28752afd") format("truetype"),

However, it should be src: url("./font-path.ttf?844d80a3a20d138df75d79cb28752afd") as specified in .fantasticonrc.js.
Edit: Same thing happens for the CSS file, possibly in other places as well.

You can use fontsUrl config option


revise exit handling

A valid exit code means that a thread calls the system call exit. In this case, we have to terminate all threads like the behaviour of exit. This current version is the reason that PR hermitcore/libhermit-rs#160 doesn't pass all tests.

bors try

bors try

bors retry

bors retry

Why did codecov/patch fail?

Why did codecov/patch fail?

Why did codecov/patch fail?

I think that is because the default settings for this status check require the code coverage for patches that change code to not let coverage (of the modified portion) fall below the average percentage for the whole project.
This can be modified by adding a toml file for codecov, or we can ignore it for now, since the status is not relevant for bors.

Why did codecov/patch fail?

I think that is because the default settings for this status check require the code coverage for patches that change code to not let coverage (of the modified portion) fall below the average percentage for the whole project.
This can be modified by adding a toml file for codecov, or we can ignore it for now, since the status is not relevant for bors.

How can I disable codecov/patch?

How can I disable codecov/patch?

I've thought about this again, and I think it would be better if we would treat the case where all threads terminate correctly separately.
Instead of using std::process::exit if one thread exits, we could schedule a SIGALARM (and register a handler), that can be used to terminate uhyve, if the remaining threads don't terminate until the alarm goes off.

I've thought about this again, and I think it would be better if we would treat the case where all threads terminate correctly separately.
Instead of using std::process::exit if one thread exits, we could schedule a SIGALARM (and register a handler), that can be used to terminate uhyve, if the remaining threads don't terminate until the alarm goes off.

We are able to wait for all thread. Every thread in the user space is able to exit. For instance, a panic will do it. In this cast, we have to shutdown everything. In my opinion, is this the definition of exit.

We are able to wait for all thread. Every thread in the user space is able to exit. For instance, a panic will do it. In this cast, we have to shutdown everything. In my opinion, is this the definition of exit.

@jschwe @jbreitbart Do you prefer the latest version?

@jschwe @jbreitbart Do you prefer the latest version?

I will accept this PR because it block all other PR. I will also an issue to discuss a better solution.

I will accept this PR because it block all other PR. I will also an issue to discuss a better solution.

bors r+

bors r+

bors r+

bors r+


Action sheet button shortens when highlighted

Short description of the problem:
In iOS look, when an action sheet button is in the highlighted state, it shortens by 1 or 2 px.
What behavior are you expecting?
The button should remain the same height when highlighted.
Steps to reproduce:

Go to http://ionicframework.com/docs/v2/components/#action-sheets
Click on "Show Action Sheet"
Click and hold down on the "Delete" button in the action sheet. When the button is highlighted, it shortens.
While still holding the mouse button down, move off the "Delete" button. When the button highlight is removed, the button goes back to its original height.

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Obviously seems to be a CSS issue. Doesn't occur in the other UI types (Android, Windows).
Which Ionic Version? 1.x or 2.x
2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Using the version on your web site.

Hello! Thanks for opening an issue with us! I think this might be because the borders get removed when the button is :active on the ios theme. On android and windows there are no borders on the buttons in the action sheet, so this is why they don't look shorter when active on those platforms.

That may be why it's happening, but it's clearly undesirable behavior. Why remove the border? It could just be changed to the highlight color.

@aparajita This is what iOS native action sheet does. We are simply mimicking the native experience for action sheet.

I'm not seeing this at all. Before clicking the height of the button is 57px:

with the activated class it is 58px but it has margin-top: -1px so it really appears as 57px:

Putting them side by side:

I'm going to close this issue because I don't see anything wrong with it, please let me know if we're misunderstanding you. :smile:

There must be something wrong with the demo then, because I'm getting wrong behavior there. Alternate between these two screen shots, you can clearly see it move:

@brandyscarney I confirm this is a real issue. I created the PR for the improved action-sheet css and something is broken for safari in the last version.
Please reopen, I think I know what is going on.

I have a fix!

@brandyscarney @bensperry in safari the buttons have a non 0 margin (not sure why) this normalizes how the buttons are rendered in safari and chrome.
the change does not affect how it looks in my chrome.
https://github.com/driftyco/ionic/pull/5867
but please, merge it locally and verify it fixes it

Thanks for the PR @manucorporat. We were looking in Chrome so that explains it! I'll take a look at it soon. :smile:

@brandyscarney Sorry for not stating that it was in Safari at the beginning. I should have checked on Chrome myself.

@aparajita It's fine! We really should be testing Safari more. Thanks for finding and reporting it! :smile:

I merged the PR from @manucorporat. This will be fixed on the site once we release beta.4 and update the demos.
Thanks again, everyone!


Show specific task provider progress and allow providers to be canceled

Fixes https://github.com/microsoft/vscode/issues/90087

@chrmarti when I hide the custom quick pick button, the quick pick loses focus and then hides. Because of this, I added focusOnInput. Could you review the two quickInput files to see if you're ok with this change?