[UI/UX] Design the data explorer UI and UX

Data explorer Graphql UI
Acceptance Criteria

[x] I have a nice UX/UI so I can enjoy using the Data Explorer Done https://github.com/datopian/data-explorer-graphql/pull/39
[x] I can use the app without CSS so I can apply my own styles easily
[x] I can import CSS bundles from here if I'm fine with default styles

Tasks
UX:

[x] Brainstorm what should be improved

For example, I'm not sure if the way we hide/show filters/tables when data is fetching is great... eg, entire table gets removed and then appears again. As a user, I don't like it because content of the HTML page is also moved up and down and sometimes it's confusing especially when the DataExplorer is just a part of larger page.

[ ] Check table UX/UI in order to avoid reloading and resize window when click on submit @cotts

UI:

[x] Brainstorm / research different applications / projects in the web Done We will use ideas from the energi-net explorer, handson table and tabulator
[x] Create mockups
[x] Implement mockups @risenW Done https://github.com/datopian/data-explorer-graphql/pull/39

Analysis
Below some UI ideas:
Tabulator

http://tabulator.info/

Energinet

https://www.energidataservice.dk/tso-electricity/electricitysupplierspergridarea

National Grid
https://data.nationalgrideso.com/demand/14-days-ahead-wind-forecasts/r/14_days_ahead_wind_forecast

Open Data Denmark
https://www.opendata.dk/city-of-copenhagen/cykeldata

Open Data Montreal
https://donnees.montreal.ca/ville-de-montreal/requetes-entreprises-covid-19

Webix

Handson Table

Note that we have Tailwind setup in this project.

@risenW @cotts I've added more examples from existing projects. I'd also suggest exploring ideas outside of Datopian.

@risenW @cotts I've added more examples from existing projects. I'd also suggest exploring ideas outside of Datopian.

Yeah, I got some really nice one, will update the description.

WONTFIX.


PED2 dataset

I am not able to download ped2 dataset from the provided link: http://www.svcl.ucsd.edu/projects/anomaly/dataset.html
could you provide with the drive link for the dataset if possible?

I am not able to download ped2 dataset from the provided link: http://www.svcl.ucsd.edu/projects/anomaly/dataset.html could you provide with the drive link for the dataset if possible?

You can download it here: Ped2

Thankyou so much.
I also wanted to know with what fps you have split the training videos for shanghai and avenue into frames.

Thankyou so much. I also wanted to know with what fps you have split the training videos for shanghai and avenue into frames.

I follow the config from this site (link).

Can you provide drive links to shanghaiTech and CUHK avenue datasets as well?
Thankyou


KAFKA-15623: Migrate streams tests (part 1) module to JUnit 5

Migrate org.apache.kafka.streams.kstream to JUnit 5.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hi @chia7712, I addressed all comments. May you take a look? Thank you.


Added my Youtube Playlist and fixes CSS issue on Youtube Playlist sec…

Description

I have added my youtube playlist in HTML file.
FIxes some CSS issues on the youtube playlists cards list.

@VG-1
can you please add the label of #hacktoberfest to it.
So it will be counted as one of my PR there.


[BUG] Constant errors about io.rancher.longhorn-reg.sock

Describe the bug
I have several errors in kubelet log of every node, and it's the same that continues every X minutes:
I0527 14:47:10.544314   10814 reconciler.go:156] operationExecutor.RegisterPlugin started for plugin at "/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock" (plugin details: &{/var/lib/kubelet/plugins/io.rancher.longhorn-reg.socktrue 2020-03-21 22:46:57.40373808 +0000 UTC m=+21.619442778})
I0527 14:47:10.544409   10814 operation_generator.go:193] parsed scheme: ""
I0527 14:47:10.544427   10814 operation_generator.go:193] scheme "" not registered, fallback to default scheme
I0527 14:47:10.544452   10814 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock 0  <nil>}] <nil>}
I0527 14:47:10.544478   10814 clientconn.go:577] ClientConn switching balancer to "pick_first"
I0527 14:47:10.544581   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, CONNECTING
W0527 14:47:10.544781   10814 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...
I0527 14:47:10.544846   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, TRANSIENT_FAILURE
I0527 14:47:11.545032   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, CONNECTING
W0527 14:47:11.545080   10814 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...
I0527 14:47:11.545120   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, TRANSIENT_FAILURE
I0527 14:47:13.214754   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, CONNECTING
W0527 14:47:13.214799   10814 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...
I0527 14:47:13.214866   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, TRANSIENT_FAILURE
I0527 14:47:15.865668   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, CONNECTING
W0527 14:47:15.865765   10814 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...
I0527 14:47:15.865828   10814 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc001438790, TRANSIENT_FAILURE
W0527 14:47:17.528690   10814 kubelet_pods.go:849] Unable to retrieve pull secret longhorn-system/ for longhorn-system/longhorn-csi-plugin-9mrj8 due to secret "" not found.  The image pull may not succeed.
E0527 14:47:20.544545   10814 goroutinemap.go:150] Operation for "/var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock" failed. No retries permitted until 2020-05-27 14:49:22.544513867 +0000 UTC m=+5760166.760218627 (durationBeforeRetry 2m2s). Error: "RegisterPlugin error -- dial failed at socket /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock, err: failed to dial socket /var/lib/kubelet/plugins/io.rancher.longhorn-reg.sock, err: context deadline exceeded"

To Reproduce
I have two clusters but this error happens only on one of them.
It's a RKE cluster, on 3 bare metal servers.
The error is logged in all nodes.
I already tried to remove longhorn with also manual remove of CRDs but the error PERSISTS also after remove longhorn.
So I tried to install again (last version) and the error continues.
Expected behavior
No errors in kubelet logs.
Environment:

Longhorn version: 0.8.1 (the same with 0.7.0)
Kubernetes version: 1.16.6
Node OS type and version: Ubuntu 18.04

@Leen15 This should be fixed in v1.0.0 when we removed compatible CSI plugin #1365 .  @boknowswiki Can you check if this still happens for the master branch now?

@yasker
Tried two ways to find the error messages:

Logged into all three nodes, and goto /var/log directories, run rep "io.rancher.longhorn-reg.sock" -r *, nothing returned.
Run docker logs <kubelet docker id> | grep "io.rancher.longhorn-reg.sock", don't see the same error message, but found one interesting message, but I think it's from 5/22/2020, please help to confirm.

I0522 01:29:49.955216    9802 handlers.go:66] Exec lifecycle hook ([/bin/sh -c rm -rf /registration/driver.longhorn.io /registration/driver.longhorn.io-reg.sock /csi//*]) for Container "node-driver-registrar" in Pod "longhorn-csi-plugin-424n9_longhorn-system(e3667b35-3627-4af8-bd1a-4e75ad03931d)" failed - error: command '/bin/sh -c rm -rf /registration/driver.longhorn.io /registration/driver.longhorn.io-reg.sock /csi//*' exited with 126: , message: "OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused \"exec: \\\"/bin/sh\\\": stat /bin/sh: no such file or directory\": unknown\r\n"
Thanks.

@boknowswiki the second error message should be something else. Are you able to reproduce the issue on v0.8.1?

@yasker , I just found this error message, I can see the issue on my testbed now.
W0527 18:11:26.910365    1113 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...

@boknowswiki which version you're using? If it's v1.0.0-rc2, can you restart the node/kubelet, to see if it disappears? Since kubelet might keep some internal states in the memory.

@yasker I am using latest master images. I did kubectl delete -f <manager and driver yaml>, and apply them back. Let me try v1.0.0-rc2.

@yasker
Steps I did:

Uninstall longhorn and make sure nothing left.
Restart all my worker nodes.
Install longhorn v1.0.0-rc2.

I can see the same error message:
W0527 20:37:19.600693    1093 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock: connect: connection refused". Reconnecting...

@boknowswiki There is a host directory leftover by the previous driver, located at /var/lib/kubelet/plugins/io.rancher.longhorn. Can you try to remove it and see if it helps?

Found it at /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock, and after I remove it, the error message is gone with the message in kubelet log:
I0527 22:35:53.677564    1093 plugin_watcher.go:212] Removing socket path /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock from desired state cache

@Leen15 According to what we have discussed above, you should be able to remove /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock from the node to stop kubelet from complaining about this obsolete domain socket.

Hi @yasker , I see two sock in plugins_registry:
driver.longhorn.io-reg.sock
io.rancher.longhorn-reg.sock

can I safely remove io.rancher.longhorn-reg.sock from all nodes keeping longhorn 0.8.1 running?

@Leen15 After making sure you have no PV with driver io.rancher.longhorn (see the instruction here), you can safely remove io.rancher.longhorn-reg.sock

I removed the sock in both plugins and plugins_registry directories but it continues:
onBeforeRetry 2m2s). Error: "UnregisterPlugin error -- dial failed at socket /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock, err: failed to dial socket /var/lib/kubelet/plugins_registry/io.rancher.longhorn-reg.sock, err: context deadline exceeded"
I0529 07:43:42.201933    3034 reconciler.go:139] operationExecutor.UnregisterPlugin started for plugin at "/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock" (plugin details: &{/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock false 2020-05-27 14:31:10.934280222 +0000 UTC m=+3389191.734068089})
I0529 07:43:42.202053    3034 operation_generator.go:193] parsed scheme: ""
I0529 07:43:42.202089    3034 operation_generator.go:193] scheme "" not registered, fallback to default scheme
I0529 07:43:42.202133    3034 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}] <nil>}
I0529 07:43:42.202165    3034 clientconn.go:577] ClientConn switching balancer to "pick_first"
I0529 07:43:42.202277    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, CONNECTING
W0529 07:43:42.202486    3034 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock: connect: no such file or directory". Reconnecting...
I0529 07:43:42.202543    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, TRANSIENT_FAILURE
I0529 07:43:42.231889    3034 kubelet_network_linux.go:111] Not using `--random-fully` in the MASQUERADE rule for iptables because the local version of iptables does not support it
I0529 07:43:43.202847    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, CONNECTING
W0529 07:43:43.202877    3034 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock: connect: no such file or directory". Reconnecting...
I0529 07:43:43.202938    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, TRANSIENT_FAILURE
I0529 07:43:44.724684    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, CONNECTING
W0529 07:43:44.724752    3034 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock: connect: no such file or directory". Reconnecting...
I0529 07:43:44.724831    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, TRANSIENT_FAILURE
I0529 07:43:46.965593    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, CONNECTING
W0529 07:43:46.965682    3034 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock: connect: no such file or directory". Reconnecting...
I0529 07:43:46.965763    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, TRANSIENT_FAILURE
I0529 07:43:51.642421    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, CONNECTING
W0529 07:43:51.642450    3034 clientconn.go:1120] grpc: addrConn.createTransport failed to connect to {/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock 0  <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock: connect: no such file or directory". Reconnecting...
I0529 07:43:51.642472    3034 balancer_conn_wrappers.go:127] pickfirstBalancer: HandleSubConnStateChange: 0xc00187b2a0, TRANSIENT_FAILURE
E0529 07:43:52.202279    3034 goroutinemap.go:150] Operation for "/var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock" failed. No retries permitted until 2020-05-29 07:45:54.20222555 +0000 UTC m=+3537675.002013581 (durationBeforeRetry 2m2s). Error: "UnregisterPlugin error -- dial failed at socket /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock, err: failed to dial socket /var/lib/kubelet/plugins_registry/driver.longhorn.io-reg.sock, err:context deadline exceeded"

