Live test broken with Python 3.11

https://github.com/Azure/azure-cli/pull/25055 uses self._outcome.errors to check the test result:
https://github.com/Azure/azure-cli/blob/674625c388b36ad684e3531bec2c67cde6e00018/src/azure-cli-testsdk/azure/cli/testsdk/scenario_tests/base.py#L166
However, Python 3.11 made a change in https://github.com/python/cpython/pull/28180 that no longer buffers the errors in _Outcome. The errors are immediately sent to result and errors attribute is removed from _Outcome, causing failure during Azure CLI's live run:
> azdev test test_role_assignment_scenario --live
...
self = <azure.cli.command_modules.role.tests.latest.test_role.RoleAssignmentScenarioTest testMethod=test_role_assignment_scenario>
args = ()

    def _save_recording_file(self, *args):  # pylint: disable=unused-argument
        if self.in_recording and self.cassette.dirty:
            self.cassette._save()  # pylint: disable=protected-access
>           if self._outcome.errors or self._outcome.skipped:   # pylint: disable=protected-access
E           AttributeError: '_Outcome' object has no attribute 'errors'

src\azure-cli-testsdk\azure\cli\testsdk\scenario_tests\base.py:166: AttributeError

https://stackoverflow.com/a/39606065/2199657 suggests to check self._outcome.result.errors and claims this approach is compatible with pytest, but it is actually not. When invoked by pytest, _pytest.unittest.TestCaseFunction is passed to unittest.case.TestCase.__call__ as result. As _pytest.unittest.TestCaseFunction doesn't have errors attribute, pytest fails:
E       AttributeError: 'TestCaseFunction' object has no attribute 'errors'

unittest.case._addError calls addError on the result object, making retrieving the errors from result test-runner-dependent: https://github.com/python/cpython/blame/2258d6cfa2fcd0c290328e81b68aff25abf8c3d8/Lib/unittest/case.py#L74, https://github.com/python/cpython/blame/2258d6cfa2fcd0c290328e81b68aff25abf8c3d8/Lib/unittest/case.py#L99

https://github.com/Azure/azure-cli/pull/27649 disabled the temporary recording file functionality, thus bypassing this issue, but let's keep it open until we figure out an elegant way of retrieving the test result from a cleanup function.


Load bitmasks stored in OME-XML

User story
GeoMx outputs store the "segments" in binary fields within the OME-XML
Preferred solution
Add a fileType for obsSegmentations.ome-tiff-xml (as opposed to obsSegmentations.ome-xml which in theory could also be added in the future for pointing to XML files stored outside of the OME-TIFF)

See Jupyter notebook at https://gist.github.com/keller-mark/37e8095d095da2828413b864644662ff


[Improvement] add support for SinkRequest that has multiple statement

What changes were proposed in this pull request
This is a improved version of  #2919 .
Sorry to say that I found a bug on our production env.
Brief change log

Refactor val SinkRequest.sqlStatement: group and combine statements by the part before ‘values’ in insert statements.
Refactor ClickHouseWriterTask.buildRequest: build List of Request by SinkRequest.sqlStatement.

Verifying this change

This change is just tested (and passed) on our production env, not tested by unit test code.
Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

Thank you for your contribution! Can you provide corresponding test cases, please? 😊

Sure, since the core part of this commit change is SinkRequest.sqlStatement, the change within ClickHouseWriterTask is just to add a loop to support List variable, so I add a unit test for SinkRequest.sqlStatement, see the file SinkRequestTest.scala please.

And I also added some comments to explain the changes.

And I also added some comments to explain the changes.

Good job. Thanks for your contribution. 👏 Keep up the great work and continue participating in the project. We are looking forward to your future contributions! 😊


lxd-ui: 0.12 -> 0.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for lxd-ui is: Web user interface for LXD
meta.homepage for lxd-ui is: https://github.com/canonical/lxd-ui
meta.changelog for lxd-ui is: https://github.com/canonical/lxd-ui/releases/tag/0.8.5
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS

[!CAUTION]
A test defined in passthru.tests did not pass.

found 0.8.5 with grep in /nix/store/dq2hdgkydw2nqx93dscwfbj41xwl2337-lxd-ui-0.8.5
found 0.8.5 in filename of file in /nix/store/dq2hdgkydw2nqx93dscwfbj41xwl2337-lxd-ui-0.8.5

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

lxd-ui

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/9e2f00688dfa897b3e6fdb99e88352e0b16ed4c7#lxd-ui

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

lxd-ui

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for lxd-ui is: Web user interface for LXD
meta.homepage for lxd-ui is: https://github.com/canonical/lxd-ui
meta.changelog for lxd-ui is: https://github.com/canonical/lxd-ui/releases/tag/0.14
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.14 with grep in /nix/store/qwjmz1mhqkwsw4ijy67bixr41w7ks5k1-lxd-ui-0.14
found 0.14 in filename of file in /nix/store/qwjmz1mhqkwsw4ijy67bixr41w7ks5k1-lxd-ui-0.14

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

lxd-ui

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/c708539fb4409064f3238996a8e4d8b3451e991b#lxd-ui

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

lxd-ui

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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


[UIE-76] Add external link component

https://broadworkbench.atlassian.net/browse/UIE-76
Links to pages outside of Terra are currently coded like:
<Link href={url} {...Utils.newTabLinkProps}>
  {text} <Icon icon="pop-out" size={12} style={{ marginLeft: ... }} />
</Link>

To simplify this common pattern, this adds an ExternalLink component to the components package. The former example can now be written as:
<ExternalLink href={url}>{text}</ExternalLink>

Story: https://65fc89c9335768720ff8605a-hhqsseohiz.chromatic.com/?path=/docs/packages-components-externallink--docs

Can I talk you into adding a Storybook story for this?


Different width between braces and character with font hermit

Issue

I really love this font hermit, hope someone can fix it.
my .hyper.js

Seems hermit is broken 😢


docs: Add user guide for starring messages

Initial message starring commit, suggestions welcome

Automated message from Dropbox CLA bot
@picapi, it looks like you've already signed the Dropbox CLA. Thanks!

@picapi, minor feedback. Looks good otherwise.

You'll probably need to squash your commits into a single commit called docs: Add user guide for starring messages like your initial commit.

Please fix conflicts first.

This is messy give me a bit to sort this out


LavaLink song name bug

Type

[x] Functions: <$lavalinkExecute>
[x] Callbacks: <bot.onMessage()>
[x] Handlers: <none>

Code used:
bot.command({
    name: "queue",
    code: `
    $title[1;Player's queue]
    $image[1;$lavalinkExecute[getthumbnail;$lavalinkExecute[songinfo;identifier];hqdefault]]
    $description[1;Now playing [$lavalinkExecute[songinfo;title]]($lavalinkExecute[songinfo;url])
$lavalinkExecute[queue]
$suppressErrors[no songs in queue]
    $color[1;RANDOM]
   `
});

More:

Aoi.js version:5.0.8
Node.js version:17.0.1
Operating system:Android 8

