Change ubuntu based images to gcr.io/distroless/static.

This pull requests relates to #12122

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kramerul
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

@kramerul: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
efeb84e5514839e499ebeefbdc84dc073e0c7cae
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
d2aff2d1594c9ab17d4fa44cc24615f815ff7a46
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kramerul: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
e002f19b5c41aad5dc54d286e3d88d2e4b51d68e
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
d2aff2d1594c9ab17d4fa44cc24615f815ff7a46
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
d2aff2d1594c9ab17d4fa44cc24615f815ff7a46
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

Would these images still contain libraries like libnettle, libhogweed etc?
We are currently calling these from Lua filters in Istio because istio/proxy doesn't expose the embedded BoringSSL library.
If neither one nor the other is available, that would be a serious problem for us.

@costinm can you take a look?

@ozevren - we are not merging these PRs as is.  They are an experiment to determine if using a distroless base results in a green gate across our image set.  Thus far data looks good.
I believe the next step is to determine how to ship both a distroless and ubuntu based image in T&R.
More to come at env wg meeting.
Cheers
-steve

@sdake, thanks for the info. I'll remove myself from the reviewers, if you don't mind. :)


Table 36 - Tableextensions - RecreateSalesLines - global function ?

I need to recalculate salesline when changing "Customer Price Group" - but the standard function at T36 "RecreateSalesLines" is Local and not available.
Is it possible to make the function global ? - or do I need to clone the function into a tableextension ex. (ChangeCustPriceGrpRecalculateSalesLine)
I think the best way to do it is
    Modify("Customer Price Group")
    {
        trigger OnAfterValidate()
        var
        begin
            RecreateSalesLines(FieldCaption("Customer Price Group"));
        end;
    }

and not
    Modify("Customer Price Group")
    {
        trigger OnAfterValidate()
        var
        begin
            //ChangeCustPriceGrpRecalculateSalesLine = Clone of "RecreateSalesLine"
            ChangeCustPriceGrpRecalculateSalesLine(FieldCaption("Customer Price Group"));
        end;
    }

You need to use event in this function

OK - but stil have to clone the code from T36 because "RecalculateSalesLine" are a local function

This function is global. Please recheck
procedure RecreateSalesLines(ChangedFieldName: Text[100])
var
TempSalesLine: Record "Sales Line" temporary;


Display better error message when using hot module replacement

Fixes #68

Awesome :-) Thanks for looking into it!

No problem :+1:
Seems to work on both examples, but "Debug in Safari" crashes the app due to https://github.com/facebook/react-native/issues/2464. Just going to have Chrome in the error message for now.


Add INMANTA_RETRY_LIMITED_MULTIPLIER to tox.ini (#320)

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

Merged into branches iso5 in 0a6d9c64f09c16464922e74d7f61744ef592bafd


client: alternate server tips

At least the example should be provided.
Maybe some auxilary API.

Closing in favour of separate client package.


Forward options to the AioHTTP app.

Changes proposed in this pull request:

The **options arguments the AioHttpApp.run method are not forwarded to the run_app method of the aiohttp framework. It is analogous to what is done here: https://github.com/zalando/connexion/blob/master/connexion/apps/flask_app.py#L93, but for the flask framework.

@cognifloyd thanks for your comments. I updated my PR as discussed.
Do you have a list of contributors? Can I add my name? What is your policy on that?

I do not see a contributors doc. :) Now for someone at Zalando to hit the merge button...
@hjacobs? @jmcs? This one is a simple but helpful fix. Please merge.

:+1:


Add Marker and MarkerArray visualization support

In my last project, I needed visualization marker support in Unity so I created some of those. Later on I added the remaining ones.
I created the files based on the LaserScan structure.
This is the result in Unity:

And the same scene in RViz:

You only need to add a MarkerSubscriber / MarkerArraySubscriber to your RosConnector and enter a Marker or MarkerArray  topic. This works for all types except meshes. For meshes you need to copy the respective prefab into the Assets/Resources folder before subscribing to the topic.

Hi @Jntzko
thank you for your work on Marker Visualization in Unity and RViz and for preparing this code package.
I don't want to include it into ROS# master, however. ROS# focuses on being a communication framework that can be extended and adjusted for application-specific needs. I consider this marker visualization as a very nicely elaborated, yet application-specific extension. The concept of communication and visualization is taken over from the already existing LaserScan visualizations, whereas including this code package into ROS# would increase its complexity and maintenance effort without demonstrating really new functionality.
If you would like to share your Marker Visualization package with community, I'd suggest you publish set in a dedicated fork of the ROS# repo. If you do, please tell me the link such that I can refer to it add a dedicated place from this repo.


Fix resource_url and authority_url mapping and handling for datastore service principals

Description
This PR fixes resource_url and authority_url mapping and handling for datastore service principals.
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[X] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


SessionFactory must create sessions

SessionFactory must create a complete session.  If "create" is passed as a parameter
then DefaultSessions can be created with a null httpSession which is wrong.
The correct behavior is for the Request to control creation of the Session.
Refs #87.

I think that we have a problem in this scenario:

first request from browser => a RouteHandler calls Request.getSession()
second request from browser => a RouteHandler calls Request.getSession(false)
In the second request I retrieve a null session.

Hmm.  Ok.  You are right.


Exercise Tracker App: 5th test times out

Describe your problem and how to reproduce it:
I can't figure out why the 5th test times out with this error:
I can retrieve a full exercise log of any user by getting /api/exercise/log with a parameter of userId(_id). App will return the user object with added array log and count (total exercise count). (Test timed out)
// tests completed

The strange thing is that all other tests are passing including the last one which is using the same endpoint as the 5th one.
I also test it manually and it is working fine. I even added a middleware to check all incoming requests and used the same endpoints to clarify that there is no problem with the code.
I am using Glitch for the challenge.
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/apis-and-microservices/apis-and-microservices-projects/exercise-tracker

Hello there,
In general, I recommend an issue like this be opened as a topic on the forum. Be sure to include a link to your project. Unfortunately, the tests do not align perfectly with the challenge descriptions, and are extremely specific.
If it is determined, on the forum, that the issue is with the tests (source code), then I welcome you to reopen this issue.
For now, I am closing this.
Thank you.

Following on from this thread: https://www.freecodecamp.org/forum/t/exercise-tracker-test-times-out/383763
It has been determined that the issue is to do with the tests.

Following on from this thread: https://www.freecodecamp.org/forum/t/exercise-tracker-test-times-out/383763
It has been determined that the issue is to do with the tests.

Is this the actual test file being used for the project? https://github.com/freeCodeCamp/freeCodeCamp/blob/master/curriculum/challenges/english/05-apis-and-microservices/apis-and-microservices-projects/exercise-tracker.english.md

@pinglinh , Yes, it is.

@Sky020 What framework is it? I was trying to work out how I could potentially add a fix to this so that it fixes the timeout issue. I also have this problem on my project and would really like this to be marked as done 😅

@pinglinh , Well, the file is a MarkDown file with the tests written in a yaml syntax, but that is parsed before being run. The tests are run using Chai asserts, but most of it is plain JS.
It may help to go through the above mentioned forum post.

Between our refactors of the boilerplates, challenge tests, and markdown parser, is this issue still present?

@nhcarrigan I am going to close this, as it has not come up again since (that I have experienced or seen). It can simply be reopened if we manage to replicate it.


Project Management Console: Popup window is still displayed when navigated back to All Projects page in the browser

Background

Launch Project Management Console
Login as Project Manager
Click on Foundation(External Project)
Click on Add CLA Group
CLA Group popup window is opened
Click on Back button in the browser
User is able to navigate back to All Projects while the CLA Group popup window is still open
Issue also observed for all popups that are displayed in the page

Issue is still reproducible for all popup's in the UI and hence reopening the ticket

@dealako @nirupamav  Solved browser back button issue for popup on below model. Please let me know if any missing.

Connect Github Account
Delete Github Account
Add CLA Group
Delete CLA Group
View Signatures
View Companies
Configure Github Repositories
Add Gerrit Instance

Observed that issue is not fixed for below scenarios and hence reopening the ticket
1. CCLA template history popup

2. CCLA PDF Viewer

3. ICLA template history popup

4. ICLA PDF viewer

5. Connect LF CLA App to GitHub Organization popup

6. Github login alert

Verified below scenarios and observed that popup window is closed and projects page is displayed

