text:
I can't compile polybar

I tried different strategies to compile polybar, however, I get the following problem:
-- The CXX compiler identification is GNU 7.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type specified; using Release
-- Couldn't locate ccache, disabling ccache...
-- Performing Test HAS_SUGGEST_OVERRIDE
-- Performing Test HAS_SUGGEST_OVERRIDE - Success
-- Using supported compiler GNU-7.5.0
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Checking for module 'cairo-fc'
--   Found cairo-fc, version 1.15.10
-- Found CairoFC: /usr/include/cairo;/usr/include/glib-2.0;/usr/lib/x86_64-linux-gnu/glib-2.0/include;/usr/include/pixman-1;/usr/include/freetype2;/usr/include/libpng16;/usr/include/freetype2;/usr/include/libpng16 (found version "1.15.10")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Cairo::CairoFC".
Call Stack (most recent call first):
  cmake/modules/FindCairoFC.cmake:13 (create_imported_target)
  cmake/libpoly.cmake:49 (find_package)
  CMakeLists.txt:49 (include)

-- Found ALSA: /usr/lib/x86_64-linux-gnu/libasound.so (found version "1.1.3")
-- Found CURL: /usr/lib/x86_64-linux-gnu/libcurl.so (found version "7.58.0")
-- Checking for module 'libmpdclient'
--   Found libmpdclient, version 2.11
-- Found LibMPDClient: /usr/include (found version "2.11")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target
  "LibMPDClient::LibMPDClient".
Call Stack (most recent call first):
  cmake/modules/FindLibMPDClient.cmake:13 (create_imported_target)
  cmake/libpoly.cmake:62 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'libnl-genl-3.0'
--   Found libnl-genl-3.0, version 3.2.29
-- Found LibNlGenl3: /usr/include/libnl3 (found version "3.2.29")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target
  "LibNlGenl3::LibNlGenl3".
Call Stack (most recent call first):
  cmake/modules/FindLibNlGenl3.cmake:13 (create_imported_target)
  cmake/libpoly.cmake:68 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'libpulse'
--   Found libpulse, version 11.1
-- Found LibPulse: /usr/include (found version "11.1")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target
  "LibPulse::LibPulse".
Call Stack (most recent call first):
  cmake/modules/FindLibPulse.cmake:13 (create_imported_target)
  cmake/libpoly.cmake:76 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'xcb-randr'
--   Found xcb-randr, version 1.13
-- Found Xcb_RANDR: /usr/include (found suitable version "1.13", minimum required is "1.12")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Xcb::RANDR".
Call Stack (most recent call first):
  cmake/modules/FindXcb.cmake:55 (create_imported_target)
  cmake/libpoly.cmake:100 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'xcb-composite'
--   Found xcb-composite, version 1.13
-- Found Xcb_COMPOSITE: /usr/include (found version "1.13")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Xcb::COMPOSITE".
Call Stack (most recent call first):
  cmake/modules/FindXcb.cmake:55 (create_imported_target)
  cmake/libpoly.cmake:101 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'xcb-xkb'
--   Found xcb-xkb, version 1.13
-- Found Xcb_XKB: /usr/include (found version "1.13")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Xcb::XKB".
Call Stack (most recent call first):
  cmake/modules/FindXcb.cmake:55 (create_imported_target)
  cmake/libpoly.cmake:101 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'xcb-cursor'
--   Found xcb-cursor, version 0.1.1
-- Found Xcb_CURSOR: /usr/include (found version "0.1.1")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Xcb::CURSOR".
Call Stack (most recent call first):
  cmake/modules/FindXcb.cmake:55 (create_imported_target)
  cmake/libpoly.cmake:101 (find_package)
  CMakeLists.txt:49 (include)

-- Checking for module 'xcb-xrm'
--   Found xcb-xrm, version 1.0
-- Found Xcb_XRM: /usr/include (found version "1.0")
CMake Error at cmake/common/utils.cmake:121 (target_include_directories):
  Cannot specify include directories for imported target "Xcb::XRM".
Call Stack (most recent call first):
  cmake/modules/FindXcb.cmake:55 (create_imported_target)
  cmake/libpoly.cmake:101 (find_package)
  CMakeLists.txt:49 (include)

-- The C compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking for module 'xcb-proto'
--   Found xcb-proto, version 1.13
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.9", minimum required is "3.5")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib/x86_64-linux-gnu/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib/x86_64-linux-gnu/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib/x86_64-linux-gnu/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib/x86_64-linux-gnu/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib/x86_64-linux-gnu/libxcb-image.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so
-- Searching for xcbgen with /usr/bin/python3
-- Searching for xcbgen with python3
-- Searching for xcbgen with python
-- Found xcbgen in /usr/lib/python2.7/dist-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB_RANDR: /usr/lib/x86_64-linux-gnu/libxcb-randr.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so
-- XCB[COMPOSITE]: Found component COMPOSITE
-- Found XCB_COMPOSITE: /usr/lib/x86_64-linux-gnu/libxcb-composite.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so;/usr/lib/x86_64-linux-gnu/libxcb-composite.so
-- XCB[XKB]: Found component XKB
-- Found XCB_XKB: /usr/lib/x86_64-linux-gnu/libxcb-xkb.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so;/usr/lib/x86_64-linux-gnu/libxcb-composite.so;/usr/lib/x86_64-linux-gnu/libxcb-xkb.so
-- xpp: including xcb proto composite.xml
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Checking for module 'jsoncpp'
--   Found jsoncpp, version 1.7.4
-- Font not found: fixed:pixelsize=10
-- Font not found: unifont:fontformat=truetype
-- Font not found: siji:pixelsize=10
--  Build:
--    Version: 3.5.4-103-gcd71b96c
--    Type: Release
--    CXX: /usr/bin/c++  -Wall -Wextra -Wpedantic -Wsuggest-override -O3 -DNDEBUG
--    LD: /usr/bin/ld
--    sphinx-build: /usr/bin/sphinx-build
--  Install Paths:
--    PREFIX:  /usr/local
--    BINDIR:  /usr/local/bin
--    DATADIR: /usr/local/share
--    DOCDIR:  /usr/local/share/doc/polybar
--    MANDIR:  /usr/local/share/man
--  Targets:
-- [X]   polybar
-- [X]   polybar-msg
-- [ ]   testsuite
-- [X]   documentation
-- [X]      html
-- [X]      man
-- [X]   sample config
-- [X]   shell files
--  Module support:
-- [X]   alsa (1.1.3)
-- [X]   curl (7.58.0)
-- [X]   i3
-- [X]   mpd (2.11)
-- [X]   network (libnl) (3.2.29)
-- [X]   pulseaudio (11.1)
-- [X]   xkeyboard (1.13)
--  X extensions:
-- [X]   xcb-randr (1.13)
-- [X]   xcb-randr (monitor support) (1.13)
-- [X]   xcb-composite (1.13)
-- [X]   xcb-xkb (1.13)
-- [X]   xcb-xrm (1.0)
-- [X]   xcb-cursor (0.1.1)
--  Log options:
-- [X]   Trace logging
-- Configuring incomplete, errors occurred!
See also "/home/sander/Downloads/polybar/polybar/build/CMakeFiles/CMakeOutput.log".
See also "/home/sander/Downloads/polybar/polybar/build/CMakeFiles/CMakeError.log".

I tried with the clang, clang++, g++, etc and I get the same problem.

What distro are you using?

I am using Linux Mint T19.2 (Tina), my kernel is: Linux 4.15.0-135-generic x86_64, and the version of cmake is 3.10.2.

I think I was able to fix it in #2388. Can you check out the PR and see if it works for you?

I upgraded cmake to the version 3.19.5, and errors similar to the #463 appeared with different compilers and branches. I downgraded the libxcb-randr0-dev to the 1.11.1, and didn't work again. Finally I tried with other branches and other errors appeared.
Furthermore, I reverted the changes, build/installed python3-xcbgen and then only the branch 3.4.0 worked.
So my best advice for this kind of troubles is to build python3-xcbgen from scratch, and try with different c++ compilers and branches.

I downgraded the libxcb-randr0-dev to the 1.11.1, and didn't work again.

This is only necessary when the other randr packages are also version 1.11 otherwise it won't work and we never had this issue in ubuntu 18.04.
I also have not had any issues with python-xcbgen (instead of python3-xcbgen) on a clean ubuntu 18.04 docker image.
Did you try to build the PR I linked?