The first assigned song will not show as its already in queue and being played, due the songInfo code itself, after any songs being in queue will show.

Eventually It shows the recently added song as now playing too. I used trackID as 0 but still no affect


Android Studio Layout preview not rendering

The FreeFlowContainer is causing issues in the layout preview of Android Studio causing it not to render:
"Rendering Problems Exception raised during rendering: onMeasure() did not set the measured dimension by calling setMeasuredDimension()"

I have also found this error too. I posted in #78

I did a quick and dirty fix to get the preview working again.
In the init function of the FreeFlowContainer add this:
if(isInEditMode())
setVisibility(GONE);


JitterBuffer: Interceptor

Description
This implements a RemoteStream jitter buffer interceptor.

@thatsnotright Could you look at my issue please?


Enhance student summary

As an instructor, when you click on the student summary, the screen should default with everything visible. There will then be an option to go into student review mode where its just for the student. When leaving the student review mode, warning that things will become visible again.

When clicking on a student's grade summary, the lightbox window that opens should provide the following:
Default view - "Instructor View"

In the default view, all content behind the lightbox remains visible.
All grades/items should be visible, regardless of their release state.
Iconography from the item column should be represented, denoting EC, unreleased, not included in grade calc.
Text should denote if course grade is not visible to students.
Ability to navigate to previous / next student.

"Student View"

Once in Student View, background becomes opaque.
Should reflect student's view, with unreleased grades/items not appearing.
If an item in a column is not released, the category subtotal grade should be hidden.
No ability to navigate to previous / next student.

If exiting the Student View, provide a warning message.

Hi @steveswinsburg - just bouncing this one to you for some help.  The last requirement for this modal is a confirmation popup when closing the Wicket window, as per:

...is it possible to introduce an additional confirmation lightbox window that opens on top of the "Student Review" mode when you try to exit out, letting you know that you're about to surface other students' grades?

Happy to hack at it if you can point me in the right direction!

Hi @payten ,
Looks great. I made a few add'l notes in #186 .

Cool I think we can close this one. More stuff tracked in #186.

This one was unable to be migrated.


The front and the back doesn't have the same filtering results

when filtering from the dashboard, the number of samples in the selection is different from when it is processed by the backend

Not an issue since we removed the filtering feature ¯_(ツ)_/¯


Gracefully handle failures caused by a YouTube video that requires access to be granted by its owner

[x] I'm reporting a site feature request
[x] I've verified that I'm running youtube-dl version 2020.12.05

% youtube-dl --version
2020.12.05
%

[x] I've searched the bugtracker for similar site feature requests including closed ones

The closest matches I see are:

#25635 ('Invalid' for unrelated reasons), which actually shows the behavior I am requesting.  That behavior appears to have been lost.
#23788 which is about not aborting a playlist after failing on a private video.

Description
The following is from a private video.  When accessing the URL from a web
browser, not logged into YouTube, the site says "If the owner of this video has
granted you access, please sign in."
Per issue # 25635 it appears that in such cases 'youtube-dl' used to report,

"ExtractorError: Content Warning
If the owner of this video has granted you access, please sign in.
This video is private."

which gives the user an indication of why the download failed.
But that no longer occurs; an ExtractorError is still raised but with no information as to why:
% cat /etc/mx-version
MX-19.3_x64 patito feo October 21, 2019
% /usr/bin/python3 --version
Python 3.7.3
%
% youtube-dl --verbose https://www.youtube.com/watch?v=cyJHA_jrzaI
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=cyJHA_jrzaI']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.12.02
[debug] Python version 3.7.3 (CPython) - Linux-4.19.0-6-amd64-x86_64-with-MX-19.3-patito_feo
[debug] exe versions: ffmpeg 4.1.6, ffprobe 4.1.6
[debug] Proxy map: {}
[youtube] cyJHA_jrzaI: Downloading webpage
[youtube] cyJHA_jrzaI: Downloading embed webpage
[youtube] cyJHA_jrzaI: Refetching age-gated info webpage
WARNING: Unable to extract video title
ERROR: no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 803, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 824, in __extract_info
ie_result = ie.extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 532, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 2060, in _real_extract
raise ExtractorError('no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info')
youtube_dl.utils.ExtractorError: no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
%
TIA for looking at this.

Oops, I just noticed that while I had updated youtube-dl to 2020.12.05 before submitting the issue, the transcript of its invocation that I included was from before then, using 2020.12.02.  Apologies for that.
I am now at 2020.12.07 and its behavior is the same as above:
% youtube-dl --verbose https://www.youtube.com/watch?v=cyJHA_jrzaI
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=cyJHA_jrzaI']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.12.07
[debug] Python version 3.7.3 (CPython) - Linux-4.19.0-6-amd64-x86_64-with-MX-19.3-patito_feo
[debug] exe versions: ffmpeg 4.1.6, ffprobe 4.1.6
[debug] Proxy map: {}
[youtube] cyJHA_jrzaI: Downloading webpage
[youtube] cyJHA_jrzaI: Downloading embed webpage
[youtube] cyJHA_jrzaI: Refetching age-gated info webpage
WARNING: Unable to extract video title
ERROR: no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 803, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 824, in __extract_info
ie_result = ie.extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 532, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 2060, in _real_extract
raise ExtractorError('no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info')
youtube_dl.utils.ExtractorError: no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
%

Now, not private and handled OK.


Work around for "nullable columns" limitation for PRIMARY KEY

Hi,
Would you please advise me what is the workaround for the PRIMARY KEY column, when we change it to "nullable" on Ledger? because, when I change the PRIMARY KEY column to "nullable", I encountered the error:
"cannot define PRIMARY KEY constraint on nullable column in table 'something' "
Thanks

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

ID: 4e744313-602f-e640-86c5-ac4622fe1258
Version Independent ID: 91d1bb32-7704-02d3-eb58-c4498a62aaf7
Content: Limitations for Azure SQL Database ledger - Azure SQL Database
Content Source: azure-sql/database/ledger-limits.md
Service: sql-database
Sub-service: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@AminAvan Thank you for your question. I think this is one of the limitations in Azure SQL Ledger.
@VanMSFT Could you please confirm that.

Therefore, we cannot have PRIMARY KEY on Azure Ledger SQL database?!
If you cannot have a PRIMARY KEY on the database, then your database is not SQL (relational database)!!

@AminAvan, I meant to say in Azure Ledger Primary key cannot be nullable.
@VanMSFT Could you please share your inputs on the below question.

Ok, but the Azure Ledger cannot accept non-nullable columns as well !!
"Only nullable columns can be added to ledger tables, and when they aren't specified WITH VALUES."
so what about a PRIMARY KEY on a table, that is non-nullable column?

