Enhancement: Add Quarto support

Description:
Addresses issue #9:  Add Quarto support.
Changes Made:
This commit modifies the autocmd configuration in md-headers.lua to include the *.qmd and *.Qmd patterns. This addition allows the plugin to work seamlessly with Quarto files, extending its compatibility beyond Markdown and RMarkdown files.
TODO:

[X] Add support for Quarto files using both the .qmd and .Qmd file extension.

Screenshots:

J'approuve!

Merci beaucoup, de votre collaboration. ;)
I will now merge this PR into the master branch!


Guidance on suggested repo structures

As an example, for data science and python you can use https://drivendata.github.io/cookiecutter-data-science/#example as a project template to automatically incorporate a lot of best practices.
For DDD .NET MicroServices - https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice
Terraform?

Look at https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository for potential other templates...

This isssue is just a starting point, we can add other issues later for specific templates

Closing due to lack of activity


Support fetching artifacts by OS & architecture

Describe the problem/challenge you have
I want my project to run on different platforms and so depending on which platform I am building for I want to download different artifacts.
For example, this vendir.yml pulls in kubectl for linux/amd64.
Describe the solution you'd like
I would prefer a solution where I don't have to download artifacts for all platforms, so maybe this needs to be an argument that's passed to vendir sync.
For the example given above it seems like we could allow this to work:
url: https://dl.k8s.io/release/{tag}/bin/{os}/{arch}/kubectl

Anything else you would like to add:
This probably only makes sense for certain kinds of artifacts: GitHub releases, HTTP maybe.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

may be also would be good to scope {os}/{arch} to something like {vendir.os}/{vendir.arch}, since in the example of githubRelease+http, tag is derived from that "local" context of githubRelease.
probably also makes sense to have binary{vendir.os_ext} so that on windows it's .exe vs on linux nothing.

interesting questions on this topic:

vendir.lock.yml relationship to what os/arch is set
how are values os/arch are set: auto, manually
should vendir have rename functionality (e.g. ytt-darwin-amd64 => ytt)

+1 to this


Entity synthesis for RF scanner device

Relevant information
Creating external RF Scanner entity. The required metrics are generated after receiving and parsing a scanner generated file in JSON format and ingesting via the Events API to create two custom event types.
Checklist

[x ] I've read the guidelines and understand the acceptance criteria.
[x ] The value of the attribute marked as identifier will be unique and valid.
[x ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

Thanks for the corrections @batbore! I left some comments on failing summary metrics


Unable to get prometheus metrics

Greetings! 👋🏻
I'm new here and have just started exploring Beyla, which seems quite promising 👍🏻 . We have a self-hosted Kubernetes (K8s) cluster and rely on a self-hosted Prometheus and Grafana (kube-prometheus stack) for metrics and dashboards, and it works great ☺
Now, I'm trying to get my hands dirty with Beyla to see if we can leverage it for our internal applications. I attempted to follow the official Kubernetes documentation (https://grafana.com/docs/beyla/latest/setup/kubernetes/) and have tried the sidecar method with the following manifest (The only change is that I have removed the OTEL_EXPORTER_OTLP_ENDPOINT envVar as we don't use grafana agent and have added BEYLA_PROMETHEUS_PORT envVar for having Prometheus scrape endpoint
apiVersion: apps/v1
kind: Deployment
metadata:
  name: goblog
  labels:
    app: goblog
spec:
  replicas: 2
  selector:
    matchLabels:
      app: goblog
  template:
    metadata:
      labels:
        app: goblog
    spec:
      # Required so the sidecar instrument tool can access the service process
      shareProcessNamespace: true
      containers:
        # Container for the instrumented service
        - name: goblog
          image: mariomac/goblog:dev
          imagePullPolicy: IfNotPresent
          command: ["/goblog"]
          env:
            - name: "GOBLOG_CONFIG"
              value: "/sample/config.yml"
          ports:
            - containerPort: 8443
              name: https
        # Sidecar container with Beyla - the eBPF auto-instrumentation tool
        - name: autoinstrument
          image: grafana/beyla:latest
          securityContext: # Privileges are required to install the eBPF probes
            runAsUser: 0
            capabilities:
              add:
                - SYS_ADMIN
          env:
            - name: BEYLA_OPEN_PORT # The internal port of the goblog application container
              value: "8443"
            - name: BEYLA_PROMETHEUS_PORT
               value: "8445"
            - name: BEYLA_LOG_LEVEL
               value: "DEBUG"

I tried to send some requests to the goblog service, but no matter how many requests the service receives, all I get from the metrics endpoint is:
 curl localhost:8445/metrics
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0

According to the documentation, the exporter metrics include a handful of HTTP metrics, but I'm not sure why they are missing. Do I need to take care of any additional configurations?. I would appreciate it if someone could provide guidance here. Thanks! 🙏🏻

Hi @prasadkris, than you for giving Beyla a try.
First, I'd recommend you to try setting replicas: 1 to make sure that you query the Beyla in the same Pod that receives de requests.
Then I'd add the following section to the Beyla container:
          ports:
            - containerPort: 8445
              name: prom

This worked to me:
kubectl port-forward deployments/goblog 8443:8443 8445:8445

I did some requests in another terminal session:
curl -k https://localhost:8443/

And Beyla show me a complete set of metrics:
curl http://localhost:8445/metrics
# HELP http_server_duration_seconds duration of HTTP service calls from the server side, in seconds
# TYPE http_server_duration_seconds histogram
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-5678795459-4bctj-10111",le="0"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-5678795459-4bctj-10111",le="0.005"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-5678795459-4bctj-10111",le="0.01"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-5678795459-4bctj-10111",le="0.025"} 1

(etc...)

Thank you @mariomac, unfortunately it didn't work!
root@goblog-f4d94fb47-rbx27:/# curl http://localhost:8445/metrics
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0
root@goblog-f4d94fb47-rbx27:/# curl -sk https://localhost:8443/ | head

<html>
<head>
  <title>Blog template</title>

    <link rel="stylesheet" type="text/css" href="/static/style.css">
    <link rel="alternate" type="application/atom+xml" title="Blog" href="/atom.xml" />
    <meta charset="UTF-8">

</head>
root@goblog-f4d94fb47-rbx27:/# curl http://localhost:8445/metrics
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0
root@goblog-f4d94fb47-rbx27:/#

Thanks @mariomac  Please find the requested details below 🙏🏻
root@goblog-685f5979bd-x8sxt:/# uname -a
Linux goblog-685f5979bd-x8sxt 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 GNU/Linux

The logs are at: https://gist.github.com/prasadkris/9bce04d2c5f953f57ba826ccb6bba95a
Environment details:
K8s version: v1.28.3

Strange, can you try replacing:
            - name: BEYLA_OPEN_PORT # The internal port of the goblog application container
              value: "8443"

By:
            - name: BEYLA_EXECUTABLE_NAME
              value: "goblog"

?

I see the issue in your logs:
time=2023-11-29T23:53:52.001Z level=ERROR msg="cant start process tracer. Stopping it" component=ebpf.ProcessTracer path=/goblog pid=7 error="can't mount BPF filesystem: permission denied"

Can you confirm if this works if you add privileged: true in the securityContext: for the autoinstrument container?
We recently did some work to figure out why CAP_SYS_ADMIN isn't enough for some setups and we have some proposed solutions here:
https://github.com/grafana/beyla/issues/452#issuecomment-1825929947
If privileged: true works, we can try to apply the suggestion above to see if we can make it work without.

Thanks much @grcevski 🙏🏻 it did the trick 🎉  I could see all the metrics after adding privileged: true
root@goblog-59c787bf58-tsskj:/# curl -sk https://localhost:8443/ | head

<html>
<head>
  <title>Blog template</title>

    <link rel="stylesheet" type="text/css" href="/static/style.css">
    <link rel="alternate" type="application/atom+xml" title="Blog" href="/atom.xml" />
    <meta charset="UTF-8">

</head>
root@goblog-59c787bf58-tsskj:/# curl http://localhost:8445/metrics | head
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  722# HELP http_server_duration_seconds duration of HTTP service calls from the server side, in seconds
# TYPE http_server_duration_seconds histogram
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.005"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.01"} 0
http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.025"} 3
http_server_duratio2 n_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.05"} 4
 http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.075"} 4
  http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.1"} 4
0 http_server_duration_seconds_bucket{http_request_method="GET",http_response_status_code="200",http_route="/**",service_name="goblog",service_namespace="",target_instance="goblog-59c787bf58-tsskj-18355",le="0.25"} 4
 7222    0     0  4633k      0 --:--:-- --:--:-- --:--:-- 7052k
curl: (23) Failed writing body
root@goblog-59c787bf58-tsskj:/#

Awesome, glad to hear it! Do you mind trying to see if it works with the suggestions in the other link I pasted? I've marked what matters with #important in the comment there. There are few things, but mainly CAP_SYS_PTRACE is needed and using the standard /sys/fs/bpf file system mount.

Sure, I will try the suggestion indicated at https://github.com/grafana/beyla/issues/452#issuecomment-1825929947 and will let you know how it goes, thanks!

Unfortunately, it didn't work. I can only make it work if I deploy with privileged: true 🙁
updated manifest:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: goblog
  labels:
    app: goblog
spec:
  replicas: 1
  selector:
    matchLabels:
      app: goblog
  template:
    metadata:
      labels:
        app: goblog
    spec:
      shareProcessNamespace: true
      containers:
        - name: goblog
          image: mariomac/goblog:dev
          imagePullPolicy: IfNotPresent
          command: ["/goblog"]
          env:
            - name: "GOBLOG_CONFIG"
              value: "/sample/config.yml"
          ports:
            - containerPort: 8443
              name: https
        - name: beyla
          image: grafana/beyla:latest
          securityContext:
            runAsUser: 0
            capabilities:
              add:
                - SYS_ADMIN
                - SYS_RESOURCE
                - SYS_PTRACE
          ports:
            - containerPort: 8445
              name: prom
          env:
            - name: BEYLA_EXECUTABLE_NAME
              value: "goblog"
            - name: BEYLA_PROMETHEUS_PORT
              value: "8445"
            - name: BEYLA_LOG_LEVEL
              value: "DEBUG"
            - name: BEYLA_BPF_FS_BASE_DIR
              value: "/sys/fs/bpf"
          volumeMounts:
            - name: bpffs
              mountPath: /sys/fs/bpf
            - name: host
              mountPath: /host
            - name: run
              mountPath: /run
            - name: modules
              mountPath: /lib/modules
            - name: debugfs
              mountPath: /sys/kernel/debug
            - name: cgroup
              mountPath: /sys/fs/cgroup
      volumes:
        - name: bpffs
          hostPath:
            path: /sys/fs/bpf
        - name: host
          hostPath:
            path: /
        - name: run
          hostPath:
            path: /run
        - name: cgroup
          hostPath:
            path: /sys/fs/cgroup
        - name: modules
          hostPath:
            path: /lib/modules
        - name: debugfs
          hostPath:
            path: /sys/kernel/debug