Add GitHub  Organization popup
CLA group popup when clicked on ADD CLA GROUP
CLA group popup when clicked configuration icon for the cla group
View Signatures popup
View Companies popup from both the View Companies button
Delete alert popup
Delete confirmation popup
Configure Github Repositories popup
Add Gerrit Instance popup
Delete Github Organization

When clicked on back button from Select Template page user is redirected to Foundation details page

@nirupamav Thanks for list down missing screens. I will solve the above.

Verified below scenarios and observed that popup window is closed and projects page is displayed

Add GitHub Organization popup
Connect LF CLA App to GitHub Organization popup
Github login alert popup from Connect LF CLA App to GitHub Organization
CLA group popup when clicked on ADD CLA GROUP
CLA group popup when clicked configuration icon for the cla group
View Signatures popup
View Companies popup from both the View Companies button
Delete CLA Group alert popup
Delete CLA Group confirmation popup
Configure Github Repositories popup
Add Gerrit Instance popup
Delete Github Organization
CCLA template history popup
CCLA PDF Viewer
ICLA template history popup
ICLA PDF Viewer

When clicked on back button from Select Template page user is redirected to Foundation details page


Gene Refactor 1

I have just finished a significant refactor of the gene package to add in several new fields to the struct handling coding and UTR sequences. I have broken up the pull request to make each one easier to review.

I did some much needed simplification of fromGtf. It should be a bit easier to follow now.

I did some much needed simplification of fromGtf. It should be a bit easier to follow now.


feat(ui): mmb panning (another approach)

Summary
As part of resolving merge conflicts in #7007, I noticed two issues:

The MMB panning didn't work with pointer events, but we need to use them for tablet support.
There was also an edge case where if the tool was changed mid-MMB drag, the drag event didn't stop so it couldn't clean up after itself.

As I was troubleshooting 1) and looking at Konva's GH, I was reminded of the simpler way to implement MMB panning (as seen in this PR). I had tried approach a while ago but couldn't get it to work. Of course, the problem was (mostly) my own code.
There were two challenges:

Konva's docs say that the default drag buttons for all drag events is primary mouse, but this isn't true. The actual default is primary OR middle. Some of the weirdness I had run into during the earlier attempt was caused by this.
In the tool module's render method, we were setting the stage's draggable status depending on the selected tool. This was short-circuiting any manual drag logic we implemented. I think this was the root cause of the issue I had issue 1) in #7007.

The MMB panning implementation in this PR resolves the two challenges, and addresses the issues with the implementation in #7000.
Related Issues / Discussions

Supersedes #7007

QA Instructions
Test out MMB panning.
Merge Plan
n/a
Checklist

[x] The PR has a short but descriptive title, suitable for a changelog
[ ] Tests added / updated (if applicable)
[ ] Documentation added / updated (if applicable)

sweet and simple. just works.


Move import declaration adding into transpiler

Currently we have this code in plugin-rollup:
https://github.com/kungfooman/RuntimeTypeInspector.js/blob/555c5c602d2fbfc68cb84007e942d436d0f84c60/plugin-rollup/index.mjs#L5-L19
This has to be used by every plugin, so we have to move it into transpiler.
And then the REPL has to run the code via <script type='module'>...</script> on Shift+Enter.

Fixed by #51


Cleanup packaging

The package is not integrated with our CI, so I would prefer to omit the special formatting for changelog extraction to not suggest false perception that it does something here.

Changes are part of JB#58885


Improve native GitHub workflow

Codecov Report

Merging #342 (0fe3e06) into main (ec08514) will decrease coverage by 0.19%.
The diff coverage is n/a.

:exclamation: Current head 0fe3e06 differs from pull request most recent head cb13d69. Consider uploading reports for the commit cb13d69 to get more accurate results

@@             Coverage Diff              @@
##               main     #342      +/-   ##
============================================
- Coverage     79.70%   79.51%   -0.20%
  Complexity      114      114
============================================
  Files            45       45
  Lines          2060     2060
  Branches        303      303
============================================
- Hits           1642     1638       -4
- Misses          268      271       +3
- Partials        150      151       +1

Impacted Files
Coverage Δ