I am wondering that I could run following table and PRIMARY KEY (i.e., AccidentID) on Append-only table on Azure Ledger SQL:
creating a table
CREATE SCHEMA [Accident6]
CREATE TABLE [Accident6].[AccidentReport6]
(
[AccidentID] INT NOT NULL PRIMARY KEY CLUSTERED,
[OfficerID] CHAR (255) NOT NULL CHECK(len(OfficerID) >= 2),
[Location] CHAR (255) NOT NULL CHECK(len(Location) >= 2),
[GeoLocation] geography,
[AccidentImagesLinks] VARCHAR (2090),    -- The maximum length of URL is 2,083 characters
[AccidentVideosLinks] VARCHAR (2090),    -- The maximum length of URL is 2,083 characters
[AccidentAudioLinks] VARCHAR (2090),    -- The maximum length of URL is 2,083 characters
)
WITH (
LEDGER = ON (
APPEND_ONLY = ON
)
);
But now, I have a problem with the PRIMARY KEY of tables of a database that is defined by Entity Framwork?!
Thanks

Hey @Pietervanhove - Can you please help with this question?

Hi @AminAvan,
A primary key column can never contain a NULL value. Not even on a normal table. See
https://docs.microsoft.com/en-us/sql/relational-databases/tables/create-primary-keys?view=sql-server-ver15#Restrictions
That said, you can create a ledger table with a primary that is set to NOT NULL. The example of the append-only table that you posted will work. If you want to change your schema of your ledger table after it was created, you can only add nullable columns.
Hope this helps.
Best regards
Pieter


Use videos files instead of camera for developement

In order to ease tests and developpements for projects in any kind i would like to read, in the OpenMV IDE, video files from computer or/and sd card.
If it's possible it will be really great !

Same question here....

It's on the todo list.

This is now fixed. The IDE will be able to convert video files to the ImageWriter file format so you can pull from that.


[admission-control] Add service test into lib

Motivation
Adding AC service test into service lib so that cargo x test command can pick it up.
Test Plan
Test now runs with either:
cargo x test -p admission-control-service or cargo xtest in admission-control/admission-control-service directory

@bors-libra r+

:pushpin: Commit ca5cae4 has been approved by phlip9

:hourglass: Testing commit ca5cae4161c7323da53438a929e35575cd6d4803 with merge 3f69db8034fe3de6fc4ddb052733e0f2685a25ac...

:broken_heart: Test failed - checks-circle_commit_workflow

Looks like smoke_test::test_startup_sync_state is flaky for some reason... I don't see how it could fail from turning on this unit test. Let's just retry: @bors-libra retry

bors pls @bors-libra r+

:bulb: This pull request was already approved, no need to approve it again.

There's another pull request that is currently being tested, blocking this pull request: #1627

:pushpin: Commit ca5cae4 has been approved by phlip9

:hourglass: Testing commit ca5cae4161c7323da53438a929e35575cd6d4803 with merge 73355c46c2c2b5822d507d17bebf66b9c57f4628...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: phlip9
Pushing 73355c46c2c2b5822d507d17bebf66b9c57f4628 to master...


Replace Failed Node Command replaces the wrong node!

I have several failed nodes in my network including Node 51 and Node 54.
I requested a replace failed node for Node 51.. and tried to include the switch (Zooz Zen26 if it matters)
The application ended up replacing the failed node 54 instead of 51 with this new switch.
My version info is
App Version - 2.1.1
Zwavejs Version - 6.6.0
Zwavejs-server Version - 1.1.0
I did not capture debug logs - I can try to recreate the issue.. but here is the info log I captured.
16:15:02.838 CNTRLR   starting replace failed node process...
16:15:02.838 CNTRLR » [Node 051] pinging the node...
16:15:03.610 CNTRLR   [Node 051] Node 51 did not respond after 1 attempts, it is presumed dead
16:15:03.613 CNTRLR   [Node 051] ping failed: Failed to send the command after 1 attempts (Status No
                      Ack)
16:15:03.770 CNTRLR   handling replace node request (status = FailedNodeReplace)
16:15:03.771 CNTRLR   The failed node is ready to be replaced, inclusion started...
16:15:32.838 CNTRLR   stopping inclusion process...
16:15:32.897 CNTRLR   handling add node request (status = Done)
16:15:32.897 CNTRLR   done called for 54
16:15:32.898 CNTRLR   the inclusion process was stopped
16:16:06.393 CNTRLR « [Node 054] Received updated node info

Will open with right format


Fix hardcoded PNR paths

We are having to copy a lot of files back and forth right now because PNR assumes certain locations to find primitive JSON, lef file, map file etc. Need to make these user configurable so that they can be modified by the caller. For more details see:
https://github.com/ALIGN-analoglayout/ALIGN-public/blob/1aa38f9adb25b81acf80e196f34b4b6fab9a7cc7/align/pnr/main.py#L102

Need some mechanism to control what files from the python side so that we can avoid copying files over.
Basically the directory structure is dictated by the C++ code right now and needs relaxation.


$guild->members returning only the bot user

Hi
When i'm trying to run this:
$guild = $message->channel->guild;
$member = $guild->members;
echo PHP_EOL . "Detected: " . count($member);
I get only the bot user detected.

Use $discord->members

(I recently ran into this too) If I recall properly, it's because you, as the owner of the guild, are technically not a member.
If you do $guild->members->fetch("YOUR-MEMBER-ID")->done(function($member) { print_r($member);}); then you will find your member.

Make sure the guild member priviliged intents are enabled in your Discord developer settings:

Thanks everyone ! Looks like davidcole1340 was right!


Improve error message for arg type unsupported during typing.

As title.

This make the error message look like e.g.:
$ ipython
Python 3.6.5 |Anaconda, Inc.| (default, Apr 29 2018, 16:14:56)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.4.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import numpy as np

In [2]: from numba import njit

In [3]: njit(lambda : np.linalg.svd([1]))()
---------------------------------------------------------------------------
TypingError                               Traceback (most recent call last)
<ipython-input-3-0393378f98ef> in <module>()
----> 1 njit(lambda : np.linalg.svd([1]))()

<env>/numba/dispatcher.py in _compile_for_args(self, *args, **kws)
    347                 e.patch_message(msg)
    348
--> 349             error_rewrite(e, 'typing')
    350         except errors.UnsupportedError as e:
    351             # Something unsupported is present in the user code, add help info

<env>/numba/dispatcher.py in error_rewrite(e, issue_type)
    314                 raise e
    315             else:
--> 316                 reraise(type(e), e, None)
    317
    318         argtypes = []

<env>/numba/six.py in reraise(tp, value, tb)
    656             value = tp()
    657         if value.__traceback__ is not tb:
--> 658             raise value.with_traceback(tb)
    659         raise value
    660

TypingError: Failed at nopython (nopython frontend)
Invalid use of Function(<function svd at 0x7f6a8092db70>) with argument(s) of type(s): (list(int64))
 * parameterized
In definition 0:
    TypingError: np.linalg.svd() only supported for array types
    raised from <path>/numba/numba/targets/linalg.py:739
This error is usually caused by passing an unsupported argument type to the named function.
[1] During: resolving callee type: Function(<function svd at 0x7f6a8092db70>)
[2] During: typing of call at <ipython-input-3-0393378f98ef> (1)

