test: scheduling: add configuration item

When using Red/black tree ready queue as scheduling algorithm,
there are no limit to the number of priority levels. So set the
CONFIG_NUM_COOP_PRIORITIES to 30, testcase test_bad_prooritiesi()
will prove both cooperative and preemptive thread have no quantitative
limit.
Signed-off-by: Ying ming<EMAIL_ADDRESS>

This code change is OK, CI build failure due to https://github.com/zephyrproject-rtos/zephyr/issues/30408


Failed Android build: Android dependency has different version for the compile (27.0.1) and runtime (27.1.1) classpath

Steps to Reproduce

Launch Android Studio
Click "Start a new Flutter project"
Select "Flutter Application" and click "Next"
Fill out project information in the following screens, clicking "Next" then click "Finish" on the last screen
Open pubspec.yml in the Android Studio editor
Add the following under "dev_dependencies":

  flutter_launcher_icons: ^0.6.1
  google_sign_in: ^3.2.1
  firebase_analytics: ^1.0.3
  firebase_auth: ^0.5.20
  firebase_database: ^1.0.4
  firebase_storage: ^1.0.3
  flutter_firebase_ui: ^0.0.11
  image_picker: ^0.4.10
  image_cropper: ^0.0.8

Press the "Play" button to build and run the application.

Expected Results:
App compiles and runs successfully
Actual Results:
App fails to compile, with the following error:
Execution failed for task ':app:preDebugBuild'.

Android dependency 'com.android.support:support-core-utils' has different version for the compile (27.0.1) and runtime (27.1.1) classpath. You should manually set the same version via DependencyResolution

Logs
$ flutter doctor -v
[✓] Flutter (Channel beta, v0.11.7, on Mac OS X 10.13.6 17G3025, locale en-US)
    • Flutter version 0.11.7 at /Users/dconeybe/local/flutter
    • Framework revision 7a005e1dcd (26 hours ago), 2018-11-19 11:14:05 -0500
    • Engine revision 2e06da3df9
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/dconeybe/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode_10.0.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 30.0.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] IntelliJ IDEA Community Edition (version 2018.2.6)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 30.0.2
    • Dart plugin version 182.5124

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

Here is the Flutter application that failed to compile:
buildbug.zip

FYI I was able to work around this build problem by adding the following lines to the "android" section of android/app/build.gradle
    configurations.all {
        resolutionStrategy.force 'com.android.support:support-compat:27.1.1'
        resolutionStrategy.force 'com.android.support:appcompat-v7:27.1.1'
        resolutionStrategy.force 'com.android.support:support-v4:27.1.1'
    }

I now have other runtime issues (app crashes upon launch, most likely unrelated to this bug report) but at least it compiles :)

I dont know why or how this works, but thank you so much.


BCDB (config manager) inconsistent reads across multiple processes [unstable]

Reproduce

From one kosmos shell create a new client, change some properties in it and save and check it from another shell you will get same value.

Then repeat from the first shell change some values, check from the second shell old values are there

First shell

second shell

'www' become 'aaa' in the first shell but not updated in the second shell

No support for multiple BCDB processes, need to go through Gedis


ext_proc crash when using grpc initial_metadata and REQ/RESP headers on 1.18+

Issue was originally submitted to envoy-security, but rejected from there confirming that it was reproducible, asking to create a ticket in github:
dynamic functions like %REQ()% or %RESP()% causing crash for v1.18/v1.19. On v1.17 passing without crash.
config snippet, does not require working service, was tested with simple http:
          http_filters:
          - name: extension-matcher
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.ext_proc.v3alpha.ExternalProcessor
              failure_mode_allow: true
              message_timeout: 5s
              processing_mode:
                request_header_mode: "SEND"
                response_header_mode: "SEND"
                request_body_mode: "NONE"
                response_body_mode: "NONE"
                request_trailer_mode: "SKIP"
                response_trailer_mode: "SKIP"
              grpc_service:
                envoy_grpc:
                  cluster_name: origin
                initial_metadata:
                - key: "x-request-id"
                  value: "%REQ(x-request-id)%"
          - name: envoy.filters.http.router

cc @gbrail @snowp

It looks like the problem is that we don't pass the "StreamInfo" to the gRPC stream when starting to talk to the ext_proc server. That's pretty easy to fix, and harder to write an integration test for but I'll work on it. Thanks!

issue solved in #18190


Add burn_foundry_and_its_alias test

Added in https://github.com/iotaledger/iota-sdk/pull/378 instead


Remove Javascript tests (replaced by TypeScript tests from now on)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4074 unchanged lines in 90 files lost coverage.


BUGFIX: Prevent UniqueConstraintViolationException

Introduces commit retries with exponential backoff in order to avoid a UniqueConstraintViolationException from being thrown when many events are published almost at the same time from different processes.
Background:
Even though retrieving the currently highest version number for a stream and the insert of new event rows is done transactionally that didn't prevent the same max version from being retrieved by a 2nd process.
Fortunately we have a unique key constraint on the db level to prevent inconsistent data, but the exception wasn't nice so this introduces some retry mechanism.
Note: After the maximum number of attempts are exceeded (currently eight) this will still fail and throw a ConcurrencyException in that case. Currently this will only happen after 1.2 seconds so it is quite unlikely.
I failed to cover the fixed behavior with meaningful tests (lacking the 2nd process to actually provoke the bug) but I tested it manually by executing the following code from two separate CLI commands:
$streamName = StreamName::fromString('test');
$events = [];
for ($i = 0; $i < 10000; $i ++) {
    $events[] = new SomethingHasHappened($i);
}
$this->eventStore->commit($streamName, DomainEvents::fromArray($events));

The result is:

20.000 events in the database
no gaps in the stream version
a single gap of 1 in the sequence number

The gap in the sequence number arises from the parallel writes and can't be avoided AFAIK, but they should not pose a problem anyways.
Fixes: #245

The calculated max backoff is wrong though

You're right, I'll tweak the doc comments accordingly.  I don't see it in the code yet :)

@skurfuerst @bwaidelich Does lowering isolation level to READ_UNCOMMITTED really solve an issue here? AFAIK it will only result in not guaranteeing that the read is consistent with it's own transaction, so e.g. in the case of two interleaved (concurrent) transactions consisting of:
START TRANSACTION;
SELECT @x:=num FROM x ...;
UPDATE x SET num = num + 1 ...;
SELECT @y:=num FROM x ...;
COMMIT;

would lead to @y possibly returning @x+2 in one or the other case (and a following select on num could then again return @x+1 if the other transaction failed).
In our case that wouldn't change the semantics though, because we only do a single select+insert and the select always happens first, so whatever it sees is used in the following insert. It basically means that the select could see a stream version of another transaction that isn't committed yet, so effectively just lead to gaps in the stream version in the worst case. In contrast, increasing the isolation level to SERIALIZABLE would solve our issue, but effectively be the same as us using locking AFAIS.

@skurfuerst @albe exactly, I mixed it up before.
The isolation levels READ_UNCOMMITTED, READ_COMMITTED and REPEATABLE_READ (=default) all have the same consistent result.
Only SERIALIZABLE could lead to a db timeout because it would block reading.

I was about to fix the "exponential backoff" comment, but I think it is actually correct, even if a bit misleading:
our first attempt is $retryAttempt 0

Wait, the actual delay is rather:

first attempt
fail => wait 5ms => 1. retry
fail => wait 10ms => 2. retry
fail => wait 20ms => 3. retry
fail => wait 40ms => 4. retry
fail => wait 80ms => 5. retry
fail => wait 160ms => 6. retry
fail => wait 320ms => 7. retry
fail => wait 640ms => 8. retry
fail => max retries => exception

= 1275ms max wait
since the $retryWaitInterval = 0.005; initially and is doubled after every failure without a fixed value added on top as in the calculator (i.e. $retryWaitInterval = $retryWaitInterval * 2 + $initialRetryWaitInterval;).

