The external network cannot access the http url that uses the host name by default

After startup, I cannot enter the details interface of the specified host on the external network

not sure that I understand your issue.
assuming that everything works fine on the local host, my best guess is that your firewall blocks the HTTP connection from another host.

I have now defined supervisors_list=xxx.xx.xx, but I cannot see any information about my process group from the web UI interface, the display is empty, and there is no way to enter the detailed interface.

I have now defined supervisors_list=<mirchi>xxx.xx.xx, but I cannot see any information about my process group from the web UI interface, the display is empty, and there is no way to enter the detailed interface.

could you please share your supervisord.conf file ?

; supervisor config file
[unix_http_server]
file=/var/run/supervisor.sock   ; (the path to the socket file)
chmod=0700                       ; sockef file mode (default 0700)
[supervisord]
user=root
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)
identifier=mirchi
; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket
[inet_http_server]
port=:6688
username=pocket
password=mirchi!@#$
[rpcinterface:supvisors]
supervisor.rpcinterface_factory = supvisors.plugin:make_supvisors_rpcinterface
supvisors_list=<mirchi><IP_ADDRESS>
; newlines).  It can also contain wildcards.  The filenames are
; interpreted as relative to this file.  Included files cannot
; include files themselves.
[include]
files = /etc/supervisor/conf.d/**/*.conf

the /var/log/supervisor/supervisord.log also please ?
if you type hostname in a shell, what does it return ?
I suspect it is still configured as 'localhost'.

2023-06-06 08:30:34,701 WARN For [program:pro_mirchi_api], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:pro_mirchi_celery], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:pro_mirchi_beat], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:pro_mirchi_redis_expired], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:test_mirchi_api], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:test_mirchi_celery], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:test_mirchi_beat], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 WARN For [program:test_mirchi_redis_expired], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored
2023-06-06 08:30:34,702 INFO Included extra file "/etc/supervisor/conf.d/mirchi/pro_mirchi.conf" during parsing
2023-06-06 08:30:34,702 INFO Included extra file "/etc/supervisor/conf.d/mirchi/test_mirchi.conf" during parsing
2023-06-06 08:30:34,702 INFO Set uid to user 0 succeeded
2023-06-06 08:30:34,704 INFO RPC interface 'supervisor' initialized
2023-06-06 08:30:34,711;DEBG;SupervisorData.read_disabilities: disabilities_file=None
2023-06-06 08:30:34,711;WARN;SupervisorData.read_disabilities: no persistence for program disabilities
2023-06-06 08:30:34,711;DEBG;SupvisorsInstanceId.parse_from_string: identifier=mirchi host_id=<IP_ADDRESS> http_port=0 internal_port=0
2023-06-06 08:30:34,711;DEBG;SupvisorsInstanceId.check_values: identifier=mirchi host_name=<IP_ADDRESS> http_port=6688 internal_port=6689
2023-06-06 08:30:34,711;DEBG;SupvisorsInstanceId: host_id=<IP_ADDRESS> host_name=mirchi ip_address=<IP_ADDRESS>
2023-06-06 08:30:34,711;DEBG;SupvisorsMapper.configure: new SupvisorsInstanceId=mirchi
2023-06-06 08:30:34,711;INFO;SupvisorsMapper.configure: identifiers=['mirchi']
2023-06-06 08:30:34,711;DEBG;SupvisorsMapper.configure: nodes={'<IP_ADDRESS>': ['mirchi']}
2023-06-06 08:30:34,712;INFO;SupvisorsMapper.find_local_identifier: local_identifier=mirchi
2023-06-06 08:30:34,712;INFO;SupvisorsMapper.configure: core_identifiers=[]
2023-06-06 08:30:34,716;INFO;Supvisors: psutil not installed
2023-06-06 08:30:34,716;WARN;Supvisors: this Supvisors instance cannot not collect statistics
2023-06-06 08:30:34,716;WARN;Supvisors: cannot parse rules files: None - 'NoneType' object is not iterable
2023-06-06 08:30:34,717;INFO;RPCInterface: using Supvisors=0.16 Supervisor=4.2.5
2023-06-06 08:30:34,717;INFO;RPC interface 'supvisors' initialized
2023-06-06 08:30:35,018;INFO;RPC interface 'supervisor' initialized
2023-06-06 08:30:35,018;INFO;RPCInterface: using Supvisors=0.16 Supervisor=4.2.5
2023-06-06 08:30:35,018;INFO;RPC interface 'supvisors' initialized
2023-06-06 08:30:35,018;CRIT;Server 'unix_http_server' running without any HTTP authentication checking
2023-06-06 08:30:35,018;INFO;supervisord started with pid 2046
2023-06-06 08:30:35,018;INFO;SupervisorListener.on_running: local supervisord is RUNNING
2023-06-06 08:30:35,018;DEBG;PublisherServer._bind: binding localhost:6689
2023-06-06 08:30:35,019;DEBG;SupervisorListener.on_running: request to start main loop
2023-06-06 08:30:35,019;DEBG;SupervisorListener.on_running: main loop started
2023-06-06 08:30:35,019;DEBG;Starter.next: current_jobs=[]
2023-06-06 08:30:35,019;DEBG;Stopper.next: current_jobs=[]
2023-06-06 08:30:35,019;INFO;FiniteStateMachine.set_state: Supvisors in INITIALIZATION
2023-06-06 08:30:35,019;INFO;Context.master_identifier:
2023-06-06 08:30:35,019;DEBG;InitializationState.next: local Supvisors=mirchi still not RUNNING
2023-06-06 08:30:36,021;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for pro:pro_mirchi_api
2023-06-06 08:30:36,022;INFO;spawned: 'pro_mirchi_api' with pid 2051
2023-06-06 08:30:36,023;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for pro:pro_mirchi_celery
2023-06-06 08:30:36,024;INFO;spawned: 'pro_mirchi_celery' with pid 2052
2023-06-06 08:30:36,025;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for pro:pro_mirchi_beat
2023-06-06 08:30:36,027;INFO;spawned: 'pro_mirchi_beat' with pid 2053
2023-06-06 08:30:36,028;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for pro:pro_mirchi_redis_expired
2023-06-06 08:30:36,030;INFO;spawned: 'pro_mirchi_redis_expired' with pid 2054
2023-06-06 08:30:36,030;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for test:test_mirchi_api
2023-06-06 08:30:36,033;INFO;spawned: 'test_mirchi_api' with pid 2055
2023-06-06 08:30:36,033;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for test:test_mirchi_celery
2023-06-06 08:30:36,041;INFO;spawned: 'test_mirchi_celery' with pid 2056
2023-06-06 08:30:36,041;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for test:test_mirchi_beat
2023-06-06 08:30:36,044;INFO;spawned: 'test_mirchi_beat' with pid 2057
2023-06-06 08:30:36,045;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_STARTING for test:test_mirchi_redis_expired
2023-06-06 08:30:36,058;INFO;spawned: 'test_mirchi_redis_expired' with pid 2058
2023-06-06 08:30:36,897;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:36 +0000] [2051] [INFO] Starting gunicorn 20.1.0
[2023-06-06 08:30:36 +0000] [2051] [INFO] Listening at: http://<IP_ADDRESS>:6088 (2051)
[2023-06-06 08:30:36 +0000] [2051] [INFO] Using worker: gevent
2023-06-06 08:30:36,912;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:36 +0000] [2073] [INFO] Booting worker with pid: 2073
2023-06-06 08:30:36,977;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:36 +0000] [2055] [INFO] Starting gunicorn 20.1.0
[2023-06-06 08:30:36 +0000] [2055] [INFO] Listening at: http://<IP_ADDRESS>:8088 (2055)
[2023-06-06 08:30:36 +0000] [2055] [INFO] Using worker: gevent
2023-06-06 08:30:36,988;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:36 +0000] [2076] [INFO] Booting worker with pid: 2076
2023-06-06 08:30:37,020;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:37 +0000] [2077] [INFO] Booting worker with pid: 2077
2023-06-06 08:30:37,056;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:37 +0000] [2078] [INFO] Booting worker with pid: 2078
2023-06-06 08:30:37,057;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for pro:pro_mirchi_api
2023-06-06 08:30:37,057;INFO;success: pro_mirchi_api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,057;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for pro:pro_mirchi_celery
2023-06-06 08:30:37,057;INFO;success: pro_mirchi_celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,057;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for pro:pro_mirchi_beat
2023-06-06 08:30:37,057;INFO;success: pro_mirchi_beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,057;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for pro:pro_mirchi_redis_expired
2023-06-06 08:30:37,058;INFO;success: pro_mirchi_redis_expired entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,058;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for test:test_mirchi_api
2023-06-06 08:30:37,058;INFO;success: test_mirchi_api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,058;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for test:test_mirchi_celery
2023-06-06 08:30:37,058;INFO;success: test_mirchi_celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,058;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for test:test_mirchi_beat
2023-06-06 08:30:37,058;INFO;success: test_mirchi_beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,059;DEBG;SupervisorListener.on_process_state: got PROCESS_STATE_RUNNING for test:test_mirchi_redis_expired
2023-06-06 08:30:37,059;INFO;success: test_mirchi_redis_expired entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-06 08:30:37,076;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:37 +0000] [2079] [INFO] Booting worker with pid: 2079
2023-06-06 08:30:37,150;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:37 +0000] [2080] [INFO] Booting worker with pid: 2080
2023-06-06 08:30:39,502;DEBG;'pro_mirchi_beat' stdout output:
celery beat v5.2.6 (dawn-chorus) is starting.
__    -    ... __   -        _
LocalTime -> 2023-06-06 08:30:39
Configuration ->
. broker -> redis://:**@<IP_ADDRESS>:6379/6
. loader -> celery.loaders.app.AppLoader
. scheduler -> celery.beat.PersistentScheduler
. db -> celerybeat-schedule
. logfile -> [stderr]@%INFO
. maxinterval -> 5.00 minutes (300s)
[2023-06-06 08:30:39.502]: beat: Starting...
2023-06-06 08:30:39,562;DEBG;'test_mirchi_beat' stdout output:
celery beat v5.2.6 (dawn-chorus) is starting.
__    -    ... __   -        _
LocalTime -> 2023-06-06 08:30:39
Configuration ->
. broker -> redis://:**@<IP_ADDRESS>:6379/15
. loader -> celery.loaders.app.AppLoader
. scheduler -> celery.beat.PersistentScheduler
. db -> celerybeat-schedule
. logfile -> [stderr]@%INFO
. maxinterval -> 5.00 minutes (300s)
[2023-06-06 08:30:39.561]: beat: Starting...
2023-06-06 08:30:39,955;DEBG;'pro_mirchi_beat' stdout output:
[2023-06-06 08:30:39.955]: Scheduler: Sending due task 付费音视频定时巡检 (celery_server.mirchi.tasks.call_timing_check)
2023-06-06 08:30:40,027;DEBG;'pro_mirchi_beat' stdout output:
[2023-06-06 08:30:40.027]: Scheduler: Sending due task mirchi_beat_health (celery_server.tasks.mirchi_beat_health)
2023-06-06 08:30:40,027;DEBG;SupervisorListener.on_tick: got TickEvent from Supervisor <supervisor.events.Tick5Event object at 0x7fdc0c275b10>
2023-06-06 08:30:40,029;DEBG;'test_mirchi_beat' stdout output:
[2023-06-06 08:30:40.029]: Scheduler: Sending due task mirchi_beat_health (celery_server.tasks.mirchi_beat_health)
2023-06-06 08:30:40,051;DEBG;'pro_mirchi_beat' stdout output:
[2023-06-06 08:30:40.051]: Scheduler: Sending due task 音视频清结算扫描 (celery_server.mirchi.tasks.call_timing_settlement)
2023-06-06 08:30:40,059;DEBG;'test_mirchi_beat' stdout output:
[2023-06-06 08:30:40.058]: Scheduler: Sending due task 付费音视频定时巡检 (celery_server.mirchi.tasks.call_timing_check)
2023-06-06 08:30:40,088;DEBG;'test_mirchi_beat' stdout output:
[2023-06-06 08:30:40.087]: Scheduler: Sending due task 音视频清结算扫描 (celery_server.mirchi.tasks.call_timing_settlement)
2023-06-06 08:30:41,278;DEBG;'pro_mirchi_celery' stdout output:
-------------- celery@mirchi v5.2.6 (dawn-chorus)
--- ***** -----
-- ******* ---- Linux-5.19.0-1026-aws-x86_64-with-debian-bookworm-sid 2023-06-06 08:30:41

