[SPARK-23624][SQL]Revise doc of method pushFilters in Datasource V2

What changes were proposed in this pull request?
Revise doc of method pushFilters in SupportsPushDownFilters/SupportsPushDownCatalystFilters
In FileSourceStrategy, except partitionKeyFilters(the references of which is subset of partition keys), all filters needs to be evaluated after scanning. Otherwise, Spark will get wrong result from data sources like Orc/Parquet.
This PR is to improve the doc.

@cloud-fan

Test build #88075 has started for PR 20769 at commit bc98b20.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1381/
Test PASSed.

Test build #88075 has finished for PR 20769 at commit bc98b20.

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

Merged build finished. Test FAILed.

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

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1383/
Test PASSed.

Test build #88077 has started for PR 20769 at commit bc98b20.

Test build #88077 has finished for PR 20769 at commit bc98b20.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1389/
Test PASSed.

Test build #88083 has started for PR 20769 at commit bc98b20.

Test build #88083 has finished for PR 20769 at commit bc98b20.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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


Fix order policy

User attached to a project cannot see order items if they are not an admin when clicking through from orders attached to project.
Implement correct policy for orders.

this is corrected now. closing.


Added require 'fluent/parser'

Failing otherwise. https://github.com/imunew/fluent-plugin-monolog/issues

@amcastror
I think I fix #1 .


CI: for rake + rails, use rack v2

when rake is tested with Rails, sprockets is brought in and has a rack < 3 dependency. the multiverse suite helpers see the unpinned rack version and bring in rackup, which won't work with rack < 3.
lock rake + rails to rack v2 to let the multiverse suite helpers know to not bring in rackup.

This is a fix for the recent scheduled CI jobs failing for Ruby 2.4 and 2.5. Failure reproduced and fix confirmed with rubypants 2.4 testing.


Update build.prop files

Thanks for the PR, looks like everything works great after the gradle update!


Ripgrep globbing on "any-depth" folder search - No such file or directory

Hi, first of all amazing project!
I've been trying grug-far as Lazy included it recently, but I have some strange behaviour with globbing so I was trying to understand what I'm missing and playing around with the syntax.
Here a simple use case porting the correspondent rg command to grug but I get this error:

Here the original rg command:

I have also tried using the -g flag but I get the same.
Here the output of --debug:
rg: DEBUG|rg::flags::parse|crates/core/flags/parse.rs:97: no extra arguments found from configuration file
rg: DEBUG|rg::flags::hiargs|crates/core/flags/hiargs.rs:1260: found hostname for hyperlink configuration: adler.local
rg: DEBUG|rg::flags::hiargs|crates/core/flags/hiargs.rs:1270: hyperlink format: ""
rg: DEBUG|rg::flags::hiargs|crates/core/flags/hiargs.rs:174: using 12 thread(s)
rg: DEBUG|grep_regex::config|crates/regex/src/config.rs:175: assembling HIR from 1 fixed string literals
rg: DEBUG|globset|crates/globset/src/lib.rs:453: built glob set; 0 literals, 0 basenames, 12 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
rg: **/second: No such file or directory (os error 2)

hi @alainrk , thanks for the kind words 😄
Regarding the issue you are seeing, the rg command that grug-far issues will be done relative to your current working directory (:=vim.fn.getcwd() to see it, or maybe just :pwd), but it's spawned as a process directly, so shell expansion for paths is not supported. Using **/something/* as a Files Filter (-g flag) works though.
You can also trigger this action to see the command that is run:
   - Toggle Show Search Command <,p>     Toggle showing search command. Can be useful for debugging purposes.

Ah, I see now. My bad then, thank you for the great explanation, it makes sense now! Thanks!


Right click menu

Just a thought, I find myself using a right click (regardless of OS) to pop up context menu for Copy/Paste a lot. Most apps support. Would be nice feature if Lens did as well. This is on MacOS for reference. I can see many useful shortcuts in this approach. Currently I am forced to go tot eh application menu to do my copy/paste. Not a biggie, but a nice to have

In the meanwhile you can use ⌘+c for copy


mx.io.ImageRecordIter: seed does not change after resetting the iterator

Hi, I'm having some issues with the seed of mx.io.ImageRecordIter set for default at zero, because doing some tries I've noticed that after reading the whole rec.file and resetting the iterator I obtain in the second reading cycle exactly the same sequence of images with the exactly the same crop/rotation/etc for each one.
Does this happen also when I run the model, with the CNN training every epoch on the same identical sequence of images?
Is there a possibility to set the seed to "random"?

ImageRecordIter (shuffle=True)

Shuffle is already set to True, but it mix randomly the images always in the same order after resetting the iterator, because the seed remains fixed to zero. For the same reason random crop and random mirror produce always the same tranformation in differents epochs because the random generator starts always with seed equal to zero.

data_iter = mx.io.ImageRecordIter(
    path_imgrec="./data/caltech_train.rec", # the target record file
    data_shape=(3, 227, 227), # output data shape. An 227x227 region will be cropped from the original image.
    batch_size=4, # number of samples per batch
    resize=256 # resize the shorter edge to 256 before cropping
    # ... you can add more augumentation options here. use help(mx.io.ImageRecordIter) to see all possible choices
    )

Then
for _ in range(10):
    data_iter.reset()
    batch = data_iter.next()
    data = batch.data[0]
    for i in range(4):
        plt.subplot(1,4,i+1)
        plt.imshow(data[i].asnumpy().astype(np.uint8).transpose((1,2,0)))
    plt.show()

gives different results each time

Thanks!


Top level SQForm components should have validationSchema as an optional prop

Looks like on some of our top level components (SQForm, SQFormDialog, SQFormScrollableCard, etc) we forgot to make validationSchema optional. That prop should be optional mostly for the purposes of readonly forms.
We should check everywhere that we accept validationSchema as a prop and ensure it's optional.
One such place: https://github.com/SelectQuoteLabs/SQForm/blob/issue/244-EnableTypeScript/src/components/SQFormDialog/SQFormDialog.tsx#L58

Hello @20BBrown14, can I try to help with this?


A misbehaving gRPC AuthService can crash Envoy

Describe the bug
A gRPC AuthService that returns a response with Status=google.rpc.UNKNOWN will cause Envoy to crash with a stack trace.
To Reproduce
Steps to reproduce the behavior:

Deploy this trivial Go AuthService:

package main

import (
	"context"
	"log"
	"net"
	"net/http"
	"strings"

	"github.com/gogo/googleapis/google/rpc"
	"github.com/gogo/protobuf/types"
	"google.golang.org/grpc"

	envoyCoreV2 "github.com/datawire/kat-backend/xds/envoy/api/v2/core"
	envoyAuthV2 "github.com/datawire/kat-backend/xds/envoy/service/auth/v2alpha"
	envoyType "github.com/datawire/kat-backend/xds/envoy/type"
)

func main() {
	socket, err := net.Listen("tcp", ":8080")
	if err != nil {
		log.Fatal(err)
	}

	grpcServer := grpc.NewServer()
	envoyAuthV2.RegisterAuthorizationServer(grpcServer, &AuthService{})

	log.Print("starting...")
	log.Fatal(grpcServer.Serve(socket))
}

type AuthService struct{}

func (s *AuthService) Check(ctx context.Context, req *envoyAuthV2.CheckRequest) (*envoyAuthV2.CheckResponse, error) {
	log.Println("ACCESS",
		req.GetAttributes().GetRequest().GetHttp().GetMethod(),
		req.GetAttributes().GetRequest().GetHttp().GetHost(),
		req.GetAttributes().GetRequest().GetHttp().GetPath(),
		req.GetAttributes().GetRequest().GetHttp().GetQuery(),
		req.GetAttributes().GetRequest().GetHttp().GetFragment(),
	)
	reqObj := req.GetAttributes().GetRequest().GetHttp().GetPath()+"?"+req.GetAttributes().GetRequest().GetHttp().GetQuery()
	if strings.Contains(reqObj, "deny") {
		log.Print("=> DENY")
		return &envoyAuthV2.CheckResponse{
			Status: &rpc.Status{Code: int32(rpc.UNKNOWN)},
			HttpResponse: &envoyAuthV2.CheckResponse_DeniedResponse{
				DeniedResponse: &envoyAuthV2.DeniedHttpResponse{
					Status: &envoyType.HttpStatus{Code: http.StatusForbidden},
					Headers: []*envoyCoreV2.HeaderValueOption{
						{Header: &envoyCoreV2.HeaderValue{Key: "Content-Type", Value: "application/json"}},
					},
					Body: `{"msg": "denied"}`,
				},
			},
		}, nil
	}
	log.Print("=> ALLOW")
	return &envoyAuthV2.CheckResponse{
		Status: &rpc.Status{Code: int32(rpc.OK)},
		HttpResponse: &envoyAuthV2.CheckResponse_OkResponse{
			OkResponse: &envoyAuthV2.OkHttpResponse{
				Headers: []*envoyCoreV2.HeaderValueOption{
					{
						Header: &envoyCoreV2.HeaderValue{Key: "X-Inject", Value: "Foo"},
						Append: &types.BoolValue{Value: false},
					},
				},
			},
		},
	}, nil
}

using this YAML:
---
apiVersion: v1
kind: Service
metadata:
  name: grpc-auth
  namespace: standalone
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: AuthService
      name: authentication
      proto: grpc
      auth_service: grpc-auth
spec:
  type: ClusterIP
  selector:
    service: grpc-auth
  ports:
  - name: auth-grpc
    port: 80
    targetPort: 8080
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: grpc-auth
  namespace: standalone
spec:
  replicas: 1
  selector:
    matchLabels:
      service: grpc-auth
  template:
    metadata:
      labels:
        service: grpc-auth
    spec:
      containers:
      - name: grpc-auth
        image: {{env "GRPC_AUTH"}}
        ports:
        - name: auth-grpc
          containerPort: 8080

Observe normal "allow" behavior:

$ curl -ki 'https://ambassador.standalone.svc.cluster.local/httpbin/ip'
HTTP/1.1 200 OK
access-control-allow-credentials: true
access-control-allow-origin: *
content-type: application/json
date: Wed, 06 Mar 2019 21:24:14 GMT
server: envoy
content-length: 58
x-envoy-upstream-service-time: 3

{
  "origin": "<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>"
}

Observe crash:

$ curl -ki 'https://ambassador.standalone.svc.cluster.local/httpbin/ip?deny'
curl: (52) Empty reply from server

$ kubectl --namespace=standalone logs grpc-auth-79fd744dcb-pwtf8
2019/03/06 21:22:16 starting...
2019/03/06 21:24:14 ACCESS GET ambassador.standalone.svc.cluster.local /httpbin/ip
2019/03/06 21:24:14 => ALLOW
2019/03/06 21:27:58 ACCESS GET ambassador.standalone.svc.cluster.local /httpbin/ip?deny
2019/03/06 21:27:58 => DENY

$ kubectl --namespace=standalone logs -p ambassador-74b8c869cb-ckxxc
…
[2019-03-06 21:27:58.435][000078][critical][assert] [source/extensions/filters/common/ext_authz/ext_authz_grpc_impl.cc:42] assert failure: response->status().code() != Grpc::Status::GrpcStatus::Unknown.
[2019-03-06 21:27:58.435][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:125] Caught Aborted, suspect faulting address 0x45
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:94] Backtrace thr<78> obj</usr/glibc-compat/lib/libc.so.6> (If unsymbolized, use tools/stack_decode.py):
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #0 0x7fa19a53f46b (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #1 0x7fa19a540790 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] thr<78> obj<envoy>
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #2 0x6b8b4e (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #3 0x6bae27 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #4 0xd6c0d7 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #5 0xd6b560 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #6 0xd70638 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #7 0xd7dbdb (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #8 0xd7f5aa (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #9 0xcc880c (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #10 0xe030dc (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #11 0xe04ed2 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #12 0xe04f02 (unknown)
[2019-03-06 21:27:58.436][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #13 0xe1557b (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #14 0xe024d1 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #15 0xd57508 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #16 0xd57f2b (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #17 0xa9b24a (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #18 0xa9b35e (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #19 0xa91f2c (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #20 0xa935b9 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #21 0xa9335a (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #22 0xa8fc5c (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #23 0xa952fd (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #24 0xa8890b (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #25 0xa88610 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #26 0xa8868f (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #27 0x10d6854 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #28 0x10d6f9e (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #29 0x10d9d27 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #30 0xa83f9d (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #31 0xa75b52 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #32 0xa754e5 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #33 0xa76bea (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #34 0x502bd5 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #35 0x10e8157 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #36 0x10e817c (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] thr<78> obj</usr/glibc-compat/lib/libpthread.so.0>
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #37 0x7fa19ac10cf7 (unknown)
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] thr<78> obj</usr/glibc-compat/lib/libc.so.6>
[2019-03-06 21:27:58.437][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<78> #38 0x7fa19a6010de (unknown)
[2019-03-06 21:27:58.438][000078][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:121] end backtrace thread 78
AMBASSADOR: shutting down (0)

Expected behavior
I expected for the AuthService's {msg: "denied"} JSON message to be delivered to the client:
$ curl -ki 'https://ambassador.standalone.svc.cluster.local/httpbin/ip?deny'
HTTP/1.1 403 Forbidden
content-length: 17
content-type: application/json
date: Wed, 06 Mar 2019 21:31:44 GMT
server: envoy

{"msg": "denied"}

Versions:

Ambassador: 0.50.2
Kubernetes environment: Kubernaut
Version: 1.10.5

Additional context
The docs say that any status other than google.rpc.OK(=0) means "denied".  That doesn't seem to be the case; it seems that any value other than google.rpc.OK(=0)*orgoogle.rpc.UNKNOWN(=2) means "denied"; google.rpc.UNKNOWN`(=2) seems to mean "dear Envoy: please SIGSEGV."
You may be wondering "wait, why are you using UNKNOWN? The status code docs provide an HTTP mapping!".  That mapping is a google.rpc.Code→HTTP mapping; there are many HTTP codes that don't map to a google.rpc.Code, and there are several HTTP codes that map to multiple google.rpc.Codes.  The docs say that UNKNOWN is the appropriate choice for status code "from another address space [HTTP] belongs to an error space that is not known in this address space"; so maybe rpc.UNKNOWN isn't the right choice for http.StatusForbidden in the example above, but for several HTTP statuses it is.
It seems that the Envoy code is trying to use UNKNOWN as an "invalid" sentinel value within Envoy; when it is in fact a valid value that the AuthService can return.  If there is a need for an "invalid" value like that, perhaps -1 should be used?  If there is a need for a special "error-besides-normal-deny" code that an AuthService can return, then (1) it should be documented, and (2) Envoy's behavior should be something other than "exit with a stack trace".
Bonus issue
It seems that Envoy isn't splitting out the HTTP request's query from the path; if you look in the logs above, the gRPC CheckRequest says path="/httpbin/ip?deny" and query="".

This is, of course, easily worked around: Just use a different status code.

This was fixed by Envoy commit https://github.com/envoyproxy/envoy/commit/dcd7f4c57912a4d1045bdda490a5ca920845ae9d, which was present in Envoy v1.10.0 and is in Ambassador.


clean up logging for service port conversion

Clean up logging to address https://github.com/istio/istio/issues/19465

@sushicw Thanks for doing this I was litterally about to push and saw this :) LGTM

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

Test name
Commit
Details
Rerun command

unit-tests_istio
903b700a2c0cd99e5b4044efbc28ee2a607a6600
link
/test unit-tests_istio

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

/test unit-tests_istio

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

Test name
Commit
Details
Rerun command

unit-tests_istio
903b700a2c0cd99e5b4044efbc28ee2a607a6600
link
/test unit-tests_istio

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

/test unit-tests_istio

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

Test name
Commit
Details
Rerun command

unit-tests_istio
903b700a2c0cd99e5b4044efbc28ee2a607a6600
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
d373aba98a95c451895f901920597f1ecdabf207
link
/test integ-istioio-k8s-tests_istio

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


PathFactoids potentially ignores test failures

PathFactoids doesn't use the Specs2 API correctly. This can cause test failures to be ignored in the case where there are other expectations following the path factoid.
Instead of extending ThrownExpectations PathFactoids should extend MustThrownExpectations.

This only seems to apply to the records  and recordsByDirectory functions.


Sycn up brief page

Sycn up with the SAIR Lab ICCV23 page.

Yes, sorry for the bother. Thanks for your reminder.


React Native Navigator

Hi!
Is this component compatible with the default RN Navigator component?
Thanks!

Hello @montogeek,
I didn't test but I think it's possible to make it compatible using the openModal prop.
Here some indications:
        // default example
        openModal={(route) => {
          navigator.push(route); // The ModalWidget will be opened using this method. Tested with ExNavigator
        }}

The object route is defined here
https://github.com/FaridSafi/react-native-gifted-form/blob/master/widgets/ModalWidget.js#L72
As you can see it defines renderScene, getTitle, configureScene, renderLeftButton, renderRightButton
If you are using the default navigator I guess you need to pass this route object directly to your Navigator renderScene and to use it

@montogeek It can work with Navigator, but it does require some extra work (not much though). I updated the openModal={..} function to this:
openModal={ (route) => {
             route.giftedForm = true;
             this.props.navigator.push(route);
         }}>

I set the giftedForm property so that in my navigator methods, I can do some conditional statements. Here is my navigator in my root page render method:
<Navigator
       ref="navigator"
       initialRoute={Routes.getInitialRoute()}
       renderScene={this.renderScene}
       configureScene={this.configureScene}
       navigationBar={this.setNavigationBar()}
/>

The renderScene and configureScene function looks something like this:
renderScene: function (route, navigator) {
//...
     if (route.giftedForm == true) {
          return route.renderScene();
     }
//...
},

configureScene: function (route) {
        //...
        if (route.giftedForm) {
            return route.configureScene();
        }
       //...
    },
}

The Route object provided by Gifted Form has all the necessary methods you need to create your title, left bar button, right bar button, and scene configuration.
The only issue I have is that the modal icons are images, and I can't change the color without going into the package :(. Maybe sometime you can integrate react-native-vector-icons?
Anywho, thanks @FaridSafi for the awesome tool!

Just adding to the "only issue" i had - the icons can be set a tint color, but it looks like the tint color isn't exposed in the API. Or is it? Maybe i missed something in the documentation?

I am getting this error when am using
<GiftedForm  formName='signupForm'
openModal={ (route) => {
route.giftedForm = true;
this.props.navigator.push(route);  }}>
ERROR is : undefined is not an object (evaluating '_this2.props.navigator.push') during openModal .
Any help ?

Try consoling logging "this.props" to make sure you have "navigator" as a property. If not, it needs to get passed into your component, i.e:

@FaridSafi
Hi, would you make an compact with RN navigator?It is good not to bind it to an coustom navigator(@exponentjs/ex-navigator).Follw steps as @m4rcoperuano described,when open modal in android,we should manuly add ToolbarAndroid to it.
Would you make it better.
Thanks.

@montogeek @FaridSafi @m4rcoperuano -
I am trying to get this working and I am not getting the tool bar.
I am using react native navigator 👍
In app.js my configureScene method:
configureScene(route) {     if (route.giftedForm == true) {           return route.configureScene();      }   }
My renderScene method:
renderScene(route, navigator) {     if (route.giftedForm == true) {           return route.renderScene();      } }
After - that my openmodal method is -
 openModal={(route) => {                    console.log('route::',route);                    route.giftedForm = true;                    this.props.navigator.push(route);                   }}
is there anything else I need to to make the toolbar appear ?
Thank you very much in advance for the help.

Bar is just another ...
do anything you want in widgets/ModalWidget -> renderScene()
Don't wait for reply from @FaridSafi , everybody has limited time.
anyway, this module is good enough, oh no, it's fantastic

