Enabling Xdebug and listening with PHPStorm results in a 503 since v1.22.6.

General
Upgraded to v1.22.6 and trying to use Xdebug results in a 503 with no clear error in any of the logs. ([proxy_fcgi:error] [pid 2176] [client <IP_ADDRESS>:54646] AH01067: Failed to read FastCGI header), but no other error logs.
Reverting to v1.22.4 fixes the issue.
Is there an existing issue for this?

[X] I have searched the existing issues

Output of ddev debug test
Export v1.22.6.
Expand `ddev debug test` diagnostic information
Running bash [-c /var/folders/x_/v_8843wj1497bp2sh1grj0km0000gp/T/test_ddev.sh]
======= Existing project config =========
These config files were loaded for project project-latest-develop: [/Users/tomas.nagy/Workspace/company/project-latest-develop/.ddev/config.yaml /Users/tomas.nagy/Workspace/company/project-latest-develop/.ddev/config.local.yml]
name: project-latest-develop
type: shopware6
docroot: public
php_verscompanyn: 8.1
webserver_type: apache-fpm
webimage: ddev/ddev-webserver:v1.22.6
router_http_port: 80
router_https_port: 443
database: {mysql 8.0}
webimage_extra_packages: [build-essential libglu1 chromium libxi6 libgconf-2-4]
project_tld: ddev.site
use_dns_when_possible: true
timezone: Europe/Brussels
composer_verscompanyn: 2
nodejs_verscompanyn: 16
default_container_timeout: 120
======= Creating dummy project named  tryddevproject-7884 in ../tryddevproject-7884 =========
OS Informatcompanyn: Darwin D62269L9Q3.local 23.2.0 Darwin Kernel Verscompanyn 23.2.0: Wed Nov 15 21:54:51 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6030 arm64
ProductName:		macOS
ProductVerscompanyn:		14.2
BuildVerscompanyn:		23C64
User informatcompanyn: uid=502(tomas.nagy) gid=20(staff) groups=20(staff),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),701(com.apple.sharepoint.group.1),33(_appstore),100(_lpoperator),204(_developer),250(_analyticsusers),395(com.apple.access_ftp),398(com.apple.access_screensharing),399(com.apple.access_ssh),400(com.apple.access_remote_ae),702(com.apple.sharepoint.group.2)
DDEV verscompanyn:  ITEM             VALUE
 DDEV verscompanyn     v1.22.6
 architecture     arm64
 db               ddev/ddev-dbserver-mariadb-10.4:v1.22.6
 ddev-ssh-agent   ddev/ddev-ssh-agent:v1.22.6
 docker           24.0.7
 docker-compose   v2.23.3
 docker-platform  orbstack
 mutagen          0.17.2
 os               darwin
 router           ddev/ddev-traefik-router:v1.22.6
 web              ddev/ddev-webserver:v1.22.6
PROXY settings: HTTP_PROXY='' HTTPS_PROXY='' http_proxy='' NO_PROXY=''
======= DDEV global info =========
Global configuratcompanyn:
instrumentatcompanyn-opt-in=true
omit-containers=[]
performance-mode=mutagen
router-bind-all-interfaces=false
internet-detectcompanyn-timeout-ms=3000
disable-http2=false
use-letsencrypt=false
letsencrypt-email=
table-style=default
simple-formatting=false
use-hardened-images=false
fail-on-hook-fail=false
required-docker-compose-verscompanyn=v2.23.3
use-docker-compose-from-path=false
project-tld=
xdebug-ide-locatcompanyn=
no-bind-mounts=false
router=traefik
wsl2-no-windows-hosts-mgt=false
router-http-port=80
router-https-port=443
mailpit-http-port=8025
mailpit-https-port=8026
traefik-monitor-port=10999

======= DOCKER info =========
docker locatcompanyn: lrwxr-xr-x  1 root  wheel  53 Dec 14 11:49 /usr/local/bin/docker -> /Applicatcompanyns/OrbStack.app/Contents/MacOS/xbin/docker
Docker Desktop Verscompanyn: Print: Entry, ":CFBundleShortVerscompanynString", Does Not Exist
Print: Entry, ":CFBundleVerscompanyn", Does Not Exist
Docker Desktop for Mac File build Doesn'tDocker Desktop for Mac Exist, build WillDocker Desktop for Mac Create: build /Applicatcompanyns/Docker.app/Contents/Info.plistDocker Desktop for Mac File build Doesn'tDocker Desktop for Mac Exist, build WillDocker Desktop for Mac Create: build /Applicatcompanyns/Docker.app/Contents/Info.plist
docker verscompanyn:
Client:
 Verscompanyn:           24.0.7
 API verscompanyn:       1.43
 Go verscompanyn:        go1.20.10
 Git commit:        afdd53b
 Built:             Thu Oct 26 09:04:20 2023
 OS/Arch:           darwin/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Verscompanyn:          24.0.7
  API verscompanyn:      1.43 (minimum verscompanyn 1.12)
  Go verscompanyn:       go1.20.10
  Git commit:       311b9ff
  Built:            Thu Oct 26 09:08:17 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Verscompanyn:          v1.7.7
  GitCommit:        8c087663b0233f6e6e2f4515cee61d49f14746a8
 runc:
  Verscompanyn:          1.1.9
  GitCommit:        82f18fe0e44a59034f3e1f45e475fa5636e539aa
 docker-init:
  Verscompanyn:          0.19.0
  GitCommit:        de40ad0
DOCKER_DEFAULT_PLATFORM=notset
======= Mutagen Info =========
Mutagen is installed in ddev, verscompanyn=0.17.2
--------------------------------------------------------------------------------
Name: project-latest-develop
Identifier: sync_k9Fwact1W08RVYNTqffJmRGUY51537FIiPb7q73KZSw
Labels:
	com.ddev.config-hash: fe108c9ee901316f617e1ad61402051d9b69a0fc
	com.ddev.volume-signature: Users-tomas-nagy-orbstack-run-1702629716
Configuratcompanyn:
	Synchronizatcompanyn mode: Two Way Resolved
	Hashing algorithm: Default (SHA-1)
	Maximum allowed entry count: Default (2⁶⁴−1)
	Maximum staging file size: Default (18 EB)
	Symbolic link mode: POSIX Raw
	Ignore VCS mode: Default (Propagate)
	Ignores:
		/.git
		node_modules
		/var_cache
		/var/log
		/var/cache
		/.tarballs
		/.ddev/db_snapshots
		/.ddev/.importdb*
		.DS_Store
		.idea
		public/media
		public/thumbnail
	Permisscompanyns mode: Default (Portable)
Alpha:
	URL: /Users/tomas.nagy/Workspace/company/project-latest-develop
	Configuratcompanyn:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
	Connected: No
Beta:
	URL: docker://ddev-project-latest-develop-web/var/www/html
		DOCKER_HOST=unix:///Users/tomas.nagy/.orbstack/run/docker.sock
	Configuratcompanyn:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
		Compresscompanyn: Default (DEFLATE)
	Connected: No
Status: [Paused]
--------------------------------------------------------------------------------
Name: tryddevproject-2604
Identifier: sync_wJyWElnykDxxNZyURg041CXuKJdxpswi8DPpPaNzjGw
Labels:
	com.ddev.config-hash: 0311359b0f6eedb428c2679de60b5d021c2d717b
	com.ddev.volume-signature: Users-tomas-nagy-orbstack-run-1702630706
Configuratcompanyn:
	Synchronizatcompanyn mode: Two Way Resolved
	Hashing algorithm: Default (SHA-1)
	Maximum allowed entry count: Default (2⁶⁴−1)
	Maximum staging file size: Default (18 EB)
	Symbolic link mode: POSIX Raw
	Ignore VCS mode: Default (Propagate)
	Ignores:
		/.git
		/.tarballs
		/.ddev/db_snapshots
		/.ddev/.importdb*
		.DS_Store
		.idea
	Permisscompanyns mode: Default (Portable)
Alpha:
	URL: /Users/tomas.nagy/Workspace/company/tryddevproject-2604
	Configuratcompanyn:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
	Connected: Yes
	Synchronizable contents:
		28 directories
		76 files (106 kB)
		0 symbolic links
Beta:
	URL: docker://ddev-tryddevproject-2604-web/var/www/html
		DOCKER_HOST=unix:///Users/tomas.nagy/.orbstack/run/docker.sock
	Configuratcompanyn:
		Watch mode: Default (Portable)
		Watch polling interval: Default (10 seconds)
		Probe mode: Default (Probe)
		Scan mode: Default (Accelerated)
		Stage mode: Neighboring
		File mode: Default (0600)
		Directory mode: Default (0700)
		Default file/directory owner: Default
		Default file/directory group: Default
		Compresscompanyn: Default (DEFLATE)
	Connected: Yes
	Synchronizable contents:
		28 directories
		76 files (106 kB)
		0 symbolic links
