Take Screenshot when "find" fails

When a find operation times out we should capture a screenshot and trace other avaliable elements.
@lefthandedgoat is there already a special way how canopy proper does it? I personally would use a configuration variable for the path and just activate this by default. It's probably also important to trace other elements that we can find on the page.
@part-timedev this is particularly important on the CI. Do we already know if we can tell gitlab that we have special artifacts?

I do screenshots on any failure in canopy, but the only way I know to do it is in the runner.  Do you know if Expecto has an "On Fail" thing we can hook into and make it screenshot then?

/cc @haf @Krzysztof-Cieslak

open Expecto
let testCase name fn =
  testCase name <| fun () -> try fn () with e -> // take screenshot

That's a really nice way to do it. Thanks.
Am 24.12.2016 7:31 nachm. schrieb "Henrik Feldt"<EMAIL_ADDRESS>
open Expectolet testCase name fn =
testCase name <| fun () -> try fn () with e -> // take screenshot
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Canopy.Mobile/issues/14#issuecomment-269095350,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNFxYij1XQLhD8VyqvWROLxqZzlEVks5rLWTxgaJpZM4LUqPF
.

Actually this is so simple and yet so effective. Decades of nunit style
have made me a bit blind.
Am 24.12.2016 7:34 nachm. schrieb "Steffen Forkmann"<EMAIL_ADDRESS>
That's a really nice way to do it. Thanks.
Am 24.12.2016 7:31 nachm. schrieb "Henrik Feldt"<EMAIL_ADDRESS>
:

open Expectolet testCase name fn =
testCase name <| fun () -> try fn () with e -> // take screenshot
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Canopy.Mobile/issues/14#issuecomment-269095350,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNFxYij1XQLhD8VyqvWROLxqZzlEVks5rLWTxgaJpZM4LUqPF
.

this works very well. we should document it


[ROCm] Fix for the broken ROCm CSB.

Now that the PR #32296, and the fix for PR #32444 is rolled back in, all the tests that were failing because of them have started passing again. However there are some other test failures that have crept in during the time the CSB was in a broken state. The test failures are due to new tests/subtests that check functionality that is currently not supported on the ROCm platform (complex data types in BLAS operations, double datatype in convolution and pooling operations). This PR skips such tests to get the ROCm CSB passing again.

@whchung @jeffdaily @chsigg

@whchung please re-approve.
I pushed out a new commit to resolve the py_lint errors found in the Ubuntu Sanity CI run for the previous commit.
thanks
deven


Ensure java 6 source compatibility

The other day, I had a pull request bug as my code depended accidentally on a java 8 default method. Seems it should not have built on any JDK. I wonder if our gradle can be tightened. I'd have guessed that  the following should have done it. Either that's not being read or we need something else like animal sniffer.
sourceCompatibility = 1.6

So this is a problem with the jdk in general. Source compatibility will
keep you from using language features, so 1.6 will flag if you use lambdas
or multicatches, or diamond operators but not if you use a method on a
class that didn't exist in 1.6. Only real way to catch would be to run
compilation and tests in the target jdk. Our Nebula plugins won't run in
JDK6 because we started to use JDK7 features and since 6 was EOL a long
time ago and 7 is EOL at the end of April we won't move the plugins
themselves to be JDK6 compatible. Cloudbees and TravisCI are both set to
run in JDK7 so the pull request jobs should fail on JDK8 only methods.
On Tue, Mar 17, 2015 at 8:43 AM, Adrian Cole<EMAIL_ADDRESS>wrote:

Assigned #344 https://github.com/Netflix/denominator/issues/344 to
@rspieldenner https://github.com/rspieldenner.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/denominator/issues/344#event-257032833.

I see what you mean, though it seems that default methods on an interface
would be caught in source compatibility, right? Ex. that wasn't possible in
the language before 8.
Animal sniffer should be able to take care of at least some of this. I've
used this before in maven, but not yet gradle
http://mojo.codehaus.org/animal-sniffer-maven-plugin/
I probably need to experiment more to see if indeed JDK8 with source
compatibility set to 6 indeed should compile fail on default method usage,
or if I was just crazy earlier.
ps this is more about not having to deal with the weird language support
matrix on android than being able to run on JRE 6

Ok.
Looks like we would need to have javac's boot classpath set on the host we are building in order to enforce a language level.
tw-mbp-acole:tmp acole$ javac -source 1.6 MyIterator.java
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=utf8
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
$ cat MyIterator.java
class MyIterator implements java.util.Iterator<String> {
  public boolean hasNext() {
    return false;
  }

  public String next() {
    throw new IllegalStateException("I said I don't have next!");
  }
  // note I didn't implement remove()!
}
# Note this didn't fail as I didn't set bootclasspath to correspond with the source version
$ javac -source 1.6 MyIterator.java
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=utf8
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning

I think adding animal-sniffer for 1.6 is probably the highest leverage action to take.
Travis running 1.7 will catch most other things that would affect android (ex. accidental use of lambda or default methods).


_posts/0000-01-02-johnlarkin.md.

some thoughts today
this is what I am thinking today.

this is what I am thinking today.


Upgrade jquery-rails 4.2.1

Coverage remained the same at 100.0% when pulling f1f30b0b0709e5bdf5ad04ef892ea8d0d79de7e0 on fix/upgrade-jquery-rails-4.2.1 into 458aada0b0cc3dd305eb2a9e6bc4571562ee1ee3 on master.


Improved spanish translation

Thanks for contributing to our translations. However our translations are managed through Transifex. You'll need to sign up for an account and then submit your translations to the relevant module.
Thanks!


[HUDI-2016] Fixed bootstrap of Metadata Table when some actions are in progress.

What is the purpose of the pull request
Metadata Table cannot be bootstrapped when any action is in progress. This is detected by the presence of inflight or requested instants. The bootsrapping is initiated in preWrite and postWrite of each commit. So bootstrapping will be retried again until it succeeds.
Also added metrics for when the bootstrapping fails or a table is re-bootstrapped. This will help detect tables which are not getting bootstrapped.
Brief change log
Detect any non-complete operation on the dataset. If found, do not start the bootstrap of metadata table.
Verify this pull request

Added / updated tests in TestHoodieBackedMetadata

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #3083 (ed51501) into master (769dd2d) will decrease coverage by 1.76%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3083      +/-   ##
============================================
- Coverage     50.04%   48.27%   -1.77%
+ Complexity     3685     3479     -206
============================================
  Files           526      516      -10
  Lines         25466    24638     -828
  Branches       2886     2833      -53
============================================
- Hits          12744    11894     -850
- Misses        11454    11559     +105
+ Partials       1268     1185      -83

Flag
Coverage Δ

hudicli
39.95% <ø> (ø)

hudiclient
∅ <ø> (∅)

hudicommon
50.03% <ø> (+0.01%)
:arrow_up:

hudiflink
60.58% <ø> (ø)

hudihadoopmr
51.43% <ø> (ø)

hudisparkdatasource
66.53% <ø> (ø)

hudisync
6.79% <ø> (-44.66%)
:arrow_down:

huditimelineservice
?

hudiutilities
9.09% <ø> (ø)

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


[feat] Automatically ping / poll any dead or unresponsive nodes upon status change

Problem/Motivation
I have been experiencing a higher than usual occurrence of the "unknown" status on various Z-Wave nodes. 99% of the time, this problem is immediately fixed by running the ping command. But with 50+ devices, it becomes a daily chore. I have tried healing the network, re-interviewing frequent offenders, but nothing seems to work.
Proposed changes
If possible, could an optional function be added to ping or poll any nodes that have become "unknown" or otherwise unresponsive until they become "alive" again? After a set amount of time, if no response is heard, the devices can be marked as "dead".

PS - I've attempted to create a Home Assistant automation with this functionality, but my knowledge of scripting is subpar and I can't seem to get it working. In case anyone can spot an error in my ways, here is the automation:
id: 'xxxxxxxxxxx'
alias: Red October
description: Pings any dead or unknown nodes on Z Wave Network until a response is heard
trigger:
platform: event
event_type: state_changed
condition:
condition: and
conditions:
condition: template
value_template: '{{ trigger.event.data.new_state.domain == "sensor, switch, lock, light" }}'
condition: template
value_template: '{{ trigger.event.data.new_state.state == "dead, unavailable, unknown, none" }}'
action:
repeat:
until:

condition: template
value_template: '{{ trigger.event.data.new_state.state == "alive" }}'
sequence:
service: zwave_js.ping
target:
entity_id: '{{ trigger.entity_id }}'
delay:
hours: 0
minutes: 1
seconds: 0
milliseconds: 0
mode: parallel
max: 5

No, for multiple reasons:

Attempting communication with dead devices can introduce relatively long timeouts/delays. Some sticks even go haywire under specific circumstances.
Frequently dead devices mean there is a bigger issue with the mesh that should be solved and not just masked by essentially "ignoring" the fact that the communication has issues.
Frequently unknown devices can only happen after startup when the stick doesn't boot properly or stops to function for a longer timeframe. This can be somewhat mitigated with the softreset on startup, but many users have that turned off due to additional host-level configuration that is required to support it on many 500 series sticks.
This also means that the driver isn't done initializing, because the driver actually pings unknown devices on startup to determine if they are alive or dead.

Briefly on the subject of Home Assistant automation: The conditions are wrong.
'{{ trigger.event.data.new_state.state == "dead, unavailable, unknown, none" }}'
This means the state must match the complete value "dead, unavailable, unknown, none" exactly - all at once.
But the state only assumes one of these possible values. So it must be like this.
{{ trigger.event.data.new_state.state in ["dead", "unavailable", "unknown", "none"] }}
The same applies to domain.
PS: The automation will run "forever" if the device is actually broken.

Thanks @AlCalzone for explaining the barriers to a feature like this.
I can disable the "softreset" option my 5+ stick, but the problem doesn't seem to happen at startup. It'll be running for hours (or days) without issue and then suddenly a couple nodes will suddenly become "unknown". I can ping them and they immediately respond and change status back to "alive".
Does this still sound like a startup issue?
It sounds like it's not a really a viable change to the zwavejs2mqtt software. If it's a problem on my 5+ Z stick, do you recommend updating its firmware? or maybe changing to a new stick?
And appreciate the code fix, @christopherthiele -- is there a way I could have the ping commands run a few times and then stop it if the devices are indeed offline?