@albe yes, you're right. It's 1275ms (and that's what it says in the code comment). I just mixed it up above.
If you think the comment is still misleading, feel free to make a better suggestion and I'll gladly update it!

Well, guess the otherwise really nice link to the calculator is what's misleading. What about adjusting the calculation of the wait to match the calculator?

@albe can you provide an example? IMO the max wait time is the same that the calculator gives (1275 ms) and that's the most important bit. How can we change the calculation so that it matches in your opinion?

Yes, the total time in the comment is correct, but the listing of single wait times in the calculator don't match.
See the table above with the list of wait times compared to your table, which is equal to what the calculator shows.
At 8 attempts (rather than retries, so quitting after the 7th) the total with the calculator is 1235ms as you showed above. So it is indeed misleading.
I see two possible solutions: remove the link to the calculator, or adjust the used formula as mentioned above


Rescalc - update to v0.02

Fixes colors not matching user input from color menu in some cases, 3 bands are now shown larger, various code improvements.

Great!


Query parameter with a type being a model property crash openapi3 emitter

import "@cadl-lang/rest";

using Cadl.Http;

op foo(@query id: UserContext.id): void;

model UserContext {
  id: string;
}

Playground Link

fix in openapi3
check and fix in cadl-autorest

Yes, this bug exists in cadl-autorest as well, though not as ugly. The source of both bugs is inadequate type annotations in the code. Another example of why https://github.com/microsoft/cadl/issues/1563 would be good.


[vSphere] Failed boot2docker images ends with docker-machine zombie processes

Rancher versions:
rancher/server: 2.0.0-alpha24
Docker version: (docker version,docker info preferred)
18.03.0-ce (yes, unsupported, I know. But shouldn't have nothing to do with the specific problem itself)
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Ubuntu 16.04.4 LTS (4.4.0-116-generic)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
vSphere VM
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Make github.com certificate invalid. e.g. through rewriting DNS github.com to anything else (happend accidentally in my case)
Then create a cluster and node using the vSphere provider (in my case) with using the default boot2docker image.
Then this errors comes up:

Error creating machine: Error in driver during machine creation: Get https://github.com/boot2docker/boot2docker/releases/download/v18.03.0-ce/boot2docker.iso: x509: certificate is valid for CN_DNSBL, not github.com, Timeout waiting for ssh key

This error is ocurring permanently without a end, Rancher always keeps trying to spin up the node and starting new docker-machine processes, which ends up in zombie processes after some time.
Results:
After about half an hour there are finally about 290 zombie docker-machine processes running:
# ps aux | grep "docker-machine" | wc -l
290

And as seen in the htop output here:

I see the same error with Rancher 2.0 beta2 (i.e. creating a cluster with vSphere produces the docker-machine zombie processes). Here are the logs I see in the Rancher server container (I used one master server with etcd and controlplane and 2 worker nodes).
E0412 11:51:21.375272       1 generic_controller.go:204] ClusterRoleTemplateBindingController cluster-nv6gf/creator [mgmt-auth-crtb-controller] failed with : couldn't create role cluster-owner: roles.rbac.authorization.k8s.io "cluster-owner" already exists
2018/04/12 11:51:22 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 11:51:22 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 11:51:22 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 11:51:22 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 11:51:23 [INFO] stdout: Running pre-create checks...
2018/04/12 11:51:23 [INFO] stdout: Running pre-create checks...
2018/04/12 11:51:25 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:51:25 [INFO] stdout:
2018/04/12 11:51:25 [INFO] Generating and uploading node config master1
2018/04/12 11:51:26 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:51:26 [INFO] stdout:
2018/04/12 11:51:26 [INFO] Generating and uploading node config worker1
E0412 11:51:40.831840       1 generic_controller.go:204] NodeController cluster-nv6gf/m-nm6jw [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:51:40 [INFO] NodeController cluster-nv6gf/m-nm6jw completed with dropped err: [node-controller] failed with : Error
E0412 11:51:41.485444       1 generic_controller.go:204] NodeController cluster-nv6gf/m-7m5ck [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:51:41 [INFO] NodeController cluster-nv6gf/m-7m5ck completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:51:41 [INFO] NodeController cluster-nv6gf/m-nm6jw completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:51:42 [INFO] NodeController cluster-nv6gf/m-7m5ck completed with dropped err: [node-controller] failed with : Error
E0412 11:53:38.204688       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018/04/12 11:53:41 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 11:53:41 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 11:53:41 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 11:53:41 [INFO] stdout: Running pre-create checks...
2018/04/12 11:53:42 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 11:53:42 [INFO] stdout: Running pre-create checks...
2018/04/12 11:53:44 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:53:44 [INFO] stdout:
2018/04/12 11:53:44 [INFO] Generating and uploading node config master1
2018/04/12 11:53:45 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:53:45 [INFO] stdout:
2018/04/12 11:53:45 [INFO] Generating and uploading node config worker1
E0412 11:53:59.653730       1 generic_controller.go:204] NodeController cluster-nv6gf/m-2h45p [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:53:59 [INFO] Generating and uploading node config
E0412 11:54:00.386190       1 generic_controller.go:204] NodeController cluster-nv6gf/m-6nxgj [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:54:00 [INFO] Generating and uploading node config
2018/04/12 11:54:14 [INFO] NodeController cluster-nv6gf/m-2h45p completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:54:15 [INFO] NodeController cluster-nv6gf/m-6nxgj completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:54:15 [INFO] NodeController cluster-nv6gf/m-2h45p completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:54:17 [INFO] NodeController cluster-nv6gf/m-6nxgj completed with dropped err: [node-controller] failed with : Error
2018-04-12 11:55:30.866782 I | mvcc: store.index: compact 97891
2018-04-12 11:55:30.871782 I | mvcc: finished scheduled compaction at 97891 (took 3.743517ms)
2018/04/12 11:56:15 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 11:56:15 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 11:56:15 [INFO] stdout: Running pre-create checks...
2018/04/12 11:56:15 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 11:56:16 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 11:56:16 [INFO] stdout: Running pre-create checks...
2018/04/12 11:56:17 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:56:17 [INFO] stdout:
2018/04/12 11:56:18 [INFO] Generating and uploading node config master1
2018/04/12 11:56:18 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:56:18 [INFO] stdout:
2018/04/12 11:56:19 [INFO] Generating and uploading node config worker1
E0412 11:56:33.224566       1 generic_controller.go:204] NodeController cluster-nv6gf/m-v6wj2 [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:56:33 [INFO] Generating and uploading node config
E0412 11:56:34.253902       1 generic_controller.go:204] NodeController cluster-nv6gf/m-wxq9h [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:56:34 [INFO] Generating and uploading node config
2018/04/12 11:56:48 [INFO] NodeController cluster-nv6gf/m-v6wj2 completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:56:49 [INFO] NodeController cluster-nv6gf/m-wxq9h completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:56:50 [INFO] NodeController cluster-nv6gf/m-v6wj2 completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:56:51 [INFO] NodeController cluster-nv6gf/m-wxq9h completed with dropped err: [node-controller] failed with : Error
E0412 11:57:41.577964       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
E0412 11:57:41.578708       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
E0412 11:57:42.800411       1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
2018/04/12 11:57:55 [INFO] Purged 1 expired tokens
2018/04/12 11:58:48 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 11:58:49 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 11:58:49 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 11:58:49 [INFO] stdout: Running pre-create checks...
2018/04/12 11:58:50 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 11:58:50 [INFO] stdout: Running pre-create checks...
2018/04/12 11:58:52 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:58:52 [INFO] stdout:
2018/04/12 11:58:52 [INFO] Generating and uploading node config master1
2018/04/12 11:58:52 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 11:58:52 [INFO] stdout:
2018/04/12 11:58:53 [INFO] Generating and uploading node config worker1
E0412 11:59:07.522707       1 generic_controller.go:204] NodeController cluster-nv6gf/m-vgfcm [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:59:07 [INFO] NodeController cluster-nv6gf/m-vgfcm completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:59:08 [INFO] NodeController cluster-nv6gf/m-vgfcm completed with dropped err: [node-controller] failed with : Error
E0412 11:59:08.074531       1 generic_controller.go:204] NodeController cluster-nv6gf/m-tbp9g [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 11:59:08 [INFO] Generating and uploading node config
2018/04/12 11:59:23 [INFO] NodeController cluster-nv6gf/m-tbp9g completed with dropped err: [node-controller] failed with : Error
2018/04/12 11:59:24 [INFO] NodeController cluster-nv6gf/m-tbp9g completed with dropped err: [node-controller] failed with : Error
E0412 12:00:22.149288       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018-04-12 12:00:30.890274 I | mvcc: store.index: compact 98491
2018-04-12 12:00:30.895870 I | mvcc: finished scheduled compaction at 98491 (took 3.707193ms)
2018/04/12 12:00:43 [INFO] Running cluster events cleanup
2018/04/12 12:00:43 [INFO] Done running cluster events cleanup
2018/04/12 12:01:07 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 12:01:08 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 12:01:08 [INFO] stdout: Running pre-create checks...
2018/04/12 12:01:10 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 12:01:10 [INFO] stdout:
2018/04/12 12:01:11 [INFO] Generating and uploading node config master1
2018/04/12 12:01:23 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 12:01:23 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 12:01:24 [INFO] stdout: Running pre-create checks...
E0412 12:01:26.066977       1 generic_controller.go:204] NodeController cluster-nv6gf/m-cx92m [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 12:01:26 [INFO] NodeController cluster-nv6gf/m-cx92m completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:01:26 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 12:01:26 [INFO] stdout:
2018/04/12 12:01:27 [INFO] NodeController cluster-nv6gf/m-cx92m completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:01:27 [INFO] Generating and uploading node config worker1
E0412 12:01:42.185074       1 generic_controller.go:204] NodeController cluster-nv6gf/m-dtwmf [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 12:01:42 [INFO] Generating and uploading node config
E0412 12:01:54.212219       1 streamwatcher.go:109] Unable to decode an event from the watch stream: json: cannot unmarshal string into Go struct field dynamicEvent.Object of type v3.NodeStatus
2018/04/12 12:01:57 [INFO] NodeController cluster-nv6gf/m-dtwmf completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:01:58 [INFO] NodeController cluster-nv6gf/m-dtwmf completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:03:26 [INFO] stdout: Creating CA: management-state/node/nodes/master1/certs/ca.pem
2018/04/12 12:03:26 [INFO] stdout: Creating client certificate: management-state/node/nodes/master1/certs/cert.pem
2018/04/12 12:03:26 [INFO] stdout: Running pre-create checks...
2018/04/12 12:03:29 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 12:03:29 [INFO] stdout:
2018/04/12 12:03:29 [INFO] Generating and uploading node config master1
2018/04/12 12:03:42 [INFO] stdout: Creating CA: management-state/node/nodes/worker1/certs/ca.pem
2018/04/12 12:03:42 [INFO] stdout: Creating client certificate: management-state/node/nodes/worker1/certs/cert.pem
2018/04/12 12:03:43 [INFO] stdout: Running pre-create checks...
E0412 12:03:44.776583       1 generic_controller.go:204] NodeController cluster-nv6gf/m-xbpt6 [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 12:03:44 [INFO] NodeController cluster-nv6gf/m-xbpt6 completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:03:45 [INFO] NodeController cluster-nv6gf/m-xbpt6 completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:03:46 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/04/12 12:03:46 [INFO] stdout:
2018/04/12 12:03:46 [INFO] Generating and uploading node config worker1
E0412 12:04:01.349420       1 generic_controller.go:204] NodeController cluster-nv6gf/m-t6q9l [node-controller] failed with : Error with pre-create check: "unexpected EOF"
2018/04/12 12:04:01 [INFO] NodeController cluster-nv6gf/m-t6q9l completed with dropped err: [node-controller] failed with : Error
2018/04/12 12:04:02 [INFO] NodeController cluster-nv6gf/m-t6q9l completed with dropped err: [node-controller] failed with : Error

