Expose the mock provider for other packages to use in tests

Codecov Report

Merging #62 (22a0ae0) into main (f000bb6) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main       #62    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           50        60    +10
  Lines         3413      4197   +784
==========================================
+ Hits          3413      4197   +784

Impacted Files
Coverage Δ

pkg/i18n/en_base_config_descriptions.go
100.00% <ø> (ø)

pkg/i18n/en_base_error_messages.go
100.00% <ø> (ø)

pkg/config/cobracmd.go
100.00% <100.00%> (ø)

pkg/config/config.go
100.00% <100.00%> (ø)

pkg/dbsql/crud.go
100.00% <100.00%> (ø)

pkg/dbsql/mock_provider.go
100.00% <100.00%> (ø)

pkg/ffapi/apiserver.go
100.00% <100.00%> (ø)

pkg/ffapi/apiserver_config.go
100.00% <100.00%> (ø)

pkg/ffapi/favicons.go
100.00% <100.00%> (ø)

pkg/ffapi/handler.go
100.00% <100.00%> (ø)

... and 9 more

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


Plane class & Vector stuff

Impl plane class & new methods in vectors class:

sqrLength
equals(Vector vector, float epsilon)

I think I will merge it in the next few days.


Add class attribute on link

Hi, Very nice editor, good job.
Is it possible to add a class attribute (and the class name ) for links ? I'm missing something?

@capetrel There is no function to add a class to the A tag.


Bigtable: root package docs are missing

Extracted from https://github.com/googleapis/google-cloud-java/pull/5071#issuecomment-490117286.
Cloud Bigtable has a package-info.java:
https://github.com/googleapis/google-cloud-java/blob/master/google-cloud-clients/google-cloud-bigtable/src/main/java/com/google/cloud/bigtable/package-info.java
But it's javadoc doesn't seem to be generated and returns a 404:
https://googleapis.github.io/google-cloud-java/google-cloud-clients/apidocs/index.html?com/google/cloud/bigtable/package-summary.html

Was looking earlier - the problem is that there are no .java files in com.google.cloud.bigtable (just packages). Adding a "Test.java" to the directory created a package-summary.html file. I'm not sure if this is a javadoc bug, but in the meantime we can add two links to the README - one to point to the admin API javadoc, and one to point to the data API javadoc.

Looks like we can workaround it using an empty package protected file:
https://stackoverflow.com/questions/1138390/javadoc-for-package-info-java-only

I'm not sure if I want to add an empty file to get the javadoc to generate the page. @chingor13 WDYT?

I think the correct long-term solution is the reorganization of the javadocs by artifact (service). This link would link to the package index page for the google-cloud-bigquery artifact.

But I would still like to have the documentation in https://github.com/googleapis/google-cloud-java/blob/master/google-cloud-clients/google-cloud-bigtable/src/main/java/com/google/cloud/bigtable/package-info.java to be published regardless of where the readme link points to


[ldd-vgr] <spacecraft_clock_count_partition should be a integer>

Issue Type
bug
Describe the issue identified (if applicable)
The spacecraft_clock_count_partition is currently described as:

<
<
<

	<xs:pattern value='[0-9]?[0-9]/[0-9]{5}:[0-9]{2}(:[0-9]{3})?'/>
 <xs:minLength value="1"/>
 <xs:maxLength value="255"/>

It really should be an integer, as it is only the partition part of the sclk string.  In the VGR RAV1CUIN instance the partition values can be 0, 1, 2, 3,or 4.
Describe the solution you'd like
change spacecraft_clock_count_partition to an integer.
Describe alternatives you've considered
none
LDD Dictionary Version
PDS4 IM Version
1.16
Need-by Date
July 20, 2023
Additional context
Add any other context or examples products

https://github.com/pds-data-dictionaries/ldd-vgr/pull/9

Resolved by merge of aforementioned PR.


HDDS-1942. Support copy during S3 multipart upload part creation

Uploads a part by copying data from an existing object as data source
Documented here:
https://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html
See: https://issues.apache.org/jira/browse/HDDS-1942

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
65
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
31
Maven dependency ordering for branch

+1
mvninstall
666
trunk passed

+1
compile
412
trunk passed

+1
checkstyle
73
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
970
branch has no errors when building and testing our client artifacts.

+1
javadoc
172
trunk passed

0
spotbugs
477
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
698
trunk passed

_ Patch Compile Tests _

0
mvndep
19
Maven dependency ordering for patch

+1
mvninstall
584
the patch passed

+1
compile
381
the patch passed

+1
javac
381
the patch passed

+1
checkstyle
71
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
671
patch has no errors when building and testing our client artifacts.

+1
javadoc
156
the patch passed

+1
findbugs
704
the patch passed

_ Other Tests _

+1
unit
334
hadoop-hdds in the patch passed.

-1
unit
2991
hadoop-ozone in the patch failed.

+1
asflicense
42
The patch does not generate ASF License warnings.

9182

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.hdds.scm.pipeline.TestRatisPipelineProvider

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

hadoop.ozone.client.rpc.Test2WayCommitInRatis

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux a8dd26e8e4a8 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / cf5d895

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/1/testReport/

Max. process+thread count
5065 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
26
Maven dependency ordering for branch

+1
mvninstall
576
trunk passed

+1
compile
348
trunk passed

+1
checkstyle
76
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
840
branch has no errors when building and testing our client artifacts.

+1
javadoc
154
trunk passed

0
spotbugs
452
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
664
trunk passed

_ Patch Compile Tests _

0
mvndep
18
Maven dependency ordering for patch

+1
mvninstall
583
the patch passed

+1
compile
393
the patch passed

+1
javac
393
the patch passed

+1
checkstyle
71
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
670
patch has no errors when building and testing our client artifacts.

+1
javadoc
165
the patch passed

+1
findbugs
685
the patch passed

_ Other Tests _

+1
unit
287
hadoop-hdds in the patch passed.

-1
unit
1613
hadoop-ozone in the patch failed.

+1
asflicense
42
The patch does not generate ASF License warnings.

7379

Reason
Tests

Failed junit tests
hadoop.ozone.TestMiniChaosOzoneCluster

hadoop.ozone.client.rpc.Test2WayCommitInRatis

hadoop.ozone.client.rpc.TestFailureHandlingByClient

hadoop.hdds.scm.pipeline.TestNode2PipelineMap

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 82a979cf92cb 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9b8359b

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/2/testReport/

Max. process+thread count
3935 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
1147
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
48
Maven dependency ordering for branch

+1
mvninstall
698
trunk passed

+1
compile
419
trunk passed

+1
checkstyle
76
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
884
branch has no errors when building and testing our client artifacts.

+1
javadoc
162
trunk passed

0
spotbugs
481
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
705
trunk passed

_ Patch Compile Tests _

0
mvndep
19
Maven dependency ordering for patch

+1
mvninstall
586
the patch passed

+1
compile
407
the patch passed

+1
javac
407
the patch passed

+1
checkstyle
87
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
706
patch has no errors when building and testing our client artifacts.

+1
javadoc
164
the patch passed

+1
findbugs
751
the patch passed

_ Other Tests _

+1
unit
365
hadoop-hdds in the patch passed.

-1
unit
507
hadoop-ozone in the patch failed.

+1
asflicense
38
The patch does not generate ASF License warnings.

7905

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 330fe7eaf930 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6244502

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/3/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/3/testReport/

Max. process+thread count
1382 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thanks the review @lokeshj1703.

Can we also add a unit test related to same?

Sure, I created a real unit test. Will push it soon...

Thanks the review @bharatviswa504

Related to eTag I think we don't have backend implemented but for x-amz-copy-source-if-unmodified-since we can use lastModified from KeyInfo and do this right?

Yes, it's true. Let's do it in a separated jira (opened HDDS-1997). Can be better to do it in a separated phase as it's not a blocking feature for using ozone as a docker registry backend, and also it requires more code (especially more testing code) and can be easier to review in a separated step.

Thanks the review @bharatviswa504

Related to eTag I think we don't have backend implemented but for x-amz-copy-source-if-unmodified-since we can use lastModified from KeyInfo and do this right?

