Compiling src/liburing/register.pyx because it changed.
  Compiling src/liburing/socket.pyx because it changed.
  Compiling src/liburing/socket_extra.pyx because it changed.
  Compiling src/liburing/statx.pyx because it changed.
  Compiling src/liburing/syscall.pyx because it changed.
  Compiling src/liburing/time.pyx because it changed.
  Compiling src/liburing/version.pyx because it changed.
  Compiling src/liburing/xattr.pyx because it changed.
  performance hint: src/liburing/queue.pxd:38:36: No exception value declared for 'io_uring_queue_init_params' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:41:29: No exception value declared for 'io_uring_queue_init' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:44:29: No exception value declared for 'io_uring_queue_mmap' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:47:32: No exception value declared for 'io_uring_ring_dontfork' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:48:29: No exception value declared for 'io_uring_queue_exit' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:49:42: No exception value declared for 'io_uring_peek_batch_cqe' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:52:28: No exception value declared for 'io_uring_wait_cqes' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:57:35: No exception value declared for 'io_uring_wait_cqe_timeout' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:60:25: No exception value declared for 'io_uring_submit' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:61:34: No exception value declared for 'io_uring_submit_and_wait' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:63:42: No exception value declared for 'io_uring_submit_and_wait_timeout' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:69:31: No exception value declared for 'io_uring_enable_rings' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:70:32: No exception value declared for 'io_uring_close_ring_fd' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:72:29: No exception value declared for 'io_uring_get_events' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/queue.pxd:73:40: No exception value declared for 'io_uring_submit_and_get_events' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:21:35: No exception value declared for 'io_uring_register_buffers' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:24:40: No exception value declared for 'io_uring_register_buffers_tags' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:28:42: No exception value declared for 'io_uring_register_buffers_sparse' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:30:46: No exception value declared for 'io_uring_register_buffers_update_tag' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:35:37: No exception value declared for 'io_uring_unregister_buffers' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:37:35: No exception value declared for 'io_uring_register_eventfd' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:38:41: No exception value declared for 'io_uring_register_eventfd_async' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:39:37: No exception value declared for 'io_uring_unregister_eventfd' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:41:39: No exception value declared for 'io_uring_register_personality' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:42:41: No exception value declared for 'io_uring_unregister_personality' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:43:40: No exception value declared for 'io_uring_register_restrictions' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:47:36: No exception value declared for 'io_uring_register_iowq_aff' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:50:38: No exception value declared for 'io_uring_unregister_iowq_aff' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:51:44: No exception value declared for 'io_uring_register_iowq_max_workers' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:52:35: No exception value declared for 'io_uring_register_ring_fd' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:53:37: No exception value declared for 'io_uring_unregister_ring_fd' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:55:36: No exception value declared for 'io_uring_register_buf_ring' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:58:38: No exception value declared for 'io_uring_unregister_buf_ring' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:60:39: No exception value declared for 'io_uring_register_sync_cancel' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:67:32: No exception value declared for 'io_uring_register_napi' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:68:34: No exception value declared for 'io_uring_unregister_napi' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:72:38: No exception value declared for 'io_uring_register_files_tags' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:76:40: No exception value declared for 'io_uring_register_files_sparse' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:78:44: No exception value declared for 'io_uring_register_files_update_tag' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:83:35: No exception value declared for 'io_uring_unregister_files' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/register.pxd:84:40: No exception value declared for 'io_uring_register_files_update' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/other.pxd:58:33: No exception value declared for 'io_uring_mlock_size' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/other.pxd:59:40: No exception value declared for 'io_uring_mlock_size_params' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/syscall.pxd:7:24: No exception value declared for 'io_uring_enter' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/syscall.pxd:12:25: No exception value declared for 'io_uring_enter2' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/syscall.pxd:18:24: No exception value declared for 'io_uring_setup' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/syscall.pxd:19:27: No exception value declared for 'io_uring_register' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/socket_extra.pxd:11:14: No exception value declared for 'bind' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/socket_extra.pxd:12:16: No exception value declared for 'listen' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  performance hint: src/liburing/socket_extra.pxd:13:21: No exception value declared for 'getpeername' in pxd file.
  Users cimporting this function and calling it without the gil will always require an exception check.
  Suggest adding an explicit exception value.
  [ 5/18] Cythonizing src/liburing/helper.pyx
  [16/18] Cythonizing src/liburing/time.pyx
  [ 9/18] Cythonizing src/liburing/probe.pyx
  [ 7/18] Cythonizing src/liburing/other.pyx
  [11/18] Cythonizing src/liburing/register.pyx
  [ 4/18] Cythonizing src/liburing/futex.pyx
  [ 2/18] Cythonizing src/liburing/error.pyx
  [17/18] Cythonizing src/liburing/version.pyx
  [18/18] Cythonizing src/liburing/xattr.pyx
  [14/18] Cythonizing src/liburing/statx.pyx
  [10/18] Cythonizing src/liburing/queue.pyx
  [ 3/18] Cythonizing src/liburing/file.pyx
  [ 8/18] Cythonizing src/liburing/poll.pyx
  [15/18] Cythonizing src/liburing/syscall.pyx
  [ 6/18] Cythonizing src/liburing/os.pyx
  [12/18] Cythonizing src/liburing/socket.pyx
  [13/18] Cythonizing src/liburing/socket_extra.pyx
  [ 1/18] Cythonizing src/liburing/common.pyx
  running egg_info
  creating src/liburing.egg-info
  writing src/liburing.egg-info/PKG-INFO
  writing dependency_links to src/liburing.egg-info/dependency_links.txt
  writing requirements to src/liburing.egg-info/requires.txt
  writing top-level names to src/liburing.egg-info/top_level.txt
  writing manifest file 'src/liburing.egg-info/SOURCES.txt'
  reading manifest file 'src/liburing.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
  adding license file 'LICENSE.txt'
  writing manifest file 'src/liburing.egg-info/SOURCES.txt'
  Getting requirements to build wheel ... done
  Created temporary directory: /tmp/pip-modern-metadata-bo0zk3kl
  Running command Preparing metadata (pyproject.toml)
  running dist_info
  creating /tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info
  writing /tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/PKG-INFO
  writing dependency_links to /tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/dependency_links.txt
  writing requirements to /tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/requires.txt
  writing top-level names to /tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/top_level.txt
  writing manifest file '/tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/SOURCES.txt'
  reading manifest file '/tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
  adding license file 'LICENSE.txt'
  writing manifest file '/tmp/pip-modern-metadata-bo0zk3kl/liburing.egg-info/SOURCES.txt'
  creating '/tmp/pip-modern-metadata-bo0zk3kl/liburing-2024.4.5.dist-info'
  Preparing metadata (pyproject.toml) ... done
  Source in /tmp/pip-install-56wctot0/liburing_349352d959c44c5fb46f42dacbb623f8 has version 2024.4.5, which satisfies requirement liburing@ git+https://github.com/YoSTEALTH/Liburing.git from git+https://github.com/YoSTEALTH/Liburing.git (from shakti==2024.4.4)
  Removed liburing@ git+https://github.com/YoSTEALTH/Liburing.git from git+https://github.com/YoSTEALTH/Liburing.git (from shakti==2024.4.4) from build tracker '/tmp/pip-build-tracker-31qkszjo'