root@goblog-6447957f8d-q2g2l:/# curl -sk https://localhost:8443/ | head

<html>
<head>
  <title>Blog template</title>

    <link rel="stylesheet" type="text/css" href="/static/style.css">
    <link rel="alternate" type="application/atom+xml" title="Blog" href="/atom.xml" />
    <meta charset="UTF-8">

</head>
root@goblog-6447957f8d-q2g2l:/# curl http://localhost:8445/metrics | head
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   287  100   287    0     0   196k      0 --:--:-- --:--:-- --:--:--  280k
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0
root@goblog-6447957f8d-q2g2l:/#

logs are available at: https://gist.github.com/prasadkris/8c32517d1625088a9938cde72b99a766

Thanks for trying it! Do you mind sharing which k8s environment are you running on? Is it something self managed or one of the cloud providers? Thanks again!

Hello,
Same issue with podman on windows with following docker-compose.yaml
version: "3.8"

services:

  beyla:
    image: grafana/beyla:latest
    pid: "service:nodejs"
    container:
    cap_add:
      - SYS_ADMIN
    # If using the above capability fails to instrument your service, remove it
    # and uncomment the line below
    #privileged: true
    environment:
      BEYLA_OTEL_INSECURE_SKIP_VERIFY: true
      BEYLA_PRINT_TRACES: true
      #BEYLA_OPEN_PORT defines which app port should be "instrumented"
      BEYLA_OPEN_PORT: 4700
      #BEYLA_PROMETHEUS_PORT: 9090
      #OTEL_EXPORTER_OTLP_ENDPOINT: "http://localhost:4317"
      #OTEL_EXPORTER_OTLP_PROTOCOL: grpc

@yosiasz you need to uncomment the privileged: true line.
Cheers!

@mariomac No go on either settings. cap_add nor privileged

@yosiasz then probably it's because you are running Podman in rootless mode. Can you try configuring it as rootful? For example


Add User Authentication to Your Application (SAP HANA Cloud)

Tutorials: https://developers.sap.com/tutorials/hana-cloud-cap-add-authentication.html
STEP 5: Test.  Item 2.
I ran into issues when I tried to run:
cds bind --exec -- npm start --prefix app
I go the error since I had already run this once before and the app router service was already running on Port 5000:
user: MyHANAApp $ cds bind --exec -- npm start --prefix app
resolving cloud service bindings...
bound auth to Cloud Foundry managed service MyHANAApp-auth:default
bound db to Cloud Foundry managed service MyHANAApp-hdiMyHANAApp-db-deployer-ws-g2jh2:SharedDevKey

start
node<EMAIL_ADDRESS>
#2.0#2023 07 11 11:47:21:258#+00:00#WARNING#/LoggingLibrary################PLAIN##Dynamic log level switching not available#
#2.0#2023 07 11 11:47:22:564#+00:00#INFO#/approuter#####ljy89jk5##########ljy89jk5#PLAIN##Application router version 14.1.2#
#2.0#2023 07 11 11:47:22:567#+00:00#INFO#/Configuration#####ljy89jk8##########ljy89jk8#PLAIN##No COOKIES environment variable#
node:events:491
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use :::5000
at Server.setupListenHandle [as _listen2] (node:net:1463:16)
at listenInCluster (node:net:1511:12)
at Server.listen (node:net:1599:7)
at Object.exports.start (/home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/lib/server.js:46:10)
at /home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/approuter.js:77:15
at /home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/lib/utils/logger.js:35:5
at Function.auditLog.v2 (/home/user/projects/MyHANAApp/app/node_modules/@sap/audit-logging/index.js:26:12)
at Object.module.exports.getAuditLogger (/home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/lib/utils/logger.js:25:16)
at Approuter.start (/home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/approuter.js:72:14)
at Object. (/home/user/projects/MyHANAApp/app/node_modules/@sap/approuter/approuter.js:146:6)
Emitted 'error' event on WebSocketServer instance at:
at Server.emit (node:events:525:35)
at emitErrorNT (node:net:1490:8)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '::',
port: 5000
In order to continue, I had to kill the process.  I had to list the processes and then kill the one listening at 5000.
user: MyHANAApp $ lwctl -c basic-tools ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
user           1  0.0  0.0   3056  2120 ?        Ss   10:05   0:00 /opt/lwexec/bin/server /extbin/control/sidecar.Hz4L3e /opt/lwexec/c
user        2357  0.0  0.0   3168  1348 ?        S    11:02   0:00 server: monitor: node-10/node
user        2358  0.0  0.1<PHONE_NUMBER>8 ?        Ssl  11:02   0:00 /usr/local/bin/node /home/user/.node_modules_global/bin/cds watch -
user        2619  0.0  0.0   3168  1620 ?        S    11:16   0:00 server: monitor: node-10/npm
user        2620  0.0  0.0   2364    20 ?        Ss   11:16   0:00 node-10/node /usr/local/bin/npm start
user        2622  0.0  0.0   3168  1620 ?        S    11:16   0:00 server: monitor: node-10/node
user        2623  0.0  0.1<PHONE_NUMBER>8 ?        Ssl  11:16   0:02 npm start
user        2634  0.0  0.0   2500   604 ?        S    11:16   0:00 sh -c -- node<EMAIL_ADDRESS>user        2635  0.0  0.0   2372   232 ?        S    11:16   0:00 node-10/node<EMAIL_ADDRESS>user        2637  0.0  0.0   3168  1620 ?        S    11:16   0:00 server: monitor: node-10/node
user        2638  0.0  0.2<PHONE_NUMBER>6 ?        Ssl  11:16   0:01 /usr/local/bin/node<EMAIL_ADDRESS>user        3150  0.1  0.2 11432324 93240 ?      Sl   11:45   0:01 /opt/nodejs/node-v16.19.0-linux-x64/bin/node /home/user/.node_modul
user        3244  0.0  0.0   3168  1612 ?        S    11:59   0:00 server: monitor: #_lw_ps
user        3245  0.0  0.0   6772  3000 ?        Rs   11:59   0:00 /bin/ps aux
user: MyHANAApp $ lwctl -c basic-tools kill -9 2635
Then I was able to run that command to start the service at 5000 through the app router:
user: MyHANAApp $ cds bind --exec -- npm start --prefix app
Users might run into this issue.  It would be good to list the work around if this happens.
Thanks,
Jay

Hello Thomas, can you please respond to this user's feedback?

If you already have it running, you need to stop it and run it again. But in this tutorial we've never told you to run it yet.  So I'm assuming you just have it running still from a previous tutorial.


Bug:

PHP Version
7.4, 8.0, 8.1, 8.2
CodeIgniter4 Version
4.4.3
CodeIgniter4 Installation Method
Manual (zip or tar.gz)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
None
What happened?
Ci4 Undefined Variable returns error 500 and stops the script on that line.
Also in ci3, even if these errors are not shown on the screen in production mode, ci3 logs these errors and shows you the errors for you to debug.
Ci4 interrupts and kills the process with a 500 error on undefined variable error.
If you set error_log(0) for ci4 production.php, it will not generate 500 errors, it will continue processing as in natural php, but it will not record any logs for this error.
Steps to Reproduce
I have no idea about this but exceptionHandler should be customizable.
Expected Output
Expected output, in production mode, the native php script continues processing.
Anything else?
I recorded a video for ci3 and ci4. You can understand what I want to explain more clearly by watching the video.
https://www.youtube.com/watch?v=eoKgtHeXohM

It is true that the CI4's  behavior is different from CI3's, but I don't think this is a bug.
See #8350
You can customize Exceptions.
See https://codeigniter4.github.io/CodeIgniter4/extending/core_classes.html#replacing-core-classes

This is not a bug, and we have updated the docs:
See https://codeigniter4.github.io/CodeIgniter4/installation/upgrade_4xx.html#error-handling


Fix unexported field in collateKvRecursive

This PR :

Fixes unexported field in collateKvRecursive
Tests the fix
Updates readme

Coverage increased (+0.2%) to 81.985% when pulling 0a40cd92ea97cb2c6c42017580cb67e45061dd07 on fix-kvsource-exported-fields into b432e312f817c4b3366ae9b17ed97150af88e189 on master.

@emilevauge : Can you have a look at it ?

LGTM, once typos corrected

Coverage increased (+0.2%) to 81.985% when pulling 0267f7aa06e7eb4ec6f507e702a35fa185477692 on fix-kvsource-exported-fields into b432e312f817c4b3366ae9b17ed97150af88e189 on master.


⚠ Jenkins Plugins Artifactory has degraded performance

In 977f693, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1180 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 68d7342 after 12 minutes.


AttributeError: module 'mediapipe.python.solutions.face_mesh' has no attribute 'FACEMESH_CONTOURS'

in findFaceMesh: self.mpDraw.draw_landmarks(img, faceLms, self.mpFaceMesh.FACEMESH_CONTOURS,
AttributeError: module 'mediapipe.python.solutions.face_mesh' has no attribute 'FACEMESH_CONTOURS'
Can't understand, what's wrong, because this attribute exists in mediapipe.python.solutions.face_mesh.

I replaced 'FACEMESH_CONTOURS' with 'FACE_CONNECTIONS'

For godsakes, FACE_CONNECTIONS and FACEMESH_CONTOURS both are not working

Then try the FACEMESH_TESSELATION instead of those things


use random selection of sg list to delete to handle dependencies issues

This PR is related to #326
Instead of attempting to delete a list of SGs within a timer, select a random SG, delete it, and if deletion isn't possible, try another SG until all SGs are deleted

This PR should be closed as this is correctly fixed in https://github.com/outscale/cluster-api-provider-outscale/pull/373


not work on ios devices but work fine on safari

not work on ios devices but work fine on safari:
ERROR: {"__zone_symbol__currentTask":{"type":"microTask","state":"notScheduled","source":"Promise.then","zone":"angular","cancelFn":null,"runCount":0},"line":1278,"column":23,"sourceURL":"http://localhost:8080/Users/simeon/Library/Developer/CoreSimulator/Devices/3DCDACB6-7444-4C28-BB99-C0C158317734/data/Containers/Bundle/Application/2xx/www/assets/js/wfs.js"}
// wfs.js
`
1277:   var typeSupported = {
1278:         mp4: MediaSource.isTypeSupported('video/mp4'),
1279:        // mp2t : wfs.config.enableMP2TPassThrough && MediaSource.isTypeSupported('video/mp2t')
};
`

Media Sourse Extensions are not supported in ios
See link


Fix Android 12 and above app crashes

App didi not crash on android 13 but reader not work at all nothing in console now


bug: unable to execute custom schematic application blueprint

From @Hotell on March 18, 2018 20:3

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ ] devkit
- [x] schematics

