chore: use yarn to run scripts

use yarn instead of npm to run scripts as the repository uses yarn and contributing docs says usage of yarn as well.

I believe it's not necessary to keep consistency here. We recommend using yarn in contributing.md because there're some yarn only features used in this repository. There's no problem using npm in those npm run-scripts. And it would only cause problem if we remove yarn only features in future.

I believe it's not necessary to keep consistency here. We recommend using yarn in contributing.md because there're some yarn only features used in this repository. There's no problem using npm in those npm run-scripts. And it would only cause problem if we remove yarn only features in future.

Agreed 👍🏻

Agreed 👍🏻


Fix dindWithinRunnerContainer not to crash-loop runner pods

Apparently #253 broke dindWithinRunnerContainer completely due to the difference in how /runner volume is set up.

I got the following error when "Runner with DinD" is enabled:
/runner should be an emptyDir mount. Please fix the pod spec.

For now, we can workaround this issue by manually setting the volume as follows:
      image: summerwind/actions-runner-dind
      dockerdWithinRunnerContainer: true
      volumeMounts:
      - mountPath: /runner
        name: runner
      volumes:
      - emptyDir: {}
        name: runner

@int128 Thanks for sharing!


Regenerate proto files using the latest grpc version (dd828651e452295…

…41896bc41cd9cf2f89ac7002a) which has breaking changes to '_API_GetVersion_Handler'
Oh how annoying ... GH broke the commit hash in the title. The latest grpc hash is:
dd828651e45229541896bc41cd9cf2f89ac7002a
All I did was 'make proto'
For some reason, I seemed to need to use sudo ... since I got the following error:
$chown /var/folders/xb/wnfvvcr56cb7px04w56k1jt40000gn/T/protoeasy-input343963475/http: operation not permitted

... without it.

Do it within docker? Also make proto doesn't look like it fully ran as there are now package comments added

Hmmm ... do you have an image preference / an image you usually use to compile proto files?
We just went through docker-izing our proto build process and the assumptions/versions/dependencies for all of that. So, I'm happy to run it if you have a specific image in mind, but if you don't, then perhaps its easier for you to run?
Unless you just use a basic ubuntu image or something.

Ya, the image that is provided with protoeasy, as described in the
protoeasy readme
On Tuesday, April 19, 2016, Sean Jezewski<EMAIL_ADDRESS>wrote:

Hmmm ... do you have an image preference / an image you usually use to
compile proto files?
We just went through docker-izing our proto build process and the
assumptions/versions/dependencies for all of that. So, I'm happy to run it
if you have a specific image in mind, but if you don't, then perhaps its
easier for you to run?
Unless you just use a basic ubuntu image or something.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/peter-edge/proto-go/pull/2#issuecomment-211666575

I did this myself, closing


DBZ-4011 Surge preview teardown

Pending surge.sh preview teardown action https://issues.redhat.com/browse/DBZ-4011

@Naros, I believe you set up the Surge account originally, right? Once this PR has been merged, can you drop all the existing preview environments for any non-pending PRs (i.e. any PRs who got closed before this one, causing the preview env to be left over). Thx!

@Naros, I believe you set up the Surge account originally, right? Once this PR has been merged, can you drop all the existing preview environments for any non-pending PRs (i.e. any PRs who got closed before this one, causing the preview env to be left over). Thx!

@gunnarmorling I can take care of this once the PR is merged.

Excellent, thanks!


Error in commit 58f8f3c with Symfony 2.8

In the last commit there is an error with version Symfony 2.8.
The error is as follows:
[InvalidArgumentException]
The service "snc_redis.command.flush_all" tagged "console.command" must be public.

Thanks for reporting! @romain-pierre was there a reason why you specified public="false" for them?

Hi. Strange that this error have not been reported in tests...
This service definition is only used for sf4.
Probably you can just remove the tag, it will be private in 4: good, public in 2.8: good and public in sf >= 3.1: not needed, should work

Fixed in 2.0.6.

Thanks!


[BUG] Cluster create fails when mounting a volume that contains comma characters in its path

What did you do

How was the cluster created?

k3d cluster create -v /tmp/badly,named,directory:/foobar

What did you do afterwards?
N/A

What did you expect to happen
The cluster should be created with the /tmp/badly,named,directory directory mounted into the k3d container as /foobar
I suspect there is an issue with the parsing from viper. The fix did not look terribly intuitive to me. The easy solution is to rename the directory to something more sane, but let's just say someone many years ago made a really bad naming convention  decision that I have no choice but to live with :(.
Screenshots or terminal output
~|⇒  k3d cluster create --trace --verbose -v /tmp/badly,named,directory:/foobar
DEBU[0000] Selected runtime is 'docker.Docker'
DEBU[0000] Configuration:
agents: 0
image: docker.io/rancher/k3s:latest
network: ""
options:
  k3d:
    disablehostipinjection: false
    disableimagevolume: false
    disableloadbalancer: false
    disablerollback: false
    timeout: 0s
    wait: true
  k3s:
    extraagentargs: []
    extraserverargs: []
  kubeconfig:
    switchcurrentcontext: true
    updatedefaultkubeconfig: true
  runtime:
    gpurequest: ""
registries:
  config: ""
  create: false
  use: []
servers: 1
token: ""
DEBU[0000] Additional CLI Configuration:
cli:
  api-port: ""
  env: []
  labels: []
  ports: []
  volumes:
  - /tmp/badly
  - named
  - directory:/foobar
DEBU[0000] ========== Simple Config ==========
{TypeMeta:{Kind: APIVersion:} Name: Servers:1 Agents:0 ExposeAPI:{Host: HostIP: HostPort:} Image:docker.io/rancher/k3s:latest Network: ClusterToken: Volumes:[] Ports:[] Labels:[] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false PrepDisableHostIPInjection:false NodeHookActions:[]} K3sOptions:{ExtraServerArgs:[] ExtraAgentArgs:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest:}} Env:[] Registries:{Use:[] Create:false Config:}}
==========================
DEBU[0000] Port Exposure Mapping didn't specify hostPort, choosing one randomly...
DEBU[0000] Got free port for Port Exposure: '61956'
TRAC[0000] VolumeFilterMap: map[/tmp/badly:[] directory:/foobar:[] named:[]]
TRAC[0000] PortFilterMap: map[]
TRAC[0000] LabelFilterMap: map[]
TRAC[0000] EnvFilterMap: map[]
DEBU[0000] ========== Merged Simple Config ==========
{TypeMeta:{Kind: APIVersion:} Name: Servers:1 Agents:0 ExposeAPI:{Host: HostIP:<IP_ADDRESS> HostPort:61956} Image:docker.io/rancher/k3s:latest Network: ClusterToken: Volumes:[{Volume:/tmp/badly NodeFilters:[]} {Volume:named NodeFilters:[]} {Volume:directory:/foobar NodeFilters:[]}] Ports:[] Labels:[] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false PrepDisableHostIPInjection:false NodeHookActions:[]} K3sOptions:{ExtraServerArgs:[] ExtraAgentArgs:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest:}} Env:[] Registries:{Use:[] Create:false Config:}}
==========================
WARN[0000] No node filter specified
WARN[0000] No node filter specified
WARN[0000] No node filter specified
DEBU[0000] ===== Merged Cluster Config =====
&{TypeMeta:{Kind: APIVersion:} Cluster:{Name:k3s-default Network:{Name: External:false} Token: Nodes:[0xc0000ee640] InitNode:<nil> ExternalDatastore:<nil> KubeAPI:0xc000787a40 ServerLoadBalancer:0xc0000ee500 ImageVolume:} ClusterCreateOpts:{PrepDisableHostIPInjection:false DisableImageVolume:false WaitForServer:true Timeout:0s DisableLoadBalancer:false K3sServerArgs:[] K3sAgentArgs:[] GPURequest: NodeHooks:[] GlobalLabels:map[app:k3d] GlobalEnv:[] Registries:{Create:<nil> Use:[] Config:<nil>}} KubeconfigOpts:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true}}
===== ===== =====
DEBU[0000] ===== Processed Cluster Config =====
&{TypeMeta:{Kind: APIVersion:} Cluster:{Name:k3s-default Network:{Name: External:false} Token: Nodes:[0xc0000ee640] InitNode:<nil> ExternalDatastore:<nil> KubeAPI:0xc000787a40 ServerLoadBalancer:0xc0000ee500 ImageVolume:} ClusterCreateOpts:{PrepDisableHostIPInjection:false DisableImageVolume:false WaitForServer:true Timeout:0s DisableLoadBalancer:false K3sServerArgs:[] K3sAgentArgs:[] GPURequest: NodeHooks:[] GlobalLabels:map[app:k3d] GlobalEnv:[] Registries:{Create:<nil> Use:[] Config:<nil>}} KubeconfigOpts:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true}}
===== ===== =====
WARN[0000] Failed to stat file/directory/named volume that you're trying to mount: '/tmp/badly' in '/tmp/badly' -> Please make sure it exists
WARN[0000] Failed to stat file/directory/named volume that you're trying to mount: 'named' in 'named' -> Please make sure it exists
FATA[0000] Failed Cluster Configuration Validation:  Volume mount destination doesn't appear to be an absolute path: 'named' in 'named'

Which OS & Architecture

MacOS Big Sur 11.1

Which version of k3d
k3d version v4.2.0
k3s version latest (default)
Which version of docker
docker version:
Client: Docker Engine - Community
 Cloud integration: 1.0.4
 Version:           20.10.2
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        2291f61
 Built:             Mon Dec 28 16:12:42 2020
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.2
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8891c58
  Built:            Mon Dec 28 16:15:23 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  scan: Docker Scan (Docker Inc., v0.5.0)

docker info:
Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 20.10.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.121-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 1.942GiB
 Name: docker-desktop
 ID: MFJE:QWHB:5ADS:G4MW:T7MS:HZQS:6FD6:NQPY:UQFO:RFHI:T4RV:ZCRQ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: gateway.docker.internal:3128
 HTTPS Proxy: gateway.docker.internal:3129
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false
 Product License: Community Engine

@iwilltry42 Wondering if it's possible to avoid path validation with , if we detect that commas are in the string. I'm unsure where the check actually occurs though.