And the processes:
root@a12753703b85:/var/lib/rancher# ps waux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1 29.7 14.0 11905084 567712 ?     Ssl  Apr11 333:27 rancher --http-listen-port=80 --https-listen-port=443
root       103  0.0  0.0      0     0 ?        Z    11:51   0:00 [docker-machine] <defunct>
root       109  0.0  0.0      0     0 ?        Z    11:51   0:00 [docker-machine] <defunct>
root       122  0.0  0.0      0     0 ?        Z    11:51   0:00 [docker-machine] <defunct>
root       130  0.0  0.0      0     0 ?        Z    11:51   0:00 [docker-machine] <defunct>
root       165  0.0  0.0      0     0 ?        Z    11:53   0:00 [docker-machine] <defunct>
root       172  0.0  0.0      0     0 ?        Z    11:53   0:00 [docker-machine] <defunct>
root       193  0.0  0.0      0     0 ?        Z    11:53   0:00 [docker-machine] <defunct>
root       203  0.0  0.0      0     0 ?        Z    11:53   0:00 [docker-machine] <defunct>
root       237  0.0  0.0      0     0 ?        Z    11:56   0:00 [docker-machine] <defunct>
root       246  0.0  0.0      0     0 ?        Z    11:56   0:00 [docker-machine] <defunct>
root       266  0.0  0.0      0     0 ?        Z    11:56   0:00 [docker-machine] <defunct>
root       272  0.0  0.0      0     0 ?        Z    11:56   0:00 [docker-machine] <defunct>
root       305  0.0  0.0      0     0 ?        Z    11:58   0:00 [docker-machine] <defunct>
root       314  0.0  0.0      0     0 ?        Z    11:58   0:00 [docker-machine] <defunct>
root       335  0.0  0.0      0     0 ?        Z    11:58   0:00 [docker-machine] <defunct>
root       341  0.0  0.0      0     0 ?        Z    11:58   0:00 [docker-machine] <defunct>
root       374  0.0  0.0      0     0 ?        Z    12:01   0:00 [docker-machine] <defunct>
root       383  0.0  0.0      0     0 ?        Z    12:01   0:00 [docker-machine] <defunct>
root       413  0.0  0.0      0     0 ?        Z    12:01   0:00 [docker-machine] <defunct>
root       420  0.0  0.0      0     0 ?        Z    12:01   0:00 [docker-machine] <defunct>
root       435  0.0  0.0  18496  3380 ?        Ss+  12:03   0:00 /bin/bash
root       462  0.0  0.0      0     0 ?        Z    12:03   0:00 [docker-machine] <defunct>
root       470  0.0  0.0      0     0 ?        Z    12:03   0:00 [docker-machine] <defunct>
root       496  0.0  0.0      0     0 ?        Z    12:03   0:00 [docker-machine] <defunct>
root       505  0.0  0.0      0     0 ?        Z    12:03   0:00 [docker-machine] <defunct>
root       533  0.0  0.0      0     0 ?        Z    12:05   0:00 [docker-machine] <defunct>
root       540  0.0  0.0      0     0 ?        Z    12:05   0:00 [docker-machine] <defunct>
root       565  0.0  0.0      0     0 ?        Z    12:06   0:00 [docker-machine] <defunct>
root       574  0.0  0.0      0     0 ?        Z    12:06   0:00 [docker-machine] <defunct>
root       600  0.0  0.0      0     0 ?        Z    12:08   0:00 [docker-machine] <defunct>
root       608  0.0  0.0      0     0 ?        Z    12:08   0:00 [docker-machine] <defunct>
root       632  0.0  0.0      0     0 ?        Z    12:08   0:00 [docker-machine] <defunct>
root       642  0.0  0.0      0     0 ?        Z    12:08   0:00 [docker-machine] <defunct>
root       669  0.0  0.0      0     0 ?        Z    12:10   0:00 [docker-machine] <defunct>
root       676  0.0  0.0      0     0 ?        Z    12:10   0:00 [docker-machine] <defunct>
root       703  0.0  0.0      0     0 ?        Z    12:10   0:00 [docker-machine] <defunct>
root       711  0.0  0.0      0     0 ?        Z    12:10   0:00 [docker-machine] <defunct>
root       737  0.0  0.0      0     0 ?        Z    12:12   0:00 [docker-machine] <defunct>
root       746  0.0  0.0      0     0 ?        Z    12:12   0:00 [docker-machine] <defunct>
root       772  0.0  0.0      0     0 ?        Z    12:13   0:00 [docker-machine] <defunct>
root       780  0.0  0.0      0     0 ?        Z    12:13   0:00 [docker-machine] <defunct>
root       807  0.0  0.0      0     0 ?        Z    12:15   0:00 [docker-machine] <defunct>
root       816  0.0  0.0      0     0 ?        Z    12:15   0:00 [docker-machine] <defunct>
root       842  0.0  0.0      0     0 ?        Z    12:15   0:00 [docker-machine] <defunct>
root       853  0.0  0.0      0     0 ?        Z    12:15   0:00 [docker-machine] <defunct>
root       880  0.0  0.0      0     0 ?        Z    12:17   0:00 [docker-machine] <defunct>
root       889  0.0  0.0      0     0 ?        Z    12:17   0:00 [docker-machine] <defunct>
root       914  0.0  0.0      0     0 ?        Z    12:18   0:00 [docker-machine] <defunct>
root       920  0.0  0.0      0     0 ?        Z    12:18   0:00 [docker-machine] <defunct>
root       946  0.0  0.0      0     0 ?        Z    12:20   0:00 [docker-machine] <defunct>
root       955  0.0  0.0      0     0 ?        Z    12:20   0:00 [docker-machine] <defunct>
root       981  0.0  0.0      0     0 ?        Z    12:20   0:00 [docker-machine] <defunct>
root       990  0.0  0.0      0     0 ?        Z    12:20   0:00 [docker-machine] <defunct>
root      1018  0.0  0.0      0     0 ?        Z    12:22   0:00 [docker-machine] <defunct>
root      1025  0.0  0.0      0     0 ?        Z    12:22   0:00 [docker-machine] <defunct>
root      1051  0.0  0.0      0     0 ?        Z    12:22   0:00 [docker-machine] <defunct>
root      1058  0.0  0.0      0     0 ?        Z    12:22   0:00 [docker-machine] <defunct>
root      1085  0.0  0.0      0     0 ?        Z    12:24   0:00 [docker-machine] <defunct>
root      1092  0.0  0.0      0     0 ?        Z    12:24   0:00 [docker-machine] <defunct>
root      1119  0.0  0.0      0     0 ?        Z    12:25   0:00 [docker-machine] <defunct>
root      1126  0.0  0.0      0     0 ?        Z    12:25   0:00 [docker-machine] <defunct>
root      1153  0.0  0.0      0     0 ?        Z    12:27   0:00 [docker-machine] <defunct>
root      1160  0.0  0.0      0     0 ?        Z    12:27   0:00 [docker-machine] <defunct>
root      1186  0.0  0.0      0     0 ?        Z    12:27   0:00 [docker-machine] <defunct>
root      1193  0.0  0.0      0     0 ?        Z    12:27   0:00 [docker-machine] <defunct>
root      1219  0.0  0.0      0     0 ?        Z    12:29   0:00 [docker-machine] <defunct>
root      1229  0.0  0.0      0     0 ?        Z    12:29   0:00 [docker-machine] <defunct>
root      1255  0.0  0.0      0     0 ?        Z    12:29   0:00 [docker-machine] <defunct>
root      1263  0.0  0.0      0     0 ?        Z    12:29   0:00 [docker-machine] <defunct>
root      1289  0.0  0.0      0     0 ?        Z    12:32   0:00 [docker-machine] <defunct>
root      1298  0.0  0.0      0     0 ?        Z    12:32   0:00 [docker-machine] <defunct>
root      1325  0.0  0.0      0     0 ?        Z    12:32   0:00 [docker-machine] <defunct>
root      1331  0.0  0.0      0     0 ?        Z    12:32   0:00 [docker-machine] <defunct>
root      1358  0.0  0.0      0     0 ?        Z    12:34   0:00 [docker-machine] <defunct>
root      1368  0.0  0.0      0     0 ?        Z    12:34   0:00 [docker-machine] <defunct>
root      1393  0.0  0.0      0     0 ?        Z    12:34   0:00 [docker-machine] <defunct>
root      1400  0.0  0.0      0     0 ?        Z    12:34   0:00 [docker-machine] <defunct>
root      1428  0.0  0.0      0     0 ?        Z    12:36   0:00 [docker-machine] <defunct>
root      1436  0.0  0.0      0     0 ?        Z    12:36   0:00 [docker-machine] <defunct>
root      1462  0.0  0.0      0     0 ?        Z    12:37   0:00 [docker-machine] <defunct>
root      1469  0.0  0.0      0     0 ?        Z    12:37   0:00 [docker-machine] <defunct>
root      1496  0.0  0.0      0     0 ?        Z    12:39   0:00 [docker-machine] <defunct>
root      1503  0.0  0.0      0     0 ?        Z    12:39   0:00 [docker-machine] <defunct>
root      1532  0.0  0.0      0     0 ?        Z    12:39   0:00 [docker-machine] <defunct>
root      1539  0.0  0.0      0     0 ?        Z    12:39   0:00 [docker-machine] <defunct>
root      1566  0.0  0.0      0     0 ?        Z    12:41   0:00 [docker-machine] <defunct>
root      1573  0.0  0.0      0     0 ?        Z    12:41   0:00 [docker-machine] <defunct>
root      1599  0.0  0.0      0     0 ?        Z    12:41   0:00 [docker-machine] <defunct>
root      1607  0.0  0.0      0     0 ?        Z    12:41   0:00 [docker-machine] <defunct>
root      1636  0.0  0.0      0     0 ?        Z    12:43   0:00 [docker-machine] <defunct>
root      1643  0.0  0.0      0     0 ?        Z    12:43   0:00 [docker-machine] <defunct>
root      1670  0.0  0.0      0     0 ?        Z    12:44   0:00 [docker-machine] <defunct>
root      1676  0.0  0.0      0     0 ?        Z    12:44   0:00 [docker-machine] <defunct>
root      1708  0.0  0.0      0     0 ?        Z    12:46   0:00 [docker-machine] <defunct>
root      1715  0.0  0.0      0     0 ?        Z    12:46   0:00 [docker-machine] <defunct>
root      1741  0.0  0.0      0     0 ?        Z    12:46   0:00 [docker-machine] <defunct>
root      1749  0.0  0.0      0     0 ?        Z    12:46   0:00 [docker-machine] <defunct>
root      1775  0.0  0.0      0     0 ?        Z    12:48   0:00 [docker-machine] <defunct>
root      1784  0.0  0.0      0     0 ?        Z    12:48   0:00 [docker-machine] <defunct>
root      1811  0.0  0.0      0     0 ?        Z    12:49   0:00 [docker-machine] <defunct>
root      1818  0.0  0.0      0     0 ?        Z    12:49   0:00 [docker-machine] <defunct>
root      1846  0.0  0.0      0     0 ?        Z    12:50   0:00 [docker-machine] <defunct>
root      1854  0.0  0.0      0     0 ?        Z    12:50   0:00 [docker-machine] <defunct>
root      1879  0.0  0.0      0     0 ?        Z    12:51   0:00 [docker-machine] <defunct>
root      1888  0.0  0.0      0     0 ?        Z    12:51   0:00 [docker-machine] <defunct>
root      1913  0.0  0.0      0     0 ?        Z    12:53   0:00 [docker-machine] <defunct>
root      1922  0.0  0.0      0     0 ?        Z    12:53   0:00 [docker-machine] <defunct>
root      1948  0.0  0.0      0     0 ?        Z    12:53   0:00 [docker-machine] <defunct>
root      1955  0.0  0.0      0     0 ?        Z    12:53   0:00 [docker-machine] <defunct>
root      1979  2.3  0.0  18496  3376 ?        Ss   13:41   0:00 /bin/bash
root      1992  0.0  0.0  38976  3072 ?        R+   13:41   0:00 ps waux