1 location(s) to search for versions of dynamic-import:
* https://pypi.org/simple/dynamic-import/
Fetching project page and analyzing links: https://pypi.org/simple/dynamic-import/
Getting page https://pypi.org/simple/dynamic-import/
Found index url https://pypi.org/simple/
Looking up "https://pypi.org/simple/dynamic-import/" in the cache
Request header has "max_age" as 0, cache bypassed
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /simple/dynamic-import/ HTTP/1.1" 304 0
Fetched page https://pypi.org/simple/dynamic-import/ as application/vnd.pypi.simple.v1+json
  Found link https://files.pythonhosted.org/packages/14/bf/a55bbedd9bc73f88f20acbea36aba70bb0c3862607b0720c498d1f82263e/dynamic_import-0.9.1-py3-none-any.whl (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.5), version: 0.9.1
  Found link https://files.pythonhosted.org/packages/34/db/e294415d91d322958b1244b4d28043e60224a2940a023bae070d6a4e26f1/dynamic_import-0.9.1.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.5), version: 0.9.1
  Found link https://files.pythonhosted.org/packages/17/78/b26e25d9a1cf7b5169453a6aa383cf1e4570a17fe9370ca9997943d8f1cb/dynamic_import-0.9.2-py3-none-any.whl (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.5), version: 0.9.2
  Found link https://files.pythonhosted.org/packages/3d/4f/bdf79977ef628f93ffc9e2f6440c07bfb60671d9788b33305d724e2ca670/dynamic_import-0.9.2.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.5), version: 0.9.2
  Found link https://files.pythonhosted.org/packages/16/4e/491364e1bfff4e69dfcf8a1650b63987c4ff7966d92c37e49736b0a38718/dynamic_import-0.9.3.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.6), version: 0.9.3
  Found link https://files.pythonhosted.org/packages/5d/03/c75ac152d8d387fc5fe8d8f8270b58d215dd003f40bfa10e533308aee6a1/dynamic_import-0.9.4.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.6), version: 0.9.4
  Found link https://files.pythonhosted.org/packages/d2/fd/682ab060769869258f3d67b53df6c69ae83c5bebf62fe467ab2e18cf2b13/dynamic_import-0.9.6.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.6), version: 0.9.6
  Found link https://files.pythonhosted.org/packages/ed/88/d3a82c4a1ce13fe3263833d111e24f8436d1cbd6271f986a7c185c429801/dynamic_import-0.9.7.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.6), version: 0.9.7
  Found link https://files.pythonhosted.org/packages/68/07/61d6e6261fe1db08d9effc66bb7e97a7ab622cfb7b63d57081eb2f784966/dynamic_import-2020.2.10.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.6), version: 2020.2.10
  Found link https://files.pythonhosted.org/packages/20/54/3340940e8819e6f5af97ddbcdef66ac05a5bad4044fdcfbecf01d9dea3b6/dynamic_import-2024.1.26.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8), version: 2024.1.26
  Found link https://files.pythonhosted.org/packages/87/ab/d31a644276dc850cc0841e5483097d9f3b46d3fcc5da8460a0893033e4b4/dynamic_import-2024.2.1-py3-none-any.whl (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8), version: 2024.2.1
  Found link https://files.pythonhosted.org/packages/db/3f/9477f3fafcff6470da6c5e05177d4a40324109ea6cfa65f6eb0ec23556f2/dynamic_import-2024.2.1.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8), version: 2024.2.1
  Found link https://files.pythonhosted.org/packages/5a/22/214fcda12d435b75b0444f535310db2ce0cff2c7384f90d9bfffaaec66ac/dynamic_import-2024.2.13-py3-none-any.whl (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8), version: 2024.2.13
  Found link https://files.pythonhosted.org/packages/74/f1/fa150f1b75dfbb121e2a5cf084062c46542c4b5830388bae686495ed953f/dynamic_import-2024.2.13.tar.gz (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8), version: 2024.2.13
Skipping link: not a file: https://pypi.org/simple/dynamic-import/
Given no hashes to check 14 links for project 'dynamic-import': discarding no candidates
Collecting dynamic-import (from shakti==2024.4.4)
  Obtaining dependency information for dynamic-import from https://files.pythonhosted.org/packages/5a/22/214fcda12d435b75b0444f535310db2ce0cff2c7384f90d9bfffaaec66ac/dynamic_import-2024.2.13-py3-none-any.whl.metadata
  Created temporary directory: /tmp/pip-unpack-2avmid84
  Looking up "https://files.pythonhosted.org/packages/5a/22/214fcda12d435b75b0444f535310db2ce0cff2c7384f90d9bfffaaec66ac/dynamic_import-2024.2.13-py3-none-any.whl.metadata" in the cache
  Current age based on date: 55
  Ignoring unknown cache-control directive: immutable
  Freshness lifetime from max-age: 365000000
  The response is "fresh", returning cached response
  365000000 > 55
  Using cached dynamic_import-2024.2.13-py3-none-any.whl.metadata (14 kB)
  Created temporary directory: /tmp/pip-metadata-xudz4x1x