...parser/camelroute/CamelRouteStepParserService.java
69.23% <0.00%> (-10.26%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Correctly handles nested properties that are mandatory and have defau…

…lts.
closes #1022

Here is a nested property for a resource that is mandatory and has defaults:


Invalid Query with Combination of Parameters

Describe the bug
Query results in OperationOutcome related to a Server Error.
Response
{
    “resourceType”: “OperationOutcome”,
    “id”: “7f-0-0-1-90793d69-95e5-478a-aa88-d83f0ed45ee4",
    “issue”: [
        {
            “severity”: “fatal”,
            “code”: “exception”,
            “details”: {
                “text”: “FHIRPersistenceDataAccessException: Server error: failure retrieving count”
            }
        }
    ]
}

[ERROR   ] Failure retrieving count. SQL=SELECT COUNT(DISTINCT R.RESOURCE_ID)  FROM Claim_LOGICAL_RESOURCES LR  JOIN Claim_RESOURCES R ON R.LOGICAL_RESOURCE_ID = LR.LOGICAL_RESOURCE_ID   AND R.RESOURCE_ID = LR.CURRENT_RESOURCE_ID   AND R.IS_DELETED <> 'Y'  JOIN Claim_STR_VALUES  AS param0 ON (param0.PARAMETER_NAME_ID=1274 AND (param0.STR_VALUE = ? OR param0.STR_VALUE = ?)) AND LR.LOGICAL_RESOURCE_ID = param0.LOGICAL_RESOURCE_ID WHERE  EXISTS (SELECT 1 FROM Claim_TOKEN_VALUES  WHERE (Claim_TOKEN_VALUES .PARAMETER_NAME_ID=1430 AND Claim_TOKEN_VALUES .LOGICAL_RESOURCE_ID = R.LOGICAL_RESOURCE_ID)) JOIN Claim_DATE_VALUES  AS param2 ON (param2.PARAMETER_NAME_ID=1116 AND ((param2.DATE_END > ?))) AND LR.LOGICAL_RESOURCE_ID = param2.LOGICAL_RESOURCE_ID
  searchArgs=[https://localhost:9443/fhir-server/api/v4/Patient/17478962b6b-f5962e0b-8aa1-4f52-8b5d-13fc351a82c9, Patient/17478962b6b-f5962e0b-8aa1-4f52-8b5d-13fc351a82c9, 2001-12-31 23:00:00.0] [probeId=c0-a8-56-14-95011865-3425-4a2e-85dc-a82ab5e0a413]
Syntax error: Encountered "JOIN" at line 1, column 561.
[ERROR   ] Server error: failure retrieving count
Server error: failure retrieving count

To Reproduce
Steps to reproduce the behavior:
1 - Start the IBM FHIR Server
2 - Call
curl --location --request GET 'https://localhost:9443/fhir-server/api/v4/Claim?patient=Patient/17478962b6b-f5962e0b-8aa1-4f52-8b5d-13fc351a82c9&use:missing=false&created=gt2002-01' \
--header 'Authorization: Basic CHANGED' \
--header 'Content-Type: application/json'
```

**Expected behavior**
Bad Request or a  corrected query with a bundle response

**Additional context**
@d0roppe found this one.

Ran the 15 different searches part of the JMeter tests that was held on this issue, and they all work.


Allow code and file navigation to always open in a separate editor

I've searched for this and to my surprise didn't find it.
When control/cmd-clicking a code element to go to its source, or when clicking a file on the folder pane, sometimes the target file will open in the same editor we're using, rather than in a separate one. I don't like that.
If we're in an editor with unsaved changes, or if we double-click the file on the folder pane,  it will always open in a new editor (or an existing one, if the other file is already open)
But even in other cases it does use a separate editor, I've been unable to determine when.
I would like an option for it always to use a separate editor (a new one, or an existing one if the file is already open). I even think thats should be the default, but I'll happy if there's an option.

@entonio pls see
https://github.com/Microsoft/vscode/issues/62433#issuecomment-435580305 above.

Thank you for solving the problem I was having.

I've looked at the setting. Yes, it is what I was talking about. No, I would never be able to find it, short of reading the description of all settings one by one (which is not something I'd do when a filter is available). Neither the name, nor the default value, nor the first part of the description are in any way adequate, in my opinion. It's very por UX and would constitute a bug in itself, in my opinion.
My 'preview editors' do not show in italic font. That is objectively a bug either with the font or the description.
I think waiting a bit before autoclosing issues would be in order. Some of us don't always have immediate access to vscode during weekends.
The autoclose message's tone is condescending.

To be clear: I've struggled with this problem for months and never suspected there would be a setting already, as I didn't find one the various times I've looked for it. I'm sure I'm not alone in this.


0.12.0 updated

When can 0.12.0 be updated

Use the official image if you want to update to 0.12 - Support is now built-in so this version is redundant.

Well, thank you


Instance Id missing on domain removed events

In the zitadel evenstore all events should have an instance id, as they always belong to an instance. The instance.domain.removed events do not have an instance id, but only an aggregate id.

can not be reproduced anymore


“python setup.py install” for flash-attention reports errors

Hello there,
Thank you for your remarkable work and I am really interested in looking into it. The whole installation process works smoothly until the very last command. The “python setup.py install” for flash-attention reports "RuntimeError: Error compiling objects for extension" alongside with huge amount of error messages so that I have no clue how to debug.
Does anyone meet similar issue? Any feedback is greatly appreciated!

Never mind. Let me look for the solutions on https://github.com/Dao-AILab/flash-attention/issues first


Missing yarn/npm install step in Docs Site and README.

Hi,
This library looks interesting, but I have no idea how to add it to my project because the package name isn't listed anywhere on the readme or the docs site.
Installation is the first step –  it's important enough to put on the home page of your docs site and the README.md
Thank you,
Michael

Same problem. Can't find installation instructions anywhere.

I had the same problem. After extensive searching, I managed to find the project on npm. Here are all the useful links to get you started:
https://bestofjs.org/projects/potion
https://www.npmjs.com/package/number-picture
Note:
potion js was previously numberpicture js as declared below:
https://medium.com/@numberpicture/numberpicture-js-becomes-potion-fbf6425b3188
The link takes you to potion-js' account on medium. They also state that they have refactored the library out into several submodules: @potion/element, @potion/layout, @potion/extra and @potion/util.
These modules are all found on npm by their respective names. Links:
https://www.npmjs.com/package/@potion/element
https://www.npmjs.com/package/@potion/layout
https://www.npmjs.com/package/@potion/extra
https://www.npmjs.com/package/@potion/util
Other associated projects include:
https://www.npmjs.com/package/@potion/color
https://www.npmjs.com/package/@potion/main
https://www.npmjs.com/package/@potion/dev
I have to agree that the documentation on installation hasn't been great. But I hope the links will help you.

a bit delayed but @iMerica thanks for the feedback - I will add installation docs. @BossBele thanks for collecting the info here


Stricter TypeScript definitions

Currently mithril.d.ts has a lot of usages of the any type. Often in TypeScript it's desirable to have stricter definitions, to get the full benefit of the compiler.
any pretty much circumvents the compiler, like dynamic in C#. So it will compile, but won't necessarily be correct and may throw errors at runtime. For this PR I've systematically eliminated any from the .d.ts, which will hopefully make it easier to write correct TypeScript programs. In the process I found and fixed a few other minor differences between the defs and what Mithril actually does (and learned a ton about dynamic programming, haha).
To test that these stricter definitions are correct, I ported the unit tests to TS with minimal changes beyond adding type annotations. These compile (including with the --noImplicitAny flag) and pass. I also ported the Todo app example to TS. You can see these here. If it helps I can stick running examples on my github.io.

This looks awesome! Thanks!


Feat: add external scaler

BackGround
When stateful game servers need to be scaled horizontally, it is necessary to avoid deleting the game server that players are playing on. Therefore, the state of the GameServers need to be taken into account when scaling down. OKG determine the value of replicas according to the state of these GameServers.
Design
OKG exposes metric gssReplicas, which indicates the number of replicas of the corresponding GameServerSet.
Only GameServers whose opsState is WaitToBeDeleted will be deleted, that is to say, the desired number of replicas is the current number of replicas minus the number of WaitToBeDeleted replicas, so that the deletion of game servers can be guaranteed to be absolutely safe.

Codecov Report

Merging #39 (c894117) into master (6b58728) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c894117 differs from pull request most recent head ec267f1. Consider uploading reports for the commit ec267f1 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   22.50%   22.50%
=======================================
  Files          13       13
  Lines        1502     1502
=======================================
  Hits          338      338
  Misses       1144     1144
  Partials       20       20

Flag
Coverage Δ

unittests
22.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Precompute IDFs in scoring process

Thanks for the library!
I've been prototyping something with this and found the performance on my dataset (~1200 documents, average of 240 words) wasn't quite enough for how I'd been hoping to use it, but when I profiled the code I saw that most of the time was actually being spent in the getIDF function, which happened to be called redundantly in the main scoring loop.
Precomputing the IDF values for each keyword like this is a pretty big performance boost, I'm seeing 80%+ faster searches on my data, down from 3.6s to 280ms with three keywords.

Here are some benchmarks searching against the 20 Newsgroups dataset. 99.94% faster on a two word query over 20k documents!
I haven't added tests because testing based on performance benchmarks is not especially reliable IME, though you'll see in the script I added assertions that the output between this update and the original is identical.
Original meaning the library as installed off of npm, Updated being the compiled version from this branch.
Version | Number of documents | Number of words in the query | Run time
Original 	 500 docs 	 1 words<PHONE_NUMBER>091629ms
Updated 	 500 docs 	 1 words 	 13.642560988664627ms
Original 	 5000 docs 	 1 words 	 34165.26628398895ms
Updated 	 5000 docs 	 1 words<PHONE_NUMBER>147934ms
Original 	 19997 docs 	 1 words<PHONE_NUMBER>2899265ms
Updated 	 19997 docs 	 1 words<PHONE_NUMBER>2440834ms

Original 	 500 docs 	 2 words<PHONE_NUMBER>976501ms
Updated 	 500 docs 	 2 words 	 16.285903990268707ms
Original 	 5000 docs 	 2 words 	 70638.97426700592ms
Updated 	 5000 docs 	 2 words<PHONE_NUMBER>0047112ms
Original 	 19997 docs 	 2 words<PHONE_NUMBER>890016ms
Updated 	 19997 docs 	 2 words<PHONE_NUMBER>1711273ms

Original 	 500 docs 	 3 words<PHONE_NUMBER>753056ms
Updated 	 500 docs 	 3 words 	 13.979169011116028ms

Here's the quick script I threw together to generate that (I cut it off as it was starting to take too long with longer queries):
const BM25 = require("okapibm25").default;
const BM25Test = require("./dist/BM25.js").default;

var assert = require("assert");

const { glob } = require("glob");
const fs = require("fs");

const { performance } = require("node:perf_hooks");

const main = async () => {
  const files = await glob("20_newsgroups/**/*");

  const docs = [];

  for (let file of files) {
    if (fs.lstatSync(file).isDirectory()) {
      continue;
    }
    let data = fs.readFileSync(file, "utf8");

    if (data) {
      docs.push(data.toLowerCase());
    }
  }

  const queries = [
    "Hardware",
    "Encryption algorithms",
    "Performance issues Windows",
    "Baseball World Series results",
    "Comparison Mac PC hardware capabilities",
  ].map((i) => i.toLowerCase().match(/\w+/g));

  for (let query of queries) {
    let start = performance.now();
    let control = BM25(docs.slice(0, 500), query, { k1: 1.3, b: 0.9 });
    console.log(
      `Original \t 500 docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    start = performance.now();
    let test = BM25Test(docs.slice(0, 500), query, { k1: 1.3, b: 0.9 });
    console.log(
      `Updated \t 500 docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    assert(JSON.stringify(control) === JSON.stringify(test));

    start = performance.now();
    control = BM25(docs.slice(0, 5000), query, { k1: 1.3, b: 0.9 });
    console.log(
      `Original \t 5000 docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    start = performance.now();
    test = BM25Test(docs.slice(0, 5000), query, { k1: 1.3, b: 0.9 });
    console.log(
      `Updated \t 5000 docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    assert(JSON.stringify(control) === JSON.stringify(test));

    start = performance.now();
    control = BM25(docs, query, { k1: 1.3, b: 0.9 });
    console.log(
      `Original \t ${docs.length} docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    start = performance.now();
    test = BM25Test(docs, query, { k1: 1.3, b: 0.9 });
    console.log(
      `Updated \t ${docs.length} docs \t ${query.length} words \t ${performance.now() - start}ms`,
    );
    assert(JSON.stringify(control) === JSON.stringify(test));

    console.log();
  }
};

main();

Hey, your changes have now been published. Thank you for your contribution!


Possibility to add Blinds

Hi,
Thank you for your really nice solution. Works like a charm...
Unfortunatly, currently there is no device for Blinds... i use the lock device, but it works not perfektly for blinds...
is there any posibility to add this type of device or is there already a work-a-round?
Thank you
Martin

No, Blinds were added at a later version of the Amazon Smart home spec and it would require a full ground up rewrite of the service to add them, which I just don't have time to do.
You can use lights with the brightness control, with on/off being fully open/closed and brightness % being partial open. But you need to talk to it as if it's a light which is not natural.

Thank you for your reply... i currently use switch command and it works because the Blinds are just have a up/and a down switch. No need for %, but the main issue is to use "on" and "off" for open and close... is there no simple way to just add a 2th kind of switch that supports up and down instead of on/off?
thank you
Martin

No, all the voice processing is done by Amazon. As I said the only way to get support for Blinds is to rewrite the entire service. This is not going to happen


fix(curriculum): Added 15 missing solutions to challenges in the Functional Programming section

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Added working solutions to the following 15 challenge files in the Functional Programming section.  Tested all of them locally and passed when running npm run test:curriculum.

curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/add-elements-to-the-end-of-an-array-using-concat-instead-of-push.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/apply-functional-programming-to-convert-strings-to-url-slugs.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/combine-an-array-into-a-string-using-the-join-method.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/combine-two-arrays-using-the-concat-method.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/implement-map-on-a-prototype.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/implement-the-filter-method-on-a-prototype.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/refactor-global-variables-out-of-functions.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/remove-elements-from-an-array-using-slice-instead-of-splice.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/return-a-sorted-array-without-changing-the-original-array.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/return-part-of-an-array-using-the-slice-method.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/sort-an-array-alphabetically-using-the-sort-method.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/split-a-string-into-an-array-using-the-split-method.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/use-the-every-method-to-check-that-every-element-in-an-array-meets-a-criteria.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/use-the-filter-method-to-extract-data-from-an-array.english.md
curriculum/challenges/english/02-javascript-algorithms-and-data-structures/functional-programming/use-the-some-method-to-check-that-any-elements-in-an-array-meet-a-criteria.english.md

update fps

curriculum/challenges/english/02

curriculum/challenges/english/02

challenges

state.myCommentId

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


[Serialization] Try to load implementation-only dependencies of modules with testing

Implementation-only dependencies may be referenced from internal decls in a module that enabled testing. If that module is imported as testable by a client, the client can access those internal decls that reference transitive dependencies and may need to import them.
It would be project breaking to make those dependencies as required so let's do the next best thing and just try to load them.
rdar://79459263

@swift-ci Please smoke test

I'm putting this up for reference and holding off on merging for now. In theory, this should not influence compilation outside of test targets but in practice it could open the door to leaks.

FYI @bnbarham

@swift-ci Please smoke test Windows

Closing in favor of #64783 which provides a safer, more precise solution to the same problem.


Nothing happens after "connected" after linking metamask account

After the green checkbox ,nothing happens and by entering private key,red  box appears with quotes "something went wrong"

Same issue


!m pl Error

No matter what youtube playlist I link ie !m pl https://www.youtube.com/playlist?list=PLrRtwIUSeaCFFecNtIQ19ZfeksVEpdTwx
The console returns "Error in GetPlaylistId: The remote server returned and error: (400) Bad Request
I am running v0.8 b14.2
It plays all other individual videos just fine. There only seems to be issues with playlists.

That means you didn't setup your google api key properly. Watch the video tutorial and read the comprehensive guide.


Fix codegen to add T of Promise<T> in CodegenSchema.js

Summary
Promise<T> is used very often in turbo module as function return types. So T is a critical thing for type safety. To enable future generator to produce more specific type for Promise, T is added to the schema.
Changelog
[General] [Changed] - Fix codegen to add T of Promise<T> in CodegenSchema.js
Test Plan
yarn jest react-native-codegen passed

I don't know why I can only "Re-request review" for one reviewer, if I click another, the original one will be reset.

I did some internal research on the issue @ZihanChen-MSFT and @christophpurrer.
Internally, we have modules that returns these type of promises:

Promise<string[]>
Promise<Object[]>
Promise<number | null>
Promise
Promise<{ [string]: 'authorized' | 'denied' | 'undetermined' | true | false }>

For the Array, I think we have to support them as proper generic type inside a promise. It make sense to have a function in a module that returns a list of something.
The Promise<number | null> it sounds a lot like an optional. I am not a flow expert, but shouldn't it be Promise<number?>?
The Promise<empty> should be easy to handle. We can just support the EmptyTypeAnnotation. Although, I don't know what it means. Perhaps I can ask the team to replace it with void and see what happens.
Otherwise, the easy way for the last three is to threat the Promise of an unsupported type as Promise<any>, as much as we were doing before. This is probably the most conservative, backward compatible, approach.
What do you think?

@cipolleschi Hi, supporting these types will add a big piece of code, including changing the schema, and I don't think I want to make so many thing into one PR. In order to elegantly supporting A|null|undefined in TypeScript I've made multiple PRs.
Do you think it is acceptable to skip the type if it is not recognized? The previous version didn't check them at all, so by doing this it doesn't make things worse. After that we could add them one by one in future PRs.

/rebase

@ZihanChen-MSFT > thanks for fixing this ;-)
I just stumbled upon the same problem last week. Glad that is getting fixed!

:( We have another type that did not pop up earlier: Promise<AuthorizationStatus>;, where AuthorizationStatus is:
export type AuthorizationStatus = 'authorized' | 'denied' | 'undetermined';

And the error is:
UnsupportedTypeAnnotationParserError: Module NativeTwilightMessenger: Flow type annotation 'StringLiteralTypeAnnotation' is unsupported in NativeModule specs.

Which is a bit weird, because it should have been catched by the latest changes, right?

Which is a bit weird, because it should have been catched by the latest changes, right?

But the type is actually supported, I've tested that in a new submitted test case.

My bad, the error was much subtler than what I understood at first sight.
So, the failing example is something like this:
export type CustomObject = {|
  field1: Array<Object>,
  field2: boolean,
  field3: string,
  type: 'A_String_Literal',
|};

export interface Spec extends TurboModule {
  // ...
  someMethod() => Promise<CustomObject>;
  // ...
}

And it fails when emitting the Promise<CustomObject> because it has a member that is type: 'A_String_Literal'.

@cipolleschi Hi, I add a new test case and fix the issue. I think 'a' should be treated like 'a' | 'b' | ... if it is a valid case, comparing to when we have only one member in an enum.


(module name): Listen to components deployment finish/status event

Hello. We need to listen to Greengrass components deployment finish event in our greengrass component.
Is it possible to get this event from nucleus for example using mqtt or SDK?
I've found only the shadow AWSManagedGreengrassV2Deployment, but this is not exactly what we need.
Thank you in advance

Hi, have you tried using the IPC API for subscribing to notifications about when a deployment is about to be executed and then another notification once it has done executing it?
https://docs.aws.amazon.com/greengrass/v2/developerguide/ipc-component-lifecycle.html#ipc-operation-subscribetocomponentupdates
This probably suits your need but if not, please let us know what additional capability you need

Thanks for your reply. This approach doesn't not seem exactly what we need. We are looking for an approach to track an event, namely the end of all components deployment, as we see in the shadow of AWSManagedGreengrassV2Deployment with the deployment status. Is it possible?
We are looking exactly for this event but from the nucleus side. Thanks

Ticket has not been updated in 7 days. I will close this ticket now since using the component update event is the right way to know that a deployment has been completed on the device side.
Please reopen if needed if you have a response to the previous answer.


add prettier + ensure syntax workflow

Description
This adds a .prettierignore and .prettierrc to enforce consistent formatting across the repository. This will automatically hook into most user's code formatters. You can learn more about Prettier from their docs.
A .github/workflows/formatting.yml file was also added to ensure that formatting was followed. It runs on any PRs.
The files mentioned here were the only ones with actual changes. You can view these changes specifically here. The rest of the modifications are simply formatting changes triggered to adhere to the Prettier configuration.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Passes all unit, integration tests and local testing. Workflow has been tested manually.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

alrighty LGTM

@Tatsinnit I could use your review on this when you get the chance 😄.


Reformat exercise config files

This runs the bin/configlet fmt --update command to
reformat the exercise configs.

cool, will merge.


Add CDK reference page

A brief intro to using the Restate CDK constructs library.

I'm wondering if we shouldn't completely replace https://docs.restate.dev/category/aws-lambda with this method of deploying Lambda handlers! It's so much more streamlined.


[Hub Generated] Publish private branch 'containerservice/official/v20230122'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
Has been deployed to all regions in public cloud on 02/11.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
02/13.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/11119

This is an released pr based on https://github.com/Azure/azure-rest-api-specs-pr/pull/11119, and is approved in API Spec Review process.


Tales of Argosa - update to version 1.1

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

1- "Others" of personal information and Gear row become "Other"
2- Initiative attribute say "INIT" instead of "INI"
3 – The setting are removed as none of them are revelnt anymore in TOA
4 – Fixed the logo link
5 – Updated the official Logos

Character Sheet Info Roll20 Internal Use only.


Disable "check for updates"

Kiota is checking for updates by making a request to https://api.github.com/repos/microsoft/kiota/releases each time a command is started.
I'm working in an offline environment with no Internet access, so this check is useless for me and time consuming because I have to wait for the network timeout in order for Kiota to actually do the work.
How can I disable checking for updates?

Hi @Otiel ,
Thanks for using kiota and for reaching out.
This is not possible today, but we could add an environment variable to support this.
I suggest we name this environment variable "KIOTA_OFFLINE_ENABLED" or something along those lines.
The check for the new version is being done here.
https://github.com/microsoft/kiota/blob/fa26451e3d56ee4f0ebd339dc937d8cc9c14699e/src/kiota/Handlers/BaseKiotaCommandHandler.cs#L100
And you can read the environment variable from the configuration
Lastly, we should add an entry to this table
With all those details in mind, is this something you'd be interested in submitting a pull request for?


feat: Add markdown.nvim integration

Before

After

I used the name render_markdown since there's already a markdown integration, but still tried to clarify in the README that the actual plugin is markdown.nvim.

Maybe markdown_nvim?

The plugin suggests in its README the use of the name render-markdown to avoid collisions with other plugins, the actual package uses the same name and the highlight groups and commands use RenderMarkdown as a prefix, so maybe is ok?

Makes sense


feat: Implementation - back end

Create pull request for app feature to merge with main

How should we go about this? will all of us creating PRs create merge conflict?
in the meantime, I could paste here the R code for my part: https://github.com/gn385x/dsci532-2022-ia1-lgnguyenr/blob/main/app.R


Scroll to newly created searches

Ran into this bug while working on this: http://jsfiddle.net/xegnuh92/
If the new input was focused before it scrolled in, the layout was broken.


Fail in iOS 9: Bitcode

I'm trying to compile my project with this framework in the device, but there is a internal library inside in the project (libfreetds.a) that is not compile to iOS 9. I try to disable bitcode in pods project, but if I do this, the app will crash in the device. Please, recompile all the project with iOS 9.

Until recompile the library in iOS 9, you can use this repository through manual installation. The problem is with the library and the intermediate bitcode in Pods project. I've used the repository with manual installation and it works! =)


Fix typos: NDDE -> NODE, permenantly -> permanently

Fix typos: NDDE -> NODE, permenantly -> permanently

/assign @random-liu

/lgtm
/approve


[nodejs] Add test cases for align and config APIs

Impacted tests: new 26, update 0, delete 0
Unit test platform: Ubuntu 16.04
Unit test result summary: pass 24, fail 0, block 2

@halton please have a review

Add @tingshao for review

@haoyunfeix Why is the examples/package-lock.json file removed? It's not related with this change I think.

I removed package-lock.json file changing from this PR.

LGTM


Feature request: text field for filtering driver in webinterface when changing driver

When using the webinterface and adding a new printer I get a list of ~40 drivers. It would be nice, if above the list there would be a text field, where I can enter a string and the list get reduced to only the driver names that contain the string.

Please report this to the OpenPrinting CUPS project.


Adding hover effect to social media links.

After reviewing the website, I think it will be better to add a small hover effect like turning the icon in blue to help users understand which social media icon to click. Please assign me to this issue I am a Gssoc contributor.

Please assign me this issue as GSSOC 23


Enable zipkin

Release note:

None

@yutongz: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
17756f3337c5974b8471827117c23ea24cd93b54
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yutongz: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
17756f3337c5974b8471827117c23ea24cd93b54
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-no_rbac-no_auth.sh
17756f3337c5974b8471827117c23ea24cd93b54
link
/test e2e-suite-no_rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yutongz: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-no_rbac-no_auth.sh
17756f3337c5974b8471827117c23ea24cd93b54
link
/test e2e-suite-no_rbac-no_auth

prow/e2e-suite-rbac-no_auth.sh
b052e2863b6fb1a73963f26ee74ee5c7a7d0da55
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@yutongz: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-no_rbac-no_auth.sh
17756f3337c5974b8471827117c23ea24cd93b54
link
/test e2e-suite-no_rbac-no_auth

prow/e2e-suite-rbac-no_auth.sh
b052e2863b6fb1a73963f26ee74ee5c7a7d0da55
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yutongz: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
b052e2863b6fb1a73963f26ee74ee5c7a7d0da55
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-no_rbac-no_auth.sh
b052e2863b6fb1a73963f26ee74ee5c7a7d0da55
link
/test e2e-suite-no_rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Remove tags from the ECS cluster (not supported)

Removed the tags from the ECS cluster (again).
Tagging is only possible with the "new ARN format". Which is currently a manual opt-in, and new ECS clusters will get the new format from 1-2-2020 (source).
To prevent people adding the tags again in the future (with good intentions) kept the code but commented, with documentation on why it's disabled.

Merged and tagged (v0.1.5)


fix(list-item): add hover fix

Add hover style for list item. This was accidentally removed while implementing theming.
Description
Related Issue

list item has no hover effect

Screenshots:
Before (If applicable):

After:

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Already fixed by #920


Timesync dependency issue?

On provisining on a new node, I get the following error for the first Puppet run:
Exec[vmwaretools_timesync_disable] (/etc/puppetlabs/puppet/environments/future_371/modules/vmwaretools/manifests/timesync.pp:39)
Property	Message
Could not find command '/usr/bin/vmware-toolbox-cmd'
This clears on the second Puppet run, but is there a dependency there that should be handled in the module? e.g. for exec { "vmwaretools_timesync_${cmd_action}":
require => Class['vmwaretools::install']
If this is okay, I'll submit a pull request.

Thanks for the bug report, I've fixed this in commit 01d1104 - can you retest with these changes?

It looks good - thanks!


SPOS  hardware-aware  nas  multi_trial.py  don't work

Describe the issue:
Environment: ubutu

NNI version:2.4
Training service (local|remote|pai|aml|etc):
Client OS:
Server OS (for remote mode only):
Python version:3.7
PyTorch/TensorFlow version:PyTorch
Is conda/virtualenv/venv used?:conda
Is running in Docker?:

Configuration:

Experiment config (remember to remove secrets!):
Search space:

Log message:

nnimanager.log:
dispatcher.log:
nnictl stdout and stderr:

/opt/conda/envs/pytorch1.9/lib/python3.7/site-packages/deprecate/deprecation.py:115: LightningDeprecationWarning: The Accuracy was deprecated since v1.3.0 in favor of torchmetrics.classification.accuracy.Accuracy. It will be removed in v1.5.0.
stream(template_mgs % msg_args)
Traceback (most recent call last):
File "/opt/conda/envs/pytorch1.9/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/opt/conda/envs/pytorch1.9/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/nni/retiarii/trial_entry.py", line 25, in
engine.trial_execute_graph()
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/nni/retiarii/execution/base.py", line 128, in trial_execute_graph
graph_data.evaluator._execute(model_cls)
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/nni/retiarii/evaluator/pytorch/lightning.py", line 100, in _execute
return self.fit(model_cls)
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/nni/retiarii/evaluator/pytorch/lightning.py", line 128, in fit
self.module.set_model(model)
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/nni/retiarii/evaluator/pytorch/lightning.py", line 37, in set_model
self.model = model()
File "/home/notebook/code/personal/gzh/compression_toolkit/nni_v24/nni/examples/nas/oneshot/spos/_generated_model/G7UFOW.py", line 5580, in init
self.__first_conv = _model__first_conv(input_shape=[[1, 3, 32, 32]], output_shape=[[1, 16, 16, 16]])
TypeError: init() got an unexpected keyword argument 'input_shape'
我找到了G7UFOW.py文件，发现_model__first_conv类的构造函数没有入参（如下），确实有bug：

How to reproduce it?:  just run

Delegate to nn-meter team for support.

Delegate to nn-meter team for support.

Copy that. We will handle it as soon as possible.

Delegate to nn-meter team for support.

Copy that. We will handle it as soon as possible.

@JiahangXu - any updates for this issue? thanks.

Hi GeorgeW9527 and Scarlett, sorry for the late reply. This issue is in the process. The dev branch for nni is https://github.com/JiahangXu/nni/tree/dev-refine-shape-attr and for nn_meter is https://github.com/microsoft/nn-Meter/tree/dev/refine-shape-attr. The PR will be ready in one day.


Fix warnings of IDE/Lint about null check before "instanceof"

I am not sure whether "null" check is the commitment of the project or not before instanceof being used, however, the IDE make warnings really.
If it is commitment, this PR can be ignored.

Thanks for your continued contributions. These files will be converted to Kotlin during this project. So we currently prefer not to touch them until they are translated.


Connection close issue

Server did not shutdown connection when clients went away. This PR resolves the issue.

Could you please rebase on the main branch? Parts of this are already included there.


change return type of doctrine query

the return type of the query is not correct.

Hi, thanks for your PR, I'm goint o close it in favor of #7437 which changes the get*Result() method to a more appropriate one.


Update: UI/UX overhaul for GM GN Wallet

Description

UI and UX improvements through out the wallet for all sections
Improve payment experience
Improve multisend
Improve WalletConnect integration

Reference issue

#261

Category

Other

Approved

Deployment: https://gmgn.app
Repo: https://github.com/gmgn-app/gmgn

Approved for 1500 KAIA

Dorahacks BUIDL


Add extra_rpms field to baremetal config

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold for testing

/approve


Livebook Desktop for Mac icon improvements

[x] #1594
[x] Menu bar icon is low resolution. It should be a template icon too [1] [2]

[ ] app icon is low-resolution in the biggest size:

Fixed in #1932.


libsass: 3.4.8 -> 3.4.9

Semi-automatic update. These checks were performed:

built on NixOS
found 3.4.9 with grep in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9
found 3.4.9 in filename of file in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9

cc "@codyopel @offline"

Success on x86_64-darwin (full log)
Partial log (click to expand)
make[2]: Entering directory '/private/tmp/nix-build-libsass-3.4.9.drv-0/libsass-3.4.9'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/private/tmp/nix-build-libsass-3.4.9.drv-0/libsass-3.4.9'
make[1]: Leaving directory '/private/tmp/nix-build-libsass-3.4.9.drv-0/libsass-3.4.9'
post-installation fixup
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/adv5qxisi0lzc6r1mqaw6kj4f0nkrzi0-libsass-3.4.9/lib
patching script interpreter paths in /nix/store/adv5qxisi0lzc6r1mqaw6kj4f0nkrzi0-libsass-3.4.9
/nix/store/adv5qxisi0lzc6r1mqaw6kj4f0nkrzi0-libsass-3.4.9

Success on x86_64-linux (full log)
Partial log (click to expand)
make[2]: Leaving directory '/tmp/nix-build-libsass-3.4.9.drv-0/libsass-3.4.9'
make[1]: Leaving directory '/tmp/nix-build-libsass-3.4.9.drv-0/libsass-3.4.9'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9
shrinking /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9/lib/libsass.so.0.0.9
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9/lib
patching script interpreter paths in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9
checking for references to /tmp/nix-build-libsass-3.4.9.drv-0 in /nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9...
/nix/store/biismabsawadk87l7m83a62d8cj08iy1-libsass-3.4.9

Success on aarch64-linux (full log)
Partial log (click to expand)
make[2]: Leaving directory '/build/libsass-3.4.9'
make[1]: Leaving directory '/build/libsass-3.4.9'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9
shrinking /nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9/lib/libsass.so.0.0.9
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9/lib
patching script interpreter paths in /nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9
checking for references to /build in /nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9...
/nix/store/pjywngkpyla4hj0dd15mi53vflzfy77b-libsass-3.4.9


test: fix unit-tests

All fixmes resolved

@paolodamico two commented tests look outdated, what to do with them?


pex is inexplicably slow for a small project

Reproduction

Clone https://github.com/zmanji/git-squash
Checkout 505cf06c598409db9d119a521480e43de3fa8908
Run pex . -vv -r requirements.txt --no-build --wheel --no-transitive --inherit-path=false --output-file /Users/zmanji/code/git-squash/dist/git-squash-0.0.1.pex --script git-squash -o dist/out.pex

With latest pex on macOS.
Expectation
Because of --no-build, --wheel, --no-transitive and a fully resolved requirements.txt from pip-compile building a pex should be very fast. The wheels can be fetched from pypi if they are not cached locally, the package it self a single file, so building the wheel should be very fast and then building the pex should be straight forward
For reference building the wheel for git-squash via python ./setup.py bdist_wheel takes about 0.3s on my computer.
Reality
I see this output
pex . -vv -r requirements.txt --no-build --wheel --no-transitive --inherit-path=false --output-file /Users/zmanji/code/git-squash/dist/git-squash-0.0.1.pex --script git-squash -o dist/out.pex
pex: Building pex :: Resolving distributions (['.', 'requirements.txt']) :: Resolving requirements. :: Resolving for:
  DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macpex: Hashing pex                                                                                pex: Hashing pex: 67.4ms
pex: Isolating pex: 0.1ms
pex: Building pex :: Resolving distributions (['.', 'requirements.txt']) :: Resolving requirements. :: Building distributions for:
  BuildRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', pex: Building /Users/zmanji/code/git-squash to /Users/zmanji/.pex/built_wheels/local_projects/git-squash/fa682a73c509acd8bf4e7e52f387f55f3d0b3e6e/cp39-cp39
pex: Building pex :: Resolving distributions (['.', 'requirements.txt']) :: Resolving requirements. :: Calculating project names for direct requirements:
  LocalProjectRequirement(line=LogicalLine(raw_text='.', processed_text='.', source='<string>', start_line=1, end_line=1), path='/Users/zmanji/code/git-squash', extras=(), marker=None, editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='gitdb==4.0.7\n', processed_text='gitdb==4.0.7', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=7, end_line=7), requirement=Requirement.parse('gitdb==4.0.7'), editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='gitpython==3.1.17\n', processed_text='gitpython==3.1.17', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=9, end_line=9), requirement=Requirement.parse('gitpython==3.1.17'), editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='smmap==4.0.0\n', processed_text='smmap==4.0.0', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=11, end_line=11), requirement=Rpex: Building pex :: Resolving distributions (['.', 'requirements.txt']) :: Resolving requirements. :: Installing:
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/GitPython-3.1.17-py3-none-any.whl', fingerprint='59d63e79b53503f5403220d3159d8e409c46e107')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/smmap-4.0.0-py2.py3-none-any.whl', fingerprint='5eb1d8910b7c93de92bd8db25d0a8293b2d1de6f')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/gitdb-4.0.7-py3-none-any.whl', fingerprint='9dacbc989a247dabdad014d6397d8482fd55f26c')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/Users/zmanji/.pex/built_wheels/local_projects/git-squash/fa682a73c509acd8bf4e7e52f387f55f3d0b3e6e/cp39-cp39/git_squash-0.0.1-pex: Using cached installation of GitPython-3.1.17-py3-none-any.whl at /Users/zmanji/.pex/installed_wheels/59d63e79b53503f5403220d3159d8e409c46e107/GitPython-3.1.17-py3-none-any.whl
pex: Using cached installation of smmap-4.0.0-py2.py3-none-any.whl at /Users/zmanji/.pex/installed_wheels/5eb1d8910b7c93de92bd8db25d0a8293b2d1de6f/smmap-4.0.0-py2.py3-none-any.whl
pex: Using cached installation of gitdb-4.0.7-py3-none-any.whl at /Users/zmanji/.pex/installed_wheels/9dacbc989a247dabdad014d6397d8482fd55f26c/gitdb-4.0.7-py3-none-any.whl
pex: Installing /Users/zmanji/.pex/built_wheels/local_projects/git-squash/fa682a73c509acd8bf4e7e52f387f55f3d0b3e6e/cp39-cp39/git_squash-0.0.1-py3-none-any.whl in /Users/zmanji/.pex/installed_wheels/c355002f497d1f36a0bae44b05e55b4338da8a0f/git_squash-0.0.1-py3-none-any.whl
pex: Set entrypoint to console_script 'git_squash.git_squash:main' in git-squash 0.0.1 (/Users/zmanji/.pex/installed_wheels/c355002f497d1f36a0bae44b05e55b4338da8a0f/git_squash-0.0.1-py3-none-any.whl)
pex: Building pex: 13722.4ms
pex:   Resolving distributions (['.', 'requirements.txt']): 13720.7ms
pex:     Resolving requirements.: 13709.1ms
pex:       Resolving for:
  DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))): 6592.5ms