Build: v2.0.0-beta4-rc1
Ran for 20~ minutes. Invalidated github cert. Verified zombie process are not present for "docker-machine" during failed provisioning.


(Catalyst) 404 Not Found when downloading file returned as internal error processing file

https://github.com/livepeer/task-runner/pull/107/files#diff-33d20f5d5f41105e4334b7eb8ece1a7b748ed5e6f39acfab43ec28abfea3fed0R482 added a 404 Not Found string matching check. But, it doesn't seem to work because when humanizeErrors = true, the error returned by task-runner still seems to be internal error processing file. Related to Catalyst considering a 404 non-retryable when it reports a transcode status message?
Would be better if a 404 Not Found when downloading a file results in a file not accessible error returned by task-runner.

Closed by #113


store SLD on geopackage

The qgis_geopackage_extension defines a table qgis_layer_styles  which seems not created by the current qgis plugin. The layer_styles table has a field styleSLD and a field styleQML. The idea is when loading a geopackage to see which of the fields is filled, and use that to render the layer?
See also this discussion https://github.com/opengeospatial/geopackage/issues/270 which discusses similar goal from a more wider OGC perspective.

Will look at that in the course of #7, thanks!

I propose a separate table for that. See #11

Included in #14


WFMP-84 fix NPE when using path-elements for modulesPath

See WFMP-84 for further explanation.

This looks reasonable.
We require that all contributions be made under the terms of the MIT License, http://www.opensource.org/licenses/mit-license.php. Do you agree to the these terms?

Of course, I do.


a bunch of problems

Main problem is that terminals don't have the hud and dont even work,the  second one is the OST not playing and the third is skyblocks not functioning correctly(they are transparent and more like an x-ray through blocks), also skull doors dont work

remove iris or any other rendering mods like it. that'll fix skyblocks and terminals
as for the music, make sure music (top left slider) isn't at 0% volume in your sound settings

alright thanks, as for the music I had an old version of the mod so i just had to update it


Remove unused TypeScript files

It seems, that all files mentioned in this commit are not used by the project currently and can be removed.

That's alright. If some of the files are still used, just keep them and remove only the unused files :)


Besm4e extras dev

Changes / Comments
BESM4eExtras.html
Cached values framework - provides performance enhancements by collecting all sheet values on open event, then maintaining a cache of these values in a single JSON called each successive event after open.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[x] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Feature/health chk post edges

Performs sanity check after Edges have been POSTed in bulk
fixes openreview/openreview#1902

Before approving, I was thinking that this check should be done in the openreview backend not here. What do you think?

Yes, let's do the checking in the backend too.


Unable to download JSON metadata: HTTP Error 404: NOT FOUND (caused by HTTPError());

detail error log info 👍
Unable to download JSON metadata: HTTP Error 404: NOT FOUND (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 502, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2106, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 435, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 473, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
version info 👍
[debug] Encodings: locale ANSI_X3.4-1968, fs ANSI_X3.4-1968, out ANSI_X3.4-1968, pref ANSI_X3.4-1968
[debug] youtube-dl version 2017.05.14
[debug] Python version 2.7.12 - Linux-4.4.0-64-generic-x86_64-with-Ubuntu-16.04-xenial
[debug] exe versions: ffmpeg 2.8.11-0ubuntu<IP_ADDRESS>, ffprobe 2.8.11-0ubuntu<IP_ADDRESS>

Carefully read new issue template and provide all requested information.


Active healthcheck for cluster is failing

Active healthcheck for cluster is failing
Active healthcheck is failing though I am getting response from the upstream. Not sure if I am missing anything in the configuration.
Admin and Stats Output:
cluster.sample-cluster.bind_errors: 0
cluster.sample-cluster.external.upstream_rq_200: 11
cluster.sample-cluster.external.upstream_rq_2xx: 11
cluster.sample-cluster.external.upstream_rq_301: 1
cluster.sample-cluster.external.upstream_rq_3xx: 1
cluster.sample-cluster.health_check.attempt: 12
cluster.sample-cluster.health_check.failure: 12
cluster.sample-cluster.health_check.healthy: 0
cluster.sample-cluster.health_check.network_failure: 12
cluster.sample-cluster.health_check.passive_failure: 0
cluster.sample-cluster.health_check.success: 0
cluster.sample-cluster.health_check.verify_cluster: 0
cluster.sample-cluster.lb_healthy_panic: 12
cluster.sample-cluster.lb_local_cluster_not_ok: 0
cluster.sample-cluster.lb_recalculate_zone_structures: 0
cluster.sample-cluster.lb_subsets_active: 0
cluster.sample-cluster.lb_subsets_created: 0
cluster.sample-cluster.lb_subsets_fallback: 0
cluster.sample-cluster.lb_subsets_removed: 0
cluster.sample-cluster.lb_subsets_selected: 0
cluster.sample-cluster.lb_zone_cluster_too_small: 0
cluster.sample-cluster.lb_zone_no_capacity_left: 0
cluster.sample-cluster.lb_zone_number_differs: 0
cluster.sample-cluster.lb_zone_routing_all_directly: 0
cluster.sample-cluster.lb_zone_routing_cross_zone: 0
cluster.sample-cluster.lb_zone_routing_sampled: 0
cluster.sample-cluster.max_host_weight: 0
cluster.sample-cluster.membership_change: 1
cluster.sample-cluster.membership_healthy: 0
cluster.sample-cluster.membership_total: 1
Config:
node:
  id: some-node
  cluster: default-cluster
  locality:
        zone: default-zone

admin:
  access_log_path: /dev/stdout
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 9901 }

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address: { address: <IP_ADDRESS>, port_value: 10000 }
    filter_chains:
      filters:
      - name: envoy.http_connection_manager
        config:
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: sample-cluster
          http_filters:
          - name: envoy.router
  clusters:
  - name: sample-cluster
    type: LOGICAL_DNS
    connect_timeout: 0.25s
    lb_policy: ROUND_ROBIN
    dns_lookup_family: V4_ONLY
    hosts:
    - socket_address:
        protocol: TCP
        address: some-domain.com  #have changed it for privacy concern
        port_value: 80
    health_checks:
      timeout: 2s
      interval: 5s
      interval_jitter: 1s
      unhealthy_threshold: 1
      healthy_threshold: 3
      no_traffic_interval: 60s
      event_log_path: /dev/stdout
      http_health_check:
        path: /