Created temporary directory: /tmp/pip-unpack-yoz7qcsx
Looking up "https://files.pythonhosted.org/packages/5a/22/214fcda12d435b75b0444f535310db2ce0cff2c7384f90d9bfffaaec66ac/dynamic_import-2024.2.13-py3-none-any.whl" in the cache
Current age based on date: 55
Ignoring unknown cache-control directive: immutable
Freshness lifetime from max-age: 365000000
The response is "fresh", returning cached response
365000000 > 55
Using cached dynamic_import-2024.2.13-py3-none-any.whl (18 kB)
Downloading link https://files.pythonhosted.org/packages/5a/22/214fcda12d435b75b0444f535310db2ce0cff2c7384f90d9bfffaaec66ac/dynamic_import-2024.2.13-py3-none-any.whl (from https://pypi.org/simple/dynamic-import/) (requires-python:>=3.8) to /tmp/pip-unpack-yoz7qcsx/dynamic_import-2024.2.13-py3-none-any.whl
Building wheels for collected packages: shakti, liburing
  Created temporary directory: /tmp/pip-wheel-7rge3jhd
  Destination directory: /tmp/pip-wheel-7rge3jhd
  Running command Building wheel for shakti (pyproject.toml)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-cpython-311
  creating build/lib.linux-x86_64-cpython-311/shakti
  copying src/shakti/__init__.py -> build/lib.linux-x86_64-cpython-311/shakti
  running egg_info
  writing src/shakti.egg-info/PKG-INFO
  writing dependency_links to src/shakti.egg-info/dependency_links.txt
  writing requirements to src/shakti.egg-info/requires.txt
  writing top-level names to src/shakti.egg-info/top_level.txt
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing.h won't be automatically included in the manifest: the path must be relative
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing/compat.h won't be automatically included in the manifest: the path must be relative
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing/io_uring.h won't be automatically included in the manifest: the path must be relative
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing.h won't be automatically included in the manifest: the path must be relative
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing/compat.h won't be automatically included in the manifest: the path must be relative
  dependency /tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/include/liburing/io_uring.h won't be automatically included in the manifest: the path must be relative
  reading manifest file 'src/shakti.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no directories found matching 'example'
  warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
  adding license file 'LICENSE.txt'
  writing manifest file 'src/shakti.egg-info/SOURCES.txt'
  creating build/lib.linux-x86_64-cpython-311/shakti/event
  copying src/shakti/event/__init__.pxd -> build/lib.linux-x86_64-cpython-311/shakti/event
  copying src/shakti/event/entry.pxd -> build/lib.linux-x86_64-cpython-311/shakti/event
  copying src/shakti/event/entry.pyx -> build/lib.linux-x86_64-cpython-311/shakti/event
  copying src/shakti/event/run.pxd -> build/lib.linux-x86_64-cpython-311/shakti/event
  copying src/shakti/event/run.pyx -> build/lib.linux-x86_64-cpython-311/shakti/event
  creating build/lib.linux-x86_64-cpython-311/shakti/core
  copying src/shakti/core/__init__.pxd -> build/lib.linux-x86_64-cpython-311/shakti/core
  copying src/shakti/core/async.pxd -> build/lib.linux-x86_64-cpython-311/shakti/core
  copying src/shakti/core/async.pyx -> build/lib.linux-x86_64-cpython-311/shakti/core
  creating build/lib.linux-x86_64-cpython-311/shakti/os
  copying src/shakti/os/__init__.pxd -> build/lib.linux-x86_64-cpython-311/shakti/os
  copying src/shakti/os/time.pxd -> build/lib.linux-x86_64-cpython-311/shakti/os
  copying src/shakti/os/time.pyx -> build/lib.linux-x86_64-cpython-311/shakti/os
  running build_ext
  building 'shakti.core.async' extension
  creating build/temp.linux-x86_64-cpython-311
  creating build/temp.linux-x86_64-cpython-311/src
  creating build/temp.linux-x86_64-cpython-311/src/shakti
  creating build/temp.linux-x86_64-cpython-311/src/shakti/core
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/local/include/python3.11 -c src/shakti/core/async.c -o build/temp.linux-x86_64-cpython-311/src/shakti/core/async.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/shakti/core/async.o -L/usr/local/lib -o build/lib.linux-x86_64-cpython-311/shakti/core/async.cpython-311-x86_64-linux-gnu.so
  building 'shakti.event.entry' extension
  creating build/temp.linux-x86_64-cpython-311/src/shakti/event
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/lib -I/usr/local/include/python3.11 -c src/shakti/event/entry.c -o build/temp.linux-x86_64-cpython-311/src/shakti/event/entry.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/shakti/event/entry.o -L/usr/local/lib -o build/lib.linux-x86_64-cpython-311/shakti/event/entry.cpython-311-x86_64-linux-gnu.so
  building 'shakti.event.run' extension
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tmp/pip-build-env-xep1d19g/overlay/lib/python3.11/site-packages/liburing/lib -I/usr/local/include/python3.11 -c src/shakti/event/run.c -o build/temp.linux-x86_64-cpython-311/src/shakti/event/run.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/shakti/event/run.o -L/usr/local/lib -o build/lib.linux-x86_64-cpython-311/shakti/event/run.cpython-311-x86_64-linux-gnu.so
  building 'shakti.os.time' extension
  creating build/temp.linux-x86_64-cpython-311/src/shakti/os
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/local/include/python3.11 -c src/shakti/os/time.c -o build/temp.linux-x86_64-cpython-311/src/shakti/os/time.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/shakti/os/time.o -L/usr/local/lib -o build/lib.linux-x86_64-cpython-311/shakti/os/time.cpython-311-x86_64-linux-gnu.so
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  creating build/bdist.linux-x86_64
  creating build/bdist.linux-x86_64/wheel
  creating build/bdist.linux-x86_64/wheel/shakti
  creating build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/__init__.pxd -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/entry.pyx -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/run.pyx -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/entry.pxd -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/run.pxd -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/run.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/shakti/event
  copying build/lib.linux-x86_64-cpython-311/shakti/event/entry.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/shakti/event
  creating build/bdist.linux-x86_64/wheel/shakti/core
  copying build/lib.linux-x86_64-cpython-311/shakti/core/async.pyx -> build/bdist.linux-x86_64/wheel/shakti/core
  copying build/lib.linux-x86_64-cpython-311/shakti/core/__init__.pxd -> build/bdist.linux-x86_64/wheel/shakti/core
  copying build/lib.linux-x86_64-cpython-311/shakti/core/async.pxd -> build/bdist.linux-x86_64/wheel/shakti/core
  copying build/lib.linux-x86_64-cpython-311/shakti/core/async.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/shakti/core
  copying build/lib.linux-x86_64-cpython-311/shakti/__init__.py -> build/bdist.linux-x86_64/wheel/shakti
  creating build/bdist.linux-x86_64/wheel/shakti/os
  copying build/lib.linux-x86_64-cpython-311/shakti/os/__init__.pxd -> build/bdist.linux-x86_64/wheel/shakti/os
  copying build/lib.linux-x86_64-cpython-311/shakti/os/time.pxd -> build/bdist.linux-x86_64/wheel/shakti/os
  copying build/lib.linux-x86_64-cpython-311/shakti/os/time.pyx -> build/bdist.linux-x86_64/wheel/shakti/os
  copying build/lib.linux-x86_64-cpython-311/shakti/os/time.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/shakti/os
  running install_egg_info
  Copying src/shakti.egg-info to build/bdist.linux-x86_64/wheel/shakti-2024.4.4-py3.11.egg-info
  running install_scripts
  creating build/bdist.linux-x86_64/wheel/shakti-2024.4.4.dist-info/WHEEL
  creating '/tmp/pip-wheel-7rge3jhd/.tmp-e7ic62do/shakti-2024.4.4-cp311-cp311-linux_x86_64.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
  adding 'shakti/__init__.py'
  adding 'shakti/core/__init__.pxd'
  adding 'shakti/core/async.cpython-311-x86_64-linux-gnu.so'
  adding 'shakti/core/async.pxd'
  adding 'shakti/core/async.pyx'
  adding 'shakti/event/__init__.pxd'
  adding 'shakti/event/entry.cpython-311-x86_64-linux-gnu.so'
  adding 'shakti/event/entry.pxd'
  adding 'shakti/event/entry.pyx'
  adding 'shakti/event/run.cpython-311-x86_64-linux-gnu.so'
  adding 'shakti/event/run.pxd'
  adding 'shakti/event/run.pyx'
  adding 'shakti/os/__init__.pxd'
  adding 'shakti/os/time.cpython-311-x86_64-linux-gnu.so'
  adding 'shakti/os/time.pxd'
  adding 'shakti/os/time.pyx'
  adding 'shakti-2024.4.4.dist-info/LICENSE.txt'
  adding 'shakti-2024.4.4.dist-info/METADATA'
  adding 'shakti-2024.4.4.dist-info/WHEEL'
  adding 'shakti-2024.4.4.dist-info/top_level.txt'
  adding 'shakti-2024.4.4.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Building wheel for shakti (pyproject.toml) ... done
  Created wheel for shakti: filename=shakti-2024.4.4-cp311-cp311-linux_x86_64.whl size=321047 sha256=64abd43308996c629b426b8eb6009c635bd409ed386944048e055e66f13208ef
  Stored in directory: /tmp/pip-ephem-wheel-cache-fg9ae4qx/wheels/d4/3b/2f/443d924497e5a4858deb1c3cfe1d016cd2570e71db2fed02ef
  Created temporary directory: /tmp/pip-wheel-2mtvpjby
  Destination directory: /tmp/pip-wheel-2mtvpjby
  Running command Building wheel for liburing (pyproject.toml)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-cpython-311
  creating build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/probe.py -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/version.py -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/__init__.py -> build/lib.linux-x86_64-cpython-311/liburing
  running egg_info
  writing src/liburing.egg-info/PKG-INFO
  writing dependency_links to src/liburing.egg-info/dependency_links.txt
  writing requirements to src/liburing.egg-info/requires.txt
  writing top-level names to src/liburing.egg-info/top_level.txt
  reading manifest file 'src/liburing.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
  adding license file 'LICENSE.txt'
  writing manifest file 'src/liburing.egg-info/SOURCES.txt'
  copying src/liburing/__init__.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/common.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/common.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/error.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/error.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/file.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/file.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/futex.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/futex.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/helper.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/helper.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/os.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/os.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/other.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/other.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/poll.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/poll.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/probe.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/probe.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/queue.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/queue.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/register.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/register.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/socket.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/socket.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/socket_extra.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/socket_extra.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/statx.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/statx.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/syscall.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/syscall.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/time.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/time.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/version.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/version.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/xattr.pxd -> build/lib.linux-x86_64-cpython-311/liburing
  copying src/liburing/xattr.pyx -> build/lib.linux-x86_64-cpython-311/liburing
  creating build/lib.linux-x86_64-cpython-311/liburing/include
  copying src/liburing/include/liburing.h -> build/lib.linux-x86_64-cpython-311/liburing/include
  creating build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/__init__.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/file.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/futex.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/io_uring.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/poll.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/socket.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/statx.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/type.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  copying src/liburing/lib/uring.pxd -> build/lib.linux-x86_64-cpython-311/liburing/lib
  creating build/lib.linux-x86_64-cpython-311/liburing/include/liburing
  copying src/liburing/include/liburing/barrier.h -> build/lib.linux-x86_64-cpython-311/liburing/include/liburing
  copying src/liburing/include/liburing/compat.h -> build/lib.linux-x86_64-cpython-311/liburing/include/liburing
  copying src/liburing/include/liburing/io_uring.h -> build/lib.linux-x86_64-cpython-311/liburing/include/liburing
  copying src/liburing/include/liburing/io_uring_version.h -> build/lib.linux-x86_64-cpython-311/liburing/include/liburing
  running build_ext
  building 'liburing.common' extension
  building 'liburing.file' extension
  building 'liburing.futex' extension
  building 'liburing.error' extension
  creating build/temp.linux-x86_64-cpython-311
  creating build/temp.linux-x86_64-cpython-311
  creating build/temp.linux-x86_64-cpython-311
  building 'liburing.helper' extension
  creating build/temp.linux-x86_64-cpython-311
  building 'liburing.poll' extension
  building 'liburing.os' extension
  building 'liburing.other' extension
  creating build/temp.linux-x86_64-cpython-311/src
  building 'liburing.probe' extension
  creating build/temp.linux-x86_64-cpython-311/src
  building 'liburing.queue' extension
  building 'liburing.socket' extension
  creating build/temp.linux-x86_64-cpython-311/src
  building 'liburing.socket_extra' extension
  building 'liburing.statx' extension
  building 'liburing.syscall' extension
  building 'liburing.register' extension
  creating build/temp.linux-x86_64-cpython-311/src
  building 'liburing.time' extension
  creating build/temp.linux-x86_64-cpython-311/src
  creating build/temp.linux-x86_64-cpython-311/src
  creating build/temp.linux-x86_64-cpython-311/src
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  creating build/temp.linux-x86_64-cpython-311/src/liburing
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/other.c -o build/temp.linux-x86_64-cpython-311/src/liburing/other.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/futex.c -o build/temp.linux-x86_64-cpython-311/src/liburing/futex.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/common.c -o build/temp.linux-x86_64-cpython-311/src/liburing/common.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/probe.c -o build/temp.linux-x86_64-cpython-311/src/liburing/probe.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/queue.c -o build/temp.linux-x86_64-cpython-311/src/liburing/queue.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/file.c -o build/temp.linux-x86_64-cpython-311/src/liburing/file.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/socket.c -o build/temp.linux-x86_64-cpython-311/src/liburing/socket.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/statx.c -o build/temp.linux-x86_64-cpython-311/src/liburing/statx.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/socket_extra.c -o build/temp.linux-x86_64-cpython-311/src/liburing/socket_extra.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/register.c -o build/temp.linux-x86_64-cpython-311/src/liburing/register.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/syscall.c -o build/temp.linux-x86_64-cpython-311/src/liburing/syscall.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/helper.c -o build/temp.linux-x86_64-cpython-311/src/liburing/helper.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/error.c -o build/temp.linux-x86_64-cpython-311/src/liburing/error.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/time.c -o build/temp.linux-x86_64-cpython-311/src/liburing/time.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/poll.c -o build/temp.linux-x86_64-cpython-311/src/liburing/poll.o -O3 -g0
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/os.c -o build/temp.linux-x86_64-cpython-311/src/liburing/os.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/error.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/error.cpython-311-x86_64-linux-gnu.so
  building 'liburing.version' extension
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/version.c -o build/temp.linux-x86_64-cpython-311/src/liburing/version.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/version.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/version.cpython-311-x86_64-linux-gnu.so
  building 'liburing.xattr' extension
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/liburing/lib -I/tmp/tmp6zf6frwf/libs/liburing/src/include -I/usr/local/include/python3.11 -c src/liburing/xattr.c -o build/temp.linux-x86_64-cpython-311/src/liburing/xattr.o -O3 -g0
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/helper.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/helper.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/poll.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/poll.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/probe.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/probe.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/other.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/other.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/register.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/register.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/time.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/time.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/futex.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/futex.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/os.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/os.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/xattr.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/xattr.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/socket_extra.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/socket_extra.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/file.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/file.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/statx.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/statx.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/common.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/common.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/queue.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/queue.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/syscall.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/syscall.cpython-311-x86_64-linux-gnu.so
  gcc -shared build/temp.linux-x86_64-cpython-311/src/liburing/socket.o -L/tmp/tmp6zf6frwf/libs/liburing/src -L/usr/local/lib -luring -o build/lib.linux-x86_64-cpython-311/liburing/socket.cpython-311-x86_64-linux-gnu.so
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  creating build/bdist.linux-x86_64
  creating build/bdist.linux-x86_64/wheel
  creating build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/helper.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/probe.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket_extra.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/__init__.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/probe.pyx -> build/bdist.linux-x86_64/wheel/liburing
  creating build/bdist.linux-x86_64/wheel/liburing/include
  creating build/bdist.linux-x86_64/wheel/liburing/include/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/include/liburing/io_uring.h -> build/bdist.linux-x86_64/wheel/liburing/include/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/include/liburing/io_uring_version.h -> build/bdist.linux-x86_64/wheel/liburing/include/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/include/liburing/barrier.h -> build/bdist.linux-x86_64/wheel/liburing/include/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/include/liburing/compat.h -> build/bdist.linux-x86_64/wheel/liburing/include/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/include/liburing.h -> build/bdist.linux-x86_64/wheel/liburing/include
  copying build/lib.linux-x86_64-cpython-311/liburing/os.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/register.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/version.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/common.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/helper.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/probe.py -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/futex.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/poll.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/syscall.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/file.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket_extra.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/other.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/other.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket_extra.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/syscall.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/os.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/error.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/common.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/futex.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/error.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/other.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/version.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/register.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/probe.pxd -> build/bdist.linux-x86_64/wheel/liburing
  creating build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/type.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/__init__.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/poll.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/file.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/uring.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/futex.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/statx.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/io_uring.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/lib/socket.pxd -> build/bdist.linux-x86_64/wheel/liburing/lib
  copying build/lib.linux-x86_64-cpython-311/liburing/poll.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/queue.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/version.py -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/time.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/queue.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/register.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/statx.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/common.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/futex.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/file.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/queue.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/statx.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/version.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/xattr.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/xattr.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/poll.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/xattr.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/os.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/statx.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/syscall.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/error.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/socket.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/time.pyx -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/__init__.py -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/helper.pxd -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/time.cpython-311-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/liburing
  copying build/lib.linux-x86_64-cpython-311/liburing/file.pyx -> build/bdist.linux-x86_64/wheel/liburing
  running install_egg_info
  Copying src/liburing.egg-info to build/bdist.linux-x86_64/wheel/liburing-2024.4.5-py3.11.egg-info
  running install_scripts
  creating build/bdist.linux-x86_64/wheel/liburing-2024.4.5.dist-info/WHEEL
  creating '/tmp/pip-wheel-2mtvpjby/.tmp-8pp2ibw9/liburing-2024.4.5-cp311-cp311-linux_x86_64.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
  adding 'liburing/__init__.pxd'
  adding 'liburing/__init__.py'
  adding 'liburing/common.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/common.pxd'
  adding 'liburing/common.pyx'
  adding 'liburing/error.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/error.pxd'
  adding 'liburing/error.pyx'
  adding 'liburing/file.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/file.pxd'
  adding 'liburing/file.pyx'
  adding 'liburing/futex.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/futex.pxd'
  adding 'liburing/futex.pyx'
  adding 'liburing/helper.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/helper.pxd'
  adding 'liburing/helper.pyx'
  adding 'liburing/os.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/os.pxd'
  adding 'liburing/os.pyx'
  adding 'liburing/other.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/other.pxd'
  adding 'liburing/other.pyx'
  adding 'liburing/poll.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/poll.pxd'
  adding 'liburing/poll.pyx'
  adding 'liburing/probe.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/probe.pxd'
  adding 'liburing/probe.py'
  adding 'liburing/probe.pyx'
  adding 'liburing/queue.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/queue.pxd'
  adding 'liburing/queue.pyx'
  adding 'liburing/register.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/register.pxd'
  adding 'liburing/register.pyx'
  adding 'liburing/socket.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/socket.pxd'
  adding 'liburing/socket.pyx'
  adding 'liburing/socket_extra.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/socket_extra.pxd'
  adding 'liburing/socket_extra.pyx'
  adding 'liburing/statx.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/statx.pxd'
  adding 'liburing/statx.pyx'
  adding 'liburing/syscall.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/syscall.pxd'
  adding 'liburing/syscall.pyx'
  adding 'liburing/time.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/time.pxd'
  adding 'liburing/time.pyx'
  adding 'liburing/version.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/version.pxd'
  adding 'liburing/version.py'
  adding 'liburing/version.pyx'
  adding 'liburing/xattr.cpython-311-x86_64-linux-gnu.so'
  adding 'liburing/xattr.pxd'
  adding 'liburing/xattr.pyx'
  adding 'liburing/include/liburing.h'
  adding 'liburing/include/liburing/barrier.h'
  adding 'liburing/include/liburing/compat.h'
  adding 'liburing/include/liburing/io_uring.h'
  adding 'liburing/include/liburing/io_uring_version.h'
  adding 'liburing/lib/__init__.pxd'
  adding 'liburing/lib/file.pxd'
  adding 'liburing/lib/futex.pxd'
  adding 'liburing/lib/io_uring.pxd'
  adding 'liburing/lib/poll.pxd'
  adding 'liburing/lib/socket.pxd'
  adding 'liburing/lib/statx.pxd'
  adding 'liburing/lib/type.pxd'
  adding 'liburing/lib/uring.pxd'
  adding 'liburing-2024.4.5.dist-info/LICENSE.txt'
  adding 'liburing-2024.4.5.dist-info/METADATA'
  adding 'liburing-2024.4.5.dist-info/WHEEL'
  adding 'liburing-2024.4.5.dist-info/top_level.txt'
  adding 'liburing-2024.4.5.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Building wheel for liburing (pyproject.toml) ... done
  Created wheel for liburing: filename=liburing-2024.4.5-cp311-cp311-linux_x86_64.whl size=2261947 sha256=1398caa3f59155f3154f4f6278dd433fe4b82314871bf176be935cb9c6605d19
  Stored in directory: /tmp/pip-ephem-wheel-cache-fg9ae4qx/wheels/79/46/77/bc3c838cfa39f2799938216fa35111954ccea4b9e3a24d5058