File "<ipython-input-3-0393378f98ef>", line 1:
njit(lambda : np.linalg.svd([1]))()
^

This is not usually a problem with Numba itself but instead often caused by
the use of unsupported features or an issue in resolving types.

The change in error message requires updating this test (now failing on Travis CI):
https://github.com/numba/numba/blob/b8151838cc195d0ea6974b618ec22eed02a56fa2/numba/tests/test_operators.py#L1039-L1052

@seibert thanks, fixed that one too :)

Codecov Report

Merging #3147 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3147      +/-   ##
==========================================
+ Coverage   81.14%   81.14%   +<.01%
==========================================
  Files         384      384
  Lines       75028    75037       +9
  Branches     8434     8435       +1
==========================================
+ Hits        60878    60888      +10
  Misses      12859    12859
+ Partials     1291     1290       -1


Grammar

There are some grammatical error on this page. Example, the flat/lateral definition and the combining structures definition... Many more on this page too...

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

ID: 8a1426ac-9a20-b0a3-0ebd-8ce4b2a50882
Version Independent ID: 771f2efb-f781-ed49-5ff0-5c95f2bc4868
Content: Navigation basics for UWP apps - UWP app developer
Content Source: windows-apps-src/design/basics/navigation-basics.md
Product: windows
GitHub Login: @serenaz
Microsoft Alias: sezhen

Fixed - thanks for the catch!