Yes, it's true. Let's do it in a separated jira (opened HDDS-1997). Can be better to do it in a separated phase as it's not a blocking feature for using ozone as a docker registry backend, and also it requires more code (especially more testing code) and can be easier to review in a separated step.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
84
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

0
mvndep
11
Maven dependency ordering for branch

+1
mvninstall
631
trunk passed

+1
compile
370
trunk passed

+1
checkstyle
61
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
826
branch has no errors when building and testing our client artifacts.

+1
javadoc
155
trunk passed

0
spotbugs
424
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
612
trunk passed

_ Patch Compile Tests _

0
mvndep
19
Maven dependency ordering for patch

+1
mvninstall
554
the patch passed

+1
compile
361
the patch passed

+1
javac
361
the patch passed

-0
checkstyle
34
hadoop-ozone: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
677
patch has no errors when building and testing our client artifacts.

+1
javadoc
150
the patch passed

+1
findbugs
631
the patch passed

_ Other Tests _

+1
unit
352
hadoop-hdds in the patch passed.

-1
unit
3260
hadoop-ozone in the patch failed.

+1
asflicense
51
The patch does not generate ASF License warnings.

9038

Reason
Tests

Failed junit tests
hadoop.ozone.container.server.TestSecureContainerServer

hadoop.ozone.scm.TestXceiverClientManager

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.hdds.scm.pipeline.TestRatisPipelineProvider

hadoop.ozone.TestMiniOzoneCluster

hadoop.ozone.client.rpc.TestOzoneRpcClientForAclAuditLog

hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

hadoop.ozone.client.rpc.TestReadRetries

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 31f3792bf7c2 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 10ec31d

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/4/artifact/out/diff-checkstyle-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/4/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/4/testReport/

Max. process+thread count
4199 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
44
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

0
mvndep
26
Maven dependency ordering for branch

+1
mvninstall
598
trunk passed

+1
compile
340
trunk passed

+1
checkstyle
62
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
820
branch has no errors when building and testing our client artifacts.

+1
javadoc
163
trunk passed

0
spotbugs
432
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
630
trunk passed

_ Patch Compile Tests _

0
mvndep
18
Maven dependency ordering for patch

+1
mvninstall
574
the patch passed

+1
compile
385
the patch passed

+1
javac
385
the patch passed

-0
checkstyle
36
hadoop-ozone: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
649
patch has no errors when building and testing our client artifacts.

+1
javadoc
154
the patch passed

+1
findbugs
674
the patch passed

_ Other Tests _

+1
unit
293
hadoop-hdds in the patch passed.

-1
unit
2091
hadoop-ozone in the patch failed.

+1
asflicense
39
The patch does not generate ASF License warnings.

7768

Reason
Tests

Failed junit tests
hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.container.server.TestSecureContainerServer

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 6745475e8bcc 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ee7c261

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/5/artifact/out/diff-checkstyle-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/5/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/5/testReport/

Max. process+thread count
5301 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

+1 LGTM.
Need to verify test failures, for acceptance test not able to verify them, as it is opening an html code contained in Github.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
44
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

0
mvndep
17
Maven dependency ordering for branch

+1
mvninstall
622
trunk passed

+1
compile
382
trunk passed

+1
checkstyle
83
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
848
branch has no errors when building and testing our client artifacts.

+1
javadoc
179
trunk passed

0
spotbugs
454
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
660
trunk passed

_ Patch Compile Tests _

0
mvndep
21
Maven dependency ordering for patch

-1
mvninstall
288
hadoop-ozone in the patch failed.

-1
compile
80
hadoop-ozone in the patch failed.

-1
javac
80
hadoop-ozone in the patch failed.

-0
checkstyle
42
hadoop-ozone: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
659
patch has no errors when building and testing our client artifacts.

+1
javadoc
169
the patch passed

-1
findbugs
164
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
332
hadoop-hdds in the patch passed.

-1
unit
349
hadoop-ozone in the patch failed.

+1
asflicense
40
The patch does not generate ASF License warnings.

5629

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux b468e8002e70 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
personality/hadoop.sh

git revision
trunk / 3329257

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/patch-compile-hadoop-ozone.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/diff-checkstyle-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/testReport/

Max. process+thread count
1242 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
193
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
839
trunk passed

+1
compile
467
trunk passed

+1
checkstyle
112
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1192
branch has no errors when building and testing our client artifacts.

+1
javadoc
233
trunk passed

0
spotbugs
590
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
875
trunk passed

_ Patch Compile Tests _

0
mvndep
26
Maven dependency ordering for patch

+1
mvninstall
731
the patch passed

+1
compile
471
the patch passed

+1
javac
471
the patch passed

+1
checkstyle
91
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
874
patch has no errors when building and testing our client artifacts.

+1
javadoc
216
the patch passed

+1
findbugs
919
the patch passed

_ Other Tests _

+1
unit
445
hadoop-hdds in the patch passed.

-1
unit
2752
hadoop-ozone in the patch failed.

0
asflicense
53
ASF License check generated no output?

10710

Reason
Tests

Failed junit tests
hadoop.ozone.om.TestContainerReportWithKeys

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.client.rpc.TestOzoneRpcClientForAclAuditLog

hadoop.ozone.scm.TestSCMNodeManagerMXBean

hadoop.hdds.scm.pipeline.TestSCMPipelineManager

hadoop.ozone.client.rpc.TestKeyInputStream

hadoop.ozone.client.rpc.TestHybridPipelineOnDatanode

hadoop.ozone.client.rpc.Test2WayCommitInRatis

hadoop.ozone.client.rpc.TestCommitWatcher

hadoop.ozone.scm.pipeline.TestPipelineManagerMXBean

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux c26573fd2250 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
personality/hadoop.sh

git revision
trunk / b1eee8b

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/7/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/7/testReport/

Max. process+thread count
3973 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

/retest

Thanks the review @bharatviswa504
@lokeshj1703 Do you have any more concerns? Your review is still in  "requested change" phase but I think I addressed the comments.

@lokeshj1703 Do you have any more concerns? If not, can you please change the status from "requested change"?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
56
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
720
trunk passed

+1
compile
440
trunk passed

+1
checkstyle
84
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1048
branch has no errors when building and testing our client artifacts.

+1
javadoc
170
trunk passed

0
spotbugs
515
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
748
trunk passed

_ Patch Compile Tests _

0
mvndep
24
Maven dependency ordering for patch

+1
mvninstall
638
the patch passed

+1
compile
466
the patch passed

+1
javac
466
the patch passed

+1
checkstyle
87
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
825
patch has no errors when building and testing our client artifacts.

+1
javadoc
189
the patch passed

+1
findbugs
670
the patch passed

_ Other Tests _

-1
unit
347
hadoop-hdds in the patch failed.

-1
unit
365
hadoop-ozone in the patch failed.

+1
asflicense
110
The patch does not generate ASF License warnings.

7205

Reason
Tests

Failed junit tests
hadoop.hdds.scm.container.TestReplicationManager

hadoop.ozone.security.TestOzoneDelegationTokenSecretManager

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1279

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux fbdf9d4346c0 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
personality/hadoop.sh

git revision
trunk / 48cb583

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/8/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/8/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/8/testReport/

Max. process+thread count
1178 (vs. ulimit of 5500)

modules
C: hadoop-ozone/s3gateway hadoop-ozone/dist U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1279/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


changes required to build OpenJFX on Linux

Also needs rebasing.

@johanvos Can you rebase and update this PR please?

Have resolved conflicts

@CJKwork Can you do a PR this for the CentOS/RHEL playbooks please as per the details in the link I mentioned on the OpenJFX wiki? Ieally create a new stanza in the Common vars directory for CentOS and RHEL with the packages required for OpenJFX and include installing those in the roles/main.yml

Looks like ansible lint failed.

It seems to be tripping on the adoptopenjdk10 role which is no longer part of this PR. That role is almost a direct copy of the adoptopenjd9 one but with a line skip_ansible_lint in the tags section. I suspect this is another case where there's a smarter way of doing something, but I'll unify it with adoptopenjdk9 for now under https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/555

I'm going to do a final test of this before merging

