Error building picom

Followed the instructions accordingly still getting this issue (Using PopOS 20.04 64-bit)
Here's a screenshot : https://ibb.co/jw46BSj
Getting error while building picom with meson
Run-time dependency libev found: NO (tried pkgconfig and cmake)
Run-time dependency xcb-glx found: NO (tried pkgconfig and cmake)
src/meson.build:31:1: ERROR: Dependency "xcb-glx" not found, tried pkgconfig and cmake

Here's the log file:
Build started at 2021-02-12T16:31:32.746944
Main binary: /usr/bin/python3
Build Options: -Dbuildtype=release
Python system: Linux
The Meson build system
Version: 0.53.2
Source dir: /home/niteshkumar/Downloads/picom
Build dir: /home/niteshkumar/Downloads/picom/build
Build type: native build
Project name: picom
Project version: 8
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.c -o /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe -pipe -D_FILE_OFFSET_BITS=64
Sanity check compile stdout:

-----
Sanity check compile stderr:

-----
Running test binary command: /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe
C compiler for the build machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the build machine: cc ld.bfd 2.34
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.c -o /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe -pipe -D_FILE_OFFSET_BITS=64
Sanity check compile stdout:

-----
Sanity check compile stderr:

-----
Running test binary command: /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe
C compiler for the host machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the host machine: cc ld.bfd 2.34
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: x86_64
Host machine cpu: x86_64
Target machine cpu family: x86_64
Target machine cpu: x86_64
Program git found: YES (/usr/bin/git)
Running command: /usr/bin/git rev-parse --short=5 HEAD
--- stdout ---
60eb0

--- stderr ---

Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp2d9g9uhp
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp2d9g9uhp/testfile.c -pipe -E -P -D_FILE_OFFSET_BITS=64 -P -O0 -std=c11

Code:

        #ifdef __has_include
         #if !__has_include("stdc-predef.h")
          #error "Header 'stdc-predef.h' could not be found"
         #endif
        #else
         #include <stdc-predef.h>
        #endif
Compiler stdout:

Compiler stderr:

Has header "stdc-predef.h" : YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wall

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wall: YES
meson.build:63: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wcast-function-type

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wcast-function-type: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wignored-qualifiers

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wignored-qualifiers: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wmissing-parameter-type

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wmissing-parameter-type: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wnonnull

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wnonnull: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wshadow

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wshadow: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-type-limits -Wtype-limits

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wno-type-limits -Wtype-limits: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wold-style-declaration

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wold-style-declaration: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Woverride-init

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Woverride-init: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wsign-compare

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wsign-compare: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wtype-limits

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wtype-limits: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wuninitialized

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wuninitialized: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wshift-negative-value

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wshift-negative-value: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wunused-but-set-parameter

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wunused-but-set-parameter: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wunused-parameter

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wunused-parameter: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wimplicit-fallthrough

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wimplicit-fallthrough: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-unknown-warning-option -Wunknown-warning-option

Code:
 int i;

Compiler stdout:

Compiler stderr:
 cc: error: unrecognized command line option '-Wunknown-warning-option'

Compiler for C supports arguments -Wno-unknown-warning-option -Wunknown-warning-option: NO
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-missing-braces -Wmissing-braces

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wno-missing-braces -Wmissing-braces: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wconversion

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wconversion: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wempty-body

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wempty-body: YES

Executing subproject test.h method meson

Project name: test.h
Project version: undefined
C compiler for the build machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the build machine: cc ld.bfd 2.34
C compiler for the host machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the host machine: cc ld.bfd 2.34
Build targets in project: 0
Subproject test.h finished.

Pkg-config binary for MachineChoice.HOST is not cached.
Pkg-config binary missing from cross or native file, or env var undefined.
Trying a default pkg-config fallback at pkg-config
Trying pkg-config binary pkg-config for machine MachineChoice.HOST at ['/usr/bin/pkg-config']
Found pkg-config: /usr/bin/pkg-config (0.29.1)
Determining dependency 'libev' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion libev` -> 1

CMake binary for MachineChoice.HOST is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Trying CMake binary cmake for machine MachineChoice.HOST at ['/usr/bin/cmake']
Found CMake: /usr/bin/cmake (3.16.3)
Extracting basic cmake information
Try CMake generator: auto
No CXXFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Failed to find a fortran compiler for CMake. This might cause CMake to fail.
Called `/usr/bin/cmake --trace-expand .` in /home/niteshkumar/Downloads/picom/build/meson-private/cmake_libev -> 0
  -- Module search paths:    ['/', '/opt', '/usr', '/usr/local']
  -- CMake root:             /usr/share/cmake-3.16
  -- CMake architectures:    ['i386-linux-gnu', 'x86_64-linux-gnu']
  -- CMake lib search paths: ['lib', 'lib32', 'lib64', 'libx32', 'share', 'lib/i386-linux-gnu', 'lib/x86_64-linux-gnu']
Preliminary CMake check failed. Aborting.
Run-time dependency libev found: NO (tried pkgconfig and cmake)
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lev -Wl,--end-group -Wl,--allow-shlib-undefined

Code:
 int main(void) { return 0; }
Compiler stdout:

Compiler stderr:

Library ev found: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lm -Wl,--end-group -Wl,--allow-shlib-undefined

Code:
 int main(void) { return 0; }
Compiler stdout:

Compiler stderr:

Library m found: YES
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'x11' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion x11` -> 0
1.6.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags x11` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11 --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lX11
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11 --libs` -> 0
-lX11
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0

Code:
 #include<stdio.h>

        int main(void) {
            printf("%ld\n", (long)(sizeof(void *)));
            return 0;
        };
Compiler stdout:

Compiler stderr:

Program stdout:

8

Program stderr:

Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 --print-search-dirs

Code:

Compiler stdout:
 install: /usr/lib/gcc/x86_64-linux-gnu/9/
programs: =/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/
libraries: =/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib/:/lib/x86_64-linux-gnu/9/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/9/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../:/lib/:/usr/lib/

Compiler stderr:

Run-time dependency x11 found: YES 1.6.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'x11-xcb' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion x11-xcb` -> 0
1.6.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags x11-xcb` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11-xcb --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lX11-xcb -lX11 -lxcb
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11-xcb --libs` -> 0
-lX11-xcb -lX11 -lxcb
Run-time dependency x11-xcb found: YES 1.6.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-renderutil' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-renderutil` -> 0
0.3.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-renderutil` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-renderutil --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-render-util -lxcb -lxcb-render
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-renderutil --libs` -> 0
-lxcb-render-util -lxcb -lxcb-render
Run-time dependency xcb-renderutil found: YES 0.3.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-image' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-image` -> 0
0.4.0
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-image` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-image --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-image -lxcb -lxcb-shm
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-image --libs` -> 0
-lxcb-image -lxcb -lxcb-shm
Run-time dependency xcb-image found: YES 0.4.0
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xext' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xext` -> 0
1.3.4
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xext` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xext --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lXext
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xext --libs` -> 0
-lXext
Run-time dependency xext found: YES 1.3.4
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'pixman-1' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion pixman-1` -> 0
0.38.4
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags pixman-1` -> 0
-I/usr/include/pixman-1
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config pixman-1 --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lpixman-1
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config pixman-1 --libs` -> 0
-lpixman-1
Run-time dependency pixman-1 found: YES 0.38.4
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-render' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-render` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-render` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-render --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-render
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-render --libs` -> 0
-lxcb-render
Run-time dependency xcb-render found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-damage' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-damage` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-damage` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-damage --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-damage
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-damage --libs` -> 0
-lxcb-damage
Run-time dependency xcb-damage found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-randr' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-randr` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-randr` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-randr --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-randr
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-randr --libs` -> 0
-lxcb-randr
Run-time dependency xcb-randr found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-sync' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-sync` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-sync` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-sync --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-sync
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-sync --libs` -> 0
-lxcb-sync
Run-time dependency xcb-sync found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-composite' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-composite` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-composite` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-composite --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-composite
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-composite --libs` -> 0
-lxcb-composite
Run-time dependency xcb-composite found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-shape' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-shape` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-shape` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-shape --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-shape
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-shape --libs` -> 0
-lxcb-shape
Run-time dependency xcb-shape found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-xinerama' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-xinerama` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-xinerama` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xinerama --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-xinerama
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xinerama --libs` -> 0
-lxcb-xinerama
Run-time dependency xcb-xinerama found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-xfixes' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-xfixes` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-xfixes` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xfixes --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-xfixes
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xfixes --libs` -> 0
-lxcb-xfixes
Run-time dependency xcb-xfixes found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-present' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-present` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-present` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-present --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-present
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-present --libs` -> 0
-lxcb-present
Run-time dependency xcb-present found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-glx' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-glx` -> 1

