How do you change memory block size?

I want to change it from 1.8GB to 4GB to 8GB to 16GB ...etc to see if it corrupts memory

What GPU and OS do you have?
Note that memtest_vulkan tests video memory which is different from system memory for all GPUs except integrated. It already tries to allocate as much GPU memory as possible, but due to several reaasons it allocates consecutive memory, not several isolated regions.

Also, the behavior of the maximum available memory may be driver dependent. For example, for the AMD rx580 8GB GPU on Linux it is possible to install two vulkan loadable drivers simultaneously on one system - one RADV from Mesa project, and the other AMDVLK driver. Then the driver can be explicitly selected by specifying VK_DRIVER_FILES environment variable
with Khronos vulkan loader libvulkan.so version below v1.3.207 (use VK_ICD_FILENAMES instead of VK_DRIVER_FILES. And the
[user@host ~]$ VK_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json ./memtest_vulkan
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C

1: Bus=0x01:00 DevId=0x67DF   8GB AMD Radeon RX 580 Series (RADV POLARIS10)
Standard 5-minute test of 1: Bus=0x01:00 DevId=0x67DF   8GB AMD Radeon RX 580 Series (RADV POLARIS10)
      1 iteration. Passed  0.0324 seconds  written:    1.8GB 179.3GB/sec        checked:    3.5GB 154.5GB/sec
     32 iteration. Passed  1.0063 seconds  written:   54.2GB 178.5GB/sec        checked:  108.5GB 154.4GB/sec
^C
memtest_vulkan: no any errors, testing PASSed.
  press any key to continue...
[user@host ~]$ VK_DRIVER_FILES=/usr/share/vulkan/icd.d/amd_icd64.json ./memtest_vulkan
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C

1: Bus=0x01:00 DevId=0x67DF   8GB AMD Radeon RX 580 Series
Standard 5-minute test of 1: Bus=0x01:00 DevId=0x67DF   8GB AMD Radeon RX 580 Series
      1 iteration. Passed  0.0637 seconds  written:    3.5GB 181.7GB/sec        checked:    7.0GB 157.6GB/sec
     17 iteration. Passed  1.0189 seconds  written:   56.0GB 181.6GB/sec        checked:  112.0GB 157.6GB/sec
^C
memtest_vulkan: no any errors, testing PASSed.
  press any key to continue...

So with mesa RADV driver only 3.5GB is allocated and for AMDVLK driver 7.0GB is allocated. It seems that RADV has a 32-bit address space limit. This example shows that the behavior is very driver-dependent.
(0.5-1.0 GB memory is automatically ignored by memtest_vulkan to avoid system freeze, since allocating all video memory can freeze the system).

I have Intel Arc A770 on Linux 6.3 with Mesa 22.
It only allocates blocks of 1.8 GB. I want to allocate more than 4 GB to see if they corrupt.
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C

1: Bus=0x03:00 DevId=0x56A0   16GB Intel(R) Arc(tm) A770 Graphics (DG2)
2: Bus=0x00:00 DevId=0x0000   2GB llvmpipe (LLVM 13.0.1, 256 bits)
(first device will be autoselected in 0 seconds)   Override index to test:
    ...first device autoselected
Standard 5-minute test of 1: Bus=0x03:00 DevId=0x56A0   16GB Intel(R) Arc(tm) A770 Graphics (DG2)
      1 iteration. Passed  0.0082 seconds  written:    0.9GB 381.1GB/sec        checked:    1.8GB 295.5GB/sec
    130 iteration. Passed  1.0073 seconds  written:  112.9GB 402.5GB/sec        checked:  225.8GB 310.6GB/sec
    743 iteration. Passed  5.0001 seconds  written:  536.4GB 381.4GB/sec        checked: 1072.8GB 298.5GB/sec
   4467 iteration. Passed 30.0023 seconds  written: 3258.5GB 387.1GB/sec        checked: 6517.0GB 301.9GB/sec
   8250 iteration. Passed 30.0055 seconds  written: 3310.1GB 394.2GB/sec        checked: 6620.2GB 306.4GB/sec
  12004 iteration. Passed 30.0045 seconds  written: 3284.8GB 390.7GB/sec        checked: 6569.5GB 304.2GB/sec
  15792 iteration. Passed 30.0063 seconds  written: 3314.5GB 395.3GB/sec        checked: 6629.0GB 306.6GB/sec
  19567 iteration. Passed 30.0048 seconds  written: 3303.1GB 393.8GB/sec        checked: 6606.2GB 305.6GB/sec
  23310 iteration. Passed 30.0040 seconds  written: 3275.1GB 389.9GB/sec        checked: 6550.2GB 303.2GB/sec
  27100 iteration. Passed 30.0074 seconds  written: 3316.2GB 396.1GB/sec        checked: 6632.5GB 306.6GB/sec
  30895 iteration. Passed 30.0069 seconds  written: 3320.6GB 396.4GB/sec        checked: 6641.2GB 307.0GB/sec
  34673 iteration. Passed 30.0073 seconds  written: 3305.8GB 393.9GB/sec        checked: 6611.5GB 305.9GB/sec

The memory size to test can be directly specified in command line - the first argumet is GPU index to test, the next is VRAM size to test in bytes.
However as far as I mentioned I suppose that it is a limitation of intel vulkan driver - it can't allocate contigous block greater than 2GB (example from integrated GPU):
user@host ~/m %  ./memtest_vulkan 1<PHONE_NUMBER>
Standard 5-minute test of 1: Bus=0x00:02 DevId=0x9A49   12GB Intel(R) Xe Graphics (TGL GT2)
      1 iteration. Passed  0.0943 seconds  written:    0.9GB  22.8GB/sec        checked:    1.8GB  31.3GB/sec
     12 iteration. Passed  1.0762 seconds  written:    9.6GB  21.4GB/sec        checked:   19.2GB  30.7GB/sec
^C%
user@host ~/m % ./memtest_vulkan 1<PHONE_NUMBER>
VK_ERROR_OUT_OF_DEVICE_MEMORY
user@host ~/m %

The limitation seems to be a limitation for contigous memory region, since two instances of memtest_vulkan testing 1.8GB each can be started just fine. Unfortunately the use of a single contigous buffer is a part of current design of memtest_vulkan, so it can't be easily changed.

A more detailed out-of-memory error output can be got if the binary is named as memtest_vulkan_verbose:
```
user@host ~/m % cp ./memtest_vulkan ./memtest_vulkan_verbose
user@host ~/m % ./memtest_vulkan_verbose 1<PHONE_NUMBER>
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.239
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
Available:
VK_LAYER_MESA_device_select, VK_LAYER_KHRONOS_validation, VK_LAYER_MESA_overlay, VK_LAYER_INTEL_nullhw
Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace, VK_KHR_portability_enumeration
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
Loading memory info for selected device index 0...
Inserted device layer "VK_LAYER_KHRONOS_validation" (libVkLayer_khronos_validation.so)
Failed to find vkGetDeviceProcAddr in layer "libVkLayer_MESA_device_select.so"
Using "Intel(R) Xe Graphics (TGL GT2)" with driver: "/usr/lib/x86_64-linux-gnu/libvulkan_intel.so"
Validation Information: [ UNASSIGNED-cache-file-error ] Object 0: handle = 0x563a42a8d090, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xf0bb3995 | Cannot open shader validation cache at /home/user/.cache/shader_validation_cache-1000.bin for reading (it may not exist yet)
0 MemoryType { property_flags: DEVICE_LOCAL | HOST_VISIBLE | HOST_COHERENT | HOST_CACHED, heap_index: 0 }
CoherentIO memory          type 0 inside heap MemoryHeap { size:<PHONE_NUMBER>4, flags: DEVICE_LOCAL }
Trying   2.002GB buffer...
VK_ERROR_OUT_OF_DEVICE_MEMORY
Retrying with lower memory due to ERROR_OUT_OF_DEVICE_MEMORY while getting erupt::generated::vk1_0::DeviceMemory in context allocate_memory
</details>

I suppose that for descrete Intel GPU the message is the same -
```Trying   2.002GB buffer...
VK_ERROR_OUT_OF_DEVICE_MEMORY
Retrying with lower memory due to ERROR_OUT_OF_DEVICE_MEMORY while getting erupt::generated::vk1_0::DeviceMemory in context allocate_memory

However, if you have different error - please post it here

This is advertised in maxMemoryAllocationSize output of vulkaninfo:
 % vulkaninfo | grep -C 4 VkPhysicalDeviceVulkan12Properties
	protectedNoFault                  = false
	maxPerSetDescriptors              = 1024
	maxMemoryAllocationSize           = 0x80000000

VkPhysicalDeviceVulkan12Properties:
-----------------------------------
	driverID                                             = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
	driverName                                           = Intel open-source Mesa driver
	driverInfo                                           = Mesa 23.0.2
--
	protectedNoFault                  = false
	maxPerSetDescriptors              = 1024
	maxMemoryAllocationSize           = 0x80000000

VkPhysicalDeviceVulkan12Properties:
-----------------------------------
	driverID                                             = DRIVER_ID_MESA_LLVMPIPE
	driverName                                           = llvmpipe
	driverInfo                                           = Mesa 23.0.2 (LLVM 15.0.7)

UPDATE
Mesa 23.1.0~rc1 removes this limitation! https://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa-23.1.0-rc1&id=71fe9dfe07b53115a9e8f8b031a04f6f387937d6

Example run (in verbose mode)
```
 % ./memtest_vulkan_verbose
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.239
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
Available:
VK_LAYER_MESA_device_select, VK_LAYER_KHRONOS_validation, VK_LAYER_MESA_overlay, VK_LAYER_INTEL_nullhw
Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace, VK_EXT_surface_maintenance1, VK_KHR_portability_enumeration
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
1: Bus=0x00:02 DevId=0x9A49 API 1.3.246  v23(0x5C01000)  12GB Intel(R) Xe Graphics (TGL GT2)
2: Bus=0x00:00 DevId=0x0000 API 1.3.246  ver1  2GB llvmpipe (LLVM 15.0.7, 256 bits)
(first device will be autoselected in 8 seconds)   Override index to test:
...testing default device confirmed
Loading memory info for selected device index 0...
heap size 11.5GB budget 11.2GB usage  0.0GB flags=DEVICE_LOCAL
Spawned child Child { stdin: None, stdout: None, stderr: None, .. } with PID 76521
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.239
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
WARNING:          vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "libVkLayer_MESA_device_select.so"
Available:
VK_LAYER_MESA_device_select, VK_LAYER_KHRONOS_validation, VK_LAYER_MESA_overlay, VK_LAYER_INTEL_nullhw
Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace, VK_EXT_surface_maintenance1, VK_KHR_portability_enumeration
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
linux_read_sorted_physical_devices:
Original order:
[0] llvmpipe (LLVM 15.0.7, 256 bits)
[1] Intel(R) Xe Graphics (TGL GT2)
Sorted order:
[0] Intel(R) Xe Graphics (TGL GT2)
[1] llvmpipe (LLVM 15.0.7, 256 bits)
Loading memory info for selected device index 0...
Inserted device layer "VK_LAYER_KHRONOS_validation" (libVkLayer_khronos_validation.so)
Failed to find vkGetDeviceProcAddr in layer "libVkLayer_MESA_device_select.so"
Using "Intel(R) Xe Graphics (TGL GT2)" with driver: "/usr/lib/x86_64-linux-gnu/libvulkan_intel.so"
Validation Information: [ UNASSIGNED-cache-file-error ] Object 0: handle = 0x564adee5b970, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xf0bb3995 | Cannot open shader validation cache at /home/vasiliy.galkin/.cache/shader_validation_cache-1000.bin for reading (it may not exist yet)
0 MemoryType { property_flags: DEVICE_LOCAL, heap_index: 0 }
1 MemoryType { property_flags: DEVICE_LOCAL | HOST_VISIBLE | HOST_COHERENT, heap_index: 0 }
2 MemoryType { property_flags: DEVICE_LOCAL | HOST_VISIBLE | HOST_COHERENT | HOST_CACHED, heap_index: 0 }
CoherentIO memory          type 1 inside heap MemoryHeap { size:<PHONE_NUMBER>4, flags: DEVICE_LOCAL }
Trying  10.813GB buffer...
Test memory size  10.8GB   type  0: MemoryType { property_flags: DEVICE_LOCAL, heap_index: 0 } MemoryHeap { size:<PHONE_NUMBER>4, flags: DEVICE_LOCAL }
Standard 5-minute test of 1: Bus=0x00:02 DevId=0x9A49 API 1.3.246  v23(0x5C01000)  12GB Intel(R) Xe Graphics (TGL GT2)
1 iteration. Passed  0.6808 seconds  written:    7.0GB  20.0GB/sec        checked:   10.5GB  31.7GB/sec
3 iteration. Passed  1.3355 seconds  written:   14.0GB  21.0GB/sec        checked:   21.0GB  31.4GB/sec
11 iteration. Passed  5.3045 seconds  written:   56.0GB  21.2GB/sec        checked:   84.0GB  31.5GB/sec
^CSubprocess status exit status: 65 parent_close_requested true
memtest_vulkan: no any errors, testing PASSed.
press any key to continue...
</details>

Upgrading from Mesa 23.0 to Mesa 23.1 using the PPA broke vulkan on my system. I will wait for mesa 23.1 the official ubuntu repos
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
Loading memory info for selected device index 0...
ERROR | DRIVER: terminator_CreateDevice: Failed in ICD /usr/lib/x86_64-linux-gnu/libvulkan_intel.so vkCreateDevice call
ERROR: vkCreateDevice:  Failed to create device chain.
Runtime error: a Vulkan function returned a negative `Result` value
Subprocess status exit status: 68 parent_close_requested false
retrying subprocess with smaller memory limit 665845760
Spawned child Child { stdin: None, stdout: None, stderr: None, .. } with PID 5461
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.204
Available:
VK_LAYER_MESA_device_select, VK_LAYER_MESA_overlay, VK_LAYER_INTEL_nullhw
Extensions: VK_KHR_device_group_creation, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_debug_report, VK_EXT_debug_utils, VK_KHR_display, VK_KHR_get_display_properties2, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace

ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
Loading memory info for selected device index 0...
ERROR | DRIVER: terminator_CreateDevice: Failed in ICD /usr/lib/x86_64-linux-gnu/libvulkan_intel.so vkCreateDevice call
ERROR: vkCreateDevice:  Failed to create device chain.
Runtime error: a Vulkan function returned a negative `Result` value
Subprocess status exit status: 68 parent_close_requested false
Using in-process testing method with small memory limit 665845760
Using in-process testing method
ERROR | DRIVER: terminator_CreateDevice: Failed in ICD /usr/lib/x86_64-linux-gnu/libvulkan_intel.so vkCreateDevice call
ERROR: vkCreateDevice:  Failed to create device chain.
Runtime error: a Vulkan function returned a negative `Result` value

memtest_vulkan: INIT OR FIRST testing failed due to runtime error
  press any key to continue...

@galkinvv
Using Mesa 23.2.0. I can allocate more than 4GB but they are all corrupt.
./memtest_vulkan 1<PHONE_NUMBER>
Error found. Mode NEXT_RE_READ, total errors 0x20000000 out of 0x2C000000 (72.72727273%)
Errors address range: 0x30000000..=0xAFFFFFFF  iteration:1
values range: 0x00000000..=0x00000000   FFFFFFFF-like count:0    bit-level stats table:
         0x0 0x1  0x2 0x3| 0x4 0x5  0x6 0x7| 0x8 0x9  0xA 0xB| 0xC 0xD  0xE 0xF
SinglIdx                 |   1             |                 |       1
TogglCnt       2   56 761|6673 42k 205k793k|  2m  6m  14m 27m| 45m 63m  76m 81m
   0x1?  74m 58m  40m 24m| 12m  5m   1m589k|145k 28k 4277 457|  31   1
1sInValu536m             |                 |                 |

Error found. Mode INITIAL_READ, total errors 0x20000000 out of 0x2C000000 (72.72727273%)
Errors address range: 0xE0000000..=0x15FFFFFFF  iteration:1
values range: 0x00000000..=0x00000000   FFFFFFFF-like count:0    bit-level stats table:
         0x0 0x1  0x2 0x3| 0x4 0x5  0x6 0x7| 0x8 0x9  0xA 0xB| 0xC 0xD  0xE 0xF
SinglIdx                 |   1             |                 |       1
TogglCnt       2   56 761|6673 42k 205k793k|  2m  6m  14m 27m| 45m 63m  76m 81m
   0x1?  74m 58m  40m 24m| 12m  5m   1m589k|145k 28k 4277 457|  31   1
1sInValu536m             |                 |                 |

Error found. Mode INITIAL_READ, total errors 0x20000000 out of 0x2C000000 (72.72727273%)
Errors address range: 0x190000000..=0x20FFFFFFF  iteration:1
values range: 0x00000000..=0x00000000   FFFFFFFF-like count:0    bit-level stats table:
         0x0 0x1  0x2 0x3| 0x4 0x5  0x6 0x7| 0x8 0x9  0xA 0xB| 0xC 0xD  0xE 0xF
SinglIdx                 |   1             |                 |       1
TogglCnt       2   56 761|6672 42k 205k793k|  2m  6m  14m 27m| 45m 63m  76m 81m
   0x1?  74m 58m  40m 24m| 12m  5m   1m589k|145k 28k 4277 457|  31   1
1sInValu536m             |                 |                 |

Standard 5-minute test of 1: Bus=0x03:00 DevId=0x56A0   16GB Intel(R) Arc(tm) A770 Graphics (DG2)
      1 iteration. Passed  5.6310 seconds  written:    5.5GB 956.2GB/sec        checked:    8.2GB   1.5GB/sec
Error found. Mode NEXT_RE_READ, total errors 0x20000000 out of 0x2C000000 (72.72727273%)
Errors address range: 0x30000000..=0xAFFFFFFF  iteration:1
values range: 0x00000000..=0x00000000   FFFFFFFF-like count:0    bit-level stats table:
         0x0 0x1  0x2 0x3| 0x4 0x5  0x6 0x7| 0x8 0x9  0xA 0xB| 0xC 0xD  0xE 0xF
SinglIdx                 |   1             |                 |       1
TogglCnt       2   56 761|6673 42k 205k793k|  2m  6m  14m 27m| 45m 63m  76m 81m
   0x1?  74m 58m  40m 24m| 12m  5m   1m589k|145k 28k 4277 457|  31   1
1sInValu536m             |                 |                 |

Error found. Mode INITIAL_READ, total errors 0x20000000 out of 0x2C000000 (72.72727273%)
Errors address range: 0xE0000000..=0x15FFFFFFF  iteration:2
values range: 0x00000000..=0x00000000   FFFFFFFF-like count:0    bit-level stats table:
         0x0 0x1  0x2 0x3| 0x4 0x5  0x6 0x7| 0x8 0x9  0xA 0xB| 0xC 0xD  0xE 0xF
SinglIdx                 |   1             |                 |       1
TogglCnt       2   56 760|6653 42k 204k789k|  2m  6m  14m 27m| 45m 63m  76m 81m
   0x1?  74m 58m  40m 24m| 12m  5m   1m589k|145k 28k 4277 457|  31   1
1sInValu536m             |                 |                 |

In short: Thanks! Please install vulkaninfo tool and post the output of vulkaninfo | grep -B 20 -i StorageBufferRange
Detailed: Thanks for the update. It seems that the problem is caused by the fact that memtest_vulkan is ignoring maxStorageBufferRange limit reported by vulkan driver (hardcoded limit of TEST_WINDOW_MAX_SIZE=4GB is currently used instead).
This limit is used internally by memtest_vulkan for selecting the memory region size tested by a single dispatched command.
A latptop with integrated Intel graphics has a maxStorageBufferRange=4GB, which corresponds to the internally hardcoded value, so it is working fine, but if the descrete intel GPU has this limit smaller - it may cause such behaviour.
I'm working on a fix, however to recheck the problem reason it would be useful to see the output of the command mentioned in first line.
Example output from integrated Intel GPU:

 % vulkaninfo | grep -B 20 -i StorageBufferRange
GPU0:
VkPhysicalDeviceProperties:
---------------------------
        apiVersion        = 1.3.251 (4206843)
        driverVersion     = 23.1.99 (96473187)
        vendorID          = 0x8086
        deviceID          = 0x9a49
        deviceType        = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
        deviceName        = Intel(R) Xe Graphics (TGL GT2)
        pipelineCacheUUID = 303aa8b0-afa9-b0a7-3336-7a249170c686

VkPhysicalDeviceLimits:
-----------------------
        maxImageDimension1D                             = 16384
        maxImageDimension2D                             = 16384
        maxImageDimension3D                             = 2048
        maxImageDimensionCube                           = 16384
        maxImageArrayLayers                             = 2048
        maxTexelBufferElements                          = 134217728
        maxUniformBufferRange                           =<PHONE_NUMBER>
        maxStorageBufferRange                           =<PHONE_NUMBER>
--
GPU1:
VkPhysicalDeviceProperties:
---------------------------
        apiVersion        = 1.3.251 (4206843)
        driverVersion     = 0.0.1 (1)
        vendorID          = 0x10005
        deviceID          = 0x0000
        deviceType        = PHYSICAL_DEVICE_TYPE_CPU
        deviceName        = llvmpipe (LLVM 15.0.7, 256 bits)
        pipelineCacheUUID = 76616c2d-742d-3038-3566-366563203200

VkPhysicalDeviceLimits:
-----------------------
        maxImageDimension1D                             = 16384
        maxImageDimension2D                             = 16384
        maxImageDimension3D                             = 4096
        maxImageDimensionCube                           = 32768
        maxImageArrayLayers                             = 2048
        maxTexelBufferElements                          = 134217728
        maxUniformBufferRange                           = 65536
        maxStorageBufferRange                           = 134217728

@galkinvv
vulkaninfo | grep -B 20 -i StorageBufferRange
GPU0:
VkPhysicalDeviceProperties:
---------------------------
	apiVersion        = 4206838 (1.3.246)
	driverVersion     = 96473187 (0x5c01063)
	vendorID          = 0x8086
	deviceID          = 0x56a0
	deviceType        = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName        = Intel(R) Arc(tm) A770 Graphics (DG2)
	pipelineCacheUUID = fcc500d8-8a65-8853-deef-d91eec1217d5

VkPhysicalDeviceLimits:
-----------------------
	maxImageDimension1D                             = 16384
	maxImageDimension2D                             = 16384
	maxImageDimension3D                             = 2048
	maxImageDimensionCube                           = 16384
	maxImageArrayLayers                             = 2048
	maxTexelBufferElements                          = 134217728
	maxUniformBufferRange                           =<PHONE_NUMBER>
	maxStorageBufferRange                           =<PHONE_NUMBER>


Fuzzy IntelliSense matching vs Haxe metadata completion

We noticed a regression in the Haxe extension's metadata completion (https://github.com/vshaxe/vshaxe/issues/121). The issue first appeared in the March release (1.11.0), more specifically https://github.com/Microsoft/vscode/commit/264908a434e98f9b22f8de358b3636200c332ea4 (isolated using git bisect). It can be reproduced with this code:
'use strict';
import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
    vscode.languages.registerCompletionItemProvider('foo', {
        provideCompletionItems(doc, pos) {
            return [new vscode.CompletionItem(':foo'), new vscode.CompletionItem(':Foo')];
        }
    }, "@", ":");
}

Somehow :foo is missing here, while :Foo still matches.

Compare this with the behavior in the February release:

Note: I realize that this is fixed by removing the : trigger character, but this is necessary in the Haxe extension to provide completion for type hints. Related issue: #12772

@rebornix not sure who owns this, you probably have a better idea 😄

Interesting... Because the word definition doesn't contain : and because the suggestions don't define a range to replace both are compared just against f, so score f against :foo and :Foo. None should match because we want matches to start at the first character... So some reason tho the latter does match...

Thanks, that seems to fix our use case. :)
On a related note, is there a way to avoid the flicker / close and reopen of the completion list that happens because : is a trigger character?

I guess it would be less noticable if the language server responded faster, but the flicker is still visible even with the minimal example. I tried playing around with setLanguageConfiguration() / wordPattern, but that didn't help.

Yeah, the flicker happens because for a short moment there are no suggestions. None matches the @: prefix and : has triggered a new completions. Not so much we can do, except for adding some more animations. Which we already do a little, right @joaomoreno ?

None matches the @: prefix

Is the prefix even being considered? Adding some logs to completionModel.ts, word always seems to be the string after the trigger character.

Is the prefix even being considered? Adding some logs to completionModel.ts, word always seems to be the string after the trigger character.

It depends: If your completion item don't set a range to overwrite we use the range of the word at that position. That again depends on the word-definition of your language but likely doesn't contain : or @. Then we use the range to select the current text to filter/rank it against the future text

Oh, I hadn't realized that completion items have a range (because it's not present in the language server protocol: https://github.com/Microsoft/language-server-protocol/issues/165).
Anyway, that seems like a much cleaner solution in theory, but even when correctly setting the range + language configuration, the list is still closed + reopened on the trigger character:
'use strict';
import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
    vscode.languages.registerCompletionItemProvider('foo', {
        provideCompletionItems(doc, pos) {
            sleepFor(200); // make the close / reopen delay noticable
            let item = new vscode.CompletionItem('@:foo');
            item.range = new vscode.Range(new vscode.Position(0, 0), pos);
            return [item];
        }
    }, "@", ":");

    vscode.languages.setLanguageConfiguration('foo', {wordPattern: /@:?\w*/});
}

function sleepFor(sleepDuration) {
    var now = new Date().getTime();
    while (new Date().getTime() < now + sleepDuration) {}
}

Should I open a separate issue for this, or is this the expected behavior?

Yeah, that is because you hit two trigger characters in a row. We first call your provider after @ and then after :. I can look into making the widget show loading for that time but the thing is that we remove all current results because their provider wants to recompute, then no items are left and the widget hides...

I have pushed another change to keep the widget stable when retriggering suggestions, e.g hitting another trigger character when suggest is already active

Thanks, that fixes it for the Haxe extension as well. 👍

vs before:


operator callback and workspaces cleanup and fixes

What changes are proposed in this pull request?

Load workspace on save
Add loading state to delete and save
code cleanup
Style tweaks

How is this patch tested? If it is not, please explain why.
Using the workspaces in the app
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Summary by CodeRabbit

New Features

Enhanced operator execution by introducing a new callback functionality for improved interactivity and responsiveness.
Added new constants for workspace operations (load, save, delete, list) in the Workspaces component.
Renamed components from SavedSpaces to Workspaces and SavedSpace to Workspace for clarity and consistency.
Introduced a new MuiButton component with a loading indicator for enhanced user experience.

Bug Fixes

Ensured functionality consistency by updating function calls and hooks to align with new component and operator names.

Refactor

Utilized the newly introduced MuiButton component in modified components and functions.
Replaced deprecated hooks and methods with updated ones in the workspace management components.

Documentation

Updated component names and descriptions to reflect the renaming and new features in workspace management tools.

@imanjra I'll defer to others for code review but I just tested this PR and everything looks and works great!
With respect to the positioning of the . Unsaved [icon] component, I definitely prefer the new layout compared to the old one. Maybe decrease the right padding just a bit more so the right edge of the workspace icon aligns with the right edge of the grid reset icon?


Use namespace to expose inner interfaces in a structured manner

Fix #162

@UNIDY2002 Nice!
I added tsd in #164, do you mind merging main into this branch and adding a couple of exceptTypes to test-d/index.test-d.ts for how one might use these types.

@silas I'd like to. I'll add some cases after the weekend.

Wow! Thanks for the fast turnaround on this @UNIDY2002 ❤

@silas This PR is ready for review


All devices disabled, cannot mine!

打印信息如下
[1970-01-02 16:19:09.655] Started cgminer 4.11.1
[1970-01-02 16:19:09.656] Probing for an alive pool
[1970-01-02 16:19:09.656] Testing pool stratum+tcp://<IP_ADDRESS>:3333
[1970-01-02 16:19:09.656] Succeeded delayed connect
[1970-01-02 16:19:09.656] RECVD: {"id":0,"result":[[["mining.set_difficulty","01000005"],["mining.notify","01000005"]],"01000005",8],"error":null}
[1970-01-02 16:19:09.656] Pool 0 stratum session id: 01000005
[1970-01-02 16:19:09.657] Pool 0 confirmed mining.subscribe with extranonce1 01000005 extran2size 8
[1970-01-02 16:19:09.657] SEND: {"id": 1, "method": "mining.authorize", "params": ["jack", "x"]}
[1970-01-02 16:19:09.657] RECVD: {"id":1,"result":true,"error":null}
[1970-01-02 16:19:09.657] Stratum authorisation success for pool 0
[1970-01-02 16:19:09.657] Pool 0 stratum+tcp://<IP_ADDRESS>:3333 alive
[1970-01-02 16:19:10.656] All devices disabled, cannot mine!
root@joen-virtual-machine:/work/cgminer# ./cgminer -o stratum+tcp://<IP_ADDRESS>:3333 -u jack -p 1 --debug --protocol-dump
[1970-01-02 16:19:34.051] Started cgminer 4.11.1
[1970-01-02 16:19:34.052] Probing for an alive pool
[1970-01-02 16:19:34.052] Testing pool stratum+tcp://<IP_ADDRESS>:3333
[1970-01-02 16:19:34.052] Succeeded delayed connect
[1970-01-02 16:19:34.053] RECVD: {"id":0,"result":[[["mining.set_difficulty","01000006"],["mining.notify","01000006"]],"01000006",8],"error":null}
[1970-01-02 16:19:34.053] Pool 0 stratum session id: 01000006
[1970-01-02 16:19:34.053] Pool 0 confirmed mining.subscribe with extranonce1 01000006 extran2size 8
[1970-01-02 16:19:34.053] SEND: {"id": 1, "method": "mining.authorize", "params": ["jack", "1"]}
[1970-01-02 16:19:34.054] RECVD: {"id":1,"result":true,"error":null}
[1970-01-02 16:19:34.054] Stratum authorisation success for pool 0
[1970-01-02 16:19:34.054] Pool 0 stratum+tcp://<IP_ADDRESS>:3333 alive
[1970-01-02 16:19:35.052] All devices disabled, cannot mine!

这个消息表示的是本地没有 cgminer 支持的显卡或者其它挖矿设备。


Material Design Widget "materialdesign - Input": Is it possible to add attribute „autofocus“?

Material Design Widget "materialdesign - Input": Is it possible to add attribute „autofocus“?
like: https://wiki.selfhtml.org/wiki/Referenz:HTML/Attribute/autofocus

i use the vuetify api. seems there is an option for autofocus.
https://vuetifyjs.com/en/api/v-text-field/#props
will give it a try

That would be great. Maybe this command can also be implemented in the „materialdesign  autocomplete“ widget.


check if our element already hiden, so it could not interfere with ot…

…her directives (like xeditable)

@Anisotropic thanks for the update, it looks good and tested fine, so happy to merge in. Thanks again!


[Bug]: Getting a runtime error while invoking the client methods for a generated client

Description
We have generated a client for Slack API using the Ballerina OpenAPI tool and when trying to invoke methods in the connector we are getting a runtime error.
Steps to Reproduce

Publish the Slack client [1] to local ballerina central.

Write a small test case using the Slack client.
import ballerinax/slack;

configurable string token = ?;
public function main() returns error? {
    slack:Client slack = check new({ auth: {token} });
    var response = check slack->/users\.getPresence();
}

Following error is thrown.
error: No such method: $gen$Client&0046$get$users&0046getPresence
    at nivedhtith.test_function.0:main(main.bal:14)

[1] - https://github.com/adibmbrk/module-ballerinax-slack
Affected Version(s)
Ballerina SL 2201.9.0
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Seems like a bug from with https://github.com/ballerina-platform/ballerina-lang/pull/41885 changes.


Allow inline markdown in notification body messages

This PR fixes raw markdown showing in the down message.
By default, Filament doesn't render markdown. By adding Str::inlineMarkdown it allows inline elements such as <strong> and <em> to render while also not being sanitised by Laravel's Str::sanitizeHtml method.
Before:

After:

Thanks for making this package!

Hello, thanks for the PR! I'll create a new release with the changes.


wpsoffice: can not convert to pdf

Describe the bug
can not use export to pdf function
Steps To Reproduce
Steps to reproduce the behavior:

new a doc/docx file
export to pdf

Expected behavior
successfully export to pdf
Screenshots

Additional context
There might be a explain: https://forums.debiancn.org/t/topic/3930
Notify maintainers
@mlatus @th0rgal @rewine @pokon548

Metadata
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.2-zen1, NixOS, 24.11 (Vicuña), 24.11.20240529.ad57eef`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/qgbn0imyridkb9527v6gnv6z3jzzprb9-source`

Add a :+1: reaction to issues you find important.

Reproducible on my side. Will try to investigate and push a pr if feasible

pretty sure we already handle the libtiff.so.5 dependency:
https://github.com/NixOS/nixpkgs/blob/b7ad06c253087c39fa0a73a3291f7075f55019fd/pkgs/applications/office/wpsoffice/default.nix#L121-L122
as mentioned in the thread, can you try running export QT_DEBUG_PLUGINS=1 followed by wpspdf (or applicable command) to confirm thi actual cause?

I have tried to run wpspdf with export QT_DEBUG_PLUGINS=1, here is the log: https://pastebin.mozilla.org/VCTNSYa5.
Seems like there is nothing to do about libtiff.so, maybe something else is broken in otherwise.

Never mind. When I tried to create libtiff.so link to libtiff.so.6 on somewhere and running wpspdf with LD_LIBRARY_PATH=/path/to/libtiff-so-link wps, it works.
Maybe the workaround is not working as expected.

@plokid Can you try this pr https://github.com/NixOS/nixpkgs/pull/318500 and see whether this fix this issue for you?

@pokon548 还是有问题，我这边直接crash了。把测试的文件发给你。你试试
测试文件.zip

又测试了下，是文件里有图片就崩溃

又测试了下，是文件里有图片就崩溃

Fixed in latest push. Feel free to drop a message if further issues appear.

ok, it works fine for me


"undefined method `shift' for nil" with proxy plugin and WebMock

When I have the proxy plugin automatically loaded due to the presence of http_proxy, and try to use WebMock, I get an "undefined method 'shift' for nil" error. It took a lot of debugging because the stack trace was only showing my code's HTTPX...post(...) call, even when I tried to remove the silencers from the backtrace cleaner, but finally I managed to find that the proxy plugin was responsible with this stack trace:
[
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/plugins/proxy.rb:169:in `fetch_response'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/plugins/proxy/http.rb:27:in `fetch_response'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/plugins/retries.rb:98:in `fetch_response'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/session.rb:272:in `block in receive_requests'",
  "<internal:kernel>:187:in `loop'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/session.rb:267:in `receive_requests'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/session.rb:246:in `send_requests'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/session.rb:72:in `request'",
  "/home/alexey/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/httpx-1.3.1/lib/httpx/chainable.rb:10:in `post'",
  ... my code
]

That is, here https://github.com/HoneyryderChuck/httpx/blob/2443ded12b982a8852925f383a6c928362f87ad7/lib/httpx/plugins/proxy.rb#L168-L169 @_proxy_uris is nil. The response is an ErrorResponse wrapping an (intentional) HTTPX::TimeoutError, which is why proxy_error? returns true even though it isn't really a proxy error. "my code" in the stack trace above can be simplified to
HTTPX.post("http://localhost:3800/some_path", body: "")

I hope that's enough to reproduce; if not, I'll try to make a minimal example.

Hi @alexeyr-ci , thx for the report. I'll see about creating a self-contained webmock example in the conditions you describe, and we can move on from there.

Looking at the proxy_error? implementation again, the fix I propose is to replace true in https://github.com/HoneyryderChuck/httpx/blob/2443ded12b982a8852925f383a6c928362f87ad7/lib/httpx/plugins/proxy.rb#L200-L202 with
!(@_proxy_uris && !@_proxy_uris.empty?)

similar to the above cases. I don't know if that's enough for a PR or if you want to add tests as well.

Or make it return false if @_proxy_uris.blank? as a slight simplification.

Is it OK to add WebMock there? If not, I need to somehow trigger an ErrorResponse wrapping one of https://github.com/HoneyryderChuck/httpx/blob/2443ded12b982a8852925f383a6c928362f87ad7/lib/httpx/plugins/proxy.rb#L19 in this super call in fetch_response https://github.com/HoneyryderChuck/httpx/blob/2443ded12b982a8852925f383a6c928362f87ad7/lib/httpx/plugins/proxy.rb#L165-L166 and it isn't obvious to me how to do that. E.g.
session.stub(:fetch_response) do ... end

won't work, because it stubs the complete fetch_response method.
But if it's possible, then repeating https://github.com/HoneyryderChuck/httpx/blob/2443ded12b982a8852925f383a6c928362f87ad7/standalone_tests/env_proxy_test.rb#L28-L32 should reproduce the issue. Would you prefer it as a separate test or added to test_plugin_http_no_proxy?

OK, I see what the commands you mentioned mean now :) Let me try to use them instead.