Successfully built shakti liburing
Installing collected packages: dynamic-import, liburing, shakti

Successfully installed dynamic-import-2024.2.13 liburing-2024.4.5 shakti-2024.4.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Remote version of pip: 24.0
Local version of pip:  24.0
Was pip installed by pip? True
Removed build tracker: '/tmp/pip-build-tracker-31qkszjo'

We can see here that it compiles the C code for Shakti only once when creating the wheel.
It does compile the code for liburing once for the build environment and another one for the installation environment. This is due to the combined effect of the build isolation (opt-out behaviour in pip when you have pyproject.toml) + the limitation of pip when it comes to caching the wheel from VCS reference. But this part was already explained in https://github.com/pypa/pip/issues/12604#issuecomment-2029705978, so I assume that is not the reason why you opened this issue in setuptools.


ngx_http_auth_ldap_module.c:38: error: unknown option after ‘#pragma GCC diagnostic

/usr/local/src/nginx-auth-ldap/ngx_http_auth_ldap_module.c:38: error: unknown option after ‘#pragma GCC diagnostic’ kind
/usr/local/src/nginx-auth-ldap/ngx_http_auth_ldap_module.c:395:8: error: #warning "http_auth_ldap: Compiling with OpenSSL < 1.0.2, certificate verification will be unavailable. OPENSSL_VERSION_NUMBER == " XSTR(OPENSSL_VERSION_NUMBER)
make[1]: *** [objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o] Error 1
make[1]: Leaving directory `/usr/local/src/nginx-1.6.2'
make: *** [build] Error 2
how do to it?

this is my parameter:
cd /usr/local/src/nginx-1.6.2 && ./configure --user=www --group=www
--prefix=/usr/local/nginx
--with-http_stub_status_module
--with-http_ssl_module
--with-http_gzip_static_module
--with-http_flv_module
--add-module=/usr/local/src/nginx-auth-ldap
--with-http_realip_module  && make && make install

I replied over there at issue #123. Also, your email inbox is full. :D

@victorhahncastell or @wanggaolin,
Was wondering if anyone else had the same GCC error for CentOS 6.8. I am having the same issue compiling the ngx_http_auth_ldap_module.c module.
Getting the following error:
/github/ldap/nginx-auth-ldap//ngx_http_auth_ldap_module.c:43: error: unknown option after ‘#pragma GCC diagnostic’ kind
github/ldap/nginx-auth-ldap//ngx_http_auth_ldap_module.c:404:8: error: #warning "http_auth_ldap: Compiling with OpenSSL < 1.0.2, certificate verification will be unavailable. OPENSSL_VERSION_NUMBER == " XSTR(OPENSSL_VERSION_NUMBER)
make[1]: *** [objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o] Error 1
make[1]: Leaving directory `github/nginx'
make: *** [modules] Error 2
I found some references to a fix for OSX here: https://github.com/kvspb/nginx-auth-ldap/pull/139/files. Is there a known issue for CentOS 6.8 or the specific version of GCC?
Thanks,
Any help or suggestions are welcome.