Hi @hrivera-ntap & @nickgerace , it's exactly what you mentioned already:

I suspect there is an issue with the parsing from viper.

Viper doesn't work with the StringArray flags of Cobra (that we used before and where , in the path should be ok (?) ). Thus, we had to switch to StringSlice type flags, which unfortunately also split on , in flag values.
I hope we can switch back very soon (once it's fixed in Viper upstream).
See https://github.com/spf13/viper/issues/246 & https://github.com/spf13/viper/pull/398

Thanks @iwilltry42. I put a comment and will submit a PR there if there's no movement. https://github.com/spf13/viper/pull/398#issuecomment-789131214

I beleive I am experiencing the same problem, but on the --env flag. Here is an example of the k3s command I'm trying to run:
k3d cluster create --verbose --api-port 6443 --servers 1 --agents 3 --env 'http_proxy=http://proxy.com:8080' --env 'https_proxy=http://proxy.com:8080' --env 'no_proxy=localhost,localaddress,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>/8,host.docker.internal,host.k3d.internal' -p 80:80@loadbalancer -p 443:443@loadbalancer --k3s-server-arg '--disable=traefik' local

Here is the verbose output showing how its splitting the no_proxy value:

I guess I could write all this into a config file, but this is part of a larger shell script that is trying to dynamically create the k3d command based on input from a number of sources. Any ideas for workarounds?

IDK if this should fix the --env parsing as well (like here: https://github.com/rancher/k3d/issues/519), but I assume it does not:
❯ HTTP_PROXY="http://blubb:blah@myproxy.com:8080" ./create-test-cluster.sh
k3d version v4.4.1-rc.0
k3s version v1.20.4-k3s1 (default)
FATA[0000] Failed to parse node filters: invalid format or empty subset in 'myproxy.com:8080'

Simply escaping the "@" does not work either (and neither does it work with any env variable w/o an "@").
However, I can work around that issue by suffixing a "@" (and escaping the "@" in the URL):
❯ HTTP_PROXY="http://blubb:blah\@myproxy.com:8080@" ./create-test-cluster.sh
k3d version v4.4.1-rc.0
k3s version v1.20.4-k3s1 (default)
WARN[0000] No node filter specified
# creates cluster...

Or use it in the config file like this:
env:
  - envVar: HTTP_PROXY_DUMMY=http://user:password@some.proxy.com:8080
    nodeFilters:
      - server[*]
      - agent[*]

So anyhow: It seems like k3d requires a node filter all the time, even when there is only one server.

Hi @ederst , that's true :thinking:
When I do e.g. k3d cluster create test --env 'test=foo@bar@servers[0]', it will log FATA[0000] Invalid flag 'test=foo@bar@servers[0]': only one unescaped '@' allowed for node filter(s) (Escape literal '@' with '\').
So yep, @ has to be escaped if it's not used for designating a node-filter.
Also, node-filters are always required, even if there's only one server, as there's also still a loadbalancer (usually), which also counts as a node.

Tried out the new build, and it addresses the original issue for me. Thanks!

The (temporary) fix was released in https://github.com/rancher/k3d/releases/tag/v4.4.1 by using a viper fork, that includes the fix from https://github.com/spf13/viper/pull/398 :+1:
We will revert to upstream viper as soon as this got fixed there.


Fixes #922

Merged as https://github.com/spring-cloud/spring-cloud-stream/commit/516ba13402e035ef9ccb4507e56f25f9ebc0df20


TVMC: Allow to overwrite TVM_CONFIGS_JSON_DIR via environment variables

If a non-default location for the build directory is used, e.g. set via TVM_LIBRARY_PATH
we need to provide the user a way to overwrite CONFIGS_JSON_DIR as well.
This is related to the feature implemented in #11012.

@Mousius

@Mousius done.


should replace all IBitmap

IBitmap will be internal in later version . so，it should replace .
And I will create a PR

Perhaps IImage should be used ? hope soon ~~


Users Public Information {"error":"unauthorized","reason":"You are not authorized to access this db."}

Description
I followed the instructions in the documentation for Users Public Information, but that don't work for me.
Current Behavior
I shared the field "name". I set up the public_fields configuration option with the next command:

curl -X PUT http://localhost:5984/_node/nonode@nohost/_config/couch_httpd_auth/public_fields
-H "Content-Type: application/json"
-d '"name"'
-u admin

I modified this for using in Windows with mi user "epi":

curl -X PUT http://localhost:5984/_node/couchdb@localhost/_config/couch_httpd_auth/public_fields -H "Content-Type: application/json" -d "\"name\"" -u epi

But when i check Jan’s document, CouchDB will respond with:
{"error":"unauthorized","reason":"You are not authorized to access this db."}
I have a user "jan" created in my database _users as can see below:

Also i have "name" in the public_fields configuration option.

Expected Behaviour
When i request a user document with the command:

curl http://localhost:5984/_users/org.couchdb.user:jan

CouchDB will respond with:
{"_id":"org.couchdb.user:jan","_rev":"2-724d8f9af35639db6d96504acda22a25","name":"jan"}
Your Environment

CouchDB version used: 3.1.0
Operating system and version: Windows 10 Pro 1909

This is probably a duplicate of #2881 .
If it's not, please comment and we can reopen.

In this case i want to see public infomation of that user.
I followed the instructions in the documentation for Users Public Information, I shared the field "name". I set up the public_fields configuration option. I should be able to view this information from this user as the documentation shows:
{"_id":"org.couchdb.user:jan","_rev":"2-724d8f9af35639db6d96504acda22a25","name":"jan"}
Issue #1881 doesn't change public_fields in http: // localhost: 5984 / _node / nonode @ nohost / _config / couch_httpd_auth / public_fields

Did you do this first?

@wohali  Thank you for help me, your time is important. It would be helpful if that is included in the oficial documentation. These changes are very relevant and users like me who we are learning about CouchDB from oficial documentation we can get confused.

@hamiltonsalazar Yup, we are tracking that here: https://github.com/apache/couchdb-documentation/issues/513

{"error":"unauthorized","reason":"You are not authorized to access this db."}..but authorisation will be correct

in my case this happened when there is no query activities for several minutes. Is there any session implemented?


[QUESTION] Programatically set cal hooks

Hi,
Out of curiosity, is there a way to configure the middleware that runs in $beforeRoutesInit and $afterRoutesInit without invoking these methods specifically. I am working on creating my own wrapper around tsed and this ability would be perfect
As it stands, I can use configuration and other ways to set specific details but the middleware is throwing me off. Would I simply use the underlying use() method, or something else that needs to be developer?
Michael

Hello @pirouet
You can create you custom configuration key on Server level then consume it in the middleware:
@Configuration({
  myConfig: {}
})
class Server {}

@Middleware()
class MyMiddleware {
  @Constant('myConfig')
  protected myConfig: any;
}

See you
Romain :)

Ah of course, I forgot about the @Constant decorator!
Thank you very much
Michael


[BUG] S3 TestEvent stuck in SQS queue

Describe the bug
The Data Prepper S3 source fails to process s3:TestEvent objects. These remain the SQS queue and are reprocessed over and over again.
To Reproduce
Configure the S3 bucket to send notifications to SQS. It will create an SQS record for s3:TestEvent.
Create an S3 source pipeline in Data Prepper. Run it.
Expected behavior
Data Prepper should recognize the s3:TestEvent and remove it from the SQS queue. It should also not add this to the buffer. Ideally it does output the fact it received it since this can be useful for whomever is running Data Prepper to check that the SQS queue reads work.
Actual Output
2022-10-15T17:09:11,275 [Thread-1] ERROR org.opensearch.dataprepper.plugins.source.SqsWorker - Invalid JSON string in message body of bf803036-5fd3-4857-9db2-d608be440d8d
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "Service" (class org.opensearch.dataprepper.plugins.source.S3EventNotification), not marked as ignorable (one known property: "Records"])
 at [Source: (String)"{"Service":"Amazon S3","Event":"s3:TestEvent","Time":"2022-10-15T16:36:25.510Z","Bucket":"***","RequestId":"***","HostId":"***"}"; line: 1, column: 233] (through reference chain: org.opensearch.dataprepper.plugins.source.S3EventNotification["Service"])
	at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:1127) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:2023) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1700) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperties(BeanDeserializerBase.java:1650) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:540) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1405) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:352) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:185) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4674) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3629) ~[jackson-databind-2.13.4.jar:2.13.4]
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3597) ~[jackson-databind-2.13.4.jar:2.13.4]
	at org.opensearch.dataprepper.plugins.source.S3EventNotification.parseJson(S3EventNotification.java:58) ~[s3-source-2.1.0-SNAPSHOT.jar:?]
	at org.opensearch.dataprepper.plugins.source.SqsWorker.convertS3EventMessages(SqsWorker.java:137) ~[s3-source-2.1.0-SNAPSHOT.jar:?]
	at java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180) ~[?:?]
	at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) ~[?:?]
	at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625) ~[?:?]
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?]
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?]
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) ~[?:?]
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?]
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) ~[?:?]
	at org.opensearch.dataprepper.plugins.source.SqsWorker.getS3MessageEventNotificationRecordMap(SqsWorker.java:132) ~[s3-source-2.1.0-SNAPSHOT.jar:?]
	at org.opensearch.dataprepper.plugins.source.SqsWorker.processSqsMessages(SqsWorker.java:99) ~[s3-source-2.1.0-SNAPSHOT.jar:?]
	at org.opensearch.dataprepper.plugins.source.SqsWorker.run(SqsWorker.java:76) ~[s3-source-2.1.0-SNAPSHOT.jar:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]

Environment (please complete the following information):
Data Prepper 2.1.0-SNAPSHOT from main build.
Additional context
Connecting an S3 Event Subscription to SQS will create this test message.