OK, I can reproduce it by copying the test from test/session_test.rb:
  def test_plugin_http_no_proxy_timeouts
    server = TCPServer.new("<IP_ADDRESS>", CONNECT_TIMEOUT_PORT)
    begin
      uri = build_uri("/", "http://<IP_ADDRESS>:#{CONNECT_TIMEOUT_PORT}")
      session = HTTPX.with(timeout: { connect_timeout: 0.5 })
      response = session.get(uri)
      verify_error_response(response)
      verify_error_response(response, HTTPX::ConnectTimeoutError)
    ensure
      server.close
    end
  end

But for some reason I don't understand it takes a minute to fail despite connect_timeout being set and then maybe retries 2 times since the failure message takes 2 more minutes (note the "Finished in" line):
root@87acbea41878:/home# bundle exec ruby -Itest standalone_tests/env_proxy_test.rb
DEPRECATED: use MT_CPU instead of N for parallel test runs
/home/test/support/websocket_test_plugin.rb:4: warning: base64 was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add base64 to your Gemfile or gemspec to silence this warning.
Run options: --seed 62594

# Running:

...first test failed: EnvProxyTest#test_plugin_http_no_proxy_timeouts
this thread also executed: EnvProxyTest#test_env_proxy_coalescing, EnvProxyTest#test_multiple_get_no_concurrency, EnvProxyTest#test_plugin_http_no_proxy
E