Logs:
$ [2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:183] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
[2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:185] statically linked extensions:
[2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:187]   access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
[2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:190]   filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.header_to_metadata,envoy.filters.http.jwt_authn,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
[2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:193]   filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
[2018-07-19 20:54:09.457][19][info][main] source/server/server.cc:196]   filters.network: envoy.client_ssl_auth,envoy.echo,envoy.ext_authz,envoy.filters.network.thrift_proxy,envoy.http_connection_manager,envoy.mongo_proxy,envoy.ratelimit,envoy.redis_proxy,envoy.tcp_proxy
[2018-07-19 20:54:09.458][19][info][main] source/server/server.cc:198]   stat_sinks: envoy.dog_statsd,envoy.metrics_service,envoy.stat_sinks.hystrix,envoy.statsd
[2018-07-19 20:54:09.458][19][info][main] source/server/server.cc:200]   tracers: envoy.dynamic.ot,envoy.lightstep,envoy.zipkin
[2018-07-19 20:54:09.458][19][info][main] source/server/server.cc:203]   transport_sockets.downstream: envoy.transport_sockets.capture,raw_buffer,tls
[2018-07-19 20:54:09.458][19][info][main] source/server/server.cc:206]   transport_sockets.upstream: envoy.transport_sockets.capture,raw_buffer,tls
[2018-07-19 20:54:09.463][19][debug][main] source/server/server.cc:234] admin address: <IP_ADDRESS>:9901
[2018-07-19 20:54:09.464][19][info][config] source/server/configuration_impl.cc:50] loading 0 static secret(s)
[2018-07-19 20:54:09.465][22][debug][grpc] source/common/grpc/google_async_client_impl.cc:39] completionThread running
[2018-07-19 20:54:09.466][19][debug][upstream] source/common/upstream/cluster_manager_impl.cc:707] adding TLS initial cluster sample-cluster
[2018-07-19 20:54:09.466][19][debug][upstream] source/common/upstream/logical_dns_cluster.cc:70] starting async DNS resolution for some-domain.com
[2018-07-19 20:54:09.466][19][debug][upstream] source/common/network/dns_impl.cc:147] Setting DNS resolution timer for 5000 milliseconds
[2018-07-19 20:54:09.466][19][debug][upstream] source/common/upstream/cluster_manager_impl.cc:61] cm init: adding: cluster=sample-cluster primary=1 secondary=0
[2018-07-19 20:54:09.466][19][info][config] source/server/configuration_impl.cc:60] loading 1 listener(s)
[2018-07-19 20:54:09.466][19][debug][config] source/server/configuration_impl.cc:62] listener #0:
[2018-07-19 20:54:09.466][19][debug][config] source/server/listener_manager_impl.cc:528] begin add/update listener: name=listener_0 hash=16491985507912357005
[2018-07-19 20:54:09.466][19][debug][config] source/server/listener_manager_impl.cc:38]   filter #0:
[2018-07-19 20:54:09.466][19][debug][config] source/server/listener_manager_impl.cc:39]     name: envoy.http_connection_manager
[2018-07-19 20:54:09.466][19][debug][config] source/server/listener_manager_impl.cc:42]   config: {"http_filters":[{"name":"envoy.router"}],"route_config":{"virtual_hosts":[{"name":"local_service","domains":["*"],"routes":[{"match":{"prefix":"/"},"route":{"cluster":"sample-cluster"}}]}],"name":"local_route"},"stat_prefix":"ingress_http","codec_type":null}
[2018-07-19 20:54:09.468][19][debug][config] source/extensions/filters/network/http_connection_manager/config.cc:279]     http filter #0
[2018-07-19 20:54:09.468][19][debug][config] source/extensions/filters/network/http_connection_manager/config.cc:280]       name: envoy.router
[2018-07-19 20:54:09.468][19][debug][config] source/extensions/filters/network/http_connection_manager/config.cc:284]     config: {}
[2018-07-19 20:54:09.468][19][debug][config] source/server/listener_manager_impl.cc:414] add active listener: name=listener_0, hash=16491985507912357005, address=<IP_ADDRESS>:10000
[2018-07-19 20:54:09.468][19][info][config] source/server/configuration_impl.cc:94] loading tracing configuration
[2018-07-19 20:54:09.468][19][info][config] source/server/configuration_impl.cc:116] loading stats sink configuration
[2018-07-19 20:54:09.468][19][info][main] source/server/server.cc:410] starting main dispatch loop
[2018-07-19 20:54:09.468][19][debug][upstream] source/common/upstream/logical_dns_cluster.cc:78] async DNS resolution complete for some-domain.com
[2018-07-19 20:54:09.468][19][debug][client] source/common/http/codec_client.cc:25] [C0] connecting
[2018-07-19 20:54:09.468][19][debug][connection] source/common/network/connection_impl.cc:570] [C0] connecting to <IP_ADDRESS>:0
[2018-07-19 20:54:09.468][19][debug][connection] source/common/network/connection_impl.cc:579] [C0] connection in progress
[2018-07-19 20:54:09.472][19][debug][connection] source/common/network/connection_impl.cc:475] [C0] delayed connection error: 111
[2018-07-19 20:54:09.472][19][debug][connection] source/common/network/connection_impl.cc:133] [C0] closing socket: 0
[2018-07-19 20:54:09.472][19][debug][client] source/common/http/codec_client.cc:81] [C0] disconnect. resetting 1 pending requests
[2018-07-19 20:54:09.472][19][debug][client] source/common/http/codec_client.cc:104] [C0] request reset
[2018-07-19 20:54:09.472][19][debug][hc] source/common/upstream/health_checker_impl.cc:170] [C0] connection/stream error health_flags=healthy
[2018-07-19 20:54:09.472][19][debug][upstream] source/common/upstream/cluster_manager_impl.cc:844] membership update for TLS cluster sample-cluster
{"health_checker_type":"HTTP","host":{"socket_address":{"protocol":"TCP","address":"<IP_ADDRESS>","resolver_name":"","ipv4_compat":false,"port_value":0}},"cluster_name":"sample-cluster","eject_unhealthy_event":{"failure_type":"NETWORK"}}
[2018-07-19 20:54:09.472][19][debug][upstream] source/common/upstream/cluster_manager_impl.cc:89] cm init: init complete: cluster=sample-cluster primary=0 secondary=0
curl -v http://some-domain.com:80

