Yetus 234

This is work in progress, not yet ready for formal review.  I wanted to share something early so that the ZooKeeper team can see what a personality file looks like.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
111
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
1
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

138

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux f5b1cd2806ba 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / bdb0f18

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/1/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
51 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/1/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
114
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
1
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

140

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 18c42b9fa780 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 5475b06

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/2/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/2/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
140
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

164

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 44c1d5386612 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 82f3493

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/3/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/3/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
159
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

186

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux bef2d37179af 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / dd7ecd7

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/4/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/4/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
149
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
1
The patch has no whitespace issues.

_ Other Tests _

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

176

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 20b5b4e734cd 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / ffcf2b9

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/5/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
47 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/5/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
166
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

194

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux e19cb100f8f1 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / ff435e9

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/6/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/6/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
146
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
1
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

173

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux e3ae7b0018ab 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / e113117

maven
version: Apache Maven 3.3.9

shellcheck
v0.6.0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/7/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/7/console

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
153
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

181

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 7adf9b1faeea 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / ed583bb

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/8/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/8/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
157
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

183

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 9fe81248a8cd 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
precommit/src/main/shell/personality/yetus.sh

git revision
master / bcd6e83

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/9/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
47 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/9/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
145
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
1
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

193

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/10/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 54d7dd8746c6 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 0f54f6f

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/10/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/10/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
85
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

116

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux ff563f5cc4b5 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / e2f9288

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/11/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/11/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
87
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

133

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/12/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 767d5aae7b62 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 17b82a0

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/12/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/12/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
133
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

159

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/13/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 357e70b60931 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / f723d32

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/13/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/13/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
80
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

111

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/14/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux ff3a5f2f5ec2 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / d77718c

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/14/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/14/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
134
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

164

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/15/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 285b33eb9221 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 90fd5f9

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/15/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/15/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
85
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

115

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/16/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 0a27c5aaddec 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 5cf772d

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/16/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/16/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
91
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

122

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/17/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux fcba8a3a7cd2 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 37c8a5f

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/17/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/17/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
123
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
1
The patch has no whitespace issues.

_ Other Tests _

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

152

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/18/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 8cdbbe0596f1 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / dc129a6

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/18/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/18/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
85
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

114

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/19/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux c20c0074a03a 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 3e09b6e

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/19/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
51 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/19/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
87
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

116

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/20/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 9fe79bceb7e7 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / bb43873

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/20/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/20/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
934
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

962

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/21/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux afd278b7fdab 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 0255243

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/21/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/21/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
80
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

107

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/22/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 7f5a571b6fef 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / f24f66e

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/22/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/22/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
124
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

155

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/23/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 14cb1a5cfbba 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / d76a93e

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/23/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/23/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
121
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
1
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

148

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/24/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 8e22c7e12a4d 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / 8df783b

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/24/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
47 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/24/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
113
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

141

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/25/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 66e36b70919a 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
precommit/src/main/shell/personality/yetus.sh

git revision
master / 5aca27b

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/25/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
47 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/25/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
119
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

-1
shelldocs
0
The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

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

147

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/26/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/1

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux b017c143ca76 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
precommit/src/main/shell/personality/yetus.sh

git revision
master / ebdf1ea

shelldocs
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/26/artifact/out/diff-patch-shelldocs.txt

Max. process+thread count
46 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-1/26/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

Closing this since this PR appears to be dead.


Backgrounding Downloads

It would be nice to background file downloads.
'cause they are not right now.

Good idea, we will definitely look at implementing this.

Unfortunately this isn't going to be easy due to the current agent architecture. We have someone working on a revamped jobs approach, after which it may be easier. If not we'll revisit and see if we can adapt the code in some way.

Hey @Ph1LZ,
We currently have a development timeline set for some much needed updates to the internal architecture of the framework. We are laying the groundwork so we can work in the more "complex" architecture updates in the near future (background jobs being one of them). We definitely have this (with many other things) lined up to be added.
Thanks!


fmd-1080 - Add  pattern to refresh period

Adds Not provided pattern to Refresh period on details page


If collection items fail to resolve for some reason, don't do the edit

