text:
added pip freeze to output dir

implements  #51
can be merged now.
should have no conflicts to anyother branches.
review is not needed IMO, but since this is a new feature, you may want to be aware of it.

the content of pip.freeze after each experiment will look like this:

atari-py==0.2.6
attrs==20.3.0
bokeh==2.0.0
box2d-py==2.3.8
certifi==2020.6.20
cffi==1.14.0
chardet==3.0.4
click==7.1.2
cloudpickle==1.3.0
cma==3.0.3
cycler==0.10.0
Cython==0.29.17
dask==2020.12.0
deap==1.3.1
decorator==4.4.2
distributed==2.17.0
fasteners==0.15
filelock==3.0.12
flake8==3.8.4
fsspec==0.7.4
future==0.18.2
glcontext==2.2.0
glfw==1.11.0
greenlet==0.4.15
gym==0.17.3
gym3==0.3.3
HeapDict==1.0.1
idna==2.10
imageio==2.8.0
imageio-ffmpeg==0.3.0
iniconfig==1.0.1
Jinja2==2.11.2
joblib==0.15.1
jsonpatch==1.26
jsonpointer==2.0
kiwisolver==1.2.0
locket==0.2.0
lockfile==0.12.2
MarkupSafe==1.1.1
matplotlib==3.3.3
mccabe==0.6.1
memory-profiler==0.58.0
mock==4.0.2
moderngl==5.6.1
monotonic==1.5
more-itertools==8.3.0
msgpack==1.0.0
mujoco-py==2.0.2.9
mypy==0.790
mypy-extensions==0.4.3
networkx==2.5
nptyping==1.3.0
numpy==1.19.4
numpy-stubs @ git+git://github.com/numpy/numpy-stubs.git@c49d2d6875971a669a166ea93ef998911af283a1
opencv-python==4.2.0.34
packaging==20.4
partd==1.1.0
Pillow==7.1.2
pluggy==0.13.1
procgen @ git+https://github.com/neuroevolution-ai/procgen.git@3a5d86c3b89d362983c1a90df970b9173c0bd79b
psutil==5.7.0
py==1.9.0
pybullet==3.0.7
pycodestyle==2.6.0
pycparser==2.20
pyflakes==2.2.0
pygame==2.0.0
pyglet==1.5.0
Pympler==0.9
PyOpenGL==3.1.5
pyparsing==2.4.7
pytest==6.2.1
pytest-mock==3.4.0
pytest-mypy==0.8.0
pytest-parallel==0.1.0
python-dateutil==2.8.1
PyYAML==5.3.1
pyzmq==19.0.0
requests==2.24.0
scikit-learn==0.23.1
scipy==1.4.1
scoop==0.7.1.1
six==1.14.0
sklearn==0.0
sortedcontainers==2.1.0
tblib==1.6.0
threadpoolctl==2.1.0
tikzplotlib==0.9.6
tk==0.1.0
toml==0.10.1
toolz==0.10.0
torch==1.7.1
torchfile==0.1.0
torchvision==0.7.0
tornado==6.0.4
typed-argument-parser==1.6.1
typed-ast==1.4.1
typing-extensions==3.7.4.2
typing-inspect==0.6.0
typish==1.6.0
urllib3==1.25.10
visdom==0.1.8.9
wcwidth==0.1.9
websocket-client==0.57.0
zict==2.0.0

here procgen has been installed with
python -m pip install git+https://github.com/neuroevolution-ai/procgen.git@3a5d86c3b89d362983c1a90df970b9173c0bd79b
and numpy_stubs has been installed via requirements.txt, which has this line
git+git://github.com/numpy/numpy-stubs.git#egg=numpy-stubs
It is notworthy that in both cases the output of pip freeze contains the exact commit, which was used to install the module. Which is great news, I think. Because it resolves the confusion about which exact state of our custom procgen env was installed

the content of pip.freeze after each experiment will look like this:

atari-py==0.2.6
attrs==20.3.0
bokeh==2.0.0
box2d-py==2.3.8
certifi==2020.6.20
cffi==1.14.0
chardet==3.0.4
click==7.1.2
cloudpickle==1.3.0
cma==3.0.3
cycler==0.10.0
Cython==0.29.17
dask==2020.12.0
deap==1.3.1
decorator==4.4.2
distributed==2.17.0
fasteners==0.15
filelock==3.0.12
flake8==3.8.4
fsspec==0.7.4
future==0.18.2
glcontext==2.2.0
glfw==1.11.0
greenlet==0.4.15
gym==0.17.3
gym3==0.3.3
HeapDict==1.0.1
idna==2.10
imageio==2.8.0
imageio-ffmpeg==0.3.0
iniconfig==1.0.1
Jinja2==2.11.2
joblib==0.15.1
jsonpatch==1.26
jsonpointer==2.0
kiwisolver==1.2.0
locket==0.2.0
lockfile==0.12.2
MarkupSafe==1.1.1
matplotlib==3.3.3
mccabe==0.6.1
memory-profiler==0.58.0
mock==4.0.2
moderngl==5.6.1
monotonic==1.5
more-itertools==8.3.0
msgpack==1.0.0
mujoco-py==2.0.2.9
mypy==0.790
mypy-extensions==0.4.3
networkx==2.5
nptyping==1.3.0
numpy==1.19.4
numpy-stubs @ git+git://github.com/numpy/numpy-stubs.git@c49d2d6875971a669a166ea93ef998911af283a1
opencv-python==4.2.0.34
packaging==20.4
partd==1.1.0
Pillow==7.1.2
pluggy==0.13.1
procgen @ git+https://github.com/neuroevolution-ai/procgen.git@3a5d86c3b89d362983c1a90df970b9173c0bd79b
psutil==5.7.0
py==1.9.0
pybullet==3.0.7
pycodestyle==2.6.0
pycparser==2.20
pyflakes==2.2.0
pygame==2.0.0
pyglet==1.5.0
Pympler==0.9
PyOpenGL==3.1.5
pyparsing==2.4.7
pytest==6.2.1
pytest-mock==3.4.0
pytest-mypy==0.8.0
pytest-parallel==0.1.0
python-dateutil==2.8.1
PyYAML==5.3.1
pyzmq==19.0.0
requests==2.24.0
scikit-learn==0.23.1
scipy==1.4.1
scoop==0.7.1.1
six==1.14.0
sklearn==0.0
sortedcontainers==2.1.0
tblib==1.6.0
threadpoolctl==2.1.0
tikzplotlib==0.9.6
tk==0.1.0
toml==0.10.1
toolz==0.10.0
torch==1.7.1
torchfile==0.1.0
torchvision==0.7.0
tornado==6.0.4
typed-argument-parser==1.6.1
typed-ast==1.4.1
typing-extensions==3.7.4.2
typing-inspect==0.6.0
typish==1.6.0
urllib3==1.25.10
visdom==0.1.8.9
wcwidth==0.1.9
websocket-client==0.57.0
zict==2.0.0

here procgen has been installed with
python -m pip install git+https://github.com/neuroevolution-ai/procgen.git@3a5d86c3b89d362983c1a90df970b9173c0bd79b
and numpy_stubs has been installed via requirements.txt, which has this line
git+git://github.com/numpy/numpy-stubs.git#egg=numpy-stubs
It is notworthy that in both cases the output of pip freeze contains the exact commit, which was used to install the module. Which is great news, I think. Because it resolves the confusion about which exact state of our custom procgen env was installed

Nice I would merge it if its okay

authors: bjuergens pdeubel


text:
xrdp crashes if login-manager configured for autologin

xrdp version
0.9.17-2ubuntu2
Detailed xrdp version, build options
xrdp 0.9.17
  A Remote Desktop Protocol Server.
  Copyright (C) 2004-2020 Jay Sorg, Neutrino Labs, and all contributors.
  See https://github.com/neutrinolabs/xrdp for more information.

  Configure options:
      --enable-ipv6
      --enable-jpeg
      --enable-fuse
      --enable-rfxcodec
      --enable-opus
      --enable-painter
      --enable-vsock
      --build=x86_64-linux-gnu
      --prefix=/usr
      --includedir=${prefix}/include
      --mandir=${prefix}/share/man
      --infodir=${prefix}/share/info
      --sysconfdir=/etc
      --localstatedir=/var
      --disable-silent-rules
      --libdir=${prefix}/lib/x86_64-linux-gnu
      --libexecdir=${prefix}/lib/x86_64-linux-gnu
      --disable-maintainer-mode
      --disable-dependency-tracking
      --with-socketdir=/run/xrdp/sockdir
      build_alias=x86_64-linux-gnu
      CFLAGS=-g -O2 -ffile-prefix-map=/build/xrdp-asBei3/xrdp-0.9.17=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
      LDFLAGS=-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now -Wl,--as-needed
      CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-error=deprecated-declarations
      PKG_CONFIG_PATH=/build/xrdp-asBei3/xrdp-0.9.17/pkgconfig

  Compiled with OpenSSL 3.0.2 15 Mar 2022

Operating system & version
Xubuntu 22.04
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorgrdp
What desktop environment do you use?
Xfce
Environment xrdp running on
Stock HP ProDesk 600 G6 Mini (i7-10700T)
What's your client?
KRDC
Area(s) with issue?
Crashes such as segfault
Steps to reproduce
If the user account has autologin enabled in lightdm, instead of a meaningful error message, xrdp crashes with a segfault.  This can be reproduced by selecting the autologin option when doing a clean install of the operating system.  It can be fixed by editing /etc/lightdm/lightdm.conf and removing the autologin-user settings and rebooting.
I assume it would also apply to other login managers too, not just lightdm, but that happens to be where I encountered it.
✔ Expected Behavior
I was expecting a meaningful error message explaining that the user was already logged into the machine and needed to logout first.
❌ Actual Behavior
The client disconnected and whoopsie caught and sent an error report log of the crash (a segfault).  Every attempt to connect resulting in the same crash.  After realizing that the user can't be logged in for RDP to work, I changed the user setting, as I outlined above, and it works fine as expected.
Anything else?
Even though I've solved my problem, I wanted to report it so that it can be fixed and be less confusing to other users (and perhaps prevent you guys having to dig through those extra core dumps).

@dewhisna
Can you give us more details of the segfault? I suspect it's the window manager crashing and not xrdp itself, but we should really get to the bottom of this.
The autologin behaviour is effectively explained in the FAQ.

You are indeed correct.  I just tried recreating it and it was the indeed the xfce4-session process that I misread as being xrdp.  And worse, this time not just one thing crashed, but four things: /usr/bin/xfce4-session, /usr/bin/xiccd, /usr/lib/xorg/Xorg, and /usr/bin/blueman-applet.
Now, I'm not sure the blueman-applet crash is related, as I saw at least one of those under other conditions.  But the Xorg, xiccd, and xfce4-session I think were all related -- and at least triggered by trying to do an XRDP connection while already logged in.
I moved the whoopsie data for those four from /var/crash to a subfolder for safe keeping, in case anyone wants the call stacks.  But yeah, it seems I misread it yesterday and filed an invalid bug report.  Sorry about that.  Feel free to close this issue out as being unrelated.

