gastraeadae, brachiostrophosis

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,g]

/trunk merge


Why Newtonsoft Json.NET dependency is required?

First of all, I want to say thanks for open sourcing DAPR Sidekick. I am very interested in leveraging it.
One question that I have is related to the Newtonsoft Jason.NET library and understand why this is required. I have used this library a lot in the past but I've found a lot of benchmarks comparing different Json libraries and it seems that it's performance is one the main disadvantages.
Thanks again to all of the MAN Group team members for developing this package.

When we run daprd we pass the parameter --log-as-json so that all log messages emitted by the Dapr sidecar can be easily parsed and re-generated as structured logging methods via the Microsoft.Extensions.Logging framework. We use Newtonsoft.Json purely for this parsing purpose. I agree that for very high-performance scenarios the newer System.Text.Json is much more efficient with far fewer allocations, for what we're doing though I think it's a reasonable choice.

Thanks Simon for your reply!
BTW: I loved your presentation about how MAN Group evolve their platform in the DAPR Community Call.


Error when using CW Agent on KernelApp

Hi all,
I am new to Sagemaker Studio and I was wondering if there is a way to monitor the studio usage, like, how many machines are being used, how much RAM and CPU the users are using. I've seen another repo of examples from notebook-lifecycle-config-examples (https://github.com/aws-samples/amazon-sagemaker-notebook-instance-lifecycle-config-samples) and I saw a very interesting lifecycle configuration: publish-instance-metrics.
I tried to reproduce this notebook-lifecycle-configuration inside studio-lifecycle-configuration, but no success. Here is my studio lifecycle configuration:
#!/bin/bash

set -e

# OVERVIEW
# This script publishes the system-level metrics from the Notebook instance to Cloudwatch.
#
# Note that this script will fail if either condition is not met
#   1. Ensure the Notebook Instance has internet connectivity to fetch the example config
#   2. Ensure the Notebook Instance execution role permissions to cloudwatch:PutMetricData to publish the system-level metrics
#
# https://aws.amazon.com/cloudwatch/pricing/
apt-get update
apt-get -y install jq

# PARAMETERS
NOTEBOOK_INSTANCE_NAME=$(jq '.ResourceName' /opt/ml/metadata/resource-metadata.json --raw-output)

echo "Fetching the CloudWatch agent configuration file."
wget https://raw.githubusercontent.com/aws-samples/amazon-sagemaker-notebook-instance-lifecycle-config-samples/master/scripts/publish-instance-metrics/amazon-cloudwatch-agent.json

sed -i -- "s/MyNotebookInstance/$NOTEBOOK_INSTANCE_NAME/g" amazon-cloudwatch-agent.json

echo "Starting the CloudWatch agent on the Notebook Instance."
/opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -c file://$(pwd)/amazon-cloudwatch-agent.json -s

In order to reproduce and try to understand what happened, I decided to use a terminal tab inside Sagemaker Studio and run the commands one by one and see what happens. The last command gave me the following output:
/opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl: 469: /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl: systemctl: not found
unknown init system

I don't know if there is anything I'm missing, or if it isn't supported yet by sagemaker studio. Can you please help me on this issue?
P.S.: I'm using a Kernel with Python3 and Data Science docker image.

Anyone?

@cabral1888 I have struggled with this recently and it's worth understanding the difference between SageMaker Notebook documentation and SageMaker Studio.
In the AWS docs it's sometimes hard (because they lack clarity) to understand which bit they are talking about.
Anyway the code you mention above is for running in an NoteBook instance not a Studio KernelGateway instance running your notebook. In the KernelGateway there is no init system and you shouldn't try and make one as that kinda breaks the idea of running Docker.
Instead... have a look into running a metric gathering process that's not reliant on an init system and can be spawned into the background e.g.
nohup custom-tool --config /opt/custom-tool/config.conf > /opt/custom-tool/output.log 2>&1 &
For me...I used telegraf with a CloudWatch output plugin


Support Spleeter's 5-stem model, other fixes

Added

Support Spleeter's 5-stem model which separates piano in addition to other accompaniment

Changed

Update separator form UI to use buttons instead of dropdown menus
Improve form field validation
Bring back 'iterations' param for X-UMX model
Update dependencies
Fix Dev Docker Compose config
Fix bug where deleting dynamic mix may cause blank screen

Removed

Remove frontend upload size check and rely on Nginx and backend instead

Wow, you're fast!

I know this is closed but when will there be a "release" with these features?
With the current release, I couldn't find anything in the web interface (docker) for piano (5 stems).

Thanks, I forgot to create a release. The docker compose files aren't pinned to a release so it should still grab the latest, can you pull the latest changes and try again?


ConnectionResetError: [Errno 104] Connection reset by peer

I am receiving an error each time when I try to upload a large stream (not just file):
[2016-08-01 20:13:48,253: ERROR/Worker-4] encountered error while terminating multipart upload; attempting cancel
Traceback (most recent call last):
  File "/opt/mypath/myapp/apps/lib/awsutils/s3stream.py", line 21, in bucket_put_stream
    fout.write(buffer)
  File "/opt/mypath/venv/lib/python3.4/site-packages/smart_open/smart_open_lib.py", line 487, in write
    self.mp.upload_part_from_file(BytesIO(buff), part_num=self.parts + 1)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/multipart.py", line 260, in upload_part_from_file
    query_args=query_args, size=size)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/key.py", line 1293, in set_contents_from_file
    chunked_transfer=chunked_transfer, size=size)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/key.py", line 750, in send_file
    chunked_transfer=chunked_transfer, size=size)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/key.py", line 951, in _send_file_internal
    query_args=query_args
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/connection.py", line 668, in make_request
    retry_handler=retry_handler
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/connection.py", line 1071, in make_request
    retry_handler=retry_handler)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/connection.py", line 1030, in _mexe
    raise ex
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/connection.py", line 940, in _mexe
    request.body, request.headers)
  File "/opt/mypath/venv/lib/python3.4/site-packages/boto/s3/key.py", line 844, in sender
    http_conn.send(chunk)
  File "/usr/lib/python3.4/http/client.py", line 888, in send
    self.sock.sendall(data)
  File "/usr/lib/python3.4/ssl.py", line 741, in sendall
    v = self.send(data[count:])
  File "/usr/lib/python3.4/ssl.py", line 702, in send
    v = self._sslobj.write(data)
ConnectionResetError: [Errno 104] Connection reset by peer

The error is thrown by boto, so the issue might be related to https://github.com/boto/boto/issues/2207 . I tried all workarounds, but no luck.
My code looks like this:
def bucket_put_stream(stream, bucket, key):
    awskey = AWS_SETTINGS['AWS']['ACCESS_KEY_ID']
    awssecret = AWS_SETTINGS['AWS']['SECRET_ACCESS_KEY']
    size = 0
    with smart_open.smart_open('s3://%s:%s@%s/%s' % (awskey, awssecret, bucket, key), 'wb') as fout:
        for data in stream:
            fout.write(data)
            size += len(data)
    return size

Small file of 17Kb was uploaded without issues, so the problem shouldn't be in permissions.

Hmm, it seems the issue went away after some time.
I can recommend this SO answer: http://stackoverflow.com/a/23397672/494631
It seems 'training' S3 does make sense. I cannot explain it otherwise.

Thanks for reporting it. Closing it as "can't reproduce".

@ba1dr u probably exceeded maximum number of parts allowed on multipart upload


steam: Add python3 to runtime for steam play / proton

Motivation for this change
Proton stable added python3 as a hard dependency (can't find any official statements but games crashed with a file not found notice and it's mentioned on multiple places in the official issue tracker.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

To add, Steam Play 3.7-3 depends on python2 and still works. Steam Play 3.7-5 (intentionally) depends on python3 and therefore doesn't work.

Can you clarify whether this has any impact on users that don't participate in the Steam Play beta?

It adds a dependency, but other than that, no.
Also the steam play beta just got expanded to the stable steam client, so everybody is participating in a way.
On 1 September 2018 09:58:33 CEST, Sarah Brofeldt<EMAIL_ADDRESS>wrote:

Can you clarify whether this has any impact on users that don't
participate in the Steam Play beta?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/45855#issuecomment-417841237

@pstn Thanks!


Update @shopify/connect-wallet Storybook Playground

Description
The Storybook demo / playground for the connect-wallet package is currently styled in a way that prevents the full modal from being displayed in smaller environments.
Example
Demo

This is resolved now after an update to .dev saw an increase in the embedded frame's height.


Use fugit

This first started with me trying to implement rtc for this crate by stealing it from stm32g0xx-hal. I noticed there were some differences.
This PR changes the time related types to use fugit to make the crate a bit more consistent with stm32g0xx-hal.
Is this at all something we want?
~(Not at all tested on real hardware yet)~ - Some testing done

Any thoughts on this? Is this something that is wanted or should I close this PR?
Also please let me know if you want me to change anything :)

Thanks a lot :) @no111u3


first read suggestions

ADDITIONAL COMMENTS ON MODULES 1 & 2
Module 1

No global.json, not shown in picture either  (found out it's not included in the solution but it's in the root directory)
Ex 2 Task 3: You don't need to mess with the UI to open the folder. Just run "code ." from the command line

Module 2

Last step: following these instructions, the facebook login is going to fail. Instruction shows to use an https website URL but SSL is not even enabled on the web app. If you enable SSL and use the https://localhost:port for it, you get an error saying mismatch of return URL, and I couldn't figure out how to get around it. The only one that I found to work is the non-SSL address (http://localhost:port). Whether this is a good story or not, it's better to call it out so customers don't get bothered.


Differentiate documentation and non-documentation comment syntax

Consider giving documentation comments a dedicated syntax. The syntax that I currently favor is ## for doc-comments.
Pros:

Prevent comments that aren't intended as doc-comments from being picked up in recipe descriptions.
Make it possible to write comments about recipes that aren't doc comments.
Allow users to write multi-line doc-comments but only use the first line in --list output. (See below for an example.)
Can emit an error if doc-comments aren't used correctly.
Slightly simplify the parser.

Cons:

Users would have to change existing doc-comments to use the new syntax.
If using a doc-comment where none is expected is an error, then this will be a breaking change. The more pre-existing use of the new doc-comment syntax there is (e.g. for styling purposes), the more disruptive this change will be. ## is used by around 1% of justfiles that I've scraped from GitHub. (This doesn't count ###, since we can ignore comments that start with ### to make it a less disruptive change.) Options like #: would be less disruptive, but weirder.

If I did this, I would first make Just strip additional #s from existing doc-comments. This would make it so there would be a period where # and ## comments would work, to make the change less disruptive. (If this wasn't done, then you would see build # # description if you tried to use ## doc-comments.)
I'm still on the fence about this change. I think it would be nice, and if I was writing Just from scratch I would certainly do it from the beginning. However, I'm unsure if it's worth it, given that there are many Justfiles out there.
This could be given a phased roll-out:

Make it so ## comments work without an additional # appearing in --list output
Warn if a # comment is picked up as a doc-comment
Stop showing # as doc-comments

Multi-line doc-comment example
## Build the project
## More detail about what this command does.
build:
  ./build

$ just --list
Available recipes:
    build # Build the project

Although it might be mistaken for user styling, I think out of those I like ## the best. It's easy to type, it's similar to doc comments in other languages (in the sense that doc comment syntax is often normal syntax with one character duplicated, and it's used by at least one other language.

This would be great to support https://github.com/casey/just/issues/553. Being able to say in a doc string "I'm going to build X and put it in location (configurable via e.g. .env) Y" would add so much power to concise documentation.

@dionjwa Great point! Adding dedicated doc-comment syntax would allow for introducing new features.

I think that using ## would be very disruptive, just given the proportion of justfiles that use ## for styling, so I think ## is out.

What about @# for "hidden" documentation? This matches the existing way I add comments I don't want automatically printed out:
command:
    @# a comment that is NOT echo'd to stdout
    # This comment is echo'd to stdout
    ls

Actually, now that I write this, I would favour that # should be hidden comments, and @# should be explicit command doc strings. Writing internal comments should have smallest writing overhead, whereas command doc strings are more "special".

There is now a [doc] attribute which can be used to give recipes multi-line doc comments, or used with no argument to prevent a leading comment from being used as the recipe's doc comment.


calling FindConversation with an IndexedPageItemView causes 500 error

When we pass an IndexedPageItemView to FindConversation, server responds with 500 error – "The request failed schema validation.".
Steps to reproduce:

make a FindConversation request, and be sure to include the IndexedPageItemView object.

eg:
ews.run("FindConversation", {
        attributes: {
            Traversal: "Deep"
        },
        IndexedPageItemView: {
            Offset: "10",
            BasePoint: "Beginning"
        },
        ParentFolderId: {
            DistinguishedFolderId: {
                attributes: {
                    Id: "root"
                }
            }
        },
        QueryString: "asdf"
    }, ewsSoapHeader);

Full error is:
Potentially unhandled rejection [5] Error: a:ErrorSchemaValidation: The request failed schema validation: The prefix 'ns1' is not defined. Line 1, position 480.
    at finish (/Users/zach.arend/Desktop/ews-sandbox/node_modules/soap/lib/wsdl.js:1488:21)
    at WSDL.xmlToObject (/Users/zach.arend/Desktop/ews-sandbox/node_modules/soap/lib/wsdl.js:1471:10)
    at parseSync (/Users/zach.arend/Desktop/ews-sandbox/node_modules/soap/lib/client.js:353:23)
    at /Users/zach.arend/Desktop/ews-sandbox/node_modules/soap/lib/client.js:346:14
    at Request._callback (/Users/zach.arend/Desktop/ews-sandbox/node_modules/soap/lib/http.js:118:5)
    at Request.self.callback (/Users/zach.arend/Desktop/ews-sandbox/node_modules/request/request.js:186:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/Users/zach.arend/Desktop/ews-sandbox/node_modules/request/request.js:1081:10)
    at emitOne (events.js:96:13)

Edit: add full error and take out irrelevant property order info.

@nmarus any thoughts on this? I've tried using highsource/jsonix but it doesn't work and I keep getting "Element [" + elementValue.name.key + "] is not known in this context, could not determine its type."

I think I've run into this before, try changing "ConversationShape" to "t:ConversationShape" and see if that makes a difference. Also, is "The request failed schema validation." the full response message? It should tell you which message or type element is the offending party.

I tried changing to "t:ConversationShape" and got the same result. Here's the full error:

I think this is something to do with the "xs:choice" because FindItem crashes if I pass it an IndexedPageItemView and FindFolder crashes if I pass it an IndexedPageFolderView

This worked for me:
var EWS = require('node-ews'),
	util = require('util');

var config = {
		ews:{
			username:'MY_USERNAME',
			password:'MY_PASSWORD',
			host:'MY_EXCHANGE_SERVER_URL',
			options:{
			//  rejectUnauthorized: false,
			//  strictSSL: false,
				workstation: 'MY_WORKSTATION_NAME',
				domain: 'MY_DOMAIN'
			},
			soapHeaders:{
			  't:RequestServerVersion': {
				attributes: {
				  Version: "Exchange2013"
				}
			  }
			}
		}
	};

var ews = new EWS(config.ews.username, config.ews.password, config.ews.host,config.ews.options);

ews.run("FindConversation", {
        attributes: {
            Traversal: "Deep"
        },
        IndexedPageItemView: {
            attributes:{
				"Offset": "10",
				"BasePoint": "Beginning"
			}
        },
        ParentFolderId: {
            DistinguishedFolderId: {
                attributes: {
                    Id: "root"
                }
            }
        },
        QueryString: "asdf"
    }, config.ews.soapHeaders)
.then(response => {
	console.log("Response:",util.inspect(response,true,6,true));
});

I think it has something to do with the headers that I'm using. It was long enough ago that I don't remember why specifically I added the RequestServerVersion but I seem to recall it was due to a validation issue. If I try to run the request without the headers I get:
Potentially unhandled rejection [5] Error: a:ErrorSchemaValidation: The request failed schema validation: Could not find schema information for the element 'http://schemas.microsoft.com/exchange/services/2006/messages:IndexedPageItemView'.
    at WSDL.xmlToObject (C:\exchanger\node_modules\node-ews\node_modules\soap\lib\wsdl.js:1467:19)
    at C:\exchanger\node_modules\node-ews\node_modules\soap\lib\client.js:297:25
    at C:\exchanger\node_modules\node-ews\lib\http.js:47:9
    at finalCallback (C:\exchanger\node_modules\httpreq\lib\httpreq.js:98:7)
    at IncomingMessage.<anonymous> (C:\exchanger\node_modules\httpreq\lib\httpreq.js:376:9)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Thank you, @kcastrotech. Your example worked for me.
The problem was that I did this:
// incorrect
IndexedPageItemView: {
  Offset: "10",
  BasePoint: "Beginning"
}

instead of this:
// correct
IndexedPageItemView: {
  attributes: {
    Offset: "10",
    BasePoint: "Beginning"
  }
}

:man_facepalming:
Thank you for your help, I really appreciate it. I think we can close this issue as "user error".

Glad it was something so simple.


Fix "Build docs" CI job by temporarily pinning alabaster to 0.7.13

As of alabaster-0.7.14 the alabaster theme package requires sphinx 3.4
which conflicts with the current sphinx requirement.
As a quick fix we pin to alabaster-0.7.13 here.
Temporary workaround for #6400

cc: @tanujkhattar @smburdick


adding more details on CSP

adding more details on content security policy for widgets.
This document will be the start of widget's CSP document, following other widget list on the epic:
https://mendix.atlassian.net/browse/WC-2304
Background:
By default, CSP for "self" is sufficient (as mentioned on current CSP policy document
but some widget need access to 3rd party domain (such as map widget), which heavily dependent on the provider.
this document will give overview to that domain access request as part of CSP compliance requirements.

Other widget CSP document (as mentioned in the jira epic) will follow after this one being merged and published.
thus, we want to make sure first that this is a correct structure, place, and format for widget CSP document.
@ConnorLand

@grand

Other widget CSP document (as mentioned in the jira epic) will follow after this one being merged and published. thus, we want to make sure first that this is a correct structure, place, and format for widget CSP document. @ConnorLand

I think this is a good structure for CSP material. Is all the draft material submitted for this round? If so, I can get to work editing things.

@grand

Other widget CSP document (as mentioned in the jira epic) will follow after this one being merged and published. thus, we want to make sure first that this is a correct structure, place, and format for widget CSP document. @ConnorLand

I think this is a good structure for CSP material. Is all the draft material submitted for this round? If so, I can get to work editing things.

Yes, please continue


Dynamic cutoff for Low Cut Filter

currently the low cut filter is at a constant cutoff. we should revise it to dynamically determine the cutoff based on when dx of fourier becomes positive (this is how the old "peak at" worked - it found the x with highest y in fourier graph where x > [where dx is first positive])
this would fix low cut filter masking stupid low scanrates below 60hz

just needs a reimpl here
https://github.com/mat1jaczyyy/Keyboard-Inspector/blob/60901cba6e7aeba05a341ea1c5f25d711607cd31/Keyboard Inspector/Result/Analysis.cs?plain=1#L145C1-L147C66


[BEAM-9026] Avoid side effects from positional value provider arguments.

This doesn't address the root cause of this issue, which is that value provider arguments are still leaking into unrelated tests.
R: @udim @tvalentyn

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Looks like a good workaround. I also commented on the bug


Define TypeScript guidelines

Part of TS migration issues.

Create the first version of the guideline in app/contributingGuides/TYPESCRIPT_STYLE.md.
A rough overview of the guideline is in the design doc.
Add succinct code examples as needed.
Create sub-files if necessary to divide the guideline into sections.
While writing the guideline, if you encounter any unclear points that should be discussed, post them on the #typescript-new-expensify channel.

The new guideline is developed in this google doc

@hayata-suenaga The PR is ready to review!

@fabioh8010 thank you so much for this PR 🎉 I'll take a look at this tomorrow

the PR is still being worked on and review is still going on

The PR is actively reviewed and worked on 👍

https://expensify.slack.com/archives/C03TQ48KC/p1689011336554509

The PR has been merged. closing this


Warning: Failed prop type: Invalid prop labels supplied to VictoryScatter.

Bugs and Questions
Checklist

[x] This is a victory-native specific issue. (Issues that also appear in victory should be opened here)

[x] I have read through the FAQ and Guides before asking a question

[x] I am using the latest version of victory-native

[x] I have checked to make sure that my versions of react-native and react-native-svg are compatible with this version of victory-native. Read about version requirements

[x] I've searched open issues to make sure I'm not opening a duplicate issue

The Problem
Whenever I set labels props on the <VictoryScatter> component I get a warning in my expo:
Warning: Failed prop type: Invalid prop labels supplied to VictoryScatter
However, I can that the label is shown and I can see such props in the docos.
My code:
<VictoryChart domain={{ x: [0, 1], y: [0, 1.2] }}>
        <VictoryAxis
          orientation="left"
          label="# people"
          tickValues={[0]}
          tickLabelComponent={<VictoryLabel dx={-100} />}
        />
        <VictoryAxis
          orientation="bottom"
          tickValues={[0]}
          tickLabelComponent={<VictoryLabel dx={-100} />}
        />
        <VictoryLine
          y={(d) => Math.sin(Math.PI * d.x)}
          style={{ data: { stroke: 'red' } }}
        />
        <VictoryScatter
          style={{ data: { fill: '#c43a31' } }}
          size={6}
          data={[{ x: 0.7, y: 0.8 }]}
          labelComponent={<VictoryLabel dy={-10} dx={24} />}
          labels="Your label"
        />
      </VictoryChart>

Result:

OK, I figured that it should be the array and I need to use labels={['Your label']} instead


Enabling issues on charts repo

Sorry to open this issue in this repo but i didn't know how to contact you otherwise.
I'd like to open an issue on your fork of charts but it seems issues are disabled for that repo. Could you please enable them?

Sure, done :)

