Fix docker image creation

Breaking change

Proposed change

First PR of a few to do proper build of docker images and add-on
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the [development checklist][dev-checklist]
[ ] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #585 (6c973e5) into app_model (1295771) will increase coverage by 0.17%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           app_model     #585      +/-   ##
=============================================
+ Coverage      86.51%   86.68%   +0.17%
=============================================
  Files            108      108
  Lines           2915     2915
  Branches         309      309
=============================================
+ Hits            2522     2527       +5
+ Misses           259      255       -4
+ Partials         134      133       -1

Flag
Coverage Δ

unittests
86.68% <ø> (+0.17%)
:arrow_up:

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

Impacted Files
Coverage Δ

...mon.HassClient/Internal/HomeAssistantConnection.cs
86.66% <0.00%> (+1.90%)
:arrow_up:

...mon.HassClient/Internal/Net/WebSocketClientImpl.cs
76.31% <0.00%> (+7.89%)
: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 1295771...6c973e5. Read the comment docs.


It happens with different windows version.
For more details see https://youtrack.jetbrains.com/issue/IDEA-131748

// Currently we use https://youtrack.jetbrains.com/issue/IDEA-131748 to discuss and triangulate the issue

Note, this could actually be bug https://github.com/kohsuke/winp/issues/6 - Despite appearances, that fix is not present in winp as the merge discarded the changes.
Details here: https://github.com/kohsuke/winp/issues/22


New fixes

@girishshilamkar can you address formatting change for http://vmware.github.io/docker-volume-vsphere/documentation/install.html as part of this review?

@shuklanirdesh82 Can we merge this?

@girishshilamkar I am merging proposed changes .. please raise a new PR to supply a fix for https://github.com/vmware/docker-volume-vsphere/pull/1177#issuecomment-294598629


ng-init property

Hi! For now color-picker not support ng-init value. So i can not use update functionality. Can u fix it? Thx.

Hi @sutkovoy. I have never used ng-init and am struggling to understand how it would be used in the color picker. Are you able to give an example of what you are trying to do? There is a codepen example that you could fork.


Fix PDB 2.0 DebugId format

The previous implementation did not correctly represent the DebugId of
(very old) PDB 2.0 PE files.  The new debugid release suppots these
correctly.

Could you add a test for this behaviour?

thanks!!


[FEAT]: Add compatible ZAL implementation

Description
Recently, an abstraction API for backends in the PSE halo2 implementation was merged. It would be nice to have a wrapper around the existing ICICLE API that allowed for out-of-the-box usage of basic ICICLE features by implementing the MsmAccel trait
Motivation
Out-of-the-box usage of basic ICICLE MSM for all users of the PSE halo2 implementation

Hey I would like to help this issue if it is still available. @jeremyfelder

hi, can i take on this issue ?


[HBASE-25539] Add age of oldest wal metric

Same as https://github.com/apache/hbase/pull/2945 which was for master branch.
Master patch didn't apply cleanly. Some minor conflicts.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 40s
branch-2 passed

+1 :green_heart:
compile
4m  3s
branch-2 passed

+1 :green_heart:
checkstyle
1m 35s
branch-2 passed

+1 :green_heart:
spotbugs
2m 53s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 16s
the patch passed

+1 :green_heart:
compile
3m 59s
the patch passed

+1 :green_heart:
javac
3m 59s
the patch passed

+1 :green_heart:
checkstyle
0m 14s
The patch passed checkstyle in hbase-hadoop-compat

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-hadoop2-compat

+1 :green_heart:
checkstyle
1m  7s
hbase-server: The patch generated 0 new + 5 unchanged - 1 fixed = 5 total (was 6)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
11m 46s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 20s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 40s
The patch does not generate ASF License warnings.

46m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 1f2e0df4c07e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-1.8.0_232-b09

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 17s
branch-2 passed

+1 :green_heart:
compile
1m 44s
branch-2 passed

+1 :green_heart:
shadedjars
6m 44s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 57s
the patch passed

+1 :green_heart:
compile
1m 45s
the patch passed

+1 :green_heart:
javac
1m 45s
the patch passed

+1 :green_heart:
shadedjars
6m 48s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 31s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
130m 28s
hbase-server in the patch passed.

163m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3ef1c3301103 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/testReport/

Max. process+thread count
4197 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

-0 :warning:
yetus
0m  8s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 36s
branch-2 passed

+1 :green_heart:
compile
1m 33s
branch-2 passed

+1 :green_heart:
shadedjars
6m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 11s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 20s
the patch passed

+1 :green_heart:
compile
1m 36s
the patch passed

+1 :green_heart:
javac
1m 36s
the patch passed

+1 :green_heart:
shadedjars
6m  2s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  9s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 28s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
140m 17s
hbase-server in the patch passed.

169m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a29fc5a8ad06 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/testReport/

Max. process+thread count
4227 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 42s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 57s
branch-2 passed

+1 :green_heart:
compile
4m 19s
branch-2 passed

+1 :green_heart:
checkstyle
1m 38s
branch-2 passed

+1 :green_heart:
spotbugs
3m  0s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 49s
the patch passed

+1 :green_heart:
compile
4m 29s
the patch passed

+1 :green_heart:
javac
4m 29s
the patch passed

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-hadoop-compat

+1 :green_heart:
checkstyle
0m 14s
The patch passed checkstyle in hbase-hadoop2-compat

+1 :green_heart:
checkstyle
1m 19s
hbase-server: The patch generated 0 new + 5 unchanged - 1 fixed = 5 total (was 6)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m 42s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 37s
The patch does not generate ASF License warnings.

51m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 1e4b6a256029 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-1.8.0_232-b09

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 29s
branch-2 passed

+1 :green_heart:
compile
1m 50s
branch-2 passed

+1 :green_heart:
shadedjars
6m 57s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 18s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  9s
the patch passed

+1 :green_heart:
compile
1m 46s
the patch passed

+1 :green_heart:
javac
1m 46s
the patch passed

+1 :green_heart:
shadedjars
7m 25s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 35s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 34s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 38s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
148m  6s
hbase-server in the patch passed.

182m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d75d8377b7cf 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/testReport/

Max. process+thread count
3574 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 45s
branch-2 passed

+1 :green_heart:
compile
1m 32s
branch-2 passed

+1 :green_heart:
shadedjars
6m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  8s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 32s
the patch passed

+1 :green_heart:
compile
1m 30s
the patch passed

+1 :green_heart:
javac
1m 30s
the patch passed

+1 :green_heart:
shadedjars
6m  2s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  7s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 26s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 28s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
158m 13s
hbase-server in the patch passed.

187m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2962

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7ec470f62677 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ec680c52e0

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/testReport/

Max. process+thread count
3293 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2962/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Automatically create named directories for each output resource in a …

…TaskRun.
Changes
TaskRuns are expected to place files related to an Output in a directory named
for each Output. Right now, we expect Task authors to create this directory before
placing files there. This is onerous and error-prone, so we should automatically create
them.
There are a few approaches to doing this:

a mkdir init container
a volume
a mkdir pod container

I chose to use the final one, a mkdir pod container for consistency with Input resources.
This is prepended to the Task steps.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[X] Includes tests (if functionality changed/added)
[X] Includes docs (if user facing)
[X] Commit messages follow commit message best practices

See the contribution guide for more details.
Release Notes
Tekton now automatically creates directories for each Output resource during a Taskrun.

/test pull-tekton-pipeline-integration-tests

/lgtm


[docs] Adjusted the FAQ 'communication between projects faq'

The Issue