Versions
Angular CLI: 1.7.3
Node: 8.10.0
OS: darwin x64

Repro steps
npm i -g @martin_hotell/schematics typescript @angular/cli @angular-devkit/schematics-cli

ng new better-cli --material --collection @martin_hotell/schematics -d

The log given by the failure

Locally installed project schematics works:

And yes my schematics have been generated via @schematic/schematic
https://github.com/Hotell/ng-cli-schematics/blob/master/package.json ✌
Desired functionality
being able to generate new app via custom schematic
Mention any other details that might be useful
There were issues created before which were closed for unknown reasons :) not cool at all 👀
Related:

https://github.com/angular/devkit/issues/351
https://github.com/angular/devkit/issues/322

Copied from original issue: angular/devkit#528

The referenced package targets 1.x of the Angular CLI.  Unfortunately, the schematics are not supported on newer versions of the CLI (currently 9.x).  Angular CLI 1.x is also no longer supported.  As a result this issue cannot be further investigated.  If anyone is still encountering problems with the latest version of the CLI, please open a new issue with updated information.


Fix goreleaser and prepare to publish to Hashicorp Registry

#35  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aschepis and the rest of your teammates on  Graphite


Logout while locked

I used to be able to log out of an account while the current account is locked, i.e. without first putting in the password for the current account. Now, I can only log out after unlocking the current account. This is a minor issue, but the old way makes sense and is better for users.
v3.22.1 on Chrome

@edu-stx could removing this be the problem here?
https://github.com/hirosystems/stacks-wallet-web/pull/2786/commits/ce7ad3caa814abe7639030ebce44b3fbd90f74cb

It appears the sign out drawer is not popping up ...instead the password field becomes focused.

I actually think this PR on dev already fixed the issue: https://github.com/hirosystems/stacks-wallet-web/pull/2785

I am going to close this and link to the merged PR that fixed it. It should be in the next release, thx @obycode for reporting.


Read-only columns visualization

When entire resultset is read-only we should show a lock icon in the top-left corner.
Otherwise we should show yellow mark on a particular read-only columns.

Verified


feat: Introduce PolicySimulator

PiperOrigin-RevId: 549001229
b/291748771

This package has been released and is available on packagist:

https://packagist.org/packages/google/cloud-policysimulator
https://github.com/googleapis/google-cloud-php-policysimulator


After running the demo-app all tasks start at 0.

I am not sure if it is a configuration issue or what, but all the tasks start at 0 and end based on the date difference.
please see attached file below for the image.

Yeah this is related to the scale options that is passed start and end dates. It will default to today plus 7 days if no scale is passed. However I am looking at generating the scale based on the tasks that are passed and removing the requirement for having to have to set the scale manually.

This is now in 1.1.0-alpha.6 ng2-gantt


Disable difficulty

Describe your problem here.
Can i disable a difficulty for just 1 week? I'm porting V.S. Matt btw
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No, i didn't

just make all the charts the same or delete the code for easy and normal and leave the one difficulty u want

@DEV-idiotXD The week 1 is Easy, Normal, Hard and Old and the week 2 is Easy, Normal and Hard

No, but you can make all charts the same.

@ShadowMario What do you mean?

@ShadowMario What do you mean?

take a hint?
get the chart for the difficulty u want then copy and paste it twice then just rename it

Ok


honor stale:ok in second search step

Include 'stale' Option in second search step.

My bad! Looks like I made a mistake here; thanks for the fix.

c7526df1ba07cac8ba9321ca20f42ab1d279ce6d


java.lang.UnsatisfiedLinkError: no netty-transport-native-epoll in java.library.path