I think I have the exactly same problem:
https://github.com/neutrinolabs/xrdp/assets/91451822/69d433b3-04f4-491a-88ac-184d9021a333

@Varjokettu -- when it shuts down the connection like that, does it also get a crash?  Check /var/crash and see if any crash dumps were created.  In my case, it was resolved by disabling auto-login.  If you don't have auto-login enabled, it's probably a different issue.  If you do have auto-login enabled, you can disable it by removing the autologin entries in the /etc/lightdm/lightdm.conf file and rebooting.  Or at least that keeps it from crashing for me.

@Varjokettu -- when it shuts down the connection like that, does it also get a crash? Check /var/crash and see if any crash dumps were created. In my case, it was resolved by disabling auto-login. If you don't have auto-login enabled, it's probably a different issue. If you do have auto-login enabled, you can disable it by removing the autologin entries in the /etc/lightdm/lightdm.conf file and rebooting. Or at least that keeps it from crashing for me.

Doesn't look like there's anything:
kettu:~$ cd /var/crash
kettu:/var/crash$ ls
kettu:/var/crash$
Seems that such directory doesn't exist:
sudo nano /etc/lightdm/lightdm.conf
-bash: /etc/lightdm/lightdm.conf: No such file or directory

I'm not sure if this is of any help, but here's the log from the terminated session:
cat /var/log/syslog | grep xrdp
Nov 16 20:25:26 kettubuntu xrdp[14039]: [INFO ] connecting to sesman ip 127.0.0.1 port 3350 Nov 16 20:25:26 kettubuntu xrdp-sesman[11353]: [INFO ] Socket 8: AF_INET6 connection received from ::1 port 44414 Nov 16 20:25:26 kettubuntu xrdp[14039]: [INFO ] xrdp_wm_log_msg: sesman connect ok Nov 16 20:25:26 kettubuntu xrdp[14039]: [INFO ] sesman connect ok Nov 16 20:25:27 kettubuntu xrdp[14039]: [INFO ] sending login info to session manager, please wait... Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [ERROR] pam_authenticate failed: Authentication failure Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [INFO ] Username or password error for user: k3ttu Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [ERROR] sesman_data_in: scp_process_msg failed Nov 16 20:25:29 kettubuntu xrdp[14039]: [INFO ] xrdp_wm_log_msg: login failed for display 0 Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans Nov 16 20:25:29 kettubuntu xrdp[14039]: [INFO ] login failed for display 0 Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] connecting to sesman ip 127.0.0.1 port 3350 Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] Socket 8: AF_INET6 connection received from ::1 port 47790 Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] xrdp_wm_log_msg: sesman connect ok Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] sesman connect ok Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] sending login info to session manager, please wait... Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] Terminal Server Users group is disabled, allowing authentication Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] ++ created session (access granted): username kettu, ip <IPNUMBER> - socket: 12 Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] starting Xorg session... Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] Starting session: session_pid 14044, display :11.0, width 1440, height 900, bpp 24, client ip <IPNUMBER> - socket: 12, user name kettu Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] [session start] (display 11): calling auth_start_session from pid 14044 Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [ERROR] sesman_data_in: scp_process_msg failed Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] xrdp_wm_log_msg: login successful for display 11 Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] login successful for display 11 Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4 Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] started connecting Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] lib_mod_connect: connecting via UNIX socket Nov 16 20:25:36 kettubuntu xrdp-sesman[14046]: [INFO ] Starting X server on display 11: /usr/lib/xorg/Xorg :11 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] lib_mod_log_peer: xrdp_pid=14039 connected to X11rdp_pid=14046 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=<IPNUMBER> client_port=56205 Nov 16 20:25:36 kettubuntu xrdp[14039]: [INFO ] connected ok Nov 16 20:25:36 kettubuntu xrdp-sesman[14045]: [INFO ] Found X server running at /tmp/.X11-unix/X11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Found X server running at /tmp/.X11-unix/X11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14045]: [INFO ] Found X server running at /tmp/.X11-unix/X11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Session started successfully for user kettu on display 11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14067]: [INFO ] Starting the xrdp channel server for display 11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14045]: [INFO ] Starting the default window manager on display 11: /etc/xrdp/startwm.sh Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Session in progress on display 11, waiting until the window manager (pid 14045) exits to end the session Nov 16 20:25:36 kettubuntu xrdp-chansrv[14067]: [INFO ] Socket 12: AF_UNIX connection received Nov 16 20:25:36 kettubuntu xrdp-chansrv[14067]: [INFO ] sound_process_training: round trip time 100 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [WARN ] Window manager (pid 14045, display 11) exited with non-zero exit code 255 and signal 15. This could indicate a window manager config problem Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [WARN ] Window manager (pid 14045, display 11) exited quickly (0 secs). This could indicate a window manager config problem Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Calling auth_stop_session and auth_end from pid 14044 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Terminating X server (pid 14046) on display 11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] Terminating the xrdp channel server (pid 14067) on display 11 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] X server on display 11 (pid 14046) returned exit code 0 and signal number 0 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] xrdp channel server for display 11 (pid 14067) exit code 0 and signal number 0 Nov 16 20:25:36 kettubuntu xrdp-sesman[14044]: [INFO ] cleanup_sockets: Nov 16 20:25:36 kettubuntu xrdp-sesman[11353]: [INFO ] ++ terminated session:  username kettu, display :11.0, session_pid 14044, ip <IPNUMBER> - socket: 12

And here is the XRDP log
cat /var/log/xrdp.log
[20231116-20:25:17] [INFO ] Socket 12: AF_INET6 connection received from  port 56203
[20231116-20:25:17] [INFO ] Socket 12: AF_INET6 connection received from ::ffff: port 56204
[20231116-20:25:17] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231116-20:25:17] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231116-20:25:17] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231116-20:25:17] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231116-20:25:17] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:17] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:18] [ERROR] libxrdp_force_read: header read error
[20231116-20:25:18] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20231116-20:25:18] [ERROR] libxrdp_force_read: header read error
[20231116-20:25:18] [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed
[20231116-20:25:18] [ERROR] [MCS Connection Sequence] receive connection request failed
[20231116-20:25:18] [ERROR] xrdp_sec_incoming: xrdp_iso_incoming failed
[20231116-20:25:18] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20231116-20:25:18] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231116-20:25:18] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231116-20:25:18] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231116-20:25:18] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231116-20:25:18] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231116-20:25:18] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231116-20:25:18] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20231116-20:25:18] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20231116-20:25:19] [INFO ] Socket 12: AF_INET6 connection received from  port 56205
[20231116-20:25:19] [INFO ] Socket 12: AF_INET6 connection received from ::ffff: port 56206
[20231116-20:25:19] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231116-20:25:19] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231116-20:25:19] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231116-20:25:19] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231116-20:25:19] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:19] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:19] [ERROR] libxrdp_force_read: header read error
[20231116-20:25:19] [INFO ] Connected client computer name: *********
[20231116-20:25:19] [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed
[20231116-20:25:19] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20231116-20:25:19] [ERROR] xrdp_sec_incoming: xrdp_iso_incoming failed
[20231116-20:25:19] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20231116-20:25:19] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231116-20:25:19] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231116-20:25:19] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231116-20:25:19] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20231116-20:25:19] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x07], keyboard_subtype:[0x00], keylayout:[0x0000040B]
[20231116-20:25:19] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [fi] options []
[20231116-20:25:19] [INFO ] Non-TLS connection established from  port 56205: encrypted with standard RDP security
[20231116-20:25:20] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20231116-20:25:20] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20231116-20:25:20] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20231116-20:25:20] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20231116-20:25:20] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20231116-20:25:20] [INFO ] Loading keymap file /etc/xrdp/km-0000040b.ini
[20231116-20:25:20] [WARN ] local keymap file for 0x0000040b found and doesn't match built in keymap, using local keymap file
[20231116-20:25:26] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20231116-20:25:26] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20231116-20:25:26] [INFO ] sesman connect ok
[20231116-20:25:26] [INFO ] sending login info to session manager, please wait...
[20231116-20:25:29] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20231116-20:25:29] [INFO ] login failed for display 0
[20231116-20:25:36] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20231116-20:25:36] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20231116-20:25:36] [INFO ] sesman connect ok
[20231116-20:25:36] [INFO ] sending login info to session manager, please wait...
[20231116-20:25:36] [INFO ] xrdp_wm_log_msg: login successful for display 11
[20231116-20:25:36] [INFO ] login successful for display 11
[20231116-20:25:36] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20231116-20:25:36] [INFO ] started connecting
[20231116-20:25:36] [INFO ] lib_mod_connect: connecting via UNIX socket
[20231116-20:25:36] [INFO ] lib_mod_log_peer: xrdp_pid=14039 connected to X11rdp_pid=14046 X11rdp_uid=1000 X11rdp_gid=1000 client_ip= client_port=56205
[20231116-20:25:36] [INFO ] connected ok