It wasn't really clear where to put the docker-compose.communicate.yaml file directly
Fixed the syntax of the example, it had wrong indentation

How This PR Solves The Issue

Added a bit more context
Fixed the indentation

Manual Testing Instructions

None, as this is for the docs

Automated Testing Overview

None, as this is for the docs

Related Issue Link(s)

None, I fixed this as I saw it

Release/Deployment Notes

None, as this is for the docs

@rfay @mattstein Thanks for checking my PR so fast guys, happy to contribute as I'm a DDEV fan :-)

docs check seems to be broken right now only because xdebug.org is down.


Add IPv4-only HTTP client

This replaces the default HTTP client from the http package with a client that will always connect over IPv4.
The main reason behind this change is that the Autojoin API currently tries to autodetect the node's IPv4 by reading the HTTP request's client IP. On dual-stack machines, the request could randomly happen over IPv6 and the Autojoin API wouldn't have the minimum information required to register the node. This change mitigates that problem.

This change is

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.212%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
714

Relevant Lines:
727

💛  - Coveralls

It would help in handling the case where the server has multiple interfaces/addresses, and the host wants to serve ndt-server on a specific one (which may not be the default route).


Can we remove compress option for quantized KNN vector indexing?

Description
Spinoff from this comment.
This (compress=true) is a useful option when quantizing KNN vectors to 4 bits: it packs pairs of dimensions into a single byte, so the "hot working set" of your KNN/HNSW vectors at search time is half the already reduced (from float32 -> byte) size.  When compress is false then it's wasteful, using only four bits for every byte.
But it comes with some penalty to decode the "packed" (compress=true) form during KNN search, which is why we give this choice to the user.
But then I think there was at least one opto to that path, so maybe the performance penalty isn't so bad now?  In which case maybe we can just always hardwire compress=true when quantized bits=4?
(compress=true doesn't apply to 7 bit quantization)

I'll see if I can benchmark at least this tradeoff using luceneutil's knnPerfTest.py, at least on my intel Linux dev box.

I agree, this is worth digging into. In my benchmarking, compressed=true ended up being even marginally faster than compressed=false, but I didn't know why :/ which is why I was hesitant to remove the option before.
It would be good to benchmark this with and without panamavector enabled over intel & arm.
Note, there has been work to move all quantized comparisons off-heap: https://github.com/apache/lucene/pull/13497 the results of which may or may not effect this decision (bytes no longer being copied on heap, thus the fewer bytes being copied no longer harm/help performance). But, I kept having weird slow downs that I cannot figure out and nobody else can replicate (@ChrisHegarty has tried and couldn't see why I keep seeing significant slow downs given different JDK versions).

Well, I ran knnPerfTest.py on my Linux dev box (x86-64 Raptorlake i9-13900K).  This CPU has crazy number of flags, but NOT AVX-512:
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities

This is with Panama enabled (INFO: Java vector incubator API enabled; uses preferredBitSize=256; FMA enabled).  I'll try with Panama disabled next.
Results:
recall  latency (ms)     nDoc  topK  fanout  maxConn  beamWidth  quantized  index s  force merge s  num segments  index size (MB)
 0.319         0.167  1500000    10       6       32         50     4 bits    86.01          64.49             1          5013.19
 0.326         0.187  1500000    10       6       32         50     4 bits    89.03          74.99             1          5562.51

Unfortunately the output doesn't state it, but the first row is compress=True and 2nd is compress=False.  Indeed, latency (search time) got faster (187 usec -> 167 usec) with compress=True, and this is quite a reduction (~10% ish) in index size.  Indexing and force merge time did get a bit slower ...

OK I disabled Panama (via temporary code change in VectorizationProvider.java -- we don't accept sysprops to disable this anymore right?):
recall  latency (ms)     nDoc  topK  fanout  maxConn  beamWidth  quantized  index s  force merge s  num segments  index size (MB)
 0.318         0.312  1500000    10       6       32         50     4 bits   175.21         125.64             1          5013.21
 0.319         0.285  1500000    10       6       32         50     4 bits   174.54         124.80             1          5562.51

Indeed there is some performance penalty now (285 usec -> 312 usec, ~9.5%) ... recall also bounced around a bit, but prolly that's acceptable HNSW randomness noise.  And wow look how much slower indexing / force merging got ... those SIMD instructions clearly help ;)
But I don't think we should block removing compress option due to non-SIMD results?

But I don't think we should block removing compress option due to non-SIMD results?

I agree. At this point we're just comparing the scalar and SIMD implementation of the distance functions. For vector operations, we really need SIMD, and I think we're ok with this approach.

If we are ok with the perf hit on non-panama, I am cool with it :). It will definitely simplify the code.

But I don't think we should block removing compress option due to non-SIMD results?

Actually, thinking about this more ... I'm changing my mind.  I don't fully understand how poor our Panama/SIMD coverage is across CPU types/versions, "typically" in use by our users.  E.g. for ARM CPUs (various versions of NEON instructions).  What %tg of our users would hit the non-SIMD (non-Panama) path?
It's spooky that the likes of OpenSearch, Elasticsearch, Solr are needing to pull in their own Panama FMA wrappers around native code to better optimize for certain vectorized instruction cases (see discussion on #13572).  Ideally such optimizations would be in Lucene so we could make decisions like this (remove compress option to simplify our API / reduce surface area) with more confidence.
I'd like to run benchmarks across many more CPUs before rushing to a decision here, and I think for now we should otherwise respect the non-SIMD results?  I love our new aws-jmh dev tool (thank you @rmuir)!  I looked at its playbook.yml to figure out if I could also add "go check out luceneutil, download this massive 95 GB .vec file, and run knnPerfTest.py and summarize the results" but I haven't made much progress so far ...


CMS pages: call template from Admin Content field

Hi,
I am new to Sylius and new to SyliusCMSPlugin. I created a CMS page and I wonder if it is possible to call a template inside Content field, for example:
{% include<EMAIL_ADDRESS>%}
or with any other way?

Hi, by default you cannot do this. But if you really need it, please play with https://github.com/BitBagCommerce/SyliusCmsPlugin/blob/master/src/Twig/Parser/ContentParser.php class and the %bitbag_cms.twig.admin_functions% parameter.


Online filtering

Is there a recommended way to apply online filtering to a dataset either on webdataset level or PyTorch Dataset level?
An example use case would be training on a subset of ImageNet classes without needing to regenerate the tar files.
Or is this something out of scope of webdataset/IterableDataset?

By "filtering", you mean selecting a subset of the dataset? As far as WebDataset is concerned, processing is just a chain of iterators operating on a stream of data, so you can select, reorder, and transform any way you like.
There is a shorthand for selecting samples:
def selection(sample):
    return "training" in sample["__key__"]

ds = WebDataset(...).select(selection).decode(...).etc...

Note that this will still read all samples but then discard the samples it doesn't want/need based on the selection function. That may seem inefficient, but it is usually faster than random access anyway.
When you train on very small subsets of the original dataset (less than 10%) and you need maximal I/O performance, you may want to prefilter the data based on some criteria and generate a new dataset representing just that subset.

Thanks, this is exactly what I envisioned.

Related to this question, would it make any sense to be able to read only some of the data files (for example item.json which would contain image dimensions), select items based on it, and then only load the entire items.
The idea would be to be able to create any subset of the data by only reading smaller files (metadata instead of full media files).

@borisdayma I think you can already, try something like:
def check(x):
    x["my_filter"] = read_json(x["item.json"])["my_property"] > 42
    return x

wds.WebDataset(...).map(check).select(lambda x: x["my_filter"]).decode(...)


docs: Add Japanese documents

PR
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Other... Please describe:

What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
I created Japanese translated documents.

@eltociear Thanks for your PR submission, Japanese is not currently included in the project support language plan.


MSIGDB ingest: current base context has old version

Issue
In the latest version of the base context, MSIGDB nodes are formatted like MSIGDB_SYSTEMATIC_NAME_M0. I will need to regenerate the base context.
Explanation
The MSIG_SYSTEMATIC... convention was used in an earlier version of MSIG. The earlier version of MSIG also had its edge/node files as TXT.
CHOP updated the MSIG format, and also changed to TSV. The new format for node IDs is like MSIGDB M40835.
Edge files can have multiple file extensions, including TXT, TSV, and CSV.
We allow files to have a variety of file names and extensions. The generation script looks for files named according to a list. For nodes, we accept

OWLNETS_node_metadata.txt
nodes.txt
nodes.tsv
OWLNETS_node_metadata.tsv

Even though a new version of MSIG is available in Globus, my machine still had the older TXT files around. The script picked the old TXT file before the new TSV because nodes.txt occurs in the list before nodes.tsv.

Will close this after generating the next Data Distillery context.


Crash while copying infinity check in blueprint sandbox

The mod Blueprint Variables (0.0.7) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event blueprint-variables::on_built_entity (ID 6)
Given logistic container isn't a storage type.
stack traceback:
        [C]: in function 'get_filter'
        __blueprint-variables__/variables-manager.lua:91: in function 'getFilterVariables'
        __blueprint-variables__/control.lua:70: in function <__blueprint-variables__/control.lua:55>

Another mod addressed a similar issue thusly: https://github.com/MESLewis/FilterHelper/commit/167ec1215e1430a2727b9d689cf71b15a2cafe04


Use non-deprecated assertThat() in tests

Update the assertThat imports so it uses the non-deprecated implementation.
This doesn't change the test logic at all.
See #301

The sonar goal failed, but this seems unrelated to my changes (project key missing). Do you have an idea?

The sonar goal failed, but this seems unrelated to my changes (project key missing). Do you have an idea?

It always does for a pull request. I think it's due to the fork repo not having the access token for Sonar Cloud. I'm happy to merge this though as the build has passed.
Thanks for your contribution! :)