CMake binary for MachineChoice.HOST is cached.
Preliminary CMake check failed. Aborting.
Run-time dependency xcb-glx found: NO (tried pkgconfig and cmake)

src/meson.build:31:1: ERROR: Dependency "xcb-glx" not found, tried pkgconfig and cmake

Followed the instructions accordingly still getting this issue (Using PopOS 20.04 64-bit)
Here's a screenshot : https://ibb.co/jw46BSj
Getting error while building picom with meson
Run-time dependency libev found: NO (tried pkgconfig and cmake)
Run-time dependency xcb-glx found: NO (tried pkgconfig and cmake)
src/meson.build:31:1: ERROR: Dependency "xcb-glx" not found, tried pkgconfig and cmake

Here's the log file:
Build started at 2021-02-12T16:31:32.746944
Main binary: /usr/bin/python3
Build Options: -Dbuildtype=release
Python system: Linux
The Meson build system
Version: 0.53.2
Source dir: /home/niteshkumar/Downloads/picom
Build dir: /home/niteshkumar/Downloads/picom/build
Build type: native build
Project name: picom
Project version: 8
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.c -o /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe -pipe -D_FILE_OFFSET_BITS=64
Sanity check compile stdout:

-----
Sanity check compile stderr:

-----
Running test binary command: /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe
C compiler for the build machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the build machine: cc ld.bfd 2.34
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.c -o /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe -pipe -D_FILE_OFFSET_BITS=64
Sanity check compile stdout:

-----
Sanity check compile stderr:

-----
Running test binary command: /home/niteshkumar/Downloads/picom/build/meson-private/sanitycheckc.exe
C compiler for the host machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the host machine: cc ld.bfd 2.34
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: x86_64
Host machine cpu: x86_64
Target machine cpu family: x86_64
Target machine cpu: x86_64
Program git found: YES (/usr/bin/git)
Running command: /usr/bin/git rev-parse --short=5 HEAD
--- stdout ---
60eb0

--- stderr ---

Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp2d9g9uhp
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp2d9g9uhp/testfile.c -pipe -E -P -D_FILE_OFFSET_BITS=64 -P -O0 -std=c11

Code:

        #ifdef __has_include
         #if !__has_include("stdc-predef.h")
          #error "Header 'stdc-predef.h' could not be found"
         #endif
        #else
         #include <stdc-predef.h>
        #endif
Compiler stdout:

Compiler stderr:

Has header "stdc-predef.h" : YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5ge5hghg/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wall

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wall: YES
meson.build:63: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpme3h8rkk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wcast-function-type

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wcast-function-type: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpqw2f4ikk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wignored-qualifiers

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wignored-qualifiers: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpx4c35vwk/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wmissing-parameter-type

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wmissing-parameter-type: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp914cdyce/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wnonnull

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wnonnull: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpt2qkbvqr/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wshadow

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wshadow: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpu2l64cxp/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-type-limits -Wtype-limits

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wno-type-limits -Wtype-limits: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5dpd5zw7/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wold-style-declaration

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wold-style-declaration: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp_c45njjv/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Woverride-init

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Woverride-init: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp4jxcj4i6/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wsign-compare

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wsign-compare: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmph8ioy1_o/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wtype-limits

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wtype-limits: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpbchaenhz/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wuninitialized

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wuninitialized: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmppqxm3jj2/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wshift-negative-value

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wshift-negative-value: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpvjb3wesx/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wunused-but-set-parameter

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wunused-but-set-parameter: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp85z9mwfl/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wunused-parameter

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wunused-parameter: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpgtp88al3/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wimplicit-fallthrough

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wimplicit-fallthrough: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpw3n25o5s/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-unknown-warning-option -Wunknown-warning-option

Code:
 int i;

Compiler stdout:

Compiler stderr:
 cc: error: unrecognized command line option '-Wunknown-warning-option'

Compiler for C supports arguments -Wno-unknown-warning-option -Wunknown-warning-option: NO
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmp5qlbzds7/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wno-missing-braces -Wmissing-braces

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wno-missing-braces -Wmissing-braces: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpcmu69v52/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wconversion

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wconversion: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpdpdprvan/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 -Wempty-body

Code:
 int i;

Compiler stdout:

Compiler stderr:

Compiler for C supports arguments -Wempty-body: YES

Executing subproject test.h method meson

Project name: test.h
Project version: undefined
C compiler for the build machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the build machine: cc ld.bfd 2.34
C compiler for the host machine: cc (gcc 9.3.0 "cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0")
C linker for the host machine: cc ld.bfd 2.34
Build targets in project: 0
Subproject test.h finished.

Pkg-config binary for MachineChoice.HOST is not cached.
Pkg-config binary missing from cross or native file, or env var undefined.
Trying a default pkg-config fallback at pkg-config
Trying pkg-config binary pkg-config for machine MachineChoice.HOST at ['/usr/bin/pkg-config']
Found pkg-config: /usr/bin/pkg-config (0.29.1)
Determining dependency 'libev' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion libev` -> 1

CMake binary for MachineChoice.HOST is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Trying CMake binary cmake for machine MachineChoice.HOST at ['/usr/bin/cmake']
Found CMake: /usr/bin/cmake (3.16.3)
Extracting basic cmake information
Try CMake generator: auto
No CXXFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Failed to find a fortran compiler for CMake. This might cause CMake to fail.
Called `/usr/bin/cmake --trace-expand .` in /home/niteshkumar/Downloads/picom/build/meson-private/cmake_libev -> 0
  -- Module search paths:    ['/', '/opt', '/usr', '/usr/local']
  -- CMake root:             /usr/share/cmake-3.16
  -- CMake architectures:    ['i386-linux-gnu', 'x86_64-linux-gnu']
  -- CMake lib search paths: ['lib', 'lib32', 'lib64', 'libx32', 'share', 'lib/i386-linux-gnu', 'lib/x86_64-linux-gnu']
Preliminary CMake check failed. Aborting.
Run-time dependency libev found: NO (tried pkgconfig and cmake)
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpkzrbjlyg/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lev -Wl,--end-group -Wl,--allow-shlib-undefined

Code:
 int main(void) { return 0; }
Compiler stdout:

Compiler stderr:

Library ev found: YES
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpx1faq_wq/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lm -Wl,--end-group -Wl,--allow-shlib-undefined

Code:
 int main(void) { return 0; }
Compiler stdout:

Compiler stderr:

Library m found: YES
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'x11' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion x11` -> 0
1.6.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags x11` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11 --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lX11
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11 --libs` -> 0
-lX11
Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpzgowsza8/output.exe -pipe -D_FILE_OFFSET_BITS=64 -O0

