Background mode every whatever minute

Hi,
I know it's not an issue of this plugin.
Actually, this plugin works great on iOS background mode.(Tested on iPhone 5, iOS 9.3)
When the app goes on background, BLE can scan, connect, and read / write.
What I want to do is to run BLE on background every ~ minutes. (like 5m, 10m, etc)
Since I'm using cordova / phonegap, I was trying to implement simple javascript timer and local notification but none of these can wake up the app and run BLE.
Does anyone have an idea how to make this happen?
Thank you!

Update:
Want to share a bit of trick here.
For iOS, there are mainly 3 activities of BLE that keeps BG alive. Connecting, read and write.
We should be more careful with 'Connecting' function.
If interested, please refer
https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/CoreBluetooth_concepts/CoreBluetoothBackgroundProcessingForIOSApps/PerformingTasksWhileYourAppIsInTheBackground.html
But the issue I'm having was slightly different.
Calling connectPeripheral:options can keep BG alive until connected.
What happens after connected? Well, BG is ended and app is moved to suspended state.
So, I implemented this but I still need more methods to resolve my issue.
On BG, once it's connected, I started to call writeCharacteristicWithoutResponse.
I've noticed that this keeps BG alive for 4~5 seconds.
Now, I'm keep calling this method every 4 seconds.

@hoongoon86 Hi, thanks for sharing this, sorry for not being of much help here. I think BLE scanning will work in the background, but I don't think you can control how often the scan is performed/the app wakes up. Perhaps there are other background tasks/services that could be added to the app to wake the app up?

@mikaelkindborg Hi, thanks for your comment.
Unfortunately, I've failed to keep background alive using scanning function. I was trying to scan for non-existing services and trying to end scanning when the app comes back on foreground. Perhaps I was doing it wrong or simply it's not how it's supposed to be. I don't know.
I couldn't find other solution (methods or functions) to make BLE work on background.
Please share us if you find any.
So far, I could make BG work for about 36 hours. Of course it consumes energy from both phone and the device but it was a good experiment.

@hoongoon86 I will keep my eyes open for solutions and ideas!


Migrate to Spring Boot

This migration does the minimum I could to make the switch, still using RESTEasy instead of Jersey/SpringMVC and still
using Infinispan. Both work great thanks to community starters from PayPal and Infinispan team.
Fixes #72

Codecov Report

:exclamation: No coverage uploaded for pull request head (migrate-spring-boot@e5d4ed1).

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 a50ec19...e5d4ed1. Read the comment docs.

Just a heads up that Spring Boot 1.5.1 was just released today. Apache Camel 2.19.0 has already been upgraded. But should work on the older 1.4.x release as well.

Thanks @davsclaus - already upgraded to 1.5.1 in this PR this morning.

@jimmidyson So what are the reasons to go Spring Boot?

@KurtStam We've discussed this quite a few times, plus the issue I opened in #72 which eventually triggered me into action to do the migration. Biggest reason for migration is that firstly it just works, plus it has great documentation, many examples and a vibrant community. Personally I've found it hard to get started with Wildfly Swarm and have spent time fighting/figuring stuff out with it that would have been better spent actually coding more.