pex:       Building distributions for:
  BuildRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), source_path='/Users/zmanji/code/git-squash', fingerprint='fa682a73c509acd8bf4e7e52f387f55f3d0b3e6e'): 6475.2ms
pex:       Calculating project names for direct requirements:
  LocalProjectRequirement(line=LogicalLine(raw_text='.', processed_text='.', source='<string>', start_line=1, end_line=1), path='/Users/zmanji/code/git-squash', extras=(), marker=None, editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='gitdb==4.0.7\n', processed_text='gitdb==4.0.7', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=7, end_line=7), requirement=Requirement.parse('gitdb==4.0.7'), editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='gitpython==3.1.17\n', processed_text='gitpython==3.1.17', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=9, end_line=9), requirement=Requirement.parse('gitpython==3.1.17'), editable=False)
  PyPIRequirement(line=LogicalLine(raw_text='smmap==4.0.0\n', processed_text='smmap==4.0.0', source='/Users/zmanji/code/git-squash/requirements.txt', start_line=11, end_line=11), requirement=Requirement.parse('smmap==4.0.0'), editable=False): 4.3ms
pex:       Installing:
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/GitPython-3.1.17-py3-none-any.whl', fingerprint='59d63e79b53503f5403220d3159d8e409c46e107')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/smmap-4.0.0-py2.py3-none-any.whl', fingerprint='5eb1d8910b7c93de92bd8db25d0a8293b2d1de6f')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/private/var/folders/1j/9xbcby_57tx1kmn6s8zfsbww0000gn/T/tmpvty3ch2e/Users.zmanji..pyenv.versions.3.9.4.bin.python3.9/gitdb-4.0.7-py3-none-any.whl', fingerprint='9dacbc989a247dabdad014d6397d8482fd55f26c')
  InstallRequest(target=DistributionTarget(interpreter=PythonInterpreter('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', PythonIdentity('/Users/zmanji/.pyenv/versions/3.9.4/bin/python3.9', 'cp39', 'cp39', 'macosx_11_0_x86_64', (3, 9, 4)))), wheel_path='/Users/zmanji/.pex/built_wheels/local_projects/git-squash/fa682a73c509acd8bf4e7e52f387f55f3d0b3e6e/cp39-cp39/git_squash-0.0.1-py3-none-any.whl', fingerprint='c355002f497d1f36a0bae44b05e55b4338da8a0f'): 430.6ms