Code:
 #include<stdio.h>

        int main(void) {
            printf("%ld\n", (long)(sizeof(void *)));
            return 0;
        };
Compiler stdout:

Compiler stderr:

Program stdout:

8

Program stderr:

Running compile:
Working directory:  /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj
Command line:  cc /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj/testfile.c -o /home/niteshkumar/Downloads/picom/build/meson-private/tmpzi0g17pj/output.obj -pipe -c -D_FILE_OFFSET_BITS=64 -O0 --print-search-dirs

Code:

Compiler stdout:
 install: /usr/lib/gcc/x86_64-linux-gnu/9/
programs: =/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/
libraries: =/usr/lib/gcc/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/9/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib/:/lib/x86_64-linux-gnu/9/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/9/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/lib/:/usr/lib/gcc/x86_64-linux-gnu/9/../../../:/lib/:/usr/lib/

Compiler stderr:

Run-time dependency x11 found: YES 1.6.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'x11-xcb' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion x11-xcb` -> 0
1.6.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags x11-xcb` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11-xcb --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lX11-xcb -lX11 -lxcb
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config x11-xcb --libs` -> 0
-lX11-xcb -lX11 -lxcb
Run-time dependency x11-xcb found: YES 1.6.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-renderutil' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-renderutil` -> 0
0.3.9
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-renderutil` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-renderutil --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-render-util -lxcb -lxcb-render
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-renderutil --libs` -> 0
-lxcb-render-util -lxcb -lxcb-render
Run-time dependency xcb-renderutil found: YES 0.3.9
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-image' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-image` -> 0
0.4.0
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-image` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-image --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-image -lxcb -lxcb-shm
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-image --libs` -> 0
-lxcb-image -lxcb -lxcb-shm
Run-time dependency xcb-image found: YES 0.4.0
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xext' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xext` -> 0
1.3.4
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xext` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xext --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lXext
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xext --libs` -> 0
-lXext
Run-time dependency xext found: YES 1.3.4
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'pixman-1' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion pixman-1` -> 0
0.38.4
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags pixman-1` -> 0
-I/usr/include/pixman-1
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config pixman-1 --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lpixman-1
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config pixman-1 --libs` -> 0
-lpixman-1
Run-time dependency pixman-1 found: YES 0.38.4
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-render' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-render` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-render` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-render --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-render
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-render --libs` -> 0
-lxcb-render
Run-time dependency xcb-render found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-damage' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-damage` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-damage` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-damage --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-damage
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-damage --libs` -> 0
-lxcb-damage
Run-time dependency xcb-damage found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-randr' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-randr` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-randr` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-randr --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-randr
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-randr --libs` -> 0
-lxcb-randr
Run-time dependency xcb-randr found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-sync' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-sync` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-sync` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-sync --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-sync
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-sync --libs` -> 0
-lxcb-sync
Run-time dependency xcb-sync found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-composite' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-composite` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-composite` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-composite --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-composite
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-composite --libs` -> 0
-lxcb-composite
Run-time dependency xcb-composite found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-shape' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-shape` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-shape` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-shape --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-shape
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-shape --libs` -> 0
-lxcb-shape
Run-time dependency xcb-shape found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-xinerama' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-xinerama` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-xinerama` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xinerama --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-xinerama
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xinerama --libs` -> 0
-lxcb-xinerama
Run-time dependency xcb-xinerama found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-xfixes' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-xfixes` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-xfixes` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xfixes --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-xfixes
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-xfixes --libs` -> 0
-lxcb-xfixes
Run-time dependency xcb-xfixes found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-present' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-present` -> 0
1.14
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags xcb-present` -> 0

PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-present --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lxcb-present
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config xcb-present --libs` -> 0
-lxcb-present
Run-time dependency xcb-present found: YES 1.14
Pkg-config binary for MachineChoice.HOST is cached.
Determining dependency 'xcb-glx' with pkg-config executable '/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion xcb-glx` -> 1

CMake binary for MachineChoice.HOST is cached.
Preliminary CMake check failed. Aborting.
Run-time dependency xcb-glx found: NO (tried pkgconfig and cmake)

src/meson.build:31:1: ERROR: Dependency "xcb-glx" not found, tried pkgconfig and cmake

Solved. just had to install. libxcb-glx0-dev


Do not override set vars with falsy values

Related to this PR on dotenv project, could you implement the same in this project?
https://github.com/dotenvx/dotenvx/blob/f1fc7609fb54fea558d6f974a7d393913cf98488/src/lib/helpers/inject.js#L6-L14

good catch. working on the failing test and then the patch.

https://github.com/dotenvx/dotenvx/pull/177

released as v0.33.1


[Bug]: Page scrolling when space bar is pressed

Is there an existing issue for this?

[X] I have searched the existing issues and checked the recent builds/commits of both this extension and the webui

What happened?
When the space bar is pressed, the page starts to scroll down. Zooming and panning is not possible.
Steps to reproduce the problem

Press space bar

What should have happened?
Possibility to zoom and pan
Commit where the problem happens
webui: SD:next / automatic Version: c0a824d8 Mon Jun 5 10:32:08 2023 -0400
controlnet: v1.1.217
openpose-editor: v0.0.11?
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
--listen --insecure --theme=dark --disable-queue

Console logs
n/a

Browser logs
n/a
Additional information
I want to point out, that the model box is not very well implemented. The overflow of the box makes navigating difficult.
The correct way would be to have a page centered box, that adjust itself in height and inside that the iframe with 100% height.

I am going to reconsider keybinding if at least 1 other user report the same problem with SPACE key.

So ... I'm maybe doomed to not be able to use this ... ?! 😧

I suspect it might be related to firefox? I will test it on firefox later today trying to reproduce it. If I cannot reproduce it, I cannot fix it. The fallback would be change the keybinding, which can be a little bit distrubing.

Unfortunately I have no other browser installed. 😔
All I can say, is, that it is a new profile with almost no extensions or ad blockers, stricktly for SD.
The problem with the space bar in web browser is probably the reason, why canvas-zoom did not used it and chose another key. 😐

Bug confirmed on Firefox.

Will fix on next release.

Well, the bug not only happens on firefox. It happens on all platforms. If you enter the iframe and directly press space (without doing another other interactions such as click on frame), the browser seems to resend the previous frame message to the iframe, which will cause the editor clear the canvas and redraw everything.

https://stackoverflow.com/questions/369026/setting-focus-to-iframe-contents
Potential solution.
Need to fix on ControlNet side.

Fixed.

Cool! Will check ASAP.

Are you sure you have the controlnet side patch installed? Need controlnet version 1.1.220+.
Can you share a screenshot of modal overlapping as well?

Yes, CN it the latest v1.1.220

The UI seems ok in my perspective. Also, when you press space, the iframe scrolls or the main frame a1111 scrolls? Is there a specific sequence of operations to reproduce the scroll?

Chinese display error, the text is some symbols

If you already have the correction in mind, I am happy to merge your PR in ControlNet repo. The modal code is mostly generated by ChatGPT and I stop iterating when the appearnce satisfies my need.
I guess if I cannot reproduce the issue, I will just add another alt keybinding to panning, make it possible to pan using both SPACE key and F key.