*** --- * ---
** ---------- [config]
** ---------- .> app:         mirchi_celery_app:0x7f5c6e86f5f8
** ---------- .> transport:   redis://:**@<IP_ADDRESS>:6379/6
** ---------- .> results:     mysql://admin:**@database-2.ck8kpi4jl3yj.ap-south-1.rds.amazonaws.com:3306/habibi_pro
*** --- * --- .> concurrency: 100 (gevent)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
-------------- [queues]
.> mirchi_base_queue exchange=mirchi_base_exchange(direct) key=mirchi_base_queue
.> mirchi_base_queue_health exchange=mirchi_base_exchange_health(direct) key=mirchi_base_queue_health
.> mirchi_base_queue_main exchange=mirchi_base_exchange_main(direct) key=mirchi_base_queue_main

[tasks]
. celery_server.mirchi.tasks.async_call_settlement
. celery_server.mirchi.tasks.async_call_withholding
. celery_server.mirchi.tasks.async_im_send_message
. celery_server.mirchi.tasks.call_timing_check
. celery_server.mirchi.tasks.call_timing_settlement
. celery_server.tasks.mirchi_beat_health
2023-06-06 08:30:41,308;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:41.308]: Connected to redis://:**@<IP_ADDRESS>:6379/6
2023-06-06 08:30:41,312;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:41.312]: mingle: searching for neighbors
2023-06-06 08:30:41,339;DEBG;'test_mirchi_celery' stdout output:
-------------- celery@mirchi v5.2.6 (dawn-chorus)
--- ***** -----
-- ******* ---- Linux-5.19.0-1026-aws-x86_64-with-debian-bookworm-sid 2023-06-06 08:30:41

*** --- * ---
** ---------- [config]
** ---------- .> app:         mirchi_celery_app:0x7f7fd7ffed68
** ---------- .> transport:   redis://:**@<IP_ADDRESS>:6379/15
** ---------- .> results:     mysql://admin:**@database-2.ck8kpi4jl3yj.ap-south-1.rds.amazonaws.com:3306/habibi
*** --- * --- .> concurrency: 100 (gevent)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
-------------- [queues]
.> mirchi_base_queue_test exchange=mirchi_base_exchange_test(direct) key=mirchi_base_queue_test
.> mirchi_base_queue_test_health exchange=mirchi_base_exchange_test_health(direct) key=mirchi_base_queue_test_health
.> mirchi_base_queue_test_main exchange=mirchi_base_exchange_test_main(direct) key=mirchi_base_queue_test_main

