[FEAT] Create a DIContext like is doing in @tsed/common

Information
Is your feature request related to a problem? Please describe.
Create context will allow to use @InjectContext in CLI context. The CLI logger will be attached to the DIContext and an ID will be generated to trace the log in a logger management. Also the cli arguments can be retrieved through the DIContext.
Acceptance criteria

[ ] DIContext is consumable in any services

released


yesterday's commit introduced a bug

Error detected while processing TextChangedI Autocommands for "*":
Error executing lua callback: .../nvim/site/pack/packer/start/nvim-cmp/lua/cmp/source.lua:325: attempt to call method 'com
plete' (a nil value)
stack traceback:
.../nvim/site/pack/packer/start/nvim-cmp/lua/cmp/source.lua:325: in function 'complete'
...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:289: in function 'complete'
...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:169: in function 'callback'
...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:219: in function 'autoindent'
...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:161: in function 'on_change'
...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/init.lua:313: in function 'callback'
...ite/pack/packer/start/nvim-cmp/lua/cmp/utils/autocmd.lua:49: in function 'emit'
...ite/pack/packer/start/nvim-cmp/lua/cmp/utils/autocmd.lua:23: in function <...ite/pack/packer/start/nvim-cmp/lua
/cmp/utils/autocmd.lua:22>

Can you provide any info on how to reproduce this? I haven't seen this error so far.

I saw this when still had hrsh7th/cmp-copilot installed.  Once removed, all was well.

Closing because this ins't reproducible and is caused by a plugin conflict


[SPARK-20005][WEB UI]fix 'There is no "Newline" in UI in describtion'.

What changes were proposed in this pull request?
Before I fix this issue, if the describtion is too long, the content is still displayed on a line, causing the cell to be stretched indefinitely. The UI page is very ugly.
Add a css class, if the overdone is too long, I will automatically intercept the string, with '...' to replace, if the user wants to see more detailed in the word, you can double click to describtion, then more lines show the detail of describtion, then the UI page comparison Regular.
Please refer to the attachment of issue 'SPARK-20005',before_fix_jobs.png, before_fix_stages.png and after_fix_jobs.png, after_fix_stages.png.
issue url:https://issues.apache.org/jira/browse/SPARK-20005.
How was this patch tested?
manual tests
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

@srowen
Look at the attachment of 'SPARK-20005', you know what happened.
sorry,this is Unrelated. I merge code is error about docs/monitoring.md.

Ping @guoxiaolongzte to fix or close but i'm not yet clear this does only what you intend.
CC @ajbozarth

@ajbozarth

Does the PR nobody deal with it?@srowen

@guoxiaolongzte I'm not sure what you're asking. It is up to you to fix this pull request, or else close it if you're not going to.


Failed to open /dev/dri/renderD128 as DRM device node.

Hey!
Thanks for this awesome tool (as far a I can tell based on the concept). Unfortunately I'm unable to start it up.
Everything seems fine until I receive FFmpeg process has exited.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.low viseron0
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes
************************ UID/GID *************************
User uid:    911
User gid:    911
************************** Done **************************
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-set-env-vars: executing...
****** Checking for hardware acceleration platforms ******
OpenCL is available!
VA-API is available!
CUDA cannot be used
*********************** Done *****************************
[cont-init.d] 30-check-if-rpi: executing...
********** Checking if we are running on an RPi **********
Not running on any supported RPi
*********************** Done *****************************
[cont-init.d] 30-check-if-rpi: exited 0.
[cont-init.d] 40-gid-video-device: executing...
[cont-init.d] 40-gid-video-device: exited 0.
[cont-init.d] 50-edgetpu-permission: executing...
/var/run/s6/etc/cont-init.d/50-edgetpu-permission: line 3: lsusb: command not found
stat: cannot stat '/dev/bus/usb//': No such file or directory
groupmod: invalid group ID ''
[cont-init.d] 50-edgetpu-permission: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-05-15 10:17:11] [viseron                 ] [INFO    ] - -------------------------------------------
[2021-05-15 10:17:11] [viseron                 ] [INFO    ] - Initializing...
[2021-05-15 10:17:11] [viseron                 ] [DEBUG   ] - Starting cleanup scheduler
[2021-05-15 10:17:11] [viseron                 ] [DEBUG   ] - Running initial cleanup
[2021-05-15 10:17:11] [viseron.cleanup         ] [DEBUG   ] - Running cleanup
[2021-05-15 10:17:11] [viseron.detector        ] [DEBUG   ] - Initializing object detector darknet
[2021-05-15 10:17:14] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic */frame/scan/object, <queue.Queue object at 0x7fe820bf6e80>
[2021-05-15 10:17:14] [viseron.detector        ] [DEBUG   ] - Object detector initialized
[2021-05-15 10:17:14] [viseron                 ] [INFO    ] - Initializing NVR threads
[2021-05-15 10:17:14] [viseron.nvr.frontdoor   ] [DEBUG   ] - Initializing NVR thread
[2021-05-15 10:17:14] [viseron.camera.frontdoor] [DEBUG   ] - Initializing camera Frontdoor
[2021-05-15 10:17:14] [viseron.camera.frontdoor] [DEBUG   ] - Getting stream information for rtsp://*****:*****@****//h264Preview_01_sub
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Stream information from FFprobe: Width: 640 Height: 480 FPS: 0 Video Codec: h264 Audio Codec: aac
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Resolution: 640x480 @ 7 FPS
[2021-05-15 10:17:31] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/decode/object, <queue.Queue object at 0x7fe820c1d820>
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Starting decoder thread
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Running decoder frontdoor.object_detection at 1.0s interval, every 7.0 frame(s)
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Camera Frontdoor initialized
[2021-05-15 10:17:31] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/processed/object, <queue.Queue object at 0x7fe820c1d2b0>
[2021-05-15 10:17:31] [viseron.motion.frontdoor] [DEBUG   ] - Initializing motion detector
[2021-05-15 10:17:31] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/decode/motion, <queue.Queue object at 0x7fe8203a9580>
[2021-05-15 10:17:31] [viseron.motion.frontdoor] [DEBUG   ] - Starting decoder thread
[2021-05-15 10:17:31] [viseron.motion.frontdoor] [DEBUG   ] - Running decoder frontdoor.motion_detection at 1.0s interval, every 7.0 frame(s)
[2021-05-15 10:17:31] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/scan/motion, <queue.Queue object at 0x7fe8203a9040>
[2021-05-15 10:17:31] [viseron.motion.frontdoor] [DEBUG   ] - Motion detector initialized
[2021-05-15 10:17:31] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/processed/motion, <queue.Queue object at 0x7fe820c1dd90>
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - Starting capture thread
[2021-05-15 10:17:31] [viseron.recorder.frontdoor] [DEBUG   ] - Initializing ffmpeg recorder
[2021-05-15 10:17:31] [viseron.recorder.frontdoor] [DEBUG   ] - Creating folder /segments/Frontdoor
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [DEBUG   ] - FFMPEG decoder command: ffmpeg -hide_banner -loglevel debug -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -rtsp_transport tcp -i rtsp://*****:*****@***//h264Preview_01_sub -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a copy /segments/Frontdoor/%Y%m%d%H%M%S.mp4 -filter:v fps=1 -f rawvideo -pix_fmt nv12 pipe:1
[2021-05-15 10:17:31] [viseron.nvr.frontdoor   ] [DEBUG   ] - NVR thread initialized
[2021-05-15 10:17:31] [viseron.nvr.frontdoor   ] [DEBUG   ] - Waiting for first frame
[2021-05-15 10:17:31] [viseron                 ] [INFO    ] - Initialization complete
Splitting the commandline.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-avoid_negative_ts' ... matched as AVOption 'avoid_negative_ts' with argument 'make_zero'.
Reading option '-fflags' ... matched as AVOption 'fflags' with argument 'nobuffer'.
Reading option '-flags' ... matched as AVOption 'flags' with argument 'low_delay'.
Reading option '-strict' ...Routing option strict to both codec and muxer layer
 matched as AVOption 'strict' with argument 'experimental'.
Reading option '-fflags' ... matched as AVOption 'fflags' with argument '+genpts'.
Reading option '-use_wallclock_as_timestamps' ... matched as AVOption 'use_wallclock_as_timestamps' with argument '1'.
Reading option '-vsync' ... matched as option 'vsync' (video sync method) with argument '0'.
Reading option '-stimeout' ... matched as AVOption 'stimeout' with argument '5000000'.
Reading option '-hwaccel' ... matched as option 'hwaccel' (use HW accelerated decoding) with argument 'vaapi'.
Reading option '-rtsp_transport' ... matched as AVOption 'rtsp_transport' with argument 'tcp'.
Reading option '-i' ... matched as input url with argument 'rtsp://*******//h264Preview_01_sub'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'segment'.
Reading option '-segment_time' ... matched as AVOption 'segment_time' with argument '5'.
Reading option '-reset_timestamps' ... matched as AVOption 'reset_timestamps' with argument '1'.
Reading option '-strftime' ... matched as AVOption 'strftime' with argument '1'.
Reading option '-c:v' ... matched as option 'c' (codec name) with argument 'copy'.
Reading option '-c:a' ... matched as option 'c' (codec name) with argument 'copy'.
Reading option '/segments/Frontdoor/%Y%m%d%H%M%S.mp4' ... matched as output url.
[AVHWDeviceContext @ 0x557a2bf20980] Failed to open /dev/dri/renderD128 as DRM device node.
[AVHWDeviceContext @ 0x557a2bf20980] No VA display found for device /dev/dri/renderD128.
[2021-05-15 10:17:31] [viseron.camera.frontdoor] [ERROR   ] - FFmpeg process has exited