Attempt to help with items disappearing from playlists.
May not help, but shouldn't hurt anything either.
This fixes a scenario where resolving of collection items has failed for some reason. And the edited version of the list would end up only having the new item in it.
Now it will show additional error notification, and doesn't do the edit.
doFetchItemsInCollection seems to have some catching, so calling it even if items were already fetched, doesn't create unnecessary new claim_searches
Few minor ugly things, will polish if this helps with the main issue(still better than the list being wiped silently):
-Even if the error happens the checkbox stays checked (need to manually uncheck/recheck)
-The "item added" notification will also be shown still (it's behind the error notification)

Should we send a message to the error channel in this case?
Should it also tell the user to retry their last action?


Fix Font Settings not propagating to the Channel View

Hi!
I was using WinIRC and I found out that the font settings didn't affect anything. Here's a fix for that

@mlarouche how the hell did I miss that
Thanks for the PR!


$HOME/.Xilinx

I just found out that I have ~/.Xilinx/ after auto-installed using flatpak wrapper.  There is .Xilinx/xinstall/xinstall_1634630342179.log with today's timestamp.
So, is this norm? I thought it provides sand-boxing?

Sorry for the very late reply, somehow the notifications for this project were disabled.
It is sandboxed, however ~/.Xilinx is explicitly exposed to the sandbox, as it contains logs and the license files. I will add a note in the README.md file though, thank you for reporting it.


Add file extensions to generated imports

Adds file extensions to auto-generated imports so user's can use Tanstack's file-based router with Deno (v2+)
(and other tools that enforce strict ECMAScript module compatibility.)
To test:

Have Deno v2 installed
Build and run the project as outlined in CONTRIBUTING.md
Navigate to an example project
Delete tsconfig.json file
Run : deno task dev

The example project should start without errors.

I think we already handle this via addExtensions, see https://github.com/TanStack/router/discussions/2528#discussioncomment-10926617


v20210517: strange numbers for wind data

Hi,
Unfortunately I can't figure out some of the wind values as output by the plugin. In my setup all data (apparent wind, course and mag heading) originate from signalK:  in the attached screenshot (output of wget http://<IP_ADDRESS>:8080/viewer/avnav_navi.php?request=gps ) you find these marked by checkmarks in blue circles.
Some derived values (greenish check) are correct, however I have no explanation for the others marked by question mark.
Would you mind to have a look into this?

the bug was caused by using some values from a previous run (see commit).
Nevertheless the wind-direction calculation (AWD and TWD) was correct, based on wind-angle and COG.
Closed with v20210531

Sorry and excuse me, I can't follow ... what's the impact of COG? To my understanding COG is irrelevant, especially as speed is zero - it reflects erratic GPS jumps (the 'boat' is presently moored on my desk).
When moored AWA should equal to TWA, as well as AWS to TWS.
AWA relates to the boat's bow (the bow hardly ever points in exact COG direction, thinking of leeway (drift) or current) - so HDG should be used to determine AWD (and TWD, of course).
Just my 2 cents - maybe we can discuss via chat or forum?

just an addition: are you aware of the mariner's odd habit (including signalK) to define 'true wind' as windspeed over water  - not as windspeed over ground (GWD) as the rest of the world in meteorology and aviation does)
Unless you are boating on a river the difference might be marginal - however STW would have to be used instead of SOG


Added Laravel Build in method for conditional execution

PR Description:
This PR introduces replace the method for conditional execution within the workflow management system. The when and unless method allows the execution of a callback and a default callback based on a provided condition, enhancing the flexibility and readability of workflow definitions.
Changes Include:
Added build in Laravel Conditionable trait for conditional execution.
Updated WorkflowTraits to utilize the Conditionable Trait for tracking events and registering observers conditionally.
Example Usage:
<?php

namespace App\Workflows;

use App\Actions\CalculateTotal;
use App\Actions\MakePayment;
use App\Actions\ValidateCartItems;
use App\Actions\SendEmailReceipt;
use Safemood\Workflow\WorkflowManager;

class PaymentWorkflow extends WorkflowManager
{
    public function handle()
    {
        $this->when(true, function () {
            $this->registerObservers([
                DummyModel::class => DummyModelObserver::class,
            ]);
        });

        $this->when(true, function () {
            $this->addBeforeActions([
                new DummyAction(),
                new DummyAction(),
            ]);
        });

        $this->unless(
            value: false,
            callback: fn () => $this->trackAllEvents(),
            default: fn () => $this->doSomething()
        );
    }
}

Thanks for the PR! This is a much better approach. I appreciate the improvements you've made.


fix: directory refactor

current design works well enough, but to support maintainability and future enhancements, the file structure should be refactored to make better use of idiomatic rust directory layout.

The advantages of this wont be apparent until we add functionality outside of core capycrypt, i.e. zero-knowledge proving mechanisms. Put this on hold until we need it.

Then, in the Cargo.toml at the head of the project, we include all of the members:
[workspace]
members = [
    "lib_name",
    "bin_name",
    "another_lib"
]

this is needed somewhat more urgently now in order to bring the curve back in, which will resolve #40.


Integration testing of components

Hi,
I am having trouble getting integration tests to pass without explicitly injecting the i18n service inside the component, which defeats the purpose of this add-on.
Can you please recommend a way to test so that the service gets injected properly?

These injections are for a running app, not integration tests. I'm assuming you are integration testing. Initializers are not run in component integration tests. See more here https://github.com/emberjs/ember.js/issues/12114


Improve dependencies column on resources page (Issue #2878, PR #2910)

Description
iso4
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso4 in 69e033a140b40cf986b875f6236beb1e020f549c


Add option to exclude line patterns

This extends the functionality already provided of ignoring LCOV_EXCL_LINE and lines with only '}'.
You can now give on the command line (or in the yml) exclude-lines-pattern, a list of regex matching lines to ignore.
Moreover, this adds the default of also ignoring lines with only '};' (as created by the end of an array or a lambda).

Any timeline on a release with that patch? I'm using pip to install cpp-coveralls on travis, I'd like to avoid having to clone it manually.

@nitnelave  Thanks a lot for the contribution! a fresh 0.4.0 version is released. Enjoy :)


[bug] macos window fixed center

Describe the bug
With a clean install on macos, when running yarn tauri dev the window is fixed center, always on top, non-movable.
I have tried adding
 "center": false,
 "alwaysOnTop": false

to window, but no change.
Reproduction
yarn tauri dev
Expected behavior
Window is movable, and not always on top
Platform and versions
Operating System - Mac OS, version 11.6.0 X64

Node.js environment
  Node.js - 14.17.1
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 6.14.13
  yarn - 1.22.17

Rust environment
  rustc - 1.57.0
  cargo - 1.57.0

App directory structure
/node_modules
/public
/src-tauri
/src

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../build
  devPath - http://localhost:3000
  framework - React

Stack trace
No response
Additional context
No response

Can you try using the next branch and see if the issue still exists?

change tauri and tauri versions in src-tauri/Cargo.toml

tauri = { git = "https://github.com/tauri-apps/tauri", features = [..] }
tauri-build = { git = "https://github.com/tauri-apps/tauri" }

install the git version of the cli

cargo install tauri-cli --git https://github.com/tauri-apps/tauri

run the app

cargo tauri dev

this failed to build with error[E0658]: use of unstable library feature 'is_symlink'
tauri-utils/src/platform/starting_binary.rs:71:16
.map(std::fs::Metadata::is_symlink)

@omaksi is_symlink is stable since<EMAIL_ADDRESS>(latest is 1.58.1). So the "fix" is to upgrade your rust version.
Keep in mind that there are huge changes in the next branch since amr posted this (we merged the audit changes and are preparing the first rc), so you may hit more blockers than this.

Ok, updated rust and the build went through, but yarn tauri dev returned:
process didn't exit successfully: `.../src-tauri/target/debug/build/app-3244ac4e2def1d4d/build-script-build` (exit status: 101)

  --- stdout
  cargo:rerun-if-changed=src/Cargo.toml
  cargo:rerun-if-changed=tauri.conf.json

  --- stderr
  thread 'main' panicked at 'error found during tauri-build: unknown field `readTextFile`, expected one of `scope`, `all`, `readFile`, `writeFile`, `readDir`, `copyFile`, `createDir`, `removeDir`, `removeFile`, `renameFile` at line 1 column 924', .../tauri-9dcc2f9152472c1a/d0f9a03/core/tauri-build/src/lib.rs:103:5

Yep, that's one of the pain points. You can't use the npm cli until the next release. So for now it's cargo tauri dev (you probably need to re-install the cli first so that it includes changes added the last 2 days) -> see amr's step 2 + 3

@omaksi is_symlink is stable since<EMAIL_ADDRESS>(latest is 1.58.1). So the "fix" is to upgrade your rust version.

Are you sure?

Actually is_symlink was stabilized in Rust 1.58: https://blog.rust-lang.org/2022/01/13/Rust-1.58.0.html#stabilized-apis

Ah whoopsie, i was pretty sure it was 1.57 🤷
Our MSRV is wrong then btw

Yeah we forgot to update this. I'll PR it.

Is there a reason why you haven't updated rust?

I use Nixpkg and 1.57.0 is the newest one I see a commit hash for at the moment

I did find a workaround, I just had to dig until I found that installing using the Dec 28th 2019 commit hash on the next branch fixes the issue for me

can you share the commit hash please?

Sure!
# pinned to tauri next-branch ~v1.0.0-beta.7 2021-12-28
cargo install --git https://github.com/tauri-apps/tauri/ --rev efbf236f35a1dd4064c0615b56881e4132a249f4 tauri-cli

This version shouldn't work with tauri@rc, or at least not 100% (apart from 3 months of bugfixing ofc), if you need rc support you can install the cli from this branch: https://github.com/tauri-apps/tauri/pull/3579

Yeah like I said I'm using pinned older versions of Tauri to avoid instability.
[build-dependencies]
tauri-build = { version = "1.0.0-beta.0", features = [] }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "= 1.0.0-beta.1", features = ["api-all"] }
tauri-utils = "= 1.0.0-beta.0"
tauri-codegen = "= 1.0.0-beta.0"
tauri-macros = "= 1.0.0-beta.1"
tauri-runtime = "= 0.1.1"
tauri-runtime-wry = "= 0.1.1"

