[TRACE] [AQ] atomic drm request: adding id 53 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 53 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 32 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 32 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 32 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 32 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 32 prop 17 with value 100
[TRACE] [AQ] atomic drm request: adding id 32 prop 20 with value 53
[TRACE] [AQ] atomic drm request: adding id 32 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 48
[TRACE] [AQ] atomic drm request: adding id 48 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 14 with value 0
[LOG] output eDP-1 succeeded basic test on format DRM_FORMAT_XRGB8888
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 0, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] [AQ] drm: Modesetting eDP-1 with<EMAIL_ADDRESS>[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[ERR] Couldn't commit output named eDP-1
[LOG] arrangeMonitors: 1 to arrange
[LOG] arrangeMonitors: eDP-1 auto [0, 0]
[LOG] arrangeMonitors: eDP-1 xwayland [0, 0]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Monitor eDP-1 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 0, pos 0x0, 10b 0
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] [hookSystem] New hook event registered: render
[LOG] Monitor eDP-1 -> destroyed all render data
[LOG] Shaders initialized successfully.
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Creating a texture for BGTex
[LOG] Framebuffer created, status 36053
[LOG] Background created for monitor eDP-1
[LOG] [AQ] drm: Modesetting eDP-1 with<EMAIL_ADDRESS>[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[TRACE] Monitor state commit failed, retrying without a fence
[LOG] [AQ] drm: Modesetting eDP-1 with<EMAIL_ADDRESS>[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[TRACE] Monitor state commit failed
[TRACE] Aquamarine did not return an explicit out fence
[TRACE] Explicit: 0 presented
[LOG] New output with name HDMI-A-2
[LOG] Applying monitor rule for HDMI-A-2
[TRACE] [AQ] GBM: Allocating a buffer: size [Vector2D: x: 1920, y: 1080], format XR24, cursor: false, multigpu: false, scanout: true
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000005 as it's not renderable
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000003 as it's not renderable
[TRACE] [AQ] GBM: Using modifier-based allocation, modifiers: 5
[TRACE] [AQ] GBM: | mod 0x0
[TRACE] [AQ] GBM: | mod 0x100000000000004
[TRACE] [AQ] GBM: | mod 0x100000000000002
[TRACE] [AQ] GBM: | mod 0x100000000000001
[TRACE] [AQ] GBM: | mod 0x0
[LOG] [AQ] GBM: Allocated a new buffer with size [Vector2D: x: 1920, y: 1080] and format XR24 with modifier<PHONE_NUMBER>7927940 aka Y_TILED_CCS
[TRACE] [AQ] GBM: Allocating a buffer: size [Vector2D: x: 1920, y: 1080], format XR24, cursor: false, multigpu: false, scanout: true
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000005 as it's not renderable
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000003 as it's not renderable
[TRACE] [AQ] GBM: Using modifier-based allocation, modifiers: 5
[TRACE] [AQ] GBM: | mod 0x0
[TRACE] [AQ] GBM: | mod 0x100000000000004
[TRACE] [AQ] GBM: | mod 0x100000000000002
[TRACE] [AQ] GBM: | mod 0x100000000000001
[TRACE] [AQ] GBM: | mod 0x0
[LOG] [AQ] GBM: Allocated a new buffer with size [Vector2D: x: 1920, y: 1080] and format XR24 with modifier<PHONE_NUMBER>7927940 aka Y_TILED_CCS
[LOG] [AQ] Swapchain: Reconfigured a swapchain to [Vector2D: x: 1920, y: 1080] XR24 of length 2
[LOG] CMonitorState::ensureBufferPresent: no buffer, attaching one from the swapchain for modeset being possible
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: plane 0 has fd 71, got handle 1
[TRACE] [AQ] drm: CDRMFB: plane 1 has fd 72, got handle 1
[TRACE] [AQ] drm: Using drmModeAddFB2WithModifiers to import buffer into KMS: Size [Vector2D: x: 1920, y: 1080] with format XR24 and mod<PHONE_NUMBER>7927940
[TRACE] [AQ] drm: new buffer 144
[TRACE] [AQ] Connector blob id 145: clock 297000, 1920x1080, vrefresh 120, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 120
[TRACE] [AQ] atomic addConnector values: CRTC 75, mode 145
[TRACE] [AQ] atomic drm request: adding id 129 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 75 prop 23 with value 145
[TRACE] [AQ] atomic drm request: adding id 129 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 129 prop 120 with value 1
[TRACE] [AQ] atomic drm request: adding id 129 prop 131 with value 8
[TRACE] [AQ] atomic drm request: adding id 75 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 75 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 54 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 54 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 54 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 54 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 54 prop 17 with value 144
[TRACE] [AQ] atomic drm request: adding id 54 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 54 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 70
[TRACE] [AQ] atomic drm request: adding id 70 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 14 with value 0
[LOG] Monitor HDMI-A-2: requested<EMAIL_ADDRESS>found available mode: 1920x1080@120000mHz, applying.
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574aa6b0
[TRACE] [AQ] Connector blob id 146: clock 297000, 1920x1080, vrefresh 120, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 120
[TRACE] [AQ] atomic addConnector values: CRTC 75, mode 146
[TRACE] [AQ] atomic drm request: adding id 129 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 75 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 129 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 129 prop 120 with value 1
[TRACE] [AQ] atomic drm request: adding id 129 prop 131 with value 8
[TRACE] [AQ] atomic drm request: adding id 75 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 75 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 54 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 54 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 54 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 54 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 54 prop 17 with value 144
[TRACE] [AQ] atomic drm request: adding id 54 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 54 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 70
[TRACE] [AQ] atomic drm request: adding id 70 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 14 with value 0
[LOG] output HDMI-A-2 succeeded basic test on format DRM_FORMAT_XRGB8888
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 0, needsFrame true, isPageFlipPending false, frameEventScheduled false
[LOG] [AQ] drm: Modesetting HDMI-A-2 with<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574aa6b0
[TRACE] [AQ] Connector blob id 145: clock 297000, 1920x1080, vrefresh 120, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 120
[TRACE] [AQ] atomic addConnector values: CRTC 75, mode 145
[TRACE] [AQ] atomic drm request: adding id 129 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 75 prop 23 with value 145
[TRACE] [AQ] atomic drm request: adding id 129 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 129 prop 120 with value 1
[TRACE] [AQ] atomic drm request: adding id 129 prop 131 with value 8
[TRACE] [AQ] atomic drm request: adding id 75 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 75 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 54 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 54 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 54 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 54 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 54 prop 17 with value 144
[TRACE] [AQ] atomic drm request: adding id 54 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 54 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 70
[TRACE] [AQ] atomic drm request: adding id 70 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 14 with value 0
[LOG] Monitor HDMI-A-2 -> destroyed all render data
[LOG] arrangeMonitors: 2 to arrange
[LOG] arrangeMonitors: HDMI-A-2 explicit [1920, 0]
[LOG] arrangeMonitors: eDP-1 auto [0, 0]
[LOG] arrangeMonitors: eDP-1 xwayland [0, 0]
[LOG] arrangeMonitors: HDMI-A-2 xwayland [1920, 0]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame false, isPageFlipPending true, frameEventScheduled true
[LOG] Monitor HDMI-A-2 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 0, pos 1920x0, 10b 0
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574aa6b0
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 120
[TRACE] [AQ] atomic addConnector values: CRTC 75, mode 0
[TRACE] [AQ] atomic drm request: adding id 129 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 129 prop 120 with value 1
[TRACE] [AQ] atomic drm request: adding id 75 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 75 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 54 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 54 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 54 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 54 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 54 prop 17 with value 144
[TRACE] [AQ] atomic drm request: adding id 54 prop 20 with value 75
[TRACE] [AQ] atomic drm request: adding id 54 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 54 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 70
[TRACE] [AQ] atomic drm request: adding id 70 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 70 prop 14 with value 0
[LOG] Added new monitor with name HDMI-A-2 at [1920, 0] with size [1920, 1080], pointer 563b56466a90
[LOG] New monitor: WORKSPACEID 2, exists: 0
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame false, isPageFlipPending true, frameEventScheduled true
[LOG] [IWaylandProtocol] Registered global [WLOutput (HDMI-A-2)]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 7, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 7, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Applying monitor rule for eDP-1
[LOG] Setting preferred mode for eDP-1
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b56f5f770
[TRACE] [AQ] Connector blob id 146: clock 152840, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 53, mode 146
[TRACE] [AQ] atomic drm request: adding id 99 prop 20 with value 53
[TRACE] [AQ] atomic drm request: adding id 53 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 99 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 99 prop 104 with value 8
[TRACE] [AQ] atomic drm request: adding id 53 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 53 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 32 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 32 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 32 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 32 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 32 prop 17 with value 100
[TRACE] [AQ] atomic drm request: adding id 32 prop 20 with value 53
[TRACE] [AQ] atomic drm request: adding id 32 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 48
[TRACE] [AQ] atomic drm request: adding id 48 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 14 with value 0
[LOG] output eDP-1 succeeded basic test on format DRM_FORMAT_XRGB8888
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 0, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] [AQ] drm: Modesetting eDP-1 with<EMAIL_ADDRESS>[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[ERR] Couldn't commit output named eDP-1
[LOG] arrangeMonitors: 2 to arrange
[LOG] arrangeMonitors: HDMI-A-2 explicit [1920, 0]
[LOG] arrangeMonitors: eDP-1 auto [3840, 0]
[LOG] arrangeMonitors: eDP-1 xwayland [0, 0]
[LOG] arrangeMonitors: HDMI-A-2 xwayland [1920, 0]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Monitor eDP-1 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 0, pos 3840x0, 10b 0
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Applying monitor rule for HDMI-A-2
[LOG] Not applying a new rule to HDMI-A-2 because it's already applied!
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Monitor HDMI-A-2 -> destroyed all render data
[LOG] Shaders initialized successfully.
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Framebuffer created, status 36053
[LOG] Creating a texture for BGTex
[LOG] Framebuffer created, status 36053
[LOG] Background created for monitor HDMI-A-2
[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[TRACE] Monitor state commit failed, retrying without a fence
[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[TRACE] Monitor state commit failed
[TRACE] Aquamarine did not return an explicit out fence
[TRACE] Explicit: 0 presented
[LOG] New output with name DP-5
[LOG] Applying monitor rule for DP-5
[TRACE] [AQ] GBM: Allocating a buffer: size [Vector2D: x: 1920, y: 1080], format XR24, cursor: false, multigpu: false, scanout: true
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000005 as it's not renderable
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000003 as it's not renderable
[TRACE] [AQ] GBM: Using modifier-based allocation, modifiers: 5
[TRACE] [AQ] GBM: | mod 0x0
[TRACE] [AQ] GBM: | mod 0x100000000000004
[TRACE] [AQ] GBM: | mod 0x100000000000002
[TRACE] [AQ] GBM: | mod 0x100000000000001
[TRACE] [AQ] GBM: | mod 0x0
[LOG] [AQ] GBM: Allocated a new buffer with size [Vector2D: x: 1920, y: 1080] and format XR24 with modifier<PHONE_NUMBER>7927940 aka Y_TILED_CCS
[TRACE] [AQ] GBM: Allocating a buffer: size [Vector2D: x: 1920, y: 1080], format XR24, cursor: false, multigpu: false, scanout: true
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000005 as it's not renderable
[TRACE] [AQ] GBM: Dropping modifier 0x100000000000003 as it's not renderable
[TRACE] [AQ] GBM: Using modifier-based allocation, modifiers: 5
[TRACE] [AQ] GBM: | mod 0x0
[TRACE] [AQ] GBM: | mod 0x100000000000004
[TRACE] [AQ] GBM: | mod 0x100000000000002
[TRACE] [AQ] GBM: | mod 0x100000000000001
[TRACE] [AQ] GBM: | mod 0x0
[LOG] [AQ] GBM: Allocated a new buffer with size [Vector2D: x: 1920, y: 1080] and format XR24 with modifier<PHONE_NUMBER>7927940 aka Y_TILED_CCS
[LOG] [AQ] Swapchain: Reconfigured a swapchain to [Vector2D: x: 1920, y: 1080] XR24 of length 2
[LOG] CMonitorState::ensureBufferPresent: no buffer, attaching one from the swapchain for modeset being possible
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: plane 0 has fd 75, got handle 1
[TRACE] [AQ] drm: CDRMFB: plane 1 has fd 76, got handle 1
[TRACE] [AQ] drm: Using drmModeAddFB2WithModifiers to import buffer into KMS: Size [Vector2D: x: 1920, y: 1080] with format XR24 and mod<PHONE_NUMBER>7927940
[TRACE] [AQ] drm: new buffer 142
[TRACE] [AQ] Connector blob id 147: clock 148500, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] Connector blob id 147: clock 148500, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] Connector blob id 147: clock 148352, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] drm: calculateMode: modeline dump:<PHONE_NUMBER> 2048 2248 2576 1080 1083 1088 1120 60 6
[TRACE] [AQ] Connector blob id 147: clock 173000, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[ERR] Custom resolution FAILED, falling back to preferred
[ERR] Monitor 2 has NO PREFERRED MODE, and an INVALID one was requested<EMAIL_ADDRESS>[LOG] [AQ] drm: Modesetting DP-5 with<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] drm: calculateMode: modeline dump:<PHONE_NUMBER> 2048 2248 2576 1080 1083 1088 1120 60 6
[TRACE] [AQ] Connector blob id 147: clock 173000, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[ERR] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET PAGE_FLIP_EVENT
[WARN] state.commit() failed in CMonitor::onCommit
[LOG] Added new monitor with name DP-5 at [-1, -1] with size [0, 0], pointer 563b564657f0
[LOG] New monitor: WORKSPACEID 3, exists: 0
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] Output DP-5 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] [IWaylandProtocol] Registered global [WLOutput (DP-5)]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 7, needsFrame true, isPageFlipPending false, frameEventScheduled false
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 7, needsFrame true, isPageFlipPending false, frameEventScheduled true
[LOG] Applying monitor rule for eDP-1
[LOG] Setting preferred mode for eDP-1
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b56f5f770
[TRACE] [AQ] Connector blob id 147: clock 152840, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 53, mode 147
[TRACE] [AQ] atomic drm request: adding id 99 prop 20 with value 53
[TRACE] [AQ] atomic drm request: adding id 53 prop 23 with value 147
[TRACE] [AQ] atomic drm request: adding id 99 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 99 prop 104 with value 8
[TRACE] [AQ] atomic drm request: adding id 53 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 53 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 32 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 32 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 32 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 32 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 32 prop 17 with value 100
[TRACE] [AQ] atomic drm request: adding id 32 prop 20 with value 53
[TRACE] [AQ] atomic drm request: adding id 32 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 32 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 48
[TRACE] [AQ] atomic drm request: adding id 48 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 48 prop 14 with value 0
[LOG] output eDP-1 succeeded basic test on format DRM_FORMAT_XRGB8888
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 0, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] [AQ] drm: Modesetting eDP-1 with<EMAIL_ADDRESS>[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[ERR] Couldn't commit output named eDP-1
[LOG] arrangeMonitors: 3 to arrange
[LOG] arrangeMonitors: HDMI-A-2 explicit [1920, 0]
[LOG] arrangeMonitors: DP-5 explicit [0, 0]
[LOG] arrangeMonitors: eDP-1 auto [3840, 0]
[LOG] arrangeMonitors: eDP-1 xwayland [0, 0]
[LOG] arrangeMonitors: HDMI-A-2 xwayland [1920, 0]
[LOG] arrangeMonitors: DP-5 xwayland [3840, 0]
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Monitor eDP-1 data dump: res<EMAIL_ADDRESS>scale 1.00, transform 0, pos 3840x0, 10b 0
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] Output DP-5 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending false, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Applying monitor rule for HDMI-A-2
[LOG] Not applying a new rule to HDMI-A-2 because it's already applied!
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[LOG] Applying monitor rule for DP-5
[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] Connector blob id 146: clock 148500, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] Connector blob id 146: clock 148500, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] Connector blob id 146: clock 148352, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[LOG] Monitor DP-5: REJECTED available mode<EMAIL_ADDRESS>[TRACE] [AQ] drm: Committed a buffer, updating state
[TRACE] [AQ] drm: CDRMFB: buffer has drmfb attachment with fb 563b574bb0f0
[TRACE] [AQ] drm: calculateMode: modeline dump:<PHONE_NUMBER> 2048 2248 2576 1080 1083 1088 1120 60 6
[TRACE] [AQ] Connector blob id 146: clock 173000, 1920x1080, vrefresh 60, name: 1920x1080
[TRACE] [AQ] atomic addConnector blobs: mode_id 23, active 22, crtc_id 20, link_status 5, content_type 0
[TRACE] [AQ] atomic addConnector values: CRTC 97, mode 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 97 prop 23 with value 146
[TRACE] [AQ] atomic drm request: adding id 139 prop 5 with value 0
[TRACE] [AQ] atomic drm request: adding id 139 prop 113 with value 8
[TRACE] [AQ] atomic drm request: adding id 97 prop 22 with value 1
[TRACE] [AQ] atomic drm request: adding id 97 prop 24 with value 0
[TRACE] [AQ] atomic planeProps: prop blobs: src_x 9, src_y 10, src_w 11, src_h 12, crtc_w 15, crtc_h 16, fb_id 17, crtc_id 20, crtc_x 13, crtc_y 14
[TRACE] [AQ] atomic drm request: adding id 76 prop 9 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 10 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 11 with value 125829120
[TRACE] [AQ] atomic drm request: adding id 76 prop 12 with value 70778880
[TRACE] [AQ] atomic drm request: adding id 76 prop 15 with value 1920
[TRACE] [AQ] atomic drm request: adding id 76 prop 16 with value 1080
[TRACE] [AQ] atomic drm request: adding id 76 prop 17 with value 142
[TRACE] [AQ] atomic drm request: adding id 76 prop 20 with value 97
[TRACE] [AQ] atomic drm request: adding id 76 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 76 prop 14 with value 0
[TRACE] [AQ] atomic planeProps: disabling plane 92
[TRACE] [AQ] atomic drm request: adding id 92 prop 17 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 20 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 13 with value 0
[TRACE] [AQ] atomic drm request: adding id 92 prop 14 with value 0
[LOG] [AQ] atomic drm request: failed to commit: Invalid argument, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
[ERR] Custom resolution FAILED, falling back to preferred
[ERR] Monitor 2 has NO PREFERRED MODE, and an INVALID one was requested<EMAIL_ADDRESS>[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] Output eDP-1 rejected hardware cursors, falling back to sw
[TRACE] Output HDMI-A-2 rejected hardware cursors, falling back to sw
[TRACE] Output DP-5 rejected hardware cursors, falling back to sw
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 6, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending true, frameEventScheduled true
[TRACE] [AQ] CDRMOutput::scheduleFrame: reason 3, needsFrame true, isPageFlipPending false, frameEventScheduled true
[LOG] Shaders initialized successfully.
[CRITICAL]
==========================================================================================
ASSERTION FAILED!