docker-compose.yml
version: "3.7"
services:
  viseron01:
    image: roflcoopter/viseron:dev
    container_name: viseron01
    volumes:
      - "viseron/recordings:/recordings"
      - "viseron/config:/config"
      - "/etc/localtime:/etc/localtime:ro"
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size:<PHONE_NUMBER>
    devices:
      - /dev/dri/renderD128
    restart: unless-stopped
    ports:
      - 8888
    deploy:
      resources:
        limits:
          memory: 1024M

config.yml
cameras:
  - name: Frontdoor
    mqtt_name: viseron_frontdoor
    stream_format: rtsp
    host: ***
    port: 554
    username: ***
    password: "***"
    path: //h264Preview_01_sub
    width: 640
    height: 480
    fps: 7
    ffmpeg_loglevel: debug
logging:
  level: debug

Same setup works fine with frigate (/dev/dri/renderD128,...).
I noticed this log entry, could that mean something? groupmod: invalid group ID ''
Any idea what I can try?

Does it work if you add this?
    environment:
      - PUID=0
      - PGID=0

If so i need to take a look at why permissions arent set properly.
Also the groupmod: invalid group ID '' is a bug introduced by the latest pull but it should not affect the video devices.

@roflcoopter wow that was fast!
Seems to work, thanks!

[AVHWFramesContext @ 0x560968283300] Map surface 0x4000012.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000012.

[AVHWFramesContext @ 0x560968283300] Map surface 0x4000013.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000013.

[AVHWFramesContext @ 0x560968283300] Map surface 0x4000012.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000012.

[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000013.
[Parsed_fps_0 @ 0x560968402400] Read frame with in pts 4596230, out pts 51
[segment @ 0x5609682d4dc0] stream:1 start_pts_time:45.5467 pts:814158 pts_time:50.8849 dts:814158 dts_time:50.8849 -> pts:85410 pts_time:5.33812 dts:85410 dts_time:5.33812
[segment @ 0x5609682d4dc0] stream:1 start_pts_time:45.5467 pts:815251 pts_time:50.9532 dts:815251 dts_time:50.9532 -> pts:86503 pts_time:5.40644 dts:86503 dts_time:5.40644
[segment @ 0x5609682d4dc0] stream:1 start_pts_time:45.5467 pts:816171 pts_time:51.0107 dts:816171 dts_time:51.0107 -> pts:87423 pts_time:5.46394 dts:87423 dts_time:5.46394
[segment @ 0x5609682d4dc0] stream:0 start_pts_time:45.5467 pts:4596230 pts_time:51.0692 dts:4596230 dts_time:51.0692 -> pts:497025 pts_time:5.5225 dts:497025 dts_time:5.5225
[h264 @ 0x56096827ce80] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 1
[h264 @ 0x56096827ce80] Param buffer (type 0, 672 bytes) is 0x8000000.
[h264 @ 0x56096827ce80] Param buffer (type 1, 240 bytes) is 0x8000001.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000012.

[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000013.

[AVHWFramesContext @ 0x560968283300] Map surface 0x4000012.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000012.
[Parsed_fps_0 @ 0x560968402400] Read frame with in pts 4632641, out pts 51
[Parsed_fps_0 @ 0x560968402400] Dropping frame with pts 51
[segment @ 0x5609682d4dc0] stream:0 start_pts_time:45.5467 pts:4632641 pts_time:51.4738 dts:4632641 dts_time:51.4738 -> pts:533436 pts_time:5.92707 dts:533436 dts_time:5.92707
[h264 @ 0x56096827ce80] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 1
[h264 @ 0x56096827ce80] Param buffer (type 0, 672 bytes) is 0x8000003.
[h264 @ 0x56096827ce80] Param buffer (type 1, 240 bytes) is 0x8000002.
[AVHWFramesContext @ 0x560968283300] Map surface 0x4000013.
[AVHWFramesContext @ 0x560968283300] Unmap surface 0x4000013.

Unfortunately I'm not able to validate if it works correctly, because the Web UI doesn't seem to work.
Any quick fix? Otherwise I can just open another issue, because this error seems to be fixed :)
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/tornado/web.py", line 1681, in _execute
    result = self.prepare()
  File "/usr/local/lib/python3.8/dist-packages/tornado/web.py", line 2430, in prepare
    raise HTTPError(self._status_code)
tornado.web.HTTPError: HTTP 404: Not Found

Great! For me it works even tho i dont run as root.
Could you start the container again without the environment part and paste the output of these commands?
docker exec -it viseron01 ls -lh /dev/dri
docker exec -it viseron01 id abc
ALso about the webserver, what endpoint are you trying to hit?

 No endpoint just :8888 (through Traefik). Thought there's some kind of basic UI.
 No endpoint just :8888 (through Traefik). Thought there's some kind of basic UI.
Same 404 Error with /frontdoor/stream

I think you cut out some of the output from vainfo.
Ahh i see, sadly there is no UI yet. This is something i am planning but its not in the works yet.
/frontdoor/mjpeg-stream should work but i just realized there is a regression in :dev that breaks it

updated

Thanks, the permissions looks correct to me.
You can see that renderD128 is in the root group, and user abc is in the root group.

Can you also run ls -lh /dev/dri on the host for me?

crw------- 1 root root 226,   0 May 15 01:14 card0
crw------- 1 root root 226, 128 May 15 01:14 renderD128

Fixed the regression with the stream endpoint in dev, you can see when the build is finished here:
https://dev.azure.com/jespernilsson93/Viseron Pipelines/_build

Currently it doesn't progress after Getting stream information :sweat_smile:
[2021-05-15 13:06:03] [viseron                 ] [INFO    ] - -------------------------------------------
[2021-05-15 13:06:03] [viseron                 ] [INFO    ] - Initializing...
[2021-05-15 13:06:03] [viseron                 ] [DEBUG   ] - Starting cleanup scheduler
[2021-05-15 13:06:03] [viseron                 ] [DEBUG   ] - Running initial cleanup
[2021-05-15 13:06:03] [viseron.cleanup         ] [DEBUG   ] - Running cleanup
[2021-05-15 13:06:03] [viseron.detector        ] [DEBUG   ] - Initializing object detector darknet
[2021-05-15 13:06:03] [viseron.detector        ] [DEBUG   ] - OpenCL activated
[2021-05-15 13:06:05] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic */frame/scan/object, <queue.Queue object at 0x7f85b92b1310>
[2021-05-15 13:06:05] [viseron.detector        ] [DEBUG   ] - Object detector initialized
[2021-05-15 13:06:05] [viseron                 ] [INFO    ] - Initializing NVR threads
[2021-05-15 13:06:05] [viseron.nvr.frontdoor   ] [DEBUG   ] - Initializing NVR thread
[2021-05-15 13:06:05] [viseron.camera.frontdoor] [DEBUG   ] - Initializing camera frontdoor
[2021-05-15 13:06:05] [viseron.camera.frontdoor] [DEBUG   ] - Getting stream information for rtsp://*****:*****@****/h264Preview_01_sub

Hmm its just stuck forever there?

Didn't really change something but after some restarts it works. Still trying to figure out what's the issue, mqtt integration, debug mode,...
However if it come up, it doesn't detect any movements (according to mqtt queue)... Will dig deeper later :)

It's ffprobe getting stuck when trying to connect to your camera.
I will add a timeout and some retry logic to get around it

Didn't really change something but after some restarts it works. Still trying to figure out what's the issue, mqtt integration, debug mode,...
However if it come up, it doesn't detect any movements/person objects (according to mqtt queue)... Will dig deeper later :)

Missed the part about no detections, that is strange. Any indications in the log?

Is that the correct state?
************************** Done **************************
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-gid-video-device: executing...
[cont-init.d] 20-gid-video-device: exited 0.
[cont-init.d] 30-edgetpu-permission: executing...
[cont-init.d] 30-edgetpu-permission: exited 0.
[cont-init.d] 40-set-env-vars: executing...
****** Checking for hardware acceleration platforms ******
OpenCL is available!
VA-API is available!
[services.d] done.
[2021-05-15 17:41:35] [viseron                 ] [INFO    ] - -------------------------------------------
[2021-05-15 17:41:35] [viseron                 ] [INFO    ] - Initializing...
[2021-05-15 17:41:35] [viseron                 ] [DEBUG   ] - Starting cleanup scheduler
[2021-05-15 17:41:35] [viseron                 ] [DEBUG   ] - Running initial cleanup
[2021-05-15 17:41:35] [viseron.cleanup         ] [DEBUG   ] - Running cleanup
[2021-05-15 17:41:35] [viseron.mqtt            ] [INFO    ] - Initializing MQTT connection
[2021-05-15 17:41:35] [viseron.detector        ] [DEBUG   ] - Initializing object detector darknet
[2021-05-15 17:41:35] [viseron.detector        ] [DEBUG   ] - OpenCL activated
[2021-05-15 17:41:37] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic */frame/scan/object, <queue.Queue object at 0x7fb074797640>
[2021-05-15 17:41:37] [viseron.detector        ] [DEBUG   ] - Object detector initialized
[2021-05-15 17:41:37] [viseron                 ] [INFO    ] - Initializing NVR threads
[2021-05-15 17:41:37] [viseron.camera.frontdoor] [DEBUG   ] - Initializing camera frontdoor
[2021-05-15 17:41:37] [viseron.camera.frontdoor] [DEBUG   ] - Getting stream information for rtsp://*****:*****@<IP_ADDRESS>:554/h264Preview_01_sub
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Stream information from FFprobe: Width: 640 Height: 480 FPS: 0 Video Codec: h264 Audio Codec: aac
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Resolution: 640x480 @ 7 FPS
[2021-05-15 17:41:53] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/decode/object, <queue.Queue object at 0x7fb0747ac6a0>
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Starting decoder thread
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Running decoder frontdoor.object_detection at 1s interval, every 7 frame(s)
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Camera frontdoor initialized
[2021-05-15 17:41:53] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/processed/object, <queue.Queue object at 0x7fb0747ac2e0>
[2021-05-15 17:41:53] [viseron.motion.frontdoor] [DEBUG   ] - Initializing motion detector
[2021-05-15 17:41:53] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/decode/motion, <queue.Queue object at 0x7fb07473a760>
[2021-05-15 17:41:53] [viseron.motion.frontdoor] [DEBUG   ] - Starting decoder thread
[2021-05-15 17:41:53] [viseron.motion.frontdoor] [DEBUG   ] - Running decoder frontdoor.motion_detection at 1s interval, every 7 frame(s)
[2021-05-15 17:41:53] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/scan/motion, <queue.Queue object at 0x7fb07473a220>
[2021-05-15 17:41:53] [viseron.motion.frontdoor] [DEBUG   ] - Motion detector initialized
[2021-05-15 17:41:53] [viseron.data_stream     ] [DEBUG   ] - Subscribing to data topic frontdoor/frame/processed/motion, <queue.Queue object at 0x7fb0747acf40>
[2021-05-15 17:41:53] [viseron.nvr.frontdoor   ] [DEBUG   ] - Starting camera
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - Starting capture thread
[2021-05-15 17:41:53] [viseron.recorder.frontdoor] [DEBUG   ] - Initializing ffmpeg recorder
[2021-05-15 17:41:53] [viseron.recorder.frontdoor] [DEBUG   ] - Creating folder /segments/frontdoor
[2021-05-15 17:41:53] [viseron.camera.frontdoor] [DEBUG   ] - FFMPEG decoder command: ffmpeg -hide_banner -loglevel fatal -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -rtsp_transport udp -i rtsp://*****:*****@****:554/h264Preview_01_sub -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a copy /segments/frontdoor/%Y%m%d%H%M%S.mp4 -filter:v fps=1 -f rawvideo -pix_fmt nv12 pipe:1
[2021-05-15 17:41:53] [viseron.nvr.frontdoor   ] [DEBUG   ] - NVR thread initialized
[2021-05-15 17:41:53] [viseron.mqtt            ] [DEBUG   ] - MQTT connected with returncode 0
[2021-05-15 17:41:53] [viseron.nvr.frontdoor   ] [DEBUG   ] - Waiting for first frame
[2021-05-15 17:41:53] [viseron                 ] [INFO    ] - Initialization complete
[2021-05-15 17:42:02] [viseron.nvr.frontdoor   ] [DEBUG   ] - First frame received
[ WARN:0] global /tmp/opencv/modules/core/src/utils/filesystem.cpp (489) getCacheDirectory Using world accessible cache directory. This may be not secure: /var/tmp/
OpenCV(ocl4dnn): consider to specify kernel configuration cache directory
                 via OPENCV_OCL4DNN_CONFIG_PATH parameter.

mqtt:
  broker: mosquitto01
cameras:
  - name: frontdoor
    mqtt_name: viseron_frontdoor
    stream_format: rtsp
    rtsp_transport: udp
    host: ***
    port: 554
    username: ***
    password: ***
    path: /h264Preview_01_sub
    width: 640
    height: 480
    fps: 7
    #static_mjpeg_streams:
    #  frontdoor-stream:
    #    width: 640
    #    height: 480
    #    draw_objects: True
    motion_detection:
      interval: 1
      trigger_detector: false
    object_detection:
      interval: 1
      labels:
        - label: person
          confidence: 0.7
        - label: pottedplant
          confidence: 0.9
logging:
  level: debug

Just set another log level for FFmpeg
[segment @ 0x55e751e02900] Non-monotonous DTS in output stream 0:1; previous: 2511775, current: 2511773; changing to 2511776. This may result in incorrect timestamps in the output file.
[rtsp @ 0x55e751d99880] max delay reached. need to consume packet
[rtsp @ 0x55e751d99880] RTP: missed 101 packets
[rtsp @ 0x55e751d99880] max delay reached. need to consume packet
[rtsp @ 0x55e751d99880] RTP: missed 278 packets
[rtsp @ 0x55e751d99880] max delay reached. need to consume packet
[rtsp @ 0x55e751d99880] RTP: missed 527 packets
[2021-05-15 20:33:33] [viseron.mqtt            ] [DEBUG   ] - MQTT connected with returncode 0

I dont think you need to worry about those messages from FFmpeg unless the recordings are looking weird.
I noticed you set a limit on the memory of the container, im thinking that could be why you are not seeing any detections.
Loading the YOLO model takes quite a bit of memory aswell as keeping some frames in memory

Seems to work, thanks! :)