Status: Watching for changes
--------------------------------------------------------------------------------
======= Docker Info =========
Docker platform: orbstack
Using Docker context: default (unix:///Users/tomas.nagy/.orbstack/run/docker.sock)
docker-compose: v2.23.3
Using DOCKER_HOST=unix:///Users/tomas.nagy/.orbstack/run/docker.sock
Docker verscompanyn: 24.0.7
Able to run simple container that mounts a volume.
Able to use internet inside container.
Docker disk space:
Filesystem                Size      Used Available Use% Mounted on
overlay                 399.6G     15.5G    384.1G   4% /

 Container ddev-tryddevproject-2604-db  Stopped
 Container ddev-tryddevproject-2604-web  Stopped
 Container ddev-tryddevproject-2604-db  Stopped
 Container ddev-tryddevproject-2604-web  Stopped
 Container ddev-tryddevproject-2604-db  Removed
 Container ddev-tryddevproject-2604-web  Removed
 Network ddev-tryddevproject-2604_default  Removed
Project tryddevproject-2604 has been stopped.
Stopped Mutagen daemon
The ddev-ssh-agent container has been removed. When you start it again you will have to use 'ddev auth ssh' to provide key authenticatcompanyn again.
Network ddev_default removed
Existing docker containers:
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
Network ddev_default created
Starting tryddevproject-7884...
Network ddev-tryddevproject-7884_default created
 Container ddev-ssh-agent  Created
 Container ddev-ssh-agent  Started
ssh-agent container is running: If you want to add authenticatcompanyn to the ssh-agent container, run 'ddev auth ssh' to enable your keys.
Building project images...
Project images built in 0s.
 Container ddev-tryddevproject-7884-db  Created
 Container ddev-tryddevproject-7884-web  Created
 Container ddev-tryddevproject-7884-db  Started
 Container ddev-tryddevproject-7884-web  Started
You have Mutagen enabled and your 'php' project type doesn't have `upload_dirs` set.
For faster startup and less disk usage, set upload_dirs to where your user-generated files are stored.
If this is intended you can disable this warning with `ddev config --disable-upload-dirs-warning`.
Starting Mutagen sync process...
Mutagen sync flush completed in 1s.
For details on sync status 'ddev mutagen st tryddevproject-7884 -l'
Waiting for web/db containers to become ready: [web db]
Starting ddev-router if necessary...
 Container ddev-router  Created
 Container ddev-router  Started
Waiting for additcompanynal project containers to become ready...
All project containers are now ready.
Successfully started tryddevproject-7884
Project can be reached at https://tryddevproject-7884.ddev.site https://<IP_ADDRESS>:32791
======== Curl of site from inside container:
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 15 Dec 2023 09:00:03 GMT
Content-Type: text/html; charset=UTF-8
Connectcompanyn: keep-alive
Vary: Accept-Encoding

======== curl -I of http://tryddevproject-7884.ddev.site from outside:
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Date: Fri, 15 Dec 2023 09:00:03 GMT
Server: nginx
Vary: Accept-Encoding

======== full curl of http://tryddevproject-7884.ddev.site from outside:
Success accessing database... db via TCP/IP
ddev is working. You will want to delete this project with 'ddev delete -Oy tryddevproject-7884'
======== Project ownership on host:
drwxr-xr-x@ 4 tomas.nagy  staff  128 Dec 15 09:59 ../tryddevproject-7884
======== Project ownership in container:
drwxr-xr-x 1 tomas.nagy dialout 16 Dec 15 08:59 /var/www/html
======== In-container filesystem:
Filesystem     Type  1K-blocks     Used Available Use% Mounted on
/dev/vdb1      btrfs 418890880 16394336 402506048   4% /var/www
======== curl again of tryddevproject-7884 from host:
Success accessing database... db via TCP/IP
ddev is working. You will want to delete this project with 'ddev delete -Oy tryddevproject-7884'
Thanks for running the diagnostic. It was successful.
Please provide the output of this script in a new gist at gist.github.com
Running ddev launch in 5 seconds

Expected Behavior
Xdebug to work.
Actual Behavior
Enablling Xdebug and listening for connections in PHPStorm results in a 503 on every page.
Steps To Reproduce

Start project
Enable Xdebug
Start listening for debug connections

Anything else?
No response

I'm unable to recreate this problem. I see you were using PHP 8.1 and xdebug.
Could you please do a ddev logs after you get the 503 and provide its output?

I have also now tested this on php8.1 a mac M1 (arm64) architecture without any trouble. Could you please try a plain vanilla project of your CMS type and see what happens with it? I do think ddev logs will tell the story of your problem.

Please mention what actual Mac model you have - is it an M3?
You may want to try webimage_extra_packages: [php8.1-xdebug] to pick up the very latest php8.1-xdebug.
Also take a look at recent xdebug issues to see if something might be related to your situation.

@rfay @tomasnagy I have the same problem since the update. However, it does not always occur and only when PhpStorm starts listening and has breakpoints. If I disable listening or remove all breakpoints, then the calls work. I am still on PHP 8.0 with Apache webserver. Environment is all in WSL2 (DDEV, Docker, PhpStorm).
Output of ddev logs:
[Fri Dec 15 13:35:38.677347 2023] [proxy_fcgi:error] [pid 3146] [client <IP_ADDRESS>:37938] AH01067: Failed to read FastCGI header, referer: https://test.ddev.site/
[Fri Dec 15 13:35:38.677378 2023] [proxy_fcgi:error] [pid 3146] (104)Connection reset by peer: [client <IP_ADDRESS>:37938] AH01075: Error dispatching request to : , referer: https://test.ddev.site/
[15-Dec-2023 13:35:38] WARNING: [pool www] child 3179 exited on signal 11 (SIGSEGV) after 211.697300 seconds from start
[15-Dec-2023 13:35:38] NOTICE: [pool www] child 3223 started

This is a SEGV in xdebug I think. Have you already tried webimage_extra_packages: [php8.0-xdebug] to get the very latest xdebug?
Probably https://bugs.xdebug.org/view.php?id=2221
Seems also reported in https://github.com/oerdnj/deb.sury.org/issues/2059

@rfay Adding php8.1-xdebug to extra packages fixed the issue, thanks!
Yes on an M3 and had the exact same error log as @blankse

@rfay Adding php8.0-xdebug to webimage_extra_packages doesn't work for me. The version of xdebug in the phpinfo is unchanged (With/Without 3.3.0). The error is the same.
@tomasnagy Is the version changed with the extra package with PHP 8.1?

@blankse version remains the same (3.3.0) but with the extra package it doesn't crash anymore. Destroying and building everything without the extra package reintroduces the problem for me.

Those of you struggling with this, please follow the upstream issues (https://bugs.xdebug.org/view.php?id=2221) (in xdebug), but

If you're trying the webimage_extra_packages approach, do a ddev debug refresh to force image rebuild.
Please try to direct-install-from-pecl approach in https://stackoverflow.com/questions/77582344/how-can-i-install-xdebug-on-ddev-for-php-8-3-before-its-ready-in-a-release

xdebug 3.3.1 is out, and request has been made to update to it in

https://github.com/oerdnj/deb.sury.org/issues/2059#issuecomment-1874172801

Notice: webimage_extra_packages with php8.1-xdebug does not solve the problem for me.

I hope you'll try the peck approach and report back, https://github.com/ddev/ddev/issues/5633#issuecomment-1866915333

xdebug 3.3.1 is available in the deb.sury.org repository now.
When I add php8.0-xdebug to webimage_extra_packages and execute ddev debug refresh, the xdebug version is updated.
@rfay In the next version of ddev, it is updated without adding it to webimage_extra_packages?

Yes, of course.

@rfay The problem occurs for php 8.1 for some reason. I changed php version to 7.4 and it worked fine. I have tested with 8.2 also and it works. Just 8.1 is not working for some reason

@zaifastafa could you please check what php8.1-xdebug version you have? If you have 3.3.1 it shouldn't be happening, I don't think.
Use $ ddev config --php-version=8.1 && ddev restart && ddev xdebug && ddev php --version to see
$ ddev xdebug && ddev php --version
Enabled xdebug
PHP 8.1.27 (cli) (built: Dec 21 2023 20:17:59) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.27, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.27, Copyright (c), by Zend Technologies
    with Xdebug v3.3.1, Copyright (c) 2002-2023, by Derick Rethans

If it doesn't have 3.3.1 for the xdebug version, please use ddev config --webimage-extra-packages=php8.1-xdebug && ddev restart and see if it's solved.

I´m still having this problem?
$ ddev -v
ddev version v1.22.7

$ ddev xdebug && ddev php --version
#Enabled xdebug
PHP 8.1.27 (cli) (built: Dec 21 2023 20:17:59) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.27, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.27, Copyright (c), by Zend Technologies
    with Xdebug v3.3.1, Copyright (c) 2002-2023, by Derick Rethans

[Wed Mar 27 09:58:42.730505 2024] [proxy_fcgi:error] [pid 2282] [client <IP_ADDRESS>:39528] AH01067: Failed to read FastCGI header
[Wed Mar 27 09:58:42.730530 2024] [proxy_fcgi:error] [pid 2282] (104)Connection reset by peer: [client <IP_ADDRESS>:39528] AH01075: Error dispatching request to :
[27-Mar-2024 09:58:42] WARNING: [pool www] child 9184 exited on signal 11 (SIGSEGV) after 42.926748 seconds from start

@ktallafus The version 3.3.1 also have crashing bugs. This should be fixed in the next version. See https://github.com/oerdnj/deb.sury.org/issues/2059#issuecomment-1946339644
In the meantime I use the 3.2.2 version:

Add a Dockerfile in /.ddev/web-build/Dockerfile
Add following lines

ARG BASE_IMAGE
FROM $BASE_IMAGE
RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests php-pear php${DDEV_PHP_VERSION}-dev;
RUN pecl install xdebug-3.2.2;

Restart ddev ddev restart

@blankse Oh my god, thank you so much. This was annoying the hell out of me :)
It worked, just had to add build-essentials to make the image build successfully:
ARG BASE_IMAGE
FROM $BASE_IMAGE
RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests build-essential php-pear php${DDEV_PHP_VERSION}-dev;
RUN pecl install xdebug-3.2.2;

Xdebug upstream is now at 3.3.2 and should be OK with
webimage_extra_packages: [php${DDEV_PHP_VERSION}-xdebug]


Post Request

How to use POST option kindly share any sample how to post data to web api in virtual scrolling

// this.data.items.push(item); // exist in component what does it means kindly share some detail on how it is used in component.ts what is mean by item

sample virtual-scroll
Where did you find this.data.items.push(item)?

I fond it in demo.service
kindly helps me i stuck in my project on urgent basis plzzz
i want to post data to web api how can i do this plz help

demo.service.ts
post(item: any): Promise {
// this.data.items.push(item); // exist in component
return new Promise((resolve) => {
setTimeout(() => resolve(item), 250);
});
}
put(item: any): Promise {
// this.data.items[this.findSelectedItemIndex(item)] = item; // exist in component
return new Promise((resolve) => {
setTimeout(() => resolve(item), 250);
});
}
delete(item: any): Promise {
// this.data.items.splice(this.findSelectedItemIndex(item), 1); // exist in component
return new Promise((resolve) => {
setTimeout(() => resolve(item), 250);
});
}
how can i use the above method with web api plz guide me

sample virtual-scroll
Where did you find this.data.items.push(item)?

i want POST PUT DELETE also in it how can i do this

sample services
another sample

sample services
Thanks for your swift response how can i use this service in virtual-scroll.ts plz guide your crud table is awesome and i m newbie if you help me so it's much useful for me how can i utilize put post delete in vistual-scroll.ts from the service sample service

  const columns: Column[];
  const settings: CdtSettings = <CdtSettings>{
    virtualScroll: true,
  };
this.dataManager = new DataManager(columns, settings, yourService);

in template:
<app-crud-table [dataManager]="dataManager">

How can i use my web api url i mean
for eg my web api address is www.abc.com/api/ceratenewalbum so in post method where i can use it will u plz explain ,i am sorry i disturb you again and again but your crud table is awesome and easy to use so i have to utilize it ,how can my component ts file connect with service post put delete method

interface DataSource {
  getItems(requestMeta: RequestMetadata): Promise<PagedResult>;
  getItem(row: any): Promise<any>;
  post(row: any): Promise<any>;
  put(row: any): Promise<any>;
  delete(row: any): Promise<any>;
  getOptions?(url: string, parentId: any): Promise<any>;
}

You need to create a class and implement interface methods
export class YourService implements DataSource {
}

export class ApiService {
WEB_API_SERVICE = "http://localhost:22387/api/Yarn";
constructor(private httpClient: HttpClient) { }
readYarnColor():Observable<Yarncolor[]>{
return this.httpClient.get<Yarncolor[]>(${this.WEB_API_SERVICE}/YarnColors);
}
createYarn(yarncolor:Yarncolor):Observable{
return this.httpClient.post(${this.WEB_API_SERVICE}/CreateYarn, yarncolor);
}
updateYarn(yarncolor:Yarncolor){
return this.httpClient.put(${this.WEB_API_SERVICE}/${yarncolor.YarnColorID}, yarncolor);
}
deleteYarn(id:number){
return this.httpClient.delete(${this.WEB_API_SERVICE}/api/?id=${id});
}
}
This is my custom service how can i use this with your grid all functionalities of crud filter and virtual scroll

help plz sir

readYarnColor -> getItems
createYarn -> post
updateYarn -> put
deleteYarn ->  delete

thanks for your time where i can write this in which file

you must write your class and pass the object to the DataManage constructor
const apiService = new ApiService(...);
new DataManager(columns, settings, apiService);

you must write your class and pass the object to the DataManage constructor
const apiService = new ApiService(...);
new DataManager(columns, settings, apiService);

sorry to disturb u again sir but i found this issue

YarncolorService must implement the DataSource interface

This is my yarncolor service how can i implement Datasource interface in it i m newbie dont know programming much kindly guids me once again sorry sir to disturb u again

Sir you help me too much but kindly explain me one more thing
post(row: any): Promise  what is row here

import {Injectable} from '@angular/core';
import {HttpClient  } from '@angular/common/http';
import {RequestMetadata, DataSource, PagedResult} from '../../lib/ng-crud-table';
import {Yarncolor} from './yarncolor;'

@Injectable({
  providedIn: 'root'
})
export class YarncolorService implements DataSource {

  WEB_API_SERVICE = 'http://localhost:22387/api/Yarn';

  constructor(private httpClient: HttpClient) {}

  getItems(requestMeta: RequestMetadata): Promise<PagedResult> {
    return this.httpClient.get<Yarncolor[]>(`${this.WEB_API_SERVICE}/YarnColors`)
      .toPromise()
      .then(this.extractData);
  }

  getItem(id: number): Promise<Yarncolor> {
    return this.httpClient.get<Yarncolor>(`${this.WEB_API_SERVICE}/api/?id=${id}`).toPromise();
  }

  post(yarncolor: Yarncolor): Promise<Yarncolor> {
    return this.httpClient.post<Yarncolor>(`${this.WEB_API_SERVICE}/CreateYarn`, yarncolor).toPromise();
  }

  put(yarncolor: Yarncolor): Promise<Yarncolor> {
    return this.httpClient.put<Yarncolor>(`${this.WEB_API_SERVICE}/${yarncolor.YarnColorID}`, yarncolor).toPromise();
  }

  delete(id: number): Promise<Yarncolor> {
    return this.httpClient.delete<Yarncolor>(`${this.WEB_API_SERVICE}/api/?id=${id}`).toPromise();
  }

  private extractData(res: any): PagedResult {
    const meta = {
      'totalCount': 10,
      'perPage': 10
    };
    const body = <PagedResult>{'items': res, '_meta': meta};
    return body;
  }

}

You can also inherit an existing class.
export class NewService extends YarncolorService implements DataSource

ERROR in src/app/demo/basic-demo.component.ts(36,69): error TS2345: Argument of type 'YarncolorService' is not assignable to parameter of type 'DataSource'.
Type 'YarncolorService' is missing the following properties from type 'DataSource': getItems, getItem, post, put, delete
src/app/virtual/virtual.component.ts(34,79): error TS2345: Argument of type 'YarncolorService' is not assignable to parameter of type 'DataSource'.


Fix the Indication message on Date Filter for Between

This PR was raised as requested by an User in the previous PR's comment.
https://github.com/webbingbrasil/filament-advancedfilter/pull/26#issuecomment-1638725241
I've made the change to deal the fix for the Indication message for the Between Filter. Kindly do a check before the merge.
Thanks

waiting for this to be merged

Will this work with filament v2?

This PR works on filament v2
The new version is v1.2.5


Container Registry VM Disks

The ContainerRegistryDisk feature is being proposed as an alpha feature. The Corresponding proposal for this pull request can be found here #310. The issue associated with these patches can be found here #315
NOTE: This feature shouldn't be seen as conflicting with the concepts proposed in #311. Once we have a long term strategy for how storage should be represented in KubeVirt, we may choose to revise the user facing parts of the ContainerRegistryDisk feature conform in a consistent way with respects to how we want KubeVirt represent storage in the VM definition. We are making no guarantees about backwards compatibility by introducing this alpha feature.
Overview
The ContainerRegistryDisk:v1alpha feature allows users to place VM disks in container images which can be stored in the container registry. From there, users can attach any number of disks stored in the container registry as local ephemeral storage for a VM.
For people familiar with AWS services, the pattern used here is very similar to AWS's instance store-backed AMIs
With this pattern VM disks are stored somewhere reliably on the network (In AWS's case this is S3, for KubeVirt this is the container registry) and pulled in as local ephemeral storage for VMs to consume at launch.
While the local data is not persistent between VM restarts, there are some advantages to using this pattern over persistent network block storage.

Resiliency: Active VMs continue to work despite an outage to the block storage service.
Simplicity: Reduced operational complexity. No block storage required. There are hidden costs organizations pay for each component introduced into a distributed system.

User Example
Place a bootable VM disk into the container registry
cat << END > DockerFile
FROM kubevirt.io:registry-disk-v1alpha
ADD fedora25.qcow2 /disk
END

docker build -t vmdisks/fedora25:latest .
docker push vmdisks/fedora25:latest

Attach VM disk as local ephemeral storage to a VM definition
cat << END > vm.yaml
apiVersion: kubevirt.io/v1alpha1
kind: VM
metadata:
  name: testvm-ephemeral
spec:
  domain:
    devices:
      disks:
      - type: ContainerRegistryDisk:v1alpha
        source:
          name: vmdisks/fedora25:devel
        target:
          dev: vda
      interfaces:
      - source:
          network: default
        type: network
    memory:
      unit: MB
      value: 2048
    os:
      type:
        os: hvm
    type: qemu
END

Launch the VM using the KubeVirt runtime
kubectl create -f vm.yaml

Testing
Manual Testing
In our vagrant dev environment this feature can be tested by posting the cluster/vm-ephemeral.yaml file to a cluster.  This VM definition attaches the VM disk placed in the cirros-registry-disk-demo:devel container image, which is pre-built during 'make vagrant-deploy'
cluster/kubectl create -f cluster/vm-ephemeral.yaml

Functional Testing
A new functional test is introduced to exercise the ContainerRegistryDisk feature. /tests/registry_disk_tests.go
Implementation Details

KubeVirt provides a base container that serves up VM disks as a iscsi network block device libvirt can consume. This base container is found in /cmd/registry-disk-v1alpha
Users push their VM disks into the container registry using the base image. An example of this is found in /images/cirros-registry-disk-demo
Users reference VM disks backed by the container registry with the ContainerRegistryDisk:v1alpha disk type when defining the VMs.
virt-controller searches the VM definition for ContainerRegistryDisk:v1alpha disks and places containers for each disk in the virt-launcher pod.
The virt-launcher pod is launched with the the container backed disks and readiness checks are performed to determine when the disks are accessible.
virt-controller places the VM on the node with the corresponding virt-launcher pod once all container disks' readiness checks pass.
When virt-handler is defining the domain xml for a VM spec, the ContainerRegistryDisk:v1alpha disk type is converted to iscsi network disk (pointing to the disks served up by the containers) automatically.
Anything the VM writes to the local ephemeral disks are destroyed when when the VM is torn down as a result of the virt-launcher pod being destroyed.

Future Work

I intentionally left out iscsi CHAP authentication from this initial pull request. If we decide to proceed with this feature, virt-controller should generate auth credentials automatically that ensure only the VM associated with the corresponding virt-controller pod can access the disks.
Read-Only disks.
More advanced functional tests need to be added that exercise failure conditions.
The initial feature set only includes support local ephemeral disks.  In the future we will consider the possibility of automating the dynamic provisioning of block storage for container registry disks for persistent storage. More thoughts on that can be found in this proposal. #311

No, i fundamentally disagree with making this a core component, and want to see the generic pluggable approach taken.

So @berrange , to summarise again, what has already been said: This PR does not in any way block thoughts in having a common layout for doing storage. If your idea gains traction, get's accepted and it makes sense to move this kind of plugin behind this then developed abstraction, we will do it.
Right now, this PR implements a very well described use-case in #310, which no one is questioning. Also the user-facing API is pretty much independent from any implementation details. Also everyone agrees that we don't need a perfect solution from the start, and that we can improve it.
Could you please also try to answer to the brought up arguments in the comments before too? If you have reasonable concerns, then we definitely should consider them.

There are some disagreements around the approach and implementation.
I share @berrange s concerns. But OTOH we also see support for this implementation.
KubeVirt is still in an early phase: In general I see us still in the situation where we need to conduct research in many areas, trying out different approaches, to finally end up with an optimal solution considering the constraints and requirements.
I'd like to see that we use this freedom and experiment and eventually fail. But I'm also confident that we get back on track after identifying mistakes or finding a better path.
Hence I'd go forward and get this PR merged but also expect motivation for follow up fixes once they become necessary.

It is already clear that we need a generic mechanism for handling dynamic storage - my PR has already outlined multiple scenarios in which it is useful. If the proposal I've made is not satisfactory then provide an alternative suggestion that enables a generic mechanism for dynamic storage which doesn't involve code changes in virt-handler/virt-controller for each storage type. The proposal I've made is simple & straightforward to implement & can easily be done in this PR instead of taking a short term hack to rush in a feature that is not time critical to merge

sigh... I understand your point of view Dan... At this point I'm pretty sure you understand where I'm coming from as well. I disagree the generic storage api has to be coupled with this PR (for reasons I've already sited multiple times)... and so the circle goes.
@berrange We're on the same team here. Please continue work on fleshing out and demonstrating the generic storage api so we can continue that discussion with you outside of this PR.  I think that's the way this is supposed to work. Someone makes a proposal that argues why a feature is necessary, they demonstrate the proposal with code, gain support/contributors, get merged... Holding another PR hostage to attempt to force someone else to demonstrate your proposal is not a solid plan for garnering support. I know that sounds harsh and isn't a perfect analogy, but I believe that is a fair representation of where this discussion is headed.
The project isn't going to fall apart while we iterate on storage techniques. I believe in your ideas. Go make them a reality so we can make awesome things together.

updated the patches to work with new client-go changes and fixed merge conflicts in the hack/default-config file

alrighty, I rebased the patches, addressed @admiyo comments, and included some new enhancements related to readiness checks.
I also added a registry disk for fedora atomic to the repo. Since the qcow2 image is around 700mb, I made this image optional.
To run fedora atomic with an ephemeral registry disk run the following
make vagrant-sync-optional
cluster/kubectl create -f cluster/vm-atomic.yaml

The atomic image is something I'm using to prove another patch series related to cloud-init that I'll be submitting a PR for soon.
If we're over the discussion phase on this feature, I'd encourage the team to merge this. It's about to start blocking other PRs.

patch updated to address @rmohr feedback. Includes controller unit test to exercise registry disk logic.

We also need to add the possibility to specify the pullPolicy per disk. Kubernetes support Always, IfNotPresent and Never. However, that is fine for me, if it is introduced later.

Good idea. I've noted that on the list of things I want to follow up on after this patch is merged.


Fix RichTextLabel not updating on theme/theme override change until text is updated.

Instead of actual font and font size, store default font type in the ItemFont to ensure the correct font is used when theme is changed, but text is not reshaped.

Thanks!


Support for vh/vw/cqw/cqh

Are there plans to add viewport and container query units for sizing?

Thanks for the question. This is not currently on our roadmap but we will consider it in the future.


not found:  no file libstd.so

environment: linux debian
buzz version : [0.2.0](https://github.com/buzz-language/buzz/releases/tag/0.2.0)

code  :
import "std";

| 👨🚀 buzz is a simple unambiguous scripting language
object Person {
    str name,
    int age = 18,

    fun growUp() > int {
        this.age = this.age + 1;

        return this.age;
    }
}

fun main([str] args) > void {
    Person me = Person{
        name = "Giann",
        age = 36,
    };

    print("Hello I'm {me.name} and I'm {me.age}.");
}

error
root@dmls:/tmp/buzz-0.2.0-linux-x86_64# ./bin/buzz test.buzz
std:4:58: Syntax error: External library `` not found:     no file `./libstd.so`
    no file `./std/src/libstd.so`
    no file `/usr/share/buzz/libstd.so`
    no file `/usr/share/buzz/std/src/libstd.so`
    no file `/usr/share/local/buzz/libstd.so`
    no file `/usr/share/local/buzz/std/src/libstd.so`
    no file `/tmp/buzz-0.2.0-linux-x86_64/lib/buzz/libstd.so`
    no file `/tmp/buzz-0.2.0-linux-x86_64/lib/buzz/std/src/libstd.so`

     3 | || @param message message printed if `condition` is false
     4 | export extern fun assert(bool condition, str message) > void;
                                                                ^
     5 |
test.buzz:1:13: Syntax error: Could not compile import or import external dynamic library `std`
     1 | import "std";
                   ^
     2 |
     3 | object Person {

but /tmp/buzz-0.2.0-linux-x86_64/lib/buzz/libstd.so this file exists
root@dmls:/tmp/buzz-0.2.0-linux-x86_64# ls /tmp/buzz-0.2.0-linux-x86_64/lib/buzz/libstd.so
/tmp/buzz-0.2.0-linux-x86_64/lib/buzz/libstd.so

I'll try to reproduce. In the meantime could you try to build buzz yourself following those instructions and see if that solves the problem?

I compiled from this machine and ran normally, but I packaged the compiled files on another machine

I found the cause of the problem. Here the std dependency was not found
root@VM-16-4-ubuntu:/tmp/buzz-test# ldd /tmp/buzz-test/lib/buzz/libstd.so
	linux-vdso.so.1 (0x00007fff08319000)
	/$LIB/libonion.so => /lib/x86_64-linux-gnu/libonion.so (0x00007f6c26c00000)
	libbuzz.so => /lib/libbuzz.so (0x00007f6c26a2e000)
	libos.so => not found
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6c26806000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f6c26d83000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6c26d1f000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f6c26790000)
	libmimalloc.so.2 => /lib/x86_64-linux-gnu/libmimalloc.so.2 (0x00007f6c2670a000)

Check on the machine where it was compiled again
root@dmls:/tmp/buzz-test# ldd lib/buzz/libstd.so
	linux-vdso.so.1 (0x00007ffe1d362000)
	libbuzz.so => /tmp/buzz/zig-cache/o/d21e7899da6ea71072e7dee90cb4c5ae/libbuzz.so (0x00007f4bd33c2000)
	libos.so => /tmp/buzz/zig-cache/o/30501b96cb97d5849e75a560d63f7b84/libos.so (0x00007f4bd327c000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4bd3000000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4bd35e8000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4bd2f8a000)
	libmimalloc.so.2 => /lib/x86_64-linux-gnu/libmimalloc.so.2 (0x00007f4bd2f04000)

There is a problem with the location of the dependency so file
If opening the so fails, it shouldn't tell you that the file doesn't exist.

Thanks for this. I'll remove the linux binary from the release for now.

Could you try again with the updated main branch? This commit should fix the issue

It's ready to run now


feat!: Add support for OTF format streams

Description
Some videos have formats that are a bit different than other ones, YouTube seems to refer to these as OTF. According to NewPipeExtractor (https://github.com/TeamNewPipe/NewPipeExtractor/blob/dev/extractor/src/main/java/org/schabi/newpipe/extractor/services/youtube/DeliveryType.java#L23-L38) these can occur on videos with low view counts and live stream replays that have just been reencoded to normal videos. Instead of allowing you to request arbitrary chunks with the range query parameter, instead you use the sq query parameter to request sequences, the first sequence (&sq=0) contains the duration of the sequences, so we need to request it while building the DASH manifest.
This implementation was inspired by the NewPipeExtractor implementation, so big thanks to them :).
Here is a video with OTF streams: https://www.youtube.com/watch?v=DJ8GQUNUXGM
The 720p and 360p streams are normal, the other ones (144p, 240p and 480p) are OTF streams
⚠ Breaking change ⚠
The toDash functions are now asynchronous, they return a Promise<string> instead of a string, as we need to fetch the first sequence while building the manifest.
Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

Okay so apparently videos with OTF streams have the dash url field populated, so we don't need to generate these manifests in YouTube.js.


Add diarization workflow to examples

Linked issue(s):
Fixes KOL-3666
What change does this PR introduce and why?
Adds diarization workflow to examples
Please check if the PR fulfills these requirements

[x] Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Relevant tests for the changes have been added
[ ] Relevant docs have been added / updated

All comments have been addressed, all that remains is to change LabeledTimeSegment -> TimeSegment

@billbai0102 to get CI green, you'll need to add Poetry project files for this example — also please include a README and add a bullet to the README in ./examples for speaker diarization. Feel free to DM me with questions

All comments have been addressed, should be ready to merge now.

May need a final linting.
Here's how the quickstart doc looks (zoomed out)


Add Browser compatibility to README

It would be extremely valuable to have the browser compatibility right within the README and DOCUMENTATION.
This will help users understand compatibility right away, and may also increase engagement of users downloading Amplitude.

Here is a good example of what it should look like:

Found it here: https://github.com/godban/browsers-support-badges/

This is what should be supported since everything revolves around the HTML5 audio element: https://www.w3schools.com/html/html5_audio.asp. Please test thoroughly and confirm for display.


App not unique per request.

I have developed an application using rendr and just noticed some strange behaviour under load.  After some testing I've discovered that it seems the App object is not unique per request and my bugs was caused by attaching state to the App, which seems to be globally unique.  My understanding was that it is suppose to be unique per request on the server side.  Unfortunately I can't remember where I saw that, but if my understanding is incorrect or if maybe this behaviour was changed from a previous version  it would be great if someone could clarify.
Thanks.

It should indeed be unique, to access it on the server you should be looking at the req.rendrApp which is unique per request.  However, it can be fairly simple to get the scope incorrect somewhere and have a reference to it somewhere that will make a singleton instance of the object.  I would suggest doing a quick dive through your code to make sure that isn't the case as that's the only time I've seen that issue.
Sorry for the slow response, I've been a bit sick as of late.  Hopefully, I'll be able to response a lot faster and help with any other problems you're having!

@efuquen were you able to resolve this issue?  Let me know if you still are having problems or need any additional help


Bifurcating soma

Hello,
I am trying to load this neuron (Which loads well on NEURON) but I get this error:
SomaError: Bifurcating soma

Any idea why?
C51A_scaled_exp.swc.zip

Because there is a soma bifurcation  at ID 4. Children are ID 5 and ID 171 (which is probably not expected)

Can I close this ?

I am trying to figure out a way to fix it. You can close it, but once I
will manage to find a solution I will post it here.
On Tue, Sep 11, 2018, 08:53 Benoit Coste<EMAIL_ADDRESS>wrote:

Can I close this ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BlueBrain/NeuroM/issues/714#issuecomment-420167191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIkUoRuBSIFFZ9JjASvdshvuMbBndu2iks5uZ13kgaJpZM4WasJD
.

My guess is that the bifurcation starting at ID 171 has an incorrect section type soma. You could change the type of each points of the branch to something else (axon or dendrite). You can find the mapping section type to their code here: http://www.neuronland.org/NLMorphologyConverter/MorphologyFormats/SWC/Spec.html


Enhancement request: Mouse Pointer Highlight to show when sharing in Teams

Description of the new feature / enhancement
I am using the Mouse Pointer Highlight option, but when I am sharing a specific window in Teams, it doesn't work.
Scenario when this would be used?
When using Teams to share the screen or a specific window.
Supporting information
No response

Are you sharing a single app or the whole screen?
/needinfo

Hi Aaron,
The issue only appears when sharing a specific Window in Teams.
When sharing the whole screen, the feature works fine.

Thank you for your answer.
I'm sorry this is something we can't fix as teams just records the window and not what we're drawing over it.


Migration Document: Groups.coffee

Description
This pull request has been created with a markdown document for the component "Groups.coffee" by reviewing the project task Migration Groups.coffee.
This is used to display the availability of group work within a module. Once the user click on the module, and directed to groups, if there are no group works available, it displays an message with an icon "No group work Enabled".
This enhance the efficency and it provides the detaild clearly.
This is component combination of groups.coffee and groups.tpl.html
Fixes # (issue)
No issues
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)
[x] Documentation (update or new)

How Has This Been Tested?
Created the file and previewed the document.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have requested a review from ... on the Pull Request

Hi Jayani ,  you have successfully identified the component and its ready to migrate


Pan and Zoom issues

I am having issues with pan and zoom. simple pan and zoom actions cause the map to disappear.

Hi @jmeurer986, what browser are you using ? I can't replicate this issue.

@jmeurer986 this should be resolved now after #2


Can you please release new versions?

You know, 6.1.3 and 6.2.2 of elasticsearch & kibana have already been released, so when can you release related sentinl plugins?

SENTINL development is based on best effort and contributions. 6.x versions are being worked on as you can see in other threads and branches. Feel free to join in testing anytime! Thanks.


[Bug]: Compress level

Installation Method
None
The Problem
The compress level selection goes from 1 to 9 instead of 1 to 4 previously and the pdf doesn't seem to change size whatever the compress level I select.

Version of Stirling-PDF
0.35.0
Last Working Version of Stirling-PDF
0.33.1
Page Where the Problem Occurred
https://stirlingpdf.io/compress-pdf
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
I have only tested on the demo stirlingpdf.io and I'm pretty sure it was working correctly in 0.33.1 but now in 0.35.0 it's broken.
Also when dragging a file over the tab the page stays dark with the text "Drop files anywhere to upload" instead of correctly adding the file (I can still interact with the buttons however). I can open another issue for this if needed.
Browsers Affected
Firefox, Chrome
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

Drag and drop will be patched today already have a fix for that
No need to make new issue

Can you send the docker logs of what it's doing for the compression? Will help figure out cause

Sorry just read you only tested on demo and hence can't grab logs

Sorry not at home at the moment but what I wanted to show is that when you choose the optimization level it should be from 1 to 4 as was previously and it's what written on the page. However now the dropdown menu shows from 1 to 9 and there isn't the text on the option 4 which was terrible for text images or something.

Yes correct the 1-4 needs changing to say 1-9 now, the backend compression logic has changed

For it not working, i believe it should work but it might be your PDF cant be compressed due to its structure, would love to see docker logs to investigate that side

I'll try again later when I can, thanks for your work 👍
I liked the indication of the compression level being too much to be able to read text images. So if it's still relevant it would be cool to have it back.

I tested again with another pdf and the compression worked, I was probably confused by the change of scale and used it on a pdf that was already compressed to some degree.


Add endpoint relationship and metrics tests in the e2e check list.

I and @dmsolr have been misguided in the #4570 process, we thought it is an influxdb storage change error, but it turns out, it is endpoint relationship entity id building codes issue.
We miss this test, so other storage tests passed, which mislead us.
Please add this into e2e too.

Endpoint dependency tests have been added.
https://github.com/apache/skywalking/blob/master/test/e2e-v2/cases/gateway/expected/dependency-endpoint.yml


Not working.

microsoft .net framework unhandled exception has occurred in your application the given key was not present in the dictionary
i have this error.
my fps config is something like this
{
"DllList": [],
"Priority": 3,
"MonitorNum": 0,
"CustomResY": 1080,
"CustomResX": 1920,
"FPSTarget": 120,
"UsePowerSave": false,
"StartMinimized": false,
"IsExclusiveFullscreen": false,
"UseCustomRes": false,
"Fullscreen": false,
"PopupWindow": false,
"AutoClose": false,
"AutoDisableVSync": true,
"AutoStart": false,
"GamePath": ""
}
if i edit game path to
{
"DllList": [],
"Priority": 3,
"MonitorNum": 0,
"CustomResY": 1080,
"CustomResX": 1920,
"FPSTarget": 120,
"UsePowerSave": false,
"StartMinimized": false,
"IsExclusiveFullscreen": false,
"UseCustomRes": false,
"Fullscreen": false,
"PopupWindow": false,
"AutoClose": false,
"AutoDisableVSync": true,
"AutoStart": false,
"GamePath": "E:\Genshin Impact\Genshin Impact Game\GenshinImpact.exe"
}
then it wont error but the game wont load.i run as admin.
it just blinking for some second then nothing happen.
i install genshin on C drive but i move to E drive.i manually set gamepath then nothing happen.no error but nothing happen.

Disable windows protection/antivirus or add program in whitelist
Download latest v2.1.1
Try again

broken .NET framework
or outdated unlocker version

reinstall official launcher and update your game path there


[stalk]Stalk does not include a part of nickname

If we stalk pingwindyktator we get below output:

12:25 < daniel1302> .stalk pingwindyktator
12:25 <@botpingwina> other nicks of pingwindyktator: {'stonoga', 'pingwindyktator', 'botpingwina_', 'botpingwina', 'pingwindyktator2'}

But if we stalk pingwin we dont get only question from bot :(

12:26 < daniel1302> .stalk pingwin
12:26 <@botpingwina> pingwin? what's that then?

That's how it had been designed. Please explain why it should behave like you described.

This is huge time saving option for the client so probably it's worth your effort.


Reproducing ReMixMatch + DARP + cRT on CIFAR-10

Thanks for the great work. I have a question regarding reproducing the results in table 6 in the supplementary material.
I was trying to reproduce the 79.7% bACC from ReMixMatch + DARP + cRT on CIFAR-10 with the imbalance ratio of 150. According to appendix E, I re-initialized the linear classifier and re-trained it for 20 epochs while freezing other parameters. The re-weighting loss I used is the standard re-weighting by frequency (your paper refers to the loss from [24], maybe mistaken?). The classifier was trained on the labeled dataset.
Other hyper-parameters are: SGD with a learning rate 0.1, momentum 0.9, and weight decay 0.0005. The learning rate of SGD decays by 0.01 at the 16th and 18th epoch.
Despite the random initialization, the best bACC I got is 76.94%. I wonder where I did wrong. Could you please share your implementation details for this experiment?
Thanks!

Thanks for your interest in our works!
It might be due to the different experimental setups that you have been tried and actually used in the experiments.
For helping to reproduce our results, the related codes are now updated (train_crt.py & run_crt.sh)
I hope that it will be helpful for your project.
Thanks!


Laravel 8.22.1 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v8.22.1 branch.
Before merging, you need to:

Checkout the shift-ci-v8.22.1 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:information_source: If you are running PHP 8 be sure to run composer update locally to ensure you have the proper versions of your dependencies to reflect your PHP 8 environment.

:information_source: If you are running PHP 8 be sure to run composer update locally to ensure you have the proper versions of your dependencies to reflect your PHP 8 environment.


The renderComponentIntoRoot component encountered an error while loading.

Describe the Bug with repro steps
When opening a large Logic App in the Preview Designer, get an error message and the Logic App will not open. The browser console provides a detailed message with fhe following: "Microsoft_Azure_EMA]  6:14:08 AM renderComponentIntoRoot ReactInternalComponentError: {"message":"Maximum call stack size exceeded","stack":"RangeError: Maximum call stack size exceeded"}"
Workflow JSON
Attached

Screenshots or Videos
Workflow.txt
Browser
Chrome
Additional context
No response

Hi @berellax, this issue was caused because the function to render the nodes in the workflow is getting recursively calling itself too many times, causing a crash. I looked at your workflow definition at it seems that the Switch ActionType node has some errors. Some action nodes inside have the same name as the case, resulting in trying to render itself a lot of time. Specifically, all the else cases of Create_Lead, Update_Contact and Update_Lead. I tried to rename those actions and it seems to work fine.

Create_Lead

Update_Contact

Update_Lead

After all the changes, this is the final result. You can see that the nodes have different names.
Please, if this is still happening after the changes, feel free to reopen and we can have a deeper dive of why its happening for you


⚠ Redacted has degraded performance

In 91955c4, Redacted ($RED) experienced degraded performance:

HTTP code: 200
Response time: 10722 ms

Resolved: Redacted performance has improved in 3afdada.


Always sets connection to nil when interrupted

Fixes #70
Updates detailed comment to explain why this is

I tested this branch against the scenario described in #70 and confirmed it now works as expected, the send in step 4 now succeeds.

@amomchilov for your review. It'd be beneficial reading through #70 first for context.

@amomchilov friendly ping if you have a few minutes to take a look


First step in updating to a new minimum Unity version

This change updates to Unity 2020.3.2f1, checks for 2020.3 on project load, removes the 2018.4 .net backend AR Foundation workaround and updates the package manifest.
Checking this in to a feature branch while we make the final call on the minimum Unity version for MRTK v3.

/azp run

/azp run

Looks like we need a Unity 2020.3 build on our CI systems

Are we going to make 2020 the new minimum supported version?

We are. Per #9597.

I will clean this PR up (merge latest and confirm that it builds correctly in 2020.3) and will merge into the feature branch this week

@davidkline-ms is this PR still relevant?

This is done. The v3 codebase has yet to be brought to github.


Pan and button head M3s will not work for the crossbar

Button head and pan head screws do not work with the crossbar. The bored out hole is too small.

I'm printing a 6.4mm wide hole now. That's two layers and should hopefully give plenty of clearance. I have button head screws here and will test.

Fixed in 0.9.8.


Nice work, its all going as expected.

Nice work, its all going as expected with new version and instantaneous values.
Now I just need to convince you to add PPV1 and PPV2 values ;)
Coordinator.py
                inverterdata.update({"Instantaneous Load": invertor["powerdata"]["ppv1"] + invertor["powerdata"]["ppv2"] + invertor["powerdata"]["pmeter_dc"] + invertor["powerdata"]["pbat"] + invertor["powerdata"]["pmeter_l1"] + invertor["powerdata"]["pmeter_l2"] + invertor["powerdata"]["pmeter_l3"] })
                inverterdata.update({"Instantaneous PPV1": invertor["powerdata"]["ppv1"]})
                inverterdata.update({"Instantaneous PPV2": invertor["powerdata"]["ppv2"]})
                self.data.update({invertor["sys_sn"]: inverterdata})

enums.py
    Load = "Instantaneous Load"
    PPV1 = "Instantaneous PPV1"
    PPV2 = "Instantaneous PPV2"

sensor.py
        key=AlphaESSNames.Load,
        name="Instantaneous Load",
        native_unit_of_measurement=POWER_WATT,
        device_class=SensorDeviceClass.POWER,
        state_class=SensorStateClass.MEASUREMENT,
    ),
        AlphaESSSensorDescription(
        key=AlphaESSNames.PPV1,
        name="Instantaneous PPV1",
        native_unit_of_measurement=POWER_WATT,
        device_class=SensorDeviceClass.POWER,
        state_class=SensorStateClass.MEASUREMENT,
    ),
        AlphaESSSensorDescription(
        key=AlphaESSNames.PPV2,
        name="Instantaneous PPV2",
        native_unit_of_measurement=POWER_WATT,
        device_class=SensorDeviceClass.POWER,
        state_class=SensorStateClass.MEASUREMENT,
    ),
]

Originally posted by @Spookster in https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/7#issuecomment-1233424049

Yes those should be simple to add.

Obviously useful for monitoring strings facing different directions, but another possible use could be to detect dirty panels for same-facing strings. I'm looking forward to this!
Are more of the parameters that are visible on the inverter's display (like voltages and currents) available to be retrieved this way?

These are a list of values that DasLetzEinhorn lists as returns from his add on. I would assume that they would be exposed in the same way.
What are the useful ones and why?
"ppv1": 1151,
"ppv2": 1302,
"ppv3": null,
"preal_l1": 362,
"preal_l2": 0,
"preal_l3": 0,
"pmeter_l1": -247,
"pmeter_l2": -84,
"pmeter_l3": 324,
"pmeter_dc": 926,
"soc": 86,
"factory_flag": 0,
"pbat": -1908.2,
"sva": 524,
"varac": 0,
"vardc": 0,
"ev1_power": 0,
"ev1_chgenergy_real": 0,
"ev1_mode": 0,
"ev2_power": 0,
"ev2_chgenergy_real": 0,
"ev2_mode": 0,
"ev3_power": 0,
"ev3_chgenergy_real": 0,
"ev3_mode": 0,
"ev4_power": 0,
"ev4_chgenergy_real": 0,
"ev4_mode": 0,
"poc_meter_l1": 0,
"poc_meter_l2": 0,
"poc_meter_l3": 0

I am no expert but this may shed some light:
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwj8_7PlrZL6AhUMJ8AKHdCFASEQFnoECAoQAQ&url=https%3A%2F%2Fcommunity.openenergymonitor.org%2Fuploads%2Fshort-url%2F2qysTQ2mAaEEctdEIHXuaaofYIQ.pdf&usg=AOvVaw3MQPnmteJ_orHO6ncd3C6Z
Not sure why there would be a ppv3 if we have only two MPPT controllers. I've noticed that the two string voltages go active quite some time before the MPPTs start making power at sunrise. Maybe handy for fault finding?
Something that I really miss (and I don't see it in the document linked above) is a simple flag to indicate when the Alpha is in UPS mode (it is indicated on the LCD display on my Smile-5). Neither the mobile apps nor the web app provide this. As most of my loads are on the essential load outputs, I don't notice when the grid fails, and it would be handy if I could get that info on Home Assistant. Is it perhaps captured in the InvWorkMode parameter?

@Spookster I've accepted your pull request and the latest version contains your code to show PPV1 and PPV2


MAINT: Increase minimal nibabel required version to 3.0.1

I think that this should help resolve CI errors in #76,#77, #78, etc.

our smriprep version also requires nibabel 3.0.0rc1. we may need to bump this up as well but i think there are changes to the way output spaces are handled in the new version.

Looks like I am getting some mysterious errors from nipype now. Anyone know these?

I think @josephmje is right. Will bump smriprep before the meeting today.

Solved via #83


Generate Bearer Token Script

Describe the solution you'd like
A quick python script that allows user to enter an email address and generate a bearer token. This will make it so much easier to test our backend API endpoints via Postman (especially the ones that require user authentication).
The python script should be able to be executed through a command like python gen_access_token.py<EMAIL_ADDRESS>If you want a Python script to parse Command Line Arguments, look into the argparse library
Additional context
Bearer token is an access token that is temporarily generated by firebase when a user is authenticated
Setup Instructions (what branch to work off of)
Run the following commands
git checkout nextjs
git pull origin nextjs
git checkout -b bearer-token-gen-script

FYI: If you are not able to immediately run git checkout nextjs make sure you commit your changes in the current branch or run git stash and then execute the above commands

Food for thought on the approach @augustochang:

Since it's more likely that you would know a user's email rather than a user's uid, you can have the script look up the uid of a given email account in Firebase
Given the uid of the email account in Firebase, you can then use firebase functions to generate the bearer token and output that. This script is to be executed strictly on the developer's terminal

Resources: https://firebase.google.com/docs/reference/admin/python/firebase_admin.auth
https://firebase.google.com/docs/reference/admin/python/firebase_admin
You'll need to do pip install firebase-admin


Bump up<EMAIL_ADDRESS>

Codecov Report

Merging #75 (97d49fd) into master (6bd0710) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 97d49fd differs from pull request most recent head 4eef9b3.

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


Is there a way to avoid using superValidate to create forms?

Is your feature request related to a problem? Please describe.
I dont want to bind my form components to any routes. Right now it sometimes requires a lot of coupling and props drilling for page-level data.form to reach form component
Describe the solution you'd like
I want to instantiate forms without using superValidate
Looking back at react-hook-form and vee-validate, they don't require me to use any server load function to instantiate the form. I understand that this is for accessibility for users with no javascript enabled, but is there any way to use forms just with javascript as I could do in React and other frameworks?

Prop drilling is avoided with svelte context

Prop drilling is avoided with svelte context Maybe context and SPA mode works for you?

Yeah, sorry, guess I haven't read the docs thoroughly. Thanks for letting me know! :)


add React to global scope

- Summary
Trying to port react components to be widgets but the bundles are not reasonable because I need to include react, prop types, immutable prop types, etc.
If it's accepted, I hope we have immutable js, immutable prop types and prop types too in the global scope

- Test plan

- Description for the changelog
Add React to global scope

- A picture of a cute animal (not mandatory but encouraged)

@talves @tech4him1 @Benaiah thoughts?

Deploy preview for cms-demo ready!
Built with commit 9bf488d50818e9ad3b0431686b15c25b5c406b9e
https://deploy-preview-1292--cms-demo.netlify.com

Seems like a Netlify issue caused the build failures, but a redeploy fixed it (though it isn't showing up in the checks here).

What does this solve that making react a peerDependencies not solve?

He's using the cms and the widget via script tag, so he'd need to include a second version of React separately.

Deploy preview for netlify-cms-www ready!
Built with commit f76f591cae5e5cdd8741c777498177dec5adacd3
https://deploy-preview-1292--netlify-cms-www.netlify.com

I think this needs more discussion.
Discussion (Globals):
I am wondering if at a minimum all the globals should go under window.CMS
Also, do we pollute the global CMS with each at that level or maybe use window.CMS.lib for example
Discussion (mono-repo):
When we convert to a mono-repo solution(2.0). This may be a mute point right now, but should be brought up for compatibility down the road.

Hmm.. should I edit to be CMS.* or just close it?

@ekoeryanto we may be able to get something merged in the short term. Can you rebase and squash this down to one commit?

Just trying with webpack ProvidePlugin,
I think it should be on CMS.* and window.CMS.*

Not sure that would be needed. I thought it supported the path location.

I don't see the end solution for the globals being consumed within webpack. I think there should be a core library that uses these as a peerDependencies. Are you trying to extend the CMS in a pure react app?

No, I'm even trying this in nuxtjs

@ekoeryanto if someone is using Webpack, they should be able to just import React and friends as peer dependencies. The global should only be needed for folks not using a bundler, Babel, etc. So Tony's just saying add React at window.CMS.lib.React.

Got the config for window.CMS.* as external, I think I should revert the last commit 😄
module.exports = {
  devtool: 'source-map',
  externals: {
    'netlify-cms': 'CMS',
    react: 'var CMS.React'
  },
  output: {
    library: 'FooWidget',
    libraryTarget: 'umd'
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        loader: 'source-map-loader',
        enforce: 'pre',
      },
      {
        test: /\.jsx?$/,
        loader: 'babel-loader',
      },
      {
        test: /\.css$/,
        loader: ['style-loader', 'css-loader'],
      },
    ],
  },
}

I hope it is accepted as I have to create netlify-cms-extended with this change to use in here
https://github.com/ekoeryanto/netlify-cms-widgets

I really think we only need to provide React - a widget can pull in the others if needed. @talves you agree or think differently?

@erquhart I am still not sure where @ekoeryanto is using the globals in the repo he linked. Can one of you point me to the code?

What if we make a separate build say it extended.js just like what i did here<EMAIL_ADDRESS>

@talves I've read facebook/prop-types#44 and the readme but as they are not on the global (window) scope, it's depend to the developer to follow the recommendation and include the prop-types or not, except there's a security reason to not include prop-type as external or peerDepedencies.
Also i seen cdn method on the readme, which means it's not a strict recommendation CMIIW.
I think it is more flexible.
if there is an disadvantage of this PR, let me know.

The disadvantage is writing all of this stuff to the global environment.
I'm thinking we publish an official lib from the Netlify org netlify-cms-lib, that would provide these globals for extensions. It would move to the monorepo once it's in place.
For right now I'm cool with publishing some dependencies to global scope under window.CMS.lib if @talves is, but we should document under Beta Features for now since we know it's suboptimal.
Sent with GitHawk

The disadvantage is writing all of this stuff to the global environment for all Netlify CMS installations.

it is my solution about that
https://github.com/ekoeryanto/netlify-cms/blob/extended/src/extended.js
https://github.com/ekoeryanto/netlify-cms/blob/fdb7b3aa4d0d7be4004de924a18b1a306c64ce60/webpack.prod.js#L11

I Just want to make sure anything in this global (CMS.lib) setup ONLY lasts until we split out the core and add the peer dependencies instead. This to me is really only solving a small part of the issue. Any references to methods should be exposed through the API not globals IMO. Later, rather than publishing the proposed extended build, the CMS will build a core library with peerDependencies and a full cms app like it does today and users can create their own "extended" cms using the core. So I am fine publishing this with a life-cycle of beta only until the core library is created.
@erquhart we should make sure to state that these globals will be deprecated prior to 2.0 release and are not supported. This should only be a solution for those who understand using externals and are willing to try to take it on to decrease their bundle size today rather than wait for 2.0.

Hello, I think I don't need it anymore, except you have a plan to (only) add React to the global scope.
I've found a way for reducing bundle with script tag method.
I created a starter here

Hmm that's a great approach, we should consider that for the main starter.

I think and planing to create the webpack starter too with that approach.
And I think about creating lerna starter for widget creator, too 🦀

We'll be sharing a bunch of libs for dependencies to use, but we need to determine the best approach. Closing.


BitmapFont producing incorrect values for ascent, descent, and cap height

I am loading a BitmapFont from png and fnt file (uploaded as a txt because of restrictions) like so:
public class SSCCE implements ApplicationAdapter{

  public static void main(String[] args) throws Throwable{
    new LwjglApplication(new SSCCE());
  }

  public void create(){
    BitmapFont font = new BitmapFont(Gdx.files.internal("cnc.fnt"), Gdx.files.internal("cnc.png"), false);
    System.out.println("Line Height: " + font.getLineHeight());
    System.out.println("Cap Height: " + font.getCapHeight());
    System.out.println("Ascent: " + font.getAscent());
    System.out.println("Descent: " + font.getDescent());
  }

  public void render(){}

}

The fnt file includes the following:

lineHeight=13
base=11
height=9 (on all characters)
yoffset=-2 (on all characters)

Issue 1: Incorrect getDescent
Expectation: According to the docs, getDescent() is described as "the distance from the bottom of the glyph that extends the lowest to the baseline. This number is negative". All characters have a -2 yoffset so are 2 pixels below the baseline, and I expect a descent of -2.
Result: font.getDescent() produces 0, which is incorrect. If I change all yoffsets from -2 to 2 font.getDescent() still produces 0.
Notes: This needed a few changes because of flip, and also because if all yoffsets are positive, then all glyphs are above the baseline and descent will be positive - therefore it cannot be initialised at 0.
Change L548 to: descent = Integer.MAX_VALUE;
Change L596 to: if (glyph.width > 0 && glyph.height > 0) descent = Math.min((flip ? 0 : glyph.height) + glyph.yoffset, descent);
Add Before L598: if(descent == Integer.MAX_VALUE) descent = 0;
With this change the docs should probably be clarified to say "This number is negative if the lowest glyph is below the baseline", or otherwise just don't implement the MAX_VALUE lines.
Edit: actually I was thinking about this a bit more and the fnt format seems to generally work with variables considering 0,0 to be in the top left with y down as positive. My yoffset maybe should be 2 not -2, and the above code might need a change. Either way its broken though.
Issue 2: Incorrect getCapHeight
Expectation: According to the docs, getCapHeight() is described as "the distance from the top of most uppercase characters to the baseline". Every character is height 9 and yoffset -2, so I expect a cap height of 7.
Result: font.getCapHeight() produces 9, which is incorrect.
Notes: I can see in the code that cap height does not incorporate yoffset at all. In most fonts capitals will always be at baseline, and my example file has 2 pixels of blank space below each character which arguably makes my configuration incorrect, but its not impossible for a font to exist with elaborate capitals (like cursives) that have details below the baseline requring a yoffset. Additionally I can see from the code that where the docs say "most uppercase characters" it should probably say "a typical uppercase character".
Issue 3: Incorrect getAscent
Expectation: According to the docs, getAscent() is described as "the distance from the cap height to the top of the tallest glyph". Every character is the same height, so my capitals are equal to the tallest glyphs, and I expect an ascent of 0.
Result: font.getAscent() produces 2, which is incorrect.
Notes: I can see in the code at L660 that ascent is actually calculated as:
ascent = baseLine - capHeight;
Which is the distance from the cap height to the top of the line. In this case, either:

The docs are correct. I don't think it's this because in most fonts, the capitals will be the tallest characters anyway, and therefore this value will very often just be 0.
The code is correct. I don't think it's this because then getAscent will no longer be the opposite of getDescent (i.e. calculating a distance within the height of the glyphs)
Both are incorrect, and it should be the difference between the top of lower case letters and the tallest character. (i.e the diff between xHeight and capHeight... I don't know maybe)

Related mini feature request:
getAscent and getDescent return (according to their current docs at least) vertical spacing within the glyph. It would be good to add something like:
getAscentBuffer(): return the distance between cap height or maybe the tallest glyph, and the top of the line (i.e. current behaviour of getAscent())
getDescentBuffer(): return the distance between the bottom of lowest glyph and the bottom of the line (i.e. opposite of above)
Version of LibGDX and/or relevant dependencies
Latest commit ac4c5331a2d646efcf0911c51964eff0e99ea31a
However, this appears to have been the case for a long time.
Affected platforms

[X] Android
[X] iOS (robovm)
[X] iOS (MOE)
[X] HTML/GWT
[X] Windows
[X] Linux
[X] MacOS

Noticed also, descent is having padBottom added to it incorrectly at L598. Since the docs say more negative means more descent, padBottom should be subtracted from descent, but it is being added.

N

not even the industrial adobe standard does define one: https://www.adobe.com/content/dam/acom/en/devnet/font/pdfs/5005.BDF_Spec.pdf

You are confusing Bitmap Distribution Format by Adobe with Bitmap Fonts by Angelcode, the latter being used by Libgdx. However even if that weren't the case, the y position of glyphs in the Adobe format is provided by VVECTOR, which provides the offset from origin (read, baseline). Since we have the rendering position from origin, the descent is whatever is below the origin line given the height of the glyph.

Issue 1: Incorrect getDescent
this is a bitmap font, and since the fnt-file does not contain a explicit value for descender, any calculated value is of questionable quality at best.

The descent in angelcode bitmap fonts are determined the same way. According to the bitmap font docs, "The yoffset gives the distance from the top of the cell height to the top of the character.", so since we have the position of the character in relation to the baseline (which is the bottom of the cell) and we have the height of the character, the descent is quite clearly the portion of the character that descends below the baseline.
I don't understand why this calculation is "questionable at best", or why you might think that libgdx's approach of [undocumented mystery calculation] is better.

Issue 2: Incorrect getCapHeight
9 is correct, again this is a bitmap font so the value is mostly irrelevent, but capital height is "base size"(11) minus "descender"(2) = 9

This makes no sense because:

Libgdx currently returns a descent of 0, not 2 (which is the value it should be according to my bug report).
It is actually being calculated as I already mentioned in the OP - as simply 9, which is the raw height of the glyphs, not taking into account their position relative to the baseline.

This value is certainly not irrelevant because it is being used when calculating the rendering position (Which it probably shouldn't be, since rendering according to "most uppercase characters" will inevitably be incorrect for characters which aren't "most")

Issue 3: Incorrect getAscent
same as issue 1

I don't understand this. The libgdx docs are clear that this is "the distance from the cap height to the top of the tallest glyph", which has nothing to do with issue 1.

I've started doing a big extremely breaking rewrite of all the font code. Given how breaking it is, I understand if it is never incorporated, but I'll still keep track here of other bugs I discover along the way.
First one, according to the docs:

info: This tag holds information on how the font was generated.

That line includes a "padding" field, and this padding is applied to the glyphs in BitmapFontData. It should not be doing this - just like the rest of the fields in the info line, the padding field is informational only, it describes the padding the exporter applied to the glyphs when it laid them out onto the texture(s). This can be double checked quite easily by playing with the padding fields in the exporter and examining the resulting layout in the png.

In BitmapFontData.setGlyphRegion, if the glyph turns out to be outside of the region bounds, then the code updates it's the position on the texture and also clips the glyph. It sets the new position by changing xoffset and yoffset when it should really be changing srcX and srcY. The offsets are data points used to describe how to position the glyph on the screen when rendering it, they are not related to how the glyph is positioned on the texture.


[5.5] Fix SQS Queue for PHP7.2

Simple fix for issue https://github.com/laravel/framework/issues/22373
Includes a test to prevent regression (this test fails on 7.2 without the fix).
I checked the Git history for this file. We can safely backport this fix all the way back to Laravel 5.1 if you want to backport PHP7.2 support to previous Laravel versions. Let me know, and I'll do PRs for the other versions for you.

Includes a test to prevent regression (this test fails on 7.2 without the fix).

Woho! ;)

+1 would love to get the fix for Laravel 5.4 as well :)