Chinese display error, the text is some symbols

Can you submit separate issue and attach some screenshots?

Pan with key F enabled in v0.0.17. You can try whether key F is working for you now.

Is F + mousewheel scroll used to zoom?

Modal style fixed in https://github.com/Mikubill/sd-webui-controlnet/pull/1623.

Great! 👍
Is a update sufficient or do we also need to download the dist folder ... ?

Great! 👍 Is a update sufficient or do we also need to download the dist folder ... ?

This change is on ControlNet extension so all you need to do is to update the ControlNet extension. So the autoupdate script is not working for you? You can check the version by inspecting dist/version.txt. When you update the repo the dist directory will not update. It will be updated when you launch the WebUI.
If you meet any difficulties on the autoupdate feature (Other than network issue with Github), I would encourage you file a new issue for it.

BTW, recent updates of the editor solved a major problem in v0.1.0+, which allows you to scale/rotate grouped objects. I strongly encourage you to update if you have not done so.


Sidecar-injector TLS handshake error when using Istio mTLS

In what area(s)?

/area sidecar-injector
What version of Dapr?

0.4
Description
I'm trying to use Dapr alongside Istio service mesh, but I'm having problem with Dapr's sidecar injector as it doesn't work as expected. When my isito mTLS is enabled I get the error below as I apply a new deployment with dapr.io/enabled: "true". Although it works fine with istio's mTLS disabled.
time="2020-02-24T21:43:43Z" level=info msg="log level set to: info"
time="2020-02-24T21:43:43Z" level=info msg="starting Dapr Sidecar Injector -- version 0.4.0 -- commit v0.3.0-rc.0-73-ga1e270f-dirty"
time="2020-02-24T21:43:44Z" level=info msg="Sidecar injector is listening on :4000, patching Dapr-enabled pods"
2020/02/24 21:44:02 http: TLS handshake error from <IP_ADDRESS>:43092: EOF

Any suggestions on what I'm missing or if I have configuration conflicts between Istio service mesh and Dapr ?
Steps to Reproduce the Problem

Initialize isito with mTLS enabled on istio-system namesapce
Install dapr with helm on dapr-system namesapce
Create a new Deployment with dapr.io enabled
Check out dapr-sidecar-injector logs

Hey @maminio, if using Istio and Dapr, you should disable mTLS on either Istio or Dapr.
You also need to make sure Istio is not enabled on the dapr-system namespace.
In order to disable mTLS on Dapr, edit the default Dapr configuration and set mTLS to false.
kubectl edit configurations default -n dapr-system

Next, restart your pods for the change to take effect.
More info here.
Please keep us updated, and glad to hear it works when Istio's mTLS is turned off - this is the way to go. (have either Istio or Dapr do mTLS).

Thank you @yaron2,
Yes disabling mTLS in dapr-system worked and now sidecar injector works fine.
Although as I use mTLS for all of my connections it still has problem connecting to redis as Envoy blocks its connection.
For a way around:

I used mode: PERMISSIVE in my istio meshpolicy
Labelled dapr-system with istio-injection=enabled
Disabled dapr mTLS

I know using PERMISSIVE is not secure as it enables services to take both HTTP and mutual TLS traffic , that's why I'm looking to find a better way.

Great to hear it's working now @maminio, thanks for updating.
So to be clear, the issue now is how to get Istio to authenticate with Redis?
I'm not an Istio guru by any means, but I think you can use Istio authentication policies to achieve that.
More info here:
https://istio.io/faq/security/#auth-mix-and-match

Actually, more accurate:
https://istio.io/faq/security/#accessing-non-istio-services

Great!
Thanks, I configured istio DestinationRule to enable Dapr apis to pass through and it works fine now.

You can create these Destination rules as follow for dapr services.
I'm not sure that it is required for all of them by certainly you need it for dapr-sidecar-injector and dapr-api.
# For Dapr sidecar injector
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
 name: "dapr-sidecar-injector"
spec:
 host: "dapr-sidecar-injector.dapr-system.svc.cluster.local"
 trafficPolicy:
   tls:
     mode: DISABLE

# For Dapr-Api
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
 name: "dapr-api"
spec:
 host: "dapr-api.dapr-system.svc.cluster.local"
 trafficPolicy:
   tls:
     mode: DISABLE

If you installed dapr in a different namespace other than dapr-system, make sure to change the host value.

I am using Actors with Redis as a actor state store
then you need to disable mtls for redius as well
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
 name: "redis-disable-mtls"
spec:
 host: "*.redis.svc.cluster.local"
 trafficPolicy:
   tls:
     mode: DISABLE


Sharing Entire Window is Malfunctioning

Description
The sharing screen of other windows is working fine. But when I switch back and forth to close or reopen the screen sharing snippet, it gets broken and PC gets hanged.
Current behavior
Unable to share window (or the tab) in which the meeting tab (link) is opened in the browser.

Expected Behavior-
Should share the screen of itself (same tab in which it is opened) without getting broke. It should share entire windows.
Possible Solution
should stop sharing itself (or calling itself) like console.log(console) in JS.
Steps to reproduce
Environment details
Debian 4.19.67-2  x86_64 GNU/Linux
Mozilla Firefox 75.0

This repository is for Jitsi Desktop, the legacy chat and VoIP client.
In general, please discuss issues in the community forums first before opening bugs on GitHub. If it is confirmed there, the proper repository for Jitsi Meet is here: https://github.com/jitsi/jitsi-meet


Provide a grouping rule for ruff formatter conflicting rules

Ruff warns these rules conflict with the formatter, would be nice if we could disable these in a single line then need to disable one by one:
  "COM812", # conflicts with formatter
  "COM819", # conflicts with formatter
  "E501", # conflicts with formatter
  "ISC001", # conflicts with formatter
  "Q000", # conflicts with formatter
  "Q001", # conflicts with formatter
  "Q002", # conflicts with formatter
  "Q003", # conflicts with formatter
  "W191", # conflicts with formatter

perhaps we could have rule FORM1 that would be an alias to all the rules conflicting with ruff formatter?

My use case: I currently include "ALL" rules and deactivate the few groups and rules I don't want or conflict with type-checkers or formatters.
I don't really care about superfluous or unused rules because Ruff is so darn fast.
This ends up being less maintenance for me to stay up to date with new rules. And it's easier to document with comments what we don't want or agree with.
But having a way to configure "ALL but rules conflicting with formatter" would be nice to simplify configs (and automatically stay up to date with formatter updates!). Bonus for including "rules obsoleted by, but but conflicting with formatter", although not needed for me.

#8196 removes the warnings for all but 2 rules, except if you changed the configuration for some of the potentially conflicting rules.

The latest release shipped a few improvements that should drastically reduce the warnings. Please take a look and comment on this issue if you think that  a dedicated grouping for conflicting rules would still be valuable and we'll reopen the issue.

As long as the number is greater than one, I think it would still be helpful. So I'm asking to reopen this.


Add map controls to the public map view

Zoom controls
Legends
Torque timeline
Layer selector
Searchbox
Odyssey controls
...

unify changes on design. The last ones are in "Public - Map - Comments : Not logged"


OperationBased codegen model with possible shapes

Hi
I just finished implementing #4272.
Here is explanation how the new code working:
Most of the changes are in OperationBasedModelGroupBuilder.kt
fun buildField,
I calculate all possible shapes (without shapes from GQLFragmentSpread field), filter out shapes that won't happened, and attached that information inside OperationField.
OperationField.toModelGroup(),