One possible solution is to have the following condition in the following method,
private List<S3EventNotification.S3EventNotificationRecord> convertS3EventMessages(final Message message) {
        if (message.body().contains("s3:TestEvent") && message.body().contains("Amazon S3")) {
            deleteSqsMessages(Collections.singletonList(buildDeleteMessageBatchRequestEntry(message)));
        }

https://github.com/opensearch-project/data-prepper/blob/a66da8e16ae95bab9b0e86a50af0f7efb6b5b98b/data-prepper-plugins/s3-source/src/main/java/org/opensearch/dataprepper/plugins/source/SqsWorker.java#L135-L143

Here is the body from my SQS queue:
{"Service":"Amazon S3","Event":"s3:TestEvent","Time":"2022-10-15T16:36:25.510Z","Bucket":"bucketname","RequestId":"***","HostId":"***"}

I think it would make sense to try to parse the message like we normally do. Then we can add the condition you have as part of the exception handling.
A couple reasons to recommend this:

I'd prefer that we assume the message is an S3 notification. This way, in the unlikely scenario those strings are in the body somewhere else, we don't let them interfere.
These messages are only created when setting up an S3 notification. This should happen relatively rarely, so we don't have to waste time checking the message for these strings.

Also, I think it is worthwhile to print that Data Prepper received the TestEvent. It could be useful for debugging. Maybe just an INFO line about it.


SvgSvgElement does not have contains method in Internet Explorer

Internet Explorer 11 does not have a 'contains' method for its svg elements.  This causes an error when one attempts to use the contains method on the SvgSvgElement.

It is not planned to PolyFill additional methods for IE-11 only support.
(You can always add the PolyFill yourself in JS)


AzureCLI@2 Task example

On page is desribed argument scriptType as
Select bash/pscore script when running on Linux agent or batch/ps/pscore script when running on Windows agent.
but in example is ps. What is correct?

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

ID: 8de3304e-98f9-bac0-3ccc-c65f68a89e87
Version Independent ID: 8fb2f6a9-545d-dff1-ff86-974694a85054
Content: Azure CLI task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-cli.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @ushan
Microsoft Alias: UshaN

Oh I understood now. Corres value is one of bash pscore ps batch :D


Frontend gets stuck with nothing apparently changed

Home Assistant release with the issue:
➜  ~ hassio ha info
{
    "result": "ok",
    "data": {
        "version": "0.79.3",
        "last_version": "0.80.1",
        "machine": "raspberrypi3",
        "image": "homeassistant/raspberrypi3-homeassistant",
        "custom": false,
        "boot": true,
        "port": 8123,
        "ssl": true,
        "watchdog": true,
        "wait_boot": 600
    }
}

Last working Home Assistant release (if known):
0.79.3
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io 1.3.1
Component/platform:

Description of problem:
Frontend gets stuck
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):
2018-10-17 14:19:18 INFO (MainThread) [homeassistant.components.http.view] Serving / to <IP_ADDRESS> (auth: False)
2018-10-17 14:19:18 INFO (MainThread) [homeassistant.components.http.view] Serving /api/websocket to <IP_ADDRESS> (auth: False)
2018-10-17 14:19:20 ERROR (MainThread) [frontend.js.latest.201809270] https://xxxxxx.duckdns.org:8123/frontend_latest/core-b17de732.js:1:11901 SyntaxError: JSON.parse: unexpected character at line 1 column 17016 of the JSON data

Additional information:
How can it be debbuged?

When I try to lauch hassio commands different of info commands I get forbidden errors:
➜  ~ hassio ha logs
Error decoding json invalid character ':' after top-level value: 403: Forbidden#

And the following is shown in the supervisor log:
18-10-17 13:55:02 WARNING (MainThread) [hassio.api.security] /homeassistant/logs no role for a0d7b954_terminal
18-10-17 13:55:02 ERROR (MainThread) [hassio.api.security] Invalid token for access /homeassistant/logs

Another effect I noted is that when I reload the HA frontend from the browser the following message appears at the bottom left corner: Service system_log/write called.

Hit F12 to check browser console log, you will get slightly better stack trace.

Chrome debugger is showing more detail of the problem:

I am guessing your exception was thrown from here:
https://github.com/home-assistant/home-assistant-js-websocket/blob/5d14aee9cae755d4cc9f5db2d2a82d89ddcb544d/lib/socket.ts#L86
You can enable DEBUG log for websocket_api to check why the websocket message JSON contains invalid character.
# configuration.yaml
logger:
  default: info
  logs:
    homeassistant.components.websocket_api: debug

Yes, that is problem. None in python should serialize to null in JSON

It because the debug message was in python Dict format, not in JSON format.


SubProcess ended with return code:<PHONE_NUMBER> with tensorflow-gpu 2.4.0rc cuda11.0 cudnn8.0.2 on windows 10

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: --
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.4.0rc3
Python version: 3.8.5
Bazel version (if compiling from source): --
GCC/Compiler version (if compiling from source): --
CUDA/cuDNN version: CUDA11.0 cudnn-11.0-windows-x64-v<IP_ADDRESS> graphics driver version: 457.30
GPU model and memory: RTX 3070 8G

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
A lot of I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER> are printed when run tf code on windows 10.
Describe the expected behavior
I have no idea of what the meaning of these logs. And when I ran the same code on other machines with RTX2070s or RTX 2080Ti or GTX1080Ti and tensorflow-gpu 2.3,   these logs hadn't been shown.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
import tensorflow as tf
import numpy as np
from tensorflow.keras import layers
from tensorflow.keras.models import Sequential

physical_devices = tf.config.list_physical_devices('GPU')
tf.config.experimental.set_memory_growth(physical_devices[0], True)

x = np.random.normal(size=(100, 28, 28, 1)).astype(np.float32)
y = np.zeros([100, 10], dtype=np.float32)
y[:, 1] = 1.

train_ds = tf.data.Dataset.from_tensor_slices((x, y)).shuffle(buffer_size=100).batch(32)
num_classes = 10

model = Sequential([
  layers.Conv2D(16, 3, padding='same', activation='relu'),
  layers.MaxPooling2D(),
  layers.Conv2D(32, 3, padding='same', activation='relu'),
  layers.MaxPooling2D(),
  layers.Conv2D(64, 3, padding='same', activation='relu'),
  layers.MaxPooling2D(),
  layers.Flatten(),
  layers.Dense(128, activation='relu'),
  layers.Dense(num_classes)
])
model.compile(optimizer='adam',
              loss=tf.keras.losses.CategoricalCrossentropy(from_logits=True),
              metrics=['accuracy'])
epochs=3
history = model.fit(
  train_ds,
  epochs=epochs
)

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Here is the logs:
C:\Users\dell\Anaconda3\envs\tf24rcpy38\python.exe F:/python_ws/helloworld/main.py
2020-11-25 13:14:29.035547: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2020-11-25 13:14:31.301152: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2020-11-25 13:14:31.301719: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library nvcuda.dll
2020-11-25 13:14:31.330039: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:65:00.0 name: GeForce RTX 3070 computeCapability: 8.6
coreClock: 1.815GHz coreCount: 46 deviceMemorySize: 8.00GiB deviceMemoryBandwidth: 417.29GiB/s
2020-11-25 13:14:31.330233: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2020-11-25 13:14:31.338262: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublas64_11.dll
2020-11-25 13:14:31.338376: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublasLt64_11.dll
2020-11-25 13:14:31.341810: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cufft64_10.dll
2020-11-25 13:14:31.342848: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library curand64_10.dll
2020-11-25 13:14:31.350072: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusolver64_10.dll
2020-11-25 13:14:31.352437: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusparse64_11.dll
2020-11-25 13:14:31.353100: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
2020-11-25 13:14:31.353270: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2020-11-25 13:14:31.357024: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-11-25 13:14:31.357735: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:65:00.0 name: GeForce RTX 3070 computeCapability: 8.6
coreClock: 1.815GHz coreCount: 46 deviceMemorySize: 8.00GiB deviceMemoryBandwidth: 417.29GiB/s
2020-11-25 13:14:31.357961: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2020-11-25 13:14:31.358056: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublas64_11.dll
2020-11-25 13:14:31.358145: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublasLt64_11.dll
2020-11-25 13:14:31.358240: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cufft64_10.dll
2020-11-25 13:14:31.358335: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library curand64_10.dll
2020-11-25 13:14:31.358452: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusolver64_10.dll
2020-11-25 13:14:31.358577: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusparse64_11.dll
2020-11-25 13:14:31.358702: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
2020-11-25 13:14:31.358878: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2020-11-25 13:14:32.004910: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-11-25 13:14:32.005024: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]      0
2020-11-25 13:14:32.005085: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1280] 0:   N
2020-11-25 13:14:32.005286: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1406] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6177 MB memory) -> physical GPU (device: 0, name: GeForce RTX 3070, pci bus id: 0000:65:00.0, compute capability: 8.6)
2020-11-25 13:14:32.006266: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
Epoch 1/3
2020-11-25 13:14:32.533116: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2020-11-25 13:14:32.625497: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublas64_11.dll
2020-11-25 13:14:33.613410: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublasLt64_11.dll
2020-11-25 13:14:33.619608: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
2020-11-25 13:14:35.296892: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code: 0

2020-11-25 13:14:35.310216: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:35.310607: W tensorflow/stream_executor/gpu/redzone_allocator.cc:314] Internal: ptxas exited with non-zero error code -1, output:
Relying on driver to perform ptx compilation.
Modify $PATH to customize ptxas location.
This message will be only logged once.
2020-11-25 13:14:35.320291: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:35.331970: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

# ...(lots of SubProcess ended with return code:<PHONE_NUMBER>)

2020-11-25 13:14:36.014622: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:36.230275: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:36.231899: I tensorflow/stream_executor/cuda/cuda_blas.cc:1838] TensorFloat-32 will be used for the matrix multiplication. This will only be logged once.
2020-11-25 13:14:36.289355: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:36.302906: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

2020-11-25 13:14:36.315136: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

# ...(lots of SubProcess ended with return code:<PHONE_NUMBER>)

1/4 [======>.......................] - ETA: 16s - loss: 2.3410 - accuracy: 0.0000e+002020-11-25 13:14:37.514428: I tensorflow/core/platform/windows/subprocess.cc:308] SubProcess ended with return code:<PHONE_NUMBER>

# ...(lots of SubProcess ended with return code:<PHONE_NUMBER>)

4/4 [==============================] - 7s 591ms/step - loss: 1.7706 - accuracy: 0.5053
Epoch 2/3
4/4 [==============================] - 0s 6ms/step - loss: 0.0604 - accuracy: 1.0000
Epoch 3/3
4/4 [==============================] - 0s 5ms/step - loss: 8.0053e-05 - accuracy: 1.0000