@Varjokettu -- No, it looks like yours isn't the crash I was seeing, but a permissions problem.  Notice:
[20231116-20:25:19] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:19] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20231116-20:25:19] [ERROR] libxrdp_force_read: header read error
[20231116-20:25:19] [INFO ] Connected client computer name: *********
[20231116-20:25:19] [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed

If you look in the /etc/xrdp/xrdp.ini settings file for xrdp, you'll see:
; X.509 certificate and private key
; openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
; note this needs the user xrdp to be a member of the ssl-cert group, do with e.g.
;$ sudo adduser xrdp ssl-cert

If you run that command, sudo adduser xrdp ssl-cert, it will likely fix that.  Even the default ssl-cert-snakeoil key is owned by root and in the ssl-cert group.  So, xrdp needs to be in the ssl-cert group as well to see it, even if you haven't created a more valid key-pair.
And if that doesn't fix it, double check the username and password combination, as the syslog snippet you included says it couldn't authenticate it:
Nov 16 20:25:27 kettubuntu xrdp[14039]: [INFO ] sending login info to session manager, please wait...
Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [ERROR] pam_authenticate failed: Authentication failure
Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [INFO ] Username or password error for user: k3ttu
Nov 16 20:25:29 kettubuntu xrdp-sesman[11353]: [ERROR] sesman_data_in: scp_process_msg failed
Nov 16 20:25:29 kettubuntu xrdp[14039]: [INFO ] xrdp_wm_log_msg: login failed for display 0

But the authentication error was probably from it not being able to read the SSL key to do the decryption of the username/password in the first place, which the ssl-cert group fix would solve.

Yeah
I had a wring username forst in that attempt but after fixing that problem, the actual failure happened.

If you run that command, sudo adduser xrdp ssl-cert, it will likely fix that. Even the default ssl-cert-snakeoil key is owned by root and in the ssl-cert group. So, xrdp needs to be in the ssl-cert group as well to see it, even if you haven't created a more valid key-pair.

Unfortunately this didn't fix the issue.
I reinstalled whole Ubuntu and started fresh.
Only thing I have done so far:

Install SSH connection -> this works
Install XRDP and did the  sudo adduser xrdp ssl-cert

Here's the log dump from that event.

cat /var/log/xrdp.log
[20231117-14:39:36] [INFO ] address [0.0.0.0] port [3389] mode 1
[20231117-14:39:36] [INFO ] listening to port 3389 on 0.0.0.0
[20231117-14:39:36] [INFO ] xrdp_listen_pp done
[20231117-14:39:38] [INFO ] starting xrdp with pid 5055
[20231117-14:39:38] [INFO ] address [0.0.0.0] port [3389] mode 1
[20231117-14:39:38] [INFO ] listening to port 3389 on 0.0.0.0
[20231117-14:39:38] [INFO ] xrdp_listen_pp done
[20231117-14:41:24] [INFO ] Received termination signal, stopping the server accept new connections thread
[20231117-14:41:24] [INFO ] address [0.0.0.0] port [3389] mode 1
[20231117-14:41:24] [INFO ] listening to port 3389 on 0.0.0.0
[20231117-14:41:24] [INFO ] xrdp_listen_pp done
[20231117-14:41:26] [INFO ] starting xrdp with pid 5139
[20231117-14:41:26] [INFO ] address [0.0.0.0] port [3389] mode 1
[20231117-14:41:26] [INFO ] listening to port 3389 on 0.0.0.0
[20231117-14:41:26] [INFO ] xrdp_listen_pp done
[20231117-14:41:42] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<PUBLIC_IP_NUMBER> port 53102
[20231117-14:41:42] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231117-14:41:42] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231117-14:41:42] [ERROR] SSL_read: I/O error
[20231117-14:41:42] [ERROR] libxrdp_force_read: header read error
[20231117-14:41:42] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20231117-14:41:42] [ERROR] [MCS Connection Sequence] receive connection request failed
[20231117-14:41:42] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20231117-14:41:42] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231117-14:41:42] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231117-14:41:42] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231117-14:41:42] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20231117-14:41:44] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<PUBLIC_IP_NUMBER> port 53108
[20231117-14:41:44] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20231117-14:41:44] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20231117-14:41:44] [INFO ] Connected client computer name: <MY_WINDOWS_COMPUTER_NAME>
[20231117-14:41:44] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20231117-14:41:44] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20231117-14:41:44] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x07], keyboard_subtype:[0x00], keylayout:[0x0000040B]
[20231117-14:41:44] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [fi] options []
[20231117-14:41:44] [INFO ] TLS connection established from ::ffff:<PUBLIC_IP_NUMBER> port 53108: TLSv1.2 with cipher <SHA_whatever?>
[20231117-14:41:44] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20231117-14:41:44] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20231117-14:41:44] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20231117-14:41:44] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20231117-14:41:44] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20231117-14:41:44] [INFO ] Loading keymap file /etc/xrdp/km-0000040b.ini
[20231117-14:41:44] [WARN ] local keymap file for 0x0000040b found and doesn't match built in keymap, using local keymap file
[20231117-14:41:50] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20231117-14:41:50] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20231117-14:41:50] [INFO ] sesman connect ok
[20231117-14:41:50] [INFO ] sending login info to session manager, please wait...
[20231117-14:41:50] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20231117-14:41:50] [INFO ] login successful for display 10
[20231117-14:41:50] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20231117-14:41:50] [INFO ] started connecting
[20231117-14:41:50] [INFO ] lib_mod_connect: connecting via UNIX socket
[20231117-14:41:50] [INFO ] lib_mod_log_peer: xrdp_pid=5141 connected to X11rdp_pid=5144 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=::ffff:<PUBLIC_IP_NUMBER> client_port=53108
[20231117-14:41:50] [INFO ] connected ok

--> RDP terminates<--

Here's the short description for other people having same issue:

Install XRDP: sudo apt install xrdp
Allow xrdp user in ssl-cert group: sudo adduser xrdp ssl-cert
Removed my Autologin from Ubuntu: sudo nano /etc/gdm3/custom.conf
3.1 Search for these lines and comment them out, if they are acive:

AutomaticLoginEnable = true
AutomaticLogin =

Restart gdm (if that's your display manager): sudo systemctl restart gdm
Restart XRDP service: sudo systemctl restart xrdp

Also, if you are using firewall, remember to open ports for your rdp connection:

Allow your port: sudo ufw allow  (default for windows RDP is 3389)
If you have changed the port, remember to close the default if it's on: sudo ufw deny 3389

Finally, open ports for your RDP through your router firewall.
Hope it helps!

@Varjokettu -- yes, you've confirmed that it doesn't work with autologin enabled (and it's not supposed to).  And apparently you are using a different login-manager than I am -- gdm3 in your case, where I am using lightdm, since mine is a Xubuntu install instead of Ubuntu -- i.e. Xfce instead of Gnome.  But it doesn't appear that you recreated the crash that this issue was about.
This issue was specifically about a system crash in this scenario in addition to the login failing.  I was incorrect in thinking that it was xrdp that was crashing.  Instead it was Xfce and the xiccd color manager and apparently even the X-server itself on occasion.  It's a crash that causes a dialog like this:

Now, that image is of the blueman-applet crash, which as I stated above is UNRELATED to this issue, but happens more often and was easier to grab a screenshot to illustrate the sort of crash this issue is about (i.e. not just the login connection closing).  The crash when logging in with xrdp with auto-login enabled causes a dialog like this for xfce4-session and sometimes xiccd and Xorg as well, and always produces a crash dump (or multiple dumps) in the /var/crash folder.  Yours isn't crashing, so this issue isn't related to what you are seeing (which is normal behavior).  Now, it would be nice if your computer could tell you why it's dropping your connection, but it's not crashing on you.
I think the problem I'm seeing is a bug in the Xfce session manager and that there's a series of race-conditions that happen.  Sometimes, I see no crash at all.  Sometimes only the Xfce4 session manager.  Sometimes a random combination of two or even all three crashes at the same time.  My guess is there's a shutdown signal that doesn't always get processed ahead of something using the pointer for the thing shutting down and the object is being destroyed while it's still being used -- a use-after-free type error.  But that's only a guess based on how it's behaving.
In any case, disabling auto-login in the login-manager (be that lightdm or gdm or whatever) at least papers over the issue and prevents the crash.

@dewhisna
Yeah, seems that I had different error. I'm super happy still that I got it sorted out, so big thanks to you!

source: gharchive/issue

authors: Varjokettu dewhisna matt335672

repo: neutrinolabs/xrdp

license_type: permissive

license_source: bigquery


text:
Update 11.restore.md

spelling correction

Addressed with #90

source: gharchive/pull-request

authors: garricktam nunix

repo: neuvector/docs

license_source: github-api


text:
Has component

Almost same as #647 but simpler, instead of res T it produces res bool

This can just be implemented as a wrapper on top of #647

Yes, probably it can!

repo: nevalang/neva

license: MIT


text:
Add xcode flags

Now works on OS X  :^)

Thanks!

authors: nevermnd tofuness

repo: nevermnd/anitomy-js

license: mit


text:
chore(deps): upgrade nfpm, goreleaser and more

Attempt to fix Dependabot Alert

https://github.com/newrelic/newrelic-client-go/security/dependabot/17

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bfd4e5d) 37.64% compared to head (1caaeaa) 37.64%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1087   +/-   ##
=======================================
  Coverage   37.64%   37.64%
=======================================
  Files          85       85
  Lines        5409     5409
=======================================
  Hits         2036     2036
  Misses       3221     3221
  Partials      152      152

Flag
Coverage Δ

unit
37.64% <ø> (ø)

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

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

authors: codecov-commenter pranav-new-relic

repo: newrelic/newrelic-client-go


text:
fix(EpochTime) fix EpochTimeUnix unit test

One unit test is failing for my previous PR:https://github.com/newrelic/newrelic-client-go/pull/997
So i made fix for that
Failed CI: https://github.com/newrelic/newrelic-client-go/actions/runs/4345000784/jobs/7589103597
@sanderblue

Thanks again. Closing per #1000

authors: diabeticMike sanderblue


text:
Synthetics Info Header Support

Overview

Add support for new X-NewRelic-Synthetics-Info header.
This PR is reopened from #896 after reverting with #983

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (1986366) 81.78% compared to head (db08923) 81.84%.

Files
Patch %
Lines

newrelic/common/encoding_utils.py
91.30%
1 Missing and 1 partial :warning:

newrelic/core/transaction_node.py
75.00%
0 Missing and 2 partials :warning:

newrelic/api/transaction.py
91.66%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #984      +/-   ##
==========================================
+ Coverage   81.78%   81.84%   +0.06%
==========================================
  Files         190      190
  Lines       19607    19676      +69
  Branches     3407     3428      +21
==========================================
+ Hits        16035    16104      +69
  Misses       2590     2590
  Partials      982      982

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

authors: TimPansino codecov-commenter

repo: newrelic/newrelic-python-agent


text:
feat: New example app

Adding new example app with v0.0.8. Contains functionality for API calls and some examples from the current example app

Marking as draft while I work on some android issues I'm noticing.

repo: newrelic/newrelic-react-native-agent


text:
Logging: Don't send payloads with empty message attributes

Overview
Adds a guard statement to NewRelic::Agent::LogEventAggregator#record to return if the formatted_message argument is nil or an empty string.
Related Github Issue
Closes #984
Testing
Adds unit tests for not recording empty or nil messages

Blocked by original logging PR being merged into dev

repo: newrelic/newrelic-ruby-agent


text:
Update README.md

started some updates on the Readme

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

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

authors: CLAassistant mattshandera

repo: newrelic/nr-ngo-validation-serverless


text:
Testing, please ignore

Please do not approve this

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Gomez Addams seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: newrelic/quickstarts-synthetics-library


text:
sass --watch does not compile stylesheets when it starts

When I run sass --watch to watch a directory's worth of stylesheets, if the destination directory is empty sass does not compile my stylesheets when it starts. To get the stylesheets compiled I have to compile them myself initially. It would be helpful if sass --watch made a pass over all sources and compiled them if the corresponding destination stylesheets did not exist or were outdated.

This should work, and works for me. What's your sass --watch command line? What OS, Sass version, and Ruby version are you using?

It was my mistake. I did:
sass --watch public/stylesheets/ public/compiled/stylesheets/
when the correct syntax is:
sass --watch public/stylesheets/:public/compiled/stylesheets/
It would be nice if sass either accepted both or complained about the first one.