[tasks]
. celery_server.mirchi.tasks.async_call_settlement
. celery_server.mirchi.tasks.async_call_withholding
. celery_server.mirchi.tasks.async_im_send_message
. celery_server.mirchi.tasks.call_timing_check
. celery_server.mirchi.tasks.call_timing_settlement
. celery_server.tasks.mirchi_beat_health
2023-06-06 08:30:41,372;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:41.372]: Connected to redis://:**@<IP_ADDRESS>:6379/15
2023-06-06 08:30:41,396;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:41.396]: mingle: searching for neighbors
2023-06-06 08:30:42,353;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.353]: mingle: all alone
2023-06-06 08:30:42,373;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.373]: pidbox: Connected to redis://:**@<IP_ADDRESS>:6379/6.
2023-06-06 08:30:42,385;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.385]: celery@mirchi ready.
2023-06-06 08:30:42,437;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.436]: Task celery_server.tasks.mirchi_beat_health[9ee87d5c-966a-4eb5-9438-3947573a70c2] received
2023-06-06 08:30:42,439;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42,438]celery_server:mirchi_celery beat health
2023-06-06 08:30:42,453;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.453]: Task celery_server.tasks.mirchi_beat_health[9ee87d5c-966a-4eb5-9438-3947573a70c2] succeeded in 0.014862981999613112s: None
2023-06-06 08:30:42,455;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:42.455]: Task celery_server.mirchi.tasks.call_timing_settlement[0dfd5e0b-cf2f-4911-9f36-2dd79676a64b] received
2023-06-06 08:30:42,456;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:42.455]: mingle: all alone
2023-06-06 08:30:42,475;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:42.475]: celery@mirchi ready.
2023-06-06 08:30:42,594;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:42.593]: Task celery_server.mirchi.tasks.call_timing_check[b4def0b8-3ec9-4f04-8855-5282791f51b7] received
2023-06-06 08:30:43,202;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43.202]: Task celery_server.mirchi.tasks.call_timing_check[7aa03dd6-0f1b-4d46-850b-5f97d3f9fbf6] received
2023-06-06 08:30:43,206;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43.205]: Task celery_server.mirchi.tasks.call_timing_settlement[57a73dd0-79f1-4915-8a19-bf9a1c0555ec] received
2023-06-06 08:30:43,206;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.206]: Task celery_server.tasks.mirchi_beat_health[68a5095a-9534-4b4c-a6fe-843d22c0335f] received
2023-06-06 08:30:43,208;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43,208]celery_server:mirchi_celery beat health
2023-06-06 08:30:43,223;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43,222]celery_server:task:celery_server.mirchi.tasks.call_timing_settlement[0dfd5e0b-cf2f-4911-9f36-2dd79676a64b], arg:[], kwargs:{}, successful!
2023-06-06 08:30:43,223;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43.223]: Task celery_server.mirchi.tasks.call_timing_settlement[0dfd5e0b-cf2f-4911-9f36-2dd79676a64b] succeeded in 0.7658018769998307s: None
2023-06-06 08:30:43,224;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.223]: Task celery_server.tasks.mirchi_beat_health[68a5095a-9534-4b4c-a6fe-843d22c0335f] succeeded in 0.015874937000262435s: None
2023-06-06 08:30:43,226;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.226]: Task celery_server.mirchi.tasks.call_timing_settlement[53142d62-5ea0-4397-8141-b21ebb031ad8] received
2023-06-06 08:30:43,242;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43,242]celery_server:task:celery_server.mirchi.tasks.call_timing_check[7aa03dd6-0f1b-4d46-850b-5f97d3f9fbf6], arg:[], kwargs:{}, successful!
2023-06-06 08:30:43,243;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43.242]: Task celery_server.mirchi.tasks.call_timing_check[7aa03dd6-0f1b-4d46-850b-5f97d3f9fbf6] succeeded in 0.03815862500050571s: None
2023-06-06 08:30:43,243;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43,242]celery_server:task:celery_server.mirchi.tasks.call_timing_check[b4def0b8-3ec9-4f04-8855-5282791f51b7], arg:[], kwargs:{}, successful!
2023-06-06 08:30:43,243;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.243]: Task celery_server.mirchi.tasks.call_timing_check[b4def0b8-3ec9-4f04-8855-5282791f51b7] succeeded in 0.6471626140000808s: None
2023-06-06 08:30:43,247;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.246]: pidbox: Connected to redis://:**@<IP_ADDRESS>:6379/15.
2023-06-06 08:30:43,259;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43,259]celery_server:task:celery_server.mirchi.tasks.call_timing_settlement[57a73dd0-79f1-4915-8a19-bf9a1c0555ec], arg:[], kwargs:{}, successful!
2023-06-06 08:30:43,260;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:43.260]: Task celery_server.mirchi.tasks.call_timing_settlement[57a73dd0-79f1-4915-8a19-bf9a1c0555ec] succeeded in 0.052447858000050473s: None
2023-06-06 08:30:43,264;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43,263]celery_server:task:celery_server.mirchi.tasks.call_timing_settlement[53142d62-5ea0-4397-8141-b21ebb031ad8], arg:[], kwargs:{}, successful!
2023-06-06 08:30:43,264;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:43.264]: Task celery_server.mirchi.tasks.call_timing_settlement[53142d62-5ea0-4397-8141-b21ebb031ad8] succeeded in 0.035363155000595725s: None
2023-06-06 08:30:45,266;DEBG;SupervisorListener.on_tick: got TickEvent from Supervisor <supervisor.events.Tick5Event object at 0x7fdc0c275b10>
2023-06-06 08:30:50,272;DEBG;SupervisorListener.on_tick: got TickEvent from Supervisor <supervisor.events.Tick5Event object at 0x7fdc0c275b10>
2023-06-06 08:30:55,057;DEBG;'pro_mirchi_beat' stdout output:
[2023-06-06 08:30:55.056]: Scheduler: Sending due task 音视频清结算扫描 (celery_server.mirchi.tasks.call_timing_settlement)
2023-06-06 08:30:55,057;WARN;received SIGINT indicating exit request
2023-06-06 08:30:55,057;DEBG;SupervisorListener.on_tick: got TickEvent from Supervisor <supervisor.events.Tick5Event object at 0x7fdc0c275b10>
2023-06-06 08:30:55,058;WARN;SupervisorListener.on_stopping: local supervisord is STOPPING
2023-06-06 08:30:55,058;DEBG;SupervisorListener.on_stopping: stopping main loop
2023-06-06 08:30:55,155;DEBG;SupervisorListener.on_stopping: main loop stopped
2023-06-06 08:30:55,155;DEBG;SupervisorListener.on_stopping: stopping internal publication thread
2023-06-06 08:30:55,155;DEBG;PublisherServer.stop: stopping publisher server
2023-06-06 08:30:55,155;DEBG;PublisherServer.stop: publisher server stopped
2023-06-06 08:30:55,155;DEBG;PublisherServer.stop: stopping publisher thread
2023-06-06 08:30:55,558;DEBG;PublisherServer.stop: publisher thread stopped
2023-06-06 08:30:55,558;DEBG;SupervisorListener.on_stopping: internal publication thread stopped
2023-06-06 08:30:55,558;DEBG;killing test_mirchi_redis_expired (pid 2058) process group with signal SIGTERM
2023-06-06 08:30:55,558;DEBG;killing test_mirchi_beat (pid 2057) process group with signal SIGTERM
2023-06-06 08:30:55,558;DEBG;killing test_mirchi_celery (pid 2056) process group with signal SIGTERM
2023-06-06 08:30:55,558;DEBG;killing test_mirchi_api (pid 2055) process group with signal SIGTERM
2023-06-06 08:30:55,559;INFO;waiting for pro_mirchi_api, pro_mirchi_celery, pro_mirchi_beat, pro_mirchi_redis_expired, test_mirchi_api, test_mirchi_celery, test_mirchi_beat, test_mirchi_redis_expired to die
2023-06-06 08:30:55,559;DEBG;'pro_mirchi_celery' stdout output:
[2023-06-06 08:30:55.062]: Task celery_server.mirchi.tasks.call_timing_settlement[1ab83a1a-833b-4339-b1c7-04be5c534e6b] received
[2023-06-06 08:30:55,078]celery_server:task:celery_server.mirchi.tasks.call_timing_settlement[1ab83a1a-833b-4339-b1c7-04be5c534e6b], arg:[], kwargs:{}, successful!
[2023-06-06 08:30:55.078]: Task celery_server.mirchi.tasks.call_timing_settlement[1ab83a1a-833b-4339-b1c7-04be5c534e6b] succeeded in 0.014653308999186265s: None
2023-06-06 08:30:55,559;DEBG;'test_mirchi_celery' stdout output:
[2023-06-06 08:30:55.092]: Task celery_server.mirchi.tasks.call_timing_settlement[8151d1ca-2fb8-4506-979e-7f90dcc85779] received
[2023-06-06 08:30:55,107]celery_server:task:celery_server.mirchi.tasks.call_timing_settlement[8151d1ca-2fb8-4506-979e-7f90dcc85779], arg:[], kwargs:{}, successful!
[2023-06-06 08:30:55.107]: Task celery_server.mirchi.tasks.call_timing_settlement[8151d1ca-2fb8-4506-979e-7f90dcc85779] succeeded in 0.014355353999235376s: None
2023-06-06 08:30:55,559;DEBG;'test_mirchi_beat' stdout output:
[2023-06-06 08:30:55.087]: Scheduler: Sending due task 音视频清结算扫描 (celery_server.mirchi.tasks.call_timing_settlement)
2023-06-06 08:30:55,559;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:55 +0000] [2055] [INFO] Handling signal: term
2023-06-06 08:30:55,560;DEBG;'test_mirchi_celery' stdout output:
worker: Warm shutdown (MainProcess)
2023-06-06 08:30:55,564;DEBG;fd 34 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>60288 for <Subprocess at<PHONE_NUMBER>60240 with name test_mirchi_redis_expired in state STOPPING> (stdout)>
2023-06-06 08:30:55,564;WARN;stopped: test_mirchi_redis_expired (terminated by SIGTERM)
2023-06-06 08:30:55,564;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:55,683;DEBG;fd 31 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>60192 for <Subprocess at<PHONE_NUMBER>60144 with name test_mirchi_beat in state STOPPING> (stdout)>
2023-06-06 08:30:55,684;INFO;stopped: test_mirchi_beat (exit status 0)
2023-06-06 08:30:55,684;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:56,166;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:56 +0000] [2076] [INFO] Worker exiting (pid: 2076)
2023-06-06 08:30:56,231;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:56 +0000] [2080] [INFO] Worker exiting (pid: 2080)
2023-06-06 08:30:56,295;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:56 +0000] [2078] [INFO] Worker exiting (pid: 2078)
2023-06-06 08:30:56,553;DEBG;fd 28 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>60096 for <Subprocess at<PHONE_NUMBER>60048 with name test_mirchi_celery in state STOPPING> (stdout)>
2023-06-06 08:30:56,554;WARN;received SIGINT indicating exit request
2023-06-06 08:30:56,663;DEBG;'test_mirchi_api' stdout output:
[2023-06-06 08:30:56 +0000] [2055] [INFO] Shutting down: Master
2023-06-06 08:30:56,663;INFO;stopped: test_mirchi_celery (exit status 0)
2023-06-06 08:30:56,663;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:56,685;DEBG;fd 25 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>60000 for <Subprocess at<PHONE_NUMBER>59904 with name test_mirchi_api in state STOPPING> (stdout)>
2023-06-06 08:30:56,685;INFO;stopped: test_mirchi_api (exit status 0)
2023-06-06 08:30:56,686;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:56,686;DEBG;killing pro_mirchi_redis_expired (pid 2054) process group with signal SIGTERM
2023-06-06 08:30:56,686;DEBG;killing pro_mirchi_beat (pid 2053) process group with signal SIGTERM
2023-06-06 08:30:56,686;DEBG;killing pro_mirchi_celery (pid 2052) process group with signal SIGTERM
2023-06-06 08:30:56,686;DEBG;killing pro_mirchi_api (pid 2051) process group with signal SIGTERM
2023-06-06 08:30:56,686;DEBG;'pro_mirchi_celery' stdout output:
worker: Warm shutdown (MainProcess)
2023-06-06 08:30:56,687;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:56 +0000] [2051] [INFO] Handling signal: term
2023-06-06 08:30:56,691;DEBG;fd 22 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>59808 for <Subprocess at<PHONE_NUMBER>59760 with name pro_mirchi_redis_expired in state STOPPING> (stdout)>
2023-06-06 08:30:56,691;WARN;stopped: pro_mirchi_redis_expired (terminated by SIGTERM)
2023-06-06 08:30:56,691;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:56,797;DEBG;fd 19 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>59712 for <Subprocess at<PHONE_NUMBER>59664 with name pro_mirchi_beat in state STOPPING> (stdout)>
2023-06-06 08:30:56,797;INFO;stopped: pro_mirchi_beat (exit status 0)
2023-06-06 08:30:56,797;DEBG;received SIGCHLD indicating a child quit
2023-06-06 08:30:57,052;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:57 +0000] [2073] [INFO] Worker exiting (pid: 2073)
2023-06-06 08:30:57,222;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:57 +0000] [2077] [INFO] Worker exiting (pid: 2077)
2023-06-06 08:30:57,223;WARN;received SIGINT indicating exit request
2023-06-06 08:30:57,243;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:57 +0000] [2079] [INFO] Worker exiting (pid: 2079)
2023-06-06 08:30:57,490;DEBG;'pro_mirchi_api' stdout output:
[2023-06-06 08:30:57 +0000] [2051] [INFO] Shutting down: Master
2023-06-06 08:30:57,528;DEBG;fd 13 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>65664 for <Subprocess at<PHONE_NUMBER>59520 with name pro_mirchi_api in state STOPPING> (stdout)>
2023-06-06 08:30:57,528;WARN;received SIGINT indicating exit request
2023-06-06 08:30:57,576;DEBG;fd 16 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>59616 for <Subprocess at<PHONE_NUMBER>59184 with name pro_mirchi_celery in state STOPPING> (stdout)>
2023-06-06 08:30:57,576;INFO;stopped: pro_mirchi_api (exit status 0)
2023-06-06 08:30:57,576;INFO;stopped: pro_mirchi_celery (exit status 0)
2023-06-06 08:30:57,576;DEBG;received SIGCHLD indicating a child quit

all right. the issue is clearly that the Supvisors internal com does not work properly on your host.
Supvisors uses a TCP socket on port 6689, (when no option is set, the port is supervisor's port + 1 by default)
the binding worked, the supervisor events are received but the connected side is silent.
as the Supervisor logger is not thread-safe, there is no log traces in the Supvisors connect thread.
when an error happens there, it does not get reflected in the supervisor log file because it is send to the stderr, which is not captured by the Supervisor logger.
however, if you start the supervisor daemon non-daemonized in a terminal, the error will be displayed.
could you please try to start supervisor like this in a shell ?
supervisord -n -c <your conf file>

Hello, the above log is the result of running a separate shell. sudo supervisord -n -e debug -c /etc/supervisor/supervisord.conf >> test.log

Hello, seeing your last answer, I suddenly realized that I still have a 6689 port left without developing public network access

Thank you very much, everything is fine now

good news !
fyi, '>>' does not capture stderr. '&>>' does.


Connection with a vpn at android is not recognized

Platforms

Android
Versions

Android: 9 (Samsung Galaxy S8)
react-native-netinfo: 2.0.9
react-native: 0.59.0

Description

Calling NetInfo.getConnectionInfo() returns type "unknown", if a vpn is activated and the device have a connection with wifi/cellular.
The deprecated intern React Native Package have the correct return of "wifi" by calling getConnectionInfo().
Also calling NetInfo.isConnected() return "false".

👋 Thanks for the report. Can you provide some more details for me:

What VPN software does this happen with?
Does it matter if the VPN is used over Wifi or mobile? Do they both return "unknown"?

I use vpn with the internal settings of the Samsung Galaxy S8.

In both cases it will be returned "unknown"

Ok. Thank you. I don't have a Samsung device on hand, but I can test using my own VPN software.
It would be really helpful if you could run your Android app through the Android studio debugger and let me know the values of mNetworkCapabilities and mNetwork in this function:
https://github.com/react-native-community/react-native-netinfo/blob/master/android/src/main/java/com/reactnativecommunity/netinfo/NetworkCallbackConnectivityReceiver.java#L54-L77
Those are the variables which store what state we detect the network is in, so maybe Samsung are using some non-standard values when using a VPN?

this issue is reproducible with other Android devices and a vpn connection

Without VPN:

mNetworkCapabilities = [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED Unwanted:  LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -63]

mNetwork = „626“

With VPN:

mNetworkCapabilities = [ Transports: VPN Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED Unwanted: ]

mNetwork = „627“

Are these the values you need?

I guess we need to handle TYPE_VPN?

It is possible for the NetworkCapabilities to have multiple transports, however, in this case it looks like that is not happening.
Currently, if connected to a VPN which includes that transport along with a Wifi one, the library will work as expected.
I think we need to add a new type to the library as a fallback for this situation where we only know that it's a VPN connection.
This will likely be done after #84 is merged in and we add the feature from #12.

ok thanks :)

