Project does not compile after installing esp-idf v4.4-dev-3657-gdf0929009a (IDFGH-6221)

Hi,
I installed esp-idf version v4.4-dev-3657-gdf0929009a following this link:
https://docs.espressif.com/projects/esp-idf/en/release-v4.4/esp32/get-started/windows-setup.html
When i compile the esp-idf project this error appear:
Cannot parse CMake requirements line: __component_set_property(__idf.global_conf REQUIRES "cxx;newlib;freertos;esp_hw_support;heap;log;lwip;soc;hal;esp_rom;esp_common;esp_system;esp32")
i tried to follow this:
https://github.com/espressif/vscode-esp-idf-extension/issues/388
but when i put "ESP-IDF: Open ESP-IDF Terminal" in cmd or esp-idf cmd
'ESP-IDF:' is not recognized as an internal command
or external, an operable program or a batch file.
How to solve this problem ???

I tried this, but not solved the problem.

Some suggestion on how to solve this ?
Thank's.

@brianignacio5 and @0xjakob and @igrr

I am trying in 2 computers this installation and same problem on 2 computers.
I am stuck in this problem.
Whenever i go to install a new idf is this annoyance.
Ever.
For this reason i go months without updating esp idf (6 months or more).
Espressif should choose a single ide and focus all efforts on it.

@baldhead69 The command ESP-IDF: Open ESP-IDF Terminal is for the esp-idf extension in vscode. In terminal this doesn't work because it is not part of it.
If you are using the terminal itself, after updating idd-component-manager, delete your project's build folder and try again. Check if there is an environment variable IDF_COMPONENT_MANAGER enabled in your terminal. Delete it, delete the build folder and try to build again.

@brianignacio5
How to update idd-component-manager ?
I understand very little about the esp-idf build tools.

@brianignacio5
Did you mean idf-component-manager ?
If so, i already have installed.
[code]
IDF_TOOLS_PATH not set. Setting to C:.espressif
Setting PYTHONNOUSERSITE, was not set
Using Python in C:.espressif\python_env\idf4.4_py3.8_env\Scripts
Python 3.8.7
Using Git in C:.espressif\tools\idf-git\2.30.1\cmd
git version 2.30.1.windows.1
Setting IDF_PATH: C:\esp-idf
Adding ESP-IDF tools to PATH...
C:.espressif\tools\xtensa-esp32-elf\esp-2021r2-8.4.0\xtensa-esp32-elf\bin
C:.espressif\tools\xtensa-esp32s3-elf\esp-2021r2-8.4.0\xtensa-esp32s3-elf\bin
C:.espressif\tools\riscv32-esp-elf\esp-2021r2-8.4.0\riscv32-esp-elf\bin
C:.espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin
C:.espressif\tools\esp32s2ulp-elf\2.28.51-esp-20191205\esp32s2ulp-elf-binutils\bin
C:.espressif\tools\cmake\3.20.3\bin
C:.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902\openocd-esp32\bin
C:.espressif\tools\ninja\1.10.2
C:.espressif\tools\idf-exe\1.0.2
C:.espressif\tools\ccache\4.3\ccache-4.3-windows-64
C:.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64
C:\esp-idf\tools
Checking if Python packages are up to date...
Python requirements from C:\esp-idf\requirements.txt are satisfied.
Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
idf.py build
C:\esp-idf>pip
Usage:
pip  [options]
Commands:
install                     Install packages.
download                    Download packages.
uninstall                   Uninstall packages.
freeze                      Output installed packages in requirements format.
list                        List installed packages.
show                        Show information about installed packages.
check                       Verify installed packages have compatible dependencies.
config                      Manage local and global configuration.
search                      Search PyPI for packages.
cache                       Inspect and manage pip's wheel cache.
index                       Inspect information available from package indexes.
wheel                       Build wheels from your requirements.
hash                        Compute hashes of package archives.
completion                  A helper command used for command completion.
debug                       Show information useful for debugging.
help                        Show help for commands.
General Options:
-h, --help                  Show help.
--debug                     Let unhandled exceptions propagate outside the main subroutine, instead of logging them
to stderr.
--isolated                  Run pip in an isolated mode, ignoring environment variables and user configuration.
-v, --verbose               Give more output. Option is additive, and can be used up to 3 times.
-V, --version               Show version and exit.
-q, --quiet                 Give less output. Option is additive, and can be used up to 3 times (corresponding to
WARNING, ERROR, and CRITICAL logging levels).
--log                 Path to a verbose appending log.
--no-input                  Disable prompting for input.
--proxy              Specify a proxy in the form [user:passwd@]proxy.server:port.
--retries          Maximum number of retries each connection should attempt (default 5 times).
--timeout              Set the socket timeout (default 15 seconds).
--exists-action     Default action when a path already exists: (s)witch, (i)gnore, (w)ipe, (b)ackup,
(a)bort.
--trusted-host    Mark this host or host:port pair as trusted, even though it does not have valid or any
HTTPS.
--cert                Path to PEM-encoded CA certificate bundle. If provided, overrides the default. See 'SSL
Certificate Verification' in pip documentation for more information.
--client-cert         Path to SSL client certificate, a single file containing the private key and the
certificate in PEM format.
--cache-dir            Store the cache data in .
--no-cache-dir              Disable the cache.
--disable-pip-version-check
Don't periodically check PyPI to determine whether a new version of pip is available for
download. Implied with --no-index.
--no-color                  Suppress colored output.
--no-python-version-warning
Silence deprecation warnings for upcoming unsupported Pythons.
--use-feature      Enable new functionality, that may be backward incompatible.
--use-deprecated   Enable deprecated functionality, that will be removed in the future.
C:\esp-idf>pip install
ERROR: You must give at least one requirement to install (see "pip help install")
C:\esp-idf>pip install idf-component-manager
Requirement already satisfied: idf-component-manager in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (0.3.2b0)
Requirement already satisfied: pyyaml in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (6.0)
Requirement already satisfied: schema in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (0.7.4)
Requirement already satisfied: tqdm in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (4.62.3)
Requirement already satisfied: requests-toolbelt in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (0.9.1)
Requirement already satisfied: six in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (1.16.0)
Requirement already satisfied: requests in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (2.26.0)
Requirement already satisfied: future in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (0.18.2)
Requirement already satisfied: semantic-version>="2.8" in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from idf-component-manager) (2.8.5)
Requirement already satisfied: certifi>=2017.4.17 in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from requests->idf-component-manager) (2021.10.8)
Requirement already satisfied: charset-normalizer~=2.0.0 in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from requests->idf-component-manager) (2.0.7)
Requirement already satisfied: idna<4,>=2.5 in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from requests->idf-component-manager) (3.3)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from requests->idf-component-manager) (1.26.7)
Requirement already satisfied: contextlib2>=0.5.5 in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from schema->idf-component-manager) (21.6.0)
Requirement already satisfied: colorama in c:.espressif\python_env\idf4.4_py3.8_env\lib\site-packages (from tqdm->idf-component-manager) (0.4.4)
C:\esp-idf>%IDF_COMPONENT_MANAGER%
'%IDF_COMPONENT_MANAGER%' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\esp-idf>set | more
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Rangel\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=BALDHEAD
ComSpec=C:\WINDOWS\system32\cmd.exe
DriverData=C:\Windows\System32\Drivers\DriverData
FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer
FPS_BROWSER_USER_PROFILE_STRING=Default
HOMEDRIVE=C:
HOMEPATH=\Users\Rangel
IDF_CCACHE_ENABLE=1
IDF_GIT=C:/.espressif/tools/idf-git/2.30.1/cmd/git.exe
IDF_GIT_DIR=C:.espressif\tools\idf-git\2.30.1\cmd
IDF_PATH=C:\esp-idf
IDF_PYTHON=C:/.espressif/python_env/idf4.4_py3.8_env/Scripts/python.exe
IDF_PYTHON_DIR=C:.espressif\python_env\idf4.4_py3.8_env\Scripts
IDF_PYTHON_ENV_PATH=C:.espressif\python_env\idf4.4_py3.8_env
IDF_TOOLS_PATH=C:.espressif
JAVA_HOME=C:\Program Files\Android\Android Studio\jre
LOCALAPPDATA=C:\Users\Rangel\AppData\Local
LOGONSERVER=\BALDHEAD
MOZ_PLUGIN_PATH=C:\Program Files (x86)\Foxit Software\Foxit Reader\plugins
NUMBER_OF_PROCESSORS=12
OneDrive=D:\OneDrive - UDESC Universidade do Estado de Santa Catarina
OneDriveCommercial=D:\OneDrive - UDESC Universidade do Estado de Santa Catarina
OPENOCD_SCRIPTS=C:.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902\openocd-esp32\share\openocd\scripts
OS=Windows_NT
PARAM=esp-idf-603734d526b91e4aff20573199812fef
Path=C:.espressif\tools\xtensa-esp32-elf\esp-2021r2-8.4.0\xtensa-esp32-elf\bin;C:.espressif\tools\xtensa-esp32s3-elf\esp-2021r2-8.4.0\xtensa-esp32s3-elf\bin;C:.espressif\tools\riscv32-esp-elf\esp-2021r2-8.4.0\riscv32-esp-elf\bin;C:.espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin;C:.espressif\tools\esp32s2ulp-elf\2.28.51-esp-20191205\esp32s2ulp-elf-binutils\bin;C:.espressif\tools\cmake\3.20.3\bin;C:.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902\openocd-esp32\bin;C:.espressif\tools\ninja\1.10.2;C:.espressif\tools\idf-exe\1.0.2;C:.espressif\tools\ccache\4.3\ccache-4.3-windows-64;C:.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64;C:\esp-idf\tools;C:.espressif\python_env\idf4.4_py3.8_env\Scripts;C:.espressif\tools\idf-git\2.30.1\cmd;C:.espressif;C:\Program Files\Microsoft Network Monitor 3;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\WINDOWS\System32\OpenSSH;C:\Windows\System32\OpenSSH;C:\WINDOWS\System32\OpenSSH;C:\Program Files\dotnet;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\PuTTY;C:\Program Files\nodejs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Windows\System32\WindowsPowerShell\v1.0;C:\WINDOWS\system32;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS;C:\Users\Rangel\AppData\Local\Microsoft\WindowsApps;C:\Users\Rangel\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Rangel\AppData\Roaming\npm;C:\Users\Rangel.dotnet\tools;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PREFIX=C:/.espressif/python_env/idf4.4_py3.8_env/Scripts/python.exe C:/esp-idf/
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 158 Stepping 10, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=9e0a
PROG27B48B2C054=1
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
PYTHONNOUSERSITE=True
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\Rangel\AppData\Local\Temp
TEMP_IDF_GIT_PATH="C:\Users\Rangel\AppData\Local\Temp\idf-git-path.txt"
TEMP_IDF_PATH=C:\Users\Rangel\AppData\Local\Temp\idf-path.txt
TEMP_IDF_PYTHON_PATH="C:\Users\Rangel\AppData\Local\Temp\idf-python-path.txt"
TMP=C:\Users\Rangel\AppData\Local\Temp
USERDOMAIN=BALDHEAD
USERDOMAIN_ROAMINGPROFILE=BALDHEAD
USERNAME=Rangel
USERPROFILE=C:\Users\Rangel
windir=C:\WINDOWS
ZES_ENABLE_SYSMAN=1
C:\esp-idf>cd c:\esp32Projects\wss_server_and_ui_integration
c:\esp32Projects\WSS_SERVER_AND_UI_INTEGRATION>idf.py build
Executing action: all (aliases: build)
Running cmake in directory c:\esp32projects\wss_server_and_ui_integration\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=1 c:\esp32projects\wss_server_and_ui_integration"...
-- Found Git: C:/.espressif/tools/idf-git/2.30.1/cmd/git.exe (found version "2.30.1.windows.1")
-- Component directory C:/esp32Projects/WSS_SERVER_AND_UI_INTEGRATION/components/communication does not contain a CMakeLists.txt file. No component will be added
-- Component directory C:/esp32Projects/WSS_SERVER_AND_UI_INTEGRATION/components/ui does not contain a CMakeLists.txt file. No component will be added
-- ccache will be used for faster recompilation
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32
Cannot parse CMake requirements line: __component_set_property(__idf.global_conf REQUIRES "lvgl;cxx;newlib;freertos;esp_hw_support;heap;log;lwip;soc;hal;esp_rom;esp_common;esp_system;esp32")
CMake Error at C:/esp-idf/tools/cmake/component.cmake:238 (message):
Call Stack (most recent call first):
C:/esp-idf/tools/cmake/build.cmake:491 (__component_get_requirements)
C:/esp-idf/tools/cmake/project.cmake:378 (idf_build_process)
CMakeLists.txt:15 (project)
-- Configuring incomplete, errors occurred!
See also "C:/esp32Projects/WSS_SERVER_AND_UI_INTEGRATION/build/CMakeFiles/CMakeOutput.log".
cmake failed with exit code 1
c:\esp32Projects\WSS_SERVER_AND_UI_INTEGRATION>
[/code]

