CI: K8sIstioTest Istio Bookinfo Demo Tests bookinfo inter-service connectivity: Istio sidecar proxies are not reachable

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.14-kernel-4.9/25/testReport/junit/Suite-k8s-1/14/K8sIstioTest_Istio_Bookinfo_Demo_Tests_bookinfo_inter_service_connectivity/
6dfeb230_K8sIstioTest_Istio_Bookinfo_Demo_Tests_bookinfo_inter-service_connectivity.zip
Stacktrace
/home/jenkins/workspace/Cilium-PR-K8s-1.14-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Timed out after 244.373s.
Istio sidecar proxies are not reachable
Expected
    <bool>: false
to be true
/home/jenkins/workspace/Cilium-PR-K8s-1.14-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/istio.go:429

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
⚠  Number of "level=warning" in logs: 14
Number of "Cilium API handler panicked" in logs: 0
⚠  Number of "Goroutine took lock for more than" in logs: 23
Top 5 errors/warnings:
Unable to restore endpoint, ignoring
BPF NodePort services needs kernel 4.17.0 or newer. Disabling BPF NodePort.
BPF host reachable services for TCP needs kernel 4.17.0 or newer. Disabling the feature.
BPF host reachable services for UDP needs kernel 4.19.57, 5.1.16, 5.2.0 or newer. If you run an older kernel and only need TCP, then specify: --host-reachable-services-protos=tcp and --kube-proxy-replacement=partial Disabling the feature.
SessionAffinity feature requires BPF LRU maps. Disabling the feature.
Cilium pods: [cilium-vd4mw cilium-xc6t7]
Netpols loaded:
CiliumNetworkPolicies loaded: default::cnp-specs
Endpoint Policy Enforcement:
Pod                                     Ingress   Egress
istio-ingressgateway-66c59d8cff-sf6vt
istiod-77c987bcc6-p5l5v
prometheus-76d55b8c5d-lllf6
prometheus-69fd5878c7-kr7ml
details-v1-75ff589f96-7cjtq
reviews-v1-94dff74b6-9njwj
reviews-v2-7f648686f8-8lcv5
grafana-b959498b4-h9p5k
productpage-v1-5966d4b955-br8x8
ratings-v1-75c467d944-dh7tx
coredns-cc45bff6b-454sm
Cilium agent 'cilium-vd4mw': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 47 Failed 0
Cilium agent 'cilium-xc6t7': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 36 Failed 0

Standard Error
Click for details
05:44:47 STEP: Running BeforeAll block for EntireTestsuite K8sIstioTest
05:44:47 STEP: Ensuring the namespace kube-system exists
05:44:48 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
05:44:48 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
05:44:48 STEP: Downloading cilium-istioctl
05:44:49 STEP: Installing Cilium
05:44:50 STEP: Waiting for Cilium to become ready
05:44:50 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:51 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:52 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:53 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:54 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:55 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:56 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:57 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:58 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:44:59 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:45:00 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:45:01 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:45:02 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
05:45:04 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:05 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:06 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:07 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:08 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:09 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:10 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:11 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:12 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:13 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:14 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:15 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:16 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:17 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:18 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:19 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:20 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:21 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:22 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:24 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
05:45:25 STEP: Number of ready Cilium pods: 2
05:45:25 STEP: Validating if Kubernetes DNS is deployed
05:45:25 STEP: Checking if deployment is ready
05:45:25 STEP: Checking if kube-dns service is plumbed correctly
05:45:25 STEP: Checking if DNS can resolve
05:45:25 STEP: Checking if pods have identity
05:45:26 STEP: Kubernetes DNS is up and operational
05:45:26 STEP: Validating Cilium Installation
05:45:26 STEP: Performing Cilium controllers preflight check
05:45:26 STEP: Performing Cilium status preflight check
05:45:26 STEP: Performing Cilium health check
05:45:29 STEP: Performing Cilium service preflight check
05:45:29 STEP: Performing K8s service preflight check
05:45:29 STEP: Cilium is not ready yet: connectivity health is failing: Cluster connectivity is unhealthy on 'cilium-vd4mw': Exitcode: 255
Err: exit status 255
Stdout:

Stderr:
 	 Error: Cannot get status/probe: Put "http://%2Fvar%2Frun%2Fcilium%2Fhealth.sock/v1beta/status/probe": dial unix /var/run/cilium/health.sock: connect: no such file or directory

	 command terminated with exit code 255

05:45:31 STEP: Performing Cilium health check
05:45:31 STEP: Performing Cilium controllers preflight check
05:45:31 STEP: Performing Cilium status preflight check
05:45:34 STEP: Performing Cilium service preflight check
05:45:34 STEP: Performing K8s service preflight check
05:45:35 STEP: Waiting for cilium-operator to be ready
05:45:35 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
05:45:35 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
05:45:35 STEP: Labeling default namespace for sidecar injection
05:45:35 STEP: Setting label istio-injection=enabled in namespace default
05:45:35 STEP: Deploying Istio
05:46:10 STEP: Waiting for Istio pods to be ready
05:46:10 STEP: WaitforNPodsRunning(namespace="istio-system", filter="-l istio")
05:46:10 STEP: WaitforNPods(namespace="istio-system", filter="-l istio") => <nil>
05:46:10 STEP: WaitforPods(namespace="istio-system", filter="-l istio")
05:46:10 STEP: WaitforPods(namespace="istio-system", filter="-l istio") => <nil>
05:46:10 STEP: Waiting for Istio service "istio-ingressgateway" to be ready
05:46:10 STEP: Waiting for Istio service "istiod" to be ready
05:46:10 STEP: Waiting for DNS to resolve Istio service "istio-ingressgateway"
05:46:11 STEP: Waiting for DNS to resolve Istio service "istiod"
05:46:11 STEP: Creating policy in file "/home/jenkins/workspace/Cilium-PR-K8s-1.14-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/manifests/cnp-specs.yaml"
05:46:14 STEP: Creating resources in file "/home/jenkins/workspace/Cilium-PR-K8s-1.14-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v2.yaml"
05:46:14 STEP: Creating resources in file "/home/jenkins/workspace/Cilium-PR-K8s-1.14-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/manifests/bookinfo-v1.yaml"
05:46:14 STEP: Waiting for Bookinfo pods to be ready
05:46:14 STEP: WaitforPods(namespace="default", filter="-l zgroup=bookinfo")
05:46:34 STEP: WaitforPods(namespace="default", filter="-l zgroup=bookinfo") => <nil>
05:46:34 STEP: Waiting for Bookinfo endpoints to be ready
05:46:36 STEP: Waiting for Bookinfo service "details" to be ready
05:46:36 STEP: Waiting for Bookinfo service "ratings" to be ready
05:46:36 STEP: Waiting for Bookinfo service "reviews" to be ready
05:46:36 STEP: Waiting for Bookinfo service "productpage" to be ready
05:46:36 STEP: Waiting for DNS to resolve Bookinfo service "productpage"
05:46:37 STEP: Waiting for DNS to resolve Bookinfo service "reviews"
05:46:37 STEP: Waiting for DNS to resolve Bookinfo service "ratings"
05:46:38 STEP: Waiting for DNS to resolve Bookinfo service "details"
05:46:39 STEP: Testing Istio service configuration
05:46:39 STEP: Checking that Istio proxy config at "reviews-v1-94dff74b6-9njwj" has service "ratings.default.svc.cluster.local" on port "9080" for "outbound"
05:46:40 STEP: Checking that Istio proxy config at "ratings-v1-75c467d944-dh7tx" has service "ratings.default.svc.cluster.local" on port "9080" for "inbound"
05:46:41 STEP: Checking that Istio proxy config at "productpage-v1-5966d4b955-br8x8" has service "details.default.svc.cluster.local" on port "9080" for "outbound"
05:46:41 STEP: Checking that Istio proxy config at "details-v1-75ff589f96-7cjtq" has service "details.default.svc.cluster.local" on port "9080" for "inbound"
05:46:42 STEP: Checking that Istio proxy config at "productpage-v1-5966d4b955-br8x8" has service "ratings.default.svc.cluster.local" on port "9080" for "outbound"
05:46:42 STEP: Testing service local access
05:46:42 STEP: Checking that "reviews-v1-94dff74b6-9njwj" can connect to "http://<IP_ADDRESS>:9080/health"
05:46:43 STEP: Checking that "ratings-v1-75c467d944-dh7tx" can connect to "http://<IP_ADDRESS>:9080/health"
05:46:44 STEP: Checking that "ratings-v1-75c467d944-dh7tx" can connect to "http://<IP_ADDRESS>:9080/ratings/0"
05:46:44 STEP: Checking that "ratings-v1-75c467d944-dh7tx" can connect to "http://<IP_ADDRESS>:9080/health"
05:46:44 STEP: Checking that "details-v1-75ff589f96-7cjtq" can connect to "http://<IP_ADDRESS>:9080/health"
05:46:45 STEP: Checking that "productpage-v1-5966d4b955-br8x8" can connect to "http://<IP_ADDRESS>:9080/health"
05:46:45 STEP: Testing L7 filtering
05:46:45 STEP: Checking that "reviews-v1-94dff74b6-9njwj" can connect to "ratings.default.svc.cluster.local:9080/health"
Unable to connect from "reviews-v1-94dff74b6-9njwj" to "ratings.default.svc.cluster.local:9080/health": Exitcode: 8
Err: exit status 8
Stdout:

Stderr:
 	 --2021-02-11 05:46:45--  http://ratings.default.svc.cluster.local:9080/health
	 Resolving ratings.default.svc.cluster.local (ratings.default.svc.cluster.local)... <IP_ADDRESS>
	 Connecting to ratings.default.svc.cluster.local (ratings.default.svc.cluster.local)|<IP_ADDRESS>|:9080... connected.
	 HTTP request sent, awaiting response... 503 Service Unavailable
	 2021-02-11 05:47:15 ERROR 503: Service Unavailable.

	 command terminated with exit code 8

05:47:15 STEP: Checking that "reviews-v1-94dff74b6-9njwj" cannot connect to "ratings.default.svc.cluster.local:9080/ratings/0"
05:47:45 STEP: Checking that "productpage-v1-5966d4b955-br8x8" can connect to "details.default.svc.cluster.local:9080/health"
05:47:46 STEP: Checking that "productpage-v1-5966d4b955-br8x8" cannot connect to "ratings.default.svc.cluster.local:9080/health"
05:48:16 STEP: Checking that "productpage-v1-5966d4b955-br8x8" cannot connect to "ratings.default.svc.cluster.local:9080/ratings/0"
05:48:47 STEP: Checking that "reviews-v1-94dff74b6-9njwj" can connect to "ratings.default.svc.cluster.local:9080/health"
Unable to connect from "reviews-v1-94dff74b6-9njwj" to "ratings.default.svc.cluster.local:9080/health": Exitcode: 8
Err: exit status 8
Stdout:

Stderr:
 	 --2021-02-11 05:48:48--  http://ratings.default.svc.cluster.local:9080/health
	 Resolving ratings.default.svc.cluster.local (ratings.default.svc.cluster.local)... <IP_ADDRESS>
	 Connecting to ratings.default.svc.cluster.local (ratings.default.svc.cluster.local)|<IP_ADDRESS>|:9080... connected.
	 HTTP request sent, awaiting response... 503 Service Unavailable
	 2021-02-11 05:49:18 ERROR 503: Service Unavailable.

	 command terminated with exit code 8

05:49:18 STEP: Checking that "reviews-v1-94dff74b6-9njwj" cannot connect to "ratings.default.svc.cluster.local:9080/ratings/0"
05:49:48 STEP: Checking that "productpage-v1-5966d4b955-br8x8" can connect to "details.default.svc.cluster.local:9080/health"
05:49:48 STEP: Checking that "productpage-v1-5966d4b955-br8x8" cannot connect to "ratings.default.svc.cluster.local:9080/health"
05:50:19 STEP: Checking that "productpage-v1-5966d4b955-br8x8" cannot connect to "ratings.default.svc.cluster.local:9080/ratings/0"
FAIL: Timed out after 244.373s.
 Closing.


Vicuna models won't download - 404 ?