Only Laravel 5.5 LTS is supported.

@GrahamCampbell would it be possible to release this fix to illuminate/queue as well so Lumen could be patched too?
Thank you in advance for the consideration.

Thank you :fireworks:


called Option::unwrap() on a None value

Bug description
I was trying to run my API, with my database initially on Supabase. Later, I migrated it to Google Cloud using psql, pg_dump, and pg_restore. During the migration, my WiFi disconnected, causing some errors. I restarted the migration, which created duplicate data. Now, whenever I try to run it, I get this error. I thought reporting this might help improve Prisma.
How to reproduce

Migrate any existing database to another PostgreSQL DB
Disconnect the internet while migration and when it is adding the data
Try to migrate again to make duplicates
Run any findFirst() Prisma function

Expected behavior
thread 'tokio-runtime-worker' panicked at query-engine/core/src/interpreter/query_interpreters/nested_read.rs:229:50:
called Option::unwrap() on a None value
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
PrismaClientRustPanicError:
Invalid prisma.userSubscription.findFirst() invocation:
called Option::unwrap() on a None value
This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.
Prisma information

// Subscription model
model Subscription {
  id                Int                @id @default(autoincrement())
  name              String
  price             Int
  subscriptionType  SubscriptionType?
  isActive          Boolean            @default(true)
  duration          Int
  description       String?
  features          String[]
  userSubscriptions UserSubscription[]
  createdAt         DateTime           @default(now())
  updatedAt         DateTime           @updatedAt
}