If you are using the terminal itself, after updating idd-component-manager, delete your project's build folder and try again. Check if there is an environment variable IDF_COMPONENT_MANAGER enabled in your terminal. Delete it, delete the build folder and try to build again.

This not solve.

@baldhead69 Have you tried to delete the build folder as @brianignacio5 suggested above?

@baldhead69 Have you tried to delete the build folder as @brianignacio5 suggested above?

Yes.
In all attempts.

@baldhead69 do you happen to have a component directory named .global_conf inside your project? If yes, what is the contents of that directory? It looks like idf-component-manager considers it to be a component and fails because of the . symbol in the directory name.

in esp-idf version "v4.4-dev-2359-g58022f859" the program compiled ok.
And anothers versions compiled ok too.

I understand that, it's entirely possible that the same project worked before. — the error is related to the component manager, which is a new feature recently enabled in the master branch. I'm asking about that directory to try to identify the root cause of the issue. Once we know the cause, we can fix it.or give you a workaround so that you can move on with your project.

The ".global_conf" is only a folder that i put lvgl component configurations like lv_conf.h, lv_conf_checker.h, lv_version.h and lvgl.h and a CMakeLists.txt file.
CMakeLists.txt file:
idf_component_register( INCLUDE_DIRS .
REQUIRES lvgl
)

