Error modesetting with "try skipping buffer allocation" commit

Using sway (master) with wlroots commit #3085  I get errors modesetting my displays:
00:00:00.000 [INFO] [sway/main.c:311] wlroots version 0.15.0
00:00:00.001 [INFO] [sway/main.c:118] Linux <hostname> 5.13.8 #1 SMP PREEMPT Wed Aug 4 20:37:47 CEST 2021 x86_64 GNU/Linux
...
00:00:00.006 [INFO] [wlr] [backend/backend.c:234] Found 1 GPUs
00:00:00.006 [INFO] [wlr] [backend/drm/backend.c:173] Initializing DRM backend for /dev/dri/card0 (amdgpu)
00:00:00.006 [DEBUG] [wlr] [backend/drm/drm.c:85] Using atomic DRM interface
00:00:00.006 [DEBUG] [wlr] [backend/drm/drm.c:98] ADDFB2 modifiers supported
00:00:00.006 [INFO] [wlr] [backend/drm/drm.c:260] Found 6 DRM CRTCs
00:00:00.006 [INFO] [wlr] [backend/drm/drm.c:187] Found 13 DRM planes
00:00:00.019 [INFO] [wlr] [render/egl.c:175] Supported EGL client extensions: EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_MESA_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
00:00:00.019 [DEBUG] [wlr] [render/egl.c:413] Using EGL device /dev/dri/card0
00:00:00.023 [INFO] [wlr] [render/egl.c:316] Supported EGL display extensions: EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_create_context_no_error EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_MESA_query_driver EGL_WL_bind_wayland_display
00:00:00.023 [INFO] [wlr] [render/egl.c:318] Supported EGL device extensions: EGL_EXT_device_drm EGL_EXT_device_drm_render_node
00:00:00.023 [INFO] [wlr] [render/egl.c:320] Using EGL 1.5
00:00:00.023 [INFO] [wlr] [render/egl.c:321] EGL vendor: Mesa Project
00:00:00.023 [DEBUG] [wlr] [render/egl.c:150] Supported DMA-BUF formats: AB4H XB4H AR30 XR30 AB30 XB30 AR24 AB24 XR24 XB24 AR15 RG16 R8   R16  GR88 GR32 YUV9 YU11 YU12 YU16 YU24 YVU9 YV11 YV12 YV16 YV24 NV12 P010 P012 P016 NV16 AYUV XYUV Y410 Y412 Y416 YUYV UYVY Y210 Y212 Y216
00:00:00.023 [DEBUG] [wlr] [render/egl.c:151] EGL DMA-BUF format modifiers supported
00:00:00.024 [DEBUG] [wlr] [render/egl.c:439] Using EGL_PLATFORM_DEVICE_EXT
00:00:00.024 [INFO] [wlr] [render/gles2/renderer.c:727] Creating GLES2 renderer
00:00:00.024 [INFO] [wlr] [render/gles2/renderer.c:728] Using OpenGL ES 3.2 Mesa 21.3.0-devel (git-566970f273)
00:00:00.024 [INFO] [wlr] [render/gles2/renderer.c:729] GL vendor: AMD
00:00:00.024 [INFO] [wlr] [render/gles2/renderer.c:730] GL renderer: AMD Radeon RX 6900 XT (SIENNA_CICHLID, DRM 3.41.0, 5.13.8, LLVM 14.0.0)
00:00:00.024 [INFO] [wlr] [render/gles2/renderer.c:731] Supported GLES2 extensions: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_s3tc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_EXT_draw_instanced GL_EXT_texture_sRGB_decode GL_OES_EGL_image GL_OES_depth_texture GL_AMD_performance_monitor GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_NV_conditional_render GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_OES_viewport_array GL_ANGLE_pack_reverse_row_order GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_occlusion_query_boolean GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness GL_KHR_texture_compression_astc_ldr GL_NV_pixel_buffer_object GL_OES_depth_texture_cube_map GL_OES_required_internalformat GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_sRGB_write_control GL_EXT_separate_shader_objects GL_EXT_shader_group_vote GL_EXT_shader_implicit_conversions GL_EXT_shader_integer_mix GL_EXT_tessellation_point_size GL_EXT_tessellation_shader GL_ANDROID_extension_pack_es31a GL_EXT_base_instance GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_gpu_shader5 GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box GL_EXT_render_snorm GL_EXT_shader_io_blocks GL_EXT_texture_border_clamp GL_EXT_texture_buffer GL_EXT_texture_cube_map_array GL_EXT_texture_norm16 GL_EXT_texture_view GL_KHR_blend_equation_advanced GL_KHR_context_flush_control GL_KHR_robust_buffer_access_behavior GL_NV_image_formats GL_OES_copy_image GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_gpu_shader5 GL_OES_primitive_bounding_box GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_io_blocks GL_OES_shader_multisample_interpolation GL_OES_tessellation_point_size GL_OES_tessellation_shader GL_OES_texture_border_clamp GL_OES_texture_buffer GL_OES_texture_cube_map_array GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array GL_OES_texture_view GL_EXT_blend_func_extended GL_EXT_buffer_storage GL_EXT_float_blend GL_EXT_geometry_point_size GL_EXT_geometry_shader GL_EXT_shader_samples_identical GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_RG8 GL_KHR_no_error GL_KHR_texture_compression_astc_sliced_3d GL_OES_EGL_image_external_essl3 GL_OES_geometry_point_size GL_OES_geometry_shader GL_OES_shader_image_atomic GL_EXT_clip_cull_distance GL_EXT_disjoint_timer_query GL_EXT_texture_compression_s3tc_srgb GL_EXT_window_rectangles GL_MESA_shader_integer_functions GL_EXT_clip_control GL_EXT_color_buffer_half_float GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_texture_compression_bptc GL_KHR_parallel_shader_compile GL_NV_alpha_to_coverage_dither_control GL_AMD_framebuffer_multisample_advanced GL_EXT_EGL_image_storage GL_EXT_texture_shadow_lod GL_INTEL_blackhole_render GL_MESA_framebuffer_flip_y GL_NV_compute_shader_derivatives GL_EXT_demote_to_helper_invocation GL_EXT_depth_clamp GL_EXT_texture_query_lod GL_MESA_bgra
00:00:00.027 [DEBUG] [wlr] [render/allocator.c:30] Trying to create gbm allocator
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 8 VGPRS: 32 Code Size: 44 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 24 VGPRS: 32 Code Size: 128 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 24 VGPRS: 32 Code Size: 124 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 24 VGPRS: 32 Code Size: 124 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 32 VGPRS: 16 Code Size: 272 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.028 [DEBUG] [wlr] [GLES2] Shader Stats: SGPRS: 32 VGPRS: 16 Code Size: 268 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0
00:00:00.029 [DEBUG] [wlr] [render/gbm_allocator.c:196] Created GBM allocator with backend drm
00:00:00.029 [DEBUG] [wlr] [render/gbm_allocator.c:199] Using DRM node /dev/dri/card0
00:00:00.029 [INFO] [sway/main.c:358] Starting sway version 1.6-f4cda515 (Aug  4 2021, branch 'master')
00:00:00.029 [DEBUG] [sway/server.c:61] Initializing Wayland server
00:00:00.029 [DEBUG] [wlr] [types/wlr_idle.c:247] idle manager created
00:00:00.029 [INFO] [wlr] [backend/noop/backend.c:59] Creating noop backend
00:00:00.029 [INFO] [wlr] [backend/headless/backend.c:227] Creating headless backend with parent renderer
00:00:00.029 [DEBUG] [wlr] [render/allocator.c:30] Trying to create gbm allocator
00:00:00.032 [DEBUG] [wlr] [render/gbm_allocator.c:196] Created GBM allocator with backend drm
00:00:00.032 [DEBUG] [wlr] [render/gbm_allocator.c:199] Using DRM node /dev/dri/renderD128
00:00:00.035 [INFO] [sway/config.c:406] Loading config from /home/username/.config/sway/config
...
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 93: # Output configuration
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 94: # ----------------------------------------------------------------------------
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 95: output $output1 resolution 3440x1440@160Hz pos 0 565
00:00:00.036 [INFO] [sway/commands.c:377] Config command: output $output1 resolution 3440x1440@160Hz pos 0 565
00:00:00.036 [INFO] [sway/commands.c:397] After replacement: output DP-1 resolution 3440x1440@160Hz pos 0 565
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: resolution 3440x1440@160Hz pos 0 565
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: pos 0 565
00:00:00.036 [DEBUG] [sway/config/output.c:210] Adding non-wildcard output config
00:00:00.036 [DEBUG] [sway/config/output.c:227] Config stored for output DP-1 (enabled: -1<EMAIL_ADDRESS>position 0,565 scale -1.000000 subpixel unknown transform -1) (bg (null) (null)) (dpms 0) (max render time: -1)
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 96: output $output1 adaptive_sync on
00:00:00.036 [INFO] [sway/commands.c:377] Config command: output $output1 adaptive_sync on
00:00:00.036 [INFO] [sway/commands.c:397] After replacement: output DP-1 adaptive_sync on
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: adaptive_sync on
00:00:00.036 [DEBUG] [sway/config/output.c:204] Merging on top of existing output config
00:00:00.036 [DEBUG] [sway/config/output.c:227] Config stored for output DP-1 (enabled: -1<EMAIL_ADDRESS>position 0,565 scale -1.000000 subpixel unknown transform -1) (bg (null) (null)) (dpms 0) (max render time: -1)
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 97: #output $output1 resolution<EMAIL_ADDRESS>pos 0 0
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 98: #output $output1 resolution<EMAIL_ADDRESS>pos 0 0
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 99:
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 100: output $output2 resolution 2560x1440 pos 3440 0
00:00:00.036 [INFO] [sway/commands.c:377] Config command: output $output2 resolution 2560x1440 pos 3440 0
00:00:00.036 [INFO] [sway/commands.c:397] After replacement: output DP-2 resolution 2560x1440 pos 3440 0
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: resolution 2560x1440 pos 3440 0
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: pos 3440 0
00:00:00.036 [DEBUG] [sway/config/output.c:210] Adding non-wildcard output config
00:00:00.036 [DEBUG] [sway/config/output.c:227] Config stored for output DP-2 (enabled: -1<EMAIL_ADDRESS>position 3440,0 scale -1.000000 subpixel unknown transform -1) (bg (null) (null)) (dpms 0) (max render time: -1)
00:00:00.036 [DEBUG] [sway/config.c:820] Read line 101: output $output2 transform 90
00:00:00.036 [INFO] [sway/commands.c:377] Config command: output $output2 transform 90
00:00:00.036 [INFO] [sway/commands.c:397] After replacement: output DP-2 transform 90
00:00:00.036 [DEBUG] [sway/commands.c:428] Subcommand: transform 90
00:00:00.036 [DEBUG] [sway/config/output.c:204] Merging on top of existing output config
00:00:00.036 [DEBUG] [sway/config/output.c:227] Config stored for output DP-2 (enabled: -1<EMAIL_ADDRESS>position 3440,0 scale -1.000000 subpixel unknown transform 3) (bg (null) (null)) (dpms 0) (max render time: -1)
...
00:00:01.086 [INFO] [wlr] [backend/drm/drm.c:1228] Scanning DRM connectors on /dev/dri/card0
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1282] Found connector 'DP-1'
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1318] 'DP-1' connected
00:00:01.088 [DEBUG] [wlr] [backend/drm/drm.c:1319] Current CRTC: 77
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1330] Physical size: 800x330
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1361] Detected modes:
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   3440x1440@143923 (preferred)
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   3440x1440@60001 (preferred)
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   3440x1440@160000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   3440x1440@99990
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1200@143923
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@74977
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@59940
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@50000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1600x1200@143923
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1680x1050@59954
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1600x900@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x1024@75025
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x1024@60020
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1440x900@143923
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x800@59810
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1152x864@59972
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@59940
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@50000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   1024x768@60004
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   800x600@60317
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   720x576@50000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@59940
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@60000
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@59940
00:00:01.088 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1282] Found connector 'DP-2'
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1318] 'DP-2' connected
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1319] Current CRTC: 80
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1330] Physical size: 600x340
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1361] Detected modes:
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   2560x1440@59951 (preferred)
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1200@59951
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   2048x1080@59998
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   2048x1080@23997
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1920x1080@50000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1600x1200@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1680x1050@59951
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x1024@75025
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x1024@60020
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1440x900@59951
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x800@59951
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1152x864@75000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1280x720@50000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1024x768@75029
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   1024x768@60004
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   800x600@75000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   800x600@60317
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x576@50000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x576@50000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x480@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@75000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@60000
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   640x480@59940
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1383]   720x400@70082
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1282] Found connector 'DP-3'
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1282] Found connector 'HDMI-A-1'
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1082] Reallocating CRTCs
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1093] State before reallocation:
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1099]   'DP-1' crtc=0 state=1 desired_enabled=1
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1099]   'DP-2' crtc=1 state=1 desired_enabled=1
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1099]   'DP-3' crtc=-1 state=0 desired_enabled=0
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1099]   'HDMI-A-1' crtc=-1 state=0 desired_enabled=0
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1150] State after reallocation:
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1157]   'DP-1' crtc=0 state=1 desired_enabled=1
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1157]   'DP-2' crtc=1 state=1 desired_enabled=1
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1157]   'DP-3' crtc=-1 state=0 desired_enabled=0
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:1157]   'HDMI-A-1' crtc=-1 state=0 desired_enabled=0
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1435] connector DP-1: Requesting modeset
00:00:01.091 [DEBUG] [sway/desktop/output.c:839] New output 0x55a69fb1a960: DP-1
00:00:01.091 [DEBUG] [sway/config/output.c:351] Turning on output DP-1
00:00:01.091 [DEBUG] [sway/config/output.c:355] Set DP-1 mode to 3440x1440 (160.000000 Hz)
00:00:01.091 [DEBUG] [sway/config/output.c:269] Assigning configured mode to DP-1
00:00:01.091 [DEBUG] [sway/config/output.c:329] Output DPI: 109.220000x110.836364
00:00:01.091 [DEBUG] [sway/config/output.c:382] Auto-detected output scale: 1.000000
00:00:01.091 [DEBUG] [sway/config/output.c:390] Set DP-1 adaptive sync to 1
00:00:01.091 [DEBUG] [sway/config/output.c:412] Committing output DP-1
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:730] connector DP-1: Modesetting with '3440x1440@160000mHz'
00:00:01.091 [ERROR] [wlr] [backend/drm/drm.c:743] connector DP-1: Missing FB in modeset
00:00:01.091 [ERROR] [sway/config/output.c:417] Failed to commit output DP-1
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:1435] connector DP-2: Requesting modeset
00:00:01.091 [DEBUG] [sway/desktop/output.c:839] New output 0x55a69fa52a40: DP-2
00:00:01.091 [DEBUG] [sway/config/output.c:351] Turning on output DP-2
00:00:01.091 [DEBUG] [sway/config/output.c:355] Set DP-2 mode to 2560x1440 (-1.000000 Hz)
00:00:01.091 [DEBUG] [sway/config/output.c:269] Assigning configured mode to DP-2
00:00:01.091 [DEBUG] [sway/config/output.c:371] Set DP-2 transform to 3
00:00:01.091 [DEBUG] [sway/config/output.c:329] Output DPI: 60.960000x191.247059
00:00:01.091 [DEBUG] [sway/config/output.c:382] Auto-detected output scale: 1.000000
00:00:01.091 [DEBUG] [sway/config/output.c:412] Committing output DP-2
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:730] connector DP-2: Modesetting with '2560x1440@59951mHz'
00:00:01.091 [ERROR] [wlr] [backend/drm/drm.c:743] connector DP-2: Missing FB in modeset
00:00:01.091 [ERROR] [sway/config/output.c:417] Failed to commit output DP-2
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:662] connector DP-1: Output has a desired mode and a CRTC, attempting a modeset
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:730] connector DP-1: Modesetting with '3440x1440@160000mHz'
00:00:01.091 [ERROR] [wlr] [backend/drm/drm.c:743] connector DP-1: Missing FB in modeset
00:00:01.091 [DEBUG] [wlr] [backend/drm/drm.c:662] connector DP-2: Output has a desired mode and a CRTC, attempting a modeset
00:00:01.091 [INFO] [wlr] [backend/drm/drm.c:730] connector DP-2: Modesetting with '2560x1440@59951mHz'
00:00:01.091 [ERROR] [wlr] [backend/drm/drm.c:743] connector DP-2: Missing FB in modeset
00:00:01.091 [INFO] [wlr] [backend/headless/backend.c:28] Starting headless backend