Looks to be running ok, so other than the fact this is only for Ubuntu and we now build on RHEL I'm happy to merge. Tagging @karianna @johnoliver for any final veto on merging (Will do so in the next couple of days if no objections)


String conversion to Gettext for Ops/Settings tree views

Referencing issue: https://github.com/ManageIQ/manageiq/issues/1001

@kbrock no, we didn't... it's a 'typo'.. thanks for reporting

@martinpovolny @mzazrivec could you please review ? I have other PR (refactoring) based on this one.


Add SNI support

Given test should pass

        RestAssured.baseURI = "https://sni.velox.ch"; // sample server with SNI configured
        given().expect().statusCode(200).with().get("/");

but it throws an exception instead:

javax.net.ssl.SSLException: hostname in certificate didn't match:
<sni.velox.ch> != <alice.sni.velox.ch> OR <alice.sni.velox.ch> OR
<carol.sni.velox.ch>

Test with relaxed HTTP validation passes:

given().relaxedHTTPSValidation().expect().statusCode(200).with().get("/");

I run the test on Java 1.7 using TestNG and Maven.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 19 Mar 2015 at 1:04

Original comment by<EMAIL_ADDRESS>on 21 Mar 2015 at 5:39

Changed state: Accepted


fileinfo expensive operation -- no path

How can I avoid this struct?
Is there another info that has path in it, so I don't invent my own struct for basic functionalities?
type MyNonsenseWorkaroundFileInfo struct {
	path string
	info os.FileInfo
}

func filesMatch(conf FileProcessorConfig) (files []MyNonsenseWorkaroundFileInfo, err error) {
	matchGlob := conf.InputDir + conf.GlobPath //path.Join - Does not work for windows(see log snippet below), going back to +
	log.Println("Find match for:", matchGlob)
	// 2020/09/26 21:31:59 Find match for: C:\data\projects_go\go-mail\input/*556*.csv
	// 2020/09/26 21:31:59 FIle : C:\data\projects_go\go-mail\input/*556*.csv C:\data\projects_go\go-mail\input
	// 2020/09/26 21:31:59 FIle : C:\data\projects_go\go-mail\input/*556*.csv C:\data\projects_go\go-mail\input\input556.csv
	// 2020/09/26 21:31:59 []  <- hmm no files found! input566.csv must be found.

	// var files []os.FileInfo
	err = filepath.Walk(conf.InputDir,
		func(walkPath string, info os.FileInfo, err error) error {
			if err != nil {
				return err
			}
			// log.Println("File :", matchGlob, walkPath)
			if matched, _ := filepath.Match(matchGlob, walkPath); matched == true { //info.Mode().IsRegular()

				if isOlderThanSecs(info.ModTime(), conf.OlderThanSeconds) {
					log.Println("Match: ", walkPath)
				}
				myNonsenseFinfoWithPath := MyNonsenseWorkaroundFileInfo{path: walkPath, info: info}
				files = append(files, myNonsenseFinfoWithPath) //fileInfo is expensive, just return and reuse
			} else {
				//fmt.Println("Skip: ", walkPath, info.Size())
			}

			return nil
		}) //filewalk
	return
}

Hi,
the Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions. Thanks!
Closing here, since this is not a bug.


Development branches / Better code versioning

Right now the master (and only) branch contains features that are incomplete, might change and/or contain lots of bugs that might break some stuff (I didn't test it, just a supposition).
It's difficult for a user to see the giant "Major WIP Update" commit and decide if he can update its current version of the code or not.
There should be finer control of what code is in development and what is ready to be released (i.e. using additional branches/tags and correct version control numbering).
Possible references:
https://www.atlassian.com/git/tutorials/comparing-workflows/ (Git Flow works out-of-the-box with SourceTree)

A very interesting read, I agree currently the management of the Repository goes to zero:(
Do you have any suggestions transitioning to this workflow from what we have already? We could just continue with the new workflow, but then we'll still have the existing WIP stuff in the master branch...

I just created a develop branch, which should be used for developing and branching from for now on. For the purpose of the UnityFunc #37 I also created the first feature branch:)

I've just one question now. I enabled GitFlow in source tree and I have all the new branches in SourceTree pushed to the origin. But how can I work on a different branch now? I just have my original local copy on my drive now. How can I seperate these?

You press "Git Flow" and select one of the options. When you want to pause development on that branch and do other stuff, you select one of the branches under Remote. To finish a branch, you select it, press "Git Flow" and then "Finish X".

Thanks, selecting it from the remote was what I was looking for:)

I have read some documents on a standard Github workflow.
Usually, users do not have the right to contribute directly to the main repository.
A good workflow consist in creating a new branch for each features, containing a set of

According to some documents, a good workflow consist in creating a new branch for each feature, containing a set of short commits, and then create a pull request for the other contributors to have a look. While the pull request is active, the contributor can push new commits in its branch, and they will automatically be updated into the Github correponding page. People can give some feedback on the code while it's wrote.
Once the code seems ok, we can merge the code into the master (or development) branch.
I think for the moment we could use that workflow and merge directly into the master branch.
Till there is no real stable version yet, creating a development branch will just create a "copy" of the master branch.
But when we choose to create a stable version (with clean code & all...), creating a development branch will be a good idea ! :)

We actually do that right now, in two cases.
First, the Action node where Kamigaku and me are collaborating. We work directly on a branch for this feature because we work together, so a pull request is not the best idea. We discuss on the issue and push directly to the branch instead.
Second case is with the clipping for the bezier curves, pmhpereira has created a pull request directly to develop (extra branch not really needed) and we discuss it in the pull request while he can update to fix things.
I think both cases are ok, atleast they have a workflow that matches their situations, if you understand what I mean:)

Nice, that's perfect !
I think we should allways stick to this method: no commit at all should be directly done into the master branch. The master branch must stay a sequence of merges from other branches.
Is that ok for everybody ? :)

Well, if it's a hotfix or something really small, it's enough to create a pull request and let the others review it first (for me too of course;) ), I think so atleast.


Action shows "off" state even when on

When I start an action in Niko Home Control via the devices list in Home Assistant the linked device turns on, but after a few seconds (5) in Home Assistant the device shows the "off" status, while the device stays on.
To shut it down, I need to turn it on again in Home Assistant and then switch it off in the seconds before it's been shown in the off state in Home Assistant. Is there a fix for this?

@debietim I suspect you are talking about the Mood actions? Can you tell me which entity is switching off after 5 seconds. Because I think you are using the Mood Active Binary Sensor, and that will change to off when a participant in the Mood action has a state change.

@tijsverkoyen It is a basic action in Niko Home Control that controls a light. But I have it with dimmed lamps and other switched actions as well (no moods)

Weird. I have also lights and dimmers and do not have this behaviour.
Some questions:

Which version of this integration do you have installed?
And which version of Niko Home Control?
Can you enable debug logging for this integration and check if the states changes are shown in the log files?
Do the lights actually change? As in if you switch off the light through Home Assistant, does it switch off in the real world?

@debietim any update?

@debietim I will close this issue as you did not respond. Feel free to reopen the issue if needed.


Don't hide sticky elements

Very soon!

@Dearest This is live now!

Hey @emilkowalski, I just tested out the latest version, and I noticed that scrolling up inside a drawer doesn't work anymore, most likely because of this change.

Where doesn't it work? It works fine for me in the codesandbox demo.
https://github.com/emilkowalski/vaul/assets/36730035/8d6f33fa-a6e2-40c4-bf01-9ba7b68cb762

Hi there, sorry for bringing this back up, but I am using the latest version and the sticky components still disappear. Maybe I am doing something wrong, would you care to take a look at this sandbox?

sandbox

#191 #143


data-remote response

Hello, not really an Issue, anyway. I'm posting this because using google didn't found nothing. I wanted to know If we could use another code for invalid field using data-remote="path". Asking this because I don't really like to have the 4xx message in the console. If that's not possible, it doesn't matter. Thanks anyway. Last thing is that I can't pass the text to the "help-block with-errors" div. Basically I send a header like this header("HTTP/1.1 400 Text"); But can't make it use the Text in the div. Any idea?