Finished in 180.338237s, 0.0222 runs/s, 0.0887 assertions/s.

  1) Error:
EnvProxyTest#test_plugin_http_no_proxy_timeouts:
NoMethodError: undefined method `shift' for nil
    lib/httpx/plugins/proxy.rb:169:in `fetch_response'
    lib/httpx/plugins/proxy/http.rb:27:in `fetch_response'
    lib/httpx/session.rb:272:in `block in receive_requests'
    <internal:kernel>:187:in `loop'
    lib/httpx/session.rb:267:in `receive_requests'
    lib/httpx/session.rb:246:in `send_requests'
    lib/httpx/session.rb:72:in `request'
    lib/httpx/chainable.rb:10:in `get'
    standalone_tests/env_proxy_test.rb:41:in `test_plugin_http_no_proxy_timeouts'

4 runs, 16 assertions, 0 failures, 1 errors, 0 skips
Coverage report generated for ruby-3.3.5 to /home/coverage/ruby-3.3.5.
Line Coverage: 60.27% (2813 / 4667)

I hope you can improve on this reproduction.

Setting read_timeout instead of/in addition to connect_timeout works: https://gitlab.com/os85/httpx/-/merge_requests/350.

Hey @alexeyr-ci , glad you sorted the test env issues out, and managed tocreproduce it!
I'll need your changes to proceed. Do you mind either sending me the diff, or opening an MR with your changes so far?