About to connect() to some-domain.com port 80 (#0)
Trying 148.x.x.x...

Connection #0 to host some-domain.com left intact

Envoy expects a 200 status code in the response for the healthcheck to succeed. See Architecture Overview: Healthchecking.
Your example curl is returning 301.

I  have also tested with health check returning 200. It made no difference.
On Thu, Jul 19, 2018, 4:19 PM Daniel Hochman<EMAIL_ADDRESS>wrote:

Envoy expects a 200 status code in the response for the healthcheck to
succeed. See Architecture Overview: Healthchecking
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/health_checking#arch-overview-health-checking
.
Your example curl is returning 301.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/3908#issuecomment-406442714,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ47GrhKofm-qY84iEOBSee9mETOA1daks5uIRP_gaJpZM4VXG1O
.

What intrigues me is that the health check event shows address as <IP_ADDRESS> and port 0. It isn't using what is defined in the cluster's socket_address. It also indicates failure_type as NETWORK, which isn't helpful much. Thx.
Here is the health check event log.
{"health_checker_type":"HTTP","host":{"socket_address":{"protocol":"TCP","address":"<IP_ADDRESS>","resolver_name":"","ipv4_compat":false,"port_value":0}},"cluster_name":"sample-cluster","eject_unhealthy_event":{"failure_type":"NETWORK"}}

@psrin7 ,
can you refer this config and try. And hook this to a service which has /health URI
node:
id: nodexxx
cluster: dc1
admin:
access_log_path: /tmp/admin_access.log
address:
socket_address: { address: <IP_ADDRESS>, port_value: 8001 }
static_resources:
listeners:

name: listener_0
address:
socket_address: { address: <IP_ADDRESS>, port_value: 8005 }
filter_chains:

filters:

name: envoy.http_connection_manager
config:
stat_prefix: ingress_http
codec_type: AUTO
route_config:
name: local_route
virtual_hosts:
- name: local_service
domains: ["*"]
routes:
- match: { prefix: "/greetings" }
route: { cluster: envoyservice-1 }
http_filters:

name: envoy.router
clusters:

name: envoyservice-1
connect_timeout: 0.25s
lb_policy: ROUND_ROBIN
type: STATIC
hosts:  [{ socket_address: { address: x.x.x.x, port_value: 2236 }}]
health_checks:

timeout: 1s
unhealthy_threshold : 2
healthy_threshold: 1
interval: 1s
http_health_check: {path: "/health"}

@vgomprakash - Thanks for you inputs. The above configuration works. The caveat is that the type (cluster.discoverytype) is STATIC and you need to provide an IP address. But, I have a need to use DNS. Since, I am using DNS for the hosts address, I have useSTRICT_DNS or LOGICAL_DNS. When I change the type to STRICT_DNS, the active health checking is working. But, it isn't working with  LOGICAL_DNS as the type.

I can confirm that switching from logical_dns to strict_dns resulted in my active health checks working.
The behaviour I observed is that the envoy proxy is not sending packets at all when set to logical_dns. I suspect this may be because it resolves the hosts as '<IP_ADDRESS>', as this is what shows up in the stats endpoint on the envoy admin ui, plus in the debug logs.


Add an example framework to do batch processing.

Add an example framework to do batch processing, to show the flexibility of this framework.

Not sure we shoud do this anymore.


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #81.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #81

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Bug: co-op doesn’t work

Seems as though coop doesn’t work with the mod

[15:10:01.280] During invoking native->managed trampoline
Il2CppInterop.Runtime.Il2CppException: System.NullReferenceException: Object reference not set to an instance of an object.
--- BEGIN IL2CPP STACK TRACE ---
System.NullReferenceException: Object reference not set to an instance of an object.
  at VampireSurvivors.Objects.Characters.SpriteOutlinerControl.ShowOutline (UnityEngine.SpriteRenderer spriteRenderer, UnityEngine.Color colour) [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Objects.Characters.CharacterController.ShowMultiplayerIndicator () [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Framework.GameManager.ResumeGame () [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Framework.GameManager.InitializeGameSession () [0x00000] in <00000000000000000000000000000000>:0
--- END IL2CPP STACK TRACE ---

   at Il2CppInterop.Runtime.Il2CppException.RaiseExceptionIfNecessary(IntPtr returnedException) in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Runtime/Il2CppException.cs:line 36
   at DMD<Il2CppVampireSurvivors.Framework.GameManager::InitializeGameSession>(GameManager this)
   at (il2cpp -> managed) InitializeGameSession(IntPtr , Il2CppMethodInfo* )
[15:10:01.291] During invoking native->managed trampoline
Il2CppInterop.Runtime.Il2CppException: System.NullReferenceException: Object reference not set to an instance of an object.
--- BEGIN IL2CPP STACK TRACE ---
System.NullReferenceException: Object reference not set to an instance of an object.
  at VampireSurvivors.Objects.Characters.SpriteOutlinerControl.ShowOutline (UnityEngine.SpriteRenderer spriteRenderer, UnityEngine.Color colour) [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Objects.Characters.CharacterController.ShowMultiplayerIndicator () [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Framework.GameManager.ResumeGame () [0x00000] in <00000000000000000000000000000000>:0
  at VampireSurvivors.Framework.GameManager.InitializeGameSession () [0x00000] in <00000000000000000000000000000000>:0
--- END IL2CPP STACK TRACE ---

   at Il2CppInterop.Runtime.Il2CppException.RaiseExceptionIfNecessary(IntPtr returnedException) in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Runtime/Il2CppException.cs:line 36
   at DMD<Il2CppVampireSurvivors.Framework.GameManager::InitializeGameSession>(GameManager this)
   at (il2cpp -> managed) InitializeGameSession(IntPtr , Il2CppMethodInfo* )


Black screen leaving fullscreen

Bug description:

In android leaving fullscreen from a youtube embed keeps webview in place but inner video goes offscreen.
To Reproduce:

Just create new project.
react-native init RNWebview

copy paste to file App.js

import React from 'react';
import { View } from 'react-native';

import { WebView } from 'react-native-webview';
const App = () => (
  <View style={{ height: 500, width: '100%' }}>
    <WebView
      style={{ height: 200, width: '100%' }}
      allowsFullscreenVideo
      source={{ uri: 'https://www.youtube.com/embed/zZ-0SHxMIt8' }}
    />
    <View style={{ height: 200, backgroundColor: 'red' }}/>
  </View>
)

export default App;

I also found out if I use a parent View with flexbox it works as expected like this
  <View style={{ flex: 1 }}>
    <WebView

but if one of the parents views doesn't use flexbox it will break.
like this
<View style={{ flex: 1 }}>
  <View style={{ height: 200, width: '100%' }}>
    <View style={{ flex: 1 }}>
      <WebView

Expected behavior:

Screenshots/Videos:

Environment:
System:
    OS: macOS Mojave 10.14.5
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 29.80 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    Android SDK:
      Android NDK: 20.0.5594570
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
    Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.1 => 0.61.1
  npmGlobalPackages:
    react-native-cli: 2.0.1

Tried with<EMAIL_ADDRESS>and it happens. So it happens since fullscreen support on android was enabled

Same Here.
<EMAIL_ADDRESS><EMAIL_ADDRESS>


Fix ChatMessageHistory

The initialization of the array of ChatMessageHistory is buggy.
The list is shared with all instances.

i think there might be some pydantic magic under the hood that prevents sharing across instances, but I might prefer making that explicit anyways so this is great. thanks @pprados!


Added TypeScript Definition

Hello,
Today my friend asked me to help him create TypeScript Definition for this library:
I have created typings with all the props described in the Docs. I hope it will be useful to devs who are using React together with TypeScript like me, which is highly beneficial for props validation and autocomplete of the entire API with parameter types. Even pure JS devs can benefit from it using IDE that can parse TypeScript declaration (Visual Studio, VS Code, WebStorm).
If you want to see how TypeScript integrate with React please check my Starter-Kit project, it's very clean and simple to follow and grasp (using ES6):

https://github.com/piotrwitek/react-ts-jspm-starter-kit

In this PR I have also included typings property for package.json, so developers installing this package can have declarations added to their project automatically from node_modules while importing/requiring packages (TypeScript can do it :smile: )

Typings property explained: https://www.typescriptlang.org/docs/handbook/typings-for-npm-packages.html

hey there! Thanks a lot for the pull request. I think that TS type defs would be a nice help to folks using this component with TS. Here is the concern though, I/we don't use TS, so as soon as the api changes these type defs will be wrong, and no one maintaining RBC will have the motivation or knowledge to update them, or test that they work still. To that end it may be better to host such things on the DT or similar...I know that TS itself is moving away from that, but I'm not sure we can be good stewards of this code once it was merged.

I understand your concerns, no worries, I have already contributed to Definitely Typed, and it was merged with master repo  :)
You can already install it using typings npm package
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/react-big-calendar
Regarding DT from recent TypeScript blog post I don't think they are moving away from DT, as they have introduced a new way of installing typings from DT using npm install command, and all definitions are automatically redistributed from DT to npm registry and also versioned using semver by Microsoft Worker Service as a response to versioning issues with DT.
You can install most definitions by now using command npm i -D @types/<libraryName>, Unfortunately react-big-calendar is not published yet to npm and I didn't have time to investigate why, but I'll check that in my free time.

@piotrwitek I have submitted a PR to definitely typed which updates the exposed module format to be commonjs as that is what is in fact exported by v0.11.1. Hopefully this is ok, let me know if you have any concerns, thanks.

@frankwallis review is ready, I requested some clarification, thx


How to select from custom docker images and optionally include devices

I have a question that I'm trying to figure out how to help people with my add-on...
I have a system DOODS that has a number of docker images and possible USB devices.
I have docker images for several variants of AMD64 which different CPU instructions. I also have USB devices that can be used. I don't want to maintain a ton of different copies of the same add-on.. I would like the user to be able to select the docker image from their config. I would also like to be able to include or not include devices. Hyper-V doesn't support USB passthrough so my default config with devices chokes on Hyper-V.
It really would be ideal to allow customizing this stuff from the user config vs having to maintain a myriad of different Add-Ons for each possible configuration.
There has to be a better way to do this... What am I missing?

Dynamic device options are not support currently. There was some requests and people they want implement that. I look forward for this.
We can try to discover a fix with udev if you want implement it?

I am not sure I follow. The issue is that for this add-on there may or may not be a device. The problem is that you cannot change the device config to say there isn't a device. The add-on properly discovers the device regardless of the name. The udev fix doesn't help me at all. I would rather be able to customize the config to specify devices and docker image tags as I also need to be able to specify different possible docker image tags depending on cpu flags supported.

That means, this will be only possible if someone work on this. I close this PR now because we don't allow feature requests as issue. If you want work on this feature feel free to reopen it for discusion about the implementation.


Allow getSecret() to be used with @secure() objects

Bicep version
Bicep CLI version 0.11.1 (030248df55)
Describe the bug
I am not able to use keyvault getSecret with secure object params passed directly to module.
To Reproduce
This code snippet works:
main.bicep
module testmodule 'testmodule.bicep' = {
  name: 'testmodule'
  params: {
    linuxPassword: kv.getSecret('linuxPassword')
  }
}

testmodule.bicep
@secure()
param linuxPassword string

This snippet does not:
main.bicep
module testmodule 'testmodule.bicep' = {
  name: 'testmodule'
  params: {
    config: {
      linuxPassword: kv.getSecret('linuxPassword')
      SomeOtherConfigParam1: kv.getSecret('foo')
      SomeOtherConfigParam2: kv.getSecret('boo')
    }
  }
}

testmodule.bicep
@secure()
param config object

It yields with an error
Function "getSecret" is not valid at this location. It can only be used when directly assigning to a module parameter with a secure decorator.bicep(BCP180)
Additional context
I need to pass dozens of app settings as secure params  to the module and I was hoping this would work.
Those settings have nested structure.
Is bicep really supporting only basic types as string, bool, array for keyvault getSecret() function?
Any hints here Guys?

Thanks, I was afraid of this answer. That means for my specific scenario getSecret() is useless.
If I do secrets one-by one it is going to be awful mess.

If it's possible to share, can you provide some more detail as to the type of bicep module that would have 256 secret values? It would be helpful to understand the scenario/complexity in more detail.
@miqm / @jeskew -- out of curiosity, is this limit related to untyped objects and could it be addressed after #4158?

@alex-frankel I think we'll need to figure out how the @secure decorator should work on typed objects. Currently, the secure flag can only be declared and never inferred, so the type of config.linuxPassword in @Vox1984's example would be string, not secureString. In theory, if config used property-level declarations, this limitation would no longer apply, e.g.,
@secure()
type secret = string

@secure
param config { [string]: secret }

would assign a type of secureString to every property of config, but you need a @secure() decorator at every level of the object to prevent the value being output. It might make sense to define rules for how the secure flag could cascade (automatically apply to every property of config because it is marked as secure), taint (automatically apply to config because it has one or more secure properties), or both. The current state of #8673 is that @secure() cannot be used on types or type properties because the information flow control expectations are a bit vague.

I can provide an example with array of secure strings that you need to provide. Container apps - https://learn.microsoft.com/en-us/azure/templates/microsoft.web/containerapps?pivots=deployment-language-bicep for example have secrets which is array. So if you want to give the option end user to choose to provide 1, 10 or 100 secrets no easy way to do this.

Hi Guys,
My scenario might be not 100% typical. It is about keeping appServices configuration in key vault, which is probably not the usual case.
The following snippet shows settings I wanted to move to key vault:
siteConfig: {
        linuxFxVersion: 'ubuntu:22'
        acrUseManagedIdentityCreds: false
        alwaysOn: true
        appSettings: [
          {
            name: 'settingNr1'
            value: 'valueofNr1'
          }
          {
            name: 'settingNr2'
            value: 'valueofNr2'
          }
          {
            name: 'settingNrN'
            value: 'valueofNrN'
          }

each app have same section and the naming sometimes overlaps.
So as you see it would be nice to be able to pass to the module with getSecret() secure object appSettings at least.
@alex-frankel I can hit 256 limit easily just multiply appSettings (if we pass them one by one) by the number of apps.
also object solves the issue of overlaping parameters with the same name, but belonging to different apps.

Hi afscrome,
I know I could use the reference, and that was my first choice. But as you said I would need to have managed identity.
Also as far I understand, If I use getSecret and a secure string with @secure() decorator, those values won't be available after the deployment and they won't be in the code repo as well

Use securestring for all passwords and secrets. If you pass sensitive data in a JSON object, use the secureObject type. Template parameters with secure string or secure object types can't be read after resource deployment.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/best-practices

@SimonWahlin -- can you take a look at this one?

It is generally not recommended to use KeyVaults for configuration settings, mainly for performance and throttling reasons, see Best practices for secrets management.
I would recommend looking at Azure App Configuration to centralize configuration over multiple app services and/or function apps. If using managed identity is not an option, you can connect to App Configuration using a Connection String.
If you still want to use a secret to supply an object to your module, you can do this today by using a secret string in your module and use the function json() to convert it to a json object/array as a workaround.
As an example I defined a parameter in my module named appSettingString like this:
@secure()
param appSettingString string

In my sites resource I then convert this to json like this (with unrelated properties cut out):
resource sites 'Microsoft.Web/sites@2022-03-01' = {
  name: name
  location: location
  properties:{
    siteConfig: {
      appSettings: json(appSettingString)
    })
  }
}

This lets me consume the module in main.bicep like this:
param serverFarmId string

resource kv 'Microsoft.KeyVault/vaults@2022-07-01' existing = {
  name: 'Issue8733-kv'
}

module site 'sites-functionApp.bicep' ={
  name: 'site'
  params: {
    appSettingString: kv.getSecret('settings')
    location: 'westeurope'
    name: 'Issue8733-site'
    serverFarmId: serverFarmId
  }
}

The secret settings contains the following data:
[
    {
        "name": "settingNr1",
        "value": "valueofNr1"
    },
    {
        "name": "settingNr2",
        "value": "valueofNr2"
    },
    {
        "name": "settingNrN",
        "value": "valueofNrN"
    }
]

Once deployed it looks like this in the portal:

Closing due to no response. Please re-open if this is still an issue.

I'm not sure why this was closed if no code changes were made to fix it? Is this still an issue? The comments regarding key vault performance are irrelevant since this issue has very little to do with that.

@SimonWahlin @alex-frankel Also curious why this was completed when this is still an issue. Regardless, could this be re-opened? I think there are legitimate uses cases for this.
Moreover, I think the @secure() should be compatible with arrays to enable passing a list of secrets to a module. I put an example below. In my use case, I wish to pull a variable number of secrets from a key vault and use them as protectedParameters in a VM run command. As a workaround, I am having to use a module and script invocation for each secret, but I feel like there should be a better way. Thanks!
myModule 'module.bicep' = {
    name: ...
    scope: ...
    properties: {
        secrets: [for secret_name in list_of_secret_names: kv.getSecret(secretName)]
    }
}

Using LogicApps I have to create Microsoft.Web/connections but I am unable to pass the API Key from getSecrets to parameterValues.
Effectively the CARML Module for Microsoft.Web/connection is a secure object:
https://github.com/Azure/ResourceModules/blob/d84d4f7287616a1b2883837fff5f2fcb14a45e67/modules/web/connections/main.bicep#L23-L25
Which prevents getSecret usage:
module MandrillConnection '../.carml/web/connections/main.bicep' = {
  name: 'TestWebConnection'
  params: {
    location: location
    name: 'mandrill'
    displayName: 'Emailer'
    api: {
      name: 'mandrill'
      displayName: 'Mandrill'
      type: 'Microsoft.Web/locations/managedApis'
      id: '/subscriptions/${subscription().subscriptionId}/providers/Microsoft.Web/locations/${location}/managedApis/mandrill'
    }
    customParameterValues: {}
    nonSecretParameterValues: {}
    parameterValues: {
      apiKey: KeyVault.getSecret('MySecretName') // Function "getSecret" is not valid at this location. It can only be used when directly assigning to a module parameter with a secure decorator.bicep(BCP180)
    }
  }
}

What would the recommended solution be for this?


how to change app name with lua

Describe your problem here.
how do i change the application name that you see at the top left of the window when you're playing, but with lua instead of source
and where do i put the lua file
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

function onCreate()
    setPropertyFromClass("openfl.Lib", "application.window.title", "App Name")
end

function onCreate()
    setPropertyFromClass("openfl.Lib", "application.window.title", "App Name")
end

where do i put the script

mods/scripts/
(or mods/data/song-name/ if you wanna go song-specific)

function onCreate()     setPropertyFromClass("openfl.Lib", "application.window.title", "App Name") end
how do i name it

function onCreate() setPropertyFromClass("openfl.Lib", "application.window.title", "App Name") end
how do i name it

“App Name” to whatever you want

function onCreate() setPropertyFromClass("openfl.Lib", "application.window.title", "App Name") end
how do i name it

“App Name” to whatever you want

it wont change

function onCreate() setPropertyFromClass("openfl.Lib", "application.window.title", "App Name") end
how do i name it

“App Name” to whatever you want

it wont change

same


Apple not approve application

Environment
System:
OS: macOS 12.4
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 37.11 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.11 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.0 => 0.66.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Platforms
iOS
Description
Hi everyone! Recently, we tried to replace the old and deprecated RN Clipboard library with yours, but Apple rejected our applications. When we reverse just this change it's OK and approved, otherwise we can't use your library. Do you have any chance to check it? I'll share Apple's response with you; I hope it'll be helpful. Farewell!

Dear Developer,
We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again.
ITMS-90338: Non-public API usage - The app references non-public selectors in InstantPickerApp: estimatedProgress, initWithFrame:configuration:, isMainFrame, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, setNavigationDelegate:, setProcessPool:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, targetFrame, userContentController, websiteDataStore. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at https://clicktime.symantec.com/3B5NFMBRDMdcEyHtR48XbX47GS?u=http%3A%2F%2Fdeveloper.apple.com%2Fsupport%2Ftechnical%2F

I was facing the same problem on my app. So i ran yarn install on the root folder of my project, change to the ios folder, ran pod install, ran npx pod-install on the same ios folder and tried to re-archive. The Xcode uploaded my app successfully and Apple didn't reject this time.
Also, if you're using Codepush, try to run the codepush deploy command after update your app build on App Store


Add support for resolve.root in webpack

Hi @shacharz, thanks for the suggestion! Could you provide a description (or, preferably, a link to documentation) of how this should work?

https://webpack.github.io/docs/configuration.html#resolve-root
I was thinking of being able to add those roots in the octolinker options, and maybe check those that you want out of all those you've used. If for example you're looking at a different repository that the currently used roots somehow mess with it.

Thanks for the link. Another way this could work is that the extension reads the webpack.config.js file (similar to how https://github.com/OctoLinker/browser-extension/issues/186 would work). That way, you wouldn't have to manually configure it.

even better :)

FWIW, as an extensive user of webpack's resolve.alias in things derived from compass-plugin, I think resolve.root from @shacharz comments and / or resolve.alias would be really awesome to have.
CC @matt-d-rat


Add renames to fetch json output

Currently the json output for fetch gives no indication that an artifact was renamed. e.g.
> coursier fetch --json-output-file dep-tree.json org.apache.commons:commons-io:1.3.2
/Users/cheister/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/commons-io/commons-io/1.3.2/commons-io-1.3.2.jar

> cat dep-tree.json | python -m json.tool
{
    "conflict_resolution": {},
    "dependencies": [
        {
            "coord": "commons-io:commons-io:1.3.2",
            "dependencies": [],
            "directDependencies": [],
            "file": "/Users/cheister/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/commons-io/commons-io/1.3.2/commons-io-1.3.2.jar"
        }
    ],
    "version": "0.1.0"
}

could a renames field be added to the json that lists the artifact renames that were found during the fetch?

I'm surprised that org.apache.commons:commons-io:1.3.2 doesn't appear as is in the output, with a dependency on commons-io:commons-io:1.3.2. That's how relocations are represented internally (as a dependency towards the new name). That could be a bug in the JSON report...
If / when org.apache.commons:commons-io:1.3.2 appears in the JSON report, we can rely on the relocated field of Project to explicitly mark a dependency as relocated.

Adding it as a dependency in the JSON report also works for me.

Is it possible this issue is the underlying failure downstream in https://github.com/sbt/sbt/issues/6976#issuecomment-1188303007 or is that a different bug that should be separately filed?


ValueError: No gradients provided for any variable

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.12
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I have run a PyTorch code that computes the gradient of the gradient w.r.t some computation. It works just fine. Now, I want to translate PyTorch code into TensorFlow but got some errors.
Standalone code to reproduce the issue
Here is the reproducible code. Gist.
The above collab is small and quickly reproduces the run of PyTorch and TensorFlow. PyTorch runs as expected but TensorLow doesn't. Below is the main spot to look at:
Main Part
In PyTorch,
rand_model = Rnadom()
model = Model()
ran_optim = torch.optim.SGD(
    ran_model.parameters()
)

model_params = model.parameters()
loss_mod  = model.forward(x)
loss_rand = model.forward(y)

model_grad = torch.autograd.grad(loss_mod, model_params)
rand_grad  = torch.autograd.grad(
    loss_rand,
    model_params,
    create_graph=True
)

loss = some_method(model_grad, rand_grad)
rand_model.zero_grad()
loss.backward()
ran_optim.step()

In pytorch, the above create_graph=True is crucial.
In TensorFlow, I tried
ran_model = Random()
ran_optim = tf.keras.optimizers.SGD()

model = Model()
model.build(input_shape=(1, 784))
optim = tf.keras.optimizers.SGD(0.01)
model_params = model.trainable_variables

with tf.GradientTape(persistent=True) as tape:
    tape.watch(ran_model.trainable_variables)
    loss_mod = tf.reduce_mean(tf.math.log(model(x)[:, i]))
    loss_rand = tf.reduce_mean(tf.math.log(model(y)[:, i]))
grads_mod = tape.gradient(loss_mod, model_params)
grads_rand = tape.gradient(loss_rand, model_params)

loss = some_method(model_grad, rand_grad)
ran_model_grads = tape.gradient(loss, ran_model.trainable_variables)
ran_optim.apply_gradients(
  zip(ran_model_grads, ran_model.trainable_variables)
)

The tf code gives the following error.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-3-01562609cda8> in <cell line: 33>()
     44         loss += tf.reduce_sum(tf.stack([a, b], axis=0))
     45     ran_model_grads = tape.gradient(loss, ran_model.trainable_variables)
---> 46     ran_optim.apply_gradients(zip(ran_model_grads, ran_model.trainable_variables))
     47
     48

3 frames
/usr/local/lib/python3.10/dist-packages/keras/optimizers/utils.py in filter_empty_gradients(grads_and_vars)
     75     if not filtered:
     76         variable = ([v.name for _, v in grads_and_vars],)
---> 77         raise ValueError(
     78             f"No gradients provided for any variable: {variable}. "
     79             f"Provided `grads_and_vars` is {grads_and_vars}."

ValueError: No gradients provided for any variable: (['Variable:0'],). Provided `grads_and_vars` is ((None, <tf.Variable 'Variable:0' shape=(10, 1, 784) dtype=float32, numpy=

This is probably because the ran_model_grads, ran_model.trainable_variables are not connected. As mentioned in this doc,

When a target is not connected to a source, the gradient will return None

In PyTorch, create_graph=True is used to compute the gradient of the gradient in the later part. To compute grad-of-grad, but didn't work (shown below). The reason probably is the same as before, source and target are not connected.

for i in range(5):

    with tf.GradientTape() as tape1:
        loss_mod = tf.reduce_mean(tf.math.log(model(x)[:, i]))
    grads_mod = tape1.gradient(loss_mod, model_params)

    with tf.GradientTape() as tape3:
        with tf.GradientTape() as tape2:
            loss_rand = tf.reduce_mean(tf.math.log(model(y)[:, i]))
        grads_rand = tape2.gradient(loss_rand, model_params)

    loss = 0
    for a, b in zip(grads_mod, grads_rand):
        loss += tf.reduce_sum(tf.stack([a, b], axis=0))
    [ISSUE] > ran_model_grads = tape3.gradient(loss, ran_model.trainable_variables)
    ran_optim.apply_gradients(zip(ran_model_grads, ran_model.trainable_variables))

But in this case, how to resolve this in TensorFlow?

@SuryanarayanaY Any update so far?

@SuryanarayanaY Hi.
Can we take this as an incomplete feature of gradient tape? Could you please confirm, I like to close this issue anyway?

@innat ,
It seems incomplete implementation. IMO, this can be potential feature request if not a bug. I will escalate the dev team to have a look into this.
Similar issue #61199

A gentle reminder on this topic.

If you switch to pytorch temporarily in keras, when debugging this you can see if it has the correct "grad" function attached to the tensor.
Basically, any math you write MUST contain y_pred somehow since that is the tracked variable (not y_true)
Which led me to have to write this dumb code to make it work for me (I am just trying to write a loss function that ignores correct sided predictions and only consider wrong sided)
return ops.mean(ops.where((y_pred >= 0.) == (y_true >= 0.), 0*y_pred, ops.abs(y_true)*(y_pred/y_pred)), axis=-1)


fix: set correct path for test package

Current dependencies on/for this PR:

main

PR #42   👈

This comment was auto-generated by Graphite.


Publishing latest versions to NPM

Is there any opposition to keeping the latest version bumps published on NPM? I feel like anyone using this package should be aware of the possibility of breaking changes, but there are also new features available in unreleased versions (namely, inline dropdowns) that would be very helpful to have available via NPM.
I figure better to publish all tags and be able to revert in the event of a breaking change rather than not having the latest versions available at all (given the only alternative is to fork and configure installs from the repo).
By the way, thanks for all of the effort put into this so far – we at @contactually look forward to contributing as we're able.

Agreed.  Though, apparently NPM will suddenly not allow me nor any other package owner to publish stardust.  This is strange and frustrating.
I'm getting in touch with their support to get it fixed.  As soon as I can publish the 0.14 I just pushed I will.

Great, thanks!

@jaredhughes 0.14 is now published.  Thanks.


VIM::Buffers() should consistently handle unlisted buffers

In the Perl interface, the VIM::Buffers() function handles unlisted
buffers differently if the buffer is referred to by number (succeeds) or
by name (fails).
It boils down to buflist_findpat() being told to ignore unlisted
buffers:
https://github.com/vim/vim/blob/89894aa671ed1db03d95d38cab300702c242239d/src/if_perl.xs#L1561
This patch changes the behaviour such that VIM::Buffers() will find a
buffer, even an unlisted one, by either number or name.

Codecov Report

Merging #2692 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2692      +/-   ##
==========================================
- Coverage   74.75%   74.74%   -0.01%
==========================================
  Files          92       92
  Lines      133827   133828       +1
==========================================
- Hits       100036   100033       -3
- Misses      33791    33795       +4

Impacted Files
Coverage Δ

src/if_perl.xs
85.86% <100%> (ø)
:arrow_up:

src/if_xcmdsrv.c
84.35% <0%> (-0.36%)
:arrow_down:

src/channel.c
82.82% <0%> (-0.09%)
:arrow_down:

src/gui_gtk_x11.c
47.65% <0%> (-0.05%)
:arrow_down:

src/eval.c
81.22% <0%> (-0.05%)
:arrow_down:

src/if_py_both.h
76.59% <0%> (ø)
:arrow_up:

src/term.c
59.39% <0%> (+0.05%)
:arrow_up:

src/gui.c
47.78% <0%> (+0.1%)
:arrow_up:

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 89894aa...9647e31. Read the comment docs.


[Feature] adjust the width of the drop-down list of published topics

Motivation
Thank you guys for this great software,
The items in the topic history drop-down list gets truncated when the topic is long (around 20 chars) and sometimes these items lacks the latter part so I can't find the exact topic I want. And unfortunately, topics in this kind of length can occur anytime.
Following is the screenshot:

Detailed design
Horizontal auto-growing the list is the most favorable way I can think of because increasing it with fixed amount will not solve the problem especially when the topic is super long.
Alternatives
No alternatives at present.
More detail (optional)
N/A

Hi @puhitaku sorry, I'm late replying, I was on vacation last week and will consider this optimization. But here I would recommend using topic alias for overly long topics, not the alias in mqtt5, you can set it when you add a subscription.

No problems, thanks for a reaction.
Following is the screenshot when I subscribed to testtopic/# with alias test and published a test payload to testtopic/#. The subscription list shows the alias test but any other panes including the publish history list don't shorten the topic with the alias.
Alias feature fits nicely in the subscription list but unfortunately it does not solve the issue I posted 😢

Oh, yes, I will optimize this issue in the next version to try to avoid your troubles, thanks for the feedback.


Added d3 for calculation, added connectNulls, zeroBaseline and barGap Feature

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add support for displaying private key discreetly for snarkos account new

Motivation
Currently, running snarkos account new will show private key dicrectly in current terminal, it would be better to output it in an alternate screen. See following pics

@howardwu Hi sir, suggestions has addressed, looking forward for your review again

@howardwu Hi sir, is there anything else need to add? Or can we get this merged then😁


[Error message] :: Error detaching session Session already detached. Most likely the page has been closed.

Getting this error: "Error detaching session Session already detached. Most likely the page has been closed." in console during test execution if recording is on.
Is there work around or possible solution how to disable this message?I am able to see recorded video, but message in console little bit confusing
I am using cucumber+puppeteer

Hi @ValeryMazharau
Thanks for reaching out and raising your concern.
Could you please share the scenario under which your experience this issue?
Kindly share a sample code to reproduce the same behavior. I would recommend you to try with the latest version which has couple of bug fixes related to switching screen.

Sorry I've accidentally closed this issue. Reopened it again.

I am getting this error as well. I am using version 2.0.2
The case where we get it is when multiple tabs are opened (which are not being followed).

@prasanaworld Any update on this?

I'm getting this error when I start recording, stop recording, and then start the recording again on the same page.

@niieani
This is expected and as per design, once the recording is stopped it cannot be started again.
If we start again, please create a new instance of the PuppeteerScreenRecorder with the same page.
  const recorder = new PuppeteerScreenRecorder(page);
  await recorder.start('./report/video/part1.mp4');
  // do something
  await recorder.stop();

  const recorder1 = new PuppeteerScreenRecorder(page);
  await recorder1.start('./report/video/part2.mp4');
  // do something
  await recorder1.stop();

Hi @brianbrookes-wk,
Kindly accept my apology for the delayed response.
The configuration which you provide seems good to me, However, If you could share a sample test logic under where your experience this issue would be helpful to reproduce the behavior effectively. (A sample code of the test shared in codepen would also help)

@prasanaworld I figured out that creating a separate instance is a workaround for this, however it doesn't feel too intuitive design-wise. Looking at the internals, it should be possible to reuse the same instance, as long as some of the state were to be reset as part of the stop() method. An issue I've had with recording with multiple instances is that sometimes there would be refed timeouts hanging the node process indefinitely, leading me to have to force quit the process with process.exit() at the end of the runtime. Something must not be getting cleaned up properly when multiple instances get attached to the same page. Interestingly, it only happens some of the time.

Any progress on that?

I proposed a solution to this problem in #21


remove {build,release}-image-terraform actions

After recent refactors, the only place these actions are used are inside this repo.
They've both been reduced to doing effectively the same thing:

install tools like terraform, cosign, crane
run terraform init && terraform apply
surface warnings/errors reported from (2) as JSON

In release.yaml we set up creds to push to cgr.dev. In presubmit-build.yaml we push to localhost:5000.
We'll find out if I missed anything in the presubmit leg if the presubmit passes. We won't be able to test the release workflow without doing it postsubmit.

We need to inline it here first: https://github.com/chainguard-images/images-private/blob/6c2b4a1cccf740544e311ded0f0617c9522726f3/.github/workflows/release.yaml#L229

This should BRFAL.


htpasswd not a command

I've deployed this to heroku, but I'm confused about the htpasswd authentication. When I do
./bin/get-htpasswd > ./htpasswd
htpasswd -nB steve >> ./htpasswd

I get htpasswd: command not found. I'm positive that it is me doing something wrong. Any help would be greatly appreciated!

it's this tool https://httpd.apache.org/docs/2.4/programs/htpasswd.html
it's not part of this package


fix(UTXO.get()): Added detection of null-tagged UTXOs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Webcamtest

Is your feature request related to a problem? Please describe.
A web development project which displays your webcam output on the screen built with Html css js & ruby which is fully responsive.
I have checked all the previous issues and current projects in the web dev. folder. This is a new addition to Project Guidance.
I would like to contribute to this issue under GSSOC'22
Describe the solution you'd like.
None
Describe alternatives you've considered.
No response
Add any other context or screenshots about the feature request here.

I would like to contribute to this issue under GSSOC'22. Can the mentors pls assign it to me

Also can anyone guide me, should I put this project in the basic folder of web dev.?


Crashes Game

Describe the problem
When mod is enabled game will not load, get stuck on CustomPathManager.Initialize() CustomPathManager not found, creating new instance. and will not move past it
Steps to reproduce

enable mod
load game

Log files

Savegame?

Screenshots?

Notes or questions?

Use this version of harmony mod https://github.com/boformer/CitiesHarmony/releases/tag/v2.2-0 Follow instructions.

Closing due to lack of activity. Provided solution should fix the problem completely.


Fix Studio Redirect discarding GET Parameters

This Pullrequest fixes #1470.

I tested locally and it works for me! Thanks!
For anyone testing as well: as described in #1470, there is still a bug in the studio code that is used in Opencast right now. That code also removes GET parameters. However, the difference is that with this PR, Studio at least once sees the GET parameters and you can see them in the web console output under "current settings".


🐞 Bug – elm-land customize breaks builds for other developers in a team

Problem
The current customize (and then generate/build/server) implementation doesn't work with team of more than 1 developer. When one developer customizes the app in any way, it breaks build for all other developers, and they are forced to remove the .elm-land directory.
Why this porblem is real and worth solving:

Lets's say we have a team of 5 developers and a repo with 4 elm-land apps (landing, user app, admin app and UI kit, storybook-alike).
When one developer customizes 1 thing in all 4 apps, the remaining 4 devs are forced to remove 16 directories (4 each).

Steps to reproduce:
git clone https://github.com/vladimirlogachev/elm-land-codegen-bug.git
git reset --hard 123d6307c99c8869646c1ebee9a2830b7c6ad5a2 # after `elm-land init`
elm-land build # succeeds
git reset --hard c2fded11aca270d4137393a45d63e41dfc95850d # after `elm-land customize shared`
elm-land build # fails

Your setup

What operating system (Mac/Window/Linux) are you using? Please provide a version!
Please share the output of the following commands:

macOS 14.1.2 (23B92)
node -v: v18.18.0
elm-land -v: v0.19.4

Hey @vladimirlogachev 👋
Let me know if I'm understanding this correctly:

Developer A runs elm-land customize view
Developer A pushes the new src/View.elm to version control
Developer B pulls the update
Developer B has to manually remove their .elm-land/src/View.elm, because it leads to a Elm compiler error

Is that an accurate description of the problem?

Yes, the description is accurate.
I would expect codegen to do the following:

If there is a default module and a custom module, just delete the default and proceed
If there is none (e.g. a developer deleted a custom module later), just create the default one

Hey @vladimirlogachev  – sorry for the wait, this issue is now fixed in v0.19.5 (#160)
Thanks for helping make Elm Land more bug-free! 🌈