@igrr
I took the dot from the folder and the respective CMakeLists.txt files that referenced this folder and worked.
Will espressif guys try to fix this ?
Thank you very much.
Example:
CMakeLists.txt
file(GLOB littlevgl_srcs 	src/lv_core/*.c
							src/lv_draw/*.c
							src/lv_font/*.c
							src/lv_hal/*.c
							src/lv_misc/*.c
							src/lv_objx/*.c
							src/lv_themes/*.c
	)

idf_component_register(	SRCS ${littlevgl_srcs}
						INCLUDE_DIRS 	src/lv_core/include
										src/lv_draw/include
										src/lv_font/include
										src/lv_hal/include
										src/lv_misc/include
										src/lv_objx/include
										src/lv_themes/include

						REQUIRES global_conf
						#REQUIRES fatfs sdmmc
					  )

Taking the opportunity to talk to you, what is the difference between these two files ?
I noticed that both esp32 and esp32-s3 have these 2 files.
xtensa-esp32-elf-gcc.exe
xtensa-esp32-elf-gcc-8.4.0.exe

Hi,
Now i installed "ESP-IDF VS Code Extension" and all is working.
Nice work guys.
Thank's all.

Thanks for reporting and sharing the updates, good to hear all is working now, feel free to reopen.

Taking the opportunity to talk to you, what is the difference between these two files ?
I noticed that both esp32 and esp32-s3 have these 2 files.
xtensa-esp32-elf-gcc.exe
xtensa-esp32-elf-gcc-8.4.0.exe

I only would like to know this because i use this configuration for configure intellisense on visual studio code.

A strange thing happened.
I started a installation from scratch on another computer and the dot folder problem go away.
Did you guys update anything already ?

Did you guys update anything already?

No, support for . in component names is not published yet,
but if the component manager is disabled, it shouldn't be a problem. Or, for example the issue won't appear if some CMake-based IDE is used, like Jetbrains CLion

@baldhead69  Just a quick question, did you ever have your project compiled successfully with .global_conf component (started with the leading dot)? Components with leading dots in the name were always ignored in the IDF: https://github.com/espressif/esp-idf/blob/master/tools/cmake/component.cmake#L112

@kumekay
yes, always compiled with esp32(i believe that the chip does not influence).
"Root" CMakeLists.txt
# The following lines of boilerplate have to be in your project's CMakeLists
# in this exact order for cmake to work correctly
cmake_minimum_required(VERSION 3.5)

# (Not part of the boilerplate)
set(EXTRA_COMPONENT_DIRS "${CMAKE_SOURCE_DIR}/components/ui" "${CMAKE_SOURCE_DIR}/components/ui/global_conf" "${CMAKE_SOURCE_DIR}/components/communication")   # add components "drv" "lvgl" and ".global_conf". ".global_conf" only *.h global files.
#  ${CMAKE_SOURCE_DIR} -> project root folder.

include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(wss_server)

The .global_conf folder was inside the ui folder

Thank you for the quick reply, I thought you had components/.global_conf and wondered why it ever worked.
At the same time, the CMake error in the component manager you mentioned is fixed now and will be included in the next release of it.  But the support of components with leading dots like  components/.global_conf won't be enabled in IDF (at the same time  components/ui/.global_conf should be fine)


Write more rewrite rules

Rewrite rules are useful to avoid intermediate allocations and perform more operations in a single BLAS call.
We can support at least a few standard forms, and now there is a way to test they are actualy applied.
Some functions used in rewrite rules may also be exposed in case some advanced user wants to use them directly

If this makes the neo/dense module too big, we could think of moving these advanced functions and rewrites in a separate module


Inline image does not accept resizeMode as well as positioning

My app implements Chat functionality with emoticons support. Images are intended to be drawn as child elements of the Text containers. However I can not apply any positioning to Image (to align images vertically) as well as resizeMode - they are skipped for images with parent element of Text
<Text>
     <Text>This is message with emoticon at the end</Text>
     <Image resizeMode='contain' style={{resizeMode: 'contain', top: ... }} src=.../>
</Text>

Seems it only accepts width and height attributes
Probably there are some workarounds. I tried to use View parent element with flexDirection: row and flexWrap: wrap, but it does not wrap long text messages. Seems the only possible solution for Chat messages is to put everything into Text parent only
Any help is appreciated, thanks

React Native version: 0.37
Platform: Android
Operating System: MacOS

Can you provide a minimal amount of code to reproduce this on rnplay.org? This is necessary for people to be able to see and debug the issue being reported.
Closing this issue as it is not actionable. Please open a new one with an rnplay link (preferred), or link to a GitHub repo with clear instructions how to repro.

This might indeed not be supported.

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.


ntco_ioring.t TC1 constantly fails

Describe the bug
Completion queue is overflowed during TC1 and thus assertion happens. See attached logs
ntco_ioring.t_assertion.txt
To Reproduce
Steps to reproduce the behavior:

build ntco_iuring.t
execute TC1
See assertion

[ F ][ 06SEP2023_05:34:09.243 ][             main ][                   ntco_ioring.t.cpp:1365 ]: Assertion failed: result[i] == id
Found:    21 (result[i])
Expected: 8 (id)

Environment (please complete the following information):
/bloomberg/ntf-core$ uname -a
Linux CN-HP02 <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Additional context
According to my understanding that happens because submission queue has capacity of 4 entries, completion queue has capacity of 8 entries, but this code:
        for (bsl::size_t id = 0; id < k_SUBMISSION_COUNT; ++id) {
            NTCO_IORING_TEST_LOG_PUSH_STARTING(test, id);
            test->defer(id);
            NTCO_IORING_TEST_LOG_PUSH_COMPLETE(test, id);
        }

tries to push 24 entries into the system. No way that can be handled.

https://github.com/bloomberg/ntf-core/pull/197 contains the fix


anonymous.test.example.org - see bug description

URL: http://anonymous.test.example.org/
Browser / Version: Firefox 74.0
Operating System: Mac OS X 10.15
Tested Another Browser: Unknown
Problem type: Something else
Description: elephant images
Steps to Reproduce:
View the screenshot[![Screenshot Description](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)

Browser Configuration

None

From webcompat.com with ❤

View the screenshot[![Screenshot Description](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)

View the screenshot
[![Screenshot Description](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)](http://localhost:5000/uploads/2020/1/93dc9a96-5ce0-4e1b-92c6-de06a959b866.jpeg)

View the screenshot


[digital twins] Move @azure/digital-twins-core to ESM/vitest

Packages impacted by this PR

@azure/digital-twins-core

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Moves @azure/digital-twins-core to ESM/vitest via automation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Errors in data_collector.py

Hello there,
I run into some unexpected behaviour (a bug, maybe. Not sure) when dealing with the update of vehicle calibration (please refer to this guide ). To be concise:

In file  the variable self.in_session appears to be not initialized. The error displays:

File "modules/tools/calibration/data_collector.py", line 132, in callback_canbus
if self.in_session:
AttributeError: 'DataCollector' object has no attribute 'in_session'
2)Still in the same file, the variable I had the following error:
File "modules/tools/calibration/data_collector.py", line 147, in publish_control
if self.case == 'a':
AttributeError: 'DataCollector' object has no attribute 'case'
I solved by adding the following piece of code at line 147:
        if self.vehicle_speed >= self.cmd[1]:
           self.case = 'd'
        else:
           self.case = 'a'

Did I miss something before running the script or are my considerations worthy?

Hi, Could you please add try...(related exception) in this case as well, then submit a patch to fix that?

Hi @Leonardo092 ! I have same issue. I fix it by adding
        self.case = 'a'
        self.in_session = False
into data_collector.py in method:
class DataCollector(object):
    def __init__(self):

Also there is one issue in sending deceleration command. I fix it with:
        if self.case == 'a':
            if self.cmd[0] > 0:
                self.controlcmd.throttle = self.cmd[0]
                self.controlcmd.brake = 0
            else:
                self.controlcmd.throttle = 0
                self.controlcmd.brake = -self.cmd[0]
            if self.vehicle_speed >= self.cmd[1]:
                self.case = 'd'
        if self.case == 'd':
            if self.cmd[2] > 0:
                self.controlcmd.throttle = self.cmd[2]
                self.controlcmd.brake = 0
            else:
                self.controlcmd.throttle = 0
                self.controlcmd.brake = -self.cmd[2]
            if self.vehicle_speed == 0:
                self.in_session = False
into data_collector.py in method:
class DataCollector(object):
def publish_control(self):

I gone through the file, looks your solution is good.  Also, this file could be refactored by isoldate usage into a method, a few code is written without following the pythonic style.

Thanks @gladijos! My solution works as well but I will try yours in addition(especially that regarding deceleration).

you shall use try..catch to check is there any exception raised in DataCollector construct.if DataCollector init successfully   shall not get these error print. ——Reply reference comes from the Apollo developer community issue master contest https://apollo.auto/developer/questiondata_cn.html?target=631


Warrior Static IP Network

Hi,
I have been looking on how to fix the network interface IP. But the modifications doesn't stick. I have looked at this #225 should I overwrite the bbappend systemd-conf_%.bbappend. Also my second port eth1 is in IPV6 surprisingly so the wired.network in the meta-tegra seems not to apply to the second interface.
What is the right way to configure the network on the warrior branch
eth0.network
[Match]
Name=eth0

[Network]
DNS=<IP_ADDRESS>
Address=<IP_ADDRESS>
Gateway=<IP_ADDRESS>

eth1.network
[Match]
Name=eth1

[Network]
DNS=<IP_ADDRESS>
Address=<IP_ADDRESS>
Gateway=<IP_ADDRESS>

and the recipe : systemd_%.bbappend
PACKAGECONFIG_append = " networkd resolved"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI += " \
    file://eth0.network \
    file://eth1.network \
"
FILES_${PN} += " \
    ${sysconfdir}/systemd/network/eth0.network \
    ${sysconfdir}/systemd/network/eth1.network \
"
do_install_append() {
  if ${@bb.utils.contains('PACKAGECONFIG','networkd','true','false',d)}; then
        install -d ${D}${sysconfdir}/systemd/network
        install -m 0755 ${WORKDIR}/eth0.network ${D}${sysconfdir}/systemd/network
        install -m 0755 ${WORKDIR}/eth1.network ${D}${sysconfdir}/systemd/network
  fi
}

The [Match] section in your eth1.network file doesn't look right.  Don't you want Name=eth1 there?

@madisongh Sorry It was a typo error.
When I do this :
 ifconfig eth1 <IP_ADDRESS> netmask <IP_ADDRESS> up
The interface changes.

It could be that the warrior build is using init-ifupdown to manage the network links, in which case you'll need to provide a modified copy of /etc/network/interfaces  to configure the interfaces with their static IPs.  Either that, or modify the build to remove init-ifupdown so systemd-networkd takes control of configuring the interfaces (although that might require some other changes, I'm not 100% positive that will work).

Thank you for your feedback. I will try that after I have fixed the BSP for the ethernet ports.
Keep you posted/

It seems that it's actually systemd-networkd that is handling networking.
The file /etc/network/interfaces doesn't exist. I created it but it doesn't set the IP
When I restart networking I get this :
Feb 20 18:04:55 j140-tx2 systemd-networkd[5049]: eth1: Gained IPv6LL
Feb 20 18:04:55 j140-tx2 systemd-networkd[5049]: enp2s0: Gained IPv6LL
Feb 20 18:04:55 j140-tx2 systemd-networkd[5049]: Enumeration completed
Feb 20 18:04:55 j140-tx2 systemd[1]: Started Network Service.
Feb 20 18:04:55 j140-tx2 systemd-networkd[5049]: eth1: DHCPv4 address <IP_ADDRESS>/24 via <IP_ADDRESS>
Feb 20 18:05:07 j140-tx2 systemd-networkd[5049]: eth1: Configured
Feb 20 18:07:02 j140-tx2 systemd[1]: Stopping Network Service...
Feb 20 18:07:02 j140-tx2 systemd[1]: systemd-networkd.service: Succeeded.
Feb 20 18:07:02 j140-tx2 systemd[1]: Stopped Network Service.
Feb 20 18:07:02 j140-tx2 systemd[1]: Starting Network Service...
Feb 20 18:07:02 j140-tx2 systemd-networkd[5134]: eth1: Gained IPv6LL
Feb 20 18:07:02 j140-tx2 systemd-networkd[5134]: enp2s0: Gained IPv6LL
Feb 20 18:07:02 j140-tx2 systemd-networkd[5134]: Enumeration completed
Feb 20 18:07:02 j140-tx2 systemd-networkd[5134]: eth1: DHCPv4 address <IP_ADDRESS>/24 via <IP_ADDRESS>
Feb 20 18:07:02 j140-tx2 systemd[1]: Started Network Service.

And before I fixed the file :
-- Logs begin at Thu 2020-02-20 17:55:06 UTC, end at Thu 2020-02-20 18:05:25 UTC. --
Feb 20 17:55:06 j140-tx2 systemd[1]: Starting Network Service...
Feb 20 17:55:06 j140-tx2 systemd-networkd[3165]: [[0;1;31m[[0;1;39m[[0;1;31m/etc/systemd/network/enp2s0.network:4: An address '<IP_ADDRESS>' is specified without prefix length. The behavior of parsing addr
esses without prefix length will be changed in the future release. Please specify prefix length explicitly.[[0m
Feb 20 17:55:06 j140-tx2 systemd-networkd[3165]: Enumeration completed
Feb 20 17:55:06 j140-tx2 systemd[1]: Started Network Service.
Feb 20 17:55:06 j140-tx2 systemd-networkd[3165]: eth0: Interface name change detected, eth0 has been renamed to enp2s0.
-- Logs begin at Thu 2020-02-20 17:55:06 UTC, end at Thu 2020-02-20 18:07:03 UTC. --
Feb 20 17:55:06 j140-tx2 systemd[1]: Starting Network Service...
Feb 20 17:55:06 j140-tx2 systemd-networkd[3165]: [[0;1;31m[[0;1;39m[[0;1;31m/etc/systemd/network/enp2s0.network:4: An address '<IP_ADDRESS>' is specified without prefix length. The behavior of parsing addr
esses without prefix length will be changed in the future release. Please specify prefix length explicitly.[[0m
Feb 20 17:55:06 j140-tx2 systemd-networkd[3165]: Enumeration completed

So it seems it's reading it properly. But it doesn't apply it.

I have tested it on the standard Jetpack on a Xavier. To be able to make the .network file work I had to do this.
sudo systemctl stop NetworkManager.service
sudo systemctl stop NetworkManager-wait-online.service
sudo systemctl stop NetworkManager-dispatcher.service
sudo systemctl stop network-manager.service

But these services don't exist in the image.

Yes, thankfully NetworkManager is not used by default here.  Try naming your .network files such that they will be processed earlier than 80-wired.network (which enables DHCP).  Per the systemd documentation, whichever .network file matches first wins, and a numerically prefixed file name will precede an alphabetic filename lexicographically.

Thank you very much that was the solution.


status-subscription - Make selected status more visible

Description
The selected background is not that much visible in dark mode.
before:

after:

Example URLs
https://github.com/refined-github/refined-github/pull/7798

You’re absolutely right, their “selected” style isn’t visible in dark mode, it looks decent in light mode though. My concern with making it that bright is that it might capture too much attention, plus it’s not a standard style.
I’m thinking of two alternatives:

add some color (custom CSS) just in dark mode, like some sort of glow maybe
look for similar widgets on GitHub or primer.style
use the “preview | code | blame” style found on files, which is basically the same component but styled more recently. I think we should go with this, but it might be a React-only component/style

How about this?

Is it a custom style or just an existing class? If the “preview code blame” style can be reused here I’d prefer it

We can try your custom style. We just need to make sure it works as expected on high-contrast themes too

If you still have the style I'd love to get that into the next version


dbip-country-lite: 2023-08 -> 2023-09

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252746 run on x86_64-linux 1

1 package failed to build:

qv2ray

7 packages built:

dae
dbip-country-lite
sing-geoip
v2ray
v2ray-geoip
v2raya
xray


Broken HMR in sidebar menu

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

bug report

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
When editing MenuAccordion component, the HMR is not working. An error is encountered, hence the HMR is stopped.

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue
Start the local service with 'npm run dev'
Edit src/components/sidebar/menu/MenuAccordion.vue
HMR doesn't work, because of an error.
TypeError: Cannot read properties of null (reading '_vei')

What is the expected behavior?
HMR should work.

What is the motivation / use case for changing the behavior?
Fix this issue. Because for every change in the MenuAccordion (and eventually component files "around"), the HMR is not working. So the developer needs to manually trigger the refresh of the page, and this makes a cold refresh.

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

This may be a bug in the underlying VuesticUI.
runtime-core.esm-bundler.js:571 TypeError: Cannot read properties of null (reading '_vei')

Hi, @antonio-fr. I have no quick solution for it... This might be more related to vue and requires deep dive. Would be nice to separate reproduction from Vuestic Admin and make issue in vue repo.

My current understanding of this issue is that this is not related to Vue, but to Vuestic or VuesticAdmin. One solution could be to replace va-dropdown by va-accordion in MenuAccordion.

My current understanding of this issue is that this is not related to Vue, but to Vuestic or VuesticAdmin. One solution could be to replace va-dropdown by va-accordion in MenuAccordion.

Try to update vue to latest ^3.3.4 it fixes the issue for me.


question: Why can't I pass u64 to write()?

Question
Is there any particular reason write() doesn't allow the passing of u64?

This support is on main now and will be in the next release.


Send a duplicate of the invoice to the customer

Allow the admin to send a duplicate email with the customers invoice

Hi @ghermans,
I have started working on this.


Content Suggestion: #NotiSatoshi (a Bitcoin-Only news recap in spanish)

Link to Content: https://www.youtube.com/watch?v=ZqGJdIfrJGc&list=PLZsflIub4SmESRXVrl1AkXUcu96ahF5c1
Briefly Describe Content: #NotiSatoshi is a Bitcoin only weekly recap of the main news in Bitcoin.
Suggested Section: Podcasts

Messaged @satoshienvzla on twitter who's name is shown in the video.

Pretty sure @satoshienvzla is @criptobastardo

Yes, i'm @satoshienvzla @ Twitter too.
I do use both accounts untill we grow big enough to have Community Managers
lol
Cheers!
Thanks for the adding, pals! REALLY appreciated
J-
El mié., 16 de sept. de 2020 16:44, pardus79<EMAIL_ADDRESS>escribió:

Pretty sure @satoshienvzla is @criptobastardo
https://github.com/criptobastardo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-only/bitcoin-only/issues/265#issuecomment-693655100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQROOKEB22EVRI24NBQZ5QLSGEPUBANCNFSM4PYXIY4Q
.

Ready to be turned into a Pull Request.

Was about to add this, but noticed that this show is on the same youtube channel as https://www.youtube.com/c/SatoshienVenezuela/ which is already listed.
Should this replace the existing listing?

Added


src/greenpak/i2c.py: Fix SMBus adapter write.

Fixes write by splitting - same as read was doing.  Tested.
Could we merge this before I update https://github.com/zapta/greenpak/pull/5  per your latest comments.
@zapta

Thanks. Done.
On Thu, Feb 29, 2024 at 7:54 PM dry-75 @.***> wrote:

Fixes write by splitting - same as read was doing. Tested.
Could we merge this before I update #5
https://github.com/zapta/greenpak/pull/5 per your latest comments.
@zapta https://github.com/zapta
You can view, comment on, or merge this pull request online at:
https://github.com/zapta/greenpak/pull/8
Commit Summary

a1bc781
https://github.com/zapta/greenpak/pull/8/commits/a1bc7815e79e7e12a12f5c4295441862b6381fcb
src/greenpak/i2c.py: Fix SMBus adapter write.

File Changes
(2 files https://github.com/zapta/greenpak/pull/8/files)

M src/greenpak/i2c.py
https://github.com/zapta/greenpak/pull/8/files#diff-b24ede450ac267736fd7a727b4f04653267c5333f045b5117de8a97cc993ac05
(10)
M test/smb_test.py
https://github.com/zapta/greenpak/pull/8/files#diff-7cffd867a5f1fa751838b33e1372c7f405ccd46e94a769c5187ff547dbe99fa0
(3)

Patch Links:

https://github.com/zapta/greenpak/pull/8.patch
https://github.com/zapta/greenpak/pull/8.diff

—
Reply to this email directly, view it on GitHub
https://github.com/zapta/greenpak/pull/8, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQVMQJTBX2ZJJ7D5FQGDSDYV73XLAVCNFSM6AAAAABEBCQNXSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DENJVGE4TMOA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Generate addresses from safe-deployments.py

What is needed?
addresses.py include the addresses of Safe singleton contracts (L1, L2, ProxyFactory) and the block number when the contract was deployed to start the indexing process from that block.
Search the block for every address is a cumbersome task, I would like to include a generator to get the block from blockexplorer (etherscan and blockscout) automatically for the new addresses added on safe-deployments.

We don't see this feasible for new networks, as most lack blockexplorer or they use a non standard API


I would say 0 shared datasets or 0 shared maps in the groups index

If there is any of both, just '1 shared dataset' or '1 shared map'.
And if there isn't any, 'No maps or datasets shared'

@saleiva

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Documentation incorrect

 	sync
		Synchronize database. Stores countries' data in ~/.cache/countryfetch/countries.json.
		Pass additional argument 'sync flag' to fetch and convert flags in ASCII art.
		After syncing flags, every countryfetch command will display flag ASCII art.

Should be sync flags not sync flag

fixed in #14, thanks!


Bootstrap v4.0.0-alpha.6

Bootstrap 4.0.0-alpha.6 appears to have broken the feature/v3 branch. Take a look at the output of npm start:
[1] ./~/css-loader/lib/css-base.js 1.51 kB {0} [built]
Child extract-text-webpack-plugin:

    ERROR in ./~/css-loader?limit=32768?name=images/[name].[ext]!./~/postcss-loader!./~/sass-loader?sourceMap!./docs/scss/docs.scss
    Module build failed:
    $availity-zindex-secondary-fixed: ($zindex-navbar-fixed - 10) !default;
                                      ^
          Undefined variable: "$zindex-navbar-fixed".
          in /Users/sgillespie/dev/availity-uikit/scss/_variables.scss (line 522, column 36)
Child extract-text-webpack-plugin:

    ERROR in ./~/css-loader?limit=32768?name=images/[name].[ext]!./~/postcss-loader!./~/sass-loader?sourceMap!./scss/_bootstrap.scss
    Module build failed:
    $availity-zindex-secondary-fixed: ($zindex-navbar-fixed - 10) !default;
                                      ^
          Undefined variable: "$zindex-navbar-fixed".
          in /Users/sgillespie/dev/availity-uikit/scss/_variables.scss (line 522, column 36)

Even if we fix the issue above, awesome-bootstrap-checkbox probably also needs to be updated:
    ERROR in ./~/css-loader?limit=32768?name=images/[name].[ext]!./~/postcss-loader!./~/sass-loader?sourceMap!./scss/_bootstrap.scss
    Module build failed:

                  ^
          No mixin named tab-focus

    Backtrace:
        node_modules/awesome-bootstrap-checkbox/awesome-bootstrap-checkbox.scss:205
          in /Users/sgillespie/dev/availity-uikit/node_modules/awesome-bootstrap-checkbox/awesome-bootstrap-checkbox.scss (line 205, column 16)

https://github.com/flatlogic/awesome-bootstrap-checkbox/issues/111

i've been working on this when I get time since the release of beta 6. I'm mostly done, but need to fix some of the examples (mainly the navbars since they have completely changed). I should have something up soon.

Just added [39bc05b]. This was a major change since flexbox in now the only display that is supported. This pretty much breaks all of the custom components and additions that were added by availity as they do not work well with the flexbox model. When v4 is fully released we should probably redo this from scratch.

+1. waiting for the fix, subscribing until then.

3.0.0-beta.4 was published on npm (and github) with the changes for support of alpha 6. Report any issues in a new ticket and I'll resolve them in a timely manner.


Unit Tests For Point.MarshalBinary() and Point.UnmarshalBinary().

I added some unit tests for Point.MarshalBinary() and Point.UnmarshalBinary(). This actually increase the test coverage of point.go from 70.3% to 91.9%. Hope it helps.

@ihcsim Thanks for the PR!  And apologies on the delay in response; it's been rather busy for me lately!
:+1: Looking good to me!  Merging now :)


Vulkan: VkQueryPool being used with VkCommandBuffer of other queueFamilyIndexs

Description of Bug
VulkanReplay::FetchCountersKHR() creates a VkQueryPool for queueFamilyIndex == 0 but later it is used in VkCommandBuffer of different queue families not respecting Vulkan specification and causing issues in Intel GPUs with support for multiple queues(Lunar Lake and newer).
I can workaround it by using a environment variable(ANV_QUEUE_OVERRIDE=gc=1,g=0,c=0,v=0,b=0) that disables all queues but the main one(that supports VK_QUEUE_GRAPHICS_BIT | VK_QUEUE_COMPUTE_BIT | VK_QUEUE_TRANSFER_BIT) but would be nice to have renderdoc to following specification.
Steps to reproduce

renderdoccmd capture ... <application being analyze>
qrenderdoc <file captured above>
Performance Counter Viewer tab > Capture counters > Vulkan Extended > Sample counters
VK Device is lost

Again this is only reproduced in GPUs that supports multiple queues, for Intel on Linux that would be Lunar Lake(Ultra series 2) and Battlemage(Arc B). I can definitely help with testing.
Environment

RenderDoc version: v1.x branch from today / commit 4ac6b7765c87c5f653f69161d33a85f5a74dc765
Operating System: Linux
Graphics API: Vulkan
HW: Intel Lunar Lake(Ultra series 2)

I'll look into this but at this stage it won't be until the new year. The KHR counter queries were originally contributed by @djdeath so possibly he can look into it sooner? Looking at the original PR #1600 this was mentioned as a known issue but not addressed at the time.
Also note you should never use renderdoccmd. This is an undocumented internal tool only and not for users. You should launch your program for capture from the RenderDoc UI rather than doing that as an unnecessary extra step.

Running out of time too for this year :(
I can look into it after, shouldn't be hard to avoid emitting the queries in the not supported command buffers.


Remove support for v0.3

This subsumes #146, and further removes all uses of @compat.
Closes #145
Will merge tonight or tomorrow (PST) if there are no comments.

Just make sure to bump the minor package version for the first tag after merging this.

:+1:


[Feature]: Track the originator of http request

Feature description
Is there any way to let me know that a certain or several http traffic is triggered by clicking on which element in the page?
I want to know the element that initiates these http traffic

See https://pptr.dev/api/puppeteer.httprequest.initiator/ which returns the information about the initiator of the request. Note that elements are not initiators of requests so it is not possible to associate a request with a DOM element. Also, see https://github.com/puppeteer/puppeteer/issues/12331


Squash docker image layers

What does this PR do?
Squash Datadog agent docker image layers.
Motivation
As each Datadog agent release is based on the latest Debian base image, which is updated more often than Datadog agent releases, the docker images of two consecutive Datadog agent release are sharing no common layer.
So, the layering of the Datadog agent docker images is providing no gain.
Additional Notes
I would have preferred to use docker build --squash=true … rather than a 3rd party tool but the docker daemon of the GitLab CI doesn’t have experimental features enabled.
Describe your test plan
Check that the Datadog docker images is mono-layer with docker history.

docker build --squash doesn’t work because it requires to enable the experimental features on the daemon side.
docker buildx build --squash doesn’t work because it is not implemented.
docker export | docker import doesn’t work because it looses all the metadata like CMD, ENV, VOLUMES, etc. It keeps only the filesystem content.


Method sendPromise (EIP1559)

let mergedOptions = self.transactionOptions.merge(transactionOptions)
var cleanedOptions = TransactionOptions()
cleanedOptions.from = mergedOptions.from
cleanedOptions.to = mergedOptions.to
return self.web3.eth.sendTransactionPromise(transaction, transactionOptions: cleanedOptions, password: password)
The TransactionOptions is missing when sending it by applying eip1559.
Is there any other way?

let mergedOptions = self.transactionOptions.merge(transactionOptions) var cleanedOptions = TransactionOptions() cleanedOptions.from = mergedOptions.from cleanedOptions.to = mergedOptions.to
return self.web3.eth.sendTransactionPromise(transaction, transactionOptions: cleanedOptions, password: password)
The TransactionOptions is missing when sending it by applying eip1559.
Is there any other way?


⚠ Bofrost.fr has degraded performance

In 6c34589, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1519 ms

Resolved: Bofrost.fr performance has improved in 68de5bc after 6 minutes.


Add option to throw exceptions on errors

I'm using OpenCPU to incorporate R code into an existing application, and it needs to be able to handle OpenCPU errors internally instead of having them generate alerts or log to the console. For instance, when seturl() fails, it uses alert() to raise a dialog box. And as the connection is made, messages are logged with console.log().
When getting started, and in pages, the way opencpu.js uses alert() and console.log() is very helpful, so I still think that should be the default behavior.  Would it be appropriate to create a flags on the ocpu object that tells it whether to use alert() or throw exceptions, and  whether to log debug messages?
If this would be acceptable, I can submit a pull request.

I've submitted a pull request for this issue https://github.com/jeroenooms/opencpu.js/pull/7


do not blow up when using kwargs for .open

ArgumentError: wrong number of arguments (given 3, expected 0..2)
    vendor/bundle/ruby/3.1.0/gems/dogstatsd-ruby-5.3.2/lib/datadog/statsd.rb:78:in `initialize'

I updated the test here, in a way that fails for 3.x with newer versions, if the fix is reverted.

that's all my PR's for now, can you release the gem ?

I'll put it on my list :)


Add C implementation for @stdlib/math/base/special/log1pexp

Resolves #760.
Checklist

[x] update readme.md
[x] include.gypi
[x] binding.gyp
[x] include/stdlib/math/base/special/
[x] src
[x] manifest.json
[x] lib
[x] examples
[x] benchmark
[x] test

@kgryte

All tests and benchmarks cleared, this PR can have a review.

Apologies for messing up with the headers, and braces convention, will try not to repeat those.


Aave-v2 Subgraph

Initial Aave subgraph pull request. This includes the schema, .yaml, ABIs, and mapping scripts. Work in progress...

@MichaelC1999 would you be able to resolve the merge conflicts? Should be the last thing before merging it in


Replace valloc() with memalign() to support e.g. Android arm64

valloc() no longer exists in some toolchains like Android arm64 (see here), but using memalign(getpagesize(), len) should be identical.
Caveat: I haven’t been able to verify whether support for memalign() and getpagesize() is universal.

Looks like this will need some more work. I found that memalign() is not available e.g. on macOS using the Xcode toolchain, so using posix_memalign() is probably the better choice.

memalign is a glibcism, but posix_memalign works pretty much everywhere (except Windows, but we're already special-casing Windows here).  Happy to merge a PR that uses posix_memalign.

Thanks. I’ve updated the patch to use posix_memalign with getpagesize(). I think that should be the equivalent of valloc?
I ended up inlining the VirtualAlloc call on Windows, let me know if you prefer doing it another way.


Switch purview test endpoint

Description

Resolves #XXX
How was this PR tested?
Need to be marked as "safe to test", then monitor the test result
Does this PR introduce any user-facing changes?

[ ] No. You can skip the rest of this section.

Should we do both instead of just purview?

@blrchen is refactoring the test case right now.


[iOS] Replacing centerView causes flicker

I use the leftView as a menu and when the user clicks any of the tableRows the centerView is replaced with a new navController on iOS 7.
The problem is that when the switch happens there's a brief moment of there not being a view there, and therefor it doesn't have any background, so it just shows through like this:

This causes an undesired flickery effect. I've tried setting backgroundColor white on both the navController and it's window and Ti.UI.backgroundColor = 'white';, with no luck.

https://jira.appcelerator.org/browse/TIMOB-17485 seems resolved. This issue too?

Yes. At least it never occurred to me again.

Still flickering with 4.1.0.GA. Any workaround?

I ended just setting empty windows on init. Then I add remove my views directly from the window references (removeAllChildren, add). Forced me to create my own nav but works much better.

Thanks @chrisribe I will try that. But would be nice if there is a easier way to fix this within this module.


REPL: Add support for all 6to5 options

It'd be nice to have a dropdown or something that allowed you to toggle all the options for 6to5. It'd be even nicer if it was auto generated from the latest 6to5.

It would help to quickly diagnose issues like this: https://github.com/6to5/6to5/issues/580

Dynamically understanding the current option set will be tricky.  The following options (from 6to5/lib/6to5/file.js may not necessarily be relevant to the REPL.  Unless the core exposes the kinds of options the REPL is interested in via an isolated list, it may not be practical to do this in an automated way.

filename
filenameRelative
modules
sourceMap
sourceMapName
sourceFileName
sourceRoot
moduleRoot
moduleIds
comments
keepModuleIdExtensions
code
ast
format


⚠ Bofrost.es has degraded performance

In bdd3363, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1463 ms

Resolved: Bofrost.es performance has improved in a3de9e7 after 6 minutes.


Fix blocking call error when retrieving sub profiles

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

15 of 15 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.975%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4021

Relevant Lines:
4022

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

15 of 15 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.975%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4021

Relevant Lines:
4022

💛  - Coveralls


OLS-136: data to ingress

Description
Script that collects data, packages it, and sends it to ingress.
TODO:

[x] - code needed from https://github.com/openshift/lightspeed-service/pull/673
[x] - CI secret https://github.com/openshift/release/pull/50723

@tisnik @bparees
I've pushed some changes. This version seems to be working. It sends the tarball to ingress. Some bits are still missing.
But I need some help with testing. I've added there a docker compose file, that does the e2e testing.
You can try that with
docker-compose -f ols/user_data_collection/docker-compose.yaml up --build

and then
curl -X POST -H "Content-Type: application/json" -d '{"conversation_id": "1", "user_question": "a", "llm_response": "b", "sentiment": 1}' http://<IP_ADDRESS>:8080/v1/feedback

that results in
user_data_collection-data_collector-1  | INFO:__main__:collected data from '/app-root/data'- '1' files
user_data_collection-data_collector-1  | INFO:__main__:sending collected data
user_data_collection-fake-ingress-1    | INFO:root:recieved something
user_data_collection-fake-ingress-1    | INFO:root:feedback/ae0455db-e3c6-48c6-a2d8-9c90d96a852a.json
user_data_collection-fake-ingress-1    | INFO:root:openshift_lightspeed.json
user_data_collection-fake-ingress-1    | INFO:     <IP_ADDRESS>:42562 - "POST /test_endpoint HTTP/1.1" 202 Accepted
user_data_collection-data_collector-1  | INFO:__main__:data uploaded with request_id: 'some-request-id'
user_data_collection-data_collector-1  | DEBUG:__main__:removing '/app-root/data/feedback/ae0455db-e3c6-48c6-a2d8-9c90d96a852a.json'
user_data_collection-data_collector-1  | INFO:__main__:uploaded data removed
user_data_collection-data_collector-1  | INFO:__main__:'/app-root/data' contains no data, nothing to do...

I don't have a good idea of how to translate it to our e2e suite, so any ideas are welcome. :)

/retest

I've reverted from config to the env var for the OLS_USER_DATA_PATH. Bringing config in just complicates it. Mounting unnecessary volumes, updating sys path, ...

/retest

@bparees Review comments addressed. I hope I didn't miss anything.

/retest
sorry i didn't get to this one today, i promise it'll be first in my queue tomorrow

/lgtm
/approve
please address the error handling gaps in a follow up.

please address the error handling gaps in a follow up.

and please don't close OLS-136 until they're addressed


Add labels to the legend

I do not know if this is really a missing feature, I just could not understand how to do it.
I am creating some markers (with labels) on a MapPlot, adding stars and other object populations, then I call p.legend() and I only see e.g. "Star", "Open cluaster" etc... but I do not see my custom objects.
That function does not seem to return anything and I don't think I should have to meddle with matplotlib low-level API to interface with the legend (if it's even possible to interface with MapPlot artists)

Ah! the legend_label keyword is what I should use. My bad it was explained in the docs...

no worries! perhaps the legend_label shouldn't default to None like it does currently -- my thinking there was it's probably more likely that people would plot multiple markers with custom labels but would want them all labelled in the legend the same way.


cloneNode doesn't clone changed attribute

Hello Polymer team !
Please take a look at this codepen :
http://codepen.io/anon/pen/LEpBeE
Change the input value, see in the console that element's command attribute is changed.
Click clone : the cloned element's command attribute stay as if it was unchanged.
Why such behavior ?
Thank you !

+1

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Resolve input and output execution states explicitly

The PR makes resolving a task's output and input states before execution explicit. This means that instead of snapshotting the inputs and outputs on demand when needed, these operations happen in specific places in the execution chain.
This allows two things:

moving more task executors to :execution in preparation for incremental/cacheable artifact transforms,
better capture the snapshotting times; we now know when snapshotting happens, and we can also measure the time it takes to snapshot inputs and outputs (before and after execution) separately. This helps resolve this comment from @ldaley.

@ldaley please give some advice here.
Before this PR, we had quite a bit of mess around capturing the bookkeeping time for snapshotting stuff and calculating cache keys. We captured and measured a single build operation in ResolveBuildCacheKeyExecuter that included a few separate steps. We had to measure these steps together because they were done atomically. Here's your comment about it:
https://github.com/gradle/gradle/blob/ff0ed56cc64e224b7b028a07045d2a36158d957b/subprojects/core/src/main/java/org/gradle/api/internal/tasks/execution/ResolveBuildCacheKeyExecuter.java#L139-L155
In this PR each step now happens in its own separate class, and thus can be captured and measured separately, making that comment and the existing build operation obsolete.

snapshot the task's outputs before execution: ResolveBeforeExecutionOutputsTaskExecuter
snapshot the task's inputs before execution: ResolveBeforeExecutionStateTaskExecuter
calculate the cache key from the inputs: ResolveBuildCacheKeyExecuter
snapshot the task's output after execution: SnapshotOutputStep

(The *Executer types will move to the :execution project at some point, and become *Steps, but they will stay separate steps.)
How should we move forward with the current single build operation? The goal should be to measure these things separately indeed, but we need to keep backwards compatible, too. Please advise.

I've added a test for ResolveBeforeExecutionOutputsTaskExecuter, but it's pretty trivial. What cases do you think we should test for ResolveBeforeExecutionStateTaskExecuter?

@ldaley I've added the non-wrap-around BuildOperation feature here: https://github.com/gradle/gradle/pull/8038/commits/705a42270926100a03fc3710422100f6029e2e57
It doesn't yet check if all child operations are finished, but I think the approach is already worth reviewing. Could you take a look?

Regarding: https://github.com/gradle/gradle/pull/8038/commits/ea106fcba012a7fac2b6c7429f6782800892dcbf

The duplication in the executor should be dealt with before merge or immediately after, otherwise it will diverge.
I didn't find a test for the handling of bugged code not finishing the child op before the parent finishes
We should have an understanding of what will happen if we ship with a bug that means that child tries to outlive the parent - does the build fail reasonably? Or does this cause a cascade of failures that is entirely unintelligible? The latter might still be OK, but I think we should know this.

Regarding tests for ResolveBeforeExecutionStateTaskExecuter: I would expect tests that the fingerprints are correctly created from the taskProperties and the task class/actions. If we have other tests which already check this, then we don't need to add more tests.
The handling of isTaskHistoryMaintained should probably also be tested.

@wolfs I've addressed your comments. For testing ResolveBeforeExecutionStateTaskExecuter I've added https://github.com/gradle/build-cache/issues/1391.


'Exception: Connection refused - not authorised' when HA starts

This has been working fine until today, when I updated my NIko API token and let the Niko software update do its updates.
When HA starts, I get the following error in the log:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.9/threading.py", line 910, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3591, in _thread_main
    self.loop_forever(retry_first_connection=True)
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
    rc = self._loop(timeout)
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop
    rc = self.loop_read()
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read
    rc = self._packet_read()
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read
    rc = self._packet_handle()
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle
    return self._handle_connack()
  File "/usr/local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack
    on_connect(
  File "/config/custom_components/nhc2/nhccoco/coco.py", line 124, in _on_connect
    raise Exception(MQTT_RC_CODES[rc])
Exception: Connection refused - not authorised

All the Niko devices show in Lovelace but are greyed out. When I click on one to view its details, it says 'This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.'
I know that the new token is OK and there is nothing wrong with Niko because I can connect to the controller using MQTT Explorer using the same credentials as are in my configuration.yaml. The Niko app on my phone works fine.
This has happened before, and my previous solution (which took days to find!) was to delete the Niko integration from the list of Integrations in the HA Configuration. However, doing this means I have to reallocate all my 84 devices to their correct areas, which I do not want to have to do again.
I have tried the following, in this order, and nothing has made any difference:

Disabled and reenabled the Niko integration.
Shutdown the actual server and restarted it.
Found the Niko integration in HACS, downloaded new version, restarted HA.
Updated the Mosquitto broker and restarted the whole machine.
Unplugged the Niko Ethernet cable for a few minutes then plugged it back in again.
Restarted the whole machine again.
Updated HA from 2022.3.8 to 2022.8.1 and rebooted the host.

I'm wondering if the old API token is cached somewhere in HA or something, but I have no idea how to tell. Or perhaps it's something completely different ...
Any ideas on what might be causing this and/or how I can try to find the problem?

FIXED with the help of petro on the HA Configuration forum, who suggested looking in the .storage folder.
I started looking through the core.* files in .storage, which I found are readble json files. When I got to core.config_entries I found that the password for nhc2 was the old one. Copied & pasted in the new one, saved the file, restarted HA and, lo and behold, everything is working again!


mini.base16: Hidden window separator caused by the way highlight groups are set

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.base16
Description
The window separator character, displayed when laststatus is set to not show a status line everywhere, is hidden, because the WinSeparator and VertSplit highlight groups's foreground and background colors are both set to the same color (base02). This is in contrast to mini.hues's randomhue not having this issue.
The VertSplit highlight group should also not be used because it's deprecated.
Setting WinSeparator to the background still doesn't look as good because of the different color of the number line on the left side.
Neovim version
0.9.4
Steps to reproduce

Use the mini.base16 module with any palette.
Set the vim laststatus option to something like 3.
Open another window in a split, like with :split or :vsplit.

Expected behavior
The foreground and background colors of both the WinSeparator and VertSplit highlight groups should be different, so that the separator in between windows can be visible when using a laststatus option that hides the status line in some cases.
The VertSplit highlight group should also not be set at all, because it's deprecated according to Neovim's documentation (:help hl-VertSplit).
Actual behavior
Instead, the foreground and background colors of both the WinSeparator and VertSplit highlight groups are both set to base02 (according to the source code of the plugin), which leads to the window separator character (default "─") being essentially invisible because both the foreground and background colors are the same.
In addition to that, the VertSplit highlight group shouldn't be set, as it's deprecated.
I don't know if this is a bug or a feature; it could be that it's intended to hide the window separator to compensate for the supposed inconsistency of the number line on the left side being displayed with another background color. Here's what it looks like after setting WinSeparator to the background:

Maybe this issue can be avoided by disabling the coloration of the number line and instead having it just be the background (which I, myself, would prefer) or by having this fix/feature available as a configurable option. Setting the LineNr* highlight groups to the background looks like this:

Damn, that's quite the essay for a problem with a highlight group that could lead to a possible PR fix consisting of a few lines

Thanks for the issue!
I am aware of this issue and agree with you that it doesn't look as good as 'mini.hues' and your second example (with gutter and window separators having same background as Normal). However, 'mini.base16' is set to follow Base16 standard, which has it this way.
If any reasonable deviation to be made, it makes sense to have it patch other issues. Like adjusting FloatBorder to have the same background color as window itself, etc. I am not yet sure how I feel about making this deviation.
Dropping "VertSplit" is reasonable, but not an issue in itself (as it just one extra highlight group which is not used). It is there to, again, have more in common with 'base16-vim'.
I'll let this be open for a while and think about it.

I guess that would make sense considering the author of that Vim plugin also created Base16 and the Tomorrow themes. The official, albeit somewhat vague, Base16 style guide also does suggests base16-vim as a reference, but not necessarily as a strict set of guidelines.
However there are also other Base16 (Neo)vim plugins like this one that seem to be more popular (but unofficial) and implement things in a slightly differently way.

Thanks again for the suggestion, but I think I am going to close this one as not planned. I would like 'mini.base16' to follow upstream Vim color scheme as much as possible.
For minor adjustments there is always a way of overriding highlight groups.


Is it possible to write to specific file when invoke log?

For example:
logger.log("msg log","filename1.txt");
logger.log("continue msg log," filename1.txt);
logger.log("msg2 log","filename2.txt");
logger.log("continue msg2 log," filename2.txt);

You can use the Logger-name to route to a specific-file. Ex:
var logger1 = NLog.LogManger.GetLogger("FileLogger.FileName1");
logger1.Info("continue msg log");
var logger2 = NLog.LogManger.GetLogger("FileLogger.FileName2");
logger2.Info("continue msg log");

With the following NLog Logging Rules:
<nlog>
<targets>
    <target type="file" name="fileLogger" fileName="${logger:shortName=true}.txt" />
</targets>
<rules>
    <logger name="FileLogger.*" writeTo="fileLogger" />
</rules>
</nlog>

See also: https://github.com/NLog/NLog/wiki/Configuration-file#rules

thank you your respond @snakefoot, this solution can help. Then is it can kindly combine with dependency injection when using ILogger instead of using the global/static variables? Due to considerations of others customized logger tool, Thanks.

You can use the ILoggerFactory to create logger with the wanted name:
public class MyClass
{
      public MyClass(ILoggerFactory loggerFactory)
      {
            var fileLogger1 = loggerFactory.CreateLogger("FileLogger.FileName1");
            fileLogger1.LogInformation("continue msg log");
            var fileLogger2 = loggerFactory.CreateLogger("FileLogger.FileName2");
            fileLogger2.LogInformation("continue msg log");
      }
}

Great thanks, is it better to add those to document? Or do you mind me to raise pr for those docs? Thanks

The NLog Wiki is open for editing. If you find places that can be improved, then you are welcome to make the change.
Sent from my Galaxy
-------- Original message --------
From: Eric @.>
Date: 11/09/2024 09:23 (GMT+01:00)
To: "NLog/NLog.Targets.MauiLog" @.>
Cc: Rolf Kristensen @.>, Mention @.>
Subject: Re: [NLog/NLog.Targets.MauiLog] Is it possible to write to specific file when invoke log? (Issue #32)
Great thanks, is it better to add those to document? Or do you mind me to raise pr for those docs? Thanks
—
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog.Targets.MauiLog/issues/32#issuecomment-2342859431, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HDP5DBD2346BQ3TYPTZV7VWDAVCNFSM6AAAAABN7BRHK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBSHA2TSNBTGE.
You are receiving this because you were mentioned.Message ID: @.***>

Closing due to inactivity. If you need guidance in how to update the NLog-wiki-pages that I have presented, then don't hesitate to reach out.


Fix error messages

Error messages that are returned should not start capitalized

Change some error messages to be more descriptive

#42 closes this


[BUG] Icons are wrong

Describe the bug
Icons are being loaded, but the color order must be wrong. (red and blue appear swapped.  maybe more than that)
Example: this should be case red.  It certainly is in game.

For posterity:  DDSParse and Decode-DXT appear to be functioning perfectly correctly.  Did a color bar image test, order of the rgba Buffer was as expected.
nativeImage from electron was flipping the color fields.  I have no idea why - it was cross platform with windows and linux, and it's a 4-byte sequence, so it's not and endian-ness issue.  It's not really the intended use of nativeImage, so I backed off and used a different library.
I would file a ticket with electron, but I'm honestly not convinced I'm simply using it wrong.  Maybe some other time.


⚠ ClamAV has degraded performance

In 8f73084, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 89 ms

Resolved: ClamAV performance has improved in 0acb385.


GH-617 Retain PrintString defaults across node refreshes

Fixes #617

Applied to main (=2.1) and branch 2.0


sshuttle: python not found

Describe the bug
Upon invokation, sshuttle immediately exits:
/bin/sh: line 0: exec: python: not found
client: fatal: server died with error code 127

To Reproduce
Steps to reproduce the behavior:

Install shuttle via nix-env -iA nixos.sshuttle
Run sshuttle, e.g. sshuttle -r<EMAIL_ADDRESS><IP_ADDRESS>/0
sshuttle may ask for local sudo password (as expected) before immediately crashing with above output

Expected behavior
Shuttle applies firewall rules and functions as a VPN over SSH
Notify maintainers

@domenkozar
@carlosdagos
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.10-zen1, NixOS, 21.05pre270709.6b1057b452c (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(root): `"nixos-21.05pre270709.6b1057b452c"`
 - channels(johannes): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

https://sshuttle.readthedocs.io/en/stable/requirements.html#server-side-requirements
Is python installed on your server?

@JohnAZoidberg solved!
Didn't realize the error was due to the server side. Python must have been removed from it at some point.


flutter run fails on iOS -- BUILD TARGET google_sign_in OF PROJECT Pods WITH CONFIGURATION Debug

Steps to Reproduce

Create a new Flutter project
Setup up for Firebase - include google-services.json and GoogleService-Info.plist where they belong.
Add below dependencies to pubspec.yaml

  firebase_auth: '^0.5.10'
  google_sign_in: '^3.0.3'
  flutter_twitter_login: "^1.1.0"
  flutter:
    sdk: flutter

Run flutter packages get to update packages

Logs

Launching lib/main.dart on iPhone 6 in debug mode...
Starting Xcode build...
Xcode build done.                                            1.0s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET google_sign_in OF PROJECT Pods WITH CONFIGURATION Debug ===
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:5:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:80:42: warning: 'UIUserNotificationSettings' is only available on iOS 8.0 or newer [-Wunguarded-availability]
        didRegisterUserNotificationSettings:(UIUserNotificationSettings*)notificationSettings;
                                             ^
    In module 'UIKit' imported from /../../test_flutter_auth_with_firebase/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIUserNotificationSettings.h:43:12: note: 'UIUserNotificationSettings' has been explicitly marked partial here
    @interface UIUserNotificationSettings : NSObject
               ^
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:5:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:79:1: note: annotate 'application:didRegisterUserNotificationSettings:' with an availability attribute to silence this warning
    - (void)application:(UIApplication*)application
    ^
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:95:44: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
              fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
                                               ^
    In module 'UIKit' imported from /../../test_flutter_auth_with_firebase/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
                                ^
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:5:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:93:1: note: annotate 'application:didReceiveRemoteNotification:fetchCompletionHandler:' with an availability attribute to silence this warning
    - (BOOL)application:(UIApplication*)application
    ^
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:140:58: warning: this block declaration is not a prototype [-Wstrict-prototypes]
                          completionHandler:(nonnull void (^)())completionHandler;
                                                             ^
                                                              void
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:148:49: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
        performFetchWithCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
                                                    ^
    In module 'UIKit' imported from /../../test_flutter_auth_with_firebase/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
                                ^
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:5:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:147:1: note: annotate 'application:performFetchWithCompletionHandler:' with an availability attribute to silence this warning
    - (BOOL)application:(UIApplication*)application
    ^
    /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:70:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
            signInAnonymouslyWithCompletion:^(FIRAuthDataResult *dataResult, NSError *error) {
                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:7:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:420:73: note: passing argument to parameter 'completion' here
    - (void)signInAnonymouslyWithCompletion:(nullable FIRAuthResultCallback)completion;
                                                                            ^
    /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:103:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
                                 completion:^(FIRAuthDataResult *dataResult, NSError *error) {
                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:7:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:517:61: note: passing argument to parameter 'completion' here
                     completion:(nullable FIRAuthResultCallback)completion;
                                                                ^
    /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:131:37: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
                             completion:^(FIRAuthDataResult *dataResult, NSError *error) {
                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:7:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:323:57: note: passing argument to parameter 'completion' here
                 completion:(nullable FIRAuthResultCallback)completion;
                                                            ^
    /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:188:43: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
                                   completion:^(FIRAuthDataResult *dataResult, NSError *error) {
                                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.m:5:
    In file included from /../../.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.5.10/ios/Classes/FirebaseAuthPlugin.h:7:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
    In file included from /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
    /../../test_flutter_auth_with_firebase/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:464:63: note: passing argument to parameter 'completion' here
                       completion:(nullable FIRAuthResultCallback)completion;
                                                                  ^
    4 warnings and 4 errors generated.
Could not build the application for the simulator.
Error launching application on iPhone 6.

flutter analyze
Analyzing test_flutter_auth_with_firebase...
No issues found! (ran in 2.7s)

flutter doctor -v
[✓] Flutter (Channel dev, v0.4.4, on Mac OS X 10.13.4 17E202, locale en-GB)
    • Flutter version 0.4.4 at /../../../sdks/flutter
    • Framework revision f9bb4289e9 (5 days ago), 2018-05-11 21:44:54 -0700
    • Engine revision 06afdfe54e
    • Dart version 2.0.0-dev.54.0.flutter-46ab040e58

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /../../Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.3.1, Build version 9E501
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.2

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 24.2.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2018.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 22.2.2
    • Dart plugin version 173.4700

[✓] VS Code (version 1.23.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Dart Code extension version 2.12.1

[✓] Connected devices (4 available)
    • Android SDK built for x86 • emulator-5554                        • android-x86 • Android 7.1.1 (API 25) (emulator)
    • iPhone 6                  • FB910E11-3F80-47AE-A553-AAFE7048A9B6 • ios         • iOS 11.3 (simulator)
    • iPhone 7                  • 06D3328D-47D8-45D2-8CB9-3759255D3612 • ios         • iOS 11.3 (simulator)
    • iPhone X                  • C43CCCC2-8709-4361-A629-2BA9E19BC87E • ios         • iOS 11.3 (simulator)

• No issues found!

Having the same issue.
For me it seemed to appear after I added firebase_cloud: to the pubspec.yaml.
No clue though if related, or if that just triggered me downloading the 0.5.10 version instead of having the 0.5.9 version

Updating the pods repo should resolve this

Thanks, @mravn-google. Running the following fixed the issue for me
rm -rf ~/Library/Caches/CocoaPods
rm -rf ios/Pods
pod update //in ios directory

I had the same error and I solved with:
1 - delete Podfile, Podfile.lock, pod directory in ios directory, .flutter-plugins, .packages, pubspec.lock
2 - pod repo update
2 - update pubspec.yaml packages to latest version
3 - flutter packages get


Expose "Start Date" column on Google Ads and Facebook Ads "per month" reports to allow date range filter

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1915
Originally created by @DouweM on 2020-03-26 22:54:20

View 4 previous comments from the original issue on GitLab


Local pull request success status testing

Docs Build status updates of commit 78aec1c:
:clock10: Pending: waiting for processors (12 builds ahead of you)
:warning: Docs Build is busy, currently there are 12 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 78aec1c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Http Response method withStatus not compatible with Psr Interface

zend-stratigility 1.3.3
Zend\Stratigility\Http\Response method withStatus is not compatible with Interface Psr\Http\Message\ResponseInterface. Second parameter $reasonPhrase should default to empty string but defaults to null. zend-diactoros added a string check in method setStatusCode that throws an InvalidArgumentException when $reasonPhrase is not a string.

The version 1 series is no longer supported. Please upgrade to version 2.2 (LTS version) or 3.0 (stable version). These versions no longer implement the PSR-7 wrappers, making the point moot.

I just want to note this breaks applications using zend-expressive 1.x because zend-expressive relies on zend-diactoros and zend-stratigility. While I do understand v1.x is discontinued - zend-diactoros 1.x was changed recently (https://github.com/zendframework/zend-diactoros/pull/320). That change causes applications to malfunction.

Expressive 1.x is also no longer supported; the current oldest LTS is 2.2. Please see https://framework.zend.com/long-term-support
You can always pin your application to earlier versions of libraries by either explicitly requiring them with appropriate constraints, or putting in a conflicts rule in your application package to prevent installation of newer versions.


How to train on my data

Hi, your job is fantastic!
I have RGB and depth information collected by an RGBD camera, and I can obtain the camera pose through the calibration plate. Do I already have all the data needed for training? How should I prepare the data?

Hi, then it should be possible to train the descriptor part. The detector relies on SfM, so can be a bit tricky to retrain.
You will need to make a dataloader for you dataset that gives you the two images, depth, relative pose, and intrinsics in a similar way as megadepth.py.
Let me know if you face any issues :)

/en 感谢你的回复，我并不是从事这方面的人员，我只是想通过rgb图像去估计物体的位姿信息，通过使用ransac pnp。
我想我应该先去了解一下megadepth数据集的结构，并尝试用我的数据去构建与megadepth相同结构的数据集。


Docker push in v1.4.1 doesn't work against private registry running behind nginx ssl proxy (with suggested config)

When pushing against a private registry (running v0.9.1), it fails with the following message:
FATA[0051] mux: variable "hcg-uwsgi" doesn't match, expected "^(?:[a-z0-9]+(?:[._-][a-z0-9]+)*/){1,4}[a-z0-9]+(?:[._-][a-z0-9]+)*$"