https://gitlab.com/os85/httpx/-/merge_requests/350 (this includes a fix, not just reproduction).

fixed with fda0ea8b0e57b1162b150a07f04be95220497bdc

Hi all, we are having the same issue in our app. Do you know when is going to be available a new version of the gem with fix?

Hi @carlos-benito-sequra . I'm still dealing with some backlog, but I should be able to release a patch version in the coming week. Meanwhile, feel free to use (and test) the master branch.


adding support for chart overrides

Issue #, if available:
Description of changes:
Allow EKS to override charts if available
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: f7fac98ba0928068209dbefb7268aa1eca8a48f1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Remove systemd units without a corresponding pod

Description
On startup the systemd units in the system-stackable slice are compared to the pods assigned to this node. If a systemd unit is as expected then it is kept and the Stackable Agent will take ownership again in a later stage. If there is no corresponding pod or the systemd unit differs from the pod specification then it is removed and the Stackable Agent will create a new systemd unit afterwards.
Closes #180
Test
It is not possible to test this change with the agent-integration-tests because systemd units must be prepared and the Stackable Agent must be started afterwards, which is not possible over the Kubernetes API. Therefore it must be tested manually.
The following script can be used for manual testing:
#!/bin/sh

setup_stackable_repository() {
echo Setup Stackable repository

echo -n "
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: repositories.stable.stackable.de
spec:
  group: stable.stackable.de
  versions:
    - name: v1
      served: true
      storage: true
      schema:
        openAPIV3Schema:
          type: object
          properties:
            spec:
              type: object
              properties:
                repo_type:
                  type: string
                properties:
                  type: object
                  additionalProperties:
                    type: string
  scope: Namespaced
  names:
    plural: repositories
    singular: repository
    kind: Repository
    shortNames:
    - repo
" | kubectl apply -f -

echo -n "
apiVersion: stable.stackable.de/v1
kind: Repository
metadata:
  name: integration-test-repository
  namespace: default
spec:
  repo_type: StackableRepo
  properties:
    url: https://raw.githubusercontent.com/stackabletech/integration-test-repo/main/
" | kubectl apply -f -
}