I to plan to update everything incrementally, but only after making sure all my test cases pass.

We don't support the beta anymore @jeff-hykin

When I was trying RC versions I got the error that was mentioned earlier
--- stderr
  thread 'main' panicked at 'error found during tauri-build: unknown field `readTextFile`, expected one of `scope`, `all`, `readFile`, `writeFile`, `readDir`, `copyFile`, `createDir`, `removeDir`, `removeFile`, `renameFile` at line 1 column 924', .../tauri-9dcc2f9152472c1a/d0f9a03/core/tauri-build/src/lib.rs:103:5

Suggestion I found online was to install Tauri-cli directly from the latest master. That had compiler issues for me.
There was version mismatches + ,conflicts between tauri-utils, tauri-macros, tauri-runtime, etc which is why I had to pin all of them down via guess-and-check to get them to be compatible with each other.
That worked and I can build apps atm, but it's possible the most up to date is still broke on Mac.

@jeff-hykin - please create a new issue or discussion please, because this is really about the question if the center is fixed, or not.
We NEVER promised that beta would be stable or even work for anyone for any purpose. It was a stepping stone to get us where we are today, and now we are in the RC phase. Yes, software in alpha and beta and RC changes. That is the nature of the beast.

I'm not able to reproduce this, so closing for now. Feel free to open a new issue if you experience it again

Encase anyone still hits this, I'm no longer able to reproduce with this setup:
tauri-cli (master as of today)  cargo install --git https://github.com/tauri-apps/tauri/ --rev 6839fde11de39e6eafaee31782825eda1d7f2266 tauri-cli
Rust
rustc 1.61.0-nightly (76d770ac2 2022-04-02)
cargo 1.61.0-nightly (1ef1e0a12 2022-03-31)
Cargo.toml
[build-dependencies]
tauri-build = { version = "1.0.0-rc.5", features = [] }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "= 1.0.0-rc.6", features = ["api-all"] }
tauri-utils = "= 1.0.0-rc.4"
tauri-codegen = "= 1.0.0-rc.4"
tauri-macros = "= 1.0.0-rc.4"
tauri-runtime = "= 0.3.4"
tauri-runtime-wry = "= 0.3.5"

Yeah I'm getting the same error when running with yarn and rustc 1.58, cargo 1.58.
  thread 'main' panicked at 'error found during tauri-build: unknown field `readTextFile`, expected one of `scope`, `all`, `readFile`, `writeFile`, `readDir`, `copyFile`, `createDir`, `removeDir`, `removeFile`, `renameFile` at line 1 column 924', .../tauri-9dcc2f9152472c1a/d0f9a03/core/tauri-build/src/lib.rs:103:5

Fixed by running
cargo tauri dev


Don't write empty dev tools extensions file

Remove the DevTools Extensions file when the loaded extensions array is empty instead of writing an empty array to the file.
This prevents the file from getting created when no extensions are used in the app.
Fixes #4296

/cc @jlord :eyes:

:+1:


GOLD: measure user conversion through a funnel

Spike a branch that introduces these events:

[x] VisitorLanded

[ ] add utm_source, utm_campaign and similar

[x] VisitorTookAction

[x] commit
[ ] add Referer
[x] add a visitorId
[x] make visitorId unique per visitor
[x] track visitorId in acquisition events

[x] UserAcquired

[ ] which should happen before UserLoggedIn, or maybe VisitorLoggedIn?

[x] UserLoggedIn
[ ] funnel report

[ ] columns

[x] visitor landed
[ ] visitor took action
[x] user acquired
[x] user followed community

[x] as a count

[x] date selector for cohort of visitors
[x] ~how to exclude visitors that turn out to be users acquired before?~ arguably best not to do this, as we wouldn't be excluding visitors that are users but do not log in

and write queries to write a cohort conversion report.

@BlueReZZ any pull?

Yes, the higher level metrics that fit nicely at a strategy level are similar to ones that a lot of start ups use:
Monthly Active Users (MAU)
User Cohort Retention
Customer Acquisition Cost (CAC)
User Churn Rate
I'd like to focus on one of these at a time, while keeping an eye on the others and ensuring they aren't going the wrong way. For example, we have the opportunity to drive lots of traffic to the site soon (via eLife and other Twitter accounts) but we want to make sure we acquire those users from that traffic. Next step is to ensure we retain those users once acquired.
Good metrics for that would be helpful all round.
Some interesting reading on the caveats with MAU https://baremetrics.com/academy/startups-know-monthly-active-users
Also googling those terms throws up some interesting reading

Spike branch: spike/funnel

Sample events generated locally using 2 Twitter accounts and a few incognito windows:
thehive=# SELECT * FROM events ORDER BY date;
                  id                  |              type              |          date           |                                        payload