If there are more than one possible shape, the result IrModelGroup will be a polymorphic model group which consists of the followings classes:

AbstractionModel (generated as sealed interface)
ShapedModel (generated one class for one possible shape),
FallbackModel (for unknown __typename)

In fun toProperty, if the target field has more than one possible shape, the field's model type will be changed into AbstractionModel class.
When generating ShapedModel, I make nullable field become non-null field by evaluating whether field condition always true after considering shape's possible type.

TODO: Java codegen is currently not working because polymorphic adapter is not currently support in Java. I think I will ignore shape information in OperationField.toModelGroup() when target language = Java, and leave Java codegen untouched.

This will need to be behind an opt-in flag (codegenModels.set("operationBased2")) to avoid breaking all the users that currently rely on operationBased codegen
OK.

Given that Java doesn't have sealed interfaces neither exhaustive when statements, I'd say Java codegen is largely out of scope
OK

I think we'll need to clarify a bit what the expectations are in terms of codegen.
I would say it generates models according to interesting types (as I described here). Do you think inline fragment is more official word for my "interesting types"?

What would you say about adding a design-docs/operationBased2 (until we find a better name for the feature 😅 ) with a few example of queries and the expected (pseudo) generated code?
Yes, I would be really happy to do that.

This will need to be behind an opt-in flag (codegenModels.set("operationBased2")) to avoid breaking all the users that currently rely on operationBased codegen

Added.
@martinbonnin  I have revised code as your comments. If everything is ok, I will start on design-docs tomorrow.

@martinbonnin I have revised code as your comments. If everything is ok, I will start on design-docs tomorrow.

Thanks! Sorry I didn't have much time to look too much into this this week. Design docs and most importantly examples of how we want the codegen to work would be awesome as it's easier to read and discuss than the actual compiler implementation

Design doc added. But I will revise my code a bit as I described in comment.

@chalermpong what about nested fragments?
{
  node {
    ... on Animal {
      species
      ... on WarmBlooded {
        temperature
      }
      ... on Pet {
        name
      }
    }
  }
}

what do we want in that case?
class Data(val node: INode)
sealed interfaceINode(val onAnimal: OnAnimal?)
class AnimalNode(val onAnimal: OnAnimal)
class OtherNode(val onAnimal: OnAnimal?)

So far so good but should OnAnimal be a sealed interface too? If not then we're having the same issue where one has to check for null on WarmBlooded to determine what to do:
val animal = data.node.onAnimal

if (animal?.onWarmBlooded != null) {
  // do something
}
if (animal?.onPet != null) {
  // do something
}

Ideally we'd want something like this:
sealed interface IOnAnimal(val onWarmBlooded: OnWarmBlooded?, val onPet: OnPet?)
class OnWarmBloodedAnimal(val onWarmBlooded: OnWarmBlooded, val onPet: OnPet?)
class OnPetAnimal(val onWarmBlooded: OnWarmBlooded?, val onPet: OnPet)
class OnPetWarmBloodedAnimal(val onWarmBlooded: OnWarmBlooded, val onPet: OnPet)
class OnOtherAnimal(val onWarmBlooded: OnWarmBlooded, val onPet: OnPet)

So that we could do
val onAnimal = data.node.onAnimal

when (animal) {
  is OnWarmBloodedAnimal -> // do something
  is OnPetAnimal -> // do something
  is OnPetWarmBloodedAnimal -> // do something
  is OnOtherAnimal -> // do something
}

Writing all of this, sounds like it's a lot of noise. Is it ok to have "interfaces" for top level fields but not for nested fragments?

@martinbonnin First of all. Thank you for being patient with my issue. I think I am the only one who cannot use responseBased codegen and needs this feature.
For animal query in your previous comment, here is the current output code from operationBased2 model:
public data class Data(public val animal: IAnimal?)

// To shorten the code, I will skip val __typename: String which appears in every class
sealed interface IAnimal { val onAnimal: Animal.IOnAnimal }
data class WarmBloodedAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class PetAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class WarmBloodedPetAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class Animal(val onAnimal: IOnAnimal): IAnimal

public sealed interface IOnAnimal {
  val species: String,
  val onWarmBlooded: OnAnimal.OnWarmBlooded?,
   val onPet: OnAnimal.OnPet?
}
data class WarmBloodedOnAnimal(
  val species: String,
  val onWarmBlooded: OnAnimal.OnWarmBlooded,
  val onPet: OnAnimal.OnPet?
): IOnAnimal
data class PetOnAnimal(
  val species: String,
  val onWarmBlooded: OnAnimal.OnWarmBlooded?,
  val onPet: OnAnimal.OnPet,
): IOnAnimal
data class WarmBloodedPetOnAnimal(
  val species: String,
  val onWarmBlooded: OnAnimal.OnWarmBlooded,
  val onPet: OnAnimal.OnPet,
): IOnAnimal
data class OnAnimal(
  val species: String,
  val onWarmBlooded: OnWarmBlooded?,
  val onPet: OnPet?,
): IOnAnimal

So we can already do this...
when (val onAnimal = response.data!!.animal!!.onAnimal) {
   is TestOperation.Data.Animal.OnAnimal -> TODO()
   is TestOperation.Data.Animal.PetOnAnimal -> print(onAnimal.onPet.name)
   is TestOperation.Data.Animal.WarmBloodedOnAnimal -> TODO()
   is TestOperation.Data.Animal.WarmBloodedPetOnAnimal -> TODO()
}

For the current output code, I don't like IAnimal interface and its subclasses because they are all the same. It will do just fine with only data class Animal. Do you think I should revise this?
sealed interface IAnimal { val onAnimal: Animal.IOnAnimal }
data class WarmBloodedAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class PetAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class WarmBloodedPetAnimal(val onAnimal: Animal.IOnAnimal): IAnimal
data class Animal(val onAnimal: IOnAnimal): IAnimal

Now, let review animal query but this time using named fragment:
query TestOperation {
  animal {
    ... AnimalFragment
  }
}

fragment AnimalFragment on Animal {
  species
  ... on WarmBlooded {
    temperature
  }
  ... on Pet {
    name
  }
}

Here is the output code:
sealed interface IAnimal { val animalFragment: IAnimalFragment }
data class WarmBloodedAnimal(val animalFragment: IAnimalFragment): IAnimal
data class PetAnimal(val animalFragment: IAnimalFragment): IAnimal
data class WarmBloodedPetAnimal(val animalFragment: IAnimalFragment): IAnimal
data class Animal(val animalFragment: IAnimalFragment): IAnimal

sealed interface IAnimalFragment {
  val species: String
  val onWarmBlooded: AnimalFragment.OnWarmBlooded?
  val onPet: AnimalFragment.OnPet?
}
data class WarmBloodedAnimalFragment(
  val species: String,
  val onWarmBlooded: AnimalFragment.OnWarmBlooded,
  val onPet: AnimalFragment.OnPet?
): IAnimalFragment
data class PetAnimalFragment(
  val species: String,
  val onWarmBlooded: AnimalFragment.OnWarmBlooded?,
  val onPet: AnimalFragment.OnPet
): IAnimalFragment
data class WarmBloodedPetAnimalFragment(
  val species: String,
  val onWarmBlooded: AnimalFragment.OnWarmBlooded,
  val onPet: AnimalFragment.OnPet
): IAnimalFragment
data class AnimalFragment(
  val species: String,
  val onWarmBlooded: AnimalFragment.OnWarmBlooded?,
  val onPet: AnimalFragment.OnPet?
): IAnimalFragment