Attempted to draw NULL texture!

at: line 1546 in OpenGL.cpp

can you do this to get kernel drm logs
echo 0x19F | sudo tee /sys/module/drm/parameters/debug # Enable verbose DRM logging
sudo dmesg -C # Clear kernel logs
dmesg -w >dmesg.log & # Continuously write DRM logs to a file, in the background
Hyprland
fg # Kill dmesg -w with Ctrl+C
echo 0 | sudo tee /sys/module/drm/parameters/debug # Disable DRM logging

you just need to run this, plug in 3rd monitor, then exit Hyprland, finally ctrl+c
then give dmesg.log (btw it might be really big but thats fine)

@ikalco Is this it? I used hyprland-git/aquamarine-git, so plugging in the 3rd monitor still just crashes Hyprland right away.
dmesg.log

@ramonpzg downgrading works! But now the plugins are not working. Updating fails.

P.S.: sorry for offtopic

and it still happends with the monitor fixes in aq-git hl-git from yesterday?

@gulafaran Not crashing anymore, but get no signal on the monitor, it just stays black. Probably the same as https://github.com/hyprwm/Hyprland/issues/7321

@ikalco @vaxerski Should we close this issue as the crash is resolved? Is there any way to confirm that the blank screen is the same as #7321?

hi @yyyyyyyan since i'm still experiencing a blank screen as posted here, the issues are probably not the same. I guess.