Saving PEX file to dist/out.pex
pex: Zipping PEX file.: 148.4ms
pex . -vv -r requirements.txt --no-build --wheel --no-transitive    --script   9.65s user 4.27s system 96% cpu 14.348 total

Notice:
pex:     Resolving requirements.: 13709.1ms

This is very unexpected and there is no information in the output as to why it takes so long. With all of the caching PEX uses, I would expect this to be very fast.

Can you run the equivalent pip wheel command and report the timing? Pex fundamentally can't beat Pip without picking back up aspects of resolution it dropped when transitioning to Pip.

Related: #1093

There are the results of comparing pip wheel with pex. I am using hyperfine to produce benchmarks and I believe this is the equivalent pip command.
hyperfine 'pip wheel -w dist/ --only-binary ":all:" -r requirements.txt .'
Benchmark #1: pip wheel -w dist/ --only-binary ":all:" -r requirements.txt .
  Time (mean ± σ):      7.270 s ±  0.259 s    [User: 4.640 s, System: 2.305 s]
  Range (min … max):    6.853 s …  7.648 s    10 runs

vs
hyperfine 'pex . -vv -r requirements.txt --no-build --wheel --no-transitive --inherit-path=false --output-file /Users/zmanji/code/git-squash/dist/git-squash-0.0.1.pex --script git-squash -o dist/out.pex'
Benchmark #1: pex . -vv -r requirements.txt --no-build --wheel --no-transitive --inherit-path=false --output-file /Users/zmanji/code/git-squash/dist/git-squash-0.0.1.pex --script git-squash -o dist/out.pex
  Time (mean ± σ):      9.114 s ±  3.147 s    [User: 5.976 s, System: 2.798 s]
  Range (min … max):    7.327 s … 15.257 s    10 runs