setup_unit_with_pod() {
echo Setup unit with pod

echo -n "[Unit]
Description=default-cleanup-test-ok-noop-service
StartLimitIntervalSec=0

[Service]
Environment=\"KUBECONFIG=/root/.kube/config\"
ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
RemainAfterExit=no
Restart=always
RestartSec=2
Slice=system-stackable.slice
StandardError=journal
StandardOutput=journal
TimeoutStopSec=30

[Install]
WantedBy=multi-user.target" > /lib/systemd/system/default-cleanup-test-ok-noop-service.service

systemctl daemon-reload
systemctl enable default-cleanup-test-ok-noop-service.service
systemctl start default-cleanup-test-ok-noop-service.service

echo "
apiVersion: v1
kind: Pod
metadata:
  name: cleanup-test-ok
spec:
  containers:
    - name: noop-service
      image: noop-service:1.0.0
      command:
        - noop-service-1.0.0/start.sh
  nodeName: localhost
  nodeSelector:
    kubernetes.io/arch: stackable-linux
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: stackable-linux
" | kubectl apply -f -
}

setup_unit_without_pod() {
echo Setup unit without pod

echo -n "[Unit]
Description=default-cleanup-test-no-pod-noop-service
StartLimitIntervalSec=0

[Service]
Environment=\"KUBECONFIG=/root/.kube/config\"
ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
RemainAfterExit=no
Restart=always
RestartSec=2
Slice=system-stackable.slice
StandardError=journal
StandardOutput=journal
TimeoutStopSec=30

[Install]
WantedBy=multi-user.target" > /lib/systemd/system/default-cleanup-test-no-pod-noop-service.service

systemctl daemon-reload
systemctl enable default-cleanup-test-no-pod-noop-service.service
systemctl start default-cleanup-test-no-pod-noop-service.service
}

setup_unit_with_unexpected_content() {
echo Setup unit with pod

echo -n "[Unit]
Description=You did not expect this, did you?

[Service]
ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
Slice=system-stackable.slice

[Install]
WantedBy=multi-user.target" > /lib/systemd/system/default-cleanup-test-unexpected-content-noop-service.service

systemctl daemon-reload
systemctl enable default-cleanup-test-unexpected-content-noop-service.service
systemctl start default-cleanup-test-unexpected-content-noop-service.service

echo "
apiVersion: v1
kind: Pod
metadata:
  name: cleanup-test-unexpected-content
spec:
  containers:
    - name: noop-service
      image: noop-service:1.0.0
      command:
        - noop-service-1.0.0/start.sh
  nodeName: localhost
  nodeSelector:
    kubernetes.io/arch: stackable-linux
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: stackable-linux
" | kubectl apply -f -
}

setup_unit_with_terminating_pod() {
echo Setup unit with terminating pod

echo -n "[Unit]
Description=default-cleanup-test-terminating-noop-service
StartLimitIntervalSec=0

[Service]
Environment=\"KUBECONFIG=/root/.kube/config\"
ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
RemainAfterExit=no
Restart=always
RestartSec=2
Slice=system-stackable.slice
StandardError=journal
StandardOutput=journal
TimeoutStopSec=30

[Install]
WantedBy=multi-user.target" > /lib/systemd/system/default-cleanup-test-terminating-noop-service.service

systemctl daemon-reload
systemctl enable default-cleanup-test-terminating-noop-service.service
systemctl start default-cleanup-test-terminating-noop-service.service

echo "
apiVersion: v1
kind: Pod
metadata:
  name: cleanup-test-terminating
spec:
  containers:
    - name: noop-service
      image: noop-service:1.0.0
      command:
        - noop-service-1.0.0/start.sh
  nodeName: localhost
  nodeSelector:
    kubernetes.io/arch: stackable-linux
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: stackable-linux
" | kubectl apply -f -

kubectl delete pod cleanup-test-terminating &
}

setup_stackable_repository
setup_unit_with_pod
setup_unit_without_pod
setup_unit_with_unexpected_content
setup_unit_with_terminating_pod

The log output of the Stackable Agent should be:
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::cleanup] The systemd unit [default-cleanup-test-unexpected-content-noop-service.service] will be removed because it differs from the corresponding pod specification.
    expected content:
    [Unit]
    Description=default-cleanup-test-unexpected-content-noop-service
    StartLimitIntervalSec=0

    [Service]
    Environment="KUBECONFIG=/root/.kube/config"
    ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
    RemainAfterExit=no
    Restart=always
    RestartSec=2
    Slice=system-stackable.slice
    StandardError=journal
    StandardOutput=journal
    TimeoutStopSec=30

    [Install]
    WantedBy=multi-user.target

    actual content:
    [Unit]
    Description=You did not expect this, did you?

    [Service]
    ExecStart=/opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
    Slice=system-stackable.slice

    [Install]
    WantedBy=multi-user.target
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::cleanup] The systemd unit [default-cleanup-test-terminating-noop-service.service] will be removed because the corresponding pod is terminating.
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::cleanup] The systemd unit [default-cleanup-test-ok-noop-service.service] will be kept because a corresponding pod exists.
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::cleanup] The systemd unit [default-cleanup-test-no-pod-noop-service.service] will be removed because no corresponding pod exists.
[2021-09-24T11:26:39Z INFO  warp::server] TlsServer::run; addr=<IP_ADDRESS>:3000
[2021-09-24T11:26:39Z INFO  warp::server] listening on https://<IP_ADDRESS>:3000
[2021-09-24T11:26:39Z INFO  krator::runtime] Got a watch restart. Resyncing queue...
[2021-09-24T11:26:39Z INFO  krator::runtime] Finished resync of objects.
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::downloading] Looking for package: noop-service:1.0.0 in known repositories
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::downloading] Package noop-service:1.0.0 has already been downloaded to "/opt/stackable/packages/_download", continuing with installation
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::downloading] Looking for package: noop-service:1.0.0 in known repositories
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::downloading] Package noop-service:1.0.0 has already been downloaded to "/opt/stackable/packages/_download", continuing with installation
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::installing] Package noop-service:1.0.0 has already been installed
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::installing] Package noop-service:1.0.0 has already been installed
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::creating_service] Creating service unit for service default-cleanup-test-ok
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::creating_service] Creating service unit for service default-cleanup-test-unexpected-content
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::starting] Starting systemd unit [default-cleanup-test-unexpected-content-noop-service.service]
[2021-09-24T11:26:39Z INFO  stackable_agent::provider::states::pod::starting] Enabling systemd unit [default-cleanup-test-unexpected-content-noop-service.service]
[2021-09-24T11:26:40Z INFO  stackable_agent::provider::states::pod::terminated] Pod default-cleanup-test-terminating was terminated

Leftover
The implementation of SystemDUnit was adapted as far as necessary but a complete refactoring would be required. This will be done in #244.
Review Checklist

[x] Code contains useful comments
[x] (Integration-)Test cases added (or not applicable)
[x] Documentation added (or not applicable)
[x] Changelog updated (or not applicable)

Systemd units where the corresponding pod is terminating, are removed now.
I extended the test script with the function setup_unit_with_terminating_pod.
State before starting the Stackable Agent:
# kubectl get pod cleanup-test-terminating
NAME                       READY   STATUS        RESTARTS   AGE
cleanup-test-terminating   0/1     Terminating   0          14s

# systemctl status default-cleanup-test-terminating-noop-service.service
● default-cleanup-test-terminating-noop-service.service - default-cleanup-test-terminating-noop-service
   Loaded: loaded (/usr/lib/systemd/system/default-cleanup-test-terminating-noop-service.service; enabled; vendor preset: disabled)
  Drop-In: /run/systemd/system/default-cleanup-test-terminating-noop-service.service.d
           └─zzz-lxc-service.conf
   Active: active (running) since Fri 2021-09-24 11:52:10 UTC; 24s ago
 Main PID: 27865 (start.sh)
   CGroup: /system.slice/system-stackable.slice/default-cleanup-test-terminating-noop-service.service
           ├─27865 /bin/sh /opt/stackable/packages/noop-service-1.0.0/noop-service-1.0.0/start.sh
           └─27866 sleep 1d

Sep 24 11:52:10 centos7 systemd[1]: Started default-cleanup-test-terminating-noop-service.
Sep 24 11:52:10 centos7 start.sh[27865]: test-service started

Corresponding log output of the Stackable Agent:
[2021-09-24T11:54:43Z INFO  stackable_agent::provider::cleanup] The systemd unit [default-cleanup-test-terminating-noop-service.service] will be removed because the corresponding pod is terminating.
[2021-09-24T11:54:45Z INFO  stackable_agent::provider::states::pod::terminated] Pod default-cleanup-test-terminating was terminated

State after starting the Stackable Agent:
# kubectl get pod cleanup-test-terminating
Error from server (NotFound): pods "cleanup-test-terminating" not found

# systemctl status default-cleanup-test-terminating-noop-service.service
Unit default-cleanup-test-terminating-noop-service.service could not be found.


rm drew from codeowners

Description & motivation
This PR removes me from the CODEOWNERS file for all docs in this repo 😢
Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

haha - please feel free to @runleonarun! Always happy to help - just want to be avoid being a blocker for reviews that don't need my eyeballs on them :)


Dynamic variable serialization

Is it possible to extract dynamic value (V8ScriptItem), serialize it and later insert as host item into another V8Engine instance (right way)?
I can explore all properties via Engine.Script property, can enumerate whole structure of dynamic object. Even determine array types via
engine.Script.Array.isArray(value);

(Hope there is better way to do this)
But I cannot create object instance of the same V8ScriptItem type in another engine programmatically from host side. (with out reflection)

My data is not simple :) I figured out how to process my case but found 5 different issues.
Here is example: https://github.com/BlackGad/ClearScriptIssue
Issue 1: Invalid dynamic object constructor parsing on Evaluate
engine.Evaluate("{a: 'b'}")