Process finished with exit code 0

I use ...(lots of SubProcess ended with return code:<PHONE_NUMBER>) to represents many lines of "SubProcess ended with return code:<PHONE_NUMBER>" for saving space.

I have the same problem

I have the same problem
System information:
Python version: 3.6.8
tf-nightly-gpu 2.5.0
CUDA11.1
GPU RTX 3070 8G
windows 10

same for me on RTX 3070, testet with cuda 11.0 and 11.1

I have the same error code when a module packaged with pyinstaller 4.1 is spawned as a node child process.
It never goes beyond that line :
model = tf.keras.models.load_model(model_path)

No error is displayed but the exit code shows that there is a problem :
child process exited with code<PHONE_NUMBER>

python 3.7.9
tensorflow-cpu 2.3.1
Windows 10 20H2
Version	19042.630
Windows Feature Experience Pack 120.2212.31.0

I had the same problem on my system with an RTX 3070.
I solved the issue for me as follows:

delete the cuda v.10.1 variable value and change to v.11.1 in the variable name: $Path
after this my pycharm asks for cusolver64_10.dll
I simply copied this from v10.1 to v11.1
now my system is running

The SubProcess ended with return code:<PHONE_NUMBER> error is most likely relates to PTX compiler (ptxas.exe) not supporting your GPU (sm_86) in CUDA <= 11.0.
This issue is tracked at https://github.com/tensorflow/tensorflow/issues/44750 including some workarounds.

@cheshire can you PTAL (also see the internal bug).

@xldrx Thanks, it works.
I follow the suggestions at #44750 and the article:

copy C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin\ptxas.exe into C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\ptxas.exe.

The SubProcess ended with return code:<PHONE_NUMBER> error has gone.

But after replacing the cuda11.0's ptxas.exe with cuda11.1's ptxas.exe, sometimes a error will be raised, then the process end with non zero exit code, here is the log:
2020-12-02 17:19:39.715059: F .\tensorflow/core/kernels/reduction_gpu_kernels.cu.h:847] Non-OK-status: GpuLaunchKernel(CleanupSegments<T*, OUT_T, Op>, new_grid_dim, block_dim, 0, cu_stream, (T*)temp_storage.flat<int8_t>().data(), out, extent_x, extent_y, grid_dim.y, op, init) status: Internal: unspecified launch failure
2020-12-02 17:19:39.715176: E tensorflow/stream_e
Process finished with exit code -1073740791 (0xC0000409)

@SilenceEagle Thanks,I solved the problem according to your method!!!

@xldrx Thanks, it works.
I follow the suggestions at #44750 and the article:

copy C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin\ptxas.exe into C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\ptxas.exe.

The SubProcess ended with return code:<PHONE_NUMBER> error has gone.

Thanks,I solved the problem according to your method!!!

@SilenceEagle,
Closing the issue as it has been resolved. Thanks!

@xldrx Thanks, it works.
I follow the suggestions at #44750 and the article:

copy C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin\ptxas.exe into C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\ptxas.exe.

The SubProcess ended with return code:<PHONE_NUMBER> error has gone.

Thanks,I solved the problem according to your method!!!

worked! Better, would be using the 11.1 cuda version and remove the 11.0.

I had the same problem on my system with an RTX 3070.
I solved the issue for me as follows:

delete the cuda v.10.1 variable value and change to v.11.1 in the variable name: $Path
after this my pycharm asks for cusolver64_10.dll
I simply copied this from v10.1 to v11.1
now my system is running

Hey Can you please email me cusolver64_10.dll file to<EMAIL_ADDRESS>I have cusolver64_11.dll but it asks for 10.
Please it's urgent. Thanks!!

@xldrx Thanks, it works.
I follow the suggestions at #44750 and the article:

copy C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin\ptxas.exe into C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\ptxas.exe.

The SubProcess ended with return code:<PHONE_NUMBER> error has gone.

wow!! thanks!! I solve the problem!!!

The SubProcess ended with return code:<PHONE_NUMBER> error is most likely relates to PTX compiler (ptxas.exe) not supporting your GPU (sm_86) in CUDA <= 11.0.
This issue is tracked at #44750 including some workarounds.

Thanks! It solved my problem!
But my logs still show 'SubProcess ended with return code: 0'
Is there any solution to this problem?
Thank you!

The SubProcess ended with return code:<PHONE_NUMBER> error is most likely relates to PTX compiler (ptxas.exe) not supporting your GPU (sm_86) in CUDA <= 11.0.
This issue is tracked at #44750 including some workarounds.

Thanks! It solved my problem!
But my logs still show 'SubProcess ended with return code: 0'
Is there any solution to this problem?
Thank you!

I think 'return code: 0' means successfully ended the process.

@xldrx 按照这个方法，我的问题还是没得到解决


Pressing X could minimize to taskbar by default?

Pressing the close button on the app window could minimize to taskbar by default? This seems a preferrable solution to me compared to X minimizes to tray because i have just randomly blinking badges next to the tray icon which tell me if there are new messages. this is not very reliable

This is the default behaviour as of 1.3.2. Please try the latest release and re-open the issue if it's not fixed.

I've just rechecked this and indeed, pressing the close button closes the window and only the tray icon is visible. In my opinion, this is the right behaviour because that's what the close button is supposed to do. If you want to minimise it to the taskbar, then use the "minimise" button.