Makefile: Allow out-of-tree builds

Signed-off-by: Patrick Williams<EMAIL_ADDRESS>

This change is

Bump...

Thanks!


FEATURE: MSF-10828 Add ruby self-service feature to java GoodData SDK

Coverage decreased (-0.6%) to 80.669% when pulling df1e0f4487e62acf4b689807167481631010c74d on Tantalor93:obe-develop into<PHONE_NUMBER>51635b401b77a2ae91b4846803464a on martiner:master.


Populate the lists from a rest call

It would be great to be able to populate the lists via a rest call, so we could always have up to date lists.

Unfortunately this is an extension and not part of the core product. You can certainly make REST calls to get the entire list of values in a picklist.

Just want to confirm I'm following you, is there a way to do a rest call to populate the cascading picklist, or are you saying just for a normal picklist.  The use case is I have a CRM system that we pull our customers from and based on the customer I want a list of the custom products they have.  So parent picklist is Customer and child(cascaded pick list) is product.


Navigation is generating additional module

After generating the documentation, there is an additional entry called "module:app" in the navigation. I dont want it there and I do not even have a module called like this.
In particular the "module: app" with the "overview" and the subpoint "home" appears. But I'd like to have the point "overview" in the "module: app.home". How can I achieve this?

/**
 * @ngdoc overview
 * @name app.home
 * @description This module is very important
 */
angular.module('app.home', [])

    /**
     * @ngdoc controller
     * @name HomeCtrl
     * @memberOf app.home
     * @description controller returns 'hello world'
     * @param $scope {service} controller scope
     * @param $q {service} promise service
     */
    .controller('HomeCtrl', /*@ngInject*/ ["$scope", function ($scope, $q) {

        /**
         * @memberOf HomeCtrl
         * @function helloWorld
         * @description Returns hello world as a string
         * @returns {String} string
         */
        function helloWorld () {
            return 'hello world';
        }

    }])

    /**
     * @ngdoc controller
     * @name HomeCtrl2
     * @memberOf app.home
     * @description very important controller
     * @param $scope {service} controller scope
     */
    .controller('HomeCtrl2', /*@ngInject*/ ["$scope", function ($scope) {

    }])

/**
 * @ngdoc service
 * @name ImportModal
 * @memberOf app.home
 * @param {service} $q promise service
 * @description Important service
 */