// User subscription model
model UserSubscription {
  id             Int          @id @default(autoincrement())
  user           User         @relation(fields: [userUid], references: [uid], onDelete: Cascade)
  userUid        String
  subscription   Subscription @relation(fields: [subscriptionId], references: [id], onDelete: Cascade)
  subscriptionId Int
  startDate      DateTime
  endDate        DateTime
  createdAt      DateTime     @default(now())
}

const activeSubscription = await prisma.userSubscription.findFirst({
            where: {
                userUid,
                startDate: { lte: new Date() },  // Subscription started
                endDate: { gte: new Date() }     // Subscription hasn't ended
            },
            include: {
                subscription: true,
                user: true,
            }
        });

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v21.0.0

Prisma Version
prisma                  : 5.21.1
@prisma/client          : 5.19.1

Hi @HeyAvi, I see that you're using misaligned versions of Prisma. Can you please try upgrading @prisma/client to 5.21.1 (like prisma), and try again? Thanks.


drawings not made invisible when lighting is enabled

Description
the option to not disable the visuals of a drawing when you enable lighting effects
allowing the following

Context
ive been trying to use the drawing features youve added to make smoke clouds, but when enable the lighting settings for a drawing it turns off there visuals meaning you can no longer see the smoke cloud texture the drawing had examples below