Hi @kennys-pt,
I guess you're compiling with Clang, not GCC, as your compiler does not understand the GCC instruction not to escalate this warning to error. And yes, this is exactly what PR #139 is supposed to fix :)
Anyway, please note that you won't get secure SSL unless you upgrade OpenSSL prior to compiling.
Best,
Victor

@kennys-pt: Wait... your getting this even after the patch, right? Which compiler are you using? Could you give us your gcc -v output please?

@victorhahncastell,
Correct this is after the patch which shows merged into master, in which I pulled down this morning.
Cloned from here: https://github.com/kvspb/nginx-auth-ldap
here is the gcc info:
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-<IP_ADDRESS>/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC)
Thanks,
-Kenny

@kennys-pt,
this is most peculiar. Could you by any chance be compiling using g++ instead of gcc? There seems to be an open issue in the GNU C++ compiler. I can't really think about a reason why gcc would ignore this directive otherwise.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686178

@kennys-pt: In any case, if you're looking for a quick fix you can always just remove line 404 (the one starting with "#warning"

@victorhahncastell,
Removed line 404 but I still get the GCC error:
make modules
make -f objs/Makefile modules
make[1]: Entering directory /opt/home/kenny/github/nginx' cc -c -fPIC -pipe  -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g  -I src/core -I src/event -I src/event/modules -I src/os/unix -I objs -I src/http -I src/http/modules \         -o objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o \         /home/kenny/github/ldap/nginx-auth-ldap//ngx_http_auth_ldap_module.c cc1: warnings being treated as errors /home/kenny/github/ldap/nginx-auth-ldap//ngx_http_auth_ldap_module.c:43: error: unknown option after '#pragma GCC diagnostic' kind make[1]: *** [objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o] Error 1 make[1]: Leaving directory /opt/home/kenny/github/nginx'
make: *** [modules] Error 2
Also removed line 43 and that let it complete the compile.

@victorhahncastell - so I compiled with only a single config
./nginx -V
nginx version: nginx/1.10.1
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC)
configure arguments: --add-dynamic-module=/home/kenny/github/ldap/nginx-auth-ldap/
I added load_module "modules/ngx_http_auth_ldap_module.so"; into nginx.conf and it did not complain about the module ngx_http_auth_ldap_module.so.
However - if I copy ngx_http_auth_ldap_module.so to another machine with the nginx 1.10.1 installed from the Nginx repo and add that file to /installdir/nginx/modules and then add the load module into nginx.conf it fails.
Error:
"/etc/nginx/modules/ngx_http_auth_ldap_module.so" is not binary compatible in /etc/nginx/nginx.conf:8
It seems this should support dynamic loading of that module but perhaps since default packaged version of Nginx 1.10.1 does not have that compiled in it wont work?
Thanks again for all the help.

@kennys-pt: I actually have little experience with dynamic nginx modules but it seems plausible that compatibility between different machines is very limited. I suppose those would have to use the same version of libc and other libraries.

Hello all,
Can anyone instruct me to fix this issue?
I am using CentOS release 6.4  and git the latest commit
/usr/local/src/nginx-auth-ldap/ngx_http_auth_ldap_module.c:43: error: unknown option after ‘#pragma GCC diagnostic’ kind
/usr/local/src/nginx-auth-ldap/ngx_http_auth_ldap_module.c:423:8: error: #warning "http_auth_ldap: Compiling with OpenSSL < 1.0.2, certificate verification will be unavailable. OPENSSL_VERSION_NUMBER == " XSTR(OPENSSL_VERSION_NUMBER)
make[1]: *** [objs/addon/nginx-auth-ldap/ngx_http_auth_ldap_module.o] Error 1

@victorhahncastell
I just deleted the warning line, but still got "/usr/local/src/nginx-auth-ldap/ngx_http_auth_ldap_module.c:43: error: unknown option after ‘#pragma GCC diagnostic’ kind" error
I think there are 2 issues:
1, gcc
2, open ssl.
thanks.

The warning option of "-Wcpp" is available for gcc-5.x or later, thus the corresponding pragma directive leads to an error if you compile the code with gcc-4.x. The remedy is, for example, that the line 42 is replaced by
#if GNUC > 4