commands run:
docker tag hcg-uwsgi docker.example.com/hcg-uwsgi:latest
docker --debug=true push docker.example.com/hcg-uwsgi

The reason is because v1.4.1 attempts to hit https://docker.example.com/v2/.  With the suggested nginx config (https://github.com/docker/docker-registry/blob/f96d5ec35a797953cee18a35410e5c0cd5394e56/contrib/nginx/nginx_1-3-9.conf#L30), this returns a 401 (unauthorized).
Forcing a 404 for the /v2/ url makes docker v1.4.1 fallback to the /v1/ restful endpoint, and everything works great.
Example:
    location /v2/ {
        auth_basic off;
        return 404;
    }

Output of docker info:
Containers: 22
Images: 120
Storage Driver: devicemapper
 Pool Name: docker-253:0-1194892-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 4.443 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 7.512 MB
 Metadata Space Total: 2.147 GB
 Udev Sync Supported: false
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.16.3-200.fc20.x86_64
Operating System: Fedora 20 (Heisenbug)
CPUs: 2
Total Memory: 1.955 GiB
Name: <redacted>
ID: <redacted>

I think this might be a duplicate of this issue: https://github.com/docker/docker/issues/10226

@lsowen can you confirm whether this issue still exists in the latest build of the master branch?

@jlhawn do I have to build it myself, or is there somewhere to download it?  Or do you want me to test the v1.5.0-rc1 release?