@girish989 i'm using the nativebase.io, simply put in the header will get the toolbar appear
<GiftedForm.ModalWidget
               title='Gender'
               displayValue='gender'
               image={require('./../../img/icons/apartment.png')}
               scrollEnabled={false}
             >
               <Container style={styles.container}>
                 <Header style={styles.header}>
                   <Button transparent onPress={()=>{this.props.navigator.pop()}}>
                     <Icon name="ios-arrow-back" size={30} style={{color: theme.textColor}} />
                   </Button>
                   <Title style={{color: theme.textColor, fontFamily: theme.fontFamily}}>Gender</Title>
                 </Header>
                 <Content style={styles.content}>
                   <GiftedForm.SelectWidget name='gender' title='Gender' multiple={false}>
                     <GiftedForm.OptionWidget image={require('./../../img/icons/apartment.png')} title='Female' value='F'/>
                     <GiftedForm.OptionWidget image={require('./../../img/icons/apartment.png')} title='Male' value='M'/>
                   </GiftedForm.SelectWidget>
                 </Content>
               </Container>
             </GiftedForm.ModalWidget>

anyone had success with this package an ex-navigation?

@montogeek was wondering how to set the navigator object up.  As per your recommendation, I do not know what Routes.getInitialRoute() would translate into?  I have a navigatorRenderScene function in my main app.  which switches based upon route.id.  I set the route.id as follows:
return (
<GiftedForm
formName='signupForm'
openModal={(route) => {
route.giftedForm = true;
route.id = 'RegisterUser';
this.props.navigator.push(route) ;
}}
onValueChange={this.handleValueChange.bind(this)}
>
and in my main app I set the
navigatorRenderScene(route, navigator) {
_navigator = navigator;
switch (route.id) {
case 'RegisterUser':  //modal page
return (<Navigator
ref="navigator"
initialRoute={Routes.getInitialRoute()}
renderScene={this.renderScene}
configureScene={this.configureScene}
            />)

I have added the configure and render Scene methods.  For the time being I took out the toolbar property.  Am wondering if you can assist here.
Question: What will be the Routes.getInitialRoute()?  How can I get a reference to Routes?
Thanks
......
configureScene(route) { if (route.giftedForm == true) { return route.configureScene(); } }
renderScene(route, navigator) { if (route.giftedForm == true) { return route.renderScene(); } }
....


redundant conformance to CKRecordRepresentable error

Not sure if I am missing something, however in the CKRecordRepresentable.swift when you use a typealias for CKEncodable CKDecoable and CKCodable it causes an error.
I fixed this by changing them all to protocols rather than type alias, which is how it was in the CustomCloudKitEncodable project.

Hi @MadeByDouglas, thanks for the report. Sorry about the delay. Can you provide a little bit more information? What error have you faced?

the error is when you try to use a struct and have it adhere to the CKCodable protocol. it says "redundant conformance to protocol CKRecordRepresentable"

I'm afraid is not just the struct the problem you are facing. If you look at the Example Objects of the project you'll see that all of them are structs as well. May you provide me an example project reproducing the bug?

Right, its not just because of structs. I’m not sure why it works in the example project and not mine. Sorry don’t have time to troubleshoot any further at the moment since I found a work around.

On Jul 24, 2019, at 6:03 AM, Guilherme Girotto<EMAIL_ADDRESS>wrote:
I'm afraid is not just the struct the problem you are facing. If you look at the Example Objects https://github.com/ggirotto/NestedCloudKitCodable/tree/master/NestedCKCodableExamples/Example Objects of the project you'll see that all of them are structs as well. May you provide me an example project reproducing the bug?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ggirotto/NestedCloudKitCodable/issues/2?email_source=notifications&email_token=ACS24RIN57M5TUXTL6Z6A3DQBAZHHA5CNFSM4IABQ5U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2V7QYA#issuecomment-514586720, or mute the thread https://github.com/notifications/unsubscribe-auth/ACS24RNHGZNOMN77XV5NCPDQBAZHHANCNFSM4IABQ5UQ.


Soft deleting Eloquent repository.

This is a good idea. Could you change the newQuery method to use this structure instead?
query = parent::newQuery()
if (this.withTrashed) query.withTrashed()
if (this.onlyTrashed) query.onlyTrashed()
return query

I can return the parent yes. Unfortunately I cannot call them methods without them being static and returning new queries.

Are you sure? I thought the softdeleting scope thingy added macros to the model's query builder.

They have to be called statically. https://github.com/laravel/framework/blob/4.2/src/Illuminate/Database/Eloquent/SoftDeletingTrait.php#L119

$query->withTrashed() and $query->withoutTrashed() works fine in my local install at least.
I can't find the entire trace of how it works, but macros are being added to the builder here:
https://github.com/laravel/framework/blob/5.0/src/Illuminate/Database/Eloquent/SoftDeletingScope.php#L116-L150

Updated code to reflect what you said.

Thanks! I'll look more at this later, I just realized that setting up tests for all versions of Laravel for this is going to be a challenge.

Maybe we should only test one version (latest version)?

That'd be nice, but I use this in 4.1 and 4.2 systems and don't plan on using 5.0 any time soon.
I think I'll just merge this as an undocumented feature and figure out the tests later.
Thanks!


Remove ad-hoc combines/wraps

Replace massive Combine module with a couple simple methods
Replace not-so-small WrapMethods module with Relation#wrap
Encapsulate creation of nodes and wraps in Association::Abstract
Remove all code that was related to generating graphs without
associations

🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉


Clear jobs in scheduler before shutting down quartz scheduler. Added …

…logs

Current coverage is 36.49% (diff: 16.66%)

Merging #228 into develop will decrease coverage by 0.01%

@@            develop       #228   diff @@
==========================================
  Files           260        260
  Lines         14169      14176     +7
  Methods           0          0
  Messages          0          0
  Branches       2379       2380     +1
==========================================
+ Hits           5173       5174     +1
- Misses         8274       8281     +7
+ Partials        722        721     -1

Powered by Codecov. Last update f4a176a...6d2f3bc


fix(select): add scope to zh-cn doc of select

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

:tada: This PR is included in version 1.0.0-alpha.38 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


SSL "Internal error" when spinning up the client

There might be something missing in sslopts (#)
packages: newest dev
client present in clients.db (mycroft node): yes             (double checked the values)
2022-01-20 15:39:08,258 [DEBUG]         [doorpi.event.handler] [3P7Q73] Executing 2 action(s) for OnStartup
2022-01-20 15:39:08,259 [DEBUG]         [doorpi.event.handler] [3P7Q73] Executing Connecting mycroft
2022-01-20 15:39:08,259 [DEBUG]         [doorpi.actions.mycroft.connect] Creating new mycroft connect instance
2022-01-20 15:39:14,183 [INFO]          [HiveMind-presence] Fetching Node data: http://<IP_ADDRESS>:8088/device.xml
2022-01-20 15:39:14,197 [INFO]          [HiveMind-presence] UpNp Node Found: <IP_ADDRESS>:5678
# logs added
2022-01-20 15:39:14,199 [INFO]          [HiveMind-websocket-client] crypto_key: x #  (16-char)
2022-01-20 15:39:14,199 [INFO]          [HiveMind-websocket-client] SSL: True
2022-01-20 15:39:14,200 [INFO]          [HiveMind-websocket-client] host: <IP_ADDRESS>
2022-01-20 15:39:14,200 [INFO]          [HiveMind-websocket-client] port: 5678
2022-01-20 15:39:14,201 [INFO]          [HiveMind-websocket-client] key: x
2022-01-20 15:39:14,201 [INFO]          [HiveMind-websocket-client] useragent: HiveMind-websocket-client
#
2022-01-20 15:39:14,212 [ERROR]         [HiveMind-websocket-client] === SSLError(1, '[SSL] internal error (_ssl.c:1131)') ===
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/websocket_client-1.2.3-py3.8.egg/websocket/_app.py", line 312, in run_forever
    self.sock.connect(
  File "/usr/local/lib/python3.8/dist-packages/websocket_client-1.2.3-py3.8.egg/websocket/_core.py", line 249, in connect
    self.sock, addrs = connect(url, self.sock_opt, proxy_info(**options),
  File "/usr/local/lib/python3.8/dist-packages/websocket_client-1.2.3-py3.8.egg/websocket/_http.py", line 136, in connect
    sock = _ssl_socket(sock, options.sslopt, hostname)
  File "/usr/local/lib/python3.8/dist-packages/websocket_client-1.2.3-py3.8.egg/websocket/_http.py", line 274, in _ssl_socket
    sock = _wrap_sni_socket(sock, sslopt, hostname, check_hostname)
  File "/usr/local/lib/python3.8/dist-packages/websocket_client-1.2.3-py3.8.egg/websocket/_http.py", line 250, in _wrap_sni_socket
    return context.wrap_socket(
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL] internal error (_ssl.c:1131)

tossing "ssl_version": ssl.PROTOCOL_TLSv1 got it running


Unreliable DNS during Container Builds

I have a GitHub Actions pipeline that roughly process like so:

Connect to a private Tailscale network using this Github Action.
Start a docker build of a multi-stage Dockerfile where an internal python package index[1] is accessed to pull dependencies.

[1]: This package index is available within the Tailscale network and is discovered using DNS of an internal DNS server configured in Tailscale.
Step 2 occasionally fail due to DNS lookups for the package index failing, thus DNS resolving not working reliably.

Are you using buildx? I was having this issue, but it seems to be resolved by setting network=host in driver-opts

I was dealing with basically the same issue--container builds that rely on internal resources failing to resolve dns--and the thing that finally fixed it in my case was to configure buildx with the internal dns hosts:
- name: Setup buildx with internal DNS
  uses: docker/setup-buildx-action@v3
  with:
    config-inline: |
      [dns]
        nameservers="<comma separated list>"

Even that is also incosistant, it works sometimes. Mostly doesn't.

Following @henworth's example, I had to change it slightly to get it working:
with:
  buildkitd-config-inline: |
    [dns]
      nameservers=["..."]

Still same though @tpanum.
mines looks like this
- name: Set up Docker Buildx
        uses<EMAIL_ADDRESS>        with:
          buildkitd-config-inline: |
            [dns]
              nameservers=["100.78.xx.xx","100.78.xx.xx"]

And errors out
#45 ERROR: failed to push git.local.puvvadi.net/***/blog:e234247: failed to do request: Head "https://git.local.puvvadi.net/v2/***/blog/blobs/sha256:bbba97e7b63ba8e2a28aa20a0a10b6ba491f29a395e8f7cc5bdf6ff4fe783000": dial tcp: lookup git.local.puvvadi.net on <IP_ADDRESS>:53: no such host

We've also seen this same issue on docker run github actions steps, so it's not a docker build issue only.
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
search vnw05d5vvvpeplv1mpaxmbipab.bx.internal.cloudapp.net tail1abc1.ts.net
root@35f3013f9caf:/opt/code#

This way we had many issues resolving Tailscale hosts inside this container. Fortunately, we managed to fix it using the --dns docker run option:
runner@fv-az1797-395:~/work/repo/repo$ docker run --dns=<IP_ADDRESS> -it --rm \
                --env ENV_VAR \
                <aws_account_id>.dkr.ecr.us-east-2.amazonaws.com/repo:latest /bin/bash
root@35f3013f9caf:/opt/code# cat /etc/resolv.conf
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver <IP_ADDRESS>
search vnw05d5vvvpeplv1mpaxmbipab.bx.internal.cloudapp.net tail1abc1.ts.net
root@35f3013f9caf:/opt/code#

Regards

This also creates a scenarion where any action with
runs:
  using: docker

is unreliable

I think I've discovered why this happened, to me at least.
The GitHub actions runners are on <IP_ADDRESS>/16
\n===== Network Interfaces =====
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo
       valid_lft forever preferred_lft forever
4: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
\n===== Routing Table =====
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev eth0 proto kernel scope link src <IP_ADDRESS>

I have a subnet router that was advertising that same cidr. As soon as I connected Tailscale via actions, any docker based workload could no longer get to the DNS server inside the runner
Status: Downloaded newer image for nicolaka/netshoot:latest
===== DNS Configuration =====
# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.

nameserver <IP_ADDRESS>
search grvplcbrxqwulonopmolb0o12f.dx.internal.cloudapp.net tail9e93b.ts.net

# Based on host file: '/run/systemd/resolve/resolv.conf' (legacy)
# Overrides: []
\n===== Network Interfaces =====
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen [100](https://github.com/jaxxstorm/tailscale-actions-example/actions/runs/9829717610/job/27135072514#step:5:101)0
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo
       valid_lft forever preferred_lft forever
5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
\n===== Routing Table =====
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev eth0 proto kernel scope link src <IP_ADDRESS>
\n===== DNS Resolution Test =====
;; communications error to <IP_ADDRESS>#53: timed out
;; communications error to <IP_ADDRESS>#53: timed out
;; communications error to <IP_ADDRESS>#53: timed out
;; no servers could be reached

;; communications error to <IP_ADDRESS>#53: timed out
;; communications error to <IP_ADDRESS>#53: timed out
;; communications error to <IP_ADDRESS>#53: timed out
;; no servers could be reached


Trying to understand fail/success test status

We are currently running an OpenSpeedMonitor instance using version 4.5.2 git commit id 1640cd27f8.
This OpenSpeedMonitor instance is connected to a local WebPageInstance and the flow is working fine overall.
The part we are trying to understand is the status reported by OpenSpeedMonitor for any given script where the WebPageInstance reports logs for our test runs as:
2018/05/17 04:45:10 - Test Created
2018/05/17 04:45:11 - Starting test (initiated by tester wpt-regional-agent-<IP_ADDRESS>)
2018/05/17 04:45:11 - Run 1 assigned to wpt-regional-agent-<IP_ADDRESS>
2018/05/17 04:46:13 - Test Run Complete. Run: 1, Cached: 0, Done: 1, Tester: wpt-regional-agent-<IP_ADDRESS>, Test Run Error: "Page Load Timeout"
2018/05/17 04:46:13 - Marked shard 1 as complete: {"1":true}
2018/05/17 04:46:13 - All 1 runs are complete
2018/05/17 04:46:13 - Extracting 932156 byte uploaded file '/tmp/phpnyGlnV' to './results/18/05/17/R1/J'
2018/05/17 04:46:13 - Done Processing. Run: 1, Cached: 0, Done: 1, Tester: wpt-regional-agent-<IP_ADDRESS>, Test Run Error: "Page Load Timeout"
2018/05/17 04:46:13 - Test Complete

With some steps with a non-zero exit code matching the log above:

Nevertheless, OpenSpeedMonitor reports these runs as successful.
I took a look at your demo in particular to jobId=125 which includes failed tests in OpenSpeedMonitor but the correspondent WebPageTests steps reports have zero exit codes:

Questions:
a. How does OpenSpeedMonitor determine to fail or pass a test? Do WebPageTest exit codes play any role in that process?
b. Are results for each test run stored in the OpenSpeedMonitor db including WebPageTest exit codes? We were considering running queries against this db to get more accurate status per run but could not find a table/field that could help us with this purpose. Perhaps we overlooked it thus the question.
c. Do you have any recommendations to achieve failing a test in OpenSpeedMonitor when WebPageTest reports at least one step with non-zero exit code?

Hi there,
OpenSpeedMonitor distinguishes between a JobResult and an EventResult.
An event result is the entity which contains the performance metrics for a single measurement of a specified page. There you can also find the wptStatus which corresponds to the error code you posted in the images like 0, 99995 and so on.
A job result contains all the necessary informations for a job which is started with the OpenSpeedMonitor like a reference to the navigationScript, WPT server and location, ... Also this entity contains both:

a wptStatus: An optional String containing error messages from WPT server and
a httpStatusCode: status code returned by WPT server (such as 200, 101, ...)

A job result will be persisted no matter what. Either the test run is succesful, then its httpStatusCode will be 200 (this is the status code returned from WebPagetest) or we get an error like a timeout than this status code will be persisted. We get the codes by parsing the result xml/json from WebPagetest which you can view by replacing the URL from a test
http://<wpt-base-url>/result/<test-id>/

with the following part:
http://<wpt-base-url>/jsonResult.php?test=<test-id>/

Then you get the JSON of the test result and you can search for statusCode which is the status of the job result. The error codes for the single steps are named result and you can find them under data > runs > 1 > firstView > steps in the JSON (steps is a list of steps where each step contains an entry named result).
Having said that the answers to your questions would be:

Yes, WebPagetest exit codes play a role in deciding if a single step or job was successful or not.
Yes, the exit codes are also persisted in the db. The fields you are looking for are:

wpt_status for event results
wpt_status and http_status_code for job results

We actually tried to achieve the quit opposite approach. We want a job result to be persisted even though some steps failed. This is because we often have quite long measurement scripts and we don't want to lose the whole job result just because one or more steps didn't work.
We have some tickets in the backlog for more advanced handling of failed steps but currently we do not have them on a high priority. You are welcome to take a look into that as contribution is always appreciated.

I hope I could give you some useful insights. If you have further questions feel free to ask.

Hi again,
I'm closing this issue, since there is no activity anymore.
But I wanted to give an update on the current error handling:
We introduced the JobResultStatus a while ago (see here) and we are handling the error cases in another way since my last answer.
A JobResult gets persisted every time when it is started (defined via a cron job). Depending on the WPT status codes we map them onto useful status codes in OSM which you can see in linked file above. This means that we now detect if a WPT job failed and mark the job in OSM as failed as well when it matches a code in the JobResultStatus, for example Incomplete.
We also display the current status of Jobs on the start page of OSM. The logic for the status of jobs is to check the last 5 job runs and when at least one failed, we mark it orange and when at least 2 out of the last 5 failed we mark it red.
I hope this helps and as always feel free to ask when there is something not clear.
Cheers.


"Using environment variables" does not write config to ".env"

At the moment checking this will load config from an existing .env file, but will not write config to a new one, should it not exist.
It should be trivial to fix this and DatabaseAdapterRegistry to build an .env writer that just writes to root dir.

Should the installer write to a .env in these circumstances? Did it used to write to a _ss_environment.php?
I feel like we shouldn't be doing this...

I think we all have different understandings of what this means... I understand "read from env" but @sminnee reads it as "write to env".
The bug is "the behaviour is not clear", but the enhancement is "make it write to .env if it doesn't already have these settings". Even if we don't implement the enhancement we need to fix the UX issue.

OK I believe it's pretty clear that the installer should be writing the .env file.
By "install SilverStripe" I mean "set the environment up as close as practical to how an experienced SilverStripe developer would set their environment up".
And as I'm sure you'll agree, in SS3 this means writing database credentials to an _ss_environment.php file, and in SS4, writing to a .env file (updating the apache config to include env vars there isn't really practical).
I guess from the above comments that this wasn't the previous behaviour. But I can't see any argument for this not being the default behaviour.

My understanding was that all the settings used to be written to mysite/_config.php and it didn't set up an env file if you asked to set up from one.
It just used that env file to populate the installer instead of manually entered details.
Now I'm not against changing how the installer works, but if the aim is to "set the environment up as close as practical to how an experienced SilverStripe developer would set their environment up", then I don't think this feature should be opt in it should be the only way of doing it...
I caveat this all with the fact I rarely ever touch the installer when setting up a site so I may misremember how it works and apologies if that's the case.


feat: download snapshots from CloudFlare

Summary of changes

Changes introduced in this pull request:

Download snapshots from CloudFlare.
Use reqwest instead of aria2c.
Log to stderr in forest-tool.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

aria2c is no longer needed now that the snapshots are downloaded from a CDN.

aria2c is no longer needed now that the snapshots are downloaded from a CDN.

Did you compare the speed of both approaches?

aria2c is no longer needed now that the snapshots are downloaded from a CDN.

Did you compare the speed of both approaches?

My download speed in Europe from CloudFlare is top-notch. Hailong tested from China and got 12MiB/s from CloudFlare (using wget) and only 300KiB/s from DO (using aria2c -x5). CloudFlare has much better bandwidth than non-cdn DO.


Cannot pay when transaction is being signed

a transaction seems "stuck" in the signing stage, it has been many days since it was initiated
if I re-attempt the transaction I receive the error in the title

Can you try running :btc-wallet|command [%broadcast-tx <hex code for tx here>] (without the lesser/greater than symbols)?

thanks for the reply, I tried what looked to potentially be the broadcast tx from the output of :btc-wallet +dbug and got a generator failure error...I don't get the entire dojo scrollback in webterm and my ship is hosted so I'm unsure if the tx I tried is the one I need to run the command against
is there a command that will print a list of transactions I can use to get what I'm looking for?

>
dojo: nest-need
[ [ now=@da
   eny=@uvJ
   beak=[p=@p q=@tas r=?([%da p=@da] [%tas p=@tas] [%ud p=@ud])]
 ]
 [   comm
   ?(
     [ %add-wallet
       xpub=@ta
       fprint=[wid=@ dat=@ux]
       scan-to=u([p=@ud q=@ud])
       max-gap=u(@ud)
       confs=u(@ud)
     ]
     [%broadcast-tx txhex=@t]
     [%check-payee payee=@p]
     [%check-provider provider=@p]
     [%delete-wallet xpub=@ta]
     [%gen-new-address %~]
     [%init-payment payee=@p value=@ud feyb=@ud note=u(@t)]
     [ %init-payment-external
       address=?([%base58 @uc] [%bech32 @t])
       value=@ud
       feyb=@ud
       note=u(@t)
     ]
     [%set-current-wallet xpub=@ta]
     [%set-provider provider=u(@p)]
   )
   %~
 ]
 %~
]
dojo: nest-have
[ [ now=@da
   eny=@uvJ
   bec=[p=@p q=@tas r=?([%da p=@da] [%tas p=@tas] [%ud p=@ud])]
 ]
 [[%broadcast-tx @ux] %~]
 %~
]
> :btc-wallet|command [%broadcast-tx 0x1.0000.0000.0101.4e62.ff66.254b.0697.ea72.3a42.b6c7.06f3.13c6.052e.03a4.2fe0.51ca.168a.3dcd.830d.0100.0000.00ff.ffff.ff02.cec2.4a00.0000.0000.2200.209f.5678.943e.783a.ebf8.e6ca.a44b.08bf.204e.1950.9670.76cf.82f8.4cb7.a8c0.8f6a.ffb1.f302.0000.0000.0016.0014.3f04.f696.720a.f170.6f8b.892e.bcd3.c5c0.4fc8.b3f3.0248.3045.0221.0092.40ca.37f1.bebb.5fa5.2c64.2f5a.1c9a.bee2.79d9.eff1.fcf3.7255.4e80.f17a.412e.7002.2033.28c0.d847.cd9f.fed9.cf35.0d3a.c833.ad36.b68c.0f36.9633.d695.401d.7f96.7aee.9901.2102.f220.39de.13c4.6264.913e.5660.a637.f6b2.84d3.2606.ad58.c67e.e12f.3536.94ee.5740.0000.0000]
dojo: generator failure
~riblur-sipryx:dojo>

Well, at least we know it was a valid command now. It looks like there may be something else going on here on the backend. Will look into it this week.

anything else needed from me here?

Hey, sorry @riblur-sipryx, this got bumped in favor of a bunch of work on groups. I will try to get to it this week.

@liam-fitzgerald this one goes over my head, any ideas on what's happening here?

Not sure @timlucmiptev might know

anyone?

nprz might know more, he's worked on the bitcoin stuff more recently

Sorry for the delayed response. Not sure I saw what you are describing when working on the bitcoin provider. You're attempting to broadcast a tx from the wallet? Is it possible the tx is in a format not recognized/accepted by the urbit btc wallet?
I did run into a separate issue with the UI not updating with correct amount of BTC while working on the grant, but sounds like you're describing something different.

You're attempting to broadcast a tx from the wallet?
yes, the transaction was executed via the UI

Is it possible the tx is in a format not recognized/accepted by the urbit btc wallet?
not sure, most likely not as this was done within the UI entirely

at this point I would be fine with just cancelling that transaction somehow from terminal and trying a different one, just stuck at this point as the tx is stuck and I can't execute new ones, any assistance is appreciated

other than the code itself does any documentation on the wallet/provider exist?

other than the code itself does any documentation on the wallet/provider exist?

anyone?

other than the code itself does any documentation on the wallet/provider exist?

anyone?

Not that I know of, unfortunately.

thanks for the reply
anyone familiar with how to open the urbit wallet in another application? it isn't clear to me how this might be done as I'm not familiar with exactly how the private key is generated other than it is derived from a master ticket

closing as the wallet is/has been unsupported, anyone looking for help should find me on urbit ~riblur-sipryx or join ~pindet-timmut/urbitcoiners


Custom Region Navigation Support

Sometime I have to write thousand lines of code, and using custom code region (#region ... #endregion) could help to make the code more readable.
In Pycharm I know there is a shortcut Ctrl+Alt+. to show the TOC of all custom regions, it really improves the efficiency.

I think #58658 is the same request. Closing as dup.


Ionic 4 version doesn't work well on device: cannot change active tab

I cloned the latest version of https://github.com/zyra/ionic-super-tabs-example and installed all dependencies. It works fine in the browser. I also updated my own application to the latest version of Ionic Super tabs (v6.0.0-beta.8), and it's also working fine in browser.
Both applications are installed correctly on device, I can see the interface outside of super-tabs, and I can see super tabs toolbar. But changing tabs doesn't work. Tab buttons are clickable, indicator moves left and right, but content is not changed and also I cannot swipe.
This happens on both Android and iOS emulators.
I know Super Tabs for Ionic 4 is still in beta, just wanted to ensure you don't miss this issue. I'd be really thankful for any updates on this. It prevents me from upgrading my app to Ionic 4.
P.S: created a duplicate issue there as well, wasn't sure what's the right place for it
https://github.com/zyra/ionic-super-tabs-example/issues/31

@agrinko this is the right place as it is clearly an issue with ST not the example implementation.
I can confirm this issue on an actual device (iPhone 6s, Safari, iOS 12.2). Unfortunately this issue doesn't throw an error on the iPhone, so I tried it in an older Android browser and could reproduce the same issue. In the old Android browser it throws this error:
TypeError: r.scrollTo is not a function
    at scroll (chunk-39d8d03b.js:1)
    at Array.<anonymous> (chunk-39d8d03b.js:1)
    at p (supertabs.core.js:5)
    at d (supertabs.core.js:5)
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
    at Object.onInvokeTask (core.js:17289)
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:422)
    at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)
    at push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask (zone.js:498)
    at ZoneTask.invoke (zone.js:487)

Hope it helps.

#379 fixed this

@st3h3n , that's great, thank you!
Don't you know when it is going to be released (i.e. tagged beta.9)?

no, but you can fix it yourself in the meantime:
super-tabs-container {
  height: 100%!important;
}

Good idea, thank you!


Create Game Functionality

Create Game Functionality
A user needs to have the ability to create a game within the system for other users to play on. The ability to add additional users through an invite system will be implemented later as it is not part of the MVP. This functionality should be part of the GameManager class.
Detailed Requirements

Invitees should not contain the user that is creating the Game. It would not make sense to invite yourself. This does not need to throw an error, but it should be remedied without alerting the user.
Spectators should never contain any invitees. We don't want a player who is playing to be able to spectate the game as well. This should throw an error.
The game should be in an started state upon creation (For MVP)
Any Unit that is on the Map should be owned by user (For MVP)
No invites will be sent out from this method (For MVP)

Implementation
GameManager.cs: public static Task GameManager.CreateGame(User user, ObjectId mapId, List inviteeIds = null, List spectatorIds = null)

user is the user that creates and owns the new game

The user should be added to the Players array

map is the Map that the game will be played on.

map contains a list of Unit that should be copied to the game's Units as it is created.

invitees is a list of ObjectId that represent Ids of users that will be taking turns within the game. They should be included in the game's Players property.

If no value is provided, invitees will default to null and the only User in the Players list should be user
This list should not include user. Add a check to remove user from invitees if it exists.

spectators is a list of PlayerInfo that have the ability to watch the game. They should be included in the game's Spectators property

If no value is provided, spectators will default to null, and Spectators will be null on the created Game
spectators should never include ANY PlayerInfo in the PlayerInfo array (unique on Id). Add a check to assure this. If this check fails (a player is present within spectators), throw an IllegalArgumentException with a proper message.

CurrentPlayer should default to user (For MVP)
CreateGame returns the ObjectId of the newly created Game.

Tests

Happy Path
Creation of a game with just the first two parameters
Creation of a game with an invitee
Creation of a game with two invitees, one of which is user.  Players should have a Count of 2.
Creation of a game with no invitees and a spectator
Creation of a game with no invitees and a spectator that is user. This should throw an error.

Closing issue.


Initial test integration

Integrate testing tools into the project. My thinking is to use ScalaCheck inside DocTest blocs.
This is not a ticket to implement all the tests, just to setup the tools.

Implemented


feat: Support branch in resolve.

Fixes #3616.

CI is failing

CI is still not happy

@mcollina CI is finally happy!


RLS 1.1.1

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

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.

The pypy builds failed for 1.1.0 as well. I think they can be ignored unless someone wants to investigate.

@TomAugspurger what needs to be done here

Just need to merge. Are you listed as a maintainer here? If not then we can add you on the next build.


Fix container size for portrait videos

Previously, the <InlinePlayer> would always mirror the aspect ratio of the video itself, even when its height was greater that its width. This lead to portrait videos not using the available vertical space and instead be displayed too small. By swapping the values in these instances, we make sure that the container will always have a "landscape" orientation.
Closes #775

Not necessarily the whole screen, but basically what the existing height calculation says: 90vh - 80px or sth like that. Certainly more than right now.

Might be partially fixed in #792


Add Vue 3 compatibility

Attempting to add Vue 3 support while maintaining Vue 2 support.

[x] Works on Vue 3 - Connects and subscribes to a real websocket server without error.
[x] Works on Vue 2 - Works the same as it did before.
[x] Test suites are passing on Vue 3 and Vue 2.

Thank you so much for working on adding Vue 3 support!

@x8BitRain Kindly send me the code snippet for setting up ActionCableVue in Vue 3 so I can add it to the readme for other users.

@x8BitRain Kindly send me the code snippet for setting up ActionCableVue in Vue 3 so I can add it to the readme for other users.

You mean like this?

import { createApp } from "vue";
import App from "./App.vue";
import ActionCableVue from "actioncable-vue";

const websocketOptions = {
  debug: true,
  debugLevel: "error",
  connectionUrl: wss://localhost:8080,
  connectImmediately: false
};

createApp(App)
  .use(store)
  .use(router)
  .use(ActionCableVue, websocketOptions)
  .mount("#app");

I was wondering if there would be a way to access the $cable in the composition API. I tried passing the context and importing the destructurized cable from the library but I don't seem to understand how to do it. I can use it in Vue3 but I think it should be usable inside setup method as I need to use the old lifecycle hooks outside of setup to access this.$cable

I was wondering if there would be a way to access the $cable in the composition API. I tried passing the context and importing the destructurized cable from the library but I don't seem to understand how to do it. I can use it in Vue3 but I think it should be usable inside setup method as I need to use the old lifecycle hooks outside of setup to access this.$cable

You can't access this from setup() so you can only access this.$cable is if you export access to it from a service or store. You store this.$cable in vuex and access it from within setup() via store.state. Not ideal but it works. Not 100% sure on this is the only way though.

I ended up using getInstance from vue like so:
const instance = getCurrentInstance();
const cable = instance.ctx.$root.$cable
Not ideal either but it works. I declare the channels like in the example and I call my setup methods in the channels hooks like so:
received(data) {
this.receivedMessage(data)
}
granted that I returned the function receivedMessage in the setup function.

@gglobensky how setup works can you show a little demo


pub doesn't like the location of the SDK to change

What steps will reproduce the problem?

Install SDK in some directory - /dart-editor/12224/dart-sdk
Run 'pub install' on a project that uses unittest from the SDK
Reinstall SDK in a new directory /dart-editor/12279/dart-sdk
Try to run 'pub install' again

What is the expected output? What do you see instead?
DirectoryIOException: Directory listing failed, path = /Users/kevin/source/github/dartlib/packages/unittest (OS Error: No such file or directory, errno = 2)
Bonus issue: --trace doesn't show the stack trace
What version of the product are you using? On what operating system?
Mac, 64, 12279
Please provide any additional information below.

This issue has been moved to dart-lang/pub#109.


Fixes #278 , Maps now plotted through location_mark which adds fuzziness in marker locations

I am merging this for now as this does not review only location_mark is used in place of location_point.Tested locally.


Error

Describe your bug here.
Why does some mods show this error at the time of loading? They are more or less recent mods

Crash Log or logcat logs (if existing)
No response
Are you modding a build from source or with Lua?
I am not modding
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
No

Does it happen in probability or every time？

@beihu235 It always happens when you load a song from a mod, for example that one from the gifanny and others at the time of loading it releases that error and takes me out of the game

Are you sure your assets files are in order

The problem you reported is because the first one is missing ogg file and the second one is missing xml, which is not a normal error

El juego no deja abrir

There is a bug that in some songs the instrumental and the voices do not sound synchronized, for example the song toyboy sounds similar, or various mods

有一个错误，在某些歌曲中，乐器和声音听起来不同步，例如歌曲“toyboy”听起来相似，或者各种mod

If the number of frames is not stable when the music starts playing, this will cause vocal delay, which I also found after the release of v1.1.0

Why is everyone reporting mistakes here


Search cosmetics enhancement

Cosmetic fixes on small screens

Focus search input after clicking the magnifying glass
On first load, show search box when typing

Fixes #320

Resolves: #320

The old website is hopefully EOL soon, so we're probably not going to merge anything here anymore.

@razzeee Is there alreday a preview or source for the new Website aviable?

The old website is hopefully EOL soon, so we're probably not going to merge anything here anymore.

Wait, I've never heard of this, where's the new website? Or the announcement at least?

https://github.com/flathub/backend/
https://github.com/flathub/frontend
You can find a sort of preview here on my vercel https://flathub.vercel.app/ but that's not an official place. Just so you know.

https://github.com/flathub/backend/ https://github.com/flathub/frontend
You can find a sort of preview here on my vercel https://flathub.vercel.app/ but that's not an official place. Just so you know.

Looks nice and smooth with Next.js


[Bug] Constraint withTransactions::<N>::MAX_TRANSACTIONS will make the network stuck in some circumstances

https://hackerone.com/reports/2310792
Summary:
In snarkVM, the number of transactions and aborted_transactions is limited by Transactions::<N>::MAX_TRANSACTIONS (65536):
    fn verify_transactions(&self) -> Result<()> {
        let height = self.height();

        // Ensure there are transactions.
        ensure!(!self.transactions.is_empty(), "Block {height} must contain at least 1 transaction");

        // Ensure the number of transactions is within the allowed range.
        if self.transactions.len() > Transactions::<N>::MAX_TRANSACTIONS {
            bail!(
                "Cannot validate a block with more than {} confirmed transactions",
                Transactions::<N>::MAX_TRANSACTIONS
            );
        }

        // Ensure the number of aborted transaction IDs is within the allowed range.
        if self.aborted_transaction_ids.len() > Transactions::<N>::MAX_TRANSACTIONS {
            bail!(
                "Cannot validate a block with more than {} aborted transaction IDs",
                Transactions::<N>::MAX_TRANSACTIONS
            );
        }

However, this can be violated with BullShark in some circumstances and will block the whole network.
Steps To Reproduce:
No
Proof-of-Concept (PoC)
In Bullshark, the subdag may commit many transactions at one time. For example, the max number of transaction in one batch is:
pub const MAX_TRANSMISSIONS_PER_BATCH: usize = 250; // transmissions
Suppose we have 100 validators,  at each round's certificate, we have at least 34 certificates to commit. If in some circumstances, we commit a subdag with 20 rounds, then it will contain 34 * 250 * 20 = 165000 transactions. As 165000 > 2 * MAX_TRANSACTIONS, the network will halt because snarkVM won't commit:
        atomic_finalize!(self.finalize_store(), FinalizeMode::DryRun, {
            // Ensure the number of transactions does not exceed the maximum.
            if num_transactions > 2 * Transactions::<N>::MAX_TRANSACTIONS {
                // Note: This will abort the entire atomic batch.
                return Err(format!(
                    "Too many transactions in the block - {num_transactions} (max: {})",
                    2 * Transactions::<N>::MAX_TRANSACTIONS
                ));
            }

Another issue is that: In fn atomic_speculate<'a> function, the aborted transaction may exceed MAX_TRANSACTIONS. Suppose, we call fn atomic_speculate<'a> with MAX_TRANSACTIONS + 10 transactions. However, if all the transactions are aborted, then the function will return MAX_TRANSACTIONS + 10 aborted transactions. Then it will not be accepted as a block and will halt the whole network.
Fix Suggestions
Make sure that: Once Bullshark commits a subdag, snarkVM must successfully commit the subdag. Add more check before signing a BatchPropose. If a subdag contains too many transactions, we can just drop some transactions.
Impact
Constrain withTransactions::<N>::MAX_TRANSACTIONS will make the network stuck in some circumstances

Closing with #2309


'dotnet' platform support

For use by non-desktop runners, e.g. DNX.
Requires linking to xunit 2.1.

Any plans to support .net core?

Hi Albert. This is planned for the 2.1 release. This will be linked to
xunit 2.1 (currently in beta), which also introduces .net core support.
On 10:50, Thu, 27 Aug 2015 Albert Weinert<EMAIL_ADDRESS>wrote:

Any plans to support .net core?
—
Reply to this email directly or view it on GitHub
https://github.com/xbehave/xbehave.net/issues/224#issuecomment-135343769
.

@adamralph is there any nuget distribution of betas for 2.1? I'm specially interested in the dnx support.

@mvalipour none yet I'm afraid. It seems to be a popular theme so I'm marking this as a top priority.

@adamralph
OK, I managed to build a dnx package and get xbehave to run successfully on it!
The code is on a repo here (for now)
https://github.com/mvalipour/xbehave.dnx.test
99.9% of the code is same as the desktop execution, but I have copied them across for now.
if you are happy with this, we could discuss merging this into the main repo.

@mvalipour it's great that you got it working!
Would you like to send a pull request?

@mvalipour I'd like to play around with your DNX version of Xbehave.
Is your repo replacing the 'Xbehave' dependency in a typical DNX project?
Is the 'ScenarioX' attribute required to make this work?
I have several DNX projects using beta7, and already linking with xunit 2.1, and had been using xunit.runner.dnx.  Just wasn't sure what I'd need to change to try out your test build?

@kirk-marple I'm preparing a PR to be hopefully be merged into xbehave, however you are welcome to use my unofficial version for now.
There is a test project in my repo which contains the calculator example. And yes, that attribute has been added on my repo to hack around, however would change on the finished version.

@mvalipour Thanks, if this is being worked on, I'll wait for the beta of xbehave, I guess.  I'd prefer not to use the hacked attribute for now.
@adamralph Adam, is there any ETA on when you may have a beta ready?  We really want to move to Xbehave ASAP, but are using DNX projects.  I have some tests built, but no way to run them yet :)

@kirk-marple it depends how soon @mvalipour can send the PR :smile:

Update
I have pulled-together dnx projects which can be found here. However there are some issues I'm having trouble with which maybe not be fixed until next week (I'm unavailable for a week).
Specifically the issue is around the fact that xunit picks up dotnet execution and hits this not-supported-exception which is invoked by this part of xbehave.
In case you guys wanted to try it out, I have pushed these temporary packages to my myget feed at:
https://www.myget.org/F/mvalipour/

PR: #279

@adamralph It's been a while since the PR, do you have any plans for merging?

@mvalipour I had a brief look but I haven't had time to look in detail. The addition of dotnet TFN support is quite a major change and I don't really know exactly how things should look without spending a lot more time on it. Your PR is hugely appreciated, please don't take the delay in merging as a lack of appreciation. I'm hoping to get enough time in December to not only merge your PR but also push out the  stable package to NuGet.

@adamralph not at all, I would look forward for that to happen.

for reference: https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/standard-platform.md

Putting this on hold for now.
There's just too much churn coming in RC2 to spend any time on this now. Most of the effort would probably be wasted.

This is all set to change with .NET Core so I don't think it's worth investing any time in this. I also think that, ultimately, support for all platforms will be provided via support for the relevant .NET Standard, so I don't think explicit support for anything other than net45 will ever be a thing in xBehave.net. For that reason, I'm going to close this issue.

Replaced by #300


Don't patch objects if there are no changes

Currently we send a request to update some objects on each reconciliation, even if these objects were not modified.
To prevent this we introduce checks to ensure that changes were made before sending patch requests.

i don't think the test failures are related
/lgtm

/approve
/retest-required

/hold
ci is broken, I'm fixing it.


173632883 Data Problem (vino)

Issue reported by vino at 2020-07-02 15:21:23 UTC
Time: 2020-07-02T15:20:16+00:00
Session ID: 9137c96be5b0dcc44d1cd4589cd293c2
Problem Page URL: https://test3.freebmd.org.uk/best_guess/5efdfb12e93790116a6be884/237597994/william-walker-callum-death?locale=en
Previous Page URL: https://test3.freebmd.org.uk/contacts/237597994/report_error?locale=en&query=5efdfb12e93790116a6be884
Reported Issue:
test
https://test3.freebmd.org.uk/uploads/contact/screenshot/5efdfb73e93790116a6be886/Screenshot_2020-05-21_at_20.58.50.png

Test. Closing.


fix code stype format

fix https://github.com/kubernetes/website/issues/15144

better to follow the style of English version: https://raw.githubusercontent.com/kubernetes/website/master/content/en/docs/tasks/inject-data-application/define-command-argument-container.md

/lgtm
/assign @tengqm

was this fixed? let me know if you have any problems :)

@idealhack Hi, I saw the pr https://github.com/kubernetes/website/pull/15268 has been merged for this issue , although that pr is created after this one. So I close this pr, sad.

@zwwhdls oh... ok, feel free to find more reviewers on slack next time! thank you anyway!


RiverPod and ResoCoder

RiverPod is new state management technique by Remi Rousselet.
Reso coder is provided an intermediate course for a flutter by Matt Rešetár.

Thanks @Abhishek01039 . I think this will help people know more about RiverPod.


Add a better error message when a invalid class_uid is used

When loading the OSCF schema a FileNotFoundError is thrown due to the SCHEMA_CLASS returning nil.
[?] : ocsf_schema_1.0.0-rc.2
 > ocsf_schema_1.0.0-rc.2

{'version': 'ocsf_schema_1.0.0-rc.2', 'path': '***'}

Validating Against Event Class:  (1000)...

Traceback (most recent call last):
  File "/amazon-security-lake/validate_1.0.0-rc.2/validate.py", line 259, in <module>
    main()
  File "/amazon-security-lake/validate_1.0.0-rc.2/validate.py", line 198, in main
    with open(str(path.parent).replace('\\', '/')
FileNotFoundError: [Errno 2] No such file or directory: '/amazon-security-lake/validate_1.0.0-rc.2/ocsf_schema_1.0.0-rc.2/.json'

Added support for error handling on invalid schemas.


GUVNOR-2545: Workbench specific files should not be mandatory

See https://issues.jboss.org/browse/GUVNOR-2545

@Rikkola Could you please review. Thanks.

+1

Waiting for Jenkins to be green, before merging...


'Add tasks.json' command that copied tasks.json into current project

Add command to copy template-tasks.json into .vscode folder in root of open folder.
cc @chuckries, @gregg-miskelly

:+1


Issue 907

identified too many negative aspects. Don't merge as it will be closed after deeper analysis of each topic

feature was implemented from scratch after refactoring retry analyzer in scope of
https://github.com/qaprosoft/carina/pull/912


Modifications to Military Features GDB Field Schemas

Based on work done in exporting military feature field schemas from JMSML, a study of the current baseline field schemas, and the contents of 2525D, suggests the following changes should be made to our military feature class fields..
The contextual impact of these recommended changes are illustrated with the sample, prototype, JMSML output available here.

Feature Class
Field
Changes
Justification

Activities
symbolset
Default: 40
No other symbol set code makes sense

Activities
entity
Alias: Activity Entity
Consistency with other feature classes

Activities
additionalinformation
Length: 20
Consistency with DoD doctrine

Activities
staffcomment
Length: 20
Consistency with DoD doctrine

Activities
combateffectiveness
Length: 3
Error in 2525D.  CP will correct

Activities
z
Alias: Altitude/Depth
Consistency with 2525D

Air
entity
Alias: Air Entity, Remove domain value
Consistency with other feature classes. Domains set in subtypes

Air
modifier1
Remove domain value
Domains set in subtypes

Air
modifier2
Remove domain value
Domains set in subtypes

Air
uniquedesignation
Alias: Unique Designation
Consistency with other feature classes

Air
additionalinformation
Length: 20
Consistency with DoD doctrine

Air
staffcomment
Length: 20
Consistency with DoD doctrine

Air
idmode
Alias: IFF/SIF/AIS
Consistency with other feature classes

Air
type
Length: 24
Consistency with DoD doctrine

Air
speedunit
New field
Required to draw speed (MIL-STD-6040)

Air
countrycode
Remove field
Not used in Air dimension

Control Measure Areas
symbolset
Default: 25
No other symbol set code makes sense

Control Measure Areas
entity
Alias: Area Entity
Consistency with other feature classes

Control Measure Areas
echelon
Alias: Echelon
Alias should be capitalized

Control Measure Areas
uniquedesignation
Length: 30
Consistency with DoD doctrine

Control Measure Areas
additionalinformation
Length: 20
Consistency with DoD doctrine

Control Measure Areas
additionalinformation2
Length: 20
Consistency with DoD doctrine

Control Measure Areas
multiple fields
Re-order
Consistency with other feature classes

Control Measure Lines
identity
Nullability: NULLABLE
Consistency with other feature classes

Control Measure Lines
symbolset
Default: 25
No other symbol set code makes sense

Control Measure Lines
entity
Alias: Line Entity
Consistency with other feature classes

Control Measure Lines
uniquedesignation
Length: 30
Consistency with DoD doctrine

Control Measure Lines
uniquedesignation2
Length: 30
Consistency with DoD doctrine

Control Measure Lines
additionalinformation
Length: 20
Consistency with DoD doctrine

Control Measure Lines
multiple fields
Re-order
Consistency with other feature classes

Control Measure Points
symbolset
Default: 25
No other symbol set code makes sense

Control Measure Points
entity
Alias: Point Entity
Consistency with other feature classes

Control Measure Points
additionalinformation
Length: 20
Consistency with DoD doctrine

Control Measure Points
additionalinformation2
Length: 20
Consistency with DoD doctrine

Control Measure Points
speed
New field
Would complement direction of movement indicator amplifier

Control Measure Points
speedunit
New field
Required to draw speed (MIL-STD-6040)

Cyberspace
entity
Alias: Cyberspace Entity
Consistency with other feature classes

Cyberspace
additionalinformation
Length: 20
Consistency with DoD doctrine

Cyberspace
staffcomment
Length: 20
Consistency with DoD doctrine

Cyberspace
combateffectiveness
Domain: CombatEffectiveness, Length: 3
Needs to be constrained. Error in 2525D.  CP will correct

Cyberspace
type
Length: 24
Consistency with DoD doctrine

Cyberspace
speedunit
New field
Required to draw speed (MIL-STD-6040)

Cyberspace
multiple fields
Re-order
Consistency with other feature classes

Installations
symbolset
Default: 20
No other symbol set code makes sense

Installations
entity
Alias: Installation Entity
Consistency with other feature classes

Installations
additionalinformation
Length: 20
Consistency with DoD doctrine

Installations
staffcomment
Length: 20
Consistency with DoD doctrine

Installations
idmode
Alias: IFF/SIF/AIS
Consistency with other feature classes

Installations
speedunit
New field
Required to draw speed (MIL-STD-6040)

Land
symbolset
Default: 15
No other symbol set code makes sense

Land
entity
Alias: Equipment Entity
Consistency with other feature classes

Land
additionalinformation
Length: 20
Consistency with DoD doctrine

Land
staffcomment
Length: 20
Consistency with DoD doctrine

Land
idmode
Alias: IFF/SIF/AIS
Consistency with other feature classes

Land
speedunit
New field
Required to draw speed (MIL-STD-6040)

METOCAreas
entity
Alias: METOC Area Entity
Consistency with other feature classes

METOCAreas
additionalinformation
Length: 20
Consistency with DoD doctrine

METOCAreas
multiple fields
Re-order
Consistency with other feature classes

METOCLines
entity
Alias: METOC Line Entity
Consistency with other feature classes

METOCLines
additionalinformation
Length: 20
Consistency with DoD doctrine

METOCLines
multiple fields
Re-order
Consistency with other feature classes

METOCPoints
entity
Alias: METOC Point Entity
Consistency with other feature classes

METOCPoints
additionalinformation
Length: 20
Consistency with DoD doctrine

METOCPoints
multiple fields
Re-order
Consistency with other feature classes

SeaSubsurface
identity
Nullability: NULLABLE
Consistency with other feature classes

SeaSubsurface
entity
Alias: Subsurface Entity, Remove domain value
Consistency with other feature classes. Domains set in subtypes

SeaSubsurface
additionalinformation
Length: 20
Consistency with DoD doctrine

SeaSubsurface
staffcomment
Length: 20
Consistency with DoD doctrine

SeaSubsurface
idmode
Alias: IFF/SIF/AIS
Consistency with other feature classes

SeaSubsurface
type
Length: 24
Consistency with DoD doctrine

SeaSubsurface
speedunit
New field
Required to draw speed (MIL-STD-6040)

SeaSubsurface
multiple fields
Re-order
Consistency with other feature classes

SeaSurface
symbolset
Default: 30
No other symbol set code makes sense

SeaSurface
entity
Alias: Surface Entity
Consistency with other feature classes

SeaSurface
uniquedesignation
Alias: Unique Designation, Length: 30
Consistency with DoD doctrine

SeaSurface
additionalinformation
Length: 20
Consistency with DoD doctrine

SeaSurface
staffcomment
Length: 20
Consistency with DoD doctrine

SeaSurface
idmode
Alias: IFF/SIF/AIS
Consistency with other feature classes

SeaSurface
type
Length: 24
Consistency with DoD doctrine

SeaSurface
direction
New field
Required to complement direction of movement indicator

SeaSurface
speedunit
New field
Required to draw speed (MIL-STD-6040)

SeaSurface
z
New field
Consistency with other feature classes

SeaSurface
multiple fields
Re-order
Consistency with other feature classes

SIGINT
entity
Alias: SIGINT Entity
Consistency with other feature classes

SIGINT
additionalinformation
Length: 20
Consistency with DoD doctrine

SIGINT
staffcomment
Length: 20
Consistency with DoD doctrine

SIGINT
higherformation
Length: 21
Consistency with DoD doctrine

SIGINT
type
Length: 24
Consistency with DoD doctrine

SIGINT
direction
New field
Required to complement direction of movement indicator

SIGINT
speedunit
New field
Required to draw speed (MIL-STD-6040)

SIGINT
z
Label: Altitude/Depth
Consistency with other feature classes

SIGINT
multiple fields
Re-order
Consistency with other feature classes

Space
entity
Alias: Space Entity
Consistency with other feature classes

Space
uniquedesignation
Length: 30
Consistency with DoD doctrine

Space
additionalinformation
Length: 20
Consistency with DoD doctrine

Space
staffcomment
Length: 20
Consistency with DoD doctrine

Space
speedunit
New field
Required to draw speed (MIL-STD-6040)

Space
x
New field
Added to complement z

Space
y
New field
Added to complement z

Units
entity
Alias: Unit Entity
Consistency with other feature classes

Units
additionalinformation
Length: 20
Consistency with DoD doctrine

Units
staffcomment
Length: 20
Consistency with DoD doctrine

Units
speedunit
New field
Required to draw speed (MIL-STD-6040)

Units
multiple fields
Re-order
Consistency with other feature classes

Given the use of subtypes for some of these feature classes, it is more appropriate to put the symbolset domain restriction and default values under the subtype schemas (like each of the Cyberspace symbol sets).
Consistency with other feature classes => where at all possible, fields representing the same conceptual information in two or more feature classes should have all of the same properties (field name, type, length, alias, etc).  Exceptions should be minimized and only allowed if DoD doctrine clearly requires the exception.
Consistency with DoD Doctrine => where at all possible, field properties, particularly length, should conform to DoD doctrinal values.  While there is no widely used DoD standard for military database schemas, and 2525 is a display standard, not a database standard, the DoD military message standards (VMF, USMTF, etc) that specify data transmission lengths should largely influence our field property values.  In some known instances, there are errors and inconsistencies in this regard (incorrect display lengths for some text amplifiers) in 2525D.  Change proposals for 2525D Change 1 will be authored to ensure/fix the field/amplifier display length inconsistencies that are closely tied to the DoD message data transmission lengths and our own field schema specifications, so everything will correlate.
Consistency with 2525D => where at all possible, field properties should comply with the details for text amplifiers and drawing rule requirements for control measures, in 2525D.  With the knowledge that 2525D has some errors and inconsistencies within it and is not considered a data standard.

Thanks for giving the GDB such a thorough review - looks really good & seems good to implement as is to me - but @jrweakland can let us know if he wants to give this a more thorough review and/or have a review meeting given the number of changes.
Most of the changes look like:

Changing field lengths
Changing field aliases
Added a few new/missing fields ("speedunit" field most common)

From a quick check, the only one that I'm not completely sure of is that "speedunit" field since this could possibly be included with the speed field (if that field were changed to type string) - and it isn't an obvious field called out in the standard (unless there is a CP to do that, but not mentioned) - also one could possibly justify having a "units" field on every numeric field so that is the only reason I'm not sure - but I don't have strong feelings either way (so no need to argue this point, but a 2525D CP would be good since I think the doc referenced in not for public distro).
Assigning to @abouffard to implement as part of the GDB automation task - thanks again

@csmoore , a CP for speed units is already planned, but not being authored by us.  @ottenw was planning to write it up, I believe.  It would simply remove the reference to MIL-STD-6040 and bring the speed unit format specified therein into 2525D Change 1 itself.
Sure, making speed an 8 character long string is the other option, but a numeric value is useful in the feature class for analytical and comparison reasons, and having to parse the string value to get the numeric information would be the cost of having one field.
I'm easy either way, actually, but I think we have to have some solution that allows us to display the unit string following the speed string.

I think this can be closed in light of the acceptance of what JMSML is now exporting and the new GP tools for creating a template GDB is building.

I created this issue so I am going to close it.


Finetuning for emotion analysis but nan output

Hi,
I have downloaded the CMU-MOSEI dataset, and I am fine-tuning TVLT for emotion analysis on the MOSEI dataset. Although I could not obtain the labels_emotion folder in the downloaded zip file, I have compiled my own emotion label file using the [timestamp file] (http://immortal.multicomp.cs.cmu.edu/timestamped_links/) from CMU, but when I use the [fine-tuning script](url) to fine-tune it on CMU-MOSEI, the model outputs nan values after some iterations. Could you shed some light on what could be wrong?

Could you explain how did you convert the values to the labels?

I just took the mosei.csv file and removed columns 1:5. And changed column 0, i.e., id column, to Filename column by: column_0 + '_' column_2

And in moseiemo_dataset.py, line number 78, I changed it to emolist = np.array(self.labels[self.labels['FileName']==self.keys[index]].iloc[0, 1:] > 0.0), and that gives me boolean labels


Feature request: Add environment variable to rename spotify device name

It would be cool if we could rename the device from "aoede" in Spotify to our own custom name (ex: Music Llama).

Happy to accept a PR for this.

Decided to give this a try, although I'm new to Rust and the open source world.  Here's the PR:
https://github.com/codetheweb/aoede/pull/53


Repeated module.exports expressions are erroneously flagged as problematic

VSCode Version: (0.10.11) f291f4ad600767626b24a4b15816b04bee9a3049
OS Version: OS X 10.10.5

Steps to Reproduce:

This code is perfectly fine, and should not be flagged as an error. The error message is:

Duplicate identifier 'export='.

This will work with the March release (insiders build already available).


(java-sdk) Next round of refactoring

Context#error is now protected and used to extract the error message for the ExtismException
ByteArrayWasmSource is now correctly serialized (wasm data is now encoded base64)
Renamed ManifestMemory to MemoryOptions to align with rust codebase
Introduced WasmSourceResolver to load wasm source
Added unit tests
Revised Unit tests
Polished javadoc
Added necessary metadata for release to maven central
Removed maven-assembly-plugin as we want to allow consumers to control the dependencies

@bhelx here is the next round of refactoring, additional javadoc and tests.


chore: update dependencies across packages

@ojeytonwilliams looks like I have the same issue as you and the CI keeps crashing at times.

Yep. These package-locks won't install in CI, even though they're fine locally. I'll try creating them in a different environment tomorrow.

Do we want to try smaller PRs, with one application at a time?


Use GCS Storage for GitHub hosted runners

We use GitHub-hosted runners for some platforms where our CI needs are more narrow, platform provisioning is more difficult, and/or our security requirements are stricter. However, we have had repeated issues with GitHub-provided caching and artifact storage. It is limited in size and the transfer speeds are shockingly (like actually I don't understand how it's possible) bad.
Related: #12905, #9881
We've now configured things so that we can access our GCS bucket from the GitHub runners (don't ask why this was hard. It should not have been), so we can switch to using that for things that currently use the GitHub Actions cache and artifact mechanisms. Note that this will only be writable on postsubmit (since it uses GitHub secrets), so cannot be used for passing artifacts between jobs, but can be used for updating caches and such.

Follow https://github.com/google-github-actions/auth to set up auth. The service-account key secret is IREE_OSS_GITHUB_RUNNER_BASIC_TRUST_SERVICE_ACCOUNT_KEY

The service account keys will need to be updated every 90 days by policy. Documenting how to do that and coming up with a mechanism so we don't lose track of them is part of this task. The command to do so for an appropriately credentialed person (service account key creator in GCP and organization admin in GitHub) is
gcloud iam service-accounts keys create /dev/stdout \
<EMAIL_ADDRESS>\
  | jq --compact-output '.' \
  | gh secret set --org openxla IREE_OSS_GITHUB_RUNNER_BASIC_TRUST_SERVICE_ACCOUNT_KEY

I've moved everything over. We're theoretically supposed to be able to switch to OIDC in the next couple months, so I'm going to punt on coming up with a system. I've regenerated the key just now and set a reminder to do it again in 2 months :-/

The command above is actually bad and wrong. Don't use it! It turns out that the GitHub API for secrets only lets you reset the entire secret, including the secret visibility. The CLI similarly only offers this functionality. Since we have visibility set to "selected repos", listing them on the the command line is kind of a pain. For now, you may have to set it from the UI (though hopefully no one will ever have to do this again): https://github.com/organizations/openxla/settings/secrets/actions/IREE_OSS_GITHUB_RUNNER_BASIC_TRUST_SERVICE_ACCOUNT_KEY.
The other option is first fetching the selected repos and then using that to construct the set command. That introduces race conditions in general, but could be ok for this sort of manual thing.