I got the following with the PR you linked me:
Scanning dependencies of target doc_html
[  1%] Generating generated-sources/include/xpp/proto/composite.hpp
[  2%] Generating generated-sources/include/xpp/proto/xkb.hpp
Scanning dependencies of target polybar-msg
Scanning dependencies of target doc_man
[  3%] Generating generated-sources/include/xpp/proto/randr.hpp
[  4%] Generating generated-sources/include/xpp/proto/x.hpp
Scanning dependencies of target i3ipc++
[  4%] sphinx-build html: see doc/builder-html.log
[  5%] Building CXX object bin/CMakeFiles/polybar-msg.dir/ipc.cpp.o
[  6%] sphinx-build man: see doc/builder-man.log
[  7%] Building CXX object lib/i3ipcpp/CMakeFiles/i3ipc++.dir/src/ipc.cpp.o
[  8%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/env.cpp.o
Configuration error:
There is a syntax error in your configuration file: invalid syntax (conf.py, line 234)
list: size, ['red', 'green', 'blue']
doc/CMakeFiles/doc_html.dir/build.make:76: recipe for target 'doc/CMakeFiles/doc_html' failed
make[2]: *** [doc/CMakeFiles/doc_html] Error 1
CMakeFiles/Makefile2:477: recipe for target 'doc/CMakeFiles/doc_html.dir/all' failed
make[1]: *** [doc/CMakeFiles/doc_html.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Configuration error:
There is a syntax error in your configuration file: invalid syntax (conf.py, line 234)
list: size, ['red', 'green', 'blue']
[  9%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/file.cpp.o
doc/CMakeFiles/doc_man.dir/build.make:76: recipe for target 'doc/CMakeFiles/doc_man' failed
make[2]: *** [doc/CMakeFiles/doc_man] Error 1
CMakeFiles/Makefile2:450: recipe for target 'doc/CMakeFiles/doc_man.dir/all' failed
make[1]: *** [doc/CMakeFiles/doc_man.dir/all] Error 2
[ 10%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/string.cpp.o
[ 11%] Building CXX object lib/i3ipcpp/CMakeFiles/i3ipc++.dir/src/ipc-util.cpp.o
[ 12%] Linking CXX executable polybar-msg
[ 12%] Built target polybar-msg
[ 13%] Linking CXX static library libi3ipc++.a
[ 13%] Built target i3ipc++
Scanning dependencies of target xpp
[ 14%] Linking CXX static library libxpp.a
[ 14%] Built target xpp
Makefile:148: recipe for target 'all' failed
make: *** [all] Error 2

I used cmake (default) .. and the clang cmake option.

There is a syntax error in your configuration file: invalid syntax (conf.py, line 234)

What python version are you using? That syntax should be supported in all python 3 versions.
As a workaround you can disable building the documentation with cmake -DBUILD_DOC=OFF ..

I am going through a similar issue except after building with #2388 I get the following output.
Scanning dependencies of target doc_man
Scanning dependencies of target doc_html
[  1%] sphinx-build man: see doc/builder-man.log
[  1%] sphinx-build html: see doc/builder-html.log
[  1%] Built target doc_man
[  2%] Generating generated-sources/include/xpp/proto/x.hpp
[  2%] Built target doc_html
[  3%] Generating generated-sources/include/xpp/proto/composite.hpp
[  4%] Generating generated-sources/include/xpp/proto/randr.hpp
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
Scanning dependencies of target i3ipc++
[  5%] Building CXX object lib/i3ipcpp/CMakeFiles/i3ipc++.dir/src/ipc.cpp.o
[  6%] Building CXX object lib/i3ipcpp/CMakeFiles/i3ipc++.dir/src/ipc-util.cpp.o
[  7%] Generating generated-sources/include/xpp/proto/xkb.hpp
Scanning dependencies of target xpp
[  8%] Linking CXX static library libxpp.a
[  8%] Built target xpp
Scanning dependencies of target polybar-msg
[  9%] Building CXX object bin/CMakeFiles/polybar-msg.dir/ipc.cpp.o
[ 10%] Linking CXX static library libi3ipc++.a
[ 10%] Built target i3ipc++
[ 11%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/env.cpp.o
Scanning dependencies of target doc
[ 11%] Built target doc
Scanning dependencies of target poly
[ 12%] Building CXX object bin/CMakeFiles/poly.dir/__/generated-sources/settings.cpp.o
[ 13%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/file.cpp.o
[ 14%] Building CXX object bin/CMakeFiles/poly.dir/cairo/utils.cpp.o
[ 15%] Building CXX object bin/CMakeFiles/poly.dir/components/bar.cpp.o
[ 16%] Building CXX object bin/CMakeFiles/polybar-msg.dir/utils/string.cpp.o
[ 17%] Linking CXX executable polybar-msg
[ 17%] Built target polybar-msg
[ 18%] Building CXX object bin/CMakeFiles/poly.dir/components/builder.cpp.o
[ 19%] Building CXX object bin/CMakeFiles/poly.dir/components/command_line.cpp.o
[ 20%] Building CXX object bin/CMakeFiles/poly.dir/components/config.cpp.o
[ 21%] Building CXX object bin/CMakeFiles/poly.dir/components/config_parser.cpp.o
[ 22%] Building CXX object bin/CMakeFiles/poly.dir/components/controller.cpp.o
[ 23%] Building CXX object bin/CMakeFiles/poly.dir/components/ipc.cpp.o
[ 24%] Building CXX object bin/CMakeFiles/poly.dir/components/logger.cpp.o
[ 25%] Building CXX object bin/CMakeFiles/poly.dir/components/renderer.cpp.o
[ 26%] Building CXX object bin/CMakeFiles/poly.dir/components/screen.cpp.o
[ 27%] Building CXX object bin/CMakeFiles/poly.dir/components/taskqueue.cpp.o
[ 28%] Building CXX object bin/CMakeFiles/poly.dir/drawtypes/animation.cpp.o
[ 29%] Building CXX object bin/CMakeFiles/poly.dir/drawtypes/iconset.cpp.o
[ 30%] Building CXX object bin/CMakeFiles/poly.dir/drawtypes/label.cpp.o
[ 30%] Building CXX object bin/CMakeFiles/poly.dir/drawtypes/progressbar.cpp.o
[ 31%] Building CXX object bin/CMakeFiles/poly.dir/drawtypes/ramp.cpp.o
[ 32%] Building CXX object bin/CMakeFiles/poly.dir/events/signal_emitter.cpp.o
[ 33%] Building CXX object bin/CMakeFiles/poly.dir/events/signal_receiver.cpp.o
[ 34%] Building CXX object bin/CMakeFiles/poly.dir/modules/backlight.cpp.o
[ 35%] Building CXX object bin/CMakeFiles/poly.dir/modules/battery.cpp.o
[ 36%] Building CXX object bin/CMakeFiles/poly.dir/modules/bspwm.cpp.o
[ 37%] Building CXX object bin/CMakeFiles/poly.dir/modules/counter.cpp.o
[ 38%] Building CXX object bin/CMakeFiles/poly.dir/modules/cpu.cpp.o
[ 39%] Building CXX object bin/CMakeFiles/poly.dir/modules/date.cpp.o
[ 40%] Building CXX object bin/CMakeFiles/poly.dir/modules/fs.cpp.o
[ 41%] Building CXX object bin/CMakeFiles/poly.dir/modules/ipc.cpp.o
[ 42%] Building CXX object bin/CMakeFiles/poly.dir/modules/memory.cpp.o
[ 43%] Building CXX object bin/CMakeFiles/poly.dir/modules/menu.cpp.o
[ 44%] Building CXX object bin/CMakeFiles/poly.dir/modules/meta/base.cpp.o
[ 45%] Building CXX object bin/CMakeFiles/poly.dir/modules/script.cpp.o
[ 46%] Building CXX object bin/CMakeFiles/poly.dir/modules/systray.cpp.o
[ 47%] Building CXX object bin/CMakeFiles/poly.dir/modules/temperature.cpp.o
[ 48%] Building CXX object bin/CMakeFiles/poly.dir/modules/text.cpp.o
[ 49%] Building CXX object bin/CMakeFiles/poly.dir/modules/xbacklight.cpp.o
[ 50%] Building CXX object bin/CMakeFiles/poly.dir/modules/xwindow.cpp.o
[ 50%] Building CXX object bin/CMakeFiles/poly.dir/modules/xworkspaces.cpp.o
[ 51%] Building CXX object bin/CMakeFiles/poly.dir/tags/action_context.cpp.o
[ 52%] Building CXX object bin/CMakeFiles/poly.dir/tags/context.cpp.o
[ 53%] Building CXX object bin/CMakeFiles/poly.dir/tags/dispatch.cpp.o
[ 54%] Building CXX object bin/CMakeFiles/poly.dir/tags/parser.cpp.o
[ 55%] Building CXX object bin/CMakeFiles/poly.dir/utils/actions.cpp.o
[ 56%] Building CXX object bin/CMakeFiles/poly.dir/utils/bspwm.cpp.o
[ 57%] Building CXX object bin/CMakeFiles/poly.dir/utils/color.cpp.o
[ 58%] Building CXX object bin/CMakeFiles/poly.dir/utils/command.cpp.o
[ 59%] Building CXX object bin/CMakeFiles/poly.dir/utils/concurrency.cpp.o
[ 60%] Building CXX object bin/CMakeFiles/poly.dir/utils/env.cpp.o
[ 61%] Building CXX object bin/CMakeFiles/poly.dir/utils/factory.cpp.o
[ 62%] Building CXX object bin/CMakeFiles/poly.dir/utils/file.cpp.o
[ 63%] Building CXX object bin/CMakeFiles/poly.dir/utils/inotify.cpp.o
[ 64%] Building CXX object bin/CMakeFiles/poly.dir/utils/io.cpp.o
[ 65%] Building CXX object bin/CMakeFiles/poly.dir/utils/process.cpp.o
[ 66%] Building CXX object bin/CMakeFiles/poly.dir/utils/socket.cpp.o
[ 67%] Building CXX object bin/CMakeFiles/poly.dir/utils/string.cpp.o
[ 68%] Building CXX object bin/CMakeFiles/poly.dir/utils/throttle.cpp.o
[ 69%] Building CXX object bin/CMakeFiles/poly.dir/x11/atoms.cpp.o
[ 70%] Building CXX object bin/CMakeFiles/poly.dir/x11/background_manager.cpp.o
[ 70%] Building CXX object bin/CMakeFiles/poly.dir/x11/connection.cpp.o
[ 71%] Building CXX object bin/CMakeFiles/poly.dir/x11/ewmh.cpp.o
[ 72%] Building CXX object bin/CMakeFiles/poly.dir/x11/extensions/composite.cpp.o
[ 73%] Building CXX object bin/CMakeFiles/poly.dir/x11/extensions/randr.cpp.o
[ 74%] Building CXX object bin/CMakeFiles/poly.dir/x11/icccm.cpp.o
[ 75%] Building CXX object bin/CMakeFiles/poly.dir/x11/registry.cpp.o
[ 76%] Building CXX object bin/CMakeFiles/poly.dir/x11/tray_client.cpp.o
[ 77%] Building CXX object bin/CMakeFiles/poly.dir/x11/tray_manager.cpp.o
[ 78%] Building CXX object bin/CMakeFiles/poly.dir/x11/window.cpp.o
[ 79%] Building CXX object bin/CMakeFiles/poly.dir/x11/winspec.cpp.o
[ 80%] Building CXX object bin/CMakeFiles/poly.dir/x11/xembed.cpp.o
[ 81%] Building CXX object bin/CMakeFiles/poly.dir/adapters/alsa/control.cpp.o
[ 82%] Building CXX object bin/CMakeFiles/poly.dir/adapters/alsa/mixer.cpp.o
[ 83%] Building CXX object bin/CMakeFiles/poly.dir/modules/alsa.cpp.o
[ 84%] Building CXX object bin/CMakeFiles/poly.dir/modules/github.cpp.o
[ 85%] Building CXX object bin/CMakeFiles/poly.dir/utils/http.cpp.o
[ 86%] Building CXX object bin/CMakeFiles/poly.dir/modules/i3.cpp.o
[ 87%] Building CXX object bin/CMakeFiles/poly.dir/utils/i3.cpp.o
[ 88%] Building CXX object bin/CMakeFiles/poly.dir/adapters/mpd.cpp.o
[ 89%] Building CXX object bin/CMakeFiles/poly.dir/modules/mpd.cpp.o
[ 90%] Building CXX object bin/CMakeFiles/poly.dir/adapters/net.cpp.o
[ 90%] Building CXX object bin/CMakeFiles/poly.dir/modules/network.cpp.o
[ 91%] Building CXX object bin/CMakeFiles/poly.dir/adapters/net_nl.cpp.o
[ 92%] Building CXX object bin/CMakeFiles/poly.dir/adapters/pulseaudio.cpp.o
[ 93%] Building CXX object bin/CMakeFiles/poly.dir/modules/pulseaudio.cpp.o
[ 94%] Building CXX object bin/CMakeFiles/poly.dir/x11/cursor.cpp.o
[ 95%] Building CXX object bin/CMakeFiles/poly.dir/modules/xkeyboard.cpp.o
[ 96%] Building CXX object bin/CMakeFiles/poly.dir/x11/extensions/xkb.cpp.o
[ 97%] Building CXX object bin/CMakeFiles/poly.dir/x11/xresources.cpp.o
[ 98%] Linking CXX static library ../libs/libpoly.a
[ 98%] Built target poly
Scanning dependencies of target polybar
[ 99%] Building CXX object bin/CMakeFiles/polybar.dir/main.cpp.o
[100%] Linking CXX executable polybar
../libs/libpoly.a(alsa.cpp.o): In function `polybar::modules::alsa_module::teardown()':
alsa.cpp:(.text+0x858): undefined reference to `snd_config_update_free_global'
../libs/libpoly.a(alsa.cpp.o): In function `polybar::modules::module<polybar::modules::alsa_module>::stop()':
alsa.cpp:(.text._ZN7polybar7modules6moduleINS0_11alsa_moduleEE4stopEv[_ZN7polybar7modules6moduleINS0_11alsa_moduleEE4stopEv]+0x229): undefined reference to `snd_config_update_free_global'
../libs/libpoly.a(http.cpp.o): In function `polybar::http_downloader::http_downloader(int)':
http.cpp:(.text+0x192): undefined reference to `curl_easy_init'
http.cpp:(.text+0x1ab): undefined reference to `curl_easy_setopt'
http.cpp:(.text+0x1c1): undefined reference to `curl_easy_setopt'
http.cpp:(.text+0x1d9): undefined reference to `curl_easy_setopt'
http.cpp:(.text+0x1ed): undefined reference to `curl_easy_setopt'
http.cpp:(.text+0x2ab): undefined reference to `curl_easy_setopt'
../libs/libpoly.a(http.cpp.o):http.cpp:(.text+0x2e7): more undefined references to `curl_easy_setopt' follow
../libs/libpoly.a(http.cpp.o): In function `polybar::http_downloader::get(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
http.cpp:(.text+0x5ec): undefined reference to `curl_easy_perform'
http.cpp:(.text+0x8bb): undefined reference to `curl_easy_setopt'
http.cpp:(.text+0xa6e): undefined reference to `curl_easy_strerror'
../libs/libpoly.a(http.cpp.o): In function `polybar::http_downloader::response_code()':
http.cpp:(.text+0xcb8): undefined reference to `curl_easy_getinfo'
../libs/libpoly.a(http.cpp.o): In function `polybar::http_downloader::~http_downloader()':
http.cpp:(.text+0x3d4): undefined reference to `curl_easy_cleanup'
../libs/libpoly.a(control.cpp.o): In function `polybar::alsa::control::wait(int)':
control.cpp:(.text+0x112): undefined reference to `snd_ctl_wait'
control.cpp:(.text+0x11c): undefined reference to `snd_ctl_event_sizeof'
control.cpp:(.text+0x131): undefined reference to `snd_ctl_event_sizeof'
control.cpp:(.text+0x14f): undefined reference to `snd_ctl_read'
control.cpp:(.text+0x15c): undefined reference to `snd_ctl_event_get_type'
control.cpp:(.text+0x184): undefined reference to `snd_ctl_event_elem_get_mask'
../libs/libpoly.a(control.cpp.o): In function `polybar::alsa::control::test_device_plugged()':
control.cpp:(.text+0x20e): undefined reference to `snd_ctl_elem_value_sizeof'
control.cpp:(.text+0x223): undefined reference to `snd_ctl_elem_value_sizeof'
control.cpp:(.text+0x241): undefined reference to `snd_hctl_elem_read'
control.cpp:(.text+0x250): undefined reference to `snd_ctl_elem_value_get_boolean'
../libs/libpoly.a(control.cpp.o): In function `polybar::alsa::control::control(int)':
control.cpp:(.text+0x30c): undefined reference to `snd_ctl_open'
control.cpp:(.text+0x31a): undefined reference to `snd_config_update_free_global'
control.cpp:(.text+0x327): undefined reference to `snd_hctl_open_ctl'
control.cpp:(.text+0x338): undefined reference to `snd_config_update_free_global'
control.cpp:(.text+0x341): undefined reference to `snd_hctl_load'
control.cpp:(.text+0x34f): undefined reference to `snd_ctl_elem_id_sizeof'
control.cpp:(.text+0x364): undefined reference to `snd_ctl_elem_id_sizeof'
control.cpp:(.text+0x37f): undefined reference to `snd_ctl_elem_id_set_numid'
control.cpp:(.text+0x384): undefined reference to `snd_ctl_elem_info_sizeof'
control.cpp:(.text+0x399): undefined reference to `snd_ctl_elem_info_sizeof'
control.cpp:(.text+0x3b5): undefined reference to `snd_ctl_elem_info_set_id'
control.cpp:(.text+0x3c1): undefined reference to `snd_ctl_elem_info'
control.cpp:(.text+0x3d5): undefined reference to `snd_ctl_elem_info_get_id'
control.cpp:(.text+0x3e1): undefined reference to `snd_hctl_find_elem'
control.cpp:(.text+0x3fc): undefined reference to `snd_ctl_subscribe_events'
control.cpp:(.text+0x52a): undefined reference to `snd_ctl_elem_id_get_numid'
control.cpp:(.text+0x5d1): undefined reference to `snd_ctl_elem_id_get_numid'
control.cpp:(.text+0x699): undefined reference to `snd_ctl_close'
../libs/libpoly.a(control.cpp.o): In function `polybar::alsa::control::~control()':
control.cpp:(.text+0xca): undefined reference to `snd_hctl_close'
../libs/libpoly.a(control.cpp.o): In function `void polybar::alsa::throw_exception<polybar::alsa::control_error>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, int)':
control.cpp:(.text._ZN7polybar4alsa15throw_exceptionINS0_13control_errorEEEvONSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi[_ZN7polybar4alsa15throw_exceptionINS0_13control_errorEEEvONSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi]+0x1e): undefined reference to `snd_strerror'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::~mixer()':
mixer.cpp:(.text+0xcd): undefined reference to `snd_mixer_close'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::get_volume()':
mixer.cpp:(.text+0x169): undefined reference to `snd_mixer_selem_get_playback_volume_range'
mixer.cpp:(.text+0x17f): undefined reference to `snd_mixer_selem_has_playback_channel'
mixer.cpp:(.text+0x198): undefined reference to `snd_mixer_selem_get_playback_volume'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::get_normalized_volume()':
mixer.cpp:(.text+0x25a): undefined reference to `snd_mixer_selem_get_playback_dB_range'
mixer.cpp:(.text+0x270): undefined reference to `snd_mixer_selem_has_playback_channel'
mixer.cpp:(.text+0x28a): undefined reference to `snd_mixer_selem_get_playback_dB'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::set_volume(float)':
mixer.cpp:(.text+0x40f): undefined reference to `snd_mixer_selem_has_playback_channel'
mixer.cpp:(.text+0x429): undefined reference to `snd_mixer_selem_get_playback_switch'
mixer.cpp:(.text+0x47f): undefined reference to `snd_mixer_selem_get_playback_volume_range'
mixer.cpp:(.text+0x4cc): undefined reference to `snd_mixer_selem_set_playback_volume_all'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::set_normalized_volume(float)':
mixer.cpp:(.text+0x51f): undefined reference to `snd_mixer_selem_has_playback_channel'
mixer.cpp:(.text+0x539): undefined reference to `snd_mixer_selem_get_playback_switch'
mixer.cpp:(.text+0x5ab): undefined reference to `snd_mixer_selem_get_playback_dB_range'
mixer.cpp:(.text+0x64c): undefined reference to `snd_mixer_selem_set_playback_dB_all'
mixer.cpp:(.text+0x67c): undefined reference to `snd_mixer_selem_set_playback_dB_all'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::toggle_mute()':
mixer.cpp:(.text+0x6c4): undefined reference to `snd_mixer_selem_get_playback_switch'
mixer.cpp:(.text+0x6d9): undefined reference to `snd_mixer_selem_set_playback_switch_all'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::is_muted()':
mixer.cpp:(.text+0x73f): undefined reference to `snd_mixer_selem_has_playback_channel'
mixer.cpp:(.text+0x759): undefined reference to `snd_mixer_selem_get_playback_switch'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::process_events()':
mixer.cpp:(.text+0x7ca): undefined reference to `snd_mixer_handle_events'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::mixer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
mixer.cpp:(.text+0x901): undefined reference to `snd_mixer_open'
mixer.cpp:(.text+0x90f): undefined reference to `snd_config_update_free_global'
mixer.cpp:(.text+0x91b): undefined reference to `snd_mixer_attach'
mixer.cpp:(.text+0x930): undefined reference to `snd_mixer_selem_register'
mixer.cpp:(.text+0x941): undefined reference to `snd_mixer_load'
mixer.cpp:(.text+0x94f): undefined reference to `snd_mixer_selem_id_sizeof'
mixer.cpp:(.text+0x968): undefined reference to `snd_mixer_selem_id_sizeof'
mixer.cpp:(.text+0x97f): undefined reference to `snd_mixer_selem_id_set_index'
mixer.cpp:(.text+0x98b): undefined reference to `snd_mixer_selem_id_set_name'
mixer.cpp:(.text+0x996): undefined reference to `snd_mixer_find_selem'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::wait(int)':
mixer.cpp:(.text+0xbbd): undefined reference to `snd_mixer_wait'
mixer.cpp:(.text+0xbca): undefined reference to `snd_mixer_handle_events'
../libs/libpoly.a(mixer.cpp.o): In function `polybar::alsa::mixer::set_mute(bool)':
mixer.cpp:(.text+0x699): undefined reference to `snd_mixer_selem_set_playback_switch_all'
../libs/libpoly.a(mixer.cpp.o): In function `void polybar::alsa::throw_exception<polybar::alsa::mixer_error>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, int)':
mixer.cpp:(.text._ZN7polybar4alsa15throw_exceptionINS0_11mixer_errorEEEvONSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi[_ZN7polybar4alsa15throw_exceptionINS0_11mixer_errorEEEvONSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi]+0x1e): undefined reference to `snd_strerror'
collect2: error: ld returned 1 exit status
bin/CMakeFiles/polybar.dir/build.make:105: recipe for target 'bin/polybar' failed
make[2]: *** [bin/polybar] Error 1
CMakeFiles/Makefile2:589: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

@l4dbill8745 Please open a separate issue and use the build issue template. This is likely a different issue.

My mistake will do.

repo: polybar/polybar


text:
Pass annotated assignment tests

tests_folder

finished in #389

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
primary name switch for FYPO:0006424

Primary name
from
FYPO:0006424 abolished meiotic sister chromatid cohesion at centromere during meiosis I
to
Abolished centromeric cohesion protection at meiosis I
A cellular process phenotype in which  cohesion between sister chromatids does not occur in centromeric regions during the first meiotic nuclear division resulting in kinetochores separating at the first division.

Will the name of the GO term used in the logical def also have its name changed, or at least get an exact synonym, to match (at present it's GO:0051754 meiotic sister chromatid cohesion, centromeric)? If not, what's the rationale for diverging?
I rashly assume other FYPO terms should be treated identically (i.e. you don't want FYPO:0006424 to become inconsistent with FYPO:0004667, FYPO:0005579, FYPO:0006423, FYPO:0006425, and FYPO:0007759).

I'll take this until I figure out the GO stuff, which won't be soon....

repo: pombase/fypo


text:
more white space needed

Minor thing; small displays could use some more white space between the image and the text "recent news"

Minor thing; small displays could use some more white space between the image and the text "recent news"

That's fixed now.  And I've made the "Recent news" heading bigger.

authors: Antonialock kimrutherford

repo: pombase/website


text:
added genestorian to collabs

Closes #1947

thumbs up emoji!

source: gharchive/pull-request

authors: ValWood manulera


text:
Required functionality for continuous time-pondersource-com -> m-ld push

For https://github.com/federatedbookkeeping/timesheets/issues/27 we need to be able to push a given change (addition, update, or deletion of a timesheet entry) in time-pondersource-com to m-ld.
Additionally, we should make it possible to configure this push to happen automatically.

Setting this in my .env:
TIMELD_HOST=https://timeld.org
TIMELD_USERNAME=michielbdejong
TIMELD_PASSWORD=...

And running:
php src/cli-single.php timeld-api-import "Timesheet" "michielbdejong/michielbdejong" "fedb/fedt" my-timesheet "22 August 2021" 8

The timeld-api-export command seems unfinished.
It calls exportTimeld which ports data from Timeld to Prejournal (so export from the Timeld perspective, but I would call it import from the Prejournal prespective).

The importTimld function comes closer to what we need. Let's try to get that working.

There is a side-effect of also creating the movement locally, let's comment that out.
There is nothing showing up in the main fedb/fedt timesheet, but I do see a project created:
curl https://timeld.org/api/rpt/michielbdejong/own/michielbdejong -u $CREDENTIALS
{"@type":"Timesheet","@id":"michielbdejong\/michielbdejong","project":[{"@id":"fedb\/fedt"}],"external":{"@id":"my-timesheet"}}

To generate the example request body from the Timeld docs I would need to do:
php src/cli-single.php timeld-api-import Project org1/pr1 dummy http://ex.org/project/1
php src/cli-single.php timeld-api-import Timesheet org1/ts1 org1/pr1 http://ex.org/timesheet/1
php src/cli-single.php timeld-api-import Entry dummy dummy http://ex.org/timesheet/1/entry/1

But there would still not be a way to set the activity, duration, or start. :(
I'll create a command for it from scratch.

prejournal=# select id, timestamp_, amount  from movements where fromcomponent=12 and tocomponent=8 and type_='worked';
id  |     timestamp_      | amount
-----+---------------------+--------
121 | 2022-07-05 00:00:00 |      8
122 | 2022-07-15 00:00:00 |      2
123 | 2022-07-15 00:00:00 |      1
[...]

Convert that to:
{"@id":"fedb/fedt","@type":"Project"}
{"@id":"michielbdejong/my-timesheet","project":{"@id":"fedb/fedt"},"@type":"Timesheet"}
{"activity":"Worked","duration":480,"start":{"@value":"2022-07-05T00:00:00.000Z","@type":"http://www.w3.org/2001/XMLSchema#dateTime"},"@type":"Entry","vf:provider":{"@id":"http://time.pondersource.com/michiel"},"external":{"@id":"http://time.pondersource.com/movement/121"}}
{"activity":"Worked","duration":120,"start":{"@value":"2022-07-05T00:00:00.000Z","@type":"http://www.w3.org/2001/XMLSchema#dateTime"},"@type":"Entry","vf:provider":{"@id":"http://time.pondersource.com/michiel"},"external":{"@id":"http://time.pondersource.com/movement/122"}}
{"activity":"Worked","duration":60,"start":{"@value":"2022-07-05T00:00:00.000Z","@type":"http://www.w3.org/2001/XMLSchema#dateTime"},"@type":"Entry","vf:provider":{"@id":"http://time.pondersource.com/michiel"},"external":{"@id":"http://time.pondersource.com/movement/123"}}
[...]

As part of this work, reported https://github.com/m-ld/timeld/issues/84
Next step: push out single entry as and when it's created.

For server reset, worked through https://github.com/pondersource/prejournal/issues/172 and apart from https://github.com/m-ld/timeld/issues/87 I think that is fine now.
Next: whenever a movement of type 'worked' is created or updated, push that one entry out to timeld.org.

time.pondersource.com now pushed to the fedb/from-pounder-source-with-love whenever a movement is created with type 'worked'.
The description and worker name are not coming through yet.
Also, should do the same for updateMovement.

Ah, updateMovement is only available from import so don't need to add it there for now

repo: pondersource/prejournal


text:
Update to using main-actor-documentation-action

https://github.com/ponylang/main-actor-documentation-action

The same issue was closed in http due to main-actor's deprecation, so I guess this one can also be closed.

Yup. Thanks. I missed this one.

authors: SeanTAllen Trundle


text:
Last Week in Pony - Aug 21st, 2022

use "ponynews"

@redvers I mean this in the kindest way, but not sure how to write it to be funny.

use "ponynews"

According to the Style Guide...blah, blah, blah: "pony_news"

Was there any intention on keeping up with the Issue Highlight that was started briefly? That is, highlight a good first issue which we think a new Pony dev could reasonably tackle? It wasn't in LWIP for long, but I thought it was a good addition.

Patch accepted :-)
As for the "Issue Highlight", we absolutely can do that - just need suggestions to be fed into the comments here.

Perfect. I will take a look at issues later today and suggest a few I think would be good for highlight. I wasn't trying to add work to your plate suggesting we bring the highlight back. I don't think we should highlight more than one a week, but I will probably post a few to choose from.

Not at all!  I'm looking for as much as we can put in it.  I'd really like to expand its scope some more and tell more of the pony story.  We have a compiler and runtime which solves some hard problems in a unique way.
The world needs more ponies.

@redvers
Here are a couple of "good first issues" & "help wanted" issues which I think are reasonable to highlight:

https://github.com/ponylang/ponyc/issues/4148

Improving error messages always make it easier for new Pony developers to understand what is wrong -- having a new developer help us here is always appreciated! :smile:

https://github.com/ponylang/ponyc/issues/4015

Improving error messages always make it easier for new Pony developers to understand what is wrong -- having a new developer help us here is always appreciated! :smile:

Audio from the August 16, 2022 Pony Development Sync is available: https://sync-recordings.ponylang.io/r/2022_08_16.m4a

Closed by https://github.com/ponylang/ponylang-website/pull/787

authors: SeanTAllen redvers rhagenson

repo: ponylang/ponylang-website


text:
Error while using useProseMirror hook

Hello,
I'm trying to setup this dependency on a fresh create-react-app app.
`import 'prosemirror-view/style/prosemirror.css';
import React from 'react';
import {schema} from 'prosemirror-schema-basic';
import {useProseMirror, ProseMirror} from 'use-prosemirror';
export default function MyEditor() {
const [state, setState] = useProseMirror({schema});
return ;
};`
I'm getting the following error on the console:
Uncaught TypeError: Cannot read properties of undefined (reading 'create')
Any idea?
Thanks.

I'm also experiencing this issue after upgrading react-scripts to version 5.0.1. Any updates on this?

repo: ponymessenger/use-prosemirror


text:
Sfont compile fixes

sfont~.c compilation was broken due to a recent source change in shared/elsefile. Also added an auto-detection for Homebrew in the Makefile. (pd-lib-builder just always assumes Fink, but many people, myself included, use Homebrew these days.)

BTW, if sfont~ is an (optional?) component of ELSE, why not have a target for it in the main Makefile, and have it installed in the proper location? Not sure how pd-lib-builder does make in subdirs, though.

actually I don't build sfont~ from ELSE and use prebuilt binaries and just copy them. The actual repository is in https://github.com/porres/pd-sfont and this is all quite messy, I know.
The thing is I don't really know how to compile this myself, I need the help of others and can only compile myself for macOS see https://github.com/porres/pd-sfont/issues/27
Also, I believe this would be better if it could be statically linked, there are a few issues with it also, see https://github.com/porres/pd-sfont/issues/30
@timothyschoen does compile them statically but it's also messy.

I actually have this working in the real repository https://github.com/porres/pd-sfont/search?q=panel_click_open
best to just update elsefile in here

sfont~.c compilation was broken due to a recent source change in shared/elsefile.

Oh no, I made changes to elsefile recently, did I do this?

Oh no, I made changes to elsefile recently, did I do this?

nope... anyway, I updated it now so ELSE is in line with https://github.com/porres/pd-sfont

Hmm, I see that you instead opted to revert Tim's changes from #1385. Can you explain why? Tim did these to resolve some public symbol clashes between cyclone and ELSE. Which not only affects plugdata, but, as Tim pointed out in #1385, this makes it potentially hazardous to use cyclone alongside ELSE in vanilla as well. I'm with Tim on these; I think that these changes are necessary.
Tim just overlooked two instances of these symbols in the sfont~ subproject. That's something which can happen easily, and was also very easy to fix, as I did in this PR.

Oh, so it was his fault :)
damn, can you do it again @timothyschoen ? I see I have to update this also in the sfont repo instead

No worries, I can send you another PR to fix things up again.

sorry guys, I just got really confused, can anyone just send me a PR with

No worries, I can send you another PR to fix things up again.

great, thanks

Well, it would be nice if you could stop committing new stuff to master while I'm doing this, so that my changes will apply cleanly.

Also, can you please reopen this PR so that I can update it? Thanks.

Oh well, I guess that I'll just submit a new PR then. Alexandre, you're really confused sometimes. ;-)

New one up at #1424.

authors: agraef porres timothyschoen

repo: porres/pd-else

license: WTFPL


text:
Import default + others not working

As discussed on the Mithril channel, something like import modal, {status1, status2} from './modal' doesn't work. You suggested it was a regex issue, and after studying it, it looks like the isModuleRegex.test() is returning undefined. I could make it work by adding |\w just before (?!type). Not sure if that's correct, though.

Hi @osban. So sorry I didn't get around to answer you on gitter.. It's been really busy around here, but I did manage to fix it with this commit : https://github.com/porsager/flems/commit/7a1b8a83a08a70da18d2480b5df5393fa7dc4178
I think \w would bring some false positives, but the above is better and fixes the issue, I just haven't gotten around to deploying to flems.io yet.
Hopefully tonight or tomorrow 😉
Thanks for the help 😉

Ok finally got around to deploying to flems.io as well ;) sorry for the wait

Great! No worries, I only created the issue because I thought you might've forgotten ;)

authors: osban porsager

repo: porsager/flems


text:
[Feature Request] image search in REPOSITORY support

Support search image in REPOSITORY I think it's very useful when people create container or service or pull images (in create service, create container, pull images pages),
for example like this:
Create a service, usd cirros, search cirros

cc @ncresswell

Yeah,  nice to have feature, but lower in priority.
Rgds,
Neil Cresswell
On 16/07/2018, at 6:43 PM, Anthony Lapenna <notifications@github.commailto:notifications@github.com> wrote:
cc @ncresswellhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ncresswell&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=EQhT4mLMvev4zlZyfQ1SlkftyMFERFsmHMSheJVGwXQ&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2043-23issuecomment-2D405160254&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=xIgyCulmWOMakgPYaT0gEsekeL3Ew2DD-yxak34U_Wc&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlfzM0Nm5-5F2KGS6KX-2Db3pO1jlkM7uks5uHDYJgaJpZM4VQKP5&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=3CH4pbGQ9EQY8awUJ4alLM0S77T46ieFnJG147SeIAc&s=Ag-9aIARNihQn7AOuwn4pp99vCVDP2FLJBBVd4E6X_c&e=.

Super disagree with search being of lower priority. With all the other great features of Portainer, this seems a very odd omission. Not sure how you guys work, but I often browse through docker hub looking at various images before choosing one to use. Synology's docker package and Cockpit's container management both have this feature, so it seems out of place that I have to have 2 browser windows open and copy and paste the image name to portainer

Same here, should be high as priority

Tghis really is the only missing thing using portainer

authors: a575606 aiminickwong deviantony luftschlucker ncresswell rumples-GitHib

repo: portainer/portainer

license: Zlib


text:
404 error for https://portainer.io/download/portainer-agent-stack.yml

Bug description
Downloading the stack file (as described in https://portainer.readthedocs.io/en/stable/deployment.html#inside-a-swarm-cluster) fails. It reports http error 404 - page not found.
Expected behavior
I should get the yaml file.
Steps to reproduce the issue:
open this link: https://portainer.io/download/portainer-agent-stack.yml
Technical details:

Browser: firefox

Additional context
Work-around: open the link shown on https://www.portainer.io/download/

@SimonHeimberg We're sorry for this and are currently updating our website as well as our asset service.
Documentation will be updated soon. In the meantime I'll keep this issue open.
Note, file can be accessed via https://downloads.portainer.io/portainer-agent-stack.yml
curl -L https://downloads.portainer.io/portainer-agent-stack.yml
 -o portainer-agent-stack.yml

Documentation and website updated.

authors: SimonHeimberg deviantony


text:
[Feature Request] Built-in Management for haproxy / nginx proxy instance.

For people who have used some of the larger orchestration tools, most allow you to manage some form of reverse proxy with integration into the deployment gui.
This allows for easily reusing ports 80/443 without managing your own reverse proxy. It spins up a managed container, and maps dns to container ips for easy access without using -p or managing your own instances.
If portainer could manage a instance of haproxy for example which we could map to from the container interface (during creation or after) that would be awesome.
Basic Features would be: DNS to Container IP Mapping, Managing SSL Certificates for Mappings.
More advance would be mapping based on labels or environmental variables. (ie: docker/dockercloud-haproxy)

maybe look for Containous/Traefik...

Just a suggestion, can integrate with something like this - https://github.com/jwilder/nginx-proxy for nginx.

Those services should be added in default templates
Users can choose to use them or not
Services likes :

containous/traefik
docker/dockercloud-haproxy
jwilder/nginx-proxy
And some others maybe

Closing in favor of #2045

authors: WTFKr0 davistan deviantony gjaegle xInsertx


text:
Custom OAuth Provider with Microsoft Graph API

Bug description
When configuring a custom OAuth provider to use Azure AD, it fails to login when using the Microsoft Graph API (https://graph.microsoft.com).
Expected behavior
The OAuth login flow should work with the Microsoft Graph API, as the Azure AD Graph API has been deprecated (https://techcommunity.microsoft.com/t5/azure-active-directory-identity/end-of-support-for-azure-ad-graph-permission-sign-up-through/ba-p/2464404), and full support will be dropped in June 2022.
Portainer Logs
management_portainer.1.yatburcnap71@esdocker-swarm01    | level=info msg="2022/02/08 15:30:48 http error: Unable to authenticate through OAuth (err=Unauthorized) (code=500)"
management_portainer.1.yatburcnap71@esdocker-swarm01    | level=info msg="2022/02/08 15:31:28 [DEBUG] - Failed retrieving oauth user name: invalid character '<' looking for beginning of value"
management_portainer.1.yatburcnap71@esdocker-swarm01    | level=info msg="2022/02/08 15:31:28 [DEBUG] - OAuth authentication error: invalid character '<' looking for beginning of value"
management_portainer.1.yatburcnap71@esdocker-swarm01    | level=info msg="2022/02/08 15:31:28 http error: Unable to authenticate through OAuth (err=Unauthorized) (code=500)"
management_portainer.1.yatburcnap71@esdocker-swarm01    | level=info msg="2022/02/08 15:31:57 http error: Error looking up service (err=Error: No such service: de7p0mu2rwoscm9r6l6mlravg) (code=500)"

Steps to reproduce the issue:

Configure OAuth provider as per Portainer Docs (https://docs.portainer.io/v/ce-2.11/admin/settings/authentication/oauth#azure)\
Use Microsoft Graph API for Resource URL

Technical details:

Portainer version: 2.11.1
Docker version: 20.10.12
Platform (windows/linux): linux
Command used to start Portainer: docker stack deploy ... using docker-compose.yml
Browser: Firefox
Use Case: Using Portainer at Home.
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
All the documentation around setting up the Azure OAuth provider on Portainer-CE is still pointing at the now deprecated Azure AD Graph endpoint (https://graph.windows.net/{tenant id}/me?api-version=2013-11-08).
More information available on deprecation: https://devblogs.microsoft.com/microsoft365dev/end-of-support-timelines-for-azure-ad-authentication-library-adal-and-azure-ad-graph/.
From what I can see the Go Lang OAuth provider should support the Microsoft Graph API.

Managed to find the recommended configuration for Microsoft graph API. This will likely break when using the Microsoft OAuth provider and will need to be updated: https://github.com/portainer/portainer/blob/edf048570bd3f2fe6903fbf95f4483149d7bfd4c/app/portainer/oauth/components/oauth-settings/providers.js
The graph endpoint used: https://graph.microsoft.com/v1.0/{{ tenant ID }}/me


text:
fix(k8s):fix difficulties selecting mixed protocols when creating k8s application EE-1073

close EE-1073

Close https://github.com/portainer/portainer/issues/5521

authors: WaysonWei huib-portainer


text:
Blockers for alpha release

[ ] Decide on defaults for formatter
[ ] Add some basic documentation
[ ] Add the TOML configuration parser (it will be nice to have hierarchical configuration option setting eventually) https://github.com/posit-dev/air/issues/83
[ ] Develop the CLI enough to be able to format with a few configurable options
[x] Binaries for air using ruff approach https://github.com/posit-dev/air/pull/67
[ ] OpenVSX extension
[ ] VS Code Marketplace extension
[ ] README with installation instructions

[ ] Instructions for Positron / VS Code
[ ] Instructions for RStudio

Great tools! I have tried to install the CLI in my computer and it worked

repo: posit-dev/air


text:
docs: Upgrading Core links to Express links isn't always wanted

The quartodocs rendering process finds shiny.ui.___ links and upgrades them to shiny.express.ui.____ links
https://github.com/posit-dev/py-shiny/blob/ea5db0e222c39128202da9d54afe51488f660d87/docs/_renderer.py#L61-L72
but this isn't always desirable, as in the case of :func:`~shiny.ui.page_auto` which only exists in shiny.ui. When the Express counterpart doesn't exist, the function is rendered as code without a link. See https://shiny.posit.co/py/api/express/express.ui.page_opts.html

I'm ok if we white list exceptions until a bigger pattern emerges. The docs handling code doesn't need to be pretty

Maybe we could try importing converted using something like this, then informatively warn/error if it doesn't exist?

...or just use the original link if the converted link doesn't exist.

authors: cpsievert gadenbuie schloerke

repo: posit-dev/py-shiny


text:
🛑 ku-s is down

In 41ef611, ku-s ($KU_API_STATUS_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ku-s is back up in 57f586e.

repo: positive-infinity/api-status


text:
Fix critical vulnerability CWE-78

Since the uniqid package depends (sadly) on macaddress, it causes https://nodesecurity.io/advisories/654 to pop up in the npm security audits of the huge amount of packages that depend on postcss-filter-plugins. A hardware-based ID wasn't really needed, so I replaced it with (version 4) UUIDs which will be just as unique.

Thanks for submitting this; my question is why do we need a UUID function; wouldn't just a plain old Math.random().toString() works?

Fixed in https://github.com/postcss/postcss-filter-plugins/pull/19.

authors: Narvey RyanZim

repo: postcss/postcss-filter-plugins

license: mit

license_source: bigquery


text:
Table & Replace function yields "Error: Schema must contain unique named"

I have a table and a function to replace all values of a project within the table. Code below. When trying to get postgraphql started for this I get this error: Error: Schema must contain unique named types but contains multiple types named "RevenueYear".
Am I doing something wrong or is this a bug? Any feedback greatly appreciated
create table vb.revenue_year (
  id               uuid primary key default vb_private.uuid_generate_v1mc(),
  project_id        uuid not null references vb.project(id),
  year              smallint,
  revenue           real, -- 6 digits precision
  revenue_target    real
);

CREATE FUNCTION
  vb.revenue_year_replace_all(project_id uuid, input vb.revenue_year[])
RETURNS vb.revenue_year[]
    LANGUAGE plpgsql
    AS $_$
DECLARE
	ret vb."revenue_year"[];
BEGIN
  DELETE FROM vb."revenue_year" where project_id = $1;
  INSERT INTO vb."revenue_year"
      (project_id, "year", revenue, revenue_target)
      SELECT
      (a)."project_id",
      (a)."year",
      (a)."revenue",
      (a)."revenue_target"
      FROM (SELECT unnest($2) AS a) x WHERE (a)."project_id" = $1
      returning * into ret;
    RETURN ret;
END;
$_$;

grant execute on function vb.revenue_year_replace_all(uuid, vb.revenue_year[]) to vb_person;

So that error means that two things are boiling down to the same name: "RevenueYear". Without your whole schema I can't tell you what they are but look for things named:

revenue_year
revenue_years
"revenueYear"
"revenueYears"
"RevenueYear"
"RevenueYears"
etc

Likely there is more than one of them, and the conversion of them to GraphQL is causing a clash.
What version of PostGraphQL are you using?

I use version 3.2.0.
When I drop the function it works (keep the table) it works, so it seems related to the function I posted above.
PS) (I corrected a slight error in my post - it said create table vb.project_revenue_year, not create table vb.revenue_year)

So that function references vb.revenue_year (both in the argument list and the return type); is that table already exposed?
Ooo, I wonder if it's because it's an array - do you use vb.revenue_year[] anywhere else? We've recently squashed a whole load of array-of-compound-types bugs in v4 - maybe give that a try? npm install -g postgraphql@next (see #506 for breaking changes).

I tried to upgrade to v4 and it solved the problem. Thanks a lot @benjie!

authors: benjie dmattsson

repo: postgraphql/postgraphql


text:
docs: update readme

docs update increment methods

Thanks but you don't need an increment action with pinia!

repo: posva/pinia


text:
Can't open file syntax/jade.vim

Hi
When i try to open a file.vue, i have this error :
 Can't open file syntax/jade.vim

Any idea ?
Thanks !

@stephanedemotte I just started using Vue last night and encountered this same problem.  On the offhand chance that you haven't figured this out yet, it's failing because you're missing a syntax file for Jade which doesn't come with a default installation of vim.  In my case, I was missing CoffeScript and Stylus.
To fix the issue, install this plugin:

Jade https://github.com/digitaltoad/vim-jade

Other possible culprits for people who stumble upon this same issue:

CoffeeScript https://github.com/kchmck/vim-coffee-script
Stylus https://github.com/wavded/vim-stylus

There's gotta be a way to use Vundle, pathogen, or w/e. to fetch these dependencies on install, but I don't have time to sort that out and open a PR on this project right now.

@stephanedemotte God, I'm sorry, I wasn't watching my repo so I wasn't receiving any notifications...
As @gconsidine pointed it out, you're missing the some syntax files. I need to just disable the syntax highlight if the syntax is missing... That'd be easier.

@gconsidine Thank you very much BTW. That was such a nice answer :smiley:

Thanks all :)

authors: gconsidine posva stephanedemotte

repo: posva/vim-vue


text:
intensityScale not calculated correctly

The potree converter is not functioning correctly when an Intensity Range is specified. The following line:
https://github.com/potree/PotreeConverter/blob/0c8d08480310d55fa2d2dae500a2771d30e246e9/PotreeConverter/include/XYZPointReader.hpp#L68
needs to be changed to:
https://github.com/potree/PotreeConverter/blob/ce40b22ddf2d9506b2faedb413ee6f51e5d3e9c6/PotreeConverter/include/XYZPointReader.hpp#L66
In it's current implementation the intensityScale does not correctly take into account the lower value when not set to 0. For example when the intensityRange is set as follows [-4, 4] and [2, 4] it will calculate intensityScale to be 4 when it should in actual fact be 8 and 2 respectively.
I tried to push this commit about a year ago but it was rejected when it failed the travis-CI test which wasn't implemented when i initially committed: https://github.com/potree/PotreeConverter/commit/ce40b22ddf2d9506b2faedb413ee6f51e5d3e9c6

The link leads to "page not found".
I'm a bit confused because ``intensityScale = ìntensityRange[1] - intensityRange[0]``` sounds right to me whereas colorScale is the one that needs to be changed to do the same thing that intensityScale does?

Sorry about that I seem to have gotten myself confused and the original commit I tried to push didn't go through but seems to have been fixed since then anyway.
the original line used to be this:
intensityScale = (float)intensityRange[1];

authors: headart potree

repo: potree/PotreeConverter


text:
🛑 PowBot SDN is down

In 7226704, PowBot SDN (https://api.powbot.org/products) was down:

HTTP code: 502
Response time: 497 ms

Resolved: PowBot SDN is back up in dc72579 after 9 minutes.

repo: powbot/status


text:
Stop add event on child list from propagating to parent list

See https://github.com/powmedia/backbone-forms/issues/502

@exussum12 - although stopPropogation is fairly severe, the Add button is really only used for the list editor - I can't forsee any fallout, but can you?

Going to merge this as we only use the event in the forms.

authors: glenpike miketonks

repo: powmedia/backbone-forms


text:
Proposal: kf-app CRDs

The following is a proposed CRD for representing a kf app, called kf-app throughout this document.
In theory the kf controller will use this CRD to:

Build the app
Serve the app
Update the app if properties change
Supply an event stream

The kf-push command will:

Upload source as a container image, (currently via kontext)
Apply a new kf-app object
Listen for controller events and status conditions to replicate the build/deploy output of cf push

Here is the rough draft for the CRD itself. I followed the documentation here
Note that my use of comments. This is either for brevity or for sections which still have ambiguous requirements.
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: kfapps.some-group
spec:
  group: some-group
  versions:
    - name: v1alpha1
      served: true
      storage: true
  scope: Namespaced
  names:
    plural: kfapps
    singular: kfapp
    kind: KfApp
  validation:
    openAPIV3Schema:
      properties:
        spec:
          properties:
            src-image: some.com/docker/uri:latest (uploaded via context during cf push)
            # The properties here would match those of an `application` in a CF manifest)
            # see https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#optional-attributes)
status:
  conditions:
    - # src-image updates
    - # kbuild updates
    - # kserve updates

However, CF app manifest files support multiple files. Here's a couple of push use cases:

cf push multiple app manifest: client pushes 1 image, creates n kf-app CRDs
cf push multiple app manifest but selects one app: client pushes 1 image, creates 1 kf-app. Note that this is identical to case 1 if the manifest has 1 app
cf push with no manifest: client creates a pseudo-manifest (abstracted away from the user), continues as if case 1

Now I'm not sure if CF manifests supply top level configuration which is applied to all apps in a cf manifest file. I think this sort of functionality is deprecated, but can someone confirm?
Conditions (and status in general) should be convenient for the controller; the ideas I have above are just a rough idea.
the docker app lifecycle
Cloud Foundry applications can follow the buildpack app lifecycle (src) or the docker app lifecycle (src).
In both cases an application can use a CF manifest. See the docker attribute in manifest files for more info.
However, we use buildpacks.io, also known as Cloud Native Buildpakcs, which is a slightly different thing, and I do not know if buildpacks.io support docker images in the same manner CF does.  ¯\(ツ)/¯
To support both (and in general, multiple) lifecycles, we need a way to detect which one an app follows.
I believe cf does this by knowing that the docker and buildpacks attributes must be mutually exclusive. We could do the same check when creating the schema, or even better put this logic into the validation schema.
Alternatively, this "detection" could happen client side, and the CRD could have a lifecycle_type string field. I would recommend against this in the initial design, because it seems we could add it later with little consequence.

Couple of thoughts:

Would you expound on the structure for different cases e.g. what does a docker only deploy look like compared to a source deploy?
What do you think about following Knative's lead and using the standard Kubernetes pod spec as a base? That would make our syntax similar to Pods/Deployments/KSvc/RepliaSets.
What do you think about using this CRD to manage an app's state? (started | stopped)

Would you expound on the structure for different cases e.g. what does a docker only deploy look like compared to a source deploy?

I added a section that speaks to the docker app lifecycle. It seems that CF manifest files are composed with restrictions such that CF can tell which lifecycle to take by the manifest structure. From the cf docs:
Note: Using the docker attribute in conjunction with the buildpacks or path attributes will result in an error.

In the docker case, src-image would be the compiled image, and no build pipeline would be required.

What do you think about following Knative's lead and using the standard Kubernetes pod spec as a base? That would make our syntax similar to Pods/Deployments/KSvc/RepliaSets.

I envision this CRD having top-level knative, istio, and tekton resource templates under it, but not pods.
In the link you posted: PodSpec is referenced in a RevisionSpec, and a RevisionSpec is referenced in a Revision, but a PodSpec is not referenced on a Revision or any higher level concept. So since kf-app is the root level abstract, why should it concern itself with the actual pods?

What do you think about using this CRD to manage an app's state? (started | stopped)

Yes, thats my intention. The CRD's status would contain the top level status string, plus the status of the underlying components. The controller would be what sets this information.

I envision this CRD having top-level knative, istio, and tekton resource templates under it, but not pods. In the link you posted: PodSpec is referenced in a RevisionSpec, and a RevisionSpec is referenced in a Revision, but a PodSpec is not referenced on a Revision or any higher level concept. So since kf-app is the root level abstract, why should it concern itself with the actual pods?

Here's the deck where they talk about inlining PodSpecs as the base for Knative 0.6 and beyond: https://docs.google.com/presentation/d/10wuLMFXyol731WKuO5x7lalWrH0A6YVHa4exIERQaQ8/edit Their argument is that Deployment, ReplicaSet, DaemonSet, StatefulSet, and Jobs all embed PodSpecs so they should too rather than inventing their own template.
My general thought was that we should probably reflect the look and feel of Knative/K8s rather than copying fields directly over from the app manifest. For example, cf app manifests have an env map, but maps are an anti-pattern in K8s. It sounds like you're planning on doing a template like thing to solve that so I'm happy.

Yes, that's my intention. The CRD's status would contain the top level status string, plus the status of the underlying components. The controller would be what sets this information.

Ah, I was thinking we should be able to set it on the spec field as well so a user could stop an app by setting the field to "stopped" or the like. I filed an issue with Knative serving and it looks like a feature we'll have to implement at this level rather than farther down: https://github.com/knative/serving/issues/4262

@mattysweeps and I had a whiteboarding session to fill in the details for the CRD.
Specifically, we wanted to ensure it could support the following operations:

push
start
stop
scale
restage
stage
restart

Under the following scenarios:

An operator patches a base image, and wants to rebuild apps but doesn't have the source.
A developer wants to change some property of the app without needing to rebuild.
A developer sees that something went wrong during the build and wants to re-trigger without changing anything.
A developer or operator wants to take an applicaiton down temporarially.

apiVersion: kf.dev/v1beta1
kind: Application
metadata:
  name: some-app
spec:
  source:
    uid: # if changed, forces a rebuild, even if all other fields are the same.
    docker:
      image: gcr.io/my-company/myapp # the path to the docker image
      credentials: # a secret containing the credentials to connect to the image repo
    buildpackBuild:
      source:
      stack:
      buildpack:
    # potentially extended in the future for other types of build
    # like copying a docker image from an external registry to a
    # local one, builds from Dockerfiles, etc.
  template:
    uid: # if changed, forces a restart, even if all other fields are the same.
    scale:
      min: 0 # minimum scale
      max: 0 # maximum scale, 0 for inf
    spec:
      # This is a PodSpec minus the image name.
      # It holds environment variables, quotas, etc.
      # It will be copied directly to a Kservice once the build
      # completes.
  routes:
    # This is an abstraction over a VirtualService that provides
    # cf-like functionality.
  services:
    # this field will hold references to secrets along with
    # the metadata needed to turn them into VCAP style
    # environment variables.

  # if false, the app is "stopped", serving.service gets scheduled
  # a dummy container and we tell Istio to 404 all the routes.
  # this is at the top level because it affects multiple resources.
  serve: true | false
status:
  build:
    # status of the build
    image: # the image the build says we should use for serving
  service:
    # status of the service
    # probably embedding the serving.service
  routes:
    # status of the routes
  services:
    # status of the attached services

The source, routes and services fields will be broken out into further
(hidden) CRDs that can be implemented independently and contributed back upstream.

@josephlewis42 I'm very excited about this. I had a few questions/comments:

Does the stage operation map to cf push myapp -i 0?
In regards to docker.credentials, should this be a service account instead? That seems to be the normal way knative receives this type of information.
So the implication of having stack and buildpack listed separately is that the space configuration (that will drive what builder the space uses) will need to instead have a collection of builders. The reason for this is, a builder can only reference a single stack. Therefore if we want to support the use case where CF upgraded from cflinuxfs2 to cflinuxfs3, we would have a builder for each.
Scale's sentinel values are confusing. If I set scale.min=0 and scale.max=0, I think I would expect the number of instances to stay 0. However, this looks like it would simply set it normal autoscaling. How would I scale the app to 0 (I see that I would need to set serve=false, however I'm not sure I find this intuitive)? Could we instead use -1 or just recommend a huge number?
serve seems redundant to scale in some way (This assumes the sentinel values are adjusted).

Does the stage operation map to cf push myapp -i 0?

I think that would depend on how we mapped the -i flag. If we mapped it to also ensure the app was stopped at 0, then yes.

In regards to docker.credentials, should this be a service account instead? That seems to be the normal way knative receives this type of information.

That's a good question. Today a user can set credentials in the app manifest, but we didn't want to have those plaintext in the cluster. Maybe we could implement a hook similar to Secrets that translates plaintext values to a service account or secret and replaces the values with that? WDYT?

So the implication of having stack and buildpack listed separately is that the space configuration (that will drive what builder the space uses) will need to instead have a collection of builders. The reason for this is, a builder can only reference a single stack. Therefore if we want to support the use case where CF upgraded from cflinuxfs2 to cflinuxfs3, we would have a builder for each.

We debated a bit what we wanted stack to mean in this context and weren't fully sure. WDYT about allowing that field to contain either an alias ("cflinuxfs3", "alpine") or a full buildpack builder image?
It would be the responsibility of a space to ensure that any apps put in that space had a valid image chosen from a list of available ones. The space could hold aliases for each image and replace on the fly so you could have multiple builders supporting say "alpine" or "cflinuxfs3". That would also allow us to support things like a heroku stack.

Scale's sentinel values are confusing. If I set scale.min=0 and scale.max=0, I think I would expect the number of instances to stay 0. However, this looks like it would simply set it normal autoscaling. How would I scale the app to 0 (I see that I would need to set serve=false, however I'm not sure I find this intuitive)? Could we instead use -1 or just recommend a huge number?
serve seems redundant to scale in some way (This assumes the sentinel values are adjusted).

It is confusing, but I'd like to keep the 0 value being the default for when we translate to/from go structs if possible. I think we need some other field to keep track of state so we can stop/start without losing whatever we'd set before. Maybe it would be less confusing if we brought it into the top level with something like this:
instances: # scale to n
  exactly: 3

instances: # scale to 0
  max: 5

instances: # stopped
  stopped: true
  min: 1
  max: 5

Where the implementation of instances is:
instances:
  stopped: # true if the service and routes should stop traffic
  exactly: # exactly this number can run
  min: # minimum of this number
  max: # maximum of this number, 0 = infinite

Maybe we could implement a hook similar to Secrets that translates plaintext values to a service account or secret and replaces the values with that? WDYT?

I like this idea. I think it warrants its own proposal and discussion. Would developers store their own credentials in this same way? I believe cf cups was often used for this before, but that was less than desirable.

I've started this in the feature/kfapps branch, but unfortunately I am blocked by https://github.com/kubernetes/kubernetes/issues/79149
Update: no longer blocked by this

authors: josephlewis42 mattysweeps poy

repo: poy/kf


text:
Application Error

Hi @nishantspanwar thanks for opening an issue but I can't do anything without the logs and a description of what you tried to do.

I just completed the setup as per the guide and then open the app. How can I get the logs when I look for logs (More > View logs) it shows nothing

I have the Build Logs if you can catch something from that.
`-----> Node.js app detected
-----> Creating runtime environment
   NPM_CONFIG_LOGLEVEL=error
   NODE_ENV=production
   NODE_MODULES_CACHE=true
   NODE_VERBOSE=false

-----> Installing binaries
engines.node (package.json):  >=10.0.0
engines.npm (package.json):   unspecified (use default)
   Resolving node version >=10.0.0...
   Downloading and installing node 13.7.0...
   Using default npm version: 6.13.6

-----> Installing dependencies
Installing node modules (package.json + package-lock)
   > quiz-player-app@1.0.0 preinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee
   > rm -fr src/client/resources/dist

   > fibers_node_v8@3.1.5 preinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers_node_v8
   > node preinstall.js

   > fibers@4.0.2 install /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers
   > node build.js || nodejs build.js

   make: Entering directory '/tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers/build'
     CXX(target) Release/obj.target/fibers/src/fibers.o
     CXX(target) Release/obj.target/fibers/src/coroutine.o
     CC(target) Release/obj.target/fibers/src/libcoro/coro.o
     SOLINK_MODULE(target) Release/obj.target/fibers.node
     COPY Release/fibers.node
   make: Leaving directory '/tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers/build'
   Installed in `/tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers/bin/linux-x64-79-glibc/fibers.node`

   > fibers_node_v8@3.1.5 install /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/fibers_node_v8
   > node build.js

   ignore install

   > husky@3.1.0 install /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/husky
   > node husky install

   husky > Setting up git hooks
   Command failed: git rev-parse --show-toplevel --git-common-dir
   fatal: not a git repository (or any parent up to mount point /)
   Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
   husky > Failed to install

   > ejs@3.0.1 postinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/ejs
   > node ./postinstall.js

   > nodemon@2.0.2 postinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/nodemon
   > node bin/postinstall || exit 0

   Love nodemon? You can now support the project via the open collective:
    > https://opencollective.com/nodemon/donate

   > husky@3.1.0 postinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee/node_modules/husky
   > opencollective-postinstall || exit 0

   > quiz-player-app@1.0.0 postinstall /tmp/build_072e4ff920c2ac636a37ad9d24e98eee
   > mkdir -p src/client/resources/dist && cp node_modules/normalize.css/normalize.css src/client/resources/dist/.

   added 2129 packages from 958 contributors and audited 909355 packages in 72.04s

   29 packages are looking for funding
     run `npm fund` for details

   found 3 vulnerabilities (1 low, 1 moderate, 1 high)
     run `npm audit fix` to fix them, or `npm audit` for details

-----> Build
Running build
   > quiz-player-app@1.0.0 build /tmp/build_072e4ff920c2ac636a37ad9d24e98eee
   > lwc-services build -m production

   ⚡⚡⚡⚡⚡  Lightning Web Components ⚡⚡⚡⚡⚡

   ⌛  Creating build configuration
   📦  Starting build process.
          Build duration: 8.013
   🎉  Build successfully created.

-----> Caching build
- node_modules
-----> Pruning devDependencies
   > husky@3.1.0 preuninstall node_modules/husky
   > node husky uninstall

   husky > Uninstalling git hooks
   Command failed: git rev-parse --show-toplevel --git-common-dir
   fatal: not a git repository (or any parent up to mount point /)
   Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
   husky > Failed to uninstall
   removed 67 packages and audited 909048 packages in 18.051s

   28 packages are looking for funding
     run `npm fund` for details

   found 3 vulnerabilities (1 low, 1 moderate, 1 high)
     run `npm audit fix` to fix them, or `npm audit` for details

-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> web
-----> Compressing...
Done: 90.4M
-----> Launching...
Released v4
https://lk-sf-devs.herokuapp.com/ deployed to Heroku`

I can add you as a collaborator if you want.

I don't think that's necessary. Looking at the logs, it seems that the app isn't connecting to Salesforce.
Can you double check your Heroku config variables (username, password, personal security token...) and restart the dyno?

Great! It worked. I used the access token generated by the SFDX CLI earlier using the
H:\QuizApp\quiz-host-app>sfdx force:user:display -u <username> command.
I generated the security token and password with the legacy way from setup and it worked.
Thanks for the support and we can close the issue now.

authors: nishantspanwar pozil

repo: pozil/quiz-host-app


text:
Update golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign  after the PR has been reviewed.
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Update conformance jobs to use latest all-in-one

Changing the CI conformance jobs to use the latest all-in-one image with upgraded Terraform.
https://github.com/ppc64le-cloud/test-infra/pull/179
Removing the plugins installation steps as they are available in all-in-one:0.3 image.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Rajalakshmi-Girish
To complete the pull request process, please assign mkumatag after the PR has been reviewed.
You can assign the PR to them by writing /assign @mkumatag in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @mkumatag

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mkumatag, Rajalakshmi-Girish
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mkumatag]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Rajalakshmi-Girish: Updated the job-config configmap in namespace prow at cluster default using the following files:

key test-kubernetes-periodics.yaml using file config/jobs/periodic/kubernetes/test-kubernetes-periodics.yaml
key kubernetes-postsubmit.yaml using file config/jobs/ppc64le-cloud/builds/kubernetes-postsubmit.yaml

In response to this:

Changing the CI conformance jobs to use the latest all-in-one image with upgraded Terraform.
https://github.com/ppc64le-cloud/test-infra/pull/179
Removing the plugins installation steps as they are available in all-in-one:0.3 image.

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

authors: Rajalakshmi-Girish ltccci


text:
hi practice

hihi

안녕

repo: ppjjyo/github-slideshow


text:
是否有人曾提过类似的问题？
否（No）
你觉得APP有什么不足之处？
大佬在wiki里面也提到了，现在的企业微信应用需要可信ip才能进行转发，但是家用宽带最多只给动态公网ip，我专门买了一台vps做微信转发代理，但是应用里面并没有这个选项
你觉得该怎么去完善会比较好？【非必答】
No response

直接反向代理（proxy_pass）api地址？

请重新下载每周构建版测试
https://github.com/pppscn/SmsForwarder/actions/workflows/Weekly_Build.yml

请重新下载每周构建版测试 https://github.com/pppscn/SmsForwarder/actions/workflows/Weekly_Build.yml

已经下载测试了，但是填入我自己搭建的微信转发代理之后，点击测试提示not found

反向代理到这个  https://qyapi.weixin.qq.com/cgi-bin 吗?

反向代理到这个 https://qyapi.weixin.qq.com/cgi-bin 吗?
或者 你贴一下你的反向代理配置

location /cgi-bin/gettoken {
proxy_pass https://qyapi.weixin.qq.com;
}
location /cgi-bin/message/send {
proxy_pass https://qyapi.weixin.qq.com;
}
location  /cgi-bin/menu/create {
proxy_pass https://qyapi.weixin.qq.com;
}

已经按 proxy_pass https://qyapi.weixin.qq.com/; 处理，请重新下载每周构建版测试
https://github.com/pppscn/SmsForwarder/actions/workflows/Weekly_Build.yml

已经按 proxy_pass https://qyapi.weixin.qq.com; 处理，请重新下载每周构建版测试
https://github.com/pppscn/SmsForwarder/actions/workflows/Weekly_Build.yml

已经测试成功了，非常感谢大佬的耐心

repo: pppscn/SmsForwarder


text:
fix joystick-related binding issues & raise button limit

Joystick AxisNegative & AxisPositive buttons to respect deadzones
Prevent deadzones from being less than FLOAT_EPSILON as this hurts the math
Add support for up to 128 joystick buttons

Currently, if you try to bind your keys (even keyboard / mouse) while a joystick is plugged in, Osu will record the ever-present wiggle of the axes due to there not being a deadzone for the virtual joy buttons. Another issue is that when a deadzone is not set, a value of 0 is used, which will cause issues since we're working with floats.
The button limit increase for https://github.com/ppy/osuTK/pull/59 also made it in here.

For future contributions, please make sure to make a branch called something related to the change (ie. don't make pull requests from your "master" branch).

authors: galister peppy

repo: ppy/osu-framework


text:
Make nullability checking more defined

Currently, checking nullability only takes in account whether a given type is a generic or not. This check is very lossy as it may return true to other generic types even if its not Nullable<> and does not reflect the XML doc for IsNullable. The change makes it so that it properly checks if the type is a Nullable<>.

Needs tests added to https://github.com/ppy/osu-framework/blob/master/osu.Framework.Tests/Extensions/TestIsNullableTypeExtensions.cs

I'm confused by the test case added in f147b4a. It doesn't fail when cherry-picked onto master. And upon a manual check in sharplab it has no right to:

@LeNitrous can you explain where precisely did you first run into this, and update the test case so that it actually demonstrates the case where the method didn't work properly for you? I'm not saying that the change is invalid (it looks more proper), but right now it is hard to objectively justify it without a concrete example where the old code was failing.

Yeah I also saw the change and the description and noticed a discrepancy, the original code would only be caching non-nullable types as null and therefore not have any effect on the end result of the method.

For the record, was this closed as "no longer deemed necessary"?

Yes

authors: LeNitrous bdach frenzibyte peppy smoogipoo


text:
how to reset filepond instance?

   let pond;
  //open popup modal window select files
   function importpic() {
     $('#importModal').modal('toggle');
     $('#label').val('');
     $('#description').val('');
     const inputElement = document.querySelector('input[type="file"]');
     pond = FilePond.create(inputElement);
   }
  //execute upload files
   function uploadfiles() {
     if (pond) {
       var v = $('#uploadfiles-form').valid();
       var files = pond.getFiles();
       console.log(files, v);
       if (v && files.length > 0) {
         pond.processFiles().then(() => {
           $('#importModal').modal('toggle');
           reload();
           pond.removeFiles();
         });
       }
     }
   }

first open poup modal upload files is work!but completed first upload process,second time open popup model,and select files, click uploadfiles pond.getFiles() is empty.so not process upload file,
why?how to solve this problem

As stated in the issue template, please use SO for questions

As stated in the issue template, please use SO for questions

？

Click on "New issue", it's right there:

🧠 If you have a question, please ask it on StackOverflow -> https://stackoverflow.com/questions/ask?tags=filepond

https://stackoverflow.com/questions/58522474/why-unable-to-upload-file-twice-use-filepond-component

authors: neozhu rikschennink

repo: pqina/filepond


text:
[Feature] be able to setting all options using data-attributes

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe.
The documentation shows that filepond can read options from the data attributes. I also use similar features for datatables and select2. So initially I thought this will be the same in filepond. It turns out, it's not. In datatables, I'm using data-order='[[1, "asc"]]' and it's working. For filepond, I try using data-accepted-file-types='["image/*"]' but it didn't work.
After reading the filepond source code, I found that filepond will convert the string value of the options. So now I can make this work using data-accepted-file-types="image/*" instead.
I want to know, is it possible to pass all the options only using data-attributes? I tried to use it for server settings, but so far I cannot make it work.
Describe the solution you'd like
The documentation of filepond only covers the limited example for passing the options from data-attributes. I've tried to search the issues, StackOverflow, but only find unrelated code samples. The vue-filepond code sample is also limited, only shows the simple server prop, but didn't show the advanced server setting.
If passing options using only data-attributes is possible, especially for the server option, then please add more sample code to show this capability. Perhaps each option's explanation in the documentation will show the js code and the alternative code, using only data-attributes.
Describe alternatives you've considered
I'm ready to help to update the documentation if this feature is already possible. I am also ready to help implements the features to filepond so all the filepond options can be passed from data-attributes.

To answer your question, it's not possible to use this for all options.

authors: donnykurnia rikschennink


text:
监听键盘收起

我发现输入法启动的时候，会回调IInputMethodManagerService中的windowGainedFocus该方法，这个方法中会创建EditText和InputMethodService的通道，即IInputConnectionWrapper，在创建这个Binder的过程中，需要参数InputConnection对象，而这里是可以hook住的。这样键盘收起的时候就可以监听到了。测试6.0可以检测到，不知道对于完善你的Hook是否有帮助，麻烦了。

感谢！回头我研究研究。你也可以提交 PR 呀：）

IInputConnectionWrapper是否hook成功

authors: 985557461 paozhuanyinyu pqpo

repo: pqpo/InputMethodHolder


text:
Reunião para auxiliar na montagem dos currículos

Na reunião de líderes do dia 14/04 foi conversado a respeito do quanto a nossa participação no PRACTICE pode agregar nos nossos currículos, diante disso o @Dovyski deu a ideia de realizarmos uma reunião para que ele nos auxilie em quais informações, de acordo com o trabalho de cada um, pode ser acrescentada no mesmo da melhor forma possível.
Essa issue tem como intuito definir qual a melhor data para esta reunião, eu acredito que pode ser mais no final desse semestre, ou até mesmo no intervalo que teremos entre este e o próximo semestre, que seria mais ou menos entre os dias 01/06 e 07/06. O que acham? aguardo as sugestões de vocês e então farei um doodle pra definirmos de fato.
@practice-uffs/todos

Criei as pastas dessa issue no Google Drive:

 Pasta da issue
🔽 Entrada
🔼 Saída

Boa tarde,
Eu amei a ideia e acho que será extremamente útil! Como o semestre termina dia 26, acho que podemos marcar esta reunião nas férias, para que todos consigam participar. Entre os dias 01/06 ate 07/06 está ótimo pra mim.
Atenciosamente.

Ahhh que ideia incrível!!!!!
Concordo com a Isa, uma data na semana de recesso é perfeito! Entre os dias 01 à 07 de junho.

@practice-uffs/todos, votem no doodle para definirmos o dia e o horário desta reunião.

Respondido!

Reunião para auxílio na montagem dos currículos
Sexta-feira, 4 de junho · 3:00 até 5:00pm
Informações de participação do Google Meet
Link da videochamada: https://meet.google.com/qxb-oysp-boj

O @Dovyski teve imprevistos nesta semana, com isso peço que respondam este novo doodle para que realizemos este evento no próximo período de recesso.
@practice-uffs/todos

Respondam este novo doodle para que realizemos este evento nas semanas dos dias 19/07 a 30/07.
@practice-uffs/todos

Obrigada à todos que responderam o doodle <3.
A data do evento: Reunião para auxiliar na montagem dos currículos acontecerá no dia 19/07 das 15h30 as 17h00!!!
Nosso mentor será o @Dovyski
Auxilio na montagem dos currículos: Fernando Bevilacqua
Segunda-feira, 19 de julho · 3:30 até 5:00pm
Informações de participação do Google Meet
Link da videochamada: https://meet.google.com/oqt-thte-qvm

O evento foi realizado com sucesso e ajudou muito a todos que participaram!!
Aos que não puderam a @GessicaZanon tem a gravação!!
Ficou combinado de tentarmos fazer nosso modelo de currículo e na próxima segunda-feira dia 26/072021 quem tiver alguma dúvida ou quiser que o Fernando dê algum feedback ai é só entrar na vídeo chamada de feedback dos currículos que ele vai estar a disposição.
Feedbacks currículos
Segunda-feira, 26 de julho · 3:30 até 4:30am
Informações de participação do Google Meet
Link da videochamada: https://meet.google.com/zzs-zxxs-sjq

A gravação está sendo inserida na pasta de saída! Eu comecei a gravação uns 10 minutos após o início. O site em que o Fernando está confeccionando o currículo é esse: https://resume.io/

authors: Claudineia-VR GessicaZanon MilenaPaz2020 PracticeUFFSBot isabelirk

repo: practice-uffs/programa


text:
Add newline so reStructuredText renders correctly

https://junebug.readthedocs.io/en/latest/cli-reference.html

:+1:

authors: alexmuller smn

repo: praekelt/junebug


text:
Feature questions

Polls feature - Admin can create questions, choices and map questions to the pages. Polls associated to the pages will get displayed in the front end. Basic UI alignment is covered in the polls display. Conflicts resolved and adapt to new folder structure. Polls have been created as a separate app and included in the settings. We have checked for the flake8 standards for this poll feature.

Simon, we will check for the standards in another revision and update the same here.

I merged in #4 to remove some of the commits that were already reviewed earlier.
Going forward please use git flow to manage your branches, it makes it easier to review & keep track of work in progress. It's documented in our ways of working document but please shout if we need to explain this again separately.

Looping in @bruskiza & @saeedmb8 so they're aware of the review going on and can follow along as needed.

@techaffinity thanks for the pull request, I have reviewed it. There were still a few missing {% trans ... %} and {% url ... %} bits but significantly less than #4. Also thanks for making sure pep8 compliance, there was one problem with settings/base.py having an extra new line which I've attended to.
However there does seem to be a problem with your migrations though, check the travis build logs for the details.

Sticking a foot in here... is it not a wagtail version thing? I may have similar issues.

@techaffinity please pull in the latest changes before you continue work on this. @miltontony and myself have been busy fixing a bunch of things in the mean time.

@techaffinity you've broken the build, please fix it. I will review once the build passes. I suspect it's related to @miltontony's earlier comment

We have checked this build in our end and we could see this build now that have been passed without any migration issue.

I'm going to go ahead and merge this in. If there's more work to be done please create a separate pull-request.

authors: bruskiza smn techaffinity

repo: praekelt/molo-ndoh-yep


text:
Separate fake AMQP channel from real AMQP client

We have a few tests that look for fake AQMP things on the channel objects belonging to clients. As part of the work in #1000, AMQP clients will get real channel objects instead fake ones and will have to look at channel._fake_channel to get at the fake stuff.
To make that transition easier, it seems sensible to wrap the current fake channel with a more realistic one and expose the underlying fake on channel._fake_channel.

:+1:

Reviewed 8 of 8 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

:+1:

Comments from the review on Reviewable.io

Reviewed 8 of 8 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks pending.

Comments from the review on Reviewable.io

authors: JayH5 jerith smn

repo: praekelt/vumi


text:
How can I import OpenTelemetryModuleOptions, OpenTelemetryOptionsFactory interfaces?

Expecting Behaviors
I want to configure OpenTelemetryModule with forRootAsync({ useClass: ... }) method by utilizing nestjs/config.
But, it seems that nestjs-otel package is not exporting OpenTelemetryModuleOptions, OpenTelemetryOptionsFactory interfaces.
    OpenTelemetryModule.forRootAsync({
      useClass: OtelConfigService
    }),

import { Injectable, Logger } from '@nestjs/common'
import { ConfigService } from '@nestjs/config'
import { OpenTelemetryOptionsFactory, OpenTelemetryModuleOptions } from 'nestjs-otel';

@Injectable()
export class OtelConfigService implements OpenTelemetryOptionsFactory {
  private readonly logger = new Logger(OtelConfigService.name)

  constructor(private configService: ConfigService) {}

  createOpenTelemetryOptions(): Promise<OpenTelemetryModuleOptions> | OpenTelemetryModuleOptions {
    const { hostMetrics, apiMetrics } = this.configService.get('otel')

    return {
      metrics: {
        hostMetrics: hostMetrics.enabled,
        apiMetrics: {
          enable: apiMetrics.enabled,
        },
      },
    };
  }
}

Errors
0.145 yarn run v1.22.22
0.156 $ nest build
2.123 src/otel/otel-config.service.ts:3:10 - error TS2305: Module '"nestjs-otel"' has no exported member 'OpenTelemetryOptionsFactory'.
2.123
2.123 3 import { OpenTelemetryOptionsFactory, OpenTelemetryModuleOptions } from 'nestjs-otel';
2.123            ~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.123 src/otel/otel-config.service.ts:3:39 - error TS2724: '"nestjs-otel"' has no exported member named 'OpenTelemetryModuleOptions'. Did you mean 'OPENTELEMETRY_MODULE_OPTIONS'?
2.123
2.123 3 import { OpenTelemetryOptionsFactory, OpenTelemetryModuleOptions } from 'nestjs-otel';
2.123                                         ~~~~~~~~~~~~~~~~~~~~~~~~~~
2.123
2.123   node_modules/nestjs-otel/lib/opentelemetry.constants.d.ts:1:22
2.123     1 export declare const OPENTELEMETRY_MODULE_OPTIONS = "OpenTelemetryModuleOptions";
2.123                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2.123     'OPENTELEMETRY_MODULE_OPTIONS' is declared here.
2.123
2.125 Found 2 error(s).

Which version are you using?
https://github.com/pragmaticivan/nestjs-otel/blob/main/src/index.ts#L7
https://github.com/pragmaticivan/nestjs-otel/blob/main/src/opentelemetry.constants.ts#L1

Version is 0.53.0.
How can I use forRootAsync({ useClass: ... }) with your suggested constant value?
Is there any example code?
I'm working on my first Nest.js project, so I don't know much about it yet. 😂

repo: pragmaticivan/nestjs-otel


text:
[GSSoC'23] Sudoku Game using Java

Describe the project you want to add with tech stack
The Sudoku game is a popular logic-based puzzle where players need to fill a 9x9 grid with digits from 1 to 9. The objective is to ensure that each column, each row, and each of the nine 3x3 subgrids contains all of the digits from 1 to 9 without any repetition.
I'll use JAVA to make the application.
Expected behavior
The Sudoku game as a Java desktop application allows users to play Sudoku puzzles on their computers. The application provides a graphical user interface (GUI) where users can interact with the game by selecting cells and inputting numbers.
Screenshots (optional)

Additional context (optional )
PLz assign me this issue, under GSSoC'23, I'll make a good Java desktop game.

I want to contribute to your project by working on this issue

I would like to contribute to this project. i have worked on the same project in C++, would like to try with Java too.

repo: pranjay-poddar/Dev-Geeks


text:
Frontend project

Describe the project you want to add with tech stack
Pig game
Expected behavior
a multiplayer dice rolling game.
Screenshots (optional)

Additional context (optional )

@pranjay-poddar please assign this issue to me.

Please assign me this issue. I have a frontend project.

authors: ePSA-eJya geetanjalising


text:
A resume website

Describe the project you want to add with tech stack

I want to add a resume website that has made with HTML, CSS  only.
Expected behavior

Screenshots (optional)

Additional context (optional )

@pranjay-poddar  sir, @MohitGupta121  sir and @TusharKesarwani sir please assign this issue to me under GSSOC'23

Thanks @MohitGupta121  . Also please review and merge my PR

@Developer-Swati please link your PR properly with your issue otherwise it won't be reviewed.

Ok I will look into this

Food Ordering Website by Developer-Swati · Pull Request #4145 · pra... @MohitGupta121  please review my this PR for another issue


text:
Formfield should be renamed to FormField for consistency

But it's a breaking change so it might not be doable.

lets keep this on hold till a breaking change comes from mdc-web.

@filoozom with next release Textfield is being changed to TextField do you think we should rename this as well?

Yes, for sure. I'll open a PR real quick!

authors: filoozom prateekbh

repo: prateekbh/preact-material-components


text:
Rise: Add placementId parameter to bidder ext

Resolves #3131

prebid-server PR: https://github.com/prebid/prebid-server/pull/3626

@SerhiiNahornyi Can someone please take a look at this one 🙏🏻

repo: prebid/prebid-server-java