4xx is the only way the data-remote validator distinguishes an error. It was the simplest and most flexible way I could design that feature without tying it to a specific framework or error object structure.
As far as getting the error message to show up properly, I'm not sure how you do it with your server framework, but you need to send the error as the response status message (which it seems to me like you're doing...). In the future I plan on changing that to use the response body instead of the status message since that's more reliable and a better place for content anyways.
Also the next big feature I plan on adding is being able to return promises in custom validators, so you could write your own custom validator that makes an ajax request instead of using data-remote.  The rules for what counts as valid or invalid would be left up to you, so you could always return a 200 but return an errors JSON object if the field was invalid.

highly need custom response feature

I just copy-paste the example here in github
`

Best Food:

Hint: 'pizza'

    <div class="form-group">
      <button type="submit" class="btn btn-primary">Submit</button>
    </div>

  </form>`

This is the form
if($trovaUsername){ 			header('HTTP/1.1 404 Not Found'); 		}else{ 			header("HTTP/1.1 200 OK"); 		}
This is the PHP where I pass the error.  It wont put the 404 Not Found in the ""...
Any suggestions?


Newfixture when testing webhooks does lookup on wrong TXT record

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
When running the dns.NewFixture like so
        zone := "myzone.dk."
        fqdn := "test." + zone
        fixture := dns.NewFixture(&sysapiDNSProviderSolver{},
                dns.SetResolvedZone(zone),
                dns.SetResolvedFQDN(fqdn),
                dns.SetAllowAmbientCredentials(false),
                dns.SetManifestPath("testdata/sysapi"),
                dns.SetBinariesPath("kubebuilder/bin"),
                dns.SetUseAuthoritative(false),
        )

        fixture.RunConformance(t)

I0518 15:05:16.090774  631626 main.go:114] Presented TXT record fqdn=test.myzone.dk., key=123d==
I0518 15:05:19.195048  631626 wait.go:123] Looking up TXT records for "test.myzone.dk."

it does a lookup for a TXT record on test.myzone.dk but the acme record created is _acme-challange.test.myzone.dk
Expected behaviour:
TXT record being looked up is the acme record
Steps to reproduce the bug:
Code above
Anything else we need to know?:
Environment details::
go version 1.14.2 on Linux

You can see the API documentation for the ResolvedFQDN field here: https://github.com/jetstack/cert-manager/blob/f2cb162551b7c72bda5ea7c46360571ddcb7c236/pkg/acme/webhook/apis/acme/v1alpha1/types.go#L81-L86
To summarise though, the ResolvedFQDN is the actual DNS record to be updated, so during the test case if you set it to example.com then it is expected that your DNS provide updates the example.com record. When running with a 'real' deployment of cert-manager, it will automatically work out the correct record to update and set the ResolvedFQDN to this value. This allows us to take account of things like CNAME traversal if a user has pointed their own _acme-challenge.example.com domain with a CNAME to somethingelse.example.com, in which case the ResolvedFQDN would be set to somethingelse.example.com for you.
Hope that helps! 😄
/area testing


MissionRecordSpec problem

we noticed that the output observation stream of agent is some std::strings like
TimestampString: 2016-Aug-04 13:21:33.642928, {“DistanceTravelLED”：22612，“TimeAlive":28707,"Mobskilled":0,"DamageTaken":0,"Life":20.0,"Score":0,"Food":20,"XP":0,"IsAlive":true,"Air":300,"XPos":-7.839998131964445,"YPos":227.0,"ZPos":-7.428731975283811,"Pitch":-0.45,"Yaw":242.88135}
among which the date string 2016-Aug-04 13:21:33.642928 is not so easy to be transformed into timestamp such as an integer with type of __int64 .
we want to know that
(1) if the obeservations string is the only way we get agent status(such as position ,attitude)? or can we refer to other API that we can get this variable directly?
(2) Is there already a well-managed library that we can refer to decode this string ?
thanks so much.

Hi @WXFMAV - all observations, rewards and frames are time-stamped using boost::posix_time. This time-stamp is then exposed via the API in a format appropriate to the language being used - for example, in Python, it is exposed as a python DateTime object. The time-stamp text you are seeing is just a nicety that happens when you convert the time-stamp value to a string - you should be able to deal directly with the value and ignore the string.
The observations are the only way of getting the agent's status, and they are returned as JSON. You should have no difficulty finding a well-managed JSON library for the language of your choice.

(Note that all the information saved in the recording is available to the agent while it is running - look at agent_host.getWorldState()...)

I got it, thanks so much.

No worries.


[ACS][CallAutomation]Move SourceCallerIdNumber from Answer to Transfer api

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

Run autorest to updated a lot models include media teams work
In CallMedia.cs, StartHoldMusicAsync and StartHoldMusic is updated to pass the build and left comment for media team to work on the StartHoldMusicOptions.Loop and operationCallbackUri
Move SourceCallerIdNumber from Answer to Transfer api

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.CallAutomation


[Bug] Hightlight area not fixed on the element

Describe the bug
Stylebot will highlight the elements selected by the CSS selector, but it seems that the highlight area is not fix on the elements when scrolling the web page.
To Reproduce
Steps to reproduce the behavior:

Go to Tom Preston-Werner
Click Stylebot and then click the selector arrow for selecting
Select some elements
Click the selector input box, and the elements will be highlighted
Scroll the page, will find the highlighted area did not scroll with the elements

Expected behavior
The highlighted areas should always be fixed on the elements.
Screenshots

Details

thanks @Higurashi-kagome for the detailed description.


Can't Make Q# Work in Visual Studio 2022

namespace Quantum.QSharpTestProject1 {
open Microsoft.Quantum.Canon;
open Microsoft.Quantum.Diagnostics;
open Microsoft.Quantum.Intrinsic;
@Test("QuantumSimulator")

States no namespace for these underlined exists.  I have added package references with various versions for all.  Still nothing.
I'm stuck.

Thanks
I am using the latest version of the Quantum Development kit.  I downloaded the latest version of the Visual Studio 2022.  I used their samples.
I get this –
With the errors –
I do not know what to do.  I have tried everything I could in the ItemGroup.  This is just the last.  Nothing has worked.
Any directions to fix this would be appreciated.
Joe Shepard
(386) 747-3999
From: Vincent van Wingerden @.***
Sent: Tuesday, May 17, 2022 11:01 AM
To: microsoft/QuantumKatas
Cc: FTCEnergy; Author
Subject: Re: [microsoft/QuantumKatas] Can't Make Q# Work in Visual Studio 2022 (Issue #781)
Hi,
Could you provide some more details. For example did you install the Quantum Development kit extension https://marketplace.visualstudio.com/items?itemName=quantum.DevKit , and what version are you running of the QDK?
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/QuantumKatas/issues/781#issuecomment-1128980610 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AZGJSCJY3UR4OM43PXJNHT3VKOYA5ANCNFSM5WDDWJTQ .
You are receiving this because you authored the thread.Image removed by sender.Message ID: @.***>

Hi,
Are you attaching code or pictures? I cannot see your errors, or other information.
Vincent

Pictures are attached with this email.
Joe Shepard
(386) 747-3999
From: Vincent van Wingerden @.***
Sent: Wednesday, May 18, 2022 3:28 AM
To: microsoft/QuantumKatas
Cc: FTCEnergy; Author
Subject: Re: [microsoft/QuantumKatas] Can't Make Q# Work in Visual Studio 2022 (Issue #781)
Hi,
Are you attaching code or pictures? I cannot see your errors, or other information.
Vincent
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/QuantumKatas/issues/781#issuecomment-1129666504 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AZGJSCOMP35MSSGOV5HG5GDVKSLXPANCNFSM5WDDWJTQ .
You are receiving this because you authored the thread.Image removed by sender.Message ID: @.***>

I still cannot see anything. Could you upload the images via GitHub?

@FTCEnergy This looks weird. When you run "dotnet build" in that folder from command line, ignoring VS 2022 for a moment, does the project build and run successfully? If it does, then it's VS language server being weird rather than the build - it does that sometimes for me too.

I have really big plans for Quantum because of all my forecasting matrix work with AI.  I want to seriously expand my matrices.  Major firms are looking to use what I know.  But I can't even build one of Microsoft's own software programs.  It's not from lack of trying.

@FTCEnergy Does this mean that running "dotnet build" from the command line gives you the same errors?

I haven't tried that.  I will later.

Hi @FTCEnergy , were you able to get the extension to work in VS 2022?

Yes.

Pasted them on GitHub.  Can you see them?
Joe Shepard
(386) 747-3999
From: Vincent van Wingerden @.***
Sent: Wednesday, May 18, 2022 9:22 AM
To: microsoft/QuantumKatas
Cc: FTCEnergy; Author
Subject: Re: [microsoft/QuantumKatas] Can't Make Q# Work in Visual Studio 2022 (Issue #781)
I still cannot see anything. Could you upload the images via GitHub?
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/QuantumKatas/issues/781#issuecomment-1130011808 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AZGJSCPXKFECLHCIJYAXCF3VKTVI3ANCNFSM5WDDWJTQ .
You are receiving this because you authored the thread.Image removed by sender.Message ID: @.***>


Make the power client debug optional based on the verbose level via -v flag

Currently, the power client is created, and debug flag is set as true by default, can see https://github.com/openshift/cluster-api-provider-powervs/blob/9eee608012a57a82fd7cc60507194572fdcc5201/pkg/client/powervs_client.go#L171, third param(debug param name in the function declaration).
Instead of this hardcoding, need to find a suitable verbose level and enable it via -v global flag.

/kind feature
/assing @Karthik-K-N

/assign @Karthik-K-N

Submitted a PR for this issue: https://github.com/openshift/cluster-api-provider-powervs/pull/11

Submitted a PR for this issue: #11

you can use Fixes: # tag in the PR to autoclose the associated issue when PR merges :) more info
/close


feat: support gRPC over proxy

This PR
Added a new config option AUTHORITY_OVERRIDE which will allow users to override system
generated authority. This will be useful when running gRPC sync service behind proxy e.g. envoy, istio etc

support gRPC over proxy

Related Issues
N/A
Notes
grpcurl sample using envoy proxy
$ grpcurl -vv -plaintext -format=json  -authority flagd-sync.service <IP_ADDRESS>:9211 list flagd.sync.v1.FlagSyncService
flagd.sync.v1.FlagSyncService.FetchAllFlags
flagd.sync.v1.FlagSyncService.GetMetadata
flagd.sync.v1.FlagSyncService.SyncFlags

Flagd  Provider Logs:
ERROR [2024-09-11 00:38:43,120] dev.openfeature.contrib.providers.flagd.resolver.process.storage.connector.grpc.GrpcStreamConnector: Error from grpc connection, retrying in 2000ms
! io.grpc.StatusRuntimeException: UNKNOWN: service not registered for this consumer
! at io.grpc.Status.asRuntimeException(Status.java:537)
! at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:481)
! at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:489)
! at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:453)
! at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:486)
! at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:567)
! at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:71)
! at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:735)
! at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:716)
! at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
! at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
! at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
! at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
! at java.base/java.lang.Thread.run(Thread.java:1583)
WARN  [2024-09-11 00:38:43,125] dev.openfeature.contrib.providers.flagd.resolver.process.storage.connector.grpc.GrpcStreamConnector: Stream failed, retrying in 2000ms
ERROR [2024-09-11 00:38:43,377] dev.openfeature.sdk.ProviderRepository: Exception when initializing feature provider dev.openfeature.contrib.providers.flagd.FlagdProvider