This also occurs with the use of the app from cloudfare <IP_ADDRESS>

A PR for this has been opened: #95.

issue still exists for me.
here are the details:
Mobile: Realme2Pro, Moto G4
OS 9
NetworkChecker getConnectionInfo
 is returning the below.
type:unknown
effectiveType:unknown
isConnected is true
can you please throw some light on this?

Hey there,
Thanks for all the work on this lib. It's super useful. We are, however, having issues getting readings on VPN connection types.
Details -
Device: Nexus 6P
Android: 8.1.0
We are attempting to log the presence of a VPN connection, but it seems to always be overridden by either WIFI (if wifi is on) or CELLULAR (if using cellular service), or NONE (if both are turned off). Has anyone experienced a similar issue/have any thoughts on how we can get VPN readings?
Thanks!

Hey, I am not getting the type as vpn, even though am connected to a vpn over my cellular network.
still the type remains cellular or wifi, even am connected through vpn.
HOW to solve this ??
Am using
@react-native-community/netinfo": "^5.7.0,
"react-native": "0.61.5",
Devices :
Honor 8x ,  Realme XT
Both devices are behaving the same.
Please Help, I cant release my app, am stuck over this.

Hey there,
I am trying to detect if android device is connected to VPN or not but always getting that it is connected even if device is connected to VPN or not
NetInfo.fetch(NetInfoStateType.vpn).then(state => {       console.warn("STATE is ", state);  });
outputs the same if the device is connected to VPN or not
{"details": {"isConnectionExpensive": true}, "isConnected": true, "isInternetReachable": false, "isWifiEnabled": true, "type": "vpn"}
I am using "@react-native-community/netinfo": "7.1.7"
and "react-native": "0.65.1"
Device:
Samsung Galaxy s7

same, in some case like latest SDK is working, but if you use old devices it cant be detected even using SDK 30 cant detect VPN over mobile data.

I faced the same problem - when VPN enabled over WiFi, the state.type = wifi (but expected vpn).
https://github.com/aspidvip/react-native-vpn-status - this lib correct detect VPN. Please see how implement logic in netinfo also:
https://github.com/aspidvip/react-native-vpn-status/blob/main/android/src/main/java/com/reactnativevpnstatus/VpnStatusModule.java

@bulkinav Matt Oakes has not contributed to this repository in some time, and in general we rely on people interested in specific problems to post solutions for those specific problems. What you have posted about another module that is able to determine VPN status correctly looks promising, I have the ability to merge PRs here if you post one

@mikehardy oh, I'd love to, but I'm not a developer and not to be able help with PR ☹


Document --direct-mounts

The --direct-mounts flag as talked about here is not documented in the CLI-reference

There are in fact a bunch of spin up options that are not in that list e.g.

--allow-transient-writes
--cache
--disable-cache
--follow / --follow-all
--log-dir
--runtime-config-file

Hi @mikkelhegn and @itowlson, just a quick note to let you know that there is a PR in to resolve the above.
Please see https://github.com/fermyon/developer/pull/263

The following have been catered for.
--direct-mounts
--allow-transient-writes
--cache
--disable-cache
--follow / --follow-all
--log-dir
--runtime-config-file

In addition, there are smaller changes like plugin -> plugins etc.


Extending gravstrap-theme

I'm trying to extend theme to customize it, but Grav gives me error:
syntax error, unexpected '-', expecting '{'
Might be something to do with the hyphen. My code here:
class MyThemeName extends Gravstrap-Theme { }

Hi,
you must not extend GravstrapTheme but Theme class:
use Grav\Common\Theme;

class MyThemeName extends Theme {}

though that's not mandatory, while you must add the follwing code to mytheme.yaml:
streams:
   schemes:
     theme:
       type: ReadOnlyStream
       prefixes:
         '':
         - user/themes/mytheme
         - user/themes/gravstraptheme

You will find more information about theme inheritance here: https://getgrav.org/blog/theme-development-with-inheritance


Enable SC1091 for hadolint

Waiting https://github.com/hadolint/hadolint/issues/905 to be clarified.

Disabled instead based on https://github.com/hadolint/hadolint/issues/905#issuecomment-1321255432


example to show correct iroh get behaviour

@faassen the last commit here takes your work and adds back in the correct behavior when using the outpath and when using nested ipfs paths!
iroh get Qmfoo
saves the output of Qmfoo to Qmfoo
iroh get Qmfoo new_file
saves the output of Qmfoo to new_file
iroh get Qmfoo/bar
saves the output of Qmfoo/bar to ./bar
iroh get Qmfoo/bar new_file
saves the output of Qmfoo/bar to new_file
NOTE:
I couldn't figure out exactly what the fixtures and tests were asking for.
I also was just a bit confused about the output for the tests anyway, as I mention in https://github.com/n0-computer/iroh/pull/331#discussion_r995071344


Script setup?

Any thoughts on supporting Vue 3 and emitting code in script setup style?

Actually, I mercilessly hacked the package to suite my needs and it worked great.
I wanted to convert several Vue 2 apps that used class components to Vue 2.7 with script setup. We chose this as our evolutionary path to Vue 3 as several of our dependencies don't have stable Vue 3 support yet (Vuetify being one).
The hacked tool did 70% of the work on each file and I had a set of manual fixes after that. There was a script setup learning curve to get the right output.
But it saved countless hours. Thank you for the tool, it was a great starting point.

@mobsense Glad to hear that! Hopefully other people looking to do 2 to 3 migration will be able to do the same. If there's something you think is generally useful to the package, feel free to send a PR and I'll merge it, too.
Cheers!


Define what the home page should show

What should the home page show?  Probably any active season standings (or links to them), plus a link to any "registration" if any are open, + link to rules / info about the league.

Link to tv if we ever get it done.
Link to slack.
Contact for moderators/admins - maybe registration is good enough...

We have a dynamic home page mostly implemented. Any additional changes can have a new issue created.


Exposed ports get a non-working IP address in UI link and API data structure

Rancher Version:
1.1.0-dev1
Docker Version:
1.9.1
OS and where are the hosts located? (cloud, bare metal, etc):
AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node, internal DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

create a project with one service and published port (either with explicit or random port mapping)

Results:

The UI will show a clickable port number. The link behind the port number will have an IP address of "172...", which is non-routable because container-internal.
also the API will return this information in the publicEndpoints structure

Expected:

A clickable link which gets me to the website on a working link
An API return value which reflects the reachable IP of the host

Comment:
I really don't know if that's a bug or a feature, but I see little sense in returning a link or data field pointing to a non-reachable address to be honest.
Screenshot:
see attached screenshot. The mouse hovers over the "5000" link.

Is that the IP on the host that the service is deployed on? If you go to your hosts screen, do you see that <IP_ADDRESS> on the host?

strangely enough, I do. if it's supposed to be the host IP it is plainly wrong as you can see. I have another host now next to it with docker 1.11.1, and ubuntu 16.04 (in contrast to 15.10), where the IP address seems to be right.

Is the left host also the one that is running the rancher/server container?  http://docs.rancher.com/rancher/latest/en/faqs/troubleshooting/#are-the-ips-of-the-hosts-correct-in-the-ui

Yes it is. Although it does not only happen with the master host, but also with others.
I also did now know about this bug. Does the IP stay constance once you have manually set the host IP? I'm asking because I want to use the API to create a dynamic routing into my services, and if that would be an issue that goal is highly in danger.

@flypenguin Yes, the IP will stay the same once you register the host with the correct IP. But if your host were to have their IP change (through reboot or restart), Rancher will not automatically update it. You would need to re-register the host with the new IP.
After updating the IP of the host, are you able to get your services set up correctly?

Actually I didn't try yet, cause I want to modify my automation accordingly before. Is the issue the same with a host which is set up from within Rancher? I assume this host would use RancherOS then, correct?

When you create a host through the Rancher UI, you are actually just calling a docker-machine command. Depending on the cloud provider or driver that you select the host OS could be whatever you want. If you wanted to go with RancherOS, you could use AWS and select a RancherOS AMI to spin up a host with RancherOS. Make sure you input rancher as the ssh user.
List of RancherOS AMIs are located in our Readme.

@flypenguin Please let me know if you still have further issues after you've updated the IP of your host. After that, you should have no issues with your load balancer exposed IP/port.


Missing dependencies for fresh install on Raspberry Pi 3B+ with Buster Lite  (IDFGH-2352)

Environment