no clue, but there are 10 "blank screen" issues open and I think thats enough


[NextDNS] optimistic update attempt

@pernielsentikaer instead of using onRemove and utils, why not pass the entire mutate to the list-item component and handle everything over there? This PR shows how we can achieve this.

In the lates commit we also have error handling for the case of "200 OK" yet an error.
Passing mutate directly to list-item will let us handle all the toggle, add, remove cases for both allowlist and denylist in single functions rather than use onRemove and similar in AllowList and DenyList separately. But we can also do it the way you have done - your call 💪.

Your idea sounds more solid indeed, I might have forgot to pull before going ahead 🫠

I should have started this in a branch for sure 🫠

@xmok do you think you can help with the merge conflict, let's continue with your ideas

Yes I've checked out your latest changes locally first to review then I'll see the conflicts.

Sorry about that, I like your idea better 🔥

Maybe it's better to start over and move the files to a branch?

You're da best

OK I think we're good to go. Had to mix and match some of the code but we're in a good place now. It can definitely be optimized but the main mutate functions seem to be working ok i.e I can add and toggle!

Updated the code some more, it's starting to look pretty dope 🙂


Added serviceAccount to initializer.

Without the serviceAccount, the initializer will be failed to
retrive the unintialized objects and thus caused all of the
deployment stuck in pending for 30s and then timeout.
Fixed https://github.com/kubernetes/charts/issues/2442
/cc @lachie83

ping @lachie83

Can you rebase because I've fixed values to pass the linter. Also please bump the chart version

@lachie83 done, thanks.


[SPIKE] Investigate OpenStack Ansible [TIMEBOX]

Spike Story