Bug description
Unable to download the vicuna models - have they moved?
Steps to reproduce
Running with the command line:
docker run -d -v weights:/usr/src/app/weights -v datadb:/data/db/ -p 8008:8008 ghcr.io/nsarrazin/serge:latest
Navigate to localhost/models
Click either of the Vicuna buttons
Environment Information
Docker version 20.10.21, build 20.10.21-0ubuntu1~22.04.3
Ubuntu 22.04.2 LTS
Architecture:           aarch64
CPU op-mode(s):       32-bit, 64-bit
Byte Order:           Little Endian
CPU(s):                 16
On-line CPU(s) list:  0-15
Vendor ID:              ARM
Model name:           Neoverse-N1
Screenshots
No response
Relevant log output
INFO:     <IP_ADDRESS>:53198 - "GET /model/all HTTP/1.1" 200 OK
Downloading Vicuna-7B model from eachadea/ggml-vicuna-7b-1.1...
INFO:     <IP_ADDRESS>:53198 - "POST /model/Vicuna-7B/download HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 436, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 92, in __call__
    await self.simple_response(scope, receive, send, request_headers=headers)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 147, in simple_response
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 109, in __call__
    await response(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 270, in __call__
    async with anyio.create_task_group() as task_group:
  File "/usr/local/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 662, in __aexit__
    raise exceptions[0]
  File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 273, in wrap
    await func()
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 134, in stream_response
    return await super().stream_response(send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 262, in stream_response
    async for chunk in self.body_iterator:
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 98, in body_stream
    raise app_exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 70, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "/usr/local/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 443, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "/usr/local/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 66, in app
    response = await func(request)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 237, in app
    raw_response = await run_endpoint_function(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 165, in run_endpoint_function
    return await run_in_threadpool(dependant.call, **values)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/starlette/concurrency.py", line 41, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/serge/routers/model.py", line 132, in download_model
    urllib.request.urlretrieve(url, WEIGHTS+f"{model_name}.bin.tmp")
  File "/usr/local/lib/python3.11/urllib/request.py", line 241, in urlretrieve
    with contextlib.closing(urlopen(url, data)) as fp:
                            ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 525, in open
    response = meth(req, response)
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 634, in http_response
    response = self.parent.error(
               ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 563, in error
    return self._call_chain(*args)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/local/lib/python3.11/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found

Confirmations

[X] I'm running the latest version of the main branch.
[X] I checked existing issues to see if this has already been described.

@raymondclowe Hello. I also come to this. The model is not anymore available since like 24H+ in https://huggingface.co/eachadea/ggml-vicuna-13b-1.1/tree/main. And some of the actual available, if you DL it like ggml-vic13b-uncensored-q5_1.bin , are not yet compatible :
llama.cpp: loading model from /usr/src/app/weights/ggml-vic13b-uncensored-q5_1.bin  error loading model: **unrecognized tensor type 7**
llama.cpp has been updated. abetlen/llama-cpp-python also, but have not built release yet. So I beg "Serge" is not up to date at the moment to handle these models. In case you have the knowledge to build yourself the "up-to-date" docker ... (maybe that's not enough ... just my analysis).

same!

https://github.com/nsarrazin/serge/pull/248

Merging this now, will be available with the latest tag


[FEATURE REQUEST] Enable Subscription of own applications

Which area is mainly impacted
Configuration
Requested Feature
Currently it is only possible to subscribe to applications which are listed as entiltments in the global account. In cases where there is an own application deployed which can be subscribed from within that global account the usecase check that happens in the beginning will fail.
It would be good if the we could decide per serivce/application if that should be taken into account for the prerequisites check.
Use Case/Scenario
In our scenario we would like to subacribe to an application that has been deployed by a previous run of the setup automator. With that we can completely automate the setup of a multitenancy application including the creation of a consumer subaccount and the subscription to the application.
Would you like to support us?

[ ] Yes, I would like to support you

Anything else?
No response

Hi Alex,
can you provide more details and example usecases for this setup? From the top of my head I would assume that some adoptions are needed in the btpsa as this is not a service registered at the service manager right? But would like to validate that on a dedicated example.

Hi @lechnerc77 ,
the general idea is to call the usecase after we have setup and deployed our kyma application. With the second usecase which is attached we want to create a second subaccount where we subscribe that application. The application is registered in the saas registry on global account level (not at the service manager as it's not a service).
You can test it on this global account with the subaccount btp-setup-test:
https://cockpit.eu10.hana.ondemand.com/cockpit/#/globalaccount/2505dea8-1524-4e5f-924e-276483596166/subaccount/4dd99aac-238c-43ea-9d8c-32472e8816e5/subaccountoverview
The usecase can be executed with the following command:
./btpsa -usecasefile 'attached usecase' -globalaccount easyfranchise -myemail  -subaccountname btp-automator-test  -region eu10
usecase-consumer.txt
If you run into problem let me know.
Thanks
Alex

@AlexRieder : Thanks for the additional info. I see where the issues comes from, now just need to find a clever way to resolve it :-)

Status Quo: branch custom-apps contains the enhancements for the request.
ToDo:

Regression test
Enhancement of documentation

Documentation is updated, Docker image is built and available


Add cursornext to performance benchmarks

Hi, i would like to add a new lib to the benchmarks list. Does this seem okey?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @clitetailor
It seems to me that cursornext is a set of helper utilities to assist in hand crafting a parser. But I am not sure that fully qualifies as a "Parsing Library" e.g:

Automatic lookahead logic calculation
Detection of ambiguities.
Error Recovery
Syntax Diagrams.

Don't get me wrong, cursornext is still useful!
Chevrotain itself had similar lower level APIs starting point... However If the benchmark was created to compare parsing libraries and there is already an example of an hand crafted parser present...

https://github.com/sap/chevrotain/blob/gh-pages/performance/jsonParsers/handbuilt/handbuilt.js

I am not sure another variant of an hand crafted parser would add much value.
Particularly as there are already too many scenarios in the benchmark (11).
If I wanted to benchmark CursorNext I would compare it with hand-crafted Parsers primarily, E.g write a few simple syntax (JSON/XML/TOML) using CursorNext and compare vs existing hand-crafted parsers, otherwise it would be comparing apples and oranges.
It would also be interesting to compare the readability of a cursornext based Parser vs a "standard" switchcase based implementation side by side.
Cheers.
Shahar.

Hi @bd82. Thanks for your suggestion. You're right, the list is so height and cursornext does not align well with the others. However, it's great to see there's such a complete parsing benchmark like chervotain for comparison.
I will try to find a more suitable benchmark methodology for cursornext. Maybe your suggestion would be a great way to start.
Best regard.


some help tags about function details are inconsistent

This command outputs all the help tags matching the pattern -function*-details:
pu=getcompletion('-function*-details', 'help')

job-functions-details
sign-functions-details
test-functions-details
popup-function-details
assert-functions-details
channel-functions-details
terminal-function-details

Notice that all the tags use the plural of the word "function":
job-functions-details
            ^
sign-functions-details
             ^
test-functions-details
             ^
assert-functions-details
               ^
channel-functions-details
                ^

Except these 2:
popup-function-details
             ^
             ✘

terminal-function-details
                ^
                ✘

This is inconsistent.

If you run this global command while reading :h eval:
:g/are documented/p

You get this output:
assert_ functions are documented here: |assert-functions-details|
ch_ functions are documented here: |channel-functions-details|
job_ functions are documented here: |job-functions-details|
popup_ functions are documented here: |popup-functions|.
prop_ functions are documented here: |text-prop-functions|.
sign_ functions are documented here: |sign-functions-details|
term_ functions are documented here: |terminal-function-details|
test_ functions are documented here: |test-functions-details|

Notice that all the lines end with a tag name using the keyword "details" and without a dot at the end:
assert_ functions are documented here: |assert-functions-details|
                                                         ^-----^

ch_ functions are documented here: |channel-functions-details|
                                                      ^-----^

job_ functions are documented here: |job-functions-details|
                                                   ^-----^

sign_ functions are documented here: |sign-functions-details|
                                                     ^-----^

term_ functions are documented here: |terminal-function-details|
                                                        ^-----^

test_ functions are documented here: |test-functions-details|
                                                     ^-----^

Except these 2:
prop_ functions are documented here: |text-prop-functions|.
                                                         ^^
                                                         details is missing; dot is superfluous

popup_ functions are documented here: |popup-functions|.
                                                      ^^
                                                      details is missing; dot is superfluous

This is also inconsistent.

The following patch tries to address these issues:
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index a2e1af919..0f7e14ec4 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -7607,7 +7607,7 @@ perleval({expr})					*perleval()*
 <		{only available when compiled with the |+perl| feature}

-popup_ functions are documented here: |popup-functions|.
+popup_ functions are documented here: |popup-functions-details|

 pow({x}, {y})						*pow()*
@@ -7890,7 +7890,7 @@ prompt_setprompt({buf}, {text})				*prompt_setprompt()*
 		Can also be used as a |method|: >
 			GetBuffer()->prompt_setprompt('command: ')

-prop_ functions are documented here: |text-prop-functions|.
+prop_ functions are documented here: |text-prop-functions-details|

 pum_getpos()						*pum_getpos()*
 		If the popup menu (see |ins-completion-menu|) is not visible,
@@ -10552,7 +10552,7 @@ tempname()					*tempname()* *temp-file-name*
 		option is set or when 'shellcmdflag' starts with '-'.

-term_ functions are documented here: |terminal-function-details|
+term_ functions are documented here: |terminal-functions-details|

 terminalprops()						*terminalprops()*
diff --git a/runtime/doc/popup.txt b/runtime/doc/popup.txt
index 8a0f2ba51..187682570 100644
--- a/runtime/doc/popup.txt
+++ b/runtime/doc/popup.txt
@@ -13,7 +13,7 @@ Displaying text in a floating window.	*popup* *popup-window* *popupwin*
    Popup buffer and window	|popup-buffer|
    Terminal in popup window	|popup-terminal|
 2. Functions			|popup-functions|
-   Details			|popup-function-details|
+   Details			|popup-functions-details|
 3. Usage			|popup-usage|
    popup_create() arguments	|popup_create-arguments|
    Popup text properties	|popup-props|
@@ -201,7 +201,7 @@ Other:
 	|popup_list()|		get list of all popups

-DETAILS						*popup-function-details*
+DETAILS						*popup-functions-details*

 popup_atcursor({what}, {options})			*popup_atcursor()*
 		Show the {what} above the cursor, and close it when the cursor
diff --git a/runtime/doc/terminal.txt b/runtime/doc/terminal.txt
index ff5207854..6db37f07c 100644
--- a/runtime/doc/terminal.txt
+++ b/runtime/doc/terminal.txt
@@ -23,7 +23,7 @@ If the result is "1" you have it.
       Special keys				|terminal-special-keys|
       Unix					|terminal-unix|
       MS-Windows				|terminal-ms-windows|
-2. Terminal functions			|terminal-function-details|
+2. Terminal functions			|terminal-functions-details|
 3. Terminal communication		|terminal-communication|
       Vim to job: term_sendkeys()		|terminal-to-job|
       Job to Vim: JSON API			|terminal-api|
@@ -455,7 +455,7 @@ Environment variables are used to pass information to the running job:

 ==============================================================================
-2. Terminal functions				 *terminal-function-details*
+2. Terminal functions				 *terminal-functions-details*

 							*term_dumpdiff()*
 term_dumpdiff({filename}, {filename} [, {options}])
diff --git a/runtime/doc/textprop.txt b/runtime/doc/textprop.txt
index ac6d12a69..ce4a9b153 100644
--- a/runtime/doc/textprop.txt
+++ b/runtime/doc/textprop.txt
@@ -115,6 +115,8 @@ prop_list({lnum} [, {props}])  		text properties in {lnum}
 prop_remove({props} [, {lnum} [, {lnum-end}]])
 					remove a text property

+DETAILS						*textprop-functions-details*
+
 						*prop_add()* *E965*
 prop_add({lnum}, {col}, {props})
 		Attach a text property at position {lnum}, {col}.  {col} is

This command outputs all the help tags matching the pattern -function*-details:
pu=getcompletion('-function*-details', 'help')

job-functions-details
sign-functions-details
test-functions-details
popup-function-details
assert-functions-details
channel-functions-details
terminal-function-details

Notice that all the tags use the plural of the word "function":
job-functions-details
            ^
sign-functions-details
             ^
test-functions-details
             ^
assert-functions-details
               ^
channel-functions-details
                ^

Except these 2:
popup-function-details
             ^
             ✘

terminal-function-details
                ^
                ✘

This is inconsistent.

This comes from adding "-details" after "some-functions".  But it reads
strange, perhaps we should follow the last two.  Not sure though.
Opinions?

If you run this global command while reading :h eval:
:g/are documented/p

You get this output:
assert_ functions are documented here: |assert-functions-details|
ch_ functions are documented here: |channel-functions-details|
job_ functions are documented here: |job-functions-details|
popup_ functions are documented here: |popup-functions|.
prop_ functions are documented here: |text-prop-functions|.
sign_ functions are documented here: |sign-functions-details|
term_ functions are documented here: |terminal-function-details|
test_ functions are documented here: |test-functions-details|

Notice that all the lines end with a tag name using the keyword "details" and without a dot at the end:
assert_ functions are documented here: |assert-functions-details|
                                                         ^-----^

ch_ functions are documented here: |channel-functions-details|
                                                      ^-----^

job_ functions are documented here: |job-functions-details|
                                                   ^-----^

sign_ functions are documented here: |sign-functions-details|
                                                     ^-----^

term_ functions are documented here: |terminal-function-details|
                                                        ^-----^

test_ functions are documented here: |test-functions-details|
                                                     ^-----^

Except these 2:
prop_ functions are documented here: |text-prop-functions|.
                                                         ^^
                                                         details is missing; dot is superfluous

popup_ functions are documented here: |popup-functions|.
                                                      ^^
                                                      details is missing; dot is superfluous

This is also inconsistent.

OK, let's remove the dots.

The following patch tries to address these issues:
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index a2e1af919..0f7e14ec4 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -7607,7 +7607,7 @@ perleval({expr})					*perleval()*
 <		{only available when compiled with the |+perl| feature}

-popup_ functions are documented here: |popup-functions|.
+popup_ functions are documented here: |popup-functions-details|

I prefer using popup-functions here, as it gives an overview of the
functions, before going into details.
--
Q: Is selling software the same as selling hardware?
A: No, good hardware is sold new, good software has already been used by many.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

This comes from adding "-details" after "some-functions".  But it reads
strange, perhaps we should follow the last two.  Not sure though.
Opinions?

I guess it would work too.  Using the last two as a template for the other ones would bring the whole set of tags more in line with all the -functions tags which don't jump to another file (like :h tag-functions, :h list-functions, ...).


Force vertical layout when struct_variant_width is 0

Currently rustfmt does not force vertical layout. Closes #1809.

Thanks! (I don't think this closes #1809 - we still need to do something in the default case, which is blocked on a spec decision).


Convert flatbuffer binary to json

Why is this needed? We are already saving the generated TTNN IR with other reports in default reportify directory...

This was added as a way to dump the generated binary and json so that it can be used to run generate_md script present in this branch as an experiment.
CC: @dgolubovicTT

This change was made in order to generate json files for unique ops so that we could generate ttnn configurations for the ttnn folks. @tt-mpantic contacted me to check if this json generation works as input to generate_md.py  script for generating ttnn configurations. I verified that it had worked and generated ttnn configurations Mladen needed.
If we are going to provide those configurations to ttnn folks, we should have this in main... Question for @tt-mpantic: Is this recurring and can you give more details on that ttnn effort? Are they using these for debugging, planning or something else?

recurring and can you give more details on that ttnn effort? Are they using these for debugging, planning or something

Thanks for the context!
The information you shared, this will be valuable information to have for the long run. I.e. to have this data stored in our database. Let's discuss the details tomorrow and determine next steps :))


baseline.rs: remove constant declaration checks per arch

We already are checking for target_arch when using the constants. Just instantiating them when we are in a target arch makes the build fail when we are building on a arch that that hits the constraint we created for initiating the constant.
closes #112

draft while I test this locally. I just messed up my toolbox by upgrading to f39. So this is just a theory atm... I can't see anything else that could be wrong.

It builds ok locally and I started up a s390x debug pod, ran:
cosa shell
sudo dnf install openssl-devel glib2-devel ostree-devel
cargo build

and got a good build:
   Compiling bootc v0.1.0 (/home/jenkins/agent/workspace/debug-pod/bootc/cli)
    Finished dev [optimized + debuginfo] target(s) in 2m 26s
[coreos-assembler]$ uname -a
Linux 1830b359aaec 6.3.12-200.fc38.s390x #1 SMP Thu Jul  6 03:39:39 UTC 2023 s390x GNU/Linux

A procedural note, we don't usually include the file suffix ".rs" in the topic prefix.  This is about the install code (module).  And it's usually best in the subject message to explain a bit more what the goal is.  Something like:

install: Compile (but error at runtime) on non-x86_64/aarch64

This all said, while I'm not opposed to this fix...thinking about this a bit more, what seems it'd be better (and about equally easy) is to change the build configuration in Cargo.toml to only enable the install feature on x86_64 and ppc64le.
Then we can drop many of the architecture conditionals in that code.  Conceptually we'd be going from bootc install on those arches saying "This isn't implemented" to "command not found" which I think is probably more right.
Hmm...I'm not totally sure Cargo has support for conditionally enabling a crate feature for a given arch (without resorting to a build script).  It does support this for dependencies https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#platform-specific-dependencies
Well...in the end, let's just do some cleanup for this commit message and merge!
(Of course the real fix is to actually implement the install flow for those arches, but that's more involved)

BTW just for reference this install logic is a Rust rewrite of https://github.com/coreos/coreos-assembler/blob/main/src/create_disk.sh


result.Prediction type

Problem encountered on https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/consume
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Hi, In the final step I am getting the output for console app still like 1 and 0 instead of true/false.
From line: Console.WriteLine($"Text: {input.SentimentText}\nIs Toxic: {result.Prediction}");
Not a big deal really.

It's because value for your label is 1/0.
To be detailed, we used to try parsing label type as boolean before but we found it might be confuseing in some cases, (for example, should we also parse value "true", "false" to boolean? if so the output will be "True", "False", which just does too much and might not be expected. So then we decided to keep label's value as what it is.

Close due to no response, feel free to reopen it if you still have the problem


*: reduce dependence on our sysinfo

Problem Summary: we currently use our own fork of the sysinfo crate. This is suboptimal since it is regularly updated and we miss out on those updates.
What's Changed: this PR effectively inlines a few commits from our fork: tikv/sysinfo as a step towards using upstream sysinfo.
PTAL @lonng @zhangjinpeng1987

/merge

/merge


[DSIP-35][Alert] Refactor the alert thread model

Purpose of the pull request
close #15931
Brief change log

Add EventFetcher、EventPendingQueue、AlertEventLoop interface and implement these.

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report
Attention: Patch coverage is 38.42795% with 282 lines in your changes are missing coverage. Please review.

Project coverage is 39.65%.  Consider uploading reports for the commit fb54c8c to get more accurate results

Files
Patch %
Lines

...phinscheduler/alert/service/AbstractEventLoop.java
0.00%
38 Missing :warning:

...nscheduler/alert/service/AbstractEventFetcher.java
0.00%
37 Missing :warning:

...inscheduler/alert/service/AbstractEventSender.java
72.81%
22 Missing and 6 partials :warning:

...scheduler/alert/service/AlertBootstrapService.java
0.00%
21 Missing :warning:

...r/plugin/registry/zookeeper/ZookeeperRegistry.java
27.58%
16 Missing and 5 partials :warning:

...inscheduler/plugin/registry/etcd/EtcdRegistry.java
0.00%
19 Missing :warning:

...inscheduler/alert/service/ListenerEventSender.java
55.88%
14 Missing and 1 partial :warning:

...he/dolphinscheduler/alert/service/AlertSender.java
68.18%
12 Missing and 2 partials :warning:

...er/alert/service/AlertSenderThreadPoolFactory.java
0.00%
11 Missing :warning:

...org/apache/dolphinscheduler/alert/AlertServer.java
0.00%
7 Missing :warning:

... and 31 more

Additional details and impacted files
@@             Coverage Diff              @@
##                dev   #15932      +/-   ##
============================================
- Coverage     39.72%   39.65%   -0.08%
+ Complexity     5034     5032       -2
============================================
  Files          1349     1363      +14
  Lines         45615    45656      +41
  Branches       4891     4853      -38
============================================
- Hits          18122    18103      -19
- Misses        25578    25642      +64
+ Partials       1915     1911       -4

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

It's strange, miss ready-to-merge?

It's strange, lack ready-to-merge?
The input is incorrect, maybe a bug.

Same confusion, and when I remove or add labels, it will not trigger new label check.

It's strange, lack ready-to-merge?
The input is incorrect, maybe a bug.

It's odd. I can't trigger the re-execution either. It seems to be out of order...

Is there any way we can retrigger the action?

I click the Re-run button, but it doesn't work.
I have created an issue to mergeable repo https://github.com/mergeability/mergeable/issues/745, it might be a bug.

Close/Reopen to retrigger the checker.

We may need to remove this bot, otherwise we need to wait recovery.

We may need to remove this bot, otherwise we need to wait recovery.

Agreed. Remove it for now.


Increased logging details to assist in debugging

It is not possible to debug with current level of logging. Increasing the log details to check all errors when we hit the error cases for TDI tables

yes, I am raising this against the mev-ts-1.6 target branch and will also update the same on networking-recipe


#75 Use ctx.request.files instead of ctx.request.body.files

I see a big security problem of putting file objects in ctx.request.body.files from https://github.com/dlau/koa-body/issues/75.
so I changed it to put file objects in ctx.request.files instead of ctx.request.body.files, because there's a couple issues at the current version.

if there's files field and multipart file included in request at the same time, there'd be a conflict.
if somebody specifies files field to request, somebody could view any contents on the server by specifying the path on files field.  details in the issue.

Shouldn't we also put ctx.request.body.fields directly into ctx.request.body in this case? This would allow the same handler to handle both simple POST and multipart POST with the same code.
This would make it work similar to Django, where there is always request.POST (ctx.request.body) and optionally request.FILES (ctx.request.files)

@IlyaSemenov it would also make it consistent no matter what the POST body type is. Having to try to adjust to the current unpredictable data structure is a serious headache, especially with typescript.

For the time being, I am using this:
app.use(koaBody({ multipart: true })) // prepare ctx.body
app.use((ctx, next) => {
	if (ctx.is('multipart')) {
		const { files, fields } = ctx.request.body
		ctx.request.files = files
		ctx.request.body = fields
	}
	return next()
})

and to please the type checker, this (in root index.d.ts):
import { Request } from 'koa'

declare module 'koa' {
	interface Request {
		files?: Array<any>
	}
}

(not sure if there's better type than any for the case)

@IlyaSemenov I like that approach, honestly.
Anyways I'm trying to throw together a PR that does just that, but as it turns out, the tests won't pass.
The tests can't pass.
supertest isn't setting res.files at all with what goes into ctx.request.files, even if you patch the node ctx.req object with a .files property.
From the tests:
    request(http.createServer(app.callback()))
      .post('/users')
      .type('multipart/form-data')
      .field('names', 'John')
      .field('names', 'Paul')
      .attach('firstField', 'package.json')
      .attach('secondField', 'index.js')
      .attach('secondField', 'package.json')
      .attach('thirdField', 'LICENSE')
      .attach('thirdField', 'README.md')
      .attach('thirdField', 'package.json')
      .expect(201)
      .end( (err, res) => {
        if (err) return done(err);
        res.body.names.should.be.an.Array().and.have.lengthOf(2);
        res.body.names[0].should.equal('John');
        res.body.names[1].should.equal('Paul');
        res.files.firstField.should.be.an.Object;
        res.files.firstField.name.should.equal('package.json');

Once we get to the req.files lines, it explodes. No matter what I try, req.files is undefined.  Hmm.

Apologies for the lateness, yes this should go in.
How about a one-off test that bypasses supertest and manually constructs a request?

Closing in favor of #89, which this was the basis of.

How does one find out that the files are under request.files and not request.body.files? I found it here (took me a while) but it doesn't appear to be documented anywhere?

@laurent22 added a quick note here https://github.com/dlau/koa-body/commit/8f95cfbaf4c4e50f1609b20dfe4a43502a82d53a . Feel free to PR more documentation.


Better integration with JSON-B and MP Rest Client

I am attempting to write a REST Client for a health check endpoint like this:
    public static class HealCheckResponses {
        public List<HealthCheckResponse> checks;
        public HealthCheckResponse.State status;
    }

    @ApplicationPath("/health")
    public static interface HealthEndpoint {

        @GET
        @Path("liveness")
        @Produces(MediaType.APPLICATION_JSON)
        public HealCheckResponses liveness();
    }

However, this does not work because HealthCheckResponse is an abstract class that requires a concrete implementation and some sort of HealthCheckResponseProvider in order to simply create an instance?
From what I can see, HealthCheckResponse should be a simple concrete data class and have no external dependencies (not dependent on any Services being present etc).
Proposed changes

Make HealCheckResponses a concrete class, instead of abstract
Add a new public constructor (in addition to the no-orgs ctor for backwards compatibility) where all values can be initialized upon construction to preserve immutability:
public HealthCheckResponse(String name, State state, Optional<Map<String, Object>> data)
[Optional] Add JSON-B annotations to HealthCheckResponse, such as @JsonbCreator and @JsonbProperty for out-of-the-box JSON-B compatibility

Thanks for looking at this @antoinesd and @xstefank!


Flask-Login v0.3 breaks backwards compatibility

From Flask-Login CHANGES:
 BREAKING: The `is_authenticated`, `is_active`, and `is_anonymous` members of
 the user class are now properties, not methods. Applications should update
 their user classes accordingly.

I hope one of the following will work:
current_user.is_authenticated() if callable(current_user.is_authenticated) else current_user.is_authenticated

We'll need to address this in many locations:

Flask-User python code
Flask-User html templates
Example and test python code
User customized html templates.

I have placed a warning in the docs for now.

Flask-User v0.6.8 has been released.
It supports Flask-Login v0.3+ in addition to Flask-Login v0.2.x.


Accessible view: pressing the "Menu" key breaks all context menus and accessible view

Testing #210598
VS Code: latest 1.89.0-insider
OS: Windows_NT x64 10.0.22631
GHPR extension: v0.87.2024042204 (pre-release)

Checkout PR with multiple comments

Open Comments pane

Open accessible view with Alt+F2

Press the "Menu" keyboard key -> accessible view closes unexpectedly

Press Alt+F2 again -> accessible view doesn't open and an error is shown:
Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

All right-click actions in VS Code no longer work (e.g. right-click a file in Explorer view no longer shows the context menu)

Run Reload Window command to restore all functionality

Note: pressing Shift+F10, which can be substitute for the Menu key, doesn't have this effect.

This is really odd. I do not have a keyboard with a menu key 🤔 , no idea why it would cause such issues.


Text channels ?

Hi,
I was wondering why there isn't any text channel feature on NXCord ...? I don't know how it works but i think it wouldn't be really hard to show text channels and send / receive messages. Is there a reason why it is not already in the app ?

I don't really see the point of add text channels. Just using your phone is way more convenient.


Add pre-commit hook for Puppetlabs PDK - need help with negative rspec tests

Greetings Overcommit team,
I've created an additional pre-commit hook that runs puppetlabs 'pdk validate' and it seems to work quite well. Reason for doing this is because:

Puppetlabs has bundled the toolset of their own and it's great!
It basically replaces the separate toolings like puppet-lint, yamllint, yamlsyntax, rubocop...

However i am a bit struggling with the rspec tests, can't get negative testing right. Would you be so kind as to nudge me in the right direction to do this?
the spec test in question can be found here
Once i have this right, i can squash and make a PR.
Thank you for your feedback.

@sds

I'm not sure I understand your question, @NeatNerdPrime. The file you link to has no negative tests.
There are many examples of negative tests that have already been written. Here is one for RuboCop: https://github.com/sds/overcommit/blob/dd9ba2adcc5988ffd27e922486773c304bf2cc08/spec/overcommit/hook/pre_commit/rubo_cop_spec.rb#L37-L53.
Again, not sure I'm understanding what you're asking. I hope this helps.

Yeak kinda helps, what i don't understand is: Is the "file1.rb" which  is mentioned here some file added to the test suite that exists explicitly for raising this warning?  I'll try to figure it out and expect a PR in the coming days. Apologies for my late reply.

Apologies for not responding. file1.rb is just fake output—it can be anything. In this case we're mocking the output.
Closing this ticket due to age, but feel to submit a pull request if you'd like to see this implemented!


@A9G-Data-Droid there are many reasons users may encounter problems executing winget. Generally this falls into a few areas.

@A9G-Data-Droid there are many reasons users may encounter problems executing winget. Generally this falls into a few areas.

The APP Installer on the host machine doesn't include the Windows Package Manager.
The App Installer isn't registered for the user (account) attempting to execute winget.
App Execution Alias isn't enabled for the Windows Package Manager.
Something is corrupt or has been modified related to the App Installer (or associated files / path)

When we can clearly isolate the issues and find consistent mechanisms to reproduce them, we work on fixing them, and/or we work on adding documentation. The original author of the issue hasn't responded to this issue to help clarify what they are experiencing and responding to questions.
The bot looks for the "Needs-Author-Feedback" label, and whether the author or another user from the community has responded to the issue. If no activity has happened after 7 days, the issue is labeled "No-Recent-Activity". If there is no activity 7 days after that, then the bot will automatically close the Issue.
This issue has a very broad scope. There isn't likely to be any single solution. With issues like this, we try to break them down into bite sized pieces we can tackle. Many other users with the same "winget command does not work" issues have been resolved, and may contain answers for an individual scenario. We try to keep actionable issues open until we can fix them.
Much of the content on this issue is more of a "discussion". We don't close discussions.
With this issue, I would try to help the original author as we work towards better answers / guidance. In many cases I get notifications when users comment on closed issues. We are very active here. I try to respond to any questions, or something actionable. Unfortunately, this issue is just too broad in scope to find a single solution.
My hope with this response is the list of currently known problem spaces will help others find something that resolves their particular issue.
Originally posted by @denelon in https://github.com/microsoft/winget-cli/issues/995#issuecomment-862549567
faced with the same issue
Get-AppxPackage microsoft.DesktopAppInstaller command result
Name              : Microsoft.DesktopAppInstaller
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 1.4.3161.0
PackageFullName   : Microsoft.DesktopAppInstaller_1.4.3161.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.4.3161.0_x64__8wekyb3d8bbwe
IsFramework       : False
PackageFamilyName : Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
Dependencies      : {Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe, Microsoft.VCLibs.140.00_14.0.29231.0_x64__8wekyb3d8bbwe, Microsoft.DesktopAppInstaller_1.4.3161.0_neutral_split.language-ru_8wekyb3d8bbwe, Microsoft.DesktopAppInstaller_1.4.3161.0_neutral_split.scale-100_8wekyb3d8bbwe}                                                                                IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

i checked the path to AppInstaller, and there is only python scripts

also I joined the Windows Package Manager Insiders Program

@and-bulk what version of Windows are you running?
When did you join the Windows Package Manager Insider Program?

@and-bulk what version of Windows are you running?
When did you join the Windows Package Manager Insider Program?

today

It takes a few days to actually get registered in the Insider program. We have a manual process to add users. Unfortunately, the e-mail confirmation is immediate. We're looking into the possibility of delaying the e-mail notification or modifying the template.

It takes a few days to actually get registered in the Insider program. We have a manual process to add users. Unfortunately, the e-mail confirmation is immediate. We're looking into the possibility of delaying the e-mail notification or modifying the template.


Custom naming archive

I would like to be able to name the final archive myself, maybe use text/template ? For example I want to name the archive counter-test-v0.2.2-Windows_x86_64.tar.gz, currently I would have to generate the config using a template myself, it would be nice if it was to do that with config itself.

yeah, I think this was asked by other people too, so this is surely a must.
thanks!


Provide discovery via package.json

Close the loop, barely, on #4427.
Todo

[x] add tabs to /on/npm/ with stub for default, uploading a package.json
[x] style tabs
[x] implement package.json pasting and parsing
[ ] differentiate the approval states

Look familiar? We're right back to https://github.com/gratipay/gratipay.com/pull/4135#issuecomment-254098891. ☺

https://docs.npmjs.com/files/package.json

So can we repurpose the project-listing.html template for this? I am thinking we want our own (still punting on refactoring all that).

Alright, let's maybe cram this all into one test case.

claimed by self
claimed by other
unclaimed
unknown

55e21aad728a1de14e4d355b66a3f2ca76efe06c

Kinda ridiculous to be hitting these whack-a-mole testing issues:

https://travis-ci.org/gratipay/gratipay.com/builds/241331213#L2968 → e22cfe76dc34396a1b13944b6b5513856c3f3843
https://travis-ci.org/gratipay/gratipay.com/builds/241335720#L2983 → 7f76e26f90ca1032f552730dcd0be937f10ab1d6

Good lord I hit another one! 😩

/me restarts https://travis-ci.org/gratipay/gratipay.com/builds/241344561 ...

3c22a1b678d7f7da4eb68f546649160fbb41dccc

Email whack-a-mole (number 1) is not fixed. Restarting ...

I'm putting this in Review, @mattbk @rohitpaulk et al. Have at it!

Rebased, was 3c22a1b678d7f7da4eb68f546649160fbb41dccc.

Rebased after pushing a a few commits upstream to #4511. Was d6496d489c3d7ef63d2320ee0e5826aac1500f90.

Rebased after significant refactoring on #4488, was c92d7f37b028b2945d23f83b61dc822806462341.

Looks like we've got some CSS regressions:

Regressions fixed! Fixes included in new 395303c5d8001a2c482acca06a4ffea4023bfcb7 and cdc2a5be9276795dff33b29185ba64ccec96f07f.

In 034614f12d7495ef85fa2a71ba88abe6638e3f17 I flipped it so anon can search for packages, no need for a sign-in wall for that.

Ooh! Ooh! Ghost includes mysql, which is already on Gratipay! Let's make sure clicking "Find packages" by default shows a package to actually really give to.

b81084e6e5603a18aa76a66c582642d50661be66 💃

Blorp. Follow-on is rough. Click an unclaimed package and you get a prompt to sign in to accept payments. But you were there to give payments! And if you click "Back" you get a form post reconfirmation. 😕

Pledging (#4195) will help I guess.

Tweaked slightly in bf38cdb11903e3d23277ac2782f1969a7805ddd6:

60a26ba4e743eeceff0d657d5822c9fcd4604872:

Squashed and busting up. Was 781edd0c33b1be0b6f73f3682832ebcd82f0596d.


Should input without schema be default to https?

I mean this line:
https://github.com/matthew-andrews/isomorphic-fetch/blob/master/server.js#L6
While it's safer, it's probably not what browser would do (I mean if you type example.com, it would default to http, at least currently they are.)
I struggle with this decision when writing node-fetch (there are no origin to speak of), and decide user should just normalize the url the way they prefer instead.

hmm. You're right but it probably doesn't matter too much. If you're using //example.com style URLs then you have to make sure the URL you're loading will work on https anyway.  I choose https because I wanted to encourage https :-).  But your notes about the browser are probably right.

Thinking about this more I think if you're using //example.com schema you probably know that endpoint supports https (otherwise you'd use http explicitly) so we might as well use it.
I think this a reasonable case where we don't have to try to match browser behaviour (which is probably the way it is for legacy reasons) and do something better — ie. put security first.


Bug with group meshes

This bug reported via community under the post. Main problem is grouping meshes according to their materials when they are under the group or component. Instead group meshes, theoratically we should send them separately because when we receive back they will be handled as separate objects. And also realized that currently we do not send orphan edges (edge that does not involve any face) in the group.
PS: Performance should be checked.

Regardless of this issue, when SketchUp have face that have more than one pieces that are disconnected, causes below mesh problem.

Self intersecting is detected.


Add UC Browser - mimic IE

Related: https://github.com/Financial-Times/polyfill-service/issues/846
Grabbing name from https://github.com/ua-parser/uap-core/blob/master/regexes.yaml#L113
Using caniuse.com I've found that a majority of items UC Browser does not support closely match IE and am proposing this browser to act as IE (IE10 more specifically) on recent versions of UC Browser 9.9.

Hi @zslabs, thanks for taking the time to create a pull request to this project, I'm always happy to see new faces offering to help out :-)
You can ignore the CI issues, they are happening because your fork doesn't contain SauceLabs environment variables.
Are you able to test this on UC browser and confirm your assumption that we can alias UC to IE? It would help us have confidence that this is in fact true.
I also need to check that you have read and agreed to our contribution terms (pasted inline for convenience):

All contributions to the polyfill service are made under the MIT licence. It is important therefore that you agree to the following when contributing code to the service:

Any contribution I make to the polyfill service by way of Pull Request contains only data that is:

wholly my own work, upon which I am legally permitted to grant a licence; or
wholly the work of individuals within the same organisation to which the copyright in all work created by employees is assigned, of which I am a current employee and authorised representive for the purposes of this contribution, and which is legally permitted to grant a licence; or
licensed by the original author under the MIT licence or equivalent terms

In respect of any part of my contribution that is not already available under an MIT or compatible licence, I hereby grant to the Financial Times Limited (FT) and to recipients of software distributed by the FT a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable license to make, have made, use, offer to sell, sell, import, and otherwise transfer the data.

It is helpful to us if you can clearly state your agreement to the above terms when creating a pull request. If you don't, you may be asked to post a followup comment to accept the terms, before we can merge your PR.

Thanks again for this, if there is anything I can help with, feel free to ask.

Hi @JakeChampion, sure - I'm fine with the above terms. In terms of the coverage, I used caniuse.com to run through as many properties as I could and related them more closely to IE than any other browser. I don't have UC Browser personally, but it's come up enough times on Bugsnag that I figured it'd be a good one to patch if possible ;) so I'm leaning on caniuse.com to help.

@zslabs Hey Zack.  Currently your change will map every version of uc browser to IE10 (including all future versions of UC Browser).  That seems like it might not be a great match.  I think a couple of specific version mappings would be OK, but as proposed I think this change would make targeting worse over time (because the gap between UC latest and IE10 would widen)

Hey @triblondon yeah I 100% agree. The version area supports wildcards, correct? I've added in a more specific version-range based on the research I was able to compile with caniuse.com
Thanks!

@zslabs can you screenshot and paste the docs that you're using as a reference for those figures?  And also a sample uc browser UA string which we can use to test the browser identification?

Hey @triblondon,
While pasting a screen shot of all of the comparables between the two browsers would be pretty darn big, if you visit http://www.caniuse.com and click the "Settings" link at the top, you can turn on/off specific browsers for a more detail oriented look between the two.
Here's a screen shot from the page for version usage:

This site has some example UA headers that can be used for testing, with a 9 example being Mozilla/5.0 (Linux; U; Android 4.4.2; en-us; Aqua 3G Build/Aqua_3G) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 UCBrowser/<IP_ADDRESS>9 U3/0.8.0 Mobile Safari/533.1 taken from an Android 4.2 device.

OK.  I tweeted at UC to ask them if this seems like a reasonable mapping to them:
https://twitter.com/triblondon/status/774065264736415745
If they are OK with it or don't respond then I'm happy to merge it.

Hi @triblondon,
It doesn't look like they've responded yet - how are we feeling about this one?

@zslabs This is now live on http://qa.polyfill.io - would you be able to report back whether we have fixed your issue?


How to load images ?

Hello,
I been playing around with LiteNN, and i wanted to say great job on the LiteNN. also i want to ask how to load images as there seem no official way to load batches of images, my current stop gap measure is to use opencv to load images and convert it into numpy array afterward convert it into a Tensor.
imgcv = cv2.imread(imgpath)
test_tensor = nn.Tensor_from_value(imgcv)

Will there be a way to load images directly from LiteNN  ?,

LiteNN receives only numpy data

yes sorry, what wanted to ask is will there be in inbuilt function to load images similar to pytorch "DataLoader" ?
as for the OpenCV, it is just the easiest way i know to load images as numpy array.

why? just use cv2 imread , or lod through PIL


Latest commit causing action to fail

Hi there,
I'm using this to authenticate and deploy my app onto Google Cloud Run. Snippet below is from my github workflow file:
- uses: GoogleCloudPlatform/github-actions/setup-gcloud@master

It's started immediately failing, I believe due to the latest commit. I re-ran passed workflows from yesterday which now fail. The error on these and all new workflows is:
Run GoogleCloudPlatform/github-actions/setup-gcloud@master
/home/runner/work/_actions/GoogleCloudPlatform/github-actions/master/setup-gcloud/dist/index.js:7860
        methods.forEach(function(m) {
        ^^^^^^^

SyntaxError: Unexpected identifier
    at Module._compile (internal/modules/cjs/loader.js:718:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:785:10)
    at Module.load (internal/modules/cjs/loader.js:641:32)
    at Function.Module._load (internal/modules/cjs/loader.js:556:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:837:10)
    at internal/main/run_main_module.js:17:11
##[error]Node run failed with exit code 1

Any ideas?

A syntax error seems to be causing this issue.
https://github.com/GoogleCloudPlatform/github-actions/blob/0c32120a9a2dda7fb9b392e6c3b90fa413b4642e/setup-gcloud/dist/index.js#L7853-L7863
Checking out an older commit worked for me as a workaround.
- uses: GoogleCloudPlatform/github-actions/setup-gcloud@4d8f7a1

@mingles @wktk Thanks for pointing this out, let me know if you have any other issues.

@stephenashank Thank you for the update!
Unfortunately, it is still failing for me.  It seems that we need to rebuild setup-gcloud/dest/index.js.
 /home/runner/work/_actions/GoogleCloudPlatform/github-actions/master/setup-gcloud/dist/index.js:9124
          })(b64chars);
           ^

SyntaxError: Unexpected token )
    at Module._compile (internal/modules/cjs/loader.js:718:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:785:10)
    at Module.load (internal/modules/cjs/loader.js:641:32)
    at Function.Module._load (internal/modules/cjs/loader.js:556:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:837:10)
    at internal/main/run_main_module.js:17:11
##[error]Node run failed with exit code 1

A quick postmortem revealed this was caused by eslint not playing nice with the code ncc was generating. I've reverted the manual changes to the dist/ folder and re-ran npm build.  I will follow up with a PR removing eslint from scripts and adding an IT which will ensure something like this doesn't get released again.


Make Docker badge link to Docker Hub page

You appear to have a stray ] after the docker badge. Also, PRs are merged into develop although this shouldn't have any merge conflicts so I've just changed the base to merge into for you.

Thanks, fixed.

Sweet, merging in now :+1:


Error when try to run supervised/semi supervised experiment (mac version)

So i have download moses for mac, but it seems that there are some incomplete dependency to xmlrpc-c

Python 3.7.7

Hello,
This is a duplicate from issue #11
We didn't test our source code on mac. The error might be caused by the compiled binary file provided by the author of the Moses Toolkit.
Sorry for the inconvenience

I have the same problem when I runned it from WSL2 (Windows Subsystem for Linux 2)

Hello @Picasso1503,
Could you run this script on your stif-indonesia folder and paste the error here?
nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and                         -reordering msd-bidirectional-fe                         -lm 0:3:/mnt/d/Documents/Projects_Company/Research/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza

Change the [ABSOLUTE_PATH_TO_STIF_INDONESIA] with the absolute path of stif-indonesia folder (use pwd).

Thankyou. This is what I've got
On Fri, Dec 11, 2020 at 3:09 PM Haryo AW<EMAIL_ADDRESS>wrote:

Hello @Picasso1503 https://github.com/Picasso1503,
Could you run this script on your stif-indonesia folder and paste the
error here?
nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and                         -reordering msd-bidirectional-fe                         -lm 0:3:/mnt/d/Documents/Projects_Company/Research/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza
Change the [ABSOLUTE_PATH_TO_STIF_INDONESIA] with the absolute path of
stif-indonesia folder (use pwd).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/haryoa/stif-indonesia/issues/12#issuecomment-743042253,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARUIF2HWP5CKSCMXMJHYJZ3SUHHTLANCNFSM4UAPEG4Q
.

Thankyou. This what I've got

and what do you mean about change the path to absolute path? I dont understand yet

Absolute path means the path file from your root directory to your file or directory in your OS.
For example:
/home/muhammadrizky15/stif-indonesia/
use pwd command in your WSL2 terminal to see the absolute path of the folder stif-indonesia
I cannot see your Capture.PNG. Would you mind to edit it? Thank you.

This what I've got

change [ABSOLUTE_PATH_TO_STIF_INDONESIA]/stif-indonesia/output/supervised/lm/blm/data.blm.for to /home/muhammadrizky15/stif-indonesia/stif-indonesia/output/supervised/lm/blm/data.blm.for in your -lm arguments. That /mnt/d/ path is for my local computer...

change [ABSOLUTE_PATH_TO_STIF_INDONESIA]/stif-indonesia/output/supervised/lm/blm/data.blm.for to /home/muhammadrizky15/stif-indonesia/stif-indonesia/output/supervised/lm/blm/data.blm.for in your -lm arguments. That /mnt/d/ path is for my local computer...

I don't understand, can u explain about the command line, bcs I never used linux system before

nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and                         -reordering msd-bidirectional-fe                         -lm 0:3:/home/muhammadrizky15/stif-indonesia/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza

Here you go

nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and                         -reordering msd-bidirectional-fe                         -lm 0:3:/home/muhammadrizky15/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza

Here you go

I've got error

is it important to install miniconda? but I've been installed python environment to WSL2

As long as you have Python 3.7++ on your WSL2, it is good to go. You do not need to install miniconda.
Can you do these steps in sequence:

rm -rf output (remove output folder)
python -m stif_indonesia --exp-scenario supervised (run supervised experiment that will output the error)
nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and -reordering msd-bidirectional-fe -lm 0:3:/home/roggl552vw/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza (run training)
Screenshot your error here

Note the roggl552vw on the step 3. I use your username on your WSL2. If you use different username, you need to change that part.

First, delete output folder.

The second command line, I've got this error

The third command line, I've got this error as the same as before

I think the error is caused when the program do training process. It didn't output extract.o.sorted.gz on your folder.
I think, I need your full log to inspect your error.
Before you do the following, are you sure you download the right moses by running this command bash scripts/download_moses.sh ?
I can run it perfectly with my WSL2 on WSL2 Ubuntu 20.04 (I think if you have Ubuntu 17.04++, it can work).
Do these:

rm -rf output (remove output folder)
python -m stif_indonesia --exp-scenario supervised (run supervised experiment that will output the error)
sudo nice moses/moses/scripts/training/train-model.perl -root-dir output/supervised/train -corpus data/labelled/train -f inf -e for -alignment grow-diag-final-and -reordering msd-bidirectional-fe -lm 0:3:/home/roggl552vw/stif-indonesia/output/supervised/lm/blm/data.blm.for -core 2 -external-bin-dir moses/training-tools --mgiza &> out.log (run training and redirect the output to out.log. I add sudo here because I suspect that you didn't give permission to write to the folder.)
upload out.log here.

Also I need you to screen shot your ls -al ls -al output/supervised/train/model after you do these steps.

out.log
That's All

Ya, I've double check, I runned bash scripts/download_moses.sh in stif-indonesia folder

First, delete output folder.

The second command line, I've got this error

The third command line, I've got this error as the same as before

Hello @Picasso1503 , have you try to delete output directory and retrain?

First, delete output folder.

The second command line, I've got this error

The third command line, I've got this error as the same as before

Hello @Picasso1503 , have you try to delete output directory and retrain?

Yap @goFrendiAsgard , I've been removed it using rm -rf output


Fixed error in MemoryRegion.containsRange() function.

Fixed error. When both end and length parameters to MemoryRegion.containsRange() are not given, None was used in an arithmetic expression.

I am not certain of the appropriate way you take pulls. Do you prefer lots of small pulls, or one big one? Also, do you accept corrections of unnecessary code that is not harmful but it is just useless (example in CortexM class reset() method default parameter as None, since that trick is only needed when the parameter is a mutable object)

Hi @David-Garcia-Polo , thanks for the pull request!  Code corrections are appreciated even when the code being changed is harmless.  For stylistic changes, try to stick with pep8/pylint.
Pull request size is fairly open ended.  It's a little nicer to have smaller pull requests but it's not a requirement.  It is helpful if each commit within a pull request is a single logical change grouped together.  If you do end up creating several pull requests, it is encouraged to rebase each pull request on top of the previously merged pull request.  That way there is a more linear commit history.
Finally, you mention that the default parameter for reset is set to None.  I think the purpose of this was to allow additional information to be passed to reset, allowing it to determine the type of reset that is required - soft (True), hard (False) or either/unspecified (None).  For example if resetStopOnReset, which calls reset, had software_reset=True by default then reset would see that a software reset is required, even if it hasn't been explicitly specified by the caller of resetStopOnReset.

I agree with you that an assert will be more convenient to check parameter correctness. Updated pull as you suggested.

@David-Garcia-Polo can you please sign http://developer.mbed.org/contributor_agreement/ ?

You accepted the Contributor Agreement on Mon 30 Nov 2015.
I have accepted with another name, for some reason David-GArcia-Polo was not acceptable. The name is Advenedizo. Will it cause problems?

+1

Sorry for the delay.  Nope it won't cause problems.  Patch looks good


feat: Pull request workflow

Summary of changes

Report of required housekeeping

[ ] Wrote tests
[ ] Github issue OR spec proposal link
[ ] Added a relevant changelog entry to CHANGELOG.md

(FOR ADMIN) Before merging

[ ] Added appropriate labels to PR
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)
[ ] Confirm added tests are consistent with the intended behavior of changes
[ ] Ensure all tests pass

Hmm,  This is not js repository. $ npm build does not generate anything.


Go through the plugins and remove their dependency on Scribe Common

Now that scribe common is no longer separate from Scribe, it will be worth going through all the plugins that use it and updating them accordingly.
See this for an example.

https://github.com/guardian/scribe-plugin-curly-quotes
https://github.com/guardian/scribe-plugin-intelligent-unlink-command
https://github.com/guardian/scribe-plugin-smart-lists

All the plugins have now been updated so post the newsroom rollout I will need to update the dependencies on Scribe and Composer
Update Scribe example

[ ] Curly quotes
[ ] Intelligent unlink
[ ] Smart lists


make getting-started notebook runnable and add notebook to tests

Description
Make getting-started notebook runnable and add notebook to tests.  This is based on user feedback that this notebook is too confusing due to missing parameters and not runnable.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[ ] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[ ] No new tests required.
[x] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Codecov Report

Merging #1223 (d53c212) into main (f8e5d5a) will increase coverage by 8.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1223      +/-   ##
==========================================
+ Coverage   67.19%   75.58%   +8.38%
==========================================
  Files          91       10      -81
  Lines        4393      258    -4135
==========================================
- Hits         2952      195    -2757
+ Misses       1441       63    -1378

Flag
Coverage Δ

unittests
75.58% <ø> (+8.38%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ponsibleai/responsibleai/_tools/causal/__init__.py

raiwidgets/raiwidgets/model_analysis_dashboard.py

...iwidgets/raiwidgets/fairness_metric_calculation.py

responsibleai/responsibleai/__init__.py

raiwidgets/raiwidgets/explanation_constants.py

...tools/counterfactual/dashboard_schemas/__init__.py

raiwidgets/raiwidgets/utils.py

raiwidgets/raiwidgets/responsibleai_dashboard.py

...ai/responsibleai/_tools/error_analysis/__init__.py

responsibleai/responsibleai/_internal/__init__.py

... and 71 more

Continue to review full report at Codecov.

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


[core-js] Duplicate identified 'export='

There are tons of errors when starting sample 00 SimpleForm related to TypeScript and compilation with webpack:
ERROR in <<PATH>>/samples/react/00<EMAIL_ADDRESS>(3069,5): error TS2300: Duplicate identifier 'export='.

Steps to reproduce:

Clone the repository
cd samples/react/00\ SimpleForm/
npm install
npm start

Can we close this issue?

We will move to TS + Babel, we won't make use of core-js


Windows error on build:lib command, rest-hooks package

https://github.com/coinbase/rest-hooks/blob/105a3f1060b9c08f9d5830f653df78f597d95eb4/packages/rest-hooks/package.json#L55
The RESOLVER_ALIAS environment variable is set to '{\"^rest-hooks(.+)$\":\"./src/\\\\1.js\"}' however this fails when run on windows.
SyntaxError: [BABEL] C:\Users\ryanw\Documents\self\rest-hooks\packages\rest-hooks\src\index.ts: Unexpected token } in JSON at position 32 (While processing<EMAIL_ADDRESS>Per the cross-env docs: https://www.npmjs.com/package/cross-env

Variable should be set to {\\\"^rest-hooks(.+)$\\\":\\\"./src/\\\\1.js\\\"} and it builds correctly on windows.

Would love a PR that makes this work. My attempts failed. I develop exclusively on windows, but I use WSL. So if that's an option for you it should at least be a workaround. Otherwise I'd love to see how to make this work given the complexity of the commands needing to be issued.

Since we're using yarn 3 (berry) now this should work fine.


DBZ-2199 Avoid IndexOutOfBoundsException when no task config is available

https://issues.redhat.com/browse/DBZ-2199

LGTM, awaiting CI.

Looks like the error is related to one reported in DBZ-2177 which I am looking into now.

Thanks, @Naros!


RT-AC56U fails due to missing libxml2 (ARM)

The source is included, but all binary libs are exclusively for MIPS

arm-brcm-linux-uclibcgnueabi-ld -shared -o libws.so output/ws_src/curl_api.o output/ws_src/parse_xml.o output/ws_src/wb.o output/ws_src/wb_util.o output/ws_src/ssl_api.o output/ws_src/log.o -L/data/oliver/asus-merlin-local/release/src-rt
-6.x.4708/router/openssl -lcrypto -lssl -L/data/oliver/asus-merlin-local/release/src-rt-6.x.4708/router/curl-7.21.7/lib/.libs -lcurl -L/data/oliver/asus-merlin-local/release/src-rt-6.x.4708/router/libxml2/.libs -lxml2
arm-brcm-linux-uclibcgnueabi-ld: skipping incompatible /data/oliver/asus-merlin-local/release/src-rt-6.x.4708/router/libxml2/.libs/libxml2.so when searching for -lxml2
arm-brcm-linux-uclibcgnueabi-ld: skipping incompatible /data/oliver/asus-merlin-local/release/src-rt-6.x.4708/router/libxml2/.libs/libxml2.a when searching for -lxml2
arm-brcm-linux-uclibcgnueabi-ld: cannot find -lxml2

Tried running the script in "sudo-mode" and got a different error.
This time involving libxml2:
---- Output ----
checking that generated files are newer than configure... done
configure: creating ./config.status
Done configuring
make[4]: Leaving directory /home/bengt/asuswrt-merlin/release/src/router/libxml2' make[3]: *** [libxml2] Error 2 make[3]: Leaving directory /home/bengt/asuswrt-merlin/release/src/router'
make[2]: *** [all] Error 2
make[2]: Leaving directory /home/bengt/asuswrt-merlin/release/src-rt' make[1]: *** [bin] Error 2 make[1]: Leaving directory /home/bengt/asuswrt-merlin/release/src-rt'
make: *** [rt-n16] Error 2
make: Leaving directory `/home/bengt/asuswrt-merlin/release/src-rt'
Your image can be found here:
release/src-rt/image/*.trx

Is that the complete output?

Same module different error.  Can mail you config.log if you supply me with an email address

I am seeing warn issues about automake version mismatch for the build portion related to libxml2 in the logs when building for MIPS based RT-N16 build.  Here is the portion from the log of the current asuswrt-merlin github repo code:
touch libxml2/stamp-h1
make -C libxml2 all -j`grep -c '^processor' /proc/cpuinfo`
make[4]: Entering directory `~/release/src/router/libxml2'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash ~/release/src/router/libxml2/missing --run autoconf
 cd . && /bin/bash ~/release/src/router/libxml2/missing --run automake-1.11 --gnu
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
/bin/bash ./config.status --recheck
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
configure.in:50: version mismatch.  This is Automake 1.11.6,
configure.in:50: but the definition used by this AM_INIT_AUTOMAKE
configure.in:50: comes from Automake 1.14.1.  You should recreate
configure.in:50: aclocal.m4 with aclocal and run automake again.
running CONFIG_SHELL=/bin/bash /bin/bash ././configure --host=mipsel-linux --build= --prefix=/usr --without-python --disable-dependency-tracking build_alias= host_alias=mipsel-linux CC=mipsel-uclibc-gcc CFLAGS=-Os -Wall -DLINUX26 -DCONFIG_BCMWL5 -DDEBUG_NOISY -DDEBUG_RCTEST -pipe -DBCMWPA2 -funit-at-a-time -Wno-pointer-sign -mtune=mips32r2 -mips32r2 -DLINUX_KERNEL_VERSION=132630  LDFLAGS=-ldl --no-create --no-recursion
configure.in:53: required file `./compile' not found
configure.in:53:   `automake --add-missing' can install `compile'
checking build system type... x86_64-unknown-linux-gnu
checking host system type... mipsel-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
~/release/src/router/libxml2/missing: Unknown `--is-lightweight' option
Try `~/release/src/router/libxml2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing

Same happens when building RT-AC68U, I was building with IPSec support and got the same error:
Disabling code coverage for GCC
checking that generated files are newer than configure... done
configure: creating ./config.status
Done configuring
make[4]: Leaving directory '/home/victor/asus/asuswrt-merlin/release/src/router/libxml2'
Makefile:3186: recipe for target 'libxml2' failed
make[3]: *** [libxml2] Error 2
make[3]: Leaving directory '/home/victor/asus/asuswrt-merlin/release/src/router'
Makefile:170: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/victor/asus/asuswrt-merlin/release/src-rt-6.x.4708'
Makefile:2179: recipe for target 'bin' failed
make[1]: *** [bin] Error 2
make[1]: Leaving directory '/home/victor/asus/asuswrt-merlin/release/src-rt-6.x.4708'
Makefile:2235: recipe for target 'rt-ac68u' failed
make: *** [rt-ac68u] Error 2
make: Leaving directory '/home/victor/asus/asuswrt-merlin/release/src-rt-6.x.4708'
Your image can be found here:
        release/src-rt-6.x.4708/image/RT-AC68U_378.53_0.trx

CLEANUP: extended cleanup of source tree changes
+ mv /home/victor/asus/asuswrt-merlin/release/src/router/libxml2/configure.in.BAK-build-image /home/victor/asus/asuswrt-merlin/release/src/router/libxml2/configure.in

Also this fixed my build: http://www.snbforums.com/threads/stock-asuswrt-ac56u-libxml-build-problem.22904/

@YasharF: did you install the prerequisites accordingly?
@victor-rds: so pass --add-missing to all automake command lines or to particular ones? I can probably include that in the script, but the forum post is either cut off or a bit vague.

I reran using ./debian-build-image --prereq RT-N16 and I don't see the message about "Automake 1.11.6" anymore.  The following I think is the logs for the same section.
touch libxml2/stamp-h1
make -C libxml2 all -j`grep -c '^processor' /proc/cpuinfo`
make[4]: Entering directory `/home/yasharf/Workspace/AsusWRT/asuswrt-merlin/release/src/router/libxml2'
CDPATH="${ZSH_VERSION+.}:" && cd . && autoconf
 cd . && automake-1.14 --gnu
automake-1.14: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
/bin/bash ./config.status --recheck
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
configure.in:69: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:138: _LT_SETUP is expanded from...
m4/libtool.m4:67: LT_INIT is expanded from...
m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
configure.in:69: the top level
running CONFIG_SHELL=/bin/bash /bin/bash ././configure --host=mipsel-linux --build= --prefix=/usr --without-python --disable-dependency-tracking build_alias= host_alias=mipsel-linux CC=mipsel-uclibc-gcc CFLAGS=-Os -Wall -DLINUX26 -DCONFIG_BCMWL5 -DDEBUG_NOISY -DDEBUG_RCTEST -pipe -DBCMWPA2 -funit-at-a-time -Wno-pointer-sign -mtune=mips32r2 -mips32r2 -DLINUX_KERNEL_VERSION=132630  LDFLAGS=-ldl --no-create --no-recursion
configure.in:50: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
configure.in:50: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:53: error: required file './compile' not found
configure.in:53:   'automake --add-missing' can install 'compile'
Makefile.am:9: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
automake-1.14: warning: autoconf input should be named 'configure.ac', not 'configure.in'
checking build system type... x86_64-unknown-linux-gnu
checking host system type... mipsel-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/yasharf/Workspace/AsusWRT/asuswrt-merlin/release/src/router/libxml2/missing: Unknown `--is-lightweight' option
Try `/home/yasharf/Workspace/AsusWRT/asuswrt-merlin/release/src/router/libxml2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing

@assarbad no, you need to add a single line in asuswrt-merlin/release/src/router/Makefile the target libxml2/stamp-h1 should look like this:
libxml2/stamp-h1:
        cd libxml2 && \
        CC=$(CC) AR=$(AR) RANLIB=$(RANLIB) LD=$(LD) CFLAGS="-Os -Wall $(EXTRACFLAGS)" LDFLAGS=-ldl \
        ./$(CONFIGURE) --prefix=/usr --without-python --disable-dependency-tracking
        cd libxml2 && automake --add-missing
        touch $@

And although worked, I'm not sure if this is solution or just a workaround.

I'm wondering, should this be a patch submitted to asuswrt-merlin instead of build-asuswrt-merlin, or is the issue only when build-asuswrt-merlin is used?

@YasharF I'm wondering that too, and to be honest I only posted here because it was the first place I found same issue as mine.

Not a big deal, this script already patches up various things, I can add it here and keep it in a defensive coding style ... e.g. using patch ... so that if upstream fixes this, the script won't mess it up once again, for example ;)

Just checking to see if you had a chance to do the test builds.

+1
@victor-rds thanks that worked!

I've used this to make it works (Debian 7) :
libxml2/stamp-h1:
        cd libxml2 && \
        CC=$(CC) AR=$(AR) RANLIB=$(RANLIB) LD=$(LD) CFLAGS="-Os -Wall $(EXTRACFLAGS)" LDFLAGS=-ldl \
        ./$(CONFIGURE) --prefix=/usr --without-python --disable-dependency-tracking
        cd libxml2 && libtoolize && aclocal && autoheader && automake --add-missing
        touch $@