Added Code Template for Merge Sort

Added username details afterwards in CONTRIBUTING.md file

Reason Behind Updating Full CONTRIBUTION.md file.?

Kindly Review the updated CONTRIBUTION.md made by you change is good but must have same pattern through out file.
Make it clear will surely merge.
@sayskar500

Good to see such standard way of representation ~ update in contribution.md file
Need you help in some small stuff.
If you can then it would be appreciable.
@sayskar500 .

PR accepted @sayskar500.
Successfully merged to HacktoberFest_22 repo.
🚀🚀👍

sure @py3-coder where should we converse for furthur information?


Add support for old.reddit.com URLs.

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Add support for old.reddit.com URLs. As far as youtube-dl is concerned, they work the same way as www.reddit.com URLs.

A test has been added.


fix(explore): faster search for Change Dataset modal

SUMMARY
Reduce the debounce delay in dataset search for the UI can feel more responsive
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before
https://user-images.githubusercontent.com/335541/105427574-4f984000-5c02-11eb-8d0c-06c5f4ba8fc0.mp4
After
https://user-images.githubusercontent.com/335541/105427590-5757e480-5c02-11eb-96e0-dd537a1c5da4.mp4
TEST PLAN
Manual verification. Try change dataset and search.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12669 (cb348c2) into master (6280b34) will decrease coverage by 3.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12669      +/-   ##
==========================================
- Coverage   66.93%   63.42%   -3.51%
==========================================
  Files        1018      486     -532
  Lines       49792    29982   -19810
  Branches     4877        0    -4877
==========================================
- Hits        33327    19017   -14310
+ Misses      16342    10965    -5377
+ Partials      123        0     -123

Flag
Coverage Δ

cypress
?

javascript
?