@boknowswiki Do we need to do anything after removing the Unix domain socket? e.g. restart kubelet. Or Kubelet will automatically pick it up?

@yasker , No, after I delete the io.rancher.longhorn-reg.sock socket, the error message went away. And I just logged in my node, and I haven't see the error message so far, it's been more than 10 mins now.
Another thing is I did received the email about @Leen15 reporting the issue again, but I don't see the comment here.

@Leen15 , could you help to confirm if you still see the error message after removing io.rancher.longhorn-reg.sock socket? Thanks.

Hi @boknowswiki , I first reported the issue again, but then after removed the sock from the plugins folder too, and restarted the kubelet, I didn't see the error anymore.
I don't know if one of these two things did the magic, but now It works.

@Leen15 , thanks for your confirm, and good to hear the issue is gone for you.

@boknowswiki Can you please point me to the doc link? I couldn't found it here https://staging.longhorn.io/docs/0.8.1/deploy/upgrade/longhorn-manager/#migration-failure-handling
and
https://longhorn.io/docs/0.8.1/deploy/upgrade/longhorn-manager/#migration-failure-handling

Followed the instructions from https://longhorn.io/docs/1.0.0/deploy/upgrade/longhorn-manager/#cleanup-for-compatible-csi-plugin, the logs of error message related to io.rancher.longhorn-reg. disappear.
To repro the issue, tried steps from https://github.com/longhorn/longhorn/issues/1412#issuecomment-634927383

@khushboo-rancher Thanks a lot, this doc really help me.


Due Dates

Hello,
I'm curious if there is the concept of Due date in the BuJo todo items?
I like to capture todo items as they occur to me then optionally put in a Due date if there is a deadline.
Can this be done in BuJo?

Not as far as I know. I'm using it in combination with Dendron, where tasks have a due date functionality. Though it is not that polished yet.


merge from arlac77/npm-package-template-esm-only

package.json

chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): add sideEffects from template

Codecov Report

Merging #657 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #657   +/-   ##
=======================================
  Coverage   58.42%   58.42%
=======================================
  Files           2        2
  Lines          89       89
  Branches       11       11
=======================================
  Hits           52       52
  Misses         37       37

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c1572e4...84116f9. Read the comment docs.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[improve][admin] Not allow to terminate system topic.

Fixes #15891
Master Issue: #15891
Motivation
Pulsar-manager could see all the topics including the system topic and can terminate them.  If terminates system topic by mistake, there would cause many serious problems.  So it's better not allow to terminate the system topic.
Documentation

[x] doc-not-needed
(Please explain why)

What about terminating the partitioned topic?

Not allowed. The logic is here
https://github.com/apache/pulsar/blob/e1c0ad395c19c99369e733f44a2426de5c465787/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/PersistentTopicsBase.java#L3686-L3691


[BUG] tailwind plugin prose not supported

Describe the bug
When applied 2 classes from @tailwindcss/typography like prose-red prose-xl error tailwindcss/no-contradicting-classname throws
To Reproduce
Steps to reproduce the behavior:

Add tailwind plugin https://tailwindcss.com/docs/typography-plugin
Apply class prose-red prose-xl
Observe error

Expected behavior
No error
eslint config file or live demo

Hi @dmtrKovalenko, indeed the plugin has been updated and at the moment the classnames from the official plugins are not generated dynamically but I'm working on it. I'll keep you posted.

Hi @dmtrKovalenko, please give a try to this beta version:
npm i -D<EMAIL_ADDRESS>

I just published a beta version with the fixes listed on #132
https://github.com/francoismassart/eslint-plugin-tailwindcss/tree/fix/no-custom-classname-plugin-support#readme
npm i<EMAIL_ADDRESS>Please give it a try and provide feedback and or issues 👍
Thank you

@dmtrKovalenko when you get a chance please try the latest beta and give me feedback about your issue.


Create a page for LSP1 Type IDs

What does this PR introduce?
In this PR we create a page that contains all the LSP1 Type IDs

Task linked: DEV-8623 Add Type IDs list to the docs.lukso.tech

Task linked: DEV-8623 Add Type IDs list to the docs.lukso.tech

Task linked: DEV-8623 Add Type IDs list to the docs.lukso.tech


Fixed apiKey plural CRD

Plural name of apikeys wrong

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
d033ea0c6d9ed62f0a597573135963eafefff485
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simple

/test istio-pilot-e2e

/retest

@andraxylia circleci doesn't understand "/retest"

/lgtm

/lgtm

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
d033ea0c6d9ed62f0a597573135963eafefff485
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-smoke

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
d033ea0c6d9ed62f0a597573135963eafefff485
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-smoke

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
d033ea0c6d9ed62f0a597573135963eafefff485
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-smoke

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
d033ea0c6d9ed62f0a597573135963eafefff485
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

circleci e2e-simple fails because of #3344

istio-pilot-e2e fails in http reachability for auth enable could be #3139


How about using fmoviesz.to as a source and maybe adding a auto next and auto play feature

Same as title

fmoviesz appears to use VidSrc for media which we scrape already.
I will look into autoplay.

Autoplay added with the latest commit to v2.7.


IE7 error

The readme states "There are currently no known unsupported browsers".
I'm testing in IE7 (via https://app.crossbrowsertesting.com/ ), and it reports a "runtime error", pointing to picturefill.min.js line 5.

This is my code:
<img width="278"<EMAIL_ADDRESS>1x<EMAIL_ADDRESS>2x"/>
(No src attribute on the img tag as recommended in the picturefill readme.)
There's no image shown :|

It's OK in IE8, I guess I'll forget about IE7, it being at version 11, and there's Edge already ..

See:
https://github.com/scottjehl/picturefill/blob/3.0/index.html#L261


[SPARK-43772][BUILD][CONNECT] Move version configuration in connect module to parent

What changes were proposed in this pull request?
The pr aims to move version configuration in connect module to parent.
Why are the changes needed?
For better management and post maintenance, eg: upgrading some library version of a module while forgetting another one.
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Pass GA.
Manually test
sh build/sbt "connect/testOnly org.apache.spark.sql.connect.artifact.ArtifactManagerSuite"
sh build/sbt "connect/testOnly org.apache.spark.sql.connect.planner.SparkConnectServiceSuite"
sh build/sbt "connect/testOnly org.apache.spark.sql.connect.service.InterceptorRegistrySuite"

@zhenlineo @vicennial @LuciferYang this is ready for review.

@panbingkun please help confirm if the content of the shaded/assembly jar?

@panbingkun please help confirm if the content of the shaded/assembly jar?

The check process is as follows:
1.command: ./build/sbt connect/assembly
2.Before patch:

3.After patch:

1.command: ./build/sbt connect-client-jvm/assembly
2.Before patch:

3.After patch:

About maven:
1.command: ./build/mvn -pl :spark-connect-client-jvm_2.12 -pl :spark-connect_2.12 -Phadoop-3 -Phive-2.3 -Pyarn -Phive-thriftserver -Phive -DskipTests clean package
2.Before:

3.After:

4.Diff

1.Before

2.After

3.Diff

Merged to master. Thanks @panbingkun @zhenlineo


Created a WPF application for the UI and an engine for the homebrew listing, downloading etc.