Btw not sure why it was not opened, maybe github auto disable them for forked repo?

I think it copies the settings from the original repo, no?

I don't know indeed, anyway that's not a problem :)


fix some public download data bits

should fix #94

[x] pytest works
[x] toy config from public computer repo folder works
[x] esco config from public computer repo folder works
[x] toy config from public computer pip install
[x] esco config from public computer pip install

Running on a public computer
You will need to install the aws and unzip command line tools to download the data this way.
pip installation
pip install ojd_daps_skills@git+https://github.com/nestauk/ojd_daps_skills@fix-download-public-data#egg=ojd_daps_skills
python -m spacy download en_core_web_sm

In python
from ojd_daps_skills.pipeline.extract_skills.extract_skills import ExtractSkills

es = ExtractSkills(config_name="extract_skills_toy", local=True)

es.load()

job_adverts = [
        "You will need to have good communication and excellent mathematics skills. You will have experience in the IT sector.",
        "You will need to have good excel and presenting skills. You need good excel software skills",
    ]

predicted_skills = es.get_skills(job_adverts)
job_skills_matched = es.map_skills(predicted_skills)

Usage from repo
Running the code from the repo folder.
mkdir .cookiecutter/state
touch .cookiecutter/state/conda-create.log
make install
conda activate ojd_daps_skills
python -m spacy download en_core_web_sm

Then in python:
from ojd_daps_skills.pipeline.extract_skills.extract_skills import ExtractSkills

es = ExtractSkills(config_name="extract_skills_toy", local=True)

es.load()

job_adverts = [
        "You will need to have good communication and excellent mathematics skills. You will have experience in the IT sector.",
        "You will need to have good excel and presenting skills. You need good excel software skills",
    ]

predicted_skills = es.get_skills(job_adverts)
job_skills_matched = es.map_skills(predicted_skills)

Checklist:

[ ] I have refactored my code out from notebooks/
[ ] I have checked the code runs
[ ] I have tested the code
[ ] I have run pre-commit and addressed any issues not automatically fixed
[ ] I have merged any new changes from dev
[ ] I have documented the code

[ ] Major functions have docstrings
[ ] Appropriate information has been added to READMEs

[ ] I have explained the feature in this PR or (better) in output/reports/
[ ] I have requested a code review

Looks good! I have some fears about boto3 / selenium (for the altair graphs) / fsspec compatibility because we had some requirements issues in the ai_genomics project but we haven't come across it here so maybe i'm just afraid for no reason

hmm..good point.. well lets fix that when/if it breaks I suppose :/


Edge fails to connect to test runner when vpn connection is open

On my local Windows 10 machine, Edge fails to connect to the TestCafe tests proxy/platform when I'm connected to my work VPN. That VPN needs to be active for testing, due to application authentication.
My tests work fine on Chrome and Firefox.

I connect to the VPN
I started my tests with $ testcafe edge "test/e2e/**/*.spec.js"
Edge opens to http://<IP_ADDRESS>:56680/browser/connect/fDl~1T1
Edge shows an error page "Hmmm...can’t reach this page"

Try this
Make sure you’ve got the right web address: http://<IP_ADDRESS>:56680
Search for "http://<IP_ADDRESS>:56680" on Bing

I've tried specifying a hostname in .testcaferc.json of <IP_ADDRESS> but that didn't have any effect.
Your Environment details:

testcafe version:                   1.1.0
node.js version:                    v11.9.0
command-line arguments:  $ testcafe edge "test/e2e/**/*.spec.js"
browser name and version: Microsoft Edge 44.17763.1.0
platform and version:          Windows 10 x64

It looks like MS Edge has a problem with the VPN connection. Please try to install and run http-server with the following commands:
npm i - g http-server
http-server

After http-server starts, try to open http://<IP_ADDRESS>:8080 in MS Edge.

I've tried specifying a hostname in .testcaferc.json of <IP_ADDRESS> but that didn't have any effect.

Do you mean that MS Edge showed the  http://<IP_ADDRESS> url after you specified <IP_ADDRESS> in the config file? Have you tried to use the --hostname CLI switch or specify localhost as a hostname?

You're right, I suspect Edge is somehow failing without testcafe involved.
Trying http-server, and Edge fails to connect to it while Chrome works fine.

Just noting in case anyone has this issue: My VPN was configured without IPv6 support. Enabling that allowed Edge and IE11 to work.


FR: Provide a way to dynamically enable/disable Screen Reporting

Feature proposal

Firebase Component: Analytics

Right now you can only either enable screen reporting or disable it completely via FirebaseScreenReportingEnabled in app's .plist.
In our case, some clients don't want the data to be sent to 3rd parties. Others are ok with it.
We would like to keep the screen reporting for those clients who are ok with it.
However, clients can sign in/sign out without quitting the app. Therefore runtime enabling/disabling Screen Reporting policy change is required.
If you try to set the screen name while FirebaseScreenReportingEnabled is NO, it doesn't work:
6.26.0 - [Firebase/Analytics][I-ACS031000] Ignoring call to setScreenName:screenClass:. Screen reporting is disabled.

I've done more tests and it looks like if we keep FirebaseScreenReportingEnabled = YES, then we can control the actual sending of data by setting:
Analytics.setAnalyticsCollectionEnabled(true/false)
FirebaseApp.app()?.isDataCollectionDefaultEnabled = true/false

is that right?
Like if we set FirebaseScreenReportingEnabled = YES and then call
Analytics.setAnalyticsCollectionEnabled(false)
FirebaseApp.app()?.isDataCollectionDefaultEnabled = false

we can still see log statements like
6.26.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: LoginViewController,<PHONE_NUMBER>790172807.
But in Firebase DebugView, the screen_view events are no longer reported.
Could somebody, please, confirm that in that case Screen View events are not reported to Firebase servers?
Thanks!

We're working on a more selective screen reporting API that may met your needs. The workaround you listed is not recommended since it will stop all analytics events from sending (including screen recording events).

@morganchen12 Thank you for information!
It happens that stopping all analytics events dynamically is exactly what we need, so I think that should work for us. Closing the issue.


Accept addons that timeout in validation (bug 1185022)

This should pull in https://github.com/mozilla/amo-validator/pull/323 also.

This needs a rebase, but looks good to me, thanks!
@kmaglione could you please have a look too?

r+


mj-social-element appending unnecessary text to href

Describe the bug
For Twitter, Facebook, and LinkedIn some unncessary text from each, is appended to the href.
Twitter: "https://twitter.com/home?status="
Facebook: "https://www.facebook.com/sharer/sharer.php?u="
LinkedIn: "https://www.linkedin.com/shareArticle?mini=true&url="
These are the only 3 I am using in this situation, so other social-element's may have them too.
They appear as though they are set to "share" somehow, but I would like to just add an href url of my own choosing, which makes more sense.
To Reproduce
Steps to reproduce the behavior:

Use 'mj-social-element'
Render to HTML
See links for social-elements

Expected behavior
href should be the URL I enter, and not append another URL
MJML environment (please complete the following information):

OS: Windows 10
MJML Version 4.2.0 (4.3.0)
MJML tool used VS Code extension and online editor

Email sending environment(for rendering issues):
N/A
Affected email clients (for rendering issues):
N/A
Screenshots
N/A
Additional context
N/A

It's the intended behavior 👍
Cf the documentation :
Supported networks with a share url:
- facebook
- twitter
- google
- pinterest
- linkedin
- tumblr
- xing

Without a share url:
- github
- instagram
- web
- snapchat
- youtube
- vimeo
- medium
- soundcloud
- dribbble

When using a network with share url, the href attribute will be inserted in the share url (i.e. https://www.facebook.com/sharer/sharer.php?u=[[URL]]). To keep your href unchanged, add -noshare to the network name. Example :

<mj-social-element name="twitter-noshare" href="my-unchanged-url">Twitter</mj-social-element>

@iRyusa Apologies for not seeing this in the docs! Thank you so much for taking the time to answer. I am loving MJML, btw!


Encoding issues on Windows

[x] Add a PowerShell task that prints the character 'ç'.
Fixed by https://github.com/Microsoft/vsts-agent/pull/378
[ ] Garbled output in Copy Files task on ja-JP/ko-KR/zh-CN/zh-TW
Regressed by https://github.com/Microsoft/vsts-agent/pull/378
I'm working to find a solution that works everywhere.

It appears node.exe outputs UTF8 when not in TTY mode. The fix is:

Modify ProcessInvoker to accept an encoding to use when interpreting STDOUT/STDERR of the invoked process.
Modify NodeHandler to pass System.Text.Encoding.UTF8 to ProcessInvoker.


Implement new media auth proposals (MSC3916 & MSC3911)

Auth: https://github.com/matrix-org/matrix-spec-proposals/pull/3916
Association: https://github.com/matrix-org/matrix-spec-proposals/pull/3911
Replaces https://github.com/turt2live/matrix-media-repo/issues/266
Replaces https://github.com/turt2live/matrix-media-repo/issues/103
For https://github.com/turt2live/matrix-media-repo/issues/31
For https://github.com/turt2live/matrix-media-repo/issues/36

MSC3916 is implemented via https://github.com/t2bot/matrix-media-repo/pull/509


Bugfix/schema and timeout

Fixes "List out of Index" showing up when redis is empty and schema graph computed is also empty

SELECT a:gene->b:disease
FROM "/schema"
WHERE a="curie:ismissing"

Fix makes  behavior  return an empty response with the query graph evaluated from the query.

Adds timeouts to queries this is configurable as per deployment via
"REDIS_QUERY_TIMEOUT" env variable. And value is in milliseconds.

Adds get parameter for /schema endpoint so we can do force refresh through an api call. Could be useful when roger pipeline finishes building graph we can let tranql recompute the schema. And don't need to wait till the next update interval.

Hi @waTeim , thanks for the review. Just added a default to options as empty dict.
WRT schema computation, the main reason for re-doing the schema is i think when graph has changed in redisgraph.

One of the ways we can detect this change maybe using counts of nodes and edges per type maybe.
Something like

grab node types and counts for each,
grab edge types and counts for each,
make a hash value
if hash value is diff from previous one recalc schema

Another way maybe having a meta node in the graph , that the roger pipeline would write out , something with version and time graph was build. That way we can check if this node has changed.

A third option is increasing interval that we do this calc. This wouldn't change the efficiency but would reduce the frequency of making schema calc cypher query calls to redisgraph.  Since we have the api endpoint to force update the schema, we can make http request to that endpoint. In this scenario , roger pipeline on airflow would build the graph and make a force_update schema call to tranql once the graph has done building.

@YaphetKG - please let me know when this is tested in heal-dev - i.e. ensuring search/indexing/etc is working as expected.


Lazy initialValues

🚀 Feature request
Current Behavior
The initialValues prop passed in to Formik must be evaluated on every re-render, even though it's typically only necessary on the first render.
Desired Behavior
A lazy way to specify initialValues would be excellent.
Suggested Solution
A getInitialValues() prop would solve this problem for us.
Who does this impact? Who is this for?
This should improve performance for any app where computing initialValues is relatively expensive.
Describe alternatives you've considered
We currently compute & memoize the value of initialValues at the start of the app, but this is not ideal.
Additional context
The initial values for our form state is derived from query params on the URL, which are expensive to access and parse on each render.

Closing due to long inactivity


methods for FlatList, ScrollView, SectionList, VirtualizedList and Vi…

closes #604
These components are interrelated in the sense of being based on each other and inheriting props, however, applicable methods are not inherited quite so consistently.
This PR removes unavailable methods from each component.

I have added scrollToLocation that was missing from SectionList and removed all unavailable methods from these components.
However, there are still a few other methods that I will add later.

Later like in another PR? :)
Should we merge this one?