Outputs are not enabled and sway aborts.
Rolling back 1 wlroots commit fixes the issue for me.

Can you try https://github.com/swaywm/wlroots/pull/3087?

That fixed the issue. Thank you.


During autotagging text is logged at cursor position, not end of screen

From<EMAIL_ADDRESS>on November 05, 2014 15:14:51
What version of ComicTagger are you using? 1.1.15-beta On what operating system (Mac, Linux, Windows)? What version? Mac GUI or command line? GUI What steps will reproduce the problem? 1. Auto tag some comics
2. Click somewhere on the screen
3. Text will begin to print at the cursor location What is the expected output? What do you see instead? The text should continue to print at the end of the log rather then at the cursor.
Original issue: http://code.google.com/p/comictagger/issues/detail?id=59

fixed in #214


re-apply fix for msvc

Let's get this in as is for v0.5. We can revisit approaches that remove the ifdef in the future.
The WG can decide which versions are okay to submit with. I assume it'll be okay for Windows submitters to use the loadgen with this change included.

Thanks Brian!!


AWS SDK for Delphi

[AWS SDK for Dephi](https://github.com/landgraf-dev/aws-sdk-delphi). `[Delphi]` Unofficial AWS (Amazon Web Services) SDK for Delphi.

Added, thanks! But it would be better if you mentioned that it requires paid libs. I'll add a bold warning regarding this.


Pass history event header fields to StartWorkflow activation job

Why?
Used by interceptors to pass metadata from the client
Checklist

How was this tested:
Tested with the Node SDK

The headers are attached to a specific workflow history event which correlates to an activation job in the core-lang terminology.
As far as ease of use, it's easier for the headers to be attached to a single job and not the whole activation.


chore: Update Rubocop to 1.64.0

Rubocop 1.64.0 Release Notes.
The main introduction is the Style/SuperArguments linter.
It also lints the Vitess Propagator. It looks like this propagator is not currently being tested, so I'll add that to the CI in a separate PR.

Once this is merged, we can continue the release.


[script]ndarray constructor: support Any type

ndarray constructor: support shape  is type any during compiling
ndarray constructor: report error when type of shape is invalid ( #64 )

Thanks @bhshu


Allow loading qboard from network JSON

And make signatures in files.ts how they should have been
Updated version of #103
Resolves #102
You may want to drop c73dc71

not sure i see the purpose of this (again)

Well, I believe the first two commits should happen regardless of implementing the feature.
Then, the feature commit, cf343d1afca0ceb07c026a9de2104eefc23824e0, really just adds a one-liner to read the query params and set a default pagesJSON if requested by the user.
It's up to you whether to include the final commit, but I generally would lean towards doing that (if for nothing else, to improve the experience for developers who use qboard and happen to run into an error while using this feature).
Benefits (they're really all the same):

Allows users to host qboard files such that anyone can immediately use them. I have done this a few times when creating issues on this repo itself. (Note also that I couldn't have done it by uploading the JSON files since GitHub doesn't support that.)
Ease of use:

Whenever I give a qboard json file to others to use, they don't know what to do with it. This is the case even when I explain to non-qboard users how to open the file.

Allows direct linking:

Should someone have a website with templates, they can just provide a direct link to the templates for use by the end user.
This is huge:

For sharing math proofs, diagrams, etc (relates to ease of use)
For developer profiles: devs can just link to the pre-loaded qboard file instead of linking to qboard, the json file, and providing instructions
For product showcasing, et:c ^
For schooling:

to link to slides/notes that were generated from a qboard lecture
for teachers to make interactive, no-code activities
to give guided lecture note sheets, for students to fill out while following lecture

For dogfooding: you can now direct link to your sample qboard file

None of the past concerns seem to apply:

YANGNI: I have used it extensively, in all of the above use cases
Out of scope:

In general, this only applies when implementing a completely new feature. This PR is really just giving a new interface for existing functionality.
Should collaboration be implemented, it would use almost exactly this at one stage of the document lifecycle.

Code clutter: It's a one-liner that does exactly what it looks like it does.
Burden to the user: A user does not need to use this feature if they don't want to. This is unlike other features in other projects, such as async/await in ES, that force the user to learn to use it even if they don't want to.
Code bloat/dependency bloat/too much added to the build:

The dependency @mehra/ts has no dependencies itself (see this project's package-lock)
Suppose it is not tree-shakeable (although I believe it should be).  I generally would not worry about this.


Add fields about electronic workflows following the structure of BT-92, BT-743, BT-93

See also https://github.com/open-contracting-extensions/european-union/issues/5#issuecomment-517271339

The electronicInvoicing field would use the shared permissions code list (allowed, required, notAllowed).

These fields should go to a Contract terms extension: https://github.com/eForms/eForms/issues/322#issuecomment-517403313

Reopened until work starts on the Contract terms extension, as a reminder.

Here is the permission code list. We may need to make the subject more generic than "tenderers", since in some cases the field may apply to the buyer.
required,Required,The tenderers are required to perform the activity.
allowed,Allowed,The tenderers are allowed to perform the activity.
notAllowed,Not allowed,The tenderers are not allowed to perform the activity.

Here is the schema part:
"hasElectronicPayment": {
          "title": "Electronic payment used",
          "description": "Whether electronic payment is used.",
          "type": [
            "boolean",
            "null"
          ]
      },
      "hasElectronicOrdering": {
          "title": "Electronic ordering used",
          "description": "Whether electronic ordering is used.",
          "type": [
            "boolean",
            "null"
          ]
      },
      "electronicInvoicing": {
          "title": "Electronic invoicing",
          "description": "",
          "type": ["string", "null"],
          "openCodelist": false,
          "codelist": "permission.csv",
          "enum": [
            "required",
            "allowed",
            "notAllowed",
            null
          ]
      }

A has* field implies a boolean value, but these are permission levels. I suggest removing the prefix has.
We can change the code descriptions to "The activity is [required, allowed, not allowed]."

So (1) I misread which fields used permission levels and which were boolean :) (I updated my earlier comment).
However, so far, we have used has* when there is another object that describes the attribute in more detail. Here, we just have a boolean attribute, which elsewhere we don't prefix with has, e.g. successiveReduction. Do you think it's likely that there will be e.g. an electronicPayment object in future? If not, should we remove the has prefix?

I think

we shouldn't burn bridges to an electronicPayment or electronicOrdering object, as I can perfectly imagine data about these things. They are not leaf concepts by nature
the presence or absence of a detailed object shouldn't determine the spelling of the label of the boolean field. Apparently, hasEnquiries is the only boolean field in core OCDS, and it follows this pattern. I think we should stick to it.

OK to update the code descriptions to "The activity is [code]".

Sounds good, re: has and OK to update code descriptions.

We have implemented these fields in the contractTerms extension.


map first, then flatten

to properly implement flatmap

Coverage decreased (-1.4%) to 98.592% when pulling 1aeb97103258813af9a414c43f6810a6a474acf4 on fix_flat_map into 77d5d69749bccca77107acecc03d2b815caa6c7f on master.

Coverage remained the same at 100.0% when pulling da7865adbf75b87d969cf9a73d6b1ebb79d8cbc1 on fix_flat_map into 77d5d69749bccca77107acecc03d2b815caa6c7f on master.

Coverage remained the same at 100.0% when pulling da7865adbf75b87d969cf9a73d6b1ebb79d8cbc1 on fix_flat_map into 77d5d69749bccca77107acecc03d2b815caa6c7f on master.

Coverage remained the same at 100.0% when pulling 7d501453d52a07edad87e7614f573a58ce88e718 on fix_flat_map into 77d5d69749bccca77107acecc03d2b815caa6c7f on master.

Coverage remained the same at 100.0% when pulling 7d501453d52a07edad87e7614f573a58ce88e718 on fix_flat_map into 77d5d69749bccca77107acecc03d2b815caa6c7f on master.


The location of the dialog title and the buttons 'Save' and 'Cancel' are incorrect if drag the bottom scrollbar to right

Storage Explorer Version: 1.33.0-dev (96)
Build Number: 20240204.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.3(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running test case
Regression From: Previous release (1.32.1)
Steps to Reproduce

Expand one storage account -> Blob Containers.
Right click one blob container -> Click 'Manage Stored Access Policies...'.
Click 'Add' on the 'Access Policies' dialog.
Drag the scrollbar to the right.
Check whether the location of the dialog title and the buttons 'Save' and 'Cancel' are correct.

Expected Experience
The location of the dialog title and the buttons 'Save' and 'Cancel' are correct.

Actual Experience
The location of the dialog title and the buttons 'Save' and 'Cancel' are incorrect.

This does not reproduce if there is already at least one stored access policy for the container. The root of the issue in in the dialog window auto-sizing mechanism. It only runs once when the window is opened. In this case, an empty access policy list takes less space, so the dialog does grow as much when there are policies. But when a user adds a policy to the list, the dialog suddenly needs more space.
I think the answer here is not to remove all the labels when the list is empty. That way, the dialog is more correctly sized when it opens.

Hi @craxal Verified this issue on the main build 20240207.6. This issue doesn't reproduce on the new dialog.
There is an extra scrollbar on the new dialog if add five access policies for blob containers.
Could you please help to take a look?

@v-vianya Spacing should now be fixed.

Verified this issue on the main build 20240208.4. Fixed.


Add PolarisDAO space

[x] The threshold is set to 40000 $ARIS
[ ] Logo is same with the one on statemine asset page https://statemine.statescan.io/asset/16
[x] Currently only Statemine, maybe multiple chains when our multiple chain support is ready.

file
symbol&icon-polarisdao.zip
preview

[ ] Replace Kintsugi space image

file
symbol-kintsugi.png.zip

[ ] Please replace the space image and icon

file
polarisdao.zip


runScript(filename) should check if CPG is already loaded

Looks like run(filename) (without the cpg parameter) loads cpg.bin.zip by deafult. This can be quite slow for large graphs. Can we check if a graph is already loaded and use that if so?

As discussed with @fabsx00  remove the standalone runScript(filename) and instead add an extension to Cpg that allows something along the lines of cpg.runScript(filename) that translates to runScript(filename, cpg)

Resolved in https://github.com/ShiftLeftSecurity/joern/pull/180


[Xiaomi/Chrome] - Update Email forms prefilled

When going to Update Email, email and password forms are prefilled by autocomplete but shouldn't be because we will be using new ones.

After consulting with @kacperknapik, I will take this one. Assigned by comment due to lack of repository access yet.

Steps for QA:

Sign in with credentials & save them in browser.
Go to My account > Email Address
Update Email view form shouldn't be prefilled with saved credentials.

Tested on chrome, safari and firefox. Now "update email" form isn't prefilled when we save our credentials on the browser.


Update outdated links

Changing explorer and source code links to reflect present configuration: !6793

Thanks for the updates, @maxtori!


Large projects

Does it code large projects correctly?

Theoretically there is no limit, but currently the generated large projects don't work well. There is some work in roadmap to do better.

Theoretically there is no limit, but currently the generated large projects don't work well. There is some work in roadmap to do better.

I know that the similar project "Aider" uses Universal-Ctags to better keep track off and understand large code. Maybe that's something for the devs here to look into?

@MightEnlightenYou yes. write it later


Still having problems to complie to dll

You didn't say what kind of error you got, but I guess it's some kind of "something isn't initialised or available" error. The reason for that would be that you are calling PyInit_some() directly, which is not the right way to initialise an embedded module.
Instead, call PyImport_AppendInittab("some", &PyInit_some) before calling Py_initialize().
We should make that clear in the documentation. Currently, only the CPython docs mention it.

Not any error messages
I found some problems that I may describe
In fact, no function can run, such as print
i modify the code:
dllmain.c
#include <Python.h>
#include <Windows.h>
#include "some.h"

extern __declspec(dllexport) char*  __stdcall test() {
    return _test();
}

BOOL WINAPI DllMain(HINSTANCE hinstDLL,DWORD fdwReason,LPVOID lpReserved) {
    switch( fdwReason ) {
        case DLL_PROCESS_ATTACH:
            PyImport_AppendInittab("some", &PyInit_some) ;
            Py_Initialize();
            break;
        case DLL_PROCESS_DETACH:
            Py_Finalize();
            break;
    }
    return TRUE;
}

some.pyx
cdef public char* _test():
    return "ok return well"

and write a c program to call it:
#include "stdio.h"

extern char* __stdcall test(void);
int main(void){
    printf("%s",test());
}

the result is:
D:\msys64\home\songwz\cytest\diff_no>loaddll
ok return well
but i change the code:
some.pyx
cdef public char* _test():
    print("hello")
    return "ok return well"

He will not return anything
The code below is the same
def hello():
    pass
cdef public char* _test():
    hello()
    return "ok return well"

But the code below works：
cdef hello():   #<-----cdef works
    pass
cdef public char* _test():
    hello()
    return "ok return well"

Originally posted by @yafengabc in https://github.com/cython/cython/issues/3509#issuecomment-613237803

Let's keep this in context. I'll reply in the original ticket.


Project Proposal: Memory game

Overview
Cards memory game is a board game
Key Features
No response
Additional Information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have starred the repository
[X] I'm a gssoc-24-extd contributor
[X] I want to work on this project proposal
[X] It is not duplicate

@Mansi07sharma give more details


Support for C.H.I.P.

Hi,
First of all, great library! I use it to control my porch light through a component in Home Assitant. I recently migrated my setup from a RPi to a C.H.I.P. and noticed that this package does not work anymore. This because RPi.GPIO of course only works on a RPi. However there is a (almost) drop-in replacement for this dependency called CHIP_IO. The only method that CHIP_IO seems to lack is GPIO.setmode.
With this patch a got the library working on the C.H.I.P.:
diff --git a/rpi_rf/rpi_rf.py b/rpi_rf/rpi_rf.py
index 3949169..72c1e70 100644
--- a/rpi_rf/rpi_rf.py
+++ b/rpi_rf/rpi_rf.py
@@ -6,7 +6,10 @@ import logging
 import time
 from collections import namedtuple

-from RPi import GPIO
+try:
+    from RPi import GPIO
+except:
+    from CHIP_IO import GPIO

 MAX_CHANGES = 67

@@ -54,8 +57,11 @@ class RFDevice:
         self.rx_proto = None
         self.rx_bitlength = None
         self.rx_pulselength = None
-
-        GPIO.setmode(GPIO.BCM)
+        # the method 'setmode' is not available in CHIP_IO.GPIO
+        try:
+            GPIO.setmode(GPIO.BCM)
+        except:
+            pass
         _LOGGER.debug("Using GPIO " + str(gpio))

     def cleanup(self):

If you are willing to add support for C.H.I.P. I could make a PR out of this patch.
Cheers!

I think it would make more sense to make the module injectable by some means. This could then also be used for Beaglebone black with Adafruit_BBIO.

Yes, I agree that using injection would be a cleaner approach.
I can imagine that an important requirement is to stay backwards compatible, so that the default gpio module would be RPi version.

Hello guys, i started porting rpi-rf (that i love) to CHIP using the new CHIP_IO.GPIO from @xtacocorex
It's working now... or sort of... you can check it out here https://github.com/nunojusto/CHIP-rf/
The problem is that i cannot have clear results and i', working directly with CHIP_IO guy to solve some of the error.
Please try and help if you can :)
Thankx
@bachp @chrisvis @milaq

The setmode() function isn't supported on the BBB either (CHIP_IO is ported from it), so the try/except catch you have @chrisvis is awesome.  Which GPIO pins were you using @chrisvis when you got this working?  Since this library uses callbacks, only the XIO and AP-EINT pins can be used on the CHIP.
If needed, I can always add the setmode() into CHIP_IO and have it do nothing.

Also @chrisvis, i see that AP-EINT PINs are the only ones who can give a good response. XIO have much more interference. And also, 3,3v for receiver, works better than 5v.


Доверяй, но проверяй - Trust, but verify.

/cc @aaronlehmann for code review, @LK4D4 for the proverb review.
Signed-off-by: Diogo Monica<EMAIL_ADDRESS>

@diogomonica tests failed!

[Current coverage][cc-pull] is 54.32%

Merging [#931][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

2 files (not in diff) in agent were modified. more

Misses -3
Partials -2
Hits +5

File ca/config.go (not in diff) was modified. more

Misses -1
Partials -1
Hits +2

File .../test/deepcopy.pb.go (not in diff) was modified. more

Misses +1
Partials -1
Hits 0

File ...chestrator/global.go (not in diff) was modified. more

Misses +4
Partials +2
Hits -6

@@             master       #931   diff @@
==========================================
  Files            75         75
  Lines         11290      11300    +10
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6134       6139     +5
- Misses         4294       4298     +4
- Partials        862        863     +1

[][cc-pull]

Powered by Codecov. Last updated by [682c68a...1db0a97][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/682c68a8421ea5f735d4094ca2a29ff806d22c25...1db0a97ea4915c4023b83ffb69cb70d660e75ecc
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/931?src=pr

LGTM

LGTM


Full rank linear model

A simple full rank linear model for multi-class classification
@deerzq @yolken @christhetree

LGTM!


MultipleObjectsReturned: get() returned more than one Beer -- it returned 2!

Beer objects are intended to have a unique combination of name and device, but this constraint isn't enforced when the Beer is created. Add checks to form validation to ensure this is enforced.
MultipleObjectsReturned: get() returned more than one Beer -- it returned 2!
(1 additional frame(s) were not displayed)
...
  File "brewpi-script/brewpi.py", line 234, in startNewBrew
    config = util.configSet(configFile, dbConfig, 'beerName', newName)
  File "scriptlibs/BrewPiUtil.py", line 154, in configSet
    new_beer, created = models.Beer.objects.get_or_create(name=value, device=db_config_object)
  File "django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "django/db/models/query.py", line 464, in get_or_create
    return self.get(**lookup), False
  File "django/db/models/query.py", line 384, in get
    (self.model._meta.object_name, num)

MultipleObjectsReturned: get() returned more than one Beer -- it returned 2!

http://sentry.optictheory.com:9000/sentry/fermentrack-deployed/issues/457/


tests scripts: use /bin/bash, not /bin/sh

e.g. 'time' is not in all /bin/sh

The ci script should be fixed or disabled.

The ci script should be fixed or disabled.

#95


Lumen app() helper resolves to Illuminate\Foundation\Application instead of Laravel\Lumen\Application

Larastan Version: 1.0.4 and 2.4.1
--level used: 2

Description
The use of app()->withEloquent() results in:
Call to method withEloquent() on an unknown class Illuminate\Foundation\Application

Lumen code where the issue was found
app()->withEloquent();

Reproduction Steps
Setup project:
composer create-project --prefer-dist laravel/lumen larastan-test

cd larastan-test

composer require nunomaduro/larastan:^2.0 --dev

phpstan.neon.dist
includes:
    - ./vendor/nunomaduro/larastan/extension.neon

parameters:

    paths:
        - routes/web.php

    level: 2

web.php
<?php

app()->withEloquent();

Analyse code:
./vendor/bin/phpstan analyse

Hello Ollie! 👋🏻
Thank you for your report.

an unknown class Illuminate\Foundation\Application

That is because Larastan does not support Lumen.

It's not strictly marked as supporting it but there is code in order to support the booting of a Lumen application:
if ($app instanceof Application) {
    $app->make(Kernel::class)->bootstrap();
} elseif ($app instanceof LumenApplication) {
    $app->boot();
}

It seems that was not removed.

Hi,
Lumen is not supported.


Encrypt and Decrypt chunk pieces in parallel

Encrypting/Decrypting a whole chunk with a single thread is pretty slow. This PR moves that code to the worker threads to encrypt/decrypt on a per-piece basis.

are there places where we don't want to decrypt in-place?

@lukechampine It looks like quite a few tests in the wallet are failing if I change it to be in-place by default.

Need to add a new function to the encryption package that does encryption in-place. Then only have that function be called in the renter so that compatibility in the other places that we use encryption is not threatened.

I reverted the commits for the parallel encryption for now since it is just too much of a hack to do it in-place right now. Once we get rid of the nonce in the sector after moving to Threefish, we can implement a much easier in-place solution for this.


Column gasPrice is wrong.

The column gasPrice is the same as the column gas_fee_cap, and gasPrice never the same as the gas price in Etherscan

Thanks for the report!
The value is coming from here: https://github.com/flashbots/mempool-dumpster/blob/be96643715108ec0eb80138fbeeac0ebc910f303/common/txsfile.go#L190
Would appreciate if anyone wants to help figuring this out 🙏


Cannot have one Fragment two more Presenter?

This picture is four of the fragment exists in one of the activities?
If i want to reuse business logic(presenter) i should create new fragment?
For example, i need in a fragment two more business logic(presenter).

Presenter is not business logic, presenter is just the connection between business logic (the blue boxes) and the view. Presenter just tells the View what to display, so Presenter kind of coordinates the view.
For example, MailProvider (Business logic) is used by InboxPresenter and MailPresenter to either display a list of mails (InboxView) or to display a single Mail (MailView).
So creating entirely new Presenters is cheap. If you want to reuse a Presenter you can do that too. Presenter programms against a View Interface. So if you want a new View (i.e. Fragment) that displays the same data just in another way simply implement the View interface on your new Fragment and reuse the same presenter.

Thanks for answers!


New version: SAPIEN.PowerShellStudio version <IP_ADDRESS>

This pull request is automatically generated by 🥟 Dumplings in #3144
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335226 2024-01-17 13:22:18.737 [CLI ] ShellExecute installer failed: 1603 LookupUserGroupFromRid() FAILED LookupAccountSidW() FAILED LookupUserGroupFromRidSDDL() FAILED LookupAliasFromRid() FAILED Property(S): ErrorDialog = ErrorDlg MSI (s) (C4:DC) [13:22:12:688]: Product: PowerShell Studio 2024 -- Installation failed. MSI (s) (C4:DC) [13:22:12:688]: Windows Installer installed the product. Product Name: PowerShell Studio 2024. Product Version: <IP_ADDRESS>. Product Language: 1033. Manufacturer: SAPIEN Technologies, Inc.. Installation success or error status: 1603.

(Automated response - build 586.)

@wingetbot waivers Add Validation-Shell-Execute


[Enhancement] javadoc and sources jars not included in maven publications

A requirement of publishing to maven central is to include javadoc and sources jars for java publications.
There are javadoc and sources jar tasks defined with the OpenSearch publish plugin here.
When running publish commands these artifacts should be build and included with each publication.  Instead these tasks if run separately place them under src/*.
To Reproduce
Steps to reproduce the behavior:

Clone the repository
Execute publishToMavenLocal command
Under ~/.m2/repositories/org/opensearch/** See that only .pom, .jar and .module files are included for each.

Expected behavior
These artifacts should be included for any jar publication.
Additional context
These commands could obviously be executed and then the artifacts copied over from each dir manually, but they should be built & included with a single publish command.

A block like this should solve the issue for each publication that needs to end up in central
publishing {
  publications {
    nebula {
      artifactId 'opensearch'
      artifact javadocJar
      artifact sourcesJar
    }
  }
}

but it would be great to centralize this for anything using the publish plugin vs duplicating across config.

See also https://discuss.opendistrocommunity.dev/t/how-to-build-opensearch-including-all-plugins/6274/4

Resolved by #1049


[Feature][RayJob] Support light-weight job submission

Why are these changes needed?
Some users are not willing to allocate additional compute resources for the submitter Kubernetes Job. Hence, this PR implements the light-weight job submission which uses a HTTP request to submit the Ray job.
Related issue number
Closes #1558
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

cc @andrewsykim @astefanutti


Mac software update?

Hi there, I was just wondering whether there'll be an update for Mac users too, now that the MIQ website has changed? Cheers :)

Yes, wondering this too, patiently rechecking thinking its in progress ;)

@jvolker Do you have time to make a new mac release for 0.10.1 please?

The latest version of Windows seems to be missing the month selection too

@marak210 can you post a screenshot of what you mean? Did you try selecting 'no' for find any date?

Thank you so much @alexDrinkwater @jvolker :)

@alexDrinkwater @jvolker Hey guys, I've just downloaded the new Mac version but sadly it doesn't refresh the page. Is there any way to fix his? Cheers :)

Sorry, I didn't get to it earlier. I've just uploaded the new version: https://github.com/jvolker/miq-nz-booking-tools/releases/latest

@jvolker thanks mate, quick query, when I enter a month a can't seem to restart the search, it's greyed out and the page just refreshes july. Any thoughts on why? Many many thanks for all your help to everyone

@hiltmacc You don't need to restart the search. It picks it up as soon as you add it. Don't worry that you don't see the month change. It checks the month in the background without switching.

@alexDrinkwater ah ok thanks Alex, much appreciated! :)

Thank you Alex so much.


Error: cannot find symbol - class RandomGenerator

Can someone explain how to fulfil this step: RandomGenerator.class should be saved in the cs2030/simulator directory?

You can try have a look at @BrendanCheong's comment at #216

You can try have a look at @BrendanCheong's comment at #216

I tried javac -d . *.java in my /Project folder, but the cs2030/simulator folder did not appear.

Did you package your .java files properly?
There should be a package cs2030.simulator; at the top of most of your .java files except your Mains.

Did you package your .java files properly?
There should be a package cs2030.simulator; at the top of most of your .java files except your Mains.

I did.

Interesting. I think some issue mentioned about the workaround but what I did is manually creating the directory 🤣🤣🤣

Your .class files should be created in the cs2030/simulator directory if done properly. That's strange. Do you know where your .class files are being created?

Your .class files should be created in the cs2030/simulator directory if done properly. That's strange. Do you know where your .class files are being created?

I have no idea 🤣

For me after doing javac -d . *.java, a separate cs2030/simulator is created. Then I needed to manually place the RandomGenerator.class inside and give it read/write permission.
But in the end, I used the decompiled .java file someone posted earlier and that worked as well, just need to not include it when submitting.

I had the same issue before, just manually create the folder and manually put the class into the folder.


Allow actual validations to be defined on UsaValidation component.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HBASE-26070: Rewrite 1.7.0 faulty table descriptors at bootstrap

This patch rewrites incorrectly serialized table descriptors and states
from HBASE-26021 into PBs prior to the incompatible change. The patch
does this as a part of the active HMaster bootstrap.
This approach is not fool proof as it does not handle all the edge cases
and may break certain rolling upgrade semantics. However it does provide a way
out for tables created with 1.7.0 PB definitions and an upgrade path for 1.7.1.
Easiest way is to shutdown the 1.7.0 cluster, reboot with 1.7.1 binaries and
everything should work cleanly. However, rolling upgrade could potentially be
broken as 1.7.0 client may not be compatible with 1.7.1 server.
As noted in the jira, it is not possible that any one upgraded to 1.7.0 yet
because they will run into HBASE-26021, however new clusters may have been
created with 1.7.0 and hence they need an upgrade path.
Tested locally:

Created a mix of enabled/disabled tables created with 1.7.0
Upgraded the cluster without this patch, noticed deserialization errors
Upgraded the cluster with patch and table metadata has been re-serialized
in correct format and table states are preserved.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 47s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
2m 31s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m  5s
branch-1 passed

+1 :green_heart:
compile
1m 29s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m 36s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
5m  1s
branch-1 passed

+1 :green_heart:
shadedjars
3m  3s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 15s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 18s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
2m 45s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 32s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s
the patch passed

+1 :green_heart:
compile
1m 26s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
cc
1m 26s
the patch passed

+1 :green_heart:
javac
1m 26s
the patch passed

+1 :green_heart:
compile
1m 38s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
cc
1m 38s
the patch passed

+1 :green_heart:
javac
1m 38s
the patch passed

+1 :green_heart:
checkstyle
2m 37s
The patch passed checkstyle in hbase-protocol

-1 :x:
checkstyle
0m 35s
hbase-client: The patch generated 2 new + 51 unchanged - 0 fixed = 53 total (was 51)

+1 :green_heart:
checkstyle
1m 37s
hbase-server: The patch generated 0 new + 230 unchanged - 1 fixed = 230 total (was 231)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

-1 :x:
shadedjars
0m 34s
patch has 10 errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 31s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 53s
the patch passed

+1 :green_heart:
javadoc
1m  4s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 22s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
6m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol in the patch passed.

-1 :x:
unit
2m 47s
hbase-client in the patch failed.

-1 :x:
unit
136m  6s
hbase-server in the patch failed.

-1 :x:
asflicense
1m 26s
The patch generated 2 ASF License warnings.

209m  0s

Reason
Tests

XML
Parsing Error(s):

hbase-protocol/pom.xml

Failed junit tests
hadoop.hbase.TestInterfaceAudienceAnnotations

hadoop.hbase.replication.TestReplicationSource

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3463

JIRA Issue
HBASE-26070

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile xml cc hbaseprotoc prototool

uname
Linux 8b8621a5da1f 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-3463/out/precommit/personality/provided.sh

git revision
branch-1 / 67b26c2

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/diff-checkstyle-hbase-client.txt

xml
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/xml.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/patch-shadedjars.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/patch-unit-hbase-client.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/testReport/

asflicense
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/artifact/out/patch-asflicense-problems.txt

Max. process+thread count
4375 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
2m 32s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m 11s
branch-1 passed

+1 :green_heart:
compile
1m 28s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m 36s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
4m 55s
branch-1 passed

+1 :green_heart:
shadedjars
3m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 16s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 18s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
2m 44s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 31s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s
the patch passed

+1 :green_heart:
compile
1m 28s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
cc
1m 28s
the patch passed

+1 :green_heart:
javac
1m 28s
the patch passed

+1 :green_heart:
compile
1m 37s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
cc
1m 37s
the patch passed

+1 :green_heart:
javac
1m 37s
the patch passed

+1 :green_heart:
checkstyle
2m 36s
The patch passed checkstyle in hbase-protocol

+1 :green_heart:
checkstyle
0m 36s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 33s
hbase-server: The patch generated 0 new + 230 unchanged - 1 fixed = 230 total (was 231)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
2m 52s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 29s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 52s
the patch passed

+1 :green_heart:
javadoc
1m  3s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 21s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
6m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 28s
hbase-protocol in the patch passed.

-1 :x:
unit
2m 48s
hbase-client in the patch failed.

+1 :green_heart:
unit
134m 54s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
1m 24s
The patch does not generate ASF License warnings.

203m 55s

Reason
Tests

XML
Parsing Error(s):

hbase-protocol/pom.xml

Failed junit tests
hadoop.hbase.TestInterfaceAudienceAnnotations

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3463

JIRA Issue
HBASE-26070

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile xml cc hbaseprotoc prototool

uname
Linux 14455e29e2ad 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-3463/out/precommit/personality/provided.sh

git revision
branch-1 / 67b26c2

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

xml
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/2/artifact/out/xml.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/2/artifact/out/patch-unit-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/2/testReport/

Max. process+thread count
4307 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/2/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
2m 28s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m  7s
branch-1 passed

+1 :green_heart:
compile
1m 30s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m 37s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
4m 58s
branch-1 passed

+1 :green_heart:
shadedjars
3m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 16s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 20s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
2m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 33s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 51s
the patch passed

+1 :green_heart:
compile
1m 29s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
cc
1m 29s
the patch passed

+1 :green_heart:
javac
1m 29s
the patch passed

+1 :green_heart:
compile
1m 36s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
cc
1m 36s
the patch passed

+1 :green_heart:
javac
1m 36s
the patch passed

+1 :green_heart:
checkstyle
2m 39s
The patch passed checkstyle in hbase-protocol

+1 :green_heart:
checkstyle
0m 36s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 34s
hbase-server: The patch generated 0 new + 230 unchanged - 1 fixed = 230 total (was 231)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
2m 51s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 30s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 53s
the patch passed

+1 :green_heart:
javadoc
1m  2s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 20s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
6m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol in the patch passed.

-1 :x:
unit
2m 42s
hbase-client in the patch failed.

-1 :x:
unit
135m 13s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
1m 27s
The patch does not generate ASF License warnings.

204m 15s

Reason
Tests

XML
Parsing Error(s):

hbase-protocol/pom.xml

Failed junit tests
hadoop.hbase.TestInterfaceAudienceAnnotations

hadoop.hbase.replication.TestReplicationSource

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3463

JIRA Issue
HBASE-26070

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile xml cc hbaseprotoc prototool

uname
Linux d44226e3f7d5 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-3463/out/precommit/personality/provided.sh

git revision
branch-1 / 67b26c2

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

xml
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/artifact/out/xml.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/artifact/out/patch-unit-hbase-client.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/testReport/

Max. process+thread count
4382 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/3/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Fixed check style/RAT issues, test failure is unrelated and xml parsing error is a known issue in branch-1.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
2m 28s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m 20s
branch-1 passed

+1 :green_heart:
compile
1m 26s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m 39s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
4m 53s
branch-1 passed

+1 :green_heart:
shadedjars
3m  6s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 19s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
2m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 31s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 51s
the patch passed

+1 :green_heart:
compile
1m 29s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
cc
1m 29s
the patch passed

+1 :green_heart:
javac
1m 29s
the patch passed

+1 :green_heart:
compile
1m 37s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
cc
1m 37s
the patch passed

+1 :green_heart:
javac
1m 37s
the patch passed

+1 :green_heart:
checkstyle
2m 42s
The patch passed checkstyle in hbase-protocol

+1 :green_heart:
checkstyle
0m 36s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 35s
hbase-server: The patch generated 0 new + 230 unchanged - 1 fixed = 230 total (was 231)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
2m 52s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 37s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 55s
the patch passed

+1 :green_heart:
javadoc
1m  3s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 21s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
6m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol in the patch passed.

+1 :green_heart:
unit
2m 44s
hbase-client in the patch passed.

-1 :x:
unit
135m  9s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
1m 24s
The patch does not generate ASF License warnings.

204m 39s

Reason
Tests

XML
Parsing Error(s):

hbase-protocol/pom.xml

Failed junit tests
hadoop.hbase.TestPartialResultsFromClientSide

hadoop.hbase.namequeues.TestSlowLogAccessor

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3463

JIRA Issue
HBASE-26070

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile xml cc hbaseprotoc prototool

uname
Linux a3d0f71d4417 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-3463/out/precommit/personality/provided.sh

git revision
branch-1 / 67b26c2

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

xml
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/4/artifact/out/xml.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/4/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/4/testReport/

Max. process+thread count
4197 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/4/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
2m 30s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m  6s
branch-1 passed

+1 :green_heart:
compile
1m 29s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
1m 40s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
5m  1s
branch-1 passed

+1 :green_heart:
shadedjars
3m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 15s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 18s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
2m 44s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 35s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s
the patch passed

+1 :green_heart:
compile
1m 27s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
cc
1m 27s
the patch passed

+1 :green_heart:
javac
1m 27s
the patch passed

+1 :green_heart:
compile
1m 38s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
cc
1m 38s
the patch passed

+1 :green_heart:
javac
1m 38s
the patch passed

+1 :green_heart:
checkstyle
2m 35s
The patch passed checkstyle in hbase-protocol

+1 :green_heart:
checkstyle
0m 36s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 35s
hbase-server: The patch generated 0 new + 230 unchanged - 1 fixed = 230 total (was 231)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
2m 51s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 27s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 54s
the patch passed

+1 :green_heart:
javadoc
1m  3s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
1m 21s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
6m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol in the patch passed.

+1 :green_heart:
unit
2m 46s
hbase-client in the patch passed.

-1 :x:
unit
135m  5s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
1m 25s
The patch does not generate ASF License warnings.

204m  6s

Reason
Tests

XML
Parsing Error(s):

hbase-protocol/pom.xml

Failed junit tests
hadoop.hbase.replication.TestReplicationSource

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3463

JIRA Issue
HBASE-26070

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile xml cc hbaseprotoc prototool

uname
Linux c15f9eccd499 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-3463/out/precommit/personality/provided.sh

git revision
branch-1 / 67b26c2

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

xml
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/5/artifact/out/xml.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/5/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/5/testReport/

Max. process+thread count
4313 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3463/5/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


python does not start in the electron version

create a new notebook, open the language manager, and click "Python".
the indicator stays yellow.

now that i think about it, does your PR for undoing generated widget JS fix this?

fixed by https://github.com/twosigma/beaker-notebook/pull/4914


how can i train on multi-gpus

can you show me some sample code

what I found was that even if you use one gpu, the training speed is as slow as using cpu, I am not sure if multi-gpu help, because most of the time the program was running on cpu I guess

Hi, since MAML is involed in 2nd order derivative, it's common to see very slow compared with general supervised learning.

May I know how long it takes to train omniglot dataset to 40000 epochs?


Backup and version policies

When I roll out a significant change to an OU, I would like to be able to pull a backup first (stored locally or as a file somewhere), so that I can easily roll back in case of problems. Ideally, I'd also have access to a versioning system with diffs.

If we solve this issue using import/export sub features, we can simply offer git as a versioning mechanism and implement configuration as code for ChromeOS admins :)


Dynamic retention - data gets less granular with time

I have an interesting question. If I keep 6 months worth of metrics, e.g. cpu usage. This fills up disk unnecessary disk space as I dont really want to see what the cpu usage was like 5 months ago at a particular minute. Would it be possible to consolidate or roll up all points in a series past a certain time period, roll them up by averaging daily and store just one value for that day instead of every scrape result.
Essentially data is deleted (for disk space and performance) but an average for a day is kept in.
I want to keep 6 months worth of data but dont really want to see a very granular view of what happened 6 months ago

There is no downsampling implemented right now, and it's not really planned either.
You can emulate the setup by having a long-term Prometheus federating at larger intervals from your short-term Prometheus.
Note that larger scrape intervals lead to worse compression, so the returns of downsampling are somewhat diminished.
Finally, I recommend to discuss questions like this on the prometheus-users mailing list.


NUI-6196 | add delarative radio hints

do we need to introduce a new nui-radio-hint component whose purpose is only to project the content?
I think it would be better to extend the functionality of nui-radio by adding a new hintTemplate input that would do the same.
Similarly as FormFieldComponent has hint and hintTemplate:
https://nova-ui.solarwinds.io/bits/release_v11.x/components/FormFieldComponent.html (Hint Text section)

originally I did it with a selector only, then I wanted to try the click propagation prevention for links, but that could be a general reusable directive instead
not sure if having to supply extra template for each item is a better option, but I guess having some kind of consistency would be useful


No error on NewReceiverForQueue if the queue does not exist

Bug Report

I am using v1.4.0 of github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus
I am using NewReceiverForQueue with a queue name that does not exist
I expect the creation of the receiver to fail due to the queue not being there, however I get no error

Is this something you can reproduce and hopefully fix?

Client initialization in Azure SDKs is lazy by design. You won't see a failure until you actually attempt to do something that causes a connection to be initialized.
To get what you want you'll need to actually attempt to receive or use the queue. If you want to avoid mutating the queue (ie, receiving and locking a message, or deleting it) you could also just call PeekMessages(), which won't change anything but does make the connection initialize.


remove unnecessary input

Removes the deprecated base-branch input now that operator-workflows has been updated to no longer use it

I propose we merge this first: https://github.com/canonical/upload-charm-docs/pull/156


Set test owner to our test organization

https://github.com/pulumi/pulumi-pulumiservice/pull/88 introduced a change that modified the expected organization for a few tests. I forgot to update main.yml as well with that change, so this should fix the build.
Example failing run: https://github.com/pulumi/pulumi-pulumiservice/runs/7907754936?check_suite_focus=true

So it's the release flow that's broken?

Its not the release flow. release.yml contains that worfklow. This change fixes the workflow that runs on our main branch that tests that main is in a good state. We don't have any automation that enforces that main.yml is green before we run release.yml, but we expect a green build before we run any releases.


Adding more low-level statistical info

I would like to monitor more realtime data usage than just controller-level IOPS. I am able to view statistics in the MSA's web-portal about disk-group and pool block allocation, per-disk reads/s and writes/s, cache hits and misses, etc. I'd like to be able to view these same statistics in zabbix.
I have already modified my local copy of zbx-hpmsa.py to add the following controller-level stats.

number-of-reads
number-of-writes
data-read-numeric
data-written-numeric
read-cache-hits
read-cache-misses
write-cache-hits
write-cache-misses

I still need to modify the template
I would like to fork this project, and be able to contribute my changes back to this main branch. What issues would you need me to consider in order for you to approve my pull request?

Hi @zimage.
You needn't create any issues. Just fork my repo, make all changes you need and send me a pool request. I'll surely check it and accept it if all be fine. =)
I've checked your repository and now your copy is the same as my.


Add postgres implementation of the collections package

This PR adds an implementation of the collections and watch package that works with postgres, as well as expanding the tests in the collections package to ensure feature and behavior parity between the two implementations.
There are still a few missing tests that I'm working on, but this should be mostly reviewable.  I'll do a pass today to add comments and a README.md.

I have some concerns about the testutil stuff. The usefulness of that package actually decreases the more constructors you put in it. Once testutil references a package, it is useless to that package because it would create a circular dependency to import testutil.
I vote against moving test constructors in there, and would prefer to revert the db, chunk, and fileset test constructor changes.

Regarding this - moving stuff to the testutil package was actually a follow-up on a comment you made - that you can work around circular dependencies by putting tests into a _test sub-package which is explicitly allowed by the golang spec.  I think this is the way forward, rather than cluttering up libraries with exported test code, we put the test code into testutil and use _test packages.

we put the test code into testutil and use _test packages.

This means we can only do black-box testing.  I don't think you can share private methods or inspect private variables when the tests are in a separate package.


NotFoundHttpException in Controller.php line 269:

Hi! I followed your tutorian on Laravel 5.1. I have a working site build here and then I added the required as mentioned in the tutorial. No errors during installantion, but after I installed it, I tried to go to mysite.com/public/admin and got this error:
What could be going wrong?
Thanks in advance!
Sebas.

You should go to mysite.com/public/panel not mysite.com/public/admin . That would work .
Other thing for your security  , you should not upload all your project file in www , just public folder in www other folder of laravel should be in upper folder

Hi! Thanks a lot for your answer! I actually tried with these:

mysite.com/public/admin
mysite.com/public/panel
mysite.com/admin

Always got the same error message. Sorry I am quite new at Laravel 5, and I can't figure out how the routes in the package could become active in the main project's routes. I mean, in my main project I already have a routes.php and I see another routes.php inside your package. Obviously my instantiation of laravel can't figure out the routes in the package, but not sure why.
Thanks a lot for your time and assistance!
Sebas.

Okay that is different .

Did you install the laravel panel with php artisan panel:install ?
Did you add panel provider to your app.php in cofing folder ?

Hi! Thanks for your time!
In the end, I was able to make it work, it was a combination of two things:

Under apache, I had my vhost config file pointing directly to mysite.com/public/, this I wanted to keep that way.
In my site's routes.php file, I had

Route::controller('/', HomeController);

This generated routes with up to 5 parameters. By issuing php artisan route:list, one of the routes was something like '/index/{param1?}{param2?}{param3}'. I fixed it by using:
Route::get('/', 'HomeController@getIndex');
Route::post('/', 'HomeController@postIndex');

A combination of both had the panel finally working. I don't know if that is relevant for your documentation, but I mention this just in case. Maybe if you had a smarter setup for the main site routes.php file, it would be nice if you could share it.
Thanks again for your time and great work in the panel!!!
Sebas.

We do have this in mind to have composer commend to create full laravel project with panel just with one commend .
Should you have any other concerns, feel free to contact us back.
Thank you .

Awesome sounds great. Looking forward to it! Cheers and kepp up the good work!


unciv: 4.7.8-patch1 -> 4.7.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yairm210/Unciv/releases.
meta.description for unciv is: An open-source Android/Desktop remake of Civ V
meta.homepage for unciv is: https://github.com/yairm210/Unciv
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.7.11 in filename of file in /nix/store/qd9r8g30p7m2rz6j068glavqgs5qx05y-unciv-4.7.11

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
unciv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qd9r8g30p7m2rz6j068glavqgs5qx05y-unciv-4.7.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A unciv https://github.com/r-ryantm/nixpkgs/archive/a50da75c9d6869b8fe68620b94717b7d06ecfcfe.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qd9r8g30p7m2rz6j068glavqgs5qx05y-unciv-4.7.11
ls -la /nix/store/qd9r8g30p7m2rz6j068glavqgs5qx05y-unciv-4.7.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

unciv

Maintainer pings
cc @tex for testing.

Result of nixpkgs-review pr 246520 run on aarch64-darwin 1

1 package built:

unciv


igluctl: add linter for repeated JSON object keys

Duplicated keys are valid in Json4s, Jackson and implicitly in JSON specification, but clearly should be invalidated for our use case.
See https://github.com/snowplow/iglu-central/issues/732

Migrated to https://github.com/snowplow-incubator/igluctl/issues/25


[$200 bounty] Voice entry demo

We want to use voice entry for setting nav destinations and more. The goal of this is to get a small, self-contained demo working of detecting a phrase like "Hey comma, navigate home". The script will run forever: detect start of speech, detect end of speech, do speech to text, then print it out.
Requirements:

wake word detection needs to be local and fast
speech to text can use an API
must be low latency (<1s)
new dependencies must be used only when necessary
doesn't use any GPU; CPU and DSP are available though
has to work reliably in the expected use case

mounted on the windshield and speaking
while openpilot is onroad (everything running)
can't make the rest of openpilot lag

See how we're running other models on the device: https://github.com/commaai/openpilot/tree/master/selfdrive/modeld

Can you explain this part? ""The goal of this is to get a small, self-contained demo working of detecting a phrase like "Hey comma, navigate home"."
Do you want standalone script with demo or do you want the script to be in the repo but work separately for a demo?

https://github.com/meirdev/commaai-assistant

https://github.com/commaai/openpilot/pull/31010


feat: support 10k characters in nft description

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3015

PR #3016   👈

This comment was auto-generated by Graphite.

⏳ This pull request is set to merge as part of a Graphite merge job
Job ID: srBI9sfe6ZNRXrauhrGk.
See details on graphite.dev


make; make run errors

Trying to follow the directions in the readme to run mandelbrot server, but getting an error seemingly due to a non-existing Cargo.lock file.  Looks like make can't reference Cargo.lock in the Makefile at Line 20 where it looks passed as an argument. New to Rust and don't know much about cargo files beyond generally providing soft/hard dependency specs so wasn't sure how to try to hack it from here... looked at the Makefile and tried building the image manually, running it and then executing cargo building x86_64-unknown-linux-musl there, but that gave other compilation errors from inside the container so I gave up and watched robot chicken reruns. Thanks for getting-going pointers.
(gbdxpy36) BabyCakes:jamiepolackwich1$ git clone https://github.com/cderwin/mandelbrot.git
Cloning into 'mandelbrot'...
remote: Enumerating objects: 126, done.
remote: Total 126 (delta 0), reused 0 (delta 0), pack-reused 126
Receiving objects: 100% (126/126), 35.61 KiB | 0 bytes/s, done.
Resolving deltas: 100% (55/55), done.
(gbdxpy36) BabyCakes:jamiepolackwich1$ cd mandelbrot/
(gbdxpy36) BabyCakes:mandelbrot jamiepolackwich1$ make run
make: *** No rule to make target `Cargo.lock', needed by `target/x86_64-unknown-linux-musl/release/mandelbrot'.  Stop.

Running on macOS 10.12.1 with make version 3.81

This is happening because Cargo.lock should be version controlled but isn't (so it isn't present when the repository is cloned, but is expected to be present by the Makefile); I just added it to master.  I think there may be other build errors since the rust compiler I wrote this with is now out of date by a bit -- I'll try to see if I can get it all working again tomorrow.

Alright, I found a typo in the makefile which was probably causing problems.  I was able to get make && make run to work in a fresh git clone now, but  you might have to do a make clean first, after pulling the new commits.
Let me know if you run into any issues!


align css and js imports in site_base, search_result, and manage_projects

this fixes inability to load manage_projects page from search_results page

Thanks!


SWIG: Remove -classic Python option

It has been removed in swig 4.0, only needed to support python <2.2:
https://github.com/swig/swig/commit/728b8955bd50d79168e121f834295ef30fcdc89e

ping


[stable/prometheus-operator] Custom Grafana dashboard configmaps deployed to many namespaces causes premature delete

Describe the bug
We are installing chartA (with a configmap containing a label that the grafana dashboard scraper picks up) to 2 different namespaces (namespaceA and namespaceB).  ChartA is installed to namespaceA and the dashboard is picked up correctly by the Grafana Dashboard scraper. When chartA is installed to namespaceB, the scraper detects that the dashboard contained in the configmap is already discovered by Grafana and is not added a second time... ALL is good until this point. When namespaceB is wiped of all of its resources the scraper detects that the configmap is deleted, and deletes the Grafana Dashboard contained in chartA deployed to both namespaceA and namespaceB.
The Scraper doesn't keep track that multiple deployments of chartA are using that custom dashboard. Hence when we go to look for the dashboard containing metrics about chartA, the dashboard is missing despite being contained in a configmap in namespaceA.
This issue has been discovered since we are installing chartA to a namespace that persists and another namespace that is just present while tests are being run against it.
Version of Helm and Kubernetes:
Helm:
Client: v2.12.2
Server: v2.14.1
Kubernetes:
Client: v1.13.0
Server: v1.13.5
Which chart:
stable/prometheus-operator
What happened:
Custom Grafana dashboard contained in configmap is missing, despite being installed to namespace
What you expected to happen:
The Grafana dashboard scraper sidecar would detect and keep track of which releases use the custom dashboard, and only remove the dashboard when all releases using that dashboard are deleted
How to reproduce it (as minimally and precisely as possible):

Install chart containing configmap describing custom Grafana dashboard, with label detectable by Grafana Dashboard sidecar twice (two seperate releases)

Delete one of the releases

Files are created using the name of the file in the configmap.
data:
  my Dashboard.json: {}

https://github.com/kiwigrid/k8s-sidecar/blob/master/sidecar/resources.py#L100-L106
You can template your filenames to include the namespace, which should help address your issue. I'm not certain of the complete implications of this, since the prometheus-operator chart is just leveraging grafana and I don't maintain that chart

Thanks for your response @vsliouniaev. I have some concerns with that approach. In some cases (such as when you include a legend format such as: "legendFormat": {{pod}} ) the dashboard.json and configmap must be separate files (if in a single file when kubernetes parses the configmap it interprets "{{ }}" as a function and throws an error), and the filename of the dashboard.json is static. Also its not ideal to have replicas of a dashboard, when used in multiple namespaces.

I think your issue is fundamental to how the reloader sidecar behaves. I suggest you raise this issue with the maintainers there to see if they would be open to the enhancement you are looking for.


Add tag protection requirement

Why
Per internal agreement.
Practice "defense in depth".
What
Add a requirement to use https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules to increase the protection of our release train.

Seems like a reasonable idea to me. We might have to give a few Splunkers additional privs in some repos, however.

Maintainers are able to create a protected tag. Only admins are able to delete it. I think it is reasonable.

@pellared please be sure to update splunk-otel-go

Maintainers should be able to delete protected tags. Usually when you need tag deletion :hankey: has hit the fan and you don't want the extra overhead of catching an admin. Letting only admins delete tags does not provide more security, as the only critical part - releasing - happens when tags are created.

Maintainers should be able to delete protected tags. Usually when you need tag deletion 💩 has hit the fan and you don't want the extra overhead of catching an admin. Letting only admins delete tags does not provide more security, as the only critical part - releasing - happens when tags are created.

I disagree. The main benefit of such policy is that it reduces the changes to delete the tag after the release is published.
If everything is fine then you should never delete a tag 😉

@seemk I would rather consider to grant Admin for maintainers  (on repositories) 😉 This will make e.g. setting up branch protection rules easier. Also Admin is requires to set up many things required by the GDI spec.


Include css ootb or make it easier to override

This is related to the issue https://github.com/TriOptima/tri.table/issues/28
The generic problem is that no css file is provided out of the box for forms. Some generic styling should be provided.
Better still, a popular or several popular css frameworks could be supported using some kind of "render style" setting. This would swap out relevant templates.

This is fixed in iommi