Again, I don't like IAnimal interface and its subclasses. This is why I want to filter out possible shapes from inline fragments inside fragment spread.

@martinbonnin I revised code. Now it's ready for review.

@chalermpong I created a follow up PR there https://github.com/chalermpong/apollo-kotlin/pull/1/files to investigate. I juste added an integration test that fails on a conflicting declaration. I'll keep investigating and push my work over there. Ultimately, I'll merge in your branch.

I've updated the follow up PR with a change that mostly keeps the Ir as-is. The general idea is to:

generate nodes for each field, inline fragment and fragment definition just like for operationBased models
each of these nodes tracks its parentTypes, that is all the inline fragments type conditions that were traversed to reach this node + the type of the field itself
when generating modelGroups, compute the shapes depending on synthetic fields parentTypes (it is renamed to buckets here to work without GQLSelection/Ast)
if there are more than 1 shape/bucket, generate several model groups. For different models, patch the properties depending on the possible types.

Thanks for the PR 💙


Offer ID

Once I've followed the above instructions, my Offer ID has not changed.  I'm attempting to upgrade from my free trial to a pay-as-you-go subscription and then to transfer the subscription ownership to our business lead per these instructions: https://docs.microsoft.com/en-us/azure/billing/billing-subscription-transfer
Those instructions say you must have a qualifying Offer ID in order to transfer, and I would expect that my Offer ID would change to MS-AZR-0003P since upgrading, but it is still MS-AZR-0044P. What step am I missing?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 31d284ec-efec-44b4-8582-47b5b44a1f73
Version Independent ID: 5be7927d-cf08-7438-ecfd-554a6928d122
Content: Upgrade your free Azure subscription to Pay-As-You-Go
Content Source: articles/billing/billing-upgrade-azure-subscription.md
Service: billing
GitHub Login: @jlian
Microsoft Alias: jlian

Hi @kate-davis, you're right, upgrading the subscription from Free Trial to Pay-As-You-Go doesn't immediately change the offer ID. The offer ID changes when either

You consume all the free credits ($200) that you got, or
It's been 30 days since you started the Free Trial

So, if you need to urgently transfer the subscription, I would recommend that you open a support ticket and request their help. If you'd like to do this yourself you can try to run down the credits quickly by provisioning an expensive VM (for example).
Clearly this undocumented behavior has caused a problem for you. I will be adding a note to this doc to call this out. Thank you for pointing out this gap.

Thanks @jlian, glad to know I was going down the right path.  Today is the 30th day of my Free Trial, so should I expect to see the Offer ID change tomorrow?

Yes, in that case you should definitely see the offer ID change in a day or two (at most).

Thanks for your quick response, @jlian.
@kate-davis
We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Hello all,
This is literally the only place I've found a useful explanation as to why my Free Offer is still considered as such, even though I upgraded to Pay-as-Go.
This behavior is crippling me as a business as with the Free Trial (even de facto it is not) offer, port 25 SMTP remains closed, with no option to request it to be opened.
It would've been nice if we had this information documented somewhere, before initiating the set up of all our VMs.

Hello all,
This is literally the only place I've found a useful explanation as to why my Free Offer is still considered as such, even though I upgraded to Pay-as-Go.
This behavior is crippling me as a business as with the Free Trial (even de facto it is not) offer, port 25 SMTP remains closed, with no option to request it to be opened.
It would've been nice if we had this information documented somewhere, before initiating the set up of all our VMs.

I have been bitten by the same issue, certain Free Trial limitations being applied after I have upgraded to Pay-as-You-Go (before the trial ended). It shouldn't have taken so much searching to find this information. This issue should be reopened and the documentation updated to reflect this edge case.
This page has details about the different Pay-As-You-Go offers. Reproduced below is the relevant section:
Category | Offer name | Quota ID | Offer number
Pay-As-You-Go | Pay-As-You-Go | PayAsYouGo_2014-09-01 | MS-AZR-0003P
Pay-As-You-Go | Free Trial | FreeTrial_2014-09-01 | MS-AZR-0044P

I have been bitten by the same issue, certain Free Trial limitations being applied after I have upgraded to Pay-as-You-Go (before the trial ended). It shouldn't have taken so much searching to find this information. This issue should be reopened and the documentation updated to reflect this edge case.
This page has details about the different Pay-As-You-Go offers. Reproduced below is the relevant section:
Category | Offer name | Quota ID | Offer number
Pay-As-You-Go | Pay-As-You-Go | PayAsYouGo_2014-09-01 | MS-AZR-0003P
Pay-As-You-Go | Free Trial | FreeTrial_2014-09-01 | MS-AZR-0044P

this behavior is confusing as hell. so now i can't buy a reservation until the trial expires, even if i'm not in the trial anymore. but to figure that out, i had to scavenge the internet and faqs for like half an hour. why would you limit customer choice this way?

This issue was opened night on three years ago, yet unfortunately continues to plague us to this day.

It is confusing and I toke about 1 hour to figer it out 😢.
In the reservation page, it prompts 'Subscription not eligible for purchase...Reservations discounts apply to the offer type: Pay-As-You-Go'.
And in the subscription page, the offer field value is 'Pay-As-You-Go'.


Props tuncated issue

Using docker latest image
><EMAIL_ADDRESS>start /usr/src/app
> node server.js

Connected to management console @ 10.x.1.253:7505
Connected to management console @ 10.x.1.61:7506
props truncated ROUTING_TABLE   192.168
props truncated ROUTING_TABLE   192.168
props truncated ROUTING_TABLE   192.168
props truncated ROUTING_TABLE   192.168
props truncated ROUTING_TABLE   192.168
props truncated ROUTING_TABLE   192.168

Maybe @KarlStraussberger can help with this.

Works as disigned. I don't know why the socket read returns before the end of the message but otherwise the application aborts in an exception.
It may be caused by openvpn itself because I observe similar issues in syslog as well. It can be a multithreading issue inside openvpn.