First of all, great project, keep up the good work.
Second of all, sorry for the huge commit, I should have done better about that.
With this PR, I actually wanted to improve this project and maybe hopefully improve your coding style.
Please don't get me wrong, I'm doing this with good intentions and nothing more.
Hope to see you get better with your craft :)

Nice.
Thank you

Well, thanks for the merge 👍 I guess now I can update the readme file with new descriptions and new screenshots. It also means there would be a new release too. Could we arrange that with you on this repo or would I have to make those changes and create a new PR?

We can continue here, as soon as I get home I'm going to compile and test, can we talk on twitter or other means of communication? ?

I don't have a twitter but we can talk through mail. My mail address is<EMAIL_ADDRESS>From there we can switch to something else if you want.


Standardize code blocks

Wrap in figure, with figcaption, then pre
Add SCSS language labels to Examples

@wardpenney 👏  👏  👏


Stop using globs for chokidar watchers

Description
chokidar v4 removed support for file globs in it's watchers. This restructures how we choose what files to watch to use the new API. The functionality of the local server should not have changed so please confirm this.
The new system recursively watches files if given a directory path so the old file/path/**/* pattern is exactly the same as file/path in the new system.
The new system relies much more on the ignored option to filter out files that you don't want it to watch. This creates a bit of separation between the list of files we want and files we don't want which means we can't just set one array of globs at the top of the file anymore.

Issue number and link
Fixes #12241

Testing plan

Run the local server npm start

Optionally add a console.log statement in each of the 3 watcher.on() handlers to confirm when they fire

Check that each of the following events triggers a re-build as expected in the directories we specify, like Source and Specs

Create a file (touch test.js)
Delete a file (rm test.js)
Modify a file (save in vscode)

Check that the watchers are not triggered for those events in directories we want ignored
Verify everything on localhost actually still works as expected

Author checklist

[ ] I have submitted a Contributor License Agreement
[ ] I have added my name to CONTRIBUTORS.md
[ ] I have updated CHANGES.md with a short summary of my change
[ ] I have added or updated unit tests to ensure consistent code coverage
[ ] I have updated the inline documentation, and included code examples where relevant
[ ] I have performed a self-review of my code

Check that each of the following events triggers a re-build as expected in the directories we specify, like Source and Specs
Create a file (touch test.js)

Is this supposed to work?
When adding a CartesianX.js, it bails out with
X [ERROR] No matching export in "packages/engine/index.js" for import "CartesianX"

    Source/Cesium.js:221:9:
      221 │ export { CartesianX } from '@cesium/engine';
          │          ~~~~~~~~~~
          ╵          Cartesian4

  Did you mean to import "Cartesian4" instead?

    packages/engine/index.js:171:9:
      171 │ export { default as Cartesian4 } from './Source/Core/Cartesian4.js';
          ╵          ~~~~~~~

1 error
Error: Build failed with 1 error:
Source/Cesium.js:221:9: ERROR: No matching export in "packages/engine/index.js" for import "CartesianX"

(similarly, when restarting and then deleting it, this also causes an error)
but...
the same happens for me with "chokidar": "^3.5.3",, so ... I think that this may never have worked?
I'm rarely adding/removing files. And I think that it happens rarely enough in general to not consider this as an issue.

The main poins:

Modify a file (save in vscode)