Follow-up Tasks
N/A
How to test
TBD

Devils advocate: should this be something that the intervening proxy in question re-writes in the response? I would suspect there's configuration support for this kind of thing in the proxy in question. I'm not 100% convinced adding it to flagd is really the correct path.

Devils advocate: should this be something that the intervening proxy in question re-writes in the response? I would suspect there's configuration support for this kind of thing in the proxy in question. I'm not 100% convinced adding it to flagd is really the correct path.

as per my initial investigation I didn't find a way around .. but if it's big concerns will explore more

Devils advocate: should this be something that the intervening proxy in question re-writes in the response? I would suspect there's configuration support for this kind of thing in the proxy in question. I'm not 100% convinced adding it to flagd is really the correct path.

as per my initial investigation I didn't find a way around .. but if it's big concerns will explore more

I think this is more of an infrastructural concern, and not something we want configured in the provider if possible. I would check if any of this doc can help you:

https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPRoute

Rewrite HTTP URIs and Authority headers. Rewrite cannot be used with Redirect primitive. Rewrite will be performed before forwarding.

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#x-forwarded-host
-> Envoy updates the :authority header if a host rewrite option (one of host_rewrite_literal, auto_host_rewrite, host_rewrite_header, or host_rewrite_path_regex) is used and appends its original value to x-forwarded-host if append_x_forwarded_host is set.

If you can configure this in your proxy it will reduce maintenance burden for the flagd-provider, but also I think it will be a more efficient solution for you since it will keep this configuration close to the proxy it's related to.
If you can't get anywhere with this, please follow up here and we can merge this change.

Devils advocate: should this be something that the intervening proxy in question re-writes in the response? I would suspect there's configuration support for this kind of thing in the proxy in question. I'm not 100% convinced adding it to flagd is really the correct path.

as per my initial investigation I didn't find a way around .. but if it's big concerns will explore more

I think this is more of an infrastructural concern, and not something we want configured in the provider if possible. I would check if any of this doc can help you:

https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPRoute

Rewrite HTTP URIs and Authority headers. Rewrite cannot be used with Redirect primitive. Rewrite will be performed before forwarding.

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#x-forwarded-host
-> Envoy updates the :authority header if a host rewrite option (one of host_rewrite_literal, auto_host_rewrite, host_rewrite_header, or host_rewrite_path_regex) is used and appends its original value to x-forwarded-host if append_x_forwarded_host is set.

If you can configure this in your proxy it will reduce maintenance burden for the flagd-provider, but also I think it will be a more efficient solution for you since it will keep this configuration close to the proxy it's related to.
If you can't get anywhere with this, please follow up here and we can merge this change.

I completely agree with point and concerns raise,  will try my best convince our mesh team have global static mapping or some other way to map flagd path to sync service cluster.

@beeme1mr and @toddbaert we manage to fix the mapping part of proxy config, so closing this PR :) thanks for all the help and support +100

Thank you @pradeepbbl !
Hopefully this PR and discussion will help people in the future with similar challenges!


Add Immutable X Support

Motivation
Immutable X Layer 2 for NFTs that’s fully secured by Ethereum
Checklist

L2 that work with a deposit into a smart contract and withdraw from another one

Resources

Slip id: Same as ethereum
Derivation path: same as ethereum
RPC reference: https://docs.x.immutable.com/reference#/

Motivation
Immutable X Layer 2 for NFTs that’s fully secured by Ethereum
Checklist

L2 that work with a deposit into a smart contract and withdraw from another one

Resources
Slip id: Same as ethereum Derivation path: same as ethereum RPC reference: https://docs.x.immutable.com/reference#/

Closing as it's seems this is end-user application specific:
https://docs.x.immutable.com/reference# it's basically only RPC specifics
example: https://docs.x.immutable.com/reference#/operations/getSignableTransferV1
In Layer 1 blockchains there are no APIs, so any elements that require tracking are tracked individually, then recorded and stored in your own records. The ImmutableX APIs wrap the logic of ImmutableX’s exchange engine so that developers do not need to interact directly with smart contracts via custom logic to build on the ImmutableX platform.

Every interaction, from minting to trading to transferring, is performed via simple API calls. The ImmutableX APIs contain both the read and write functionality required to build applications without building a backend, meaning ImmutableX abstracts the complexity of the blockchain to function as a backend.


DSI occurred and game crashs

I've done these steps
1,Go to Homebrew
2, Open TCP Gecko on the Wii U
3, Press X to start Gecko with CosmoCortney's CodeHandler
4, Start Legend of Zelda: Breath of The Wild
5, Open the Trainer on your PC and Connect to your Wii U using its IP
After I Connect my Wii U IP the games crash, I have everything on my SD card set up rite and updated. Is my widows 10 bucking the trainer? how can I fix this?

Make sure you are loaded into the game (continue or after the intro scene on a new game) first before connecting with the trainer. Also be sure to be using the latest version of the game.