python
63.42% <ø> (-0.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/views/database/views.py
62.50% <0.00%> (-25.07%)
:arrow_down:

superset/databases/commands/create.py
83.67% <0.00%> (-8.17%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/sql_validators/base.py
93.33% <0.00%> (-6.67%)
:arrow_down:

superset/db_engine_specs/base.py
79.59% <0.00%> (-6.38%)
:arrow_down:

superset/db_engine_specs/sqlite.py
90.62% <0.00%> (-6.25%)
:arrow_down:

superset/db_engine_specs/presto.py
82.25% <0.00%> (-5.85%)
:arrow_down:

superset/views/database/forms.py
83.33% <0.00%> (-5.56%)
:arrow_down:

superset/databases/commands/test_connection.py
84.78% <0.00%> (-4.35%)
:arrow_down:

... and 543 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #12669 (cb348c2) into master (6280b34) will decrease coverage by 3.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12669      +/-   ##
==========================================
- Coverage   66.93%   63.42%   -3.51%
==========================================
  Files        1018      486     -532
  Lines       49792    29982   -19810
  Branches     4877        0    -4877
==========================================
- Hits        33327    19017   -14310
+ Misses      16342    10965    -5377
+ Partials      123        0     -123

Flag
Coverage Δ

cypress
?

javascript
?

python
63.42% <ø> (-0.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/views/database/views.py
62.50% <0.00%> (-25.07%)
:arrow_down:

superset/databases/commands/create.py
83.67% <0.00%> (-8.17%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/sql_validators/base.py
93.33% <0.00%> (-6.67%)
:arrow_down:

superset/db_engine_specs/base.py
79.59% <0.00%> (-6.38%)
:arrow_down:

superset/db_engine_specs/sqlite.py
90.62% <0.00%> (-6.25%)
:arrow_down:

superset/db_engine_specs/presto.py
82.25% <0.00%> (-5.85%)
:arrow_down:

superset/views/database/forms.py
83.33% <0.00%> (-5.56%)
:arrow_down:

superset/databases/commands/test_connection.py
84.78% <0.00%> (-4.35%)
:arrow_down:

... and 543 more

Continue to review full report at Codecov.

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


Moves token security closest to the location where the token enters t…

Moves the setSecret call closest to the place the token enters the scope of the task to prevent accidental logging of the token in the future.
This does mix concerns a little bit, but this prevents a change in the 4 functions in the call chain from accidentally surfacing the token in the future.
This could be refactored to a promise that can be passed to the token generator.

LGTM, @jaredfholgate any opinion?

@jessehouwing and @mericstam. For future reference I found there is a function for setting a secret: https://github.com/microsoft/azure-pipelines-task-lib/blob/0b4a3c796ae34493d86e8f8a46f414d722cd807f/node/task.ts#L219
It would be called like this in this scenario:
import tasks = require('azure-pipelines-task-lib/task');
...

tasks.setSecret(token);

@jaredfholgate agreed. Located the spot and added the code to mask the secret in a PR.
I'd forgotten that tasklib function exists. It would be a better temporary solution, but let's see if the linked PR would come through.


Cropping wallpapers don't consider status bar and navbar

When cropping wallpapers, even if the wallpaper matches the screen size, the portion of the image behind navbar and status bar are being cut out and the wallpaper ends up smaller then source image
before applying, as visible on screen

after applying the wallpaper

an easy way to verify this is using a screenshot of the wallpaper as a wallpaper

Generally, Android zooms in the current wallpaper a little bit to compensate for animations. This is an expected behaviour.

See here for the responses.


Do our own UX audit

When observing totally new people use the Weaver, I notice some UX awkwardness that I am just totally used to by now.
We should invite someone to do some intentional review of the Weaver to make it easier to use.

Started doing some card sorting and did a walkthrough with Lab team to get some ideas for reorganizing this content.
https://trello.com/invite/b/eoXa8zyx/386327c42d90bf5058abe6bf6b3e557a/new-weaver-brainstorming

We've implemented a lot of these changes in recent months. This vaguer issue isn't so actionable anymore, but we're definitely continuing the thought process in #806 and ongoing Monday brainstorming sessions.


GUI design

How was this made (an app, website, tool)?
If we need to update later, what source file can we use to maintain consistency?

Its just a draw up, Chan said it should be included in design document, made it with lucid chart. But for actual look, made in Qt designer.


PlayStore listing

Hey,
it seems the App is not listed in the PlayStore :(
Best
Hornhaut

https://github.com/ethereal-developers/OpenScan#psa


Unable to install dronekit on pi4, Missing depedancies

I'm having a bit of trouble installing python dronekit  on my raspberry pi 4B (8GB) (bullseye).
I know that dronekit does not support Python3, hence I am running a virtual python environement (dronekitty)
This is my terminal output:
I'm having a bit of trouble installing python dronekit  on my raspberry pi 4B (8GB) (bullseye).
I know that dronekit does not support Python3, hence I am running a virtual python environement (dronekitty)
What could i be doing wrong? I am pretty new to Linux.
pi@raspberrypi:~ $ source dronekitty/bin/activate
(dronekitty) pi@raspberrypi:~ $ pip install dronekit
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting dronekit
  Using cached dronekit-2.9.2-py2-none-any.whl (57 kB)
Collecting monotonic>=1.3
  Using cached monotonic-1.6-py2.py3-none-any.whl (8.2 kB)
Collecting pymavlink>=2.2.20
  Using cached pymavlink-2.4.37.tar.gz (5.7 MB)
  Installing build dependencies ... error
  ERROR: Command errored out with exit status 1:
   command: /home/pi/dronekitty/bin/python /home/pi/dronekitty/lib/python2.7/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-IoOc4V/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple --extra-index-url https://www.piwheels.org/simple -- 'setuptools>=42' future lxml
       cwd: None
  Complete output (17 lines):
  DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
  Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple, https://www.piwheels.org/simple
  Collecting setuptools>=42
    Using cached setuptools-44.1.1-py2.py3-none-any.whl (583 kB)
  Collecting future
    Using cached future-0.18.2.tar.gz (829 kB)
  Collecting lxml
    Using cached lxml-4.9.1.tar.gz (3.4 MB)
      ERROR: Command errored out with exit status 1:
       command: /home/pi/dronekitty/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-OdNcuZ/lxml/setup.py'"'"'; __file__='"'"'/tmp/pip-install-OdNcuZ/lxml/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-qUR0KC
           cwd: /tmp/pip-install-OdNcuZ/lxml/
      Complete output (3 lines):
      Building lxml version 4.9.1.
      Building without Cython.
      Error: Please make sure the libxml2 and libxslt development packages are installed.
      ----------------------------------------
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

How do i go about installing these two packages? When i try using sudo apt-get or pip, nothing is found?

try this "sudo apt-get install libxml2-dev libxslt1-dev zlib1g-dev python-py"
or you can try "sudo aptitude dronekit",this command can guide you to install dronekit.


Support simple query pushdown for Postgres

Support simple query pushdown
The goal of this task is to enable simple query pushdown for querier that look like {_id: <ObjectID>}.
Only that field name (_id) is supported, and only that value type (ObjectID).
In the future, we will add support for other fields (starting with simple scalar fields),
other values (starting with strings, numbers, and other simple scalar values),
other conditions like {_id: <ObjectID>, field: value} (so only the first part is pushed down).
Postgres
If a field name is different, value type is not ObjectID, or some other condition is present,
we should use the previous version of the code that SELECTs the whole table without any WHERE condition.
If the value type is ObjectID but the data in the value is somehow corrupted, raise an error (fjson unmarshal).
If those conditions are met, we send a SELECT query with a WHERE condition.
Proof of concept for a {_id: <ObjectID>} pushdown query, PostgreSQL:
GIN index is not used by PostgreSQL in any queries below.
So let's use the first one just because it is first.
-- this will not use these indexes:
-- CREATE INDEX values_id_idx ON public."values" USING gin ((((_jsonb -> '_id'::text) -> '$o'::text)))
-- CREATE INDEX values_id_idx ON values (((_jsonb ->> '_id')::text));
select * from values where (_jsonb->'_id')::jsonb->>'$o' = '507f1f77bcf86cd799439011'; -- no, seq scan will it use index? not that indexes

Test
Integration tests: Provide a new test flag that enables a query pushdown.
Run with and without flag: results must be the same.
When explain feature will be ready, compare the query plan.
Links
Analysis task: #847

GIN index is not used by PostgreSQL in any queries below.
So let's use the first one just because it is first.

I'm not sure I understand this but, just in case, the following index works in PostgreSQL and YugabyteDB:
yugabyte=# create table values (_jsonb jsonb);
CREATE TABLE
yugabyte=# CREATE INDEX values_id_idx ON values (((_jsonb -> '_id'::text) ->> '$o'::text));
CREATE INDEX
yugabyte=# explain
yugabyte-# select * from values where (_jsonb->'_id')::jsonb->>'$o' = '507f1f77bcf86cd799439011';
                                         QUERY PLAN
---------------------------------------------------------------------------------------------
 Index Scan using values_id_idx on "values"  (cost=0.00..5.27 rows=10 width=32)
   Index Cond: (((_jsonb -> '_id'::text) ->> '$o'::text) = '507f1f77bcf86cd799439011'::text)
(2 rows)

It is not a GIN index because it is a single value. But the indexed expression must match the one used in the equality predicate, like here.


permission fix

Coverage decreased (-0.04%) to 51.453% when pulling b44249a37b9486c234d8aa9c942b999499edc73a on yuye/authndev-permission into fe61eeac0fa06856cc1907ee8507f43fb1c3fa19 on authndev.


feat: rhel82 FIPS

What problem does this PR solve?:
Added Makefile changes and e2e test for RHEL 8.2 FIPS.
Which issue(s) does this PR fix?:

https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

@faiq AFAIK this repo does't use TC config as code: https://teamcity.mesosphere.io/buildConfiguration/ClosedSource_KonvoyImageBuilder_E2eRhel8fips?branch=&buildTypeTab=overview&mode=builds


Add support Scala Build Tool (sbt)

Add sbt_include_groups option
Update README.md to include Scala/sbt

@bradfordboyle Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@bradfordboyle We took at look at your failures and this is not an issue with your code.
The 2.1.5 issue was an html url having an underscore in a spec file instead of a dash
https://github.com/pivotal/LicenseFinder/commit/f2e6238b2b5ee149cf4b40ba4c8759f97a3dc043
The 2.2.0 issue was due to rack-test not being locked to version 0.7.0. The new version 0.8.3 requires ruby 2.2.2 to function. This is now locked in the license_finder.gemspec.
The jruby issue was the hard one. Scala needs to be run with JDK 1.8 but the docker image seemed to be using 1.7. We now have conitions that force 1.8 to be used when running with jruby.
Please see PR: https://github.com/pivotal/LicenseFinder/pull/470 for the relevant code changes. You will need to rebase your branch off master after it has been merged in.

@xtreme-shane-lattanzio Thanks for looking into this. I just rebased, so CI should be going green soon.

@bradfordboyle And green it is! We just need to get you to sign the pivotal-cla and we can merge it in. Thanks for rebasing everything.

@bradfordboyle Thank you for signing the Contributor License Agreement!


Encountered Docker Error: "When using COPY with more than one source file, the destination must be a directory and end with a /""

OS & Docker version
My docker version: 20.10.7, build f0df35096d
OS: arch-linux
Reproducing the Error:
Good day olliefr, I encountered an error when going through the golang docker tutorial.
The following commands were run:
git clone https://github.com/olliefr/docker-gs-ping
cd docker-gs-ping
docker build --tag docker-gs-ping .
The Error
When using COPY with more than one source file, the destination must be a directory and end with a /
The Solution
By changing line 12 in the Dockerfile from:
COPY *.go .
to
COPY *.go ./
I am not sure if this solution will cause other issues. I doubt it but I can investigate and make a pull request if this error is significant enough.
I am also curious if other people encountered this error or if it is only on my machine.

Hello, @PabloTheDeveloper and thank you for taking your time to submit a bug report!
I think you are right! After careful reading of the Dockerfile reference, I think that the syntax you suggested is the correct one.
Having said that, I've just tested the Dockerfile as it is on my instance of Docker and it works:

I still believe that your suggested solution is the right one, please bear with me while I investigate further and update the code and the docs.
In answer to your other question, you are the first one to report this to me 😄

Hello both of you,
I did encounter the same issue and was about to open a pull request.
Here a few more information
`➜  docker-gs-ping git:(missing-slash-character) ✗ docker version
Client: Docker Engine - Community
Version:           20.10.7
API version:       1.41
Go version:        go1.13.15
Git commit:        f0df350
Built:             Wed Jun  2 11:56:38 2021
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.7
API version:      1.41 (minimum version 1.12)
Go version:       go1.13.15
Git commit:       b0f5bc3
Built:            Wed Jun  2 11:54:50 2021
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.4.6
GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
runc:
Version:          1.0.0-rc95
GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
Running onUbuntu 20.04.2 LTS`


[SQL] Remove unused BeamIOType

Nothing uses or tests this in Beam. It appears to be a implementation of isBounded.

Follow this checklist to help us incorporate your contribution quickly and easily:

[X] 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.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

R: @akedin
cc: @kennknowles

ElasticSearchIO flakes.

run java precommit


optuna: Use summary instead of log_metric.

Prevent creation of single-row .tsv files.
Each trial creates a single DVC experiment and logs metrics a single time.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (634f911) 95.70% compared to head (e6c402c) 95.71%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #514   +/-   ##
=======================================
  Coverage   95.70%   95.71%
=======================================
  Files          41       41
  Lines        2587     2588    +1
  Branches      220      220
=======================================
+ Hits         2476     2477    +1
  Misses         66       66
  Partials       45       45

Impacted Files
Coverage Δ

src/dvclive/optuna.py
66.66% <100.00%> (ø)

tests/test_frameworks/test_optuna.py
100.00% <100.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ignore undefined in the component chain

a onEnter "middleware"-route can be in the components chain, which will be detected as undefined. as described in #33
fixes #33

not necessary, take a look at #33


SCB-977 Dependencies will not be updated in 5min when micro service is changed

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run go build go test go fmt go vet to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #462 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #462      +/-   ##
=========================================
+ Coverage   60.17%   60.2%   +0.02%
=========================================
  Files         156     156
  Lines       13415   13415
=========================================
+ Hits         8072    8076       +4
  Misses       4762    4762
+ Partials      581     577       -4

Impacted Files
Coverage Δ

server/service/event/tag_event_handler.go
7.69% <0%> (ø)
:arrow_up:

server/service/event/service_event_handler.go
12.5% <0%> (ø)
:arrow_up:

server/broker/util.go
53.47% <0%> (+0.26%)
:arrow_up:

server/govern/service.go
73.66% <0%> (+0.33%)
:arrow_up:

...erver/plugin/pkg/tracing/buildin/file_collector.go
64.07% <0%> (+0.97%)
:arrow_up:

server/service/notification/stream.go
69.56% <0%> (+4.34%)
:arrow_up:

Continue to review full report at Codecov.

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

Coverage increased (+0.1%) to 62.718% when pulling e10d2db0c4e73a6631c7c5bf6e2db4defb0250fb on little-cui:bug into bd59e8bf98179b49c997f10ed4f529b2d1c0afcf on apache:master.


all: fix some comments

Hi @cuishuang. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/ok-to-test

@cuishuang: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
true
/test release-notes

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

/test release-notes

@cuishuang: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

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

@cuishuang: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

integ-security-multicluster_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-multicluster

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

@cuishuang: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

integ-security-multicluster_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-multicluster

release-notes_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test release-notes

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

@cuishuang: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

integ-security-multicluster_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-multicluster

release-notes_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test release-notes

integ-pilot-istiodremote_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-pilot-istiodremote

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

@cuishuang: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

integ-security-multicluster_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-multicluster

release-notes_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test release-notes

integ-pilot-istiodremote_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-pilot-istiodremote-mc

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

@cuishuang: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test gencheck

integ-security-multicluster_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-multicluster

release-notes_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test release-notes

integ-pilot-istiodremote_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
c2c823378a16c3b50ac3d7a785ff09759c705632
link
unknown
/test integ-security-istiodremote

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

/retest

/retest


jQuery npm module

In package.json, the jquery module should be written in lowercase. I get a npm warning<EMAIL_ADDRESS>This is deprecated. Please use 'jquery' (all lowercase).". Then I get conflicts with my jquery module.

@ichord and @JeanCarriere I made a fix here: #358


[Feature Suggestion} Input

Was about to make a simple game with this, but just realized that there's no way for user to have input.
I don't know how hard it would be to add that, this project itself is already lookin hard.
Just a simple int/char input would be nice.
Really appreciated if it'll be added, but also understandable if not.

adding that rn to my fork

Was about to make a simple game with this, but just realized that there's no way for user to have input. I don't know how hard it would be to add that, this project itself is already lookin hard. Just a simple int/char input would be nice. Really appreciated if it'll be added, but also understandable if not.

I managed to get a somewhat working function for it, although it's disconnected from the terminal APIs and therefore only displays the question without showing what the user is typing (visually).
It will be added in the next version as yap (bsx) or input (bs).

Added in 25b992a


Update namespace for PackageRepository

Then the PackageRepository should be moved to src/Repository :)

Yup, @norkunas is correct. I put this NOT in the src/Repository/ originally just to not confuse it with "entity repositories", which this is not one.


更改动画占用内存，持续不放的问题

Description
const animations = (edge, path, duration) => {   let timeoutId;   return new Promise((resolve) => {     edge.transition(path, 1, {       duration: duration,       timing: Timing.linear,       delay: 0,       complete: ({ cell, path }) => {         if (animationRunning.value) {           resolve();           cell.updateAttrs(             {               arrow1: { atConnectionRatio: 0 },             },             { silent: true }           );           timeoutId = setTimeout(() => animations(cell, path, duration), 500);         } else {           resolve(); // 停止动画循环时，也要正常完成Promise         }       },     });     if (timeoutId) {       clearTimeout(timeoutId);     }   }); };
this.queue在动画循环下，会持续增加，导致百万级别不释放，最后内存不释放
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[ ] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

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

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 10.34%. Comparing base (a431f52) to head (1d75a1e).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4357   +/-   ##
=======================================
  Coverage   10.34%   10.34%
=======================================
  Files         180      180
  Lines       10582    10582
  Branches     2580     2580
=======================================
  Hits         1095     1095
  Misses       9398     9398
  Partials       89       89

Flag
Coverage Δ

x6
10.34% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

packages/x6/src/model/animation.ts
3.79% <0.00%> (ø)

packages/x6/src/renderer/queueJob.ts
8.21% <0.00%> (ø)


Fix a few type check failures

@jayvdb I didn't notice your PRs before I created this one. But it looks like we tackled a different set of type errors. Let me know if there are any conflicting changes and I'll revert them.

I don't see any major conflicting changes here.  If you want any of my PRs in before https://github.com/adsharma/py2many/pull/363 , let me know and i'll rebase and push them onto main


Part 2 of the rewrite

[ ] Customizing output format in the "Output format" section, linking to examples of how it's done
[ ] Move "advanced usage" to the README of the washington.core package
[ ] Some GIF demonstration, maybe of running a short test suite
[ ] HTML Browser formatter. Built in React I guess, it will need a target element to render.
[ ] Finish the "Code Document" write up
[ ] Add examples of how to replicate the scenario lifecycle of Mocha and such in a functional way ([...].map((case) => ({...case, test: compose(case.test, beforeEach) }))
[ ] Logo

Ideas (can be ignored):

[ ] Run through the examples from the cheat sheet in a screencast
[ ] Think about adding filtering, but not too hard since it can be done before passing the array of tests to Washington
[ ] Would it be possible to have a Karma reporter?
[ ] Would it be a good idea to point out that it can be used instead of Jest by wrapping the tests with JSdom?

Extract taken away from the new README:
## A vision: the code document

Combining the simplicity

## Output format

**TODO**

## Advanced usage

**TODO** you will be able to consume the output of the tests programmatically with a `folktale` Task.

> Note that the above code is not using the Washington helpers for constructing the examples. The intention is to make it transparent to you right now that the example scenarios that Washington works with are plain JavaScript objects. This opens up a [plethora of opportunities to organize your tests as it better pleases you](#a-proposal-the-code-document).

⬆ to add the "code document" writeup
But sure some of you disagree! Well, if you for some reason you really like Washington’s approach and would like to use it, but you also really want to get a nested structure of tests, remember: examples are just plain JavaScript objects. You are more than welcome to add a `namespace` or `breadcrumbs` property to them and use it in a custom formatter to organize the output of the test suite. Go ahead to the [advanced usage](#advanced-usage) section for an explanation of how to write a formatter (it’s not hard either).

Add the "advanced usage" section.

In here: https://github.com/xaviervia/washington#but-what-about-namespaces
Add the example:
const addNamespace = namespace => example =>
  ({...example, description: `${namespace}: ${example.description}`})

testSuite.map(addNamespace('Addition'))

Add explanation about starting up with Lerna (make tasks) in here: https://github.com/xaviervia/washington#collaborating


Changelog outdated?

I see this big bump to v0.5 but changelog does not mention any breaking changes :/

We're using symantic versioning so the 5 part represents minor changes that are backwards compatible.
Sorry about not keeping the changelog up to date. Been busy.

Busy happens, it is sometimes hard to justify updating when you don't know anything about the changes that come with the new version.

The changes mentioned in the OP are now in the changelog, however the 0.7.0 and 0.7.1 releases since then are missing.

The changes mentioned in the OP are now in the changelog, however the 0.7.0 and 0.7.1 releases since then are missing.

I tried using the git tags to compare the versions, however the tags seem broken?

Trying to upgrade from 0.5.2 to 0.7.1. Would be nice an updated changelog to see if there is any breaking changes.

There have been some breaking changes for sure as my app stopped working updating...


Add bower_components and dist to .npmignore.

Fixes #5244

I've switched to using files, deleted .npmignore.  This cleans a couple more files that are development only (detailed in commit message).  Redundant entries are not listed, see npmjs docs for files that are automatically included.  You can test this using npm pack, then inspect the tarball that is created.
With this change @polymer/polymer will be 1022kb unpacked.  Of this CHANGELOG.md (automatically included by npm pack) is 324k, 31% of the total install.  Maybe CHANGELOG.md should be split so it only includes the current semver-major, have a CHANGELOG-ARCHIVE.md or similar containing entries for legacy versions, add an a link to the end of the current changelog?  Not included in this commit as decreasing from 14936kb to 1022kb is a huge improvement but I still feel it's worth considering not allowing the CHANGELOG.md included in the package to expand indefinitely.


Fix typos in debugger docs

@GitHubPang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

These all look good; we'll merge. Thanks @GitHubPang.


Adds initial version

Adds an initial, working version of the tool along with readme.

Also example.png is empty.
@slonka it's not empty, the diff doesn't show because it's a binary file.

You can view the entire rendered readme here: https://github.com/allegro/envoy-perf-pprof/tree/basic.

Also example.png is empty.

@slonka it's not empty, the diff doesn't show because it's a binary file.
You can view the entire rendered readme here: https://github.com/allegro/envoy-perf-pprof/tree/basic.

I thought that images are displayed in PRs.


feat: [M3-8356] – Support Block Storage Encryption feature flag

Description 📝
Create a boolean feature flag for Block Storage Encryption (BSE) and support it in Cloud
Changes  🔄

BSE feature flag toggle added to our dev tool

Target release date 🗓
8/5/24
How to test 🧪
Verification steps
Confirm a toggle for "Block Storage Encryption (BSE)" is present in our dev tool
As an Author I have considered 🤔

[X] 👀 Doing a self review
[X] ❔ Our contribution guidelines
[X] 🤏 Splitting feature into small PRs
[X] ➕ Adding a changeset
[X] 🧪 Providing/Improving test coverage
[X] 🔐 Removing all sensitive information from the code and PR description
[X] 🚩 Using a feature flag to protect the release
[X] 👣 Providing comprehensive reproduction steps
[X] 📑 Providing or updating our documentation
[X] 🕛 Scheduling a pair reviewing session
[X] 📱 Providing mobile support
[X] ♿  Providing accessibility support

@dwiley-akamai Do you want to create a new github label for BSE?

@dwiley-akamai Do you want to create a new github label for BSE?

Done, meant to do that before my afternoon meetings started 👍🏾


Bitmap uses fallback protocol unless on 512x512 8x8

It seems like the bitmap always uses the fallback protocol unless on 512x512 pixels and 8x8 units. I am on Linux if that makes a difference.

Argh!! Yeah, linux is especially picky with custom Tauri protocols. This might also affect MIDI playback (since it uses a special protocol too). Going to investigate this in a VM this week.

Out of curiosity, does smaller resolutions work? Like 32x32 1x1? For reference, 512x512 8x8 should be equivalent to 64x64 1x1, which is fairly small. Bitmap display units is more of a legacy feature, it was added to help people using MARS instructions (where units have a confusing but real meaning).

Sorry just saw this, 32x32 1x1 does not work either, going to see if wine does the trick

Hey, I've done some experimenting on a Linux VM and I've identified the issue. It's also worth noting this is a regression from around v0.1.7 time I think? So version v0.1.5 shouldn't have this problem (and I think v0.1.6 is good too).
The issue has to do with CORS and sending headers on Linux, if you're curious. Pretty cursed.

Ohhh interesting, thank you

Funnily enough the main reason why this bug is annoying is while debugging, yet v0.1.7 adds a lot of debugging features that I would be using.

Yes it works! Thank you so much


Multipart upload automatically retry when network timeout.

What did you do?
Uploading image using multipart upload. I set the default configuration for URLSession.
What did you expect to happen?
As I starting request the image, and I do some network throttle beneath 33.6 kbps using Charles proxy. The default timeout was 60 secs, it would be return error status when network timeout.
What happened instead?
It would be an error in failure block when the time reached. However, it start next request automatically and the responseJSON block was never call in this case.
Alamofire Environment
Alamofire version: 4.7.3
Xcode version: 10.1
Swift version: 4.0
Demo Project
Alamofire.upload(
        multipartFormData: { multipartFormData in
            multipartFormData.append(imageData, withName: "photo", fileName: "fileName", mimeType: "image/jpeg")
        },
        to: "http://example.com/to",
        encodingCompletion: { encodingResult in
            switch encodingResult {
            case .success(let upload, _, _):
                upload.responseJSON { response in
                    print(response)
                }
                upload.uploadProgress { progress in
                    print(progress.fractionCompleted)
                }
            case .failure(let encodingError):
                print(encodingError)
            }
        }
    )

I'm not sure what you mean by "it start next request automatically". What next request? Do you have a RequestRetrier active? Was the responseJSON called the first time the request failed?

@jshier
As the image shows.
https://i.imgur.com/xf2XWsu.png
I set the timeout to 15 secs for demonstrate this issue.
It starts 'same' upload request after network timeout without setting any retrier.
By the time the network restored, it response each request, but all I got was the last response.
https://i.imgur.com/ZE8qz9i.png

I found something wrong with my code, thanks for helping.

@Donny8028  How did you fix the problem I am facing the same problem


docker compose - latera/homs container crashes.

When i try to install Hydra OMS using Docker Compose, latera/homs contianer crashes immediately.
This is a Copy of the container logs:
cp: target '/opt/homs/config/' is not a directory
cp: cannot stat 'config/activiti.yml.sample': No such file or directory
sed: can't read config/activiti.yml: No such file or directory
sed: can't read config/activiti.yml: No such file or directory
sed: can't read config/activiti.yml: No such file or directory
cp: cannot stat 'config/database.yml.sample': No such file or directory
sed: can't read config/database.yml: No such file or directory
^C/usr/local/lib/ruby/2.2.0/rake.rb:36:in require': Interrupt 	from /usr/local/lib/ruby/2.2.0/rake.rb:36:in <top (required)>'
from /usr/local/lib/ruby/gems/2.2.0/gems/rake-10.4.2/bin/rake:31:in require' 	from /usr/local/lib/ruby/gems/2.2.0/gems/rake-10.4.2/bin/rake:31:in <top (required)>'
from /usr/local/bundle/bin/rake:16:in load' 	from /usr/local/bundle/bin/rake:16:in '
rake aborted!
LoadError: cannot load such file -- /opt/homs/config/application
/opt/homs/Rakefile:4:in require' /opt/homs/Rakefile:4:in <top (required)>'
(See full trace by running task with --trace)
/usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:147:in parse!': missing argument: -e (OptionParser::MissingArgument) 	from /usr/local/bundle/gems/thin-1.6.4/lib/thin/runner.rb:50:in initialize'
from /usr/local/bundle/gems/thin-1.6.4/bin/thin:6:in new' 	from /usr/local/bundle/gems/thin-1.6.4/bin/thin:6:in <top (required)>'
from /usr/local/bundle/bin/thin:16:in load' 	from /usr/local/bundle/bin/thin:16:in '

Hello,
We have fixed the container and built a new version. You should now type
docker-compose pull homs
in the directory where you have downloaded the docker-compose.yml file and then run the container by issuing
docker-compose up -d.
Sorry for the inconvenience it might cause you.

Thanks.


[useFetch] Fetch State is not exported

I want to wrap useFetch to do lazy loading fetch.
import { State, useBoolean } from "usehooks-ts";
import React from "react";

const setFetch: React.useState<State | undefined>(undefined);
const isClicked = useBoolean();

React.useEffect(
    function () {
      if(isClicked.value) {
        setFetch(useFetch<whatever>(url)
      }
    }
    [isClicked, setFetch],
);

what about a new useLazyFetch hook?
import React from "react";
import { useFetch } from "usehooks-ts";

// until https://github.com/juliencrn/usehooks.ts/issues/37 is fixed
interface State<T> {
  data?: T;
  error?: Error;
}

interface Executer {
  (): void;
}

interface LazyQuery<T> {
  execute: Executer;
  state: State<T> | undefined;
}

function useLazyFetch<T = unknown>(
  url?: string,
  options?: RequestInit,
): LazyQuery<T> {
  const [state, setState] = React.useState<State<T> | undefined>(undefined);

  return {
    state,
    execute: function (): void {
      setState(useFetch(url, options));
    },
  };
}

that break the rule of hooks :(


Reissue noble scan in multi device setting (plus auto-indent code)

In case you want just the rescan (minus code indentation), please reject the pull request, I will try to add this to your current branch instead then.
Running another scan instead of stopping upon connecting the first device connects all devices upon a restart of the service.

added a max number of scans so it will stop in case a device can't be reached

AutoRestart improved ...


Implement PKCS#7 parser.

Since we have a working asn.1 parser, and the ability to extract a PKCS#7 data structure from a portable executable, we need a way to parse the PKCS#7 structure in to something more readable that will ultimately serve as the source of information in to the linter's checks.
Ultimately, we need a way to extract signatures, their digests, certificate, chain, and nested signature, etc.

This is largely done.


Allow splitting client to support concurrent read/publish

I'm using this library from a web application used to control IoT devices. I would like to publish a message in response to a web call.
The current API does not allow concurrent use of the Client.
In this PR I implemented a into_split method which, much like the tokio::net::TcpStream::into_split will split the Client into two halves: a reading half and a publishing half.
The publishing half is Sync and clonable, which allows use from multiple threads.
The reading half is not, and remains usable from only a single thread.
The current implementation in this PR is very rough (just copied various methods from the Client) and serves my purpose.
If the maintainer of this repository is interested in this functionality, I will clean it up further.

I think this is an interesting feature request. Unfortunately I have issues with the way it's currently implemented in your branch. From a brief look it seems quite a lot of code is duplicated between the new ClientReadHalf and ClientPublishHalf implementations and the original Client, and I think this would be quite hard to maintain correctly.
Is there a way for the Client*Half implementations to delegate to an inner Client, or for all of Client*Half and Client to delegate to a new ClientInner that holds most of the logic?

Thank you for the feedback. I'll work on it sometime this week:

refactor to remove code duplication. Probably remove send functions from client, and make them functions accept individual parts instead of client struct.
add better documentation, with example

I have changed the API to something I am more comfortable with, removed code duplication and added some documentation.
The new API works by allowing the creation of ClientPublisher instances (similar to the PublishHalf in the earlier concept). These instances can be cloned and are Send (so they can be used from different threads).
An example how this works:
use mqtt_async_client::client::Client;

let client = ..;

let publisher1 = client.publisher();
let publisher2 = client.publisher();  // Or use publisher1.clone()

tokio::spawn(async {
  publisher1.publish(..)
});

tokio::spawn(async {
  publisher2.publish(..)
});


neofetch prints wrong GPU type

Description
Neofetch prints the wrong GPU type. Currently it prints:
CPU: Intel i5-4670 (4) @ 3.800GHz
GPU: Intel Xeon E3-1200 v3/4th Gen Core Processor

I would expect it to print something like
GPU: Intel HD Graphics 4600`

Neofetch version
5.0.0
Screenshot
Can't currently provide one. Sorry. Here is the output.
Config file
Link
Verbose log
Link

Output of this command?:
glxinfo | grep "Device:.*Intel"

$ glxinfo | grep "Device:.*Intel"
      Device: Mesa DRI Intel(R) Haswell Desktop  (0x412)

Try (this updates the PCI ID database):
sudo update-pciids

Then:
lspci -mm | awk -F '\\"|\\" \\"|\\(' '/"Display|"3D|"VGA/ {a[$0] = $3 " " $4} END {for(i in a) {if(!seen[a[i]]++) print a[i]}}'

I updated the database. The second command results in
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller

I'm unable to fix this as lspci and glxinfo both don't have the correct information. The best I can do is display Intel HD Graphics instead of the line Xeon Processor line above.
Try the latest master and let me know if it works.

It works.
 GPU: Intel HD Graphics

Thanks for responding quickly. Issue can be closed.


Tabs block

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #84
Test URLs:

Before: https://main--bitdefender--hlxsites.hlx.page/solutions/
After: https://feat-tabs--bitdefender--hlxsites.hlx.page/drafts/scoman/tabs1

For 2 columns the last empty column should not be displayed.

@andreibogdan , I've created https://github.com/hlxsites/bitdefender/pull/173 to address the two column feature issue.


[GLUTEN-5701][VL] Add overflow test case for from_unixtime function

What changes were proposed in this pull request?
After https://github.com/facebookincubator/velox/issues/9778 is fixed, add unit test for from_unixtime with overflowed argument and query config setted time zone
Fixes: https://github.com/apache/incubator-gluten/issues/5701
How was this patch tested?
Passed unit tests

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_5894_time.csv
log/native_master_05_29_2024_588faae35_time.csv
difference
percentage

q1
33.58
33.56
-0.022
99.93%

q2
23.73
23.85
0.121
100.51%

q3
36.79
37.37
0.580
101.58%

q4
32.34
32.42
0.079
100.24%

q5
68.50
69.83
1.335
101.95%

q6
7.55
7.54
-0.006
99.93%

q7
80.48
81.75
1.272
101.58%

q8
84.35
86.57
2.219
102.63%

q9
121.09
118.35
-2.737
97.74%

q10
45.84
44.16
-1.685
96.32%

q11
19.94
22.23
2.288
111.47%

q12
28.57
26.72
-1.854
93.51%

q13
51.83
53.60
1.774
103.42%

q14
23.32
17.59
-5.729
75.43%

q15
30.98
32.89
1.916
106.18%

q16
13.84
13.41
-0.432
96.88%

q17
101.65
103.62
1.974
101.94%

q18
144.38
144.53
0.148
100.10%

q19
16.48
13.59
-2.895
82.44%

q20
27.26
29.66
2.400
108.80%

q21
257.91
260.43
2.512
100.97%

q22
12.03
13.84
1.808
115.03%

total
1262.44
1267.50
5.066
100.40%


threadx supported?

Hello,  do we have some plans about supporting Threadx

Not unless we can find a ThreadX expert to contribute. If you see our readme, most support is from contributors. I own the extension but I cannot be an expert at every RTOS :-)
Btw, MS Embedded tools supports RTOS views and we complement each other. Install their extension. They have support for cortex-debug. Not sure which debugger you are using
https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-embedded-tools
We may not have feature parity but we display some of the same info. Good luck
Please close this issue unless you want to contribute., It is a lot of work, I warn you.

thanks very much, I've tried MS embedded tool, bus it still has some something wrong to show the usage


Max retries exceeded

2020-07-20 18:03:27,588 - INFO - Importing playlist ANIIML - We.Animals (2015)...
Traceback (most recent call last):
  File "importer.py", line 235, in <module>
    Importer(spotify_client_, yandex_client_, arguments.ignore).import_all()
  File "importer.py", line 192, in import_all
    item()
  File "importer.py", line 160, in import_playlists
    self._add_items_to_spotify(tracks, self.not_imported[playlist.title], save_tracks_callback, Type.TRACK)
  File "importer.py", line 100, in _add_items_to_spotify
    if item.available:
AttributeError: 'NoneType' object has no attribute 'available'
tu@inspiron3542:~/yandex2spotify$
tu@inspiron3542:~/yandex2spotify$ python3 importer.py -u<EMAIL_ADDRESS>-l<EMAIL_ADDRESS>-p db6aaeea312a1eeea2afc526051d3591
Traceback (most recent call last):
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connection.py", line 157, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/util/connection.py", line 61, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/lib/python3.6/socket.py", line 745, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 672, in urlopen
    chunked=chunked,
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 376, in _make_request
    self._validate_conn(conn)
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 994, in _validate_conn
    conn.connect()
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connection.py", line 334, in connect
    conn = self._new_conn()
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connection.py", line 169, in _new_conn
    self, "Failed to establish a new connection: %s" % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7f427feca2e8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tu/.local/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 720, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/home/tu/.local/lib/python3.6/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.music.yandex.net', port=443): Max retries exceeded with url: /account/status (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f427feca2e8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/utils/request.py", line 194, in _request_wrapper
    resp = requests.request(*args, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.music.yandex.net', port=443): Max retries exceeded with url: /account/status (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f427feca2e8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "importer.py", line 229, in <module>
    yandex_client_ = Client.from_credentials(arguments.login, arguments.password, captcha_callback=proc_captcha)
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/client.py", line 148, in from_credentials
    token = cls(*args, **kwargs).generate_token_by_username_and_password(username, password,
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/client.py", line 118, in __init__
    self.me = self.account_status()
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/client.py", line 34, in wrapper
    result = method(*args, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/client.py", line 262, in account_status
    result = self._request.get(url, timeout=timeout, *args, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/utils/request.py", line 239, in get
    timeout=timeout, *args, **kwargs)
  File "/home/tu/.local/lib/python3.6/site-packages/yandex_music/utils/request.py", line 198, in _request_wrapper
    raise NetworkError(e)
yandex_music.exceptions.NetworkError: HTTPSConnectionPool(host='api.music.yandex.net', port=443): Max retries exceeded with url: /account/status (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f427feca2e8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

Perhaps because of so many authorizations. For this, there is authorization by token)

Anyway this must be correctly handled

Is this playlist collective?

Is this playlist collective?

yes, it is public. https://clck.ru/PmRz5

I mean... Are there any other owners? Did you invite friends to add tracks in this playlist?

I mean... Are there any other owners? Did you invite friends to add tracks in this playlist?

no

playlist = importer.yandex_client.users_playlists_list(user_id='vlad.turchinskiy')[2]
playlist.collective
Out[5]: True

Seems like you push link "Invite a friend". I don't know how to do it no collective, but such problem has already appeared.

playlist = importer.yandex_client.users_playlists_list(user_id='vlad.turchinskiy')[2]
playlist.collective
Out[5]: True

Seems like you push link "Invite a friend". I don't know how to do it no collective, but such problem has already appeared.

playlist that user can create may be private or public.
may be "collective" means "public"?
there is no feature like "invite friend to create/modify playlist"

"Collective" doesn't mean "private" or "public". It means that more than one user can add tracks in this playlist. There is such feature.

It relate to this exception:
2020-07-20 18:03:27,588 - INFO - Importing playlist ANIIML - We.Animals (2015)...
Traceback (most recent call last):
  File "importer.py", line 235, in <module>
    Importer(spotify_client_, yandex_client_, arguments.ignore).import_all()
  File "importer.py", line 192, in import_all
    item()
  File "importer.py", line 160, in import_playlists
    self._add_items_to_spotify(tracks, self.not_imported[playlist.title], save_tracks_callback, Type.TRACK)
  File "importer.py", line 100, in _add_items_to_spotify
    if item.available:
AttributeError: 'NoneType' object has no attribute 'available'

But max retries exceeded exception seems like not issue for this project. May be for yandex-music-api.

@lemonpaul ok, how about "human readable" error message and exception handling?

There is exception handling from spotify, maybe there will be exception handling from yandex in future.


[android-sdk]  skipping authentication UI

I have an app using ChatSDK , it has login process using google sign-in , so it has its own authentication process , I just need to apply this info  in chat sdk , I wonder if there is anyway to skip the login/registration process used it ChatSDK?

Yes, as soon as you authenticate with Firebase, the Chat SDK will attach the necessary listeners and set itself up. If you want to skip login, just don't load your own activity instead of the splash screen activity.


python311Packages.pyunifiprotect: 5.0.2 -> 5.1.1

Diff: https://github.com/briis/pyunifiprotect/compare/refs/tags/v5.0.2...v5.1.1
Changelog: https://github.com/AngellusMortis/pyunifiprotect/releases/tag/v5.1.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 299735 run on x86_64-linux 1

7 packages built:

home-assistant-component-tests.unifiprotect
python311Packages.pyunifiprotect
python311Packages.pyunifiprotect.dist
python312Packages.pyunifiprotect
python312Packages.pyunifiprotect.dist
unifi-protect-backup
unifi-protect-backup.dist


Fix: "service is not running" error upon boot

As mentioned in https://github.com/rootzoll/raspiblitz/issues/1467 and https://github.com/rootzoll/raspiblitz/issues/1466 there's an issue regarding a falsely reported error (service is not running) upon boot if the bitcoind service hasn't finished warming up within 10min. This PR fixes that problem by checking if the variable bitcoinErrorFull contains the error code: -28, after the 10min threshold has been surpassed.
This has been tested on two devices (Pi4/P3) several times now. In fact it is now possible to lower the 10min uptime check: https://github.com/rootzoll/raspiblitz/blob/80de4054c66e4083055a1f7148eda4b7e831c8db/home.admin/80scanLND.sh#L66 In my experience there shouldn't be a problem halving (yay another one) it down to 5min.

Thanks - looks good. I think 10minutes is a good time window before displaying an error .. bitcoind is really not a quick starter in general.

Lowerd to 5min it wouldn't show an error, it would display The bitcoind service is warming up: Loading block index Please wait ... after 5min due to my check regarding "error code -28". It would offer users more info about what it is actually doing, then just "wait at least 10min".

@CandleHater used your commited fix - tested good :)


Enable THP in kernel

See https://github.com/siderolabs/pkgs/commit/2c5785b1639a22317a1f7775f0d1f4bd0b0a4b88

Actually it's already on, but it's CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y and SideroLabs went with CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y. Not sure if it's better switch to madvise.

Now using madvise.


this sux plez help

i made something in unity and when i exported it with the stl thing and put in my 3d slicer it was covered in the mesh filter object that i chose please help me

Please open a new issue with a specific question and more details about your problem.


example workflow issues

I've installed this custom node correct and I was able to run the example workflow with Cammy correctly, but when I tried to run another example workflow like this one:  Triplane_Gaussian_Transformers_to_3DGS(DMTet and DiffRast).json
I encountered the following errors:
[ERROR] An error occurred while retrieving information for the '[Comfy3D] Load Large Multiview Gaussian Model' node.
Traceback (most recent call last):
File "G:\3DComfyUI\ComfyUI\server.py", line 420, in get_object_info
out[x] = node_info(x)
^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\server.py", line 398, in node_info
info['input'] = obj_class.INPUT_TYPES()
^^^^^^^^^^^^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\nodes.py", line 1211, in INPUT_TYPES
"model_name": (get_list_filenames(os.path.join(ROOT_PATH, cls.checkpoints_dir)), ),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\shared_utils\common_utils.py", line 122, in get_list_filenames
return [f for f in listdir(directory) if isfile(join(directory, f)) and (extension_filter is None or f.lower().endswith(extension_filter))]
^^^^^^^^^^^^^^^^^^
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\checkpoints/lgm'
[ERROR] An error occurred while retrieving information for the '[Comfy3D] Load Triplane Gaussian Transformers' node.
Traceback (most recent call last):
File "G:\3DComfyUI\ComfyUI\server.py", line 420, in get_object_info
out[x] = node_info(x)
^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\server.py", line 398, in node_info
info['input'] = obj_class.INPUT_TYPES()
^^^^^^^^^^^^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\nodes.py", line 1013, in INPUT_TYPES
"model_name": (get_list_filenames(os.path.join(ROOT_PATH, cls.checkpoints_dir)), ),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\shared_utils\common_utils.py", line 122, in get_list_filenames
return [f for f in listdir(directory) if isfile(join(directory, f)) and (extension_filter is None or f.lower().endswith(extension_filter))]
^^^^^^^^^^^^^^^^^^
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'G:\3DComfyUI\ComfyUI\custom_nodes\ComfyUI-3D-Pack\checkpoints/tgs'
It seems like I'm missing a model/checkpoint.. related to Triplane Gaussian Transformers.. Could you point me to where to download the exact model/checkpoint needed for this.. thanks

I figured it out.. you go to here: https://huggingface.co/VAST-AI/TriplaneGaussian/tree/main to download the checkpoint and put the model into
ComfyUI\custom_nodes\ComfyUI-3D-Pack\checkpoints\tgs folder.

Glad you figured it out
If you don't have the checkpoint then it should download automatically, ok, maybe a bug, I'll take a look

Ok, it's an edge case I didn't take into consideration, this issue will be fixed in the next update


add travis-ci integration

Fixed by https://github.com/yashaka/selene/commit/001300c7be3acaa1c48538cb19fc387d9cf2228d
https://github.com/yashaka/selene/commit/aa43de1281e754a193372b7f7fe7447cb711df08


Implemented respondWithFile()

Ready for review.
Implemented according to the following requirements:

User should be able to just call a default method and the file should be automatically picked based on the api path that is mocked.
Users should be able to provide a default file name during set up.
User should be able to provide a default mocked data directory structure.
User should be able to override the default directory structure and filename when writing mocks.
Add feature to look for the response file in the absolute path based on variant. If file is not present then look for file a directory up than the variant to allow use of same response file.

can you merge smocks master into this code - there are merge conflicts

see https://github.com/jhudson8/smocks/pull/9


need to update the documentation

need some changes in documentation

I can add document section in the website which can provide the following details,please label it under GSSOC Ext.24 and Hactoberfest

@YadavAkhileshh  bro i rise this isue why u assigned him

tell sir i raised this issue and u assigned to him it's unfair

@YadavAkhileshh i am going to discord and tell this to gssoc

Sir,kindly provide label to it under GSSoc,Hacktoberfest

@AyutheCoder  issue is closed, so please raise another issue and proceed with working on it


Support the copy of multiprocess_iterator

This PR correctly fixes my problem.

Thank you! @t-abe

LGTM


[FEATURE] Preview Feature

Description
Is there any way to add preview option before user clicks on the get result button.
What I mean is if I want to generate gradient text and I am not sure about the colors so I am just trying different different colors, so if I can see how the final text with gradient will look on the same page, before clicking on get result.
Currently what is happening is that, for trying different different colors I have go back and forth between generator page and result page.
What do you think about this?
Screenshots
No response

It's great having you contribute to this project by creating an issue Make sure you are assigned to this before you work on it and you read the Contributing.md file, Thank you! Welcome to the community :nerd_face:

There's already a preview for colors and gradient

Hey @Dun-sin, can i work on this feature?


Low GPU usage

I train the model on my two Tesla M40 GPU. When I use nvidia-smi command to check the GPU usage, it always keeps on a low usage, and just one GPU is used.
How can I full use the two GPUs?
I've tried to increase the queue capacity and thread numbers, but it helps little.

@basuam The Python I used is Python 3.6.0 with Anaconda 4.3.1 (64-bit), and GPU version TensorFlow (1.1) is used.
When training, the two GPUs are used, but just one for computation.
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    2     19759    C   /home/train01/heyunchao/anaconda3/bin/python 21912MiB |
|    3     19759    C   /home/train01/heyunchao/anaconda3/bin/python 21794MiB |
+-----------------------------------------------------------------------------+

Only GPU 2 is used for computation, and the GPU-Util maintains at 0% in a long time.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.39                 Driver Version: 375.39                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla M40 24GB      On   | 0000:02:00.0     Off |                    0 |
| N/A   19C    P8    18W / 250W |      0MiB / 22939MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla M40 24GB      On   | 0000:03:00.0     Off |                    0 |
| N/A   21C    P8    17W / 250W |      0MiB / 22939MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Tesla M40 24GB      On   | 0000:83:00.0     Off |                    0 |
| N/A   37C    P0    65W / 250W |  21916MiB / 22939MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  Tesla M40 24GB      On   | 0000:84:00.0     Off |                    0 |
| N/A   32C    P0    57W / 250W |  21798MiB / 22939MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

@candlewill I believe there should be a slight modification in the code to allocate both GPUs because it's not the default for tensorflow. I cannot confirm because I've never trained it with more than one GPU but I do believe you must allocate both first manually otherwise tensorflow-gpu simply allocate one GPU. Have you trained other networks before without explicitly declaring which GPUs to use and checked if it has used them all?

To my understanding, maybe this is the reason: If multiple GPUs are not explicitly declared how to allocate, TensorFlow would choose the first GPU for computation as default, but use the memory of all GPUs.

candlewill's explanation is exact. I added train_multi_gpus.py for using multiple gpus.
@basuam @candlewill  Would you run and check the file? In my environment (3 * gtx 1080), the time for an epoch has decreased to almost 1/3. But I'm not sure if it's error-free because this is the first time I've written a code for multiple gpus.

@Kyubyong In the  current train.py code, the training is completely on CPU (see here ). I commented this line to allow use one GPU.
Then, I tried to compare the time cost of one epoch between train_multi_gpus.py and train.py. I find that, multi GPUs verstion takes a longer time about 220 seconds per epoch, while the single GPU version takes about 110 seconds.
My experiment environment is four Tesla K40m GPUs.

Did you run train_multi_gpus.py?

Yes, It takes a longer time about 220 seconds per epoch.

You changed the value of num_gpus in the hyperparams.py, did you?

Yes, I changed the value into 4.

One possibility is the batch size. If you have 4 gpus, you have to multiply the batch size by 4 for a fair comparison. If you see the code, mini-batch samples are split into 4 so each is fed in each gpu tower.

@candlewill Oh, and I removed the line of tf.device('/cpu:0'). I forgot to remove it. Thanks.

@candlewill Did you find why the multi gpu version is slower than the single gpu one? For me, the former is definitely way faster than the latter.

I forgot to increase the value of batch_size by multiply with num_gpus when training.

I am running in a similar issue: GPU usage (AWS p2.xlarge, Deep Learning CUDA 9 Ubuntu AMI) is on average low, while CPU usage is always at peak.
Using python 2.7 or 3 doesn't make any difference.
It's like the GPU is used for some particular task only which is seldomly invoked.
ubuntu@ip-172-31-13-191:~$ nvidia-smi
Sat Nov  4 08:20:19 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.81                 Driver Version: 384.81                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla K80           On   | 00000000:00:1E.0 Off |                    0 |
| N/A   75C    P0    93W / 149W |  10984MiB / 11439MiB |     50%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     10238      C   python3                                    10971MiB |
+-----------------------------------------------------------------------------+
ubuntu@ip-172-31-13-191:~$ nvidia-smi
Sat Nov  4 08:20:24 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.81                 Driver Version: 384.81                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla K80           On   | 00000000:00:1E.0 Off |                    0 |
| N/A   75C    P0    73W / 149W |  10984MiB / 11439MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     10238      C   python3                                    10971MiB |
+-----------------------------------------------------------------------------+
ubuntu@ip-172-31-13-191:~$

.

@candlewill - I am facing same issue of low GPU usage as indicated by @aijanai . Could you please indicate which line did you comment to get full utilization on single GPU? The line which is mentioned by you in your comment is already commented in the code as it stands now and yet the performance is slow, hence the confusion.

candlewill's explanation is exact. I added train_multi_gpus.py for using multiple gpus.
@basuam @candlewill Would you run and check the file? In my environment (3 * gtx 1080), the time for an epoch has decreased to almost 1/3. But I'm not sure if it's error-free because this is the first time I've written a code for multiple gpus.

Can you please share train_multi_gpus.py.? It is not available now. And with train.py, I cant train on the GPUs.


Failed to execute 'insertBefore' on 'Node': with useAsyncData and Pre-Rendering

Environment

Operating System: Darwin
Node Version:     v20.11.1
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, nitro, runtimeConfig, app, modules, postcss, storyblok, image, plausible, sitemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Link: https://prisma-steuerberatung.netlify.app/blog
I can try to produce a reproduction with Stackblitz if that helps to share the code.
Describe the bug
Hi!
I have created a website that uses SSR and Prerendering. Everything works locally when using dev, but a strange problem appears when I deploy it to Netlify or preview the build locally via serve.
Here is the issue:

The website loads blog-posts from an api that I have build in /server.
On first load of the page (e.g. via direct link) the content is visible and looks good
When I navigate manually to that same page via a nav button, the content is not rendered anymore and the error on the console appears.
I fully reload the page: all ok again.

Here is a GIF of the issue:

Link to test it yourself: https://prisma-steuerberatung.netlify.app/blog
What am I doing wrong here?
Any help appreciated 🙏
Additional context
Here is the code of the index.vue to load the blogposts:

<template>

                <PageHeader
                    :blok="{
                        headline: 'Blog',
                        text: 'Im PRISMA Steuerblog finden Sie regelmäßig praxisnahe und aktuelle Steuernews. Hier informieren wir Sie über wichtige Änderungen und Neuigkeiten aus der Steuerwelt.',
                    }" />

                    <NewsArticleCard :post="article" v-for="article in data" :key="article.id" />

</template>

There are also similar issues like https://github.com/nuxt/nuxt/issues/24045 or https://github.com/nuxt/nuxt/issues/13656 where this error occured.
Logs
TypeError: Failed to execute 'insertBefore' on 'Node': parameter 1 is not of type 'Node'.
    at insert (Dv3nVqiQ.js:18:178)
    at ft (Dv3nVqiQ.js:14:41813)
    at ft (Dv3nVqiQ.js:14:41556)
    at ft (Dv3nVqiQ.js:14:41400)
    at ft (Dv3nVqiQ.js:14:41400)
    at ft (Dv3nVqiQ.js:14:41400)
    at Object.resolve (Dv3nVqiQ.js:14:7745)
    at pr (Dv3nVqiQ.js:14:42980)
    at He (Dv3nVqiQ.js:14:42086)

I'm guessing this issue might be related to #13350. Would you like to try the following method? It may help solve the error you encountered.

Thanks, @Mini-ghost.
Unfortunately, it does not solve the issue.
Now, when I am in npm run dev mode, the error also appears with the following console errors:

In the generated build, it also does not work and the errors are:

Why is there a 404 error in the generated-version? Isn't that supposed to be loaded in the SSR-Process?

I apologize, but I suspect this issue might be related to other components in your project. The method provided above is merely a workaround and does not truly solve the problem. If you could provide a minimal reproducible example, other developers in the community might be better able to help you clarify the issue.

I am currently traveling. I will provide a reproduction early next week.
Thanks for the help, everyone.

Update:
I created a reproduction of this issue and removed things that are unrelated to the /blog issue. @Mini-ghost seems to be right - the problem stops and everything seems to be okay.
Here is the deployment of the branch: https://66447bc136ba9b78c1cebb85--cute-duckanoo-2e84be.netlify.app/blog
Blog-Content is pre-rendered perfectly. No issue is visible and the content is shown.
I will go on and try to localize which component/module caused the issue.

Update 2:
I spent another couple of hours and was able to locate the issue:
I noticed that for some page navigation it worked (blog content loaded) and for some the error (insertBefore) occurred. The failing pages can one thing in common: I used a layout with a fancy SVG issue.
So I went ahead and removed all svg-backgrounds and surprisingly the error stopped and the page is now loading the prerendered content perfectly: https://prisma-steuerberatung.netlify.app/blog
Here is how I used the layouts in pages-SFCs:

File: layout/with-background.vue:
<template>

        <HeaderComponent />
        <slot />

</template>

I tried both: with ?inline and without for the svg background-image.
Any clue what might cause the issue?

I found the reason by comparing my layouts and reading the docs again:

Unlike other components, your layouts must have a single root element to allow Nuxt to apply transitions between layout changes - and this root element cannot be a .

Unfortunately, my layouts did not have one root-node.  This caused the problem. I am so glad it is working now 🎉
Suggestion: Can Nuxt show a console error if layout does not have a single root element?

For what its worth, I have an Index page that just redirects to another page:
index.ts
export default defineComponent({
    async render () {
        await navigateTo('/images')
    }
})
``

Removing async/await fixes the issue for me.


Dev-datamigration-Microsoft.DataMigration-2022-03-30-preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

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

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

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

Change to data plane APIs
Adding new properties
All removals

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

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

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

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

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@raych1 Can you take a look at this model validation error ? seems the discriminator value has already been added in the taskType definition. Is this a bug for model validation ?

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{sqlDbInstanceName}/providers/Microsoft.DataMigration/databaseMigrations/{targetDbName}": {

rename to migration name. Assuming this does not have to match the targetdb name ?

Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:19 in 7eb26c8. [](commit_id = 7eb26c84f50274e95658c4dfc02ac0a15c40f78b, deletion_comment = False)

        "name": "migrationOperationId",

So I assume everytime you create this databaseMigrations resource it starts a new Migrationoperation and then. It might have been better to have a separate resource that defines the migration and one to define the migration configuration . so you could have a history of operations etc and they are 2 separate things. But I see that you have already implemented this in this fashion for the managedinstance .. So it is fine if you want to keep this consistent but consider if this is something you would want in the future.

Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:40 in 7eb26c8. [](commit_id = 7eb26c84f50274e95658c4dfc02ac0a15c40f78b, deletion_comment = False)

    },

Why is the scope duplicated here ? It seems like since this is an extension resource the scope is defined by the resource itself ?

Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:1262 in 7eb26c8. [](commit_id = 7eb26c84f50274e95658c4dfc02ac0a15c40f78b, deletion_comment = False)

    },

What happens if the user provides a different scope here from the uri scope ?

In reply to:<PHONE_NUMBER>

Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:1262 in dad3b90. [](commit_id = dad3b90cf442206537fe0c525221c476a6cc520c, deletion_comment = False)

        "description": "The child resources to include in the response.",

Update description.

Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:50 in 7eb26c8. [](commit_id = 7eb26c84f50274e95658c4dfc02ac0a15c40f78b, deletion_comment = False)

    },

Why is the scope duplicated here ? It seems like since this is an extension resource the scope is defined by the resource itself ?
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:1262 in 7eb26c8. [](commit_id = 7eb26c8, deletion_comment = False)

Yes, this is a proxy resource. Scope in the request body is to validate permission. When you send request, arm first validates that user has permission on MI/VM/SQLDB. Arm can validate permission on property in input, so we have specified 'scope' in manifest as the property to be validated.

    },

What happens if the user provides a different scope here from the uri scope ?
In reply to:<PHONE_NUMBER>
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:1262 in dad3b90. [](commit_id = dad3b90, deletion_comment = False)

We return an error in that case. Invalid value provided for parameter 'Scope'.

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{sqlDbInstanceName}/providers/Microsoft.DataMigration/databaseMigrations/{targetDbName}": {

rename to migration name. Assuming this does not have to match the targetdb name ?
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:19 in 7eb26c8. [](commit_id = 7eb26c8, deletion_comment = False)

This operation actually creates a targetDb with the given name in target platform like SQL MI, SQL VM and SQL DB. That is why we have added targetDbName to the parameter to be more clear.

        "name": "migrationOperationId",

So I assume everytime you create this databaseMigrations resource it starts a new Migrationoperation and then. It might have been better to have a separate resource that defines the migration and one to define the migration configuration . so you could have a history of operations etc and they are 2 separate things. But I see that you have already implemented this in this fashion for the managedinstance .. So it is fine if you want to keep this consistent but consider if this is something you would want in the future.
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:40 in 7eb26c8. [](commit_id = 7eb26c8, deletion_comment = False)

In our backend we do have a distinction between migrations and migration configuration, there is only one entity object that uniquely identifies the migration resource and, each time it generates new FSM operations, but there is only one underlying migration entity object.

        "description": "The child resources to include in the response.",

Update description.
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:50 in 7eb26c8. [](commit_id = 7eb26c8, deletion_comment = False)

Done

    },

Why is the scope duplicated here ? It seems like since this is an extension resource the scope is defined by the resource itself ?
Refers to: specification/datamigration/resource-manager/Microsoft.DataMigration/preview/2022-03-30-preview/sqlmigration.json:1262 in 7eb26c8. [](commit_id = 7eb26c8, deletion_comment = False)

Yes, this is a proxy resource. Scope in the request body is to validate permission. When you send request, arm first validates that user has permission on MI/VM/SQLDB. Arm can validate permission on property in input, so we have specified 'scope' in manifest as the property to be validated.

You dont need to do this since the scope permission is implicit since it is an extension resource. User will not be able to do add the extension resource unless they have permissions on the base resource. Are you looking for some higher level of permissions here ?

You dont need to do this since the scope permission is implicit since it is an extension resource. User will not be able to do add the extension resource unless they have permissions on the base resource. Are you looking for some higher level of permissions here ?

Yes, we are looking for write permission on the resource. This is what we have in manifest:

Had offline discussion with Ashutosh. Signing off from ARM side.

@raych1 Could you take a look at the model validation error, it looks like a false alarm.

/azp run

/azp run


update dlp dependency version range

current version range for google-cloud-dlp leads to automatic downgrade to version 1.0.0 of any dlp module that was installed prior to installation of the apache_beam[gcp].
the fix increasing the upper boundary of the version range for google-cloud-dlp dependency to allow versions 3.* of the dlp package.
without this change installation of the apache_beam[gcp] after google-cloud-dlp leads to downgrade of the dlp to version 1.*.
Please add a meaningful description for your change here

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.

Run Python 3.7 PostCommit

R: @tvalentyn

Postcommit failure is a known issue tracked in BEAM-13218.


Update README.md

Fixer.io need an api key > https://fixer.io/documentation

* Currently, the only accepted inputs for the Auth field are as follows:

OAuth - the API supports OAuth
apiKey - the API uses a private key string/token for authentication - try and use the correct parameter
X-Mashape-Key - the name of the header which may need to be sent
No - the API requires no authentication to run

Hi @mlescaudron , thanks for the PR. Please update the Auth field to apiKey.

Bump

Fixed in 0274029d96e966e2766b78b35928b9273f76a592


[ECS] Configure block for e.g. LineLengthFixer doesn't work after upgrade 9.3.12

This configuration isn't respected anymore after the update.
  $services->set(LineLengthFixer::class)
      ->call('configure', [[
          LineLengthFixer::LINE_LENGTH => 140,
          LineLengthFixer::INLINE_SHORT_LINES => false,
     ]]);

This something change in this regard that I'm not aware of?

Hi Tomas,
it should be working.
Could you provide minimal failing test fixture and add it here?
https://github.com/symplify/symplify/tree/main/packages/coding-standard/tests/Fixer/LineLength/LineLengthFixer/Fixture
Copy paste one of files and add your input content + expected output

I'll try to provide a test.

But how do I add the Rules configuration to the test? E.g. LineLengthFixer::LINE_LENGTH => 140

If I correct the value directly in the LineLenghtFixer Class and not over the configure block it works like expected.

According to the code, it should still be respected:
public function configure($configuration = null)
    {
        $this->lineLength = $configuration[self::LINE_LENGTH] ?? self::DEFAULT_LINE_LENGHT;
        $this->breakLongLines = $configuration[self::BREAK_LONG_LINES] ?? \true;
        $this->inlineShortLines = $configuration[self::INLINE_SHORT_LINES] ?? \true;
    }

Hi @TomasVotruba
I think I have found the "problem"
If I get the code correct, the LineLengthFixer will be included in the Symplify set here:
https://github.com/symplify/symplify/blob/main/packages/coding-standard/config/symplify.php#L21
So when moving my
$services->set(LineLengthFixer::class)
      ->call('configure', [[
          LineLengthFixer::LINE_LENGTH => 140,
          LineLengthFixer::INLINE_SHORT_LINES => false,
     ]]);

to after the $containerConfigurator->import(SetList::SYMPLIFY); then it works like before.
I know from earlier troubles that I had that load order was important, so perhaps this should be updated in the documentation, unless I'm wrong of course. :)

Hi Tomas, I'm happy you've found the weak spot :+1:
I was thinking about throwing an exception and informing the user. But this is how Symfony configs work on purpose, so people can decorate the imported services in their own way.
Yet, updating the documentaiton would be helpful! Could you send a PR with a notice?

Sure. For this README?
https://github.com/symplify/symplify/blob/main/packages/easy-coding-standard/README.md

Yes :+1:

This is "solved" with the documentation update in #3306