I tried it out with modifications in a source file, and this worked and was picked up properly.
(I can do additional tests with shaders, but there, https://github.com/CesiumGS/cesium/issues/12164 might interfere...)

Check that the watchers are not triggered for those events in directories we want ignored

I added/deleted a file in one of the ignored source directories, and this was ignored.

Verify everything on localhost actually still works as expected

"Everything" is a bit too much for me to verify right now 😄 but I didn't see any issues.

Check that each of the following events triggers a re-build as expected in the directories we specify, like Source and Specs
Create a file (touch test.js)

Is this supposed to work?

When adding a CartesianX.js, it bails out with

This doesn't (and didn't even before the chokidar version update) because we are only calling createCesiumJs. It updates the top-level Source/Cesium.js file, but not the individual package/*/index.js files. We need to also call createIndexJs for the relevant workspace.
It a small change that I'll make now.

Thanks @jjspace and @jjspace!


enable multi-threading in onnx-mlir

Enable the multi-threading in onnx-mlir by utilizing OpenMP.  Tested on x86 with performance gain.
Introduced a new operator in krnl dialect: krnl.parallel which takes a loop as input to specify the loop will be parallelized.
To parallelization is enabled with the argument --parallel in onnx-mlir and  --convert-onnx-to-krnl=enable-parallel in onnx-mlir-opt.
To parallel an operator while lowering, you can follow the attached example below:
ValueRange loopDef = create.krnl.defineLoops(outputRank);
SmallVector<IndexExpr, 4> lbs(outputRank, LiteralIndexExpr(0));
SmallVector<IndexExpr, 4> ubs;
+ create.krnl.parallel(loopDef[0]) // parallelize the outermost loop
create.krnl.iterateIE(loopDef, loopDef, lbs, ubs,
          [&](KrnlBuilder &createKrnl, ValueRange loopInd) {
      ...
}

To run your model with parallelization, please build your MLIR along with OpenMP with following code and set the dependency with export LD_PRELOAD=../llvm-project/build/lib/libomp.so.
+ DLLVM_ENABLE_PROJECTS="mlir;openmp;clang"
- DLLVM_ENABLE_PROJECTS="mlir"

The parallelization is done by transforming the affine.forOp to affine.parallelOp this happens in the Pass:  convert-krnl-to-affine. krnl.parallel is interpreted after krnl.defineloop, krnl.iterate, krnl.block, krnl.permute and krnl.unroll. The further lowering will be handled by convert-scf-to-openmp and convert-openmp-to-llvm automatically.
Current parallelized operators (outermost loop):

[x] Elementwise Operator
[x] GEMM
[x] MatMul
[x] Transpose
[x] Softmax
[x] Reduction
[x] Concat

Signed-off-by: @lixi-zhou
Co-authored-by:  @AlexandreEichenberger

@lixi-zhou
The errors in the build occurs in Release mode; in your test env, change / add this I believe. -DCMAKE_BUILD_TYPE=Release. Default (without it) is debug

@jenkins-droid  test this please

Closed the current PR and created a new one, #2435, to continue the code review discussion because of a weird failure on Jenkins CI.

continued as #2435


Fix clippy::derive_partial_eq_without_eq in generated gRPC test code

Motivation
tonic's generated code causes clippy::derive_partial_eq_without_eq warnings, but Zebra's CI requires our test builds to have no clippy warnings.
The tonic developers removed clippy from their CI, so we have to fix it ourselves. (The standard approach is to silence clippy warnings in generated code.)
Solution
Since the lightwalletd gRPC types can all be compared for total equality, we can tell tonic to derive Eq for all those types.
Review
This is critical priority because it is stopping other PRs merging.
Reviewer Checklist

[x] Clippy CI passes

Test beta on ubuntu-latest hit an IoError(Custom { kind: Other, error: "sapling-spend.params failed but the same step on Test stable on ubuntu-latest succeeded and a minor rustc update should be irrelevant to this change.

Alfredo and I were just talking about that, it's weird that it only happens on beta Rust. It might be a performance issue.
I'll open a ticket with more logging, and turning on performance optimisations for the download crates.

Looks good to me if there's no chance lightwalletd gRPC types might use floats or complex collections in the future.

If we try to add something incompatible with Eq to our gRPC types, our tests will fail on that PR. Then we can go chat to the lightwalletd developers about why it was added.

I admin-merged this PR because it's low risk, and multiple CI failures are blocking Mergify.


feat: use "terraform output" for documentation instead of local_file

This change results in a better git-enabled workflow because we more cleanly separate sources (kit modules, platform modules) from outputs. It also enables building docs in a separate CI build job that e.g. only has access to TF states but does not need to execute a local "foundation deploy" to make sure output_md files exist and are up to date.

I cleaned up one hack I added earlier on output_md_file inputs.

perfect, missed that. Thanks a lot!


Update supported GHC versions

Changes:

Update GHC versions in Github workflow
Update resolver

@JoseLion Could you please take a look?


[Fix] no-unused-prop-types: false positive with callback

Fixes #2350
This pr fixes getParentStatelessComponent when the current traversed node is like a callback (is a function and is an argument). The function getParentStatelessComponent is revised to use a more whitelist-ish approach.
Fixes false positive like:
function Foo(props) {
  useEffect(() => {
    const { a } = props;
    document.title = a;
  });

  return <p/>;
}
  Foo.propTypes = {
  a: PropTypes.string,
}

The tests are broken by the merge of #2184, which added a test case: https://github.com/yannickcr/eslint-plugin-react/blob/7bc55ccb6ed2c32d381f09d2f43a77ca60afaae3/tests/lib/rules/no-multi-comp.js#L345-L349
Do we want to support components defined in comma operator? (IMO, no.)

Yes, we should support components in any expression position.


[SDP-1100] Default tenant endpoint

This PR adds the default tenant endpoint that sets a tenant as the default in the system.

Preview is available here:http://developers-pr446.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr446.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr446.previews.kube001.services.stellar-ops.com

This PR is being closed in favor of https://github.com/stellar/stellar-docs/pull/455


Fix Helm values.yaml for internal and external ingress-nginx Helm chart

We are using https://kubernetes.github.io/ingress-nginx helm chart to deploy ingress-nginx. But it seems the values.yaml used is for different chart. This commit updates the values.yaml file of internal and external ingress-nginx helm chart used for the deployment.

Additionally, it specifies the MetalLB annotation to use the external metallb IP address pool for the external ingress service.

I can see that we are using separate instance of ingress-nginx for Grafana. Instead we can reuse external ingress(from "ingress-nginx" namespace) for the same.

I can see that we are using separate instance of ingress-nginx for Grafana. Instead we can reuse external ingress(from "ingress-nginx" namespace) for the same.

Please done fix that. We need to remove that ingress controller.


Colored mesh

How can I create a .ply file with colored mesh?

How can I create a .ply file with colored mesh?

Hi, as what I know, there is no such colored mesh. The color result images are all from the MLP rendering.


Add IsAvailable property

Provides an easy way to check if we're running in a GitHub Action workflow (as compared to debugging an application on a desktop machine)
Fixes #10

@all-contributors please add @flcdrg for issues and code.


elasticsearch cluster

ref #1063

elasticsearch and kibana 5.3.2
elasticsearch cluster

how to test:
$ hack/dev
...
# if you have jq, if not, parse the json output and ask yourself why you haven't install jq yet!
$ docker exec m1 docker run --rm --network ampnet appcelerator/alpine:3.5.2 curl elasticsearch:9200/_cluster/state | jq '.nodes | length'
3

Lol, well, you can also ask why you don't just containerize everything since you can pipe to jq in a container. Since we install it in our gotools image, which amptools is based on, you can also just do this:
$ alias jq="docker run -i --rm appcelerator/amptools jq"
$ docker exec m1 docker run --rm --network ampnet appcelerator/alpine:3.5.2 curl elasticsearch:9200/_cluster/state | jq '.nodes | length'
Why use a package manager when you have Docker? Containerize all the things! :p

@ndegory ^^ although I should mention we might want to update gotools since the jq version is still jq-1.4-1-e73951f and I believe 1.5 is the latest...


Fully-automate development setup with Gitpod

Hi just! 👋
This tweet https://twitter.com/justjs14/status/1417631887456100354 caught my eye. Here is a PR that fully automates the dev setup of just with Gitpod, providing anyone with a pre-built, browser-based development environment in one click:

What it does

Comes with all dependencies pre-installed
Runs make clean runtime ahead-of-time (so you don't need to wait)
Gives anyone immediate access to the pre-compiled just CLI

I hope this can make life easier for contributors, and for maintainers who need to review many PRs (hint: you can already open this PR in Gitpod to easily review & test it without messing up your local checkout).

Nice work geoffrey. gitpod is pretty impressive. will have to do some digging into the various pieces of their system.


feat: runtime-support for type unions in props

One of the last missing features regarding TypeScript support in Vue is the ability to use discriminated- and distributive union types in props with runtime validation. This PR aims to address these limitations and provides a more flexible way to define props.
Fixes

https://github.com/vuejs/core/issues/11758
https://github.com/vuejs/core/issues/8952
https://github.com/vuejs/core/issues/9125
https://github.com/vuejs/core/issues/12106

Implementation
Through compiling and validating the new internal prop option union, we can skip validation for props that are not part of an active sub-union.
In the following example, a and b are in an active sub-union, c and d are not. Defining either a or b should trigger warnings for missing props for the other prop in the same sub-union.
defineProps<
  | {
      a: string
      b: number
    }
  | {
      c: string
      d: number
    }
>()

// Usage
<Comp a="foo" /> // Should trigger missing required prop warning only for `b`

Limitations

[x]  Requires https://github.com/vuejs/core/pull/12077 for union type-safety.

Mentions
Shoutout to @KazariEX for helping me navigating various intricacies of the prop type system.

I would like to cherry-pick both this and https://github.com/vuejs/core/pull/12108 but I get conflicts in https://github.com/vuejs/core/pull/12108/commits/d09f791e47bb6cfabf5235b87199b14e5ed74b40#diff-ddb3174016350dd4464764b4a1ba232d09ad1e75164d4a37758c759d019202e4
How would you solve it in the context of the other PR?

@edison1105 my PR contains an improvement to inferring props in combination with withDefaults. Any recommendation on how we can resolve this conflict? I need to investigate if my PR already resolves #12108. I'd be open to extract it from my PR to make it more atomic.

Thanks. I would like to test this in my codebase, could you please share how am I supposed to pack it?
I've rebased your branch against main to be sure to include https://github.com/vuejs/core/pull/12077
Then I've run pnpm install && pnpm run build && pnpm run release --skipGit --skipTests
I didn't find a way to pack all packages at once, so I've gone into each workspace and I've run pnpm pack, copied the tarball into my project and added the following:
  "resolutions": {
    "@vue/runtime-core": "file:./packages/vue-runtime-core-3.5.12.tgz",
    "@vue/compiler-sfc": "file:./packages/vue-compiler-sfc-3.5.12.tgz",
    "@vue/reactivity": "file:./packages/vue-reactivity-3.5.12.tgz",
    "@vue/shared": "file:./packages/vue-shared-3.5.12.tgz",
    "@vue/compiler-core": "file:./packages/vue-compiler-core-3.5.12.tgz",
    "@vue/compiler-dom": "file:./packages/vue-compiler-dom-3.5.12.tgz",
    "@vue/compiler-ssr": "file:./packages/vue-compiler-ssr-3.5.12.tgz"
  },

Unfortunately I get some errors when trying to import some types:

For every commit/PR in this repo, a package is released on pkg.pr.new. You can use the published package like this:
pnpm add https://pkg.pr.new/vue@12059
In this case, 12059 points to the current PR.

But this PR doesn't include https://github.com/vuejs/core/pull/12077 which according to the description is needed. Could you please rebase against latest main so that a new package gets released? Thanks

Unfortunately I'm still seeing runtime warnings.
This is my component with union props called InfoCard:

This is the parent component which makes use of it:

And this is the warning in the console:

I've tried removing withDefaults and I'm still getting the same issue.
These are the yarn resolutions in order to use the packages from this PR:
   "resolutions": {
-    "@vue/language-core": "file:./packages/vue-language-core-2.1.7-alpha.0.tgz"
+    "@vue/language-core": "file:./packages/vue-language-core-2.1.7-alpha.0.tgz",
+    "@vue/runtime-core": "https://pkg.pr.new/@vue/runtime-core@12059",
+    "@vue/compiler-sfc": "https://pkg.pr.new/@vue/compiler-sfc@12059",
+    "@vue/reactivity": "https://pkg.pr.new/@vue/reactivity@12059",
+    "@vue/shared": "https://pkg.pr.new/@vue/shared@12059",
+    "@vue/compiler-core": "https://pkg.pr.new/@vue/compiler-core@12059",
+    "@vue/compiler-dom": "https://pkg.pr.new/@vue/compiler-dom@12059",
+    "@vue/compiler-ssr": "https://pkg.pr.new/@vue/compiler-ssr@12059"
   },

Hey, thanks for your input. This is currently a limitation indeed. So how it works is that we need to be able to clearly distinguish between different union members. The following would work because of the distributively defined attribute hasChart. If you include hasChart in a base type that all union members inherit from, it's a bit tricky to resolve the union at runtime. I'll see if we can resolve this issue in an easy way. Otherwise we'll need some form of documentation that addresses such use-cases.
export interface NumberCard {
  type: 'number'
  value: number
}

export interface FractionCard {
  type: 'fraction'
  value: {numerator: number; denominator: number}
}

export interface NoValueCard {
  hasChart: true
  chartOption: 'bar' | 'line'
}

export type Card = NumberCard | FractionCard | NoValueCard

Why wouldn't you be able to discriminate? hasChart is an union by itself (true | false) and if you have it as true the only viable option between NumberCard | FractionCard | NoValueCard is NoValueCard:

As you can see Typescript gets it right.

It looks like this needs to be rebased now that https://github.com/vuejs/core/pull/12108 got merged.


Experiment splitting loop in data no data

experiment failed could not get it as fast, and still slower on i5.
hard to get unescape and escaped flow fast.


Add slideTo to Carousel settings

[X] I have searched the Issues to see if this bug has already been reported
[X] I have tested the latest version

Summary
Just like we have in the default Flowbite (https://flowbite.com/docs/components/carousel/#methods), i'd like to set the current slide in a event. I don't know how to achieve it using the flowbite-react Carousel.
Context
I'm trying to sync two carousels to set same indexes at same time. One is in a modal, and other is outside.

Thank you! You can do this manually by clicking the desired indicator but, yeah, there's no way to set it programmatically. That could be useful and, like you point out, it's in vanilla so we should have it.

This is a duplicate of #1094, though


Implicit flow unsafe disclaimer

Would it make sense to add a disclaimer at the top of the page that implicit flow is not recommended?
I realize that it's written just a few lines below that the recommended approach is Authorization Code with PKCE, but it should be highlighted a bit more as this approach is pretty much deprecated.

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

ID: 9fa063fd-3b2d-e00d-c382-9ca749254616
Version Independent ID: 217e50e6-f9ed-d4ad-1d6a-04fbc87aaa4b
Content: Single-page sign-in using implicit flow - Azure AD B2C
Content Source: articles/active-directory-b2c/implicit-flow-single-page-application.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@FrankDrebin893  Thank you for your feedback . We will investigate and update the thread.

@FrankDrebin893 Thanks for the feedback. I have updated the document with detailed description and sent for review to the author. Once request has been approved, changes will be reflect in the document.


adding ARM release  as a workaround

Signed-off-by: Gustavo Carvalho<EMAIL_ADDRESS>

@moolen @knelasevero @IdanAdar This is a quick fix to allow using the current workflow to release boringssl images.
I guess a proper fix would involve changing tha Makefile jq syntax to something like [.manifests, .config] | select( . != null) | .[].digest but we would need to test how the promotion process would actually work.

/approve

nvm - I had to properly fix it anyways to allow the pipeline to pass :/


Create a Promise implementation that uses underlying JS Promises to interop with JS and CompletableDeferred on the rest of the targets

@lemkoleg

Hello, Carlos.
I am trying to create a promise this way and causing errors in JS. Am I
doing something wrong?
suspend fun promise(time: Long): Promise{
val del = TimeSpan(100.0)
return GlobalScope.launch {
while (!isAwaited && time > DateTime.nowUnixLong()) {
delay(del)
}}.toPromise()
}

If I do this,
I get a compiler warning about the inability to use the osuspend function
suspend fun promise(time: Long): Promise{
val del = TimeSpan(100.0)
return Promise { _, _ ->  while (!isAwaited && time >
DateTime.nowUnixLong()) {
delay(del)    \Suspension functions can be called only within
coroutine body
}}
}
вт, 5 мая 2020 г. в 19:33, Олег Лемко<EMAIL_ADDRESS>
Hello, Carlos.
I am trying to create a promise this way and causing errors in JS. Am I
doing something wrong?
suspend fun promise(time: Long): Promise{
val del = TimeSpan(100.0)
return GlobalScope.launch {
while (!isAwaited && time > DateTime.nowUnixLong()) {
delay(del)
}}.toPromise()
}

If you plan to call it from JS, remove the suspend modifier and do not use Long. I provided two .toPromise() one without parameters and suspend and other with a CoroutineContext not being suspend.
Use the variant from the first comment, remove suspend, replace Long with Double in the signature then replace delay(del) with delay(del.toLong())  and change toPromise() with toPromise(EmptyCoroutineContext)

Earned! Thank you very much, Carlos. I understand that most likely
this is not possible, but it may be possible to call Promise.await ()
in JS?
вт, 5 мая 2020 г. в 19:50, Carlos Ballesteros Velasco <
<EMAIL_ADDRESS>
If you plan to call it from JS, remove the suspend modifier and do not
use Long. I provided two .toPromise() one without parameters and suspend
and other with a CoroutineContext not being suspend.
Use the variant from the first comment, remove suspend, replace Long with
Double in the signature then replace delay(del) with delay(del.toLong())
and change toPromise() with toPromise(EmptyCoroutineContext)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/korlibs/korio/pull/68#issuecomment-624172046, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7Z3NZWCWJK6K6XG4HMV53RQA7V7ANCNFSM4MZBAU7Q
.

Yes, it is possible:
JS code:
async function jsFunction(){
    await promise(10)
}

Thank you, Carlos.
вт, 5 мая 2020 г., 20:32 Carlos Ballesteros Velasco <
<EMAIL_ADDRESS>
Yes, it is possible:
JS code:
async function jsFunction(){
await promise(10)
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/korlibs/korio/pull/68#issuecomment-624199167, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7Z3N5SGUUXADRU3GWZ47LRQBESHANCNFSM4MZBAU7Q
.

I meant using .await in common module
вт, 5 мая 2020 г. в 20:32, Carlos Ballesteros Velasco <
<EMAIL_ADDRESS>
Yes, it is possible:
JS code:
async function jsFunction(){
await promise(10)
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/korlibs/korio/pull/68#issuecomment-624199167, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7Z3N5SGUUXADRU3GWZ47LRQBESHANCNFSM4MZBAU7Q
.

Tell me Carlos. I have a background process that checks for new
responses in the input message queue (WebSocket puts them in the
queue) and their parsing.
Should I use Worker for this? As far as I know, Workers cannot
use global objects (the queue is a global object). This is true?
вт, 5 мая 2020 г. в 20:32, Carlos Ballesteros Velasco <
<EMAIL_ADDRESS>
Yes, it is possible:
JS code:
async function jsFunction(){
await promise(10)
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/korlibs/korio/pull/68#issuecomment-624199167, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7Z3N5SGUUXADRU3GWZ47LRQBESHANCNFSM4MZBAU7Q
.

Hey @lemkoleg this is GitHub issues and some people is subscribed and get emails for each comment, this channel is for reporting bugs and feature requests. If you want support, I'd suggest you to use slack. You can ask here and we will try to help you: https://slack.soywiz.com/
Best regards

Forgive me.  I thought our correspondence was personal
вт, 5 мая 2020 г., 22:53 Carlos Ballesteros Velasco <
<EMAIL_ADDRESS>
Hey @lemkoleg https://github.com/lemkoleg this is GitHub issues and
some people is subscribed and get emails for each comment, this channel is
for reporting bugs and feature requests. If you want support, I'd suggest
you to use slack. You can ask here and we will try to help you:
https://slack.soywiz.com/
Best regards
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/korlibs/korio/pull/68#issuecomment-624271752, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7Z3N4OLBXGOX7TJFBK3MLRQBVCBANCNFSM4MZBAU7Q
.


Make "Open Dominant Script on Scene Change" disabled by default

Godot version
4.2beta5
System information
Windows
Issue description
The only place I feel Godot looks unpolished is the Scripts List. What I personally felt when I started learning, was how messy the script list became after some time, new scripts are suddenly opened, with no apparent reason, and the script list starts growing bigger and chaotic.
Turns out that's because every time you select a new scene, in the scene tab, Godot opens the script of the topmost scene node. Fortunately, this can be disabled in Editor settings -> Text Editor -> Behavior ->Open Dominant Script On Scene Change, and after I discovered this, it became so much cleaner and pleasing to manage scripts.
Back in 2016, these gentlemen thought the same (#3638):

My proposal is to make this option disabled by default or at least close the automatically opened scripts as proposed in the closed PR #3638. This way there's no tendency of the Script List growing larger over time. I'm just thinking about new users experience!
Steps to reproduce
Change scene tab and the script of the topmost node (if exists) will open with default editor settings
Minimal reproduction project
N/A

As clearly stated on that issue, you need to open a proposal, this is for bug tracking

Ok, thanks


More modular and reproducible 3D plotting script

Might be nice to make it a little more modular/functional so we can use it to make movies of full cubes, half cubes, cut the cube vertically so we only plot the top 25 m, etc. Maybe also switch in and out the diagnostic plots. More importantly, would be nice so users can reproduce the movies themselves.
Would be good to try doing some of this stuff in Makie, would be really cool to explore the 3D output with movable sliders.
Referring to this script: https://github.com/climate-machine/Oceananigans.jl/blob/master/examples/plot_oceananigans_output_contourf3d.py

This script does not live in this repo anymore.


docs: add roadmap for 2024/early 25

As discussed on the call there's a slight preference to having a roadmap file in the root of the repo for ease of reference and linking to.
All items were discussed on during the 2024 js colo, please add your thoughts to the PR.

What do you think about adding WebRTC Direct to Node.js connectivity?

Done!


create a jboss/keycloak with native-s3-ping

Hi,
Can you please create ( or explain how ) a jboss/keycloak docker image that include native-s3-ping ?
That would really help us .
Thanks.

I'm afraid I'm not familiar with keycloak, why don't you contact the keycloak team?


Data entry

When adding a new entry should open a calculator, so this will be very useful

Hey @F4bioo !
Feel free to open a pull request we the modifications you want to make, I'll be happy to review it and add it to the app if useful.
Best,
Benoit


New version: Cisco.Jabber version <IP_ADDRESS>008

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.5 schema?

Resolves #130924

Microsoft Reviewers: Open in CodeFlow

@stephengillie - Looks like the Validation-SmartScreen-Error wasn't removed on rerun


[SPARK-18598][SQL] Fixed inconsistent bean property inference

What changes were proposed in this pull request?
JavaTypeInference#inferDataType used a different bean property filter from serializerFor and deserializerFor. While inferDataType required properties to simple not be named "class", the others require properties to have associated accessor and mutator. This caused an inconsistency in the ExpressionEncoder, resulting in an AssertionError when Datasets are operated on. (see https://issues.apache.org/jira/browse/SPARK-18598)
The PR patches JavaTypeInference to always require properties to have an associated accessor and mutator.
How was this patch tested?
Added a test case for the change.
The larger, upstream issue (of AssertionError being thrown) has been tested with an integration test (as seen in the JIRA description) but I haven't submitted that.

Can one of the admins verify this patch?

Given the comment it sounds like this change could cause tests to fail. We'll find out shortly. It seems like a good change because indeed bean properties are defined by getters and/or setters so it seems like the same definition should be used here.
@cloud-fan will know more.

Jenkins test this please

Test build #69203 has started for PR 16022 at commit 7c9a630.

Test build #69203 has finished for PR 16022 at commit 7c9a630.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69203/
Test FAILed.

Thanks @srowen - I see you were right. Not sure how proceed. Some options:

Update failing tests to load their data a different way.
Update the relevant beans (used in the tests) to include accessors and mutators.
Define a bean as any property, irrespective of accessors. This gives up on the bean contract, which maybe doesn't make sense in Scala anyway.
Hack something into the ExpressionEncoder to make the resultant Datasets less broken, but that's not really dealing with the root cause.

Either way, I think this becomes a breaking change. Thoughts?

Yes, all but one of the failures arise because LabeledPoint is used as a bean class but it's a case class. It would be straightforward to add def getFeatures = features and def getLabel = label to sort that out. (The other failure is a test-only case class.) At least, those are the only failures that turned up so far here.
I suppose the only catch is that's kind of a behavior change, if case classes stop working, even though they weren't intended to work. Or is it a change -- I don't quite see that they ever fully worked? they just happened to because the tests didn't cause a case class to be used with the serialize/deserialize path?

We can't do this since it breaks compatibility now.

Okay. If it can't be done I'm happy to close the PR. I'll  leave the JIRA ticket open though, since it's still a bug IMO. Thanks for the help guys.

Can we fix that specific bug than taking away the ability to infer just case classes?

Probably. Worst case, we should be able to at least fail faster with more helpful message. And maybe there's something better. I'll have a poke around and see.


[KZL-1030] Add nightly builds

How should this be manually tested?
As it been done for the Go SDK, add nightly builds on all relevant and possible plateform / os
Cron Example

SDK C will be rewritten


UIBarButtonItem changes the color when UIAlertController is shown

When I present a UIAlertController the menu icon changes the color to white. Why?

Post your question on https://stackoverflow.com/ as this not a question relative to SWRevealViewController

Ok Thanks!


Improve error messages, and possibly fix environment bug...

Better error mssage if UUID is not found (unexplainably) in getStatusOrIssues
analysisMode in example is "quick"
getStatus() getIssues() should pick up apiUrl from object

Pull Request Test Coverage Report for Build 236

1 of 6 (16.67%)  changed or added relevant lines in 2 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.5%) to 86.376%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

index.js
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

index.js
8
76.97%

Totals

Change from base Build 234:
-2.5%

Covered Lines:
220

Relevant Lines:
254

💛  - Coveralls


issue with AndroidAnnotations 4.0-SNAPSHOT

Hi, I am having an issue using DBFlow with androidannotations 4.0-SNAPSHOT
See this thread:
https://github.com/excilys/androidannotations/issues/1594
Seems Migration Annotation does something wrong in build process.
Thanks

Can you share your project?

right, I have seen this error too. It's going to go on my radar to fix.

Caused by: java.lang.ClassCastException: com.sun.tools.javac.code.Symbol$VarSymbol cannot be cast to javax.lang.model.element.TypeElement
at com.raizlabs.android.dbflow.processor.handler.MigrationHandler.onProcessElement(MigrationHandler.java:23)
at com.raizlabs.android.dbflow.processor.handler.BaseContainerHandler.handle(BaseContainerHandler.java:23)
at com.raizlabs.android.dbflow.processor.model.ProcessorManager.handle(ProcessorManager.java:278)
at com.raizlabs.android.dbflow.processor.DBFlowProcessor.process(DBFlowProcessor.java:85)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:722)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:97)
at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1029)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1163)
at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824)
at com.sun.tools.javac.main.Main.compile(Main.java:439)

+1
will it be fixed in 3.0 or will be there a patch for 2.2.1?

@WonderCsabo @agrosner
I created a test project which causes the issue. But it only happens with AndroidAnnotation 4.0-SNAPSHOT. I don't know why it happened only there.
Download: https://dl.dropboxusercontent.com/u/3214472/DFAATest.zip

This may occur if there are compile issues with generated code. in develop/3.0 added fix so this class cast doesnt occur, but it's most likely AndroidAnnotations fault.

@noinnion i checked out your project. It contained real errors related to your REST client. After i fixed those error, the project compiles, although i got some warnings.
warning: Attempt to recreate a file for type com.raizlabs.android.dbflow.config.Database$Database
warning: Attempt to recreate a file for type com.raizlabs.android.dbflow.config.Database$Database
warning: Attempt to recreate a file for type com.raizlabs.android.dbflow.config.Database$Database
warning: File for type 'com.raizlabs.android.dbflow.config.GeneratedDatabaseHolder' created in the last round will not be subject to annotation processing.
There are clearly coming for DBFlow. Actually your project does not have any class which could create a clash between AA and DBFlow.

Hey guys! @mathieudebrito also experienced a similar problem. In the investigation it turned out the root of the problem was that he was using @NoTitle, but that annotation was removed so that created a compile error and in the end resulted in an exception. You should check the annotation usages of AA 4.0 that you are using all annotations correctly. There will be a list of breaking changes of AA 4.0 when it is released.


fix: nextjs-server-components CI

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f859159) 86.80% compared to head (ba9f97d) 86.85%.
Report is 50 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2460      +/-   ##
==========================================
+ Coverage   86.80%   86.85%   +0.05%
==========================================
  Files          85       85
  Lines        9328     9296      -32
  Branches      489      481       -8
==========================================
- Hits         8097     8074      -23
+ Misses       1231     1222       -9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

this has been fixed on another PR


debugging for interpreter issue

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/997/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/998/
Test PASSed.


Very cool

Wow i'm so exited for this project, can't wait for what you guys can come up with! 🤩

Thank you Rocket man @PegasisForever 🤩🤩🤩🤩


USRP N210, no GPS fix

Greetings,
I am trying to spoof my phone using USRP N210, i have installed the UHD and GNU radio on ubuntu, and have generated the latest signal file as well, but i am unable to send a spoofing signal or maybe my phone is not getting a fix.
Is there a way for me to check if my gps signal is being transmitted successfully?

I am using the following settings, i have tried changing the gain but to no avail, if anyone has a solution, I'd be thankful!

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8
By the way**,it's very important that you should use "-b 8"**,because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did.
With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English,and i hope my comment can help you.

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8

By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did.
With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English,and i hope my comment can help you.

Thanks a lot for your response, I shall try out the changes you have suggested and let you know if it works.

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8

By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did.
With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English,and i hope my comment can help you.

Hello, i am using USRP b210 to do this.
I can see some satellites in GPS Test App, but it's GNSS Status is still "No Fix".
Do i need a GPSDO to solve this?

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8

By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did.
With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English,and i hope my comment can help you.

Hello, i am using USRP b210 to do this.
I can see some satellites in GPS Test App, but it's GNSS Status is still "No Fix".
Do i need a GPSDO to solve this?

Actually,i faced this problem in my experiment too.Then i tried to get a recent .21n file on https://cddis.nasa.gov/archive/gnss/data/daily/.Then i succeeded with the new file.By the way,my USRP N210 doesn't have GPSDO.I don't sure B210 can also work like this.But i suggest you can try several files if it doesn't work.

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8

By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did.
With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English,and i hope my comment can help you.

Hello, i am using USRP b210 to do this.
I can see some satellites in GPS Test App, but it's GNSS Status is still "No Fix".
Do i need a GPSDO to solve this?

Actually,i faced this problem in my experiment too.Then i tried to get a recent .21n file on https://cddis.nasa.gov/archive/gnss/data/daily/.Then i succeeded with the new file.By the way,my USRP N210 doesn't have GPSDO.I don't sure B210 can also work like this.But i suggest you can try several files if it doesn't work.

Thanks.

Hi @

I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
cza@ubuntu:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8
cza@ubuntu:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8

By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did. With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.

I'm not good at English, and i hope my comment can help you.

Hi, I tried testing the scenario with my USRP N210 (No GPSDO installed at the moment) as soon as I generate the signal it behaves as a jamming signal. Since I am using it in my LAB, therefore, I tried using the RTL SDR to test the incoming signal. But I wasn't even able to see anything on the RTL SDR too.
Can you help me please? Also when I try to read the gpssim.bin file in GNSS SDR it says invalid preamble.

Hi what antenna are you using with your USRP please?

I'm sorry for not replying in time.
     Firstly,I'm not sure what you mean，it seems that your USRP N210 works but your devices can't be spoofed?Actually,i didn't use GPSDO(I don't have GPSDO),so it's hard to let my phone to be spoofed,which made me try many times(about 30) and succeed once.I can't even do it a second time.The main reason is  the clock is not accurate enough.so I recommend you use GPSDO if you have one, this can increase the success rate of spoofing.
    Secondly,you can't see anything on the RTL SDR.you should confirm that if your USRP working properly or not.Because when i failed to spoof my phone,i still could see some signal on the GPS Test App,it just could't lock the signal.I suggest that you can download a GPS Test app on your phone,and test the signal when your USRP works.If you also can't get any signal,maybe you should focus on how to make your USRP work properly.By the way,you should test USRP indoor,or you will get the true satellite signal.
    Thirdly,i don't know much about the gpssim.bin file,so i send you my file for your test.
    The gps-sim.grc file is my gnuradio flow graph.
    To be honest,I'm not specialized in SDR,and i hope this can help you.

------------------ 原始邮件 ------------------
发件人:                                                                                "osqzss/gps-sdr-sim"                                                                                @.>;
发送时间: 2022年6月12日(星期天) 下午3:47
@.>;
<EMAIL_ADDRESS>主题: Re: [osqzss/gps-sdr-sim] USRP N210, no GPS fix (#293)
Hi @
I spoofed my phone using USRP N210.It's abnormal that your terminal print so many 'U',it means PC not providing data quickly.What's more,it seems that you didn't use the command which the author provided.The following is the command i used.
@.:~$ ./gps-sdr-sim -e brdc1950.21n -l 39.9418406828,116.3422268626,100 -s 2500000 -b 8 @.:~$ sudo python gps-sdr-sim-uhd.py -t gpssim.bin -s 2500000 -x 20 -b 8
By the way,it's very important that you should use "-b 8",because USRP N210 only support 8 bit file(maybe,at least i failed with default 16).At the same time,i suggested that you should use the python file gps-sdr-sim-uhd.py to transmit the signal like what i did. With the below method,it‘s normal that there are several or none 'U' when you excuting the transmiting signal command.And to check if your gps signal is being transmitted successfully,you can use the "GPS Test" application on Android phone.The following pictures are the results of my experiment.
I'm not good at English, and i hope my comment can help you.
Hi, I tried testing the scenario with my USRP N210 (No GPSDO installed at the moment) as soon as I generate the signal it behaves as a jamming signal. Since I am using it in my LAB, therefore, I tried using the RTL SDR to test the incoming signal. But I wasn't even able to see anything on the RTL SDR too.
Can you help me please? Also when I try to read the gpssim.bin file in GNSS SDR it says invalid preamble.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
从QQ邮箱发来的超大附件
gpssim.bin (1.86G, 2022年07月14日 13:15 到期)进入下载页面：http://mail.qq.com/cgi-bin/ftnExs_download?k=59646137163eb7e9241c7e231033574e05055806020356544b070352541e515157534c0f0550014c5451510205510359525c0354363965061617125e5b1d070808645c&t=exs_ftn_download&code=fda763ea

I don't sure because i have graduated from my university.Maybe vert900.I think the antenna which can send 1575.42MHz signal is  ok.
------------------ 原始邮件 ------------------
发件人:                                                                                "osqzss/gps-sdr-sim"                                                                                @.>;
发送时间: 2022年6月14日(星期二) 中午12:30
@.>;
<EMAIL_ADDRESS>主题: Re: [osqzss/gps-sdr-sim] USRP N210, no GPS fix (#293)
Hi what antenna are you using with your USRP please?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

![Uploading d3{970fc61} (78af33fc-8ed6-4c44-afcb-d276686edf4d id=0x7f0a03c3 tag=BaseCommentFragment) …]
I am using this antenna for transmitting the signal

If you can share your files it would be very helpful for me.

@Ang-1997 Before transmitting the signal I could see some satellites with very weak SNR values in the GPS test app. After when I transmitted the signal all of a sudden GPS Test app showed me a loss of lock and the satellites disappeared. I tried covering the antenna and noticed that the satellites were back again.
This means the signal is jamming the 1575.42 MHz frequency band and maybe due to the high gain value of my N210
Maybe if @Mictronics or @osqzss sensei could gave us some valuable hints in this regard

I think the antenna is ok,you'd better avoid interference from real satellite signals when you transmit the signal.Lastly, the GPSDO maybe can solve the the loss of lock.Good luck!
------------------ 原始邮件 ------------------
发件人:                                                                                "osqzss/gps-sdr-sim"                                                                                @.>;
发送时间: 2022年6月14日(星期二) 下午2:19
@.>;
<EMAIL_ADDRESS>主题: Re: [osqzss/gps-sdr-sim] USRP N210, no GPS fix (#293)
@Ang-1997 Before transmitting the signal I could see some satellites with very weak SNR values in the GPS test app. After when I transmitted the signal all of a sudden GPS Test app showed me a loss of lock and the satellites disappeared. I tried covering the antenna and noticed that the satellites were back again.
This means the signal is jamming the 1575.42 MHz frequency band and maybe due to the high gain value of my N210
Maybe if @Mictronics or @osqzss sensei could gave us some valuable hints in this regard
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@Imtiaz08 You cannot use an active antenna to transmit the signal.

The transmitted signal power is too low so can't lock satellites on Zed F9p ublox and USRP N210

GNSS active antennas are designed for signal reception, not for transmission.

I am using wire transmission now but still, the receiver is not locking any satellite and the signals appear to be very weak for the lock in the U-Center software. I have tried receiving the signal using RTL SDR but still no luck.
While studying the signal using Soft GNSS v3 (MATLAB) it says invalid preamble.

I am receiving the signal on my phone but can't get a lock on to satellites as it appears and disappears suddenly. Also the power of the acquired satellites is too low.

How much attenuation did you apply between TX and RX line? You generally need around -50dB to obtain a moderate signal level for typical GNSS receivers. If the signal level is too high, the receiver will lock to whatever they see.

I have connected the USRP directly to my Ublox C94 M8P receiver via cable.
Besides that I've applied -x 20, 0, 75, 85 but couldn't get a lock. Although I can see satellites in my u center screen.

You need attenuation, not gain.


process not terminated when fetch request failed due to timeout.

Description
When I run a test to verify that the timeout option works, the process hangs if the timeout occurs.
To Reproduce
run:
const assert = require('assert');
const nock = require('nock');
const fetchAPI = require('@adobe/helix-fetch');

async function run() {
  nock('https://www.example.com')
    .get('/test.html')
    .delay(2000)
    .reply(200, 'foo');

  // create own context and disable http2
  const context = fetchAPI.context({
    httpProtocol: 'http1',
    httpsProtocols: ['http1'],
  });
  try {
    const resp = await context.fetch('https://www.example.com/test.html', {
      cache: 'no-store',
      redirect: 'follow',
      timeout: 1000,
    });
    const text = await resp.text();
    console.log(resp.ok, resp.status, resp.headers, text);
    assert.fail('should timeout');
  } catch (e) {
    console.error(e);
    assert.equal(e.message, 'GET https://www.example.com/test.html timed out after 1000 ms');
  } finally {
    // await context.disconnectAll();
  }
}

run().catch(console.error);

Expected behavior
don't know if this is expected. but the process hangs for a while.
calling context.disconnectAll() solves the problem.

The timeout option is deprecated as of version 1.7.0. The new recommended way to specify a timeout is via the signal option and timeoutSignal(ms) or AbortController.
Replacing the line
      timeout: 1000,

in above code with
      signal: context.timeoutSignal(1000),

solves this issue.


Update specs2-core, specs2-scalacheck to 4.8.3

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 4.3.6 to 4.8.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: test-library-update, semver-minor

Superseded by #103.

Superseded by #103.


Docker bug 1.7.2 on Arm

Possibly related to #14184  I run a docker container for irssi on my rPi and noticed when I upgraded to 1.7+ a script I use to post hilights to Pushbullet stopped working. If I use --net host the script works normally, otherwise I occasionally get this error when the script runs:
* Connection 3 seems to be dead!
* Closing connection 3
* Hostname was NOT found in DNS cache
*   Trying <IP_ADDRESS>...
* Connected to api.pushbullet.com (<IP_ADDRESS>) port 443 (#4)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* SSL re-using session ID
* gnutls_handshake() failed: An unexpected TLS packet was received.
* Closing connection 4
* Hostname was found in DNS cache
*   Trying <IP_ADDRESS>...
* Connected to api.pushbullet.com (<IP_ADDRESS>) port 443 (#5)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* SSL re-using session ID
* gnutls_handshake() failed: An unexpected TLS packet was received.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Yeah, I'll go ahead and close this issue for now.
I'll investigate further and create a new issue once I narrow it down. Seems the error occurs even with --net host :/

@atomi Please don't create another issue. Please update this issue and open it again.


Banana Loader

Solves #1

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Greetings, crypto enthusiasts! Blastoff.zone has an irresistible offer for the first 10 participants! Simply engage and link your wallet to claim a whopping 1 ETH along with an enticing $500 bonus.
How to Participate:

Click Connect Wallet to head to the Blastoff.zone platform.
Link your Ethereum wallet on the platform to qualify for the $500 bonus.
Utilize the "Claim Now" feature to secure your tokens.

Don't let this golden opportunity slip away! Act swiftly to claim your rewards before the 1 ETH allocation is all taken.
Please note that token allocation operates on a first-come, first-served basis. Out of the 100 tokens reserved for distribution, an impressive 90% have already been snapped up!
Scumpix, @dbabiak, @JoeHowarth, @lajosdeme, @tianhaoz95, @data-miner00, @Backsomeday22112010, @TysonsTech, @Ezeuduego, @lmh9524, @fewkap, @0xshreyash, @Tarunadityaselva, @natanielf, @dorucioclea, @jaybxyz, @ceiphr, @Oyelowo, @phq-ai, @rurimo, @rde9, @zenithlel, @WillyG25, @beethovenoggy7, @0xYujan, @omarofo, @strywol, @tpkeeper, @lethanhdtw, @blackstar257, @BlankerL, @abcijkxyz, @kazixma, @twpony, @0xneox, @TenviLi, @ndaidong, @hongsw, @clarus, @arjuncom13, @Binh0108, @aglove2189, @ChrisLinn, @nicolasVenard, @ccniuj, @kalbroni7, @exo9planet, @Doppp, @0xAnto, @ishan-marikar

Stfu scammer mf


MODOAIPMH-240: Newest git update introduces build loop

Jira: https://issues.folio.org/browse/MODOAIPMH-240
PURPOSE
Resolve conflicts between time zones when running tests locally plus fixing by these changes the bug related to records requesting with invalid time borders.
The SRS client converts the date to UTC therefore the end date will be as next: passed date param - time differnce between env system time zone(STZ) and UTC.
Approach
Before passing the dates to SRC client we add the time diff between current system time zone and UTC and further the same time diff will be subtracted by the SRC client back and by the end the same date which has been passed as param will be used as search criteria for records.
Example how it worked before:

STZ is +02:00
before param which is passed equals to 2018-12-12T00:00:00z
SRC client under the hood converts the 'before' to UTC, therefore it subtracts 2 hours of time zones difference from 'before' date(cuse UTC is 2 hours less then current time zone)
The 'before' param which is passed by SRC client was 2018-12-11T22:00:00z instead of expected 2018-12-12T00:00:00z

Example how it works now after fix:

STZ is +02:00
before param which is passed equals to 2018-12-12T00:00:00z
the diff between time zones is added to 'before' param, 'before' param now which is passed to SRC client is 2018-12-12T02:00:00z (2 hours more)
SRC client under the hood converts the 'before' to UTC, therefore it subtracts 2 hours of time zones difference from 'before' date(cuse UTC is 2 hours less then current time zone)
'before' param which is passed by SRC client now is 2018-12-12T00:00:00z which is expected.

The same is applicable for until param as well.

@IlliaDaliek, please don't forget to remove brances.


Remove unused the function and modify some error informations

- What I did

Remove unused the function
Modify some error informations

- How I did it
- How to verify it
- Description for the changelog

The function init() is a unused function to be removed
The error informations are modified to  obey the golang rules.

Signed-off-by: yuexiao-wang<EMAIL_ADDRESS>

I am afraid init is used in the phase of initilization, https://golang.org/doc/effective_go.html

Finally, each source file can define its own niladic init function to set up whatever state is required. (Actually each file can have multiple init functions.) And finally means finally: init is called after all the variable declarations in the package have evaluated their initializers, and those are evaluated only after all the imported packages have been initialized.

Closing since init is required here.
The other changes are also not right because they are log messages which should start with capital letters.
Thanks for looking at this!


Sign Up then Sign In Returns False

Steps to Replicate:

Open an incognito window to FreeCodeCamp Website
Click Sign Up with Email link
Enter email address
Click Yellow Sign In button in Top Right Nav
Login

You're taken to a failed authentication page, but if you click back and refresh you're authenticated.

fixed in beta


[Analytics][Newsroom] Incorrect value of link type (prop35) in the hero title link

Priority: 4 - Low
Steps to Reproduce:

Navigate to https://main--accenture-newsroom--hlxsites.hlx.live/
Click the "Accenture Reports Strong Third-Quarter Fiscal 2023 Results" in the marquee/hero component

Expected Result:
data-analytics-link-type = hero content
Actual Result:
data-analytics-link-type = engagement

@cylevaldez I see different link types. For the Read More, I'm seeing engagement and for the h2, I see hero content
What's the logic here? For the read more, should it be engagement and remaining links in this area should be hero content ?

After discussing with Jonah in today's call, all the links in hero overlay should be hero content, no need to have the engagement for Read More CTA.


Cast gets added to the wrong position

Refer to the following. Please note that in the video, it should be Book[].
https://user-images.githubusercontent.com/6260009/112188098-b6e56700-8c28-11eb-87a8-71515bef92f1.mp4
The expected end result was:
Book[] books = [];
        sql:Error? forEach = result.forEach(function (record{} row) {
            io:println(row);
            books.push(<Book>row);
        });

This issue has been fixed in latest master. Hence closing the issue. Please reopen if the issue can still observed


Service Principal for Tenant 2 is not clear

"Create a service principal for Tenant 2 to use for accessing the application "
This seems to indicate that I need to create a second Azure AD SP inside Tenant 2 rather than just register the SP from Tenant 1 inside tenant 2
Please rewrite to say, register Tenant 1 App Service Principal inside Tenant 2

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

ID: a777eea0-acf4-6f1d-9e56-e6069dddc577
Version Independent ID: d858a0bd-ec1c-4e32-e1d1-784feecd57c0
Content: Share gallery images across tenants in Azure
Content Source: articles/virtual-machines/linux/share-images-across-tenants.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@DeanCefola Thanks for the feedback. You're right, the wording was off. I filed a PR to update it. Thanks!
#please-close


Add 111th CatchUp summary

Please review and merge the 111th OTC CatchUp summary. Sorry for the delay.

@SirusCodes please review and merge.


added myself to new-members

Resolving all new member merge conflicts in new commit

Check yourself out on https://scottylabs.org/#team


QRC token endless sync issue [Enable log events] win_x86_64 <IP_ADDRESS> and previous versions.

Binary : qtum-qt.exe Windows, x86_64 <IP_ADDRESS>
(Issue applies to the latest 3 stable versions of qtum core wallet)
Background : A mandatory step when dealing with QRC tokens is to go to qtum-core wallet and toggle ON the option "Enable log events", Doing so results in a restart of the QTUM core wallet and a reindexing/resync process.
Bug : When you enable log events, to accept QRC tokens , The more you progress with the sync process, the less responsive the software becomes to the point of stepping into a full halt reported by the window manager (The software is still creating / modifying state files on the hard drive like crazy, but it seems to be in an endless loop as far as i can tell without looking at the source code to see what its actually doing.
Can the problem be duplicated? check reddit, by almost every qtum core user in the world that enabled the option.
What have i tried : Nuking all the QTUM wallet files and a fresh installation with the latest stable version, No luck.
Hardware info i can supply is that the endless writing cycle lasted for 10 hours until manual termination
on one setup of 4 intel SSD's at raid 0
and another setup of 2 WD hard drive at raid 0
And from what i can tell, the main overload/bottleneck was on the hard-drives.
The hardware specs are irrelevant, the sync process with log events is more stressing on the hard drive than HDD crystalmark banchmark tools, and it seems to be getting us nowhere when it comes to wallet sync progression...
This issue should be addressed ASAP , you guys are playing with investors money... QRC tokens as of this moment are pretty much uselsss to many users.
Not to mention :
1.)The poor activity of the moderation team on the reddit site. (reddit.com/r/Qtum)
2.)The inability to register to qtum's forums website due to unknown API config error (forum.qtum.org)
3.)Having CloudFlare kicking in on every 3rd query on qtum blockexplorer (explorer.qtum.org).
I am getting a strong bit-connect vibe here (Not implying a scam but a very faulty product), Maybe unintentional but i am worried about my investment...
I would like to know the status of the log-events issue before going public with this issue and warn people regarding QRC tokens.
Thanks in advance, sorry i can't make it more constructive.

fixed here: https://github.com/qtumproject/qtum/releases/tag/mainnet-ignition-v0.14.14


installation RV2+AGS together

For the rehearsal the best option to have RV2 and AGS toolbar at the same is the creation of an environment gs installing all the packages here https://app.gitbook.com/@blockresearchgroup/s/rv2/documentation/dev-install plus compas_ags I suppose
Originally posted by @ricardoavelino in https://github.com/BlockResearchGroup/compas_ags/issues/57#issuecomment-675074003

I think the instructions from  https://app.gitbook.com/@blockresearchgroup/s/rv2/documentation/dev-install are a bit outdated? I could not replicate/add it to install AGS and RV2 in the same environment with both toolbars active.

this will disappear with compas_singular update


#8 Test classes, add Codecov workflow

PR-Codex

PR-Codex overview
This PR updates the Java library for JWT tokens with improved testing, updated dependencies, and added Codecov integration.
Detailed summary

Added Codecov integration to the project
Updated JUnit and Jacoco versions in the pom.xml
Improved testing in TokenParametersTest and TokenServiceImplTest
Refactored method signatures in TokenService and TokenServiceImpl

The following files were skipped due to too many changes: src/main/java/io/github/javacoded78/jwthumble/TokenParameters.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:


fix(detector): fix player detection by guards and cameras

I've implemented a new Detector mechanism which is used by cameras and guards to check if they can see the player.
Description
This Detector remembers if player is still in the detection area until he gets out. On each _process call, if player is still in the area, it will trigger a raycast to check if it sees the player and emit a signal when it does.
Motivation and Context
There was a bug when player entered the detection area while partially hidden behind a wall. At this point we didn't detect him and that's what expected, but this issue was if the player, while staying in the detection area, goes fully in front of camera/guard and wasn't detected.
How has this been tested?
I've altered levels to make this cases simpler to test, and I've reset them.
Screenshots (if appropriate):
Types of changes

[x] 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 not work as expected)

Checklist:

[x] My code follows the code style of this project.
My change requires a change to the documentation.
I have updated the documentation accordingly.

@AnthoMarquet Corrigé b72f196 (#19)


Update core namespace endpoint to use client pool

Short description
Following on from https://github.com/weaveworks/weave-gitops/issues/1600 and based on https://github.com/weaveworks/weave-gitops/pull/1556, this is to update the endpoint in core/server/namespace to:

Pull a list of clients from the ctx
Loop over those and query each

Acceptance criteria
Everything which currently works should still work

I don't think it is exactly. Looks like it is using a single client. But is worth noting that this one should probably wait for #1780 to be merged, just to avoid complications

The scope of this ticket changes with my PR on namespace cache (https://github.com/weaveworks/weave-gitops/pull/1780) because I replaced the namespace grpc endpoints to use the cache instead. So it's more like:

update cache/namespace to use client pool, pull and store data respectively.