@davsclaus Downgraded to Spring Boot 1.4.4 when I tried adding Spring Cloud Sleuth for Zipkin tracing (breaking changes in Spring Boot 1.5.1 it seems that Cloud can't work with yet).

Please final comments/review so we can merge this sucker today.

[merge] please


Repo social media preview image

This is low-priority, but we can add a logo for our repo so that when people link to it from social media, it uses the logo.
See docs.

I have access to the entire Adobe Creative Cloud through work! I'm sure we can leverage that to make something super cool


Topic model over time viz isn't working

On "Influential Words" page in Topics, (navigated to from the "Details" button on the Language tab), the topic model over time visualization is not loading. Have tried multiple topics. No error message, just spinning followed by "can't load the data."

I assume you mean the Topic Word Space Over Time ? locally it renders for me but not on prod:
https://topics.mediacloud.org/api/topics/2729/word2vec-timespans?snapshotId=2785

@rahulbot I didn't get past why this wasn't loading on prod

Adding that in my latest topic, the word cloud that shows up in the overall topic model is different from the one that shows up in the Language tab (topic #2976)

looking at the summary word page and the influential word page, the word clouds are rendering and do match, but I am still getting a:
app_js.d15be65b.js:12 GET https://topics.mediacloud.org/api/topics/2990/word2vec-timespans?snapshotId=3195 504 (Gateway Time-out)

on production


ARROW-4011: [Gandiva] Install irhelpers.bc and use it

If we don't install irhelpers.bc, users need to keep build directory
that has irhelpers.bc.

This is needed to build Gandiva deb/rpm packages.

Codecov Report

Merging #3232 into master will increase coverage by 1.19%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3232      +/-   ##
==========================================
+ Coverage   88.18%   89.38%   +1.19%
==========================================
  Files         535      477      -58
  Lines       72873    68846    -4027
==========================================
- Hits        64260    61535    -2725
+ Misses       8506     7311    -1195
+ Partials      107        0     -107

Impacted Files
Coverage Δ

cpp/src/gandiva/tests/binary_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/test_util.h
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/date_time_test.cc
100% <100%> (ø)
:arrow_up:

...c/gandiva/tests/projector_build_validation_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/in_expr_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/null_validity_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/engine_llvm_test.cc
95.58% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/literal_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/projector_test.cc
100% <100%> (ø)
:arrow_up:

cpp/src/gandiva/tests/hash_test.cc
100% <100%> (ø)
:arrow_up:

... and 66 more

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 1a8c8f0...7ff4cf2. Read the comment docs.

Looks like the Java build will require some changes to be able to do this https://travis-ci.org/apache/arrow/jobs/470799486#L5073

Thanks for doing this , this makes it easier for customers to use rpm packages as you rightly pointed out.

CI is green. I'll merge this.


Now that nerdicons has been updated, would you mind rebasing your PR? Thanks.

I'll do that, but I'll also add system icons configuration so stuff like folder icons and chevrons and others can also be changed


Merge darwin/libdispatch-1121 to master

Merge tag darwin/libdispatch-1121 on darwin/trunk. This includes the latest Apple source drop libdispatch-1121 (up from 913.1.4), on top of tag darwin/darwin-012 which is the result of pulling into the Apple repository the PRs since the merge of darwin/libdispatch-913.1.4 (PR #289).

@swift-ci please test


OrientDB no longer works behind NGINX reverse proxy.

OrientDB Version, operating system, or hardware.

v2.2.8

Operating System

[x] Linux
[ ] MacOSX
[ ] Windows
[ ] Other Unix
[ ] Other, name?

Expected behavior and actual behavior
The issue I am having is that somewhere after 2.2.0, trying to use nginx as reverse proxy for OrientDB no longer works.  When I try to log into the database I get the following error in the browsers:
https://localhost/orientdb/command/-9199765851322639105/sql/-/-1?format=rid,type,version,class,graph net::ERR_INCOMPLETE_CHUNKED_ENCODING
In the NGINX console i get:
2016/09/02 06:16:34 [error] 8#8: *2 upstream prematurely closed connection while reading upstream, client: <IP_ADDRESS>, server: localhost, request: "POST /orientdb/command/-9199765851322639105/sql/-/20?format=rid,type,version,class,graph HTTP/1.1", upstream: "http://<IP_ADDRESS>:2480/command/-9199765851322639105/sql/-/20?format=rid,type,version,class,graph", host: "localhost", referrer: "https://localhost/orientdb/studio/index.html"
And in OrientDB console I get:
2016-09-02 06:45:53:254 SEVER Internal server error:
java.net.SocketException: Socket closed [ONetworkProtocolHttpDb]
This worked in version 2.2.0, but when I upgrade to 2.2.5 it stopped working.  It is still not working in 2.2.8.
I have done a bunch of reading and it seems that this is likely to do some HTTP streaming / chunked encoding issues.  I noticed that proxies are very sensitive to this, and I also see that in recent version orient has updated how it is doing response streaming.
Steps to reproduce the problem
I am going to try to create a simple set of docker containers that reproduce the problem, and also narrow down which 2.2.x version cause the problem.

@tglman So far I have found that the reverse proxy setup works in 2.2.3 but is broken in 2.2.4.  I have a set of docker-compose files which demonstrates both the working and not working versions.  So the bug was introduced in 2.2.4.  I am going to post them somewhere.

It also looks like between 2.2.3 and 2.2.4 is where the streaming functionality was introduced.  For example commit 4a9fec067b03ba576a6a023d60577421c94b60e1.
So I am pretty sure my guess around the issue is correct.

I can confirm that setting network.http.streaming=false resolves the issue, which is what I have done for now.

I have posted a set of docker containers the show the code working in 2.2.3, not working in 2.2.4 and working in 2.2.4 with streaming disabled.
You can check out the project here:
https://github.com/mmacfadden/orientdb-reverse-proxy

Good. So I'm closing this issue, ok?

@lvca I don't know that I would close the issue.  I think there still may be a bug in the new streaming feature.  I have been reading up and using the chunked transfer encoding for HTTP is pretty tricky in a lot of system.  There were a lot of systems that didn't work with streaming HTTP when behind a proxy.  In some cases the proxy was to blame, but in most cases the HTTP Service (e.g. OrientDB in this case) was not 100% implementing the HTTP 1.1 spec properly.
I assume that you all have implemented the streaming feature because you feel it is valuable. At this point I have had to disable it.  I think we should leave it open until we determine if the issue is with OrientDB or NGINX.  Since NGINX is a VERY common system and has supported streaming encoding for a long time, I think it is more likely that there is something not quite right with OrientDBs implementation of the streaming functionality.  Like I said I have seen a lot of systems who implemented streaming for the first time and had an issue with proxying.
I could be wrong though, but until we invetigate a little more,  I wouldn't close the issue, since there could actually be an issue with OrientDB worth investigating.  I do have a workaround for now but I am willing to do some more digging if you are willing to keep the bug open ;-)

If I could put in my 2 cents. Since the root cause hasn't been clearly determined, the issue should stay open, until it is.
Scott

Sorry I thought everything worked by using a flag, but you're right this is still a bug.

@mmacfadden hi tried your docker setup https://github.com/mmacfadden/orientdb-reverse-proxy
and it seems to work fine for me. the "not working" link does in fact work, and this is what i see in the logs:
proxy_1          | 2016/09/16 11:59:00 [warn] 5#5: *5 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/1/00/0000000001 while reading upstream, client: <IP_ADDRESS>, server: localhost, request: "GET /orientdb_2_2_4/studio/scripts/scripts.js HTTP/1.1", upstream: "http://<IP_ADDRESS>:2480/studio/scripts/scripts.js", host: "<IP_ADDRESS>:8080", referrer: "http://<IP_ADDRESS>:8080/orientdb_2_2_4/studio/index.html"

(note: i'm using docker-machine and docker-compose on windows 7 host)

Hi All,
We did some  changes on the support of streaming, and some fixes on the http protocol as well, this should not be a problem anymore from 2.1.10.
do you confirm ?

Unfortunately, it is still an issue with 2.2.12-SNAPSHOT (commit 8373f0b261d196ee8af2c742043a815a88685244) , nginx 1.11.3 and network.http.streaming=true (works fine if false)
nginx log:
[error] 404#0: *57 upstream prematurely closed connection while reading upstream, client: [MYIP], server: [MYSERVER], request: "POST /api/command/devaprint-production/sql/-/20?format=rid,type,version,class,graph HTTP/2.0", upstream: "http://<IP_ADDRESS>:10480/command/devaprint-production/sql/-/20?format=rid,type,version,class,graph", host: "[MYSERVER]", referrer: "https://[MYSERVER]/"

orientdb log:
Remote client connected from: OClientConnection [id=20, source=?, since=1476193675217]
Internal server error:
                                                            java.net.SocketException: Socket closed

@voondo Just so we can start homing in on this.  What OS / Browser are you using.
I was on a Mac primarily using Chrome.  Another of our developers was on Windows with Chrome.  I don't think it has to do with the browser, but just wondering.

@mmacfadden Chrome / Linux

hi @mmacfadden, @voondo,
Can you try the 2.2.14, we fixed some wrong value in flags, the issue should be gone now.
Regards

I will test this out shortly.

hi @mmacfadden,
Any new on this ?
Bye

I got this error in 2.2.17

tested with 2.2.20: all work fine


Crash with cavespider-spawner with no ai

I converted a spawner to cavespiders (using egg from dna from mobgrinder-mod) and added the fruit to remove ai. I also had added a comparator to redstone control it.
The moment the first spider spawned the server crashed.
I have a few other spawners with no ai and no crash.
I tried doing the same in a creative world and my client crashed as soon as the first spider spawned.
Before removing the ai I spawned a few spiders without any crash.
DW20 1.19 v1.1.1 modpack
Apotheosis 6.0.3

Please share the crash log, Use a site lite pastebin for a github gist please

https://pastebin.com/LAKqS8Y9
I noticed that in this pack spiders move differently (more "natural") might be a 1.19, but more likely a mod...

yeah, this is the crashlog when I changed my creative spawner to normal spiders and it crashed the same
https://pastebin.com/UA17bmNy

https://github.com/FTBTeam/FTB-Modpack-Issues/issues/2449
they seem to have some kind of clue how to fix it in the modpack :)
sorry if it wasn't apoteosis fault <3

It caused by a bad interaction with a mixin from https://www.curseforge.com/minecraft/mc-mods/nyfs-spiders, I tested this with a profile with just apotheosis and was able to get cave spiders to spawn fine with no ai, added this mod and crashed when attempting the same

Its more than just cave spiders
crash-2023-02-07_13.40.58-server.txt
crash-2023-02-07_13.19.09-server.txt
crash-2023-02-06_18.50.33-server.txt
crash-2023-02-04_22.39.49-server.txt

The other linked crash is an unrelated CME.  The spider crashes are the fault of the other mod's mixin and I cannot fix them, you'll need to report it to them.


Container running with sysbox-runc runtime not responding

Hi,
We're running several containers, where only one of them is run with sysbox-runc runtime. After some time, the container that is running with the sysbox-runc runtime seem to not work properly, and can't be closed (docker rm -f just hangs until timeout is reached).
Meanwhile, the other containers running with the normal runc runtime works properly.
System information:

Linux ip-172-31-37-92 5.13.0-1017-aws #19~20.04.1-Ubuntu SMP Mon Mar 7 12:53:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Installed shiftfs kernel module based on branch k5.13

Supplying the logs for sysbox-mgr as it does state an error unlike sysbox-fs.
Debug logs from sysbox-mgr.log:
time="2022-04-08 14:00:57" level=info msg="released resources for container 91674898f90d" time="2022-04-08 14:01:04" level=debug msg="dockerVolMgr: created volume for container 8ec38dddb942" time="2022-04-08 14:01:04" level=debug msg="k3sVolMgr: created volume for container 8ec38dddb942" time="2022-04-08 14:01:05" level=debug msg="rke2VolMgr: created volume for container 8ec38dddb942" time="2022-04-08 14:01:05" level=debug msg="autoRemoveCheck: Docker query start for 8ec38dddb942" time="2022-04-08 14:01:08" level=debug msg="FIXME: Got an status-code for which error does not match any expected type!!!: -1" module=api status_code=-1 time="2022-04-08 14:01:08" level=debug msg="autoRemoveCheck: Docker query for 8ec38dddb942 failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" time="2022-04-08 14:01:08" level=debug msg="marked shiftfs for /var/lib/docker/overlay2/138b4468e27813eee3e9190b5ed2ca3eece8035c10bac04ea4a1b0bb5b9c5ad8/merged at /var/lib/sysbox/shiftfs/021301a4-d28b-4d0c-a3de-06c12efb7c02" time="2022-04-08 14:04:22" level=debug msg="unmarked shiftfs for /var/lib/docker/overlay2/138b4468e27813eee3e9190b5ed2ca3eece8035c10bac04ea4a1b0bb5b9c5ad8/merged at /var/lib/sysbox/shiftfs/021301a4-d28b-4d0c-a3de-06c12efb7c02" time="2022-04-08 14:04:22" level=debug msg="kubeletVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:22" level=debug msg="k0sVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:22" level=debug msg="buildkitVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:22" level=debug msg="containerdVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:23" level=debug msg="dockerVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:23" level=debug msg="k3sVolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:23" level=debug msg="rke2VolMgr: sync'd-out volume for container 8ec38dddb942" time="2022-04-08 14:04:23" level=debug msg="added fs watch on /var/lib/docker/overlay2/138b4468e27813eee3e9190b5ed2ca3eece8035c10bac04ea4a1b0bb5b9c5ad8" time="2022-04-08 14:04:23" level=info msg="unregistered container 8ec38dddb942" time="2022-04-08 14:04:24" level=debug msg="rootfsMon: rm on /var/lib/docker/overlay2/138b4468e27813eee3e9190b5ed2ca3eece8035c10bac04ea4a1b0bb5b9c5ad8" time="2022-04-08 14:04:24" level=debug msg="kubeletVolMgr: destroyed volume for container 8ec38dddb942" time="2022-04-08 14:04:24" level=debug msg="k0sVolMgr: destroyed volume for container 8ec38dddb942" time="2022-04-08 14:04:24" level=debug msg="buildkitVolMgr: destroyed volume for container 8ec38dddb942" time="2022-04-08 14:04:24" level=debug msg="containerdVolMgr: destroyed volume for container 8ec38dddb942"
Core dump of sysbox-mgr:
https://easyupload.io/fg546r

@OriGlassman, thanks for filing this issue.
Question. Is this container that appears in the logs above (8ec38dddb942) the one where problem was observed? If that's the case, I wonder if there was something special being done with the dockerd daemon at the time these logs were reported. This log indicates that Sysbox was unable to interact with dockerd during the container initialization, which is something that we don't usually see in docker-based setup like yours, so wondering if this has anything to do with this abnormal behavior.
time="2022-04-08 14:01:08" level=debug msg="FIXME: Got an status-code for which error does not match any expected type!!!: -1" module=api status_code=-1 time="2022-04-08 14:01:08" level=debug msg="autoRemoveCheck: Docker query for 8ec38dddb942 failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" time="2022-04-08 14:01:08" level=debug msg="marked shiftfs for

A few more questions:

Was this a one-off event? Can you reproduce the issue?
Which Sysbox release are you running?

Thanks.

Question. Is this container that appears in the logs above (8ec38dddb942) the one where problem was observed? If that's the case, I wonder if there was something special being done with the dockerd daemon at the time these logs were reported. This log indicates that Sysbox was unable to interact with dockerd during the container initialization, which is something that we don't usually see in docker-based setup like yours, so wondering if this has anything to do with this abnormal behavior.

We're running an environment where we every few minutes remove the container and then start a new one. There are a couple more consecutive messages like these. I guess that after a few times our code that is responsible for creating the new container fails (it says due to timeout with removing the container) and then it stops trying. When trying manually with docker cli, it's indeed in a state where the remove just blocks and nothing happens.

Was this a one-off event? Can you reproduce the issue?

A reboot to the VM releases the blocking situation. It happened several times so we can reproduce it (although the time to reproduce may vary as there isn't seem to be any special event that occurs prior to the problematic behaviour).

Which Sysbox release are you running?

v0.5.0

Question: after the error occurs, can you launch new docker containers (e.g., with the standard runc)?

Yes

Hi @OriGlassman,
Looking at the log you posted:
time="2022-04-08 14:01:05" level=debug msg="autoRemoveCheck: Docker query start for 8ec38dddb942"
time="2022-04-08 14:01:08" level=debug msg="FIXME: Got an status-code for which error does not match any expected type!!!: -1" module=api status_code=-1
time="2022-04-08 14:01:08" level=debug msg="autoRemoveCheck: Docker query for 8ec38dddb942 failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

it's clear that Sysbox is having trouble connecting to Docker engine via its API, though I don't quite understand why.
The FIXME message provides a clue: this message comes from docker engine, here.
This tells me that Docker engine is responding with an error that is not one of the "known" errors. Not sure why though.
A couple of follow ups:

Looks like your host is a Ubuntu Focal VM on AWS, with kernel 5.13, correct?

What version of docker engine are you running on the host (i.e., docker version)?

Looks like your host is a Ubuntu Focal VM on AWS, with kernel 5.13, correct?

Correct

What version of docker engine are you running on the host (i.e., docker version)?

`Client: Docker Engine - Community
Version:           20.10.14
API version:       1.41
Go version:        go1.16.15
Git commit:        a224086
Built:             Thu Mar 24 01:48:02 2022
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.9
API version:      1.41 (minimum version 1.12)
Go version:       go1.16.8
Git commit:       79ea9d3
Built:            Mon Oct  4 16:06:37 2021
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.5.11
GitCommit:        3df54a852345ae127d1fa3092b95168e4a88e2f8
runc:
Version:          1.0.3
GitCommit:        v1.0.3-0-gf46b6ba
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
`

Hi @OriGlassman,
I tried reproducing the problem using the exact same Docker CLI + Engine version you posted above, but was unable to do so. In fact I ran the entire Sysbox test suite (> 100 tests) using that Docker CLI + Engine versions and don't see any sign of the error you are getting.
This, combined with the fact that we've never seen a report of this error before, leads me to think this is an issue specific to your environment, though it's not clear to me what triggers it.
Looking again at the sysbox-mgr log you posted above, it seems the Docker daemon is not responding to the sysbox-mgr's query for 3 secs, at which point the sysbox-mgr times-out and reports the error.
time="2022-04-08 14:01:05" level=debug msg="autoRemoveCheck: Docker query start for 8ec38dddb942"
time="2022-04-08 14:01:08" level=debug msg="FIXME: Got an status-code for which error does not match any expected type!!!: -1" module=api status_code=-1
time="2022-04-08 14:01:08" level=debug msg="autoRemoveCheck: Docker query for 8ec38dddb942 failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

What caused the Docker engine to not respond? I've no idea.
The reason you don't see this with the regular runc is that it never queries Docker back for any info, but Sysbox does.  Nonetheless, I don't believe there is a bug in Sysbox, as the evidence points to Docker not responding via it's API. We just have to figure out why.
Question: when the failure occurs, what other operations was Docker doing at the time? I wonder if it's busy with something and therefore not responding on it's API.

In one environment there were other containers (with runc runtime) which docker restart occasionally and in other environment the only container was with sysbox-runc runtime so basically it shouldn't be busy doing other operations

Hi @OriGlassman, thanks.
Is there anything in the Docker log (e.g., sudo journalctl -u docker) around the time of the failure (time="2022-04-08 14:01:08") that would give a hint on why Docker was not responding via it's API?


Payment Intents support

The notification at the top of Stripe's documentation for Elements indicates that Payment Intents should be used starting September 2019 for all business in Europe https://stripe.com/docs/stripe-js/elements/quickstart.
Additional information on using Payment Intents can be found here https://stripe.com/docs/payments/payment-intents/quickstart.
It looks like all integrations with Stripe should migrate to using this process as soon as possible. I did a quick look on Magento's module and it looks like they are already using Payment Intents. This should make things easier if anything changes with how back-end expects data.

After further testing I'm realizing this is more critical than I initially thought. Since the Magento 2 Stripe module already uses Payment Intent, placing an order with Stripe without using Payment Intent won't work, at least when working with Magento 2 backend.
Unfortunately I don't see an API endpoint in Stripe's module for creating this token, but there is one for resetting the token. I don't think it will work though because it uses the checkout session to get the cart, and I don't think that's dependable via API. So it looks like a new endpoint will be needed for generating the Payment Intent and returning the secret, and then a VSF API will need to be created to middle-man this.
Maybe there's a better solution, but this is what I've found so far.

I spent the past day trying to get this module working with Stripe's Payment Intent with Magento 2, and unfortunately the conclusion that I have come to is that it requires Stripe's official M2 module to either be updated to make it work via API, or you need to extend their module for these updates.
The modifications in this module were pretty straight forward. Mostly involved changing the this.stripe.instance.createToken() call to this.stripe.instance.createPaymentMethod() and then formatting the response in the way their M2 module expects (discussed in issue #17 ). However, these modifications don't do any good until the backend platform (Magento in this case) can process it properly. The method I used is for the "manual" confirmation process because that is what the Magento 2 module uses. There is another way to do "automatic" confirmation process if you want to provide that as an option.
So it seems this issue is either pending Stripe's module to be updated, or requires a Magento 2 module to extend theirs. Alternatively this module could be updated accordingly and have the disclaimer that this module only provides the front-end functionality necessary and in order to use it users will need to have back-end support according to their platform.


feat: control plane repository server conf

This PR adds control plane repository server configuration with Gatling Enterprise private packages enabled.

The current implementation makes the control plane repository server configuration and its variables optional. They are not mandatory.
However, when end user uses the private package module directly by specifying the source argument as the corresponding module file from this repo (source="git::git@github.com:gatling/gatling-enterprise-control-plane-deployment//terraform/aws/location"), they need an interface to assign values to the server's optional configuration.
Otherwise, the end user would have to change the module source code (not recommended) and either:

Download the module code, add/uncomment the server configuration in the corresponding module, and point to their updated module configuration file as the source for the private package module instead of our git source.
Modify the cached version of the module locally before running the main configuration file each time.

Both options are unsuitable for distributing Terraform modules and will add unnecessary complexity. I'm submitting this PR to streamline the process for end users who need to modify their control plane repository server configuration.

I don't think any dev not in vacation atm would be able to review this PR.
Feel free to merge.


stratisd: init at 3.2.1

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

to test:
{
  systemd.packages = [ pkgs.stratisd ];
  services.dbus.packages = [ pkgs.stratisd ];
  services.udev.packages = [ pkgs.stratisd ];
  systemd.services.stratisd.wantedBy = [ "sysinit.target" ];
}

We should move that into a nixos module, right?

We should move that into a nixos module, right?

I'd like to take care of that and add some tests later.

I just noticed that this will not work since both variables are fixed output derivations

There are works on making these fetchers overriable: https://github.com/NixOS/nixpkgs/pull/158018

Can we bush that back until it is figured out how to do that? Right now it is really vague and nothing concrete. Maybe this gets so big that we get a treewide change and convert everything? We don't know yet and I would like to avoid compatibility code for something that might come eventually.


How can I use the Arrow-Up key in the Android RDP app  (useful for getting the last command in a shell)

.

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

ID: 45d9f311-2994-948d-ad91-f5c7370d73ec
Version Independent ID: 5f978676-6f53-3f2d-fabb-3554027edbcc
Content: Get started with Remote Desktop on Android
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/remote-desktop-android.md
Service: unspecified
GitHub Login: @lizap
Microsoft Alias: elizapo

Oh, I found it. Use the keyboard option at the very top and then there is a row with special keys above the normal Android keyboard, scroll to the very right of this row, then tap the 123 button and a keyboard with more options will show up.


lib: posix: support for pthread_attr_setstacksize()

We already support pthread_attr_getstacksize(). It would also make sense to support pthread_attr_setstacksize().
Fixes #44722
(Compliance check is a false positive)

Compliance check is a false positive

Just noticed this:
3: UC4 Line exceeds max length (76>75): "Tests for `pthread_attr_setstacksize(3)` and `pthread_attr_getstacksize(3)`."

Will fix it up

@stephanosio - sorry for the rebase, just wanted to keep line lengths legal. Please ack again when you have a minute.


Investigate hot reload performance benchmark regression with engine roll f56da86

The engine roll in #11219 very significantly regressed hot reload times:

Though it improved hot restart benchmarks:

To reproduce:
cd dev/devicelab
../../bin/cache/dart-sdk/bin/dart bin/run.dart -t bin/tasks/hot_mode_dev_cycle__benchmark.dart

@tvolkert @rmacnak-google

Commits included in that engine roll:
8ba522eea Avoid to freeze the system if hot reloading during debug (#3833)
354d90a95 Add missing virtual methods in PlatformView (#3867)
74d6f6055 Enable text autocorrect on Android with a flag to disable it (#3866)
e385c1b45 [Fuchsia] Pass command line arguments for tracing (#3868)
63bf1d282 a11y: Add SemanticsAction "showOnScreen" (#3856)
a64921e38 Hold the TestRunner's platform view through a shared_ptr (#3870)
79d008ffc Fix engine on iOS (#3871)
9f21bfa9b Fix build, OnHandleReady signature change (#3874)
1db18a40d Revert "Reland "Run Flutter on iOS and Android with color correct Skia (#3826)" (#3878)
f56da86f9 Invert the autocorrect flag (#3875)

In that list, 8ba522eea directly affects hot reload.
/cc @B3rn475

@yjbanov for running the devicelab tests locally and for how we're collecting the data in the relevant benchmarks.

A possible difference introduced by https://github.com/flutter/engine/commit/8ba522eeae35d8c70ada3c7b8e200ca2274f4f95 is that https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/run_hot.dart#L142 will potentially return sooner due to the fact that the RPC invoked inside refreshViews https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/vmservice.dart#L776 doesn't synchronize anymore with the UI Thread

Added repro steps to the issue description.

@B3rn475 it doesn't look like the call to refreshViews() is factored into our benchmark data.
Search run_hot.dart for benchmarkMode to see how to calculate our benchmark data for reload and restart.

@tvolkert refreshViews is not invoked in between timer start and timer stop, but it has a different side effect now.
Due to this change refreshViews is no more waiting for the UI thread to finalize all of its operations.
I can't be sure that this is the actual difference, but before the change refreshViews was ensuring that the UI thread (the one where the Dart Isolate leaves) was idle before starting, now it is not, so potentially we are measuring even the time needed for the isolate to idle.

@B3rn475 I think I just confirmed your theory.  With an arbitrary delay of 5 seconds added immediately after the call to refreshViews() in between our full restart and hot reload, the reported hot reload time went from 3.5s to 1.2s on my local device.
@yjbanov can you work with @B3rn475 to make the appropriate adjustments to our benchmarking?

Sure. How can I help? I'm not familiar with what this benchmark does, but I'm familiar with the benchmark infra, so I can help there.


IBA::resize -- fix precision for double images

The innards of IBA::resize() has to accumulate the weighted
contributions of source pixels under the filter window, and that
accumulator used 'float'. This is fine except when the input image is
'double', in which case you might want just a touch more precision.
So we define an Accum_t typedef template that is double when double is
needed, and float for all other cases. Adds the precision that double
image resize needs, but retains the speed and precision of the prior
float behavior in all other cases.
Fixes #2210

This change fixes it for my use case. Thanks!


Add parameter on Install-Module to AllowClobber

Currently the use of the resource PSModule does not have any parameter to allowClobber.
If there are Cmdlets on the machine that already exist, then the module install with fail.

Yes!!! or be even more general and allow ANY switch parameter to be passed in

closing since this repo is no longer in use.


hasOne creates the right mutation, however API doesn't reflect it

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
8.5.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
I tried to create a relationship between 2 tables so I could get the information from one another, however, when I generate the code, the mutations.ts have the proper code, with the one-to-one relationship, however, the API.ts does not contain that property, so when using the mutation generated in a lambda function, it throws the following error The variables input contains a field name 'createdBy' that is not defined for input object type 'UpdateTradeInput' .
Expected behavior
The expected behaviour was to be able to save into the table and not getting an error?
Reproduction steps

created the schema
created a lambda function
use a graphql request from lambda to call the mutation
returns error

GraphQL schema(s)

# Put schemas below this line

type User @model
  @auth(
    rules: [
      { allow: owner, ownerField: "username" }
      { allow: private, operations: [read, update], provider: iam },
      { allow: groups, groups: ["Admin"] }
    ]
  )
{
  username: String! @primaryKey
  email: String!
  name: String!
  initials: String
  photo: String
}

type Trade @model
  @auth(
    rules: [
      { allow: private, provider: iam },
      { allow: owner, operations: [create] }
      { allow: groups, operations: [read, update, delete], groups: ["Admin"] }
    ]
  )
  {
    id: ID!
    title: String

    createdByUsername: String
    createdBy: User @hasOne(fields: ["createdByUsername"])
}

API.ts

export type UpdateTradeInput = {
  id: string,
  title?: string | null,
  createdByUsername?: string | null,
};

mutations.ts

export const updateTrade = /* GraphQL */ `
  mutation UpdateTrade(
    $input: UpdateTradeInput!
    $condition: ModelTradeConditionInput
  ) {
    updateTrade(input: $input, condition: $condition) {
      id
      title
      createdByUsername
      createdBy {
        username
        email
        name
        initials
        photo
        createdAt
        updatedAt
      }
      createdAt
      updatedAt
      owner
    }
  }
`;

Log output

# Put your logs below this line

Additional information
No response

Hey @rafaelfaria :wave: thanks for raising this! As we begin to look at this issue can you share an example of how you're using the generated type with the API call in your Lambda? From the error it sounds like we may be passing createdBy along with the other defined properties

Hi @rafaelfaria 👋,  Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you.
Thank you!


iOS version requirement?

Hi,
I wanted to try this out, but your podspec has a requirement of iOS 8, but your readme has iOS 6+. Does it really require 8.0?
Thanks

Sorry for the late answer.
CocoaPods requires using frameworks for Swift libraries and frameworks are only available on iOS 8 or later. Nothing in the code requires iOS 8.


Write script which generates GitHub Issues (API) based on RDF errors

This is largely implemented, isn't it?
Just pointing to the affected lines and files is not (as can be seen from #24).

Implemented in: https://github.com/mobivoc/vocol/commit/8b43a8e52e3a1225c4a1515d50e8fd41111ab9d5


Add helper procs

Img procs added that return the image so don't have to create a result (dst) image before calling the procs
Tests file added

Please resolve conflicts.

The png file was causing the conflict.
I have separated that out into another PR.
Conflicts resolved.

It seems that this image is still in this PR.

Also, I think it would be great if you put these convenience procs into a separate module.


Add stack trace to func host start import errors

Hi folks,
it seems like my worker starts fine with func host start but it then encounters a problem with my .js file.
Since it is compiled, I am not sure where it is breaking and not enough information is shown:
[6/6/18 11:37:59 PM] Worker was unable to load function init-store: 'SyntaxError: Unexpected token .'
[6/6/18 11:37:59 PM] Worker fa653417-0a2c-438d-8e6a-278d561bc95f malformed message functionLoadResponse.result.result: string expected
[6/6/18 11:37:59 PM] Worker fa653417-0a2c-438d-8e6a-278d561bc95f uncaught exception:  functionLoadResponse.result.result: string expected
[6/6/18 11:37:59 PM] Worker fa653417-0a2c-438d-8e6a-278d561bc95f exited with code 1

Is there a way to understand which line breaks? Or enable stack traces?

@arichiardi - would you mind sharing a code snippet? Seeing your function.json would also help, since your error is on function load.

The code snippet is ClojureScript compiled down to JS. Here is function.json:
{
  "disabled": false,
  "bindings": [
    {
      "authLevel": "anonymous",
      "type": "httpTrigger",
      "direction": "in",
      "name": "request",
      "methods": [
        "POST"
      ]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "response"
    }
  ]
}

Is there a way to enable the stacktrace for the error?

awesome, thank you! we usually do have the stacktrace along with the error by default. i think you've hit a corner case where we likely don't handle our error gracefully.

I was able to repro your error. I don't know exactly how ClojureScript compiles down, but my guess is that your index.js looks something like this:
module.exports = {
   // Do cool stuff in JS
}

However, to work with the runtime, you should define module.exports equal to a function (can be async, as a side-note). context is not a global object as it differs per function execution, so you'll need to pass it in as a function parameter.
Your index.js should look like this, with at least context passed in as a param, but you could also add request. You can read more here:
module.exports = function(context) {
   // Do cool stuff in JS
}

I will investigate more, but if I check the generated JS it looks similar to what you are writing:
ep_cloud.init_store.http_handler = (function ep_cloud$init_store$http_handler(ctx,request){
 ...
}

I can confirm that node agrees:
> const h = require("./init-store")
> h.toString()
'function ep_cloud$init_store$http_handler(ctx,request){
...

To add an additional data point. The lambdas work individually (I have three of them, I move two to a temp folder temporarily so that only one is loaded - that one works).
In any case I think the problem of this particular issue is that no stacktrace is provided, I will try to debug the other problem and open another issue in case.

are you using one single function.json for multiple functions ("lambdas") that you're trying to invoke? each trigger and entry point should have a corresponding function.json.
one concept that's different from AWS lambda (if that's your background!) is the notion of a "function app" - which is a bundle of one or many functions. this can be especially helpful in trying to answer questions like "should i do one big function or multiple smaller ones". But again, each function.json corresponds to one index.js entry point.
Here's an example of a valid file structure:
    MyFunctionApp
    |     host.json
    |____ business
    |     |____ logic.js
    |____ function1
    |     |____ index.js
    |     |____ function.json
    |____ function2
          |____ index.js
          |____ function.json

In "function1/index.js" and "function2/index.js"
    var logic = require("../business/logic");

    module.exports = logic;

The function.json of function1 and function2 can be configured to different triggers.
In "business/logic.js
    module.exports = function (context, req) {
        // This is where shared code goes. As an example, for an HTTP trigger:
        context.res = {
            body: "<b>Hello World</b>",
            status: 201,
            headers: {
                'content-type': "text/html"
            }
        };
        context.done();
    };

All this just as FYI / to help you in your debugging, we'll still fix printing a stack trace

Yep I am separating like the above but each index.js has basically in theory has its own runtime. So guess this was what I was trying to understand how different is the isolation of Azure lamdbas compared to AWS so thank you for opening the topic for me :smile:
In AWS requiring of the two lamdbas are required in their own node process so that you basically get process isolation effectively and statelessness.
I observed that in the case of func this does not hold true anymore: the two index.js files are required within the same node process.
Can you confirm that? It can be what causes my second issue.

In Azure Functions, you can think of a single function as a combination of a function.json + index.js script entry point. A "function app" is a group of functions and potentially other files of shared code. So each instance of a function app will run on the same process.
So yes, you're right! multiple functions can and do run on the same process

Note that in production, when your functions scale out, you may have multiple instances of function apps running, so multiple processes executing your code. So you shouldn't treat anything as truly global for preserving state, but you certainly can share code. or treat SDK objects, for example, as global.

Closing as issue was resolved on in azure-functions-host. The error message now shows that entry point must be indicated.


token not work

r = requests.post(url, headers=cls._build_headers(token))

TypeError: _build_headers() missing 1 required positional argument: 'token'

I see, there's a bug. I'll fix it.
Thanks for raising

@kennychan07811  please update to latest version and retry, I have a fix for that https://github.com/Vaayne/NotionAI/commit/734b331b38c3a4dc191bf601ffeb3163dc395113

i have the error
def get_spaces(cls, token: str) -> list[dict]:
TypeError: 'type' object is not subscriptable

@kennychan07811  could you try this python script, and check the full result
import os

import requests

TOKEN = os.getenv("NOTION_TOKEN")

def main():
    url = "https://www.notion.so/api/v3/getSpaces"
    headers = {
            "accept": "application/json",
            "Cookie": "; ".join(["token_v2=" + TOKEN]),
            "Content-Type": "application/json",
        }
    r = requests.post(url, headers=headers)
    if r.status_code != 200:
        raise ValueError("Cannot get spaces")
    res = r.json()
    print(res)
    spaces = []
    for _, val in res.items():
        space = val.get("space")
        if space:
            for k, v in space.items():
                space_id = k
                space_name = v["value"]["name"]
                spaces.append({"id": space_id, "name": space_name})
    return spaces

if __name__ == "__main__":
    res = print(main())

"Cookie": "; ".join(["token_v2=" + TOKEN]),

TypeError: can only concatenate str (not "NoneType") to str

It seems that you have not set the TOKEN environment variable correctly. You can replace this with a hard-coded string instead.


[k8s_0.29] Update k8s.io API to version 0.29

Updating the statefulset scaledown controller code to use newer k8s.io API, version 0.29

not ready for review yet, work in progress

It's ready for review now

@luksa, it would be great if you could review and approve, so that other people can take use of this PR, thanks!


Incorporate ontology review changes to PROV-S

@davearcher - you are the reviewer and since we agreed on this, can you review / approve this request AFTER the conflict is resolved.

@davearcher - you are the reviewer and since we agreed on this, can you review / approve this request AFTER the conflict is resolved.

I think this one is good to go, after agentName is removed by @glguy

I think this one is good to go, after agentName is removed by @glguy


fix: Change DialogueView to a mixin class

Description
The DialogueView is responsible for handling and (almost always) displaying the dialog to the user. A very common use case requires the DialogueView to be a PositionComponent or other visual component in the game. This would require extending from both PositionComponent and DialogueView.
Problem: The current DialogueView implementation is an abstract class. Dart does not support multiple inheritance. This means that the case above is difficult to implement.
Solution: Changing the DialogueView from an abstract class to a mixin class allows the developer to extend PositionComponent and mix in DialogueView. The class can now be used as a base class OR as a mixin. All existing tests still pass. An additional test has been added that validates the use as a mixin (extending one class and mixing in DialogueView).
Checklist

[x] I have followed the Contributor Guide when preparing my PR.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[x] I have updated/added relevant examples in examples or docs.

Notes on docs: Updated class docs. Checked doc pages. These still read correctly.
Notes on examples: Currently no jenny examples.
Breaking Change?

[ ] Yes, this PR is a breaking change.
[x] No, this PR is not a breaking change.

Related Issues
NA

Ah, didn't know that was possible, thanks @spydon. Tests still pass, too.


Split properly archived and force archived counters.

Fixes #10082
Status
ready
Description
Splits the archived counter in two separate counters:

One counting the number of workflows that are having the Forcearchived flag set to True (such as Resubmissions) - those workflows basically bypass the whole logic of MSRuleCleaner and are sent directly for archival
The other is counting the workflows that have actually passed through the cleaning pipelines and have reached the archival step (and have been eventually properly archived)

Is it backward compatible (if not, which system it affects?)
YES
Related PRs
No
External dependencies / deployment changes
No

Todor, I haven't reviewed the whole PR because there is still a unit test failing. However, why don't we use a flat structure for self.wfCounters, something like:
self.wfCounters = {'cleaned': {},
                              'properArchived': 0,
                              'forceArchived': 0}}

?
And about naming, I'd suggest normalArchived instead of properArchived.

Hi @amaltaro,
About the naming convention - I agree, your suggestion seems to be better than what I came up with.
About the data structure I believe having them separated as cleaned and archived counters makes things look a little bit better organized, because in they are related to two consequent and well defined steps in the code.
The change about the renaming is on its way. I am about to fix the Unittest   in a separate commit - it is because of the change of the names of those exact counters. Please review the following change I am about to make so I can push the fix for the unit test at the end of the PR.

About the data structure I believe having them separated as cleaned and archived counters makes things look a little bit better organized, because they are related to two consequent and well defined steps in the code.

the key name already contains Archived in it, so it looks clear enough to me. Having a nested dictionary to be used as a counter seems unneeded and error prone to me as well. Anyhow, whatever you prefer.

@todor-ivanov can you please squash those commits? If it's ready to go, please remove the do not merge label as well.

As reminded over slack, next time keep unit tests in its own commit please.


Extract the contents of zip files without redundant folder

I launch eodag with the following eodag.yml configuration
.
onda:
    priority:
    search:
    download:
        extract:
        outputs_prefix: workspace/products/
.

When I use the function to download and extract the products  dag.download_all(products_to_download) I get the following folder structure:

~/workspace/products/product_x.SAFE/product_x.SAFE/*

Is this kind of redundancy  the normal behavior?
Instead what I would like to do is to create a folder with the extracted files (.SAFE) that will have the following structure:

~/workspace/products/product_x.SAFE/*

Is it feasible?

Hello @iliion  and thanks for this feature request. It is feasible and already planned, see #251.
I close this issue and let you follow the existing issue


Visio Diagrams for Architecture Center

It would be great to have access to the Visio Diagrams for all of the Architecture Center Azure patterns.
Where can a Microsoft employee access?

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

ID: 6724a3b3-3c90-3f27-a51d-454819e88f37
Version Independent ID: 0c1b3984-7fbd-70ab-98e1-a2bb7697876b
Content: Profisee master data management with Azure Data Factory - Azure Architectures
Content Source: docs/reference-architectures/data/profisee-master-data-management-data-factory.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 401032

You can browse for specific architecture visio diagrams here:  https://learn.microsoft.com/en-us/azure/architecture/browse/


Update for Pinta 2.1.1

This is a minor bugfix release

Merged; I'll push it to stable when it's built.

Thanks!


AttributeError: 'module' object has no attribute 'events_pending'

Hello everyone,
Since few weeks I am experiencing problem in launching torbrowser, in spite that it was working fine before few weeks. I am on Debian 9 stretch:
#torbrowser-launcher
Traceback (most recent call last):
File "/usr/bin/torbrowser-launcher", line 29, in
import torbrowser_launcher
File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/init.py", line 31, in
from common import Common, SHARE
File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/common.py", line 54, in
gtk2reactor.install()
File "/usr/lib/python2.7/dist-packages/twisted/internet/gtk2reactor.py", line 99, in install
reactor = Gtk2Reactor(useGtk)
File "/usr/lib/python2.7/dist-packages/twisted/internet/gtk2reactor.py", line 73, in init
_glibbase.GlibReactorBase.init(self, gobject, _gtk, useGtk=useGtk)
File "/usr/lib/python2.7/dist-packages/twisted/internet/_glibbase.py", line 119, in init
self._pending = self._gtk.events_pending
AttributeError: 'module' object has no attribute 'events_pending'
Any idea .. I don't remember I changed any python package that could affect tor
thanks in advance

Can you tell us what versions you are running for the following python modules?

twisted
pygtk

The traceback indicates you get as far as gtk2reactor.install() in common.py at which point there is a hand-off from torbrowser-launcher to the Python twisted.internet module and its Gtk2Reactor. So, my first guess is twisted.internet or pygtk updated at some point which triggered this problem, so I want to narrow down the versions before and after to find out what changed and how it's affecting things here.
I'm most familiar with Fedora and Red Hat but I'm happy to throw up a Debian 9 vm and try to isolate the issue.

I checked if I have updated any of these packages, but it seems not.
So pyGTK is installed by debian (2.24), actually pip refuse to install or update pygtk.
Twisted is 16.6.0, exactly as in stretch repositories.

Thanks. I'll try to replicate the issue tonight on a Debian Stretch vm and get back to you when I can.

Oh yeah, what version of torbrowser-launcher do you have installed? Same as Debian Stretch or are you cloning from git?

I am very very sorry. It appeared it is my mistake!! totally user problem.
Few weeks ago I installed vtk on python3 only, and I had to pass the location to pythonpath:
export PYTHONPATH=$PYTHONPATH:/usr/local/lib/python3.5/dist-packages/vtk
apparently vtk conflicted with pygtk in python2 !! and caused the problem !
I am very sorry if I have wasted your time yesterday. Many thanks for the help.


Blob tags are editable in the secondary container

The service should be returning errors when tags are edited from a secondary container, but it doesn't do so. Tag changes do not propagate from the secondary location to the primary. Tag changes in the primary will overwrite any changes in the secondary.

Let's just disable editing tags in the secondary for now.

Verified this issue on the build main/20220324.2. Fixed.
The blob tags can't be edited in the Secondary blob container.


KAFKA-16343: Add unit tests of foreignKeyJoin classes

Added unit tests of two processors included in foreignKey join : SubscriptionSendProcessorSupplier and ForeignTableJoinProcessorSupplier.
Renamed ForeignTableJoinProcessorSupplierTest to SubscriptionJoinProcessorSupplierTest as that's the processor which the test class is testing.

The failing tests are not related.

@wcarlson5 @mjsax In which release will these tests and of course the fix in KAFKA-16394 be integrated?

This PR was merged, and it did go into 3.8 release.


/v1.23/containers/json API returns empty string for NetworkID.

Output of docker version:
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 22:00:43 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 22:00:43 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 62
 Running: 5
 Paused: 0
 Stopped: 57
Images: 57
Server Version: 1.11.2
Storage Driver: zfs
 Zpool: tank
 Zpool Health: ONLINE
 Parent Dataset: tank/docker
 Space Used By Parent:<PHONE_NUMBER>
 Space Available:<PHONE_NUMBER>16
 Parent Quota: no
 Compression: lz4
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: vxlan bridge null host
Kernel Version: 4.4.0-24-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.842 GiB
Name: dc1-dks04
ID: T37Y:UHKY:FDQD:36FE:46U2:I2OV:TPO7:GG5G:KMRA:7FX4:XQRA:TZ5A
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Cluster store: consul://dc1-dks04.in.trilliumstaffing.com:8500
Cluster advertise: <IP_ADDRESS>:2376

Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:

docker run -d busybox sleep 1000
curl --unix-socket /var/run/docker.sock http:/v1.23/containers/json | jq

Describe the results you received:
[
  {
    "Id": "ce43bbddcd79c43797eed177d18b8a0cbdea4827f18b6a0580947d3d2637f508",
    "Names": [
      "/small_yonath"
    ],
    "Image": "busybox",
    "ImageID": "sha256:47bcc53f74dc94b1920f0b34f6036096526296767650f223433fe65c35f149eb",
    "Command": "sleep 1000",
    "Created":<PHONE_NUMBER>,
    "Ports": [],
    "Labels": {},
    "State": "running",
    "Status": "Up 3 minutes",
    "HostConfig": {
      "NetworkMode": "default"
    },
    "NetworkSettings": {
      "Networks": {
        "bridge": {
          "IPAMConfig": null,
          "Links": null,
          "Aliases": null,
          "NetworkID": "",
          "EndpointID": "09bca838a4d3244f2fcc02f3509edd665d75182397e54a8ab0ff12577f8349b3",
          "Gateway": "<IP_ADDRESS>",
          "IPAddress": "<IP_ADDRESS>",
          "IPPrefixLen": 16,
          "IPv6Gateway": "",
          "GlobalIPv6Address": "",
          "GlobalIPv6PrefixLen": 0,
          "MacAddress": "02:42:ac:11:00:02"
        }
      }
    },
    "Mounts": []
  }
]

Describe the results you expected:
The  "NetworkID" field should contain the networkID, not the empty string. The sample in the docs has the NetworkID.

I notice it as well
[{"Id":"6171043c7d573854201495710d320a73d44c007de6a16c4155662e48da1de50b","Names":["/stoic_leakey"],"Image":"docker-dev:rename-error","ImageID":"sha256:c65e430fcd406f4d231adb65df8e8c13cb1272821064135919ee470e0e2f7e8b","Command":"hack/dind bash","Created":1466019354,"Ports":[],"Labels":{},"State":"running","Status":"Up 4 hours","HostConfig":{"NetworkMode":"default"},"NetworkSettings":{"Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"","EndpointID":"55d8acf72c6f186325ad88bebbb711a1a9280aaa268d5adc631addce7e6f297d","Gateway":"<IP_ADDRESS>","IPAddress":"<IP_ADDRESS>","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}}},"Mounts":[{"Source":"/home/sainath/sources/docker-dev/docker","Destination":"/go/src/github.com/docker/docker","Mode":"","RW":true,"Propagation":"rprivate"},{"Name":"48cf622bbc538c1ae8e6b0ba47ef660b39e0792de72c641a9ddd3e5e0beca042","Source":"/var/lib/docker/volumes/48cf622bbc538c1ae8e6b0ba47ef660b39e0792de72c641a9ddd3e5e0beca042/_data","Destination":"/var/lib/docker","Driver":"local","Mode":"","RW":true,"Propagation":""}]}]
Client:
Version:      1.12.0-dev
API version:  1.24
Go version:   go1.5.4
Git commit:   2f7c841-unsupported
Built:        Tue May 10 17:32:30 2016
OS/Arch:      linux/amd64
Server:
Version:      1.12.0-dev
API version:  1.24
Go version:   go1.5.4
Git commit:   2f7c841-unsupported
Built:        Tue May 10 17:32:30 2016
OS/Arch:      linux/amd64
I will take a look.

NetworkID assignment is missing in the daemon code
I will submit a PR #dibs

#dibs


404 README link

A very minor detail, but the link to https://github.com/AthanasiosDelis/img/compare_basis.png is "not found."

Fixed, thanks


Fix Typos in integration tests

Signed-off-by: David Gageot<EMAIL_ADDRESS>

@dmp42 @nathanleclaire Can you take a look at these typos please?

LGTM


Avoid markdown confusion

GitHub was rendering the 1) at the start of this line as a numbered list.

Thanks!


Make maximum visited nodes configurable

To ensure that one can run none-CH in production we need an option to avoid full graph exploration

Is anyone working on this? If not, I can try my hand at it. I am new to grasshopper source code, and this looks like a low hanging fruit

Not in the next days :)
And yes, it should be very similar if not identical to the weight limit

BTW: If you look for other low hanging fruits: have a look into the good first issues :)

Wow, aamazing that you have a tag for this. Definitely helps


Android Build tools version outdated

Every time I re-install my node-modules, I get a warning to update my react-native-sound android build tools version from 23.0.1 to 25.0.0 minimum. Then it works, but i have to keep on doing it every time I have to re-install my modules. Help would be appreciated.
Specifications
React Native (0.44.0)
Android
Windows 10
React Native Sound (4.2.0)

same here


MacOS Sequoia v15 Beta 3: lots of crashes & bugs (after 9 July 2024)

After updating to MacOS 15.0 beta 3, the BlueBubbles apps has tons of new bugs:

It no longer sends photo or videos. On 1.9.7 Server version, photo will always showing waiting for iMessage but will never get sent. On 1.9.8 Beta version server, it will crash the server on Mac
The server kept crashing after updating to 1.9.8 beta version of the server.
FindMy doesnt work, it doesnt show anything on my Android phone BlueBubble app, no friends, no item airtags nothing
Headless mode no longer launch iMessage app on Mac which resulted in Headless mode doesnt work at all.

It's confirmed related to Private API Attachment send. After turning it off, attachments are sent normally. Kindly fix this bug after the new macOS 15 Beta 3

To follow up, here are relevant logs for the crash:
Request to /api/v1/message/attachment took 120011 ms	8/14/2024, 12:28:50 AM

bh: [500] Attachment Send Error at sendAttachment (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:261780) at async validateAttachment (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:292759) at async /Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:302661 at async vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:249951) at async Bh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284522) at async Vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284901) at async qh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284028) at async Vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284901)	8/14/2024, 12:28:50 AM

API Error: [500] Attachment Send Error -> Transaction timeout	8/14/2024, 12:28:50 AM

Raw Error: bh: [500] Attachment Send Error	8/14/2024, 12:28:50 AM

Request to /api/v1/message/attachment took 120014 ms	8/14/2024, 12:27:20 AM

bh: [500] Attachment Send Error at sendAttachment (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:261780) at async validateAttachment (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:292759) at async /Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:302661 at async vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:249951) at async Bh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284522) at async Vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284901) at async qh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284028) at async Vh (/Applications/BlueBubbles (ARM).app/Contents/Resources/app.asar/dist/main.js:1:284901)	8/14/2024, 12:27:20 AM

API Error: [500] Attachment Send Error -> Transaction timeout	8/14/2024, 12:27:20 AM

Raw Error: bh: [500] Attachment Send Error	8/14/2024, 12:27:20 AM

[Messages] [stderr] 2024-08-14 00:26:52.971 Messages[3846:190678] +[IMKClient subclass]: chose IMKClient_Legacy	8/14/2024, 12:26:52 AM

[Messages] [stderr] CoreData: error: addPersistentStoreWithType:configuration:URL:options:error: returned error NSCocoaErrorDomain (256) CoreData: error: userInfo: CoreData: error: reason : Unknown failure to access file: 1 CoreData: error: storeType: SQLite CoreData: error: configuration: (null) CoreData: error: URL: file:///Users/joshuafhiggins/Pictures/Photos%20Library.photoslibrary/database/Photos.sqlite?readonly_shm=1 CoreData: annotation: options: CoreData: annotation: NSSQLitePersistWALOption : 1 CoreData: annotation: NSReadOnlyPersistentStoreOption : 1 CoreData: annotation: NSPersistentStoreTrackIndexUseOptionKey : 0 CoreData: annotation: NSSQLitePragmasOption : { "journal_mode" = WAL; "wal_autocheckpoint" = 0; } CoreData: annotation: NSPersistentHistoryTrackingKey : { NSPersistentHistoryAllowPartialHistoryMigration = 1; NSPersistentHistoryTrackingEntitiesToExclude = ( AssetAnalysisState, MediaAnalysisAssetAttributes, PhotoAnalysisAssetAttributes, ComputedAssetAttributes, SceneClassification, DetectedFaceGroup, Sceneprint, DetectedFaceprint, CharacterRecognitionAttributes, VisualSearchAttributes, GlobalKeyValue, BackgroundJobWorkItem ); NSPersistentHistoryUseContextObjectsForDeletes = 1; }	8/14/2024, 12:26:52 AM

[Messages] [stderr] CoreData: error: Executing as effective user 501 CoreData: error: Information for /Users/joshuafhiggins/Pictures/Photos Library.photoslibrary/database/Photos.sqlite CoreData: error: --------------------------- CoreData: error: File Device ID: 0 CoreData: error: Device ID: 16777232 CoreData: error: File Size: 11685888 bytes CoreData: error: File inode: 51953 CoreData: error: File user ID: 501 CoreData: error: File group ID: 20 CoreData: error: File Permissions: CoreData: error: - CoreData: error: 644 CoreData: error: file is not a symbolic link CoreData: error: Information for file system CoreData: error: --------------------------- CoreData: error: File system type: 0x1a CoreData: error: File system flags: 0x4909080 CoreData: error: MNT_JOURNALED CoreData: error: Total data blocks: 59840624 CoreData: error: Free data blocks: 12295776 CoreData: error: Free blocks for nonsuperuser: 12295776 CoreData: error: Total i-nodes: 492201949 CoreData: error: File system ID: 0x1000010, 0x1a CoreData: error: Free i-nodes: 491831040 CoreData: error: Owner UID: 0 CoreData: error: Filesystem type name: apfs CoreData: error: Mount on name: /System/Volumes/Data CoreData: error: Mount from name: /dev/disk3s5	8/14/2024, 12:26:52 AM

I can help test any patch builds, just lmk.

I do not think the devs are testing at all on Sequoia so I dont think this will be done until offical release. I do think there was quite a few API changes in Sequoia

1.9.8 is not working at all for me on macOS 15.1, but I appreciate that's the gamble with running a beta.  BlueBubbles is the only thing I'm running that isn't working, though, so overall, it is a very stable beta release

thats because apple changed the apis


Add easily visible script version to readme

Why is this needed? Both GM and TM will show you a popup with the version before you install. The master branch is always cutting edge. With this you have to update the version number on two places every time.
:-1:

I have found that TamperMonkey doesn't always update, even when you try to manually. I think it might be cached or something. It would be helpful for users of the script to easily see which is the current version to make sure they are up to date and to leave no doubt that it might be caching an old version. It's a little extra work but it will be quite helpful for people, especially in the group chat when they say to update your scripts.


Special chars cause server errors

Putting almost any special char like : "  ! ... in the search query produces a server error. e.g.
http://bibsoup.net/test/pitman?q=abstract%3A&collection=["pitman"]&size=100&showkeys=abstract&search=Search
http://bibsoup.net/test/pitman?q="Brownian+motion"&collection=["pitman"]&size=100&showkeys=abstract&search=Search
is OK (capability to search for quoted strings should be documented: also capability with * ) but with only one quote it crashes
http://bibsoup.net/test/pitman?q="Brownian+motion&collection=["pitman"]&size=100&showkeys=abstract&search=Search

OK, this will require a custom parser to deal with NASA ADS data,
but this should be made a high priority to write, and it shouldnt be hard, as
generally NASA ADS data is very high quality, and there is a ton of it.
The extent to which NASA ADS metadata can be reprocessed without legal
impediment is not clear. I have approached in the past for cooperation but
never got a response.  I have some connections at Berkeley who will I
expect be interested in the sort of access to NASA ADS data that could
be facilitated by BibServer. Possibly they could be persuaded to host a
BibServer front to NASA ADS if the maintenance burden were low enough.
Or maybe Doug you could encourage the same development at Harvard?
NASA ADS might or might not want to encourage that.
--Jim
Doug Burke<EMAIL_ADDRESS>wrote:

Not sure if this is the same issue, but I suspect it is related. I have a small test sample, exported from a web service (http://adswww.harvard.edu/) at
http://bibsoup.net/djburke/test

which has journal names of "\apj", "\mnras", ... (i.e. these are LaTeX definitions which have not been converted by the exporting program). When I select one of these in the Journal facet I get an Internal Server Error: for example
http://bibsoup.net/djburke/test?collection=["test"]&owner=["d","j","b","u","r","k","e"]&journal.name=["\apj"]&showfacets=collection,type,journal.name,author.name,year&
I can facet on the Author or Year facets, which have more-sensible values in the input BibTeX.

Reply to this email directly or view it on GitHub:
https://github.com/okfn/bibserver/issues/103#issuecomment-3766848

I do not understand why the requirement for a custom parser here. It seems that Doug already has one. All it needs added to it is to add latex handling. Re. the first problem on this ticket, special chars should now be properly dealt with, apart from the ":" in the aforementioned search. I will add a catch for that. (This issue seems to have been accidentally missed or left open after updates to the search box.)

markmacgillivray<EMAIL_ADDRESS>wrote:

I do not understand why the requirement for a custom parser here.
It seems that Doug already has one.

So much the better. But this should be treated generically just like a parser from any other big data source, e.g. DBLP and BibSonomy. We need some expectations/standards for those, and there are the issues of

who is responsible for maintaining the parser?
do we just parse opportunistically as users add small subcollections from the source, or do we aim to convert the entire source?
Presumably this is an issue for the parser maintainer, but it is partly social
and partly technical because the source keeps incrementing. What are the
options for supporting BibJSON export on NASA ADS? That would be a big step
forward politically if it were possible.

Doug, can you All it needs added to it is to add latex handling. Re. the first problem on this ticket, special chars should now be properly dealt with, apart from the ":" in the aforementioned search. I will add a catch for that. (This issue seems to have been accidentally missed or left open after updates to the search box.)

Reply to this email directly or view it on GitHub:
https://github.com/okfn/bibserver/issues/103#issuecomment-3768822

This particular report was purely about the problems in the search, and not the lack of, or need for, support for ADS. I have a Google+ post about possible Astronomical interest at
https://plus.google.com/u/0/112827453273405701734/posts/2fxAyv49xY4

which, if it gets traction, may end up with more requests. Or just changes at the ADS end for it's export capability (maybe to support BibJSON). I should point out that I do not speak for the ADS here.
Thanks, Doug

Understood Doug, thanks for reporting the issue. Please let us know if you have any other problems if you do further tests.


[Feature] Prev/Next links

Description
Doc gen sites like Docusaurus and Nextra typically include a prev/next button at the bottom of each page's content.  These buttons take the user to the adjacent documentation pages (i.e. the previous or next available sidebar item).
Proposed solution
Add two properties to each NgDocNavigation element in the NgDocContext:
prevRoute: NgDocNavigation
nextRoute: NgDocNavigation

Alternatives considered
I've created a component as a workaround.  It flattens the sidebar routes and omits sections that can't be navigated to (e.g. collapsible=true).  Then I render a simple component at the bottom of each page.

export class PageLinksComponent implements OnInit, OnDestroy {
  prevLink: NgDocNavigation | undefined
  nextLink: NgDocNavigation | undefined

  eventSub: Subscription

  constructor(
    private router: Router,
    @Inject(NG_DOC_CONTEXT)
    readonly context: NgDocContext,
  ) {}

  ngOnInit() {
    this.collectRoutes(this.context.navigation)
    this.eventSub = this.router.events.subscribe((event) => {
      if (event instanceof NavigationEnd) {
        const url = event.url.split("#")[0]
        this.prevLink = this.getPrevRoute(url)
        this.nextLink = this.getNextRoute(url)
      }
    })
  }

  // flattens the site's available routes to simplify finding the adjacent routes.
  private collectRoutes(routes: NgDocNavigation[]) {
    routes.forEach((route) => {
      // expandable routes don't have a page to navigate to, so we skip them.
      if (!route.expandable) {
        this.routes.push({route: route.route, title: route.title})
      }
      if (route.children) {
        this.collectRoutes(route.children)
      }
    })
  }

  getNextRoute(url: string) {
    const index = this.routes.findIndex((route) => route.route === url)
    if (index === -1) {
      if (isDevMode()) {
        console.error(`Route not found: ${url}`)
      }
      return
    }
    // if on the last route, there is no next route
    if (index === this.routes.length - 1) {
      return
    }
    return this.routes[index + 1]
  }

  getPrevRoute(url: string) {
    const index = this.routes.findIndex((route) => route.route === url)
    if (index === -1) {
      if (isDevMode()) {
        console.error(`Route not found: ${url}`)
      }
      return
    }
    // if on the first route, there is no previous route
    if (index === 0) {
      return
    }
    return this.routes[index - 1]
  }

  ngOnDestroy() {
    this.eventSub?.unsubscribe?.()
  }
}

Maybe I'd better implement this as a default feature for each page? I think it will be a useful feature


now dev with python on MacOS

Hi, using now dev doesn't work well for python lambdas on MacOS (I'm running MacOS 10.13.6 and now cli 15.8.7)
I'm working on the python example in now examples repo.
If I use now to deploy it, it works fine (now.sh url works fine)
When I use now dev, it starts listening on localhost:3000
If I try to connect a nonexisting path such as localhost:3000/test/test it successfully returns a 404 in browser.
However, when I try to connect localhost:3000 or localhost:3000/index.py the browser gets stuck in loading (terminal logs for now dev looks fine, no errors are thrown, and when I make a request to localhost:3000 or localhost:3000/index.py it starts building the file, and logs as it did build fine, check it below)

Initially I've been using python3.7 (from homebrew) it did not work.
I've tried removing it and installing python3.6.5 via brew, it did not work.
I've tried reinstalling 3.7 via brew, installing pyenv, and creating an env with 3.7 under pyenv, it did not work.
I've tried creating a env with venv file and sourcing  it before using now dev, it did not work.
I've tried reinstalling pip with get-pip.py (priorly I was using the pip/pip3 that came with brew), it did not work
Also, I made sure not to accidentally use python2 (python, python3, pip, pip3 were both linked to python3)
(I mean when it did not work, I received the same error)
I've opened up a docker node:alpine image, installed python3 via apk, installed git via apk, cloned now-examples repo, installed now via npm, ran now dev in the python example. The same situation did happen! (I exposed port 3000 to host machine, and it does start building the python lambda when I make a request, but no response is received)
That's a dockerfile I wrote to make it easily reproducible.
FROM node:alpine
WORKDIR /home/node
RUN apk add git python3 && \
    git clone https://github.com/zeit/now-examples.git && \
    cd now-examples && \
    git checkout add/examples-api && \
    cd python && \
    npm i -g now --unsafe-perm
EXPOSE 3000

(using that build an image and provide a name:tag, then run
docker run -p 3000:3000 --it <localImageName:Tag> sh
cd /home/node/now-examples/python
now dev, the same situation happens)
Later on I've opened up a GCloud f0 micro VM Debian and tried doing the same steps. However, it did work! So, I'm thinking it is related to my host machine or MacOS.

Hi @corupta
The canary channel has updated now dev to use the python3 and pip3 found in the current PATH instead of installing python automatically.
Can you try npm i -g now@canary and also change the now.json file to use @now/python@canary to see if now dev works on your Mac?

We shipped the change to the stable channel.
Please use npm i -g now@latest to install the latest stable version, thanks!


Feature request: Add the ability to talk with window / injected script

Please add the ability to talk with window / injected script, perhaps as another package that extend messaging package?
such as webext-core/window-messaging
then we can call background script even in window context or sending data to window.

Released in v1.4.0


velero server: log version and git SHA at startup

Signed-off-by: Steve Kriss<EMAIL_ADDRESS>We're currently only logging the Git SHA in the server log on startup. Log both the version and the Git SHA.
(Note: prior to #1124 this was actually displaying the version, because FormattedGitSHA() actually showed a version number if it was a tagged commit. A/o 1124 this changed to actually displaying the git SHA. In any case, I'd like to show both)

@nrb this one could go to since it's trivial


List of terms with (Count) instead of Wordcloud

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
TBD
What type of pull request would this be?
New Feature
Any links to similar examples or other references we should review?
No response

#13


Spaceship::UnauthorizedAccessError: Unauthorized Access thrown 8 hours after deployment

The issue:
We've deployed boarding to a Docker container hosted on our internal application platform and we are able to successfully add new Beta Testers after deployment.
However, after about 8 hours, users trying to sign up start to see the following error in the UI:
Something went wrong, please contact the application owner: Unauthorized Access

I checked the application logs after a failed sign up attempt and I see the following:
April 6th 2020, 09:59:14.101 | #<Spaceship::UnauthorizedAccessError: Unauthorized Access>
April 6th 2020, 09:59:14.101 | /usr/local/bundle/ruby/2.6.0/gems/fastlane-2.126.0/spaceship/lib/spaceship/client.rb:844:in `send_request'
April 6th 2020, 09:59:14.101 | /boarding/app/services/boarding_service.rb:57:in `block in add_tester'
April 6th 2020, 09:59:14.101 | Could not add (email address) to app: (our app name)

What I'd like to be able to do:
Deploy boarding in a way that doesn't require frequent maintenance to resolve these issues.
What I've tried:

I've seen some chatter of 2FA being enabled having some impact on this, however, the ITC_USER specified is an App Manager role that does not have 2FA enabled so I don't believe this is related.
I've also tried passing in a valid FASTLANE_SESSION (generated via command line) by setting
export FASTLANE_SESSION=(the fastlane session) prior to bundle exec puma -C config/puma.rb being executed by our app platform. In doing so, I see Session loaded from environment variable is not valid. Continuing with normal login. in the application logs – Googling this leads me right back to the 2FA conversations.

I've also looked through the docs and seemingly related GitHub issues, however, I haven't been able to find anything conclusive.
Thanks in advance for your help in resolving this.

@abardallis did you ever find a solution to this?

@rodgutierrez not by using boarding unfortunately. Ended up just building out a sign up form and calling the App Store Connect API directly. This way the JWT token can be refreshed if needed prior to sending the POST to the /betaTesters endpoint.
Generating JWT tokens for App Store Connect
App Store Connect API docs

thank you @abardallis, this is helpful!


chore: Update CHANGELOG.md

:tada: This PR is included in version 0.11.0-one-repository.1 :tada:
The release is available on:

npm package (@test dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.11.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Exec tachikoma update<PHONE_NUMBER>2103

:hamster::hamster::hamster:   Strategy bundler
Powered by Bundle Update as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage remained the same at 12.651% when pulling ff4af6ef36adb58e42dd510230569c0ac7a16d98 on pazjacket:tachikoma/update-20170719092103 into 00ca8808c8a7964dd2c8eebc60eaeef911e277c1 on Protom512:master.


Merge has caused bookView and updating of window focus type to be lost.

Some calls were replaced with event emissions, and the parent is calling the children's methods. Sometimes clicking on the thumbnail strip no longer updates the canvas.

Darn, I thought I reverted that before I pushed.  Will fix.

Still getting the behaviour in master. Just to make sure we mean the same thing:

This seems to be for #458

Whoops, yep. Sorry.


Add Store.send(_ action:) return StoreTask

I think the addition of Store.send is very innovative because it makes it clear that the View does not need to observe changes in State.
However, I noticed that Store.send is not returning a StoreTask, unlike ViewStore.send.
I want Store.send to also use .task { await store.send(.task).finish() }, just like ViewStore.
Is there any reason why Store.send isn't implemented that way?
If so, you can ignore this PR.
Thanks.

Thanks!


Improve bash-it version output

As we now have "stable" releases and "dev" type of versions, version command should
provide usefull output on that

Thanks for the review @cornfeedhobo :smile:


[docs][hive-transactional-tables] Add hive transactional tables documents.

Proposed changes
[docs] [hive-transactional-tables] Add hive transactional tables documents.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Text within CTA is not aligned within the button

While viewing the site, the user notices that the text within the CTA is not aligned correctly.
The spacing on the left side is more than the right side of the text.

fixed

Verified.


Fix calling deprecated submit()

Summary
Resolves #126
Details and comments
I chose to do this in a way that's compatible with the currently defined min Qiskit version and avoids deprecation warnings for future versions where in PrimitiveJob its now _submit()
I altered the text about an empty class its no longer true when looking at the source, and in the docs it not appear that way at all anyway since it showed all the inherited methods. I also added a note about the why it exists and a TODO as a reminder to potentially revisit this in the future.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 90.583%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
6474

Relevant Lines:
7147

💛  - Coveralls


Vault deafulting to homepage view mode

Summary
Every time i access my homepage, my vault goes to reading mode
Steps to reproduce
I set my homepage in reading mode (homepage plugin settings) for formatting issues but the rest of my vault is set to editing view (obsidian settings->editor) (live preview) for the practicality.
Now every time i acces my homepage, everything goes to reading mode and stops my flow when starting to work on a note.
Is there an easy fix for this? Thanks!
Obsidian info
Settings > Editor: Default view for new tabs, editing mode and live preview
Settings > Homepage: Homepage default view reading mode
Plugins:
Dataview
tasks
Templatr
banners
file tree alternative plugin
homepage
Obsidian version
1.1.8
Checklist

[X] I updated to the latest version of the plugin.

There’s no way to automatically restore the previous mode after going to another note from the homepage, but this is as designed, not a big. I’ll consider adding it as a feature though, as this is probably the more convenient behaviour for most people.