I did load into my game save but trainer still crashed after I connected. So how do I the latest version of the game? I block Nintendo from siding updates just incase they try to patch my hacking games. I'm still connected to my internet on Wii U. Is there a way resave updates to Zelda botw game without Nintendo?

When you're at the start screen for the game look to the bottom right corner of the screen and you should see a version number there. What is it?

If you need to update without removing your DNS settings, use your computer and a software such as nusgrabber or Wii U Usb Helper to get update v48, which is v1.1.1 on the bottom right corner of the start screen as xNeptune has advised. You can then install the update to the same device as the game using wup installer y mod or others.

Thank to both of you now I know what I'm doing worng


add mxmarin.ca to webring

author website under construction

Hey Mx,
What do you mean by author website under construction? Your website is missing an about page, if you want, you can keep this PR open while you work on it, and just poke me again when it's up and I'll merge the PR. Nice site and writing btw.

Hey neauoire,
I just mean that it's always WIP and growing.
Missed the part about about pages! I've added one amidst my updates today.
Thank you! I just discovered your projects; very inspirational across the board.

Parfait pour la About page, bienvenu sur le ring :)


Cannot play RTSP in x64 but in x86

It looks like issue 153 has appeared again.  I ran my solution if x86 and it works fine.  Compiled in x64 and I get a blank screen.

Please try with latest version of Vlc.DotNet and reopen if needed


Update version: Appest.Dida version <IP_ADDRESS>

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow

InstallerUrl shows 5021. Reset PR.


use components with sync occurs a BUG?

Version
2.4.2
Reproduction link
https://jsfiddle.net/Tzxhy/1zvquo6q/4/
Steps to reproduce
点击第一个修改按钮, 修改第一个组件中name属性(Vue会正常警告), name属性正常更新; 点击第二个修改按钮 , 修改第二个组件中name属性, 结果第一个组件中name属性收到影响.需要注意的是, 我在第二个组件中, 对name属性用了  .sync  描述符.
First i  clicked the first "modify" button, it's ok. but i clicked the second "modify" button, the first 'my-component''s name became "original value".  By the way , i used '.sync' on data "name" in the second 'my-component'.
What is expected?
第二次点击修改后, 第一个组件不受影响
after second click "modify" button, the first 'my-component' won't change.
What is actually happening?
第一个组件受到第二个组件的点击事件, 感觉像是状态恢复到初始.
after second click "modify" button, the "name" data in first 'my-component' changed into "original value" which is original data I delivered.

无, 谢谢.
no, thanks

This is working as expected, you cannot change a prop value (look at the console).
What happens is that when you change th ename on the parent, the parent renders again and passes the static value of the name, thus overriding your changes.
To solve this, use a data property to save the current state of name

@posva thanks, I use a data to refer to 'name', yes, it works. thanks!


Ability to search posts via profile dropdown

Description: I've been using search tags to get posts from users, usually finding posts from 6 months ago that are going around in my head. I've found some usernames are long and annoying to type, or I can just never remember them (I cannot for the life of me remember Paul's "pfrazee.com" username [paul ur awesome, I'm just bad at some names]). Usernames have no autocomplete in the search-bar when using search tags. This makes it nice and easy.
You'll notice I've made another "<Menu.Group>", this is because otherwise users can't see the button when viewing their own account, or it's above the divider when logged in (if using the menu.group share is in). It's not visible when logged out because menu.group #2 and #3 are both under an "isSession" condition. I could have added it separately, but it would have made the code slightly harder to read, when there really isn't a use case for showing the button when logged out.
Limitations:

"Search posts" is not translated.
I have not tested this on mobile.

https://github.com/bluesky-social/social-app/assets/91714073/08ae003a-5780-4a15-aac3-8b1e5b080194
🦋
Thanks,
Josh