--------------------------------------+--------------------------------+-------------------------+----------------------------------------------------------------------------------------
 9d892eff-4f90-4f20-a9b2-95ab59cc1cdc | VisitorLanded                  | 2020-10-01 13:54:39.714 | {"visitorId": "709aa15e-051c-4deb-bb27-d2f24e749dfe"}
 2a3c8b85-b482-44fa-9aae-dcf18c902b87 | VisitorTookAction              | 2020-10-01 13:55:12.63  | {"visitorId": "709aa15e-051c-4deb-bb27-d2f24e749dfe"}
 707e3dee-3337-4e57-bf46-319e58ab98df | UserAcquired                   | 2020-10-01 13:55:15.639 | {"userId": "47998559", "visitorId": "709aa15e-051c-4deb-bb27-d2f24e749dfe"}
 a6b5a91f-13d1-4614-b416-a1c0dfaad2b0 | UserLoggedIn                   | 2020-10-01 13:55:15.659 | {"userId": "47998559", "visitorId": "709aa15e-051c-4deb-bb27-d2f24e749dfe"}
 625c2bef-4299-44c6-bacc-470fad2807d4 | UserFollowedEditorialCommunity | 2020-10-01 13:55:28.012 | {"userId": "47998559", "editorialCommunityId": "b560187e-f2fb-4ff9-a861-a204f3fc0fb0"}
 83e280c6-b846-4899-9ad3-4f338cc2792e | VisitorLanded                  | 2020-10-01 13:56:41.768 | {"visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 ab651c83-c5f3-467f-a837-a42ffda276e3 | VisitorTookAction              | 2020-10-01 13:56:50.945 | {"visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 62d01209-5962-46b7-938a-a500a3ed8a64 | UserAcquired                   | 2020-10-01 13:56:56.512 | {"userId": "1295307136415735808", "visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 14855789-5bd0-4db0-86ab-9dcc7c893c02 | UserLoggedIn                   | 2020-10-01 13:56:56.537 | {"userId": "1295307136415735808", "visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 1448bc2e-d2fe-400f-a601-2e0332dd81d3 | VisitorLanded                  | 2020-10-01 13:57:18.209 | {"visitorId": "0f9d0dcb-61de-4dd5-80c1-99653f40dde8"}
 5fb7c1c8-66cf-4d51-8fed-da734adfc40b | VisitorTookAction              | 2020-10-01 13:57:21.499 | {"visitorId": "0f9d0dcb-61de-4dd5-80c1-99653f40dde8"}
 44894f29-68a8-455b-bf85-8dbbb6c08a67 | VisitorTookAction              | 2020-10-01 13:57:34.104 | {"visitorId": "0f9d0dcb-61de-4dd5-80c1-99653f40dde8"}
 db71ed36-55e3-4e85-8819-29619be87d7c | VisitorTookAction              | 2020-10-01 13:58:13.665 | {"visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 de6ce86a-30c4-4777-9821-54cd5a45a6b2 | UserLoggedIn                   | 2020-10-01 13:58:16.248 | {"userId": "1295307136415735808", "visitorId": "7119a603-139e-4cec-ae92-697c23da167c"}
 11a32264-6307-417e-a967-6bc658a9ee11 | VisitorTookAction              | 2020-10-01 13:58:21.983 | {"visitorId": "0f9d0dcb-61de-4dd5-80c1-99653f40dde8"}
 f0c4ce32-b44f-4043-bedd-54b7f8d602d0 | VisitorLanded                  | 2020-10-01 14:14:35.646 | {"visitorId": "9b56ad96-a8dc-4306-b964-c0900cea376c"}
 39e11ff6-ff0a-412f-a2d2-a6b382535455 | VisitorLanded                  | 2020-10-01 14:14:55.294 | {"visitorId": "0fd19bd6-cc54-4857-9cf1-ae0416797480"}
 72ef5c49-f443-4c3b-bb7e-280dac7f37f7 | VisitorTookAction              | 2020-10-01 14:14:57.086 | {"visitorId": "0fd19bd6-cc54-4857-9cf1-ae0416797480"}
 0a421ade-4ff2-41b3-b4de-7e1eadda3f40 | UserFollowedEditorialCommunity | 2020-10-01 14:38:42.962 | {"userId": "47998559", "editorialCommunityId": "10360d97-bf52-4aef-b2fa-2f60d319edd7"}
(19 rows)

make funnel:
   cohort   |   landed   | took_action |      acquired       | followed
------------+------------+-------------+---------------------+----------
 2020-10-01 | 709aa15... | t           | 47998559            |        2
 2020-10-01 | 7119a60... | t           |<PHONE_NUMBER>415735808 |        2
 2020-10-01 | 0f9d0dc... | t           |                     |        3
 2020-10-01 | 9b56ad9... | f           |                     |        1
 2020-10-01 | 0fd19bd... | t           |                     |        1
(5 rows)


Adopt jupyter assign issues rotation

Auto assign issues based on day of the week

Current rotation:
Saturday: Bill
Sunday: Erik
Monday: Heejae
Tuesday: Jude
Wednesday: Rich
Thursday: Rich
Friday: Erik
At standup we talked about how to make triage go faster. The proposed solution was to auto assign a person every day to be responsible for the first level of investigation of a bug.
That person would

Determine if there is a bug or not
Do some root cause analysis if possible
Assign to triage if something needs to be decided on what to do


different result type of client and requesttransport

Currently the Result[_] type for the client (MonadError[Result, SlothClientFailure]) requires the same type for the RequestTransport. This is also required because the transport actually provides the result. But it does not really make sense to leak our own failure type into the transport implementation. It does not hurt with a future but is kind of awkward in the case of an Either[SlothClientFailure, ?]. You can define your own ErrorType with an implicit for SlothClientFailure or return SlothClientFailure.TransportError(Throwable) in case of an error, this also what is returned downstream when an exception is catched. But SlothClientFailure should not be part of the RequestTransport signature.
How to improve this?

I actually think this fine now. We need the result type to swallow the error.


Calling validate with no arguments exits silently

I used yo office to generate a manifest-only project, and tried yarn validate to check the generated manifest, which (after I fixed line endings, see #16), exited silently, which I assumed meant validation succeeded.
It turns out that I needed to specify the path to the manifest file to validate, but that wasn't clear to me (I didn't read the readme closely enough).  I propose providing a help message to users if they try to run the validator without an argument, letting them know they should specify the path to a manifest file to validate.

Closing all issues since this repo is being archived and no longer maintained.


add css modules

Description

Add css modules

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use pgtyped to handle raw queries

Problem
Since Prisma can't guarantee type safety for raw SQL queries, I decided to use pgtyped for the raw queries, while using Prisma for the other queries.
In order to run a query, I need to create a new pg client, connect to it, run the query and then close the connection:
// taken from https://pgtyped.now.sh/docs/sql-file-intro
async function main() {
  await client.connect();
  const books = await findBookById.run(
    {
      bookId: 42,
    },
    client,
  );
  console.log(`Book name: ${books[0].name}`);
  await client.end();
}

The thing is, since Prisma has already created a new client, I get the following error in runtime:
Error: sorry, too many clients already

at Parser.parseErrorMessage (../node_modules/pg-protocol/src/parser.ts:357:11)

Suggested solution

Expose pg client outside.
Alternatives
Set the maximum connections to be fixed

Additional context

https://github.com/prisma/prisma/issues/3991 Possible related

The connection limit issue is coming from postgres, not prisma, so that's not really a limit they can increase. I imagine you can create a connection pool to handle just pgTypes queries although it's weird that you'd get an error like that with 2 connected clients in the first place.
I'm not sure if Prisma would be able to expose the client safely since the entire point is to be an abstraction over multiple database drivers.

@Xetera regarding the error, you're right. It doesn't make sense and apparently, it happened because I didn't end the connections on failed tests.
About exposing the client, I understand the whole idea of abstraction and the motives, but by not exposing it, we're fully dependent on Prisma's API which still missing crucial operations. I will fully understand even if they will expose it as prisma.__unsafeConnection.client or something that will make all of the engines happy.
In any case, I'm closing this issue since it's solved.


[useInfiniteQuery] succeeds in fetching the data, but does not update the data.

Describe the bug
Example code
model
class Post {
    public readonly id: number;
    public readonly images: string[];
    public readonly content: string;

    constructor(data) {
        ...
    }
}

api
class PostRepository {
    public async getListByPage(page: number): Promise<PageResponse<Post>> {
        try {
            const response = await this.client.get(`/v1/posts?page=${page}`);

            return PageRespons.parse<Post>(response.data); // it returns posts with page data likes hasNextPage, etc.
        } catch(e) {
            throw new Error();
        }
    }
}

view
const MyPostListScreen = () => {
    const { data, status } = useInfiniteQuery(
        queryKey: ['post', 'list'],
        queryFn: async ({ pageParam }) => {
            const data = await PostRepository.getListByPage(pageParam.page);

            console.log('FIRST CONTENT:', data.items[0].content); // log content of first post

            return data;
        },
        initialPageParam: {
            page: 1,
        },
        getNextPageParam: calculateNextPageParam, // this function will returns next page param
    );

    useEffect(() => {
        console.log('DATA UPDATED!!'); // log data updated
    }, [data]);

    if (status === 'pending') return <Loading />;
    if (status === 'error') return <Error />;

    return (
        <FlatList ... />
    );
};

console
DATA UPDATED!!
FIRST CONTENT: I am first content
DATA UPDATED!!

// Modify the content to "I'm modified" on another route, then enter the MyPostListScreen again.

DATA UPDATE!! // previous posts rendered
FIRST CONTENT: I'm modified // we can check a new content, but no update data

Why isn't the data updated even though got the data well through the server API call?
When use the useQuery in the same way, the data is updated well.
Your minimal, reproducible example
see in description
Steps to reproduce
see in description
Expected behavior
DATA UPDATED!!
FIRST CONTENT: I am first content
DATA UPDATED!!

// Modify the content to "I'm modified" on another route, then enter the MyPostListScreen again.

DATA UPDATED!!
FIRST CONTENT: I'm modified
DATA UPDATED!!

How often does this bug happen?
None
Screenshots or Videos
No response
Platform
OS: iOS, Android
Browser: React Native
Tanstack Query adapter
react-query
TanStack Query version
5.8.4
TypeScript version
No response
Additional context
No response

Sorry, I tried to runnable reproduction but failed to resolve module from Expo Snack..😓
I realized that's the case in certain situations.
my hook
export const useGetPostsByPage = (params: {
    postRepository: PostRepository;
    filter?: string; // optional filter
}) => {
    const { postRepository, filter } = params;

    return useInfiniteQuery<
        PagingResponse<Post>,
        ServerException,
        InfiniteData<Post, PaginateQuery>,
        QueryKey,
        GetPostListByPageParams
    >({
        queryKey: ['post', 'list', typeof filter === 'string' ? filter : 'all'],
        queryFn: ({ pageParam }) => postRepository.getListByPage(pageParam),
        initialPageParam: {
            size: 20,
            page: 1,
            filter,
        },
        getNextPageParam: calculateNextPageParam,
    });
};

When calling this hook from the view component, it will always be updated without filter.
but If allocate the filter, it was not updated properly.
Is there a problem with the code above?

@TkDodo
I implemented it  in expo, but worked properly.
So I was confused about why my project was having problems, but I knew why.
I was using fetchNextPage as a callback for FlatList's onEndReached, The initial data call and fetchNextPage were being called together because the list had few scrolling areas.
<FlatList
    ...
    onEndReched={hasNextPage ? fetchNextPage : null}
/>

It was completely my mistake. I'll close this issue. Thanks!

@TkDodo
I implemented it in expo, but worked properly. So I was confused about why my project was having problems, but I knew why. I was using fetchNextPage as a callback for FlatList's onEndReached, The initial data call and fetchNextPage were being called together because the list had few scrolling areas.
<FlatList
    ...
    onEndReched={hasNextPage ? fetchNextPage : null}
/>

The problem was solved by using the code as above. It was completely my mistake. I'll close this issue. Thanks!

We had the exact same issue : my guess is if your code is calling fetchNextPage on initialRender, it'll conflict with initial fetch performed by react-query and will results with stale data.
The documentation indicates clearly to not call fetchNextPage if there is no next page :

Keep in mind that imperative fetch calls, such as fetchNextPage, may interfere with the default refetch behaviour, resulting in outdated data. Make sure to call these functions only in response to user actions, or add conditions like hasNextPage && !isFetching.
https://tanstack.com/query/latest/docs/framework/react/reference/useInfiniteQuery


circles on skills radar are broken when we have to much skills

I've noticed this bug in staging env.
When I add more than 25 skills with 3 and 3 as desire and skill level, the circles with 3 and 2, 2 and 3 ect. disappear

On this screen, Angular 7 will disappear in first then Anglais will too..

I'm waiting before working on this, because it could be fix by : https://github.com/Zenika/skillZ/pull/223


Links to static content lead to null body

Describe the bug
I'm not sure at what layer of the stack this problem is occurring, but I've included static content (e.g. a CV) in /static and I'd like to link to it in my index (home page). Adding a relative link via:
CV
seems to work -- however, when I render the site and follow the link -- it leads to a null body (see below):

Any ideas why this happens? Does this seem like a Obsidian thing, or a Hugo thing?
To Reproduce
Steps to reproduce the behavior:

Add static content and a link to it in a post inside the .obsidian managed dir.
Follow the link.

Expected behavior
Expected to lead to the content, not a null body page.
Screenshots
Screenshot attached above.
Desktop (please complete the following information):

Apple M2, Macbook Pro.
MacOS
Firefox

I think this is the same as #167, whose fix was in-progress but seems incomplete.

It seems links within the same domain can sometimes lead to null pages, such as post aliases in Hugo and static files. In my case, disabling the enableSPA setting temporary resolved the issue by forcing the page to reload instead of only replacing the content.

This issue should be fixed in Quartz 4. I'll be closing it for now but please reopen this issue if this persists in the new version.


Create landing page

Landing page have been updated then before

We added Images and text Description to show what the website is used for and have Sign up and Login buttons. This has made the landing page of website more user friendly. Thank you.


How can I interface with the Espect web service from my app?

Short version:
How can I interface with the Espect web service from my app?
Long version:
I need to check the content quality of our own outgoing promotional emails before sending them.
I think using spamassassin for my use case is ideal and i can read here that "Espect is a tiny web service that accepts e-mails, runs them through SpamAssassin and ClamAV and returns JSON. "
In my case, checking every single email sent is not needed, as these are promotional emails and once created they get sent to a chunk of our database, the emails need to be checked for "content quality" just once after creation.
My questions are:
Would it make sense to use espect as standalone?
Is this even a possibility since it´s been merged with postal?
If it can be used as standalone, could you give some guidance as how to do this?
If it must be used as part of postal, Can I enable it for this use case I just explained but keep spamassassin disabled for postal (to save resources as I don´t think I need incoming emails checked for spam, or do i?)

Postal only knows how to send an email to SpamAssassin, if there was another service running on your system that accepted the same input format and returned the same output format that could work transparently.
Postal is mainly designed to just send what it is given, it would be better to use espect yourself as necessary to verify the message before giving it to Postal. I suspect that this would allow you multiple attempts as well.

Great, yes I am sure one single email would be tested several times upon reaching a satisfactory rate.
Question remains tho, how do you interface with the Espect web service from an external APP?

Sorry I completely misunderstood your request.
I don't think you can work with espect externally, it has been embedded into Postal as per https://github.com/atech/postal/commit/f779e45f451cc8f822f9a4196cb9106b5a2eedf9
The spam and virus checking helps mainly when integrating Postal with contact forms, if you want to verify how spammy a message is after you have prepared it, you might get on better with https://www.mail-tester.com/.
If you rely on Postal to vet the messages, it wouldn't be as obvious or detailed as third parties would be.

I understand, for now I would be more than happy if I could just get a basic "spam rate" to show within my app.
I guess I could send an email to postal using my own email address and then route it to my app via http endpoint?

I can't remember if the Postal spam score is included in the email headers but if the message goes past the threshold for spam, it won't be sent at all.

It is my understanding that right postal uses Spamassassin, and Spamassassin can pass an email along with some data about what´s its opinion is about an email without aking any action upon it, so I´m guessing would´t be that hard to tell Espect to behave in the same way.

As per my earlier message, the espect code has been fully immersed into Postals so it isn't a separate queryable entity.
Postal is primarily just an email sender so including a Check My Message function would need a completely separate path through the system and probably falls under https://github.com/atech/postal/wiki/FAQs#can-you-add-mailing-list-feature

Agreed!


fix Refactor some code of trino-connector jni reader

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run buildall

run buildall


Default UDEVDIR=/usr/lib/udev

/etc/udev/rules.d is your local administration directory, where you override rules from system rules directories.
https://www.freedesktop.org/software/systemd/man/udev.html

@omnivagant I picked /etc/udev because this is a kind of local admin install -- hence also /usr/local/bin etc and /etc/systemd

I see what you mean, but I don't think it's right (but who am I to be?). Even if this is installed by a local admin (like doas make install) I still think these default rules should go into something under /usr and any overrides you do as a local admin you do with your editor to files under /etc.
But maybe the default UDEVDIR should be /usr/local/udev then? So that it doesn't conflict when you have already installed this as a distro package..?


odd behaviour

after clicking on add project i just see "/admin/projects" written on page , it does not redirects to project list page

I'll look into it. Feel free to send me a PR if you have a fix.

now your web hook does not work any more it seems bitbucket changed the payload format

I haven't had the time to maintain this project. Feel free to send me a PR
for the updated format if you happen to fix it.
On Sat, Aug 15, 2015 at 1:53 AM, rajneeshojha<EMAIL_ADDRESS>wrote:

now your web hook does not work any more it seems bitbucket changed the
payload format
—
Reply to this email directly or view it on GitHub
https://github.com/jesalg/SlimJim/issues/14#issuecomment-131317389.


Is possible install in raspbian?

Hi, i am a user of this great app in windows (at work) and in os x (Home) but i have a raspberry with raspbian and i wanna make a music server and used by remote control with the phone.
I see a version for linux but im a newbie and i dont know if this version work with a raspberry 2 and raspbian jessie. Is possible?
Thanks in advance!

I am not too familiar with the installation of things on raspberry pi's.
If you can install .deb or .rpm files for either ia32 or x64 architecture then yes it is compatible, otherwise no 👍


Fix ffe lists

This PR fixes a recent issue with ffe-lists where medium and large modifiers were broken.
I've also added this in the docs of ffe-lists-react:

The last commit in the PR is more of a suggestion, where we can allow long words in the description term, without cutting it off and without breaking the layout. Here's a screenshot of what it looks like:

Coverage remained the same at 81.934% when pulling 87af2f4bca25d95386ea0640ef63ee3fc0e33c24 on fix-ffe-lists into ddf619da4aad9738ae0553affb59f2916147b7e8 on develop.


Lines with some colors rendered as white in Linux+NVidia+Firefox 50

When I draw lines with Color.GREY or some other colors lines are being drawn with pure white color.
Take a look at the following example: http://cesiumjs.org/Cesium/Apps/Sandcastle/index.html?src=Hello World.html&label=Showcases&gist=c92b0fbbf5994d7cf07e049dbf1e799a
Here how it looks to me on Ubuntu 16.04 with NVidia driver 367.57 in Firefox 50.0.2

Same result in Firefox 52.0a2:

But I think in some previous versions of Firefox it worked correctly (I haven't noticed this issue on the same version of Cesium in my app about a month ago).
It looks as expected on the same machine in Chromium 53.0.2785.143:

I'm noticing this as well, happens with entity rectangle materials w/ a color fill, but everything works fine when rendering an image texture to the rectangle material

Maybe this is related to #4658?

I see this in Chrome on my Windows 10 laptop Intel HD 4000, so I don't think #4658 is related.

Hi. We've also ran into this issue. It's also been reported to Firefox themselves at https://bugzilla.mozilla.org/show_bug.cgi?id=1321768 Firefox 51 and 52 seems to fix these problems but have other problems mainly in performance areas.

Thanks @HeercoGrond!
@rutsky can you also confirm that this is fixed in the latest Firefox 52 since you saw this issue in  Firefox 52.0a2?

Same model ( a pine tree gltf with an alpha ) , white artifacts in Firefox 50.1.0 (64 bit) and showing up correctly in Firefox 52.0a2

@pjcozzi I can confirm that the issue is not reproduced in latest Firefox Developer Edition (52.0a2 (2017-01-03)):

@mramato , do you think that in https://github.com/AnalyticalGraphicsInc/cesium/issues/4704#issuecomment-264328648 you saw this issue, or was it different issue (so that this one can be closed)?


Update the file where the image names are held to be configure.sh

This is expected to fail for now.


Reduce listinv ore size

About the PR
Ore bags currently have an issue where they do not fill to capacity and are significantly smaller than their upstream counterpart to a crippling level. This should hopefully fix the issue when mining materials where the ore bag fills too quickly and as well as not to capacity.
Why / Balance
Salvagers currently cannot mine as much ore as they probably should be able to vs upstream, meaning it takes more trips and therefore more time to mine due to having to go back and empty out the ore bags very frequently.
Media
N/A

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

tweak: Ore is now smaller!

Did you test these changes in-game?

Tested it, ore bag actually fills up now. Also it holds significantly more now


System Requirements

Main system requirements to implement the library in your own environment.

Document found here:
https://docs.google.com/document/d/1HfPgjmG87e343LBMI4KSSKIK7cysTEZe5peypTC373Y/edit#


Add ClearCommandSystemTest #551

Part of #551. Don't do full review of this first; review #636 and #638 as both tests update AddressBookSystemTest more, which may cause some changes to this PR after they are merged.

v1
@Zhiyuan-Amos submitted v1 for review.

[v1 1/2] Convert ClearCommandTest to ClearCommandSystemTest
[v1 2/2] ClearCommandSystemTest: Add additional tests

(:books: Archive)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/639/1/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

Add test: FindCommand following by ClearCommand

v2
@Zhiyuan-Amos submitted v2 for review.

[v2 1/2] Convert ClearCommandTest to ClearCommandSystemTest
[v2 2/2] ClearCommandSystemTest: Add additional tests

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v1 and v2)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/639/2/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

Cleaned up a bit.

Made the code cleaner; ignore v.1

@yamgent since you've already approved the other 2 PRs, here's one more for you to review :P

@damithc tagging you in for review since system tests are due in the coming week (Week 4) and there shouldn't be major issues with this PR apart from possible missing test cases.


Add documentation about env vars

Description of change
Add documentation and sample for expected env vars
Not having the APP_CLIENT_ID, TENANT_ID
secrets will cause the server to timeout
locally
Not having the SWAGGER_ENDPOINT var
means you will not be able to get to
the swagger docs /docs locally.

strange, the --upgrade command on the apk add for expat in the dockerfile should automatically upgrade it to the newest version which doesn't have this security vulnerability - going to re-run the pipeline for you and see if this fixes it


Frequent "Invalid signature for user or client"

I cannot reproduce it consistently, but I frequently get transient errors for the api key when connecting to the chef server.  I've verified that I'm using the correct key, and there are no time sync issues between the servers.

@phene this usually means times are off.  What versions? There is not nearly enough information here to help me adequately diagnose the problem.

As stated before, I verified the times were in sync as that was my first suspicion.  I am running my own chef server on version 11.12.8.  I agree that there's not a lot of info to go on here, but I figured it would be worth posting this in case others ran into the same issue, which may be indicative of a problem in the library.

@phene without a solid reproduction case and no other user's reporting this problem, the only conclusion is something amiss in your Chef server installation. If you are able to provide more information in the future, we can re-open this issue.

Here's a related ticket https://github.com/chef/chef-server/issues/5

@phene the fact that it's intermittent makes me feel as though it's definitely a server error and not a client error. I'm not denying this is a bug in Chef API, but I can't reproduce the issue, and you are unable to provide a solid reproduction case. Without more information, there's nothing I can do.
I use the Chef API gem very heavily and have never experienced this issue with Hosted Chef, which also leads me to believe there is an issue with your local Chef Server installation. The authentication module is pretty straight forward and follows the exact algorithm for generating the signed header auth as presented in the Chef documentation and Chef itself. ChefAPI has a very verbose debug mode that will output all the signed headers, etc, so you could compare those to what Chef is generating.
I'm not trying to be dismissive, but I do not really know what you want me to do here... I can't fix an issue that even you yourself are unable to reproduce reliably :smile:.

FYI. Last night I was seeing the same issue. My tests were getting ~15% failure rate and today ~1% randomly across all API endpoints. Hosted Chef support verified that this was a server-side issue, and they will be diving deeper on Monday.
Having said that, would make sense to have retry logic in chef-api?

@skierkowski I'm usually :-1: on retries in a library because the end-user likely wants more control over the functionality. So, instead of:
Thing.all(retry: 3, retry_on: [ResourceNotFound], timeout: 50)

and supporting a complex API with every option a user could ever want, I prefer the API to just be:
Thing.all

and the implementing library can wrap that in whatever retry logic it wants:
def retry(&block)
  Timeout.timeout(50) do
    yield
  end
rescue MyCustomException
  do_something
rescue MyOtherCustomException
  do_something_else
end

retry do
  Thing.all
end

Thanks. That makes sense. I'll likely wait it out for the server-side pieces to get fixed before I dive into (dreaded) retries.

I know this has been closed, but I see the same thing. I assumed it was a problem server-side as well, I've been working with Chef Enterprise support for a few weeks on this issue and am 100% unable to reproduce the problem on our Enterprise server install. I wrote a threaded wrapper around a shell/curl script that runs similar API calls. I can do 10k API calls over an hour and get no signature problems, but as soon as I use something with chef-api, the signature problems start showing up in 20-50% of cases, roughly.
I've included chef-api as part of a hack-and-slash Sinatra project.  I'm unsure yet where in the stack the problem falls, but I think I definitively say that it's not chefd.

I can reproduce this rather consistently and I have captured tcp dumps of both successful and unsuccessful api calls. While I do suspect this is a bug in chef server, because it only affects api calls with this ruby gem, I'm posting my data here instead of https://github.com/chef/chef-server/issues/5 since
Symptoms:

Fails about 5 to 10 times out of 50 attempts.
When the ruby script fails, running knife commands in a separate terminal will also fail for a few seconds. (I've never had a knife command fail otherwise)
Fails more often on longer "fetches" (like getting cookbook versions)

I don't consider myself a developer, but here is some ruby which reproduces the problem quite nicely.
sausage.rb
require 'chef-api'
include ChefAPI::Resource

sausage = ChefAPI::Connection.new(
  endpoint: 'https://api.opscode.com/organizations/spuder',
  client:   'spuder',
  key:      '~/.chef/sausage.pem'
)

@aCookbook   = 'elasticsearch'
@theEnvironments = sausage.environments.list
@aDatabagItem = 'foo'

@cookbooks = Hash.new({ value: 0 })
@cookbookAttribHash = Hash.new({ value: 0 })

def cookbookVersions(organization)
  @theEnvironments.each do |anEnvironment|
    cookbook_version = organization.environments.fetch(anEnvironment).cookbook_versions[@aCookbook]
    @cookbooks[anEnvironment] = { label: anEnvironment, value: cookbook_version }
  end
  return @cookbooks.values
end

def environmentAttributes(organization)
  @theEnvironments.each do |anEnvironment|
    if organization.environments.fetch(anEnvironment).default_attributes[@aCookbook]
      cookbook_version = organization.environments.fetch(anEnvironment).default_attributes[@aCookbook]['foo']
      @cookbookAttribHash[anEnvironment] = { label: anEnvironment, value: cookbook_version }
    else
      @cookbookAttribHash[anEnvironment] = { label: anEnvironment, value: nil }
    end
  end
  return @cookbookAttribHash.values
end

puts cookbookVersions(sausage)
puts environmentAttributes(sausage)

You can replace the organization, key and client information, then test like so:
F=0; for i in {1..50}; do echo "Executing run $i"; ruby sausage.rb; if [ $? !=0 ];then F=$((F+1));fi; done; echo "Failed $F times"

In my last test, I had 14 failures out of 50 attempts.
Here is what good output should look like.
The first 9 rows show the version of 'elasticsearch' in each of my environments
The second 9 rows show the value of a default attribute in an environment.
foo@bar-MBP:$ ruby sausage.rb
{:label=>"_default", :value=>nil}
{:label=>"datacenter01", :value=>nil}
{:label=>"datacenter02", :value=>"<= 1.1.1"}
{:label=>"datacenter03", :value=>"~> 2.2.2"}
{:label=>"datacenter04", :value=>"~> 9.9.9"}
{:label=>"datacenter05", :value=>nil}
{:label=>"datacenter06", :value=>nil}
{:label=>"datacenter07", :value=>nil}
{:label=>"datacenter08", :value=>nil}
{:label=>"_default", :value=>nil}
{:label=>"datacenter01", :value=>nil}
{:label=>"datacenter02", :value=>nil}
{:label=>"datacenter03", :value=>nil}
{:label=>"datacenter04", :value=>nil}
{:label=>"datacenter05", :value=>nil}
{:label=>"datacenter06", :value=>20160808.2}
{:label=>"datacenter07", :value=>nil}
{:label=>"datacenter08", :value=>nil}

A failure will output the following

foo@bar-MBP:$ ruby sausage.rb
{:label=>"_default", :value=>nil}
{:label=>"datacenter01", :value=>nil}
{:label=>"datacenter02", :value=>"<= 1.1.1"}
{:label=>"datacenter03", :value=>"~> 2.2.2"}
{:label=>"datacenter04", :value=>"~> 9.9.9"}
{:label=>"datacenter05", :value=>nil}
{:label=>"datacenter06", :value=>nil}
{:label=>"datacenter07", :value=>nil}
{:label=>"datacenter08", :value=>nil}
/Users/foo/.rvm/gems/ruby-2.2.0/gems/chef-api-0.5.0/lib/chef-api/connection.rb:413:in `error': The Chef Server requires authorization. Please ensure you have specified the correct client name and private key. If this error continues, please verify the given client has the proper permissions on the Chef Server. (ChefAPI::Error::HTTPUnauthorizedRequest)

    {"error":["Invalid signature for user or client 'spuder'"]}
	from /Users/foo/.rvm/gems/ruby-2.2.0/gems/chef-api-0.5.0/lib/chef-api/connection.rb:282:in `block in request'
	from /Users/foo/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/net/http.rb:853:in `start'
	from /Users/foo/.rvm/gems/ruby-2.2.0/gems/chef-api-0.5.0/lib/chef-api/connection.rb:268:in `request'
	from /Users/foo/.rvm/gems/ruby-2.2.0/gems/chef-api-0.5.0/lib/chef-api/connection.rb:106:in `get'
	from /Users/foo/.rvm/gems/ruby-2.2.0/gems/chef-api-0.5.0/lib/chef-api/resources/base.rb:252:in `fetch'
	from sausage.rb:30:in `block in environmentAttributes'
	from sausage.rb:28:in `each'
	from sausage.rb:28:in `environmentAttributes'
	from sausage.rb:42:in `<main>'

I have captured wireshark dumps and filtered to just a couple hundred packets that show success and failure scenarios. Unfortunately, chef appears to be preferring ECDHE, which from my research uses perfect forward secrecy, and is impossible to decrypt, even with my chef private and public keys. (If anyone knows a way to get decrypted tcp dumps with chef, please let me know).
Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)

Here are the wireshark dumps. Two are on my home network, and two are while tethered to my cellphone 4g connection.
https://dl.dropboxusercontent.com/u/460997/chef-bug/good-sausage-filtered.pcapng
https://dl.dropboxusercontent.com/u/460997/chef-bug/good-sausage-4g-filtered.pcapng
https://dl.dropboxusercontent.com/u/460997/chef-bug/bad-sausage-filtered.pcapng
https://dl.dropboxusercontent.com/u/460997/chef-bug/bad-sausage-4g-filtered.pcapng
Interesting data points

Every tcp dump has packets that arrived out of order, and also dropped packets
There are a lot of "Server Hello" transactions which seems to indicate the gem is opening a new connection for every api call. (I haven't worked much with API's and development to know if that is normal.)

Environment
Mac Yosemite
Chef Development Kit Version: 0.3.5
Hosted chef (with 0 nodes, 1 user,  ~ 8 environments, 2 organizations)

I tested this again against a local chef server (instead of hosted), and I can reproduce it here too. (Though at a much lower frequency).

Different user
Different key
no ssl

chef_lab = ChefAPI::Connection.new(
  endpoint: 'https://devops-chef.example.com/organizations/dev',
  client:   'foo',
  key:      '~/.chef/foo.pem',
  ssl_verify: false
)

chef-server 12.0.8
chef-client: 12.3.0

@spuder Thanks for the detailed investigation!
@sethvargo As a heads up, I'll take a look at this from the chef-server side this week.

Hi @stevendanna
Thanks!

OK.  I don't think this is a server bug.  In the cases I was able to reproduce, the following was the problem: https://github.com/sethvargo/chef-api/pull/39
It's interesting to me that some reporters where seeing this frequently, since it should occur pretty randomly if that is the only cause of it.  My guess is that the reporters here were experiencing some combination of the bug I posted above and intermittent server load issues.

@stevendanna , thanks a ton for the PR. We've been running into this issue for a while on and off as well.
@sethvargo , will there be a new release for the merged PR?
many thanks to you both.


More compact window option?

The window takes up most of my screen on 1080p so I was wondering if it was possible to make it a more compact window

The window is resizeable, but there is currently a minimum allowable size for the window based on the window's contents...I will look into making this more customizable.
Thanks!

I've pushed a quick fix to the repository, the window can now be minimized much smaller, and the main content area becomes scrollable.  I'll update the .exe momentarily.


ImageWithRoundedCorners not loading however same using visible in layout inspector.

https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example/blob/a44eb99d13516a98ecb3d5f07eff00c6d50d7106/app/src/main/java/com/example/jetpackcompose/image/ImageActivity.kt#L123

Were you running this on the emulator by any chance?

Same for the newly created emulator.

Can you try now. I've just updated it to dev09. I did not see this issue even on dev08 but maybe dev09 fixed it for you @mwshubham

Yes, it is fixed in the latest pull.

Great!


coding with VS Code and but I can't emulate the flutter app in real device (phone)

0
coding with VS Code but i cant emulate the flutter app in real device (phone) and icant use emulator or Android Studio cuz RAM [the syntaxe error on VS Code]
The error is in the image below:

showing issues

i installed ANDROID STUDIO and I fix the problem with the device emulator . but its still tell me
the ANDROID SDK LISCENCE is not found . you should update your SDK. but i did that many times .
so my pc is mindless

I had the same problem when i first started flutter. You need to download some things in android studio. Can't remember what exactly but check out some flutter installation videos on youtube.
Good luck!

For instructions on how to get setup with flutter, see https://flutter.dev/docs/get-started/install


Users SBAT verify faster

Expected Behavior
IBFT has instant finality, so this might speed verification up
Current Behavior
We currently await for a confirmation, which is the block after the one in which a transaction is found?

I believe this is wrong, getting a receipt also triggers getting a confirmation, so we should already move on appropriately


Terraform configs aligned to terraform 1.0.0

What this PR does / why we need it:
Require terraform 1.0.0 and specify all the provider plugins properly.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Terraform 1.0.0 is required

/lgtm


Slides are not working properly with ngFor and loop

From @brandyscarney on December 15, 2015 23:42
<ion-slides loop="true" id="loopSlider" (slideChanged)="onSlideChanged($event)" pager>
  <ion-slide *ngFor="#slide of slides" [ngClass]="slide.class">
    {{ slide.name }}
  </ion-slide>
</ion-slides>

This causes the slide to go to the second slide on loop.
Copied from original issue: driftyco/ionic2#751

From @3dd13 on December 21, 2015 9:29
the DOM element generated is different for with and without ngFor.
perhaps because the DOM7 logic is executed before the ngFor rendering is done
without ngFor:

with ngFor:

Not seeing this in the most recent version.


Jesse: Watch abqcarpetclean.com

Jesse requests the watch of the watch_keyword abqcarpetclean\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

abqcarpetclean\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Running tc016 provides empty est_data output

Issue
No est_data output is included in the output for tc016 (unchanged).
This issue was inherited from the master branch.
Running run_computation and checking the values stored for est_data provides the following output:
[1] PKDATAROWID SDEID       TIME        CEST_KEL    CEST_INT    CEST_EXT    CEST_C0     CEST_TLAST
<0 rows> (or 0-length row.names)

Update
This issue is caused by tc016 having no flags under FLGEXKEL and is expected behaviour. As a result any testing of est_data for tc016 requires OPTIMIZEKEL == 1.