.factory('ImportModal', /*@ngInject*/ function ($q) {
...

I've already tried to add "@memberOf app.home" to the first comment, but that did not work.
Is this a bug, or is it supposed to be that way?

You need to name the overview. When you specify the @name annotation it will assume, that the last part is the name and the part before the point the module it's connected to.
That means you need to set @name like this:
@name app.home.myName


Cherry-pick RDNA1 fix into 6.1 release

This PR requests to cherry-pick #1897 into ROCm 6.1 release.
#1897 enables RDNA1 (gfx101*) users to run rocBLAS with the rocblas package from AMD's official repository. Since rocBLAS is almost ubiquitous in ML workflows, this means that all RDNA1 users are essentially unable to run any programs related to ML right now (ROCm/ROCm#2527).
Admittedly, RDNA1 GPUs are not officially supported, but this is such a small change that would benefit all users of RDNA1 GPUs, so I believe is very worth it.
This is a NFC for all architectures besides gfx1010.
#1897 requires #1888 to function properly, but it seems like #1888 is already cherry-picked into the release/rocm-rel-6.1 branch in #1905, so cherry-picking #1897 would not break anything.

Rocm6.1 release branch is already finalized and no further release plan for 6.1.
This will be included in rocm 6.2.

@nakajee Thank you for your quick response. Would you mind if I create a PR to release-staging/rocm-rel-6.2, or will someone from AMD cherry-pick this internally?

Nevermind, I see this is already included in release-staging/rocm-rel-6.2. Thank you!

Rocm6.1 release branch is already finalized and no further release plan for 6.1.

To be clear, there is a ROCm 6.1.1 release planned. Though, perhaps there are no changes planned for Tensile specifically.
@GZGavinZhao, it is not a simple process to cherry-pick a change into a patch release. There is an internal change management process for cherry-picks. Unfortunately, it is mostly handled manually and it is very time-consuming. And even a small change in Tensile requires retesting a large suite of libraries and applications for performance and correctness.
This is a great PR and it highlights some of the difficulties with the existing cherry-pick process. I'm hopeful we can improve to the point that a PR like this could be accepted in the future.

@cgmb I see. I understand that the cherry-picking process may require extensive testing, hence this PR is more of a request to cherry-pick. I thought that maybe some Tensile changes are planned for the next patch release, so if this change can be considered together that'd be great, but releasing in ROCm 6.2 is totally fine as well. Anyway, Thank you so much for your explanation!


Open WidgetInspectorService APIs to use by package/devtools extensions authors

Use case
My team and I are building a new package and devtools extension, that would highly benefit from the ability to tell which widget from the local project corresponds to a specific coordinate on screen - exactly like the WidgetInspector does with the "Select Widget" feature.
My first thought was to learn how it's implemented in WidgetInspector and try to tap into the same APIs, but I quickly learned that those APIs clearly were not meant to be called from the "outside", and while I was able to work my way around their limitations, it's very hacky and definitely not the intended way to do it.
The issue I'm facing is that most of the WidgetInspectorService methods are either private or protected. The class is designed in such a way, that a lot of methods that return some useful data are private and have their protected counterpart that converts their return value into JSON for transfer to devtools. For example:
  String getChildrenSummaryTree(String diagnosticsNodeId, String groupName) {
    return _safeJsonEncode(_getChildrenSummaryTree(diagnosticsNodeId, groupName));
  }

and
List<Object> _getChildrenSummaryTree(String? diagnosticableId, String groupName) {
    final DiagnosticsNode? node = _idToDiagnosticsNode(diagnosticableId);
    if (node == null) {
      return <Object>[];
    }

    final InspectorSerializationDelegate delegate = InspectorSerializationDelegate(groupName: groupName, summaryTree: true, service: this);
    return _nodesToJson(_getChildrenFiltered(node, delegate), delegate, parent: node);
  }

And if we assume that the devtools is the only consumer of that data, then it's perfectly understandable why it was designed that way. But since it's all protected or private, there's no "right" way for external packages to check whether a specific widget was created by local project.
I think it basically comes down to a single small method within WidgetInspectorService, that allows for checking the object creation location:
_Location? _getObjectCreationLocation(Object object) {
  return object is _HasCreationLocation ? object._location : null;
}

And since the _HasCreationLocation class doesn't seem to be explicitly used anywhere else I can only assume that it is somehow dynamically added to objects by the engine in runtime.
Proposal
My proposal is to either open up the WidgetInspectorService APIs to allow package authors to tap into the methods it provides, or even just allow the _HasCreationLocation class to be used outside of the WidgetInspector environment by making it public.
I'm aware this is a rather niche feature request that wouldn't be used by many developers, but if there's no significant arguments against it, I'd be happy to prepare a PR with a proposal of how the updated API could look like.

I think the framework team doesn't own the WidgetInspector, the devtool team does. Assigning to tool team for now, please reassign accordingly.
cc @kenzieschmoll


⚠ Bofrost.at has degraded performance

In 5378248, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3180 ms

Resolved: Bofrost.at performance has improved in 97462ed.


Write a test and build action

To figure out why things are being packaged incorrectly. Same as publish, but without publishing.

Closed in 797e074b4a6cf079d899fa31fe330155a02a2fac


Distance from an quic-tls draft 11 implementation

Hi quic-go maintainers,
I am working on a go implementation of a modified version of QUIC. However the modification requires at minimum a draft 11 implementation to build off of. Your project seems to be the most mature quic implementation in go I was able to find, but it seems that it has not reached the feature set of draft 11 yet.
I was wondering if you have a rough idea where the quic-go project is in terms of having all the functionality of a draft 11 implementation, or which draft you would say the project is closest to.
Thanks,
Alishah

We’re not aiming to implement a specific draft version, but to follow the current version of the draft. Since there were some big changes recently, a lot of work is needed to catch up. I’d say quic-go is roughly between 11 and 12 at the moment.
Which feature of draft 11 do you need that quic-go doesn’t implement yet?

Thank you for your response. The main features I need are those that relate to the handshake and packet protection. I saw that encrypted packet numbers are still an open issue, so I thought that there might be other features of draft 11 not yet implemented.

I’ve been working on packet number encryption, but it’s complicated... however, this should only matter if you’re trying to interop with other implementations of the working group draft (which will likely fail because we’re already implementing some changes after draft-11).

I misread the changelog, encrypted packet numbers are a draft 11 feature. I will keep an eye out, but at least for now I don't see other draft 11 features that I need not implemented yet.
I am hoping to interop with other wg implementations. My current objective is to be able to successfully handshake with another draft 11 implementation. Do you know some of the post draft 11 changes that have been implemented?

I don't see a lot of value in doing interop with an outdated draft version. If you think this is worth pursuing, you'll have to go through the commit history and figure out the changes yourself.


AppDetails Screenshot resizing and animation

Linked issue: https://github.com/d4rken/reddit-android-appstore/issues/141
Added functionality to resize screenshot area in AppDetails based on width and height of screenshots. Also added simple slide in/out animations for screenshots

Thanks for the contribution!


The operator should receive a human-readable error if region is invalid

A user on the bosh slack specified "us-east" instead of "us-east-1" as the region in their manifest. Instead of a human-readable error (e.g. "Invalid region 'us-east'"), they received this:
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3012'... Failed (00:00:05)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Command 'deploy' failed:
  creating stemcell (bosh-aws-xen-hvm-ubuntu-trusty-go_agent 3012):
    CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"getaddrinfo: nodename nor servname provided, or not known","ok_to_retry":false}

Steps to reproduce at the unit level:
provider = AWS::Core::CredentialProviders::StaticProvider.new(:access_key_id => 'ACCESS_KEY', :secret_access_key => "SECRET_KEY")
client = AWS::EC2.new(:credential_provider => provider, :region => 'bogus')
client.regions.first

Output:
SocketError: getaddrinfo: nodename nor servname provided, or not known

+1 from the bosh mailing list. Search for "[cf-bosh] bosh-init on AWS failed"

I think this was improved in v52 and can be closed.


(PUP-11771) Rubocop Naming Cops

This PR comprises commits to address Rubocop naming cops and associated issues.

@joshcooper Thanks for the review, I've reverted the issues you've flagged

Ah sorry, the Naming/PredicateName cop is confusing... I was hoping to keep the is_XXX? and has_XXX? methods as is. But if there's a private is_XXX/has_XXX method, then renaming/appending ? sounds good. And if the method is public, then skip the cop like you're doing sounds good. I think what I'm looking for can be done using and then taking into account whether the method is private:
Naming/PredicateName:
  ForbiddenPrefixes: []

@joshcooper Gotcha, I think I understand now. I've updated my commit with your suggestions. Let me know if I can make any other changes.


StageGL: BitmapText Doesn't Call _updateText() on Redraw

So my BitmapText wasn't rendering and I learned that for StageGL canvases the text is never redrawn because _updateText() is never called
For 2D canvases _updateText() is called whenever draw() is called, but StageGL doesn't use draw() so the text is never updated.
During my debug process I also noticed this which gave me a bit of a scare:
https://github.com/CreateJS/EaselJS/blob/5d1d5a2f7dc7a1af963fec9770e474a675c2b060/src/easeljs/display/StageGL.js#L2412
It seems like it might be a lot safer in the long run to enum-ify the _webGLRenderStyle property of each class's prototype. I spent a good 5 hours thinking that's where the problem was only to find out otherwise. There is also not much benefit in looping through an array of classes here in general.
Also btw do you guys have a home for active development discussion like Slack or a discussion board? I know there's a Reddit, Google+, and Twitter but those places seem more appropriate for generic things like questions/announcements, etc. I'm interested in contributing and following along with future developments :)

Here's the callstack by which that function is intended to get called. You might be missing it if you're simply calling "draw" instead of "update", I'll make sure that gets put into the BitmapText documentation.
As for why:
There was a minor change to BitmapText. We used to trigger it's update text inside of the scene-graph walk. As StageGL had it's own way of walking the scene-graph (for optimizations sake) we would either need a special case for only BitmapText (not awesome) or to build in a API by which any DisplayObject could be warned to do a "update". Like an event that it was about to be drawn, so rather than re-invent the wheel I tied it into the existing draw start/end events. This was the same way we're doing the DOMObject, so more consistency and a win all-around. These event listeners are added during the private _tick function, which is again only engaged if you call update rather than draw.
So everything should work smoothly if you're calling update, which should be what most of our demos show. If it isn't or you've got some ideas feel free to get back to us. I'll get the documentation fixed so others don't have the same mystery.

Also re: enumifying the types, that would definitely be a good approach and one I've considered, as you can see there's a comment just above the code showing we're actively considering other alternatives. But there's a few questions internally we haven't decide on answers for to pick the best approach, like how many draw types are there probably ever going to be. When adjusting something that's going to get processed for every object it can have quite the speed impact when you process as many objects as StageGL is intended to, so I don't want to make any poor choices.

@DavidHGillen Thanks for the response, I looked into what you said and it turns out that the reason I wasn't seeing updates was because we set tickEnabled to false globally for performance reasons. And of course since _updateText() is tied to those draw event listeners that explains why it didn't work with the new StageGL. Another note for the docs I suppose!
Also take your time with the enums thing, it was merely a suggestion. Though I don't think you can really go wrong here as long as you keep those values internal to the library. Since there are so few display classes to be concerned with, a good start would probably be to remove that forEach loop in favor of clearly stating what the integers represent in the form of a comment until you decide what to do with it

Closing this, since its not longer relevant with the latest changes. Feel free to reopen if there are still related issues.


Improve HTML

Improved Icon Loading, Scroll-Up Button and Icon Enhancement, Script Section Enhancement, Resolved Hidden FAQ Section Comment #222 #41 #229

@Prerrna why are you working on other peoples issues


Error during installation of version