@lsowen using the RC should do it.

I installed the v1.5.0 rc from https://test.docker.com/builds/Linux/x86_64/docker-1.5.0, and it looks like that does fix the issue.  It still tries to hit /v2/ first, but handles receiving the HTTP 401 response correctly, and falls back to the /v1/ endpoint.
Thanks for your help!


Bump dependencies for 6.2.0-m5 release

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/5142017811

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/5142017811
Status: success


Proper JSON highlighting using Pygments-JSON

Stole code from: https://github.com/orb/pygments-json

I don't think, this is the right way to do it … I would rather add pygson to the requirements. Unfortunately the module does not support pygments.lexers.get_lexer_for_mimetype yet, so you have to wait for orb/pygments-json#1 to be committed for now.
diff --git a/httpie/pretty.py b/httpie/pretty.py
index 774839d..6b16a31 100644
--- a/httpie/pretty.py
+++ b/httpie/pretty.py
@@ -8,12 +8,13 @@ from pygments.formatters.terminal256 import Terminal256Formatter
 from pygments.formatters.terminal import TerminalFormatter
 from pygments.lexer import RegexLexer, bygroups
 from pygments.styles import get_style_by_name, STYLE_MAP
+from pygson.json_lexer import JSONLexer
 from . import solarized

 DEFAULT_STYLE = 'solarized'
 AVAILABLE_STYLES = [DEFAULT_STYLE] + STYLE_MAP.keys()