sass --watch public/stylesheets/ public/compiled/stylesheets/ is a perfectly reasonable command. It means "watch all stylesheets in public/stylesheets and all stylesheets in public/compiled/stylesheets." I don't think there's a good way for Sass to determine that that's not what you meant here.

Fair enough.


text:
Software configuration

Dear,
is it possible to configure parts of the system? I'm currently refereing to the number of scans which can be performed in parallel? The default installatuion only allows one at a time. At scancode-toolkit, for instance, you can configure number of used threads or the properties you wwant to scan for (e.g. licenses, copyright, ...). Do I have something similar in scancode.io?
Thanks for your hel
Raphael

s it possible to configure parts of the system?

Yes, see the list of available settings at https://scancodeio.readthedocs.io/en/latest/scancodeio-settings.html

At scancode-toolkit, for instance, you can configure number of used threads or the properties you wwant to scan for (e.g. licenses, copyright, ...)

You can configure the multiprocessing with https://scancodeio.readthedocs.io/en/latest/scancodeio-settings.html#scancodeio-processes
Note that this setting configure the number of CPUs available per scan.

I'm currently refereing to the number of scans which can be performed in parallel? The default installatuion only allows one at a time.

By default, only one worker is started, you can start as many worker as you want (depending on your machine configuration) to perform multiple scans in parallel.

Hi @RaphaelHerd did you manage to configure ScanCode.io as you wanted?

@RaphaelHerd I'm closing, please re-open if you couldn't configure with the currently available settings.

authors: RaphaelHerd tdruez


text:
Modal with animated got flashing abnormally when visible

Describe the bug
When Modal animated is true (by default), modal will blink when it appears.
Steps to reproduce
CodeSandbox: https://codesandbox.io/s/next-ui-modal-1r2w18
It doesn't always flashing when popup, but usually appears in the first few popup animations after the page has been loaded.
If not see the flashing, please try after refreshing.
Expected behaviour
popup with smooth animation.
Environment / Context

Desktop
Operating System: Windows 10 Pro
Browser and version Chrome 98.0.4758.82 (Official Build) (64-bit)
Device: Dell Inspiron 7560

I'm experiencing the same issue.

I'm experiencing the same issue.
I'm showing 2 different files (audio and video) in the modal simultaneously and on file timeline change this issue occurs.
Note that I'm using VideoJS

authors: Deihim007 pourya-ataee tianenpang

repo: nextui-org/nextui


text:
[BUG] - Dropdown does not work when backdrop is setted on mobile

NextUI Version
@nextui-org/dropdown": "^2.1.29
Describe the bug
I have a Dropdown that opens a modal (which by default has an opaque backdrop). When the Modal opens and I close it, the Dropdown Trigger that initially opened the modal stops working unless I click it multiple times quickly to try to reopen it. This issue only affects the specific Dropdown Trigger that opened the Modal, even if the Modal is controlled outside the dropdown. The problem only occurs on mobile, and I have tested it on my phone as well.
IMPORTANT NOTE: After recording the old video (now is the updated one), I noticed that even without the Modal (just the Dropdown with the backdrop set), it still wouldn’t work. My Dropdown Trigger is a Card, but I also tested it with a Button and text (just the trigger itself).
As a workaround, I removed the backdrop from the Dropdown, and now it seems to work fine on mobile devices. However, this is still a bug.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Trigger dropdown with backdrop
Open modal (not mandatory) or leave the dropdown (mandatory)
Close modal (not mandatory)
Trigger dropdown (bug)

Expected behavior
Open dropdown
Screenshots or Videos
https://github.com/user-attachments/assets/1443b0a7-dc5b-4277-8032-c4ac13ae235f
Operating System Version
Android, Windows
Browser
Chrome

please share a minimal reproducible environment.

same is happening for me on the nextui website. i can produce a minimal reproducible environment if you want me to? just seems to happen when the dropdown with a backdrop is used on any android devices. i've tested it myself and had lots of users report it on my website
https://github.com/user-attachments/assets/c3d4e4bb-e992-4d91-8398-5cf829a793ae

authors: Starman3787 lucarampi wingkwong


text:
[Feature Request] A Drawer Component for NextUI

Is your feature request related to a problem? Please describe.
I've been using NextUI in one of my side projects lately. I appreciate the simple and robust approach it offers, and I adore the UI overall. However, I am surprised it doesn't have a Drawer component! Although, I implemented it using a third-party library. But it's not enough. Third-party components lack native NextUI effects and support. It's also not the best approach, I guess.
NextUI should also have a Drawer like other UI libraries, e.g., Material UI, Ant Design, Mantine, etc.
Describe the solution you'd like
It'd be great to have a native Drawer component for NextUI. It'll save a lot of tedious jobs and broken tests.
As the Hacktoberfest has begun, it brings a fantastic opportunity to address this lacking feature and implement it right now.
I'd like to suggest that you guys should open an issue for this to implement that. I was also tinkering with the NextUI repo myself.
I'd love to work on that feature and contribute.
Describe alternatives you've considered
I'm temporarily using React Modern Drawer. It's minimal and easy to customize.
Screenshots or Videos
No response

+1

A temporary alternative would be to use modal component with full-screen prop with inline css and media queries to setup max width to something like 30vw-70vw on different devices

A temporary alternative would be to use modal component with full-screen prop with inline css and media queries to setup max width to something like 30vw-70vw on different devices

@gajendr4 Yeah, that's a straightforward option. But still, it would be great if we had such a component.

Hey @maxtondelaney!
That looks cool and robust since we don't have any drawer components! Looking forward to explore more.
Thanks for the example

authors: gajendr4 moeen-mahmud ytkg


text:
why i can't bind my service?

Environment
Debian GNU/Linux 12 (bookworm) x86_64
Nezha Version
Nezha 1.3.0
Describe the bug
I  got an error when i want to bind my server.
![image](https://github.com/user-attachments/assets/5451bfac-a17b-4f50-8e97-e3be37d4525b)
To Reproduce
Problems encountered when binding the server after successful deployment
Additional Context

Validation

[X] I confirm this is a bug about nezha (Nezha Dashboard).
[X] I have searched Issues and confirm this bug has been reported before.

What do you mean by 'binding'?
A server is created after the first successful Agent authorization.
The pop-up indicates there is no server available.

"Bind" is just a habitual way of saying it.... Sorry for the misunderstanding, what I meant was "(used for) nezha-agent installation command (to bind the server)"
I have used the installation command on the server, but it didn't work, and then an error pop-up window popped up (see the picture below)

Normally the installation command will install nezha-agent on your system.
Then the server should be shown in the admin dashboard.
Please provide logs so we can investigate what the problem is.

The above is the information provided by my server. During this process, I also found a new problem, that is, the nezha-dashboard installed in docker cannot be detected normally.
There is no valuable information in the log, and everything runs according to the script during the execution process. The problem is unlikely to occur in my own deployment problem or network error.
But I still cannot use nezha-agent by installing the command. There is no server with nezha-agent installed on the dash master.

What do you mean by 'binding'?
A server is created after the first successful Agent authorization.
The pop-up indicates there is no server available.

"Bind" is just a habitual way of saying it.... Sorry for the misunderstanding, what I meant was "(used for) nezha-agent installation command (to bind the server)"
I have used the installation command on the server, but it didn't work, and then an error pop-up window popped up (see the picture below)

我也是报一模一样的错误，1panel+nezhav1.3.0

这一版本的nezha事情还是多，还是等修复吧

强制刷新就会没有这个错误了

authors: jin-gubang zixuanya

repo: nezhahq/nezha


text:
Travis CI Test Implementation

The EAGER 2.0 pipeline will have fully automatic consistency tests

[ ] Human Genome, autosomal (hg19)
[ ] Human Genome, mitochondrial (RSRS, rCRS)
[ ] An exemplary bacterial genome

I'll create test reference genomes with a couple of KB in size to test things quickly and then
Set up three test scripts for the datasets:

[ ] A GATK variant calling testcase
[ ] A low coverage testcase including sequenceTools
[ ] BWA / CircularMapper testcases
[ ] Picard / DeDup testcases

I'll look for:
non-human shotgun/mitochondria (assuming you still want human specific stuff)
low-complexity bacterial sample (probably pestis)
high-complexity bacteria sample (some calculus thing)

Yeah, need to update this ticket still, but this seems reasonable! We'll have some specific tweaks for human vs bacterial vs other stuff, but I'd say for most things it should be fairly identical.

Actually, speaking of which. How do you envision the tweaks between human/bacterial/other?
Is it worth having default modifications that way, or is it better to let the user decide?
Just curious, as IIRC the only difference between human and bacterial in EAGER 1.9 was inclusion of QF values in report table.

Honestly, I don't see that much differences as you said already - the basic processing is identical, with some specific tools for human (e.g. schmutzi for example) and some specific tools for bacteria later (e.g. genConS or similar). One could in theory provide certain profiles that won't run these tools e.g. in the wrong cases but instead keep everything else identical.
Yes, thats mostly it. There were ideas to make things even smarter, but that resulted in an entire bunch of things that we'd need to implement for minimal user experience effects... so we instead focused on other things...

Exactly. Then I suggest we remove organism-specific profiles. Maybe in the documentation we can provide 'suggested' or 'example' settings which the user can then input accordingly?
That'll save you some coding work too ;)

I'm all in on that one

eager2_mammoth_testing_package.tar.gz
Contains:
## Reference Mammoth MT genome
mammoth_testing_package/
mammoth_testing_package/reference_genome/
mammoth_testing_package/reference_genome/Mammoth_MT_Krause.fasta

## EAGER 1.92.55 config file and subsequent (expected) results
mammoth_testing_package/eager_v1_9_55/
mammoth_testing_package/eager_v1_9_55/2018-06-23-12-51-EAGER.xml
mammoth_testing_package/eager_v1_9_55/Report_output_EAGER_v1_9_55.csv

## Mammoth JK2782 HiSeq MT Capture library (~10,000 reads after merging) from Fellows Yates (2017) Sci. Rep
mammoth_testing_package/fastq_data/
mammoth_testing_package/fastq_data/JK2782_TGGCCGATCAACGA_L008_R2_001.fastq.gz.tengrand.fq
mammoth_testing_package/fastq_data/JK2782_TGGCCGATCAACGA_L008_R1_001.fastq.gz.tengrand.fq

Let me know if that works/is useful.

Thats perfect! Thank you James! I will check this in under https://github.com/nf-core/test-datasets and use it for setting up testcases - probably even today as you took your time for this too :-)

Tests are up and running :tada:


text:
Remove GTF regions on unknown chromosomes

Basically this replicates the same functionality that is also present in the nf-core/rnaseq pipeline

Wait for this PR to be merged, then use the new module

repo: nf-core/circrna


text:
Update introduction.md

Recommend setting singularity cache directory #268
https://github.com/nf-core/nf-co.re/issues/268

I would drop the "as your preferred container" wording, since this will help me if I prefer Singularity or not AFAICT.

@medulka - you can use magic words fix #123 fixes #123 closes #123 etc in your PR descriptions and commits if you want. Then, when merged the referenced issue will automatically be closed.
You can also do the same using Linked issues in the sidebar on the right.

authors: ewels fabianegli medulka


text:
Update smoothxg to hopefully v0.7.1

Description of feature
The future v0.7.1 release will come with some bug fixes, so this is really required to have.

Depends on https://github.com/pangenome/smoothxg/issues/199.

repo: nf-core/pangenome


text:
Fix outstanding issues

Closes #175

Thanks guys!

repo: nf-core/viralrecon


text:
[Feature Request] Invenio validation package should check existence of annotated data

Currently, the validation package only checks for the existence of top level metadata like Investigation description and Person E-Mail.
If I remember correctly, one requirement of the package was, that the existence of annotated data is checked. I.e. that the data file names used in assay and study Annotation tables have physical data counterparts in the ARC.

related: https://github.com/nfdi4plants/arc-validation-packages/issues/1

Closed via https://github.com/nfdi4plants/arc-validation-packages/pull/3.

authors: HLWeil kMutagene omaus


text:
Keycloak Authentication

Added and modified several commands related to authentication to git services:

arc auth will open a browser window of a token specified in the arc config. The user can login there and a the credentials to a specific git service (like a gitlab instance) will be automatically stored using the git credential manager interface. The response from the token service additionally contains user metadata (name and email) used in signing commits. These will be stored in the arc config. (Command name deprecated, see this comment)
arc sync now checks whether this user metadata in the arc config matches the metadata in the git config. If not, it will abort and suggest to the user to run the following command:
arc config setgituser will take the git user metadata stored in the arc config and transfer it to the git config. Per default only the local git config of the repo will be overwritten. But this can be changed via --local and --global flags. Additionally, alternative name and email can also be provided

So a common workflow will look like this:
A user must use arc auth once for each distinct gitlab instance he wants access to. Then they can download arcs from that gitlab using arc get. If they want to store their git user metadata for each arc locally they then have to run arc config setgituser. Alternatively they can run it once globally after authentication. Afterwards they can use arc sync everytime they want to pull or push changes for this arc.
Edit: Pronouns
Edit2: Added reference to comment showing new command syntax

Interesting work! Could you elaborate briefly what the intended use cases are? It almost reads as if direct auth with some GitLab instance is now the preferred way of accessing ARCs, which I think should not be the goal, due to breaking the prior constraint of not taking advantage of any specific implementation (could have a GitHub repo or some other Git host).
I do think it's ok to have functions in the ARC commander to help users set up SSH keys / access tokens in specific circumstances, e.g. for DataPLANT HUB. From a security POV, I don't think it's wise to store user credentials inside an ARC?

Mini-nitpick: not all users are male, suggest using "they/them" as pronouns.

Thanks for your input!

Interesting work! Could you elaborate briefly what the intended use cases are? It almost reads as if direct auth with some GitLab instance is now the preferred way of accessing ARCs, which I think should not be the goal, due to breaking the prior constraint of not taking advantage of any specific implementation (could have a GitHub repo or some other Git host).

The arc auth functionality is not meant to directly connect to a GitLab instance. Sry that was a bit missworded. The goal here is to receive an access token from an authorization service. This will enable hopefully seemless authorization for the specific git service this token is meant to be used for.
The arc sync and arc get are not necessarily dependent on this. One could directly use these commands on e.g. an arc stored in Github or an GitLab instance.

I do think it's ok to have functions in the ARC commander to help users set up SSH keys / access tokens in specific circumstances, e.g. for DataPLANT HUB. From a security POV, I don't think it's wise to store user credentials inside an ARC?

The user name and password are only used in the browser window of the token service. The received username and access token  for the git service then get handed directly to git and not stored in the arc config. Stored in the arc config is only the the metainformation used to sign commits: Full name and e-mail of the user. But that is something anyone can see if he checks git locally or visits the git service online.

Mini-nitpick: not all users are male, suggest using "they/them" as pronouns.

Done ;)