IDF version (run git describe --tags to find it): v4.1-dev-1086-g93a8603c5
Build System:         CMake
Compiler version (run xtensa-esp32-elf-gcc --version to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2019r2) 8.2.0
Operating System:     Linux (Raspbian Buster Lite
Power Supply:         USB

Problem Description
//Detailed problem description goes here.
Expected Behavior
when running install.sh, the tools installation should succeed.
Actual Behavior
Installation fails at 2 stages:
It first miss libffi, then opensslv.
To fix the missing dependencies I've run the following command :

sudo apt-get install libffi-dev libssl-dev

After installing the 2 additional dependencies, install.sh succeed.
When proceeding to build the hello-world example, the compilation fails with segfault error.
To fix this, I updated the Raspberry Pi firmware using

sudo rpi-update

Building works successfully after the update.
Steps to repropduce
Install a fresh Raspbian Buster Lite on a RPI3B+, follow esp-idf getting started for linux.

Hi @AloyseTech. Did you install the prerequisites for Debian according to this page https://docs.espressif.com/projects/esp-idf/en/latest/get-started/linux-setup.html?

Hi @dobairoland ,
Yes, I followed the getting started guide for linux/debian and installed the following dependencies :
sudo apt-get install git wget flex bison gperf python python-pip python-setuptools python-serial python-click python-cryptography python-future python-pyparsing python-pyelftools cmake ninja-build ccache

Thank you for your report. I'll update the documentation. Newer versions of apt-get doesn't install as many packages as older ones and we need to add more and more packages to our list manually. Thanks!

Please also note that without updating the Raspberry Pi firmware, the build fails with segfault. I'm not sure what cause the issue though (I tried the firmware update after reading this : https://github.com/esphome/issues/issues/677).

We don't have recommendations in the documentation regarding to do system update for any operating systems. I just assume (hope) that everyone keeps up-to-date their systems with regular security and bugfix updates.
I'm guessing that apt-get installed the latest versions of these packages and the rest of the system was out-of-date and linked against different or older packages.


I can't make it return null

Hello, when I leave the Money input empty instead of returning a null (?) it returns an empty string (' '), and I need it to return null and not an empty string.

Yes, it should probably return null in that case. I will look into this.

Sorry, for not fixing this yet. I have been really busy the last few weeks.
I should be able to fix this next week.

@DevDanielAlvarez Sorry for the delay and thank you for the patience. This should now be fixed in 1.2.1.

Looks like you have fixed the formatting, but this error happens durring the save (resulting in a broken query)
I will supply a simple fix in a PR.
The code works for sure, but i dont know if it is in line with you codestyle. So feel free to change it!

Looks like you have fixed the formatting, but this error happens durring the save (resulting in a broken query) I will supply a simple fix in a PR.
The code works for sure, but i dont know if it is in line with you codestyle. So feel free to change it!
Edit: @pelmered, the PR is submitted.  My bad.
Thanks for the PR. I added a comment there.

Now in version 1.2.2 this should finally be fixed.


feat: support sessions & remove expiring app property

Description
This adds support for sessions in the dotnet SDK, & remove the CanCreateExpiringApplications property from Applications

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.45.0 :tada:
The release is available on:

v1.45.0
GitHub release

Your semantic-release bot :package::rocket:


Getting "LoadError" when trying to use the gem as dependency

I'm trying to use langchainrb gem, which has tiktoken_rb as a dependency. I'm getting a LoadError when trying to use the gem:
LoadError - cannot load such file -- /gems/ruby/3.0.0/gems/tiktoken_ruby-0.0.5-x86_64-linux-musl/lib/tiktoken_ruby/tiktoken_ruby:
 |   tiktoken_ruby-0.0.5-x86_64-linux (musl) lib/tiktoken_ruby.rb:10:in `require_relative'
 |   tiktoken_ruby-0.0.5-x86_64-linux (musl) lib/tiktoken_ruby.rb:10:in `rescue in <top (required)>'
 |   tiktoken_ruby-0.0.5-x86_64-linux (musl) lib/tiktoken_ruby.rb:6:in `<top (required)>'

Is this something I can get help with? Thanks!

I had the same issue. Ended up forking langchainrb and removing the tiktoken dep

@weilandia I had gone ahead and demoted tiktoken to an optional dep: https://github.com/patterns-ai-core/langchainrb/pull/649

I think this is actually fixed on x86_64-linux  so no longer an issue, but nice to be optional.


Fix for RO FSOI diag.bin issue

Update other repos - no change to fixtures:
GEOSana - fix for RO diag.bin error that made FSOI got bad
GMAO_Shared - update restricted RO database (consistent w/ x0046d - summer)
GEOSgcm_App - revise regrid-method for few FP streams
zero diff as long as FSOI is not running; otherwise it fixes an error there.

Thank you.


Syntax and performance questions?

Hello. This seems great, it is very good to have same syntax as underscore.

Is syntax different from https://lodash.com that everyone in javascript world is using now?
Has anyone done performance tests against https://luafun.github.io?

Hi @stuta
Moses have lots of functions which were inspired/taken from lodash. As such, they have a quite similar syntax. Either way, since Moses is Lua and lodash is JavaScript, there are indeed some differences. Check out the tutorial for examples.
Regarding LuaFun, no there are no performance tests comparing Moses to LuaFun that I know of. But I believe on some points, LuaFun might be faster than Moses, since it ws designed with performance in mind and taking advantage of LuaJIT.

I tried this code:

local function filterFn(x)
	return x % 2 == 0
end
local function mapFn(x)
	return x + 0.1
end
local time1 = util.seconds()
local gen1 = fn.iter(arr):filter(filterFn):map(mapFn):take(3):totable()
time1 = util.seconds(time1)
print(string.format('%.6f seconds: %s', time1, table.concat(gen1, ', ')))
local time2 = util.seconds()
local gen2 = _(arr):filter(filterFn):map(mapFn):take(3):value()
time2 = util.seconds(time2)
print(string.format('%.6f seconds: %s', time2, table.concat(gen2, ', ')))
print(string.format("time1: %.6f / time2: %.6f, luafun is %.0f times faster than moses", time1, time2, time2/time1))

Result is different (filter is not working?), maybe I'm doing something wrong in moses?
0.000043 seconds: 2.1, 4.1, 6.1
0.943609 seconds: 1.1, 2.1, 3.1
time1: 0.000043 / time2: 0.943609, luafun is 21730 times faster than moses

I refactored the code.
Luajit 5.1:
0.000062 seconds: 2.1, 4.1, 6.1
3.179571 seconds: 2.1, 4.1, 6.1
time1: 0.000062 / time2: 3.179571, luafun is 51283 times faster than moses

Luajit 2.1 git:
0.000051 seconds: 2.1, 4.1, 6.1
0.958241 seconds: 2.1, 4.1, 6.1
time1: 0.000051 / time2: 0.958241, luafun is 18789 times faster than moses

There are some differences in times when running multiple times. Luafun does this lazily so the jit compiler does not kick in in 3 loops and luajit vs lua5.1 times are equal (depending on the run, times are very small).
Luafun is not maintained any more. If community could take all the good parts from there to moses it would be very good library.

Fixed code:
local _ = require "moses" -- https://github.com/Yonaba/Moses/blob/master/doc/tutorial.md
local fn = require "luafun" -- https://github.com/rtsisyk/luafun
local function filterFn(x)
  return x % 2 == 0
end
local function mapFn(x)
  return x + 0.1
end
local function filterFn2(_, x)
  return x % 2 == 0
end
local function mapFn2(_, x)
  return x + 0.1
end
local time1 = os.clock()
local gen1 = fn.iter(arr):filter(filterFn):map(mapFn):take(3):totable()
time1 = os.clock() - time1
print(string.format('%.6f seconds: %s', time1, table.concat(gen1, ', ')))
local time2 = os.clock()
local gen2 = _(arr):filter(filterFn2):map(mapFn2):take(3):value()
time2 = os.clock() - time2
print(string.format('%.6f seconds: %s', time2, table.concat(gen2, ', ')))
print(string.format("time1: %.6f / time2: %.6f, luafun is %.0f times faster than moses", time1, time2, time2/time1))

Since a specific error was not reported here, I will close this issue.
Thanks.


Remove RequestContext.current global and logging from BentleyError constructor.

The global variable RequestContext.current was used for "magic" logging of RPC requests. That was very problematic due to async methods. It meant that any async code had to keep a static variable "current". Logging for unhandled exceptions from RPC is now automatically handled in the RPC layer, so the static variable is no longer necessary. For performance/trace logging, code must pass the "context" information it wishes to log - it is no longer "magically" appended.

The base exception class BentleyError used to accept an argument for Logger and would log a message in the constructor. This was a very bad idea since it generated log messages for exceptions that were later handled and therefore should not be noticeable in the logs. That argument has been removed, and logging for exceptions should always happen when they're caught but unexpected.

continued cleanup of methods on DgnDb:
a) that accepted stringified JSON
b) that returned a status rather than throwing an exception
c) renamed methods for iModelId, iTwinId, and changeset as appropriate

Depends on #193625

I'm about confused about the usage of IModelHost.session. Wouldn't we always want that sessionId to be the one coming in via the RPC request, otherwise default it to the one supplied during IModelHost.startup?
If so, the handful of places that IModelHost.session is used may not work correctly when it's called via an incoming request. Unless I'm missing something about how we'll handle/update it in RpcInvocation.

@kabentley ah okay, that makes sense. So we're splitting up the areas that can be called from the frontend vs. something that's only callable by the backend.

We could just pass a constant string rather than one that's unique every session. I considered that, and may that would be preferable, just so there's no confusion.

I like that each "session" (which in this case is each time IModelHost.startup is run) will be a different id, that will help separate logs between different Agent runs or different backend instances that are the exact same otherwise.

@kabentley ah okay, that makes sense. So we're splitting up the areas that can be called from the frontend vs. something that's only callable by the backend.

We could just pass a constant string rather than one that's unique every session. I considered that, and may that would be preferable, just so there's no confusion.

I like that each "session" (which in this case is each time IModelHost.startup is run) will be a different id, that will help separate logs between different Agent runs or different backend instances that are the exact same otherwise.

(I hate that GitHub won't let you have a threaded discussion except by commenting on code - that's why i commented that way).
It isn't that we're "splitting up areas that can be called from the frontend". It's that there's only a very few interfaces that are callable from RPC. They're easily identified because you have to register them. Knowing whether something originates from RPC or not is important because only then do we know that:

the iModel is always readonly and can't accept changesets
there can be more than one frontend connected with simultaneous activity
the backend can't trust anything about the frontends

For IPC, there's always one frontend paired and trusted by the backend. The functions here can be "called from the frontend", just not an RPC frontend. HTH

NextVersion.md?

pushed. Needs a learning article, but I decided not to spend too much time on this now since very few consumers write backend code yet (and almost none write backend RPC code)

@Mergifyio update


Interface check for friends depends on current working directory

guido@fox:~/r/fstar/master(master)$ ./bin/fstar.exe examples/micro-benchmarks/friends/1/FriendConsumer.fst
examples/micro-benchmarks/friends/1/FriendConsumer.fst(17,0-17,21): (Error 310) 'friend' declarations are not allowed in modules that lack interfaces
1 error was reported (see above)

guido@fox:~/r/fstar/master/examples/micro-benchmarks/friends/1(master)$ ../../../../bin/fstar.exe FriendConsumer.fst
FriendProvider.fst(0,0-0,0): (Warning 241) Unable to load FriendProvider.fst.checked since checked file FriendProvider.fst.checked does not exist; will recheck FriendProvider.fst (suppressing this warning for further modules)
Verified module: FriendConsumer (336 milliseconds)
All verification conditions discharged successfully

I think both of these should succeed.

Isn't this just a dependency analysis issue, in that in the first case you don't have examples/micro-benchmarks/friends/1/ on your include path, but in the second, you do, because the current directory is always on the include path?

That seems consistent with the behavior of --include semantics and dependency analysis and which files are discoverable (at least to me).


Update checkstyle dtd urls

Import checkstyle dtds from https://checkstyle.org for secure issue, related with https://github.com/checkstyle/checkstyle/issues/6478

Codecov Report

Merging #593 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #593   +/-   ##
========================================
  Coverage    36.05%   36.05%
========================================
  Files           73       73
  Lines         2832     2832
  Branches       387      387
========================================
  Hits          1021     1021
  Misses        1732     1732
  Partials        79       79

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 a8664c0...2f47567. Read the comment docs.


Highlighting completion state

I'm not quite sure how this is supposed to work, so I'm probably missing some ingenious feature here..
But to me the highlighting on the first word of the command seems a bit random. For example if I type mplayer, it stays yellow/underlined until I type the r, then turns green. When I type pidgin, it turns red after typing the g, and then green when the whole word is there. What's that supposed to tell me?
My suggestion would be to leave the word white by default, change it to red if it doesn't match anything in the path (i.e. pressing <tab> gives you nothing), and green if it's a valid command. Now that we have the yellow color freed up, we can use that to indicate when there is a unique completion already matching our command (telling me I can simply press <tab> now), and maybe even something else to "warn" me that I typed more than would strictly be necessary for a unique completion)
For example, pidg<tab> completes to pidgin, so pid should be white (since it has other possible completions like pidof), pidg yellow (now I can simply press <tab>), pidgi magenta (or whatever, to tell me I wouldn't have had to type that last character) and pidgin green.

But to me the highlighting on the first word of the command seems a bit random. For example if I type mplayer, it stays yellow/underlined until I type the r, then turns green. When I type pidgin, it turns red after typing the g, and then green when the whole word is there. What's that supposed to tell me?

I guess your cwd is ~ when you try this. When you type mplaye (sic), that helpfully gets matched against your ~/.mplayer directory and highlighted as yellow+underline by the path_approx style. Pidgin isn't affected because it uses ~/.purple.
The yellow underline is path_approx highlighting, which has no right to kick in for the command word, unless the "approximately spelled file" is a executable, or is a readable directory and AUTO_CD is set. So that's a bug.
In any case, I like your suggestion of revisiting the command-word highlighting. What possible states need the highlighting distinguish?
How about [valid command / invalid command] × [unique completion / ambiguous completion]? All four combinations (valid/unique, valid/ambiguous, invalid/unique, invalid/ambiguous) are possible. "Ambiguous" would mean that there is more than one possible completion, including the word-so-far itself, that is a valid command word (e.g., vi is ambiguous since either vi or vim could be intended). If the command word is valid and the cursor isn't inside the command word, then the "unambiguous" variant would be used. There is a fifth option, "invalid command / no completions", which would be red/bold like today.
Does that sounds like a good specification? Does it cover all cases?
Are there other variables the command word's highlighting should depend on? For example, the kind of the potential completions (whether they are aliases or functions or external commands, etc)?

The yellow underline is path_approx highlighting, which has no right to kick in for the command word, unless the "approximately spelled file" is a executable, or is a readable directory and AUTO_CD is set. So that's a bug.

Now tracked as #187.

path_approx has been removed (see #187).

5 years later and this still hasn't been implemented yet?  I can see this is somewhat true for paths to files/directories (if I'm in ~ and start typing Downloads, it will be green/underlined, and when I type Downloadsx it turns red), but this is untrue for commands (e.g. if I type ifconfi the text is red,  and only turns green when I type ifconfig).
It seems like https://github.com/zsh-users/zsh-syntax-highlighting/pull/152 and https://github.com/zsh-users/zsh-syntax-highlighting/pull/244 were attempting to solve it, but has not been merged

@vegerot Feel free to start a design discussion if you're interested in helping make this happen.  Sorry for the late reply.

@danielshahaf thank you!  I don't really know how to go about doing that.

@vegerot That's not hard.  We hold discussions on github (IRC is doable too).  Just propose a user-facing behaviour.  For example, how should ifconfi be highlighted?  What's the general rule?
(Don't worry about implementation right now; just about observable behaviour.)

Cross-referencing #695.


Warden Env up no such service: php-fpm

I was trying to run warden env up  on my local Mac book pro on Mojave (10.4.6) and getting the following error.
It also showed that it successfully created php debug and php-fpm
$ warden env up
Connecting traefik to maste_default network
Connecting tunnel to maste_default network
Connecting mailhog to maste_default network
[+] Running 9/9
 ⠿ Container maste-redis-1             Running                                                                                0.0s
 ⠿ Container maste-elasticsearch-hq-1  Running                                                                                0.0s
 ⠿ Container maste-elasticsearch-1     Running                                                                                0.0s
 ⠿ Container maste-db-1                Running                                                                                0.0s
 ⠿ Container maste-rabbitmq-1          Running                                                                                0.0s
 ⠿ Container maste-php-fpm-1           Running                                                                                0.0s
 ⠿ Container maste-php-debug-1         Running                                                                                0.0s
 ⠿ Container maste-nginx-1             Running                                                                                0.0s
 ⠿ Container maste-varnish-1           Running                                                                                0.0s
no such service: php-fpm

$ warden shell
service "php-fpm" is not running container #1

How do I ensure that the service php-fpm runs?

+1 same here on the latest warden, latest Monterey on M1

Solved:
I had the following config:
WARDEN_ENV_NAME=customer.tld
TRAEFIK_DOMAIN=customer.tld.test
Switched it to:
WARDEN_ENV_NAME=customer
TRAEFIK_DOMAIN=customer.test
System is no up and running after warden env up
So, apparently, no extra dots like adding tld schema is allowed in both env vars. We should wether update the documentation, add some troubleshooting or declare this as an issue and solve this.
@davidalger your choice?

I am getting this error on running warden shell command service
"php-fpm" is not running
I am trying to setup maento 2.4.6 -p2 using warden setup
can anyone help me with this

@navarr  Please check I am sharing you result of above command  warden env logs php-fpm

php-fpm-1  | sendmail_path = "/usr/local/bin/mhsendmail --smtp-addr='mailhog:1025'"
php-fpm-1  |   installing : node-v12.22.12
php-fpm-1  |        mkdir : /usr/local/n/versions/node/12.22.12
php-fpm-1  |        fetch : https://nodejs.org/dist/v12.22.12/node-v12.22.12-linux-x64.tar.gz
php-fpm-1  |      copying : node/12.22.12
php-fpm-1  |    installed : v12.22.12 to /usr/local/bin/node
php-fpm-1  |       active : v16.20.2 at /bin/node
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: fpm is running, pid 1
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: ready to handle connections
php-fpm-1  | [19-Apr-2024 14:03:48] NOTICE: systemd monitor interval set to 10000ms
php-fpm-1  | sendmail_path = "/usr/local/bin/mhsendmail --smtp-addr='mailhog:1025'"
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: fpm is running, pid 1
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: ready to handle connections
php-fpm-1  | [20-Apr-2024 11:31:21] NOTICE: systemd monitor interval set to 10000ms


Adds mispelled service:bicycle tags

Since version 2.23 iD adds the tag
service:bicycle:bicycle_sales_and_service
instead of the common spelling
service:bicycle:Bicycle_Sales_and_Service
Might be related to https://github.com/openstreetmap/id-tagging-schema/issues/654

fixed in dcd7fb493

As far as I remember, this specific tag was introduced by iD itself in 2017, without discussion (as was common at this time).
I don't think this tag makes much sense and should be replaced by the common, regular tags
service:bicycle:sales
service:bicycle:service
Until then I suggest to keep the uppercase spelling and not introduce a new, lowercase spelling.

As far as I remember, this specific tag was introduced by iD itself in 2017, without discussion (as was common at this time).

I don’t think iD ever had any code specifically about “bicycle sales and service”, however capitalized. Originally, it only had separate, hardcoded fields for service:bicycle:chain_tool and service:bicycle:pump. When the service field was later implemented in a6cf49db8008ca6013ab66eb977b4df7efc1c8f1, its definition looked like this:
https://github.com/openstreetmap/iD/blob/8aca4f820d515355ea4276665e51650283dd9396/data/presets/fields/service/bicycle.json#L1-L5
Whatever taginfo reported as common service:bicycle:* values would’ve shown up in the field. The key’s linear growth is probably a result of mappers seeing that value in the taginfo-based suggestions after this field was deployed as part of v2.0.0 sometime in late 2017, well after the key came into use. iD didn’t used to have very stringent filters on these suggestions, after all.


convert docs Dockerfiles to use docs/base:oss

speeds up make docs, and reduces the svn checkout timeout issue.

tested, LGTM
we should try to get those base images a bit smaller, some layers are really huge

author LGTM, and merging


fix bug with Damage Force particle parameters

getting a null exception on this method when DamageForce is passed

this is only happening with MC heroes. I'll add this patch under MC for now.


tmpdir is hardcoded to /tmp

The tmpdir for all MySQL instances is hardcoded to "/tmp", and doesn't seem to have any way to reset it. This is breaking down badly on VM's provisioned with modest "/" partitions, and generous "/var/lib/mysql-default" partitions configured precisely for the database.
Unfortunately, I'm not confident enough in rewriting the LWRP library functions to turn this into an attribute that is manageable for individual instances, or whether it should be a universal attribute.

Hi Nico.
This falls under https://github.com/chef-cookbooks/mysql/issues/281
I'm planning on fixing that up in the next feature release.
Overriding it with an mysql_config resource is the best thing to do for now.

#281


dominance graph

@Changhe160

i can't receive email timely, so i would like to discuss the problem here

Sorry that I got meeting for the whole day.  How's it going on?

the new version has been tested and uploaded

See my comments.


NIFI-12162 Upgrade Netty from 4.1.98 to 4.1.99

Summary
NIFI-12162 Upgrades Netty from 4.1.98 to 4.1.99 correcting an issue when running on Java 21.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

on it will merge shortly


Support compression of large gRPC messages directly in client/server

For potentially large messages such as ListIndexesMetadataResponse, IndexesMetadataResponse, etc., some fields are compressed/decompressed ad hoc. We would like the RPC framework to take care of that for us.
Since tonic does not support per method compression/decompression, one solution could be to rely on a custom Codec.

quickwit-oss/quickwit-datasource#131


Exercise Tracker microservices test broken

Affected page
https://www.freecodecamp.org/learn/back-end-development-and-apis/back-end-development-and-apis-projects/exercise-tracker
Solution link
https://replit.com/@ankitkandari/freecodecamp-exercisetracker
Forum link
https://forum.freecodecamp.org/t/exercise-tracker-test-broken-for-date-to-be-string/491710
Expected behavior
Test should be passed as no issue in data
Failing test
The date property of any object in the log array that is returned from GET /api/users/:id/logs should be a string… Use the dateString format of the Date API.
Unable to pass this test.
Please help

Exercise tracker test broken

Hi there, it looks like you successfully received guidance on your forum post.
We'll go ahead and close this issue. Making a forum post for questions about your code is the way to go 🙂


python311Packages.pyinstrument: 4.5.3 -> 4.6.0

Diff: https://github.com/joerick/pyinstrument/compare/refs/tags/v4.5.3...v4.6.0
Changelog: https://github.com/joerick/pyinstrument/releases/tag/v4.6.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 265451 run on x86_64-linux 1

2 packages failed to build:

baserow
baserow.dist

12 packages built:

python310Packages.coffea
python310Packages.coffea.dist
python310Packages.pyinstrument
python310Packages.pyinstrument.dist
python310Packages.strawberry-graphql
python310Packages.strawberry-graphql.dist
python311Packages.coffea
python311Packages.coffea.dist
python311Packages.pyinstrument
python311Packages.pyinstrument.dist
python311Packages.strawberry-graphql
python311Packages.strawberry-graphql.dist


BUG/API: QuarterBegin n=0 #11406

closes #11406 - makes QuarterBegin for n=0 match Month/Year.
xref #11427 - once this is merged the failures there should pass - there is also a little more documentation about general offset semantics in that PR.

cc @cancan101
cc @seth-p
look ok to you?

Looks fine to me,  though I don't recall ever commenting on offsets.
On Dec 7, 2015, at 1:24 PM, Jeff Reback <notifications<EMAIL_ADDRESS>wrote:
cc @cancan101https://github.com/cancan101
cc @seth-phttps://github.com/seth-p
look ok to you?

Reply to this email directly or view it on GitHubhttps://github.com/pydata/pandas/pull/11777#issuecomment-162493690.

From #8435 does this now return something sensible?
pd.Timestamp('11/2/2012', tz='US/Eastern') + pd.tseries.offsets.QuarterBegin()
Out[29]: Timestamp('2012-12-01 00:00:00-0500', tz='US/Eastern')
pd.Timestamp('11/2/2012', tz='US/Eastern') + pd.tseries.offsets.QuarterEnd()
Out[30]: Timestamp('2012-12-31 00:00:00-0500', tz='US/Eastern')

cc @MichaelWS

Looks sensible to me

@rockg I believe that @chris-b1 next PR, #11370 wiill address that (and is dependent on this PR)

merged via https://github.com/pydata/pandas/commit/56fd4e34a1d8ec8e82bcaa37ba0237ec94431834
thanks!


Setup on windows :ImportError: No module named 'spacy.attrs'

Hi
I tried to setup the code on windows 7 professional version with 64 bit.
I used chocolatey to install python  and then use following steps in command prompt
 cd <sourcecode directory>
 python -m pip install -U pip virtualenv
 git clone https://github.com/spacy-io/spaCy.git

 #activate .env
 virtualenv .env
 .env\Scripts\activate

 cd spaCy
 pip install -r requirements.txt

 pip install spaCy

 #install model
 sputnik --name spacy --repository-url http://index.spacy.io install en==1.1.0

 python -c "import spacy; spacy.load('en'); print('OK')"

However i am getting error  "ImportError: No module named 'spacy.attrs' "
Details
Traceback (most recent call last):
File "", line 1, in
File "D:\spacy.io\code\test\spaCy\spacy_init_.py", line 3, in
from .util import set_lang_class, get_lang_class
File "D:\spacy.io\code\test\spaCy\spacy\util.py", line 9, in
from .attrs import TAG, HEAD, DEP, ENT_IOB, ENT_TYPE
ImportError: No module named 'spacy.attrs'
what am i missing ?
Also, does anyone know steps to open this project in visual studio 2015?
Vishal

Figured out I forgot  "pip install e."
For anyone who is interested in setting up this on windows ( I used win 7 with 64 bit), here are steps
a. Goto command line (open in admin previlliages ) and run following to install Chocolatey
@powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object
System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH
%;%ALLUSERSPROFILE%\chocolatey\bin"
b. Use Chocolatey To install python :  It installs in C:\ProgramData\chocolatey\lib\python3
cinst python
c. Create a source directory for spacy code and then
cd
d. Setup virtual environment framework
python -m pip install -U pip virtualenv
e. Get git code
git clone https://github.com/spacy-io/spaCy.git
f. setup virutal enviornment name .env
virtualenv .env
g. activate .env and run remaining instllation steps of spacy
.env\Scripts\activate
cd spaCy
pip install -r requirements.txt
pip install spaCy
sputnik --name spacy --repository-url http://index.spacy.io install en==1.1.0
pip install -e .
h. check success to see 'OK'
python -c "import spacy; spacy.load('en'); print('OK')"
###########################
I still need to figure out how to open this project in VS 2015.
In case anyone knows it, please let me know.


fix(proxy) set http_if_terminated false by default

Summary
Assume a (very mildly) more agressive posture by disabling interpretation of the X-Forwarded-Proto header in HTTPS-only APIs by default when the client sent a plaintext connection. This does not improve any functional posturing in the analysis of plaintext connections, but it does require that operators explicitly set this value (and thus assumedly understand the current implications of such a configuration)
Full changelog

Set the http_if_terminated API schema member to false by default.

Issues resolved
Fix #2583

LGTM @p0pr0ck5


Switch to Noble for Rolling.

  /usr/bin/bash -c source /opt/ros/rolling/setup.sh && colcon coveragepy-result --packages-select libstatistics_collector --verbose --coverage-report-args -m
  /usr/local/lib/python3.12/dist-packages/colcon_core/argument_parser/type_collector.py:9: UserWarning: 'colcon_core.argument_parser.type_collector.TypeCollectorDecorator' has been deprecated
    class TypeCollectorDecorator(ArgumentParserDecorator):
  /usr/local/lib/python3.12/dist-packages/colcon_core/argument_parser/type_collector.py:62: UserWarning: 'colcon_core.argument_parser.type_collector.SuppressTypeConversions' has been deprecated, use 'colcon_core.argument_parser.action_collector.SuppressTypeConversions' instead
    class SuppressTypeConversions:
  usage: colcon [-h] [--log-base LOG_BASE] [--log-level LOG_LEVEL]
                {build,coveragepy-result,extension-points,extensions,graph,info,lcov-result,list,metadata,mixin,test,test-result,version-check}
                ...
  colcon: error: unrecognized arguments: -m

This was just fixed and I just created a new release, so I'll try to re-trigger the job.

Warning: Unexpected input(s) 'colcon-mixin-name'

This needs to be replaced by colcon-defaults (#591), e.g.: https://github.com/ros2/ros2_tracing/blob/c0e59c442e61f6c638f06a48a00ecf10913442fb/.github/workflows/test.yml#L76

Whooppee!  It works, finally.  @christophebedard I could use review when you have a minute.

Thanks, appreciated!  With that, I'm going to merge this in since it only touched the github jobs and not the code at all.


Refactor webhook payload convertion

As title.

Codecov Report

Merging #12310 into master will increase coverage by 0.07%.
The diff coverage is 16.50%.

@@            Coverage Diff             @@
##           master   #12310      +/-   ##
==========================================
+ Coverage   43.32%   43.39%   +0.07%
==========================================
  Files         646      647       +1
  Lines       71625    71487     -138
==========================================
- Hits        31028    31023       -5
+ Misses      35582    35442     -140
- Partials     5015     5022       +7

Impacted Files
Coverage Δ

modules/webhook/discord.go
1.93% <0.00%> (+0.15%)
:arrow_up:

modules/webhook/feishu.go
0.00% <0.00%> (ø)

modules/webhook/msteams.go
0.00% <0.00%> (ø)

modules/webhook/payloader.go
0.00% <0.00%> (ø)

modules/webhook/telegram.go
4.62% <5.55%> (+0.87%)
:arrow_up:

modules/webhook/dingtalk.go
6.81% <6.66%> (+0.84%)
:arrow_up:

modules/webhook/slack.go
30.00% <32.00%> (+2.85%)
:arrow_up:

modules/webhook/matrix.go
34.96% <47.22%> (+4.66%)
:arrow_up:

modules/util/timer.go
42.85% <0.00%> (-42.86%)
:arrow_down:

modules/indexer/stats/db.go
43.47% <0.00%> (-17.40%)
:arrow_down:

... and 13 more

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 e1535c7...0c3a8cf. Read the comment docs.


System.IO.IOException: 'unexpected packet in stream: ' for Public-Key Encrypted Session Key

When I try to read a PGP message which contains a Public-Key Encrypted Session Key I get the error message: System.IO.IOException: 'unexpected packet in stream: '
With the following PGP message in binary format: [193,94,3,45,185,208,183,54,93,229,221,18,1,7,64,28,103,55,88,116,186,18,206,0,68,88,68,101,113,237,234,176,198,229,155,232,35,103,18,53,238,124,136,130,107,16,39,48,117,235,162,201,115,115,33,123,66,54,129,185,141,193,85,212,0,144,107,119,41,49,156,58,202,104,246,181,75,204,33,225,194,14,97,208,97,244,248,98,56,44,70,139,155,79,26,239]
I expect the following code snippet to correctly parse the message:
MemoryStream contentKeyPacket_ms = new MemoryStream(new byte[] { 193, 94, 3, 45, 185, 208, 183, 54, 93, 229, 221, 18, 1, 7, 64, 28, 103, 55, 88, 116, 186, 18, 206, 0, 68, 88, 68, 101, 113, 237, 234, 176, 198, 229, 155, 232, 35, 103, 18, 53, 238, 124, 136, 130, 107, 16, 39, 48, 117, 235, 162, 201, 115, 115, 33, 123, 66, 54, 129, 185, 141, 193, 85, 212, 0, 144, 107, 119, 41, 49, 156, 58, 202, 104, 246, 181, 75, 204, 33, 225, 194, 14, 97, 208, 97, 244, 248, 98, 56, 44, 70, 139, 155, 79, 26, 239 });
Stream contentKeyPacket_s = PgpUtilities.GetDecoderStream(contentKeyPacket_ms);
PgpObjectFactory fac = new PgpObjectFactory(contentKeyPacket_s);
PgpObject nextObj = fac.NextPgpObject() => throws the error

The same PGP message can correctly be parsed using openpgp.js readMessage() function.

The data appears to contain only an isolated "Public-Key Encrypted Session Key Packets (Tag 1)", which we can parse.
However the PgpObjectFactory is processing higher-level constructs, in this case a PgpEncryptedDataList, which is one or more session keys followed by a data packet (being the data encrypted by the session key).
I suppose if you want to parse individual packets for yourself you should be using BcpgInputStream directly.

Thanks for that clarification.
Can you please advice on how to create a BcpgInputStream? It doesn't seem to have any public constructor and I also can't extract it from the PgpObjectFactory object.
Thank you,

Sorry yeah, it's actually not designed to be exposed, I spoke too soon. I guess you could propose some change to support just low-level packet parsing, but it's not really what the current API is designed for. Also it's better for us to drive OpenPGP changes from the bc-java version, which is usually ahead of the bc-csharp one.

Thanks for your answer. I ended up going in the other direction and appending the encrypted data packet to the encrypted session key and I got successful results from the NextPgpObject() function. (I also managed to decrypt the data packet which is what I was looking to do all along.)
Thanks again for pointing that out it helped me tremendously.


subsys: settings: nvs: use dedicated lookup cache hash function

NVS lookup cache currently uses CRC8/16 as a hash function to determine the cache position for the given NVS ID. When NVS is used as the settings backend, this often results in costly collisions between rarely written keys and more frequently written values. Such collisions can significantly increase the time to discover NVS ID for the given key.
Overall, CRC8/16 should probably be replaced with a better integer hash function, but when NVS is used as the settings backend, a dedicated hash function can result in almost zero collisions given the way the backend allocates NVS IDs to keys and values. Add a way to inject a custom hash function for the lookup cache and provide a hash function for settings. In our test scenarios, it helped significantly: e.g. the boot time in one scenario was reduced from 15s to 1s.
Additionally, add a test case to verify that the default hash function is not extremely bad, and update the existing test cases.

@Damian-Nordic, I haven't gone through the PR but is this method going to work when the nvs system is used for both nvs user writes (id 0-32767) and nvs settings writes (32768-...) ?

The new method allows one to specify a hash function per NVS instance. Is writing user NVS IDs to the settings NVS supported? I assumed it's not as the NVS is owned by the settings backend, but let me know if this I'm wrong and if this is documented somewhere. But if you're asking if it's going to work when one NVS instance is used for settings and another one for user entries, then the answer is 'yes'.

@Damian-Nordic, writing user nvs id's to the settings nvs instance is supported.

@Laczen Can you point me where this is documented? But in any case, my solution may not be suitable for user NVS IDs as we don't know the distribution of those, so for user writes a generic hash function is probably a better choice. Thus, I may need to add a Kconfig for this feature as I don't know how to solve this differently in an elegant way.

@Laczen Can you point me where this is documented? But in any case, my solution may not be suitable for user NVS IDs as we don't know the distribution of those, so for user writes a generic hash function is probably a better choice. Thus, I may need to add a Kconfig for this feature as I don't know how to solve this differently in an elegant way.

The settings subsystem has a routine to get the backend. This can be used to retrieve the nvs file system that is used for settings and can then be used to store data: https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/settings/src/settings_nvs.c#L403.
It is definitively needed to take that into account in the cache lookup (returning invalid position in case the id is less than 0x32768).
I am still hesitant about adding yet another cache method and I'm wondering what the newly proposed cache method really means and then what its implications might be. I am wondering if the proposed method is only good at the start but as gc is being done the behavior is actually worsened.

@Laczen I'm not adding yet another cache method but trying to improve the hash function based on the knowledge about the distribution of input values (how the settings NVS backend allocates NVS IDs). The GC shouldn't have any impact on the cache behavior. What could have an impact is adding lots of settings keys and then removing most of them. That could leave a lot of gaps in the 0x8000-0xc000 NVS ID range and that would contradict the assumption of the proposed hash function that NVS IDs are allocated sequentially. But that rarely happens in practice.
Maybe I will first propose another PR to replace CRC8/16 with something that better resembles a random permutation as that should help in all scenarios.

IMO gc will have influence as it will move older id's to the front of the fs and change what is in the cache table.
IIRC your use case uses the settings subsystem mainly as a key-value store and does a lot of retrieval by key. I have created an out of tree real key value store for zephyr (https://github.com/Laczen/kvs). This provides a direct routine to retrieve the value for a specific key but it also has settings support (of course with worse direct retrieval performance because this is not how settings is intended to be used).

@Laczen I have created another PR to simply replace CRC with a better hash function: https://github.com/zephyrproject-rtos/zephyr/pull/61643 and I will close this PR for now given that I haven't taken into account those user writes to the settings NVS. Maybe we will have to apply this patch in our project only when we know that a customer doesn't use NVS directly.
We have seen your KVS implementation and it's great that you started working on this. I may have some comments regarding this solution when I get back from vacation but overall it would be great to have a solution that is more suitable for a dynamic key-value store that is mandatory in modern application stacks. This doesn't change the situation to existing devices in the field so we still have to make sure that the settings over NVS is efficient for some time.


UraniumUI.Material conflicts with CommunityToolkit.Maui.SourceGenerators

I don't have CommunityToolkit as far as I know I've looked into the nugets and I could not find it, but still I am getting this conflict I couldn't pin point from where its coming.
I am not even using the timepicker control.
Any ideas?
best regards.
Severity	Code	Description	Project	File	Line	Suppression State
Warning	CS0436	The type 'ColorAnimationExtensions_TimePicker' in 'CommunityToolkit.Maui.SourceGenerators\CommunityToolkit.Maui.SourceGenerators.Generators.TextColorToGenerator\TimePickerTextColorTo.g.shared.cs' conflicts with the imported type 'ColorAnimationExtensions_TimePicker' in 'UraniumUI.Material, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'CommunityToolkit.Maui.SourceGenerators\CommunityToolkit.Maui.SourceGenerators.Generators.TextColorToGenerator\TimePickerTextColorTo.g.shared.cs'.	TestProject (net7.0-android)	F:\Projects\TestProject\TestProject\CommunityToolkit.Maui.SourceGenerators\CommunityToolkit.Maui.SourceGenerators.Generators.TextColorToGenerator\TimePickerTextColorTo.g.shared.cs	41	Active

UraniumUI uses. version 3.0.0 of communitytoolkit
https://github.com/enisn/UraniumUI/blob/ac2ab07e826b0ba0fb19c0df622070baf8581b08/src/UraniumUI/UraniumUI.csproj#L26
If you're installed it manually into your project with a different version it can make a conflict.
By the way it already comes with UraniumUI, you don't need to add it manually again.

In addition I have also tried with the preview in hope it was something todo with .net 6 vs 7 and the result was the same with stable and preview on .net 7

CommunityToolKit package has been separated, so I'm closing this issue. Feel free to re-open if same error occurs


Namespace is not being emitted to openapi

When I have a below sample model created in typespec then when we run the npx cadl compile command to emit this model to open api I have noticed the namespace is not being emitted.
_namespace test.test1.test2 {
model user {
s: string;
}
}_
However when we specify a file based namespace (sample below) then the namespace is being emitted to open api
_namespace test.test1.test2;
namespace test.test1.test2 {
model user {
s: string;
}

}_

Hey @darshanbhoir07  do you have @service on your namespace? This is how it discover how to include a namespace or not for an http service.
If you are still having issue can you send a repro using the playground https://cadlplayground.z22.web.core.windows.net/


reconcile code review and refactor

Signed-off-by: 662962756<EMAIL_ADDRESS>

 Code review for -reconcile


Update init.py - bringing PR over from OG repo

async_get_registry was deprecated and removed in hass 2023.5.0. This imports async_get instead and requires only this modification to work in 2023.5.0

PR has changes already fixed by PR #6


refactor(tabs): updated to new tab design

closes: #1855
Tabs component preview
https://patternfly-next-pr-2757.surge.sh/documentation/core/components/tabs
Breaking changes

Removed .pf-m-start
Removed .pf-m-end
Removed .pf-m-start-current
Removed .pf-m-end-current
Removed --pf-c-tabs__item--BorderColor
Removed --pf-c-tabs__item--m-current--ZIndex
Removed --pf-c-tabs__item--m-current--Color
Removed --pf-c-tabs__item--m-current--BorderTopWidth
Removed --pf-c-tabs__item--hover--Color
Removed --pf-c-tabs__button--Color
Removed --pf-c-tabs__button--PaddingRight
Removed --pf-c-tabs__button--PaddingLeft
Removed --pf-c-tabs__scroll-button--Widtht
Removed --pf-c-tabs__scroll-button--ZIndex
Removed --pf-c-tabs__scroll-button--m-secondary--hover--Color
Removed --pf-c-tabs__scroll-button--m-secondary-right--m-start-current--Color
Removed --pf-c-tabs__scroll-button--m-secondary--nth-of-type-1--BoxShadow
Removed --pf-c-tabs__scroll-button--m-secondary--nth-of-type-2--BoxShadow

Moved item border to button::before border
Scroll buttons are inline with items rather than above

Preview: https://patternfly-next-pr-2757.surge.sh

Did the change to the secondary color go through yet? @mattnolting the inactive text color and border color is #737679 instead of #6A6E73.
And also the divider lines should be pf-global-black-300 #d2d2d2
I can review the rest later tonight

@ajacobs21e All that looks correct to me

Hey @mattnolting I took a closer look at everything and compared it to the design. Here are my review notes, I think some you already addressed but I'll leave it here to include everything. Thanks!

attribute
design
implementation

default "compact" sizinghorizontal tabs
16px 16px 16px 16px
missing 16 32 16 32 is the comfortable "chonky" version

borders
pf-global-black-300
#737679 (old secondary color)

hover color
pf-global-black-400
pf-global-black-300

Leading/trailing linesvertical open tabs
24px
none

Leading/trailing linesvertical box tabs
32px
none

Filled horizontal box tabs

missing

Mobile spacing
8px 16px 8px 16px
missing

Overflow arrow default color
pf-global-clolor-100
#737679 (old secondary color)

Inset style &tabs with sub tabs
not requested from our side so have no specs

@coreyvickery

@ajacobs21e is there a state for when the vertical nav is taller than the vertical window?

@christiemolloy on the web we'd want to use the browser scroll rather than overflow arrows or something like that

Sorry everyone, the lint error was failing any new builds, so the preview wasn't reflective of your requested changes. Preview should be responding now.

Should there be a max-width on the tabs component so that if the text is really long it would truncate?

left border isn't lining up to the lines

Will we allow inset with scroll buttons? Maybe we should make a note about whether they should be used together or not

Is it possible to add scroll buttons to the sub-nav? I know this was an accessibility/usability issue initially, because since the scroll bar is hidden, users need a way to know if there are more elements or not.

Is it possible to add scroll buttons to the sub-nav? I know this was an accessibility/usability issue initially, because since the scroll bar is hidden, users need a way to know if there are more elements or not.

@christiemolloy yes, the default pf-c-tabs scroll buttons can be added

Should there be a max-width on the tabs component so that if the text is really long it would truncate?

@mcarrano wdyt? max-width and truncation?

I'd prefer max-width and text wrapping, assuming that each application can set what the max width is

@mattnolting this looks good to me! Just left some comments. I'll wait until it's approved and ready to merge to review the breaking changes in the description.

Thanks Matt!


Char/String builtins for the Lurk Transpiler

Closes #171.

TODO: Add the num and char special functions to our interpreter. To be done in later PR
TODO: Similar builtins for UInt32 and Fin. To be done in later PR
Seal off more core API for String and List, wherever we can be way more efficient

We can now move on to greater heights!

Apologies as this is not the cleanest PR... but essentially the most important bit is in LurkFunctions.lean and Transpiler.lean; everything else is sort of collateral damage from me trying to fix bugs/test things/just other stuff.


Is there a way we can directly ping the API so it sends us a notification whenever slots are available in our desired pin-code?

Govt closed the API, very little that I can do right now!