I've had the same issue as @tianjiaolaozu on CentOS 6 because of the following:

nginx compiles with -Werror (treating warnings as errors)
CentOS 6 has OpenSSL 1.0.1e and so the LDAP module has a warning on compile
CentOS 6 has GCC 4.4.  This version treats #pragma GCC diagnostic warning "-Wcpp" as itself an error and thus skips the statement, leading the the #warning still being an error.

It doesn't appear that < GCC 4.6 has any way of ignoring unknown pragmas from the code; there's apparently "-Wno-unknown-pragmas" but that involves getting that option into nginx's compilation.  For a toolkit like https://hg.nginx.org/pkg-oss/, that involves forking/etc.
So, in short, this module doesn't compile on CentOS 6 with the default nginx compilation/configure options.  For a workaround, just remove the warning from the source and add a condition with the GCC version (eg https://github.com/jcu-eresearch/nginx-auth-ldap/commit/143188675124822ec5144ba230bd05b116a40a1c).


Importing yara rules: comment treated as "include" statement

Describe the bug
I'm trying to configure rule sets from https://yarahq.github.io/
It looks like the function replace_include is called on every line starting with include, even if it's just a comment.
To Reproduce
Steps to reproduce the behavior:

Go to Update sources.
Configure new YARA source with https://github.com/YARAHQ/yara-forge/releases/latest/download/yara-forge-rules-core.zip as an URL
Save and wait till updated
See error 'NoneType' object has no attribute 'group'

Expected behavior
Rules are imported
Environment (please complete the following information if pertinent):

Assemblyline Version: <IP_ADDRESS>
YARA service: <IP_ADDRESS>

Additional context
The file contains two lines starting with include, both are comments with the license:
included in conveying the object code work. (41388)
includes interface definition files associated with source files for (41234)
If I removed them, signatures are correctly imported.
PS. I also tried to go with extended rule set, but it produced errors I wasn't able to easily identify, so I assume some rules there aren't comply with CCCS standard

Should be fixed in the latest stable release of the service.


/dev/loop* not functional

A brief description
Hello, I am trying to use the loopback devices (with the command "losetup") but there are no /dev/loop* devices!

Expected results
running "losetup -f" should return the available loopback devices

Actual results (with terminal output if applicable)
$ losetup -f
losetup: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.)

$ modprobe loop
modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-43-Microsoft/modules.dep.bin'

Your Windows build number
Build 15007.rs_preprelease.170107-1846

Steps / All commands required to reproduce the error from a brand new installation
losetup -f
modprobe loop

Both fail due to lack of /dev/loop* existing.

Required packages and commands to install
None

Loop device support is on our backlog. Please help us prioritize the feature by voting for it on our User Voice.

OK I have voted for it
Thanks for the quick response
prasoc

1 year has gone by without any activity, hence wondering if this is in roadmap or not yet. I need loopback device for mounting secure file as a drive. This seems to be pretty basic requirement.

well @prasoc closed this issue when creating a Uservoice doesn't mean closing the issue. It should be re-opened and get more feedback to get this in place. I did notice the Uservoice created for it was thrown into another that has a considerable amount of votes. So it's up there...along with other things still stuck on backlog.

It should be re-opened and get more feedback to get this in place.

Actually no, some people are just more prone to following CONTRIBUTING.md than others. "...wondering if this is in the roadmap or not yet I need loopback device for mounting secure file as a drive" is precisely what UserVoice is for.

I want loop devices..... I need to mount dumps of filesystems.

Loop devices are the most basic thing you could ask from a linux system

#131

It should be re-opened and get more feedback to get this in place.

Actually no, some people are just more prone to following CONTRIBUTING.md than others. "...wondering if this is in the roadmap or not yet I need loopback device for mounting secure file as a drive" is precisely what UserVoice is for.

Please be advised that as of today 11/4/2019 (nearly three years since this issue was opened) that UserVoice is not accepting submissions and loops back to this repo.
Please count me as another person who needs this feature. I went through the whole installing WSL deal only to find that I couldn't work with dumps of images/filesystems.


Discrepancy in Information Retrieval for CN106056591B Between SearXNG and Perplexica

Hello, I found an issue. When I opened 4000:8000 and searched for CN106056591B using SearXNG, I received some relevant information. However, when I requested an introduction to CN106056591B in Perplexica, the response contained incorrect information. What's going on?
The following images show the results returned by SearXNG and Perplexica, respectively.

The former is correct: 'A method for urban density estimation by fusing spectral images and lidar data.' The latter is incorrect: 'A method for determining the optimal number of clusters in data clustering.' Why didn't Perplexica generate an answer based on the results obtained from SearXNG?

Can someone give me some suggestions?


Define pulse protocol to open markdown files from web

We can handle pulse:// urls with the desktop app and allow us to open markdown files from web with the desktop app.

@demian-arenas so you want to do this? How do you plan to do implement it?
How do you think it will work the protocol?

My first idea was to take advantage of the 'Raw' option of Github to see files, put a simple URL like this

https://github.com/PlatziDev/pulse/blob/master/CODE_OF_CONDUCT.md

and convert to this

https://raw.githubusercontent.com/PlatziDev/pulse/master/CODE_OF_CONDUCT.md

then with simple Fetch API download the content. Use Github API to save the file. But I don't know if that's the better idea.

This was my idea with pulse://:
I go to a website which offer me a way to edit content as Markdown (e.g. Platzi) and they can give me a button with something like Edit on Pulse, that link should has a URL with the pulse protocol  and if I have Pulse installed on my computer will open it with the content so I can update it there.
But it should work everywhere and it doesn't matter of the site and should be easy to implement for everysite.
I like the idea of using a simple URL and adding a RAW options so we could have pulse://domain.com/blog/my-post and then the editor could fetch it adding ?raw or something like that. I don't want to use a subdomain since it could require more work from the website using the protocol.
The way to implement it server side should be super simple with minimal work.

oh right, now I understand...
when you say 'client app' do you refer to pulse-editor, right? could be used something like this
function runPulse() {    WshShell = new ActiveXObject('WScript.Shell')    WshShell.Run('c:/url/to/pulse.exe') }
from pulse-editor, but that only open desktop app... could send the content as arguments to pulse.exe?

@demian-arenas Electron has a native way to define a protocol to be handled by the desktop app, I tried it before and it works but I didn't defined how it should work.
And with client app I mean Pulse (this pulse, not pulse-editor).

@sergiodxa What protocol method did you use?
Reading the protocol documentation I saw that you can use protocol.registerHttpProtocol (scheme, handler [, completion]) where the handler is a function with a request object and that support Post request, sending the data via uploadData. In the form of Buffer, could send the data with that option and response to web with message like 'The file is ready in Pulse'
But, when a protocol is registered, is it still listening to with the closed app? or should have it open Pulse whenever you want to do that, or leave Pulse in the background with a small process waiting for the protocol event "pulse://"?

I think it was protocol.registerFileProtocol.
And yes it works even if the app is closed because the first time you open it is registered on the system.


KMP + Xcode 5.4 - Error: ld: symbol(s) not found for architecture arm64