New commit: Moved arc auth into a command tree for handling remote access to make its name more descriptive of what it actually does. The command now also takes the authentication protocol and the host address as arguments. E.g.:
arc remoteaccess accesstoken get --openid -s "https://keycloak.dev.bwsfs.uni-freiburg.de/auth/realms/sandbox"
I'm currently working on functionality to receive tokens via the oauth2 authentication protocol, which Github uses. This will then hopefully look like this:
arc remoteaccess accesstoken get --oauth2 -s "https://GitHub.com"

Will merge this for now, receiving access token trough oauth2 will be added in a later PR

authors: HLWeil chgarth


text:
Create navigation map

From R3 folks: when zoomed in close on a workcell, they'd like an overview map that gives an indication where they are currently looking within the workcell.

+1 - agree that would be usefull

This has been implemented in the newest update. When in the workcell view, the tools section now has a 'Geo Overview' tab. We will eventually need to remove the hard-coded layer path in here.

repo: ngageoint/geoq


text:
Deprecation Workaround for scipy.misc.comb

scipy.misc.comb is used in csk.py, radarsat.py, and sentinel.py under io/complex/utils, and maybe others.  This scipy function has been deprecated since version 1.0.0 (documentation here).
The following solution (from here) is an alternative that requires no external dependencies:
from math import factorial
def comb(n, k):
return factorial(n) / factorial(k) / factorial(n - k)

Agreed.  We will fix.

a PR has been submitted to address this issue.  The implemented fix checks the scipy version number and imports from scipy.special if the scipy version is 1 or higher, and from scipy.misc otherwise.  It should work with new versions of scipy and provide backward compatability for older versions.

authors: elwell67 jcasey-beamio utwade

repo: ngageoint/sarpy


text:
Update package.json

Hi there, most of the dependencies in package.json are very out of date.  I've tried updating a few to their latest versions but encounter all kinds of errors when I do so based on interconnected dependencies.  If someone has a better understanding of the modules listed here, it would be great to get an updated version.  If I end up cracking the right version numbers myself, I can submit a pull request.

same here.. facing issue with updating the packages. Seems like this nice project will die 'cos of lack of suppport.

I use ngbp for an enterprise application which has may modules and sub modules. I never had to blindly update the dependencies. I  usually read release notes of each new version and if it is compatible with the version of Angular i am using i will update the version number to the one i want to use in package.json and run bower install. I never faced any problem updating this way .

authors: kundusandeepan manichandra yaronguez

repo: ngbp/ngbp


text:
Add option to pass parameters in contract deployment

The visual tracker allows to deploy contracts via the GUI. Though, contracts that expect a data parameter in their _deploy method can't be handled correctly, since it is not possible to pass a parameter via the visual tracker's GUI. Thus, this issue asks for the option of passing parameters in the process of deploying a contract with the visual tracker.

I'm assuming this issue still hasn't been addressed, correct? I tried getting it to work on my own setup but was unsuccessful...? @devhawk

This has not been addressed to my knowledge

This would be a really convenient feature imo. When developing a contract with deployment data, developers currently are forced to use an SDK to deploy the contract. I rewrote the example in neow3j's boilerplate, hardcoding an address instead of passing it in the deployment, so that developers can more easily get started with the boilerplate and the visual devtracker together. It would be awesome if this option was provided to showcase new developers in a more convenient way that something like this does not need to be hardcoded in the contract, but can just be passed when deploying.
It's been a while since this issue was opened, @devhawk do you think this could get some priority in the near future?

authors: csmuller devhawk mialbu robliou


text:
Working on vhost, not working on apparently identical vhost

Hi there,
I am going mad.... nginx-proxy is installed and working on first container below (pasted key parts from docker inspect). But the second is basically identical and not working. It was working until this morning, I didn't do anything to it that I recall... But I was messing around with the nginx/letsenc setup. I have killed the nginx/letsenc setup and its volumes and re run those two containers several times just in case.
I get a 500 error on that second backend container when it is awake (503 when down, which is expected i guess). The 500 error is apparently a cert problem because the cert req is failing with:

CA marked some of the authorizations as invalid

for which I have disabled ipv6, which didnt seem to be needed in this case, but I am getting frustrated and trying anything! All the domains are on cloudflare, so it's not the DNS provider. It doesn't even appear to arrive on the backend container httpd, cos nginx is falling over first at https.
If I force a renew, the working one renews happily. And the others fail in the same way.
I have directly tested whether https is responding via the exposed 8443 port on the IP set via the nginx-proxy docker network subnet, which is set for the VIRTUAL_PORTs defined in ENV vars. https is responding happily on the exposed (unpublished) ports. Going mad...
If I run the below, it confirms the same behaviour, where i get Hello World on the working vhost, but a 500 error on the other:
you@remotedockerhost$ docker exec your-le-container bash -c 'echo "Hello world!" > /usr/share/nginx/html/.well-known/acme-challenge/hello-world'
you@localcomputer$ curl http://yourdomain.tld/.well-known/acme-challenge/hello-world Hello world!
you@localcomputer$ curl -6 http://yourdomain.tld/.well-known/acme-challenge/hello-world Hello world!
Some of inspect contents from the containers (sensitive details removed inc. domains)
Working one:
 "Env": [             "APACHE_HTTPS_PORT_NUMBER=8443",             "APACHE_HTTP_PORT_NUMBER=8080",             "WORDPRESS_HTTPS_PORT=8443",             "WORDPRESS_HTTP_PORT=8080",             "VIRTUAL_HOST=dev.em.com",             "VIRTUAL_PORT=8443",             "VIRTUAL_PROTO=https",             "LETSENCRYPT_HOST=dev.em.com",         ],         "ExposedPorts": {             "443/tcp": {},             "8080/tcp": {},             "8443/tcp": {}         },
Not working:
  "Env": [             "APACHE_HTTPS_PORT_NUMBER=8443",             "APACHE_HTTP_PORT_NUMBER=8080",             "WORDPRESS_HTTPS_PORT=8443",             "WORDPRESS_HTTP_PORT=8080",             "VIRTUAL_HOST=lux.rr.com",             "VIRTUAL_PORT=8443",             "VIRTUAL_PROTO=https",             "LETSENCRYPT_HOST=lux.rr.com",         ],         "ExposedPorts": {             "443/tcp": {},             "8080/tcp": {},             "8443/tcp": {}         },

Sharing for completeness, but I think this is fine, or the first working backend container wouldn't work at all:
docker run --detach  --name nginx-proxy  --publish 80:80 --publish 443:443    --volume /etc/nginx/certs    --volume /etc/nginx/vhost.d   --volume /usr/share/nginx/html    --volume /var/run/docker.sock:/tmp/docker.sock:ro --network nginx-proxy  jwilder/nginx-proxy:alpine
docker run --detach  --name nginx-letsencrypt  --volumes-from nginx-proxy  --volume /var/run/docker.sock:/var/run/docker.sock:ro    --env "DEFAULT_EMAIL=r@notmyemail.com"   jrcs/letsencrypt-nginx-proxy-companion