I would expect pex to have minimal to no overhead over pip in cases like this.

Hrm, I find different. My only change was to eliminate some default Pex flags for brevity (--wheel and --inherit-path) and add a missing equivalent flag for pip wheel to be fair to pip (--no-deps):
/tmp $ git clone https://github.com/zmanji/git-squash
Cloning into 'git-squash'...
remote: Enumerating objects: 93, done.
remote: Counting objects: 100% (27/27), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 93 (delta 10), reused 27 (delta 10), pack-reused 66
Receiving objects: 100% (93/93), 11.62 KiB | 11.62 MiB/s, done.
Resolving deltas: 100% (37/37), done.
/tmp $ cd git-squash/
/tmp/git-squash (master) $ git reset --hard 505cf06c598409db9d119a521480e43de3fa8908
HEAD is now at 505cf06 fix
/tmp/git-squash (master) $ python -mvenv tools.venv
/tmp/git-squash (master) $ source tools.venv/bin/activate
(tools.venv) /tmp/git-squash (master) $ pip -q install -U pip
(tools.venv) /tmp/git-squash (master) $ pip -q install -U pex
(tools.venv) /tmp/git-squash (master) $ pip --version
pip 21.1.2 from /tmp/git-squash/tools.venv/lib/python3.9/site-packages/pip (python 3.9)
(tools.venv) /tmp/git-squash (master) $ pex --version
2.1.42
(tools.venv) /tmp/git-squash (master) $ which pip
/tmp/git-squash/tools.venv/bin/pip
(tools.venv) /tmp/git-squash (master) $ which pex
/tmp/git-squash/tools.venv/bin/pex
(tools.venv) /tmp/git-squash (master) $ hyperfine -w2 'tools.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' 'tools.venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'
Benchmark #1: tools.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .
  Time (mean ± σ):      2.826 s ±  0.021 s    [User: 2.450 s, System: 0.259 s]
  Range (min … max):    2.792 s …  2.854 s    10 runs