Hi
I am having this error again
TypeError: Cannot read property 'split' of undefined
    at client.procData (/usr/src/app/openvpn.js:107:53)
    at /usr/src/app/openvpn.js:60:16
    at Array.forEach (<anonymous>)
    at Socket.<anonymous> (/usr/src/app/openvpn.js:58:13)
    at Socket.emit (events.js:310:20)
    at addChunk (_stream_readable.js:286:12)
    at readableAddChunk (_stream_readable.js:268:9)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:186:23)```

Hi, i have the same issue
Attaching to openvpn-status
openvpn-status    |
openvpn-status    | ><EMAIL_ADDRESS>start /usr/src/app
openvpn-status    | > node server.js
openvpn-status    |
openvpn-status    | Connected to management console @ xxx.xxx.xxx.xxx:9994
openvpn-status    | props truncated ROUTING_TABLE       <IP_ADDRESS>
openvpn-status    | props truncated ROUTING_TABLE       <IP_ADDRESS>
Any hint?

On our side socket.read returns too early so the remaining details are added to the next call. I do not know why this happens and when it startet. I just managed to stabilize the script. Maybe somebody can see the error already.

thanks for reply, so openvpn responds too slow?

Maybe, as soon as we know the reason, we can think about a solution.

ok, thanks for your help


Openapi.yaml

Closes #46

I tried this out on the OpenAPI editor and /ping worked fine in the network tab, so I don't see why we need to change the ping route. The error looks to be application/json related, not networking.

Without the change I receive an error:
Undocumented | TypeError: Failed to fetch
I get the same for ofac (which hasn't been changed)
curl -X GET "http://localhost:8084/ping" -H "accept: /"

Code
Details

Undocumented
TypeError: Failed to fetch


Exception messages were not rendering well

Before:

After:

This primarily came down the ex.getMessage() not always returning a valid value.

Fixes https://github.com/OctopusDeploy/octopus-jenkins-plugin/issues/91


No module named 'datasets.tasks'

when running MMTEB, i got the error:
  File "/home/bo/.cache/huggingface/modules/datasets_modules/datasets/SpellOnYou--kor_sarcasm/0
0d38c200d4d563ed94efb9ff4ca119ded94fe3cdf1e381ed95274de0a9d59f0/kor_sarcasm.py", line 21, in <m
odule>
    from datasets.tasks import TextClassification
ModuleNotFoundError: No module named 'datasets.tasks'

The reason is in huggingface datasets 3.X, the tasks has been removed: https://github.com/huggingface/datasets/pull/6999
This affect some of the MMTEB datasets, such as https://huggingface.co/datasets/SpellOnYou/kor_sarcasm, the temp solution is to downgrade huggingface datasets to datasets==2.21.0 (the latest before 3.0).

I can reproduce the error. Added a specific fix here #1364
rerunning MTEB(Multilingual, beta) to see if there is other cases


replace 192 and 512 logos

These still look blurry and not sharp to me?

Are you sure? They're smallish images that shouldn't be blown up too much

Yeah but they should be as sharp as they can be at 512/192 px when blown up. It'll look equally good when downsampled to be smaller.


spyder-kernels problem version 5.0.0

on MACOS (macos big sur 11.2.3) previous versions worked smoothly but after updating to spyder 5.0.0  spyder‑kernels not working and cannot be installed using ( conda install spyder‑kernels OR pip install spyder‑kernels )
#ERROR Message :
You have missing dependencies!
Mandatory:
spyder_kernels >=2.0.1,<2.1.0 : 2.0.1 (NOK)
Please install them to avoid this message.
Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.
Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.

Hey @Shaimahameed, thanks for reporting. Sorry for this problem, it was a mistake on our side and you can safely ignore it.
It'll be fixed in our next version, to be released in a couple of days.

@ccordoba12  thank you for the fast reply i'll be waiting

Hi @ccordoba12

Hey @Shaimahameed, thanks for reporting. Sorry for this problem, it was a mistake on our side and you can safely ignore that message.
It'll be fixed in our next version, to be released in a couple of days.

I just want to report I have the same issue on Windows 10 + Python 3.9.3.
But as you described I ignore the message and Spyder does not complain and I can work!
If I restart the Spyder I get the error message again!
Thank you for your efforts.

Same issue in Windows 10 + Python 3.8.9. I also have spyder-kernels 2.0.1 installed, all via pip.

in your file "\Lib\site-packages\spyder\dependencies.py", change line 66
from
SPYDER_KERNELS_REQVER = '>=2.0.1,<2.1.0'
to
SPYDER_KERNELS_REQVER = '>=2.0.1;<2.1.0'
and it will be fine

For Linux, assuming that you have done a local installation, follow the advice of @stonebig but in this directory:
$HOME/.local/lib/python/site-packages/spyder/

I wonder how that wasn't noticed during testing before the release.

there are integration bugs "with the user" that CI don't/can't catch, it's very frequent.

there are integration bugs "with the user" that CI don't/can't catch, it's very frequent.

I would definitely be kind of nervous before a big release like 5.0.0 and start up spyder once before releasing. Especially if I merged some bots translation files. Although I can see how the issue happened.

The army of unpaid volunteers missed something between the 2 packages.  Maybe that file was edited weeks ago.  Distractions like real life happen.  I've commited the same sin in another set of github projects and so has other members of my organisation.

For Linux using pip, assuming that you have done a local installation, follow the advice of @stonebig but in this directory:
$HOME/.local/lib/python<VERSION>/site-packages/spyder/

and on macOS where is it ?
I installed Spyder 5 on a local basis but can't find this file. I found a lot of dependencies.py files (in users/opt/anaconda3) so I suppose they are from my previous installation with anaconda.
I also tried to find it in .lib/site-packages but can't find Spyder root after
Thx for your help.

in your file "\Lib\site-packages\spyder\dependencies.py", change line 66
from
SPYDER_KERNELS_REQVER = '>=2.0.1,<2.1.0'
to
SPYDER_KERNELS_REQVER = '>=2.0.1;<2.1.0'
and it will be fine

@stonebig after applying the above correction I get the new error as below (Windows 10 + Python 3.9.3)
\lib\site-packages\setuptools\distutils_patch.py:25: UserWarning: Distutils was imported before Setuptools. This usage is
discouraged and may exhibit undesirable behaviors or errors. Please use Setuptools' objects directly or at least import
Setuptools first.
 warnings.warn(

@stonebig after applying the above correction I get the new error as below (Windows 10 + Python 3.9.3)
\lib\site-packages\setuptools\distutils_patch.py:25: UserWarning: Distutils was imported before Setuptools.

Do you have the newest version for these packages? That can lead to errors.

Do you have the newest version for these packages? That can lead to errors.

I updated the setuptools after reading your comment! While I have recently installed Python 3.9.3+Spyder 5.0, it seems my setuptools- was <IP_ADDRESS>.0 after updating using `` it is now setuptools-54.2.0
The error is gone now! In summary for my case

I applied the @stonebig correction https://github.com/spyder-ide/spyder/issues/15091#issuecomment-812848088
I updated my setuptools using pip install -U setuptools
Spyder 5 now works without any error!

Thank you @real-yfprojects and @stonebig

on MACOS (macos big sur 11.2.3) previous versions worked smoothly but after updating to spyder 5.0.0 spyder‑kernels not working and cannot be installed using ( conda install spyder‑kernels OR pip install spyder‑kernels )
#ERROR Message :
You have missing dependencies!
Mandatory:
spyder_kernels >=2.0.1,<2.1.0 : 2.0.1 (NOK)
Please install them to avoid this message.
Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.
Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.

The same issue occurs for a clean install on macOS 11.2.3 using the DMG installer from http://docs.spyder-ide.org/current/installation.html.

I have the same issue after installing Spyder 5.0.0 on Windows 10 using Anaconda.

in your file "\Lib\site-packages\spyder\dependencies.py", change line 66
from
SPYDER_KERNELS_REQVER = '>=2.0.1,<2.1.0'
to
SPYDER_KERNELS_REQVER = '>=2.0.1;<2.1.0'
and it will be fine

Why not just SPYDER_KERNELS_REQVER = '>=2.0.1' ?

Why not just SPYDER_KERNELS_REQVER = '>=2.0.1' ?

See PR #15100.

Thank you for the tip.  When using the DMG-based installer on macOS, it looks like the path to the affected file is actually as follows:
/Applications/Spyder.app/Contents/Resources/lib/python3.9/spyder/dependencies.py

On Apr 7, 2021, at 7:53 AM, Kochise @.***> wrote:
in your file "\Lib\site-packages\spyder\dependencies.py", change line 66
from
SPYDER_KERNELS_REQVER = '>=2.0.1,<2.1.0'
to
SPYDER_KERNELS_REQVER = '>=2.0.1;<2.1.0'
and it will be fine
Why not just SPYDER_KERNELS_REQVER = '>=2.0.1' ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/15091#issuecomment-814889288, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2RJERNY3AW6WJR46HBFLTHRIVDANCNFSM42J22UGQ.

it is version 5.0.2 and the problem still there, and changing the , to ; does not work

This problem was fixed a month ago in 5.0.1 but unfortunately the Anaconda team hasn't updated Spyder yet, even after asking them to do it several times.


Collaboration with MMDetection3D

Hi, developers of ImVoxelNet,
Glad to see your insightful project is implemented based on MMDetection3D! Actually, multi-view image based 3D detection and a general detector could handle both indoor and outdoor scenes are also part of the original motivation to develop MMDetection3D. Great to see you take a step forward toward general 3D detection.
I would like to ask if there is any plan to contribute an implementation of ImVoxelNet to MMDetection3D? If so, maybe we can have a detailed discussion about it? Please feel free to ask if there is any help needed from MMDet3D team.
On behalf of the MMDet3D Development Team
Best,
Tai

Hi, @Tai-Wang
First, I would like to thank you again for your incredible work on the mmdetection3d. In fact, your FCOS3D is not least general-propose compared to ImVoxelNet. Also thanks for your interest in our work. It would be an honor for me to contribute to mmdetection3d. I think, I can close this issue and open a new one in mmdetection3d repo.

Hi @filaPro ,
No problem. I am also working for some advancements (and have made some progress) on image-based 3D detection based on FCOS3D, and we do hope to push it forward with our codebase in the near future, so I believe your work could bring good insights.
Please feel free to open new issues or PRs in mmdetection3d repo if needed. Many thanks for your contributions~


feat(headless): add Case Assist controller

https://coveord.atlassian.net/browse/SFINT-3742
This PR adds a complete Case Assist controller. It includes:

the headless-case-assist controller itself
the service-api-client that calls the Customer Service API
the unit tests

@samisayegh You are right, even with the removal of the Usage Analytics code, the PR is still a large one.
Basically, the Case Assist goal is to provide tools to optimize the case creation process and improve the case deflection rate. To do so, we provide the:

case classification, which suggests field values based on the case information as the user types it. It improves the case information quality.
document suggestions, which are relevant documents matching the case information as the user types it. If the user can find the solution there, he won't submit the case.

See Customer Service API Usage for details on the REST API itself.
We are expecting a user journey will look like this:

user enters the case creation form
user types in case information (subject, description, and other fields)
as the user fills the form, the Case Assist controller is invoked to retrieve field classifications. For example, we could suggest values for product or category fields.
we could also call the Case Assist controller to retrieve document suggestions trying to actually solve the issue.
finally, the user will either find a solution, or submit a case.

Regarding screenshots, I am currently testing with very basic LWC components only to test the full working loop. We'll eventually implement quantic components leveraging the case assist controller.
The debug controller was implemented to avoid proxying the actions through the case assist controller. I figured we might need to pass the debug flag to many other features in the future. Having the controller ready, makes it easier.
I can setup a meeting to discuss all of this in detail.

After discussion with @samisayegh we should break the Case Assist controller into many. It makes sense, especially to benefit from the treeshaking as more features are added to Case Assist over time.
Closing this PR. Will open new PRs with smaller changes.

@lbergeron is there going to be a follow up to this? Case Assist is a feature we are hoping to utilize in @coveo/headless and it's been over 4 months since the last I've seen any news.


Python3 wrapper build fails on OS X

Swig fails to link the correct libraries to compile _simstring*.so

Undefined symbols for architecture x86_64:
"_PyArg_ParseTuple", referenced from:
_wrap_delete_SwigPyIterator(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_value(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_incr(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_decr(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_distance(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_equal(_object*, _object*) in export_wrap.o
_wrap_SwigPyIterator_copy(_object*, _object*) in export_wrap.o
...

A similar problem occurred in another project and a solution was found.
https://github.com/chokkan/crfsuite/issues/11
I have verified that the same solution works by halting installation after the simstring tgz is unpacked, adding '-Wl,-undefined,dynamic_lookup' to extra_link_args in simstring/swig/python/setup.py.in, and resuming the installation.

thanks for pointing this out! I'll take a look at it later today.

I worked on this a little more. This will compile the file, but without the  correct links to PyArg or libiconv.
I noticed you made some progress within the osx-bug branch of Georgetown-IR-Lab/SimString, but I'm still having trouble compiling SimString with either project.

I found another repo that has a solution for compiling the module on OSX: github.com/blinkhealth/simstring-python-package
Generate the .so:

git clone https://github.com/blinkhealth/simstring-python-package
cd simstring-python-package
python setup.py build_ext --inplace

Then it just needs to be copied to the destination (after the standard installation fails, the correct folder is quickumls/simstring).

Thanks for pointing the repo out. It seems that your solution works, at least on OS X. Let me test it on some linux distribution, too. If it works there as well, I will switch over. Thanks a lot!

I've just released a new version that integrates the version of simstring you suggested. Again, thanks for the help! Let me know if you stumble across any other issue.


Publish 06/13/2022, 10:30 AM

Docs Build status updates of commit b01a2ed:
:warning: Validation status: warnings

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md
:warning:Warning
View (sharepoint-ps)
Details

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPODataConnectionSetting.md
:warning:Warning
View (sharepoint-server-ps)
Details

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPSite.md
:white_check_mark:Succeeded
View (sharepoint-server-ps)

sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.New-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Remove-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPODataConnectionSetting'.

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPODataConnectionSetting.md

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.New-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Remove-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPODataConnectionSetting'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

close/re-open PR

close/re-open after manual build on main

Docs Build status updates of commit b01a2ed:
:warning: Validation status: warnings

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md
:warning:Warning
View (sharepoint-ps)
Details

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPODataConnectionSetting.md
:warning:Warning
View (sharepoint-server-ps)
Details

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPSite.md
:white_check_mark:Succeeded
View (sharepoint-server-ps)

sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.New-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Remove-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPODataConnectionSetting'.

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPODataConnectionSetting.md

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.New-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Remove-SPODataConnectionSetting'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPODataConnectionSetting'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7b0fa42:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPODataConnectionSetting.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPSite.md
:white_check_mark:Succeeded
View (sharepoint-server-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Legend values and bins should be customisable per data story scenario

Currently the legend is fixed with four bins labeled 1 to 4, regardless of the scenario:

For example, that scenario would be better labelled with perhaps 5 bins (0-20 %, 20-40 %, 40-60 %, 60-80 %, 80-100 %), where the last meets the target threshold.
This should be defined within a data story, without a user having to supply html code.  e.g. just supply values and optionally corresponding labels.  The number of values supplied indicates number of bins (e.g. 4 for LTS, or 5 for 20mnMelbourne).

This is resolved, e.g.

The data story JSON code to define the above is,
"legend": [
    {"upper":"≤20%"},
    {"upper":"20%", "lower":"to 40%"},
    {"upper":"40%", "lower":"to 60%"},
    {"upper":"60%", "lower":"to 80%"},
    {"upper":"80%", "lower":"to 100%",
     "label": "Target threshold",
      "title": "80% or greater (policy target)"
    }
],


[TACHYON-619] Cascading LRUEvictor

https://tachyon.atlassian.net/browse/TACHYON-619
resolve left comments in https://github.com/amplab/tachyon/pull/1041.
implement cascading LRUEvictor.
unit test for LRUEvictor will be added after https://github.com/amplab/tachyon/pull/1042 is merged.

Jenkins, test this please.

Could you resolve the conflicts please?

@calvinjia @apc999 comments resolved and unit test for LRUEvictor added!

+1 LGTM