lighting enabled smoke cloud not visible vision restricted by smoke cloud

lightning disable smoke cloud visible vision unrestricted by smoke cloud

two seperate drawings layered over each other allowing players to see the smoke cloud restricting there vision
i intended to use advanced drawing tools editiable polygons to make dynamic smoke clouds that used this module to restrict vision, two of my players are focused around vision denial one an opaque darkness generator and the other creates large moving smoke clouds, while i can still theoreticaly do this it requires me to copy the drawing so i have one for vision and for visual then delete one edit the main drawing and then copy again every time i alter the shape of the cloud
edit:
also is it possible to make a specific token not effected by a specfic vision restricting drawings as my players character can see through there own smoke/darkness but not each others

I wouldn't recommend to use lighting drawings for this. The reason is that, if you ever use other lighting drawings in your scene, the drawing of the smoke cloud will override the lighting (darkness level etc) defined by another drawing. So assume you have a lighting drawing with Darkness Level 1 for the interior in a building but outside the Darkness Level 0 (scene config); if you then spawn the drawing for the fog in the interior, then this drawing would override the Darkness Level to 0, which it inherits from the scene config, and would brighten the interior. For temporary vision limitation templates (or light sources if it is magical darkness) is the right choice. Templates are of course more limited shape-wise.
Another minor issue would be that drawings are rendered below tokens. So the token would appear to be above the smoke instead of in it.