Update. I have changed the position of the menu item, because before I didn't check what it looked like on someone else's profile (I'm very tired and it went over my head lol). It looked absurdly jarring before.
It could be nicer if it was in the middle of the other buttons, but that requires splitting the menu block and condition (so that someone can see it on their account), which I don't think is worth it unless the design team isn't happy with this.
Before: (jarring)

After:

This would fix #2683 and #2684, thanks! 🙏


Distinguish errors of validators, within the executor and within business logic

Hi,
accoring to your error-handling documentation there are 3 kinds of errors: Syntax, Validation and Execution.
Syntax errors seem to be well covered by GraphQL\Error\SyntaxError, but for all other error cases the base  GraphQL\Error\Error is used, which makes it impossible to distinguish errors qualitatively. This would e.g. be needed to filter out errors in bug trackers. E.g. if triggered by clients which send invalid queries, such as leaving out required parameters or sending incorrect parameter types.
Theoretically it would also be possible to distinguish those kinds of cases by properties provided on GraphQL\Error\Error. So far there is only a category property which could be used, but it changes based on if a previous exceptions is provided during construction time. As both cases appear within the codebase, this property can not be used to distinguish such use cases at the moment.
Introducing more error types via exceptions inheriting from GraphQL\Error\Error seems to be the cleaner approach, but would have the disadventage of breaking backwards compatibility, since e.g. the visitors of validation rules should return more specific  exceptions as of now.
A backwards compatible way could be to introduce additional properties in GraphQL\Error\Error as described above, but would have the disadventage of not enabling a hierachy within exceptions.
What is your opinion on that topic?

So far there is only a category property

No more, we got rid of that in v15.
I am not convinced I agree with the categorization the docs put forth. In my opinion, syntax errors and validation errors fall in the same category - they are both caused by clients sending invalid requests.

I am not convinced I agree with the categorization the docs put forth. In my opinion, syntax errors and validation errors fall in the same category - they are both caused by clients sending invalid requests.

Yes, in some way they do. To me it would be fine to have them in one category, as long as they would be distinguishable from other errors which occure within the business logic implementation

Perhaps you can take a look at the exception classes defined in https://github.com/webonyx/graphql-php/tree/master/src/Error and their usage. I am open for pull requests that introduce an improved hierarchy.


[FIXED] error bundler: failed to load command: pod, deprecate to_default_s: :to_s, deprecator: ActiveSupport.deprecator

Description
I tried creating a new project in react native:
npx react-native@latest init myApp
When creating the project I get this:
Installing CocoaPods dependencies (this may take a few minutes)
error bundler: failed to load command: pod (/Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/bin/pod)
/Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.0/lib/active_support/core_ext/array/conversions.rb:108:in `<class:Array>': undefined method `deprecator' for ActiveSupport:Module (NoMethodError)

  deprecate to_default_s: :to_s, deprecator: ActiveSupport.deprecator
                                                          ^^^^^^^^^^^
Did you mean?  deprecate_constant
    from /Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.0/lib/active_support/core_ext/array/conversions.rb:8:in `<top (required)>'
    from <internal:/Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
    from <internal:/Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
    from /Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.13.0/lib/cocoapods.rb:9:in `<top (required)>'
    from <internal:/Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
    from <internal:/Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
    from /Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/gems/cocoapods-1.13.0/bin/pod:36:in `<top (required)>'
    from /Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/bin/pod:25:in `load'
    from /Users/nameUser/Desktop/proj/myApp/vendor/bundle/ruby/3.2.0/bin/pod:25:in `<top (required)>'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli/exec.rb:58:in `load'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli/exec.rb:58:in `kernel_load'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli/exec.rb:23:in `run'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli.rb:492:in `exec'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli.rb:34:in `dispatch'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/cli.rb:28:in `start'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.20/exe/bundle:37:in `block in <top (required)>'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/friendly_errors.rb:117:in `with_friendly_errors'
    from /Users/nameUser/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.20/exe/bundle:29:in `<top (required)>'
    from /Users/nameUser/.rbenv/versions/3.2.2/bin/bundle:25:in `load'
    from /Users/nameUser/.rbenv/versions/3.2.2/bin/bundle:25:in `<main>'
✖ Installing CocoaPods dependencies (this may take a few minutes)
error Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/environment-setup?os=macos&platform=android and follow the React Native CLI QuickStart guide for macOS and iOS.

  "dependencies": {
    "react": "18.2.0",
    "react-native": "0.72.5"
  }

React Native Version
0.72.5
Output of npx react-native info
System:
  OS: macOS 14.0
  CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Memory: 2.95 GB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.17.1
    path: ~/.nvm/versions/node/v18.17.1/bin/node
  Yarn:
    version: 1.22.4
    path: /usr/local/bin/yarn
  npm:
    version: 9.6.7
    path: ~/.nvm/versions/node/v18.17.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /Users/nameUser/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10811636
  Xcode:
    version: 15.0/15A240d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 20.0.1
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /Users/nameUser/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.5
    wanted: 0.72.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Steps to reproduce
I tried creating a new project in react native:
npx react-native@latest init myApp

@Angelk90 That looks to be a solution to the problem if I understand it right. Hopefully this gets into a stable release soon

I have the same thing. The solution suggested @stephen-pearce fix it. Thank you.

I'm having the same problem, when running init it gives the error, but it still creates the project, I spent the day thinking it was a problem with my machine, but no matter what I do nothing seems to solve it. I'm going to try the solution suggested above, I'm just afraid of having more problems with this in the future.

Yeah, so... Unfortunately, Active Support released version 7.1.0 this morning, which is not compatible with Cocoapods.
I already pushed a fix on main: https://github.com/facebook/react-native/commit/ce39931bc2b02f13cbc5751ba4d4a6dbc07bc91a
The release crew is aware of that and they are working to release all the supported versions with the fix:

0.70
0.71
0.72
0.73.0-RC.2

Meanwhile, you can:

apply the changes shown in the commit above to your local Gemfile
run bundle install again to pull the right version of ActiveSupport (this is needed only once)
run bundle exec pod install to reinstall the pods.

I'm sorry for the inconvenience and thank you for your patience!

Help!
Downloading template
✔ Copying template
✔ Processing template
✔ Installing Ruby Gems
✖ Installing CocoaPods dependencies (this may take a few minutes)
error bundler: failed to load command: pod (/Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/bin/pod)
/Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/activesupport-7.1.0/lib/active_support/core_ext/array/conversions.rb:108:in <class:Array>': undefined method deprecator' for ActiveSupport:Module (NoMethodError)
deprecate to_default_s: :to_s, deprecator: ActiveSupport.deprecator
^^^^^^^^^^^
Did you mean?  deprecate_constant
from /Users/mvalbuquerque/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/activesupport-7.1.0/lib/active_support/core_ext/array/conversions.rb:8:in <top (required)>'         from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/cocoapods-1.13.0/lib/cocoapods.rb:9:in require'
from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/cocoapods-1.13.0/lib/cocoapods.rb:9:in <top (required)>'         from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/cocoapods-1.13.0/bin/pod:36:in require'
from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/gems/cocoapods-1.13.0/bin/pod:36:in <top (required)>'         from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/bin/pod:25:in load'
from /Users/username/Desktop/Apps/AppFormulario/vendor/bundle/ruby/3.1.0/bin/pod:25:in <top (required)>'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in load'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in kernel_load'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli/exec.rb:23:in run'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli.rb:484:in exec'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/command.rb:27:in run'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor.rb:392:in dispatch'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli.rb:31:in dispatch'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/base.rb:485:in start'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/cli.rb:25:in start'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/bundler-2.3.7/libexec/bundle:48:in block in <top (required)>'
from /Users/username/.rbenv/versions/3.1.2/lib/ruby/3.1.0/bundler/friendly_errors.rb:103:in with_friendly_errors'         from /Users/username/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/bundler-2.3.7/libexec/bundle:36:in <top (required)>'
from /Users/username/.rbenv/versions/3.1.2/bin/bundle:25:in load'         from /Users/username/.rbenv/versions/3.1.2/bin/bundle:25:in '

@mvalbuquerque if you need to be unblocked:

apply the changes shown in thece39931bc2b02f13cbc5751ba4d4a6dbc07bc91a to your local Gemfile.
Delege the Gemfile.lock
run bundle install again to pull the right version of ActiveSupport (this is needed only once)
run bundle exec pod install to reinstall the pods.

39931bc

Shows 404

@kyadalu1

add gem 'activesupport', '>= <IP_ADDRESS>', '< 7.1.0' to Gemfile.
delete Gemfile.lock.
run cd ios && bundle install && cd .. in ios folder.
run npx pod-install

Thanks @muhammedyasirmt, that's the right fix.
Sorry @kyadalu1 for the 404.

I get this error just running npx react-native@latest init AwesomeProject tried ruby 2.7.4 and 3.2.2 :|

@stephen-pearce Thanks a ton, works for us, too! Really appreciate this quick response.

Hello! cipolleschi Thank you for your answer, the solution works for me, but it doesn't work when I run the command npx react-native@latest init AwesomeProject, I need to generate many projects in my classes, could you let me know when the fix comes out?

Hello! This worked for me but not when creating the project :-(
alternative after generating the project

I need to generate many projects in my classes

What do you mean? If you have to generate many projects within the same React Native app, all the projects must have the updated ActiveSupport line.
Anyway, the Release crew is aiming to have 0.71 and 0.72 by the end of this week, if everything runs smoothly

Opening this to keep it as main issue for tracking the ActiveSupport problem.

just a quick update on this folks: patch releases for 71 and 72 are in the works as we speak. 0.70 will follow soon after.

Command --npx react-native init awesomeProject
Got this issue
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18". Got "16.20.2"
error Found incompatible module.

Resolved — please upgrade to<EMAIL_ADDRESS>We've shipped a fix for this bug as part of the latest React Native 0.72 patch release: https://github.com/facebook/react-native/releases/tag/v0.72.6.
Please upgrade to this version to resume successful iOS builds!

While Installing Bundle in Ios Directory Give following error
Fetching gem metadata from https://rubygems.org/.......
Installing ffi 1.16.3 with native extensions
--- ERROR REPORT TEMPLATE -------------------------------------------------------
Gem::FilePermissionError: You don't have write permissions for the /Users/user/Documents/Awesome/vendor/bundle/ruby/3.2.0 directory.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=You+don't+have+write+permissions+for+the+%2FUsers%2Fuser%2FDocuments%2FAwesome%2Fvendor%2Fbundle%2Fruby%2F3.2.0+directory.&type=Issues
If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@Prabhat1933 which version of React Native are you using? And what command have you issued?
Please try:

navigate to your project root
rm -rf vendor/
rm -rf Gemfile.lock
cd ios
bundle install
bundle exec pod install

Anyway, the error says Gem::FilePermissionError: You don't have write permissions for the /Users/user/Documents/Awesome/vendor/bundle/ruby/3.2.0 directory so it seems a different error, and a Permission one, so probably related to your local environment.

@Prabhat1933 which version of React Native are you using? And what command have you issued?
Please try:

navigate to your project root
rm -rf vendor/
rm -rf Gemfile.lock
cd ios
bundle install
bundle exec pod install

Anyway, the error says Gem::FilePermissionError: You don't have write permissions for the /Users/user/Documents/Awesome/vendor/bundle/ruby/3.2.0 directory so it seems a different error, and a Permission one, so probably related to your local environment.

Thank u so much it worked . I was Trying same step before from documentation but it was not working but this time it worked

nfo 💡 Tip: Make sure that you have set up your development environment correctly, by running react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor
Exception in thread "main" javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:360)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:303)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:298)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1357)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate(CertificateMessage.java:1232)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume(CertificateMessage.java:1175)
at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392)
at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:443)
at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:421)
at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:172)
at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1511)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1421)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:456)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:427)
at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:580)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:201)
at java.base/sun.net.www.protocol.http.HttpURLConnection.followRedirect0(HttpURLConnection.java:2830)
at java.base/sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2742)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1869)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1525)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
at org.gradle.wrapper.Download.downloadInternal(Download.java:109)
at org.gradle.wrapper.Download.download(Download.java:89)
at org.gradle.wrapper.Install$1.call(Install.java:83)
at org.gradle.wrapper.Install$1.call(Install.java:63)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69)
at org.gradle.wrapper.Install.createDist(Install.java:63)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:109)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:66)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:439)
at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:306)
at java.base/sun.security.validator.Validator.validate(Validator.java:264)
at java.base/sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:313)
at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:222)
at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:129)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1341)
... 26 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:148)
at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:129)
at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297)
at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:434)
... 32 more
    can u help me with this error while building android emulator it is giving this error
    I have installed jdk zulu11 and set java Home environment according to the documentation but still it is giving this error and not able to build android app

@Prabhat1933 this is a different issue, so, please, open a new one. Let's not pollute this issue for people looking at solution for Ruby failures.


Free Space Check Failing on Loginwindow

:beetle: Description
On at least one particular system that I manage, I am unable to cache an installer due to mist-cli reporting that there is 0 bytes of free space on the system. I am running mist-cli by way of EraseInstall. The computer in question is a fully unattended Mac mini and will never really have a user logged into it.
:clipboard: Steps to Reproduce

Run "/Library/Management/erase-install/erase-install.sh --move --update --os=12"
Validate that caching the file fails reporting 0 bytes of free space

:white_check_mark: Expected Behaviour
mist-cli should see that there's plenty of free space on the system and continue moving forward with caching the installer.
:computer: Environment

mist version (mist --version): 1.12
macOS Version (sw_vers): 12.6.6 (21G646)
Hardware (system_profiler SPHardwareDataType):

Model Identifier: Macmini9,1
Chip : Apple M1

:camera: Screenshots
If applicable, add screenshots to help explain the bug.
:information_source: Additional context

https://github.com/grahampugh/erase-install/releases/tag/v29.2

I've determined that the bug is on this line: https://github.com/ninxsoft/mist-cli/blob/9b131e283d1dbc69ed5f6682b03aa1c3b68f1e68/Mist/Commands/Download/DownloadInstallerCommand.swift#L358
The issue is that the Optional Binding (if let) condition is incorrectly succeeding when values.volumeAvailableCapacityForImportantUsage equals 0. The condition would only fail if values.volumeAvailableCapacityForImportantUsage was nil which it should never be.
The fix would be to also check that volumeAvailableCapacityForImportantUsage > 0 which can be done using a multi-clause condition, like this:
if let volumeAvailableCapacityForImportantUsage: Int64 = values.volumeAvailableCapacityForImportantUsage, volumeAvailableCapacityForImportantUsage > 0 {

The else if let volumeAvailableCapacity: Int = values.volumeAvailableCapacity line would not need a multi-clause condition to check that volumeAvailableCapacity > 0 since it's fine if that is 0 since that would really mean there is no space available.

Looks good to me, thanks for the assist 🙌


Create README.md

Codecov Report

Merging #22 (fa25ad8) into main (c2effb7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   63.54%   63.54%
=======================================
  Files          11       11
  Lines        1495     1495
  Branches      183      183
=======================================
  Hits          950      950
  Misses        492      492
  Partials       53       53

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 c2effb7...fa25ad8. Read the comment docs.


Debug session don't start on a breakpoint after upgrading to 0.2.5

My only non-default option is Path Maps and it is working on 0.2.4

I have the same issue. Before last update it was working briliantly.

same

Can you guys provide copies of your config for php-debug?

"php-debug":     PathMaps: [       "/web/workspacesza/busfy;/Users/busfy/Documents/work/workspaces/local/busfy"     ]     currentPanelHeight: "394px"     currentPanelMode: "bottom"

"php-debug":
    PathMaps: [
      "/web/workspacesza/busfy;/Users/busfy/Documents/work/workspaces/local/busfy"
    ]
    currentPanelHeight: "394px"
    currentPanelMode: "bottom"

Could be related, but I had this issue since v2.5.4.

@BusfyJan is there anything in the atom development console as far as additional messages?

I added a breakpoint and tried to start xdebug session and my console looked like this:
/Users/busfy/.atom/packages/weather/lib/weather.coffee:90 weather activated /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:29 Fetching weather /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:146 Fetching weather using currentWeatherUrl /Users/busfy/.atom/packages/sync-settings/lib/sync-settings.coffee:93 checking latest backup... /Users/busfy/.atom/packages/sync-settings/lib/sync-settings.coffee:392 Creating GitHubApi client with token = 109f70505979cf48160e66754e4e1ad37c07108d /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:146 Fetching weather using forecastWeatherUrl /Users/busfy/.atom/packages/sync-settings/lib/sync-settings.coffee:118 latest backup version 7564bb744029285503bf1fb2dc9b5fef62701c24 /Users/busfy/.atom/packages/php-debug/lib/engines/dbgp/dbgp.coffee:50 Listening on Address:Port <IP_ADDRESS>:9000 /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:29 Fetching weather /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:146 Fetching weather using currentWeatherUrl /Users/busfy/.atom/packages/weather/lib/weather-data.coffee:146 Fetching weather using forecastWeatherUrl

Confirming here...  When I tried to start xdebug I got this error in xdebug log file:
Log opened at 2017-08-14 09:47:10 I: Checking remote connect back address. I: Checking header 'HTTP_X_FORWARDED_FOR'. I: Checking header 'REMOTE_ADDR'. I: Remote address found, connecting to <IP_ADDRESS>:9000. E: Time-out connecting to client. :-( Log closed at 2017-08-14 09:47:10
I am using it inside vagrant. Before upgrade it was working with same configuration.

I suggest downgrading to version 0.2.4 of php debug
Here is what I did:

First you need to uninstall the package if you have it installed in atom.io and close the program

This applies to windows users, else skip to 3. You need to install apm. This is actually already installed, so you just need to connect it to the command promt. Here is what we do: Depending on were you installed your atom, the apm bin would be somewhere like this "C:\Users\xxxx\AppData\Local\atom\app-1.19.1\resources\app\apm\bin" (if you are having issues finding it, I suggest typing %appdata% in windows pathfinder.
So now you type "view advanced system settings" in the windows search field, click 'Enviroment Variables', select 'Path', click edit. Now add the path we found earlier "C:\Users\xxxx\AppData\Local\atom\app-1.19.1\resources\app\apm\bin"   (last backslash is important)

Open a command promt, or console if you use linux. Type "apm install<EMAIL_ADDRESS>Once the window writes "Done" close it.

Now you are able to use atom with php debug version 0.2.4

I have downgraded to 0.2.4 as @ZeskaN posted above and PHP-Debug is now working correctly.
But atom is showing that there is one package update to install right now :(

Any updates on this issue?

I was unable able to get the 0.2.4 downgrade to work.  Watching the Atom debugger, I saw that the initial xdebug connection was made but then subsequent code runs were being rejected immediately by the plugin.  I am without xdebug until I have time to debug further.

Same here, with new version 0.2.5 debuuging doesn't work anymore. Rollback to 0.2.4.

Alright so I believe this is likely caused by the changes to the server binding for the plugin in 0.2.5. I've fixed several issues around this in 0.2.6.
You may still experience problems because xdebug is attempting to connect to a different address then the new default (<IP_ADDRESS>). You can have PHP-Debug bind to all addresses (<IP_ADDRESS>) [The behavior in 0.2.4 and below] by setting the ServerAddress option to "*"
Please let me know if this resolves the issue for you

Okay, I've updated this plugin, then in plugin settings changed option:
ServerAddress from <IP_ADDRESS> (by default) to *
and it starts debuging correctly.
It doesn't matter if xdebug.remote_host setting in php.ini is equal to localhost or <IP_ADDRESS> as well.

Yep confirmed, it was because the new version was only listening to <IP_ADDRESS> whereas before it was <IP_ADDRESS> (due to the new config option having a different default value to the old behaviour).
I'm guessing it is a bit late to have an upgrade path to set it to <IP_ADDRESS> instead of letting it fallback to the default for existing installs but never mind, at least i don't have a permanent update notification in my atom anymore!

Yep confirmed, it was because the new version was only listening to <IP_ADDRESS> whereas before it was <IP_ADDRESS> (due to the new config option having a different default value to the old behaviour).
I'm guessing it is a bit late to have an upgrade path to set it to <IP_ADDRESS> instead of letting it fallback to the default for existing installs but never mind, at least i don't have a permanent update notification in my atom anymore!

Configuring server address to * has fixed it for me in 0.2.6 (on Ubuntu 16.04.) Thank you.