Yes. You can extend the until condition:
{{ trigger.event.data.new_state.state == "alive" or repeat.index >= 10 }}
This exits the loop when the node is alive or 10 iterations have been reached.

I can disable the "softreset" option my 5+ stick

That's not what I meant. It should ideally be enabled.

without issue and then suddenly a couple nodes will suddenly become "unknown"

There is no state transition that allows the node status to become unknown. Its more likely that the driver is restarting for some reason (do you have driver logs?) and then you're experiencing startup issues.

@christopherthiele - I will give that a try, thank you!
@AlCalzone - copy that. I have reenabled "softreset" and will see how it goes. Right now, all nodes are showing as alive and well, but when I get up tomorrow, I will see if there are any issues. I'll provide logs if there are! Thank you for the help on this.


Duplicate entry for key 'uniq.sales_channel_domain.url'

I am constantly getting this error after the services get restarted. I am not even sure how to resolve this without updating the database.
I am wondering if it is needing something locally that can't be guaranteed if the container is swapped out. There shouldn't be a need for a shared volume, right? That would cause a few problems I would imagine.
 // Clearing the cache for the prod environment with debug
 // false

 [OK] Cache for the "prod" environment (debug=false) was successfully cleared.

22:23:39 ERROR     [console] Error thrown while running command "user:create admin --admin --password=shopware -n". Message: "User with username "admin" already exists." ["exception" => RuntimeException { …},"command" => "user:create admin --admin --password=shopware -n","message" => "User with username "admin" already exists."]

In UserProvisioner.php line 25:

  User with username "admin" already exists.

user:create [-a|--admin] [-p|--password PASSWORD] [--firstName FIRSTNAME] [--lastName LASTNAME] [--email EMAIL] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> <username>

22:23:40 ERROR     [console] Error thrown while running command "sales-channel:create:storefront --name=Storefront --url='http://xxxxxxxxx'".  There will be a single file saved with the current installed version.

Do you know if there is a way around this? I'd prefer to not need a shared volume.

You could add in a new layer a new file /state/installed_version with the current used version

I will add tomorrow a new env to provide the same information as env. Background information for what I need that:
If the file does not exists => Install Shopware
If the file exists and the content does not match the file provided in Image => Update Shopware
Maybe you have a better Idea to handle that. Got the idea from the nextcloud image 😅

Looking at this file, if it's the only variable in the file, then that is perfect for the database or env.
Currently, I have attached a share and it looks fine. It adds a little cost, though not a huge deal if it's just this one file thanks.
Thanks for the speedy response!


HBASE-23055 Alter hbase:meta

Make it so hbase:meta can be altered. TableState for hbase:meta
is kept in Master. State is in-memory transient so if  Master
fails, hbase:meta is ENABLED again. hbase:meta schema will be
bootstrapped from the filesystem. Changes to filesystem schema
are atomic so we should be ok if Master fails mid-edit (TBD)
Undoes a bunch of guards that prevented our being able to edit
hbase:meta. At minimmum, need to add in a bunch of WARNING.

TODO: Tests, more clarity around hbase:meta table state, and undoing
references to hard-coded hbase:meta regioninfo.

M hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
 Throw illegal access exception if you try to use MetaTableAccessor
 getting state of the hbase:meta table.

M hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java
 For table state, go to master rather than go to meta direct. Going
 to meta won't work for hbase;meta state. Puts load on Master.

M hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
 Change isTableDisabled/Enabled implementation to ask the Master instead.
 This will give the Master's TableStateManager's opinion rather than
 client figuring it for themselves reading meta table direct.

M hbase-client/src/main/java/org/apache/hadoop/hbase/client/RawAsyncHBaseAdmin.java
 TODO: Cleanup in here. Go to master for state, not to meta.

M hbase-client/src/main/java/org/apache/hadoop/hbase/client/ZKAsyncRegistry.java
 Logging cleanup.

M hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZNodePaths.java
 Shutdown access.

M hbase-server/src/main/java/org/apache/hadoop/hbase/TableDescriptors.java
 Just cleanup.

M hbase-server/src/main/java/org/apache/hadoop/hbase/master/TableStateManager.java
 Add state holder for hbase:meta.
 Removed unused methods.

M hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/DisableTableProcedure.java
 Allow hbase:meta to be disabled.

M hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/EnableTableProcedure.java
 Allow hbase:meta to be enabled.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 55s
Docker mode activated.

_ Prechecks _

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

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

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

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 37s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 20s
master passed

:green_heart:
compile
2m  2s
master passed

:green_heart:
checkstyle
2m 45s
master passed

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

:green_heart:
javadoc
1m 41s
master passed

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

:green_heart:
findbugs
6m 24s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
4m 59s
the patch passed

:green_heart:
compile
2m  4s
the patch passed

:green_heart:
javac
2m  4s
the patch passed

:broken_heart:
checkstyle
0m 33s
hbase-client: The patch generated 1 new + 97 unchanged - 4 fixed = 98 total (was 101)

:broken_heart:
checkstyle
1m 27s
hbase-server: The patch generated 8 new + 446 unchanged - 19 fixed = 454 total (was 465)

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

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

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

:green_heart:
javadoc
1m 46s
the patch passed

:green_heart:
findbugs
7m 38s
the patch passed

_ Other Tests _

:green_heart:
unit
3m  6s
hbase-common in the patch passed.

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

:green_heart:
unit
0m 49s
hbase-zookeeper in the patch passed.

:broken_heart:
unit
158m 12s
hbase-server in the patch failed.

:green_heart:
asflicense
2m 10s
The patch does not generate ASF License warnings.

238m 59s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.wal.TestLogRollingNoCluster

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

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

git revision
master / 3250a8021a

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-667/1/artifact/out/diff-checkstyle-hbase-client.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-667/1/artifact/out/diff-checkstyle-hbase-server.txt

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

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

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

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 11s
Docker mode activated.

_ Prechecks _

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

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

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

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 34s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 54s
master passed

:green_heart:
compile
2m  2s
master passed

:green_heart:
checkstyle
2m 47s
master passed

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

:green_heart:
javadoc
1m 32s
master passed

:blue_heart:
spotbugs
4m 17s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
6m 46s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 24s
the patch passed

:green_heart:
compile
2m  6s
the patch passed

:green_heart:
javac
2m  6s
the patch passed

:green_heart:
checkstyle
0m 27s
The patch passed checkstyle in hbase-common

:green_heart:
checkstyle
0m 35s
hbase-client: The patch generated 0 new + 97 unchanged - 4 fixed = 97 total (was 101)

:green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-zookeeper

:green_heart:
checkstyle
1m 35s
hbase-server: The patch generated 0 new + 444 unchanged - 21 fixed = 444 total (was 465)

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

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

:green_heart:
hadoopcheck
17m 14s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
1m 30s
the patch passed

:green_heart:
findbugs
7m 25s
the patch passed

_ Other Tests _

:green_heart:
unit
2m 55s
hbase-common in the patch passed.

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

:green_heart:
unit
0m 48s
hbase-zookeeper in the patch passed.

:broken_heart:
unit
236m 29s
hbase-server in the patch failed.

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

318m 39s

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

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

git revision
master / b45c0d0efa

Default Java
1.8.0_181

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

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

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

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

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

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

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

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 34s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 48s
master passed

:green_heart:
compile
2m  2s
master passed

:green_heart:
checkstyle
2m 49s
master passed

:green_heart:
shadedjars
5m  0s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
1m 31s
master passed

:blue_heart:
spotbugs
4m 22s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
6m 51s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 21s
the patch passed

:green_heart:
compile
1m 59s
the patch passed

:green_heart:
javac
1m 59s
the patch passed

:green_heart:
checkstyle
0m 27s
The patch passed checkstyle in hbase-common

:green_heart:
checkstyle
0m 35s
hbase-client: The patch generated 0 new + 97 unchanged - 4 fixed = 97 total (was 101)

:green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-zookeeper

:green_heart:
checkstyle
1m 32s
hbase-server: The patch generated 0 new + 444 unchanged - 21 fixed = 444 total (was 465)

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

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

:green_heart:
hadoopcheck
17m 13s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
1m 30s
the patch passed

:green_heart:
findbugs
7m 23s
the patch passed

_ Other Tests _

:green_heart:
unit
2m 54s
hbase-common in the patch passed.

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

:green_heart:
unit
0m 50s
hbase-zookeeper in the patch passed.

:broken_heart:
unit
160m 43s
hbase-server in the patch failed.

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

242m  2s

Reason
Tests

Failed junit tests
hadoop.hbase.master.TestMasterShutdown

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-667/3/artifact/out/Dockerfile

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

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

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

Build tool
maven

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

git revision
master / 836368189a

Default Java
1.8.0_181

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

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

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

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

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

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

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 31s
Docker mode activated.

_ Prechecks _

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

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

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

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 35s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 34s
master passed

:green_heart:
compile
1m 59s
master passed

:green_heart:
checkstyle
2m 48s
master passed

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

:green_heart:
javadoc
1m 31s
master passed

:blue_heart:
spotbugs
4m 29s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
6m 52s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 23s
the patch passed

:green_heart:
compile
2m  2s
the patch passed

:green_heart:
javac
2m  2s
the patch passed

:green_heart:
checkstyle
0m 27s
The patch passed checkstyle in hbase-common

:green_heart:
checkstyle
0m 33s
hbase-client: The patch generated 0 new + 97 unchanged - 4 fixed = 97 total (was 101)

:green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-zookeeper

:green_heart:
checkstyle
1m 35s
hbase-server: The patch generated 0 new + 444 unchanged - 21 fixed = 444 total (was 465)

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

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

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

:green_heart:
javadoc
1m 30s
the patch passed

:green_heart:
findbugs
7m 22s
the patch passed

_ Other Tests _

:green_heart:
unit
2m 54s
hbase-common in the patch passed.

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

:green_heart:
unit
0m 47s
hbase-zookeeper in the patch passed.