im using vision limitation instead of darkness level so hopefully the darkness levels should bother me at all, ive played around with templates and they are to limited in shape and functionality to use, my players will be using the smoke from the start of battles to the end so its going to be all most permenant from round one to the end of the fights

is it to hard to add an option to not hide the drawing while enabled?

you are kidding me i refreshed so many times to check if the first one had posted then the moment i do the second one its there

I added a flag that makes the drawing visible in 4.1.9. There's UI for this setting at the moment, so you need to change it with a script macro. For example:
// Select drawing(s) and then execute this to make them visible
canvas.drawings.controlled.forEach(d => d.document.setFlag("perfect-vision", "visible", true))

Awesome thank you man i really appriciate it.


Fix invalid Python tests JSON file

cc @thunderboltsid

Isn't @thunderboltsid's change ready to be merged onto v1.0.x and going to contain this fix?

Oh - I missed the approval. Yep.


How to remove a failed node completely?

Is there a way to remove a failed node?
I've tried modifying the xml file both while the server is up and down but doesn't make a difference. Can't see an option for it unless I'm missing something.
Thanks

Check Readme.md. In order to replace a failed node you firstly have to make the controller detect the node as failed, send update return routes action or update neighbors To the failed node, controller status should said "node failed" once done, now use the controller action replace failed node and the controller will turn on inclusion and will assign the replaced nodeid to the new node added