@Aluxian The behaviour you are describing (i.e. "pressing the close button closes the window and only the tray icon is visible") is in Windows, but in Linux (at least on Debian KDE x64) is different: pressing the close button quits altogether the application (of course the tray icon is no more visible). (I'm using release 1.4.2)

@cassiodoroVicinetti The close button exits the app on Linux because the tray icon doesn't work for every distro.


Line/Area Charts w/ Line Interopolation Bulbs don't align

Line/Area Charts w/ Line Interopolation of type bundle the Bulbs don't align
http://www.screencast.com/t/lwC91AF50DYH

This is actually by design: http://bl.ocks.org/mbostock/4342190


[Enhancement Req] - Incorporate "Differential Diffusion"? (Re: Soft inpainting)

Hello!
I'm not a developer so I'm not sure if this even makes sense, but is there any chance this new Differential Diffusion method (https://github.com/exx8/differential-diffusion?tab=readme-ov-file) could be incorporated into your extension (or perhaps even just as a new extension)? I trialed the huggingface demo using an image from my HD and just one of their sample soft-painting masks (Whcih doesn't even match my image). Generating w/ the softpainted mask led to some cool results, and soft painting is now available in both the Forge fork of A1111 and the current release candidate for A1111 v1.8.
Here's their demo: https://huggingface.co/spaces/exx8/differential-diffusion
Thanks for considering if this method could add functionality to the cool extension you've developed here, or perhaps could be incorporated into a stand alone extension for A1111.

I've never used Soft Inpainting myself. But Forge does have a toggle for it in the img2img tab.
Does this Extension not work with it? Or is it missing something?


force:auth:web:login for already-auth'ed user but different alias doesn't update alias (recent regression?)

I had a user report a behavior in IC2 where he added an OAuth connection which uses force:auth:web:login under the hood and that username/alias combination wasn't available afterward. After digging into the logs to see the embedded execution of force:auth:web:login followed by force:org:list, I was able to see that the provided username was in the list from the latter, but it was associated with a different alias than the one provided to force:auth:web:login. I then reproduced this locally on sfdx-cli/7.103.0 win32-x64 node-v14.17.0 by doing the following:
sfdx force:auth:web:login -a alias1 # Log in successfully via browser with username<EMAIL_ADDRESS>sfdx force:org:list                 # shows<EMAIL_ADDRESS>as having alias 'alias1'
sfdx force:auth:web:login -a alias2 # Log in successfully via browser with username<EMAIL_ADDRESS>sfdx force:org:list                 # still shows<EMAIL_ADDRESS>as having alias 'alias1' when it should be 'alias2'

Please let me know if you need more details.

fixed in 7.107.0 https://github.com/forcedotcom/cli/blob/main/releasenotes/README.md#71070-june-24-2021


Modifying CMakeLists to copy libhwloc-15.dll to the binary folder in Windows, independently

References #6394 , #6392
Proposed Changes

Added the HwlocDLL custom target (defined in #6394), used for copying libhwloc-15.dll to the binary folder, directly as a psuedo-target
Hence, the above copy operation is now independent of the examples psuedo-target

Background context
https://github.com/STEllAR-GROUP/hpx/pull/6394#discussion_r1466557733

Can one of the admins verify this patch?

What's the status of this PR?

I have made all the requested changes. Please review....


4 grunt builds

Applied Technical Systems » schematic-js #21 FAILURE
Looks like there's a problem with this pull request
(what's this?)


Custom Categories example from docs does not work

🐛 Describe the bug
I am trying to reuse this example from docs in order to create custom categories but it throws error. Here's my code:
custom_categories = [
    {"cooking": "For users interested in cooking, including recipes, cooking tips, and culinary experiences."},
    {"fitness": "Includes content related to fitness, such as workouts, exercises, and fitness tips."}
]

messages = [
    {"role" : "user", "content" : "Hi, my name is Alice. I love to play badminton."},
    {"role" : "assistant", "content" : "Hello Alice! It's nice to meet you. Badminton is such an amazing sport. How can I assist you today?"},
    {"role" : "user", "content" : "I am a fitness freak, I go to gym daily."},
    {"role" : "assistant", "content" : "That's great! Regular exercise is very beneficial for health."},
    {"role" : "user", "content" : "Because of my gym plan, I mostly cook at home."},
    {"role" : "assistant", "content" : "Cooking at home is a good way to ensure you have a balanced diet."}
]
config = {
"llm":  # defining secrets for llm
"embedder":  # secrets for embedder
}

from mem0 import Memory
m = Memory.from_config(config)
m.add(messages, user_id="alice", custom_categories=custom_categories)

Here's the error I get:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-4-615dd71b2dd0>](https://localhost:8080/#) in <cell line: 1>()
----> 1 m.add(messages, user_id="alice", custom_categories=custom_categories)

TypeError: Memory.add() got an unexpected keyword argument 'custom_categories'

Hello @uahmad235 ,
Mem0 add method does not support this key anymore, docs need updates.
Thanks

Hey @ketangangal
Is this completely deprecated or moved to a different API?

Hey @uahmad235, The doc refers to use custom_categories for the platform and not OSS package. So you can switch to platform by passing api_key in order to use custom_categories.


fixing typo

Hi @4c74356b41, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

Looks good. Thanks. #sign-off


Roll engine 1cada0a6dca6..f15cc3402938 (1 commits)

git@github.com:flutter/engine.git/compare/1cada0a6dca6...f15cc3402938
git log 1cada0a6dca6..f15cc3402938 --no-merges --oneline
2019-09-19<EMAIL_ADDRESS>Roll src/third_party/skia 18531cde2ab7..9a8b846baf43 (1 commits) (flutter/engine#12360)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6738807400955904 , https://cirrus-ci.com/task/4513395866337280 , https://cirrus-ci.com/task/6175857447534592 , https://cirrus-ci.com/task/5639295773179904 , https://cirrus-ci.com/task/5076345819758592 , https://cirrus-ci.com/task/4909220052336640

Commit queue failed; closing this roll.


Qwerty and qwertz layout

Heya, loving it so far - however would you consider implementing a keyboard layout dropdownmenu?
Thanks <3

I've tried testing this by changing my keyboard layout by adding a new keyboard under my language settings, but it seems to still work fine, after all it's simulating the "Z" key to press the lowest note, not "press the key to the right of L shift" or am I confused here?
I can implement it, but it seemed to have worked fine even if I changed it to QWERTZ, DVORAK, AZERTY, etc.

Yeah its a bit weird, when im on the QWERTZ layout the player mixes up the Z and Y, however when I switch over to the US layout and restart the game with the US layout active it is working as intended

Well alright, regardless whether I know it works or not, I'll just add it in. It would be useful when I implement a way to create piano sheet and output it to a text file instead of playing it in the game.

Keyboard layout support was added in v1.3.1


Set KeepAliveTimeout to 620000 (620secs)

Fix 502 error

PTAL! @liayoo

LGTM. Thanks for fixing the issue!

PTAL! @platfowner


Read components.json

I think it would could be handy to replace the url (for cni-[xxx]) to the "$alisases.components" in components.json and then fallback to "@/components/ui" if not defined or if any error.
For example, in my projects, I use "~" instead of "@" and this is the default in many generator (ex: t3 stack)
Thanks for reading 👍

dope idea will look into it in free time, meanwhile feel free to push such updates if doable on your end 😄


Rename to Jam

Renames occurrences of the old "Joinmarket Web UI" to "Jam" as per #22.
I also updated the readme accordingly and added a screenshot.
👉 Readme preview here.
Also, checkout the new theme-responsive readme: 😄
https://user-images.githubusercontent.com/10026790/156028902-62338adb-e01e-4e17-aadb-7e572e17abaf.mov

@theborakompanioni I'd go with the latter. We should keep on communicating the JoinMarket connection.

Regarding JoinMarket in the name, that's what I brought up as well in the naming issue but we eventually settled on keeping it in the tagline. Nothing's set in stone though.

I like Jam - powered by JoinMarket as a short tag-line, and then for the longer form something like Jam - A web UI for JoinMarket with a focus on user-friendliness. The UI aims to provide sensible defaults and be easy to use for beginners while still providing the features advanced users expect.

LGTM!
Any objections to merging?


azure-pipelines.yml: check ci config

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

@commitay What's up, just poking around to see what's going on on Azure? Any thoughts?

Just curious if Azure would be an improvement over Travis for cask taps.
kext-consent is an issue for cask with Travis (https://github.com/travis-ci/travis-ci/issues/9377), if it was disabled switching to Azure might be an option.

@commitay 🆒. Presumably it's the same problem here?

Yes, kext-consent is enabled on Azure.
IMO Azure in general seems to be a little bit nicer and quicker but it doesn't really justify moving the cask taps away from Travis at this stage.


fix: catch permissions error

Console was just showing 500, with no info

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


FINERACT-1442 : Multi-threading-for-savings-interest-posting-job

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

Execution failed for task ':fineract-provider:licenseMain'.
> License violations were found: /home/travis/build/apache/fineract/fineract-provider/src/main/java/org/apache/fineract/portfolio/savings/service/SavingsSchedularInterestPoster.java}

@BLasan , Working on it


travis and codecove config adjusted to new repo location

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6362155). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #10   +/-   ##
========================================
  Coverage          ?   97.4%
  Complexity        ?     104
========================================
  Files             ?      23
  Lines             ?     231
  Branches          ?      29
========================================
  Hits              ?     225
  Misses            ?       4
  Partials          ?       2

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 6362155...d3909d6. Read the comment docs.


push to restore hosted dependencies

We're now using forked git deps for some core libraries (https://github.com/dart-lang/dart-services/blob/master/pubspec.yaml#L15). We'll want to go back to non-forked hosted deps for the analyzer, and possibly git deps for the other packages.

It looks like we're forking three packages:
analysis_server: git://github.com/lukechurch/dart-analysis-server-temp-working.git
analyzer: git://github.com/lukechurch/dart-analyzer-temp-working.git
dart_style: git://github.com/lukechurch/dart_style.git

I'd like to unfork the analyzer package, remove our dep on dart_style, and look at either using a hosted version of analysis_server or invoking the snapshot of it in the sdk.
@lukechurch

@devoncarew See internal thread.

Also see #223

@bwilkerson @stereotype441 @devoncarew @clayberg @danrubel
This is now deforked. Thank you for your help!


Solve #14 - Rename the Mapper to Serialize

Closes #14
Description
In this PR, the Mapper component was renamed to Serialize. For this:

The component was updated
The use cases were updated
The Documentation was updated
The tests were updated

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

68 of 68 (100.0%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
581

Relevant Lines:
581

💛  - Coveralls


SOFABoot HealthCheck disable the actuator exposed endpoints

Background
The Spring Boot Actuator expose some endpoints like this in 1.4.2.RELEASE, but in application exposes these endpoints have secure proplems and may cause secure danger
Solution
In HealthCheck Starter disable the actuator endpoints and only enable these endpoints.
/health
/health/readiness
/sofaboot/versions

But in  SOFABoot we provide config to enable the closed actuator endpoints, such as in SOFABoot configure endpoints.heapdump.enabled=true to enable actuator heapdump endpoints.The enabled configuration should be compatible with actuator.

When upgrade Spring Boot to 2.X, the exposed endpoints are onle info，we should consider the compatible.

@guanchao-yang  Currently,  SOFABoot inherits original configuration from Spring Boot. The users can configure such as endpoints.xxx.enabled to  enable or disable specified endpoint.  Maybe it's not convenient to disable all default endpoints explicitly via SOFABoot，we should follow the usage habit of Spring Boot. They should be configured by user-self.

@QilongZhang We do this only for secure consider and when user use SOFABoot we provide a  secure environment by default

Upgrade Spring Boot version to 1.5.16.RELEASE in SOFABoot v2.5.0，and the sensitive  endpoints have been disabled.

https://github.com/alipay/sofa-build/pull/1


works now with every audio file

rework getRawAudioFromFile so it works with every audio file and converts it to the desired datatype (mono, 32-bit float), plus fixes of my changes

Ok, I am sorry... I was missing the "resampy" python module, never mind.
Thank you for taking the time. Maybe the "resampy" module should be mentioned in a requirements.txt file.
I guess then my contribution will be a requirements.txt file.


Painting fence algorithm

Given a fence with n posts and k colors,this algorithm finds out the number of ways of painting the fence such that at most 2 adjacent posts have the same color.
Since answer can be large return it modulo 10^9 + 7.`

I am interested in learning this algo and implementing it.


Fix package name for proto files

Can't upgrade protobuf to v1.26.0 since proto files across the repo have the same go_package name (https://github.com/owncloud/ocis/blob/master/accounts/pkg/proto/v0/accounts.proto#L3, https://github.com/owncloud/ocis/blob/master/settings/pkg/proto/v0/settings.proto#L4)
Refer https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

@ishank011 would #1875 fix your problem? ;-)

@wkloucek looks good, thanks!


Update Kube version for kubectl download

Did not modify windows kubectl version instructions, as the path for 1.11.2 did not work.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 941cb99c12d195ee81625a4f13198bdcc2cf77ff
https://deploy-preview-7687--docsdocker.netlify.com

@david-yu PTAL to make sure version is accurate for specific versions, or do we want to use generic versions.

@ahh-docker I believe we are on 1.11.5 now due to the CVE vulnerability fix we recently pushed: https://docs.docker.com/ee/ucp/release-notes/

@david-yu if this looks good, let us know and we'll go ahead and merge.


[WIP]:cephcluster: add annotation for each deviceType in cephCR

Signed-off-by: crombus<EMAIL_ADDRESS>

Always run make ocs-operator-ci before pushing, so we don't waste AWS resources. :)
Also, why are we doing this? I thought the CRUSH device type was only for OSDs.

Always run make ocs-operator-ci before pushing, so we don't waste AWS resources. :)

ok.

Also, why are we doing this? I thought the CRUSH device type was only for OSDs.
when I am setting https://github.com/openshift/ocs-operator/blob/136e35698cb4b2bb2172c95bb4fd777847c369e9/pkg/controller/storagecluster/reconcile.go#L428

This is not being reflected in cephclusterCR.

@crombus - just out of curiosity: why is your branch for this PR called validation_test? 🤔

the branch was created to write a test for the deviceType and validate that metadata is bing set.
Doing that I came to know that metadata should be set in cephcluster. So did that first here and second commit will be for test.

/override ci/prow/red-hat-storage-ocs-ci-e2e-aws

/override ci/prow/red-hat-storage-ocs-ci-e2e-aws


WASM Compatibility

Hi @Keruspe,
Thank you for this library.
I was wondering if you are interested in making this library WASM compatible.
At the moment it does not compile for wasm due to the openssl dependency.
I already did it here: https://github.com/Gsantomaggio/amq-protocol/tree/amq-protocol-wasm
git clone  https://github.com/Gsantomaggio/amq-protocol/ .
git checkout amq-protocol-wasm
rustup target add wasm32-unknown-unknown
cargo build --target wasm32-unknown-unknown --release

So the idea would be to split the repository in two repos:

Pure AMQP protocol/types/uri
TCP part ( that I removed here  )

Hi,
I do not understand, it is already split. Also, the TLS part is optional
and master doesn’t use openssl by default anymore
On Wed 3 Feb 2021 at 17:39, Gabriele Santomaggio<EMAIL_ADDRESS>wrote:

Hi @Keruspe https://github.com/Keruspe,
Thank you for this library.
I was wondering if you are interested in making this library WASM
compatible.
At the moment it does not compile for wasm due to the openssl dependency.
I already did it here:
https://github.com/Gsantomaggio/amq-protocol/tree/amq-protocol-wasm
git clone  https://github.com/Gsantomaggio/amq-protocol/ .
git checkout amq-protocol-wasm
rustup target add wasm32-unknown-unknown
cargo build --target wasm32-unknown-unknown --release
So the idea would be to split the repository in:

Pure AMQP protocol
TCP part ( that I removed here
https://github.com/Gsantomaggio/amq-protocol/commit/d84b1169c070edead68047424b8310725652408d
)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CleverCloud/amq-protocol/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABWNXTQLE5GNG7JQMECRKDS5F343ANCNFSM4XBFL7QA
.

Ok, this is maybe my lack of RUST knowledge.
When I include the project:
amq-protocol = { git = "https://github.com/CleverCloud/amq-protocol.git" }

it builds everything.
I will look at how to import only the modules I am interested in.
Thank you

you can pass default-features=true
On Wed 3 Feb 2021 at 18:10, Gabriele Santomaggio<EMAIL_ADDRESS>wrote:

Ok, this is maybe my lack of RUST knowledge.
When I include the project:
amq-protocol = { git = "https://github.com/CleverCloud/amq-protocol.git" }
it builds everything.
I will look at how to import only the modules I am interested in.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CleverCloud/amq-protocol/issues/25#issuecomment-772670443,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABWNXU6BFYSWK6MHRTKI2TS5F7OZANCNFSM4XBFL7QA
.

I meant false obviously
On Wed 3 Feb 2021 at 18:11, Marc-Antoine Perennou<EMAIL_ADDRESS>wrote:

you can pass default-features=true
On Wed 3 Feb 2021 at 18:10, Gabriele Santomaggio<EMAIL_ADDRESS>wrote:

Ok, this is maybe my lack of RUST knowledge.
When I include the project:
amq-protocol = { git = "https://github.com/CleverCloud/amq-protocol.git" }
it builds everything.
I will look at how to import only the modules I am interested in.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CleverCloud/amq-protocol/issues/25#issuecomment-772670443,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABWNXU6BFYSWK6MHRTKI2TS5F7OZANCNFSM4XBFL7QA
.


Github action for check latest release

Description

new github action to check  age of release to support #221

How has this been tested?
Please describe the tests that you ran to verify your changes.

[x] change credsweeper dir, wait 14 days - check again

60 * 60 * 24 * 14 so 14 days or 7 days is a gracious period?

14 + - timezone gap if exists


Refactor Components

Extract all reusable components
Separate Controller components from View components

[x] Forms Extracted <- Controllers
[x] Avatar Extracted
[x] Menus Extracted <- Controllers

[x] buttons extracted


Typo RqPring -> RqPrint

@mvpotter Thanks, someone will review your pull request soon

@yegor256 review this pls (it's a rather short pull request)

@mvpotter thanks!

@yegor256 thank you, added 16 mins to your acc, payment num is 000-f110e2fc, 193 hours and 16 mins spent in total to complete... extra minutes for review comments (c=1)... +16 added to your rating, at the moment it is: +52

@rultor deploy pls

@rultor deploy pls

@davvd OK, I'll try to deploy now. You can check the progress here

@rultor deploy pls

@davvd @mvpotter Oops, I failed. You can see the full log here (spent 6min)
+ status=queued
+ '[' queued == null ']'
+ '[' queued == success ']'
+ '[' queued == failed ']'
+ echo 'waiting for AppVeyor build 2810: queued'
waiting for AppVeyor build 2810: queued
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2810
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2810: running'
waiting for AppVeyor build 2810: running
+ sleep 5s
+ true
++ jq -r .build.status
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2810
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2810: running'
waiting for AppVeyor build 2810: running
+ sleep 5s
+ true
++ jq -r .build.status
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2810
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2810: running'
waiting for AppVeyor build 2810: running
+ sleep 5s
+ true
++ jq -r .build.status
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2810
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2810: running'
waiting for AppVeyor build 2810: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2810
++ jq -r .build.status
+ status=failed
+ '[' failed == null ']'
+ '[' failed == success ']'
+ '[' failed == failed ']'
+ echo 'see https://ci.appveyor.com/project/yegor256/takes/build/2810'
see https://ci.appveyor.com/project/yegor256/takes/build/2810
+ exit 1
container ea5f21a5fb59a4161bce7468b8fe933f3dd1002b80e4013d8388a8c0f975a54d is dead
Wed May 10 14:57:48 UTC 2017


SNI support

Regardin SNI support you requested in zevenet project, have you checked SKUDONET? SNI is totally supported and SKUDONET is the fork of ZEVENET managed by the same Team.

Thanks, I switched to SKUDONET :-)


[Spark 1.6.0]ClassCastException: java.lang.String cannot be cast to org.apache.spark.unsafe.types.UTF8String

I read two geojson files(lines and points) as dataframes,
then i created buffer dataframe from the points.
I can see the geometries, but when i tried to do join between them and print the result i got this exception.
The data is valid, because before the join i can print the features of the layers well.
i tried to add option("charset", "UTF8") and also UTF16.
I saw this error in other package:
https://github.com/databricks/spark-csv/issues/206
https://github.com/databricks/spark-csv/issues/64
I am running it on windows, but connect to remote HDFS.
In Addition, i compiled the package(SparkGIS) to scala 2.10.5 instead of using scala 2.11 (All the tests pass)

Can you provide some excerpt of your code and data for a reproduction ?

Hi,
Thank you for answering so quickly.
I will add the it tomorrow.
Thanks.
On Mar 30, 2016 2:50 PM, "Emiliano Leporati"<EMAIL_ADDRESS>wrote:

Can you provide some excerpt of your code and data for a reproduction ?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/drubbo/SparkGIS/issues/8#issuecomment-203394913

Update:
I wasn't able to recreate the bug, so i close it.

I' having similar issues when creating a custom datasource.
Schema: 		StructType(Seq(StructField("Date", LongType), 			StructField("Device", StringType), 			StructField("Tag", StringType), 			StructField("TagValue", DoubleType)) 		)
Stack ob aborted due to stage failure: Task 0 in stage 2.0 failed 1 times, most recent failure: Lost task 0.0 in stage 2.0 (TID 2, localhost): scala.MatchError:<PHONE_NUMBER> (of class java.lang.Long) 	at org.apache.spark.sql.catalyst.CatalystTypeConverters$StringConverter$.toCatalystImpl(CatalystTypeConverters.scala:295) 	at org.apache.spark.sql.catalyst.CatalystTypeConverters$StringConverter$.toCatalystImpl(CatalystTypeConverters.scala:294) 	at org.apache.spark.sql.catalyst.CatalystTypeConverters$CatalystTypeConverter.toCatalyst(CatalystTypeConverters.scala:102) 	at org.apache.spark.sql.catalyst.CatalystTypeConverters$$anonfun$createToCatalystConverter$2.apply(CatalystTypeConverters.scala:401) 	at org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:59) 	at org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:56) 	at scala.collection.Iterator$$anon$11.next(Iterator.scala:328) 	at scala.collection.Iterator$$anon$14.hasNext(Iterator.scala:389) 	at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:327)

I am also facing the same issue while creating a custom data source.

Is there some update on this?


v1.1.7 menu problem

Hi,
I downloaded and activated the update.
Thanks for the update but the menu does not populate.
There is no menu action on clicking the button...just a link to https://mrneilypops.org/# (??)

@mrneilypops just updated the readme https://github.com/tomasdev/ghost-casper-plain/blob/master/README.md seems you're missing jQuery.


[Errno 10061]

Hello,
I run mqtt.py with python and I receive this error. Can you help me?
[2018-06-25 17:14:31,868] DEBUG Connected to RM2 Broadlink device at '<IP_ADDRESS>' (MAC 78:0f:77:00:b6:34)
Traceback (most recent call last):
File "C:\Python27\broadlink-mqtt-master\mqtt.py", line 385, in
mqttc.connect(cf.get('mqtt_broker', 'localhost'), int(cf.get('mqtt_port', '1883')), 60)
File "C:\Python27\lib\site-packages\paho\mqtt\client.py", line 768, in connect
return self.reconnect()
File "C:\Python27\lib\site-packages\paho\mqtt\client.py", line 895, in reconnect
sock = socket.create_connection((self._host, self._port), source_address=(self._bind_address, 0))
File "C:\Python27\lib\socket.py", line 575, in create_connection
raise err
error: [Errno 10061] No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión

Could you please show your configuration? Did you get it once or every time?

OK, this is my configuration. I try to use direct connection but have the same error. I get it once.
Type of device. Valid options are 'lookup', 'multiple_lookup', 'rm', 'sp1', 'sp2', 'a1', 'mp1'
device_type = 'lookup' # use lookup
lookup parameters
lookup_timeout = 20
#local_address = '<IP_ADDRESS>'
parameters for direct connection
#device_host = '<IP_ADDRESS>'
#device_mac  = '78:0f:77:00:b6:34'
MQTT connection parameters
mqtt_broker = 'localhost'       # default: 'localhost'
mqtt_port = 1883                # default: 1883
mqtt_clientid = 'broadlink'
mqtt_username = ''
mqtt_password = ''
mqtt_topic_prefix = 'broadlink/'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/' # use only with 'multiple_lookup' device type (allowed parameters are {type}, {host}, {mac}, {mac_nic})
MQTT TLS parameters
Required with TLS: a string path to the Certificate Authority certificate files that are to be treated as trusted by this client.
ca_certs = '/path/to/ca_certsfile'
Optional Clients Cert/Key
certfile = '/path/to/certfile'
keyfile  = '/path/to/keyfile'
Required TLS version. Valid values: 'sslv3', 'tlsv1', 'tlsv1.2'
tls_version = 'tlsv1.2'
extra parameters
broadlink_rm_temperature_interval = 120 # publish temperature from RM device to broadlink/temperature topic every two minutes
broadlink_sp_energy_interval = 30 # publish energy from SP device to broadlink/energy topic every 30 seconds
broadlink_a1_sensors_interval = 30 # publish all sensors data from A1 device to broadlink/sensors/[temperature/humidity/light/air_quality/noise] topics every 30 seconds
broadlink_a1_sensors_text_values = False # use True to send text representation of light/air quality/noise values
broadlink_a1_sensors_json = False # False to send every sensor parameter in separate topic, True - to send all together as JSON object

Thanks
Did you try using Broadlink application on the mobile phone?

Yes, it is ok

Then error looks weird
It could be related to the network connectivity problem
Is it possible to ping <IP_ADDRESS> from your computer?

Oh, sorry
There is an error with connection MQTT broker, not Broadlink device
Do you have MQTT broker run on local or any other computer in your network?

I need to open the 1883 port in firewall? I opened it in tcp protocol

Sorry,
you said you have mqtt broker at another computer
You have to specify the address of that computer in the mqtt_broker config parameter
By default it has "localhost"

I put the same ip of the computer, but i have the same error...
mqtt_broker = '<IP_ADDRESS>'       # default: 'localhost' mqtt_port = 1883                # default: 1883 mqtt_clientid = 'broadlink'

Sorry, I put the ip and the port correctly (150).
Now I have another error (debug oooops! broadlink disconnects), then I'm going to close this issue and open another if I don't find in another issues.

PLease check issue #7 , it could be related


Http Middleware

Do we want to use redux middleware to interact with various API's?
http://redux.js.org/docs/recipes/ReducingBoilerplate.html
I'm not quite sure how much this buys us, but it could be nice to not have to do the fetch -> then ->  catch in our action creators.

Yeah. Another good reason to do this is if we have a REST API vs WebSocket vs GraphQL setup. Each deployment can then choose which middleware to use.


Validation for Phone Number and Date in "Book-Table" page

Description
The validation for date and phone number isn't done. The table gets booked for a past date and the phone number gets accepted if the number of digits is less than 10. I would like to work on this issue.
Screenshot

I am a GSSOC'24 Contributor

@khushi-joshi-05 can I work on this issue?


chore: update docs link

Summary
thewidlarzgroup.github.io/react-native-video -> docs.thewidlarzgroup.com/react-native-video
Motivation
Updated all references to the documentation link throughout the entire application
Changes
Replaced documentation links
Test plan

@moskalakamil is this PR still this draft ?

@moskalakamil is this PR still this draft ?

Hey @KrzysztofMoch, yes - I need to check one more thing

@KrzysztofMoch ready 👍

@moskalakamil I think you missed some files

@freeboub thanks for vigilance! I'll check this tomorrow

Updated


[FeatureRequest] Add a Cancel method

Hi,
thank you for this awesome class !
I needed a way to cancel the callback, and I think it could benefit other people too.
I did it by adding an Enabled property that is set to True in Init and checked in DataObject_Clear
Private Sub DataObject_Clear()
    If (Not m_data Is Nothing) Or (Not Enabled) Then Exit Sub 'Ignore external logic attempts

I also added a Cancel sub that set Enabled to False but that's not really necessary.
Maybe there is a better way that actually cancel the callback instead of just making it exit immediately ?

Thanks @thefasquelle for the kind words and the feedback!
Your approach is probably what I would also do. The alternative would be to restore the correct IUnknown:Release and IUnknown:AddRef pointers in the virtual function table for the DataObject interface while also correcting the reference count.
Will try to do some work on this class in the next few weeks.
The biggest problem with this class is that the callback does not work when End is called while code is running - this might be something that has no solution but will see.

The biggest problem with this class is that the callback does not work when End is called while code is running - this might be something that has no solution but will see.

yeah, the main reason I used this callback is for unhandled errors where user press the End button. Sadly it does not work And I would be surprised you can do it without hacking into the VBA runtime itself (like vbWatchdog does). At least it works when using the stop button, which happens a lot when your users are also developers !

Thanks for the suggestion! Added a Cancel method.


SafeArea widget is Ignored while using this package

SafeArea widget is totally Ignored when i try to use this package

SafeArea add this:
SafeArea(
top: false,


[FEATURE][Forge 1.1.5] Dependencies are not declared for this specific version on the CurseForge page

Upon installing the mod through the CurseForge launcher, it will not install the dependencies, causing crash on startup. Just a human error, it happens. Still figured I should point it out. Great mod <3

Snek

Thanks for pointing it out, fixed now!


[Bugs] AMF panics at HandleRegistrationComplete when Mobility/PeriodicUpdateRegistration

Describe the bug
AMF panics at HandleRegistrationComplete() when Mobility/PeriodicUpdateRegistration.  We believes that HandleRegistrationComplete() is trying to refer RegistrationRequest's data but that is cleared before hand.
The fix is not call ue.ClearRegistrationRequestData(anType).
To Reproduce
Handle Mobility/PeriodicUpdateRegistration.
Expected behavior
No panic.
Environment (please complete the following information):

free5GC Version: 3.0.4
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version: 1.14.4 linux/amd64

Pull Request
Pull Request for the fix.

The PR has been merged.
Thanks for the contribution!!! 👍


Update to use gorm.io

@ghoti143, @Br3nda is there a plan to merge this pr and publish a release?

@Br3nda @ghoti143 Please just click that merge button! The module is completely broken without it

@jinzhu 👆


Added Python Code for Number of Connected Components In An Undirected…

You made a video for this in python but there's no code for it in your website.

Thank you so much!


problem reloading VSC

ADD ISSUE DESCRIPTION HERE
Unable to open '124208192'
Unable to resolve resource vscode-remote://codespaces%2Bfitjenzaulrich-symmetrical-system-9vgq5pr9rvgf75vx/workspaces/124208192
Version: 1.76.2
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0
Embedder: codespaces

It looks like this is caused by the Codespaces extension. Please file the issue in the Codespaces Discussion Forum. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Add Tests for components

After the great work done by @nathanmarks with the tests we should now go ahead and make unit tests for each component to ensure their integrity :+1:
This is the list of all components that need unit tests:
Components:

[ ] [AppBar] app-bar: #3487 @pradel
[ ] [AutoComplete] auto-complete
[ ] [Avatar] avatar: Partial: (#3405 @nathanmarks)
[x] [Badge] badge: #3427 @pradel
[ ] [FlatButtonLabel] buttons/flat-button-label
[ ] [Card] card/card
[ ] [CardAction] card/card-actions
[ ] [CardExpandable] card/card-expandable
[ ] [CardHeader] card/card-header
[ ] [CardMedia] card/card-media
[ ] [CardText] card/card-text
[ ] [CardTitle] card/card-title
[ ] [Checkbox] checkbox
[ ] [CircularProgress] circular-progress
[ ] [Calendar] date-picker/calendar
[ ] [CalendarMonth] date-picker/calendar-month
[ ] [CalendarToolbar] date-picker/calendar-toolbar
[ ] [CalendarYear] date-picker/calendar-year
[ ] [DateDisplay] date-picker/date-display
[ ] [DatePicker] date-picker/date-picker
[ ] [DatePickerDialog] date-picker/date-picker-dialog
[ ] [DatePickerInline] date-picker/date-picker-inline
[ ] [DayButton] date-picker/day-button
[ ] [YearButton] date-picker/year-button
[ ] [Dialog] dialog
[ ] [Divider] divider
[ ] [DropDownMenu] DropDownMenu/DropDownMenu
[ ] [EnhancedButton] enhanced-button
[ ] [EnhancedSwitch] enhanced-switch
[ ] [EnhancedTextarea] enhanced-textarea
[ ] [FlatButton] flat-button
[ ] [FloatingActionButton] floating-action-button
[ ] [FontIcon] font-icon: #3490 @pradel
[ ] [GridList] grid-list/grid-list: #3488 @pradel
[ ] [GridTitle] grid-list/grid-tile
[ ] [IconButton] icon-button
[ ] [InkBar] ink-bar
[ ] [LeftNav] left-nav
[ ] [LinearProgress] linear-progress
[ ] [List] lists/list
[ ] [ListItem] lists/list-item
[ ] [NestedList] lists/nested-list
[ ] [IconMenu] menus/icon-menu
[ ] [Menu] menus/menu
[ ] [MenuItem] menus/menu-item
[ ] [Overlay] overlay
[ ] [Paper] paper
[ ] [Popover] popover/popover
[ ] [PopoverAnimationFromTop] popover/popover-animation-from-top
[ ] [PopoverDefaultAnimationp] popover/popover-default-animation
[ ] [RadioButton] radio-button
[ ] [RadioButtonGroup] radio-button-group
[ ] [RaisedButton] raised-button
[ ] [RefreshIndicator] refresh-indicator
[ ] [RenderToLayer] render-to-layer
[ ] [CircleRipple] ripples/circle-ripple
[ ] [FocusRipple] ripples/focus-ripple
[ ] [TouchRipple] ripples/touch-ripple
[ ] [SelectField] SelectField/SelectField
[ ] [Slider] slider
[ ] [SnackBar] snackbar
[ ] [Subheader] Subheader/Subheader
[ ] [SvgIcon] svg-icon: #3489 @pradel
[ ] [Table] table/table
[ ] [TableBody] table/table-body
[ ] [TableFooter] table/table-footer
[ ] [TableHeader] table/table-header
[ ] [TableHeaderColumn] table/table-header-column
[ ] [TableRow] table/table-row
[ ] [TableRowColumn] table/table-row-column
[ ] [Tab] tabs/tab
[ ] [Tabs] tabs/tabs
[ ] [TabTemplate] tabs/tabTemplate
[ ] [TextField] TextField/TextField
[ ] [TextFieldHint] TextField/TextFieldHint
[ ] [TextFieldLabel] TextField/TextFieldLabel
[ ] [TextFieldUnderline] TextField/TextFieldUnderline
[ ] [Clock] time-picker/clock
[ ] [ClockHours] time-picker/clock-hours
[ ] [ClockMinutes] time-picker/clock-minutes
[ ] [ClockNumber] time-picker/clock-number
[ ] [ClockPointer] time-picker/clock-pointer
[ ] [TimeDisplay] time-picker/time-display
[ ] [TimePicker] time-picker/time-picker
[ ] [TimePickerDialog] time-picker/time-picker-dialog
[ ] [Toggle] toggle
[ ] [Toolbar] toolbar/toolbar
[ ] [ToolbarGroup] toolbar/toolbar-group
[ ] [ToolbarSeparator] toolbar/toolbar-separator
[ ] [ToolbarTitle] toolbar/toolbar-title
[ ] [ToolTip] tooltip

Utility Components:

[ ] [ClickAwayListener] ClickAwayListener
[ ] [muiThemeable] muiThemeable
[ ] [MuiThemeProvider] MuiThemeProvider
[ ] [ScaleIn] transition-groups/scale-in
[ ] [ScaleInChild] transition-groups/scale-in-child
[ ] [SlideIn] transition-groups/slide-in
[ ] [SlideInChild] transition-groups/slide-in-child

Styles:

[ ] [getMuiTheme] styles/getMuiTheme.js
[ ] [AutoPrefixerTransformer] styles/transformers/autoprefixer.js
[ ] [RtlTransformer] styles/transformers/rtl.js
[ ] [Transitions] styles/transitions.js

Since testing is an ongoing activity, my recommendation for this issue is that maybe we shoot for a general percentage of coverage for 0.15.0 and improved level of coverage for 0.16.0. Maybe like 70% in 0.15.0, 85% in 0.16.0. We'll see how much progress we make with @pradel's work.

@alitaheri BTW, the Avatar component could still do with a few more tests.
I don't want people to misinterpret the checked boxes as meaning, "this is perfectly tested", because at this stage the important thing is to get some basic test coverage on all the components rather than having perfect tests for half of them.

I don't want people to misinterpret the checked boxes as meaning, "this is perfectly tested", because at this stage the important thing is to get some basic test coverage on all the components rather than having perfect tests for half of them.

Yup, these are my thoughts exactly. Technically this task is never finished, but setting some internal goal would be good for all the components.

@newoga @alitaheri What do you want to test in terms of styling?
Additionally, just a side not, but it's important not to confuse 100% coverage with 100% bulletproof ;)

Additionally, just a side not, but it's important not to confuse 100% coverage with 100% bulletproof ;)

I agree, but it the numbers definitely help keep us accountable. :smile:

And ensure that the components actually do something :dancer:

I will have more time after this week btw to contribute more, just one of those weeks at the office ;)

That's great, thanks much @nathanmarks!  I've having one of those weeks as well.

By styles I mostly refer to transformers working as expected. I'll try to come up with something to reflect goal coverage :grin:

Awesome!
PS, is there a convention in place for the naming of exporting the plain components for those that have an HoC wrapping the default export?

Not really, but it would be great if there was. How about exporting as Raw or the wrapped one as default and the raw one as itself, so like: TextField?

That was my initial thought, but I was wondering if it makes it too easy to export the wrong component by accident.  Anyone else? @newoga @oliviertassinari?
import Component from 'material-ui/lib/Component';
import { Component } from 'material-ui/lib/Component';

Yeah...
import Component from 'material-ui/lib/Component';
import { Raw as Component } from 'material-ui/lib/Component';

Might be harder to get wrong, right? wrong?

700% harder to get wrong.

Yeah I need to give this more thought. I haven't thought of something I'm completely happy with. Though maybe it will make sense when we reorgnize.
import Component from 'material-ui/lib/Component';
import { Component } from 'material-ui/lib/Component';

I think the approach above shouldn't return differently, that could be confusing.
import Component from 'material-ui/lib/Component';
import { Raw as Component } from 'material-ui/lib/Component';

I think this is more explicit and much safer.
import Component from 'material-ui/lib/Component';
import RawComponent from 'material-ui/lib/Component/raw';

Just another idea.

I think the { Raw as Component } proposal by @alitaheri is the best of those 3.

I think if I had to pick one now, I'd go with:
import Component from 'material-ui/lib/Component';
import { Raw as Component } from 'material-ui/lib/Component';

Though I'm wondering raw isn't the right word.

There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton

and naming things.

That's the truth.
Out of curiosity, do we plan on supporting the exports of raw components to developers? While I do see some interesting use cases when that could be useful, I'd rather not make it available publically unless we were really sure we are ready to support it. Even if the raw exports are not documented, people will find out and use them anyway. I'd rather not have to worry about deprecating old raw named exports and paths if we ever decide we want to change or reorganize it.
Javascript isn't the best at helping us in this area. For example, see what Facebook had to do in the React source: https://github.com/facebook/react/blob/master/src/React.js#L25
I suppose the biggest difference in this case is that we only need the raw components for testing. So if we were clever, there might be a way to remove the exports when we do an actual release build. If the exports were removed, I'd be completely fine naming the exports raw or anything and not feeling bad if we need to switch it later.
Let me know if I'm being too paranoid. :laughing:

I think that they should stay undocumented. Stick /** @private */ above the export and call it a day :wink:
I also feel weird naming them all Raw. Something doesn't sit right :smile:
FWIW, in my own projects I use PlainComponent for Component where necessary.

PlainComponent Seems a LOT better :+1: :+1: :+1: Raw was what my mind could spit out in milliseconds, I didn't give it hours to compute a better word, although knowing myself given the life span of universe it would still fail :laughing: :laughing: :laughing:

I was having visions of rawTheme all over again. :wink:

I was having visions of rawTheme all over again. :wink:

:laughing: :laughing: :laughing:

Poll needed? LOL!

:+1: for PlainComponent

@alitaheri Just to confirm, by that are you thinking along the lines of PlainTextField for TextField, etc, not PlainComponent for all? Making sure I was clear when I mentioned it :+1:

Yes I was also referring to the pattern PlainXxx :+1:

Sounds good to me too!

Are there any components we should hold off on unit testing that are scheduled for heavy refactoring?

Are there any components [...] that are scheduled for heavy refactoring?

All of them. :grin:

@mbrookes :smile: hahaha.
Let me refine my question then. There are some components with questionable behaviour (table composition issues spring to mind) that I imagine might require heavy refactoring to change. Therefore, creating tests in it's current state feels like asserting undesirable behaviour (and a semi-waste of time). For example, trying to add any click handlers except on the root <Table /> component is akin to a journey down the rabbit hole.

I'd have to look over everything again with a fresh perspective. I think some component APIs are closer than others, and some will likely require a complete redesign. The challenge is I don't think we're going to have anytime to do any of the major component API refactoring in the 0.15.0 release.
That being said, I think the two that came immediately to mind that I'd like to remove are Clearfix and BeforeAfterWrapper. I'd like to remove those for sure so I wouldn't bother writing tests for those. Maybe before writing tests for any new components, maybe we should quickly regroup and decide what we think our mid and longterm goals might be for the component.

What do you mean by "new components"?

Sorry, that was confusing. I meant existing components that don't currently have tests.

If that's the case, is there anything you can advise me to definitely not write unit tests for at this time?

I just noticed the two I mentioned before @alitaheri didn't even bother including on the list. Honestly other than that I'm not too sure. I'd love to see rewrites for one or two components at the moment but it's just not on my radar at the moment.
My recommendation is if you start looking at a component that needs to be tested and you're seeing some major design flaws that maybe aren't worth testing and should be just fixed, let's discuss it on Gitter or Github and plan what we should do with it.

@newoga To continue the discussion from #3248
I think that the important thing, regardless of react-look is that we focus the unit test style assertions on styles controlled by the component. IE, making sure the prop primary looks for and applies the correct style from the theme. Asserting this internal component behaviour in the unit tests is much more useful than trying to assert the final styling applied in the DOM without a DOM.

controlled by the component, passed through the component to merge with root, and passed by the component to children.

react-look is a game changer. we would probably move a lot of logic there. I plan on adding memoization to react-look, so we can have a single call to prepareStyles with each change of inputs. it's going to be all inside the react-look. but maybe we can test the functions that take theme, state, props, etc and see if they return some expected styles.

@alitaheri since this isn't being updated we may want to get rid of that check list and close the issue.

Or start updating it.


Storage Patch Release 09/12/2022

API change check
API changes are not detected in this pull request.


Running build from msys shell breaks python scripts

In vulkan.py the code checks for sys.platform to start with win32 to identify windows, but if the shell used to invoke cmake originally is an msys shell, any python binary from msys will be picked up first so when python is invoked in cmake rules like for generating vulkan-1.def then sys.platform will equal msys.

Are you suggesting we change to this?
@@ -1276,7 +1276,7 @@ if sys.argv[1] == 'AllPlatforms':
else :
if len(sys.argv) > 3:

   if sys.platform.startswith('win32') and sys.argv[1] != 'Android':

   if (sys.platform.startswith('win32') or sys.platform.startswith('msys')) and sys.argv[1] != 'Android':
       extensions = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_win32_surface, ext_khr_display]
       extensions_all = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_win32_surface, ext_khr_display, lunarg_debug_report]
   elif sys.platform.startswith('linux') and sys.argv[1] != 'Android':

@@ -1286,7 +1286,7 @@ else :
extensions = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_android_surface]
extensions_all = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_android_surface, lunarg_debug_report]
else :

   if sys.argv[1] == 'Win32':

   if sys.argv[1] == 'Win32' or sys.argv[1] == 'msys':
       extensions = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_win32_surface, ext_khr_display]
       extensions_all = [core, ext_khr_surface, ext_khr_device_swapchain, ext_khr_win32_surface, ext_khr_display, lunarg_debug_report]
   elif sys.argv[1] == 'Android':

Yes I think something like that would work for my case. It's up to you whether you actually want to support it or not, but the compile errors you get are quite strange to diagnose so I think at least trying to detect it and bail out would be nice.

If you want, I just pushed a commit into the marky_working branch ( cce5624fa1e28ac44ad24993f566f9a52f595e21).  If you get a chance, can you try that?

I presume you mean 544c06833f44ed051809bc5c9356439c59696ba3 rather, but yes this works for me now. Thank you very much!

 That's what happens when you've got 4 tasks running simultaneously.  I'll commit that.  Thanks for verifying.