[Cherry-pick] Use correct header schema for BeginSkill (#5767)

use correct header schema for BeginSkill
Update tests.uischema
Cherry pick from #5767

#minor

Pull Request Test Coverage Report for Build 257477

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 76.167%

Files with Coverage Reduction
New Missed Lines
%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetNextViableTime.cs
1
90.91%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetPreviousViableTime.cs
1
90.91%

Totals

Change from base Build 257122:
-0.04%

Covered Lines:
23068

Relevant Lines:
30286

💛  - Coveralls


Color of crosshairs?

I'm not seeing a way to change the color of the crosshairs. If there is can we see how to do that? If not, feature request?

What crosshairs?

I'm assuming he is referring to the selected line color.

In that case, it's the highlightColor of the dataset :-)

Exactly what I needed. Thanks.


TraceParserGen error on Microsoft-Windows-NDIS-PacketCapture

Repo steps.
K:\source\perfview\src\PerfView\bin\Release\net45>PerfView.exe /nogui userCommand DumpRegisteredManifest Microsoft-Windows-NDIS-PacketCapture

K:\source\perfview\src\PerfView\bin\Release\net45>k:\source\perfview\src\TraceParserGen\bin\Release\net40\TraceParserGen.exe Microsoft-Windows-NDIS-PacketCapture.manifest.xml
Reading manifest file Microsoft-Windows-NDIS-PacketCapture.manifest.xml
Error: Error on line Microsoft-Windows-NDIS-PacketCapture.manifest.xml(37,9): An item with the same key has already been added.

From the look of the XML file (what is on line 37) the issue is that two tasks have the same opcode.  This should be supported, but evidently it has broken.     Should be easy to fix.

This is fixed by #808

I'm afraid I'm running the updated code, and still unable to generate C#
code for Kernel-Network
On Wed, Jan 2, 2019 at 7:57 PM Vance Morrison<EMAIL_ADDRESS>wrote:

This is fixed by #808 https://github.com/Microsoft/perfview/issues/808
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/perfview/issues/808#issuecomment-450934515,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEdeC-3cBa6OqJDiZkiN-g7PvF5U_OMks5u_PLzgaJpZM4ZDgQl
.


Error: Element type is invalid expected a string

I am trying to start with Moti, seems like a great package but stuck in Hello world example.
Report Type
Bug
Error Description
Trying to run Moti Hello World example.
Getting this error
Error: Element type is invalid: expected a string (for built-in components) or a class/function
(for composite components) but got:  undefined. You likely forgot to export your component from
 the file it's defined in, or you might have mixed up default and named imports.

Check the render method of `Shape`.

Full error

Setup/dependency
"dependencies": {
    "expo": "~41.0.0",
    "framer-motion": "^3.3.0",
    "moti": "^0.4.1",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz",
    "react-native-reanimated": "~2.1.0",
    "react-native-web": "~0.13.12"
  }

Please follow all the instructions and install Reanimated 2: https://github.com/nandorojo/moti/installation
Or see the starter template: https://github.com/expo/examples/tree/master/with-moti

Hi @nandorojo , Thanks for the fast reply.
I am using starter template by running
npx create-react-native-app -t with-moti
And the starter template running fine but when I try to use Hello World example from separate component, getting this error.

My guess is there's an issue on your end then, since the starter is just using the hello world

Are you on the latest version?
yarn add moti

@nandorojo  Thanks
updating Moti to latest version solve the problem.

Sounds good thanks. I have a pending PR to update the example on Expo's repo, still waiting on them to merge it


sqlparser feature request: Generate List instead of T for WHERE IN ? parameter

First of all thanks for your great work on the sqlparser library! I really think generating code from SQL is the best approach to ORMs/persistence libraries, and I'm so glad there's now a solution available for Dart users.
I have a feature request: When a bind argument exists inside an IN clause, the parameter in the generated code should have the type List<T> instead of T. For example, the query
SELECT * FROM todos WHERE id IN ?

would generate:
Future<List<TodoEntry>> todos(List<int> var1)
Stream<List<TodoEntry>> watchTodos(List<int> var1)

instead of:
Future<List<TodoEntry>> todos(int var1)
Stream<List<TodoEntry>> watchTodos(int var1)

On develop, the sql parser can already recognize if a variable should be bound to an array. However, we can't bind an array to a singular variable at runtime, so we'd have to generate code like this (just writing off the top of my head, there probably is a more efficient way).
// assuming query is "SELECT * FROM todos WHERE id = ? OR id IN ? OR content = ?" to
// make things a bit harder.
Future<List<TodoEntry>> todos(int var1, List<int> var2, int var3) {
 final resolvedVars = <Variable>[Variable.withInt(var1)];
 final var2marks = List.filled('?', var2.length).join(', ');
 var query = 'SELECT * FROM todos WHERE id = ? id IN ($var2marks) OR content = ?';
 resolvedVars.addAll(var2.map((v) => Variable.withInt(v));
 resolvedVars.add(Variable.withInt(var3));
 return customSelectStatement('...', variables: resolvedVars).then(map);
}

Yeah I think generating an appropriate-length list of ?s is expected behaviour. Might take a bit of extra effort to make sure it plays nicely with indexed bind args (stuff like SELECT * FROM todos WHERE id = ?2 OR id IN ? OR content = ?1).

Works on develop. There are two limitations to make the implementation simpler:

Array variables cannot be explicitly indexed: WHERE id IN ?1 won't work.
There can't be an explicitly indexed variable that appears after an array variable and has a higher index:  SELECT * FROM todos WHERE id IN ? OR id = ?2 won't work. Your last example would work, because the array variable will have an implicit index of 3. WHERE id IN ? OR id = ? would work as well.

With both of these limitations, we can just replace every array variable in the query with the expanded form with the appropriate length. We don't have rewrite other variables to change their index.


Assets from public folder are not present in dist/cloudflare

After running vite build, I can see that files from the public directory have been copied over to dist/client. However they're not found in the dist/cloudflare folder. While I'm not certain what the expected behavior is when running vike with a server, without a server, I expect the files to be present in the final cloudflare build output.
Reproduction: https://github.com/Eazash/vike-cloudflare-demo

Screenshots

Fixed in v0.1.5


Move file system watching logging to build operations

so we don't print the excessive logging at the start and the end of the build.
While there are now build operations which have
the watching statistics, is is hard to capture
those build operations:

The watching started operation is so early, no build logic did run at that point so we can't capture it.
The watching finished operation is so late, that build services already did shut down, so a BuildOperationListener - which doesn't work with configuration caching - is the only way to capture them.

Since we can't capture the start operation, the soak test can't assert anything about the received events during the build any more.
Fixes #13837.

@lptr PTAL!

@lptr I created the BuildOperationTypes. PTAL!


DOP-3660: Add openapi-changelog directive

Ticket
DOP-3660
Notes
Adds openapi-changelog directive and api-version option.

@mmeigs do we want this to go out to writers immediately?

@mmeigs do we want this to go out to writers immediately or with our next release?

Oh, this is a brand new project! This is the very first ticket. This will be finished hopefully in about 6 weeks. So, not looking to have anyone use it. Not that they will even know about this directive until then...


source_id registration of AWI-CM-1-0-LR, AWI-CM-1-0-MR, AWI-CM-1-0-HR

Since we are using three different resolutions of AWI-CM-1-0 in CMIP6, the source_id registration of AWI-CM-1-0 needs to be updated. The one which is already in the CMIP6_CVs has to be moved to AWI-CM-1-0-MR; the other two I will register separately.

@tsemmler05 thanks for this, peek at CMIP6_source_id.html and let me know if any further tweaks are required in the 3 new source_id entries


When trying to upgrade a release with no changes, the revision number is incremented

Output of helm version:
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1", GitCommit:"4485c6f18cee9a5d3c3b4e523bd27972b1b53892", GitTreeState:"clean", BuildDate:"2019-07-18T09:09:21Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

@nij4t What would you expect to happen here? I understand the part where the release is not incremented but there needs to be messaging around it and the rest of the user experience needs to be taken into account.

This is partially intentional behaviour. As part of helm 3, we now take into consideration the live state as part of the release. If someone were to kubectl edit a bunch of live resources and choose to revert back to their original state, they can do so now with helm rollback‘ or helm upgrade`. The chart might’ve never changed, but it’s possible that a patch was generated with the three-way merge patch.

Helm v3 introduced a nice feature of 3 way merge, which works well when doing upgrade/rollback. However, when  trying to upgrade/rollback using --dry-run flag, the life state of the release is not being taken into account, hence no release needed to be done, even if the state of resources are changed.
That creates difficulties for GitOps systems that rely upon helm. For example, fluxcd's helm-operator performs dry-run upgrade before rolling out new release. This way the release is out only when the release in fluxcd's CRD and cluster's latest release differ. So, if, let's say, someone changed the image of a deployment, it's there until the release itself is not changed, which makes the GitOps implementation incomplete

The dry-run flag shouldn’t be recording a release in the cluster. Can you demonstrate an example?

The dry-run flag shouldn’t be recording a release in the cluster. Can you demonstrate an example?

It does not

Okay. I'm a little confused by your previous statement...

when trying to upgrade/rollback using --dry-run flag, the life state of the release is not being taken into account, hence no release needed to be done, even if the state of resources are changed.

Specifically this line:

hence no release needed to be done

Which implies that the --dry-run flag records a release.
Would you mind demonstrating an example of what you are trying to achieve?

@bacongobbler, let's assume that I have 3 relicas of a deployment in the latest release. I changed the replicaCount of a deployment to one using kubectl. Then when preforming helm diff upgrade1 using the same values (that had the replicaCount of 3) the output was empty. Which makes sense when comparing current and latest releases. And which is bad in the world of GitOps.
1Helm Diff - Community plugin that requires helm ^3.1.0

Okay. I'm a little confused by your previous statement...

when trying to upgrade/rollback using --dry-run flag, the life state of the release is not being taken into account, hence no release needed to be done, even if the state of resources are changed.

Specifically this line:

hence no release needed to be done

Which implies that the --dry-run flag records a release.
Would you mind demonstrating an example of what you are trying to achieve?

By that I mean that the helm-operator tries to do a dry-run upgrade first to check whether the release is needed to be rolled out. If it detects changes it does another upgrade but this time without dry-run which records a release.

@bacongobbler, how would you know whether a rollback is needed without doing the rollback? Now imagine that an automated systems does those checks within defined interval before committing any action. This is needed to eliminate the state drifts by resetting the state to its release declaration.

how would you know whether a rollback is needed without doing the rollback?

Helm has logic within it to determine if no update is required or not: https://github.com/helm/helm/blob/7f3339cb4eec9800cb09a46512050fb509480f7e/pkg/kube/client.go#L402-L410

Then when preforming helm diff upgrade1 using the same values (that had the replicaCount of 3) the output was empty.

It's important to keep in mind that helm-diff was created with the intent of comparing the changes between the chart installed in the cluster and what you are proposing to change. It does not include the live state into its consideration.
If you need to consider the live state, old and new chart, that sounds like either a new feature for helm-diff, or perhaps another tool (such as the gitops tool you are alluding to).

@bacongobbler, thank you for clarification!
My concern is that the gitops tool uses helm package to do upgrades with dry-run and yet the live state is not considered anyway.

it looks like it's only performing a two-way diff. For a gitops tool, that may be their intention. Have you asked the authors of flux whether this was an intentional design decision or a bug? Either way it seems like there isn't anything actionable on our end here. It sounds more like a design question for flux.

As I understand, the JSON patch is not something we record in the release, and that's intentional by design. Each upgrade's patch can change as the live objects are updated. It is up to the implementer (in this case flux) to compute the patch themselves. They have the tools required to do so, now they need to go and generate the patch :)
Here is how Helm generates the patch: https://github.com/helm/helm/blob/7fd30581b6455243e6508d50c978694c503bff70/pkg/kube/client.go#L340
Hope this helps!

Thank you very much, @bacongobbler!


Polish SCM viewlet

[ ] Provider switcher
[ ] Drag n drop
[ ] Multi select
[ ] Telemetry

Dupe of #22131


Shift+Insert for (Linux) paste primary selection possible?

Oni Version: 0.36
Neovim Version (Linux only): 0.3.1
Operating System: Linux (Arch)
Issue:
In Linux almost application support for paste primary selection(or clipboard) with Shift+Insert. Is this possible in oni?

Yes, it is. The clipboard we use just need to be set to retrieve the 'selection' content.
Meanwhile, you can use <C-r>* in insert mode or *+p in normal mode.


NOISSUE - Add prometheus and grafana for metrics

What does this do?
Add Prometheus and grafana for service metrics
Which issue(s) does this PR fix/relate to?
None
List any changes that modify/break current functionality
None
Have you included tests for your changes?
No
Did you document any new/modified functionality?
No
Notes

Codecov Report

Merging #1753 (19f5810) into master (83ff4e1) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master    #1753   +/-   ##
=======================================
  Coverage   70.59%   70.59%
=======================================
  Files         146      146
  Lines       11418    11418
=======================================
  Hits         8061     8061
  Misses       2716     2716
  Partials      641      641

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

Is it possible that you can provide some dashboard in .json also so that someone can import a basic monitoring dashboard?

Is it possible that you can provide some dashboard in .json also so that someone can import a basic monitoring dashboard?

Like creating a sample grafana dashboard? @rodneyosodo

Is it possible that you can provide some dashboard in .json also so that someone can import a basic monitoring dashboard?

Like creating a sample grafana dashboard? @rodneyosodo

Yes

Have a look at why only auth metrics are showing up and not the others in prometheus

now fixed

Change threshold on allocated bytes

Do we know what is critical value? I'd rather just leave it to be static white always

When I stop one container I still get allocated bytes

This is resolved


Connector pinhead interface

Hi, I wanted to make myself a bob cassette rewinder as a project to practice my home-made pcb skills. However I can't find what type of connector you use on your custom PCB to interface with the cassette EEPROM. I'm talking about the one named JP1 (PINHEAD_2X04) on the schematics. As I understand using a female USB-A connector would short the pads on the cassette, so it has to be plastic.
Thanks!

Hi again,
I just found it! It's called a Card Edge Connector and the one that fits is called SA08BL01D from UMAX.
Thanks @dekuNukem for this great project/hack !


Unable to open/log in The Chosen addon

Getting the Check the Log error when trying to open The Chosen addon.
Figured I might need to get a user/pass so I signed up, entered the user/pass in the addon and tried to start the addon.
Now getting a Login Attempt Failed Error, rechecked the user/pass several times (they work at the website)
TIA
(Win 10/Kodi 21.1/The Chosen 0.4.2)

Thanks, looks like they have completely changed the API (again).  It will take a couple days to sort out....

Fixed in 0.4.3, thanks for reporting!


VM Application Healthchecking

Implementation of the application healthchecking for Virtual Machines.
Design Doc (@howardjohn): https://docs.google.com/document/d/1G4s_PrmvkwCKoH_kXVeSUAszsaj3ZfpIlraSdeTSPKU/edit#
xds-proxy author: @rshriram
new PR because apparently, I cant use git

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test release-notes_istio

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

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.

Adding ref to your old PR https://github.com/istio/istio/pull/26997 because review comments will be useful to understand what changes have been made.
@adiprerepa Anyways what problem you are facing with git. Let me know if you need any help?

@shamsher31 thanks for the ref. i screwed up a rebase, which brought in a bunch of commits, so i figured that opening a new PR would be easier. I think I am good now. The other one was more of a draft/wip anyway, this is more complete.

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

Test name
Commit
Details
Rerun command

release-notes_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test release-notes_istio

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
6abcb0cbfbae93ddfb6ae8a4038ba08690468fad
link
/test lint_istio

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-pilot-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-telemetry-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-notes_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-notes_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-multicluster-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

lint_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test lint_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
2f5c410cd31b09663f9729d5fb4b9a1b10617b6e
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test unit-tests_istio

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-operator-controller-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
2f5c410cd31b09663f9729d5fb4b9a1b10617b6e
link
/test release-notes_istio

lint_istio
2f5c410cd31b09663f9729d5fb4b9a1b10617b6e
link
/test lint_istio

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.

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

Test name
Commit
Details
Rerun command

release-test_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test release-test_istio

integ-security-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
e38a56a2145d5b1c55e1097173b88e21d25bff45
link
/test integ-multicluster-k8s-tests_istio

lint_istio
2f5c410cd31b09663f9729d5fb4b9a1b10617b6e
link
/test lint_istio

release-notes_istio
4f86e075e2399d5281b786fe196b3fc798cde14f
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
4f86e075e2399d5281b786fe196b3fc798cde14f
link
/test release-notes_istio

integ-multicluster-k8s-tests_istio
4f86e075e2399d5281b786fe196b3fc798cde14f
link
/test integ-multicluster-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4f86e075e2399d5281b786fe196b3fc798cde14f
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
5a67a6e916e9409012f0dce9c56b6f8a2f6c88f4
link
/test release-notes_istio

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.


How can I use my own images and point cloud data to run BEVFusion eval

I have my own dataset with calibrated LIDAR_TOP files and 6 cameras files
I want to keep all other data files as the same but replace the images and point cloud files into my own dataset
How can I change the data loader to load from the correct path and filenames when running the test.py

Hi @Laobyy,
Yes you can do that. One simple way to do that is to reorganize your dataset info file similar to nuScenes. You could refer to this file about the expected fields in the info file. I believe as long as your dataset info file is in the same format as nuScenes, you should be able to reuse most of the dataset code from nuScenes.
Best,
Haotian


[stable/opa] Checksum logic fix

What this PR does / why we need it:
Fixes bug in conditional logic for chart. See #13734
Which issue this PR fixes
#13734
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/lgtm


Is it possible to use THREE.LOD?

Or another similar implementation?

@native1989 I had been thinking the same - it would make a lot of sense similar to how mapbox simplifies features at lower zoom levels. Might be difficult to come up with a standard simplification method though as it may vary depending on the scale and complexity of each model?


[Bug Report] [Bug Report] DatePicker type="datetimerange" , set editable false is not work

Element UI version
2.0.2
OS/Browsers version
chrome
Vue version
2.5.2
Reproduction Link
http://jsfiddle.net/pj71jkyw/673/
Steps to reproduce
DatePicker type="datetimerange" 设置editable=false
What is Expected?
不能再日期选择范围框输入值
What is actually happening?
依然可以输入值

Fixed in #7922


fix: Fix vscode-graphql-syntax’s grammar to support string literals on separate lines

Summary
We're currently working on gql.tada, which is mostly compatible with the expected syntax of graphql calls.
However, while getting this in users hands we noticed that a specific grammar that Prettier formats graphql() calls into fails to be matched by the Textmate grammar in vscode-graphql-syntax.
Specifically, when a GraphQL string literal is placed on a new line, the begin pattern of the rules can't match. This is a limitation in Textmate grammars, as it turns out, and we can't even manually match \n patterns.
I'm not an expert at Textmate grammars, but, in theory, a grammar rule that matches GraphQL calls as a lookbehind, then matches the inner string literal separately, should do the trick.

Before
After

Follow-up questions

Is there a test suite / sample files for this we can check for regressions?
Does anyone here know more about Textmate grammars to proof read this change?

Set of changes

Try out newline matches in begin rule (DELETED CHANGE)
Add separate rule for matching graphql(...) calls then matching string literals inside
Combining redundant rules into one (move generic over)
Update snapshots (remove TODO: fix this) and add more grammar checks for JS

@kitten thanks for this! to answer your questions, see the syntax extension readme

also, can you add to the test fixtures the test case you originally hoped to cover? I don't see it present in your PR

@acao: Cheers! I forgot to add some more cases for the original failing matches ✌ Those should be added in: https://github.com/graphql/graphiql/pull/3518/commits/057f22e378bd74d13928917b1541c81704aa94e7
Regarding the readme, I did test the extension manually as well, so the screenshots should cover that 🤔

@kitten amazing work here! looking forward to getting this released
I had to release a quick hotfix for the triple double quote syntax """ comment """, I hope you don't mind merging that change. for now we aren't as concerned with graphql(" query { id }") type scenarios because they are much less common than the """ comment """ syntax. if you can make both of those worlds happy, then heck yeah that's awesome! but if not, it's no bother
also, one last nice to have - maybe confirm a few weird pre-auto-formatted variations just to be sure we don't deprecate it somehow in the future. it's nice to have the strings always working no matter whether auto-formatting (prettier, etc) is used or has been applied
for example, cases like this
const query = graphql(
` query {
    something
    }
 `);

our LSP server uses normal AST parsing ofc, but with the textmate regexes so many things can go wrong haha

@acao Merged that back 👍 I'm not too concerned either. No idea what the syntax currently says for single line graphql(" \"\"\"comment\"\"\" query { id }") cases, but the original case that this PR addresses is Prettier putting a template literal (or 'query' string) onto their own lines, which broke the previous syntax definition.
Given that double-quotes " inside a GraphQl string would have to be quoted, Prettier likely would reformat the string with single quotes. And that even assumes they're single line. So, either way, we should be fine there.
re. corner cases, I'm not too concerned about adding all kinds of newline cases to the tests. There's one, which basically represents all possible cases; i.e. \n[ ]{2} before the start of a string. That's equivalent to “all” cases, so to speak, since Textmate grammar can't match past newlines, so the call syntax (e.g. graphql(\n ... \n)) is what we ultimately have to check against.
So, all good from my end 👍

Just came back from some holidays, so coming back to this, let me know if there's anything else we want to do here, or if we're good to go ✌❤

since Textmate grammar can't match past newlines
I'm not sure if this is true, if I understand?

otherwise though it looks great! i will take a closer look and see about merging it soon

actually, can you add some more test cases to test-js.md as well? it should work transparently

@acao: re. not matching past multiple lines, I found a more detailed discussion here, which is where I initially ended up for this PR. Basically, what I meant was that begin and end can't literally include matches for a newline character, since the matches are separated line by line and that's why the new rules match the function call first.
I applied some of the additions to test-js.md. I don't think the fixtures there test for code matches, but it's now covering the relevant cases for future changes to the syntax 👍

Just stumbled into this issue. Would love to see this merged soon.

There appears to be something awry with github actions, where it's not reporting the run status (for me at least), and the log output formatting is broken, but manually checking each job, it looks fine! merging now, thanks again!

bad news - it appears this github actions event is not triggering the changeset bot?
good news - once the issue recovers, we will still be able to release the changes without a problem with the next merge to main

@acao Sorry for being annoying but when will this be released?Thank you.

It has already been released: https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql-syntax

Has caused a regression, showcased in #3542.

no worries @kitten this happens! lets double check the snapshot suite and make sure we have the right fixtures for this case and/or see if the snapshot change reveals this bug

@aradalvand 0.9.2 is now released, and removes this regression by reverting the 0.9.1 release. thanks for reporting!

@kitten I think the issue we can see from the snapshot side is that the end ` and ; i think are being tokenized by graphql somehow? So i think the query remains unterminated and attempts to highlight the rest of the file from the first graphql tag to the end of the file. i would look closely at the serializer results, and follow the readme instructions for performing manual builds to visually confirm the outcomes, where you open the fixture files and can confirm that everything is as expected

I'll take a look! I've tested this before in VSCode, but I'm guessing there's either a case that isn't covered or I made a mistake while resolving conflicts 🤔

yeah, that's what I guessed as well! also, my bad for not manually confirming everything immediately pre-release myself, that's my job 😆

Not your job and not your job solely if you do consider it your job ❤ I did confirm and double-check this, but it was a subtle mistake where the pattern wasn't quite matching, because the positive lookbehind failed, and was neither applying ts/js/etc highlighting inside the function call expression, nor was it then matching correctly after the pattern, since the pattern causes an error.
At least that's my assumption.
It's easy to miss because the tests don't contain the VSCode tmLanguage patterns for JS/TS themselves, which makes it hard to see that this is happening, because it does at first glance all look correct.
This does make me think that while this may sound silly, visual snapshots would be really helpful in the future, if the VSCode team is willing to provide such a tool 🤔
I found the issue and will open a follow-up PR

Fix is in a new PR here ❤ https://github.com/graphql/graphiql/pull/3545
Sorry for messing this up!


Rotate text - horizontal writting

I miss the possibility to write in english or others ocident languages using this layout. Look likes it does not have an option to rotate text, like the first mangaEditor have.

This is the planned feature in the next version, but unfortunately I don't have time for this project recently :(

It is ok. Good luck with your goals. Unfortunately I have not a solid acknowledge in frontend development and frameworks to help you implement this feature. Would you mind to keep this issue open to remind someone else about this pending feature?

That's exactly what's in my mind. I'd keep this issue open until https://github.com/OrcaXS/mangaEditorNeue is ready.
Thanks for following this project! Knowing someone still using it gives me motivation to keep it maintained.


New subset for prokaryotes

@AndreaAuchincloss from Swiss-Prot pointed out there are no prokaryotic subset anymore, and now that more sites are using the GO ribbon (including the upcoming UniProt website, see https://beta.uniprot.org/uniprotkb/P40136/entry
So we have started to work on a prokaryote slim, see https://docs.google.com/spreadsheets/d/1i5ZquuO7nv9yWJrK5fMo1rzaKV4uxndrr5UWe7AjIII/edit#gid=664482462
We have been testing the set with the list of E. coli entries - see attached file
e.coli_AC.txt
PR is here:
https://github.com/geneontology/go-ontology/pull/23022

Changed label to goslim__prokaryotes' after discussion with @alexsign since this will allow loading in UniProt.
The plan is to rename all subsets at once (probably to gosubset_xx), later

Updated GO website documentation: https://github.com/geneontology/geneontology.github.io/compare/master...pgaudet-patch-36?quick_pull=1


Use without composer?

Is it possible to use this script without using composer? Its not installed on my webspace, but I need the recaptcha php script...
Thank you

I tried to use it with the 'recaptchalib.php' file, but I only got a captcha that looks like this:

Why is it so big and not the tiny one, showed on the recaptcha website?

We need an autoloader... Until Google gets real and understands that not everyone needing Recaptcha will want to install a whole new software just to compile a simple autoloader!
Luckly, @orlitzky has made one: https://github.com/google/recaptcha/pull/34
Get it from his fork: https://github.com/orlitzky/recaptcha/tree/manual-install

Works great :)
Can you may tell me, why the recaptche is so big? Because normally its a way tinier isn't it?
!(https://www.google.com/recaptcha/intro/images/hero-recaptcha-demo.gif)

There is an alternative mode, which is used when there is no javascript. It is also big (shows a captcha) when it has suspects about you... The screenshot looks like you fill in the first case.

Javascript is enabled in my browser (and not blocked) and on other pages the captcha is small. Could it be a issue with anything else?


docs: update middlewares.md

Information

Type
Breaking change

Doc
No

:tada: This PR is included in version 7.75.5 :tada:
The release is available on:

v7.75.5
GitHub release

Your semantic-release bot :package::rocket:


How to fix invalid peer id

Got this error:

Error 400 PEER_ID_INVALID 2 5

But i am not using peer id as parameter, what is this error means?
Here is my code:
const getChat = async () => {
  const getInfo = await client('messages.getFullChat',{
    chat_id:200275452
  })
  console.log(getInfo);
}

library version: 3.0.6

You ever figure out what was going on?


Fix redundant dividers on search for labels

Labels search dropdowns have redundant dividers when searching for labels

This PR adds data-divider-index and data-divider-group to dynamically toggle the visibility of dividers depending on filtered results. And slightly changed the logic for adding the divider if there are both Labels and OrgLabels exist.
After:
https://github.com/go-gitea/gitea/assets/17645053/5f905358-f6c3-40d9-a06d-a1306a72bd38
Locations of the dropdowns:
On sidebar of issue/pr, and on repo issue/pr list

At first glance, it's quite hacky. I guess it's not the right way.

In the video, the extra dividers are still seen while typing, so yes I think the solution can't be right.

BTW, I generally think we should rewrite these labels dropdown to a format similar to GitHub, it saves vertical space as well:

Actually, Fomantic UI does very well for "hiding dividers".
We only needs 2 lines:
  $dropdownLabelFilter.dropdown('setting', {'hideDividers': 'empty'});
  $dropdownLabelFilter.dropdown('refreshItems');

Actually, Fomantic UI does very well for "hiding dividers".
We only needs 2 lines:
  $dropdownLabelFilter.dropdown('setting', {'hideDividers': 'empty'});
  $dropdownLabelFilter.dropdown('refreshItems');

Fix label list divider #25312

That's great, I will close this.


User manual updates

This has some updates to the user manual I've been working on for a while.  I doubt there are any collisions with the master branch because unless I screwed up all the changes are in docs/source.
This includes a first draft of a page on parallel processing that you guys should look at critically as the experts in that area.  I'm a rookie and could have said something wrong in trying to produce a readable document.

Codecov Report

Merging #239 (4dc1eb9) into master (cd81013) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #239      +/-   ##
==========================================
- Coverage   47.91%   47.88%   -0.03%
==========================================
  Files         118      118
  Lines       15350    15340      -10
==========================================
- Hits         7355     7346       -9
+ Misses       7995     7994       -1

Impacted Files
Coverage Δ

python/mspasspy/algorithms/RFdeconProcessor.py
29.18% <0.00%> (-0.91%)
:arrow_down:

python/mspasspy/util/decorators.py
66.66% <0.00%> (-0.46%)
:arrow_down:

python/mspasspy/db/database.py
82.65% <0.00%> (+0.03%)
: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 cd81013...4dc1eb9. Read the comment docs.

I pushed a commit for

update for parallel_processing.rst
add user manual for configuration.

Probably needs more polish on some expressions.


Broken saving of bitmap images (also affects Copy)

Version: 0.3.1
There's a bug with Bitmap images (occurs at save which also affects copy to clipboard). They don't store their bitmap content and end up loading/showing only the default glyph (an small image frame) on paste or load.

Please don't use that version for saving documents that contain bitmap images (e.g. photos)
You can use multiple versions side-by-side. If you use different executable filename they will keep their own state to temporary storage upon closing. If you put them with same filename in different folders they'll reuse the same temp file. Since 0.3.1 fails to save photos/bitmap, if you keep it around to play with the text color selector that had been added to that version, do use a different filename, say READCOM_App_0.3.1.exe or something (and keep 0.3.0 as READCOM_App.exe)


Avoid session idle timeouts

Sessions time out. And a connection is associated with a session. If the user does not set max connection idle timeout, it is possible that they'll get errors on session timeout.
We need to either have a heartbeat, or figure out a way to invalidate the session and create a new one. Or as a last resort gracefully handle the error.

Any updates on this one?

Sorry for the delay. There were many discussions on how to deal with this and heartbeats have many drawbacks. SQL Warehouses now have a 8 hour session idle timeout, so this should not be a real issue. Is the concern now primarily related to clusters?

In my case, I have a web app that works with DataBricks and was wondering what would be the best way to handle session timeouts without restarting the server
databricks: execution error: failed to execute query: Invalid SessionHandle

No worries, thanks for the reply.
My issue is similar to @cghiban, I have an app that uses the warehouse so I have to restart it every now and again in order to refresh the session.

oh, in your case, please set https://pkg.go.dev/database/sql#DB.SetConnMaxIdleTime
This will prevent the issue you're having. No need to restart the pod


SPIKE: Begin planning for a migration off GraphQL to regular REST endpoints

Why are we doing this?
GraphQL is the source of a lot of heartburn in our current implementation. We can streamline things quite a bit of we migrate to the use of regular REST endpoints, but there is a lot of planning involved.
Action requested

Begin planning and laying the groundwork for how to go about this
Create tickets for individual controllers/feature slices (Possibly an epic, as well?)
Present research findings to the team, if relevant/necessary

Additional context
Produced by the engineering sync meeting on 27 January 2022.

Consider iceboxing in favor of moving towards the Spring for GraphQL library when that eventually comes out.

I think the Spring for GraphQL library may finally be out in 1.0: https://github.com/spring-projects/spring-graphql/releases/tag/v1.0.0

Closing as most of the frustrations here have been addressed in the upgrade to Spring for GraphQL.


Text search also searches specialities

updated developers model to include specialties

Thanks for the contribution, @nnahgodspower122!
Can you email me and let me know how you'd like to receive the bounty? I can do GitHub Sponsorships, Venmo, PayPal, Zelle, and Wise.


added name and github handle

Updated CONTRIBUTORS.md with name and Github handle

Can gssoc21 and level tag added to this?

can you please label this pr too :) with gssoc21 and level. This pr for adding my own name :))


win: remove unused code

This code appears to have just been missed in the cleanup done in #971

@vtjnash You want to land this?

Conservative CI run before push: https://ci.nodejs.org/job/libuv-test-commit/1674/

Ah, good to know: we were hard-coding these in some places—I'll avoid changing the values.
New CI: https://ci.nodejs.org/job/libuv-test-commit/1681/