Blank Screen issues with Virtualbox Additions installed

Hello xrdp team,
First order, thanks; xrdp is an amazing piece of software, and I am grateful for the project, it works well and i use it a lot.
I have isolated an issue when virtualbox additions are installed:

install virtualbox, install guest ubuntu 20.04
run: apt install -y xrdp, reboot guest
connect via rdp client, everything works
install virtualbox guest additions from mounted iso, reboot
connect via rdp client, shows a blank (black) screen with no desktop environment

^^ this "black screen" problem can be avoided by blacklisting this kernel module: vboxguest

edit this file: /etc/modprobe.d/blacklist.conf
add this line to the file: install vboxguest /bin/true      (using blacklist vboxguest doesnt work)
run: update-initramfs -u && reboot
connect via rdp client, everything works again

i would like to raise this issue for anyone that is wanting to use xrdp in virtualbox.
i can also provide logs and configurations, and recreate the issue in order to debug the issue for the xrdp team.

Hi @cbluth
Thanks for raising this.
A couple of questions for you, which may be useful for others reading this.

What is the host machine? This may have no bearing on the issue, but it would be good to record it anyway.
What backend are you using on xrdp? Presumably Xvnc as you're not installing xorgxrdp.
What is the kernel version (uname -a)?
If you leave the 'black screen' for around 3 minutes, does the connection happen eventually?

Thanks,

No more input - closing

@matt335672 Requesting a re-open of this issue, as we are experiencing this as well and it blocks local development. With GuestAdditions installed, we get a blackscreen. After uninstall and reboot, all works great but we lose vagrant synced_dirs which blocks us.

VirtualBox: 6.1.30 r148432
GuestAdditions: 6.1.16
Clients Tested:

Guacamole
Microsoft Remote Desktop (macOS)

Answering questions from last comment, but these are for our environment (not the op):
What is the host machine?

Ubuntu 20.04

Installed via: apt update && apt install xrdp

What backend are you using on xrdp?

Xvnc

What is the kernel version (uname -a)?
Linux node1 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

If you leave the 'black screen' for around 3 minutes, does the connection happen eventually?
Negative.
xrdp.ini (stock defaults from ubuntu)
[Globals]
; xrdp.ini file version number
ini_version=1

; fork a new process for each incoming connection
fork=true

; ports to listen on, number alone means listen on all interfaces
; <IP_ADDRESS> or :: if ipv6 is configured
; space between multiple occurrences
;
; Examples:
;   port=3389
;   port=unix://./tmp/xrdp.socket
;   port=tcp://.:3389                           <IP_ADDRESS>:3389
;   port=tcp://:3389                            *:3389
;   port=tcp://<any ipv4 format addr>:3389      <IP_ADDRESS>:3389
;   port=tcp6://.:3389                          ::1:3389
;   port=tcp6://:3389                           *:3389
;   port=tcp6://{<any ipv6 format addr>}:3389   {FC00:0:0:0:0:0:0:1}:3389
;   port=vsock://<cid>:<port>
port=3389

; 'port' above should be connected to with vsock instead of tcp
; use this only with number alone in port above
; prefer use vsock://<cid>:<port> above
use_vsock=false

; regulate if the listening socket use socket option tcp_nodelay
; no buffering will be performed in the TCP stack
tcp_nodelay=true

; regulate if the listening socket use socket option keepalive
; if the network connection disappear without close messages the connection will be closed
tcp_keepalive=true

; set tcp send/recv buffer (for experts)
#tcp_send_buffer_bytes=32768
#tcp_recv_buffer_bytes=32768

; security layer can be 'tls', 'rdp' or 'negotiate'
; for client compatible layer
security_layer=negotiate

; minimum security level allowed for client for classic RDP encryption
; use tls_ciphers to configure TLS encryption
; can be 'none', 'low', 'medium', 'high', 'fips'
crypt_level=high

; 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
certificate=
key_file=

; set SSL protocols
; can be comma separated list of 'SSLv3', 'TLSv1', 'TLSv1.1', 'TLSv1.2', 'TLSv1.3'
ssl_protocols=TLSv1.2, TLSv1.3
; set TLS cipher suites
#tls_ciphers=HIGH

; Section name to use for automatic login if the client sends username
; and password. If empty, the domain name sent by the client is used.
; If empty and no domain name is given, the first suitable section in
; this file will be used.
autorun=

allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
#hidelogwindow=true
max_bpp=32
new_cursors=true
; fastpath - can be 'input', 'output', 'both', 'none'
use_fastpath=both
; when true, userid/password *must* be passed on cmd line
#require_credentials=true
; You can set the PAM error text in a gateway setup (MAX 256 chars)
#pamerrortxt=change your password according to policy at http://url

;
; colors used by windows in RGB format
;
blue=009cb5
grey=dedede
#black=000000
#dark_grey=808080
#blue=08246b
#dark_blue=08246b
#white=ffffff
#red=ff0000
#green=00ff00
#background=626c72

;
; configure login screen
;

; Login Screen Window Title
#ls_title=My Login Title

; top level window background color in RGB format
ls_top_window_bg_color=009cb5

; width and height of login screen
ls_width=350
ls_height=430

; login screen background color in RGB format
ls_bg_color=dedede

; optional background image filename (bmp format).
#ls_background_image=

; logo
; full path to bmp-file or file in shared folder
ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50

; for positioning labels such as username, password etc
ls_label_x_pos=30
ls_label_width=65

; for positioning text and combo boxes next to above labels
ls_input_x_pos=110
ls_input_width=210

; y pos for first label and combo box
ls_input_y_pos=220

; OK button
ls_btn_ok_x_pos=142
ls_btn_ok_y_pos=370
ls_btn_ok_width=85
ls_btn_ok_height=30

; Cancel button
ls_btn_cancel_x_pos=237
ls_btn_cancel_y_pos=370
ls_btn_cancel_width=85
ls_btn_cancel_height=30

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=true
SyslogLevel=DEBUG
; LogLevel and SysLogLevel could by any of: core, error, warning, info or debug

[Channels]
; Channel names not listed here will be blocked by XRDP.
; You can block any channel by setting its value to false.
; IMPORTANT! All channels are not supported in all use
; cases even if you set all values to true.
; You can override these settings on each session type
; These settings are only used if allow_channels=true
rdpdr=true
rdpsnd=true
drdynvc=true
cliprdr=true
rail=true
xrdpvr=true
tcutils=true

; for debugging xrdp, in section xrdp1, change port=-1 to this:
#port=/tmp/.xrdp/xrdp_display_10

; for debugging xrdp, add following line to section xrdp1
#chansrvport=/tmp/.xrdp/xrdp_chansrv_socket_7210

;
; Session types
;

