Automatically set GOMAXPROCS to match Linux container CPU quota

Checklist

[x] Changelog has been updated and is aligned with our changelog requirements
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #4999

/run-e2e internal

/run-e2e internal


Yarn Berry Errors with record_update_job_error; Equivalent Project Runs Well on Github

Describe the bug
As of 3 weeks ago, every update using V2 of the Dependabot pipeline runner in Azure Devops gives us this error in our yarn v4 monorepo code:
{"data":{"error-type":"dependency_file_not_resolvable","error-details":{"message":"Error while loading \".yarnrc.yml\"."}},"type":"record_update_job_error"}

For a more detailed sample snippet:
updater | 2024/12/16 20:22:08 INFO <job_update_0_npm_and_yarn_all> Requirements to unlock own
updater | 2024/12/16 20:22:08 INFO <job_update_0_npm_and_yarn_all> Requirements update strategy bump_versions
updater | 2024/12/16 20:22:08 INFO <job_update_0_npm_and_yarn_all> Updating @babel/helper-function-name from 7.23.0 to 7.24.7
{"data":{"error-type":"dependency_file_not_resolvable","error-details":{"message":"Error while loading \".yarnrc.yml\"."}},"type":"record_update_job_error"}
updater | 2024/12/16 20:22:10 INFO <job_update_0_npm_and_yarn_all> Handled error whilst updating @babel/helper-function-name: dependency_file_not_resolvable {:message=>"Error while loading \".yarnrc.yml\"."}
updater | 2024/12/16 20:22:12 INFO <job_update_0_npm_and_yarn_all> Checking if @babel/helper-hoist-variables 7.22.5 needs updating
updater | 2024/12/16 20:22:13 INFO <job_update_0_npm_and_yarn_all> Latest version is 7.24.7
updater | 2024/12/16 20:22:25 INFO <job_update_0_npm_and_yarn_all> Requirements to unlock own
updater | 2024/12/16 20:22:25 INFO <job_update_0_npm_and_yarn_all> Requirements update strategy bump_versions
updater | 2024/12/16 20:22:25 INFO <job_update_0_npm_and_yarn_all> Updating @babel/helper-hoist-variables from 7.22.5 to 7.24.7
{"data":{"error-type":"dependency_file_not_resolvable","error-details":{"message":"Error while loading \".yarnrc.yml\"."}},"type":"record_update_job_error"}
updater | 2024/12/16 20:22:27 INFO <job_update_0_npm_and_yarn_all> Handled error whilst updating @babel/helper-hoist-variables: dependency_file_not_resolvable {:message=>"Error while loading \".yarnrc.yml\"."}
updater | 2024/12/16 20:22:29 INFO <job_update_0_npm_and_yarn_all> Checking if @babel/helper-member-expression-to-functions 7.24.7 needs updating
updater | 2024/12/16 20:22:30 INFO <job_update_0_npm_and_yarn_all> Latest version is 7.25.9
updater | 2024/12/16 20:22:41 INFO <job_update_0_npm_and_yarn_all> Requirements to unlock own
updater | 2024/12/16 20:22:41 INFO <job_update_0_npm_and_yarn_all> Requirements update strategy bump_versions
updater | 2024/12/16 20:22:41 INFO <job_update_0_npm_and_yarn_all> Updating @babel/helper-member-expression-to-functions from 7.24.7 to 7.25.9
{"data":{"error-type":"dependency_file_not_resolvable","error-details":{"message":"Error while loading \".yarnrc.yml\"."}},"type":"record_update_job_error"}
updater | 2024/12/16 20:22:43 INFO <job_update_0_npm_and_yarn_all> Handled error whilst updating @babel/helper-member-expression-to-functions: dependency_file_not_resolvable {:message=>"Error while loading \".yarnrc.yml\"."}

If running this project with the exact code in Github, the code runs successfully.
Categorization