In a later PR, merging this one now.


Viewing in browser works, requesting results in 500

"I swear I had this working just a minute ago"

I was trying this thing out and it all seemed to work, but somehow i turned a 200 response into a 500.
const tickers = ['NVDA', 'MMM'];

fetch(`http://<IP_ADDRESS>:8888/https://www.google.com/finance/info?q=${tickers.join(',')}`)
  .then(res => res.text())
  .then((text) => {
    console.log(JSON.parse(text.substring(3).trim()));
  });

The previous snippet does some weird-ass parsing, the one below proves my point without irrelevant errors:
const tickers = ['NVDA'];

fetch(`http://<IP_ADDRESS>:8888/https://www.google.com/finance/info?q=${tickers.join(',')}`)
  .then((res) => {
    console.debug(res);
  });

Visiting http://<IP_ADDRESS>:8888/https://www.google.com/finance/info?q=NVDA works as expected.
Am I missing something somewhere else? I wouldn't be posting here if it hadn't worked, but in a few minutes difference something broke.
Just in case, here is my cors.js
const corsProxy = require('cors-anywhere');

const host = '<IP_ADDRESS>';
const port = 8888;

corsProxy.createServer({
  originWhitelist: [],
}).listen(port, host, () => {
  console.log(`Running CORS Anywhere on ${host}:${port}`);
});

Also, sorry if this is irrelevant to the module, I'm just not sure :-(