investigate OpenStack Ansible via:
https://github.com/openstack/openstack-ansible
to see if it can help be a solution in manual integration testing of Harvester with Issue: 2274

Timeboxed and report brief findings here

Leveraging this:
https://docs.openstack.org/openstack-ansible/latest/user/aio/quickstart.html
Was unable to provision OpenStack AIO.
Seemingly there are a few issues:

The Ansible task, TASK [bootstrap-host : Check that network bridges are up] seems to cause issues per running the scripts/bootstrap-aio.sh as sudo
sudo openstack-ansible setup-infrastructure.yml doesn't find any hosts, so that playbook absolutely does nothing, thinking that there's something missing... though the prior setup-hosts.yml doesn't seem to cause any problems... it might hinge on the network issues with the scripts/bootstrap-aio.sh

I was utilizing Harvester v1.0.3 on bare-metal R720 to attempt to provision an OpenStack AIO.
12 C / 24GiB Mem / 200GiB Disk.
The cloud-config used in conjunction with Ubuntu 20.04 Cloud Image was:
#cloud-config
package_update: true
packages:
  - qemu-guest-agent
  - build-essential
  - git
  - chrony
  - openssh-server
  - python3-dev
  - net-tools
  - sudo
  - bridge-utils
  - debootstrap
  - tcpdump
  - neovim
  - vlan
runcmd:
  - - systemctl
    - enable
    - --now
    - qemu-guest-agent.service
  - git clone -b stable/yoga https://opendev.org/openstack/openstack-ansible
    /opt/openstack-ansible
  - chmod +x /opt/openstack-ansible/scripts/bootstrap-ansible.sh
  - /opt/openstack-ansible/scripts/bootstrap-ansible.sh
  - chmod +x /opt/openstack-ansible/scripts/bootstrap-aio.sh
  - /opt/openstack-ansible/scripts/bootstrap-aio.sh
ssh_authorized_keys:
  - my-ssh-key

Then additionally attempting:
# cd /opt/openstack-ansible/playbooks
# openstack-ansible setup-hosts.yml
# openstack-ansible setup-infrastructure.yml
# openstack-ansible setup-openstack.yml

But again there seems to be a problem with the scripts/bootstrap-aio.sh from the OpenStack AIO Ansible.
Their project is phenomenal though! - 5yrs of Ansible - it's a pretty intense and very involved setup - but it's rad to see they're probably getting close to the edge of what Ansible is capable of.
Closing this out, as this is intended to be timeboxed
SPIKE Investigation on Implementation Failure


Remove CUBRID support

@mtangoo want to handle it?

Yeah, removing this shouldn't be hard. I will take a shot at it!

@samdark where do I trigger framework tests after changes? Checking tests/test-local.sh but does not seem to be the right one

For anyone who is new and have same question, the missing link is https://github.com/yiisoft/yii2/blob/master/docs/internals/git-workflow.md

https://github.com/yiisoft/yii2/pull/19901

https://github.com/yiisoft/yii2/pull/19902


output stdout and stderr from custom commands, allow setting timeout for critctl

Problems

We are seeing intermittent failures on our custom command for containerd, errors from crictl appear to be printed on stderr; since only stdout is output it's difficult to debug what the failure is.

crictl at one point updated the tools timeout from 10s to 2s; it's possible this timeout is the source of our intermittent errors

Solution

output stderr as well as stdout
allow setting critctl timeout via npd configs

/assign @xueweiz
doing ^ because the bot told me to

Is there anybody out there?

/lgtm
/ok-to-test


Sass mixin still uses ~ (tilde) in $directory which is unsupported by newer bundlers

Describe the bug
The use of ~ in the css url statement for the $directory variable default is causing errors in Angular's newer esbuild-based build system.  My understanding is webpack is moving away from this convention as well.  Angular's non-esbuild build system supports with or without ~.  So it would seem to me that removing the ~ from the $directory default would allow for maximum capability.
Steps to Reproduce

Create new angular app: ng new test-app
Install fontsource package yarn add @fontsource/roboto
Include the mixin in styles.scss:

@use '@fontsource/roboto/scss/mixins' as roboto;
@include roboto.faces();

Switch angular.json to esbuild builder
Change:

...
"architect": {
  "build": {
    "builder": "@angular-devkit/build-angular:browser",
...

to
...
"architect": {
  "build": {
    "builder": "@angular-devkit/build-angular:browser-esbuild",
...

Run ng build

Expected behavior
Should build successfully.  But instead I receive the following error:
X [ERROR] Could not resolve<EMAIL_ADDRESS>[plugin angular-css-resource]

    ../../dist/components/theme.css:69:509:
      69 │<EMAIL_ADDRESS>         ╵              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can remove the tilde and use a relative path to reference it, which should remove this error.

Version
5.0.2
OS
Windows 11
Browser
Chrome
Additional context
Recommend removing the ~ from https://github.com/fontsource/fontsource/blob/0f4d2c779601f496dac118299a818a7d1069726b/packages/cli/src/sass/mixins.ts#L43-L47

I think this idea may unintentionally affect many builds with older bundlers and potentially be breaking for some of them. I'm a little uncomfortable making such a change without knowing how many users this could impact.
The current workaround would be to use the $directory Sass mixin parameter with the correct path, but maybe we could make things easier for users by including additional preset variables defining the path? e.g. we include an $esbuildDirectory variable with the non-tilde path that can be passed into $directory when importing the Sass mixins? We could then include a notice in the Angular guide to remark on the difference.

That would certainly help as things transition away from tildes.  At some point, though, it seems like non-tilde will be the norm.  So it may be worth considering reversing the defaults at some point when it makes sense.  But yeah, an interim solution might help.

Alternatively I fixed this issue by doing the following in the vite config file:
resolve: {
    alias: [
      {
        // Workaround to emulate behavior of ~ prefix in Wepback that refers to a relative path in node_modules folder
        find: /~(.+)/,
        replacement: `${process.cwd()}/node_modules/$1`
      }
    ]
  }

I have fixed this issue  by providing $directory however I am running into issue in my angular test.
Build fix:
@use '@fontsource/roboto/scss/mixins' as roboto;

@include roboto.faces(
  $directory: '@fontsource/roboto/files',
  $weights: (
    300,
    400,
    500,
    700,
    900
  ),
  $styles: (
    italic,
    normal
  ),
  $subsets: (
    latin
  ),
  $formats: (
    woff2
  )
);

After this fix I am now facing hen I run ng test
Error: Module Error (from ./node_modules/postcss-loader/dist/cjs.js):
MY-APP/node_modules/@fontsource/roboto/scss/mixins.scss:189:6: Can't resolve '../../../node_modules/<EMAIL_ADDRESS>in 'MY-APP/projects/app/src'

This looks like somehow the $directory workaround had no effect from test runtime/workflow.

@yogeshgadge s. https://github.com/angular/angular-cli/issues/26718


Support Wishbone bus

Support Wishbone b4 version.
https://github.com/fossi-foundation/wishbone/blob/master/documents/spec/wbspec_b4.pdf

I've implemented common RTL modules for wishbone interface.


[WIP]  missing skip remediation events

Why we need this PR
Adding skipped remediation event for missing use cases
Changes made
creating a skip remediation event when remediation is skipped because node lease is already taken
Which issue(s) this PR fixes
ECOPROJECT-1889
Test plan

/test 4.15-openshift-e2e

/test 4.15-openshift-e2e


[Performance] contirb.seq2seq.attention_wrapper slower due to using matmul instead of reduce_sum

tf version '1.2.0-rc0' contirb.seq2seq.attention_wrapper is great, it make using attention much easier.
However I found using attention_wrapper will be much slower then tf version 1.0.
After some experiment I found it is due to using matmul instead of reduce_sum.
from attetntion_wrapper.py 731
  expanded_alignments = array_ops.expand_dims(alignments, 1)
  attention_mechanism_values = self._attention_mechanism.values
  context = math_ops.matmul(expanded_alignments, attention_mechanism_values)
  context = array_ops.squeeze(context, [1])

Using above code for one of my application got 2.2 batch/s, after changing to use reduce_sum(as tf version 1.0 did), the speed is 3.4 batch/s, improve a lot.
  expanded_alignments = array_ops.expand_dims(alignments, 2)
  attention_mechanism_values = self._attention_mechanism.values
  context = math_ops.reduce_sum(expanded_alignments * attention_mechanism_values, [1])

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 343 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 358 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 373 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 388 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 403 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 418 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tfboyd: It has been 433 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Closing this as prefer to use eager mode seq2seq.


More realistic file import example

Closes #567
Change the file import example to display summary stats of uploaded data, such as row count, column count and column names.

This PR includes your Snowflake credentials. That doesn't seem right...
We appreciate this PR, but it's not clear to me that it is an improvement for the intended purpose of the app, which is just to illustrate how to use the file upload component. The old app just shows how to do file uploads, while the new one also adds some interactivity with checkboxes. The new version is in a sense a more realistic app, but in this case I don't think the changes are helpful for illustrating how the file upload component works.

Apologies, I looked at this too quickly and didn't see the linked issue at the top, and the discussion in that issue.

No problem, as for the snowflake credentials, it has been removed

Great, thanks!
Just a heads up: I'm working on some review comments now but I have a meeting so it'll be a couple hours before I'll be able to submit them.

Thanks, I think I should've chimed in a bit more since I think I suggested this PR. The main things I find confusing about the current example are:

It uses conditional UI which people might not know (people probably build file-import apps before they build conditional UI apps)
It uses ui.HTML output to render a table which isn't that common (most of the time people use ui.output_table or ui.output_data_frame


[$1000] Chat - The background size of the special emoji :face_in_clouds: is larger than other emojis

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the App
Login with any account
Open any chat
Send any message
Hover over the message and click the button to select an emoji to react to the message
Choose :face_in_clouds: emoji

Expected Result:
The background of the emoji is the same for every emoji
Actual Result:
The background size of the special emoji :face_in_clouds: is larger than other emojis
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
https://github.com/Expensify/App/assets/78819774/7a30b191-0f32-451c-94f7-fc3d512b7cf3

Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~016223b92b4c611126
Upwork Job ID:<PHONE_NUMBER>466743808
Last Price Increase: 2023-07-10

I cannot reproduce this on my end. This emoji is working for me as expected on android native.
https://github.com/Expensify/App/assets/54866469/b5e3a629-b76a-499a-87a3-4a55ddc1659f

@lanitochka17 I'm going to close this for now since I cannot reproduce. Could you please try again and let me know if you still can? If so, could you please share your specific device type so I can try on that? Thanks!

@joekaufmanexpensify
Reproduced on  3 devices:
Samsung Galaxy A30/Android11
Realme6/Android11
Samsung Galaxy A50/Android11

Sounds good. Thanks for confirming! I will try to reproduce on those 3 devices or ones similar.

Not overdue

Okay, when I test on a RealMe8, I am able to reproduce:

Awaiting proposals.

Same

Bumped for proposals in Slack.

Do modern emojis are supported for version of android <= 11 ?
https://developer.android.com/develop/ui/views/text-and-emoji/emoji2#appcompat

It seems to be a problem with calculating the length of the emoji since 😶🌫 has a length of 6 but when combined it is probably shorter

@ShogunFire Ah, interesting. So you think this could be related to an older version of Android?

Honestly I don't know but if I understand correctly if Android is 11 or below, they say you must use AppCompat, emoji2 or EmojiCompat, I don't know if we use one or if react native use one

@thesahindia Curious for your thoughts on this as well. I think the above comment means we may not be able to easily fix this as it specifically relates to older Android devices?

Pending input from @thesahindia on the above question

Sure, I'll check now!

Yep, I'm seeing this on android 10. I also could not reproduce on newer devices. Going to close this per @thesahindia's above comment!


found the target extension

The target extension in this guide moved from general to advanced.  Its in configuration properties -> advanced -> target file extension.  Probably not a big deal, but it took me a while to get back on the trail of this tutorial.  Thanks for making this by the way, it's really helpful for me.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 40e3b6b1-a3d2-f4f2-b1ad-dd654a062343
Version Independent ID: b2418b84-04f4-60d2-ec1d-291a5d4d0c51
Content: Write C++ extensions for Python - Visual Studio
Content Source: docs/python/working-with-c-cpp-python-in-visual-studio.md
Product: visual-studio-windows
Technology: vs-python
GitHub Login: @JoshuaPartlow
Microsoft Alias: joshuapa

Hi @prelich, thanks for trying the tutorial and opening an issue when you found a problem. Could you tell me which version of Visual Studio you're using?

Sure:  Microsofgt Visual Studio Professional 2019
Version 16.3.0
Target File Extension on superfastcode(2) project was found in
Configuration Properties-->Advanced-->Target File Extension
On Mon, Sep 30, 2019 at 2:28 PM Joshua Partlow<EMAIL_ADDRESS>wrote:

Hi @prelich https://github.com/prelich, thanks for trying the tutorial
and opening an issue when you found a problem. Could you tell me which
version of Visual Studio you're using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/visualstudio-docs/issues/3987?email_source=notifications&email_token=ADLRF6VU66IXR4UQAU5MHXTQMJANLA5CNFSM4I2CZOYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76T6LQ#issuecomment-536690478,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLRF6RAKG4KYM6UTJQHW3LQMJANLANCNFSM4I2CZOYA
.

This has already been fixed and can be closed.


[spec] Add reserved version for Xtensa architecture

See also https://github.com/ldc-developers/ldc/issues/4725
cc @TurkeyMan is Xtensa ESP always 32-bit? What to do about Xtensa-S2/Xtensa-S3? I assume they will be specified in the target triple and any information they provide can be done through other means (e.g. __traits(getTargetInfo))

ESP32 is LX6, -S2,S3 are LX7, which has some additional instructions. It's always 32bit as far as I know. LX7 has some rudimentary SIMD stuff, a MAC instruction in particular is something the backend will want to take advantage of.
It'll be nice to feed as much knowledge as possible through getTargetInfo as you say; the whole point of the Xtensa platform is to be extensible, determining if specific ISA features are present for the selected target will be more useful than comparing the target to a whole bunch of known implementations in software...

See here: https://github.com/espressif/llvm-project/blob/xtensa_release_18.1.2/llvm/lib/Target/Xtensa/Xtensa.td#L194
They specify the processors from a compound list of features... how much trouble is it to expose that list via getTargetInfo somehow? It seems like the notion of feature sets is already known to LLVM... of software can query those feature flags, it can use the hardware as it's available.

 How do we know what all those features are named to test for them?

Yeah that sounds like CPU variants, not something that should have different version.
I suspect that the different subtarget features will be handled by __traits(targetHasFeature, ...) and the different CPU variants will be handled by __traits(getTargetCPU) (which will return e.g.  "esp8266" or "esp32s3")

Sure. How do we know what all those features are named to test for them?

the string is the first argument of SubtargetFeature in feature foo in  SubtargetFeature<"foo", ...>
import std.stdio;
void main() {
  writeln("CPU = ", __traits(targetCPU));
  writeln("Has 'sse4.1' = ", __traits(targetHasFeature, "sse4.1"));
}

def FeatureSSE41   : SubtargetFeature<"sse4.1", "X86SSELevel", "SSE41",
                                      "Enable SSE 4.1 instructions",
                                      [FeatureSSSE3]>;

in
https://github.com/llvm/llvm-project/blob/main/llvm/lib/Target/X86/X86.td#L80
So for https://github.com/espressif/llvm-project/blob/xtensa_release_18.1.2/llvm/lib/Target/Xtensa/Xtensa.td#L18
the features will be
  writeln("CPU = ", __traits(targetCPU)); // prints e.g. `esp32s2`
 writeln("Has 'density' = ", __traits(targetHasFeature, "density"));
 writeln("Has 'fp' = ", __traits(targetHasFeature, "fp"));
// ditto for "windowed", "bool", etc.

I suspect that the different subtarget features will be handled by __traits(targetHasFeature, ...) and the different CPU variants will be handled by __traits(getTargetCPU) (which will return e.g. "esp8266" or "esp32s3")

Yes, this sounds perfect to me!


Use context menu to display actions that do not fit

Testing #100850
Consider using a context menu (...) at the end of the line, to surface the actions that do not fit in the view.

We rarely do this for our inline actions. However I think this is a fair feature request against our inline actions across the workbench


Wiki page menu options for code wikis aren't matching documentation

This topic suggests that the menu options for the two types of wikis (Provisioned wiki and publish code as wiki) are expected to be different, but we are observing that they are the same - when checking several code wikis we see all the options documented as being available only on a Provisioned wiki as also being visible for a code wiki.
I suspect this topic is out of date.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 59cb387d-5f46-0743-efbb-c393c4e5bd85
Version Independent ID: cb6912c2-e640-f992-0a1f-5cbbe88d87dc
Content: Differences between provisioned and published wiki - Azure DevOps
Content Source: docs/project/wiki/provisioned-vs-published-wiki.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @davidj488, Thanks so much for your feedback. We'll be in touch soon with a solution. Thanks!

Hi @davidj488, I've made some updates and replaced screenshots, thank you. This issue will automatically close once my pull request is complete. Please @mention me if you have any further feedback! Thank you!


Sometimes, right clicking on viewer opens qt checkboxes for which dockwidgets to display

Only seen on some computers.
Most likely links to https://github.com/TomographicImaging/iDVC/issues/145

could also look at disabling this when you right click on the dock widgets


Rerelease Ruby with fixed file permissions

Bumping the Ruby library version for a rerelease with fixed file permissions. The 0.1.0 gem has ruby files with permission 0640 instead of 0644.

@tswast


Updating Dependencies

Contributor Comments
[Please insert a description of the change here]
Updated Terraform to 1.3.2
Pull Request Checklist
Thank you for submitting a contribution to easy_infra!
In order to streamline the review of your contribution we ask that you review and comply with the below requirements:

[ ] Rebase your branch against the latest commit of the target branch
[ ] If you are adding a dependency, please explain how it was chosen
[ ] If manual testing is needed in order to validate the changes, provide a testing plan and the expected results
[ ] If there is an issue associated with your Pull Request, link the issue to the PR.

@digeseiso this doesn't seem to be rebased on main, can you do that and force push?


Refs #31040 -- Used 402 HTTP status in middleware_exceptions tests.

HTTP status code 418 - "I'm a Teaport" was added to http.HTTPStatus in Python 3.9.0a5 that caused failures in middleware_exceptions tests.
File "tests\middleware_exceptions\tests.py", line 250, in test_async_teapot_middleware_async
    self.assertEqual(
AssertionError: "I'm a Teapot: /middleware_exceptions/view/" != 'Unknown Status Code: /middleware_exceptions/view/'
- I'm a Teapot: /middleware_exceptions/view/
+ Unknown Status Code: /middleware_exceptions/view/

This changes HTTP status used in middleware_exceptions tests to 402, which exists in all supported versions of Python.

☕


Update conmon to v2.1.9

What type of PR is this?
/kind dependency-change
What this PR does / why we need it:
Update conmon to the latest release.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

@cri-o/cri-o-maintainers PTAL

/lgtm


float8 support for array ops

Issue type
Feature Request
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
2.12.0
Custom code
No
OS platform and distribution
macOS-13.2.1-arm64-arm-64bit
Mobile device
No response
Python version
3.9.6
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Please add FP8 datatype support for array ops (like Reshape, Transpose, GatherV2, ExpandDims, Squeeze, ConcatV2, Split, Pack, Unpack, and StridedSlice).
Standalone code to reproduce the issue
import tensorflow as tf
from tensorflow.python.framework import dtypes

a = tf.constant([[1.2345678, 2.3456789, 3.4567891], [4.5678912, 5.6789123, 6.7891234]], dtype=dtypes.float16)
print(a)

a_fp8 = tf.cast(a, dtypes.float8_e4m3fn)
print(a_fp8)

b = a_fp8[1:2] # tensorflow.python.framework.errors_impl.NotFoundError
b = tf.transpose(a_fp8, [1, 0]) # tensorflow.python.framework.errors_impl.NotFoundError

Relevant log output
No response

@youchangkim I tried to replicate the provided code, could you have a look at the log below and confirm the same?

tf.Tensor(
[[1.234 2.346 3.457]
 [4.566 5.68  6.79 ]], shape=(2, 3), dtype=float16)
tf.Tensor(
[[1.25 2.25 3.5]
 [4.5 5.5 7]], shape=(2, 3), dtype=float8_e4m3fn)
---------------------------------------------------------------------------
NotFoundError                             Traceback (most recent call last)
<ipython-input-1-4393d1d31d50> in <cell line: 10>()
      8 print(a_fp8)
      9
---> 10 b = a_fp8[1:2] # tensorflow.python.framework.errors_impl.NotFoundError
     11 b = tf.transpose(a_fp8, [1, 0]) # tensorflow.python.framework.errors_impl.NotFoundError

1 frames
/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/ops.py in raise_from_not_ok_status(e, name)
   7260 def raise_from_not_ok_status(e, name):
   7261   e.message += (" name: " + name if name is not None else "")
-> 7262   raise core._status_to_exception(e) from None  # pylint: disable=protected-access
   7263
   7264

NotFoundError: Could not find device for node: {{node StridedSlice}} = StridedSlice[Index=DT_INT32, T=DT_FLOAT8_E4M3FN, begin_mask=0, ellipsis_mask=0, end_mask=0, new_axis_mask=0, shrink_axis_mask=0]
All kernels registered for op StridedSlice:
  device='XLA_GPU_JIT'; Index in [DT_INT32, DT_INT16, DT_INT64]; T in [DT_FLOAT, DT_DOUBLE, DT_INT32, DT_UINT8, DT_INT16,<PHONE_NUMBER>27764061, DT_HALF, DT_UINT32, DT_UINT64, DT_FLOAT8_E5M2, DT_FLOAT8_E4M3FN]
  device='XLA_CPU_JIT'; Index in [DT_INT32, DT_INT16, DT_INT64]; T in [DT_FLOAT, DT_DOUBLE, DT_INT32, DT_UINT8, DT_INT16,<PHONE_NUMBER>27764061, DT_HALF, DT_UINT32, DT_UINT64, DT_FLOAT8_E5M2, DT_FLOAT8_E4M3FN]
  device='CPU'; T in [DT_QINT32]
  device='CPU'; T in [DT_QUINT8]
  device='CPU'; T in [DT_QINT8]
  device='CPU'; T in [DT_VARIANT]
  device='CPU'; T in [DT_RESOURCE]
  device='CPU'; T in [DT_STRING]
  device='CPU'; T in [DT_BOOL]
  device='CPU'; T in [DT_COMPLEX128]
  device='CPU'; T in [DT_COMPLEX64]
  device='CPU'; T in [DT_DOUBLE]
  device='CPU'; T in [DT_FLOAT]
  device='CPU'; T in [DT_BFLOAT16]
  device='CPU'; T in [DT_HALF]
  device='CPU'; T in [DT_INT32]
  device='CPU'; T in [DT_INT8]
  device='CPU'; T in [DT_UINT8]
  device='CPU'; T in [DT_INT16]
  device='CPU'; T in [DT_UINT16]
  device='CPU'; T in [DT_UINT32]
  device='CPU'; T in [DT_INT64]
  device='CPU'; T in [DT_UINT64]
  device='GPU'; T in [DT_INT32]
  device='GPU'; T in [DT_BOOL]
  device='GPU'; T in [DT_COMPLEX128]
  device='GPU'; T in [DT_COMPLEX64]
  device='GPU'; T in [DT_DOUBLE]
  device='GPU'; T in [DT_FLOAT]
  device='GPU'; T in [DT_BFLOAT16]
  device='GPU'; T in [DT_HALF]
  device='GPU'; T in [DT_INT8]
  device='GPU'; T in [DT_UINT8]
  device='GPU'; T in [DT_INT16]
  device='GPU'; T in [DT_UINT16]
  device='GPU'; T in [DT_UINT32]
  device='GPU'; T in [DT_INT64]
  device='GPU'; T in [DT_UINT64]
 [Op:StridedSlice] name: strided_slice/

Thank you!

@sushreebarsa Yes. The ask is to register float8 types to these data movement ops.

@sachinprasadhs I was able to replicate the issue reported here using TF 2.12 and 2.13 as well. Please have a look ?
Thank you!

Fixed with https://github.com/tensorflow/tensorflow/pull/61749


Fix epoch/slot calculations for preview

LGTM, @gostkin this is fix for preview network, right? Is it already tested or will be deployed on preview?

the test I added uses real values from preview network. if the test works the code will work on the real network as well


Some PR style questions from perusing the code.

No action items yet, just some thoughts!

closing because this has been discussed/resolved!


table-cache: remove getFirstLevelCache from table

@lavrukov Let's resurrect this PR! Removing unneeded extra methods from Table is always, always welcome... (and those who truly need to perform advanced magic using FirstLevelCache, will still be able to do so ;-))


The NodeJS version checker in the CLI is wrong

The current check transforms NodeJS v18.3 to the number 18.3 and transforms v18.11 to 18.11.
This means that 18.3 > 18.11 which is not correct according to semver.
You have to make the minor a two digit number by zero padding it if it's only one digit.
So v18.3 would become the number 18.03...

Created a PR for this in #19


Indent lines related to EnableRawHtmlMarkupFormatter

Signed-off-by: Ernesto Ojeda<EMAIL_ADDRESS>What this PR does / why we need it:
Fixes issue with indentation of config.yaml which is causing linting errors.
Which issue this PR fixes

fixes #11251

Special notes for your reviewer:
I am not 100% sure if this is the fix, however when I indented the lines in this commit my linting errors went away:
Before indentation:
helm lint -f jenkins-values.yml charts/stable/jenkins                                                                                [13:05:28]
==> Linting charts/stable/jenkins
[ERROR] templates/config.yaml: unable to parse YAML
        error converting YAML to JSON: yaml: line 25: could not find expected ':'

Error: 1 chart(s) linted, 1 chart(s) failed

After indentation:
helm lint -f jenkins-values.yml charts/stable/jenkins                                                                                [13:06:10]
==> Linting charts/stable/jenkins
Lint OK

1 chart(s) linted, no failures

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md, variables are already documented

/assign @lachie83

/ok-to-test
/assign

/lgtm

/lgtm


BUG || Complainant Advocate cannot be replaced in DPG-DEV

Steps :

Register case and schedule hearing
Replace advocate as primary advocate.
Check case in Old Advocate

Old Advpcate

Hi @rajeshcherukumalli
Working fine in UAT

old advocate


Subversion sql locking

resolution_fixed   |    by<EMAIL_ADDRESS>
Mike, Scott
Just to let you know that I've working out why the performance of commands such as checkout looked so bad on accessdev.
On our systems here we have configured svn to use exclusive SQLite locking of working copies.
For details see http://subversion.apache.org/docs/release-notes/1.8.html#exclusivelocking
After enabling this option for my tests on accessdev, a checkout that was previously taking ~4min is now taking ~1min 20s.
Regards,
Dave
David Matthews    Manager Modelling Infrastructure Support Systems
Met Office  FitzRoy Road  Exeter  Devon  EX1 3PB  United Kingdom
Tel: +44 (0)1392 886508   Fax: +44 (0)1392 885681
E-mail<EMAIL_ADDRESS>http://www.metoffice.gov.uk

Issue migrated from trac:118 at 2024-01-31 18:05:13 +1100

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>commented

Fixed in 549c36b, Subversion now uses exclusive locking by default

<EMAIL_ADDRESS>commented

Milestone Future deleted


cdma_app.c does not work correctly

I've been following the Zynq-7000 SoC Embedded Design Tutorial (2023.2) using a Digilent Zybo Z7-20.   The cdma-app showed FAIL even though the DMA transfer occurred (I used the Memory inspector to read 0x2000_0000 (the source) and 0x3000_0000 (the destination).  I root caused the problem to the buffer compare where it appears that 256 bytes were being compared (Length=64*sizeof(u32)) even though only 64 bytes were transferred in the DMA transfer.
The fix was pretty easy once I figured out so I thought I'd share. The problem was in the SrcPtr and DestPtr declarations.  I changed the declarations as shown:
// Changed from original code to fix pointer references
u8 SrcPtr = SourceAddr;
u8 DestPtr= DestAddr;
// end changes
Both the source and destination buffers were defined as u8 in the version of the app that I downloaded so now SrcPtr and DestPtr can access the u8 "array".
Roy

Thank you, Roy!


[AH-52] Consider moving from Webpack to Vite

consider Babel (seems like not needed, but need to double check e.g. browserlist)

Vite is good, but seems like to lightweight for such solution not including vital parts e.g. PWA-based bundling, etc.


apply action not documented.

The apply action used in the ApplyService doesn't seem to be documented in the bullhorn api. Can I have more details on this action and any other missing api actions. Thanks.
Current behavior
No documentation for '/rest-services/${corpToken}/apply/${jobID}'. I have forked the project and started investigating a client request to alter the behaviour of the application, without context for the current action it will be hard to fit the client request.
Expected behavior
Full api documentation.

Bullhorn does not supply documentation for the public-rest api... we had to proxy their api to have access to the functionality we need.


Work around the text/markdown support in setup.py

This installs pandoc and sneakily changes format of README.md from Markdown to reStructuredText, so that PyPI upload doesn't choke.

https://github.com/pypa/warehouse/pull/4099#issuecomment-393620919
https://github.com/pypa/warehouse/issues/4079#issuecomment-392924698

Thanks for solving this issue.


Modal not opening correctly in phone-view

Steps to reproduce the behavior:
Open lightbox (modal) on an apple iPhone.
Expected behavior:
Not to stop and not require interaction for modal to appear correctly
Actual behavior:
Modals doesn't open automatically when using it with a mobile device,
instead, all images are lined up next to each other and the correct view only shows up when you actually press it again. It looks really weird and something is probably wrong.

I got the same issue here when opening on iPhone. It works perfectly on android phone.
Looked for a similar issue but couldn't find any related in the list. Anyone could shed a light on this behavior?

I've got the exact same issue. It's hard to pinpoint to a specific thing that's wrong. After refreshing it looks like it's working "normally". It looks like not all styles are loaded or something like that.

Same issue here - tested Safari and Chrome on iOS 13.1.3


Issue with getting the package

Ran: go get github.com/gotmc/libusb
Expected: No issues
Got: # github.com/gotmc/libusb ../../workspace/src/github.com/gotmc/libusb/context.go: In function 'set_debug': ../../workspace/src/github.com/gotmc/libusb/context.go:11:34: error: 'LIBUSB_OPTION_LOG_LEVEL' undeclared (first use in this function); did you mean 'LIBUSB_ERROR_NO_MEM'?  //   return libusb_set_option(ctx, LIBUSB_OPTION_LOG_LEVEL, level);                                   ^~~~~~~~~~~~~~~~~~~~~~~                                   LIBUSB_ERROR_NO_MEM ../../workspace/src/github.com/gotmc/libusb/context.go:11:34: note: each undeclared identifier is reported only once for each function it appears in

It appears you're using libusb 1.0.21. There was a breaking change in libusb 1.0.22 related to libusb_set_debug, which was fixed in commit 558d53e. Is there any way you could install libusb 1.0.22 to see if this fixes the problem?

I added a v1.0.21 release to the last commit before fixing the v1.0.22 breaking change, so you could install v1.0.21 to see if that resolves the problem.

What to do next if there is a problem with v1.0.21?


[@vitejs/plugin-react] VS Code Breakpoints do not get hit after first fast refresh in plugin-react in new project

Describe the bug
After creating a brand new Vite project using create-vite(yarn create vite) breakpoints in VS Code do not get hit after the first change and refresh.
Refresh meaning the fast HMR refresh.  The app refreshes well in the browser but it leaves the VS Code debugger in an unusable state.
Refreshing the browser, or refresh through VS Code allows breakpoints until the next refresh.
Reproduction
Reproduce:

Create a react-ts vite project using yarn create vite
run yarn dev
Inside of VS Code create the following launch.json:

{
	// Use IntelliSense to learn about possible attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
		{
			"name": "Launch Chrome",
			"request": "launch",
			"type": "pwa-chrome",
			"url": "http://localhost:3000",
			"webRoot": "${workspaceFolder}"
		}
	]
}

Place a breakpoint on

  const [count, setCount] = useState(0)

Debug the app in vs code
Notice your breakpoint is hit
Change the line "Hello Vite + React" to "Test breakpoint" and save
Notice the app has successfully updated in the browser
Notice that your breakpoint is not hit
Refresh the page and notice your breakpoint is now hit

System Info
System:
    OS: Windows 10 10.0.19041
    CPU: (12) x64 AMD Ryzen 5 3600XT 6-Core Processor

    Memory: 2.59 GB / 15.91 GB
  Binaries:
    Node: 14.15.4 - C:\apps\dev\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.10 - C:\apps\dev\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (93.0.961.47)
    Internet Explorer: 11.0.19041.1202

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

me too, I can't debugging in chrome dev tool, It's a serious bug.


Kerning error

On the video published by @Shreenabh664 on Twitter (https://twitter.com/shreenabha/status/1294652394739912704), at 0 minutes 31 seconds, we can see a kerning error in the text. See https://en.wikipedia.org/wiki/Kerning about kerning.
We can see too space between "T" and "a" in "Taking", and too space between "l" and "f" in "half".
Sample .tex code:
\documentclass{article}
\begin{document}
	\emph{Taking half derivative}

	$Taking\:half\:derivative$

	$\mathit{Taking\:half\:derivative}$
\end{document}

Result:

The first and third lines are correct, the second is very ugly typography. For italic text, if you cannot be in text mode, you must use \mathit (and \: for medium spaces between words). In math mode, $word$ is the multiplication of the variables "w", "o", "r" and "d", and $\mathit{word}$ is the italicized word "word".

Sure! The simple reason for this was treating text as a Math element and comes as a choice for the user.
There is a full section dedicated to this on our website magnum.shreenabh.com
A simple fix for this is to enclose any text in \text{Taking half derivative}.


Make -r mandatory when -i (indexing only)?

This is more of a failsafe. I just realised that indexing will run with default parameters when read files not given. That is
strobealign -i idx_path ref
strobealign idx_path reads1 reads2

will index with default params (150bp reads i think?) even though reads may be shorter or longer.
Related: function estimate_read_length estimates read length when at least one read file is given, but what happens when strobealign -i idx_path ref is run? I is not clear as parameters are not printed to output.

I think we should describe what the use cases for separate index creation are. Some could be:

A user wants to map many small Illumina libraries with similar read length against the human genome and save time by pre-computing the index.
A cluster admin wants to provide a couple of genomes to their users along with pre-computed indices.

It’s an added challenge that the index is read-length specific. For case 1, the user needs to be aware that the index they created is only usable for those libraries that have roughly the same read length. For case 2, the admin would need to create multiple indices for different read lengths.
In any case, we need to clearly communicate that an index is read-length specific. Perhaps one way to do this is to include the read length in the index file name. As your issue title implies, we should probably focus on the read length as the main criterion. The IndexParameters::from_read_length function has six different indexing presets depending on the read length, so these could be the six different index variants that are possible.
So perhaps something like GRCh38.sti175 would be the index for the "read_length<=175" preset. That makes it possible to have multiple indices next to each other.
If someone wants to deviate from the presets (override k, s, l, u, etc.), we could require that they do not use a pre-computed index (or they get a file name without the read length in it).

I agree with your proposal and have made a suggestion based on what you write here in #115. I think it takes care of making it clear that index is read length specific.


MB-6643 Swap PPM image on Move 101 page

Description
The Move 101 page previously displayed foreign service members so the needed to be swapped out.
Places where the image changed:

Move 101 page, first image.
Storybook MilmoveCard component.

Not sure if this one should change. Only reason I did was since it was using the same image that was being replaced on the Move 101. I can change it back if that's preferred.

Setup
MilMove 101 Page
I'm not sure if there's an easier way to get to the screen in question or not, but this is how I got there:
Run local servers:

 make server_run

 make client_run

Then:

Log in as a user who hasn't started a shipment yet.
Click "Plan your shipments".
You should now see the updated image (the one in the "Hold on to things you'll need quickly" section).

Storybook

Run storybook

 make storybook

Navigate to the MilmoveCard component.

There are two versions:

Exdented
Indented

Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story

Screenshots
MilMove 101
Before:

After:

Storybook
Before:

After:

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-6643

  Generated by :no_entry_sign: dangerJS against 69e6f98b963a1716e017a6636169ae030c295b08

Just want to confirm that it should be .png and not a .jpg.

That's what the image was that was in the jira story. I didn't know if I should convert it.

And to answer your question, yes, the storybook component should be changed as well.

Awesome, thanks for confirming!