:green_heart:
unit
156m 53s
hbase-server in the patch passed.

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

237m 32s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-667/4/artifact/out/Dockerfile

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

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

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

Build tool
maven

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

git revision
master / 836368189a

Default Java
1.8.0_181

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

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

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

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

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

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

This message was automatically generated.

Reverted from master and branch-2. Made feature branch HBASE-23055. The first commit on the feature branch includes change that addresses the @Apache9 feedback above.


[v4]  and SSR res.status

Is there a way to return a http 404 status if no route matches on server side ?
The new declarative API <Match /> <Miss /> is great but i do not see how to properly get the status of the final SSRendered page.
My workaround is to add a <Status code={}> component into <Miss> children and rewind it at the end to know the final status.
I there a more elegant solution ?

Have you checked the react-router 4 server rendering example? It shows how to deal with no matches on the server.

This is exactly what i needed... I don't believe i missed it...
Thanks @alisd23

No problem :+1:


Chef 402

[
Description

Related Issue

](url)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

Closing this out since it looks like a mistake. If there's something you're trying to do, let us know.


will flask restful be supported in fastapi? fast_restful?

We really like flask_restful and are now experimenting with fastapi.  Do you have plans to make a similar integration in fast?
https://github.com/tiangolo/fastapi

Nope, no plans for this currently


Disable h2c tests

Changes proposed in this PR
Disable two integration tests:

test-internal-protocol
test-trailers-support-h2c-proto-sediment

Why are we making these changes?
Waiting for a new haproxy version before re-enabling these tests.

@shamsimam - We'll need to remember to turn these back on again later.


feat(HACBS-2488): change revision to legacy

This is the first change before removing versions in a feature branch. After merging this branch, all pipelines bundles will get generated again and keep a reference to the right paths in the repository even after removing the versions.