I cannot reproduce this problem. The server does not generate 500 on its own (only when the help file is missing, see https://github.com/Rob--W/cors-anywhere/blob/97c6e53020da622b006842ef112bc721cac0c47d/lib/cors-anywhere.js), so this has something to do with the resource that you're trying to proxy (i.e. Google Finance).
Is the request aborted, or does it complete with status code 500?

It completes with 500, returns me HTML with the classic Google's There was an error. Please try again later. That’s all we know..
This is what I used for the server, I don't think i fiddled with that at all in the process:
const corsProxy = require('cors-anywhere');

const host = '<IP_ADDRESS>';
const port = 8888;

corsProxy.createServer({
  originWhitelist: [],
}).listen(port, host, () => {
  console.log(`Running CORS Anywhere on ${host}:${port}`);
});

The Allow-Control-Allow-Origin: * Chrome extension does work for this so I will evacuate from the situation since I need this only locally anyway.


copied changelog to top level

This makes the changelog more visible.
For now I just copied the content of the "change-notes" tag in src/META-INF/plugins.
It would be nice if adding to the changelog could be automated for the next releases based on the git history.
We can discuss what are the usual process to get to this point.

Maybe we can use something like this to generate changelog
http://stackoverflow.com/questions/3523534/good-ways-to-manage-a-changelog-using-git

http://skywinder.github.io/Github-Changelog-Generator/
Looks nice

Yes, I like the output of this project too.
If we use this tool, it would be nice to figure a way to update
CHANGELOG.md and the changelog in plugin.xml automatically.
2015-03-13 11:17 GMT-07:00 as3boyan<EMAIL_ADDRESS>
http://skywinder.github.io/Github-Changelog-Generator/
Looks nice
—
Reply to this email directly or view it on GitHub
https://github.com/TiVo/intellij-haxe/pull/143#issuecomment-79210641.


sum(skipna=True) doesn't handle NAs as per docs

Code Sample, a copy-pastable example if possible
In [50]: df
Out[50]:
    a   b   c
0 NaN NaN NaN
1   1   1   1
2   1 NaN NaN

In [51]: df['total'] = df[['a', 'b', 'c']].sum(axis=1, skipna=True)

In [52]: df
Out[52]:
    a   b   c  total
0 NaN NaN NaN      0
1   1   1   1      3
2   1 NaN NaN      1

In [53]:

Expected Output
In [51]: df['total'] = df[['a', 'b', 'c']].sum(axis=1, skipna=True)

In [52]: df
Out[52]:
    a   b   c  total
0 NaN NaN NaN      NaN
1   1   1   1      3
2   1 NaN NaN      1

In [53]:

output of pd.show_versions()
In [68]: pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.11.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.3-1-ARCH
machine: x86_64
processor:
byteorder: little
LC_ALL: None
LANG: en_GB.UTF-8

pandas: 0.17.1
nose: 1.3.6
pip: 7.1.2
setuptools: 18.2
Cython: 0.23.4
numpy: 1.10.1
scipy: 0.16.0
statsmodels: 0.6.1
IPython: 4.0.0
sphinx: None
patsy: 0.4.0
dateutil: 2.4.2
pytz: 2015.6
blosc: None
bottleneck: 1.0.0
tables: 3.2.2
numexpr: 2.4.6
matplotlib: 1.4.3
openpyxl: 2.2.6
xlrd: 0.9.4
xlwt: None
xlsxwriter: None
lxml: 3.4.4
bs4: None
html5lib: 0.9999999
httplib2: 0.9.1
apiclient: 1.4.2
sqlalchemy: 1.0.11
pymysql: 0.6.6.None
psycopg2: 2.6.1 (dt dec pq3 ext lo64)
Jinja2: None

In [69]:

Comment
As per docs: Exclude NA/null values. If an entire row/column is NA, the result will be NA.
So for a row where all columns are NA expected output is NA, not a zero. Same behaviour also happens for a Series.

That looks like the same issue as https://github.com/pydata/pandas/issues/9422. Can you confirm that, and close this issue if so?
The short version is, this is a difference in behavior between numpy/bottleneck and pandas.

though I suppose we could add a note to the doc-string to note this difference.

@drbig would take a PR for a doc-update.

Yes, it does indeed look like a duplicate, and yes if this is the intended behaviour (what a weird choice though...) then the docs need to be fixed (which I might PR, but nobody should hold their breath over that).
Thanks for quick response!


Dev mode does not recompile/redeploy when adding upstream src/main/java

Use this project: https://github.com/OpenLiberty/guide-maven-multimodules/tree/master/finish
Delete jar/src and war/src/main/java
Run mvn install to install the project to ~/.m2 (no compilation errors occur because there is no Java code in the source of any modules)
Run mvn io.openliberty.tools:liberty-maven-plugin:3.3.5-M3-SNAPSHOT:dev
After dev mode starts up, restore the files from step 2.  Dev mode does not recompile (yet) *
Make a change in jar/src/main/java/io/openliberty/guides/multimodules/lib/Converter.java.  Dev mode DOES recompile the jar and war modules, but the following compilation error occurs **

/Users/eric/git/guide-maven-multimodules/finish/war/src/main/java/io/openliberty/guides/multimodules/web/HeightsBean.java:50: error: package io.openliberty.guides.multimodules.lib does not exist
        this.feet = io.openliberty.guides.multimodules.lib.Converter.getFeet(cm);
                                                          ^
/Users/eric/git/guide-maven-multimodules/finish/war/src/main/java/io/openliberty/guides/multimodules/web/HeightsBean.java:61: error: package io.openliberty.guides.multimodules.lib does not exist
        this.inches = io.openliberty.guides.multimodules.lib.Converter.getInches(cm);
                                                            ^
2 errors

Notice the loose application was not redeployed so the jar and war target classes directories are not in ear/target/liberty/wlp/usr/servers/defaultServer/apps/guide-maven-multimodules-ear.ear.xml ***

In summary, 3 related problems here denoted by *, **, and *** above.

Addressing the second issue stated above (step 6):
/Users/eric/git/guide-maven-multimodules/finish/war/src/main/java/io/openliberty/guides/multimodules/web/HeightsBean.java:50: error: package io.openliberty.guides.multimodules.lib does not exist
        this.feet = io.openliberty.guides.multimodules.lib.Converter.getFeet(cm);
                                                          ^
/Users/eric/git/guide-maven-multimodules/finish/war/src/main/java/io/openliberty/guides/multimodules/web/HeightsBean.java:61: error: package io.openliberty.guides.multimodules.lib does not exist
        this.inches = io.openliberty.guides.multimodules.lib.Converter.getInches(cm);
                                                            ^
2 errors

This is due to how Maven resolves classpath elements for multi module builds. When the jar/src directory exists, thanks to the Maven reactor the war module's classpath has the following entry for the jar module:
/Users/kathrynkodama/devex/sampleProjects/guide-maven-multimodules/finish/jar/target/classes
Maven uses the reactor to add target directories of upstream modules to the current modules classpath.
When dev mode starts without the jar/src/ directory, the war module's compile classpath elements has the following entry for the jar module:
/Users/kathrynkodama/.m2/repository/io/openliberty/guides/guide-maven-multimodules-jar/1.0-SNAPSHOT/guide-maven-multimodules-jar-1.0-SNAPSHOT.jar
Since the jar module is not being installed to the local repo, the war module cannot resolve the jar module's dependency even after the jar/src directory is added.
One workaround would be to call mvn compile from the top-level pom in order to trigger the reactor and have the /guide-maven-multimodules/finish/jar/target/classes directory added to the classpath. This would also require updating the artifact paths for all of the project modules.

We can document this as a limitation for now (as part of https://github.com/OpenLiberty/ci.maven/issues/1199) that dev mode must be started with an existing src/main/java dir with existing Java file(s).

Just looking over this, I think we could close this.
We have a very clear warning explaining what's going on.    I also believe we have other limitations in dev mode where we are unable to watch new directories (e.g. I think we might not be able to act to a new resource directory being added, IIRC).
Maybe the next pass we take through the issues backlog we could consider closing.


kks + kakship

As I was not able to find a forum/chat link to this plugin, I decided to share here, something to add to the docs?
Just sharing the bufline I did using kakship + kks
https://github.com/eburghar/kakship/issues/4#issuecomment-1725835251
The list of buffers on the top

BTW, it would be nice to add a command to kks that would return a string containing:
/path/to/current/buffer.ext | /other/file.ext* | {Current}/even/other/file.ext{\}

where the current opened buffer has the Current face, so we can use the theme to highlight it
the modified buffers has * after its name.
Then with this the bufline can be outputted to kakship easily, or to any other status line.


Add support for Python 3.12

Is your feature request related to a problem? Please describe.
Can't run MemGPT on a project using Python 3.12.
Describe the solution you'd like
Add support for Python 3.12.
Describe alternatives you've considered
I understand downgrading to Python 3.11 is a workaround.
Additional context
I understand the complexity of supporting 3.12 at this time due to some libraries not yet being generally available for 3.12, so I see this issue as more of tracking when support has been added for 3.12.

Yes we should support 3.12 - I believe there is some error that happens with 3.12 that needs to be resolved.

Is there any update on the error for support for Python 3.12.
I am running it on windows and there seems to be build fail for a few libraries.


not support armv5te-unknown-linux-musleabi

error[E0432]: unresolved import `std::sync::atomic::AtomicU64`
 --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/moka-0.11.3/src/common/concurrent/atomic_time/atomic_time.rs:5:20
  |
5 |     sync::atomic::{AtomicU64, Ordering},
  |                    ^^^^^^^^^
  |                    |
  |                    no `AtomicU64` in `sync::atomic`
  |                    help: a similar name exists in the module: `AtomicU32`

   Compiling rcgen v0.10.0
   Compiling sct v0.7.1
   Compiling rustls-webpki v0.101.7

Hi. Thank you for using moka.
For armv5te-unknown-linux-musleabi target, you need to disable moka's default features. Please see this guide to do so.
FYI, we run CI for armv5te-unknown-linux-musleabi and it is passing tests.
https://github.com/moka-rs/moka/actions/runs/6592768977/job/17914034354

Thanks, it's settled


apple-sdk: Include system cups libraries

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

The SDK includes cups header files, but not the libraries. The
nixpkgs.cups definition doesn't build on darwin due to the SDK being
too old. This change symlinks the system cups libraries into the old
SDK.

Does anyone have any more thoughts on this? This actually blocks my qt5 PR. I know linking system libs isn't ideal, but this was the quickest reasonable solution we could come up with on IRC when it came up.

Merged into staging at https://github.com/NixOS/nixpkgs/commit/1712366bac9fabd51543545615b1ba3bccdc8776

Merged into master by https://github.com/NixOS/nixpkgs/commit/86e4c9ed463b0e71e046c902638c0c0ed99e666f

http://hydra.nixos.org/build/45393107 🍻🎉
Thank you so much for your persistence in helping get this merged, @LnL7!

No problem, I'm going to try to keep master and staging a bit more in sync. The less they diverge the better IMHO.


The match keyword doesnt support spaces in the json path child operator.

Currently having a JSON-path child operator with a string containing a space causes the match function to fail as the variable/field name isnt properly escaped.
See attached feature file.
`
Feature: Demonstration
Scenario: a working example
* def exampleData =
"""
{
"value 1":"a",
"value 2":"b",
"value 3":"c"
}
"""
* def val2 = exampleData['value 2']
* match $val2 == 'b'
Scenario: a failing example
* def exampleData =
"""
{
"value 1":"a",
"value 2":"b",
"value 3":"c"
}
"""
* match exampleData['value 2'] == 'b'
`
The first example shows how to combat the issue by introducing a dummy variable. Im wondering whether this really is a bug or if its okay because of the bad practice of having spaces in the json field name

yes, this could be theoretically fixed, but I don't want to complicate the parser for a 1% use-case. you can always do this in two steps:
* def exampleData =
"""
{
"value 1":"a",
"value 2":"b",
"value 3":"c"
}
"""
* def temp = exampleData['value 2']
* match temp == 'b'

And if you have complicated / dynamic JsonPath, you can use the JS API: https://github.com/intuit/karate#jsonpath-filters


[im] CommandPathIB tags incorrect

Problem
Inspection of Pairing UDC messages show CommandPathIB tags of:
Endpoint = 0
Cluster = 2
Command = 3
Yet the 10.5.11. CommandPathIB of the spec defines the following tags:
Endpoint = 0
Cluster = 1
Command = 2
Logs:
matternode> tlv -t 0 -d<PHONE_NUMBER>0024000024023e24030218350124000218181818

[{"type":"struct","value":[
	{"tag":0,"type":"array","value":[
		{"type":"struct","value":[
			{"tag":0,"type":"list","value":[
				{"tag":0,"type":"uint8","value":0},    ///< Endpoint path entry
				{"tag":2,"type":"uint8","value":62},  ///< Cluster path entry
				{"tag":3,"type":"uint8","value":2}     ///< Command path entry
			]},
			{"tag":1,"type":"struct","value":[
				{"tag":0,"type":"uint8","value":2}
			]}
		]}
	]}
]}]

[1633304519.463769][10320:10320] CHIP:EM: Handling via exchange: 5680r, Delegate: 0x0x55f01b9e01e0
[1633304519.463781][10320:10320] CHIP:DMG: ICR moving to [Initialize]
[1633304519.463790][10320:10320] CHIP:DMG: InvokeCommand =
[1633304519.463797][10320:10320] CHIP:DMG: {
[1633304519.463803][10320:10320] CHIP:DMG: 	CommandList =
[1633304519.463810][10320:10320] CHIP:DMG: 	[
[1633304519.463817][10320:10320] CHIP:DMG: 		CommandDataElement =
[1633304519.463825][10320:10320] CHIP:DMG: 		{
[1633304519.463833][10320:10320] CHIP:DMG: 			CommandPath =
[1633304519.463841][10320:10320] CHIP:DMG: 			{
[1633304519.463848][10320:10320] CHIP:DMG: 				EndpointId = 0x0,
[1633304519.463854][10320:10320] CHIP:DMG: 				ClusterId = 0x3e,
[1633304519.463859][10320:10320] CHIP:DMG: 				CommandId = 0x2,
[1633304519.463865][10320:10320] CHIP:DMG: 			},
[1633304519.463871][10320:10320] CHIP:DMG:
[1633304519.463876][10320:10320] CHIP:DMG: 			CommandData =
[1633304519.463881][10320:10320] CHIP:DMG: 			{
[1633304519.463886][10320:10320] CHIP:DMG: 				0x0 = 1,
[1633304519.463892][10320:10320] CHIP:DMG: 			},
[1633304519.463896][10320:10320] CHIP:DMG: 		},
[1633304519.463903][10320:10320] CHIP:DMG:
[1633304519.463907][10320:10320] CHIP:DMG: 	],
[1633304519.463914][10320:10320] CHIP:DMG:
[1633304519.463918][10320:10320] CHIP:DMG: }

Proposed Solution
Align the spec and SDK -- update one or the other to match.
I'd be supportive of moving to global tags for path elements (all path types always tag the Cluster element 2 vs redefining the cluster element tag within each context [typically aligned with the depth in that particular path]).  In that model, this would be a spec change.

This is already fixed.


missing 'model.py'

I've followed the install instructions to the letter, but I'm unable to run  interactive.py with any of the examples in the README (stylegan, stylegan2 or biggan)
(NB the notes at the end about StyleGAN2 installation don't work - there is no setup.py in the directory)
the error is:
Traceback (most recent call last):
File "interactive.py", line 22, in
from models import get_instrumented_model
File "/xxx/ganspace/models/init.py", line 11, in
from .wrappers import *
File "/xxx/ganspace/models/wrappers.py", line 22, in
from . import stylegan2
File "/xxx/ganspace/models/stylegan2/init.py", line 14, in
from model import Generator
ModuleNotFoundError: No module named 'model'
can you help?

You probably didn't clone the submodules. You can fix this by running git submodule update --init --recursive.
Let me know if that fixes is.

ah! thank you - it's looking more promising now!

Closing, feel free to reopen in case of further issues.


dnsproxy: 0.67.0 -> 0.70.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AdguardTeam/dnsproxy/releases.
meta.description for dnsproxy is: Simple DNS proxy with DoH, DoT, and DNSCrypt support
meta.homepage for dnsproxy is: https://github.com/AdguardTeam/dnsproxy
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.70.0 with grep in /nix/store/g61v1ms4lf9qzwgpi9br8diwbxh5g8nw-dnsproxy-0.70.0
found 0.70.0 in filename of file in /nix/store/g61v1ms4lf9qzwgpi9br8diwbxh5g8nw-dnsproxy-0.70.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dnsproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g61v1ms4lf9qzwgpi9br8diwbxh5g8nw-dnsproxy-0.70.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dnsproxy https://github.com/r-ryantm/nixpkgs/archive/bfbe80a9e7480ee07253467e50789e2e26aafb90.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bfbe80a9e7480ee07253467e50789e2e26aafb90#dnsproxy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g61v1ms4lf9qzwgpi9br8diwbxh5g8nw-dnsproxy-0.70.0
ls -la /nix/store/g61v1ms4lf9qzwgpi9br8diwbxh5g8nw-dnsproxy-0.70.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

dnsproxy

Maintainer pings
cc @contrun @diogotcorreia for testing.

@NixOS/nixpkgs-merge-bot merge


Jakarta EE and Quarkus support

Is your feature request related to a problem? Please describe.
Jakarta EE (previously Java EE) and Quarkus are fairly popular alternatives to Spring, but Hilla does not currently support them.
Describe the solution you'd like
Add support for Jakarta EE and Quarkus projects - like Flow has with the Vaadin CDI Add-On.
Both Jakarta EE and Quarkus can and should be supported with the same approach as they share many underlying technologies like CDI.

SpringBoot is more then enough

Quarkus Support is a must.
Think about hybrid apps (Flow and Hilla) on the same server stack

Hi there 👋,
Pretty interested in a decoupled deployment setup with a Quarkus backend, in particular using OpenAPI as source of truth. I find endpoint annotations tend to result in APIs designed in imperative programming style. Lots of boilerplate to take away with an archetype and opinionated tooling, giving atomic control over type-safe client generation, bundling, theme generation, etc. :)

We don't have any plans for Jakarta EE or Quarkus support at this moment. We want to make Hilla really great for a single tech stack before we take on the additional technical complexity needed to support multiple runtime environments in parallel. With that "limitation", Spring Boot is the most natural alternative because of its very wide adoption.
We added Quarkus support for Flow a couple of years ago and we're still at a point where less than 1% of all Flow users use Quarkus. The usage percentage for CDI is in single-digit territory. While the philosophy behind Quarkus is more aligned with Hilla than with Flow, we have no reason to believe that the outcome with Hilla would significantly differ from what we've seen with Flow.
As a side note, we are indeed currently on another journey of adding support for multiple options in parallel by adding support for client-side templating with React in addition to the original Lit support. This is a slightly different situation since React has a similar defacto choice position as Spring Boot with very high general adoption (though Angular is putting up good competition specifically in combination with Java). Supporting multiple rendering libraries is also significantly simpler from a technical point of view since there are fewer integration points.

Thank you Leif, appreciate the elaborate response and rationale. 👍
Then I think for the purpose I described, I should be able to wire Quarkus-based APIs to a plain Lit/Mobx frontend (or React for that matter), composed with Vaadin Components, theme (via DSP) + bundler config. Let's see how that goes!

Please give us quarkus or jEE. Springboot has a lot of round holes its square pegs cannot fill.
Especially since spring native is terrible an immature and spring produces these humongous artifacts that are very expensive in the cloud

@Legioth I think the reason that the quarkus usage is in an 1% range is, that it is not supported as first level like Spring Boot. So some APIs are neither or only later supported for Quarkus or some things are still not possible like this one. I often have issues, which come from the point that vaadin is focusing on spring boot and comes from spring boot. This situation also lets me think currently about switching to Spring Boot to get things done, even if I don't like it. If you start vaadin you get at first glance hinted at spring boot and all examples are done with it. So I assume, that only users who specifically search for the quarkus support use it and the necessary knowledge is also higher because the docs and examples are rare.

You are right that it's to a certain extent at self-fulfilling prophecy that Spring is used by a majority of Vaadin users since we put that alternative in the spotlight for anyone without a strong opinion on what they want to use. We go the extra mile to provide a smooth experience specifically for Spring users but we also try our best to not put up any obstacles in the core use experience for other users (aside from explicitly Spring-only parts such as Hilla or SSO Kit that are peripheral to core Flow usage).
It doesn't significantly change the picture even if we exclude all Flow users that use the Spring integration since Quarkus is then still only at around 5%. Around three quarters of those that don't use Spring aren't using any framework integration at all (or using their own integration instead of something provided by Vaadin). Jakarta EE / CDI is the "winner" in the category but still only reaches around 17% of the non-Spring users.

We want Quarkus support please

Hi folks!
We have an exciting announcement today, we created a quarkus extension for hilla - Quarkus-Hilla !
If you're interested, you can read the full announcement or visit the repository.

Happy coding and have a great day!

Great to hear about that announcement!
While I don't want to fully derail the discussion on the original topic here, I think it could still be meaningful to discuss two things related to the extension.

Thank you very much for your feedback and suggestions @Legioth !

I understand that you have had to resort to some interesting hacks to be able to address the way the current Hilla implementation is tightly coupled to Spring APIs. Short of changing Hilla to use generic abstractions for all those cases, have you identified any low-hanging fruit that could be adjusted in Hilla to make the extension easier to maintain?

There are probably many low hanging fruits, if not even all hacks represent those. We already discussed this and want to create an additional page in the wiki of the project, where we try to list and describe all hacks we've done. This should give the Hilla team some insights, we could also add some simple ranking how easily it can be adjusted.

Would you be open to making the extension report itself to the regular usage statistics mechanism that is used by Hilla and everything else built by Vaadin? In that way, we could get a better understanding of how widely the extension is used compared to Hilla usage in general. I can help with the practical details in case you're open to the idea.

We are basically open for this, as long we comply with the legal terms and that the user can opt-out. I think it would be interesting also for us to see. In the end we need some users, because probably the one or the other could not go with our extension because it's not official, then the statistics would be empty, even if there is some interest.

I was started working with Spring but now Im using Quarkus because it very simple to use and performance as well, so if Hilla support Quarkus this gonna be super cool.
+1 Quarkus

Then maybe you want to give our extension a try?

Most users have opted out of being counted so they don't appear in your stats

That would probably not matter when looking at percentages of those who have not opted out rather than looking at absolute numbers. The case where it would matter is if there's a theory for why Quarkus users would be significantly more eager to opt out than what Spring users are.

The move from java ee to jakarta ee has put many on hold

Same here as well since it's about relative usage rather than absolute numbers. Why would Quarkus users be more affected by this effect than Spring users?

Most users can only be Spring users because most Jee and Quarkus developers didn't know about Hilla

It's quite obvious that Hilla today won't have many Quarkus users since there is no support. The big question is how many users we could expect if it would be supported. If we assume that x% of all Spring users would use Hilla and y% of all Quarkus users would use Hilla, then is there any reason to expect that y would be significantly higher than x?

All else being equal, it would certainly be beneficial to also have Quarkus support. The gotcha is that it's not equal.
Every feature we choose to build means that all the other things we could build are postponed. With Quarkus support, we assume that its impact on Hilla usage would be relatively small based on the overall ratio between Spring Boot usage and Quarkus usage in the Java world. We have other features on the roadmap that we expect to have a higher impact for similar development effort.
Every feature also needs to be maintained in the long run. The abstractions needed for supporting an additional runtime environment are, based on our experience from Flow, among the features that are particularly expensive to maintain. The impact is especially high when it comes to testing since many cases would need to be tested separately with each runtime environment. We have other features on the roadmap that we expect to have lower maintenance overhead for similar impact.

potentially benefit Spring users as PR and issues around the project could lead to continuous improvement for the whole project

That benefit comes mainly from more eyeballs in general, unless someone presents a theory for why the average Quarkus user would be more eager to submit issues and PRs than the average Spring Boot user. A new feature that brings more eyeballs and directly improves the experience for existing users is more valuable than a new feature that only brings the same amount of eyeballs but no direct improvement for existing users.

Imagine an abstraction layer of Hilla. And that cannot be measured in advance, because it is not only a question of quantity, but also of quality.

That abstraction would probably also increase the maintenance burden and occasionally get in the way of building other new features.

The Hilla experience is already good today, which is why Quarkus users want to be able to use it. But at the same time, we know so many things we want to do to make it even better. A nimble framework lets us rapidly explore those ideas so that we can quickly converge towards a truly awesome core experience. The work of adding an abstraction to support multiple runtime environments is a distraction from improving the core experience and the existence of that abstraction would make it slower to try out different alternatives.
What we need for the moment is to keep improving the experience for the existing user category (assuming it's sufficiently big to get enough feedback). Investing to reach new groups of users before that would be like pouring more water into a leaking bucket. Once the bucket is watertight, then it will start to make much more sense to work on pouring!

I am interested in Quarkus version too . +++

Hilla with Quarkus would be great. I create new Flow applications with Spring Boot because of the fast first delivery time. And then I migrate some parts (or the whole application) to Hilla. If I could do it with Quarkus, surely I would use it from the beginning.

@ricardovm maybe you checkout our quarkus-hilla extension. We are always up-to-date and doing nightly builds against the latest dev builds of vaadin. You can also start with it on quarkus starter.

One more point to consider - Trying to get multi-tenancy with keycloak using realm per tenant working, I found nothing for Spring security comparable to the support I found for multi-tenancy in Quarkus at https://quarkus.io/guides/security-openid-connect-multitenancy.  This makes me tempted to try that extension.
But I also love what I'm seeing with Hilla (like the new fly.io deployment stuff).  Coming from a Wicket background, you'd think I'd go more for the vaadin + flow, but I think that was back before I felt comfortable with javascript - now I think Hilla hits the productivity sweet spot for me, so I don't want Quarkus support to detract from that.


Update screenshot of the cockpit

Tutorial URL: https://developers.sap.com/tutorials/cp-mobile-cards-setup.html
Step 2: Go to SAP Mobile Services cockpit
Please update the screenshot of the cockpit as the list of the starter scenarios are updated as below

Best Regards,
Priyanka

Hi Sandeep,
Thanks for the reply. I am closing this Issue.
Best Regards,
Priyanka


Throw away 'Triple' and 'Pair' in favour of 'Sequence'

Triple and pair can be represented as a sequence with resp. 3 or 2 elements. This way, lots of functions can be generalized, resulting in less code duplication without performance loss.
I will experiment a little with a decorator.

👍


Add Secondary Indexes to SimpleTable

Please add the ability to specify secondary indexes and provisioned throughput.

You can set ProvisionedThroughput already https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlesssimpletable
Further, the docs specify that if you need a non-"simple" table to drop out to traditional cloudformation instead, for things like secondary indexes. I can see both points, to be honest.

Yeah, so you should just use AWS::DynamoDB::Table if you need all the jazz of DDB. If you want something quick and easy, use AWS::Serverless::SimpleTable.


Add ability to adopt a pre-existing resource via an annotation rather than using an AdoptedResource

Is your feature request related to a problem?
Currently our EKS upgrade strategy is blue/green where we provision a new cluster and migrate workloads over to the new cluster. For most applications, this is as simple as just running the same application (defined as internal helm charts) on both clusters temporarily before uninstalling the chart from the old cluster.
If we want to start tracking AWS resources alongside our applications, this gets complicated. By default, when we remove the application on the old cluster, the AWS resource (ex: S3 bucket) will get removed. I can set the retain policy annotation on the Bucket object but when the Bucket object is saved on the new cluster, ACK won’t recognize it as the Bucket wasn’t created on this cluster and it’s not an AdoptedResource. Status shows:
    - lastTransitionTime: '2023-12-14T18:04:08Z'
      message: Resource already exists
      reason: >-
        This resource already exists but is not managed by ACK. To bring the
        resource under ACK management, you should explicitly adopt the resource
        by creating a services.k8s.aws/AdoptedResource
      status: 'True'
      type: ACK.Terminal

It seems like we’d need to support both Bucket and AdoptedResource manifests and apply them differently based on whether this is the first time we’ve deployed the application or whether we’re just migrating this to a new cluster.
Describe the solution you'd like
I'd like to be able to support adoption of existing resources via annotations. Example: services.aws.k8s/adopt-resource: true. This would allow for the same manifest to be used for creation and adoption of resources.
(note: I didn't come up with this idea myself, it was provided as a suggestion in the community slack here: https://kubernetes.slack.com/archives/C0402D8JJS1/p1702579196939319)
Describe alternatives you've considered
We've considered using blue/green AWS services to coincide with the EKS migration however this isn't practical for all situations (ex: need long term storage on S3, have persistent data in RDS, etc).

/remove-lifecycle stale


esp-idf如何编译自己新建目录中的程序 (IDFGH-1067)

我想在自己新建的工程目录中，新建vendorapi目录，然后编译里面的程序，应该怎么操作？麻烦帮忙解答一下，谢谢了

@gufeng224 Thanks for reporting the issue. Would you please help provide more details as suggested in the issue template? Thanks.

@gufeng224 Please ask this kind of general questions in the forum, not here. Meanwhile, this is GitHub and there are tons of users who can't read Chinese natively. So please do ask your question in English.
In the CMake build system can either try creating your component or put your vendorapi to your main component, then add something like this in the main component's CMakeList:
file(GLOB_RECURSE VENDOR_API_SOURCES "vendorapi/*.cpp" "vendorapi/include/*.hpp")
file(GLOB_RECURSE VENDOR_API_INCLUDES LIST_DIRECTORIES true "vendorapi/include")

...
...

set(COMPONENT_SRCS "project_main.cpp" ${VENDOR_API_SOURCES})
set(COMPONENT_ADD_INCLUDEDIRS "" ${VENDOR_API_INCLUDES })
register_component()

Or alternatively, add your source files one by one to your COMPONENT_SRCS instead.


Fix curl usage for knockd install

Resolves #2026

Ah Ubuntu has /bin/sh symlinked to dash, which doesn't have pipefail. Should the script shebang be changed to bash?

Ah, I was wondering why it was acting like that. Yeah, I'll change it to bash. I almost did that and then thought it wasn't pre-installed with that base image.

It doesn't help that I'm trying out the new feature in GitHub mobile app to edit files and create PRs ☺


Document resources in Terraform script

I think it makes sense to add a short comment for each (or at least most) resources created, a bit like here https://github.com/sethvargo/vault-on-gke/blob/master/terraform/gcp.tf
I'd even add a link for each resource to the docs for this particular provisioner/task. I often find myself wondering about certain attributes of a resource and having a quick link to the docs would be imo nice.

Might be that this becomes obsolete with the current ongoing work and the work for #10 and #13. If we are generating parts of the documentation from the script I would think that this issue resolves itself.
Leaving it open for now.


Additional API Resource tab is in side panel

Describe the issue:
Additional API Resource tab is in side panel.

How to reproduce:
Login into console.
Additional API Resource tab is visible at the bottom of the side panel.
Expected behavior:
Only the API Resource tab at top should be visible in the side panel

Fixed with https://github.com/wso2/identity-apps/pull/4285


Tab bar icons disappear when adding Nuke

Hi Jean,
Appreciate your effort in creating this library. I was trying to use Nuke in one of project, and I have identified an issue. If I include Nuke in my project, my tabbar icons disappear. Is this a known issue? Any workarounds or fixes available?
I also see a similar issue raised here https://forums.xamarin.com/discussion/181348/hamburger-menu-replace-with-text-with-xamarin-forms-nuke

It's possibly related to #13. I will add a quickfix, a release will be done this week or the next one :)


move whatwg-streams to mesh-whatwg-streams

Using async iterable iterators instead which is a language feature.


ios write blob to file

Hi
I need to write the contents of an image returned from an xhr call with arraybuffer
on android this works but on ios it is a nightmare ... mainly to write the blob to file
can this library help me solve this?
thanks

To which file? JavaScript doesn't allow writing to the filesystem (unless you are in Cordova or some similar environment - that is, not a browser).

yeah i am currently doing this in cordova and soo i will use react-native ... but write now i am having problem writing blobs to file on ios ... i thought this library can help
---- On Wed, 14 Sep 2016 00:56:25 +0300 Ingvar Stepanyan<EMAIL_ADDRESS>----
To which file? JavaScript doesn't allow writing to the filesystem (unless you are in Cordova or some similar environment - that is, not a browser).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Unfortunately, can't help with that - you need to check Cordova's docs https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file/#ios-quirks, but this library doesn't have any specific workarounds for those environments at the moment.


Improve context based healthchecks

@HerrDerb, if you could also squash the commits, it would be great. Thanks!

Thanks @HerrDerb


Option to install earliest versions possible

What's the problem this feature will solve?
As far as I know, executing pip install -r requirements.txt will make sure that all requirements listed in requirements.txt are installed and satisfied.
When a package is required that is currently not installed (or does not satisfy the minimum/maximum version), pip will install/update it to the latest version that satisfies all conditions.
Of course this would be the most expected behavior, but it does make it really hard to see if the minimum requirement versions defined are correct for a package, using CI services.
Describe the solution you'd like
An option that allows for the earliest possible versions of all requirements to be installed, instead of the latest.
Something like pip install -r requirements.txt --install-earliest.
Combined with the --force-reinstall option, this could maybe also force all requirements (not just the ones that are currently not satisfied) to be installed at their lowest versions possible.
Additional context
Allowing for the earliest versions possible to be installed (where no version specified means that all versions are allowed), would allow package developers to see if their requirements.txt files are fully correct.
In my opinion, one should always specify the minimum version required for every required dependency, but over time, it becomes really hard to figure out if these minimum versions are still correct.
This feature/option would allow for exactly this to be tested using CI services.

Hi @1313e, thanks for the report. At first glance it looks like this might belong over at https://github.com/pypa/pip instead, but I'm also not sure I'm totally understanding your use case here. Could you provide an example?

Hi @1313e, thanks for the report. At first glance it looks like this might belong over at https://github.com/pypa/pip instead, but I'm also not sure I'm totally understanding your use case here. Could you provide an example?

Uhm, yeah, it most definitely belongs at pypa/pip.
No idea why I posted that here actually.
Example: let's say that I have the requirement numpy>=1.8.0 for a package.
I cannot actually test whether that minimum requirement is correct, because most people will have a newer version already installed, and CI services just install the latest version (as that is the default behavior of pip).
It would therefore be extremely useful if the earliest possible version could be installed (of NumPy in this case) that satisfies this requirement and all others, such that can be tested if this minimum requirement is correct.

Got it. There's some existing discussion this use case here, and a closed issue requesting the same thing at https://github.com/pypa/pip/issues/3188.
The main takeaways are that this would be hard to implement before https://github.com/pypa/pip/issues/988 is solved, and that you can probably get the same result by doing something like:
$ sed 's/>=/==/g' requirements.txt | pip install -r /dev/stdin

@di Alright, thanks for that.

Hi, maybe you can try a dependency diagnosis website http://www.watchman-pypi.com/dependency_analysis, which can help diagnoze dependency conflict problems and automatically visualize your dependency tree and those of your downstream projects.
Best,
Neolith

I'm going to go ahead and close this, since it appears to be a pip feature request.


[export ssd quota] allow fallback to pd-standard for source disk

We allowed fallback for worker disk and buffer disk. However, we didn't do that for source disk. Let's add this setting to avoid more ssd quota issues.

/gocheck

/gobuild

/flake8

/gobuild

/gobuild

/gobuild


The balance is not changed after using the "Claim" function. Only after reloading

Description
The balance is not changed after using the "Claim" function. Only after reloading
Precondition
Register a new account
Steps to reproduce

Click the "Claim" button
Pay attention to the "Feed" section
Reload the page
Pay attention to the screen

Actual result: The balance is not changed after using the "Claim" function. Only after reloading
Expected result: The balance is changed after using the "Claim" function
Supporting data
Env https://goodqa.netlify.com
iPhone6 12.3.1, Safari
https://www.screencast.com/t/f4BkGY0i

@qatests1001 same issue with events

Checked on https://gooddev.netlify.com
iPhone X // iOS 12.4 Safari
The bug is reproduced
https://www.screencast.com/t/8kaSghWphvK0

The issue had been tested on https://goodqa.netlify.com/, https://gooddev.netlify.com/
The bug is not reproduced.


some uncertain on .mat file reading

This is great work, thanks so much and looking forward to the EMCA roughness version.
There is a code on the load.py
=============
# load the .mat file content
elif file[-3:] == "mat":
matfile = loadmat(file)
    # extract the signal values and sampling frequency
    **signal = matfile[mat_signal][:, 0]**
    fs = matfile[mat_fs]
    fs = fs[:, 0]

==================
does it mean only reading the first value of the signal?
I tried to calculate the roughness with the 24bit wav or mp3, but it seems the framework only supports the 16bit wav. I turn to the Matlab output ".mat", is there any other method except using the ".mat"?

I have sorted it out, replace the Scipy with the Soundfile library.


bug: inconsistent redirects and locale detection

Environment

Node Version:     v16.14.2
Nuxt Version:     3.2.0
Nitro Version:    2.2.1
Builder:          vite
User Config:      ssr, modules, i18n, typescript
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-8hn8cb
Describe the bug
I think there's quite some inconsistencies/unclarity in this plugin regarding redirection and locale detection.

For the rest of this issue, suppose we have the following base config set:
  i18n: {
    locales: [
      {
        code: 'en',
        name: 'English',
        iso: 'en-GB',
      },
      {
        code: 'nl',
        name: 'Nederlands',
        iso: 'nl-NL',
      },
    ],
    defaultLocale: 'en',
  },

A few examples:

1.
with the following settings:
  i18n: {
    // ... base config ...
    strategy: 'prefix',
  },

If your browser locale is set to nl and you navigate to /, the following will happen:

the logs will detect nl is your browser locale
not redirected anywhere (stays on /) [1]
ends with a 302 Found status code [2]
locale wrongly set to en instead of nl [3]
cookie wrongly set to en instead of nl [4]

[1] although from the docs I understand the prefix strategy should redirect to the correct locale.
[2] which is not good for SEO and just in general unexpected I guess
[3] I don't know why this would happen
[4] I don't understand when a cookie will be or will not be set (see example 2. also)

2.
with the following settings:
  i18n: {
    // ... base config ...
    detectBrowserLanguage: {
      alwaysRedirect: true,
    },
    strategy: 'prefix',
  },

If your browser locale is set to nl and you navigate to /, the following will happen:

the logs will detect nl is your browser locale
not redirected anywhere (stays on /) [1]
ends with a 302 Found status code [2]
locale correctly set to nl
no cookie will be set [5]

[5] Weird because in the previous example, it was set (incorrectly, but that doesn't matter here for now). So I think it's unexpected to not set it here.

3.
with the following settings:
  i18n: {
    // ... base config ...
    detectBrowserLanguage: {
      alwaysRedirect: true,
      redirectOn: 'no prefix',
    },
    strategy: 'prefix',
  },

If your browser locale is set to nl and you navigate to /foobar, the following will happen:

the logs will detect nl is your browser locale
not redirected anywhere (stays on /foobar) [1]
ends with a 302 Found status code [2]
locale wrongly set to en instead of nl [6]
cookie wrongly set to en instead of nl [4]

[6] Which is weird, because as we saw in the previous example, for the root it was correctly set to nl
Additional context
Maybe these examples should have been split up into separate issues. But I'm not sure if they are or are not related to each other.
Logs
No response

Same error with nuxt bridge

I've encountered similar behaviour


Update Controller.php

Style:

Return early on error
Don't else-after-return

The same change should be applied to https://github.com/yiisoft/yii2/blob/master/framework/base/Module.php#L587-L592

Thanks!


Toyota: Enable Resume OP w/ Brake Hold Active

Toyota Bug Fix- Allows OP to be resumed while the Brake Hold is Active. The changes prevent the integrator from continuing to ramp up.
Tested on route 4ecfcac756318cbf|2023-07-03--09-32-23--0 and verified via log data in Cabana.
Route: 4ecfcac756318cbf|2023-07-03--09-32-23--0
Attempt at fixing issue:  Unable to activate OP while brake hold active #23095

I believe disallowing engagement when the auto brake hold feature is on is an intentional decision.


No indication that this product is no longer supported by fyneworks.

Could something be put in the Readme (and preferably on the website) showing that the author is no longer supporting this? It looks like no issues have been addressed or pull requests accepted for a long time. Even www.fyneworks.com indicates they don't do jQuery plugins anymore.

Good shout @Micteu. My bad. I've been super busy and not had much time, but I will go through all the outstanding issues and pull requests now.

Oh, hello. Glad you're still active.


[Bug] env key APPSMITH_SIGNUP_DISABLED for Docker doesn't exist or doesn't work

Description
[What happened]
Hello
In docker version, When I Go on locahost , the login page is always present .
I try set the key APPSMITH_SIGNUP_DISABLED=true in docker.env
but first the key doesn't exist, so I don't know if is normal and when I add it in docker.env and I restart the server and go and the page the login is always present.
Steps to reproduce the behaviour:
Add steps to reproduce this behaviour, include console / network logs & screenshots

Go to docker.env
set key APPSMITH_SIGNUP_DISABLED=true
Save
Restart server

Important Details

Version: [Self-Hosted  1.3.1]
OS: [MacOSX]
Browser [chrome]

Thanks

@Gi972 the login / signup page will be present but it will throw an error when you try to sign up unless you have been invited by a user

@Gi972 the login / signup page will be present but it will throw an error when you try to sign up unless you have been invited by a user

I make screenshoots for you
docker.env :

I make screenshoots for you
docker.env :

I restart the container with this command
sudo docker-compose rm -fsv appsmith-internal-server nginx && sudo docker-compose up -d

I restart the container with this command
sudo docker-compose rm -fsv appsmith-internal-server nginx && sudo docker-compose up -d

@Gi972 once you try to sign up, you should see this error

@Gi972 once you try to sign up, you should see this error

Yes Right,
this step is mandatory?
And how  can  I to connect with admin?  with credential in docker.env?

Yes Right,
this step is mandatory?
And how  can  I to connect with admin?  with credential in docker.env?

@Gi972 you can add a docker.env value for
APPSMITH_ADMIN_EMAILS=your admin email
and only this user will be allowed to sign up. The rest of the users will need to be invited by an administrator

@Gi972 you can add a docker.env value for
APPSMITH_ADMIN_EMAILS=your admin email
and only this user will be allowed to sign up. The rest of the users will need to be invited by an administrator

Ah ok , I understand, Maybe let's the key in the docker.env and comment it and specify at doc you need to signup to start,
because it's confusing, we think this key disable the login and signup panel.
So, but It works that's good.
thanks for helping :-)

Ah ok , I understand, Maybe let's the key in the docker.env and comment it and specify at doc you need to signup to start,
because it's confusing, we think this key disable the login and signup panel.
So, but It works that's good.
thanks for helping :-)

@Gi972 thank you for bringing this to our notice.
I've updated the docs below with this information. Thank you for helping make appsmith better :)
https://docs.appsmith.com/getting-started/setting-up/docker#disable-signup

@Gi972 thank you for bringing this to our notice.
I've updated the docs below with this information. Thank you for helping make appsmith better :)
https://docs.appsmith.com/getting-started/setting-up/docker#disable-signup


"No Results" when responseJSON formatted "correctly"

I'm trying to implement Ajax-Bootstrap-Select and keep getting No Results though results are being returned. I have verified that I am returning JSON, formatted like the docs suggest.
According to the console the package is receiving the responseJSON yet is still returning No results were returned. I have also tried to return an array and use the preprocessData method to preprocess the request yielding the same results. I am obviously missing something and hope someone can point me in the right direction.
HTML Code
...

    NAICS Code
        <select multiple
            id="ps-field-naics"
            class="selectpicker with-ajax show-tick"
            name="search['parameters']['naics'][]"
            data-size="6"
            data-live-search="true"
            data-actions-box="false"
            data-selected-text-format="count > 1"
            data-header="Select NAICS CODE(s)"
            data-abs-restore-on-error="false"
            data-abs-request-delay="5000"
            title=""
            size="1"
            data-width="100%"
            data-dropup-auto="true">
    </select>

...

Javascript Code
 var options = {
    ajax          : {
        url     : '/api/filterNaics',
        type    : 'POST',
        dataType: 'json',
        data    : {
            q: '{{{q}}}'
        }
    },
    locale        : {
        emptyTitle: 'Select and Begin Typing'
    },
    log           : 4
};
$('.selectpicker').selectpicker().filter('.with-ajax').ajaxSelectPicker(options);
$('#ps-field-naics').trigger('change');

Returned JSON
This is the response from /api/filterNaics where q=shirt
[
    {
        "naicsCode" : "315223",
        "naicsTitle" : "Men's and Boys' Cut and Sew Shirt (except Work Shirt) Manufacturing",
        "class" : "",
        "disabled" : false
    },
    {
        "naicsCode" : "315291",
        "naicsTitle" : "Infants' Cut and Sew Apparel Manufacturing",
        "class" : "",
        "disabled" : false
    },
    {
        "naicsCode" : "315211",
        "naicsTitle" : "Men's and Boys' Cut and Sew Apparel Contractors",
        "class" : "",
        "disabled" : false
    },
    ...
]

Console Output
Notice the responseJSON and responseText appear to be formatted according to docs - unless I am missing something

@ApeWare value is a required field in the json response for each object.  If you don't want value to the text for the option then you can also return a text property.
[
    {
        "naicsCode" : "315223",
        "naicsTitle" : "Men's and Boys' Cut and Sew Shirt (except Work Shirt) Manufacturing",
        "value" : "315223",
        "text" : "Men's and Boys' Cut and Sew Shirt (except Work Shirt) Manufacturing",
        "class" : "",
        "disabled" : false
    },
    {
        "naicsCode" : "315291",
        "naicsTitle" : "Infants' Cut and Sew Apparel Manufacturing",
        "value" : "315291",
        "text" : "Infants' Cut and Sew Apparel Manufacturing",
        "class" : "",
        "disabled" : false
    },
    {
        "naicsCode" : "315211",
        "naicsTitle" : "Men's and Boys' Cut and Sew Apparel Contractors",
        "value" : "315211",
        "text" : "Men's and Boys' Cut and Sew Apparel Contractors",
        "class" : "",
        "disabled" : false
    },
    ...
]

I made some assumptions but that's what a correct response would look like.
You can also return the structure like you have now and use preprocessData to manipulate the object returned from the server into the thing Ajax-Bootstrap-Select needs.  The usage example uses preprocessData if you need an example of how to use it.
Let me know if you have any other questions or if this doesn't work for you.

Thanks for the quick response! At one point I did have naicsCode named value - forgot why I changed it; changing it to value fixed the issue.
Thanks again for the quick response and for this package! :-)

No problem, glad it was an easy fix!


T-Rex Runner game added

Description
this is a t-rex runner game ... with additional functionality
Fixes:  #(445)

new js project added

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

the working link - https://rahulbawa777.github.io/T-Rex-Runner-game-/

You have compared wrong branches due to which there are many unwanted files in this PR. Make a new PR properly


feat: positivity extension for ite

Match https://github.com/leanprover-community/mathlib/pull/17650

bors merge


Error when running benchmark scripts

Hi,
I tried to run the benchmarking script on Jetson NX and nano. However I got following error on Nano. Any idea how to solve it?  Thank you.
shuaizh@shuaizh-nano:~/jetson_benchmarks$ sudo python3 benchmark.py --all --csv_file_path benchmark_csv/tx2-nano-benchmarks.csv --model_dir /home/shuaizh/jetson_benchmarks/models
[sudo] password for shuaizh:
Please close all other applications and Press Enter to continue...
Setting Jetson xavier-nx in max performance mode
Traceback (most recent call last):
  File "benchmark.py", line 122, in <module>
    main()
  File "benchmark.py", line 28, in main
    system_check.run_set_clocks_withDVFS()
  File "/home/shuaizh/jetson_benchmarks/utils/utilities.py", line 40, in run_set_clocks_withDVFS
    self.set_clocks_withDVFS(frequency=self.gpu_freq, device='gpu')
  File "/home/shuaizh/jetson_benchmarks/utils/utilities.py", line 61, in set_clocks_withDVFS
    from_freq = self.read_internal_register(register=self.freq_register, device=device)
  File "/home/shuaizh/jetson_benchmarks/utils/utilities.py", line 84, in read_internal_register
    reg_read = open(register, "r")
FileNotFoundError: [Errno 2] No such file or directory: '/sys/devices/gpu.0/devfreq/17000000.gv11b/cur_freq'

Sorry for the question, I just found on Nano different commands need to be used.


use the messagepack backend

Description
switches from the xattr backend to the messagepack backend for S3NG and oCIS storage driver.
Needs owncloud/ocis:3.0.0-alpha.2 release.
Could be a breaking change depending on migrations included in that release.
Related Issue

Motivation and Context
Use the messagepack backend which does not rely heavily on extended attributes like the xattr backend.
How Has This Been Tested?

in minikube

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[x] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[x] Documentation generated (make docs) and committed
[ ] Documentation ticket raised:
[ ] Documentation PR created:

Should messagepack really become the default? If we leave it up to the user, there would be no breaking change involved.

Fixed CI issues. Approval given. Ready for merge.


Sound is not playing on Safari (solution)

On desktop and mobile Safari (Mac OSX and iOS), the sounds never play and after debugging it was complaining about line 22 and 34 not having the correct parameter passed to them.
I was able to solve it by changing osc.start() and osc.stop() to their proper form osc.start(0) and osc.stop(0) – it looks like on Chrome they automatically assume 0 value, but not on Safari.

Hey, I came here to say the same thing. Had the same solution too. Nice job!