[x] This is not a permissions issue (Seek help at https://github.com/tinglesoftware/dependabot-azure-devops/discussions/1245)

Repository
https://github.com/epicstar/dependabot-yarn-test/
I have given you the repo in Github to prove it works fine on Github.
However, because our organization is private, I cannot give you the Azure Devops version of the code. Rest assured, the code is the exact same minus blanking out the githubConnection property in the Azure Devops pipeline.
To Reproduce
Steps to reproduce the behavior:
Please see README of https://github.com/epicstar/dependabot-yarn-test to run in Azure Devops.
You will have to push this repo there. The Azure Pipeline YAML should be in the given repository.
Expected behavior
It should be like the Github repo outputs:

PRs filled out correctly
GIthub Logs showing that the run was successful

Logs and screenshots
In Azure:

Extension (please complete the following information):

Host: Azure DevOps (ubuntu-latest)
Version 2.39.1099

Server (please complete the following information):

Region US East
Agent Version: 4.248.0
Version 20241117.1.0 (Image Version)

Logs TBD SOON
Additional context
We spotted this problem in our original repo that was occurring on our private Azure Artifacts version of NPM Registry; however, the problem is also happening on the standard public NPM Registry.
We had to move to V2 from V1 because we had problems with running the pipeline extension with our Private Azure Artifacts (upstream).
In addition, #1441 is not an issue on Dependabot as Dependabot on Github runs this repo in 16 minutes, as opposed to 1 hour 10 minutes.

@rhyskoedijk Here's a link to the logs. The logs are so big I had to give you the files through OneDrive :(
This ended up running over 3 hours.... that's because it hit the 3 hour timeout window and then timed out. My initial thoughts:

Still not sure why the yarnrc yaml can't be read. My initial uneducated hunch is that it is accidentally being ignored by the docker container.
#1441 -> Seems to be running over the entire yarn lock multiple times, when dependabot-core in Github seems to be only focusing on the direct dependencies from the package json.

I tested on Github vs. DevOps as well and am seeing the same behavior. Mine finishes in about 4 minutes on github but times out on DevOps.


Arnej/ensure more optimization

@havardpe please review

@arnej27959
looks good, please reverse-review my additional suggestions

everything looks good to me


Const values in package schema are not set, e.g.: create Kubernetes resources without "kind", "apiVersion"

Acceptance criteria: the following YAML example should create a Kubernetes namespace as-is.
In most of our languages, the equivalent to this YAML should create an automatically named namespace resource:
resources:
  namespace:
    type: kubernetes:core/v1:Namespace

Equivalent to new k8s.core.v1.Namespace('namespace') in TypeScript.
However this causes an error when creating the resource with an error that the property "kind" is an empty string.
That comes from the package schema for a namespace, copied below, defining two "const" properties:
        "kubernetes:core/v1:Namespace": {
            "description": "Namespace provides a scope for Names. Use of multiple namespaces is optional.",
            "properties": {
                "apiVersion": {
                    "type": "string",
                    "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources",
                    "const": "v1"
                },
                "kind": {
                    "type": "string",
                    "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
                    "const": "Namespace"
                },
...

These constants do not appear in the API docs, as the generated SDKs for each language will set these constants for the user. (This raises another question we will merely note, as answering it is out of scope for YAML: why are they properties and not built in to the provider binary if users cannot provide them and they are hardcoded to a specific value?)
This affects all resources which define constants, and a quick scan of "const" declarations in schema.json found ~3400 entries. None at an indentation level greater than a top-level property key, though I used grep and not a json parser to see if any nested objects define a constant. I would be surprised if our codegen supported nested consts, so I'm assuming not and that we can solve this by addressing the top-level resource properties in YAML.

I don't think we generally use nested const or default fields, except for enums and in those cases YAML needs a way to specify the enum type/discriminator. Closing with the partial fix and will re-open or create a new issue to track if a new resource provider or reported bug gives us a more pressing example.


Rename release tags to use standard semantic versioning

Spitfire is semantically versioned, but the release tags are of the form spitfire-0.6.18 instead of the standard v0.6.18.  Rename them.

This is now done: https://github.com/nicksay/spitfire/tags


browser.fill().fill() not a function

Before upgrading to Zombie V6.1.3, the browser.fill().fill() will work. However upon upgrading to Zombie V6.1.3, the test fails and returns as not a function.
Node Version: v10.11.0
macOS Version: Mojave (10.14)

I am facing the same erro

i have split my calls from
browser.fill().click()
to
browser.fill()
browser.click()
fill now returns a promise (as i have understood the update docu) and not a browser.

This is intended behavior (#1054). Consider something along the lines of the following instead:
browser.fill('email'<EMAIL_ADDRESS>  .then(() => browser.fill('password', 'eat-the-living'))
  .then(() => browser.pressButton('Sign Me Up!', done));

This issue can be closed.

👍

Can you please update the quick-start on the "The Bite" please? I google it and found this right away, so it's wasn't too bad. After that change, it seemed to work fine!
http://zombie.js.org/
It lists:
    before(function(done) {
      browser
        .fill('email'<EMAIL_ADDRESS>        .fill('password', 'eat-the-living')
        .pressButton('Sign Me Up!', done);
    });


Update dependencies in pipfile and package json locks

What is the context of this PR?
Mainly critical and high risk dependencies updated as part of this PR (jinja2 - jwcrypto - jsrsasign). Used dependabot PR regenerated lock as a base to avoid pinning packages.
How to review
Deploy this docker image in your env and test in benchmark (check if performance didn't degrade). Double check the versions are the correct now.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Update packages to resolve security vulnerabilities in Runner (2 SP)


Differentiate between PublishURL and PublishDir

As far as I can tell, the Wizard populates and uses the PublishURL parameter to specify the output location. The msbuild command on the other hand seems to ignore PublishURL and instead requires the use of PublishDir. This really should be mentioned here especially as it conflicts with the information provided in step 4 and 5 of "To reproduce the build from the command line". (Using VS 16.2)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1672c325-b08a-dbc0-0e3e-31c832753613
Version Independent ID: c479d585-37bb-795d-1e1c-4833c2262db6
Content: Building ClickOnce Applications from the Command Line - Visual Studio
Content Source: docs/deployment/building-clickonce-applications-from-the-command-line.md
Product: visual-studio-windows
Technology: vs-ide-deployment
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@penenkel Thank you for the feedback.
A note has been added to the documentation to help clarify.

As of now, msbuild /t:publish seems to ignore both PublishUrl and PublishDir set in your publish profile.


kvm: consider provisioning type for local data volumes

Description
Fixes #8644
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@shwstppr a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9728

@blueorangutan test

@weizhouapache a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-10316)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 46356 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9141-t10316-kvm-centos7.zip
Smoke tests completed. 130 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_trigger_shutdown
Failure
341.70
test_safe_shutdown.py


Lazily initialize boto3 resources to avoid unnecessary network calls

Importing the amazon module would previously perform several potentially slow
network calls.  As a result, running bin/ce or bin/ce_install could potentially
be very slow, even when simply printing help information.
The amazon module no longer performs any network calls when imported.
Instead, boto3 and aws resources are initialized lazily upon first use.
The thin wrapper around boto3 objects only supports getting attributes on the
boto resource it wraps.  Setting attributes is not implemented because there
does not appear to be any use case for it currently as boto3 implements all
functionality as method calls.

Results on my system
Before
$ time bin/ce --help > /dev/null

real    0m6.426s
user    0m0.408s
sys     0m0.077s

After
$ time bin/ce --help > /dev/null

real    0m0.143s
user    0m0.120s
sys     0m0.025s

Note, I am not able to fully test the functionality of bin/ce because I do not have credentials for AWS, but at the very least I can observe the same failure behavior before and after this patch.
$ bin/ce instances status
Running in staging
Traceback (most recent call last):
<truncated for brevity>
  File "/home/amorton/compiler-explorer-image/.env/lib/python3.6/site-packages/botocore/auth.py", line 357, in add_auth
    raise NoCredentialsError
botocore.exceptions.NoCredentialsError: Unable to locate credentials

Wow: great stuff! thanks!


fix: corsify issue "can't modify immutable headers"

Description
A fix was implemented in https://github.com/kwhitley/itty-router/commit/74f63abb25d12666e7c05e5e82fcf7432f8dbda4 to clone the response in corsify in order to avoid this error:
{
  "status": 500,
  "error": "Can't modify immutable headers."
}

Unfortunately, it seems not to be enough, and we're still having the issue with Cloudflare when a response is modified by corsify. A solution we found and implemented is to recreate a response by using new Response(...).
Applying the fix here.
Related Issue
Link to the related issue: related to #242
Type of Change (select one and follow subtasks)

[x] Bug fix (non-breaking change which fixes an issue)

I can open a new issue if needed, please let me know 👍
it might also be related to: https://github.com/kwhitley/itty-router/issues/249

Thanks @nicolasvienot - can you give me minimal repro steps to see this immutable headers issue on a Worker?  I use CORS on virtually all my Workers (which is what I exclusively develop on these days) and am not running into this...
I'd like to ensure this is absolutely necessary before adding so many bytes! :)

@kwhitley I think you can use this sample to reproduce the issue:
import { Router, cors } from 'itty-router'

const router = Router({
  before: [preflight],
  finally: [corsify]
})

router.get('/sample', ({ params }) => {
  const cache = caches.default
  const cached = await cache.match(request)
  if (cached !== undefined) {
    return cached
  }

  const response = new Response(null, { status: 200 })
  ctx.waitUntil(cache.put(request, response.clone()))

  return response
})

return await router.fetch(request).catch(error)

When you access the first time, it returns 200, but the next requests will return 500 error.
{
  "status": 500,
  "error": "Can't modify immutable headers."
}

And there will be a warning message in worker logs:
A ReadableStream branch was created but never consumed. Such branches can be created, for instance, by calling the tee() method on a ReadableStream, or by calling the clone() method on a Request or Response object. If a branch is created but never consumed, it can force the runtime to buffer the entire body of the stream in memory, which may cause the Worker to exceed its memory limit and be terminated. To avoid this, ensure that all branches created are consumed.

Hi @kwhitley! If it helps, I'm running into the same issue, and this fix indeed helps fix it :)


Cannot provide mask property to VisualReview

We would like to exclude a certain part of the screenshot from the comparison by using the mask functionality from VisualReview.

Hello Berry,
That indeed would be a useful feature.
It will require adding a mask parameter at https://github.com/xebia/VisualReview-protractor/blob/master/lib/vr-client.js#L82. The actual parameter should contain an array of exclusions like {"mask":{"excludeZones":[{"height":40,"x":0,"width":640,"y":0}]}}.
For more information see the VR https://github.com/xebia/VisualReview/blob/b9f8b080af61b3fcfacab7894896a6c5408539c4/doc/api.md#screenshots](Server API)
That said, I'm no longer using the tool and I'm not planning on creating the feature. If you or someone else is willing to create this feature that of course would be very much appreciated.

@RRMoelker I would like to add this feature and create a pull request for it... is there still an (informal) maintainer who could merge the PR and make a new version?


styleguide - Wagtail javascript does not load

Issue Summary
The wagtail javascript (I'm guessing the telepath libraries?) does not load when viewing the style guide. There are several related javascript errors in the console:
styleguide/:1745 Uncaught TypeError: Cannot read properties of undefined (reading 'initEditor')
    at styleguide/:1745:25
(anonymous) @ styleguide/:1745
styleguide/:1867 Uncaught ReferenceError: initDateChooser is not defined
    at styleguide/:1867:9
(anonymous) @ styleguide/:1867
styleguide/:1909 Uncaught ReferenceError: initTimeChooser is not defined
    at styleguide/:1909:9
(anonymous) @ styleguide/:1909
styleguide/:1951 Uncaught ReferenceError: initDateTimeChooser is not defined
    at styleguide/:1951:9
(anonymous) @ styleguide/:1951
styleguide/:2458 Uncaught ReferenceError: PageChooser is not defined
    at styleguide/:2458:9
(anonymous) @ styleguide/:2458
styleguide/:2571 Uncaught ReferenceError: ImageChooser is not defined
    at styleguide/:2571:9
(anonymous) @ styleguide/:2571
styleguide/:2685 Uncaught ReferenceError: DocumentChooser is not defined
    at styleguide/:2685:9
(anonymous) @ styleguide/:2685
styleguide/:2799 Uncaught ReferenceError: SnippetChooser is not defined
    at styleguide/:2799:9

The wagtail widgets that rely on these (including the draftail editor) do not load as a result.

In the extra_js block is a call to render {{ example_form.media.js }} - this attribute is empty when rendering the style guide. May be the cause?
Steps to Reproduce
No special steps needed to reproduce. Default behaviour with Wagtail 6.0.x

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: 3.12
Django version: 4.2.7
Wagtail version: 6.0.2
Browser version: Chrome 124

Fixed in #11902


Regression from powershell.exe - disabled module autoloading prevents all error printing

PowerShell version: v5.1.18362.628
PowerShell Core version: v7.0.1
Steps to reproduce
Run the following snippet in both pwsh -noprofile and powershell -noprofile:
$PSModuleAutoLoadingPreference = "None"
NonExistentCmdlet
$PSModuleAutoLoadingPreference = "All"
NonExistentCmdlet
$PSModuleAutoLoadingPreference = "None"
NonExistentCmdlet

Expected behavior
Old PowerShell throws a NonExistentCmdlet error for each case:

Actual behavior
New PowerShell Core silently ignores the non-existent cmdlet the first time, works for the other two invalid calls where it correctly prints error messages:

When running with Set-PSDebug -Trace 2, the following output is displayed:

The output indicates that while printing output, the error printing code uses Test-Path, which is not loaded because of the disabled auto-loading.
Then, I attempted to first run Import-Module Microsoft.PowerShell.Management, which contains the Test-Path cmdlet. After the import, with auto-loading still disabled, errors now correctly print.
This leads me to believe that the issue is in Get-ConciseViewPositionMessage function attempting to use Test-Path, which is unavailable due to disabled auto-loading.
Environment data
PowerShell Core:
Name                           Value
----                           -----
PSVersion                      7.0.1
PSEdition                      Core
GitCommitId                    7.0.1
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PowerShell:
Name                           Value
----                           -----
PSVersion                      5.1.18362.628
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.628
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@MatejKafka can you check if there's anything stored in $error in this case?

@vexx32 I updated the issue description with more info - I believe I found the root cause.

@MatejKafka thanks!
@SteveL-MSFT looks like something you'll want to take a look at. 🙂

It is not a regression. Please update the issue header.

@iSazonov That's debatable, as ConciseView is (as far as I know) the new default, but I agree the root of the issue is not a regression from powershell.exe, but the new ConciseView. I'll update issue title and reproduction steps accordingly.


Axis Line: Label Positioning

Adds properties to axis lines for customizing label positions. This allows labels to be moved out of the way to prevent overlapping. See code in #1972 for details.

Resolves #1972

tested/working on multi-axis plots too


Feat Data Preprocessing

Python module, to be used in the training notebook.
Given the data csv and the directory with the different instances, returns the numpy arrays of training, validation and test in the given fashion: labels (dictionary), X_train, X_s, Y_train, Y_s, X_test, X_val, Y_test, Y_val

Todo ok


improved fast-path detection in HLS

Summary
This tiny PR improves the performance of the HighLevelSynthesis transpiler pass in the case that it does not need to do anything, for instance when every gate in the circuit is either already supported or can be handled by basis translator. And this is actually quite a common use-case in practice. In fact, this "fast-handling-when-there-is-nothing-to-do" was already supported at some point in the past, but got broken due to some recent changes.
The first change is that when deciding whether synthesizing a gate can be skipped we should not abort when we see a CX or a CZ gate, even though these are controlled gates.
The second change is that we should not spend time calculating sets of clean/dirty ancillas unless there is something to do.
On the utility-scale circuits, the runtime is improved from 0.2 s to 0.02 s.
Unfortunately, this causes HLS to examine the circuit 3 times: the first time it checks if it may need to do anything at all, the second time it synthesizing objects in a DAG while keeping track of clean/dirty ancillas, and the third time it builds a new DAG performing the substitutions.
Any additional suggestions for improvements are welcome.
P.S. Not sure if this deserves a release note.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
21 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.008%) to 89.136%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
94.02%

crates/accelerate/src/two_qubit_decompose.rs
1
90.84%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
2
88.43%

crates/qasm2/src/lex.rs
5
92.48%

crates/qasm2/src/parse.rs
6
97.15%

qiskit/synthesis/two_qubit/xx_decompose/decomposer.py
6
90.84%

Totals

Change from base Build<PHONE_NUMBER>4:
-0.008%

Covered Lines:
71825

Relevant Lines:
80579

💛  - Coveralls

As you said you're already looking at porting parts of the HLS into Rust, we could maybe rewrite this as:

Skip (in Rust): Check whether all nodes are skipped.
Analysis (still in Rust): Compute auxiliary qubits for each node we want to synthesize -- but don't synthesize the node yet, just return {node: (clean aux, dirty aux)}.
Rebuilding (Python): For each node to synthesize, synthesize it in Python and append it onto the DAG.

The advantage here is that we can stay in Rust space for 1+2 and only have to move back into Python for step 3.


⚠ SkipTheCommericals has degraded performance

In ce7d579, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 5365 ms

Resolved: SkipTheCommericals performance has improved in f1c0fa8.


Starlink 26 update info

Bosoter will be 1058, this will be its eighth flight and will land on OCISLY. One fairing half flew on NROL-108 and the other on SXM-7. On board there are 52 Starlink satellites (mass 13520 kg) a Capella SAR satellite (mass unkown) and Tyvkat-0130 (mass also unkown). Shelia Bordelon will recover the two fairings.

OCISLY is towed by Mr Jonah.

Only one fairing half was recovered.


ft(add: Models, controllers, Routes)

What does this PR do?
Adds Models, Controllers and Routes
Description of Task to be completed?

N/A
What are the relevant pivotal tracker stories?
#174597501
Screenshots (if appropriate)
N/A
Questions:
N/A

@kallyas Please resolve comflicts first. This branch has conflicts in all files. Please rebase first then forcepush after you resolve conflicts.

@davidgoodson Merge conflicts resolved


[BUG] don't forward 8777 tcp

:bug::scroll:
Close the 8777 tcp port as its unnecessary

#8 fixed this


Battery calculation for House Energy

Appears there's an issue with the battery percentage calculation on the House Energy unit.

I had just inserted freshly charged batteries, so imagine it might be to do with that.
Logging this early, but I'll check your code myself tonight to do my little bit towards this great project.

Thanks for the evidence.  Please add any comments to the duplicate #31

Looks like it can now return over 100% for strong batteries!
Limit this to 100%


Replace cls-hooked with native async_hooks usage

This is an odd one, I'm raising it here mostly as a signpost to what's going on for other people hitting it, since it's not really an AWS issue (really, it seems like a rollup or node issue), but possibly there's something this package can do here.
Basically, I use rollup to create my lambda deployment packages, and when I tried adding<EMAIL_ADDRESS>it caused the lambda (runtime nodejs12.x) to fail with a core dump(!) with the message:
/var/lang/bin/node[7]: ../src/async_wrap.cc:308:void node::SetupHooks(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `env->async_hooks_init_function().IsEmpty()' failed.

If I run the bundled .js file locally with node v14.10.0, I get pretty much the same error:
[19312]: c:\ws\src\async_wrap.cc:455: Assertion `env->async_hooks_init_function().IsEmpty()' failed.

With some experimenting, I've narrowed it down to simply importing async-hook-jl, which is imported by cls-hooked when it detects node is less than v8. Due to the way rollup works, this is actually always included and run. I'm not sure if there's a better option, but I got this to work under rollup with the following mini-plugin, which also disables the pkginfo module that's throwing under rollup too:
{
  name: "exclude-modules",
  files: [
    "cls-hooked/context-legacy",
    "pkginfo",
  ].map((id) => require.resolve(id)),
  load(file) {
    if (this.files.includes(file)) {
      return { code: "" };
    }
  },
},

Ideally, since node <10 is EOL, it would be nice if the cls-hooked dependency could be dropped and the native async_hooks module was used directly, or a more modern replacement used, which would avoid this particular headache, but since you've just updated to it to drop node <8 support, I'm guessing that's not likely.

Hi @simonbuchan,
Thanks for reporting this. I'm not too familiar with rollup but this:

which is imported by cls-hooked when it detects node is less than v8. Due to the way rollup works, this is actually always included and run

does not sound like desirable behavior, is that a bug that you could open with Rollup?
In terms of removing cls-hooked and using async_hooks directly, we'd rather avoid reinventing the wheel and having to implement a CLS on top of the async_hooks lib ourselves. Node 14 introduced a native AsyncLocalStorage that we could probably replace cls-hooked with, but we'd still need the cls-hooked dependency until Node 10 and 12 were EOL.

It's not really a Rollup bug, it's a design choice AFAIK. Rollup, unlike Webpack, exports a flat ES module and expects ES module inputs if you don't use plugins (you pretty much always do), so it can't realistically conditionally run module-level code - though it's probably possible.
If there's an action to take here for this package, the nicest option would be replacing cls-hooked: the problematic legacy code is for EOL node versions, and the library hasn't been updated in 3 years. There are quite a few forks, but I haven't gone through them to see if there's a plausible path forwards. Perhaps instead importing from cls-hooked/context would be enough, though now you're depending on internals to a small extent.
But really, there's not that much code to track async context, you could quite easily associate segments automatically as simply as this:
import { executionAsyncId, createHook } from "async_hooks";

// This doesn't update a global (`process.namespaces[name].active`) on `before()` and `after()` hooks,
// as `cls-hooked` does, it simply depends on `executionAsyncId` being up to date, so it may
// be a bit slower, though honestly I doubt it.

const segments = new Map();

export function setSegment(segment) {
  segments.set(executionAsyncId(), segment);
}

export function getSegment() {
  return segments.get(executionAsyncId());
}

const hook = createHook({
  init(id, type, triggerId) {
    segments.set(id, segments.get(triggerId));
  },
  destroy(id) {
    segments.delete(id);
  }
});

hook.enable();

I've only tested this code in v14.10, but this API surface hasn't changed much since v8.6.0, so barring outright bugs (possible with an API still marked as experimental!) I doubt anything different would be seen.
Obviously you would need to do testing across your supported versions, and avoiding regressions, such as with switching between automatic and manual etc, but you would have to do that with using AsyncLocalStorage too, and this is here now, and you're transitively already using it.

@simonbuchan thanks for the write up and POC, I think this is a fair feature request given cls-hooked's rustiness. I'm going to change the name of this issue and consider it a feature request for the same if you don't mind. This would probably be considered a breaking change since we have APIs that directly expose cls-hooked Namespaces, but it's still worth pursuing especially for a major version.

Sure sounds good!
Didn't see that you expose namespace instances: you might be able to reimplement them, but I agree it's not worth the risk.

@simonbuchan @willarmiros Given that this package is already limited to Node versions > 8 it seems reasonable to do a very small patch to simply import cls-hooked/context rather than cls-hooked that would skip the version detection but not require reimplementation of the cls-hooked feature set and types.

@simonbuchan @willarmiros Since 12.7 there's been native support for Continuation Local Storage (https://nodejs.org/docs/latest-v12.x/api/async_hooks.html#async_hooks_class_asynclocalstorage) 10.x leaves LTS support in 3 months (April 2021). at which point I would assume that xray-sdk could bring up the minimum engine version and cut a major version release that just used the native CLS features?

@simonbuchan @willarmiros Since 12.7 there's been native support for Continuation Local Storage (https://nodejs.org/docs/latest-v12.x/api/async_hooks.html#async_hooks_class_asynclocalstorage) 10.x leaves LTS support in 3 months (April 2021). at which point I would assume that xray-sdk could bring up the minimum engine version and cut a major version release that just used the native CLS features?

Any update on this?
With the 25-30% performance improvements using AsyncLocalStorage vs cls-hooked this is something that would be a big win.

Any update on this?

@cheruvian x-ray will no longer core dump when using rollup. As I recall there are 2 paths forward. The first is to release a major version update since the API for x-ray has some cls-hooked classes in it. The second option is to reimplement the cls-hooked bits that are part of the x-ray API using AsyncLocalStorage. That could avoid a major version update for the most part although it does introduce some risk.

@chris-pardy is correct on this. Also, the AWS Distro for OpenTelemtry JavaScript uses AsyncLocalStorage for context management by default, and has first-class support with AWS X-Ray. I would recommend checking it out for such performance benefits.


No dates available

I believe I'm being banned from making requests to the available dates endpoint, it's always returning "no dates available" in any region, does anyone knows if I need to reduce the requests interval to avoid this kind of issue?

Same here. I am also being thrown the same issue. No Available Dates. Any help is greatly appreciated.

Yeah, it's a ban. Will be unbanned in 3-4 hours. I wrote a Puppeteer solution for same purpose. The safe request frequency is 2 minutes.

I have waited for 10 hours and nothing change. Anyone had this issue?

Yeah, it's a ban. Will be unbanned in 3-4 hours. I wrote a Puppeteer solution for same purpose. The safe request frequency is 2 minutes.

I have been banned, waited for 10 hours with no luck. Any idea how to get unbanned?

Yeah, it's a ban. Will be unbanned in 3-4 hours. I wrote a Puppeteer solution for same purpose. The safe request frequency is 2 minutes.

How to add it to the bot?

So just use the following sleep() function instead which calls the function every 2 - 5 minutes randomly:
// sleeps randomly from 2 to 5 minutes function sleep() {   const randomDelay = Math.floor(Math.random() * (300 - 120 + 1) + 120); // Generate random number between 120 and 300 (2 to 5 minutes)   return new Promise((resolve) => {     setTimeout(resolve, randomDelay * 1000); // Convert seconds to milliseconds   }); }


Add importer for ISO 9660 files

This importer adds support for "regular" iso disk files. One issue is that it uses a fairly old package: https://pkg.go.dev/github.com/hooklift/iso9660 If this is an issue it's possible to change it to shell out to mount etc like the Windows importer does.

Think it should be all updated now.


Rat character sprites

Sprite Artwork

[ ] Standing
[ ] Losing
[ ] Attacking
[ ] Charging
[ ] Take Garbage
[ ] Battle Lost
[ ] Battle Won

#75 Rat character concept

moved to meistertask


[Feature] Hide “Play your own games” section

Device
All devices
Suggestion
Hi …
The “play your own games” feature is finally there.
But at the moment I don’t own any games on the Xbox store yet. And as a cloud only user without a Xbox console, I also have no plans to start buying games now.
So I would be happy if you could add the ability to hide the new “play your own games” section on the home screen with one of the next updates.
Thanks.

Hi @KingNothing81 , that's would be a great idea, so the other folks will not confuse about it.
I already build this function, and will pull-request to it.
I'm thinking to add icon that says "need to own", on all game section.

@madebyaris I'm happy to see that I'm not the only one that would like to hide something so many have been waited for. ;)
But I don't know if we need an extra mark for the games you need to own, as the games included in Game Pass already show a little GP icon in the bottom left corner.
But what I would like to see is that you can set a filter in the all games section that just hides the games you own, so it only shows the games included in GP.

Version 6.0 will have a new setting that disable this feature on both Home & All games pages.

@redphx Thanks. That's great. I wonder if it might need an explanation text, so people will know that it will also hide games in the "all games section"? Or how about calling it somehting like "Game Pass Only Mode"?

Added in 6.0


Orders are not displayed

Hello,
I have recreated the project "Simple data app with WPF and Entity Framework 6". Everything works so far, but the orders are simply not displayed in the data grid. I've tried everything, I even downloaded the project from GitHub and opened and built 1:1 directly in VisualStudio. Even then, the orders are not displayed. Can you help here?
Thanks and Greetings

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 42c0fa43-0ca5-9c86-f8c4-4b3eb7176250
Version Independent ID: bb93e3ff-0d52-9e93-c3a8-545b16f03a30
Content: Simple data app with WPF and Entity Framework 6 - Visual Studio (Windows)
Content Source: docs/data-tools/create-a-simple-data-application-with-wpf-and-entity-framework-6.md
Product: visual-studio-windows
Technology: vs-data-tools
GitHub Login: @ghogen
Microsoft Alias: ghogen

@MichiDIT -- thank you for your feedback.  This repo is solely for documentation issues, with limited help options.  Please consider these resources, and let me if you get your project up:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.
cc @ghogen for awareness


Change license header to BSL 1.1

Change license to BSL 1.1

coverage: 96.301%. remained the same
when pulling 3db8ee4f74a3f6178e18ea0b7e47085d700300eb on feature/license-change
into 618d9232510061bc11cd84aa77c0d98085866e95 on main.


Update README.md for paper ID # 1989 (from the first author), contact<EMAIL_ADDRESS>

Hi @thanhpv2102, 👋
Your changes have been accepted and merged. Thank you for your valuable contribution!


Just a question

Hey everyone,
So, I recently set up this tool on my Mac, and it all went smoothly without any errors.
I initiated a scan using the terminal command: mantis onboard -o google -t google.com
But here's the thing: it's been over 5 hours now, and there's still nothing showing up on the Mantis Dashboard. Any clue what might be going on, or where I might've messed up?
Thank you

tool running

You probably need to wait until the first onboard scan finished before the dashboard is setup. Use a small scope target (not google.com as it's huge) to easily test if the dashboard is setup correctly afterwards.

@Teicu On that note, we have built a custom dashboard that's faster and simpler than Appsmith. Can you try it out https://github.com/PhonePe/mantis/blob/main/setup/docker/docker-setup-macos-experimental.sh ? Would like to hear some feedback.

@Teicu On that note, we have built a custom dashboard that's faster and simpler than Appsmith. Can you try it out https://github.com/PhonePe/mantis/blob/main/setup/docker/docker-setup-macos-experimental.sh ? Would like to hear some feedback.

Thank you for your answer.
Can you please explain what I have to do exactly and how? Shall I start again from scratch?

I can confirm that the scanner is up and running, and I've managed to gather some data on the domain I'm scanning, including its subdomains.
it looks like this:
app: 'None',
source: 'external',
created_timestamp: '2024-04-18T12:44:45.169309+05:30',
cdn_names: [],
waf: [],
ports: [],
as_number: null,
as_name: null,
as_country: null,
as_range: [],
dns: null,
ipinfo: {},
technologies: [],
webserver: [],
updated_timestamp: '2024-04-18T16:12:40.620592+05:30',
active_hosts: [],
stale: false,
repositories: null,
others: {}
}
]
Type "it" for more
mantis>

Basically, the scanner has been running for 27 hours already and it's only 38%.
SCAN:  38%|██████████████████████████████▍                                                  | 861/2295 [27:01:38<42:55:09, 107.75s/it]
But as I said, I don't see anything in Dashboard

Hi @Teicu , so we have a number of modules that run starting from discovery, pre-recon, recon, scan etc.
A few more questions:

db.assets_collection.find().count(), whats the count and do you see data in any of the assets ?

Also, whats the command you ran, i dont see the org name ?
The reason i ask is if this data is filled up, then you should be able to see the results on the dashboard.

Also, did you setup the dashboard basedon these instructions - https://github.com/PhonePe/mantis?tab=readme-ov-file#dashboard-setup-

And as Bharath suggested, it would be good to start with a smaller domain.
Lastly, the scan is a very CPU intensive process, it is going to run a scan (nuclei) on all the subdomains discovered. Considering that org you are scanning might have a large assets, it might take considerable time.

btw, so I will only be able to see the result in the Mantis Dashboard when the scan finishes in the terminal?

I managed to resolve the issue in the end. Essentially, I initiated the Mantis Docker dashboard from Docker Desktop, which automatically launched another dashboard on localhost. Consequently, I had been futilely waiting to observe the outcome at http://mantis.dashboard:1337.

thank you all


Interval selection, filtered and rendered, results in extra data/marks

X -> Y

Show your :heart:  for vegalite by adding a tip!

*Tips will only be transferred when the issue gets resolved

Show your :heart:  for vegalite by adding a tip!

*Tips will only be transferred when the issue gets resolved


Failing to load the GPU-trained model onto CPU-machine

What is your question?
Hi, I cannot load neither model nor checkpoint from GPU onto CPU machine.
I followed the docs but the problem still remains. How can I resolve this issue?
Please follow the code sections below and its corresponding error messages.
Code
m_ae_model = LitAE.load_from_checkpoint(r'Path\version_1_load.ckpt', in_out_size, z_size)
TypeError: 'tuple' object is not callable
(in_out_size is a tuple, image dimensions for convolutional operations, whereas z_size is the latent variable dimension)
I also tried loading ".pt" model by placing it onto the CPU using map_location.
Code
location = torch.device('cpu')
m_ae_model = torch.load("m_ae_model.pt", map_location=location)
AttributeError: 'Trainer' object has no attribute '_enable_pl_optimizer'

What have you tried?
Saving GPU-trained model onto CPU (by model.to('CPU')), loading checkpoints.
What's your environment?

OS: Win (both machines)
Packaging pip
Version 1.1.3

Hi, please share the signature of your constructor or if possible the full code so that we can see if it is expecting positional args or keywoard args. Also please share the full error message so we can see where it originates from.
If your code has changed since you saved the checkpoint, it can result in errors like this.

Hi, please share the signature of your constructor or if possible the full code so that we can see if it is expecting positional args or keywoard args. Also please share the full error message so we can see where it originates from.
If your code has changed since you saved the checkpoint, it can result in errors like this.

Hi, thanks for getting back to me. Here is the code:
class LitAE(pl.LightningModule):
def init(self, in_out_size, latent_dim, lr=2e-4):
super().init()
self.in_out_size = in_out_size
self.latent_dim = latent_dim
self.lr = lr
    # encoder
    self.encoder = Encoder(self.in_out_size, self.latent_dim)
    # decoder model
    self.decoder = Decoder(self.in_out_size, self.latent_dim)

    self.encoder.apply(self.weights_init)
    self.decoder.apply(self.weights_init)

def forward(self, data_in):
    embedding = self.encoder(data_in)
    data_out = self.decoder(embedding)
    return data_out

def training_step(self, batch, batch_idx):
    x, y = batch
    # z = self.encoder(y)
    # pred_y = self.decoder(z)
    pred_x = self(x)
    train_loss = F.smooth_l1_loss(pred_x, x)
    # train_loss.retain_grad()

    self.log('train_loss', train_loss, prog_bar=True)
    return train_loss

def validation_step(self, batch, batch_idx):
    self._shared_eval(batch, batch_idx, 'val')

def test_step(self, batch, batch_idx):
    self._shared_eval(batch, batch_idx, 'test')

def _shared_eval(self, batch, batch_idx, prefix):
    x, y = batch
    # z = self.encoder(y)
    # pred_y = self.decoder(z)
    pred_x = self(x)
    loss = F.smooth_l1_loss(pred_x, x)
    self.log(f'{prefix}_loss', loss, prog_bar=True)
    return loss

def configure_optimizers(self):
    # optimizer = torch.optim.Adam(self.parameters(), self.lr)
    optimizer = AdaBelief(self.parameters(), lr=self.lr, eps=1e-16, betas=(0.9, 0.999), weight_decouple=True, rectify=True)
    return optimizer

def weights_init(self, m):
    if isinstance(m, nn.Conv2d) or isinstance(m, nn.ConvTranspose2d):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
    if isinstance(m, nn.BatchNorm2d) or isinstance(m, nn.BatchNorm1d):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
        torch.nn.init.constant_(m.bias, 0)
    if isinstance(m, nn.Linear):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
        torch.nn.init.constant_(m.bias, 0)

Load
location = torch.device('cpu')
m_ae_model = torch.load("m_ae_model.pt", map_location=location)
m_ae_model.eval()
with torch.no_grad():
x_hat = m_ae_model(x)
x, x_hat, y = x.numpy(), x_hat.numpy(), y.numpy()
Error screenshot:

Hi, thanks for getting back to me. Here is the code:
class LitAE(pl.LightningModule):
def init(self, in_out_size, latent_dim, lr=2e-4):
super().init()
self.in_out_size = in_out_size
self.latent_dim = latent_dim
self.lr = lr
    # encoder
    self.encoder = Encoder(self.in_out_size, self.latent_dim)
    # decoder model
    self.decoder = Decoder(self.in_out_size, self.latent_dim)

    self.encoder.apply(self.weights_init)
    self.decoder.apply(self.weights_init)

def forward(self, data_in):
    embedding = self.encoder(data_in)
    data_out = self.decoder(embedding)
    return data_out

def training_step(self, batch, batch_idx):
    x, y = batch
    # z = self.encoder(y)
    # pred_y = self.decoder(z)
    pred_x = self(x)
    train_loss = F.smooth_l1_loss(pred_x, x)
    # train_loss.retain_grad()

    self.log('train_loss', train_loss, prog_bar=True)
    return train_loss

def validation_step(self, batch, batch_idx):
    self._shared_eval(batch, batch_idx, 'val')

def test_step(self, batch, batch_idx):
    self._shared_eval(batch, batch_idx, 'test')

def _shared_eval(self, batch, batch_idx, prefix):
    x, y = batch
    # z = self.encoder(y)
    # pred_y = self.decoder(z)
    pred_x = self(x)
    loss = F.smooth_l1_loss(pred_x, x)
    self.log(f'{prefix}_loss', loss, prog_bar=True)
    return loss

def configure_optimizers(self):
    # optimizer = torch.optim.Adam(self.parameters(), self.lr)
    optimizer = AdaBelief(self.parameters(), lr=self.lr, eps=1e-16, betas=(0.9, 0.999), weight_decouple=True, rectify=True)
    return optimizer

def weights_init(self, m):
    if isinstance(m, nn.Conv2d) or isinstance(m, nn.ConvTranspose2d):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
    if isinstance(m, nn.BatchNorm2d) or isinstance(m, nn.BatchNorm1d):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
        torch.nn.init.constant_(m.bias, 0)
    if isinstance(m, nn.Linear):
        torch.nn.init.normal_(m.weight, 0.0, 0.02)
        torch.nn.init.constant_(m.bias, 0)

Load
location = torch.device('cpu')
m_ae_model = torch.load("m_ae_model.pt", map_location=location)
m_ae_model.eval()
with torch.no_grad():
x_hat = m_ae_model(x)
x, x_hat, y = x.numpy(), x_hat.numpy(), y.numpy()
Error screenshot:

How did you create the checkpoint "m_ae_model.pt"? Did you just use the automatic model checkpointing from pytorch? or did you  create it in a different way? It is a bit suspicious that torch.load would try to unpickle a trainer.

How did you create the checkpoint "m_ae_model.pt"? Did you just use the automatic model checkpointing from pytorch? or did you  create it in a different way? It is a bit suspicious that torch.load would try to unpickle a trainer.

Hi! I did save the checkpoint "m_ae_model.pt" with  torch.save(...). Once when trained on GPU and once when trained over CPU.
Another time I attempted to load a checkpoint (trained on GPU) from lightning logging folder via:
model = MyLightingModule.load_from_checkpoint(PATH)
But again, the issue remained the same.
On another note, how would you advise to save (whole/partial) models?

Hi! I did save the checkpoint "m_ae_model.pt" with  torch.save(...). Once when trained on GPU and once when trained over CPU.
Another time I attempted to load a checkpoint (trained on GPU) from lightning logging folder via:
model = MyLightingModule.load_from_checkpoint(PATH)
But again, the issue remained the same.
On another note, how would you advise to save (whole/partial) models?

See here https://pytorch.org/tutorials/beginner/saving_loading_models.html#save-load-entire-model
there are many disadvantages saving the whole model by pickling it. One example you see here, it will not work with a new version of PL for example.
You should save the state_dict instead. See https://pytorch.org/tutorials/beginner/saving_loading_models.html#saving-loading-model-for-inference

See here https://pytorch.org/tutorials/beginner/saving_loading_models.html#save-load-entire-model
there are many disadvantages saving the whole model by pickling it. One example you see here, it will not work with a new version of PL for example.
You should save the state_dict instead. See https://pytorch.org/tutorials/beginner/saving_loading_models.html#saving-loading-model-for-inference

You can use Trainer.save_checkpoint if you wish to be able to load your model with LightningModule.load_from_checkpoint

You can use Trainer.save_checkpoint if you wish to be able to load your model with LightningModule.load_from_checkpoint


UI: Add missing tooltips on service offering creation

Description
This PR adds the missing tooltips helpers to fields in the service offering creation: 'Compute only disk offering' and 'Disk offering stricteness'

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

What about "Disk offering strictness" checkbox?
Any reason to say that it won't work with deploy-as-is templates unless we are using custom disk size, etc, @nvazquez ?

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

Looks good on the QA server (disk strictness checkbox is missing, since it's 4.16.1 based/ACS)
I would like to have this disk strictness also with tooltip - do we have links when user click on that, that leads to the documentation (as with other tooltips?)
This one here:

I see (if I see correctly...) that the Decoupling of disk from service offering documentation is missing?
http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering
the main branch also is missing it: https://github.com/apache/cloudstack-documentation/blob/main/source/adminguide/service_offerings.rst
This needs be corrected (asynchronously from this PR) @harikrishna-patnala cc @nvazquez

@andrijapanicsb the tooltip has been added to the disk strictness. There is a documentation PR for that change which is still in progress cc @harikrishna-patnala https://github.com/apache/cloudstack-documentation/pull/238

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6376 (SL-JID-1561)

It did not say anything about deploy as is templates

Looks good on the QA server (disk strictness checkbox is missing, since it's 4.16.1 based/ACS)
I would like to have this disk strictness also with tooltip - do we have links when user click on that, that leads to the documentation (as with other tooltips?)
This one here:

I see (if I see correctly...) that the Decoupling of disk from service offering documentation is missing? http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering the main branch also is missing it: https://github.com/apache/cloudstack-documentation/blob/main/source/adminguide/service_offerings.rst
This needs be corrected (asynchronously from this PR) @harikrishna-patnala cc @nvazquez

I'm working on the doc PR, will update it asap.
Regarding "disk offering strictness" missing, I see it on other environments along with this PR changes also. So may be some issue with qa server not up to date.

@blueorangutan build

@blueorangutan help

@andrijapanicsb I understand these words: "help", "hello", "thanks", "package", "test"
Test command usage: test [mgmt os] [hypervisor] [keepEnv]
Mgmt OS options: ['suse15', 'centos7', 'centos6', 'alma8', 'ubuntu18', 'ubuntu20', 'rocky8']
Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-rocky8', 'kvm-alma8', 'kvm-ubuntu18', 'kvm-ubuntu20', 'kvm-suse15', 'vmware-55u3', 'vmware-60u2', 'vmware-65u2', 'vmware-67u3', 'vmware-70u1', 'vmware-70u2', 'vmware-70u3', 'xenserver-65sp1', 'xenserver-71', 'xenserver-74', 'xcpng74', 'xcpng76', 'xcpng80', 'xcpng81', 'xcpng82']
Note: when keepEnv is passed, you need to specify mgmt server os and hypervisor or use the matrix command.
Package command usage: package [all(default value),kvm,xen,vmware,hyperv,ovm] - a comma separated list can be passed with package command to bundle the required hypervisor's systemVM templates. Not passing any argument will bundle all - kvm,xen and vmware templates.
Blessed contributors for kicking Trillian test jobs: ['rohityadavcloud', 'nvazquez', 'borisstoyanov', 'DaanHoogland', 'shwstppr', 'andrijapanicsb', 'Pearl1594', 'davidjumani', 'harikrishna-patnala', 'vladimirpetrov', 'sureshanaparti', 'weizhouapache', 'NuxRo']

@blueorangutan package

@andrijapanicsb a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Come on @blueorangutan , you can do it, it's been a while....

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3394


Fixes exception thrown on exit issue #208

Pull Request Test Coverage Report for Build 551

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 86.073%

Totals

Change from base Build 544:
0.04%

Covered Lines:
1953

Relevant Lines:
2269

💛  - Coveralls


This repo's code is just incorrect.

I doubt it very much. Take care of using it. The author should be more responsible by sharing your code. Please consider to improve the code or write a warning to notice in your README.md. Thanks.

I agree with you
这段代码有点问题 不是原论文的复现


[ALLUXIO-1900] Verify something was read when closing RemoteBlockInStream

https://alluxio.atlassian.net/browse/ALLUXIO-1900

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9430/
Test PASSed.

LGTM

LGTM


Filtering using date is reset after page is refreshed

If I set date filter to see only test runs that have been running today, and then refresh page date filtering is reset

Not a bug, scope is lost after refreshing the page.


Add OTEL spans to SQS trigger

TODO: Determine why span is only appearing periodically. Seems to do with how we are passing the context of the spans on spawn.

@lann for some reason we're getting weird async Span issues and using in_current_span wasn't fixing them. From what I can tell we would only need in_current_span in aws.go, but even putting it everywhere didn't solve the issue.


unable to install chaos monkey

ATH017733:~ gneha$ go get github.com/netflix/chaosmonkey/cmd/chaosmonkey
ATH017733:~ gneha$ chaosmonkey migrate
-bash: chaosmonkey: command not found
can you please let me know what im missing on

It sounds like an issue with your PATH environment variable. Check out this Stack Overflow question.

I have Spinnaker on digital ocean , version 1.6.0. I can see the application Deck running on port 9000. While trying to install Chaos Monkey, I want to edit setting.js, but unable to find this file on Spinnaker.
Please advice

@Ragr2018 I'm not familiar enough with the open source Spinnaker deployment to help. I suggest you reach out on the Spinnaker Slack

I'm going to close this for now because it doesn't seem like an issue with Chaos Monkey itself.


vcpkg upgrade error

vcpkg upgrade does not even start
E:\vcpkg>vcpkg upgrade
error: The control or manifest file for boost-vcpkg-helpers could not be loaded
due to the following error. Please remove boost-vcpkg-helpers and try again.
E:\vcpkg\ports\boost-vcpkg-helpers: error: boost-vcpkg-helpers does not exist

boost-vcpkg-helpers does not exist sphysically in e;\vcpkg\ports

duplicate of #38487


Update extra75 to be aware of default security groups

Update extra75 to be aware of default security groups. Default security groups are demoted from FAIL to INFO when unused, since the default security groups can not be deleted there are limited options to remediate an unused default security group.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@toniblyx I've opened a new pull request


Integrate the bundle in symfony 3.2

Hi! I don't have Symfony Flex. I tried to put in my appKernel.php the following line:
new Endroid\QrCodeBundle\EndroidQrCodeBundle(),
but I have some errors:
PHP Fatal error:  Uncaught Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: A "tags" entry must be an array for service "Endroid\QrCodeBundle\Controller\" in services.yaml. Check your YAML syntax. in C:\Users\JoseAdame\Documents\QuadBuild\vendor\symfony\symfony\src\Symfony\Component\DependencyInjection\Loader\YamlFileLoader.php:270
Could you help me?
thanks.

You'll have to use 3.3+ for this bundle to work. You should update to 3.3 and then to 3.4 when you have a chance, because 3.2 maintenance is already ended.


Getting Error in outbound connection setup

Hi team,
We are getting the below-given message in the outbound connection test service. please let me know how to fix the outbound connection.

Please provide the LBNID for your tenant. A dummy relationship to one of the internal test tenant has to be established. You may request it by creating an incident to SCM-LBN-INT

Here is the ID (2497837)

Seems like the LBNID is incorrect. It is a 11 digit no. You can view it in the Manage Business Profile App. Also what's the name of that you have maintained in the Business Profile

LSorry, here is the correct id LBN ID:10010001467

An invite is already sent to your tenant. You need to accept the invite in manage invitations app

Hi Ravish,
Yes, we got the invitation and accepted it. Can you tell me how to check what request is sent to our outbound endpoint? because I did not find any request in my logs from SAP LBN.

org.apache.camel.component.ahc.AhcOperationFailedException: HTTP operation failed invoking https://api-staging.stagingfareyeconnect.com/connector/api/Connector/v1/sapLbnTest/test-service with statusCode: 404

We

org.apache.camel.component.ahc.AhcOperationFailedException: HTTP operation failed invoking https://api-staging.stagingfareyeconnect.com/connector/api/Connector/v1/sapLbnTest/test-service with statusCode: 404

We get this error

Thanks for your support, we have received the request successfully in the outbound connection.


[After #102] [Example] Add edc layout to the scaffolding @open sesame 05/18 16:27

Add main.edc to separate UI design/interactions
Changes proposed in this PR:

Add main.edc
Add view.[ch]
Add data.h
Change main initiation to use view function
Move data definitions to data.h

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #104. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/.

Need to resolve the conflicts.

Need to resolve the conflicts.

Thanks :) Conflict resolved!


Need improvemnet in  the date format for graph dipalying the efforts for the project

Describe the task
Currently, efforts logged by all the team members are captured and displayed in the graph. The graph includes the Bar plot for each day, and also the date under it. Instead of the date, we should mention the day and month like 01-July.
Please refer screenshot for the current implementation

Expected behavior
The date under the bar plot of the graph should be replaced by the day of the month and month like 01-July

Hi @akriti12negi can you please add your profile pic to the your GitHub profile

This issue PR is merged. Closing it.


ffi.Function underlying Callback is garbage collected

I'm trying to use a C library that stores some callbacks in an internal structure. I would like to use the ffi.Function type instead of ffi.Callback directly, so I can have a nicer JS library.
But it looks like the underlying ffi.Callback returned by ffi.Function.toPointer is being freed after a while (ffi fatal: callback has been garbage collected!).
I did a small use-case to reproduce my issue : https://gist.github.com/BenoitZugmeyer/886ce5c4aa4b3151c8fe
Below is a fix proposal working for me. The weakmap makes the Callback instance kept alive while the fn is not garbage collected. Obviously this patch is wrong as WeakMap is not in older versions of nodejs, and I'm sure it can be done more efficiently.
diff --git lib/function.js lib/function.js
index 30d5f90..5d23093 100644
--- lib/function.js
+++ lib/function.js
@@ -38,6 +38,7 @@ function Function (retType, argTypes, abi) {
   this.retType = ref.coerceType(retType)
   this.argTypes = argTypes.map(ref.coerceType)
   this.abi = null == abi ? bindings.FFI_DEFAULT_ABI : abi
+  this.pointers = new WeakMap();
 }

 /**
@@ -70,7 +71,10 @@ Function.prototype.indirection = 1
  */

 Function.prototype.toPointer = function toPointer (fn) {
-  return Callback(this.retType, this.argTypes, this.abi, fn)
+  if (!this.pointers.has(fn)) {
+    this.pointers.set(fn, Callback(this.retType, this.argTypes, this.abi, fn));
+  }
+  return this.pointers.get(fn);
 }

 /**

@BenoitZugmeyer Thanks for bringing this up. I agree that it feels like a bug. Will you take a look at 58f26d9 and let me know if that makes any sense to you? The main problem is that the WeakMap ends up acting like a regular Map in effect, since the callback buffer internally retains a reference to the JS function instance.

Indeed if I simply change the WeakMap to Map, this new test case still passes.

The WeakMap won't behave exacly like the Map internally. Indeed, the callback buffer will keep a reference to the JS function, but with the Map, the JS function will also keep a reference to the callback buffer, causing a memory leak as the JS function won't be freed until the ffi.Function instance (and thus the Map) is collected.
Another way to fix the issue would be to store the Callback instance in a function property:
if (!fn._ffiCallback) {
  Object.defineProperty(fn, "_ffiCallback", { value: callback });
}
return fn._ffiCallback;

(not tested)
This will make a one-way reference to the callback, like the WeakMap does.

I can confirm the example posted above https://gist.github.com/BenoitZugmeyer/886ce5c4aa4b3151c8fe passes (and doesn't appear to memory leak (using memwatch next/observing)  with @BenoitZugmeyer's fix.
Adding:
 Object.defineProperty(func, '_func', {value:callback});
To line 81 at https://github.com/node-ffi/node-ffi/blob/master/lib/callback.js#L81 fixed the test case for me.

You can't be serious. After hours of confusion, @trevorlinton's 1 line fix makes everything work again.

@TooTallNate
Is this fix sanctioned by you (tests, more accurately) ?
Adding that one-liner solved the GC callback problem, but I'm not %100 on how it works. So I need some input before I can push a modified OSS to production.

@TooTallNate
trevorlinton's solution works for me , what do you think?


Module.save moves Module to CPU

Version: <IP_ADDRESS>
In contrast in Python torch.save(module, path) does not.

I did it that way because it was the quick and safe thing to do, and documented it in the article on saving and loading.
If the difference in behavior is truly problematic, it should be relatively straight-forward to address it.

@NiklasGustafsson what article are you referring to? The C++ frontend documentation has no remarks about CPU vs CUDA tensors for torch::save.

@lostmsu I'm sorry -- I'm not quite sure I understand what statement of mine you are referring to.

@NiklasGustafsson oh, sorry, I thought

and documented it in the article on saving and loading

refers to PyTorch documentation, not TorchSharp documentation you wrote.
Still I don't see anything in PyTorch C++ documentation, that would suggest, that tensors need to be moved to CPU in order to save them. Does torch::save fail for GPU tensors?
Perhaps it will make more sense to make a CPU copy of the tensor before saving it instead of moving.

Right.
My statement was intended to refer to the TorchSharp article. With this latest PR, the tensor is moved to the CPU, then moved back to where it came from. I'll look into making a copy, instead.

@lostmsu -- the problem, as far as I can tell, with copying is that for a save, I have to first clone the tensor on the GPU, then move it to CPU. Since GPU memory is a scarce resource (and there's no virtual GPU memory), that's problematic.

Turns out, copy works on save(), but not on load().


ARMv7 NEON is not tested

There appear to be blatant compile errors on the ARMv7 polyfill, which are going unnoticed due to a lack of CI tests. Perhaps an arm-linux-gnueabihf CI test could be added?
Note that some tests will not be detectable on QEMU due to NEON having some alignment-sensitive instructions and QEMU ignoring alignment checks. (see note in comment 1 on #1023)
Once CI tests are added, I will happily go through and fix the existing bugs.

Hello @easyaspi314 ; yes, we used to test on real ARMv7 (and v8) with Drone.io; but that configuration broke and I've been unable to find time to fix it. Adding a qemu test with cross compilation will be easier for me.
Or if you can get Drone.io working on your fork of SIMDe then I can look at enabling that again!

Here's the first result: https://github.com/mr-c/simde/actions/runs/5036972757/jobs/9033504694#step:9:1067 from a test run using https://github.com/mr-c/simde/commit/168d4a8b78a3c2b8b78d74a92a993d432a92c50a


Simplify form

This is a fix for issue #2. It also includes some small improvements.

Oh the merge with the source from the server is going to be hell, but will do that later.


Layers package budget

Note: for general support questions, please use the mailing list<EMAIL_ADDRESS>This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
Report a bug
What is the current behaviour?
The layer thickness change can be partitioned by terms that contribute to the heat (or salt) budget.
Currently, it is not closed with advection scheme 80/81.
Feature requests
What is the desired behaviour?
Bug reports
Describe the steps to reproduce and if possible a minimal demo of the problem
I am running an idealized channel model with
nonlinFreeSurf = 0,
convertFW2Salt = -1,
linFSConserveTr = F,
useRealFreshWaterFlux = T
tempAdvScheme=80,
saltAdvScheme=80,
When "LAYERS_THERMODYNAMICS" is defined in "LAYERS_OPTIONS.h", you can get the contribution of advection, diffusion and surface forcing terms to the time changes of the thickness of the layers. The sum of all these terms are not the same with the contribution computed from the total tendency term.
What is the expected behaviour?
You should be able to close the budget.
In order to close the budget in the layers package with the advection scheme 80 (or 81), the subroutine 'LAYERS_WSURF_TR' in 'thermodynamics.F' should be skipped.
(Or there may be a better way to fix it.)
This is because the budget at the surface closes without 'WSLTMASS' term with the advection scheme 80 (or 81).
With this advection scheme,  'ADVr_SLT' term at the surface is not zero but contains the effect what 'WSLTMASS' does.
Please tell us about your environment:
(e.g. HPC environment, compilers, model version, etc.)
MITgcm version : checkpoint66g
compilers : ifort
Other information
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Hajoon, thanks for finding and documenting this bug.
I am now working on carefully writing down how layers works in its current form. That should help us diagnose the source of this problem.


Issues understanding the input format for eth_ucy

Dear reader, thank you for the great work on this topic and for realising the code for the community to improve. I am currently trying to understand the data format however am very unclear about how the eth_ucy dataset is actually preprocessed. Do I understand it correctly that only x and y coordinates are used and no velocity and heading inofmration is extracted. As looking through the data most columns only contain -1 values. Could you provide a column name list for the inputs found in the datasets/eth_ucy files?
Furthermore, is my understadning correct that only the ego agent informatin is stored in a given row? As from reading the paper my understanding was that all agent states would be stored in a single entry for each timestep. Could you maybe elaborate on how you create the

representation of the data that is described in the paper?
Thank you!

I think your question is similar w/this https://github.com/Khrylx/AgentFormer/issues/6


Same Name Contract Issue

Introduction
The current source code results for the compilation target are located by contract name, and the path information is missing. This means that we can construct two contracts with the same name in one source code. In the end,  we cannot locate the only contract as our compilation target.
Impact
Attackers can use the eponymous contract issue to confuse users and hide backdoors in the code.
Attack Case
https://optimism-goerli.blockscout.com/address/0x3C10387CF5cC4B655d12898C3628AF38C5E792c2?tab=contract
https://goerli-optimism.etherscan.io/address/0x3C10387CF5cC4B655d12898C3628AF38C5E792c2#code

@rimrakhimov

Hi, @Hellobloc! It seems that the main contract file is indicated as the only file opened in the editor by default. When the contract tab is opened there is only the "test.sol" file shown to the user.
I agree that it may be not quite obvious though. We will discuss it with our frontend team how we can make it more informative. Just would like to make sure that I got you right and the main concern here is not some algorithmic issue but more the data description inside the UI

@rimrakhimov Thank you very much for your quick response and the attention you have given to these issues.
Yes, it is a UI presentation issue and it is a ambiguity risk due to contract name not containing path information.

@Hellobloc I see. We'll discuss it with our design team how we can indicate that more clearly to the users. Thank you

@Hellobloc we've prepared a little demo how we are going to mitigate this issue in the UI. We've added file path field into the contract general info section and also an indicator of the main file to the tabs and files tree. Please take a look and tell us what you think.


consider using subscribe() instead of assign()

https://github.com/HashDataInc/bireme/blob/8f51d4fd7217ee72a728f15ac666f5110d11254f/src/main/java/cn/hashdata/bireme/pipeline/MaxwellPipeLine.java#L31
Even for Maxwell, we are using the same consumer group so that it is better to use subscribe() instead of assign()
Kafka would not let two consumers in the same consumer group to read from the same partition. So it would be safe to make such change.

@wangzw subscribe() method subscribe to dynamically assigned partitions. For maxwell, we build a pipeline for each partition, so I think using assign() to explicitly subscribe to a fixed partitions is a better chose.

@zhouyuze That's correct that we should build a pipeline for each partition,  but by subscribe the topic for each partition and leave the kafka to dynamically assign partitions instead of do it manually.

@wangzw I don't know exactly how "dynamically" works. Suppose we have two partition for topic A, and I create a consumer to subscribe A. Will it dynamically be assigned to both partition 1 and partition 2 ? But if then I create another consumer to subscribe A, will the partition 2 dynamically be assigned to the last consumer ? So both consumers have subscribed to partition 2. I can't guarantee the order  in partition 2. I think if we want to use subscribe, we must make it clear how "dynamically" work.

@wangzw @Rucfisher There is another problem. When the latter consumer failed, will partition 2 dynamically be assigned to the first consumer? If so, we must make sure that it will consume from the last committed offset not from where the latter consumer failed. Some experiment must be designed to verify correctness or read the source of kafka consumer.

If two consume in the same consume group and subscribe to the same topic which has two partitions, each consume will only works on one partition. Kafka will not let two consume in the same consume group read from same partition. So we can guarantee the order.

@zhouyuze Good point about the failure. kafka will rebalance the consumer on failure, but only uncommitted message will be delivered to consumer. So it is safe too.

@wangzw I understand. We can guarantee that we start all consumer simultaneously. It works currently. But if one consumer failed, we can't restart it while bireme is running. (Also currently bireme doesn't support this operation.) Suppose that bireme support this problem, there will be another problem. Consumer 1 subscribe partition 1 and consumer 2 subscribe partition 2. Suddenly, consumer 2 failed, and consumer 1 subscribe both partition 1 and partition 2.  Consumer 1 poll record A but not commit it. Then we restart consumer 2 while bireme is running. Kafka will rebalance the consumer and assign partition 2 to consumer 2. Later, Consumer 2 poll record A and and record B from kafka.

I understand.


Binary with tests

Extremely similar to #94, but improved to avoid that bad-looking option generation.
It also includes tests, and the README update.
cc @mafintosh @laszbalo @Introvertuous - please test before I release as minor.

I am wondering if we should default binary to true, and always convert strings to Buffer.

I originally assumed that the default was binary and was not sure what was wrong until I stumbled upon the aedes issue (#61).

@Introvertuous I have made the default.
@mafintosh I propose to release this as a minor release. There is a change of functionality, but I argue that was a bug.

merging and releasing.


Result mismatch for YOLOv3

Dear authors, I've been trying to compile YOLOv3 with onnx-mlir but I am having problems reproducing inference results with the output of onnx-mlir.
The ONNX input file I am using is the one that is available in the ONNX model zoo and I compiled the model with default settings:
onnx-mlir yolov3.onnx -o yolov3

I compared the output of onnx-mlir with the output of ONNXRuntime (the latter of which I verified), but unfortunately the results don't match up. I attached a short python script that should illustrate the issue.
I've tried to look more closely into the discrepancies and found that box coordinates are in the same ball park but the scores and the selection results are completely off. I have already tried fixing the size of the inputs using --shapeInformation "0: 1x3x416x416" but that didn't help. Please let me know if there is anything else I can do to help debug this issue.
#!/usr/bin/env python3

from PIL import Image
import numpy as np

def letterbox_image(image, size):
    iw, ih = image.size
    w, h = size
    scale = min(w/iw, h/ih)
    nw = int(iw*scale)
    nh = int(ih*scale)
    image = image.resize((nw,nh), Image.BICUBIC)
    new_image = Image.new('RGB', size, (128,128,128))
    new_image.paste(image, ((w-nw)//2, (h-nh)//2))
    return new_image

def preprocess(image_path):

    img = Image.open(image_path)
    image_size = np.array([img.size[1], img.size[0]],
                          dtype=np.float32).reshape(1, 2)

    boxed_image = letterbox_image(img, (416, 416))
    image_data = np.array(boxed_image, dtype='float32')
    image_data /= 255.
    image_data = np.transpose(image_data, [2, 0, 1])
    image_data = np.expand_dims(image_data, 0)

    return image_data, image_size

class InferenceSessionWrapper():

    def __init__(self, session):

        self.sess = session
        self.iname_0 = session.get_inputs()[0].name
        self.iname_1 = session.get_inputs()[1].name
        self.onames = [o.name for o in session.get_outputs()]

    def run(self, inputs):

        boxes, scores, selection = self.sess.run(self.onames,
                                                 {self.iname_0: inputs[0],
                                                  self.iname_1: inputs[1]})

        return boxes, scores, selection

if __name__ == "__main__":

    from argparse import ArgumentParser
    parser = ArgumentParser()
    parser.add_argument("image_path", default="./")

    from onnxruntime import InferenceSession
    a_session = InferenceSessionWrapper(InferenceSession("yolov3.onnx"))

    from PyRuntime import ExecutionSession
    b_session = ExecutionSession("yolov3.so")

    from glob import glob
    for image_path in glob(parser.parse_args().image_path+"/*.jpg"):

        image_data, image_size = preprocess(image_path)

        a_boxes, a_scores, a_selection = a_session.run([image_data, image_size])
        b_boxes, b_scores, b_selection = b_session.run([image_data, image_size])

        print(a_selection, b_selection)

@tjingrant I remember that you have a tool to compare the result with onnx runtime op by op. Can we use that tool to detect which Op created value divergence?

Here it is: http://onnx.ai/onnx-mlir/DebuggingNumericalError.html

Thanks for pointing me toward the testing tool. I had to make some minor modifications to make it work (submitted PR https://github.com/onnx/onnx-mlir/pull/1814) but it eventually pointed me to the first convolution. I noticed that this convolution has auto_pad=SAME_UPPER set. Could this be the problem, or should that option be supported?

I believe all the auto_pad options are supported. If you believe that this might be the cause of an error, you may always print the actual padding being used (hopefully it is known at compile time) and compare it to something coming from a different runtime (not sure if possible/how to do so).
There is a test/numerical/TestConv.cpp where you can also feed some combinations of CONV manually, so you could plug them in there and see if the results verify there. The test works with RapidTest which feeds random combination, but specific ones can also be used.


How to get a version of rustc which is used by cargo?

Hi!
I'd like to show which version of rustc is used by cargo in IntelliJ GUI. Currently we just invoke /path_configured_by_user/cargo --version and /path_configured_by_user/rustc --version, but this may be wrong. For example, [the rustc may not be in PATH](not in path). Also there is RUSTC environment variable...
What do you think about extending cargo --version such that it also prints the version of the compiler, like this:
$ cargo --version --verbose
cargo 0.10.0-nightly (10ddd7d 2016-04-08)

rustc 1.9.0 (e4e8b6668 2016-05-18)
binary: rustc
commit-hash: e4e8b666850a763fdf1c3c2c142856ab51e32779
commit-date: 2016-05-18
host: x86_64-unknown-linux-gnu
release: 1.9.0

Looks like rustc version is queried anyway:
$ rm ~/.cargo/bin/rustc
$ ~/.multirust/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo --version
error: Could not execute process `rustc -vV` (never executed)

Caused by:
  No such file or directory (os error 2)

And maybe cargo --version should work even if there is no rustc available?

Ah, I must say that I can't use cargo rustc -- --version, because when you configure cargo you don't yet have a Cargo.toml.

Heh yeah today we have rustc --version on hand (it's parsed when Config is created) but I'd prefer if we didn't do that. That's just an implementation detail though, so we could change at any time!
I'd actually be fine I think if we printed out rustc --version as well when we ran cargo --version, so long as we make it clear which is which.
@brson what do you think?

I agree with the motivation, and can't think of anything smarter to do. Hopefully though we we don't need to do the same for rustdoc.
I think cargo --version should work when rustc doesn't exist. That's bitten me before.

I've though about it more and came to the conclusion that we probably don't want this feature.
As for the original motivation about IntelliJ Rust, we now always explicitly pass ( https://github.com/intellij-rust/intellij-rust/pull/517 ) RUSTC environmental variable to Cargo and it works fine so far.
Knowing which rustc is used by Cargo can be useful for the end user to troubleshot problems, but I don't think that --version is the correct place to do this. Together with the compiler version we might want to output the path to the compiler, or the path to the configuration files or some other info. Something like cargo --show-config seems a better approach hear.
But Cargo almost always just works, so there is no need to provide this functionality.

Sorry for commenting on an old issue.
I see this as an either or; either

cargo just works most of the time, so there's no harm in cargo also upgrading rustc to latest stable by itself; and whenever a cargo command fails it could check for newer releases and suggest upgrading.

or

versions are important, and Cargo.toml should allow package creators to say which versions are known good and known bad, so users don't have to rediscover this by guessing maybe rustup to latest, or to one before latest, or ...

Case: Several beta testers for https://github.com/mimblewimble/grin/ have vargo build fail with some hard to understand error, and all they would need is to get rustc >=1.21
Thanks for your time. Workaround ideas very welcome

@sesam I think the up-to-date discussion is here https://github.com/rust-lang/rfcs/pull/2182

Thanks, and sorry, it seems I pasted my comment on the wrong issue.
I noticed that RFCs get closed. Your suggested 2182 (closed), 1953 (closed), 1707 (closed).
For your own original issue, I guess you could solve that by heuristics, reimplementing the same rustc discovery and selection code that cargo already uses... which probably saves the cargo team a few code lines, and adds more code lines elsewhere.

thanks i had install using the following guide, i think i just need to set the env variable to source from the updated rust version.
https://itsfoss.com/install-rust-cargo-ubuntu-linux/


Allow encryption on all possible fields and note when not possible

// Technically no customer facing changes here since everything that was altered was in TEST classes. The field we added to the block list will need to be documented.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Asteroids DoD document to see any additional details for the items below
Any net new LWC work has Sa11y tests & 50% or above lines JEST test coverage
CRUD/FLS is enforced in Apex
Permission sets are updated to account for CRUD|FLS|Tab|Classes
Field sets are updated to account for new fields
UX approval or UX not necessary

[ ] Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name (https://github.com/SalesforceFoundation/PMM/pull/303)
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer
[ ] QA
PR contains draft release notes

[ ] QE story level testing completed

W-8530539

W-8530539


Add a few vcr marks

Related issues and pull requests

Closes #164

Description
I can't completely do away with --network-access because the download-file-size-checks don't work with pytest-vcr. cc @drnextgis
Checklist

[x] Add tests
[x] Add docs
[x] Update CHANGELOG

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

Project coverage is 84.81%.  Consider uploading reports for the commit 3c72c22 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #166      +/-   ##
==========================================
+ Coverage   80.02%   84.81%   +4.79%
==========================================
  Files          16       16
  Lines         981      981
==========================================
+ Hits          785      832      +47
+ Misses        196      149      -47

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


Fix tests workflow to use numpy version in requirements.

Msprime depends on numpy too, and the recent release of numpy 1.20.0 has
meant that 'conda install msprime' installs the latest numpy instead of
the version we have in requirements.txt. So this changes the 'conda install'
line in the tests workflow to also install numpy (with the correct version).

Why not bump the numpy version in requirements.txt? msprime should be robust to any new version of numpy (unless they've changed the ABI)

Why not bump the numpy version in requirements.txt? msprime should be robust to any new version of numpy (unless they've changed the ABI)

Because numpy 1.20.0 drops support for python 3.6 :)  #192

Ah. Might be easier to drop py36 then? Messing with conda is rarely productive...

Yeah, we might have an easier time if we drop python 3.6. But I think we should still pin the numpy version that is installed with conda.

Picked up in #197.


Helm 3: OCI dependencies not found?

Output of helm version:
version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.15.8"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:12:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS. EKS for the cluster (probably not relevant) and ECR for the registry
I'm trying out the experimental OCI support and I stumbled upon something that looks like a bug to me (though I don't want to rule out that I might be using it wrong):
I have pushed a custom chart called my-chart to an amazon ECR registry as described here
Then, in an "aggregation chart", I'm depending on this artifact using the following dependencies:
dependencies:
        - name: my-chart
          version: 0.1.0
          repository: oci://<awsaccount>.dkr.ecr.<region>.amazonaws.com
        - name: kube-prometheus-stack
          version: 14.0.1
          repository: https://prometheus-community.github.io/helm-charts

(The prometheus stack is there to have the comparison with a traditional repository)
When I then run helm dependency update, both charts are downloaded to the charts/ directory as expected:
$ ls charts/
my-chart-0.1.0.tgz  kube-prometheus-stack-14.0.1.tgz

When I then use helm install passing each of these charts individually, they are installed on kubernetes as expected (so the charts themselves seem to be okay).
However, when I run helm install . --generate-name in the "aggregation chart", I get the following output
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: <...>

Error: found in Chart.yaml, but missing in charts/ directory: my-chart
helm.go:81: [debug] found in Chart.yaml, but missing in charts/ directory: my-chart
helm.sh/helm/v3/pkg/action.CheckDependencies
	/home/circleci/helm.sh/helm/pkg/action/install.go:612
main.runInstall
	/home/circleci/helm.sh/helm/cmd/helm/install.go:216
main.newInstallCmd.func2
	/home/circleci/helm.sh/helm/cmd/helm/install.go:120
github.com/spf13/cobra.(*Command).execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
	/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
	/home/circleci/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
	/usr/local/go/src/runtime/proc.go:204
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1374

Maybe helm is expecting a different filename convention in case of a chart from an OCI registry?
If I comment out the my-chart block and only keep prometheus, the same install command works as expected.

Thanks for reporting. Can you try to unpack the mychart tgz file into a "mychart" directory, and let us know if you get the same result?

Hi @jdolitsky, unpacking the chart into a "mychart" directory leads to the same result.
However, doing this I observed something interesting: When I subsequently delete all the contents of the "mychart" directory, the result was a different one: Now it complained about there not being a Chart.yaml. I concluded that the problem must be in my chart and not in the discovery and sure enough: The name I provided in the Chart.yaml did not actually match the name in the registry.
Of course that can't work - problem between keyboard and chair. :slightly_smiling_face:
So the only possible improvement for helm would be to detect that there is a mismatch between the two and return a better error message but the behavior now appears correct to me. Feel free to close this.


Consider porting to a language that doesn't require a runtime

In contexts where you don't require a Python install for other things, including nix-gl-host drags along of python 3 as a ~100mb bump in size.
For example - I have a Rust program that I package into a Docker image, and nix-gl-host ups that image size by 100mb due to its Python dep.
I've ported nix-gl-host to Rust here https://github.com/arilotter/nix-gl-host-rs and it seems to work perfectly!

Is that project really working?
I've tried to -p option work( https://github.com/arilotter/nix-gl-host-rs/pull/1 ) but it's just clearing old nixglhost's cache.
Also is the footprint of python nix-gl-host large?
I've calculated size of my cache(cuda+gl drivers) but it's far more large:
du -sh ~/.cache/nix-gl-host/
3.1G    ~/.cache/nix-gl-host/

And is rust with libc runtime free? You're using patchelf that also requires libc
$ nix-store -q --tree result
/nix/store/g6f6sk3cxfdv01zaj9b46dhfsv9ypbkd-nixglhost-0.1.0
├───/nix/store/5adwdl39g3k9a2j0qadvirnliv4r7pwd-glibc-2.39-52
│   ├───/nix/store/h44h6473all3qkrjjhkm3v0fv63lqyms-libidn2-2.3.7
│   │   ├───/nix/store/f4dfwhawi5kn71k0q1rj296w33i61vp6-libunistring-1.2
│   │   │   └───/nix/store/f4dfwhawi5kn71k0q1rj296w33i61vp6-libunistring-1.2 [...]
│   │   └───/nix/store/h44h6473all3qkrjjhkm3v0fv63lqyms-libidn2-2.3.7 [...]
│   ├───/nix/store/kx9pbw29jml0fgrpkb89f029w25qyxwc-xgcc-13.3.0-libgcc
│   └───/nix/store/5adwdl39g3k9a2j0qadvirnliv4r7pwd-glibc-2.39-52 [...]
├───/nix/store/jfilhsiqdgm4nks2z6labx3iq9qd077a-gcc-13.3.0-lib
│   ├───/nix/store/5adwdl39g3k9a2j0qadvirnliv4r7pwd-glibc-2.39-52 [...]
│   ├───/nix/store/mqnjhrjh72d6i4nn2rr7n6nl24qjjvcs-gcc-13.3.0-libgcc
│   └───/nix/store/jfilhsiqdgm4nks2z6labx3iq9qd077a-gcc-13.3.0-lib [...]
└───/nix/store/ywz6s6bzap4x6yhg2lrx3ibqcnv051c7-patchelf-0.15.0
    ├───/nix/store/5adwdl39g3k9a2j0qadvirnliv4r7pwd-glibc-2.39-52 [...]
    └───/nix/store/jfilhsiqdgm4nks2z6labx3iq9qd077a-gcc-13.3.0-lib [...]

ah nice catch, I mis-implemented -p. will fix.
it does seem to work for wrapping executables, it lets me run a Nix CUDA application in an Ubuntu docker image :)


Bug: nothing happens when clicking "No file"

I'm using the sfizz in REAPER on KDE Arch Linux. Both the LV2 and VST3 plugins won't let me select an SFZ file to load. Nothing happens when clicking "No file" in the plugin GUI.
I also tried dragging a file onto the VST plugin GUI in REAPER and had no luck. However, dragging a file onto the LV2 plugin in Carla does work.
My file manager is the default KDE Dolphin. I doubt it's any specific issue of the file manager.

Hi, do you have either the kdialog or zenity package installed?
It needs this helper installed in order to present the file dialog.
As of the file drag&drop, it's available only on these hosts which implement the support of it.
In particular, Reaper does not permit this feature currently.

That made it work. Thanks a lot!
Why did I never have this issue with other programs? Are there many different file dialogs? Do other programs happen to use file dialogs other than kdialog and zenity?

The linux audio plugins have problems when they call directly into GTK for opening the file dialog.
eg. if a host is using Qt and the plugin calls GTK, this creates a fatal incompatibility.
It's the typical fix to this problem to invoke an external program, that will not be subject to this problem.
The approach is identical in Surge synthesizer.


Referer header is not passing to request

Bug description:

To Reproduce:

Expected behavior:

Screenshots/Videos:

Environment:

OS:
OS version:
react-native version:
react-native-webview version:

This is a very minimal description. Could you be more explicit?

i am trying to post data with header (it is working with IOS but not working with android).


Download overhead costs associated with firing GeoQuery once

The question I have is posted here in detail:
https://stackoverflow.com/questions/46896628/data-downloading-cost-of-geofire-geoquery
Summary: If I fire Geoquery once every 3 seconds, will all the keys satisfying the query be downloaded by the mobile in bulk?? or will it come as seperate downloads.
The reason I ask this is to minimize overhead costs for download. For example,
if two users (A & B) satisfy a GeoQuery (i.e they are within a certain radius of me),
then
instead of using the onKeyMoved function to download the updates of A or of B individually, isn't it better to only have a GeoQuery download the locations of both A & B initially, then disable it and restart the same query after every 3 seconds or so??
The idea I have in mind is that by clubbing A & B together in the download, I will be able to reduce my total download overhead cost.
But I may be wrong and that is why I want to know whether I am justified in using this approach and whether there are any better approaches for reducing download overhead costs associated with GeoQueries.

Have you tried analyzing this and using the Android Studio Performance Tools in 3.0.0?

Should we close this since it's inactive? If we ever run into this again we can create a new issue and put some more effort / dedication into this.

Yeah. Please close it.
On Mon, Dec 18, 2017 at 6:02 PM, Niklas Baudy<EMAIL_ADDRESS>wrote:

Should we close this since it's inactive? If we ever run into this again
we can create a new issue and put some more effort / dedication into this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/geofire-java/issues/81#issuecomment-352413232,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeBrVM-pfy8LyoEbVNW-63QiTZmDVHEDks5tBltogaJpZM4QGDe8
.


pause command

Create a command that executes the pause functionality.
Also create a command that unpauses.

Need to implement "quiz"."quiz unpause" and "quiz".""quiz pause" in API