The change LGTM, but as alluded to offline, I think it would be best to wait for some other PRs to merge first (Troy's, and I know Scott wants #203 in production asap)

Yeah, I think this should probably wait until we're done with supporting git resolvers in release strategy - because once that's done, these changes can be done pretty quickly. And in the meantime we can continue making changes to the tasks and pipelines as needed. But it's good to be able to see what the changes look like now.

@davidmogar how did you choose the pipeline versions to update? For example, I can see you updated 3 versions of the deploy pipeline, but 4 versions of the fbc-release pipeline. Do we really need more than the latest?

The change LGTM, but as alluded to offline, I think it would be best to wait for some other PRs to merge first (Troy's, and I know Scott wants #203 in production asap)

Yes. This should stay here until we go for the change.

@davidmogar how did you choose the pipeline versions to update? For example, I can see you updated 3 versions of the deploy pipeline, but 4 versions of the fbc-release pipeline. Do we really need more than the latest?

I updated the versions with git resolvers.

Legacy branch will need the latest commits added

Can we merge this?


genpy: 0.6.1-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository genpy to 0.6.1-0:

upstream repository: git@github.com:ros/genpy.git
release repository: https://github.com/ros-gbp/genpy-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.22
previous version for package: 0.6.0-0

genpy
* lazy init struct (#65 <https://github.com/ros/genpy/issues/65>)
* fix default value of lists to not expand to N items in the generated code (#64 <https://github.com/ros/genpy/issues/64>)
* simpler and more canonical hash (#55 <https://github.com/ros/genpy/pull/55>)
* various improvements to the time and duration classes (#63 <https://github.com/ros/genpy/issues/63>)

Waiting for other releases...


EspNow send function not working properly

The send function is not working if something is blocking the receive callback.
For example:
// esp now initialization ...
let queue: Arc<Mutex<VecDeque<...>>> = Arc::new(Mutex::new(VecDeque::new()));
let queue_clone = queue.clone();
espnow.register_recv_cb(move |_mac_address, data| {
            // ...
            let queue_clone_lock = queue_clone.lock().unwrap();
            // ...
        })

let queue_lock = queue.lock().unwrap();

// Here we receive a wifi message from another esp -> the receive callback is called

let espnow.send(...)

// Send function won't send anything but won't return any error, the code will continue to execute

// ...

I know that this isn't the right way to use the receive callback but can't we send messages while the receive callback is being executed?

do not block in the callbacks, its a real bad idea, just try to get the data out as fast as possible, and then try to evaluate the data in a lower priority task/ thread. Keep in mind that both callbacks running directly in the wifi_driver thread context not in your context. So you will kill the wifi essentially if you do this.
you can inject a std::channel in both the recv and send callback and then just work with the data you got in the main channel.

Okay, that's not good practice. But ideally I could send and receive simultaneously, right?

the callbacks are not related to the part where you can do stuff, they inform you that 'a your packet was send successfully 'b you got a new packet. So you can call send() whenever you want it has no direct blocking connection. This all have nothing to do with simultaneously.

And it has nothing to do with good practice in this case to make it clear. If you block in the callback, the wifi_driver cant do any other work, so potentially catastrophic.

To make your case a bit more clear, you have the main task where you do the work, you aquire a lock in the main task, while you have the lock aquired, the thread gets preamptid into the higher prio wifi_thread task. ( the main task still has the lock) . The callback now is executed inside the callback -> It will wait forever because the task has higher prio. You are in a deadlock

@Vollbrecht thanks for explaining. Closing.

I probably explained myself badly. While I shouldn't do lengthy operations in the callback function, even if the receive callback is blocked I should still be able to send messages. I understand the reason why that's happening, I'm just suggesting that this should not happen. The code above is just an explanatory example

I probably explained myself badly. While I shouldn't do lengthy operations in the callback function, even if the receive callback is blocked I should still be able to send messages. I understand the reason why that's happening, I'm just suggesting that this should not happen. The code above is just an explanatory example

OK I understand your request, but I'm not sure we can do it. If you look at the source code, EspNow is a simple wrapper around the ESP NOW functionality in ESP IDF. So in a way, what you are requesting must be implemented inside ESP IDF itself. I.e. ask them to make receive non-blocking w.r.t. send. However given that it is inside the Wifi driver, I'm very skeptical that anybody would pay any attention to this request. After all, there are tons of workarounds you can apply.

Alright. I opened this issue because for me it was difficult to find out the reason why the send function was not working in certain conditions. Thanks both for your quick reply

on another node if you are using esp-idf 5, the callback we are providing is something suboptimal, we just implemented a quick fix to have both v4 and v5 working, but with v5 you get some more meta information around esp_now_recv_info_t. I planed but did not have the time to upgrade our api to play more nicely here, but i will revisit it the next days


Files structure mismatch from the aws documentation

Hi Team,
Looks like the whole file structure and files have changed from the latest push. There is no docker_native_scripts folder and files. Where do I exactly find them?

@nik13 ,
We have removed docker related folder from this repo.
The repo went through a revamp recently and we are working on getting the documentation fixed in aws as well.
As far as dockerscripts, we are working on adding to our repos. There is no ETA on it yet.
Meanwhile, if you would like a reference the docker scripts, you could look at version 2.1.0 of the sdk and that will have the directory you are looking for.

Hello @nik13 ,
We will be adding the docker scripts to https://github.com/aws-samples/amazon-kinesis-video-streams-demos. Closing this for now. Feel free to re-open the issue in the future.


chore: add openresty to PATH

chore: add openresty to PATH

@spacewander Please check this and if it is OK please merge it thanks~
I need to build a new apisix-base after merging this PR.


add controller scaffold

What type of PR is this?
/kind feature
What this PR does / why we need it:
part #96
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

I think we still lack the clusterrolem but can be in a follow up


openapi(dm): add task config template releated openapi

What problem does this PR solve?
subtask of https://github.com/pingcap/ticdc/issues/3583
What is changed and how it works?
as title, need https://github.com/pingcap/ticdc/pull/3620 merged first
Check List
Tests

Unit test

Code changes

Has exported function/method change

Side effects

Possible performance regression
Increased code complexity

Related changes

Need to update the documentation

Release note
`add task config releated openapi`.

/hold
need add new batch import api after meeting with PM😅

/unhold
could you please take another look for this pr ? thanks 🧡🧡🧡
/cc @glorv  @okJiang @lance6716

please check this api spec of task config  if the api is sufficient for webui
/cc @zoubingwu

Codecov Report

Merging #3656 (700f2d5) into master (eed6f9b) will decrease coverage by 0.4486%.
The diff coverage is 59.6943%.

Flag
Coverage Δ

cdc
57.9577% <71.2361%> (-0.4795%)
:arrow_down:

dm
55.9502% <45.5252%> (-0.4251%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #3656        +/-   ##
================================================
- Coverage   57.3452%   56.8965%   -0.4487%
================================================
  Files           460        478        +18
  Lines         54927      56717      +1790
================================================
+ Hits          31498      32270       +772
- Misses        20180      21158       +978
- Partials       3249       3289        +40

could you please take another look for this pr ? thanks 🧡🧡🧡
@glorv  @lichunzhu  @GMHDBJD

/merge

/run-integration-test
/run-kafka-integration-test

/run-integration-test
/run-kafka-integration-test

/run-kafka-integration-test

/run-integration-test

/run-kafka-integration-test

/run-kafka-integration-test /tidb=pr/30773
/run-integration-tests /tidb=pr/30773


README's Kraftfile does not work

I have an otherwise empty directory with one Kraftfile in it.
This Kraftfile (straight from the README)
specification: v0.5

unikraft: stable

libraries:
  newlib: stable

targets:
  - name: default
    architecture: x86_64
    platform: kvm

gives
$ kraft build --plat kvm --arch x86_64
 W  could not initialize package manager: could not determine handler format=oci
<!> finding core/unikraft                                                 [0.0s]
 E  could not find: core/unikraft
<!> finding lib/newlib                                                    [0.0s]
 E  could not find: lib/newlib
could not complete search: could not find: lib/newlib

while
specification: v0.5

unikraft:
  version: stable

libraries:
  newlib:
    version: stable

targets:
  - name: default
    architecture: x86_64
    platform: kvm

works.

It works on the latest Pre-release. Sorry for the noise. :)


phlexui.com SSL cert is invalid

Can not access the website.

Hey thanks for lettting me know. I contacted @georgekettle about this and we are figuring out what is going on. We'll try to get it back online asap.


mpv + youtube-dl: Failed to initialize a decoder for codec 'av1'

Issue description
YouTube has recently begun serving some videos as AV1. Today I came across one that looks like it can't be decoded by ffmpeg.
Using just youtube-dl to download the same video, I'm seemingly served a VP9 version. Strange.
Steps to reproduce
$ nix run -f https://github.com/NixOS/nixpkgs/archive/e6293287f6f44af22b478ee852461345174a0a01.tar.gz mpv -c mpv "https://www.youtube.com/watch?v=MRqWaRMFsPs"
Driver 'opengl' has been replaced with 'gpu'!
Driver 'opengl' has been replaced with 'gpu'!
Playing: https://www.youtube.com/watch?v=MRqWaRMFsPs
 (+) Video --vid=1 (*) (av1 1280x720 25.000fps)
 (+) Audio --aid=1 --alang=eng (*) 'DASH audio' (opus 2ch 48000Hz) (external)
Failed to initialize a decoder for codec 'av1'.
Video: no video

Exiting... (Errors when loading file)

Technical details

system: "x86_64-linux"
host os: Linux 4.20.5, NixOS, 19.03pre167858.f2a1a4e93be (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2
channels(root): "nixos-19.03pre167858.f2a1a4e93be"
channels(rschuetz): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

You seem to have an old version of ffmpeg not supporting av1.
Check by ffmpeg -codec.
Modifying your youtube-dl accordingly still works, here a quick and dirty fix for both programs in .config:
youtube-dl/conf:
-f 'bestvideo[height<=720]+bestaudio/best[height<=720]'
mpv/mpv.conf
ytdl-format=bestvideo[height<=?720][fps<=?30][vcodec!=?vp9]+bestaudio/best
As youtube will most likely recode all its higher quality videos (above HD quality) into vp9 and av1 (which you can see by youtube-dl -F in the note field,
you should change to a newer ffmpeg version in the longterm.
Note, that vp9 uses webm as extension, so it is not identified easily by mpv/youtube-dl anymore.
Please close this issue, if this resolves your question.

Interestingly enough I did not find support for av1 codec in mpv.
mpv -ovc help -ovcopts help -oac help -oacopts help -of help -ofopts help | less
I would suggest you to use vp9. They finally backported supported for old hardware and it works very good now.
ytdl-format=bestvideo[height<=?720][fps<=?30][vcodec^=vp9]+bestaudio/best

Just in case. Currently, only ffmpeg-full is compiled with libaom (av1) support enabled.

The command on the top post appears to work properly with current channel:nixos-unstable, or at least it starts reading the video properly (which I assume would already fail if it's for a codec error).
Closing as the issue appears to have already been solved in master. :)

It has not been fixed:
$ nix run -f https://github.com/NixOS/nixpkgs/archive/0fc80a5.tar.gz mpv -c mpv "https://www.youtube.com/watch?v=MRqWaRMFsPs"
[15.9 MiB DL]
Driver 'opengl' has been replaced with 'gpu'!
Driver 'opengl' has been replaced with 'gpu'!
Playing: https://www.youtube.com/watch?v=MRqWaRMFsPs
 (+) Video --vid=1 (*) (av1 1280x720 25.000fps)
 (+) Audio --aid=1 --alang=eng (*) 'DASH audio' (opus 2ch 48000Hz) (external)
Failed to initialize a decoder for codec 'av1'.
Video: no video

Exiting... (Errors when loading file)

I'm regularly seeing this with many different YouTube vids.

cc @adisbladis @Infinisil

For better repro you can use this command:
nix run -f https://github.com/NixOS/nixpkgs/archive/0fc80a5.tar.gz mpv -c mpv --ytdl-raw-options=format=397 "https://www.youtube.com/watch?v=MRqWaRMFsPs"

For me, mpv compiled with ffmpeg-full outputs this:
Error while decoding frame!
[ffmpeg/video] libaom-av1: Failed to decode frame: Bitstream not supported by this decoder
[ffmpeg/video] libaom-av1:   Additional information: Buffer -1 does not contain a decoded frame

#66527 should fix this (if we decide to merge it, it's just a proposal for now), reviews and tests would be welcome :)

As ghost already (kind of) mentioned libaom is currently broken.
Bumping ffmpeg-full to 4.2 and adding libdav1d/dav1d as an additional dependency at least solves the decoding problem (haven't tried to encode anything with libaom yet).
I guess it would be sensible to update that package as well in #66527 .
Depending on how broken libaom actually is it would be also sensible to comment the relevant section in ffmpeg-full as at least mpv tries to use libaom first (-> mpv has to be run with --vd=libdav1d)

I guess it would be sensible to update that package as well in #66527 .
Depending on how broken libaom actually is it would be also sensible to comment the relevant section in ffmpeg-full as at least mpv tries to use libaom first (-> mpv has to be run with --vd=libdav1d)

Totally forgot about this comment :o
I've just created a PR for ffmpeg-full as well since no one else did it yet: https://github.com/NixOS/nixpkgs/pull/67205
I've included a patch to prefer libdav1d over libaom for decoding as I also had problems with libaom.


use in chrome extension background script

I was trying to use graphql-request in the background script of a chrome extension, but somehow it break the background script and the script won't be loaded.
a minimal example is as below:
background.js:
import { request , GraphQLClient } from "graphql-request";

const endpoint = 'http://localhost:3000/graphql';
const client = new GraphQLClient(endpoint, { headers: {} });

chrome.runtime.onInstalled.addListener(() => {
  // TODO: on installed function
});
console.log("background running!!")

when reload the extension, there won't log the text in console, and other part of the extension can't send messages to the backgound. but everything works fine if the 'new GraphqlClient' line is commented. the text is logged after reload the extension.
I was wondering if i missed anything, or it's not doable to use graphql-request like this. Thanks!

I realised that this might be my webpack config issue instead something about graphql-request. I'll close this issue. sorry for the confusion.


Implemented DoS writing function

First, I moved output variables in sys_name_DoS.out into sys_name_band.out.
Then, I implemented a function to write the density of states in  sys_name_DoS.out. Thus,  sys_name_DoS.out contains different data from previous versions.
Now, SALMON computes the DoS for solid state systems with Lorentzian broadening (0.1 eV width) at the end of GS calculation, if &analysis/out_dos is set to 'y'.

Thank you Sato san.
I think it is okey to merge.


Better control over library linking

Hi there!
Please consider this example, where exactly the same code produces different output:
Both A) and B) have exactly the same code but the output is different!!!
A) http://melpon.org/wandbox/permlink/osaUfxYIvN39iDXd
B) http://melpon.org/wandbox/permlink/u6g4AEFM5TmolbZe
The only difference, is:
A) Don't use Boost
B) Boost 1.60.0
.
.
.
What's happening here?
Well, certain boost libraries place global data on the free-store (heap).
It's as if the library has code such as this:
const int *ip = new int(0);   // new called for a global!

int main()
{
    memuse();
    return 0;
}

.
.
.
Which boost libraries do this?
(Check the links in the following table, where I specify "extra options" (with clues from here and here)
## extra options
-L/usr/local/boost-1.60.0/lib
-Wl,-rpath,/usr/local/boost-1.60.0/lib
-lboost_atomic
...

D) Not using free-store (heap) http://melpon.org/wandbox/permlink/5IXPhx0yJSkhsz79
E) Using free-store http://melpon.org/wandbox/permlink/Gi2oJxXXsxWFY2Ez

-lboost_atomic

-lboost_chrono

-lboost_container

-lboost_date_time

-lboost_exception (only as .a)

-lboost_graph

-lboost_iostreams

-lboost_math_c99f

-lboost_math_c99l

-lboost_math_c99

-lboost_math_tr1f

-lboost_math_tr1l

-lboost_math_tr1

-lboost_random

-lboost_regex

-lboost_serialization

-lboost_signals

-lboost_system

-lboost_test_exec_monitor (only as .a)

-lboost_wserialization

-lboost_context

-lboost_coroutine

-lboost_filesystem

-lboost_locale

-lboost_log

-lboost_log_setup

-lboost_prg_exec_monitor

-lboost_program_options

-lboost_timer

-lboost_thread

-lboost_type_erasure

-lboost_unit_test_framework

-lboost_wave

.
.
.
What to do about this, to give to user better control in a quick easy way (for the user)?
.
.
So here's an Idea
It would be nice to have something like:
Boost 1.59.0
Boost 1.60.0  ---(popup)--->  [ ] All libraries
                              [ ] boost_atomic
                              [x] boost_chrono
                              [ ] ...
                              ... etc.

So clicking Boost 1.60.0 shows a div, with checkboxes, that allow the user to specify which libraries to link with. Clicking All libraries, would automatically check all; unclicking All libraries would uncheck all checkboxes.
.
.
.
.
One other thing:
I've checked where the libraries seem to be set.
I think it's here:

https://github.com/melpon/wandbox/blob/0884ca33d2d19939683d1fd2ae530f689fd86c22/cattleshed/compilers.default#L1190
https://github.com/melpon/wandbox/blob/0884ca33d2d19939683d1fd2ae530f689fd86c22/cattleshed/compilers.py#L151

Boost 1.60.0 is missing the following libraries, perhaps they can be included:
-lboost_container
-lboost_python                      # hmm... but needs some extra dependencies...
-lboost_test_exec_monitor
-lboost_type_erasure
-lboost_unit_test_framework

Thanks again for this online compiler. Really valuable!
Regards,
ajneu

It is a good proposal. I thought linking all libraries was ugly.
But there is not time to busy. I will implement after.
Please use "extra options" now.


sourcing envsetup.sh crashes shell (iterm2)

on osx 10.11.5 (latest), xcode & other pre-requisites satisfied

Normal OS X Terminal works for you though?

I honestly don't see how this could be something we're doing.  Maybe iterm2 has a bug.  If there's more info that can be provided, please LMK.  Otherwise there's not much to do here.

it's probably some sort of tty issue, etc...are you not developing on osx?

Most of the team are on OS X.  We fully support both OS X and Linux.  I made several builds on my MBP earlier this evening.  Any idea where it's crashing for you within envsetup.sh?  Same thing happens with Terminal or is the crash iterm2 specific?


Problem with rosrun rviz under ROSOnWindows

Hello.This is the first time to ask a question toward Github community.
I recently started to use ROSOnWindows.
In order to launch Rvitz, I typed 'rosrun rviz rviz'. Then, I could open rviz. But, I got the bellow error in the command prompt. Also, several windows appears.
Could you tell me how to solve the problem?
////////////////////////////////////////////////////////////////////////////////////////////////////
[ERROR] [1562757974.232382400]: PluginlibFactory: The plugin for class 'rviz/Orbit' failed to load.  Error: Failed to load library C:/opt/ros/melodic/x64\bin/rviz_default_plugin.dll. Make sure that you are calling the PLUGINLIB_EXPORT_CLASS macro in the library code, and that names are consistent between this macro and your XML. Error string: Could not load library (Poco exception = C:/opt/ros/melodic/x64\bin/rviz_default_plugin.dll)
・
・
・
////////////////////////////////////////////////////////////////////////////////////////////////////

I could solved the problem by installing libraries listed in https://github.com/ms-iot/ROSOnWindows/issues/44

I am getting this exact same error and messages.  I already have QT_PLUGIN_PATH defined.  It doesn't seem to have anything to do with QT.  Also, after hitting  for two of those messages shown above (POCO exception, etc.), when rviz opens, it says, default.rviz -RViz, in the upper left corner of the display.
I checked in plugin_description.xml and the first line states:
I don't know if that is a problem or not.
Also, the list of 16 error messages corresponds to the 16 entries in file default.rviz.
I'm kind of stuck here.  I'm not sure what else to match up or check.
I have RosOnWindows as well.  And I have been using ROS for about 6 months now.
I have found that this similar issue has happened over the last 4 years in linux as well.
But some of that had to do with the change to 64 bit.
http://barelywalking.com/?p=246
I commented on this issue here because maybe it shouldn't be closed if its not a QT problem.
Any help would be appreciated.
Thanks, Smitty


Add covered branches to the meta comment

This PR adds the branches covered by each test case as a comment to the encodings. This makes it easier to spot which test cases overlap and which test cases are responsible for covering which objectives.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 8 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 49.201%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/search/lib/objective/managers/ArchiveBasedObjectiveManager.ts
0
8
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
708

Relevant Lines:
1359

💛  - Coveralls


"Keep Updated" Option Greyed Out

Just did a fresh install of zotero (version 6.0.18) and zotero-better-bibtex (latest release 6.7.42 xpi), and for some reason, I cannot enable the "keep updated" option when exporting. Image attached for reference. I tried this for both exporting a collection and a library and it still didn't work.

You cannot check "keep updated" when "export files" is on.

Oh thank you! It works now.


Fix  #3091: WebSocketMessageTransport.ReceiveAsync null return value isn't handled

RHost can fail at any time after start, including the moment when RTVS requests the handshake.

👍


fix: show errorMessage for inputs without having to pass isInvalid

Closes https://github.com/nextui-org/nextui/issues/2835
If user provides an errorMessage to an input, the input is invalid, there is no need to ask the user to also pass the isInvalid prop
This change was introduced here: https://github.com/nextui-org/nextui/commit/f724509c83ce1586f08ac1042ccacb7ce54cbe83
This was a breaking change introduced 2 weeks ago

Summary by CodeRabbit
Summary by CodeRabbit

Bug Fixes

Adjusted the conditional rendering logic across various components to improve the visibility of error messages and descriptions. Error messages will now display whenever present, and descriptions will only show when relevant and the component is in an invalid state. This change affects:

Checkbox groups
Input fields
Text areas
Radio groups
Select dropdowns

This PR is closed. Please see the following comment for details.
https://github.com/nextui-org/nextui/pull/2994


Large velocities in Soft Contact when the system is prevented from auto-disabling

In creating #961, @jselstad encountered problematic soft contact behavior when he removed Soft Contact's auto-disable timer for debugging purposes:

As far as the root cause of the issue... I don't fully know. To @Amarcolina 's question, I had been testing the soft contact by disabling the disable call to it, but it seems like the bugs I was getting only appeared when I disabled Soft Contact's ability to disable itself (and go away when it's allowed to enable and disable itself...)

I laid eyes on this bug as well; it seemed to happen more reliably when a second interaction hand entered the scene. Objects touched by a hand forcibly kept in soft contact mode would receive large forces from the soft contact system.
When we have some better graphing utilities or build out more test infrastructure for the Interaction Engine, this is a prime stress case: Can we reproduce it, and can we find out when the large velocities are introduced in the soft contact pipeline?

Closing here. Tracking as UNITY-758


Almost finished docs

All that is needed is decent examples and return types and descriptions. See the latest demo here.

The docs are completely done, save getMe(), which I'll ignore for now, since I can't find a return.

I got the default return from the getMe();

"Merged" into Dev.
Great Work!


Regression of disposable async iterators (#59633)

⚙ Compilation target
N/A
⚙ Library
ESNext, Typescript 5.7.2
Missing / Incorrect Definition
AsyncIterator is missing a [Symbol.asyncDispose] property. I found this after investigating a type error I got while creating a polyfill of node:fs's ReadStream. You can follow the rabbit hole here: https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/71307.
At the end, I discovered that AsyncIteratorObject has the [Symbol.asyncDispose] property (from #59633) and since AsyncIterator doesn't extend AsyncIteratorObject, it is missing the property. In fact, AsyncIteratorObject extends AsyncIterator.
Sample Code
declare const it: AsyncIterator<any>;

it[Symbol.asyncDispose](); // <-- error!

Error:
Element implicitly has an 'any' type because expression of type 'unique symbol' can't be used to index type 'AsyncIterator<any, any, any>'.
  Property '[SymbolConstructor.asyncDispose]' does not exist on type 'AsyncIterator<any, any, any>'.ts(7053)

Documentation Link
I wasn't able to independently find anything in the ECMAScript specification or on MDN, so the only reference I have is #59633
Fix
This can be fixed by having AsyncIterator extend AsyncDisposable.

At the end, I discovered that AsyncIteratorObject has the [Symbol.asyncDispose] property (from #59633) and since AsyncIterator doesn't extend AsyncIteratorObject, it is missing the property. In fact, AsyncIteratorObject extends AsyncIterator.

The AsyncIterator type doesn't refer to the builtin object of the same name because TypeScript already used it for the async iterator protocol where it already perfectly legal to have an async iterator that doesn't have [Symbol.asyncDispose].
The new AsyncIteratorObject is the builtin AsyncIterator object (i.e. the one on the prototype of async generators).

declare class Broken implements AsyncItWithNode {
	it: AsyncIterableIterator<any>; // <-- error!
}

The error you are getting in the linked discussion is expected, an arbitrary async iterator doesn't have [Symbol.asyncDispose]. Only those that actually extend the builtin AsyncIterator object, or those that implement it themselves, do.

Great, thanks. I'll look into resolving the issue on @types/node.


Issues with building editors/joe with ravenports-built synth

Trying to build joe or nano I get,
# synth just-build editors/joe
pkg-1.18.4.pkg failed option check.
Stand by, building pkg(8) first ... done!
Error opening terminal: xterm-256color.

# synth just-build editors/nano
pkg-1.18.4.pkg failed option check.
Stand by, building pkg(8) first ... done!
Error opening terminal: xterm-256color.

In reference to #204.

You aren't building inside a jail, right? nothing strange about your environment?

No, not inside a jail. Installing as root.

by the way, you don't still have ABI and ALTABI defined in environment do you? if so, clear that. You probably don't if you rebooted the machine though.

No, that was ephemeral. Not defined anymore.

do you have anything installed at /raven/share/misc/terminfo directory?

No. This is a brand new installation of Synth. joe is the first port I am trying to package.
# ll /raven/share/misc/terminfo
ls: /raven/share/misc/terminfo: No such file or directory

# ll /raven/share/misc/
ls: /raven/share/misc/: No such file or directory

# ll /raven/share/
total 10
drwxr-xr-x  3 root  wheel  3 Oct 18 15:43 licenses/
drwxr-xr-x  3 root  wheel  3 Oct 18 15:43 man/
drwxr-xr-x  2 root  wheel  8 Oct 18 15:43 synth/
drwxr-xr-x  3 root  wheel  3 Oct 18 15:43 zsh/

Again, many thanks for Synth!

No. This is a brand new installation of Synth. joe is the first port I am trying to package.

so that's a problem I think.
The synth port probably needs curses listed as a run dependency.
try this:
/raven/sbin/ravensw install -y ncurses-primary-standard

Then try building joe again

Trying with the install option,
# synth install editors/joe
pkg-1.18.4.pkg failed option check.
Stand by, building pkg(8) first ... done!
gmake-4.3_2.pkg failed option check.
gettext-runtime-0.21.pkg failed option check.
joe-4.6,1.pkg failed option check.
indexinfo-0.3.1.pkg failed option check.

The task is complete.  Final tally:
Initial queue size: 4
    packages built: 4
           ignored: 0
           skipped: 0
            failed: 0

Duration: 00:00:44
The build logs can be found at: /var/log/synth

raised PORTSCAN.BUILDCYCLE.CYCLE_CMD_ERROR : cmd: /raven/sbin/pkg config repos_dir (return code = 127)

/raven/sbin/pkg does not exists in that directory:
# ll /raven/sbin/
total 4897
-r-xr-xr-x  1 root  wheel  8385072 Jul 11  2020 ravensw*

This is problem:
pkg-1.18.4.pkg failed option check.
Stand by, building pkg(8) first ... done!

We'll have to look into that.
There's a conception problem though.
All we are trying to do is install a working version of synth (which is located at /raven/bin/synth I think).
Synth is going to build the freebsd ports, and it should work as before, meaning it eventually installs to /usr/local.
synth just-build only builds the package, so you would not expect joe to be present.
However, synth install should probably have installed it (at /usr/local)

what happens if you copy /usr/local/sbin/pkg to /raven/sbin/pkg ?
(for testing purposes only, you shouldn't have to do this).
Also, can you find /raven/etc/synth.ini and post it here?

also post the /usr/local/etc/synth.ini so we can compare

what happens if you copy /usr/local/sbin/pkg to /raven/sbin/pkg

That fixes it, now I can run joe.
# cp /usr/local/sbin/pkg /raven/sbin/

# ll /raven/sbin/
total 6829
-rwxr-xr-x  1 root  wheel  2966440 Oct 18 19:06 pkg*
-r-xr-xr-x  1 root  wheel  8385072 Jul 11  2020 ravensw*

# synth install editors/joe
After inspection, it has been determined that there are no packages that
require rebuilding; the task is therefore complete.
Stand by, recursively scanning 1 port serially.
Packages validated, rebuilding local repository.
Local repository successfully rebuilt
Updating Synth repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%    3 KiB   2.8kB/s    00:01
Processing entries: 100%
Synth repository update completed. 9 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        joe: 4.6,1 [Synth]

Number of packages to be installed: 1

The process will require 2 MiB more space.
[1/1] Installing joe-4.6,1...
[1/1] Extracting joe-4.6,1: 100%
Building cache database of MIME types

# which joe
/usr/local/bin/joe

/raven/etc/synth.ini and /usr/local/etc/synth.ini  do not seem to exist on my system,
# cat /raven/etc/synth.ini
cat: /raven/etc/synth.ini: No such file or directory

# cat /usr/local/etc/synth.ini
cat: /usr/local/etc/synth.ini: No such file or directory

PS: I need to run out for errands now. I will be back later.

okay, so here's what I need to do for sure.

add ncurses as a run dependency
add freebsd-pkg port, and add that as a run dependency

I checked the man page, the file is located in a subdirectory, e.g.

/usr/local/etc/synth/synth.ini
/raven/etc/synth/synth.ini

But I think the main issue was synth couldn't find the host pkg program because it assumed it was at /raven/sbin/pkg.

an easier fix is just have synth install a symlink of /usr/local/sbin/pkg to /raven/sbin/pkg.  That way I don't have to build pkg and keep it up to date.

I've already updated ravenports synth with these fixes:
https://github.com/Ravenports/ravensource/commit/46118dc7a524be05048d742ca5dfa7538fffa194
It will be a while before it's published though.

I checked the man page, the file is located in a subdirectory, e.g.
* /usr/local/etc/synth/synth.ini
* /raven/etc/synth/synth.ini

# cat /raven/etc/synth/synth.ini
; This Synth configuration file is automatically generated
; Take care when hand editing!

[Global Configuration]
profile_selected= LiveSystem

[LiveSystem]
Operating_system= FreeBSD
Directory_packages= /var/synth/live_packages
Directory_repository= /var/synth/live_packages/All
Directory_portsdir= /usr/ports
Directory_options= /var/db/ports
Directory_distfiles= /usr/ports/distfiles
Directory_buildbase= /usr/obj/synth-live
Directory_logs= /var/log/synth
Directory_ccache= disabled
Directory_system= /
Number_of_builders= 12
Max_jobs_per_builder= 5
Tmpfs_workdir= true
Tmpfs_localbase= true
Display_with_ncurses= true
leverage_prebuilt= false

It seems there is no other synth.ini anywhere on my system:
# cat /usr/local/etc/synth/synth.ini
cat: /usr/local/etc/synth/synth.ini: No such file or directory

fd -i synth.ini
raven/etc/synth/synth.ini

I've already updated ravenports synth with these fixes:
https://github.com/Ravenports/ravensource/commit/46118dc7a524be05048d742ca5dfa7538fffa194

Thank you.

to follow up, I've updated the freebsd repository so hopefully synth pulls in curses and installs a symlink to freebsd's pkg now, making the wiki instructions work as intended.

Thank you. If it makes sense, I would like to go through the process once more, possibly submitting some clarification in the wiki page directions.
I would need to:

Uninstall any package installed via synth, in this case, just joe
Uninstall synth via /raven/sbin/ravensw
Uninstall ravensw itself.
Redo all the steps one more time.

Would you advice on how to perform the first 3 steps cleanly?

Just so you know, any time I run ravensw I get warning, Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended

Would this be correct?

Uninstall any package installed via synth, in this case, just joe

# pkg remove joe
Question: how would one uninstall all packages coming from one specific repository?

Uninstall synth via /raven/sbin/ravensw

# /raven/sbin/ravensw remove synth-single-standard

Uninstall ravensw itself.

rm -rf /raven
rm -rf /var/db/ravensw
rm -rf /var/ravenports

The last 3 rm -rf commands should completely remove everything. You don't
need to do anything else.
Regarding pkg-static message, if you still get it after reinstalling synth,
your /use/local/sbin/pkg needs updating
On Sat, Oct 29, 2022, 02:47 Lisp student @.***> wrote:

Would this be correct?

Uninstall any package installed via synth, in this case, just joe

pkg remove joe
Question: how would one uninstall all packages coming from one specific
repository?

Uninstall synth via /raven/sbin/ravensw

/raven/sbin/ravensw remove synth-single-standard

Uninstall ravensw itself.

rm -rf /raven
rm -rf /var/db/ravensw
rm -rf /var/ravenports
—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/synth/issues/210#issuecomment-1295762269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISZ5QYT47RBNUAE6HHCR3WFTJBTANCNFSM6AAAAAARIHRYXQ
.
You are receiving this because you commented.Message ID:
@.***>

But If I would just apply the 3 rm, wouldn't the joe package, installed via synth ports, still be in the system but no more upgreadable (repo would be gone)?
In any case, I did the three steps above, including the 3 rm, but I could still see the synth repository being referenced by pkg.
To fix that, I also did:
rm -rf /usr/local/etc/synth`
rm /usr/local/etc/pkg/repos/00_synth.conf

Now I am going to replicate the ravensw + synth setup and report back.

The /usr/local/ files are coming from the freebsd ports tree, I guess
On Sat, Oct 29, 2022, 07:41 Lisp student @.***> wrote:

But If I would just apply the 3 rm, wouldn't the joe package, installed
via synth ports, still be in the system but no more upgreadable (repo
would be gone)?
In any case, I did the three steps above, including the 3 rm, but I could
still see the synth repository being referenced by pkg.
To fix that, I also did:
rm -rf /usr/local/etc/synth`
rm /usr/local/etc/pkg/repos/00_synth.conf
Now I am going to replicate the ravensw + synth setup and report back.
—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/synth/issues/210#issuecomment-1295825575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISZ5XYNHESUMPE4LIBEETWFULOBANCNFSM6AAAAAARIHRYXQ
.
You are receiving this because you commented.Message ID:
@.***>

Everything works with no hiccups now:
fetch http://www.ravenports.com/repository/ravensw-freebsd64-bootstrap.tar.gz
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf
/raven/sbin/ravensw upgrade
/raven/sbin/ravensw install -y synth-single-standard
synth just-build editors/joe
synth install editors/joe

Interestingly, when I ran  synth just-build editors/joe I got:
After inspection, it has been determined that there are no packages that
require rebuilding; the task is therefore complete.

It seems synth did not need to rebuild joe, but how could that be? I thought I had completely removed the whole ravensw+synth+related files?
The only possible tweak I could suggest to the wiki page is to specify to edit /raven/etc/ravensw.conf after installing ravensw:
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf

If it doesn't need building, the profile's packages are still present.
On Sat, Oct 29, 2022, 07:52 Lisp student @.***> wrote:

Everything works with no hiccups now:
fetch http://www.ravenports.com/repository/ravensw-freebsd64-bootstrap.tar.gz
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf
/raven/sbin/ravensw upgrade
/raven/sbin/ravensw install -y synth-single-standard
synth just-build editors/joe
synth install editors/joe
Interestingly, when I ran synth just-build editors/joe I got:
After inspection, it has been determined that there are no packages that
require rebuilding; the task is therefore complete.
It seems synth did not need to rebuild joe, but how could that be? I
thought I had completely removed the whole ravensw+synth+related files?
The only possible tweak I could suggest to the wiki page is to specify to
edit /raven/etc/ravensw.conf after installing ravensw:
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf
—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/synth/issues/210#issuecomment-1295828178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISZ5QNKZEDMGZNKOSTLQLWFUMZVANCNFSM6AAAAAARIHRYXQ
.
You are receiving this because you commented.Message ID:
@.***>

"synth configure" will show you where the profile packages are located.
And "synth test joe" will force a build I think
On Sat, Oct 29, 2022, 08:07 John Marino (Github) @.***> wrote:

If it doesn't need building, the profile's packages are still present.
On Sat, Oct 29, 2022, 07:52 Lisp student @.***> wrote:

Everything works with no hiccups now:
fetch http://www.ravenports.com/repository/ravensw-freebsd64-bootstrap.tar.gz
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf
/raven/sbin/ravensw upgrade
/raven/sbin/ravensw install -y synth-single-standard
synth just-build editors/joe
synth install editors/joe
Interestingly, when I ran synth just-build editors/joe I got:
After inspection, it has been determined that there are no packages that
require rebuilding; the task is therefore complete.
It seems synth did not need to rebuild joe, but how could that be? I
thought I had completely removed the whole ravensw+synth+related files?
The only possible tweak I could suggest to the wiki page is to specify to
edit /raven/etc/ravensw.conf after installing ravensw:
tar -C / -xzf ravensw-freebsd64-bootstrap.tar.gz
nano /raven/etc/ravensw.conf
—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/synth/issues/210#issuecomment-1295828178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISZ5QNKZEDMGZNKOSTLQLWFUMZVANCNFSM6AAAAAARIHRYXQ
.
You are receiving this because you commented.Message ID:
@.***>

Ah, all clear now. There were leftover directories:
Synth configuration profile: LiveSystem
===============================================================================
   [A] Ports directory            /usr/ports
   [B] Packages directory         /var/synth/live_packages
   [C] Distfiles directory        /usr/ports/distfiles
   [D] Port options directory     /var/db/ports
   [E] Build logs directory       /var/log/synth
   [F] Build base directory       /usr/obj/synth-live
   [G] System root directory      /
   [H] Compiler cache directory   disabled
   [I] Num. concurrent builders   12
   [J] Max. jobs per builder      5
   [K] Use tmpfs for work area    true
   [L] Use tmpfs for localbase    true
   [M] Display using ncurses      true
   [N] Fetch prebuilt packages    false

   [>]   Switch/create profiles
   [RET] Exit

Thank you for the patience and guidance.


feat: add ha and spread it between az

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MutationFn: Support multiple leaf edits

The current KT mutation function only supports an edit to a single map leaf.
Add support so that a single mutation can touch multiple leaves.

The need for this has been addressed by the ability to batch updates, since the sequencer will not split a batch.


Logger unit tests

Motivation
Description
A few sentences describing the overall goals of the pull request's commits.
Progress

[ ]
[ ] Unit tests
[ ] Documentation

Additional Notes

@wtrocki Can you look at this?

My overall impression is that we should really contribute new tests here and initiate conversation with the team and community around what tooling we should use for testing.

@spriadka - Let's initiate conversation with the team for this particular changes.
Closing for now as this will quickly get outdated.


NPM package lacks *.d.ts files

The published npm package should contain the type definitions.

Closing because this repo is deprecated in favor of https://github.com/kubernetes-client/javascript


Issue about example

Module build failed: SyntaxError:

20 |   handleChange = (newDate) => {
|                ^
21 |     console.log("newDate", newDate);
22 |     return this.setState({date: newDate});
23 |   }

This method define seems not valid in ES6.
May be should change to:
 handleChange () {
}

:+1: Same experience, here


[1.10.2] Rendering Block Entity

Was building an evaporation tower with a builders wand from Better builders wands and when the tower completed I saw the redstone particals then my client crashed. Looks like a rendering error.
MC: 1.10.2
forge: 2139
Mekanism: 1.10.2-<IP_ADDRESS>4
http://pastebin.com/AgPQN2Dt

Try disabling mipmapping and reproducing without Optifine.

Disabled mipmaping and removed Optifine and it built fine. But ones I added water to the multi-block it crashed.  I believe when I built the first one it already had water in it.
http://pastebin.com/DpYapNq6

similar issue but with rendering TiC Smeltery controller
http://pastebin.com/YJJf6Z27

another similar issue, but with rendering universal fluid tank
MC 1.10.2
Mekanism <IP_ADDRESS>4
Forge 1.10.2-<IP_ADDRESS>1
https://gist.github.com/jennybrush/c5c5a47700dd143884ea016554f3bd6f

Fixed in dev


Field should display template if applicable

Related to #4. In the works.

Fixed by b1556620e0ec28937494b2eeb0b9f19c66da51eb.


Not able to train lightning with tpu

To Reproduce
Link
Go to the link and click edit to run the cells for reproducing the error .

@lezwon mind have look? 🐰

This looks to be more like a kaggle memory issue. @sumanthratna try reducing the batch size? Also, to make the notebook public :)

@lezwon are u asking me ?

Tried batch_size  of 512 but still its same ... i also tried to train this 98 GB dataset on Kaggle Gpu but getting cuda device-side assert error . Made  the notebook public

The batch size of 1024 or 512 should be the problem. I tried with a batch size of 32. Seemed to work fine.

I cann't see any changes after changes..  only this thing is appearing

@lezwon  Can u please post ur changes with the progress bar ...

Try this one: https://www.kaggle.com/lezwon/landmark-detection

Thanks @lezwon Seems like it is training n
I saw you added these lines
!pip uninstall typing -y
!pip install -qU git+https://github.com/PyTorchLightning/pytorch-lightning.git
and changed the batchsize to 16 for the model to start training  on tpu ????????
Also getting the RuntimeError: CUDA error: device-side assert triggered  while running
this notebook on gpu

I installed PyTorch lightning from master itself as the TPU support is more stable there. As for batch size, I faced an out of memory issue after a while when choosing 32. Hence 16.

@rohitgr7 any idea about the cuda error?

there shall not be anything about CUDA in TPU ran... mind trace it to the source?

I think it occurs when he runs it on gpu.

@soumochatterjee just LabelEncode landmark_id, it will work.
Also, you need to fix this:
self.aug = albumentations.Compose([
                albumentations.Resize(img_height , img_width, always_apply = True) ,
                albumentations.Normalize(mean , std , always_apply = True),
                Cutout(),
                albumentations.ShiftScaleRotate(shift_limit = 0.0625,
                                                scale_limit = 0.1 ,
                                                rotate_limit = 5,
                                                p = 0.9)
            ])

since Cutout is not in albumentations, you will get an error later on. You can use albumetations.Cutout().

@soumochatterjee is your issue resolved?

Yes @lezwon thanks for all the help .

@lezwon  meet same issue here, can't start training when using tpu with pl(code run success with kaggle gpu).
i try smaller batch size, augument all use from albumentations, install from master branch, still got no luck.
Go to the link and click edit to run the cells for reproducing the error .
kaggle notebook

@lezwon  meet same issue here, can't start training when using tpu with pl(code run success with kaggle gpu).
i try smaller batch size, augument all use from albumentations, install from master branch, still got no luck.
Go to the link and click edit to run the cells for reproducing the error .
kaggle notebook

@feiwofeifeixiaowo the notebook link is not accessible.

@feiwofeifeixiaowo the notebook link is not accessible.

@lezwon @rohitgr7   Do you have any ideas for troubleshooting? Thanks

@lezwon @rohitgr7   Do you have any ideas for troubleshooting? Thanks

@feiwofeifeixiaowo I tried running the notebook with one tpu core. The training seems to start but it's extremely slow. My assumption is that there is some bottleneck when loading your data. I'm still debugging it.

@feiwofeifeixiaowo I tried running the notebook with one tpu core. The training seems to start but it's extremely slow. My assumption is that there is some bottleneck when loading your data. I'm still debugging it.

@feiwofeifeixiaowo I tried running the notebook with one tpu core. The training seems to start but it's extremely slow. My assumption is that there is some bottleneck when loading your data. I'm still debugging it.

yesterday i change read image backend from cv2 to PLI ，still got no luck .

@feiwofeifeixiaowo I tried running the notebook with one tpu core. The training seems to start but it's extremely slow. My assumption is that there is some bottleneck when loading your data. I'm still debugging it.

yesterday i change read image backend from cv2 to PLI ，still got no luck .

hi @lezwon , after set gradient_clip_val to zero everything goes well.
in xla troubleshooting guide link,
it seems that ori gradient_clip_val action will cause this slow thing.

Use torch.where to substitute control flow when applicable. E.g. The control flow with item() used in clip_grad_norm_ is problematic and impacts performance, so we have patched clip_grad_norm_ by calling torch.where instead, which gives us a dramatic performance improvement.
...
else:
  device = parameters[0].device
  total_norm = torch.zeros([], device=device if parameters else None)
  for p in parameters:
    param_norm = p.grad.data.norm(norm_type) ** norm_type
    total_norm.add_(param_norm)
  total_norm = (total_norm ** (1. / norm_type))
clip_coef = torch.tensor(max_norm, device=device) / (total_norm + 1e-6)
for p in parameters:
  p.grad.data.mul_(torch.where(clip_coef < 1, clip_coef, torch.tensor(1., device=device)))

thanks for your help again.

hi @lezwon , after set gradient_clip_val to zero everything goes well.
in xla troubleshooting guide link,
it seems that ori gradient_clip_val action will cause this slow thing.

Use torch.where to substitute control flow when applicable. E.g. The control flow with item() used in clip_grad_norm_ is problematic and impacts performance, so we have patched clip_grad_norm_ by calling torch.where instead, which gives us a dramatic performance improvement.
...
else:
  device = parameters[0].device
  total_norm = torch.zeros([], device=device if parameters else None)
  for p in parameters:
    param_norm = p.grad.data.norm(norm_type) ** norm_type
    total_norm.add_(param_norm)
  total_norm = (total_norm ** (1. / norm_type))
clip_coef = torch.tensor(max_norm, device=device) / (total_norm + 1e-6)
for p in parameters:
  p.grad.data.mul_(torch.where(clip_coef < 1, clip_coef, torch.tensor(1., device=device)))

thanks for your help again.

@feiwofeifeixiaowo ah yes.. calling .item() makes xla to forcibly execute the graph which slows it down. Sorry I didn't catch this earlier and glad you figured it out. Will keep a note of this issue in the docs 😊👍

@feiwofeifeixiaowo ah yes.. calling .item() makes xla to forcibly execute the graph which slows it down. Sorry I didn't catch this earlier and glad you figured it out. Will keep a note of this issue in the docs 😊👍

@lezwon , with albumentations augment blew, Idle Time very high. is there any trick/tips to speed up ?
train_transform = Compose(
        [
            Resize(height=image_size[0], width=image_size[1]),
            OneOf([RandomBrightness(limit=0.1, p=1), RandomContrast(limit=0.1, p=1)]),
            OneOf([MotionBlur(blur_limit=3), MedianBlur(blur_limit=3), GaussianBlur(blur_limit=3)], p=0.5),
            VerticalFlip(p=0.5),
            HorizontalFlip(p=0.5),
            ShiftScaleRotate(
                shift_limit=0.2,
                scale_limit=0.2,
                rotate_limit=20,
                interpolation=cv2.INTER_LINEAR,
                border_mode=cv2.BORDER_REFLECT_101,
                p=1,
            ),
            Normalize(mean=(0.485, 0.456, 0.406), std=(0.229, 0.224, 0.225), max_pixel_value=255.0, p=1.0),
        ]
    )

@lezwon , with albumentations augment blew, Idle Time very high. is there any trick/tips to speed up ?
train_transform = Compose(
        [
            Resize(height=image_size[0], width=image_size[1]),
            OneOf([RandomBrightness(limit=0.1, p=1), RandomContrast(limit=0.1, p=1)]),
            OneOf([MotionBlur(blur_limit=3), MedianBlur(blur_limit=3), GaussianBlur(blur_limit=3)], p=0.5),
            VerticalFlip(p=0.5),
            HorizontalFlip(p=0.5),
            ShiftScaleRotate(
                shift_limit=0.2,
                scale_limit=0.2,
                rotate_limit=20,
                interpolation=cv2.INTER_LINEAR,
                border_mode=cv2.BORDER_REFLECT_101,
                p=1,
            ),
            Normalize(mean=(0.485, 0.456, 0.406), std=(0.229, 0.224, 0.225), max_pixel_value=255.0, p=1.0),
        ]
    )

@rohitgr7 any idea about this?

@rohitgr7 any idea about this?

@rohitgr7 any idea about this?

i add prefetch dataloader, but seems not help yet.
prefetch_generator

@rohitgr7 any idea about this?

i add prefetch dataloader, but seems not help yet.
prefetch_generator

not sure about this. Is it faster when using albumentations in the case of GPUs? try increasing the batch_size (a multiple of 2 maybe) since 8 core TPU training requires a high batch_size to work effectively.
Also, you check some performance tips here:
https://github.com/PyTorchLightning/pytorch-lightning/blob/release/1.2-dev/docs/source/tpu.rst#performance-considerations
FYI, there is a prefetch option in native DataLoader too.
https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

not sure about this. Is it faster when using albumentations in the case of GPUs? try increasing the batch_size (a multiple of 2 maybe) since 8 core TPU training requires a high batch_size to work effectively.
Also, you check some performance tips here:
https://github.com/PyTorchLightning/pytorch-lightning/blob/release/1.2-dev/docs/source/tpu.rst#performance-considerations
FYI, there is a prefetch option in native DataLoader too.
https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

not sure about this. Is it faster when using albumentations in the case of GPUs? try increasing the batch_size (a multiple of 2 maybe) since 8 core TPU training requires a high batch_size to work effectively.
Also, you check some performance tips here:
https://github.com/PyTorchLightning/pytorch-lightning/blob/release/1.2-dev/docs/source/tpu.rst#performance-considerations
FYI, there is a prefetch option in native DataLoader too.
https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

i will try this, thanks~

not sure about this. Is it faster when using albumentations in the case of GPUs? try increasing the batch_size (a multiple of 2 maybe) since 8 core TPU training requires a high batch_size to work effectively.
Also, you check some performance tips here:
https://github.com/PyTorchLightning/pytorch-lightning/blob/release/1.2-dev/docs/source/tpu.rst#performance-considerations
FYI, there is a prefetch option in native DataLoader too.
https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

i will try this, thanks~


Bold followed by a hyphen on the next line becomes a header

I'm hoping these issues will turn more into PR's as I become familiar with HyperMD, but I've found another weird bug that I'm not sure what the cause is:

HyperMD's Markdown Parser is based on CodeMirror's Markdown Mode.
Just confirmed that CodeMirror has the same problem. Demo Here.
You can submit this issue to CodeMirror

According to CommonMark Spec, this is expected behavior (see https://spec.commonmark.org/0.28/#example-52 )
You can add an empty line between a list and a normal paragraph.


Fixed issue #9713

Issue Reference
Fixed issue #9713

Checked and Found that VAT ID which was missing in the Admin Order Create form was added. Please check the Screenshots for reference.
Issue Screenshot -> https://prnt.sc/-MweVwOJmbMP
Fixed Screenshot -> https://scrsht.com/59004784


Azure NetApp Files support for Europe West?

Hi guys,
I can see a difference in region support listed on this page and others.
On this page Europe West is not on the list but on the vmware solution page it IS mentioned.
https://docs.microsoft.com/en-us/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts?tabs=azure-portal
Is ANF private preview for VMware available in Europe west?
Thanks,
Joost

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

ID: 64ddeca5-94ba-b6d4-dcf9-8f57c7ae2b1c
Version Independent ID: 7a8675b0-db25-47ac-51ef-3fee1230b1c6
Content: Attach Azure NetApp Files datastores to Azure VMware Solution hosts (Preview) - Azure VMware Solution
Content Source: articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md
Service: azure-vmware
GitHub Login: @suzizuber
Microsoft Alias: v-szuber

Hi @joostvandrenth thank you for pointing this out. It would be very helpful if you could list the other Azure docs that don't list Europe West in region support so I can look at them. Thanks for your help.

@joostvandrenth Can you please share the other document you are referring to in this feedback.

https://docs.microsoft.com/en-us/azure/azure-netapp-files/whats-new
Tx for picking this up 👍🏻
On Thu, 23 Jun 2022 at 18:33, Suzi Zuber @.***> wrote:

Hi @joostvandrenth https://github.com/joostvandrenth thank you for
pointing this out. It would be very helpful if you could list the other
Azure docs that don't list Europe West in region support so I can look at
them. Thanks for your help.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/94807#issuecomment-1164630627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZYRRLOTZXN2RWP4OSV6MT3VQSGXJANCNFSM5ZUNR3WA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@suzizuber
Document update is needed for below:

@suzizuber Thanks for the details.
I have opened a feedback item on the relevant page and have assigned it to @b-hchen as recommended.

@joostvandrenth Thanks for reporting this, I have opened a feedback to update the document on the relevant page here.
I am closing this thread as the document update is not applicable to this page.
Please follow this issue for further updated.


input switch transition

would be nice to add a simple transition to the checkmark switch like so:
.custom-switch input[type=checkbox]:checked~label:after,
.custom-switch input[type=checkbox]~label:after{
    transition: left .2s ease
}

it's really simple and makes it feel a LOT better

Thank you, I will test this out and see how it works.

@ThaUnknown This has been fixed in v1.1.1: https://www.gethalfmoon.com/docs/switch
Though I did change the transition speed slightly, the faster one just looked nicer to me. I will go ahead and close this issue. You can re-open it if you think the issue is still not resolved, or open another issue. Thank you.


upload_to_app_store should have a flag to not wait for build processing

Feature Request
Motivation Behind Feature

I am automating our ios delivery process, we have around 200 apps to build and submit. I used sidekiq for concurrency and have divided the process into 3 workers.

BuildAppWorker (this executes a lane which calls gym action and generates ipa)
UploadAppWorker (this executes a lane which calls upload_to_app_store action and uploads ipa + metadata + screenshot + rating + price tier)
SubmitAppWorker (this executes a lane which calls upload_to_app_store action and just submits the uploaded build for review)

The problem arises on step3, as upload_to_app_store waits for apple build processing to complete and that results in sidekiq worker to stay in progress.
By adding a flag like wait_for_build_processing (defaults to true), then it will make this action upload_to_app_store much more efficient for automation. Atleast I will just set that flag as false for my use case and things will work perfectly.
Feature Description

There should be a wait_for_build_processing flag in upload_to_app_store action, which should default to true for backward compatibility. This flag should do nothing if submit_for_review is false. If submit_for_review is true then this flag should decide if fastlane should wait for apple to complete the build processing or not.

This should not break anything for existing users.
Alternatives or Workarounds

I am currently implementing it, and it will be similar to submit_for_review.rb

I think only the select_build function should be modified, where it calls the wait_for_build we just need to ensure if flag is true, incase its false, then we should call find_build if the build is found then proceed, else fail.

@salmanasiddiqui Heyyy 👋 Quick question on your feature request. If wait_for_build_processing: false and submit_for_review: true and the build is not yet processed, are you expecting the action to fail?

Yes, I am expecting it to fail.

@salmanasiddiqui Cool cool, just wanted to make sure.  I will think about this one 🤔 I'm not sure if this should be built directly into upload_to_app_store since this seems kind of niche but this should also be possible for you to do with spaceship directly. I will look into both options and let you know what is best here. If its the spaceship option, I will give you example code that can do what you are looking for so you can put this into a custom lane or custom action of your own 👌

oh yes this can be done with spaceship and I know how I can do that, will do it once I get rid of other blockers i keep getting 😓  (you probably know as you have commented on other issues of mine)..
I was just thinking that it should be part of fastlane too, also I too think it should be a separate action than upload_to_app_store. And there should just be a comment in the documentation of upload_to_app_store | submit_for_review parameter, that

this will submit the app for review after waiting for it to be processed by apple, but it does not work 100% of the time. As sometimes builds take time to be visible on apple (and it won't return the recently uploaded build), while other times builds just stuck in processing and requires us to upload build with new build number.

@salmanasiddiqui We are trying to limit the addition of actions right now as its more of us to maintain but it does seem like this would be a better fit for an action 🤔 I will throw that into my thinking session as well of where this best fits 👍


Refactor splatfacto gaussian params with a ParameterDict

This simplifies subclassing, and simplifies some of the logic for culling/splitting.

The change looks good to me. Some suggestions:
(1) test PLY exporter end-to-end to safeguard the workflow is fine.
(2) since the change disallow loading checkpoint from previous versions. I would suggest we bump a major version number like (1.1.0) to distinguish from previous versions. User can still use earlier versions to view their assets.

One more thing: when rebasing on top of https://github.com/nerfstudio-project/nerfstudio/pull/2945 We need to change the parameter names for splatfacto-big.

This should be ready to merge, fixed all the mentioned changes and also added loading logic to make it backwards-compatible with old checkpoints.

LGTM! Can we merge this?


Android back button does not do navigator.pop() when using run_mojo

 Issue by aghassemi
Thursday Nov 05, 2015 at 23:28 GMT
Originally opened as https://github.com/flutter/engine/issues/1973

I am running my MaterialApp in Mojo so it is using Mojo Shell instead of Sky Shell. This difference seems to be causing back button to exit the app rather than poping from navigator.
@abarth @Hixie

 Comment by abarth
Thursday Nov 05, 2015 at 23:36 GMT

There's no back button integration in MojoShell on Android.

 Comment by abarth
Friday Nov 06, 2015 at 04:50 GMT

@jamesr @j9brown Who's the right person to handle feature requests for MojoShell on Android?

 Comment by jamesr
Monday Nov 09, 2015 at 20:20 GMT

@qsr is

@abarth Should  https://github.com/domokit/mojo/issues/361 get integrated with Flutter or should the app listen for that event and pop from nav?

@aghassemi It's the same code to write either way.  The simplest thing for the demo is to write the code in the app.

Thanks, SGTM.

I'm going to close this issue because the current plan is to do this in the slides app itself.