Benchmark #2: tools.venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash
  Time (mean ± σ):      2.664 s ±  0.029 s    [User: 2.285 s, System: 0.265 s]
  Range (min … max):    2.627 s …  2.710 s    10 runs

Summary
  'tools.venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash' ran
    1.06 ± 0.01 times faster than 'tools.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .'

That result is consistent for me. After 5 runs of that same hyperfine setup I get pex 3%-5% each time. Informally I've found this to be generally true and it makes sense since pip wheel uses no parallelism but pex uses pip download and then runs pip wheel && pip install on each resulting downloaded distribution in parallel. My machine has 8 cores, so by default that backend stage gets that much parallelization.
I'm on a quiet Linux laptop with ssd and that's the only other set of strongly pertinent variables I can think of.

@zmanji if you can't repro my results on a quiet machine I'd like to dig more to understand the performance considerations I'm not taking into account. If you can't repro I'd like to close and let the issues I linked above stand for the case of optimizing pinned resolves / lockfiles.

On a second mac I can see pip and pex are pretty much equal:
 hyperfine -w2 'venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'
Benchmark #1: venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .
  Time (mean ± σ):      5.930 s ±  0.765 s    [User: 3.346 s, System: 1.565 s]
  Range (min … max):    5.253 s …  7.352 s    10 runs

Benchmark #2: venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash
  Time (mean ± σ):      5.652 s ±  0.145 s    [User: 3.502 s, System: 1.697 s]
  Range (min … max):    5.328 s …  5.825 s    10 runs

Summary
  'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash' ran
    1.05 ± 0.14 times faster than 'venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .'