Issue 2: Invalid not typed array constructor parsing on Evaluate
engine.Evaluate("['a','b']")

Issue 3: Strange behavior when 'let' was used between 2 Evaluate calls.

Could you please comment post above? Maybe I just do something in wrong way.

Hi @BlackGad,
Issue 1
The JavaScript syntax { a: 'b' } is ambiguous. You're expecting it to be interpreted as an object literal, but the parser sees it as a block containing a labeled expression. Try enclosing it in parentheses.
Issue 2
We're not seeing any incorrect behavior. In your test program, both
var simpleNotTypedArray = engine.Evaluate("['a','b']");

and
var simpleNotTypedArray = engine.Evaluate("let test2 = ['a','b']; test2;");

produce the same result – a JavaScript array with two elements.
Issue 3
Using let with the same variable name more than once in the same scope is a syntax error.
Issue 4
AddHostObject doesn't work with fundamental values such as numbers as strings. See Issue #90 for an explanation.
Normally it doesn't work with script objects for the same reason; a script object, when handed back to its engine of origin, is stripped of its .NET proxy and therefore can't support some features of AddHostObject.
Instead of using AddHostObject you can simply do this:
engine.Script.test = deserialized;

or this:
engine.Script["test"] = deserialized;

As you've noticed, AddHostObject can successfully expose a foreign script object, and that's because in that case the managed proxy is retained and all access to the object continues to go through ClearScript.
Note that exposing script objects across engine instances – via AddHostObject or the dynamic Script property – is supported but not recommended. Accessing a foreign script object is extremely expensive and can lead to deadlocks unless very carefully managed.
Issue 5
As is the case with host objects, the engine doesn't have direct access to a foreign script object. Instead, it has a proxy that routes access through ClearScript. That proxy is an instance of a special ClearScript-defined JavaScript prototype, and the actual type information of its external target is inaccessible to the local implementation of Array.isArray.
Let us know if you have any additional questions.
Good luck!

Issue 1
You are right, missed code blocks %) replaced with
dynamic result = engine.Evaluate($"new Object()");

Issue 2
Same, I made a mistake somewhere, sorry :)
Issue 3
Please clarify my understanding
ClearScript scope structure looks like this:
outer scope <- engine.Script bridge here
{
processing scope <- Evaluate executing here asynchronously
}

That's why let variable already defined on second call via Evaluate and not accessible via engine.Script bridge
Issue 4 and Issue 5 Thank you for detailed explanation!

HI @BlackGad,
Regarding Issue 3:

Script is a managed reference to the global object.

Evaluate and Execute run code within the global scope, where this refers to the global object.

In the global scope, let declares a global variable, but it does not add a property to the global object (see here). That's why you get the syntax even though the variable isn't accessible via Script.

Cheers!

Hello @hyzx86,
Yes, the test and your sample code still work. You can see it in action here.
Any idea what you might be doing differently?

Hi @ClearScriptLib ,
Thanks for your confirm
Notice that your sample is used in the Microsoft. ClearScript.Linux-x64
But I'm referring to these two packages
		<PackageManagement Include="Microsoft.ClearScript.V8.Native.linux-x64" Version="$(ClearScriptVersion)" />
		<PackageManagement Include="Microsoft.ClearScript.V8.Native.win-x64" Version="$(ClearScriptVersion)" />

I am using ClearScript in Asp.net core project
If I want to be compatible with windows and linux servers.
Which packages should I refer to?
thanks

Updated to this, trying
<PackageReference Include="Microsoft.ClearScript.V8"/>
<PackageReference Include="Microsoft.ClearScript.Core"  />
<PackageReference Include="Microsoft.ClearScript.V8.ICUData" />

Now the error message is :
Cannot load ClearScript V8 library. Load failure information for ClearScriptV8.win-x64.dll

Hi @hyzx86,
Try using the composite packages for Windows and Linux x64:

Microsoft.ClearScript
Microsoft.ClearScript.linux-x64

If you're still unable to make it work, consider sharing a minimal project that reproduces the problem. We'll be happy to take a look.
Good luck!

Also, what's the difference between the Native.xxx versions?

The V8 JavaScript engine is native code (written in C++), so there's a different binary version for each supported hardware platform and operating system.
The easiest way to incorporate ClearScript is to reference one or more of the composite packages, each of which includes everything you need for a single hardware/OS combination.
The component and native packages can be referenced individually to minimize package download, but it's easier and less error-prone to use the composite packages.

Thanks!


Elide empty variations

Don't add a "" to the variant name if the variation name is empty.  For
example, when splitting a variant with name "foo" into variations "" and
"bar", the new variants would be named "foo" and "foo_bar" instead of
"foo" and "foo_bar".
Change-Id: I82342d57e2a8e9f2d65a7d8d2872dcb7b3512899

I'm slightly worried that two mutators with the same variation names cause conflicts due to the elision. But hopefully the variations are named differently enough 😄
LGTM


Setup a second mainnet coordinator for testing stability

#544 should solve #555 and #492. However to ensure that the coordinator is running stable and the issues are truly resolved, we are starting a second mainnet coordinator to test a public channel on the longer run.

coordinator setup on testnet vm.
channel opened between lignumglacies and our test_coordinator (mainnet)


Release of v0.4.0

Just a question. Did you already release v0.4.0? It is not listed on npm: https://www.npmjs.com/package/@ogcapi-js/features

It is now released. Somehow my local npm configuration was corrupted.

No problem. Thanks for your fast response.


conformance: always check gateway positive-polarity conditions

What would you like to be added:
All the conformance tests that create a properly working Gateway, should always check the following three positive-polarity conditions are set to true, as stated here:

ResolvedRefs
Accepted
Programmed