when i try to run demo in centos6，
‘java.lang.UnsatisfiedLinkError: no netty-transport-native-epoll in java.library.path’ show up，
my run command is：/usr/local/jdk1.6.0_45/bin/java -Xms1536m -Xmx1536m -Xss1M -XX:+UseParallelGC -cp /root/demo-netty/demo-1.0.0-SNAPSHOT.jar:/root/demo-netty/lib/* com.corundumstudio.socketio.demo.ChatLauncher。 all jars require is in /root/demo-netty/lib/。my linux version is 2.6.32，thx

Add netty-transport-native-epoll  dependency to your path

Already added.Still doesn't work

you must specify the proper classifier for the dependency .see detail at http://netty.io/wiki/native-transports.html


ConsolerProgressBar not found.

Hi!
I tried to excute php artisan db:seed
PHP Fatal error:  Trait 'ViKon\Utilities\ConsoleProgressbar' not found in /home/valkyrie/phpcatalogs/project-odin/odin-server/database/seeds/ApplicantsSeeder.php on line 8

  [Symfony\Component\Debug\Exception\FatalErrorException]
  Trait 'ViKon\Utilities\ConsoleProgressbar' not found

This error shows. Any help.
Thanks!

Hi!
I fixed this issue, so now should work correctly. If any problem occurs please feel free to contact.

Hi! Thanks for the fix. :)


Tutorial - width: 100% and height: 100% has no effect

I am going through the tutorial for the chessboard, at the part where flexbox is introduced and seems like the Board's width: 100%; and height: 100%; has no effect, because <div id="root"> has no preset width or height.

Proposed fix: change the board's style from
width: '100%',
height: '100%'

to
width: '400px',
height: '400px'

This still works with the flexbox implementation, and makes it less confusing for beginners who might run into the same trouble (like me).
Here's what it looks like:

See #422. PR welcome.

Cool, I'll see if I can make a PR after I finish the tutorial. The main grunt of the work would be to refresh the images I think.

still an issue

@mdramos PR still welcome.

This is a common issue with code that may or may not assume you're using quirks-mode. The issue is that with <DOCTYPE html>, the height of the 'html' and 'body' aren't 100% so 'div' heights end up being 0. You can fix it by removing the code or explicitly setting 'html' and 'body' to 100% height.


Missing Model Error During Inference on Single Node

Problem
I'm encountering a missing model error when attempting to run the model on inference with a single node.
Current Situation

Trying to run inference on one node
Consistently getting a missing model error
No existing script for downloading the models automatically

Questions

Do I need to download the models manually?
Is there a script or process for automatically downloading the required models?

Sorry, you need download the models manually.
First, you need to download checkpoint including diffusion model, vae and text encoder.
Then, modify --model_path, --text_encoder_name_1 and --ae_path the path in script.

Yes got it, thanks

I see you added it now already https://github.com/PKU-YuanGroup/Open-Sora-Plan/commit/41e81de7cacc4770f1fc648d93ffd2973c96e3e0#diff-ac6ac22c6fc92efc50b92cc60e88898025b0f8fb3b06dee1b0f4e582cdaf0d4eR127


Bounty Board Claim button not correctly linking to the create bounty

Describe the bug
Clicking the claim button on a bounty directs you to http://https://bountyboard.bankless.community/
To Reproduce
Steps to reproduce the behavior:
http://https://bountyboard.bankless.community/
Click an open bounty
The claim link is populated as: https://bountyboard.bankless.community/
Clicking takes you to the top of the page.
Expected behavior
Click 'Claim' and takes you to the bounty.
Screenshots
https://app.usebubbles.com/4juX64EwSMSBMVtaaKTXNH/bankless-dao-bounty-board-bug-report-can-t-claim-task

@Behold3th are you able to take a look at this one?

@Behold3th are you able to take a look at this one?

can do!

Picking this one up. To give context this was an intentional choice as we wanted users to claim bounties on the Discord, as front-end claiming is only unblocked by oauth2 integration. There are a few solutions - remove the claim button and leave a helpful message such as "Claim on the discord" - or have the button deep link to the posted bounty. The second option is preferred and what I will implement

@Behold3th can you confirm if this is sorted please?

Yes, this has been sorted


the shoot-flux extension uses latest tag but it does not exist

there is no latest tag for the image: https://github.com/stackitcloud/gardener-extension-shoot-flux/pkgs/container/gardener-extension-shoot-flux/versions
from what i can tell everywhere else its already using the version: https://github.com/search?q=repo%3AYAKEcloud%2Fyake 0.12.0&type=code
but i might be missing something.
the rawChart is still correct: https://github.com/stackitcloud/gardener-extension-shoot-flux/blob/v0.12.0/deploy/extension/base/controller-registration.yaml#L7

The version for this extension is set and updated here: https://github.com/YAKEcloud/yake/blob/09252775cfcfb0447f658212dd5fd0ba050cb313/configuration/configuration/templates/extensions.yaml#L234
The helmcharts folder is just an "import" of upstream charts and we do not modify it directly. So even if you tried this change and it did fix your problem it is still not the right way to fix the problem in yake. If this is even related to a problem that you experience in your setup, I'd need more information to help you fix it.

Ok, that makes sense.
Yes we actually have to set the tag in extension-values because it tries to pull latest otherwise:
    shoot-flux:
      enabled: true
      globallyEnabled: true
      values:
        image:
          tag: v0.12.0

So the right thing to do would be to change it here in upstream?
https://github.com/stackitcloud/gardener-extension-shoot-flux/blob/504fad5002d5f81f401d0f145b376e1d18549b26/deploy/extension/base/controller-registration.yaml#L10


Remove usage of content_tag and remote attr in bootstrap themes

Hello! This PR fixes a tiny issue on the bootstrap themed _page.html.* partial templates with how content_tag differs from link_to with regards to passing in remote: remote.
By creating an anchor tag  using content_tag :a,  remote: remote, ... this actually generates the following html with a "remote=" attribute like so:
1

Which is technically not a valid html attribute for the anchor tag. Also probably not what we intended as we wanted a data-remote attr instead.
Instead if we just use link_to over a content_tag this gets our desired behaviour we want:
1

(looks like bootstrap 2/3 slim templates already do something very similar to my change so didn't include these)

Updated PR to use suggestion of just wrapping remote with data hash instead :+1:

looks great. Thanks!


useRealmCreate hook

realm.write(() => {
  realm.create('Person', {_id: PERSON_ID, name: name, age: 25});
});

it would be nice to pack that into useRealmCreate custom hook

reverting realm


HTTPCLIENT-2337: Sanitize X500Principal Logging in ClientTlsStrategy classes

This PR addresses HTTPCLIENT-2337, which involves potentially unsafe logging of X500Principal in SSLConnectionSocketFactory. The issue is caused by control characters in the X500Principal being logged without sanitization, which could interfere with log readability.

@arturobernalg I think we have kind of decided to not do it, but if no one objects I see no reason to not merge this change-set

please @garydgregory  do another pass.

@arturobernalg SSLConnectionSocketFactory has been deprecated in favor of DefaultClientTlsStrategy. I really think your time and efforts could be better spent elsewhere but if you really want to do it please move all these changes from SSLConnectionSocketFactory to AbstractClientTlsStrategy.

@arturobernalg SSLConnectionSocketFactory has been deprecated in favor of DefaultClientTlsStrategy. I really think your time and efforts could be better spent elsewhere but if you really want to do it please move all these changes from SSLConnectionSocketFactory to AbstractClientTlsStrategy.

@ok2c
Please check again.
Thank you.

Unrelated random failure:
Error:  Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.046 s <<< FAILURE! - in org.apache.hc.client5.testing.sync.TestFutureRequestExecutionService
Error:  org.apache.hc.client5.testing.sync.TestFutureRequestExecutionService.shouldCancel  Time elapsed: 0.007 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: Expected java.lang.Exception to be thrown, but nothing was thrown.
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
	at org.junit.jupiter.api.AssertThrows.assertThrows(AssertThrows.java:73)
	at org.junit.jupiter.api.AssertThrows.assertThrows(AssertThrows.java:35)
	at org.junit.jupiter.api.Assertions.assertThrows(Assertions.java:3128)
	at org.apache.hc.client5.testing.sync.TestFutureRequestExecutionService.shouldCancel(TestFutureRequestExecutionService.java:117)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at java.util.ArrayList.forEach(ArrayList.java:1259)
	at java.util.ArrayList.forEach(ArrayList.java:1259)


TIME macro not working

When using time in ALIVE, it only returns the result of the function. Using it in the terminal it shows the execution time and other informations

I'll fix this when I get a chance, hopefully this weekend. apparently time prints to trace-output instead of the standard streams. need to redirect that output to the display.


[HUDI-7438][Test][DNM] Fix Azure CI report check with new issue comments

Change Logs
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Test

Tested with
const { status2, message2, azureRunLink2 } = await checkAzureCiStatus({
              github,
              context,
              prNumber: 10744,
              latestCommitHash: '2c903b39d758f9ee365ad93d6dd3b2ff745eee74'
            });

            const { status3, message3, azureRunLink3 } = await checkAzureCiStatus({
              github,
              context,
              prNumber: 10594,
              latestCommitHash: '9c7fb2754efac58066e47e9af0312c4cfc8fa78f'
            });


Release/v0.0.4

Coverage report
 Click to see where and how coverage changed
FileStatementsMissingCoverageCoverage(new stmts)Lines missing

  server/lomas_server
  constants.py

  server/lomas_server/dp_queries/dp_libraries
  opendp.py
146-152, 156-161
  server/lomas_server/private_dataset
  utils.py

  server/lomas_server/tests
  test_api.py

  server/lomas_server/utils
  utils.py

Project Total

This report was generated by python-coverage-comment-action


Update akka-actor, akka-persistence, ... to 2.6.9

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-persistence
com.typesafe.akka:akka-slf4j
com.typesafe.akka:akka-stream-testkit
com.typesafe.akka:akka-testkit

from 2.6.7 to 2.6.9.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch

Closing in favor of #484.


Unexpected error -10004 when creating&deleting files

Related to #215 and #261
I build a testbench to evaluate spiffs and other flash filesystems for use with a large (64MB) NOR flash.
After a promising start, I now have a testcase that reliably crashes with code -10004 (some changes also resulted in code -10011). Wait for it to run until the end - it gets slow as the flash fills up. The crash is in the last loop.
Here's my code:
spiffs-testbench-crash10004.zip
What I tried and lead to nothing:

replace mmapped file with a simple calloc()'d buffer - exact same result
put volatile where i thought it might have some effect on caching
turn off SPIFFS caches using the config file

I run this on a regular x86_64 desktop PC with Linux.
I can reproduce it 100% - if you can't, then it might really be some strange machine specific shenanigans with caching. (or something supernatural :ghost:)

In spiffs_config.h, did you make sure these types are big enough:
// Block index type. Make sure the size of this type can hold
// the highest number of all blocks - i.e. spiffs_file_system_size / log_block_size
typedef u16_t spiffs_block_ix;
// Page index type. Make sure the size of this type can hold
// the highest page number of all pages - i.e. spiffs_file_system_size / log_page_size
typedef u16_t spiffs_page_ix;
// Object id type - most significant bit is reserved for index flag. Make sure the
// size of this type can hold the highest object id on a full system,
// i.e. 2 + (spiffs_file_system_size / (2*log_page_size))*2
typedef u16_t spiffs_obj_id;
// Object span index type. Make sure the size of this type can
// hold the largest possible span index on the system -
// i.e. (spiffs_file_system_size / log_page_size) - 1
typedef u16_t spiffs_span_ix;

You are correct, that was indeed the case.
I think SPIFFS_mount() could easily catch this - compare the values from spiffs_config with (1ULL << sizeof(spiffs_whatever_ix) * 8ULL) - 1ULL


Project Settings changed and movement of trademarked textures

In First commit:
Starting to use the Open Brush name.

Updating the project settings with a placeholder logo, updated the project name.
Used OpenBrush naming in App.cs.

Removing Trademarks
I am hoping the trademarks can just be dropped in with replacements and the materials using them will be updated.

Moved trademarked icons from Assets/Resources/Icons to Assets/Resources/Icons/Trademarked
Moved trademarked textures from Assets/Textures to Assets/Textures/Trademarked

Note that we should be able to use some of those trademarks, as long as we adhere to the branding guidelines.
For instance, we would want to keep the Google Drive icon to denote drive access.

Note that we should be able to use some of those trademarks, as long as we adhere to the branding guidelines.
For instance, we would want to keep the Google Drive icon to denote drive access.

Added Second commit: Rebranding

Added new logos and icons made by SiMonk0.
Replaced the Trademarked logos with the new ones, kept copies just incase.
Used the GUI to regenerate the atlas with the new images.
Updated the prefabs to use new icons.
Removed .vscode and added it to gitignore.
Removed the Google Copyright
Added Trello and a Gdoc to the README

Added Second commit: Rebranding

Added new logos and icons made by SiMonk0.
Replaced the Trademarked logos with the new ones, kept copies just incase.
Used the GUI to regenerate the atlas with the new images.
Updated the prefabs to use new icons.
Removed .vscode and added it to gitignore.
Removed the Google Copyright
Added Trello and a Gdoc to the README

**Added Second commit: **

Added new logos and icons made by SiMonk0.
Replaced the Trademarked logos with the new ones
Used the GUI to regenerate the atlas with the new images.
Removed .vscode and added it to gitignore.
Removed the Google Copyright

**Added Second commit: **

Added new logos and icons made by SiMonk0.
Replaced the Trademarked logos with the new ones
Used the GUI to regenerate the atlas with the new images.
Removed .vscode and added it to gitignore.
Removed the Google Copyright

Thanks!

Thanks!


[FEATURE] Add a progress spinner

Due to the design of our current codebase, a progress bar would be quite unfeasible as we'd need to get and pass the file size down a multitude of functions. I like how our codebase stands currently, and I don't think this one feature warrants that amount of effort/refactoring.
With that, I've decided to implement a progress spinner. It's not as descriptive as a bar, but at least it lets the user know that things are still happening. I feel like this is a good compromise between the two.
This is related to #102.
(despite it not being a progress bar, I think it adds a nice touch for larger files/slow computers)
This also adds the visual feature to dexios-core, and that will pull in indicatif and display the spinner on stream encrypt/decrypt automatically (when the encrypt/decrypt_file() functions are used).

Due to the design of our current codebase, a progress bar would be quite unfeasible as we'd need to get and pass the file size down a multitude of functions.

When we finish domain and start working on cli, we will be able to implement a normal progress indicator which will be controlled by cli and not by core or domain. But you've come up with a great solution to start with!)

Due to the design of our current codebase, a progress bar would be quite unfeasible as we'd need to get and pass the file size down a multitude of functions.

When we finish domain and start working on cli, we will be able to implement a normal progress indicator which will be controlled by cli and not by core or domain. But you've come up with a great solution to start with!)

Thank you! I had to work with what I could, and I think this is fine for now. I'm not too sure how the cli application is going to be able to update the progress bar on every block - I've thought about it since the migration over to core and none of my solutions are viable.
I'm sure we'll figure it out though, and this will be fine for now :)


No results when running in server mode, StatusbarMessage error?

When listening in server mode, I don't get any output from asn.

[2021-04-11 18:15:45]   INFO    ASN Lookup Server listening on <IP_ADDRESS>:49200
[2021-04-11 18:15:47]   INFO    Incoming connection by client <IP_ADDRESS>
[2021-04-11 18:15:47]  STARTED  Lookup request by client <IP_ADDRESS> for target github.com (Request ID: 817759845)
────────────────────────────────────────────────────────────
WARNING
No IPQualityScore token found, so disabling in-depth threat
analysis and IP reputation lookups. Please visit
https://github.com/nitefood/asn#ip-reputation-api-token
for instructions on how to enable it.
────────────────────────────────────────────────────────────
./asn: line 1389: $max_msg_size: substring expression < 0
[2021-04-11 18:15:48] COMPLETED Lookup request by client <IP_ADDRESS> for target github.com (Request ID: 817759845)

./asn: line 1389: $max_msg_size: substring expression < 0
https://github.com/nitefood/asn/blob/d280c0aeaa1edb032e3f5c1fae88cbf42282d637/asn#L1387
It looks like terminal_width is 0 at this point and thus  max_msg_size = -23

The problem is with running asn -l in the foreground. It picks up the $TERM, and thus IS_HEADLESS=false
Perhaps -l should set IS_HEADLESS=true, instead of looking for TERM=dumb?

Thanks for the analysis, this was broken in commit 7a920ad, when I changed the subshell detecting logic. What is happening is the subshell spawned by the ncat connection handler isn't getting it's $TERM variable set to "dumb" - which it instead does when launched through systemd.
In order to fix it, can you confirm that by manually setting the terminal on line 1907 from this:
		INTERNAL_CONNHANDLER_CHILD=true INTERNAL_ASNSERVER_CONNHANDLER=false "$0" "$host" |

to this:
		INTERNAL_CONNHANDLER_CHILD=true INTERNAL_ASNSERVER_CONNHANDLER=false TERM=dumb "$0" "$host" |

fixes the issue?
Thanks.

Awesome thanks. that worked


flyway: SQL SERVER: Unable to USE DDL and DML in same migration

Which version and edition of Flyway are you using?
Flyway 6.4.3
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
even with flyway 6.4.3 I am unable to use ddl and dml in same migration for sql server
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
SQL SERVER 2016
Which operating system are you using?
Windows
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
flyway: SQL SERVER: Unable to USE DDL and DML (create table) in same migration, the dml insert statement always shows Invalid column name,
DDL - Create table
DML - Insert statement
Both in same migration sql file
Even when I use Begin Transaction and Commit Transaction for creating a table, the insert statement fails saying Invalid column name.
What did you expect to see?
DDL and DML should execute successfully in the same migration
What did you see instead?
SQL State  : S0001
Error Code : 207
Message    : Invalid column name 'column name'

There's no reason why you can't mix DDL and DML. Could you share the script you're running? (If not, you could mail to<EMAIL_ADDRESS>

Hi Juliahayward,
Please find the below script which i am trying to run from fylway
USE [TEST_DB]
GO
delete from tablea where columna= 15
CREATE TABLE [dbo].test_type(
TYPE_ID [int] NOT NULL,
DESCRIPTION varchar NULL,
CONSTRAINT [T_TYPE_PK] PRIMARY KEY CLUSTERED
(
[TYPE_ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
Insert into test_type
(TYPE_ID, DESCRIPTION)
Values
(1, 'FUNCATIONAL');
Insert into test_type
(TYPE_ID, DESCRIPTION)
Values
(2, 'REGRESSION');
ALTER TABLE COLUMN_B
ADD TYPE_ID VARCHAR(16) NULL --Or NOT NULL.
DEFAULT (1)--Optional Default-Constraint.
WITH VALUES;
UPDATE COLUMN_B set TYPE_ID=TYPE_ID+','+'2' Where column_id=3;
GO

Closing the issue, there seems to be something else going on. Sorry.


Async dataloader

This branch updates promises with an asynchronous resolution and including a provisional dataloader
This PR is still WIP
Things to do before merging:

[x] Have all the tests running successfully
[x] Port Promise.all
[ ] Add promise error tracking
[ ] Improve Dataloader testing
[ ] Create a list of breaking changes
[ ] Investigate into Cython performance
[ ] Update Readme's with the new API usage

Coverage decreased (-11.3%) to 88.322% when pulling<PHONE_NUMBER>b4d70a30c278ba6007bd1ff5505251 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 11ff6835f85e019b20a5bd470ae2761b2d846b5f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 11ff6835f85e019b20a5bd470ae2761b2d846b5f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 11ff6835f85e019b20a5bd470ae2761b2d846b5f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 11ff6835f85e019b20a5bd470ae2761b2d846b5f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 8209d7256057c916daf891a8a149ece919db172e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 8209d7256057c916daf891a8a149ece919db172e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 8209d7256057c916daf891a8a149ece919db172e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.3%) to 89.249% when pulling 8209d7256057c916daf891a8a149ece919db172e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.2%) to 89.384% when pulling 2c9ca1830b8e006c1e87667acc1eb5f9d74364e0 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.2%) to 89.384% when pulling 2c9ca1830b8e006c1e87667acc1eb5f9d74364e0 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-10.2%) to 89.384% when pulling 2c9ca1830b8e006c1e87667acc1eb5f9d74364e0 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-8.8%) to 90.823% when pulling efc126446bc8ed8f8c05481194ec53b27cfec021 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-8.7%) to 90.852% when pulling b21d6268c774582195a294812c6f4837bff06fa5 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-7.5%) to 92.068% when pulling 01e71ef46b118ce1dfa3bd7bdbbe4d5299bccb81 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-7.5%) to 92.12% when pulling 93fcf22d048fc553153b12952678f161c377c26f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.683% when pulling 76ac194fac06a3098487a4302328d374c74effc3 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.683% when pulling 76ac194fac06a3098487a4302328d374c74effc3 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.683% when pulling 76ac194fac06a3098487a4302328d374c74effc3 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.683% when pulling 76ac194fac06a3098487a4302328d374c74effc3 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-7.08%) to 92.518% when pulling 6c2dadcd5647ce90413c3fc798bdc0a184909a79 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.714% when pulling b6275007799a2bddb1487a8da72ec54c7df1618f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.714% when pulling b6275007799a2bddb1487a8da72ec54c7df1618f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.714% when pulling b6275007799a2bddb1487a8da72ec54c7df1618f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.714% when pulling b6275007799a2bddb1487a8da72ec54c7df1618f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.714% when pulling b6275007799a2bddb1487a8da72ec54c7df1618f on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.8%) to 92.756% when pulling a63564fdf27db8ec1d9169c1f6dc60f94d2f3c57 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 6e26f0ee065cb4a6bc6b96d2d9665d4cb2ac9b3e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 6e26f0ee065cb4a6bc6b96d2d9665d4cb2ac9b3e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 6e26f0ee065cb4a6bc6b96d2d9665d4cb2ac9b3e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 1f103fdda286b077d95af2a626a4ac898dcd45b4 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 1f103fdda286b077d95af2a626a4ac898dcd45b4 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.9%) to 92.745% when pulling 1f103fdda286b077d95af2a626a4ac898dcd45b4 on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Coverage decreased (-6.8%) to 92.766% when pulling f98004e13ede45e3e462b3957e198ae63998273e on async-dataloader into 9539d3bbdd280d0c4f57f89797858121eeceb996 on master.

Hi @gappleto97!
I just added a feature so you can change the scheduler quite easily:
from promise import set_default_scheduler, ThreadScheduler

set_default_scheduler(ThreadScheduler())

Hope this helps! :)

Unfortunately not. It looks like the problem is stemming from promise.Promise._resolve_from_executor()
That method appears to ignore the scheduler logic entirely, and just make a direct call.

Hi @gappleto97, that is the desired behavior.
The Promise executor should always be called in the same thread where you are creating the promise, is the then method the one that should be resolved off the thread.
You can imitate this behavior in JS as well:
promise = new Promise(function (resolve, reject) {
    // This is executed immediately
    console.log("RESOLVED"));
    resolve(true);
})
console.log("AFTER PROMISE")

(this should output "RESOLVED" and then "AFTER PROMISE")
However, is the then execution is the one that is asynchronous:
p = new Promise(function (resolve, reject) {
    // This is executed immediately
    console.log("RESOLVED");
    resolve(true);
}).then(function(resolved) {
    // This is executed in a new thread after the call stack is empty
    console.log("CALLED THEN", resolved);
});
console.log("AFTER PROMISE");

(this should output ("RESOLVED", "AFTER PROMISE", "CALLED THEN true")).

Some other projects, for achieve an "async" promise execution (not resolution), use the trick of creating a resolved promise and deferring the execution on the promise resolution:
resolvedPromise = Promise.resolve();
resolvedPromise.then(function() {
// This is called async
});

https://github.com/facebook/dataloader/blob/master/src/index.js#L210
https://github.com/apollographql/graphql-server/blob/master/packages/graphql-server-core/src/runQuery.ts#L55

Huh. That's surprising to me. I guess I never noticed because you can't sleep in JavaScript. On the other hand, now I don't know quite how to proceed.
Would you be willing to add a keyword for using the scheduler in this case? Another option would be to have a single modifier inheritor (ScheduledPromise) where that one method is replaced.

A motivation to do this in that making it asynchronous in JavaScript is truly easy with a setTimeout, but there is no equivalent tool here

So I guess what I'm asking for is the ability to do:
new Promise((accept, reject)=>{
    setTimeout(()=>{
        accept(1);
    }, 2000);
});

In your library this is currently not possible.

Hi @gappleto97,
Something similar could be implemented with python promise :)
from threading import Timer
def set_timeout(fn, time):
    timer = Timer(time, fn)
    timer.start()

p = Promise(lambda accept, reject: set_timeout(lambda: accept(1), 2.0))

Does that work for your case?

It works, but it adds exactly the sort of overhead you were looking to avoid with this. At that point you might as well just start a thread in the first place.

I understand your frustration here, but I think is worth to keep the current python closer to the current Promise specifications.
I think, for your case, might be worth for you to extend the current promise implementation enabling this behavior:
from threading import Thread

class ThreadedPromise(Promise):
    def __init__(self, executor):
        def threaded_executor(resolve, reject):
            thread = Thread(target=executor, args=(resolve, reject))
            thread.start()
        super(ThreadedPromise, self).__init__(threaded_executor)

t = ThreadedPromise(lambda resolve, reject: resolve(1))


Experimental/shuffle job parts

Closing, since this is still very experimental.  It's here for record keeping of what we've experimented with.


Set cwd to project-root even if opened file is inside .git/ (#110)

https://github.com/airblade/vim-rooter/blob/d64f3e04df9914e784508019a1a1f291cbb40bd4/plugin/rooter.vim#L88
The function finddir returns the path of the first found match with the given pattern. If the pattern is part of the literal fd_dir_escaped-string then finddir returns the pattern as the root. This means if .git/ is the pattern and fd_dir_escaped is /home/user/project/.git/file then finddir will return /home/user/project/.git. This PR makes sure that /home/user/project is the actual result.
Fixes #110

I did some other bold changes. Maybe I am totally off but can't the function FindAncestor be greatly simplified? If I understand it correct the functions finddir and findfile can only return three results:

Empty String if pattern couldn't be found in path
Pattern itself if its in the cwd
Absolute Path like path/pattern

In cases 1 and 2 we don't want to change the cwd. In case 3 we want to return the path without the pattern.
The final change I did was essentially replacing all the code which computed the path which should be returned with a transformation of the path to the desired result:

empty string
pattern --> empty string
path/pattern --> path

I forgot a fourth case were the path returned by finddir and findfile can be relative. I fixed it in the last commit.

The only concern I have is when we remove the pattern from match:
let match = substitute(match, a:pattern."$", "", "")

If pattern is a directory it has a slash at the end as a file separator. If it is used on an OS which doesn't use slashes as separators can it be that it won't be able to remove the pattern from match because match might have a different separator at the end?

No longer needed as of 9b1fc7a.


Declarative bulk subscribe support

Signed-off-by: Deepanshu Agarwal<EMAIL_ADDRESS>Description

This piece adds Declarative Support to Bulk Subscribe. It also changes programmatic way, by bringing bulkSubscribe outside metadata, like this(as per consensus reached in #5499 ):
apiVersion: dapr.io/v1alpha1
kind: Subscription
metadata:
  name: orders-subscription-mqtt
spec:
  topic: orders
  route: /orders
  pubsubname: mqtt-pubsub
  bulkSubscribe: (optional)
    enabled: "true" (required, if bulkSubscribe block given)
    maxMessagesCount: "4" (optional)
    maxAwaitDurationMs: "10000" (optional)
  metadata:
    rawPayload: "true"

Please note that I haven't put any defaults for maxMessagesCount and maxAwaitDurationMs in runtime, as wanted to leave these defaults on the component side. If we intend to introduce  common defaults across components - even for that, defaults should ideally go in contrib repo.
Issue reference

Please reference the issue this PR will close: #5499
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[x] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Overall LGTM. Just minor comments to naming.

I just realized that I had forgot to raise corresponding PR in components-contrib to take MaxMessagesCount and MaxAwaitDurationMs. I have raised https://github.com/dapr/components-contrib/pull/2405 to take care of that, and this PR can be ONLY AFTER THAT PR IS MERGED. Also, I will have to remove replace from go.mod here.

@ItalyPaleAle @artursouza Please re-review. Whenever I request re-review from someone, it automatically removes re-review from others. So, putting a comment.

Overall LGTM. Just minor comments to naming.

I just realized that I had forgot to raise corresponding PR in components-contrib to take MaxMessagesCount and MaxAwaitDurationMs till component. I have raised dapr/components-contrib#2405 to take care of that, and this PR can be merged ONLY AFTER THAT PR IS MERGED. Also, I will have to remove replace from go.mod here.

https://github.com/dapr/components-contrib/pull/2405 is now merged. So, this PR can be in now, once it is Approved.

/ok-to-test


Macro output appears to late

I am using Jupyterhub with IJulia. Within such a notebook, e.g. the output of macro @timev does not always appear before the value of the cell.
For example:
Input:
@timev 2+3

Output:
  0.000002 seconds (4 allocations: 160 bytes)
Out[38]:
5
elapsed time (ns): 1873
bytes allocated:   160
pool allocs:       4

All four lines produced by @timev should appear before the actual output 5.
Within the code generated by the macro timev, println is indeed called before returning the value to the caller. However, Julia's I/O is often a bit delayed (it seems to be handled by a separate task), and so it seems to appear on stdout too late.
This could e.g. be fixed within timev by first outputting into a buffer, converting this to a string, and then outputting the string -- string output seems to have less delay than other output. However, I think this should be fixed somewhere else instead, probably here in IJulia. (The error does not happen in the REPL.) Maybe a flush or a taskwait are missing somewhere, but this is just a wild guess.

Dup of #342


Issue #2204: support v2 namespace in cpp client

Motivation
In pulsar-client-cpp, TopicName support V2 type, and contains method isV2Topic(), but NamespaceName not support it.
We need to add support for NamespaceName to make it align with java client.
Modifications

add v2 support in NamespaceName
add test case for it

Result
old behaviour not changed.

retest this please

retest this please

merged as c34ad4 to branch-2.1


Data leak between visualisations?

Hi,
Really cool package, it is exactly what I have been looking for! I noticed some "odd behaviour" when using your package. I am completely new to it, so it is probably my own understanding rather than a bug.
If I create a notebook and have two cells:
import ipyvolume as ipv
import numpy as np
x, y, z = np.random.random((3, 10000))
ipv.quickscatter(x, y, z, size=1, marker="sphere")

then:
import numpy as np
import ipyvolume as ipv
V = np.zeros((128,128,128)) # our 3d array
# outer box
V[30:-30,30:-30,30:-30] = 0.75
V[35:-35,35:-35,35:-35] = 0.0
# inner box
V[50:-50,50:-50,50:-50] = 0.25
V[55:-55,55:-55,55:-55] = 0.0
ipv.volshow(V, level=[0.25, 0.75], opacity=0.03, level_width=0.1, data_min=0, data_max=1)

The scatter will appear on top of my volume. If I reverse the cell order this doesn't occur. I am guessing that the quick* functions create a canvas, while the "normal" function (volshow) adds to existing canvas if one is available?
Is there a piece of code I can use to specificy which canvas or a way to create a new empty canvas?
Cheers,
Duncan

after a bit of digging around I see in the code that I can call:
ipv.figure()

Which created a new 3d canvas.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[1.0] fix copy file range large files

Cherry-picks commits from continuity:

containerd/continuity@afba265
containerd/continuity@a3fa14c

Codecov Report

Merging #2355 into release/1.0 will increase coverage by 0.03%.
The diff coverage is 73.33%.

@@              Coverage Diff               @@
##           release/1.0   #2355      +/-   ##
==============================================
+ Coverage        50.86%   50.9%   +0.03%
==============================================
  Files               81      81
  Lines             7189    7194       +5
==============================================
+ Hits              3657    3662       +5
  Misses            2832    2832
  Partials           700     700

Flag
Coverage Δ

#linux
50.9% <73.33%> (+0.03%)
:arrow_up:

Impacted Files
Coverage Δ

fs/copy_linux.go
44.68% <73.33%> (+6.58%)
:arrow_up:

Continue to review full report at Codecov.

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


chore: support emoji for mkdocs

Fix the emoji of mkdocs.
@ito-san has fixed this before, but still needs to sync with autoware-documentation, or the bot will complain.
I've updated autoware-documentation, and now try to sync again.

@evshary Thanks! Applied in https://github.com/autowarefoundation/open-ad-kit-docs/pull/35.

Oh, thank you @kenji-miyake
I'll close the PR.


Non-breaking change* from UK spellings to US

Fixes issue mentioned in PR #8285.
Note: By mistake, this is currently dependent on #8285
Objective
Ensure consistency in the spelling of the documentation.
Exceptions:
crates/bevy_mikktspace/src/generated.rs - Has not been changed from licence to license as it is part of a licensing agreement.
Maybe for further consistency, https://github.com/bevyengine/bevy-website should also be given a look.
Solution
Changed the spelling of the current words (UK/CN/AU -> US) :
cancelled -> canceled (Breaking API changes in #8285)
behaviour -> behavior (Breaking API changes in #8285)
neighbour -> neighbor
grey -> gray
recognise -> recognize
centre -> center
metres -> meters
colour -> color
Update engine_style_guide.md to include spelling guidelines

Changelog
Changed UK spellings in documentation to US
Migration Guide
Non-breaking changes*
* If merged after #8285

Marking this as controversial due to updating project guidelines. To make sure this is a direction we want to go in.

I'm opposed to enforcing this without an automated way to check this.

I'm opposed to enforcing this without an automated way to check this.

@alice-i-cecile Working on it! #https://github.com/BlackPhlox/bevy/pull/1

If we can get this in CI without massive false positives I'm on board with it for consistency :) Ideally we're also checking type and method names too?
I think that rather than using a generic spellchecker, we should probably consider a blacklist approach? Software dev always has a ton of "unusual" words, and game dev is even worse for that.

@alice-i-cecile Agreed! I think it might create too much friction for everyone involved if it is a whitelist. So I think we should wait until blacklist functionality has been developed for check-spelling, see check-spelling - Feature : Dictionary deltas. So currently I'm just testing by compiling my own whitelist just to see if it would work from a CI standpoint.

@alice-i-cecile I've updated my opinion on this and reflected my concerns in #8324. I think we should continue the discussion to that pr instead. Maybe then I should remove engine_style_guide.md changes from this pr, so this pr is trivial instead of marked controversial and do the changes in #8324 instead?

Agreed on moving that, and removing the style guide changes :)

Canadian spelling are obviously the superior option, but I definitely think we should standardize, even if informally.
Merging now; we can continue the discussion on automated tools to enforce this.

I don't agree that style guide changes need to be accompanied by automated enforcement. They're just guidelines, and I think that suggesting a standard style is better than being silent on it. Plus, international spellings will most likely slip past code review in the future, so having this in the style guide would make it easier for contributors to write a PR to fix them.
That said, the style guide changes should probably be in a separate PR.


shortLang behavior when fetching zh-hans

Thanks for making this awesome tool!
I've been run into this issue when I'm trying to query zh-hans (simplified chinese) as a languages options in getEntities.  It seems to force convert it to zh, what's the rational behind this? In the case of zh, we have many variants so each language code have return different result
reference: https://github.com/maxlath/wikibase-sdk/blob/452249b364093e389d47add3c3c7e413871eb0ce/lib/utils/utils.js#L2
Should the force lang leave as an option or better just leave to the end users to convert?
thanks!

thank you for reporting, as I deal mostly with languages without -, I didn't see that was causing this kind of behavior >< that's now fixed in v7.1.2


Downgrade RubyGems from 2.4.8 to 2.4.4.

Revert part of #474.

:+1:

:+1:

Curious - why was this reverted?  We needed 2.4.8 for http://blog.rubygems.org/2015/05/14/CVE-2015-3900.html and we need >2.4.6 because otherwise we pull in broken duplicate dependencies on windows because 2.4.4 does not understand universal platform packages.

@ksubrama 2.4.8 does something quirky with how it requires files, which caused some breakage for us yesterday. Figuring it out and fixing it is a blocker for 0.8.0, so this was a temporary unblocking change.
That said, the breakage occurred on Ubuntu 14.04--I only reverted the whole change out of an abundance of caution--so it's possible 2.4.8 could be re-enabled on Windows. If you do that, please give @cwebberOps a heads-up so he can keep an eye out for issues.


Replace PNG logos with vector logos

What happened
Jetbrains logo looks too small. Also, many logos look blurry on retina displays. Change to SVG where available.
Insight
Check logos look less blurry.


libvirt.NewVirConnectionWithAuth segfaults if user/pass are ""

@rmohr libvirt.NewVirConnectionWithAuth does not handle empty user/password gracefully.
I was thinking abut
 func NewConnection(uri string, user string, pass string) (Connection, error) {
-       virConn, err := libvirt.NewVirConnectionWithAuth(uri, user, pass)
+       var err
+       if user == "" {
+               virConn, err := libvirt.NewVirConnection(uri)
+       } else {
+               virConn, err := libvirt.NewVirConnectionWithAuth(uri, user, pass)
+       }
        if err != nil {
                return nil, err
        }

thoughts?

With qemu+tcp://… this is still the case.
The virt-handler segfaults if they are not given.
Adding --user and --pass fixes the issue.

Could you share the stacktrace?

Yes, but it needs to wait until monday.

Btw it is easy to reproduce
Have libvirt listen on TCP without authentication and run virt-handler --libvirt-uri qemu+tcp://ADDR/system - then retry with --user and --pass.


Routed Attached Event Won't Compile

v0.9.10
Per this documentation:
https://avaloniaui.net/docs/input/events
I couldn't get it to compile.

Error	XAMLIL	Unable to resolve suitable regular or attached property Click on type Avalonia.Controls:Avalonia.Controls.Button (line 16 position 6) Line 16, position 6.	AvaloniaApplication1

I was able to recreate the problem in a brand new project using the example code.
<Border>
  <StackPanel Orientation="Horizontal" Button.Click="CommonClickHandler">
    <Button Name="YesButton">Yes</Button>
    <Button Name="NoButton">No</Button>
    <Button Name="CancelButton">Cancel</Button>
  </StackPanel>
</Border>

public void CommonClickHandler(object sender, RoutedEventArgs e)
{
    // Handle
}

Ah yes, looks like that feature isn't yet implemented, sorry @seanocali - my bad, I thought it was implemented.
We hope to have this feature working for 0.10, but in the meantime you'll have to add a click handler to each button separately.

Does still not work as of 02/2022. Wouldn't it be nice to update the documentation? Wasted some time to figure out, that I was trying to use a feature which is not yet implemented...

Closing in favor of a more specific issue - #9507. Documentation was updated.


Roll engine 303a3910d398..c56a1a28aa30 (3 commits)

https://github.com/flutter/engine/compare/303a3910d398...c56a1a28aa30
git log 303a3910d398ee48a3411108688ebd5ccc101e8a..c56a1a28aa30e9e54366d11f3e83419add5d0c53 --no-merges --oneline
c56a1a28a Update FlutterDevCompilerTarget for the new superclass constructor in the Dart SDK (flutter/engine#9039)
135a14059 Add font features (such as tabular numbers) as an option in text styles (flutter/engine#8823)
45664a6aa Roll src/third_party/dart b11308657c..b11308657c (0 commits) (flutter/engine#9037)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6391832112529408

Commit queue failed; closing this roll.


Throttle upgrades scheduled per minute

@mpolden and @hmusum please review

I'm not sure this is the way to go based on our experiences so far. Let's discuss tomorrow.

Closing, will create a new PR.


Add more reproducibility tests

This PR adds more reproducibility tests. Closes #3392.

How did we chose which tests are opted into the reproducibility suite? And do we duplicate any? (Meaning do we run them twice - once for reproducibility and once for whatever was in the CI

How did we chose which tests are opted into the reproducibility suite? And do we duplicate any? (Meaning do we run them twice - once for reproducibility and once for whatever was in the CI

They opt-in by running the second test_mse.jl script after the initial driver job is run. By default, we use strict reproducibility, but we can set the test_broken_report_flakiness flag to true if it turns out a job is not very reproducible.
we probably don’t care about reproducibility for all jobs, though, like the flame graphs or benchmarks, so I think it’s fine to leave it as an opt-in feature.

I just added it to everything that looked like an experiment.

We probably don't need reproducibility tests for all the jobs, but if it doesn't cost much I'm fine with adding more now. Does reproducibility_test: true in the config do anything now?

We probably don't need reproducibility tests for all the jobs, but if it doesn't cost much I'm fine with adding more now. Does reproducibility_test: true in the config do anything now?

Yeah, I hope it’s not too expensive. I figure we can try it out. I think that flag no longer does anything, ever since we broke off the reproduceability test into a separate script. I’ll double check to confirm, and if it doesn’t do anything, then I’ll go and remove the flag.

Actually, I'll remove the reproducibility_test flag in the next PR since we'll need to update test_broken_report_flakiness for any jobs that are flaky anyway.

Oh, we currently use reproducibility_test to indicate that the results are exported to an NC file (so that the data is available when we run reproducibility_tests/test_mse.jl).


flow::from does not use ADL begin

We can see here that std::begin is used. For example, this does not work on std::filesystem::directory_iterator.
I can see several solutions:

using namespace std; each time begin is called. Impractical, but doable
Make libflow C++20 and use std::ranges::begin
Reproduce our own std::ranges::begin. Does not seem trivial without concepts. range-v3 impl

Hi, thanks for the bug report. I agree this should be fixed.
I think something along the lines of
namespace flow::detail {
namespace begin_cpo {

using namespace std;

struct fn {
    template <typename R>
    constexpr auto operator()(R&& rng) const
        noexcept(noexcept(begin(FLOW_FWD(rng)))
        -> decltype(begin(FLOW_FWD(rng))
    {
        return begin(FLOW_FWD(rng));
    }
};

} // namespace begin_cpo

inline constexpr auto begin = begin_cpo::fn{};

}

would solve the issue and  be "good enough" without having to go to all the lengths that ranges does, i.e. disallowing calling begin() on rvalue non-borrowed ranges (we don't really have to worry about this case for the purposes of flow::from).
Alternatively I have an implementation of std::ranges::begin from my NanoRange library which could be repurposed for libflow. It's not very pretty, but it's a bit simpler than the Range-V3 equivalent I think.
One day I'll change libflow to use C++20 and this issue will go away as we'll be able to use the real std::ranges::begin, but I'm not keen on doing that until Clang/libc++ supports ranges.


Cloud Build fails for python Google Function (functions-framework)

When using GOOGLE_FUNCTION_TARGET, the build works okay locally. Example below:
pack --verbose build <FUNC_NAME> --clear-cache --builder gcr.io/buildpacks/builder:v1 --env GOOGLE_FUNCTION_TARGET=<FUNC_NAME>
But when I trigger this in Cloud Build in GCP, it fails (with a permissions error) when trying to precompile the python code. Snippet below; full build log is attached. Kind of looks like it's failing when trying to create pycache directories, but since I can't reproduce locally, it's difficult to troubleshoot. Relevant code seems to be in cmd/python/functions_framework/main.go
Builds for regular python web apps (Flask/gunicorn) don't seem to do this compile step.
=== Python - Functions Framework<EMAIL_ADDRESS>===
--------------------------------------------------------------------------------
Running "python3 -m compileall -f -q ."
*** Error compiling './cloud_apps/costpricer_web_api.py'...
PermissionError: [Errno 13] Permission denied: './cloud_apps/__pycache__'
*** Error compiling './cloud_apps/functions.py'...
PermissionError: [Errno 13] Permission denied: './cloud_apps/__pycache__'
Done "python3 -m compileall -f -q ." (110.672077ms)

build.log

A few things to try:

Can you check the permissions on these directories locally? ls -ld cloud_apps and ls -ld cloud_apps/__pycache__
Can you try removing the __pycache__ directory locally before submitting the build?

Could you also give us some more details about how you're submitting the build? What platform you're on, etc. Are you invoking gcloud builds submit locally, pushing this to a source repository, etc?

Hi @di
The build is automatically triggered on push to git branch (code is in Cloud Source Repos). The __pycache__ dirs definitely don't exist in the repo; have double checked this.

But cloud_apps does? What are the permissions on that directory?

AFAIK there's no way of setting permissions on a directory in a git repo. Git tracks the executable-bit on files only.
The command below just ends up showing the perms on the files under that dir, and they're 644.
I would imagine on Linux, the directories end up inheriting permissions from the system's (or user's) umask.
λ git ls-files -s cloud_apps
100644 7341dbad696158535a179ca99b4e97268a654100 0       cloud_apps/costpricer_web_api.py
100644 86a2327b3f8f3f32af19e1441b88220cc2cfdbad 0       cloud_apps/functions.py

I tried to reproduce this with the following and couldn't (output here):
$ tree
.
├── cloud_apps
│   ├── costpricer_web_api.py
│   └── functions.py
├── cloudbuild.yaml
└── main.py

1 directory, 4 files

$ cat cloudbuild.yaml
steps:
  - name: 'gcr.io/k8s-skaffold/pack'
    args: ["pack", "--verbose", "build", "hello", "--clear-cache", "--builder", "gcr.io/buildpacks/builder:v1", "--env", "GOOGLE_FUNCTION_TARGET=hello"]

$ cat main.py
from cloud_apps import *

def hello(request):
   return "hi"

Is there anything different about how you're invoking pack here? Are you able to produce a minimally reproducing example so we can debug?

I think to reproduce you'd have to setup a build that is triggered remotely in GCP by git branch pushes, or tag creations.
This is part of the workflow if you setup a Cloud Run instance with Continuous Deployment (which is what I've done).
I've attached another build log where you can see it doing the git fetch at the top. I suspect there's a change of user, between doing the fetch and running the pack build. As a workaround I've stopped using GOOGLE_FUNCTION_TARGET and instead I set  GOOGLE_ENTRYPOINT  to functions-framework --target <function_name> , and I guess that bypasses the problematic step.
log-47925515-3692-42f9-bd22-0bcfd2bb1cf3.txt

Ok, so it looks like you followed https://cloud.google.com/run/docs/continuous-deployment-with-cloud-build#new-service then, is that right?
I followed this guide, using Cloud Source Repositories for the provider and Cloud Buildpacks for the build type. It created the following Cloud Build configuration:
steps:
  - name: gcr.io/k8s-skaffold/pack
    args:
      - build
      - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
      - '--builder=gcr.io/buildpacks/builder:v1'
      - '--path=.'
    id: Buildpack
    entrypoint: pack
  - name: gcr.io/cloud-builders/docker
    args:
      - push
      - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
    id: Push
  - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk:slim'
    args:
      - run
      - services
      - update
      - $_SERVICE_NAME
      - '--platform=managed'
      - '--image=$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
      - >-
        --labels=managed-by=gcp-cloud-build-deploy-cloud-run,commit-sha=$COMMIT_SHA,gcb-build-id=$BUILD_ID,gcb-trigger-id=$_TRIGGER_ID,$_LABELS
      - '--region=$_DEPLOY_REGION'
      - '--quiet'
    id: Deploy
    entrypoint: gcloud
images:
  - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
options:
  substitutionOption: ALLOW_LOOSE
substitutions:
  _LABELS: gcb-trigger-id=b6debbf6-c677-4a8e-acb1-c5f1cd6991e6
  _TRIGGER_ID: b6debbf6-c677-4a8e-acb1-c5f1cd6991e6
  _GCR_HOSTNAME: us.gcr.io
  _PLATFORM: managed
  _SERVICE_NAME: test-buildpacks
  _DEPLOY_REGION: us-central1
tags:
  - gcp-cloud-build-deploy-cloud-run
  - gcp-cloud-build-deploy-cloud-run-managed
  - test-buildpacks

And then I added this:
  - name: gcr.io/k8s-skaffold/pack
    args:
      - build
      - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
      - '--builder=gcr.io/buildpacks/builder:v1'
      - '--path=.'
+      - '--env'
+      - GOOGLE_FUNCTION_TARGET=hello
    id: Buildpack
    entrypoint: pack

And the build succeeded with the above example.
Can you provide us with the inline build configuration you're using? You can find this by going to https://console.cloud.google.com/run -> your service name -> "Edit continuous deployment" -> "Configuration" -> "Open editor"

Hi @jameslittle, are you able to share the inline build configuration that was generated for your service?

@jameslittle are you able to attach your cloud build configuration?

Hi @di & @briandealwis
Please see my build config below. Looks very similar to yours; the only meaningful difference I can see is that I have a subdirectory src as the root of the buildpack project. But this works fine for other Cloud Run instances (non GOOGLE_FUNCTION_TARGET instances)
  - name: gcr.io/k8s-skaffold/pack
    args:
      - build
      - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
      - '--builder=gcr.io/buildpacks/builder:v1'
      - '--path=src'
      - '--env'
      - GOOGLE_FUNCTION_TARGET=persist_datamodel
    id: Buildpack
    entrypoint: pack
  - name: gcr.io/cloud-builders/docker
    args:
      - push
      - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
    id: Push
  - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk:slim'
    args:
      - run
      - services
      - update
      - $_SERVICE_NAME
      - '--platform=managed'
      - '--image=$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
      - >-
        --labels=managed-by=gcp-cloud-build-deploy-cloud-run,commit-sha=$COMMIT_SHA,gcb-build-id=$BUILD_ID,gcb-trigger-id=$_TRIGGER_ID,$_LABELS
      - '--region=$_DEPLOY_REGION'
      - '--quiet'
    id: Deploy
    entrypoint: gcloud
images:
  - '$_GCR_HOSTNAME/$PROJECT_ID/$REPO_NAME/$_SERVICE_NAME:$COMMIT_SHA'
options:
  substitutionOption: ALLOW_LOOSE
substitutions:
  _SERVICE_NAME: perfectpanda-uat-datamodel-persist
  _LABELS: gcb-trigger-id=6efcdf34-9d46-4d70-b397-bff52badf935
  _TRIGGER_ID: 6efcdf34-9d46-4d70-b397-bff52badf935
  _DEPLOY_REGION: europe-west2
  _GCR_HOSTNAME: eu.gcr.io
  _PLATFORM: managed
tags:
  - gcp-cloud-build-deploy-cloud-run
  - gcp-cloud-build-deploy-cloud-run-managed
  - perfectpanda-uat-datamodel-persist

Also, in your source code repo, do you some code (python modules/packages) in subdirectories? As it seems to fail creating pycache in subdirs.

Hi @jameslittle: this is baffling. Could you provide a layout of your project so that we can try to reproduce exactly what you're seeing?
Could you add a build step prior to running pack to output the directory permissions?  That will help identify if the permission issues are happening as part of the checkout.  Something like:
  - name: 'bash'
    args: ['find', '-L', '.', '-type', 'd', '-exec', 'ls', '-ld', '{}', ';']

Do you get the same permission denied errors if you try to submit a build with gcloud builds submit?  You'll need to copy out that build script to a cloudbuild.yaml and remove the substitutions and instead provide them on the command-line.  Something like the following should work:
gcloud builds submit --project petproactive-analytics --substitutions=_GCR_HOSTNAME=eu.gcr.io,REPO_NAME=analytics,_SERVICE_NAME=perfectpanda-uat-datamodel-persist,_DEPLOY_REGION=europe-west2,COMMIT_SHA=xxx .

One odd thing: when I try to reproduce this, even the exact version of gcr.io/buildpacks/builder@sha256:19052a50a854df61dcb1be84101929b6a03f2404a4 1c3852c5c3998406465792 as in your build logs, I have a warning that appears:
Step #0 - "Buildpack": [builder] Running "python3 -m compileall -f -q ."
Step #0 - "Buildpack": [builder] Done "python3 -m compileall -f -q ." (50.328408ms)
Step #0 - "Buildpack": [builder] Handling functions with dependency on functions-framework.
Step #0 - "Buildpack": [builder] WARNING: Launch layer is setting default=true, but that is not supported until API version 0.6. This setting will be ignored.
Step #0 - "Buildpack": [builder] Warning: Warning: default processes aren't supported in this buildpack api version. Overriding the default value to false for the following processes: [web]

which isn't present in your build logs.

Quick ping @jameslittle: even just this would help

Could you provide a layout of your project so that we can try to reproduce exactly what you're seeing?

I am closing this as we don't have enough information to debug. @jameslittle please re-open if you are still having issues.


Create 163.txt

@china-zengyuanzheng This domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.


tf.data.Iterator won't release memory when reinitialized

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Win 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.10.1
Python version: 3.6.6
CUDA/cuDNN version: 9.0
GPU model and memory: NVIDIA GTX1080Ti, 11GB GPU/ 64 GB RAM

Describe the current behavior
When testing my model, I had several batches of images with batch size equals to 10. As the images are large, I loaded them from hard drive every time. My code is structured as
iterator = tf.data.Iterator.from_structure(output_types=tf.float32, output_shapes=[1536, 1536, 2])
output  = model_fn(iterator.get_next())
for images in files:
    dataset = tf.data.Dataset.from_tensor_slices(tf.constant(images))
    sess.run(iterator.make_initializer(dataset))
    output_value = []
    for _ in range(10):
        output_value.append(sess.run(output))

Here each of my images is a numpy array with a size of [10, 1536, 1536, 2].
While the code running, the memory usage is growing fast -- every image set it read in stayed there in the memory.
Describe the expected behavior
I'm expecting the iterator release the memory each time it reinitialized.
Code to reproduce the issue
For a reproducible test, I also tried this, to see if the memory leakage is due to something else:
import tensorflow as tf
import numpy as np
iterator = tf.data.Iterator.from_structure(output_types=tf.float64, output_shapes=[1536,1536,2])
sess = tf.InteractiveSession()
for i in range(100):
    data = tf.constant(np.random.rand(10,1536,1536,2))
    dataset = tf.data.Dataset.from_tensor_slices(data)
    ite_data = iterator.make_initializer(dataset)
    sess.run(ite_data)

I can still see a huge memory usage when executing this.

https://github.com/tensorflow/tensorflow/issues/23904

@yluo16 visit this issue you will get little bit help.

@yluo16 visit this issue you will get little bit help.

Thanks for advising. I'm sorry for raising a existing issue... Maybe I should upgrade to TF 2.0.

Closing since #23904 captures the explanation of behavior observed in this issue. Feel free to reopen if still have further problems. Thanks!


Update README.md

Sweet project. This fixes some minor formatting, grammar and spelling.

@ukd1 Thanks!


Suggestion: Tap to reveal as an alternative to long-press

I'd much rather just tap the card (anywhere on the card) to reveal it rather than having to long-press each time.

Thanks for the feedback! I'll add this this to the next version.

[ ] Option to set the trigger area to the entire card vs. only the button
[ ] Option to enable / disable long press
[ ] Option to enable / disable haptic feedback

This is implemented, and will be included in the upcoming release


Found XDF !!!

Paco Pando found a copy of the technical specification for our last missing standard! He scanned it and sent me a PDF so that we could archive it.

@peterdesmet Can you merge this? I don't seem to be allowed to request a reviewer.

@baskaufs I've invited you to the prior-standards team. If you accept, you should be able to set a reviewer (e.g. me). Can you test?

I didn't seem to need to accept it. In any case, I can now request your review. Thanks!


Add condition in Genus filter to SCIENTIFIC field must include spp.

Add condition for genus filter
@bestw07
@TreeMama
Please review PR

as I enter filter of "ab", tree list pictures still includes baobab. Is this ok?

@jgrenadier thanks for checking. Actually @SafiDS 's 2 PR's failed because the checkins cannot be merged. Also his work was in the AddTreeScreen.tsx (Not the info menu - which you are looking at). The 'add spp.' was a filter condition for TreeBot - and 100% UNRELATED to the info menu.
But like I said - this PR will never be merged into our branch - just based on failing the merge conflict check.
As for the info menu question - the search is doing that because it is not prioritizing the first letters in the search. It isn't a bug (that is the expected behavior) but it could be improved upon I agree. You can open an issue for it if you like :) !


Support for PHP version 5.6

Hi, I'm having trouble installing the versions 1.2.5 and 1.2.6 on a PHP 5.6 system.
It seems the releases force version 7.2 or higher.
I get an error message when trying to access my site after installing the plugin, that reads:
Your Composer dependencies require a PHP version ">= 7.2.0". You are running 5.6.40
This is caused by vendor/composer/platform_check.php in the ZIP-releases of 1.2.5 and 1.2.6.
I tried commenting out the responsible line, but that only fixed the error message and the site still didn't work.
I rolled back back to 1.2.4 which works just fine, but maybe you can help me update.
Thanks in advance.

What's the reason you're still on PHP 5.6? 5.6 has been EOL for almost 5 years!
I'd seriously suggest upgrading to PHP 8. Or, at the very least 7.4 (which has also been EOL since the end of last year)
The new features introduced in 1.2.5 (and next up, 1.3.0) use functions only available in 7.2. Hence the raised requirements. We're not planning to keep supporting 5.6, simply because eventually WordPress will also drop its support.
But, if you must, since you're installing using Composer, have you tried to append --ignore-platform-reqs to the command?

For anyone else interested, found this table, showing that PHP 5.6 support in WordPress is next up to be dropped:

Thanks for the reply!
I'm afraid i can't upgrade the PHP installation.
I installed this plugin via the Wordpress dashboard, where it's marked as still 5.6 compatible in 1.2.5 and 1.2.6.
So when i tried to upgrade, it doesn't warn you and breaks the wordpress installation.
I'm not sure whether that's a problem on your end, just wanted to give you a heads-up.
Have a good one.

Thanks for notifying me, I'll change that!