I also thought it was related to this pip issue but deleting the .git directory makes no difference in the above results.
Adding --use-feature=in-tree-build to pip shows:
hyperfine -w2 'venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'
Benchmark #1: venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .
  Time (mean ± σ):      4.342 s ±  0.740 s    [User: 2.800 s, System: 0.600 s]
  Range (min … max):    3.608 s …  5.673 s    10 runs

Benchmark #2: venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash
  Time (mean ± σ):      5.656 s ±  0.166 s    [User: 3.481 s, System: 1.700 s]
  Range (min … max):    5.445 s …  6.034 s    10 runs

Summary
  'venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' ran
    1.30 ± 0.23 times faster than 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'

Feel free to close this.

Some additional data for the record.
It seems that adding a pyproject.toml to the root slows down pip wheel immensely
With the pyproject.toml in the root:
Benchmark #1: venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .
  Time (mean ± σ):      4.726 s ±  0.210 s    [User: 3.801 s, System: 0.681 s]
  Range (min … max):    4.431 s …  5.111 s    10 runs

Benchmark #2: venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash
  Time (mean ± σ):      7.445 s ±  0.266 s    [User: 4.872 s, System: 2.265 s]
  Range (min … max):    7.035 s …  7.790 s    10 runs

Summary
  'venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' ran
    1.58 ± 0.09 times faster than 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'

After deleting pyproject.toml
hyperfine -w2 'venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'
Benchmark #1: venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .
  Time (mean ± σ):      1.218 s ±  0.033 s    [User: 915.5 ms, System: 200.2 ms]
  Range (min … max):    1.189 s …  1.306 s    10 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet PC without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark #2: venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash
  Time (mean ± σ):      3.396 s ±  0.047 s    [User: 1.483 s, System: 1.782 s]
  Range (min … max):    3.348 s …  3.481 s    10 runs

Summary
  'venv/bin/pip wheel --use-feature=in-tree-build -w pip.dist/ --only-binary ":all:" --no-deps -r requirements.txt .' ran
    2.79 ± 0.09 times faster than 'venv/bin/pex . -r requirements.txt --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash'

Reported the above to pip disabling pep517 builds makes this a bit more tolerable for me.

@zmanji that bug report is probably wanting in two ways:

It makes no mention of the important detail of which pep-517 build system you're using. Is it poetry, flit, setuptools ... ?
No significant performance change between --use-pep517 and --no-use-pep517 is a super debatable expectation.

For example, 2 - by design of the PEP - will download the build system (say setuptools) - and then run it. It will not expect the build system to be present in your current interpreters environment. So that hermetic bit of resolving the build system is new and should be expected to take time.

Hrm, I guess it does - but not in too friendly a way: https://github.com/zmanji/git-squash/commit/e714352b532f2fdfc57b23df9b7cf8dc0fed34d6
Looks like setuptools / wheel with no bounds. So latest.

It looks like --use-feature=in-tree-build is available in latest Pip. Pex is stuck back on the last Pip to support Python 2.7 / 3.5, but Pex 3 will drop support for those and move back to latest Pip. At that time we can enable the in-tree-build feature or add a flag to do so.

This issue is rambling a bit, but I'll close as agreed upon.

Hey @jsirois, what's the current status on using in-tree-build?

I've made good progress on the Pip upgrade to latest over in #1805 this week. It looks like Pex will be able to support both the current vendored Pip 20.3.4-patched and be able to download and use Pip 22.2.2 un-patched on the fly behind a flag (currently: --pip-version 22.2.2). I would have likely forgotten about exposing a knob to enable (or default and disable) in-tree-build so thanks for the reminder.

Actually, in-tree-build became the default in 21.3: https://pip.pypa.io/en/stable/news/#v21-3 and the ability to fall back was removed in 22.1b4 https://pip.pypa.io/en/stable/news/#id45, so just by using --pip-version 22.2.2 you'll get this when #1805 ships.
Using Pip 22.2.2 and my branch implementing #1805 on @zmanji's test cases I find:

git-squash HEAD (no pyproject.toml):$ hyperfine -w2 'test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' 'test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' 'test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'
Benchmark 1: test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):     731.7 ms ±  10.8 ms    [User: 512.5 ms, System: 59.7 ms]
  Range (min … max):   723.2 ms … 757.7 ms    10 runs

Benchmark 2: test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):     766.3 ms ±   4.2 ms    [User: 550.7 ms, System: 56.9 ms]
  Range (min … max):   761.7 ms … 776.3 ms    10 runs

Benchmark 3: test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):     850.1 ms ±   5.6 ms    [User: 628.2 ms, System: 63.3 ms]
  Range (min … max):   842.9 ms … 857.8 ms    10 runs

Summary
  'test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' ran
    1.05 ± 0.02 times faster than 'test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'
    1.16 ± 0.02 times faster than 'test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'

git-squash @ 63e53de - just before pyproject.toml deletion:$ hyperfine -w2 'test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' 'test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' 'test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'
Benchmark 1: test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):      1.715 s ±  0.010 s    [User: 1.296 s, System: 0.135 s]
  Range (min … max):    1.701 s …  1.733 s    10 runs

Benchmark 2: test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):      2.179 s ±  0.019 s    [User: 1.752 s, System: 0.126 s]
  Range (min … max):    2.142 s …  2.205 s    10 runs

Benchmark 3: test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/
  Time (mean ± σ):      1.892 s ±  0.019 s    [User: 1.432 s, System: 0.140 s]
  Range (min … max):    1.871 s …  1.934 s    10 runs

Summary
  'test.venv/bin/pip wheel -w pip.dist/ --only-binary ":all:" --no-deps -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/' ran
    1.10 ± 0.01 times faster than 'test.venv/bin/pex --pip-version 22.2.2 --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'
    1.27 ± 0.01 times faster than 'test.venv/bin/pex --no-build --no-transitive -o git-squash-0.0.1.pex -c git-squash -r ~/dev/zmanji/git-squash/requirements.txt ~/dev/zmanji/git-squash/'

So it's a mixed bag, but Pex is always a bit slower. Pex can come out ahead mixing in --no-compress, but that's not a fair fight since there is no such option that I'm aware of to get pip wheel to build an uncompressed wheel.

For the pep517 case could pex ship with a basic wrapper around the pep517 library that creates a venv pex to build the wheel?
It's my understanding the slowest part is building a wheel is creating a clean venv with the dependencies specified in pyproject.toml. pex could just re-use an existing venv in PEX_ROOT

It could take on building wheels, but currently it offloads to Pip all it can (Pex currently uses download for resolve, wheel for building wheels and install for installing wheels - all to be maximally robust and "works like you'd expect" on the premise Pip should always be better at both.). Pex would need to handle both legacy and PEP-517 and the building would potentially be non-uniform, since implicit partial legacy builds (egg-info) get run by Pip to fulfill its dowload command.

The issues to contend with if Pex did tackle wheel building speed optimizations would include what to do about re-use of venvs. There is no way to know just by looking at the top-level [build-system] requires whether anything has changed. Even if all the top-level requirements are pinned, a year later the venv may be stale because some  transitive deps are not pinned. In short, a lock file is needed but this is not PEP'd at all let alone for PEP-518 build systems requirements. See https://peps.python.org/pep-0665/ which actually died due to this very issue!

FWIW the infra does partially exist with an entry point here:
https://github.com/pantsbuild/pex/blob/9cc674b5b45d80338d77a20fe8a3ccaa9c74fa20/pex/build_system/pep_517.py#L60-L65
That is used when locking local projects to get a consistent hashable thing (build an sdist tarball, then extract it to a dir and hash that dir tree) that represents the relevant project contents and not extraneous bits (.pyc laying about, tool caches like .tox/, etc.)
That just supports build_sdist right now but could support building a wheel. It takes a Resolver which support reading lockfiles, but currently doesn't have the plumbing to create a lock file.


Can SWR import resources from the Impact4soil platform?

Impact4soil has recently been introduced, it is a deliverable of the orcasa project. Plans exist within the consortium to let SWR benefit from technology or content of the impact4soil platform. For that reason it needs to be clarified if any constraints (authorization, attribution, embargo) apply to those contributions of the impact4soil platform.
A meeting between the technical teams of both platforms will be scheduled in october 2024, would be good if this issue is clarified before that date.

The impact4soil platform has a number of dedicated api's to extract resources from:

scientific evidence
datasets
organisations
projects
practices