Tensorflow Extended requires absl-py<0.9,>=0.7.
On my windows machine, however,
pip install absl-py==0.8.1
generates the error
Collecting absl-py==0.8.1
  Using cached absl-py-0.8.1.tar.gz (103 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [21 lines of output]
      Traceback (most recent call last):
        File "c:\Users\z0017fjy\AppData\Local\Programs\Python\Python311\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 353, in <module>
          main()
        File "c:\Users\z0017fjy\AppData\Local\Programs\Python\Python311\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "c:\Users\z0017fjy\AppData\Local\Programs\Python\Python311\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\z0017fjy\AppData\Local\Temp\pip-build-env-d9eghk5s\overlay\Lib\site-packages\setuptools\build_meta.py", line 341, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\z0017fjy\AppData\Local\Temp\pip-build-env-d9eghk5s\overlay\Lib\site-packages\setuptools\build_meta.py", line 323, in _get_build_requires
          self.run_setup()
        File "C:\Users\z0017fjy\AppData\Local\Temp\pip-build-env-d9eghk5s\overlay\Lib\site-packages\setuptools\build_meta.py", line 488, in run_setup
          self).run_setup(setup_script=setup_script)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\z0017fjy\AppData\Local\Temp\pip-build-env-d9eghk5s\overlay\Lib\site-packages\setuptools\build_meta.py", line 338, in run_setup
          exec(code, locals())
        File "<string>", line 34, in <module>
      RuntimeError: Python version 2.7 or 3.4+ is required.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

My python version is
python --version
Python 3.11.2

Which should meet the version requirement 3.4+.
What could be the issue?

This absl-py installation issue in Python 3.10+ has been fixed in #161 and released in absl-py 0.12.0.
Please file an issue in tfx to update the absl-py requirement if they support Python 3.10+.


add option to skip reporting OK status

Closes #43

My impression is that the default behavior should be emitting a report of broken links with a failing exit status code, or no output with a successful exit status code.
To make it clearer what the tool does, we can do the reporting of HTTP 200 statuses in a --verbose option. :thinking:


Flutter (Channel beta, 2.12.0-4.1.pre Add Function

Error: The non-abstract class 'RawEditorState' is missing implementations for these members:

TextInputClient.insertTextPlaceholder
TextInputClient.removeTextPlaceholder

why this pr close?


Serum Integration

Not yet ready, but a preview of what I did for a major refactor along with the skeleton of supporting serum
There are some TODO that I have put in there which should be resolved before submitting

TODOs that I'm stuck on @brittcyr

connect serumvial websocket to forked market
cleanup event listeners to avoid duped threads after re-run & between scalps


GIT versioning management

We have to find a way to merge the changes back into the main branch.

all done.


Fix copy_wget to cope with queries embedded in the source URL

It does this by removing the query.  There doesn't seem to be any
better alternative.  (Why are queries being added anyway?  I don't
see them on TeamCity.)
Note that wget treating queries as part of the filename totally breaks
building Bloom for Linux on Jenkins.  (or on local machines that don't
have curl)

:+1:


Testing: Establishing Load Test Requirements

To design a few meaningful test scripts for our load tests we should establish reasonable performance requirements.
DoD

[ ] motivated list of requirements
[ ] first draft script for a load test (maybe in a form of a new testing ticket) - fetching data from prometheus of how many API call per minute to the KubeAPI server

AC

[ ] performance requirements are documented
[ ] first load tests are sketched

A rough first implementation of how load tests could be executed can be found in the following draft PR: https://github.com/keptn/lifecycle-toolkit/pull/599
In this PR, tests are executed with kube-burner, which might be an interesting choice for doing load tests for Operators, and it also provides a straight forward way to integrate with Prometheus.
As far as the requirements goes, we should always ensure the following:

Number of API Calls should not significantly increase with number of already reconciled objects
Memory Consumption should not significantly increase with number of already reconciled objects
CPU Usage should not significantly increase with number of already reconciled objects

So essentially, the resource footprint should roughly stay the same, regardless if we have a fresh installation or a high number of already reconciled CRDs which do not require any action anymore. E.g.., there should be no endless reconciliation loops for already finished Tasks, Evaluations etc., and memory leaks must be avoided.
Also, as a follow up task we should find the breaking point wrt to how many KLT CRDs we can actively reconcile at the same time in a cluster


Way for users to fetch other users banners

Not entirely sure if this is in Discord API yet, but a .banner command similar in function to .pfp would be neat. (Useable for one's own banner as well as others).
This suggestion was created by a user and sent by the bot:
jukebox-botto#8602

currently not possible

banner should be shown in userinfo


feat: support for new ICD hosting model

Description
Add support for the IBM Cloud Database new hosting model, including bumping minimum memory requirements from 1G to 4G.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
Reference: Cloud Database Hosting Models
The host model switching section has details of the migrations that the service is rolling out. All instances will have to be switched and the time line for the migrations is outlined.
During the transition both existing and new models are supported.
Users of this module should consider the changes being implemented by the service. It is recommended that new deployments use the shared or isolated compute models to start, by specifying the host_flavor. It is recommended that existing deployments make updates to control the upgrade process by specifying shared or isolate compute configurations and the resource required to run the service, by adding the host_flavor.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

The only change during upgrade is the group block and results in an update in-place.
This is expected and the exact details vary by the existing deployment.
existing deployment with less then 4G memory: The group memory block will update in-place to 4G of memory.
existing deployment with 4G plus memory: No change.
existing deployment adding host_flavor (as below): The group memory block will update in-place to the flavor chosen.
The upgrade test is safe to skip
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: Terraform used the selected providers to generate the following execution
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: plan. Resource actions are indicated with the following symbols:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   ~ update in-place
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:  <= read (data resources)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: Terraform will perform the following actions:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   # module.postgresql_db.data.ibm_database_connection.database_connection will be read during apply
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   # (depends on a resource or a module with changes pending)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:  <= data "ibm_database_connection" "database_connection" {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + amqps         = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + analytics     = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + bi_connector  = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + cli           = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + deployment_id = "crn:v1:bluemix:public:databases-for-postgresql:eu-de:a/abac0df06b644a9cabc6e44f55b3880e:03457398-117d-48f4-9836-25a2bdae477f::"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + emp           = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + endpoint_type = "private"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + grpc          = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + https         = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + id            = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + mongodb       = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + mqtts         = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + mysql         = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + ops_manager   = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + postgres      = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + rediss        = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + secure        = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + stomp_ssl     = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + user_id       = "admin"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + user_type     = "database"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:     }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   # module.postgresql_db.ibm_database.postgresql_db will be updated in-place
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   ~ resource "ibm_database" "postgresql_db" {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         id                        = "crn:v1:bluemix:public:databases-for-postgresql:eu-de:a/abac0df06b644a9cabc6e44f55b3880e:03457398-117d-48f4-9836-25a2bdae477f::"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         name                      = "postgres-upg-tweaqu-postgres"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         tags                      = []
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         # (21 unchanged attributes hidden)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       - group {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           - group_id = "member" -> null
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           - cpu {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               - allocation_count = 0 -> null
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           - disk {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               - allocation_mb = 5120 -> null
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           - members {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               - allocation_count = 2 -> null
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           - memory {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               - allocation_mb = 1024 -> null
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + group {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + group_id = "member"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + cpu {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               + allocation_count = 0
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + disk {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               + allocation_mb = 5120
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + host_flavor {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               + id = "multitenant"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + members {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               + allocation_count = 2
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:           + memory {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:               + allocation_mb = 4096
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:             }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:         # (3 unchanged blocks hidden)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:     }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   # module.vpe.data.ibm_is_virtual_endpoint_gateway.vpe["vpe-to-pg-vpc-postgres-upg-tweaqu-postgres"] will be read during apply
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   # (depends on a resource or a module with changes pending)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:  <= data "ibm_is_virtual_endpoint_gateway" "vpe" {
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + access_tags                  = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + allow_dns_resolution_binding = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + created_at                   = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + crn                          = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + health_state                 = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + id                           = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + ips                          = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + lifecycle_state              = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + name                         = "vpe-to-pg-vpc-postgres-upg-tweaqu-postgres"
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + resource_group               = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + resource_type                = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + security_groups              = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + service_endpoints            = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + tags                         = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + target                       = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:       + vpc                          = (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:     }
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: Plan: 0 to add, 1 to change, 0 to destroy.
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: Changes to Outputs:
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   ~ hostname                   = "03457398-117d-48f4-9836-25a2bdae477f.bpb68u2f0gvaqgd0n64g.private.databases.appdomain.cloud" -> (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185:   ~ port                       = 31915 -> (known after apply)
TestRunUpgradeCompleteExample 2024-06-28T08:59:07Z command.go:185: ╷

/run pipeline

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 3.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Quill Custom Toolbar gives addRange(): The given range isn't in document. in React

I copy pasted React example from https://quilljs.com/playground/react and added custom toolbar. To use with custom toolbar I added just module into example. There is no issue onChange function however when I click any item from toolbar (bold, italic) I got addRange(): The given range isn't in document. log and cannot change selected behaviour.
Here is sandbox link -> https://codesandbox.io/p/sandbox/quil-test-d4ngvg?file=%2Fsrc%2FQuill.tsx
version: "quill": "^2.0.2"
Editor.js
import React, { forwardRef, useEffect, useLayoutEffect, useRef } from "react";
import Quill from "quill";

// Editor is an uncontrolled React component
const Editor = forwardRef(
  ({ readOnly, defaultValue, onTextChange, onSelectionChange }, ref) => {
    const containerRef = useRef(null);
    const defaultValueRef = useRef(defaultValue);
    const onTextChangeRef = useRef(onTextChange);
    const onSelectionChangeRef = useRef(onSelectionChange);

    useLayoutEffect(() => {
      onTextChangeRef.current = onTextChange;
      onSelectionChangeRef.current = onSelectionChange;
    });

    useEffect(() => {
      ref.current?.enable(!readOnly);
    }, [ref, readOnly]);

    useEffect(() => {
      const container = containerRef.current;
      const editorContainer = container.appendChild(
        container.ownerDocument.createElement("div")
      );
      const quill = new Quill(editorContainer, {
        modules: {
          toolbar: {
            container: "#toolbar",
          },
        },
        theme: "snow",
      });

      ref.current = quill;

      if (defaultValueRef.current) {
        quill.setContents(defaultValueRef.current);
      }

      quill.on(Quill.events.TEXT_CHANGE, (...args) => {
        onTextChangeRef.current?.(...args);
      });

      quill.on(Quill.events.SELECTION_CHANGE, (...args) => {
        onSelectionChangeRef.current?.(...args);
      });

      return () => {
        ref.current = null;
        container.innerHTML = "";
      };
    }, [ref]);

    return (
      <>

            <button data-testid="bold" className="ql-bold" />
            <button data-testid="italic" className="ql-italic" />

      </>
    );
  }
);

Editor.displayName = "Editor";

export default Editor;

Hello, have you solved this problem?
@ata-wt

@Libpzzz  Unfortunately not.  I switched to another text editor 😐. But I found temp solution for a while to use quill react version but it has deprecation warning. Then found this forked version as a temporary solution.

All right, I'll see if there's any other solution.
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2024年9月20日(星期五) 下午3:49
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [slab/quill] Quill Custom Toolbar gives addRange(): The given range isn't in document. in React (Issue #4343)
@Libpzzz  Unfortunately not.  I switched to another text editor 😐. But I found temp solution for a while to use quill react version but it has deprecation warning. Then found this forked version as a temporary solution.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I am having the same error


Add redis and cache all endpoints that return mostly static data from Directus

Most requests arrive to the same endpoints over and over again, and the data is fetched from Directus over and over again even though the data rarely changes.

https://hapijs.com/tutorials/caching#last-modified would be nice to use, but I'm not getting this information easily at the moment.
See https://github.com/directus/directus/issues/1354

Added redis cache, in services/cache.js


Improve JS Lint rules

Steps to reproduce and a minimal demo of the problem
The rule set is not very complete
Current behavior
e.g. it allows if(..){ or f(..) { or f(..)
Expected/desired behavior
A more complete ruleset.
Other information

Can you provide a more descriptive example since f can be mean a function or an if.
Thank you.

I meant "if", sorry. It's just and example though.
if(..){ or if(..) { or f(..)


Update sbt to 1.5.5

Updates org.scala-sbt:sbt from 1.5.4 to 1.5.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch

Codecov Report

Merging #143 (97378f9) into master (36e79fb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #143   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           48        48
=========================================
  Hits            48        48

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 36e79fb...97378f9. Read the comment docs.


fork processing PMID:28475874

increased mitotic sister chromatid bridge formation during replication fork processing
in which one or more bridges consisting of unresolved intertwined sister chromatids form following replication fork arrest, and persist until mitotic anaphase. Bridges contain dsDNA and RPA-bound ssDNA, and may break, resulting in unequal sister chromatid segregation.
is_a fypo:3586, I think
related synonym: anaphase bridge formation

abolished DNA resection during replication fork processing (cf. fypo:4251)

normal DNA binding during cellular response to DNA damage

increased mitotic sister chromatid bridge formation during replication fork processing FYPO:0006086
abolished DNA resection during replication fork processing FYPO:0006087
normal DNA binding during cellular response to DNA damage FYPO:0006088
edit file: fe081173f5dc5a0e9bd9186dc2d824c47febc5a2
release: 67ce2158e9b9c31c8afe124f60530a6cd4bc743e


[bug] main branch is broken

The current beta OTA causes the critical error

um.. this happens only when OTA update is done from Github Actions. If we do from the console, it works fine even for the same main branch.

I could reproduced if the repo is fresh.
iOS Bundled 106ms node_modules/expo/AppEntry.js (1 module)
 WARN  Require cycle: features/app/index.tsx -> features/app/internals/AppRoot.tsx -> features/app/storybook/index.ts -> features/app/storybook/storybook.requires.ts -> features/feed/FeedItemScreen.stories.tsx -> features/testhelper/index.tsx -> features/testhelper/internals/jest.tsx -> features/app/index.tsx

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 LOG  Storybook: could not find persisted story
 ERROR  system.graphql.relay.UserServiceProviderQuery GraphQL error: Network request failed {
  "request": {
    "endpoint": "http://<IP_ADDRESS>:8080/graphql/v3",
    "body": {
      "query": "query UserServiceProviderQuery {\n  helloproject {\n    ...HelloProjectFragment\n    id\n  }\n  me {\n    ...MeFragment\n    id\n  }\n}\n\nfragment HelloProjectFragment on HelloProjectQuery {\n  artists {\n    id\n    key\n    name\n    thumbnailURL\n    members {\n      id\n      key\n      artistKey\n      artistID\n      name\n      nameKana\n      thumbnailURL\n      dateOfBirth\n      bloodType\n      joinAt\n      graduateAt\n      myFollowStatus {\n        id\n        type\n      }\n    }\n  }\n}\n\nfragment MeFragment on MeQuery {\n  id\n  username\n  clientId\n  clientName\n  sortHistories(first: 2) {\n    edges {\n      node {\n        id\n        createdAt\n        sortResult {\n          records {\n            artistId\n            memberId\n            memberKey\n            point\n            rank\n          }\n        }\n      }\n    }\n  }\n}\n",
      "variables": {}
    }
  },
  "error": {},
  "benchmark": 49768
}
 ERROR  TypeError: Cannot read property 'metadata' of undefined

This error is located at:
    in RenderServiceRootQuery (created by LoadServiceRootQuery)

The root cause is that the GraphQL endpoint is invalid, it should always point to the production.


Added support for JDKW_EXTENSION=bin

This enables installation of JDK6 (using bin extension = executable and self extracting).

Same with this as #12, if you could add a test case to the .travis.yml file I would be happy to merge this. Thanks!

Merged via #18. Closing.


Max Draw Down incorrect

Your MDD function is incorrect.
It only finds the Max return and then the trough after that.
You might be up 10% lose 50% and then gain 1000% to lose 20%.  I believe its written that it would only find that last 20% loss.
Also as per https://www.investopedia.com/terms/m/maximum-drawdown-mdd.asp
you need to divide by the peak value not the Trough
MDD = (Trough Value – Peak Value) ÷ Peak Value
def MDD(returns):
    """Max drawdown."""
    peak = returns.max()
    i = returns.argmax()
    trough = returns[i:].min()
    return (trough - peak) / trough

I found this
def max_drawdown(X):
    mdd = 0
    peak = X[0]
    for x in X:
        if x > peak:
            peak = x
        dd = (peak - x) / peak
        if dd > mdd:
            mdd = dd
    return mdd    ```

From https://stackoverflow.com/questions/22607324/start-end-and-duration-of-maximum-drawdown-in-python

That sounds right, I added your function. Cheer for picking that up.


Add an NVM file

Makes it easier to manage NPM versions when dealing with a lot of legacy projects.

Thank you @whyisjake for your contribution to the California Design System!

The team and I are discussing and testing the implications of using an nvm config file in the design system. Can I ask why you recommended .nvm instead of .nvmrc? The latter is in the nvm docs, but the only mention I could find of the former is in the DreamHost Knowledge Base. We hope to support a variety of platforms and experiences.
We recommend the LTS version of node (currently 16.14.0) and use it locally and in our build servers.
Assuming we make this change, we’ll also need to add instructions to the docs.

Todo

[ ]  Get team approval
[ ]  Add .npmrc to all component packages to set v16.14.0
[ ]  Add instructions for use
[ ]  Add update instructions
[ ]  CRM: Give contact to PMs (let them know who is messaging us) - (or chach automates this with airtable somehow)

Notes for team

The file is ignored until the command nvm use so there won’t be any impact for users who don’t have nvm installed or have to use a different node version due to server requirements.

Another important thing to note is that nvm doesn't really work on Windows. There are alternative tools, like nvm-windows, but they aren't exactly the same. While this is mentioned in the NVM docs, I think it bears repeating here because we'll need to thoroughly test and document the path for Windows devs too.

After some discovery I'm recommending that engineers Volta rather than NVM. It has better Windows support and less mental overhead. Since the config doesn't interfere with other engineers' workflow, we'll take an ad hoc approach to its the use and will continue to recommend the use of the Node LTS version for all our projects.

@zakiya Can we move this to the done column?

yes


Crash on Mac OS for no apparent reason

Jitsi on my Mac crashed for no apparent reason. It was idle and in the background and didn't even received any incoming call.
See attached logs.
BTW I used the latest daily build jitsi-2.11.5593.dmg.

<EMAIL_ADDRESS>

Another crash this morning, a few minutes after my macbook woke up:
<EMAIL_ADDRESS>

@ibauersachs I am willing to help debugging this issue. Do you have any hints or documentation?
Because I have not found any dSYM file generated by your nightly build system, used to symbolicate crash reports.
For Mac OS, should I build through Eclipse and debug from there?


Translation correction.

The word 'Submit' (Enviar) should not be translated into Portuguese because it refers to a code snippet of the button tag.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congratulations on your first merged PR into the freeCodeCamp repo. 🎉🎉🎉🎉🎉


Adding: Wouter Michiel

Onboarding checklist
Welcome @melonora!

[x] add to website: https://github.com/scverse/scverse.github.io/pull/127
[x] add to<EMAIL_ADDRESS>google group. Note: the email address used here will also get access to the shared google drive and calendars (see here)
[x] add to zulip

[ ] @core team
[x] core-team private channel (see here)

[ ] Grant "Leader" trust level on discourse
[ ] add to password manager
[ ] add to github org and scverse/core github team
[x] Add to NumFOCUS slack
[x] Send them link to core team handbook
[ ] announce the new member on twitter

I don't have the permissions to add Wouter to the scverse GitHub organization, could you help please @flying-sheep?

Numfocus can be checked already. Was already there in my role as napari core dev.

@LucaMarconato someone already did!

True @flying-sheep, he is now in the scverse org, thanks for checking. I noticed that he is still not in this list https://github.com/orgs/scverse/teams/core, can you help with that please?

@ivirshup I tried and I think I don't have the permissions to grant the "leader" trust level to Wouter in the discourse. Could you please double check: https://discourse.scverse.org/u/melonora/summary

wouter doesn't appear to have an scverse.org email. @mikelkou could you please add him?

Of course. I need him (@melonora ) to give me a personal email as a backup.

done

email done<EMAIL_ADDRESS>


Expose rewards calculations for tests

looks like this branch may not be needed at all after your changes..

Can we close this then @dkijania ?


config: add support for control plane identifier

Description: Adds support for specifying control plane identifier in Discovery Response and displays it in /configdump( we initially discussed to display in /configdump but later thought it would be as text stat since text stat is taking time I am currently displaying it in `/configdump' and once the text stat is available, will publish it as text stat also).
Risk Level: Low
Testing: Added automated tests
Docs Changes: Added
Release Notes: Updated
Fixes #5770

@fredlas No problem. There are couple of issues with text stat -

Its support in Envoy - which I think can be fixed.
Its support in stats backends - I see that prometheus does not support so as the Metrics.proto we use for Metrics service. I have not checked if statsd supports it or not. So even if we support in Envoy, not sure how many will be able to use it. That is why I am adding it to config dump as well.

@htuch if we want to view all config sources as unordered set, I guess the way is to maintain that static set in grpc_mux_impl - is that fine? Or is there any better way? Or we could pass config source to grpc_mux_impl. But we cannot stitch all of them together as a set - we have display them independently. Let me know if there is a better way

@ramaraochavali I think ConfigTracker is the right approach, you just need to allow for multiple entries for each xDS there.

@htuch Sorry for the delay here. I change the proto a bit to support multiple config sources per service and changed the grpc_mux_impl accordingly. If this is what we want and is in the right direction, I will add few more tests to validate possible combinations.

@fredlas

I realized: it looks like only gRPC xDS is supported here. If nobody who uses REST/filesystem/whatever wants this, then that makes sense.

Yes. That was intentional atleast from my side to just support it for gRPC - and if is useful and want to extend it for other subscriptions, I can do a follow-up

@ramaraochavali let me know if you need anything more from me, otherwise I'll wait for the next patch that addresses ^^

@htuch since we are good with the proto, i will add few more tests and address the other review comments and let you know.

@htuch addressed the review comments and added an integration test in cds. Please take a look. Let me know if we need any additional tests - I was thinking of adding a test that captures two clusters pointing to two different gRPC services for EDS - but seems little difficult to add with current setup. Do you have any suggestions to add it with reasonable effort?

I am busy with other things and could not get it to implementing some of the changes. Will do.

/no stale


Amplify monoRepo + AWS CLI - no support for appRoot when creating a branch.

AWS CLI does not support setting the appRoot when creating an Amplify Branch.
Version:

aws-cli/2.0.46 Python/3.7.4 Darwin/19.6.0 exe/x86_64

  create-branch
          --app-id <value>
          --branch-name <value>
          [--description <value>]
          [--stage <value>]
          [--framework <value>]
          [--enable-notification | --no-enable-notification]
          [--enable-auto-build | --no-enable-auto-build]
          [--environment-variables <value>]
          [--basic-auth-credentials <value>]
          [--enable-basic-auth | --no-enable-basic-auth]
          [--tags <value>]
          [--build-spec <value>]
          [--ttl <value>]
          [--display-name <value>]
          [--enable-pull-request-preview | --no-enable-pull-request-preview]
          [--pull-request-environment-name <value>]
          [--backend-environment-arn <value>]
          [--cli-input-json | --cli-input-yaml]
          [--generate-cli-skeleton <value>]
          [--cli-auto-prompt <value>]

Hi, @divyavanmahajan the amplify console defines how to build your app via the build spec. It looks something like this. This is where we define the appRoot.
version: 1
applications:
  - backend:
      phases:
        build:
          commands:
            - '# Execute Amplify CLI with the helper script'
            - amplifyPush --simple
    frontend:
      phases:
        preBuild:
          commands:
            - npm ci
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: build
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
    appRoot: react-amplify

You can view the build spec via this CLI command aws amplify get-app --app-id [APP-ID] --region [REGION]
To update you can run something like this aws amplify update-app.
See here for syntax details : https://docs.aws.amazon.com/amplify/latest/APIReference/API_UpdateApp.html
References : https://aws.amazon.com/blogs/mobile/set-up-continuous-deployment-and-hosting-for-a-monorepo-with-aws-amplify-console/

Hi @divyavanmahajan  is this still an issue for you?

The comment above is documented and I have used it to create a multi approot amplify build script.
appA
appB
As part of the build I need to create two separate Amplify apps. One for appA and another for appB
What is the CLI to create Amplify app for the approot appA.
What is the CLI to create Amplify app for the approot appB

Hi @divyavanmahajan there is no CLI command specific for monorepos. You would create your apps, and define the monorepo in the amplify.yml like how @nimacks showed.

Jared,
I am not creating a monorepo ( it already exists). The amplify script has multiple appRoots as explained in the monorepo docs.
I am reporting a bug.
In the Web Console - you can enter the folder in a text box when you create the amplify branch
In the CLI/Cloudformation - there no option to specify the folder and the build fails, because the amplify script has appRoots but the branch has no folder specified.
Regards
Divya

On 16. Sep 2020, at 18:38, Jared Franzone<EMAIL_ADDRESS>wrote:

Hi @divyavanmahajan there is no CLI command specific for monorepos. You would create your apps, and define the monorepo in the amplify.yml like how @nimacks showed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@divyavanmahajan Did you end up passing the approot via --environment-variables and the AMPLIFY_MONOREPO_APP_ROOT?
It should be inherited from the environment variables on the application, but if you are moving the application then it should be possible to overwrite the environment variable for the branch.

Hi, we've updated Monorepo feature and you can specify appRoot value using AMPLIFY_MONOREPO_APP_ROOT environment variables
Docs for reference: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html
Feel free to reopen this if issue persists

@victorccccc is it possible to go from monorepo and back again without creating a new project? I tried to remove the MONOREPO env variable - but now I get !!!Invalid monorepo app root, please set correct AMPLIFY_MONOREPO_APP_ROOT environment variable on some builds. Not all but some


Fix panic when region is not found on TiFlash's side in tryFlushData

What problem does this PR solve?
Issue Number: close #5602
Problem Summary:

Region is removed on TiFlash's side, however not on Proxy's side before a restart
Proxy replay log, and ask a flush for a region not exist in TiFlash

Similar to https://kb.pingcap.com/post/articles/92
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/cc @JaySon-Huang @flowbehappy @lidezhu

/run-build-arm64-release comment=true

Why this problem just affect v6.2.0?

Why this problem just affect v6.2.0?

Because in 6.2 we add a tryFlushData to decouple compact log and flushing.

Similar to https://kb.pingcap.com/post/articles/92

The root cause of the problem in this kb is that the data dir for proxy has been changed cause by upgrade. But I think this issue is not caused by the data dir change, but could happen after TiFlash restart several times?

/run-build-arm64-release comment=true

Similar to https://kb.pingcap.com/post/articles/92

The root cause of the problem in this kb is that the data dir for proxy has been changed cause by upgrade. But I think this issue is not caused by the data dir change, but could happen after TiFlash restart several times?

Like the following

TiFlash implementationAdminCmd::ChangePeer::RemoveNode, the persistence is successful after deleting the region.
However, when the proxy persisted meta information to kvdb, the node encountered unexpected downtime.

/run-all-tests

Seems this line https://github.com/pingcap/tiflash/blob/2b8d3566531d12f4f33bdda4dbe9310f3202d478/dbms/src/Storages/Transaction/KVStore.cpp#L348
should be
throw Exception("region not found when trying flush", ErrorCodes::LOGICAL_ERROR);

/run-all-tests

/run-all-tests

/run-unit-test

/merge

/run-unit-test

/run-unit-test


[READY] NPM Module

Above are the files that will be included in the node module via npm install canon-react, dist contains the min version of canon-react and demo contains all the files needed for index.html to display properly (using components defined in canon-react.min.js).
How to use:
Install via npm install canon-react
Where you would like to use react components from canon-react, add var componentName = require('canon-react').componentName;

Can I go ahead and npm publish for testing purposes? I've tested this by installing it globally on my local machine and requiring it from the node terminal so far.

looks pretty good to me, give it a shot!

:+1: :exclamation:

:shipit:


Could not initialize sysparams

Hi. I'm really keen to try the garage example out. On an Ubuntu VM I was able to successfully setup and build the example garage firmware, but it doesn't appear to want to initialize. When I make "test" the result is "Could not initialize sysparams (1)". Any tips? I'm using a Adafruit Feather with the ESP8266 chip. I noticed that there's a wemos.h which I figured I would need to reassign for the feather.
Also, is a home kit .setup pin needed in homekit_server_config_t?
$ make -C examples/garage test
make: Entering directory '/home/chris/Development/esp-homekit-demo/examples/garage'
CC /home/chris/Development/esp-open-rtos/open_esplibs/libmain/timers.c
CC /home/chris/Development/esp-open-rtos/open_esplibs/libmain/ets_timer.c
CC /home/chris/Development/esp-open-rtos/open_esplibs/libmain/spi_flash.c
...
LD build/garage.out
FW firmware/garage.bin
esptool.py v1.2
esptool.py -p /dev/ttyUSB0 --baud 115200 write_flash -fs 32m -fm qio -ff 40m
0x0 /home/chris/Development/esp-open-rtos/bootloader/firmware_prebuilt/rboot.bin 0x1000 /home/chris/Development/esp-open-rtos/bootloader/firmware_prebuilt/blank_config.bin 0x2000 ./firmware/garage.bin
esptool.py v1.2
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0040
Writing 4096 @ 0x0... 4096 (100 %)
Wrote 4096 bytes at 0x0 in 0.4 seconds (89.9 kbit/s)...
Writing 4096 @ 0x1000... 4096 (100 %)
Wrote 4096 bytes at 0x1000 in 0.4 seconds (90.0 kbit/s)...
Writing 434176 @ 0x2000... 434176 (100 %)
Wrote 434176 bytes at 0x2000 in 37.6 seconds (92.3 kbit/s)...
Leaving...
/home/chris/Development/esp-open-rtos//utils/filteroutput.py --port /dev/ttyUSB0 --baud 115200 --elf ./build/garage.out
Opening /dev/ttyUSB0 at 115200bps...
Booting rom 0.
WA�%9� Could not initialize sysparams (1)!
Also, on Ubuntu I had to enable more permissive permissions on ttyUSB to use the make file flash/test options:
$ sudoedit /etc/udev/rules.d/50-myusb.rules
KERNEL=="ttyUSB[0-9]",MODE="0666"
KERNEL=="ttyACM[0-9]",MODE="0666"
You might want to mention something about esptool usually requiring root/sudo.
Thanks for the awesome work!

Try doing make erase_flash first.

I’ll give it a try today. Thanks for the quick reply.
The 2nd part isn’t a question, it’s a documentation suggestion. If,when you try running esptool manually you find you have to sudo, then you’ll need to be more permissive with access to ttyUSB. It isn’t special to a VM (USB is passed through) and the only thing Ubuntu specific is maybe the default direct ttyUSB permissions.

Using "erase_flash" did the trick. I was able to find and add the Garagentor accessory, but I had to "flash" then "monitor" separately. If I "test" the serial output I get dead air. No problem, just letting you know what I experienced. So good progress!
I'm playing with a Adafruit Feather. How does its pins compare to the Wemos D1 pins in the wemos.h? Is there any hardware wiring for the examples provided? I mean there's little word about the Wemos D1 anywhere except the in source, but there are comments about 10k resistors.
I was hoping to add a reed magnetic switch to detect if the garage door was open, and a relay to engage the wiring to the existing wall button.

Try doing make erase_flash first.
For the second question: I'm not aware about inner workings of Ubuntu inside VM and USB support.

I tried to use this solution and received the following message:
vagrant @ vagrant-ubuntu-trusty-64: ~ $ make erase_flash
make: *** No rule to make target `erase_flash '. Stop.

And I found this after "vagrant up"
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.

Another error
vagrant@vagrant-ubuntu-trusty-64:~/esp-homekit-demo$ make -C examples/led test
make: Entering directory /home/vagrant/esp-homekit-demo/examples/led' CC /home/vagrant/esp-open-rtos/open_esplibs/libmain/ets_timer.c make: xtensa-lx106-elf-gcc: Command not found make: *** [build/open_esplibs_libmain//ets_timer.o] Error 127 make: Leaving directory /home/vagrant/esp-homekit-demo/examples/led'


support run --env flag for .env.vault runs

it should prioritize the --env flag over the .env.vault decrypted/injected values. unless overload than of course prioritize the latest.

released in 0.20.2


Broken in IE

This is really just a duplicate of #722, I've already read it, but I'd like to open a new issue, because this is something that should be fixed by the library.
Re: https://github.com/react-tools/react-table/issues/722#issuecomment-355869337
@gary-menzel I completely disagree. How is a developer supposed to know that they should use a polyfill for find? It is not the developer's responsibility to understand the inner-workings and source code of a library. It is absolutely the author's responsibility to either:

Include a polyfill in the library itself
Declare it up front, notifying developers of any and all dependencies

Can you imagine having to debug my production code in IE11 (reported by a user, who knows how many other users couldn't access my site at all?), come across this error, search our own codebase only to realize we never use the native Array.find (because we use lodash's), then trying to track down which of the zillion npm modules we're using that assumes find exists? It wasn't fun.
There is nothing in the readme about this, there is no "browser compatibility" section on the website, how could any consumer of this library know?

If you read the original article by the author (@tannerlinsley) you'll understand why it is not included.
I don't have to "imagine"... I DO (and HAVE had to) fix IE11 bugs.  It's not nice.  It's not my fault. It's not the package developers fault.  It's Microsofts fault.
We can continue to disagree on the points you've made (I deal with this type of incompatibility all day long and still manage to be a successful - and often a better - developer because of it).
I'll be as blunt as to say: "if the package doesn't suit your purposes then find one that does".


Switch blas_server to use acq/rel semantics

Heavy-weight locking isn't required to pass the work queue
pointer between threads and simple atomic acquire/release
semantics can be used instead. This is especially important as
pthread_mutex_lock() isn't fair.
We've observed substantial variation in runtime because of the
the unfairness of these locks which complety goes away with
this implementation.
The locks themselves are left to provide a portable way for
idling threads to sleep/wakeup after many unsuccessful iterations
waiting.

Unfortunately this appears to increase the risk of a hang in the "fork safety" utest.

Seems the original process is still wait()ing for the forked child to exit, while in the child the originally active thread has exited and the three others appear to be stuck on the pthread_cond_signal(&thread_status[i].wakeup) in the blas_thread_shutdown procedure at line 949 of blas_server.c

I reworked the code a little bit to test for C11. If it's present it uses __atomic... if not it uses a volatile pointer to try to convince the compiler to read it.
I can't seem to replicate the hang. I've tried Ubuntu 19.04, 20.4, and Amazon Linux 2 and I've tried with 2c/4t and 18c/36t Skylake-based systems running openblas_utest 1000 times.

Hang seems to have caused the travis failures as well, probably need to make this depend on some yet to be determined value of __GLIBC_PREREQ as well.

@martin-frbg I did manage to get this to reproduce on CentOS6. I'll try to debug it.

What seems to be hanging is the nested fork in test_fork.c:104. Running with only two threads and set follow-fork-mode child in gdb:
(gdb) info thread
* 3 Thread 0x7ffff7ff2700 (LWP 27891)  0x00007ffff7949334 in __lll_lock_wait () from /lib64/libpthread.so.0
(gdb) bt
#0  0x00007ffff7949334 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x00007ffff7946f81 in pthread_cond_signal@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#2  0x0000000000459da5 in blas_thread_shutdown_ () at blas_server.c:963
#3  0x00007ffff7361d45 in fork () from /lib64/libc.so.6
#4  0x000000000040923d in __ctest_fork_safety_run () at test_fork.c:104

Yes, this is what I am seeing as well, but I do not know what to make of it - I'd like to think of this as a long-fixed glibc bug but cannot find anything remotely matching in the glibc bugzilla. The bad part of course is that the original GotoBLAS has never been threadsafe (big surprise for me when I started to use OpenBLAS) and my sledgehammer approach to locking everything down was guided by partial knowledge more than anything else. Added to that the fork handler has always been a fragile kludge.


Consider Blocking HUNTRESS Easy Data

ON HOLD - NOT TO BE MERGED
I recall Jack asked if we scramble the order of mutation matrices before we feed them to HUNTRESS. His doubt was that perhaps the order of tree labels and the mutation matrix is somewhat beneficial to the inference performed by HUNTRESS.
To block this technical artefact we could reorder the mutation matrix rows.
We currently don't. In this PR I considered this quickly.
The issue is that HUNTRESS does take the mutation matrix indices as the node names. Thus one would have to relabel the nodes again after Huntress is performed.
This brings a few ways to introduce errors I suppose.
It is probably best to wait and see if the advantage of HUNTRESS is still so pronounced now that SCITE should be fixed soon.

The effect of the initial tree fades quickly. Thus, the usage of HUNTRESS appears to be justified, despite its great performance. This investigation shall be closed as it no longer seems worth the pursuit.


Notebook find decorations are not removed when clearing the search text

Testing #145636

Create a new .ipynb notebook with the following code in the cell

str1 = "Foo"
str2 = "Bar"

# convert both the strings into lowercase
str1 = str1.lower()
str2 = str2.lower()

# check if length is same
if(len(str1) == len(str2)):

    # sort the strings
    sorted_str1 = sorted(str1)
    sorted_str2 = sorted(str2)

    # if sorted char arrays are same
    if(sorted_str1 == sorted_str2):
        print(str1 + " and " + str2 + " are anagram.")
    else:
        print(str1 + " and " + str2 + " are not anagram.")

else:
    print(str1 + " and " + str2 + " are not anagram.")

Press Cmd + F to bring up the search widget. Press s to which will display the find decorations
Delete s in the find widget -> Find decorators are not being removed

@lszomoru thank!


Dashboard: Deleting an existing tab immediately after having created a new tab with title does not work

👍  Hi @geido thanks for PR it looks good changes, I just found some buggy behavior, can you look please:
https://user-images.githubusercontent.com/56388545/107982543-e91dfc00-6fcc-11eb-99d9-3986b30f00ad.mov
Originally posted by @simcha90 in https://github.com/apache/superset/issues/12773#issuecomment-779390572

Specific steps to reproduce:

Create a new tab and give it a title
Create another tab and give it a title
Now without moving the focus to it,  click on the "X" icon of the previous tab to delete it
Observe the issue. The Delete modal will remain stuck

https://user-images.githubusercontent.com/60598000/108106681-f7d0e580-7096-11eb-8d6e-7b35f5f82ed8.mp4

Unable to reproduce... closing issue, but will continue to track the related PR linked above which should make sure the story ends here.