During a KMP build using Swift Package Manager, I consistently get this error:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_JSContext", referenced from:
       in GoogleMobileAds[arm64][421](GADOMIDLightJSExecutor.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It occurs with any project I use that incorporates the swift-package-manager-google-mobile-ads dependency.
It also unlinks any other Swift Package Manager dependencies that were working before.
Platform Info:
Google Mobile Ads: Version 11.9.0+
Xcode: Version 15.4 (15F31d)
Android Studio: Koala Feature Drop | 2024.1.2
Gradle: Version 8.7

This was a Kotlin 2 /Xcode 16 compatibility issue found here:  https://youtrack.jetbrains.com/issue/KT-71287/Support-Xcode-16-in-Kotlin#focus=Comments-27-10684340.0-0
Issue is resolved by upgrading to Kotlin version 2.1.0-Beta1 or higher.


Add tests & Service's Configuration has optional fields that shouldn't be optional

Related to #4776
Related to https://github.com/paritytech/polkadot/pull/832
To summarize the changes:

I did not manage to validate with types the service's Configuration. But I did reduce the possibility of errors by moving all the "fill" functions to their respective structopts
I split params.rs to multiple modules: one module params for just CLI parameters and one module commands for CLI subcommands (and RunCmd). Every command and params are in their own file so things are grouped better together and easier to remove
I removed the run and run_subcommand helpers as they are not helping much anymore. Running a command is always a set of 3 commands: 1. init 2. update config 3. run. This still allow the user to change the config before arguments get parsed or right after.
I added tests for all subcommands.
I updated some feature flags with the new benchmark subcommands because client/cli couldn't build anymore. So I added a flag rocksdb

Overall the aim is to improve the situation with the Configuration and the optional parameters, add tests, make the API more consistent and simpler.

Now also fixes https://github.com/paritytech/substrate/issues/4888

I split params.rs to multiple modules:

Oh no :scream:

I split params.rs to multiple modules:

Oh no scream , already did the same thing here #4954
Rebasing is going to be a nightmare

:rofl: sorry

Assuming the params and commands didn't change other than being split up, because I only gave them a rough glance ...

Yes well it was complicated because a lot of changes have been pushed to master, especially yesterday.
TL;DR: I'm very confident nothing has been lost.
Long story: I'm experimenting a new workflow where I merge the most non-conflicting commits to my branch to update it and then I create a single merge commit with the conflicting commit where I solve the issue independently.
Because of that, I look at the commit carefully and I replicate the changes in my files properly. It's a bit like what happen with rebase (resolving conflicts commit by commit) except that it's merging instead of rebasing.

Thanks for all the tests!

You're welcome! :hugs: I have hope to improve a lot sc_cli to a point where it would be very stable and intuitive.


install error

Hello.
When I install the package with
pip instgall --user .
I got the follwoing errors.
Requirement already satisfied: tqdm in /home/m123456/anaconda3/lib/python3.12/site-packages (from echonet==1.0.0) (4.66.4)
Collecting sklearn (from echonet==1.0.0)
Using cached sklearn-0.0.post12.tar.gz (2.6 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
The 'sklearn' PyPI package is deprecated, use 'scikit-learn'
rather than 'sklearn' for pip commands.
  Here is how to fix this error in the main use cases:
  - use 'pip install scikit-learn' rather than 'pip install sklearn'
  - replace 'sklearn' by 'scikit-learn' in your pip requirements files
    (requirements.txt, setup.py, setup.cfg, Pipfile, etc ...)
  - if the 'sklearn' package is used by one of your dependencies,
    it would be great if you take some time to track which package uses
    'sklearn' instead of 'scikit-learn' and report it to their issue tracker
  - as a last resort, set the environment variable
    SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True to avoid this error

  More information is available at
  https://github.com/scikit-learn/sklearn-pypi-package
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
My pip version is 24.2, python verions is 3.12
Thanks.

Hi,there,I've installed it successfully.You should try to modify the setup.py in [install_requires] block,find the sklearn change to scikit-learn.This may be helpful.


Access to the meeting dataset

Hi,
May I ask if we still have access to download the dataset? '
When I run the command:
azcopy copy https://notsofarsa.blob.core.windows.net/benchmark-datasets/train_set/240825.1_train/MTG . --recursive
I got the error:
INFO: Scanning...
INFO: Autologin not specified.
INFO: Authenticating to source using Unknown, Please authenticate using Microsoft Entra ID (https://aka.ms/AzCopy/AuthZ), use AzCopy login, or append a SAS token to your Azure URL.
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://notsofarsa.blob.core.windows.net/benchmark-datasets
--------------------------------------------------------------------------------
RESPONSE 401: 401 Server failed to authenticate the request. Please refer to the information in the www-authenticate header.
ERROR CODE: NoAuthenticationInformation
--------------------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?><Error>NoAuthenticationInformation<Message>Server failed to authenticate the request. Please refer to the information in the www-authenticate header.
RequestId:3523a328-001e-00cb-2177-4b1feb000000
Time:2024-12-11T02:50:22.8410863Z</Message></Error>
--------------------------------------------------------------------------------

Thanks in advance!

Hi Muhan. Sure, we never planned to revoke access to this data. I am checking what happened. Will get back to you.

Hi team. I'm currently having the same issue.
from utils.azure_storage import download_meeting_subset
download_meeting_subset('train_set', '240825.1_train', 'data/meeting_data')

About 3 weeks ago, I have run it and I can download it. Due to some reason I want to download it again and it fails with the same error as @muhangao. Any help would be helpful, thanks!

Hi team, I'm currtently having the similar issue.
NOTE: I have use the command azcopy login and Tip has been successful。
However, I run the below example, it is not still working.
For example:
./azcopy copy https://notsofarsa.blob.core.windows.net/benchmark-datasets/train_set/240825.1_train/MTG . --recursive

The error log:
INFO: Scanning...
INFO: Autologin not specified.
INFO: Authenticating to source using Azure AD
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://notsofarsa.blob.core.windows.net/benchmark-datasets
--------------------------------------------------------------------------------
RESPONSE 401: 401 Server failed to authenticate the request. Please refer to the information in the www-authenticate header.
ERROR CODE: InvalidAuthenticationInfo
--------------------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?><Error>InvalidAuthenticationInfo<Message>Server failed to authenticate the request. Please refer to the information in the www-authenticate header.
RequestId:cea76fac-c01e-007d-7532-5b6d9d000000
Time:2024-12-31T03:17:42.4115452Z</Message><AuthenticationErrorDetail>Issuer validation failed. Issuer did not match.</AuthenticationErrorDetail></Error>
--------------------------------------------------------------------------------
.
ERROR DETAILS: https://aka.ms/AzCopyError/InvalidAuthenticationInfo

Looking forward to your reply.


TargetTemperature, HeatingThresholdTemperature, CoolingThresholdTemperature characteristics and get/setVal

I created a thermostat service and noticed when attempting to set the target temperatures (TargetTemperature, HeatingThresholdTemperature, CoolingThresholdTemperature) all set values were whole number in degrees C instead of giving the setpoint in degrees C with .1 degree precision.  This results in set points being a degree or two different (in Degrees F) than what I assume HomeKit really sent.  I confirmed that using setRange(min,max,stepValue) does not appear to resolve the issue, so my assumption is you have the correct stepValue set for these characteristics, although I was unable to find where in code this is maintained.
Here is what i see in debug log, where the trailing decimal seems to get lopped off:

PUT /characteristics HTTP/1.1
Host: HomeSpan\032Server-2._hap._tcp.local
Content-Length: 93
Content-Type: application/hap+json
------------ END BODY! ------------
{"characteristics":[{"aid":1,"iid":12,"value":17.800000000000001}],"pid":3524024862036870145}
------------ END JSON! ------------
In Put Characteristics #0 (<IP_ADDRESS>)...
target: 17
Updating aid=1 iid=12 (okay)

Any thoughts/insight on this would be great.  Thanks.

Are you specifying the template parameter as float (or double) as such:  getVal<float>(), getNewVal<double>(), etc.  Note that if a template parameter is not specified, HomeSpan defaults to <int>, which would explain why the 17.8 is being cast to just 17.

And there you have it.  Thanks again Gregg!


Got error 'The control-flow constructs [] are not supported by the backend.' when running a generated pass manager

Describe the bug
I didn't find a default pass manager only for mapping in Qiskit, so I call generate_preset_pass_manager to get a staged pass manager with optimization, layout and routing. Then I try to move all the actions except optmization to an empty pass manager and call it.
Steps to reproduce
Call run method of the generated pass manager to get the mapping of an input circuit.
Expected behavior
Should be able to run the pass manager with the circuit.
Suggested solutions
Additional Information

qiskit-ibm-runtime version: 0.44.2
Python version: 3.11.5
Operating system: Windows

@zuguangh can you provide more information? Like which backend were you using, and the stack trace of the error?

Please reopen with more information.


ytdl.getInfo() returns a lot of unnecessary data.

Suppose I want the info of the format_id= 22 of the youtube video, ytdl.getInfo() returns the info of the format_id along with the info of all the formats available in the "formats" key of the response which causes a delay in the call of the function.
Also there should be an option to not retrieve information about the DASH formats.

I have the same question. How to get less info to make it faster? I have to wait around 4-5 seconds.

@suraj021 Option for skipping DASH:
--username=,--password=,--youtube-skip-dash-manifest

good to know, thanks for that 🙂


Scraping comments doesn't work

Hello,
I've been facing a problem when trying to scrape comments with the parameters :
--filename users_to_scrape  --destination data/metadata --retain_username --media_types none --medi
a_metadata --include-location --comments

It throws an error after some time : requests.exceptions.ConnectionError: ('Connection aborted.', BadStatusLine('\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0
0\x00Cache-Control: private, no-cache, no-store, must-revalidate\r\n',))
It only does this with comments.
Thank you for your help,
Otherend

The error suggests that the host isn't responding in the expected manner or data received doesn't make any sense. It may be detecting that you're trying to scrape it and as a result it's deliberately disconnecting you.

Would adding random time.sleep in your code prevent me to be detected?

In order to solve this bug, we need to reproduce the error, because it doesn't occur when scraping a single account.
How many accounts were you scraping?

I was scraping 2 accounts (from a file that contains a list of users).
When I tried to do it on a server it failed. On another server it worked fine.

You could try Instaloader, a similar tool which recently got the feature of downloading comments.
pip3 install git+https://github.com/Thammus/instaloader
instaloader --comments profile1 profile2

It then creates a folder for each profile and downloads the pictures along with their captions and comments, but you can customize where exactly to download them. Looking up locations and storing them as Google Maps URL is also supported by passing the --geotags flag.


Bump nightly appimage package after successful arch linux build

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

@pajlada reminder that this PR exists.


Question: Errorformat input is wrong and I have no idea why

Initial question
I'm testing CI + reviewdog in https://github.com/Kakadu/fp2021/pull/3 and got an issue that I don't know how to resolve. The input file for reviewdog is
Lambda/lib/utils.ml:4:0: Type name `intentionalCamelCase` should be in snake case
Lambda/lib/ast.mli:4:0: Type name `notASnakeCase` should be in snake case
Lambda/lib/ast.mli:10:0:Constructor 'App' has no documentation attribute
Lambda/lib/ast.mli:14:0:Constructor 'XXX' has no documentation attribute

but I got some complains about it and only lint 2 is shown as PR comment:
$ cat Lambda/_build/default/review.golint | reviewdog -f=golint -reporter=github-pr-review -diff="git diff FETCH_HEAD"  -filter-mode=nofilter -fail-on-error -tee
Lambda/lib/utils.ml:4:0: Type name `intentionalCamelCase` should be in snake case
Lambda/lib/ast.mli:4:0: Type name `notASnakeCase` should be in snake case
Lambda/lib/ast.mli:10:0:Constructor 'App' has no documentation attribute
Lambda/lib/ast.mli:14:0:Constructor 'XXX' has no documentation attribute
Lambda/lib/utils.ml:4:0: Type name `intentionalCamelCase` should be in snake case
Lambda/lib/ast.mli:4:0: Type name `notASnakeCase` should be in snake case
reviewdog: input data has violations
Warning: [golint] reported by reviewdog 🐶
Type name `intentionalCamelCase` should be in snake case

Raw Output:
Lambda/lib/utils.ml:4:0: Type name `intentionalCamelCase` should be in snake case
Error: Process completed with exit code 1.

Clearly something goes wrong. Could you clarify why exactly my input is not OKay?
UPDATE 1
I discovered that spaces before message text are bad. After fixing the output and running review dog I have no errors:
$ cat Lambda/_build/default/review.golint | reviewdog -f=golint -reporter=github-pr-review -diff="git diff FETCH_HEAD" -fail-on-error  -filter-mode=nofilter -tee
Lambda/lib/utils.ml:4:0:Type name `intentionalCamelCase` should be in snake case
Lambda/lib/ast.mli:4:0:Type name `notASnakeCase` should be in snake case
Lambda/lib/ast.mli:10:0:Constructor 'App' has no documentation attribute
Lambda/lib/ast.mli:14:0:Constructor 'XXX' has no documentation attribute

But no comments appeared in my PR: https://github.com/Kakadu/fp2021/pull/4/ No idea how to hack this further...

I also tried to use reviewdog on desktop, but after setting many env variables I get
reviewdog: post failed for golint: status=400: failed to create gh transport: GET https://api.github.com/users/Kakadu/installation: 404 Not Found []
and don't know what does it mean

I managed to make things better when switched from golint-like otput to rdjsonl


{Compute} Remove deprecated image alias

Related command

Description

This PR is to keep consistent with https://github.com/Azure/azure-rest-api-specs/pull/29870
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Compute

/azp run


Add favourite functionality to grid view

think about adding ability to favourite from grid view. show whether it is a favourite too.

done


consider using parboiled2 as a jar dependency in v1.0.0

Relates to https://github.com/apache/incubator-pekko-http/issues/35

by having a jar dependency, our licensing requirements are simplified
by keeping a pekko copy of the source files, we need to account in more detail for this in our LICENSE and NOTICE
one particularly problematic file is https://github.com/apache/incubator-pekko-http/blob/2e8b2fade52cf0a85d0150a407226851cf00c683/akka-parsing/src/main/java/akka/parboiled2/util/Base64.java

has multiple authors at various stages and BSD and Apache licensing
even maybe possible to use Java's Base64 class at this stage

we even have a PR for this - https://github.com/apache/incubator-pekko-http/pull/14

@jrudolph this is just for discussion but I'd be interested in your views on this

one particularly problematic file is https://github.com/apache/incubator-pekko-http/blob/2e8b2fade52cf0a85d0150a407226851cf00c683/akka-parsing/src/main/java/akka/parboiled2/util/Base64.java

has multiple authors at various stages and BSD and Apache licensing
even maybe possible to use Java's Base64 class at this stage

I will comment on the other stuff later, but I wouldn't advocate for removing/changing this for Java's Base64 class. There is a reason why this Base64 implementation is there, Base64 is used frequently in the context of http and as you can ready from the comments its a far more efficient implementation then Java's Base64. Generally speaking its also not unusual for the Akka/Pekko ecosystem to reimplement JVM API's if they are not very efficient (which isn't uncommon).
As an alternative we can make this base64 into its own sbt module/artifact which would make it fairly easy to add in custom licenses in a similar to what was done with pekko-core's protobuf modules?

This is a duplicate of #1. Basically, I agree with this move. In #14, @mdedetrich suggested to move that change to the 1.1.x release but if it is easy enough to do I would also concur with doing this earlier if it simplifies the license situation.

Btw. IIRC the original reasoning for vendoring was to avoid a transitive dependency on shapeless (which has now been removed from parboiled2) to avoid having to delay releases until shapeless is out.

@jrudolph Do you have any comments on the Base64 situation?

I'll close this in favour of https://github.com/apache/incubator-pekko-http/issues/39 and link this discussion there

Also created https://github.com/apache/incubator-pekko-http/issues/40 to discuss Base64 situation specifically


updated Apache example for post-4.x

updated the apache example to match the post-4.x NGINX reccommendations
config submitted by user prixone on the forums...
https://forum.mattermost.org/t/apache-reverse-proxy-with-mm-4-0

Thanks @StingRayZA for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.


[Package Request]: BellSoft LibericaJRE

How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

What's the type of your software?
msi
Please provide the following information
Download Page Url: https://bell-sw.com/pages/downloads/
Install Options: MSI package
Publisher: BellSoft
Publisher Page: https://bell-sw.com/
Package Page: https://bell-sw.com/pages/downloads/
Package Name: BellSoft.LibericaJRE
Description: BellSoft LibericaJRE
Package Version: 8u382+6 11.0.20+8 17.0.8+7 etc...
Installer URL: https://download.bell-sw.com/java/8u382+6/bellsoft-jre8u382+6-windows-amd64-full.msi etc...
License: GPLv2
License Page: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
Copyright: BellSoft Corporation

Hello, @PakhomGolynga.
I search all pull requests related to keyword "Liberica" and see most manifests of BellSoft.LibericaJDK are submitted by you. They are created perfectly and pass the Azure pipelines without any exceptions or errors.
I'm currently working on submitting all versions of BellSoft.LibericaJRE from version 8 to 21, including standard and full edition. All above pull requests passed the pipeline but labeled Validation-Domain error.
Could you please help review and request changes of the above pull requests? I can't figure out what is wrong and have no idea how to improve my manifests. Thank you!