-TYPE_JS = 'application/javascript'
+TYPE_JSON = 'application/json'
 FORMATTER = (Terminal256Formatter
              if '256color' in os.environ.get('TERM', '')
              else TerminalFormatter)
@@ -47,12 +48,12 @@ class PrettyHttp(object):
     def body(self, content, content_type):
         content_type = content_type.split(';')[0]
         if 'json' in content_type:
-            content_type = TYPE_JS
+            content_type = TYPE_JSON
             try:
                 # Indent JSON
                 content = json.dumps(json.loads(content),
-                                    sort_keys=True, indent=4)
-            except Exception:
+                                     sort_keys=True, indent=4)
+            except:
                 pass
         try:
             lexer = get_lexer_for_mimetype(content_type)
diff --git a/setup.py b/setup.py
index e1ef638..f6eb4c1 100644
--- a/setup.py
+++ b/setup.py
@@ -9,7 +9,7 @@ if sys.argv[-1] == 'test':
     sys.exit()

-requirements = ['requests>=0.10.4', 'Pygments>=1.4']
+requirements = ['requests>=0.10.4', 'Pygments>=1.4', 'pygments-json>=0.1']
 if sys.version_info < (2, 7):
     requirements.append('argparse>=1.2.1')

Very cool, I'll merge your pull request in for now and try that out. Thanks!

+1
It would be ideal if @orb decided to contribute the lexer directly to Pygments so that JSON would be one of the languages supported by default.

It was merged into pygments here:
https://bitbucket.org/birkenfeld/pygments-main/changeset/de394bf6a997
I don't think they've made an official release yet containing it.

@orb that's great! I think the simplest solution then is to have your lexer bundled with HTTPie until there is a new release of Pygments. Are you okay with that? Both Pygments and HTTPie use the BSD licence.