My working assumption is that the failure to get the certs means that this is a problem with letsenc side of things breaking the nginx response i.e. and not the nginx-proxy itself.
Unless I am wrong?

There is a third container, not identical, but that is not even started. i am keeping that off for now...

Many thanks in advance for any other pointers or ideas!!!!!!!
I looked at traefik, but this setup is a better simpler approach for little old me. Thanks again.

The 500 error is apparently a cert problem because the cert req is failing with: CA marked some of the authorizations as invalid

My guess is that it's probably the other way around, you can't get a certificate because of the proxying error.
You should have a link providing some additional infos about why the challenge failed on the letsencrypt-nginx-proxy-companion container logs.

APACHE_HTTPS_PORT_NUMBER
APACHE_HTTP_PORT_NUMBER
WORDPRESS_HTTPS_PORT
WORDPRESS_HTTP_PORT

What are those environment variables ?
Could you post the rendered /etc/nginx/conf.d/default.conf file when both containers are up ?

Sorry for the delayed reply - the joys of pandemic :(
Firstly, these are the verbose results of forcing a renew, with only the first container working, like before (there are 2 WP containers then a Joomla):

root@docker-s-1vcpu-2gb-lon1-01:~# docker exec nginx-letsencrypt /app/force_renew -v
/etc/nginx/certs/dev.2.com /app
Creating/renewal dev.2.com certificates... (dev.2.com)
2020-05-27 17:00:51,829:INFO:simp_le:1450: Generating new certificate private key
2020-05-27 17:00:55,904:INFO:simp_le:401: Saving key.pem
2020-05-27 17:00:55,905:INFO:simp_le:401: Saving fullchain.pem
2020-05-27 17:00:55,906:INFO:simp_le:401: Saving cert.pem
/app
/etc/nginx/certs/dev.1.com /app
Creating/renewal dev.1.com certificates... (dev.1.com)
2020-05-27 17:00:57,476:INFO:simp_le:1450: Generating new certificate private key
2020-05-27 17:01:03,832:ERROR:simp_le:1417: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS provider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (see https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v02.api.letsencrypt.org/acme/authz-v3/4848418835
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
/etc/nginx/certs/lux.1.com /app
Creating/renewal lux.1.com certificates... (lux.1.com)
2020-05-27 17:01:05,247:INFO:simp_le:1450: Generating new certificate private key
2020-05-27 17:01:09,184:ERROR:simp_le:1417: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS provider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (see https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v02.api.letsencrypt.org/acme/authz-v3/4848421060
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
Reloading nginx proxy (nginx-proxy)...
2020/05/27 17:01:10 Generated '/etc/nginx/conf.d/default.conf' from 9 containers
2020/05/27 17:01:10 [notice] 285#285: signal process started
root@docker-s-1vcpu-2gb-lon1-01:~#

Environment vars on the first two vhosts in the logs, both WP containers and only the first works:

APACHE_HTTPS_PORT_NUMBER
8443

APACHE_HTTP_PORT_NUMBER
8080

WORDPRESS_HTTPS_PORT
8443

WORDPRESS_HTTP_PORT
8080

The last one is an official joomla container happily answering directly via http on port 80 with no problems, but not via nginx either.
This is the nginx.conf

bash-5.0# more /etc/nginx/conf.d/default.conf
If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
default $http_x_forwarded_proto;
''      $scheme;
}
If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
default $http_x_forwarded_port;
''      $server_port;
}
If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
default upgrade;
'' close;
}
Apply fix for very long server names
server_names_hash_bucket_size 128;
Default dhparam
ssl_dhparam /etc/nginx/dhparam/dhparam.pem;
Set appropriate X-Forwarded-Ssl header
map $scheme $proxy_x_forwarded_ssl {
default off;
https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent"';
access_log off;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384';
ssl_prefer_server_ciphers off;
resolver 127.0.0.11;
HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 80;
access_log /var/log/nginx/access.log vhost;
return 503;
}
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 443 ssl http2;
access_log /var/log/nginx/access.log vhost;
return 503;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
dev.2.com
upstream dev.2.com {
## Can be connected with "nginx-proxy" network
# wp_evemeetsadam
server 172.18.0.3:8443;
# Cannot connect to network of this container
server 127.0.0.1 down;
}
server {
server_name dev.2.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
# Do not HTTPS redirect Let'sEncrypt ACME challenge
location /.well-known/acme-challenge/ {
auth_basic off;
allow all;
root /usr/share/nginx/html;
try_files $uri =404;
break;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
server_name dev.2.com;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/dev.2.com.crt;
ssl_certificate_key /etc/nginx/certs/dev.2.com.key;
ssl_dhparam /etc/nginx/certs/dev.2.com.dhparam.pem;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/nginx/certs/dev.2.com.chain.pem;
add_header Strict-Transport-Security "max-age=31536000" always;
include /etc/nginx/vhost.d/default;
location / {
proxy_pass https://dev.2.com;
}
}
dev.1.com
upstream dev.1.com {
# Cannot connect to network of this container
server 127.0.0.1 down;
## Can be connected with "nginx-proxy" network
# joomla_RRcom
server 172.18.0.5:80;
}
server {
server_name dev.1.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
include /etc/nginx/vhost.d/default;
location / {
proxy_pass http://dev.1.com;
}
}
server {
server_name dev.1.com;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
return 500;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
lux.1.com
upstream lux.1.com {
# Cannot connect to network of this container
server 127.0.0.1 down;
## Can be connected with "nginx-proxy" network
# wp_lux
server 172.18.0.4:8443;
}
server {
server_name lux.1.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
include /etc/nginx/vhost.d/default;
location / {
proxy_pass https://lux.1.com;
}
}
server {
server_name lux.1.com;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
return 500;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
bash-5.0#

Any points or ideas very gratefully received. I am so sure that I must be missing something simple, but just cannot see it :(

Edited the above for clarity.
Many thanks again

It hasn't changed anything except for avoiding letsencrypt limits, but i stopped using the normal LE endpoint and added the env var to use the staging server, which i see changed ok :)

I've been tearing this down and redoing it many times. It's seems that the companion container just isn't making changes for each vhost in the nginx.conf and I am lost about why, especially when it manages it for one vhost. I am thinking of setting the nginx.conf manually based on the other entries so that the acme-challenge entries can exist to help the companion code, because I am giving up on this part of the automation, but it kind of loses the whole point of it.
Very frustrating. And even if I get it going, and there is some weird behaviour, I am not sure that I can trust to it to keep going... :((

BTW http on 80 works find before installing the companion container to deal with SSL certs

It's seems that the companion container just isn't making changes for each vhost in the nginx.conf

Just to clarify, this is NOT the responsibility of the companion but of nginx-proxy.
The companion never ever touches the /etc/nginx/conf.d/default.conf file.

upstream lux.1.com {
                        # Cannot connect to network of this container
                        server 127.0.0.1 down;
                        ## Can be connected with "nginx-proxy" network
                        # wp_lux
                        server 172.18.0.4:8443;
}

You should not have both server directives, they are both mutually exclusive in nginx.tmpl. I've never ever seen that happening on my setups.
This might be an nginx-proxy issue rather than an issue with the companion.

Hi there, many thanks. I hope all is well. Thank you :)
I had answered about the env vars, but I might have misunderstood what you wanted:
APACHE_HTTPS_PORT_NUMBER | 8443
APACHE_HTTP_PORT_NUMBER | 8080
WORDPRESS_HTTPS_PORT | 8443
WORDPRESS_HTTP_PORT | 8080

are the env vars for both the working and the not working WP containers. Or do you mean do those ev's should show in a log that I have not looked at? Nothing comes up in the standard container logs on stout about ev's
The stout log has for the problem containers:
2020-06-04 21:24:17,301:ERROR:simp_le:1417: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS provider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (see https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v02.api.letsencrypt.org/acme/authz-v3/5022185976

Challenge validation has failed, see error log.

Thanks for clarifying re the /etc/nginx/conf.d/default.conf generated by nginxproxy, presumably  based on the shared vhost files (should have noticed that /etc/nginx/conf.d/default.conf is not on a shared volume).

upstream lux.1.com {
                        # Cannot connect to network of this container
                        server 127.0.0.1 down;
                        ## Can be connected with "nginx-proxy" network
                        # wp_lux
                        server 172.18.0.4:8443;
}

You should not have both server directives, they are both mutually exclusive in nginx.tmpl. I've never ever seen that happening on my setups.
This might be an nginx-proxy issue rather than an issue with the companion.

Oh no...

On the other hand, the working vhost has two server directives too, one 127 localhost.
(I am new to nginx)

Important note - I am setting up both nginx and the companion at the command line, but managing via Portainer.
I am now wondering if that is causing an issue somehow. Will google

FYI I just replaced the alpine version of the nginx-proxy with the 'normal' one, deleting the volumes for both that and the companion. Reinstalled both. same problem. Totally lost

Could you share the commands you are using to spawn your Wordpress containers (both working and non working) ?

Yes, please, thank you.
I used to Portainer to set them up, so just used rekcod to reverse engineer the docker run commands.
I am convinced that I will kick myself once I see what is wrong, but I just can't see what I've done wrong.
The problem one:
docker run --name wp_ls --runtime runc -v wordpress-wp_ls:/bitnami/wordpress -p 9002:8443/tcp --net wp-wp_ls --restart always -h 3f6a5d5f5c67 --expose 443/tcp --expose 8080/tcp --expose 8443/tcp -l maintainer='Bitnami <containers@bitnami.com>' -e 'PATH=/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/wp-cli/bin:/opt/bitnami/mysql/bin:/opt/bitnami/common/bin:/opt/bitnami/nami/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' -e 'BITNAMI_PKG_CHMOD=-R g+rwX' -e 'HOME=/' -e 'ALLOW_EMPTY_PASSWORD=no' -e 'APACHE_ENABLE_CUSTOM_PORTS=no' -e 'APACHE_HTTPS_PORT_NUMBER=8443' -e 'APACHE_HTTP_PORT_NUMBER=8080' -e 'BITNAMI_APP_NAME=wordpress' -e 'BITNAMI_IMAGE_VERSION=5.4.1-debian-10-r6' -e 'MARIADB_HOST=mariadb' -e 'MARIADB_PORT_NUMBER=3306' -e 'MARIADB_ROOT_USER=root' -e 'MYSQL_CLIENT_CREATE_DATABASE_PRIVILEGES=ALL' -e 'MYSQL_CLIENT_ENABLE_SSL=no' -e 'NAMI_PREFIX=/.nami' -e 'OS_ARCH=amd64' -e 'OS_FLAVOUR=debian-10' -e 'OS_NAME=linux' -e 'PHP_MEMORY_LIMIT=256M' -e 'WORDPRESS_BLOG_NAME=User'\''s Blog!' -e 'WORDPRESS_DATABASE_NAME=wp_ls' -e 'WORDPRESS_DATABASE_PASSWORD=no' -e 'WORDPRESS_DATABASE_USER=wp_ls' -e 'WORDPRESS_EMAIL=user@example.com' -e 'WORDPRESS_FIRST_NAME=FirstName' -e 'WORDPRESS_HTACCESS_OVERRIDE_NONE=yes' -e 'WORDPRESS_HTACCESS_PERSISTENCE_ENABLED=yes' -e 'WORDPRESS_HTTPS_PORT=8443' -e 'WORDPRESS_HTTP_PORT=8080' -e 'WORDPRESS_LAST_NAME=LastName' -e 'WORDPRESS_PASSWORD=no' -e 'WORDPRESS_SCHEME=http' -e 'WORDPRESS_SKIP_INSTALL=no' -e 'WORDPRESS_TABLE_PREFIX=wp_' -e 'WORDPRESS_USERNAME=user' -e 'VIRTUAL_HOST=l.r.com' -e 'VIRTUAL_PORT=8443' -e 'VIRTUAL_PROTO=https' -e 'LETSENCRYPT_HOST=l.r.com' -e 'MARIADB_ROOT_PASSWORD=' -e 'MYSQL_CLIENT_CREATE_DATABASE_NAME=' -e 'MYSQL_CLIENT_CREATE_DATABASE_PASSWORD=' -e 'MYSQL_CLIENT_CREATE_DATABASE_USER=' -e 'MYSQL_CLIENT_SSL_CA_FILE=' -e 'SMTP_HOST=' -e 'SMTP_PASSWORD=' -e 'SMTP_PORT=' -e 'SMTP_PROTOCOL=' -e 'SMTP_USER=' -e 'SMTP_USERNAME=' -e 'WORDPRESS_DATABASE_SSL_CA_FILE=' -e 'WORDPRESS_EXTRA_WP_CONFIG_CONTENT=' -e 'WORDPRESS_RESET_DATA_PERMISSIONS=no' -d --entrypoint "/app-entrypoint.sh" bitnami/wordpress:latest 'httpd' '-f' '/opt/bitnami/apache/conf/httpd.conf' '-DFOREGROUND'
The working one:
docker run --name wp_ema --runtime runc -v wordpress-ema:/bitnami/wordpress --net wordpress-ema --restart always -h 3f6a5d5f5c67 --expose 443/tcp --expose 8080/tcp --expose 8443/tcp -l maintainer='Bitnami <containers@bitnami.com>' -e 'PATH=/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/wp-cli/bin:/opt/bitnami/mysql/bin:/opt/bitnami/common/bin:/opt/bitnami/nami/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' -e 'BITNAMI_PKG_CHMOD=-R g+rwX' -e 'HOME=/' -e 'ALLOW_EMPTY_PASSWORD=no' -e 'APACHE_ENABLE_CUSTOM_PORTS=no' -e 'APACHE_HTTPS_PORT_NUMBER=8443' -e 'APACHE_HTTP_PORT_NUMBER=8080' -e 'BITNAMI_APP_NAME=wordpress' -e 'BITNAMI_IMAGE_VERSION=5.4.1-debian-10-r6' -e 'MARIADB_HOST=mariadb' -e 'MARIADB_PORT_NUMBER=3306' -e 'MARIADB_ROOT_USER=root' -e 'MYSQL_CLIENT_CREATE_DATABASE_PRIVILEGES=ALL' -e 'MYSQL_CLIENT_ENABLE_SSL=no' -e 'NAMI_PREFIX=/.nami' -e 'OS_ARCH=amd64' -e 'OS_FLAVOUR=debian-10' -e 'OS_NAME=linux' -e 'PHP_MEMORY_LIMIT=256M' -e 'WORDPRESS_BLOG_NAME=User'\''s Blog!' -e 'WORDPRESS_DATABASE_NAME=wp_ema' -e 'WORDPRESS_DATABASE_PASSWORD=no' -e 'WORDPRESS_DATABASE_USER=wp_ema' -e 'WORDPRESS_EMAIL=user@example.com' -e 'WORDPRESS_FIRST_NAME=FirstName' -e 'WORDPRESS_HTACCESS_OVERRIDE_NONE=yes' -e 'WORDPRESS_HTACCESS_PERSISTENCE_ENABLED=yes' -e 'WORDPRESS_HTTPS_PORT=8443' -e 'WORDPRESS_HTTP_PORT=8080' -e 'WORDPRESS_LAST_NAME=LastName' -e 'WORDPRESS_PASSWORD=no' -e 'WORDPRESS_SCHEME=http' -e 'WORDPRESS_SKIP_INSTALL=no' -e 'WORDPRESS_TABLE_PREFIX=wp_' -e 'WORDPRESS_USERNAME=user' -e 'VIRTUAL_HOST=dev.ema.com' -e 'VIRTUAL_PORT=8443' -e 'VIRTUAL_PROTO=https' -e 'LETSENCRYPT_HOST=dev.ema.com' -e 'MARIADB_ROOT_PASSWORD=' -e 'MYSQL_CLIENT_CREATE_DATABASE_NAME=' -e 'MYSQL_CLIENT_CREATE_DATABASE_PASSWORD=' -e 'MYSQL_CLIENT_CREATE_DATABASE_USER=' -e 'MYSQL_CLIENT_SSL_CA_FILE=' -e 'SMTP_HOST=' -e 'SMTP_PASSWORD=' -e 'SMTP_PORT=' -e 'SMTP_PROTOCOL=' -e 'SMTP_USER=' -e 'SMTP_USERNAME=' -e 'WORDPRESS_DATABASE_SSL_CA_FILE=' -e 'WORDPRESS_EXTRA_WP_CONFIG_CONTENT=' -d --entrypoint "/app-entrypoint.sh" bitnami/wordpress:latest 'httpd' '-f' '/opt/bitnami/apache/conf/httpd.conf' '-DFOREGROUND'

Your containers have to be on the same Docker network as the nginx-proxy container.

They are normally, so it's not that, but I am beginning to wonder if it is something to do with accessing the docker socket file on the host, cos portainer has to as well...
Maybe it is not that, but I have to get this done so I am experimenting with other options so I can get something, anything going :(
Many thanks though in the meantime :)

They are normally

Well from those command line, they're not 🤷♂
I took the liberty to edit your previous post as that was barely readable.
Could you try running your containers with
-e 'VIRTUAL_PORT=8443' -e 'VIRTUAL_PROTO=https'
replaced by
-e 'VIRTUAL_PORT=8080'
?

Agreed, regarding the command line that I shared. My mistake, as I was going totally crossyeyed with this. But I know that wasn't a problem before and must have been something to do with the rekcod command line reverse engineering.
The 8433 change to 8000 shouldn't make a difference as both are the same WP image and one works on 8443, but honestly I have had to give up and move on. Pandemic plus this means I have a horrific time deficit.
Many thanks for your development and efforts with me. I do appreciated it (empty words)
Warmest regards and best wishes


text:
How to upgrade the operator on Openshift?

Hello,
The documentation is not very clear about the path to update the operator on Openshift.
According to this markdown , we need to apply CRD as a prerequisite.
What is the next step?
On operator page, we can see the latest version available (2.1.0) but it's impossible to upgrade to it.
Current version: 1.5.0
Update channel: alpha
Update approval: Manual (Don't have any button to upgrade to the latest)
Thank you

Hi @llomgui, can you please explain what you mean by  impossible to upgrade to it., are their any logs which you can share as it'll help us understand the issue better. Thanks!

Hello @vepatel,
There is no "seemless upgrade" step available on the operator, there is no button to update it.
Is there any way to do it manually? How to update to ClusterServiceVersion v1.5.2 for example?
Thank you

@vepatel Thank you, it worked. I deleted the operator then re-installed it.
I had one error about IngressClass being a string instead of an object. Quick fixed adding name attribute.
Do I have to deal with CRD as indicated by the documentation?

Hi @llomgui, or operator is helm based and unfortunately helm does not handle CRDs upgrades automatically so CRDs have to be applied manually as a pre-req.
see https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations

Thank you for you help. 👍

authors: llomgui vepatel

repo: nginxinc/nginx-ingress-helm-operator


text:
Not compatible with react 16

Hey,
first of all thanks for the project. I got the following issue after I upgrade React to v16.0.0.
npm WARN react-file-reader-input@1.1.4 requires a peer of react@^15.0.0 but none was installed.
Any update regarding a new version that supports React 16?

Fixed in https://github.com/ngokevin/react-file-reader-input/pull/18.
I'm not closing the issue until a new version is published on npm. @ngokevin Would you have any spare time to publish a new version soon?

This can now be closed! @maximerety

authors: dingdingbai gausie maximerety

repo: ngokevin/react-file-reader-input


text:
How to get a fields original config on click

Question
(v5.9.3)
I'm attempting to build a kind of WYSIWYG editor, where the end user can configure the form how they want. The idea would be that, in edit mode, they can click on a field to bring up the edit window, do their changes, save it back, and regenerate the form.
So with that out there, I have a couple of questions:

I'm noticing that I can set a click event on the fields using templateOptions.click. This returns the processed field config. Is there any way to get the original?

To the above point, ofc we have the original object because. we generated the form with it. But we would have to search it. If there's no way to get to the original config, is there some sort of property that identifies it's path in the original? _keyPath doesn't seem to do this (I can have multiple fields with the same key, so I don't have a way of using that to identify the form, and this doesn't seem to go more than 1 level deep even if I have fields in nested groups?)

Is there a way to apply this click event enmasse on all fields on the form without having to loop through and apply it before generating the form?

I'm continuing to dig through the source and look to see if there's anything that can help me in this situation, will update if I find anything.
Thanks for this awesome projects!

I'm noticing that I can set a click event on the fields using templateOptions.click. This returns the processed field config. Is there any way to get the original?

the click event emit the field through its argument

Is there a way to apply this click event enmasse on all fields on the form without having to loop through and apply it before generating the form?

yes, use custom extension see https://formly.dev/examples/advanced/i18n-alternative

authors: aitboudad blitzmann

repo: ngx-formly/ngx-formly


text:
Custom validation for array of objects

Is there a way to provide custom validation for array of objects. If yes, could you please provide an example.
In my use case I have an array like
allocations : [ {fundName: 'abc', percentage: 10},{fundName: 'def', percentage: 30}]. I want to make sure that the percentage total of the array does not exceed 100.
I have the validation for allocations defined as  "validators": {
"validation": [
{
"name": "allocation-percent-total",
"options": { "errorPath": "percentage" }
}
]
},
However the percent field is still being valid in case of an invalid scenario. Probably the "errorPath" value specified is not correct . How should be specify the error path for a property inside an array of objects

errorPath value here is wrong, you've multiple percentage fields inside array, two solution can be used:
1- Show the validation in the field array itself instead of percentage field (add https://github.com/ngx-formly/ngx-formly/issues/3170#issuecomment-1029762431 inside repeat field type)
2- pass the right key to errorPath:   { "errorPath": "0.percentage" }

Thank you


text:
add a custom popup trigger event in react wrapper

Version
@toast-ui/react-calendar": "^2.1.3"
Test Environment
testing in vs. code
windows environment
chrome browser
Current Behavior
I am using the calendar to add appointments thus I want on a date click to open a modal to enter a person's data.
I checked the suggested way in the tui calendar docs and tried to replicate in the react wrapper but it does not workout. no console logs is appearing. I could not find in the docs an event to be triggered onclick (once clicked on a day date/time)

  const clickSchedule = function (e) {
    console.log('clickSchedule', e)
  }

  const beforeCreateSchedule = function (e) {
    console.log('beforeCreateSchedule', e)
  }

  const beforeUpdateSchedule = function (e) {
    console.log('beforeUpdateSchedule', e)
  }

  const beforeDeleteSchedule = function (e) {
    console.log('beforeDeleteSchedule', e)
  }

      <Calendar
        ref={calendarRef}
        useCreationPopup={false}
        useDetailPopup={false}
        clickSchedule={clickSchedule}
        beforeCreateSchedule={beforeCreateSchedule}
        beforeUpdateSchedule={beforeUpdateSchedule}
        beforeDeleteSchedule={beforeDeleteSchedule}
      />

Expected Behavior
an event to be triggered when clicked on a date in the calendar

        clickSchedule={clickSchedule}
        beforeCreateSchedule={beforeCreateSchedule}
        beforeUpdateSchedule={beforeUpdateSchedule}
        beforeDeleteSchedule={beforeDeleteSchedule}

should be
        onClickEvent={clickSchedule}
        onBeforeCreateEvent={beforeCreateSchedule}
        onBeforeUpdateEvent={beforeUpdateSchedule}
        onBeforeDeleteEvent={beforeDeleteSchedule}

although onBeforeCreateEvent does not trigger my custom popup which is why i decided to go the root of forking the repo and editing the popup files but then i ran into this issue #1261

thanks @Melissacinta & @adhrinae for your replies.
I have followed what you mentioned but unfortunately I could not  trigger my custom popup to show upon the selection of a date.

@loralameh  i have this same issue too

@loralameh @Melissacinta
Please describe HOW you followed what I mentioned. I cannot guess what you've missed or if there are any bugs.

I have followed what you mentioned but unfortunately I could not trigger my custom popup to show upon the selection of a date.

As you mentioned the 'selection of a date', let's focus on this.
First, You need to pass the handler to the onSelectDateTime prop. This event is fired when the user selects dates or times.
https://github.com/nhn/tui.calendar/blob/main/docs/en/apis/calendar.md#selectdatetime
Then there is a gridSelectionElements in the object passed to the event handler. All you need to do is get the position from the element by using the getBoundingClientRect method(or else) and show your custom popup leveraging this position.

@adhrinae  that is the exact handler (onSelectDateTime) that I was searching for .. I was lost in the docs and could not figure it out I suggest adding this code to the react wrapper docs because it was a missing piece  for me... thank you so much for your time and help

authors: Melissacinta adhrinae loralameh


text:
[Issue] Using API addShape results in error 'The executing command state is locked.'

Version
Version: 3.5.3 (from the example given in the repo anyway)
You can reproduce online: https://nhn.github.io/tui.image-editor/latest/examples/example01-includeUi.html
Development Environment
OS : Windows 10
Browser: Chrome 77.0.3835.0 (Canary), Chrome 75.0.3770.100 (Stable)
Current Behavior
When trying to add a shape programmatically (i.e. through the provided API), there are actually 2 commands that are issued and the "Command locked' error kicks in.

Here is a very simple snippet to reproduce, simply open your DevTools and copy/paste
imageEditor.addShape('circle', {
    fill          : '#ff0000',
    stroke        : '#ff0000',
    strokeWidth   : 0,
    top           : 200,
    left          : 300,
    rx            : 80,
    ry            : 80,
    isRegular     : true
})

Expected Behavior
No error.
In the scenario above, no big deal but I have a more complex one where it completely messes up with the appplication.

@guillaumegarcia13 Thank you for your report.

I guess I found a workaround.
It all boils down to the API being too entangled with the UI (activating tabs and so on...).
I managed to rewrite the strokeRange this way (I do not use it in my implementation but as I reuse part of the UI, I have to deal with event handling).
imageEditor.ui.shape._els.strokeRange.__proto__.trigger = function() { ; };
This is really hacky, though.

Fixed in 3.9.0.


text:
command "init --remote" fails with message "Failed to fetch user data"

Describe the bug
I'm using nhost v2. I have created a remote repository and now I'm trying to spin up a local repository and link it with the remote. When I run nhost init --remote, I get Failed to fetch user data when I supply my email and password (correct values).
To Reproduce
Steps to reproduce the behavior:

Create a remote repository
Run nhost init --remote

Expected behavior
Process complete smoothly
Screenshots

Desktop (please complete the following information):

OS: macos monterey
Version: Nhost CLI v0.5.11 for darwin-arm64

Same here, I get Failed to pull migrations from remote instead.

Can you please run nhost init --remote --debug and confirm what is the exact point at which the CLI is throwing these errors? The debug flag should show you a log trace.

Not working for me either. I have created an account using the github login integration.
Despite this when I try to login using: nhost login (or any method that requires auth)
The command asks me for my email and password (account does not have a password)

Not working for me either. I have created an account using the github login integration. Despite this when I try to login using: nhost login (or any method that requires auth) The command asks me for my email and password (account does not have a password)

You can save your password on Nhost dashboard. And then use that one to login.

Since, there aren't any responses and this does seems potentially a problem from user's end, I'm closing this issue.
We can open it again if anyone can't find their way around it.

Sometimes I got this as well. Do we have a wait to bring you log file or sth similar?

Hi Sang,
Thanks for the prompt response. There is indeed the option to save a password against my account and I tried that several times last night. First whilst logged in and then after logout and login. On each occasion there was an invalid access token error.
Thanks, Ross
On Tuesday, 11 January 2022, 06:44:48 GMT, Sang Dang @.***> wrote:
Sometimes I got this as well. Do we have a wait to bring you log file or sth similar?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>

authors: artistic-differences mrinalwahal sangdth seyaobey-dev spkprav

repo: nhost/cli


text:
DB migrations not applied during upgrade

Upgrading from v0.10.0 to v0.17.0
Got this when applying Hasura metadata:

Checked the db and auth.user_authenticators does not exist
docker logs -f 83e89cade061

> hasura-auth@0.17.0 start /app
> node ./dist/start.js

{"level":"info","message":"Log level: info"}
{"level":"info","message":"Waiting for Hasura to be ready..."}
{"level":"info","message":"Hasura is ready"}
{"level":"info","message":"Applying SQL migrations..."}
{"level":"info","message":"SQL migrations applied"}
{"level":"info","message":"Applying metadata..."}
{"level":"info","message":"Metadata applied"}
{"level":"info","message":"Running on port 4000"}

That's strange.
Can you try this command? What's the output you see?
SELECT * FROM auth.migrations;

I've tried this multiple times by going back to the prev version and clearing the db and then upgrading, get the same result

authors: elitan mmmmillar

repo: nhost/hasura-auth


text:
Prefer attributes over CSS classes

Pull Request
🤨 Rationale
This PR migrates nimble away from using host CSS classes as part of the API for nimble components.
For users, host CSS classes defining styles provides poor typing compared to attributes and is strange as users expect to define classes and associated styles themselves. For nimble developers host classes make inflexible APIs as you cannot readily associate behavior changes to adding or removing classes and even doing so may defy user expectations.
See the discussion in #676 for additional background.
👩💻 Implementation
The following API changes were made per component:
breadcrumb

[appearance] enum has keys: default, prominent

removed class .prominent-links

button

[appearance-variant] enum has keys default, primary

removed class .primary

combobox

[error-visible] boolean

removed class .invalid

icon

[severity] enum has keys default, success, information, warning, error

removed classes .fail, .warning, .pass, .information

number-field

[error-visible] boolean

removed class .invalid

text-field

[full-bleed] boolean

removed class .clear-inline-padding

[error-visible] boolean

removed class .invalid

tooltip

[severity] enum has keys default, information, error

removed classes .fail, .information

[icon-visible] boolean attribute

removed class .icon-visible

In addition some minor refactors are included in this PR:

nimble-components

IHasErrorText renamed to ErrorPattern to match our other pattern conventions and used consistently
ButtonPattern was also updated to align
DesignSystem.tagFor used consistently in component templates instead of context.tagFor or hard-coded names
Various storybook updates such as generating uniqueIDs for tooltip stories, splitting text-customization story to be per component instead of a monolithic test, cleaned up shared storybook states

nimble-angular

Removed the login component of the example app to align with blazor app

nimble-blazor

Consistent whitespace formatting for razor templates

🧪 Testing
For nimble-components largely relied
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed. Doc updates are in #676

Heads up that the "Testing" section of your PR description is partially missing/ cut off - I only see "For nimble-components largely relied" in it.

authors: msmithNI rajsite

repo: ni/nimble


text:
adding localization text in niveristand-instrument-addon-custom-device-LabVIEW-Example in control page

[x] This contribution adheres to CONTRIBUTING.md.

TODO: Include high-level description of the changes in this pull request.
As part of User Story (https://ni.visualstudio.com/DevCentral/_workitems/edit/2665528/) We are trying to include localization description for Chinese, German, Japanese, French, Korean languages for different VeriStand third party products.
TODO: Justify why this contribution should be part of the project.
Taken reference from VeriStand control page (\argo\ni\nipkg\pool\ni-v\ni-veristand-2024\24.0.0\24.0.0.49451-0+f299\ni-veristand-2024_24.0.0.49451-0+f299_windows_x64.nipkg.control) and edited niveristand-instrument-addon-custom-device-LabVIEW-Examples control page accordingly.
TODO: Detail what testing has been done to ensure this submission meets requirements.
Testing is in progress

/AzurePipelines run

authors: Palshini buckd


text:
Sublime Text 3 support

This package is not listed in Package Control in Sublime Text 3. Is ST3 supported?

+1

+1

The Sublime Text 3 version of the plugin can be found here

For the record, to install the plugin @kostasx mentioned,
Command + Shift + P => Add Repository
enter the GitHub url... https://github.com/aziz/sublime-js2coffee
Then proceed to install it via package control.
BTW, I've made a PR to get this into the main package control repo: https://github.com/wbond/package_control_channel/pull/6041

authors: TangMonk aexmachina kostasx tsktsktsky voltechs