; Some session types such as Xorg, X11rdp and Xvnc start a display server.
; Startup command-line parameters for the display server are configured
; in sesman.ini. See and configure also sesman.ini.
[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=<IP_ADDRESS>
port=-1
code=20

[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask
ip=<IP_ADDRESS>
port=-1
#xserverbpp=24
#delay_ms=2000

[vnc-any]
name=vnc-any
lib=libvnc.so
ip=ask
port=ask5900
username=na
password=ask
#pamusername=asksame
#pampassword=asksame
#pamsessionmng=<IP_ADDRESS>
#delay_ms=2000

[neutrinordp-any]
name=neutrinordp-any
lib=libxrdpneutrinordp.so
ip=ask
port=ask3389
username=ask
password=ask

; You can override the common channel settings for each session type
#channel.rdpdr=true
#channel.rdpsnd=true
#channel.drdynvc=true
#channel.cliprdr=true
#channel.rail=true
#channel.xrdpvr=true

xRDP Log
[20211216-17:56:04] [INFO ] starting xrdp with pid 3044
[20211216-17:56:04] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
[20211216-17:56:04] [INFO ] listening to port 3389 on <IP_ADDRESS>
[20211216-17:56:04] [INFO ] xrdp_listen_pp done
[20211216-17:56:09] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 49116
[20211216-17:56:09] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20211216-17:56:09] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389)
[20211216-17:56:09] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20211216-17:56:09] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20211216-17:56:09] [DEBUG] TLSv1.3 enabled
[20211216-17:56:09] [DEBUG] TLSv1.2 enabled
[20211216-17:56:09] [DEBUG] Security layer: requested 3, selected 1
[20211216-17:56:09] [INFO ] connected client computer name: Guacamole RDP
[20211216-17:56:09] [INFO ] adding channel item name cliprdr chan_id 1004 flags 0xc0a00000
[20211216-17:56:09] [INFO ] adding channel item name rdpdr chan_id 1005 flags 0xc0800000
[20211216-17:56:09] [INFO ] adding channel item name rdpsnd chan_id 1006 flags 0xc0000000
[20211216-17:56:09] [INFO ] TLS connection established from ::ffff:<IP_ADDRESS> port 49116: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20211216-17:56:10] [DEBUG] xrdp_00000be8_wm_login_mode_event_00000001
[20211216-17:56:10] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20211216-17:56:10] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[20211216-17:56:10] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
[20211216-17:56:10] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20211216-17:56:10] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20211216-17:56:10] [DEBUG] return value from xrdp_mm_connect 0
[20211216-17:56:10] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20211216-17:56:10] [DEBUG] xrdp_wm_log_msg: started connecting
[20211216-17:56:10] [INFO ] lib_mod_log_peer: xrdp_pid=3048 connected to X11rdp_pid=3056 X11rdp_uid=1002 X11rdp_gid=100 client_ip=::ffff:<IP_ADDRESS> client_port=49116
[20211216-17:56:10] [DEBUG] xrdp_wm_log_msg: connected ok
[20211216-17:56:10] [DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful
[20211216-17:56:10] [DEBUG] Closed socket 18 (AF_INET6 ::1 port 56776)

After a few seconds we also get this:
[20211216-18:09:14] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again...
[20211216-18:09:14] [DEBUG] Closed socket 20 (AF_UNIX)
[20211216-18:09:18] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again...
[20211216-18:09:18] [DEBUG] Closed socket 20 (AF_UNIX)
[20211216-18:09:22] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again...
[20211216-18:09:22] [DEBUG] Closed socket 20 (AF_UNIX)
[20211216-18:09:26] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again...
[20211216-18:09:26] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan
[20211216-18:09:26] [DEBUG] Closed socket 18 (AF_INET6 ::1 port 56792)

@derks
A couple of questions for you:-

Does the same happen with the Xvnc backend?
Can you also post the contents of ~/.xorgrrdp.10.log when this happens with the Xorg backend?

Thanks.

@derks
Your info above isn't consistent. If you're running the Xvnc backend, you won't get this in the log, as it's generated by the Xorg connection module:-
[20211216-17:56:10] [INFO ] lib_mod_log_peer: xrdp_pid=3048 connected to X11rdp_pid=3056 X11rdp_uid=1002 X11rdp_gid=100 client_ip=::ffff:<IP_ADDRESS> client_port=49116

Are you sure this happens with the Xvnc backend? If so, please post recent contents of /var/log/xrdp-sesman.log when this happens.
Can you also post the contents of ~/.xorgxrdp.10.log when this happens with the Xorg backend?

Thanks.

@matt335672 apologies, I mis-read the config. It is running Xorg backend.
I was actually (recently) able to get things working and it has been without issue in testing over the last 2 weeks. In our environment we use VirtualBox with Vagrant, after adding the vagrant-vbguest plugin (which manages updating VirtualBox Guest Additions), this issue appears to have gone away.
VirtualBox: 6.1.30r148432
VirtualBox Guest Additions: 6.1.30r148432
I think this is safe to close.

OK - thanks for the update. I had a swift look through the VBox changelog and didn't see anything in the guest additions from 6.1.16 to 6.1.30 which stood out.
If you do come across it again, the contents of ~/.xorgxrdp.10.log may tell us more. Feel free to request re-open in that case.


CJK tokenization from deltas library

initial request

I removed this line, this is already taken caren of by removing external link in strip_wikitext see line "lexicon.url,"

it is also giving an error : "error: invalid group reference 5 at position 1"
'''
(re.compile(r"[" + lexicon.url + r"( ([^]]+))?]"), r"\5"),
'''

this must be done added otherwise '三之丸は比高6メートルほどの' -> '三之丸は比高anumberメートルほどの' and not ['三之丸は比高', 'anumber', 'メートルほどの']

filter function is used as 'anumberメートルほどの' becomes ['', 'anumber', 'メートルほどの']

https://stackoverflow.com/questions/952914/how-to-make-a-flat-list-out-of-list-of-lists

https://stackoverflow.com/questions/30933216/split-by-regex-without-resulting-empty-strings-in-python
'''
extracted_words = [re.split('(anumber)', word) for word in extracted_words] # noqa
extracted_words = list(itertools.chain.from_iterable(extracted_words))
extracted_words = list(filter(None, extracted_words))
'''

get rid of lists in extracted_words

Codecov Report

Merging #23 (84fbcb2) into master (5bf1a61) will increase coverage by 0.24%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   36.62%   36.87%   +0.24%
==========================================
  Files          17       17
  Lines         516      518       +2
==========================================
+ Hits          189      191       +2
  Misses        327      327

Impacted Files
Coverage Δ

mwtext/content_transformers/wikitext2words.py
94.73% <100.00%> (+0.29%)
:arrow_up:

Continue to review full report at Codecov.

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


Add COS audit logging daemonset

/lgtm
We can follow up on the open issues outside this PR.

Thanks @tallclair !
Let me merge this and create issues to track the open questions.

👋 Thank you for publishing this example. It is really helpful. One thing I am stuck on is if it is possible to add personalised auditd rules.
I can see you have set enabled=2 which makes the rules uneditable after load. And I can also see the rules are loading in from /usr/share/cloud/audit which is a read only directory. So I am pretty sure the current stance is no, but I am curious if that is intentional or if you envision a way to feed in personalised rules in the future?
Thanks very much, and I can open an issue if you see fit. For now I thought it was more a question on this specific PR but please let me know if I should open this in a better location.

👋 Thank you for publishing this example. It is really helpful. One thing I am stuck on is if it is possible to add personalised auditd rules.
I can see you have set enabled=2 which makes the rules uneditable after load. And I can also see the rules are loading in from /usr/share/cloud/audit which is a read only directory. So I am pretty sure the current stance is no, but I am curious if that is intentional or if you envision a way to feed in personalised rules in the future?
Thanks very much, and I can open an issue if you see fit. For now I thought it was more a question on this specific PR but please let me know if I should open this in a better location.


Will nullable vectors be supported?

In our index document, we have sections for different entities which we fill in, and some support vector search, and some do not.
I've found that we need to still send an array of zeros for a vector field, even if we're not using it for that entity type.  Seems to waste some effort sending this over the wire, and makes our search document larger than they need to be, in this case.
It would be useful to allow these to be nullable, and handled on the server-side if Cog Search requires converting that null to an empty array or something.
Any plans for this, or is this just by-design for how Collection fields work?

Hi @kirk-marple, thanks for the feedback. We'll add this to our backlog and keep you updated!

Hi @kirk-marple, empty collection of vectors are now supported. However, null vectors are not supported and will throw an error.


Can't complete this Seed

noglitches_normal-open-ganon_vanilla-vt25-quickswap_715572854
There are no more places to look without using glitches (unless I mistakenly marked off somewhere on the map that I didn't check).

 I totally didn't realize I had the Moon Pearl.


pkg/pod: use IncludeMostDirs bitmask instead of constructing it

Functionality didn't change, just cleanup

@rktbot ok to test

lgtm on green


feat/keto-latest-new

All the changes which are present here have been moved to spaces branch and we have upgraded keto to v0.9.


Added exit status and echo command

JIRA: RTOS-156

Description

We want to be able to get exit status of app/applet in psh.
Also somewhat fixed waitpid usage (EINTR and other errors handling)
Motivation and Context

I had no idea how to call new exit status getter applet, so I just implemented echo command along with simulated $? variable
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

[ ] Already covered by automatic testing.
[ ] New test added: (add PR link here).
[x] Tested by hand on: (stm32l4).

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly. (https://github.com/phoenix-rtos/phoenix-rtos-doc/pull/107)
[ ] I have added tests to cover my changes.
[x] All new and existing linter checks and tests passed.
[x] My changes generate no new compilation warnings for any of the targets.

Special treatment

[ ] This PR needs additional PRs to work (list the PRs, preferably in merge-order).
[x] I will merge this PR by myself when appropriate.

@niewim19 248 is equivalent to -8, not -7 (255 is -1, 254 is -2 etc), so ENOEXEC (as expected)

Added draft PR with tests to echo command in psh:

https://github.com/phoenix-rtos/phoenix-rtos-tests/pull/97

One minor bug was found. Currently this test won`t run on our CI for known causes, but locally it fails on printing two consecutive variables:
(psh)% echo $lorem$? ipsum
 ipsum

but
(psh)% echo $?$lorem ipsum
0 ipsum

I think there should be an escape from after $ eating when new $ is encountered
You can use that test on ia32-generic. One test from there is commented out as I need to consult @damianloew  about psh module feature

@niewim19 Fixed


Update README.md

I could also have mentioned that:
System.assert(mySet instanceof Iterable);
fails...

Very interesting find! It actually looks like this is broken for all Iterables (just tried it with a custom implementation)

nvm... it actually does work for custom iterables as expected.


PEAR-1678: Summary modal header button visibility on focus

pear-1678
Screenshots/Screen Recordings (if Appropriate)

I don't see the changes reflecting to the focused state of the button. It only works when the button is hovered over. The focus reaches the button but the border is not visible as asked by the ticket. cc. @alilahrime

I don't see the changes reflecting to the focused state of the button. It only works when the button is hovered over. The focus reaches the button but the border is not visible as asked by the ticket. cc. @alilahrime @cemile-ctds

The focus state indicates keyboard accessibility, highlighting the element currently receiving keyboard input. As Pari mentioned, the hover state style is changing (which we'd prefer not to happen on this ticket; hover state consistency will be addressed in a separate ticket). However, the focus state is still not visible. We need the focus state to match the style of the cohort bar. Please check the attached image for reference.

I don't see the changes reflecting to the focused state of the button. It only works when the button is hovered over. The focus reaches the button but the border is not visible as asked by the ticket. cc. @alilahrime @cemile-ctds

The focus state indicates keyboard accessibility, highlighting the element currently receiving keyboard input. As Pari mentioned, the hover state style is changing (which we'd prefer not to happen on this ticket; hover state consistency will be addressed in a separate ticket). However, the focus state is still not visible. We need the focus state to match the style of the cohort bar. Please check the attached image for reference.

I understand, removed the hover style changes. this is what it looks like on focus now. is this good?

I understand, removed the hover style changes. this is what it looks like on focus now. is this good?
This looks good @alilahrime Could you also add this style to [X] close button?

I've reviewed other summary pages (project, gene, mutation, case, file). Additionally, the focus style should be incorporated into the Project and File summary page headers.
Project: http://localhost:3000/v2/projects/TCGA-BRCA
File: http://localhost:3000/v2/files/76a0fe52-63a8-4d15-b7e8-d1e4baddce49

@alilahrime  -- pari/cemile are investigating some alternative solutions rq. please hold on further changes to this PR until they finish the investigation.

This has been put in this PR: https://github.com/NCI-GDC/gdc-frontend-framework/pull/908


Add dotnet-sdk to Dependabot

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.625%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
3490

Relevant Lines:
3726

💛  - Coveralls


Add _missing_ to make FileFormat case insensitive

This pull request makes the following changes:

Fixes issue #1340 *

The change is to make FileFormat case insensitve. The idea is to add _missing_ funtion to handle lower case in a pythonic way.
Also included corresponding test at tests/test_manifest.py.

Hey @kevinjqliu @Fokko, this PR is ready for review. Rather than modifying the __new__ method, I think it's probably a better option to modify _missing_ based on its semantic meaning. Please let me know if there is more change you would like me to make. Thanks!


feat: replace sequential jobs with concurrent jobs

Restricting the job concurrency by architecture scales better than only running the jobs sequentially.
Requires #56.

This will work when layered on top of #60 really well, I assume.

Absolutely.  This, plus the other design changes.
I've been building all 15 of the supported architectures in parallel with minimal impact on overall build time vs. just arm.  Before I reworked the design it took 1 hour 15 minutes, now it's about 10 minutes with cache and 14 minutes without.


Radar is lagged

I have a question, why radar looks lagged? You can see how it is lagged on this video https://www.youtube.com/watch?v=xxlfB91jy2A&t=5839s

In the video it looks like it's not just the radar, but the entire HUD that's lagging, so I'll assume this is a duplicate of #125.
As a workaround, try limiting the game's FPS (e.g. by typing fps_max 60 in the in-game console).


Cannot use a scalar value as an array in ... on line 44

Describe the bug
Hello everyone! :)
Basically, I have two errors as below:
Błąd 1: Cannot use a scalar value as an array in ... on line 44
Błąd 2: Trying to access array offset on value of type int in ... on line 45
full error line from log:
2023/05/19 21:40:27 [error] 29071#29071: *112960 FastCGI sent in stderr: "s3-banner.php on line 45PHP message: PHP Warning:  Cannot use a scalar value as an array in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 44PHP message: PHP Notice:  Trying to access array offset on value of type int in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  in_array() expects parameter 2 to be array, null given in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  Cannot use a scalar value as an array in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 44PHP message: PHP Notice:  Trying to access array offset on value of type int in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  in_array() expects parameter 2 to be array, null given in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  Cannot use a scalar value as an array in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 44PHP message: PHP Notice:  Trying to access array offset on value of type int in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  in_array() expects parameter 2 to be array, null given in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  Cannot use a scalar value as an array in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 44PHP message: PHP Notice:  Trying to access array offset on value of type int in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  in_array() expects parameter 2 to be array, null given in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.php on line 45PHP message: PHP Warning:  Cannot use a scalar value as an array in /var/www/status.xxx.pl/public_html/ts3-banner/ts3-banner.p
To Reproduce
Steps to reproduce the behavior:
The error appears if it's opened by the TeamSpeak client. To open it via Firefox it works without issues
Expected behavior
Has anyone had the same problem? Any thoughts or suggestions?
Desktop (please complete the following information):

OS: Windows 11
Browser Firefox
Version 113.0.1
TeamSpeak 3.5.6

Server (please complete the following information):

OS: Debian
Version 9
PHP 7.4

Hey @etobod
It looks like you are using the experimental version. Did you tried to use the newest version? https://github.com/dennisabrams/teamspeak3-banner/releases/tag/v1.0.5


Qus: Does envoy support connecting to upstream Redis with TLS enabled?

Title: Qus: Does envoy support connecting to upstream Redis with TLS enabled?
Description:

I want to use envoy as a front proxy to my Elasticache Redis instance which has TLS enabled. I use the RedisProxy Listener filter and forward the traffic to a cluster identifying my Redis instance. However the connection fails, most likely because the Redis instance requires a TLS connection. If this is supported, I would appreciate if someone can share a simple envoy configuration yaml to achieve this.

Alternatively, can the RedisProxy be configured in such a way that it allows for TLS passthrough i.e. the TLS handshake is handled between the redis client and the redis server and envoy just acts as a passthrough proxy, but still taking care of things such as handle (Clustered) Redis redirects (MOVED)?
Regards
Ani

cced Redis related owners
@msukalski @henryyyang @weisisea

I haven't tried it myself. But it seems feasible to configure Envoy for upstream TLS connections:
https://github.com/salrashid123/envoy_redis/blob/main/README.md
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl


Use type instead of name

fix #266
This should display production for the production environment
Steps to test

Get this PR
Run npm i & npm link
Test it on an app, ex 647

I think there might have been some confusion because of how these fields are named in the API. It looks like the env.name is the client_site_id.name and the env.type is the client_site_id.environment_name. I would have expected the env.name to  be client_site_id.environment_name.

Ya it is confusing - what you say is right @joshbetz - each environment has a Type (production, staging, develop, etc), then an optional Name for disambiguation if there are multiple environments of a given type.
Then an App has a Name (not a Type), which is client_site.name.

Do we move this to the API level. Do we know if we are going to break something if we change that on the API level?

I've added some code to make the env picker work on sites that have multiple environments of a given type, which would have stopped working when switching to type over name.
Now, when there are multiple environments of a given type, they should be specified with --env=develop.dev-01, rather than --env=dev-01.

Looks good to me too 👍


GH-292: Bump warp to 0.3.5

Resolves GH-292

"Update doesn't seem to break anything" is probably the best comment I've ever gotten!


RFC4180Iterator and invalid field

Feature Request

Q
A

New Feature
yes

BC Break
no

Proposal
the new RFC4180Iterator which is a userland CSV parser that try to conform to the informal RFC4180 spec. has landed on the master branch see issue #309 . But a last issue has pop up in how it should handle invalid record field. An invalid field is:

a field containing the enclosure character while not being enclosed.
a field containing the enclosure character not double while being enclosed.

Currently in both case the parser goes through without issuing any warning.
Should the parser silently continue this behavior (and thus, we should clearly document it) or should it trigger an Exception instead ?  @theodorejb  what do you think ?

We could keep the current parser behavior if we follow the Robustness principle,

Be liberal in what you accept, and strict in what you produce

As long as we document this behavior. What do you think ?

After some digging I've managed to reproduce fgetcsv behavior using my code so once I've commit my changes this issue will be resolved.


Automatically copy *.sql files to output directory

The idea of this is that when implementing a task, MSBuild will copy the .sql files into the yesql folder of the output directory and in that directory it will search for the YeSqlLoader.Load method.

The package was published here: https://www.nuget.org/packages/YeSql.Net.Properties


CI check misses obsolete MF terms with links to CHEBI participants

This problem results in downstream pipeline failures, e.g.: https://github.com/geneontology/go-ontology/issues/25338
The main issue is that the MF participants file has not been merged in prior to running SPARQL checks: https://github.com/geneontology/go-ontology/blob/ef12560160c7fb39d72a73816d177dffb1ccbaf5/src/ontology/Makefile#L92-L93
This is easy to fix but would trigger downloading of the Rhea RDF dataset on every pull request. That would add a network dependency, also could sometimes result in surprise failures in unrelated PRs after Rhea updates their file.
As part of fixing this I will instead add a cached version of the dataset into this repo, which will be updated in its own automated PRs.

Similar issue with regard to malformed taxon constraints TSV. The taxon constraints import should not be automatically rebuilt as a dependency of ontology products; leads to unexpected build failures which should be caught in a separate PR rebuilding the taxon constraints import.

Fixed.


Bumps frameworks to latest

chore: bump

Bumps open-aea to ==1.53.0
Bumps open-aea-ledger-ethereum to ==1.53.0
Bumps open-aea-ledger-ethereum-flashbots to ==1.53.0
Bumps open-aea-ledger-ethereum-hwi to ==1.53.0
Bumps open-aea-ledger-cosmos to ==1.53.0
Bumps open-aea-ledger-solana to ==1.53.0
Bumps open-aea-cli-ipfs to ==1.53.0
Bumps open-autonomy to ==0.14.14.post2
Bumps open-aea-test-autonomy to ==0.14.14.post2

Tested with Docker 25, 26, 27


Missing CONTRIBUTING.md leading to 404 page

Environment details

OS: NA
.NET version: NA
gax version: NA

Steps to reproduce

Click on CONTRIBUTING hyperlink on README.md file
404 page appears

Code causing issue:
See the
[CONTRIBUTING](https://github.com/googleapis/gax-dotnet/blob/master/CONTRIBUTING)
documentation for more information on how to get **started.**

Thanks - for the moment I'll just remove this from the readme. (We do welcome contributions, but we don't particularly expect them for this project - it's more internal support for other client libraries.)


Specify simple commutation relationships between gates

For example this could be useful when inserting CZs, because it would allow later CZs to pass over earlier CZs and find a better spot in the circuit.

What about doing this dynamically for KnownMatrixGates? Maybe use some sort of cache to avoid redoing the same check over and over. The only alternative I see is enumerating a set of gates that each gate is known to commute with, but that seems messy.

We now have the _commutes_ protocol for this, thought it has problems.
The fundamental problem is that objects that directly implement it need to know the set of other gates that it can act on.  Without the notion of "belong to these gates which form a group" this ends up being a rather bad blowup.
Closing this issue since we have a protocol, but think we should think about how this should work for sets of gates that form a group (Pauli, Clifford) and not just generators of a group.


gafana get telemetry data from influxdb error:influxDB:Bad Request

gafana get telemetry data from influxdb error:influxDB:Bad Request
SO influxdb username and password is?   Could you tell me!

To ease the usage of the reference tools, there is no need to add the datasource and create dashboard in Grafana. We have provided the pre-configured automated dashboards for both InfluxDB as well as prometheus to visualize the telemetry data. Details are in the whitepaper and YouTube video at below links:
https://dl.dell.com/content/manual3687441-idrac9-telemetry-reference-tools-data-visualization.pdf?language=en-us
https://www.youtube.com/watch?v=EBpBKBEidq8
Other than pre-configured automated dashboards, new configuration could be done by adding the datasources and the resolution for the above 'InfluxDB Error: Bad Request' error is with User:admin and Password:'token shown by DOCKER_INFLUXDB_INIT_ADMIN_TOKEN'
cat iDRAC-Telemetry-Reference-Tools/.env
USER_ID=2005
GROUP_ID=2005
DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=5fcb190e-f129-4430-8a2f-28d6e0bf8165
...

If the above works for you, this ticket could be closed.

I try this  but this error again,could you help my teams or email is<EMAIL_ADDRESS>

Had a call with @huazhou007 and provided pointers. Datasource got added successfully (using DOCKER_INFLUXDB_INIT_ADMIN_TOKEN) and 3 buckets seen, above issue with datsource is resolved. But there is no data in the dashboards because time of idrac is not in sync with time of the reference tools. idrac time future somewhere around 19:05 and docker tools ~2pm. Time needs to be fixed to see the data in the automated dashboards/configured dashboards.

I chat with @huazhou007 and helped with seeing the data in automated dashboards (powermetrics) and also add the influxdb in the grafana datasource, successfully added 3 buckets. This ticket can be closed and open others if stuck with any other issue.

@SailM23    You are very patience，Thanks a lot!


Added to_i32 and to_u32 methods to f32x8 type

The f32x8 type doesn't provide a to_i32 and to_u32 methods which seems inconsistent since f32x4 has them and so also f64x2 and f64x4 provide the 64bit version of those methods. So I assumed that this has just been overlooked and would like to add them with this pull request.
I haven't seen any tests for those types of conversion methods inside the crate. I therefore ran my tests by using simd from another crate. If you think that tests for those methods should be added than please let me know and I'll update this pull request.

@burntsushi any gotchas to worry about here? Seems okay to me.

@sfackler LGTM. (I don't have merge powers.)

(I think the only gotcha would be for the reverse direction: casting an int to a float. AFAIK, such a conversion should be labeled unsafe...)


services.yaml

Hi,
Thank for the good and very useful work you did. it works fine.
I have a little request : We probably have all this warning at Hommeassistant boot
Logger: homeassistant.helpers.service
Source: helpers/service.py:548
First occurred: 13:50:13 (3 occurrences)
Last logged: 13:50:13
Unable to find services.yaml for the securitas integration
Is it possible to create a dumb services.yaml file so that the warnin will end to raise up?
Rgds.

You just need to create an empty file services.yaml in

Thanks it works.


Type error in @synthetixio/synpress/commands/puppeteer.js l.100

Hello,
First, congrats for this great project. By trying to increase puppeteer's timeout for confirming transactions, I found what seems like a type error in file /commands/puppeteer.js line 101:
https://github.com/Synthetixio/synpress/blob/debf2c6b635bb40bfc822165707ee1b8c8224c3b/commands/puppeteer.js#L101
The problem comes from the fact that page.waitForFunction does not take a visible parameter, but only timeout and polling (https://puppeteer.github.io/puppeteer/docs/puppeteer.page.waitforfunction/#parameters). It could be useful to either remove it, or use this function to pass a parameter to set puppeteer's timeout when confirming Metamask transactions. To do so, (which I originally came for), I simply replaced this line as follows, and it worked perfectly:
await page.waitForFunction(
      `document.querySelector('${selector}') && document.querySelector('${selector}').clientHeight != 0`,
-      { visible: true },
+      { timeout: 120000 }
    );

I've set the timeout to 120000ms arbitrarily, but it could come from an option in the synpress.json config. Let me know if that makes sense to open a PR on that.
Thanks!

Hey, this is old and probably not relevant to latest synpress version (it's .js config now, not .json). If this issue still persists, please re-open. Thanks!


AppSpec doesn't support domain or domains attribute, even though Terraform provider does

https://github.com/digitalocean/terraform-provider-digitalocean/blob/v2.5.1/digitalocean/app_spec.go#L27-L39
The deprecation warning is written out, but there's no support for either of these attributes.

Great find @rdjogo
The issue here is that when we have a set or a list, we pluralise the name so domain -> domains which clashes with domains
So I need to map domain -> domainNames that would allow you to set them as expected
I'll have this fixed up and re-released tomorrow
Paul

Awesome, thanks a lot @stack72 !


Do we need a "UnitTable" component?

The clld data model distinguishes two kinds of "measurements" or "values":

measurements of properties of a language
measurements of properties of a unit of a language

The latter was introduced to cover cases like constructions, or paradigms. But it could also be used to model things like allophones (see https://github.com/cldf/cldf/issues/93#issuecomment-765235046). Now we already have components modeling particular units of language, namely FormTable and ExampleTable. So the question is: Would a generic UnitTable make sense - or should we add more specific components, modeling specific units, when the need arises?

Thinking a bit more, I'm retracting the proposal. One design principle of CLDF was to only add things that have clear use cases in analysis - rather than aiming at some sort of "completeness". Judging from the clld experience, "units" will probably end up as a catch-all category, making automated re-use almost impossible.

Thinking a bit more, I'm retracting the proposal. One design principle of CLDF was to only add things that have clear use cases in analysis - rather than aiming at some sort of "completeness". Judging from the clld experience, "units" will probably end up as a catch-all category, making automated re-use almost impossible.


Map tipee activities to taxi ones

Todo :

[ ] Fetch activities from the API in get_projects to create taxi activities (using the "external ID" as activity ID ?)
[ ] Call the API to bind activities with timesheet entries in post_push_entries.

Only available in private API...


test: improve test coverage

Nx Cloud Report
CI is running for commit 09a8c98e829ca848cb4f745a76fd6764d046d473.
📂 Click to track the progress, see the status, the terminal output, and the build insights.

Sent with 💌 from NxCloud.


Saving Notebook defaults to txt

Insiders/main

@MaddyDev @chlafreniere FYI

I'm guessing this is related to https://github.com/microsoft/vscode/pull/102100/files. This also affects query editor on my machine btw, @anthonydresser

This is actually a regression in vs code too - issue submitted
https://github.com/microsoft/vscode/issues/103704
It'd be fairly easy to fix ourselves if needed - but I think we should wait and see if they get back to this quickly.

Fixed in release/1.21


v2 create_database (nonbreaking, with backwards compatible deprecation)

Implement v2 create_database(), which drops the requirement to pass in an engine:
julia> ctx = Context(load_config())
Context("us-east", "https", "azure.relationalai.com", "443", ClientCredentials("HZON00cfTWiDZBdQkU627DpJfTPOAgjM", "OkZaHX-YuLepzV4QkCQcKjVPZI1fz3AraCBCaNvNZULcxY6Jk6pZZkzZBBhkN0AR", nothing, nothing), "https://azure.relationalai.com")

julia> create_database(ctx, "mytestdb")
JSON3.Object{Vector{UInt8}, Vector{UInt64}} with 1 entry:
  :database => {…

julia> show(ans)
{
   "database": {
                  "account_name": "relationalai-team-rd-flex",
                          "name": "mytestdb",
                            "id": "494db1da-aaa6-a08d-81ae-a585abdecf56",
                         "state": "CREATED",
                        "region": "us-east",
                    "created_on": "2022-08-09T19:02:08.147Z",
                    "created_by": "HZON00cfTWiDZBdQkU627DpJfTPOAgjM@clients"
               }
}

(i really hate the way JSON objects display in julia)
But maintain backwards compatibility with the old function call, and display a DEPRECATION warning:
julia> create_database(ctx, "mytestdb", "dba-playground", overwrite=true)
┌ Warning: DEPRECATED: Passing an `engine` is no longer required for creating a database. This will be removed in a future release. Please update your call to `create_database(ctx, name)`.
└ @ RAI ~/work/rai-sdk-julia/src/api.jl:399
┌ Warning: DEPRECATED: The `overwrite` option is no longer supported for creating a database. This will be removed in a future release. Please delete an existing database before attempting to create it.
└ @ RAI ~/work/rai-sdk-julia/src/api.jl:404
JSON3.Object{Vector{UInt8}, Vector{UInt64}} with 7 entries:
  :output       => Union{}[]
  :problems     => Union{}[]
  :actions      => Union{}[]
  :debug_level  => 0
  :aborted      => false
  :type         => "TransactionResult"
  :abort_reason => nothing

The new return format is different than the old return format, but as long as you call through the old API (by passing an engine) you will still get the old return format for now.
The next release can be a breaking release that drops support for the old API call.
Fixes https://github.com/RelationalAI/rai-sdk-julia/issues/57.

Tests seem to be failing because of the @warning

Tests seem to be failing because of the @warning

Thanks david, you were right. It turns out trailing \ to break up a string was added only in julia 1.7! 😮 thanks!


Create Rules dont accept uppercase in zone_ip, destination IP and service

We create object with uppercase and when we use create_security_rule we obtains error from pandevice.policies
[2018-03-13 16:52:37,596] {#flaskit/resource.py:232} 100a688b ERROR -  datacenter -> pre-rulebase -> security -> rules -> Test1 -> source
'['PHMBUPIAPIA']' is not an allowed keyword
datacenter -> pre-rulebase -> security -> rules -> Test1 -> source ['PHMBUPIAPIA'] is an invalid ipv4/v6 address
datacenter -> pre-rulebase -> security -> rules -> Test1 -> source '['PHMBUPIAPIA']' is not a valid reference
datacenter -> pre-rulebase -> security -> rules -> Test1 -> source ['PHMBUPIAPIA'] range separator('-') not found
datacenter -> pre-rulebase -> security -> rules -> Test1 -> source is invalid
Traceback (most recent call last):

Hello, can you share the code that leads to this error?

    source_ip = ["DHMBUPIAPIA"] # Dyn Adress group
    destination_ip = ["PHMBUPIAPIA"] # Dyn adress group
    service = ["TCP_8443"]
    rulebase = apiPano.get_rulebase(destinationDeviceGroup)
    new_rule = apiPano.create_security_rule(
                rule_name=ref,
                description="Defined by API",
                tags=None,
                source_zone=["any"],
                source_ip=source_ip,
                source_user=None,
                destination_zone=["any"],
                destination_ip=destination_ip,
                category=None,
                application=["any"],
                service=service,
                hip_profiles=None,
                group_profile=None,
                antivirus=None,
                vulnerability=None,
                spyware=None,
                url_filtering=None,
                file_blocking=None,
                data_filtering=None,
                wildfire_analysis=None,
                log_start=None,
                log_end=None,
                action="allow",
                rule_type=None,
                log_setting="default")
    apiPano.add_rule(rulebase, new_rule)

Are you sure you're on the right repo?  This pandevice library for python doesn't have any methods called get_rulebase() or create_security_rule().  What library are you using?  Are you trying to use Ansible?

yes it's my fonction :
def create_security_rule(self, **kwargs):
"""Create Security rules."""
security_rule = policies.SecurityRule(
name=kwargs['rule_name'],
description=kwargs['description'],
fromzone=kwargs['source_zone'],
source=kwargs['source_ip'],
source_user=kwargs['source_user'],
hip_profiles=kwargs['hip_profiles'],
tozone=kwargs['destination_zone'],
destination=kwargs['destination_ip'],
application=kwargs['application'],
service=kwargs['service'],
category=kwargs['category'],
log_start=kwargs['log_start'],
log_end=kwargs['log_end'],
action=kwargs['action'],
type=kwargs['rule_type']
)

I see.  The errors you're getting are coming from the Panorama which typically means the configuration you're trying to make is not valid.  pandevice doesn't check configuration for validity, it leaves that up to the firewall/Panorama.  This error stand out to me:
'['PHMBUPIAPIA']' is not an allowed keyword
The reference here is a string containing your array syntax.  So while the reference should be 'PHMBUPIAPIA' it is instead arriving at the Panorama as '['PHMBUPIAPIA']'.  This means that somewhere in your code you are likely causing the array to be treated as a string instead of an array.  Since I don't have the full code its hard to say where this might be happening.  I tested the portions you gave me and it worked fine, so there must be some other code that is causing the problem.
Hope that helps you track down the source of the problem.

Thanks I ll check
Le 14 mars 2018 22:20, "Brian Torres-Gil"<EMAIL_ADDRESS>a
écrit :

I see. The errors you're getting are coming from the Panorama which
typically means the configuration you're trying to make is not valid.
pandevice doesn't check configuration for validity, it leaves that up to
the firewall/Panorama. This error stand out to me:
'['PHMBUPIAPIA']' is not an allowed keyword
The reference here is a string containing your array syntax. So while the
reference should be 'PHMBUPIAPIA' it is instead arriving at the Panorama
as '['PHMBUPIAPIA']'. This means that somewhere in your code you are
likely causing the array to be treated as a string instead of an array.
Since I don't have the full code its hard to say where this might be
happening. I tested the portions you gave me and it worked fine, so there
must be some other code that is causing the problem.
Hope that helps you track down the source of the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PaloAltoNetworks/pandevice/issues/110#issuecomment-373178631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApnPKgS-x743BuEtgJczHsha8X_UZGRks5teYmOgaJpZM4SqDPu
.

The problem is corrected !

Wonderful!  Very glad to hear it's working.


Building separate Stylesheets for different themes with webpack

Right now we are using a scss mixin ( https://github.com/zellwk/themify ) to provide different themes for our react components in our app.
It works great, but produces rather long selector chains in the compiled css file.
While we do have to provide the ability to change themes during runtime ( which is no hassle with the current solution, we only have to switch one classname on the body element ) the default usecase is, that the theme does not change.
So we thought about reducing the complexity and filesize of our stylesheets by splitting them up in separate files.
Example:
themes.scss:
$themes: (
  red: (
    mainColor: #aa3939,
    secondaryColor: #D46A6A
  ),
  blue: (
    mainColor: #2e4272,
    secondaryColor: #4f628e
  )
);

button.sccs
@import 'themes.scss';

.button {
  @include themify($themes) {
    color: themed('secondaryColor');
    background-color: themed('mainColor');
  }}
}

This becomes:
.theme-red .button {
  color: #D46A6A;
  background-color: #aa3939;
}

.theme-blue .button {
  color: #4f628e;
  background-color: #2e4272;
}

Now I want this to become:
theme-red.css:
.button {
  color: #D46A6A;
  background-color: #aa3939;
}

theme-blue.css:
.button {
  color: #4f628e;
  background-color: #2e4272;
}

We are not depenent on the themify mixin, we could change that to any kind of solution one could make work with webpack. Any hint in the right direction would be appreciated! :)

CSS Custom Properties (CSS Variables) && postcss-custom-properties


API within to limit the area on the current browser where the intended operation can be performed

Proposed behavior
API within to limit the area on the current browser where the intended operation can be performed
Current behavior
Proximity selectors are available to specify where to look for to find a given element.Sometimes these are not enough.
Example:
I want to verify that a text  failing step is w.r.t Failing Scenario and not passing Step.

Proximity selectors like near also need not work always as the passing Step may be near to Failing Scenario but not within it.
Expected behavior
Within API should ensure that the element is within/not the given boundary.

Even within may not be helpful in this context as Failing scenario is a separate div and Failing step is not within it actually. Combination of proximity selector should actually work, like await text("passing step", near("Failing scenario"), below("failing scenario")).exists() but there seems to be a bug in using combination of proximity selectors.
As await text("passing step", near("Failing scenario")).exists() gives Does not exists whereas await text("passing step", near("Failing scenario"), below("failing scenario")).exists() gives Exists it should actually be intersection of proximity selectors if even one does not match should say Does not exists

Even if the combination of selectors work after the bug fix, within API is more simple
eg:- text("passing step", within("Failing scenario") is more clean than await text("passing step", near("Failing scenario"), below("failing scenario")).exists()
Furthermore, this is useful in cases where something like passing step may be close to qualify for near and below the Failing scenario however not within it.

Yes, the text Failing scenario is in a different div however text("passing step", within($('.scenario-container .failed')) should not give Exists as the div contains the "failing step" and not the passing step
So, even if the combination of selectors work after the bug fix, within API is more simple
eg:- text("passing step", within($('.scenario-container .failed')) is more clean than await text("passing step", near("Failing scenario"), below("failing scenario")).exists()
Furthermore, this is useful in cases where something like passing step may be close to qualify for near and below the Failing scenario however not within it.

So, even if the combination of selectors work after the bug fix, within API is more simple
eg:- text("passing step", within($('.scenario-container .failed')) is more clean than await text("passing step", near("Failing scenario"), below("failing scenario")).exists()

The downside is that the API is useful only with a selector which means flakiness.
It is Ok to be expressive using existing proximity selectors.


Autonomous Exploration Maps

Hello,
In the autonomous exploration, the simulated robot autonomously explores environments and generates a noisy map. How can I save the generated noisy global maps as images?
Thank you in advance.

Hi, I added the save figure part. Please uncomment it and try it out.
# fig_map.savefig("test.png")

Thank you so much for your prompt reply.
However, I meant saving the explored maps after running the trained environment "robot_exploration_v0.py".

Sorry, it is currently not available to save the explored maps after
running the trained model. However, you can save it by yourself by calling
"
img = sim.get_state()
cv2.imwrite("map.png", img)
"
On Tue, May 5, 2020 at 11:04 PM RemaDaher<EMAIL_ADDRESS>wrote:

Thank you so much for your prompt reply.
However, I meant saving the explored maps after running the trained
environment "robot_exploration_v0.py".
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/TeaganLi/HouseExpo/issues/2#issuecomment-624109803,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG2Q6FY4NA73JNSFLBWN7UTRQATGJANCNFSM4MZMCFXA
.

--
LI, TingguangPh.D. candidate in EE,
CUHK(852)56034944http://www.ee.cuhk.edu.hk/~tgli/
http://www.ee.cuhk.edu.hk/~tgli/Ho Sin-Hang Engineering Bldg 424, the
Chinese University of Hong Kong, Shatin, New Territories, Hong Kong


Added autoload section to autoload simple_php_captcha.php

Without that change, you have to manually include simple-php-captcha.php in your script.
With that change, just use "vendor/autoload.php" and it will be included automatically.

I normally don't bother with autoloading unless I'm working with an actual class, but this seems like a harmless and likely helpful change. Thanks.

I was just wondering, why your function wasn't usable until i figured out, that simple-php-captcha.php wasn't included by default. But thanks for merging :)

@claviska can you please tag a new release which includes this feature and add it to packagist so autoload is working on the version on https://packagist.org/packages/abeautifulsite/simple-php-captcha?
Thanks

Done.


"Cannot match any routes" after page refresh

I got "Cannot match any routes" after page refresh in my appliaction.
Without localize-router everything work fine.
With: LocalizeRouterModule.forRoot(appRoutes) in my app.module.ts I got an error in the browser.
"@angular/cli": "1.0.0-beta.31"
"@angular/compiler-cli": ">=4.0.0-beta <5.0.0"
"@angular/common": ">=4.0.0-beta <5.0.0"
"@angular/compiler": ">=4.0.0-beta <5.0.0"
"@angular/core": ">=4.0.0-beta <5.0.0"
"@angular/http": ">=4.0.0-beta <5.0.0"
"@angular/platform-browser": ">=4.0.0-beta <5.0.0"
"@angular/platform-browser-dynamic": ">=4.0.0-beta <5.0.0"
"@angular/router": ">=4.0.0-beta <5.0.0"
"ng2-translate": "5.0.0"
"localize-router": "0.6.2"

Can you provide more information:

what route are you loading?
how does your appRoutes look like?
if possible provide link to your repo

Thanks

@meeroslav It's part of enterprise project, so it's not available online.
My appRoutes is simple:
export const appRoutes: Routes = [
  {
    path: '',
    component: DashboardComponent
  },
  {
    path: 'admin',
    children: [
      {
        path: 'active-sessions',
        component: AdminActiveSessionsComponent
      }
    ]
  }
];

Load homepage
Go to admin/active-sessions
Refresh the page (F5)
Error

Well,  admin/active-sessions  should be invalid.
Once localize-router kicks in, proper URL should be e.g. en/admin/active-sessions so the message you get is correct.
Do you navigate through the application to the given route or you modify the browser URL manually?
Former would be a bug in localize-router while later would be expected behavior.
Please note that there is possibility to add flag to exclude certain routes from the localization process, but it's not yet implemented.

@meeroslav Sure, it's en/admin/active-sessions. I skipped this for clarity.
I navigate through the application. I just refresh the page by pressing F5.

@mrzepinski This would notmaly happen if you would be using lazy loaded routes (#3). If this is not the case, then I will investigate it as soon as possible.

@meeroslav It's not this case. I'm not using lazy loaded routes.

@mrzepinski Could you provide the navigation link as well?

This is caused by router version 3.4.8. Seems that navigation kicks in before APP_INITIALIZER finishes.

Yeah, looked into the changes (https://github.com/angular/angular/compare/2.4.7...2.4.8).
Looks like the process changed. They added a LOCATION_INITIALIZED which might help

This will break the backwards compatibility unfortunately, not to mention 4.x.x versions.
I need to investigate more to find proper solution.

Issue mentioned in https://github.com/angular/angular/issues/14615

Workaround for version 2.4.8. can be found here: https://github.com/angular/angular/issues/14588.
Proper solution will be done soon.

Any update on this?

Resolved with Angular version 2.4.9

Nice.
Any plans to support the new process that is used in Angular 4? There will apparently be a legacy option that makes it work like in 2.x but you can't use that with Universal.

@meeroslav
When are we going to have a new version supporting Angular 2.4.9?

The new version should be there in few days, I'm working on tests.
In the meantime, if you don't mind npm complaining, version 0.6.4 is fully functional with Angular Core 2.4.9 (and Angular Router 3.4.9).

@meeroslav
What about Angular 4.0.0 support?

On it. Sorry for waiting.

Version 0.7.0 supports Angular 4

I'm also having an issue like this on the new version of localize-router with a lazy module but steps to reproduce are quite different.
App routes :
const routes: Routes = [
  {
    path: 'user',
    loadChildren: 'app/auth/auth.module#AuthModule'
  }
];

Auth routes :
const routes: Routes = [
  {
    path: '',
    component: AuthComponent,
  },
  {
    path : 'login',
    component: LoginComponent,
  },
  {
    path: 'subscription',
    component: SubscriptionComponent
  }
];

When I enter "http://localhost:4200/en/user/subscription" or "http://localhost:4200/en/user/" directly in browser, there is no problem, components are correctly lazy loaded.

With "http://localhost:4200/fr/utilisateur" it works great

But with "http://localhost:4200/fr/utilisateur/inscription" I've got this error Cannot match any routes. URL Segment: 'fr/utilisateur/inscription'

I have another problem with this configuration when I put my links directly in the "app.component.html" file.

This works : {{ 'Login' | translate }}
This needs two clicks on link : {{ 'Subscription' | translate }} (First click throw this error Cannot match any routes. URL Segment: 'fr/utilisateur/inscription' and second click works)


Fix issue when specifying dse.yaml settings

A leftover from https://github.com/datastax/cstar_perf/pull/238
Specifying any settings in the dse.yaml field would fail with
[node1] put: <file obj> -> $HOME/fab/dse/resources/dse/conf/dse.yaml

Fatal error: put() encountered an exception while uploading '<StringIO.StringIO instance at 0x7ff468ddffc8>'

Underlying exception:
    No such file

because $HOST needs to be replaced

+1


Datetimepicker popup doesn't open

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[ ] I am running the latest version
[x] I checked the documentation and found no answer
[ ] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior
Please describe the behavior you are expecting
Current Behavior
What is the current behavior?
Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

step 1
step 2
you get it...

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Device:
Operating System:
Browser and Version:

Failure Logs
Please include any relevant log snippets or files here.

The problem is that this type of element is supported by the pro version of the template. If you compare the version of the datepicker script used in the pro version, with the original version, you will notice that there are some changes in the script. In fact, importing the pro version script instead of the original one (only the datetime picker), works.
This is because some styles of the datetimepicker have been modified that do not allow them to be viewed except with the modified script.


feat: update observability operator to v3.0.15

Description
Update Observability Operator to v3.0.15 to support GCP and allow the operand pods to be moved to other nodes to improve dynamic scaling.
Verification Steps

Run KFM and terraform an OSD cluster
Make sure the observability namespace is populated
Grab the cluster_id from the Observability resource status and query stage Observatorium for it
Make sure metrics are received from the cluster

@vmanley please take a lookg

LGTM

We’ll need to also bump the version in app-interface.
On Fri 16 Sep 2022 at 14:29, Peter Braun @.***> wrote:

Merged #1311
https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/pull/1311
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/pull/1311#event-7402825976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNDNKHE7PQFNFCNSMXBLX3V6RR2RANCNFSM6AAAAAAQOG5N7Q
.
You are receiving this because your review was requested.Message ID:
<bf2fc6cc711aee1a0c2a/kas-fleet-manager/pull/1311/issue_event/7402825976@
github.com>

--
Chitimbo Manyanda.


the current release lacks the actual files needed to import it

the actual detail issue is that setup.cfg was used incorrectly
also if possible avoid pbr, outside of openstack its just a massive broken pain

Looks like it was just the wheel, so I pulled that from pypi. The pbr opinions are unwelcome: critical opinions without constructive options are useless, keep them to yourself.


[Storage] start_storage_service waits for server to start listening

Motivation
In the tests we query storage with a client immediately after calling this function. Sometimes the server does not seem to be available by the time the client calls. The reason seems to be that the server creation is async and the function might return before the server starts listening.
As a workaround, try to connect to the server a couple of times in this function. Panic if the server fails to respond in a few seconds.
Have you read the Contributing Guidelines on pull requests?
No.
Test Plan
Currently running unit tests repeatedly in a loop on my machine.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra r=msmouse

:pushpin: Commit 626819f has been approved by msmouse

:hourglass: Testing commit 626819fa5f216449a09f9a42396cea8e51f45e81 with merge 4c1079c485622a88e0149309d913199901aec566...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: msmouse
Pushing 4c1079c485622a88e0149309d913199901aec566 to master...


fixed bug where args were unused

Hello, I was trying to use this but found a bug where the arguments from command line weren't being used.
Upon investigation, I realized it got removed somewhere along the merges. I reinstated it, with some modification so that the local website is also updated.

This PR was needed!


Implement contextual drawers and move CanvasItem tools to them

Part of https://github.com/godotengine/godot-proposals/issues/3550. Closes https://github.com/godotengine/godot-proposals/issues/3559.
This PR implements the main design for contextual drawers, which should replace contextual toolbars for various viewport tools. I've decided to do this work in parts, so it's easier to review and test, and doesn't require me to rebase too often while we wait for that. I propose we test it out on the couple of CanvasItem related tools, and then continue porting the rest of the toolbars to the new system. As such, this PR does not close the main proposal yet.

So, we are replacing these

with THIS:

Don't worry if they look massive comparatively! Check the videos below that show them in action in a more realistic way.
The core systems are as described in the proposal, but I've also implemented some suggestions that were described there. When the appropriate nodes are selected, the buttons appear in the right side of the viewport. These buttons correspond to one of the tool drawers. You can click on each one of them to open the one you need, or you can click the button at the top to toggle all of them at once. There is also a hot key for that (M by default, for not particular reason).
Buttons are styled in such a way that they should be readable regardless of the background color of the viewport. Their labels (only visible while no drawer is open), should strike the balance between informative yet not too intrusive. Drawers can have subsections for visual clarity, and the entire panel scrolls when it doesn't fit the screen. (Though, at this point I'd suggest closing some of the drawers you do not need).
If you switch away from a node with a drawer open and then switch back, the drawer will be immediately visible. This should help users to keep the workflow going. If you switch to another node that supports the same tools, the drawer will, of course, remain open.
https://user-images.githubusercontent.com/11782833/144729386-5579493f-b7de-468b-b8d0-ecd4e6813b37.mp4
Drawers themselves have been redesigned from their horizontal counterparts to better use the new format. There is more verbosity and explanations. Anchoring system has been completely redone to solve a huge usability pain from the current version. It also matches other tools that way, so should provide a clearer migration path for some users. However, overall, the usability of these tools was not the main goal here, even though I've tried to improve upon it given the opportunity.
As promised, I've also added an editor setting to have the drawers always visible, just like toolbars were. But this time they are visible over the viewport and can be nicely scrolled. This may be an interesting approach for people with bigger displays:

But it probably won't be the preference for people with smaller amount of the screen space:
https://user-images.githubusercontent.com/11782833/144729427-5f559c56-6653-4317-9e03-d0294b59e71c.mp4

Edit: Closes https://github.com/godotengine/godot/issues/58052

To sum up what I said in RocketChat, I think the feature is desired: we need to be able to have a column there that gives you quick access to the most common and visual tools you might need to edit a node. This should limit the space taken into the top toolbar by the current state of the editor.
I don't think the current implementation is great UX-wise though, by default, it takes a huge space from the viewport just to show a few labels. We could hide them, but then the icons themselves would be very difficult to learn as they are very specific to the node you are editing.
I suggest the following changes instead:

Remove the buttons and labels from the top of the Viewport, and only keep one to open/close and "advanced editors" column.
Move the different "drawers" to sections of the column (like the inspector works in fact)

You mentioned on RC that this might take too much space, while I think the most common workflow will likely to be "open the drawer" ->"do you thing" -> "close the drawer", I guess some users might prefer to keep the drawer opened all the time. As a consequence, I suggest to allow the possibility to collapse the sections you might not need.
Here is a mockup so that you undestand what I mean:

This solution:

Limits the space taken to a single button for those how don't need the advanced editor.
Keeps the discoverability thanks to the section labels
Still allow to have the column always open, with customizable expanded/collapsed sections depending on what you need.

Here is a mockup so that you undestand what I mean

Having buttons for the closed editors always visible might be useful to quickly toggle editors on/off. And collapsed sections with the label will take too much space, when all editors are closed. I would do something in between:

And maybe also "pin" button on the left side of each editor to keep in always open.

Keeps the discoverability thanks to the section labels

Closed editor icons can auto expand the full title with the label on hover, I do not see any reason to always display labels.

Closed editor icons can auto expand the full title with the label on hover, I do not see any reason to always display labels.

On hover we already have labels, but some were not convinced it was enough. There are pretty much dozens of such nitpicks, and I'd prefer to see what users think in practice. I am okay with removing labels though, I was just trying to address raised concerns.

Some missing icon:

This drawer has a few problems:

The toggleable buttons look bad when it's wide. They should probably SHRINK_CENTER.
"Set to current ratio" doesn't look clickable.
Button texts seem to be improperly capitalized (all words should start with capital letter. Although not sure if it's really consistent across the editor)
Anchors and offsets changes its text upon click. It's rather weird

This:

Same problem with wide buttons
Without Expand changes text when clicked, while it shouldn't (it's a CheckButton for a reason...)

It's also missing icon, as I already mentioned
Also the behavior is confusing. It should take effect immediately

The VSeparator besides the "View" button in the toolbar should be removed.

Okay, regarding notes from comments:

Missing icons fixed in another PR.
Text properties being stretched horizontally was a problem from a local rebase. This drawer is a vbox like any other, it should be displayed properly now.
I've renamed all CheckButtons to only use one label without flipping depending on value, and expanded tooltips to explain what toggling them does in both ways. Hopefully it remains clear this way.
I've fixed capitalization.
I've removed flatness from "Set to Current Ratio", but by default it still doesn't stand out. However, it now reacts on hover same as anchor/size flag buttons.
I've renamed "With/Without Expand" to say "Align with Expand" and moved it above the alignment buttons to mimic the same order of anchor buttons. We could make expand take effect immediately, but I think it's better to enable it and then use the alignment buttons to set the actual alignment. Otherwise, setting something + expand would always be two clicks.

I haven't looked yet into why the hidden drawers extend other drawers, but it shouldn't happen with properly laid out panels. I'll still take a look, but I don't think it's too important at the moment.
I'll also look into labels on buttons being too obstructive and maybe into implementing bruvzg's proposed layout (without the overflow button, though, not sure how it's supposed to work and the drawer container already supports scrolling).

I've renamed "With/Without Expand" to say "Align with Expand" and moved it above the alignment buttons to mimic the same order of anchor buttons. We could make expand take effect immediately, but I think it's better to enable it and then use the alignment buttons to set the actual alignment. Otherwise, setting something + expand would always be two clicks.

It should be CheckBox instead of CheckButton if it's not immediate, I think (same with other buttons).

It should be CheckBox instead of CheckButton if it's not immediate, I think (same with other buttons).

Alright, I didn't really consider there being a semantic difference between the two, or it's very small. But I guess it addresses your other concern with CheckButtons looking bad when the panel is too wide 🙃

I've tried to implement bruvzg's suggested layout, but some things are harder to make work in their current form with the scroll container used for the overflow. I'd like to collect more feedback, preferably from users, to decide which parts to keep and which to get rid of. This should make it easier to make changes then.
However, there are also two problems with the suggested layout, both in regards to the overflow. Like I've said, I'm not sure how the overflow button would work, when in theory a single panel can overflow the height of the viewport. It just doesn't fit, at least I can't see how to make it fit for now. So I was going to implement it with the current overflow system, which just enables a vertical scroll.

However, with bruvzg's layout buttons can easily appear outside of user's view without any indication. Actually, this would also be a problem if the overflow button was somehow implemented. With the current separate bar of buttons they are almost guaranteed to always appear in user's view, which should help with discoverability.
The second issue with removing the row of buttons would be that the overflow scrollbar would be right next to the viewport scrollbar. This would probably lead to a lot of accidental misclicks. Both issues make me skeptical about this approach.

In the meantime, I've fixed the issue with very vide panels, I think. The content of the scroll container wasn't resized properly on visibility changes under such circumstances, which should now be fixed.
I've also added a setting to hide button labels. I think they can be good for some folks, but if the space on smaller screens is a concern, there is now an option. At least for the time being, we can remove it later in favor of one of the options during alpha and beta testing.

Sorry, as I mentioned. I feel this way as-is is not good enough for two reasons:

Inconsistent with 3D (which can split the view into multiple viewports). We must avoid having two entirely different editors for 2D and 3D besides the viewport.
Inconsistent concept as-is, one thing is shortcuts and the other is actions. If you look at other parts of the editor instead of centering in this specific problem, it makes sense to have this difference better defined.

I will make an alternate proposal to solve this in a separate PR to be evaluate, in the meantime this should not be merged.

@reduz Why not contribute directly to the conversation in godotengine/godot-proposals#3550? Discussing the design there sounds better than jumping directly to implementation. Specially with the editor UI, it's much quicker to share mockup.

As promised, I wrote two proposals to supersede this. Sorry it took me this long:
https://github.com/godotengine/godot-proposals/issues/4273
https://github.com/godotengine/godot-proposals/issues/4274

I haven't dug too deep into the editor sources yet and apologies if this has already been discussed, but is there some technical limitation that prevents the drawer from existing on top of the viewports?

It's more a functional limitation. In 2D editor everything is in fixed place, but in 3D you can get into this situation (quick mock-up):

Although this could be solved if drawers were movable.

Although this could be solved if drawers were movable.

Plz this. (This would also help with things such as the Animation panel or the visual graph panel...)

Thank you @KoBeWi
Personally, I think that is a non-issue that is easily solved by having a toggle on/off shortcut (like n in Blender) and reducing the right margin, or by having them moveable as you said.
That being said I do use a large monitor, and on smaller resolutions the issue might be more obvious. Still I feel this is not as big of an issue as it's made to be.

@neikeq because, as mentioned, I want to bring to the table entirely different solutions to the problems at hand than contextual drawers.

Sorry, I thought you wanted to make a PR right away instead of a proposal 😅

@gaudecker In the end, you are just piling hacks over other hacks to make something work that just goes against how the rest of the UI work unnaturally. Instead of forcing it,
I think for specifically what this PR aims to solve, property pinning (https://github.com/godotengine/godot-proposals/issues/4274) makes far more sense because its entirely general purpose and does not require developers having to write a custom interface for every single type of object you want to have editing more accessible.

@reduz I think the property pinning proposal is excellent and solves the problem in an intuitive way! I also agree that the action proposal is much better than what we have now.
What I worry about is how the action panel scales with many actions (like with the mesh node). The inspector is crowded already.
I feel that this PR lends itself better to extension by plugins.
Maybe this PR can be reworked so that it is not a hack as you say? Some sort of compromise between the two?

@gaudecker The action area proposal (https://github.com/godotengine/godot-proposals/issues/4274) to me is not overlapping much with this one, its simply moving something that is very tiny (by definition because its normally in the Viewport status bar) to a place in the inspector which should not take extra space (if done like in the proposal).
Even if the contextual drawers were merged, I think the action area would still make sense for the remaining dozens of editors that are just a single button that you want to move closer to the inspector for better discoverability.

@reduz I think I misunderstood the intent of your proposals.
They do indeed solve different(if somewhat overlapping) problems.

Bye :<

We're not going to forget you Drawer-kun... may you be salvaged in future times to the delight of plugin makers.

Shamelessly screen captured.


Remove green glow

Hi! there is weird glow on the nft cards - it indicates that you are the owner.
Can we remove it?

👋🏻


Add support for Greengrass CloudFormation

Greengrass support in CloudFormation was recently launched
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-reference-greengrass.html
The provisioner should be able to output CloudFormation templates that use these features.

Launch announcement: https://aws.amazon.com/about-aws/whats-new/2019/03/aws-iot-greengrass-adds-new-connector-aws-iot-analytics-support-aws-cloudformation-templates-integration-fleet-indexing/


Don't use sinatra-assetpack as it is deprecated

See sprocket-based alternatives like sinatra-asset-pipeline and sprockets-helpers.

Fixed in 2.2.9.


Flash of Unstyled Content for quickstart plus a CSS file

Which project does this relate to?
Start
Describe the bug
I see a flash of unstyled content for a pretty minimal setup.

follow the getting started guide
add a CSS file (I used div: { border: solid 20px red; } in app/styes/app.css and loaded it by adding

import appCss from "../styles/app.css?url";
...
export const Route = createRootRoute({
  ...
  links: () => [{ rel: "stylesheet", href: appCss }],
  ...

to createRootRoute in app/routes/__root.tsx
3. deploy to Vercel with build command npm run build
4. turn off the Vercel toolbar and Vercel protection (the vercel toolbar seems necessary, not sure on the latter)
Your Example Website or App
https://start-repro.vercel.app
Steps to Reproduce the Bug or Issue
Here's the repo, deploy it on Vercel and turn off the toolbar.
Here's the link where I have it deployed: https://start-repro.vercel.app/
Load the page in desktop Safari on a mac. Load it a few times, notice the flash. Especially noticeable on an iphone for me.
Or clone the repo, npm i; npm run dev, open it in Safari and open network dev tools and disable caches to debug the dev build.
Expected behavior
I expect no flash.
Screenshots or Videos
https://github.com/user-attachments/assets/0cd750a6-010f-4460-ade6-a4e74592e70e
Platform

OS: macOS, iOS
Browser: Safari

Additional context
No response

Noteably there's not hydration error visible in the console here.

Oh cool, I can repro locally with
npx vinxi build --preset node-server
npx vinxi start

and then clicking "Disable Caches" in the Network devtools tab.

Here's an interesting diff! By stepping through the React code I saw React first committing the body, then later the head. https://gist.github.com/thomasballinger/679ef30071a682cb5da3738940140b5b
--- stuff.html	2024-11-04 18:33:00
+++ right.html	2024-11-04 17:09:24
@@ -1,15 +1,21 @@
-
+
+  <meta name="tsr-meta" />
+  <title>TanStack Start Starter</title>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1" />
+  <link rel="stylesheet" href="/_build/app/styles/app.css" />
+  <meta name="/tsr-meta" />
+

-    <button type="button">Add 1?</button
-    >
+    <button type="button">Add 1?</button>

This is seems resolved now! The repro has changed a little because of the new structure of head / links.