Thanks, I should have read that first as I simply ploughed ahead and readded the nodes that fell out of sync. Now I have 2 nodeIDs which are effectively dead, so the only way to get shot of these is to wait until i have new devices to add?

@gazoscalvertos Yes. Actually some weired thing happens when removing devices in Openzwave, scan takes lot longer and all the systems seems to be slow down, If you have died nodes I suggest you to firstly exclude them from the controller.
The best thing you can do is to exclude all devices, hard reset the controller and add all them back.


[BUG] [ws-sbom-generator] Tool complains about missing extra config file, but no -e flag was passed

Bug Description
The tool complains about a missing extra configuration file, but I did not include -e to tell it to look for one.
Steps to Reproduce

Install Python version as directed.
Run the tool with any combination of flags except -e, for example: ws_sbom_generator -u <userKey> -k <apiKey>
Receive error:

sbom_generator: /Users/me/.pyenv/versions/3.9.13/lib/python3.9/site-packages/ws_sbom_generator/resources/sbom_extra.json configuration file was not found. Be sure to create a file in the following structure (-e/--extra):
            {
                "namespace": "http://CreatorWebsite/pathToSpdx/DocumentName-UUID",
                "org_name": "Organization Name",
                "org_email"<EMAIL_ADDRESS>                "person": "person name",
                "person_email"<EMAIL_ADDRESS>            }