The ResolvedRefs is going to be always checked by #2247 .
Some tests check only Accepted (e.g., https://github.com/mlavacca/gateway-api/blob/8ab4e18ca73533793f8a5d4e8c4248626b4690bf/conformance/tests/gateway-with-attached-routes.go#L114)
Some test check only Programmed (e.g., https://github.com/mlavacca/gateway-api/blob/8ab4e18ca73533793f8a5d4e8c4248626b4690bf/conformance/tests/gateway-secret-reference-grant-specific.go#L54)
Why this is needed:
We need to consistently check that all the valid gateways have all the three positive-polarity conditions always set to true.

I can take this one if thats ok

Reading this one over, yes @levikobi I think it's ready to go.
/triage accepted
/assign @levikobi

@levikobi how are things going on this, do you need any assistance?

@shaneutt I'm good, thanks!
I think I've finished it, waiting for review


[VS Code] Joining collaboration session: Request DebuggerHostService.getLaunchConfigurations failed unexpectedly without providing any details.

Error:
Joining collaboration session: Request DebuggerHostService.getLaunchConfigurations failed unexpectedly without providing any details.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.752

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.37.1

platformName
MacOS

platformVersion
18.6.0

Closing this due to inactivity. Please reopen it if you’re still encountering the issue. Thanks!


Fix typo in azurecr.io url

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@Lakerfield : Thanks for your contribution to the Azure documentation! The author, @stevelas, has been notified to review your proposed change.

Thanks for the fix, @Lakerfield! This is good to go. #sign-off

Actually, #2103 makes this same fix. As it was submitted in June, going to request this PR be closed and let that one through, instead.
Sorry for the delay in addressing this PR, @Lakerfield, we had some issues here on the back-end with our notifications. Please continue with your contributions, we do appreciate the help!
#please-close


Update testnet-collator.md

an error has been made in the command docker pull ghcr.io/t3rn/t0rn-collator:v1.48.4-rc.0 .

Thanks @AlexSHuk for the PR! Good catch 💈
We already have a PR for fixing this issue here https://github.com/t3rn/t3rn/pull/1263 so I will close that one.
Don't hesitate to contribute next time you will spot an issue 🙏


Chapter 11 : Reusing a Keras model

Hi @ageron
I am getting an error " ValueError: The name "dense" is used 2 times in the model. All layer names should be unique." with the last line in Cell 60.

Cell 60:
.....
model_B_on_A.add(keras.layers.Dense(1, activation="sigmoid"))

Just to rule out any errors from my side, I copied the code from the Note book from github, still receiving the same error. I even tried restarting the kernal as well as issuing a keras.backend.clear_session().  But no success.
So, I added a customized name for the time being to move forward as below:
model_B_on_A.add(keras.layers.Dense(1, name = "dense_final", activation="sigmoid"))
My environment:
tensorflow 2.0.0,
keras 2.2.4-tf
Python 3.7.6
Not sure whether I did some thing wrong to get the above error or does it need the 'name' parameter for the last layer to remove ambiguity.
Thanks
Satya

Hi Satya,
Did you remove the last output layer - see code below? Tensorflow should automatically generate each layer's name to avoid this sort of issue - Page 300.
model_B_on_A = keras.models.Sequential(model_A.layers[:-1])
Let me know if that works.
Thanks
Ash


adding delay between each request?

The API I am trying to use will reject my HTTP requests if they are too frequent (say, more than 5 requests per second).
Would it be possible to provide some kind of delay between each call when creating the wrapper?
api = tortilla.wrap('https://github.com', delay=0.2)  # 200ms between each request

I am willing to write a pull request for this but I am not sure if I need to modify the Client or the Wrap class...
We could make a call to self._pause() defined below before each call:
def pause(self):
    if self.delay > 0:
        current_time = time.time()
        elapsed = current_time - self.previous_call
        if elapsed < self.delay:
            time.sleep(self.delay - elapsed)
        self.previous_call = current_time

What do you think?
Another option would be to use an adapted version of the retry decorator defined here: https://wiki.python.org/moin/PythonDecoratorLibrary#Retry

This would be an interesting and useful addition.
It would be a change in the request method of the Client class, which will then save the timestamp of the last request and sleep the remaining time (if required) when the next request comes in. I'll have a look at it.
Until this is implemented, you could also use the caching functionality if you're only executing GET requests.


qga timeout

Without the following patch, vmtest simply failed to execute guest-sync on qga socket (on my box).
diff --git a/src/qga.rs b/src/qga.rs
index 445d11d..55b056b 100644
--- a/src/qga.rs
+++ b/src/qga.rs
@@ -72,6 +72,9 @@ impl QgaWrapper {
         recv_req: Receiver<QgaWrapperCommand>,
         send_resp: Sender<Result<QgaWrapperCommandResp>>,
     ) {
+
+        std::thread::sleep(std::time::Duration::from_millis(1000 * 20));
+

Failed to connect QGA
Caused by:
Timed out waiting for QGA

QEMU 8.0.2 on latest archlinux with a qemu-guest-agent 6.2.1

It seems that QGA socket will not response anything in OVMF and grub state. And that make the first send of guest-sync block forever hence a timeout.

Ah, perhaps a retry in the qga init code is necessary. As you've probably seen, I went through some effort in qga.rs to make sure operations could be properly timed out.

I'm seeing this as well, and the issue is exactly a retry loop is required. If you connect to the QGA socket immediately after it is created, it will never respond to any commands you send it until you recreate the socket. Adding a sleep "fixes" it. We should probably do the same we do in connect_to_qmp socket, except the architecture of the QGA socket makes it a little messy since the actual requests and responses are handled on a separate thread.


SlimeRead: Unexpected Json token

Source information
SlimeRead 1.4.4
Source language
Português
Steps to reproduce
1 install The extension
2 Open The extension
3 open Any manga
Expected behavior

Actual behavior

Mihon/Tachiyomi version
0.16.4
Android version
Android 13
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Note: sometimes the manga works, but the moria when I click on the manga appears this Error and when I click on the manga again it works again

This error happens when I read and go to the next chapter
Note: I tried to replace the image above, but to no avail


Origin header of file:// sent for HTTP requests

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I'm developing an Ionic 2 app that authenticates against an API that has CORS enabled, but only allows for http:// and https:// origins to be configured. If I run my Ionic app in iOS Simulator with Charles Proxy, I can see that an Origin header with a value of file:// is sent when I try to login.
This seems to go against the advice in this blog post.

Your origin will not exist, since you are running off of a file:// URI; therefore, any request outwards will not require a CORS request.

Hello! Thanks for opening an issue with us! As this seems like more of a support question and with the fact that Ionic does not do anything different with Http than normal angular does, i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!

I already asked on the forums and haven't had a response in over a week, that's why I created an issue. ;)
https://forum.ionicframework.com/t/origin-header-of-file-sent-for-http-requests/77413
Normal Angular runs in the browser, so there's always an http-based origin header. With Ionic (and likely Cordova), I'm seeing file:// being sent. I've found that if I allow file:// on a server as an Origin it works. This is a necessary step that doesn't seem to be mentioned in the aforementioned blog post. Hence the reason I created this issue. :)

Latest discussion on the same topic:

https://github.com/ionic-team/ionic/issues/12607

Consolidating to https://github.com/ionic-team/ionic/issues/15057 (please see my comment).


fix($compile): Get Step-3 to a working stage

Update to meet changes in WebRTC library and Xirsys API
VideoRendered was deprecated from the WebRTC library and now instead the VideoView is added to the
VideoTrack by calling the method addSink.  Moreover the Xirsys API has changes and now requires
Basic Authentication, which is performed using Retrofit.


Broken shell shape and position misalignment in pysideluxcoredemo

Versions:

LuxCore #189 (as this sample is broken in master)
Python 3
PySide2

Steps to reproduce:

Start the sample
Hit "LuxBall Shape" → "Toggle Shell"
Hit "LuxBall Position" → "Move Left" (Ctrl + Left)
Hit "LuxBall Position" → "Move Left" (Ctrl + Left)
Hit "LuxBall Shape" → "Toggle Shell"

Shape/Visibility error
(Edit: Apparently this is intended, as implied by luxBallShapeIsCube - I personally assumed the shell would be toggled between visible / invisible, or at least a good looking shape)
After step 2, I get the following image (happens regardless of position; so I can also do steps in order 1, 3, 4, 2 and the error also occurs):
Click here for a screenshot: Bad shape
Position misalignment
After step 5, I get the following (only prepared by setup moves 3 and 4; also happens in order 1, 3, 4, 2, 5):

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I should have fixed the problem.

It is not fixed yet.
The issue also still remains in f673cc780a7380bf94bf67f14bac2eb4201e7068 (please try my steps to reproduce). I'm not sure if I understand the intended fix either.
I don't know enough about the LuxCore SDL yet, but what appears to happen (assumptions):

Setting the .ply property on the shell seems to reset the transformation (should it?).
Deleting an object does not reset its transformation (shouldn't it?). I assume .transformation remains set.

I've attempted to confirm these assumptions using print(self.scene.ToProperties().Get("scene.objects.luxinner.transformation")) (same for "luxshell") but the property isn't found; I blame my lack of LuxCore SDL / API knowledge for this.
Ideally the shell would be modified without resetting the transform, so deleting the objects to reset the positions (which appears to have been the intention of the fix) is not a good solution in my opinion.

It is not fixed yet.
The issue also still remains in f673cc7 (please try my steps to reproduce).

I have and now it works fine here.
Are you sure to have re-compiled pyluxcore.so and not only updated pysideluxcoredemo.py ?

You are right. I didn't realize there were changes outside of the Python script (and it appears I didn't recompile).
It works in https://github.com/LuxCoreRender/LuxCore/commit/f673cc780a7380bf94bf67f14bac2eb4201e7068.


media parameter is missing Error on Main Branch

Description
When attempting to call the image-generation on Twitter, the following error occurs on the main branch:
Error: {"errors":[{"code":38,"message":"media parameter is missing."}]}
    at uploadMedia (node_modules/agent-twitter-client/dist/node/esm/index.mjs:2211:13)
    at async createCreateTweetRequest (node_modules/agent-twitter-client/dist/node/esm/index.mjs:1954:22)

However, it works as expected on the tcm-twitter-image branch.

Just noticed it works only if disable Near plugin

the same problem happens for action callbacks which use sendTweet as well.


Sync To Hudson Fort Tracker

On Fortify system, update upstream import sheet with timestamp.

Closing, now tracking on gitlab all open issues from github.


ciftify_subject_fmri error

I tried to convert Nifti a 4D volume to surface and  I got this error:
ciftify_subject_fmri MYBASEDIR/fmri_s0025447_session3_rest.nii.gz 0025447 out
Subject HCPfolder does not exit

Any insights related to this please ?

Hey Amal,
Are you working from the current master or the latest release? I would
recommend the latest release...the master is in a little flux in prep for a
new release next week.
Sorry, I should have warned about that before,
Erin
On Wed, Mar 28, 2018 at 6:37 PM, Amal<EMAIL_ADDRESS>wrote:

Trying to convert Nifti a 4D volume to surface I got this error:
ciftify_subject_fmri fmri_s0025447_session3_rest.nii.gz 0025447 out
Traceback (most recent call last):
File "/home/boukhdha/anaconda3/bin/ciftify_subject_fmri", line 11, in
load_entry_point('ciftify==1.0.1', 'console_scripts', 'ciftify_subject_fmri')()
File "/home/boukhdha/anaconda3/lib/python3.6/site-packages/ciftify/bin/ciftify_subject_fmri.py", line 625, in main
if not os.path.exists(os.path.join(HCPData,Subject,'MNINonLinear')):
File "/home/boukhdha/anaconda3/lib/python3.6/posixpath.py", line 78, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType
Any insights related to this please ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/edickie/ciftify/issues/45, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMl59kHWw3VfdC6XjL5nQHDKbLrhxXOLks5tjBCUgaJpZM4S_eV4
.

Also, did you run ciftify_recon_all to generate the subject surface info
before running this step?
Thanks,
Erin
On Wed, Mar 28, 2018 at 9:12 PM, Erin W. E. Dickie<EMAIL_ADDRESS>wrote:

Hey Amal,
Are you working from the current master or the latest release? I would
recommend the latest release...the master is in a little flux in prep for a
new release next week.
Sorry, I should have warned about that before,
Erin
On Wed, Mar 28, 2018 at 6:37 PM, Amal<EMAIL_ADDRESS>wrote:

Trying to convert Nifti a 4D volume to surface I got this error:
ciftify_subject_fmri fmri_s0025447_session3_rest.nii.gz 0025447 out
Traceback (most recent call last):
File "/home/boukhdha/anaconda3/bin/ciftify_subject_fmri", line 11, in
load_entry_point('ciftify==1.0.1', 'console_scripts', 'ciftify_subject_fmri')()
File "/home/boukhdha/anaconda3/lib/python3.6/site-packages/ciftify/bin/ciftify_subject_fmri.py", line 625, in main
if not os.path.exists(os.path.join(HCPData,Subject,'MNINonLinear')):
File "/home/boukhdha/anaconda3/lib/python3.6/posixpath.py", line 78, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType
Any insights related to this please ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/edickie/ciftify/issues/45, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMl59kHWw3VfdC6XjL5nQHDKbLrhxXOLks5tjBCUgaJpZM4S_eV4
.


How can I limit the number of screen shots?

I'm using CI service and when trying to save the TestResult files to disk, I realized that it's quite large due to the number of screenshots. I don't need all of the screens shots, just the last 3-4 or so in order to fully understand where a test is failing. Any ideas on how I can accomplish this?

After long time... I think there is no reliable way of doing this from xchtmlreport (or any library like this).
Only developer knows about what screenshots are important to correctly diagnosticate failures. (Not always the last screenshot is the one that is bad nor the origin of the failure)
I guess you would need to create some logic to attach screenshots only when test failed. You could create some wrappers for some XCAssert functions. This is business logic dependant.


PolkSecurity

PolkSecurity
PolkSecurity is an innovative research project that aims to comprehensively analyze and enhance the security of user-facing protocols in the Polkadot ecosystem, with a specific focus on wallet interfaces. By leveraging advanced modeling techniques and rigorous security analysis, we aim to identify potential vulnerabilities, improve user experiences, and ultimately strengthen the overall security posture of Polkadot wallets.
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
[x] I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

I have read and hereby sign the Contributor License Agreement.

Thank you for the application, @developerfred. A couple of initial questions:

Who is the PolkSecurity team? If you apply as an entity, you have to provide a legal entity name and address and perform KYB.

At present, I operate independently while maintaining occasional collaborative partnerships. Should the project
requirements necessitate it, I am prepared to establish a formal business entity.

Do you have previous experience with this kind of analysis? Anything you can share?

Indeed, I possess relevant experience having developed analytical tools of this nature. In terms of public contributions, I have implemented several projects on Dune Analytics, including wallet validation algorithms. I have also engineered tracking technologies and proof-of-participation systems, such as the Gitcoin Passport and GGQuest Protocol (reputation tracking systems).

dune.xyz/codingsh
github.com/codingsh
https://hackmd.io/@8q55UMhBTyav69G13qA9iw/HJvu1S4dv

Do you have any experience with Polkadot and its ecosystem?

Yes, my initial contribution to the Polkadot ecosystem, approximately four years ago, involved implementing a curve algorithm. Since then, I have maintained an active presence in the community through conference participation and staying abreast of relevant publications

How do you determine an article to be "suitable for academic publication"?

When evaluating an article's publishability, I employ several critical criteria: it must demonstrate substantial impact on the target community, present original contributions with proper attribution to referenced research, employ rigorous methodology, adhere to academic writing conventions, and construct evidence-based argumentation. These were the standards I adhered to when publishing articles

Thanks again for the application, @developerfred, and the effort you have put into it. After discussing with our research team, it was decided that the RFP be closed and that we would no longer seek applications on this topic. I apologize for doing this only after your submission. But I hope you'll stick around and find some other interesting topic to work on that we can fund! Also, feel free to check out other funding mechanisms on our website, polkadot.com or https://www.morekudos.com/.


Need to use for our application purpose

Hi @moozzyk, We have developed websocket server using signal r client.  We want to implement their methods on mobile side, so we have used this library to invoke methods.  But due to there is no released version mentioned in Home page we are not able to go ahead.  Is this library will get support in future or also?  Because on asp.net page also they have mentioned that there is no support for swift client.  So can we use this library in production also?

You pretty much always want to use the latest version. I updated README to point to the version that is currently latest but in general I create a tag each time I release a new version and you should use the latest one.
This client was not created by Microsoft and Microsoft does not support it. I develop and maintain it in my free time. You can use it as you see it fit as long as you adhere to the LICENSE.


Wrong work of looping and slide indexes in web component in Angular project

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/romantic-rain-dl3k8p
Bug description
Hello.
The bug appears in Angular project with swiper Web Component.
Using swiper with parameters
{
  loop: true
  slidesPerView: 'auto'
}

create warning
"Swiper Loop Warning: The number of slides is not enough for loop mode, it will be disabled and not function properly. You need to add more slides (or make duplicates) or lower the values of slidesPerView and slidesPerGroup parameters
Also there are no looping slides before initial slide until slidePrev().
While changing slide from first to last swiper.realIndex value shows broken values (1,2)
UPD (28.10.23). look like problem in loop parameter only. Same warning, no rendering of looping slides and wrong indexes whith numeric slidesPerView.
Expected Behavior
No response
Actual Behavior
No response
Swiper version
11.0.3
Platform/Target and Browser Versions
Chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

I confirm that the same error happen when you're swiping, but not when you're setting the index directly with the slideTo() method

Encountering the same issue

Encountering the same issue

@begalievn Using realIndex and slideToLoop() works as it should.


Roll Flutter Engine from 3c6cab03274f to a69789f19be8 (1 revision)

https://github.com/flutter/engine/compare/3c6cab03274f...a69789f19be8
2022-12-19<EMAIL_ADDRESS>Bump github/codeql-action from 2.1.36 to 2.1.37 (flutter/engine#38391)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


🐞 bash completion setup instructions are broken when XDG_DATA_HOME is not set

What is the issue?
Here is an excerpt from the install.sh run on my server(s):
dagger has built-in shell completion. This is how you can install it for:

  BASH:

    1. Ensure that you install bash-completion using your package manager.

    2. Add dagger completion to your personal bash completions dir

      mkdir -p /bash-completion/completions
      dagger completion bash > /bash-completion/completions/dagger

Notice how mkdir -p /bash-completion/completions and the consequent line try to install the bash-completion instructions to the root / folder. #7279 hopefully fixes it.
Dagger version
dagger v0.11.2
Steps to reproduce
curl -L https://dl.dagger.io/dagger/install.sh | BIN_DIR=$HOME/.local/bin sh (and look at the bash-completion part).
Log output
No response

Resolved by https://github.com/dagger/dagger/pull/7279


test: testcases for content management system app using echo api

Description
Adding testcases for content management system app using echo api
Fixes #9421

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
locally
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=3c68c69

/ok-to-test sha=3ba31bc


Collected lots of data but still no seed?

Collected plenty of data and went to the end but still no seed? Am I doing something wrong?

Was the entire map generated in 1.15?

I'm pretty sure. Is there any way to check?


Template for Data Pipelines

Creation of a clean base template for developers creating a new data pipeline, under https://github.com/os-climate/data-pipeline-template. The template should have the base structure for data, metadata and quality tests ingestion (via DBT and great_expectations integration with OpenMetadata).

Quick note that the python version should be at least 3.9, not 3.8 (as stated in Pipfile).  There are several other minimum versions we should stipulate.  See #234.

Template has been completed for extraction / load / transform. Remaining to be tested is integration with OpenMetadata which is now failing due to integration with Airflow Managed APIs. Will proceed to close this issue and open new issues for additional work.


Add even more tools for network troubleshooting

socat - netcat-like but more universal tool
busybox-extras - telnet is in this package
tcptraceroute - find firewalls blocking TCP services
mtr - grafical traceroute
fping - ping multiple hosts and give stats
liboping - graphical (multi)host pinger noping
iptraf-ng - network device and traffic monitoring
net-snmp-tools - snmpget, snmpwalk etc
scapy - a packet manipulation tool
vim - everyone needs good text editor

LGTM ! Thanks, it should be pushed to nicolaka/netshoot:master shortly.


[Feature] My new workflow system proposal

TLDR version:
Old system:
New release → Manually packing the new version into the PPA repository → Update on Ubuntu
Proposed system:
New release → Pull request with a new .deb package (can be automated in the future) → Merging → Signing and publishing a new release in PPA using GH Actions (not by hands, as it is right now)  →  Update on Ubuntu.
Workflow will remain the same as before, but the only needed thing will be a PR with a new .deb file. GitHub Action will do the rest.

If something is hard to understand, please, contact me on Discord.

Thanks for the issue!
This repository was set up for testing purposes and has now been replaced by ppa.ablaze.one.
However, maintenance will continue and we will try to implement the new system you suggested.
Thanks!

Thanks for the issue! This repository was set up for testing purposes and has now been replaced by ppa.ablaze.one. However, maintenance will continue and we will try to implement the new system you suggested. Thanks!

I already started to create it, so I will open new PR when it's complete

Thank you!
The implementation for the new ppa.ablaze.one is
https://github.com/Floorp-Projects/Floorp/blob/ESR102/.github/workflows/linux-build-x64-deb.yml
at
I hope you will take a look there as well!

Thank you! The implementation for the new ppa.ablaze.one is https://github.com/Floorp-Projects/Floorp/blob/ESR102/.github/workflows/linux-build-x64-deb.yml at I hope you will take a look there as well!

It's literally the same as mine, but mine was intended for usage specifically in this repo.

Please let us know if you have any other concerns!


look into http2 support

http2 is coming and libcurl has support for it (http://http2-explained.haxx.se/content/en/part11.html). Let's figure out how to start supporting it.

this seems to be handled transparently by libcurl (https://curl.haxx.se/docs/http2.html). Maybe have an option in restclient-cpp to enable it


Check other dirs for .dockercfg

As per @thockin's comment, I tried to pick sane locations/priorities for .dockercfg paths without a --dockercfg which can easily be added later. This also raised the log level. This was manually tested and worked. Fixes #1767.

LGTM modulo comments

A credentialprovider user is responsible for setting the preferred dir now. Here is the order for the kubelet.
kubernetes ~: make && _output/local/bin/linux/amd64/kubelet --v=10
...
I0127 13:28:35.092134   12584 config.go:74] looking for .dockercfg at /var/lib/kubelet/.dockercfg
I0127 13:28:35.092228   12584 config.go:74] looking for .dockercfg at /home/mike/go/src/github.com/GoogleCloudPlatform/kubernetes/.dockercfg
I0127 13:28:35.092243   12584 config.go:74] looking for .dockercfg at /home/mike/.dockercfg
I0127 13:28:35.092350   12584 config.go:85] found .dockercfg at /home/mike/.dockercfg

/cc @dchen1107 @eparis

LGTM


Implement parallel support for ODBC and OLE DB

Continues the discussion around this feature from #43.

For all advanced statements (like CREATE VIEW or CREATE PROCEDURE) to work with ODBC, ExtendedAnsiSQL=1 has do be added to the connection string (see Using the ExtendedAnsiSQL Connection String Attribute (Access Driver) for further details).
We should do this implicitly in EFCore.Jet, so that nobody has to worry about it. In case anybody complains about it in the future for some reason, we can always add an option to give users the option to disable it.
I also had to switch the identifier character from [identifier] (square brackets) to `identifier` (backticks) because ODBC complaint about the square brackets when used for the newly supported ODBC 4.0 statements (like CREATE VIEW). The backtick is the official identifier character for ODBC and works for OLE DB and in Access as well.

I am going to add support for automatic provider/driver detection, so that just specifying a database name will use the newest installed database provider/driver.

In the future, we should consider refactoring the ODBC/OLE DB conditionals into their own self-contained classes, and ship them as EntityFrameworkCore.Jet.Odbc and EntityFrameworkCore.Jet.OleDb, that could then be discovered by EntityFrameworkCore.Jet at runtime.

For all advanced statements (like CREATE VIEW or CREATE PROCEDURE) to work with ODBC, ExtendedAnsiSQL=1 has do be added to the connection string (see Using the ExtendedAnsiSQL Connection String Attribute (Access Driver) for further details).
We should do this implicitly in EFCore.Jet, so that nobody has to worry about it. In case anybody complains about it in the future for some reason, we can always add an option to disable it.

Implemented in 84aafe4 of #47.

I looked at the code. There are still square brackets around (at least in RemoveBrackets method). Probably we could just find [ and replace (or, better, cover with tests because as far as I can understand all the tests work fine now).

I looked at the code. There are still square brackets around (at least in RemoveBrackets method). Probably we could just find [ and replace (or, better, cover with tests because as far as I can understand all the tests work fine now).

Thanks, I missed a couple of those! I checked the EFCore.Jet and System.Data.Jet projects and fixed the remaining occurrences.  Great!!!

They should all be running, but we are far away from having all the test green.

When you think that everything is stable enough tell me something because I'd like to help you on test fixing.

The code should be stable enough after merging #47 (which I am going to do in a couple of hours). We currently have 1110 green, 788 red and 100 skipped tests from the SimpleQueryJetTest tests.