Can you please add the hacktoberfest-accepted label to the PR as well?

@pmckeown Can you please add the hacktoberfest-accepted label to the PR as well?

@derlin Done 😄


Expose HasManager and HasToken typeclass methods to we can define instances on our own env types

can you check whether https://github.com/jpvillaisaza/slack-web/pull/55 would help?

PR #55 was now merged to master, I think it fixes the issue. It'll get released very soon together with the servant 0.13 support, so closing this bug.

	Hi there - I’m away from my computer at the moment but you may want to look at my personal fork to see the couple changes I needed to be able to use your library. There was one other thing if memory serves right.

On Tue, Feb 13, 2018 at 12:31 PM -0500, "emmanueltouzery"<EMAIL_ADDRESS>wrote:
PR #55 was now merged to master, I think it fixes the issue. It'll get released very soon together with the servant 0.13 support, so closing this bug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

hmm I see:
instance Exception SlackClientError

I'm not very familiar with this or why it would be needed. Maybe make a PR explaining why it's needed, and this can be discussed there? Unless if  @jpvillaisaza is more familiar with that.

	It’s pretty simple: I want to be able to throw exceptions rather than deal with the either in certain use cases. The instance allows for that - fairly standard practice in Haskell.

On Tue, Feb 13, 2018 at 1:10 PM -0500, "emmanueltouzery"<EMAIL_ADDRESS>wrote:
hmm I see:
instance Exception SlackClientError
I'm not very familiar with this or why it would be needed. Maybe make a PR explaining why it's needed, and this can be discussed there? Unless if  @jpvillaisaza is more familiar with that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@jpvillaisaza do we add that instance Exception SlackClientError? I can make a PR and add it to the upcoming release for servant-0.13.  Here's @ozataman's change: https://github.com/jpvillaisaza/slack-web/commit/1a83aea5132241b1b90ab8acbc8ad88843d796c8

I'm sorry, another thing. I see that this change also adds derive Typeable for SlackClientError. Once again I have no opinion. Do I add it too?

@emmanueltouzery I think that should be fine too.

	Thanks, appreciate it!

On Thu, Feb 15, 2018 at 12:42 AM -0500, "emmanueltouzery"<EMAIL_ADDRESS>wrote:
Closed #53 via 92a4fae.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


When many groups are created the page rendering is strange

What is it?
When displaying a large number of groups with names that combine to be wider than the page, group names are split over multiple lines and do not render right at all.
This PR is to make the navbar horizontally scrollable while pinning the user menu to the top right at all times.

Just noticed that these changes only render nicely if a browser can detect a mouse has side scrolling. I.E the mac magic mouse.
Otherwise a scrollbar is permanently visible.

Scrollbar should now always be visible when there is overflowing content and actually fit in with the concourse design.

Tests have failed trying to fetch package: code.cloudfoundry.org/garden/client/connection/fakes think that package should be: code.cloudfoundry.org/garden/client/connection/connectionfakes as per the garden repos. This isn't anything we have changed for this PR, is something in the ci broken?

Awesome - this makes things look so much better and clears up the terrible mess at the top of the page when you have a lot of groups. nice work @srbry

Before:

After:

Hi all,
My team is also experiencing this unfortunate issue, mostly when we try to view our build pages. Pretty frustrating to try and read the build info, or to retrigger it. Wanted to +1 this issue as a whole.

I'm glad to see that there's a discussion and an implemented solution, but not sure whether horizontal scroll would be the best option. In my experience, horizontal scroll isn't very widely used and can be tricky depending on your mouse. Our team would be fine if the groups were given n extra rows to be listed fully, and the rest of the build info (the yellow bar and below) were to start after that. However, we'd be happy with whatever solution makes sense to the community and Concourse team. We'll be following to see what comes out of this.
Thanks!
Raina
PCF RelEng

Hi @rainmaker I do agree completely, horizontal scrolling was the easiest thing for us to put in with just changing some css. We made sure the scroll bar shows properly when it needs too so you can click and drag it so it works with all mice, although it works far nicer with a mouse that can do horizontal scrolling properly, if you want to play with the format you can use a chrome plugin called stylish and apply this css override:
.content-frame .top-bar .groups {
    flex-grow: 0;
    display: flex;
    flex-direction: row;
    flex-shrink: 0;
    overflow-x: auto;
    overflow-y: hidden;
    position: fixed;
    right: 120px;
    left: 0;
}

.content-frame .top-bar .groups li {
    flex-shrink: 0;
}
.content-frame .top-bar .nav-right {
    flex-shrink: 1;
    position: fixed;
    right: 0;
}
.content-frame .top-bar .groups::-webkit-scrollbar-track {
    background-color: #1A252F;
}
.content-frame .top-bar .groups::-webkit-scrollbar {
    height: 4px;
    background-color: #1A252F;
}
.content-frame .top-bar .groups::-webkit-scrollbar-thumb {
    background-color: #E6E7E8;
}

+1. good fix thanks srbry

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