Expected Behavior
Don't look for extra config file unless prompted with -e
Environment Details

OS: MacOS 12.5 (Monterey)
Version: https://github.com/whitesource-ps/ws-sbom-generator/commit/580d830defcce3f89fad8856c9758144711d7b8e

Hi @jesse-mend , are you sure there is an error?
It should appear as a warning and shouldn't affect a report creation.
Thanks,
PS Mend Team

Hi Natalya, it is a warning (does not block creation of the report) but it seems like an error for it to appear regardless of whether I set the flag or not. Thanks!


Maximum not always showing up correct in boxplot

In your Code-Pen I've changed the data to:
const boxplotData = {
  // define label tree
  labels: ["January", "February"],
  datasets: [
    {
      label: "Dataset 1",
      backgroundColor: "rgba(255,0,0,0.5)",
      borderColor: "red",
      borderWidth: 1,
      outlierColor: "#999999",
      padding: 10,
      itemRadius: 0,
      data: [
        {
          min: 1,
          q1: 2,
          median: 3,
          q3: 5.75,
          max: 15
        },
        {
          min: 1,
          q1: 2,
          median: 3,
          q3: 5.75,
          max: 8
        }
      ]
    }
  ]
};

The outcome: The right chart seems to have the correct bounds, the left chart stops under 12 (although the Maximum is set to 15). After some threshold the chart seems to see an "outlier". The Tooltip is correct though.
I expect the upper line to be at 15.

this is the expected default behavior. The whisker extend by default to +/- 1.5 * IQR
see also
https://github.com/sgratzl/chartjs-chart-boxplot/blob/220e2d7b3de91a73dfd9ca8cb8d5247682703769/src/data.ts#L116-L123

Thank you for clarifying and responding so quickly!


TimeValue is used, include the header file [phab:D1152]

Created by salguarnieri at 2016-11-11 22:56:04:

shahms accepted this revision at 2016-11-11 22:57:20

salguarnieri closed via commit ee585aeeec963398fb97c3fadcc9f682c211a4bb at 2016-11-11 22:58:31


Make the startup system in the ecs_guide example non-thread local

The ecs_guide example uses a thread local system as its example of a startup system and the comments seem to imply that that is necessary. I assume that's a hold over from an earlier version of the engine. This PR changes it to use a regular system.
I was helping someone and pointed them to this example for an explanation of startup systems and resources and they tried to use a thread local system as a result which lead to further confusion. There's already a dedicated example of thread local systems so I don't think removing this usage reduces the coverage of the example and I believe it makes it more likely people will do the right thing starting out.

Good call!


Issue #273: Change event consumer payload log to debug

Resolves #273 plus additional upstream changes not yet local.

Closing as was addressed upstream.


Adding ProxySQL Diamond Collector

Added ProxySQL Diamond Collector. Also added tox so the tests could be run with package dependencies.

 I forgot to add tox to travis. Will do after lunch.


fix: fix wf version bug with errored activities

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1708
#1707
#1706  👈 (View in Graphite)
#1695
main

How to use the Graphite Merge Queue
Add the label merge-queue to this PR to add it to the merge queue.
You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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


0.3.0

This updates the query behavior to be compatible with RDF.rb 0.3.4. It would be great if you'd pull and release it. It also relates to your issue #2.
I did add myself as an Author, but feel free to revoke this. I just want to get it out there so it can be used.
Thanks for doing it in the first place!

Thanks Gregg!


Raspotify doesn't show up as device after wifi reconnect

When wifi connection drops, naturally Raspotify dissappears as one of the Spotify devices, however, when wifi reconnects it still won't show up and it'll require a manual reboot to get it to work again.
Please fix this.

The latest version of librespot may address this as far as I can tell. Try updating your package to 0.11.1 and let me know if it doesn't work.

Unfortunately it doesn't seem to work. I've updated Raspotify, when it automatically started I could see it in Spotify, but when I manually disabled wifi and then enabled it again, it didn't attempt to reconnect. This is also clear from the log, which just shows the initial start-up (no mention of a reconnect).

sudo service raspotify status

raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-04-30 09:44:02 CEST; 3min 52s ago
Process: 1303 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 1300 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 1305 (librespot)
CGroup: /system.slice/raspotify.service
`-1305 /usr/bin/librespot --name La Universidad --backend alsa --bitrate 320 --disable-audio-cache --initial-volume 100 --username --password

Apr 30 09:44:02 osmc-Willoughby systemd[1]: Starting Raspotify...
Apr 30 09:44:02 osmc-Willoughby systemd[1]: Started Raspotify.
Apr 30 09:44:02 osmc-Willoughby librespot[1305]: INFO:librespot: librespot (raspotify) 59cff3d (2018-04-25). Built on 2018-04-30. Build ID: 7BHFeq2k
Apr 30 09:44:02 osmc-Willoughby librespot[1305]: INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-v5wd.ap.spotify.com:4070"
Apr 30 09:44:03 osmc-Willoughby librespot[1305]: INFO:librespot_core::session: Authenticated as "something" !
Apr 30 09:44:03 osmc-Willoughby librespot[1305]: INFO:librespot_core::session: Country: "BE"
Apr 30 09:44:03 osmc-Willoughby librespot[1305]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink


pull request for e2e test at 11/10/2016 03:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


updated intellij-idea-eap (2016.3,163.3094.26)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

@vladimirdolzhenko I've created dedicated cask for next release of IntelliJ IDEA - #2508
@fanquake I've reverted this commit in #2524


Scanning won't start with latest version

With current master, I can't get scanning to start anymore. Camera real time preview works, but when I click on "Start" button, nothing happens, and I get the following output on the console.
2024-01-05 00:30:25,423 [INFO] Camera stopped
[7:22:12.644468461] [6169]  INFO Camera camera.cpp:1033 configuring streams: (0) 2028x1520-BGR888 (1) 2028x1520-SGBRG12_CSI2P
[7:22:12.647651699] [6116]  INFO RPI vc4.cpp:565 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected sensor format: 2028x1520-SGBRG12_1X12 - Selected unicam format: 2028x1520-pGCC
2024-01-05 00:30:25,432 [INFO] Configuration successful!
2024-01-05 00:30:25,493 [INFO] Camera started
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.9/tkinter/__init__.py", line 1892, in __call__
    return self.func(*args)
  File "/home/janne/ALT-Scann8/ALT-Scann8-UserInterface.py", line 2047, in start_scan
    button_status_change_except(Start_btn, ScanOngoing)
  File "/home/janne/ALT-Scann8/ALT-Scann8-UserInterface.py", line 1031, in button_status_change_except
    if except_button != Free_btn:
NameError: name 'Free_btn' is not defined
2024-01-05 00:30:30,493 [WARNING] More than 6 sec. since last command: Forcing new frame event (frame 0).
2024-01-05 00:30:36,503 [WARNING] More than 6 sec. since last command: Forcing new frame event (frame 0).
2024-01-05 00:30:42,513 [WARNING] More than 6 sec. since last command: Forcing new frame event (frame 0).
2024-01-05 00:30:48,520 [WARNING] More than 6 sec. since last command: Forcing new frame event (frame 0).
2024-01-05 00:30:54,525 [WARNING] More than 6 sec. since last command: Forcing new frame event (frame 0).

I'm also running the latest Arduino code on the nano.

Issue should be fixed in current version (1.8.18).
It was caused by a recent change where the 'unlock reels' button was moved to the experimental area so that, if experimental mode was not allowed (via -x command line) a reference to the button somewhere else was causing the error. That reference is now protected by checking before if experimental is enabled.
However, I cannot access my scanner now, so please let me know if ti works before I close the issue.

Tested it and can't reproduce it anymore. Closing the issue.


Training on own dataset

Hello, I want to replace the dad dataset with my personal dataset. There are a few questions that I hope you can answer.
1.What is data['labels'] in DADDataset？
2.What is data['ID'] in DADDataset？What is data['labels'] in DADDataset？

Hello, thanks for checking out our repository.
Below are the information that you asked:
labels: One-hot video labels to indicate whether the video contains an accident, i.e., [0, 1] denotes positive (accident) and [1, 0] denotes negative (normal).
ID: The video name for current feature file.