@srbry This looks good! Sorry for the inactivity, we kinda got ahead of ourselves and had UI changes planned for this area so we hesitated on pulling this in, but it probably makes sense to at least make the current UX better immediately first.
Tried out the CSS changes myself and confirmed that it only affects the given use case (i.e. doesn't introduce any UI changes until the scrollbar needs to appear), so this looks good to me. It would be nice to have vertical scrolling translate to horizontal scrolling as it does on the build page (for the builds under the job header), but that's surprisingly annoying to implement and involves JS, so I don't mind this as-is as it's strictly an improvement over today's UX.
Our CLA bot isn't happy though. Could you look at signing it?

@srbry can you please look at the CLA if you'd like this merged?

This has been re-raised under: https://github.com/concourse/atc/pull/174, the CLA has now been signed


description in output reference is not readable

Describe the bug

Steps to reproduce

Create a kubernetes-mysql
Create a webservice and use the mysql output

Environment

Walrus version: main

Issue 2: Missing some outputs in the list, but you can search it. For example, the username of mysql output:
https://github.com/seal-io/walrus/assets/5697937/b21468e5-2508-4f24-af92-d39914cb1243

Verified in main.


Support pytest plugins

Environment data

VS Code version:  1.59.0-insider
Extension version (available under the Extensions sidebar): v2021.7.1060902895
OS and version: macOS 10.15.7
Python version (& distribution if applicable, e.g. Anaconda): 3.8.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv
Value of the python.languageServer setting: Default

Expected behaviour
It discovers tests
Actual behaviour
The Python extension has run into an unexpected situation
while processing a pytest node during test discovery.  Please
Please open an issue at:
https://github.com/microsoft/vscode-python/issues
and paste the following output there.
nodeid: test/views/test_stations.py::describe_get_stations_with_count::describe_loggernet_data_platform::data_platform::it_queries_station_count
kind: ('function', False)
class: Function
name: data_platform::it_queries_station_count
fspath: /Users/dan/groundwork/GroundNetEngine/test/views/test_stations.py
location: ('test/views/test_stations.py', 42, 'describe_get_stations_with_count.describe_loggernet_data_platform.data_platform::it_queries_station_count')
function: <function describe_get_stations_with_count..data_platform..it_queries_station_count at 0x106ad3d30>
markers: []
user_properties: []
attrnames: ['_ALLOW_MARKERS', 'annotations', 'class', 'delattr', 'dict', 'dir', 'doc', 'eq', 'format', 'ge', 'getattribute', 'gt', 'hash', 'init', 'init_subclass', 'le', 'lt', 'module', 'ne', 'new', 'reduce', 'reduce_ex', 'repr', 'setattr', 'sizeof', 'slots', 'str', 'subclasshook', 'weakref', '_fixtureinfo', '_getobj', '_initrequest', '_nodeid', '_obj', '_prunetraceback', '_pyfuncitem', '_report_sections', '_repr_failure_py', '_request', '_store', 'add_marker', 'add_report_section', 'addfinalizer', 'cls', 'config', 'extra_keyword_matches', 'fixturenames', 'from_parent', 'fspath', 'funcargs', 'function', 'get_closest_marker', 'getmodpath', 'getparent', 'ihook', 'instance', 'iter_markers', 'iter_markers_with_node', 'keywords', 'listchain', 'listextrakeywords', 'listnames', 'location', 'module', 'name', 'nextitem', 'nodeid', 'obj', 'originalname', 'own_markers', 'parent', 'reportinfo', 'repr_failure', 'runtest', 'session', 'setup', 'teardown', 'user_properties', 'warn']
extra info:
fullname: describe_get_stations_with_count.describe_loggernet_data_platform.data_platform::it_queries_station_count
testfunc: describe_get_stations_with_count.describe_loggernet_data_platform.data_platform.it_queries_station_count
parameterized:
traceback:
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/run_adapter.py", line 22, in
main(tool, cmd, subargs, toolargs)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/main.py", line 100, in main
parents, result = run(toolargs, **subargs)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 30, in discover
ec = _pytest_main(pytestargs, [_plugin])
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/config/init.py", line 162, in main
ret: Union[ExitCode, int] = config.hook.pytest_cmdline_main(
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
return self._hookexec(self, self.get_hookimpls(), kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
res = hook_impl.function(*args)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 316, in pytest_cmdline_main
return wrap_session(config, _main)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 269, in wrap_session
session.exitstatus = doit(config, session) or 0
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 322, in _main
config.hook.pytest_collection(session=session)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
return self._hookexec(self, self.get_hookimpls(), kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
res = hook_impl.function(*args)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 333, in pytest_collection
session.perform_collect()
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 641, in perform_collect
hook.pytest_collection_finish(session=self)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
return self._hookexec(self, self.get_hookimpls(), kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
res = hook_impl.function(*args)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 107, in pytest_collection_finish
test, parents = self.parse_item(item)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 77, in parse_item
return parse_item(item)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 172, in parse_item
raise should_never_reach_here(
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 132, in should_never_reach_here
traceback.print_stack()
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 637, in perform_collect
INTERNALERROR>     hook.pytest_collection_modifyitems(
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
INTERNALERROR>     return self._hookexec(self, self.get_hookimpls(), kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
INTERNALERROR>     self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 208, in _multicall
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 80, in get_result
INTERNALERROR>     raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
INTERNALERROR>     res = hook_impl.function(*args)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 92, in pytest_collection_modifyitems
INTERNALERROR>     test, parents = self.parse_item(item)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 77, in parse_item
INTERNALERROR>     return parse_item(item)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 172, in parse_item
INTERNALERROR>     raise should_never_reach_here(
INTERNALERROR> NotImplementedError: Unexpected pytest node (see printed output).
INTERNALERROR>
INTERNALERROR> During handling of the above exception, another exception occurred:
INTERNALERROR>
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 269, in wrap_session
INTERNALERROR>     session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 322, in _main
INTERNALERROR>     config.hook.pytest_collection(session=session)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
INTERNALERROR>     return self._hookexec(self, self.get_hookimpls(), kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
INTERNALERROR>     self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 208, in _multicall
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 80, in get_result
INTERNALERROR>     raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
INTERNALERROR>     res = hook_impl.function(*args)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 333, in pytest_collection
INTERNALERROR>     session.perform_collect()
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/_pytest/main.py", line 641, in perform_collect
INTERNALERROR>     hook.pytest_collection_finish(session=self)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in call
INTERNALERROR>     return self._hookexec(self, self.get_hookimpls(), kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/manager.py", line 84, in
INTERNALERROR>     self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 208, in _multicall
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 80, in get_result
INTERNALERROR>     raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File "/Users/dan/.local/share/virtualenvs/GroundNetEngine-WLpcZVa5/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
INTERNALERROR>     res = hook_impl.function(*args)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 107, in pytest_collection_finish
INTERNALERROR>     test, parents = self.parse_item(item)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 77, in parse_item
INTERNALERROR>     return parse_item(item)
INTERNALERROR>   File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 172, in parse_item
INTERNALERROR>     raise should_never_reach_here(
INTERNALERROR> NotImplementedError: Unexpected pytest node (see printed output).
========================= 22 tests collected in 4.56s ==========================
Traceback (most recent call last):
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/run_adapter.py", line 22, in
main(tool, cmd, subargs, toolargs)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/main.py", line 100, in main
parents, result = run(toolargs, **subargs)
File "/Users/dan/.vscode-insiders/extensions/ms-python.python-2021.7.1060902895/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 44, in discover
raise Exception("pytest discovery failed (exit code {})".format(ec))
Exception: pytest discovery failed (exit code 3)
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

It fails to discover tests even if I delete all the test files except for one.

@dcavanagh Can you share the function and its params? also are you using any pytest plugins?

I've been able to get some basic tests working. It looks like the error
occurs when using @.***_like`. I will keep looking for other cases
Here are the plugins
pytest = ""
pytest-cov = ""
pytest-describe = ""
pytest-freezegun = ""
pytest-mock = ""
pytest-notifier = ""
On Mon, Aug 2, 2021 at 10:01 PM Karthik Nadig @.***>
wrote:

@dcavanagh https://github.com/dcavanagh Can you share the function and
its params? also are you using any pytest plugins?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/16852#issuecomment-891452019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACV47WBNTTB63N7PTBERO7LT25EW7ANCNFSM5BNYMOIA
.

Our current discovery code does not support plugins like pytest-describe. We have plans to improve our discovery to handle plugins.

@karthiknadig This particular plugin had been working and then stopped recently.

Plugins like pytest-describe really help us in managing tests in complex code bases. At the same time some of our devs would like to use the testing UIs in vscode. @karthiknadig can you share any info if and when support for plugins might be worked on?

@roeap We are currently working on this. https://github.com/microsoft/vscode-python/issues/17242 an objective with the re-write of the test adapter is to allow it to work with other plugins.

Thanks for the update and this great extension. Looking forward for this to land.

Will note that in the meantime, this same problem can be solved by pinning pytest-describe==2.0.0 in the environment for testing.  For some reason VSCode only breaks with pytest-describe==2.0.1

Possibly related: https://github.com/microsoft/vscode-python/discussions/19668

Thanks to @kr-hansen comment, I found that uninstalling pytest-pspec "fixes" the issue.
Thank you :D

Hello! We have just finished our testing rewrite and are beginning the roll out to users. If you are able, it would be very helpful to know if your issue still exists on the rewrite! To try it yourself, you need to be on the most recent release of the Python extension and add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"].
You can confirm you have the rewrite enabled by setting  "python.analysis.logLevel": "Trace", in your user settings then check for Experiment 'pythonTestAdapter' is active in your python logs.
Let me know if the rewrite fixes your issue. Thanks!

Generally plugins should now work on the rewrite, please open issues with specific plugins if this is not the case for you. Thanks
Trying the rewrite:
To use the rewrite yourself just add ”python.experiments.optInto": ["pythonTestAdapter"] to your user settings. You can confirm you have the rewrite enabled by setting your log level to trace, via the Developer: Set Log Level command in the command palette. Then check to see if Experiment 'pythonTestAdapter' is active is in your python logs.


New Widget: SearchBar

Provide a widget with the features described in the Patterns– Search section of the Material spec.
Features:

RawSearchBar: just input handling, no decoration
History and auto-completion
Scaffold searchBar

Hope to see this soon :smiley:

It would be cool to implement this into a a table view like ios.
https://www.raywenderlich.com/157864/uisearchcontroller-tutorial-getting-started

@HansMuller Is there any kind of information, when this will be ready? In #6691 someone said that you already had it internally.

@goderbauer is actively working on it. Next week is the Google I/O conference, so there will be a break in the action; we will keep you-all posted after that.

I was just about to start implementing my own version of this. I'm glad to see that it's being added natively! Not to nag you, but has any progress been made recently?

@goderbauer Thanks a lot for the information, this is indeed great progress. I just wanted to make clear that this issue is about Persistent Search, not Expandable Search (by what I don't necessarily want to say, that you aren't aware of that).

a very useful widget, would love to see it soon

Not to keep spamming this thread, but has any progress been made on the non-expandable material search bar?

Good job 💪. Looking forward to using it. I can help too.

@HansMuller
isn't this issue solved by SearchDelegate?

This sprit of this very old issue has been resolved by https://github.com/flutter/flutter/pull/122309 and https://github.com/flutter/flutter/pull/123256.


This version is outdated

I followed the tutorial on medium, however i can't make it work. The first problem is the openlaw url got changed from https://app.openlaw.io to https://lib.openlaw.io/api/v1/default. The submit daft didn't work too. I got the email from openlaw the template was empty.

I just updated the app. Could you tell me if that works for you now?


"GPU process isn't usable" on Ubuntu 22.04 with NVIDIA GPU

AppImage crashes directly on start with
[74043:0507/150338.750904:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

Starting with ./webos-dev-manager-1.5.2.AppImage --no-sandbox or --disable-gpu-sandbox works though. Mentioning this here for reference. I guess it's an Electron thing?
Related:
https://github.com/marktext/marktext/issues/2675
https://github.com/ebkr/r2modmanPlus/issues/735

Hi, I have updated electron version, it should be working now.

Tested webos-dev-manager-1.7.7.AppImage to work! Thanks!


%user% doesn't work without a . after it.

For the .acr command, when you type %user% the bot responds with %user$ instead:

Once you type %user%. then it works as intended:

Cannot reproduce on 1.7

Delete your old custom reaction before creating a new one with the same trigger.


Update vpn-gateway-virtual-wan-vpn-profile-intune.md

Updated line 55 regarding being able to modify the   value.

Learn Build status updates of commit 8e0226a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

includes/vpn-gateway-virtual-wan-vpn-profile-intune.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@cherylmc,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Videoplayer no longer working after updating to 2.0

We're in the process of updating our nuget packages of our xamarin.forms apps. This package is one of the packages being updated. However, after updating to 2.0.2019.716 or higher, our video player doesn't work anymore. Neither in Android nor iOS.
We use an empty forms page with a stacklayout on it, containing a MediaElement control. We use a https url as source, and have custom headers because the url points to an API for which we need to authenticate. the code looks like this:
        var contentStack = new StackLayout() { Orientation = StackOrientation.Vertical, Spacing = 0 };
        Content = contentStack;

        _mediaElement = new InTheHand.Forms.MediaElement();
        _mediaElement.HorizontalOptions = LayoutOptions.Fill;
        _mediaElement.VerticalOptions = LayoutOptions.Center;
        _mediaElement.BackgroundColor = Color.Black;
        _mediaElement.HeightRequest = 400;

        _mediaElement.AutoPlay = true;

        _mediaElement.HttpHeaders.Add("Authorization", $"bearer {<A token>}");
        _mediaElement.Source = new Uri("<the url>");

        _mediaElement.ShowsPlaybackControls = true;
        contentStack.Children.Add(_mediaElement);

This code worked fine on 1.0.2019.118. After upgrading it doesn't work anymore. Could this have something to do with custom headers?
Is there a problem is (for now) not upgrading? The 2.0 version claims to have XF4.0 support. We are using XF4.0, and the 1.0.2019.118 seems to also work with XF4.0
What can we do to fix this issue?

That's odd. You can definitely use the v1.0 version with newer versions of XF but 2.0 has some optimisations (e.g. fast renderers).  Yes I'm calling the Init. I'm sot sure what I can do to find the issue. There is no loggin of anything when the player opens, and it used to work fine.

As some extra info:
we use the component as follows:

A webview opens a document, in which media can be embedded
When the document contains a video, we show an image of a play button
When the play button is clicked, we execute some code that does a pushmodalasync of the page shown in the example

Hi, it looks like in the transition part of the HttpHeaders implementation in the native renderer was lost and so these are not being passed. I'm working on a fix.

Great!

This should now be fixed in the latest NuGet 2.0.2019.815

Nice! I'll check it out Monday!

hurray, it works again! thanks

@peterfoot
Hmm we ran into a little snag. I didn't test the new package myself, but a collegue told me it works now. This is true for android, but for iOS it seems even more broken than it was. Now iOS still doesn't play the video. I've debugged, and it seems in iOS the http source is not even requested (no call is ever done).
Furthermore, when closing the page that is displaying the mediaelement control, an exception occurs:
SIGABRT: Cannot access a disposed object. Object name: 'MediaElementRenderer'.
NSObject.get_SuperHandle ()
UIViewController.get_View ()
IVisualElementRenderer.get_NativeView ()
VisualElementPackager.OnChildRemoved (Xamarin.Forms.VisualElement view)
VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement)
VisualElementPackager.Dispose (System.Boolean disposing)
VisualElementRenderer`1[TElement].Dispose (System.Boolean disposing)
NSObject.Dispose ()
DisposeHelpers.DisposeModalAndChildRenderers (Xamarin.Forms.Element view)
INavigation.PopModalAsync (System.Boolean animated)
For now, we have downgraded to 1.0 again

Sorry, I think I only read Android as the affected platform (because someone else reported just that separately). I will get back on it and attack the iOS renderer next week

Hi, just an update - I've fixed the original bug where the video is not showing however I haven't done a release yet as I've found another bug with layout when the device is rotated, hope to have a fix shortly, if not a simple fix I'll release a preview nuget package to at least confirm the original issue is resolved.

Please check out the latest release on NuGet

This bug is resolved in 2.0.2019.913

@peterfoot
I've tried 2.0.2019.913 but the problem persists

@peterfoot
Any news on this? We are still stuck on an old version. I've taken a quick look at the code, but my knowlegde of Xamarin.iOS is not extensive enough to understand what the correct solution for this issue should be.

I wasn't able to replicate it - even creating a modal dialog and trying different ways to get the renderer to dispose. However I've added some more protection around the disposal which I think should avoid any chance of this happening. The latest should appear on NuGet shortly - 2.0.2019.1004

I've tested it, and the error is now different again. When popping the dialog, an object reference error now occurs:
System.NullReferenceException: Object reference not set to an instance of an object
at Xamarin.Forms.Platform.iOS.DisposeHelpers.DisposeModalAndChildRenderers (Xamarin.Forms.Element view) [0x00036] in D:\a\1\s\Xamarin.Forms.Platform.iOS\DisposeHelpers.cs:22
at Xamarin.Forms.Platform.iOS.Platform.Xamarin.Forms.INavigation.PopModalAsync (System.Boolean animated) [0x00143] in D:\a\1\s\Xamarin.Forms.Platform.iOS\Platform.cs:119
at Xamarin.Forms.Application+NavigationImpl.OnPopModal (System.Boolean animated) [0x0005d] in D:\a\1\s\Xamarin.Forms.Core\Application.cs:380
Maybe it has to do with the fact that we close the popup while the video is still playing?

any news on this?

Sorry, I think this was fixed in the 2.0.2019.1021 release.

I'm afraid the 1021 version hasn't fixed the issue. It remains exactly the same. I'll try to create a repro project so we can get to the bottom of this.

Thanks, that would be very helpful. What version of Xamarin Forms are you using? I will have a look at their code for DisposeHelpers and see what it is trying to do.

I was able to replicate it in a test project, and I now also understand why you coudn't. We have a bit of a special situation in our case. The popmodalasync call to close the dialog with the videoplayer is called from within a "Device.BeginInvokeOnMainThread" method. This is because it is part of a generic method for "going back" in our app, which is not always called from the UI thread. This call ensures that it is.
However, the old version didn't have any dispose issues with the same code, and no other controls seem to have this issue. So a fix would still be very much appreciated :)
I've attached the repro, don't be fooled by the name of the project, it was originally designed to test something else :)
CollectionViewSpacing.zip

Thanks, I was able to pinpoint the issue. I've reworked the Dispose method to remove the problem. Latest code is in 2.0.2019.1107

Nice! Thanks!

I'm sorry to reopen this, but it turns out we are still experiencing crashes when closing the mediaplayer dialog. Downgrading to version 1.x fixes it. There doesn't seem to be any proper stacktrace. but the error logged by the debugger is shown below.
The error doesn't actually crash the app, but it does lock it up, making it unresponsive and uncloseable.

Click to show the error
=================================================================
	Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
=================================================================
Native stacktrace:
0x1058e5614 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x1058db4d4 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x1058e9d48 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : mono_pmip
0x1888e29fc - /usr/lib/system/libsystem_platform.dylib : <redacted>
0x189721280 - /System/Library/Frameworks/Foundation.framework/Foundation : <redacted>
0x18971eb20 - /System/Library/Frameworks/Foundation.framework/Foundation : <redacted>
0x18ec96d24 - /System/Library/Frameworks/AVFoundation.framework/AVFoundation : <redacted>
0x188710a38 - /usr/lib/system/libdispatch.dylib : <redacted>
0x1887117d4 - /usr/lib/system/libdispatch.dylib : <redacted>
0x1886bf008 - /usr/lib/system/libdispatch.dylib : <redacted>
0x188c64b20 - /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation : <redacted>
0x188c5fa58 - /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation : <redacted>
0x188c5efb4 - /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation : CFRunLoopRunSpecific
0x18ae6079c - /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices : GSEventRunModal
0x1b54c1c38 - /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore : UIApplicationMain
0x10384e780 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x102fbc0bc - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x102fbbf44 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x1008a8360 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x10110c034 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : (null)
0x1058ed170 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : mono_pmip
0x1059ab194 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/*****.iOS.app/*****.iOS : mono_pmip
0x1059b1450 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A

522088/.iOS.app/.iOS : mono_pmip
0x1058cb104 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/.iOS.app/.iOS : (null)
0x105aba268 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/.iOS.app/.iOS : xamarin_localized_string_format_9
0x1008a8258 - /var/containers/Bundle/Application/85ACFCBF-8B11-4FB0-AE94-C07A9A522088/.iOS.app/.iOS : (null)
0x1887228e0 - /usr/lib/system/libdyld.dylib :
=================================================================
Basic Fault Address Reporting
Memory around native instruction pointer (0x187eaa0e0):0x187eaa0d0  1f 04 00 f1 2b 01 00 54 08 00 40 f9 08 81 7d 92  ....+..T..
@...}.
0x187eaa0e0  08 11 40 f9 08 ad 7d 92 08 05 40 f9 08 01 40 39  ..@...}...@...@9
0x187eaa0f0  00 01 00 12 c0 03 5f d6 00 00 80 52 c0 03 5f d6  ..........R...
0x187eaa100  60 02 00 b4 60 02 f8 b6 a8 20 1d f0 08 a1 3c 91  ....... .
...<.
=================================================================
Managed Stacktrace:
  at <unknown> <0xffffffff>
  at UIKit.UIApplication:UIApplicationMain <0x00007>
  at UIKit.UIApplication:Main <0x0002b>
  at UIKit.UIApplication:Main <0x00043>
  at *****.iOS.Application:Main <0x0007f>
  at System.Object:runtime_invoke_dynamic <0x00103>

=================================================================

Thanks, looking into this but stacktrace doesn't give much away

yeah I know, but unfortunately there is no more data shown than this.

Thanks, if it's hanging in the UI thread I have a suspicion that one of the observers is being called when the native AVPlayer is disposed and it can be fixed by changing the order of calls inside the Dispose method. It's tricky because it is probably not reproducable when the debugger is connected.

Eventually had to rewrite the renderer without implementing as a FastRenderer. This is now working in 2.0.2020. Some details in this post (https://peterfoot.net/2020/01/08/mediaelement-enhancements/)

All future MediaElement work will take place at https://github.com/xamarin/XamarinCommunityToolkit


"ROS distro is not set"

Following instructions on this page: https://google-cartographer-ros.readthedocs.io/en/latest/compilation.html
Ubuntu: 18.04.4
"rosdep install --from-paths src --ignore-src --rosdistro=${ROS_DISTRO} -y" returns the following error:
dpkg-query: no packages found matching liblua5.2-dev
dpkg-query: no packages found matching libprotobuf-dev
dpkg-query: no packages found matching libpcl-dev
dpkg-query: no packages found matching libprotoc-dev
dpkg-query: no packages found matching gfortran
dpkg-query: no packages found matching qtbase5-dev
dpkg-query: no packages found matching libgflags-dev
dpkg-query: no packages found matching libcairo2-dev
dpkg-query: no packages found matching libeigen3-dev
dpkg-query: no packages found matching libsuitesparse-dev
dpkg-query: no packages found matching google-mock
dpkg-query: no packages found matching protobuf-compiler
dpkg-query: no packages found matching libgoogle-glog-dev
dpkg-query: no packages found matching libatlas-base-dev
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies (ROS distro is not set. Make sure ROS_DISTRO environment variable is set, or use --rosdistro option to specify the distro, e.g. --rosdistro indigo):
cartographer_ros_msgs: Cannot locate rosdep definition for [std_msgs]
cartographer: No definition of [boost] for OS version [bionic]
cartographer_ros: Cannot locate rosdep definition for [rosunit]
cartographer_rviz: Cannot locate rosdep definition for [rviz]
ceres-solver: Cannot locate rosdep definition for [catkin]

You have to replace ${ROS_DISTRO} by your actual ROS distro, in your case melodic


Why create new environment every time on client?

I see here: https://github.com/este/este/blob/master/components/app/createRelayEnvironment.js#L21 that you are creating a new environment every page load.  However, within the next.js with-relay-modern repo, I see that they are reusing the environment client side (https://github.com/zeit/next.js/blob/canary/examples/with-relay-modern/lib/createRelayEnvironment.js#L4). I'm wondering why you made this design decision?
Side note: I am currently getting the following error: https://stackoverflow.com/questions/49940509/relay-when-refetch-container-is-called-clears-different-fragment-container when I reuse the store, but if I create a new one like you are doing, this error no longer appears. So I'm wondering if the example in the next.js repo is incorrect.

It's cheap and yes.

Thanks for the response @steida! By yes do you mean that the example in next.js is incorrect?

Probably is.


HBASE-23349 : Expose max refCount among all compacted store files and…

… reopen region for threshold value

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+0 :ok:
mvndep
0m 41s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 12s
master passed

+1 :green_heart:
compile
3m  3s
master passed

+1 :green_heart:
checkstyle
2m 44s
master passed

+1 :green_heart:
shadedjars
4m 38s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  3s
master passed

+0 :ok:
spotbugs
4m 11s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
10m  4s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 55s
the patch passed

+1 :green_heart:
compile
3m  6s
the patch passed

+1 :green_heart:
cc
3m  6s
the patch passed

+1 :green_heart:
javac
3m  6s
the patch passed

+1 :green_heart:
checkstyle
2m 41s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
15m 40s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
hbaseprotoc
3m  1s
the patch passed

+1 :green_heart:
javadoc
2m  0s
the patch passed

+1 :green_heart:
findbugs
10m 48s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 42s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
0m 34s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 39s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
0m 27s
hbase-protocol in the patch passed.

+1 :green_heart:
unit
1m 53s
hbase-client in the patch passed.

-1 :x:
unit
311m  9s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
2m 52s
The patch does not generate ASF License warnings.

402m 36s

Reason
Tests

Failed junit tests
hadoop.hbase.master.procedure.TestSCPWithReplicas

hadoop.hbase.master.TestSplitWALManager

hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.client.TestAsyncTableBatch

hadoop.hbase.client.TestFromClientSideWithCoprocessor

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/890

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 5238e0bff80e 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-890/out/precommit/personality/provided.sh

git revision
master / 97e0107000

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/1/testReport/

Max. process+thread count
4709 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+0 :ok:
mvndep
0m 40s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 15s
master passed

+1 :green_heart:
compile
3m  0s
master passed

+1 :green_heart:
checkstyle
2m 31s
master passed

+0 :ok:
refguide
5m 29s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
4m 34s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
5m  4s
master passed

+0 :ok:
spotbugs
3m 42s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
24m  0s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 39s
the patch passed

+1 :green_heart:
compile
3m 23s
the patch passed

+1 :green_heart:
cc
3m 23s
the patch passed

+1 :green_heart:
javac
3m 23s
the patch passed

+1 :green_heart:
checkstyle
2m 47s
the patch passed

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
5m 37s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
4m 37s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
16m  8s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
hbaseprotoc
8m 39s
the patch passed

+1 :green_heart:
javadoc
5m 11s
the patch passed

+1 :green_heart:
findbugs
25m  1s
the patch passed

_ Other Tests _

-1 :x:
unit
221m 19s
root in the patch failed.

+1 :green_heart:
asflicense
5m  1s
The patch does not generate ASF License warnings.

363m 28s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshotNoCluster

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/890

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux 614ef3bacda9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-890/out/precommit/personality/provided.sh

git revision
master / 97e0107000

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/testReport/

Max. process+thread count
5578 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-890/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Z-Wave sensor history and More Info using integer view, not decimal graph

This started after upgrading to 0.12.0. I have a Aeotech Multisensor 6 that has temperature and some other sensors.
Before the upgrade, clicking the Temperature sensor gave a More Info dialog with a nice graph showing temperature vs. time. Now it shows a colorbar (used elsewhere for integer settings). This happens for the Multisensor but not for some other Z-wave sensors I have (which still properly show the graph).
In the zwcfg.xml file, I find things that indicate it should be decimal type, not short or some other int.
			<CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="5" innif="true">
				<Instance index="1" />
				<Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="F" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="77.9" />
				<Value type="decimal" genre="user" instance="1" index="3" label="Luminance" units="lux" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0" />
				<Value type="decimal" genre="user" instance="1" index="5" label="Relative Humidity" units="%" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="37" />
				<Value type="decimal" genre="user" instance="1" index="27" label="Ultraviolet" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0" />

This happens when there is no unit_of_measurement defined for the entity.
On Sun, Jan 31, 2016 at 9:02 PM, Nick Touran<EMAIL_ADDRESS>wrote:

[image: screenshot from 2016-01-31 20-47-50]
https://cloud.githubusercontent.com/assets/5360219/12709178/e47a7d2a-c85d-11e5-9c28-8e3b9806812f.png
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/1079#issuecomment-177765056
.

--
PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.

Ok that's a good lead. I wonder what might have happened during the upgrade to cause it to lose its unit of measurement info. For this sensor, the state attributes are showing:
{
  "friendly_name": "Temperature",
  "unit_of_measurement": "°C",
  "node_id": 2,
  "battery_level": 100
}

So it seems that it has a unit of measurement figured out. Maybe it doesn't like the degree symbol?

Same for me. If you don't care loosing history, delete home-assistant.db does the trick for me.
Hope it helps.

The degree symbol should just work.
Don't delete your history just yet. It would be better to investigate and get this fixed.
You can look at the API results by going to this url (probably need to update entity filter):
https://localhost:8123/api/history/period?filter_entity_id=sensor.temperature
Any states that are showing weird data?
This is the code that decides which graph to show

I didn't delete but after 24 hours the graph switched to the proper style! I think maybe it had something wrong but the more info box only holds a day or so of data. It's working for me now with no changes on my part. If it happens again I'll look at the API results and post the offending data. I think it's safe to close for now.


Confusing status terminology

We currently use "active" to describe two distinct things:

a user can be either active or unavailable
users recently online have the "Active now" tooltip

I find it very confusing that you can be unavailable and active at the same time (especially because according to our status terminology active and unavailable are mutually exclusive).

@zulipbot claim

This should be discussed before being worked on.

Oh Cool , Since the users recently online have the Active now tooltip , Displaying an Recently online in  place of it and Active now for the former one looks more sensible , isn't it ?

Recently is not the same as now. I see two options:

renaming the opposite of unavailable to available
changing last active to last online (or last seen)

Which of these is preferable should be discussed on CZO ... I just created a topic for that.

Hey , Going with the 2nd option ( changing last active to last online or last seen ) looks more sensible as rightly discussed within the topic .

Yes changing the tooltips to "Online now" and "Last online: ..." appears to be the best choice. Feel free to work on a PR.

@zulipbot claim

Hey, can I work on this issue ?

Hey @dynamoh , That's really nice but I am about to submit a Pr regrading this issue now .

ok no problem


Odoo session reaper

This PR implements Odoo session management. In detail,

We disable Odoo's built-in session garbage-collection.
We implement a service to delete any Odoo session that's been inactive for longer than a configurable number of minutes. This service runs every hour on the hour.

Here's some notes about what we've found out about the way Odoo 14 manages sessions.
Session lifecycle
When you hit Odoo w/o having logged in, you get a 90-day-valid anon session cookie a which you can only really use to access the login page and download pub assets like images and CSS. There's a corresponding serialised session state s(a) Odoo stores under data/sessions.

https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1456

If you don't log in, s(a) doesn't get deleted until the session GC procedure kicks in, which is the next time someone logs in after one week:

https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1152
https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1372

But if you log in, you get a 90-day-valid authenticated session cookie c and a corresponding serialised session s(c) whereas s(a) gets deleted. When you log out, Odoo deletes s(c) but it redirects you to the login page, so you get a fresh anon cookie a' and session state s(a') again. So the session dir will fill up w/ junk over time. If you don't log out and just close the browser window, you'll still be able to use your cookie c for at least a week as inactive sessions are garbage-collected on a weekly-basis:

https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1152
https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1372

Disabling session GC
Turns out you can stop Odoo from deleting inactive sessions after a week:

https://github.com/odoo/odoo/blob/tmp.14.0/odoo/http.py#L1164-L1169

This means sessions can last as long as 90 days. Of course, you'll have to clean up stale sessions yourself, but that we'd have to do anyway since Odoo seems to leak session state, so even with the GC procedure in place, you could wind up with one gazillion files in data/sessions. Too many files in there also means slow directory access which in turn means Odoo slows down too since it has to check session state on each call.
Inactive sessions
Every time you hit Odoo with a valid session cookie c, the corresponding serialised session state s(c) gets updated. This means we've got an easy way to figure out how long a session has been inactive: just look at the last-modified file attr of s(c).


This is way, old,... could we get a new sample?

[Enter feedback here]

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

ID: ac828919-7780-c626-d071-724e0cbc5d56
Version Independent ID: 47d85824-56f3-9fa1-4348-30c864bc756b
Content: C / C++ ODBC app accessing an SQL database - ODBC Driver for SQL Server
Content Source: docs/connect/odbc/cpp-code-example-app-connect-access-sql-db.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-davidengel

@LeeRuns -- Lee, thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@David-Engel -- David, please look into this issue.

A couple of simple examples without error control to explain how to say...compile with cmake...would be great.
Principal
VESL
www.vesl.tech

From: William Anton Rohm @.>
Sent: Tuesday, January 18, 2022 3:14:35 PM
To: MicrosoftDocs/sql-docs @.>
Cc: Lee Runyon @.>; Mention @.>
Subject: Re: [MicrosoftDocs/sql-docs] This is way, old,... could we get a new sample? (Issue #7202)
@LeeRunshttps://github.com/LeeRuns -- Lee, thank you for your feedback. Please consider these resources:

SQL Server on Microsoft Q&Ahttps://docs.microsoft.com/answers/products/sql-server
DBA Stack Exchangehttps://dba.stackexchange.com/questions/tagged/sql-server
Stack Overflowhttps://stackoverflow.com/questions/tagged/sql-server

@David-Engelhttps://github.com/David-Engel -- David, please look into this issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/sql-docs/issues/7202#issuecomment-1015882262, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADZNMPRSRGCMYHURMQCIP3DUWXQ4XANCNFSM5MBUM7QQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

The last time i went to run this it failed in vs 2022, Being able to do odbc connections is a common challenge for those supporting manufacturing and businesses which are not solely tech based. While I would prefer to do graph, these samples remain important. Would be happy to gain a collaborator here to support. Would like to even add examples for porting odbc to other odd sources like ms access files or csv. This will help cpp developers see that python and R are not the only language we can use to import and analyze data.

@LeeRuns Following up. Would it be possible for you to submit a pull request yourself, to add new examples? It's much more likely to get triaged than creating an issue that languishes for a year (we are that busy).

Barring specific recommendations on how to improve this article specific to connecting to SQL Server (other data sources are out of scope for this page), I'm going to close this issue. Feel free to @ me or simply open a new PR with suggestions, for anything else related to this issue.
Thanks,
David
#please-close


[improve][broker] PIP-380: Support-setting-up-specific-namespaces-to-skipping-the-load-shedding

PIP: PIP-380 #23304
Motivation
https://github.com/apache/pulsar/pull/23304
Modifications
Add a new configuration loadBalancerSheddingExcludedNamespaces to allow disabling the load balancer shedding for specific namespaces.
Documentation

[ ] doc
[x] doc-required
[ ] doc-not-needed
[ ] doc-complete

@heesung-sn Updated. PTAL again.

LGTM


Add base class grouping and merge groupings into single operator

Closes #245

I just now looked at the unit tests. They're testing good situations, but seem to be overly complex - to test one grouping handler we need to pass the input through the operator + all the handlers. My suggestion:

Change createGroupingOperator function to optionally take an array of grouping handlers. Default to whatever is used now. This will allow us to test the operator behavior with stub handlers.
Export each grouping handler as @internal API. This will allow us to test each of them separately.

Added suggested changes to createGroupingOperator.
Changed unit tests to test grouping functions instead of the createGroupingOperator


The type of timeZone could be undefined but it's marked as a string only instead

⚙ Compilation target
es5
⚙ Library
Intl
Missing / Incorrect Definition
The type of Intl.DateTimeFormat.prototype.resolvedOptions().timeZone is incorrectly set to only string where it could also be undefined.
Sample Code
// TypeScript should raise an error in the next line since the return value can be `undefined`
const getTimeZone = (): string => {
  return new Intl.DateTimeFormat().resolvedOptions().timeZone;
};

Documentation Link
See possible values for the timeZone property in MDN resolvedOptions(), where undefined is included.

https://github.com/microsoft/TypeScript/issues/55869 ?

See https://github.com/microsoft/TypeScript/issues/55869#issuecomment-1736456729.
string is the correct type according to the specification; Chrome is apparently operating out of spec.

See #55869, the spec says this should be a string, no?

Really good catch! I've a few questions left so I've posted them there.:)

Chrome is apparently operating out of spec.

You're right @fatcerberus ! Chrome is still returning undefined in some cases, so it's either a bug on their end or misleading definitions in ECMAScript.:)
Closing this issue as duplicated now. Thanks


Refactor ActionCreator/Fields component to support different types of views

Fields components currently support one view type and have a hacky implementation of enabling the tabs view for Navigate to action.
We want to refactor the component in such a way that it is able to support different views for different actions if need be.

Closing this task, since Ravi will take up the re-design and he can make tasks according to his milestones