pyDPF-core will not open result files from Ansys version older than 21

Before submitting the issue

[X] I have checked for Compatibility issues
[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug

from ansys.dpf import core as dpf
model = dpf.Model('v18.rst')
Traceback (most recent call last):
File "", line 1, in
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/model.py", line 49, in init
server = dpf.core._global_server()
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/server.py", line 69, in _global_server
start_local_server(as_global=True)
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/server.py", line 191, in start_local_server
raise errors.InvalidANSYSVersionError(f"Ansys v{ver} does not support DPF")
ansys.dpf.core.errors.InvalidANSYSVersionError: Ansys v182 does not support DPF

Steps To Reproduce
start pyAnsys virtual environment
start python
inside python do:
from ansys.dpf import core as dpf
model = dpf.Model('v18.rst')
Which Operating System are you using?
Linux
Which DPF/Ansys version are you using?
Ansys 2022 R2
Which Python version are you using?
3.7
Installed packages
Package                               Version

aiohttp                               3.8.3
aiosignal                             1.3.1
ansys-api-mapdl                       0.5.1
ansys-api-platform-instancemanagement 1.0.0b3
ansys-corba                           0.1.1
ansys-dpf-core                        0.7.1
ansys-dpf-gate                        0.3.0
ansys-dpf-gatebin                     0.3.0
ansys-dpf-post                        0.2.5
ansys-grpc-dpf                        0.7.0
ansys-mapdl-core                      0.63.4
ansys-mapdl-reader                    0.52.4
ansys-platform-instancemanagement     1.0.2
appdirs                               1.4.4
async-timeout                         4.0.2
asynctest                             0.13.0
attrs                                 22.1.0
cachetools                            5.2.0
certifi                               2022.12.7
charset-normalizer                    2.1.1
cycler                                0.11.0
fonttools                             4.38.0
frozenlist                            1.3.3
geomdl                                5.3.1
google-api-core                       2.11.0
google-api-python-client              2.70.0
google-auth                           2.15.0
google-auth-httplib2                  0.1.0
googleapis-common-protos              1.57.0
grpcio                                1.51.1
httplib2                              0.21.0
idna                                  3.4
imageio                               2.22.4
importlib-metadata                    5.1.0
kiwisolver                            1.4.4
matplotlib                            3.5.3
multidict                             6.0.3
numpy                                 1.21.6
packaging                             22.0
pexpect                               4.8.0
Pillow                                9.3.0
pip                                   22.3.1
pooch                                 1.6.0
protobuf                              3.20.3
protoc-gen-swagger                    0.1.0
psutil                                5.9.4
ptyprocess                            0.7.0
pyasn1                                0.4.8
pyasn1-modules                        0.2.8
pyiges                                0.2.1
pyparsing                             3.0.9
python-dateutil                       2.8.2
pyvista                               0.37.0
requests                              2.28.1
rsa                                   4.9
scipy                                 1.7.3
scooby                                0.7.0
setuptools                            47.1.0
six                                   1.16.0
tqdm                                  4.64.1
typing_extensions                     4.4.0
uritemplate                           4.1.1
urllib3                               1.26.13
vtk                                   9.2.2
wslink                                1.9.2
yarl                                  1.8.2
zipp                                  3.11.0

Seems to be hardcoded in ansys/dpf/core/server.py:
line 178+
   Returns     -------     server : server.ServerBase     """     from ansys.dpf.core.misc import is_pypim_configured     use_docker = use_docker_by_default and docker_config.use_docker     use_pypim = use_pypim_by_default and is_pypim_configured()     if not use_docker and not use_pypim:         ansys_path = get_ansys_path(ansys_path)         # parse the version to an int and check for supported         try:             ver = int(str(ansys_path)[-3:])             if ver < 211:                 raise errors.InvalidANSYSVersionError(f"Ansys v{ver} does not support DPF")             if ver == 211 and is_ubuntu():                 raise OSError("DPF on v211 does not support Ubuntu")         except ValueError:             pass

@iceblink-ansys ok so the issue is that while you seem to have ANSYS 2022R2 installed (you mention it in the issue description), DPF tries to start a server using your 2018.2 installation folder.
This is most likely a problem of path/environment variable.
As shown in the code you shared, what is tested is the ansys_path variable. Yours seems to include v182.
Could you please try:
from ansys.dpf import core as dpf
dpf.server.start_local_server(as_global=True, ansys_path=FULL_PATH_TO_YOUR_222_INSTALLATION_FOLDER)
model = dpf.Model('v18.rst')

@PProfizi when i try that:

from ansys.dpf import core as dpf
my_ansys_path = "/HPC_A/system/eb/common/software/ANSYS/2022R2/v222"
dpf.server.start_local_server(as_global=True, ansys_path=my_ansys_path)
Traceback (most recent call last):
File "", line 1, in
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/server.py", line 237, in start_local_server
load_operators=load_operators, timeout=timeout, context=context)
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/server_types.py", line 843, in init
raise e
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/core/server_types.py", line 837, in init
data_processing_core_load_api(path, "common")
File "/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/lib/python3.7/site-packages/ansys/dpf/gate/utils.py", line 13, in data_processing_core_load_api
raise Exception(errorMsg.value)
Exception: Unable to load /HPC_A/system/eb/common/software/ANSYS/2022R2/v222/aisol/dll/linx64/libDataProcessingCore.so. Error is "/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /HPC_A/system/eb/common/software/ANSYS/2022R2/v222/aisol/dll/linx64/libDataProcessingCore.so)"

It may be that our IT folks have missed some environment variable when they set up the linux "module" for Ansys 2022. Though it is strange that it does find v18 then, since the linux module for that version is not loaded.
The "2022R2/v222" seems a bit double to me, but maybe that is done by our IT folks on purpose.
$ module list
Currently Loaded Modules:

shared   2) DefaultModules   3) slurm/slurm/20.02.5   4) default-environment   5) ANSYS/2022R2

$ set |grep 2022
CMAKE_PREFIX_PATH=/HPC_A/system/eb/common/software/ANSYS/2022R2
EBDEVELANSYS=/HPC_A/system/eb/common/software/ANSYS/2022R2/easybuild/ANSYS-2022R2-easybuild-devel
EBROOTANSYS=/HPC_A/system/eb/common/software/ANSYS/2022R2
EBVERSIONANSYS=2022
ICEM_ACN=/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/icemcfd/linux64_amd
LD_LIBRARY_PATH=/cm/shared/apps/bla:/cm/shared/apps/bla/lib64:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/commonfiles/CPython/3_7/linx64/Release/python/lib
LOADEDMODULES=shared:DefaultModules:bla/bla/2.2.5:default-environment:ANSYS/2022R2
PATH=/HPC_A/system/eb/common/software/ANSYS/2022R2:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/fensapice/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CEI/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/icemcfd/linux64_amd/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/Icepak/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/polyflow/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/TurboGrid/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/fluent/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CFX/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CFD-Post/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/autodyn/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/ansys/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/RSM/bin:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/aisol/bin/linx64:/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/Framework/bin/Linux64:/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/bin:/cm/shared/apps/bla/current/sbin:/cm/shared/apps/bla/current/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/mssql-tools/bin:/HPC_A/OF_ANSS/Users/me/.local/bin:/HPC_A/OF_ANSS/Users/me/bin
LMFILES=/cm/local/modulefiles/shared:/usr/share/modulefiles/DefaultModules.lua:/cm/local/modulefiles/bla/bla/2.2.5:/cm/shared/modulefiles/default-environment:/HPC_A/system/eb/common/modules/all/ANSYS/2022R2.lua
__LMOD_REF_COUNT_CMAKE_PREFIX_PATH=/HPC_A/system/eb/common/software/ANSYS/2022R2:1
__LMOD_REF_COUNT_LOADEDMODULES='shared:1;DefaultModules:1;bla/bla/2.2.5:1;default-environment:1;ANSYS/2022R2:1'
__LMOD_REF_COUNT_PATH='/HPC_A/system/eb/common/software/ANSYS/2022R2:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/fensapice/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CEI/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/icemcfd/linux64_amd/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/Icepak/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/polyflow/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/TurboGrid/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/fluent/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CFX/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/CFD-Post/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/autodyn/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/ansys/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/RSM/bin:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/aisol/bin/linx64:1;/HPC_A/system/eb/common/software/ANSYS/2022R2/v222/Framework/bin/Linux64:1;/HPC_A/OF_ANSS/Users/me/pyAnsysEnv/bin:1;/cm/shared/apps/bla/current/sbin:1;/cm/shared/apps/bla/current/bin:1;/usr/local/bin:2;/usr/bin:2;/usr/local/sbin:2;/usr/sbin:2;/opt/mssql-tools/bin:1;/HPC_A/OF_ANSS/Users/me/.local/bin:1;/HPC_A/OF_ANSS/Users/me/bin:1'
_LMOD_REF_COUNT__LMFILES='/cm/local/modulefiles/shared:1;/usr/share/modulefiles/DefaultModules.lua:1;/cm/local/modulefiles/bla/bla/2.2.5:1;/cm/shared/modulefiles/default-environment:1;/HPC_A/system/eb/common/modules/all/ANSYS/2022R2.lua:1'

@iceblink-ansys,

concerning the 2022R2/v222, yes it is redundant, yet I guess your IT made the 2022R2 folder but then Ansys does create the v222 folder during installation.
DPF can find automatically v182 as the "latest" ansys install if it is situated in the default "usr/ansys_inc" or "/ansys_inc" folder on Linux.
the new error tells me that: it found your 2022R2 install and is trying to start a server, yet one of the dependencies of DPF (/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20') is not found. My best guess is your gcc compiler/linux distribution is most likely too old or needs an update.

Hi @iceblink-ansys,
coming back to you about this issue.
It seems I was halfway right for the third point explaining your second error:
the problem is most likely that for some reason, the loaded libstdc++.so.6 on which DPF depends is the one of your system instead of the one packaged with DPF. Your Linux distribution might be a bit old, thus the one coming from your system is incompatible with GLIBCXX_3.4.20.
One solution is to add export LD_PRELOAD=$FULL_PATH_TO_YOUR_222_INSTALLATION_FOLDER/tp/stdc++/libstdc++.so.6:$LD_PRELOAD to your .bashrc file and see if the error persists.
Another solution is to use, if you can, the new standalone version of the DPF server, as described here, which works like a Python library.

If you put it this way, maybe I know where this is coming from...
The problem might be that I have setup my PyAnsys Venv in a Windows setting, and I am then using that Venv from within Linux. Could that be an issue?

@iceblink-ansys I am not sure I see how it could directly be related to the error at hand, yet to me venvs are not portable, so it might very well be a problem anyway.


Add new models, drop old models, remove default_max_tokens

Refs:

#4
#5

Tested manually like so:
llm -m llama-3-sonar-small-32k-online 'what is Datasette?'

Datasette is an open source tool that allows you to explore and publish data seamlessly in a web browser. It is specifically designed for data journalists, museum curators, archivists, local governments, scientists, researchers, and anyone with data they would like to share with the world[2].
Datasette enables data exploration and publication in a single line of code. With Datasette, you can create a database from CSV data, and then use it to generate a web interface in which to browse the data. This is achieved through the use of SQLite databases[1][2].
Installation and Basic Usage
To install Datasette, you can use pip on your terminal:
pip install datasette

After installation, you can use the serve command along with the path to your database file. This command starts a web server and makes the database accessible at http://localhost:8001/[2].
Key Features

Data Exploration: Datasette allows you to explore your data in a web browser using SQL and JSON query APIs.
Data Publication: You can publish your data as an interactive website with a range of features including filtering, sorting, and searching.
API: Datasette provides APIs for your data, which can be used for data ingestion, data processing, and data display[1][2].

Additional Features
Datasette further expands its capabilities through several additional features such as:

Datasette Lite: A WebAssembly version of Datasette that can be run entirely in your browser without a Python web application server.
Metadata Support: Datasette supports including licensing and source information in the generated website using a JSON file.
Plugin Support for Custom Functions: Plugins can be developed to enhance Datasette's functionality to suit specific needs[2].

Hortonworks Woo Carousel

(No idea what that last line is about!)
llm -m llama-3-sonar-large-32k-online 'what is Datasette?'

Datasette is a versatile tool for exploring and publishing data. It offers a diverse range of functionalities such as publishing data on an interactive web platform, enabling explorability for datasets of any shape and size, including respecting licensing and source information[1]. This tool is particularly targeted at users with data they wish to share extensively, including but not limited to data journalists, museum curators, archivists, local governments, scientists, researchers, and others[1].
Datasette can be installed using different methods, including Brew, pip, or pipx, and requires at least Python 3.8[1]. Once installed, it allows for the creation of a web server that hosts the dataset, and by adding a JSON file named metadata.json, information such as licensing and source credits can be displayed on the website and included in the API responses[1].
In addition to the main software, Datasette also has its lightweight equivalent, Datasette Lite, which can run directly in the browser[1]. This browser-based implementation relies on WebAssembly and does not require a separate web application server to run.
Datasette has seen development across various versions, with recent ones including significant updates such as alterations in how transactions are handled and new features for plugins[3]. It is well-suited for handling data sizes not require a full data warehouse and is known for its ease of use with different plugins, making it a practical tool in various contexts[4][5].

And to test the max_output option:
llm -m llama-3-sonar-large-32k-online 'what is Datasette?' -o max_tokens 40

Datasette is an open source multi-tool designed for exploring and publishing data of any shape or size[1][2][4]. It transforms data into an interactive, exploratory website and accompanying API,

Thank you, Simon, for the fast response, as always.


feat(git_push_test): curl app endpoint for "Powered by"

Closes #170.

Jenkins, test this please.

This seems to be failing because this is the first test spec to deploy a Buildpack app, and therefore it pays the price for faulting in slugbuilder/slugrunner and times out. That could be worked around by "priming" the cluster with those images, but really git push deis master shouldn't be returning until the app is routable.

We're lacking timing information in there but I suspect it goes beyond the timeout limit we have set around deploys and that's why it is returning.
We may have to set higher limits for build pack apps or detect somehow the image is being downloaded still and give it a longer timeout when the download takes a long time

Several fixes to deis/controller recently have made this test stable. :anchor:
I'm merging this and then creating another PR with a similar spec for a Dockerfile-based app, since that has a different deployment path on the back end.


📝 Update iOS SDK version in changelog

What and why?
Actually going to ship with 1.19, not 1.18
Review checklist

[ ] This pull request has appropriate unit and / or integration tests
[ ] This pull request references a Github or JIRA issue

CI Configuration (optional)

[ ] Run unit tests
[ ] Run integration tests

Bypassing checks (minor doc change)


Extract more to ide module

@ice1000

Can you also solve #795?

Can you also solve #795?

We will make Reporter and Problem generic types, is this intended?

I would make DistillerOptions a generic type 😉

Can you also solve #795?

We will make Reporter and Problem generic types, is this intended?

I think you can. Does that change a lot of existing code? 😟

Well, I just do not think it's a good idea to have Aya-specific stuffs in the tools module. It should be just tools.

bors d=ice1000


[ESP32] Debug log error in hawkbit example "CONFIG_LOG_STRDUP_MAX_STRING"

Describe the bug
I am bulding the hawkbit example from zephyr\samples\subsys\mgmt\hawkbit-esp32.
A fatal error arises when the log level is set as DEBUG CONFIG_HAWKBIT_LOG_LEVEL_DBG=y. The error is caused due to the log_strdup functions. If I build with info log level CONFIG_HAWKBIT_LOG_LEVEL_INF, it works.
To Reproduce
Steps to reproduce the behavior:

my prj.conf file for esp32:

#Turn on the Hawkbit
CONFIG_HAWKBIT=y

#Main Stack Size
CONFIG_MAIN_STACK_SIZE=4096

#Minimal Heap mem pool size for the Hawkbit working
CONFIG_HEAP_MEM_POOL_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

CONFIG_NET_IPV4=y
CONFIG_NET_IPV6=n

#Enable DHCPv4 server
CONFIG_NET_DHCPV4=y
CONFIG_NET_MGMT=y
CONFIG_NET_MGMT_EVENT=y

#Enable DNS Resolver
CONFIG_DNS_RESOLVER=y
CONFIG_DNS_SERVER_IP_ADDRESSES=y
CONFIG_DNS_SERVER1="<IP_ADDRESS>"
CONFIG_DNS_SERVER2="<IP_ADDRESS>"

#Optional if you would like test on the your server
CONFIG_SHELL=n
CONFIG_HAWKBIT_SHELL=n
CONFIG_KERNEL_SHELL=n
#CONFIG_SHELL_STACK_SIZE=4096

#Hawkbit polling mode
CONFIG_HAWKBIT_POLLING=y

#Config Hawkbit Server
CONFIG_HAWKBIT_SERVER="<IP_ADDRESS>"

#Debug helpers
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=1
CONFIG_LOG_BACKEND_UART=y
CONFIG_HAWKBIT_LOG_LEVEL_DBG=y
CONFIG_NET_LOG=y
CONFIG_NET_SHELL=n

#General Config
CONFIG_NEWLIB_LIBC=y
CONFIG_LOG_BUFFER_SIZE=4096

#Generate HEX output
CONFIG_BUILD_OUTPUT_HEX=y

#LOG Maximum string define
CONFIG_LOG_STRDUP_MAX_STRING=100
CONFIG_LOG_STRDUP_BUF_COUNT=20

CONFIG_MCUBOOT_GENERATE_CONFIRMED_IMAGE=y

#### ESP32 ####
CONFIG_WIFI=y
CONFIG_WIFI_ESP32=y
CONFIG_ESP32_WIFI_STA_AUTO=y
CONFIG_HEAP_MEM_POOL_SIZE=98304

CONFIG_NETWORKING=y
CONFIG_NET_L2_ETHERNET=y

CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_ENTROPY_ENABLED=y
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDHE_ECDSA_ENABLED=y
CONFIG_MBEDTLS_ECP_ALL_ENABLED=y

CONFIG_ESP32_WIFI_SSID="myssid"
CONFIG_ESP32_WIFI_PASSWORD="mypassword"

# To reduce the IRAM use
CONFIG_ESP32_WIFI_IRAM_OPT=n
CONFIG_ESP32_WIFI_RX_IRAM_OPT=n

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

Building

west build -b esp32 -p -- -DCONF_FILE="prj.conf"

During building, the following warning messages are displayed

warning: LOG_STRDUP_MAX_STRING (defined at subsys/logging\Kconfig.processing:126) was assigned the
value '100' but got the value ''. Check these unsatisfied dependencies: LOG1_DEFERRED (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_STRDUP_MAX_STRING and/or look up
LOG_STRDUP_MAX_STRING in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: LOG_STRDUP_BUF_COUNT (defined at subsys/logging\Kconfig.processing:135) was assigned the
value '20' but got the value ''. Check these unsatisfied dependencies: LOG1_DEFERRED (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_STRDUP_BUF_COUNT and/or look up
LOG_STRDUP_BUF_COUNT in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

signing

west sign -t imgtool -B <path_signed_app> -- --key <key.pem> --confirm --version 1.0.0

flash the image

esptool.py -p <port> -b 115200 --before default_reset --after hard_reset --chip esp32  write_flash --flash_mode dio --flash_size 4MB --flash_freq 40m 0x1000 <path_signed_app>

See error

Leaving...
Hard resetting via RTS pin...
ot] chip revision: 1
[esp32] [INF] [boot_comm] chip revision: 1, min. bootloader chip revision: 0
[esp32] [INF] Enabling RNG early entropy source...
[esp32] [INF] *** Booting MCUboot build v1.9.0-37-g1d6f98e ***
[esp32] [INF] Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x1
[esp32] [INF] Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[esp32] [INF] Boot source: primary slot
[esp32] [INF] Swap type: none
[esp32] [INF] Disabling RNG early entropy source...
[esp32] [INF] br_image_off = 0x10000
[esp32] [INF] ih_hdr_size = 0x20
[esp32] [INF] Loading image 0 - slot 0 from flash, area id: 1
[esp32] [INF] DRAM segment: start=0x15ff0, size=0x269c, vaddr=0x3ffb0000
[esp32] [INF] IRAM segment: start=0x1868c, size=0x1a6b0, vaddr=0x40080000
[esp32] [INF] start=0x40091c7c
?*** Booting Zephyr OS build v3.1.0-rc2-120-ge79c48f7c68a  ***

Backtrace:0x40092DEA:0x3FFEAB30 0x400D76D5:0x3FFEAB40 0x400D8E15:0x3FFEABC0 0x400E7416:0x3FFEAC20 0x400E7F4F:0x3FFEAC40 0x400E88CB:0x3FFEAE80 0x4008E935:0x3FFEAEC0 0x400D7B5B:0x3FFEAF00

[00:00:14.024,000] <inf> fs_nvs: 3 Sectors of 4096 bytes
[00:00:14.024,000] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:14.024,000] <inf> fs_nvs: data wra: 0, 0
[00:00:14.024,000] <dbg> hawkbit: hawkbit_init: Action id: current<PHONE_NUMBER>
[00:00:14.024,000] <inf> hawkbit: Image is confirmed OK
[00:00:14.242,000] <inf> hawkbit: Polling target data from Hawkbit
[00:00:14.268,000] <dbg> hawkbit: hawkbit_dump_base: config.polling.sleep=00:05:00
[00:00:14.268,000] <err> os:  ** FATAL EXCEPTION
[00:00:14.268,000] <err> os:  ** CPU 0 EXCCAUSE 28 (load prohibited)
[00:00:14.268,000] <err> os:  **  PC 0x40092ded VADDR (nil)
[00:00:14.268,000] <err> os:  **  PS 0x60f20
[00:00:14.268,000] <err> os:  **    (INTLEVEL:0 EXCM: 0 UM:1 RING:0 WOE:1 OWB:15 CALLINC:2)
[00:00:14.268,000] <err> os:  **  A0 0x800d76d8  SP 0x3ffca899  A2 (nil)  A3 0xfffffffc
[00:00:14.268,000] <err> os:  **  A4 0xff  A5 0xff00  A6 0xff0000  A7 0xff000000
[00:00:14.268,000] <err> os:  **  A8 (nil)  A9 0x3ffeab60 A10 (nil) A11 0x3ffca760
[00:00:14.268,000] <err> os:  ** A12 0x60b20 A13 0x3ffca78a A14 0x30 A15 (nil)
[00:00:14.268,000] <err> os:  ** LBEG 0x40092ded LEND 0x40092dfd LCOUNT 0xffffffff
[00:00:14.268,000] <err> os:  ** SAR 0x4
[00:00:14.274,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:14.274,000] <err> os: Current thread: 0x3ffcd3e0 (unknown)
[00:00:14.410,000] <err> os: Halting system

decode the backtrace

xtensa-esp32-elf-addr2line -pfiaC -e build/zephyr/zephyr.elf 0x40092DEA:0x3FFEAB30 0x400D76D5:0x3FFEAB40 0x400D8E15:0x3FFEABC0 0x400E7416:0x3FFEAC20 0x400E7F4F:0x3FFEAC40 0x400E88CB:0x3FFEAE80 0x4008E935:0x3FFEAEC0 0x400D7B5B:0x3FFEAF00

output
0x40092dea: strlen at ??:?
0x400d76d5: append_string at C:/Workspace/zephyrproject/zephyr/lib/os/cbprintf_packaged.c:218
 (inlined by) append_string at C:/Workspace/zephyrproject/zephyr/lib/os/cbprintf_packaged.c:215
 (inlined by) cbprintf_package_convert at C:/Workspace/zephyrproject/zephyr/lib/os/cbprintf_packaged.c:798
0x400d8e15: cbprintf_package_copy at C:\Workspace\zephyrproject\zephyr\samples\subsys\mgmt\hawkbit-esp32\build/../../../../../include/zephyr/sys/cbprintf.h:445
 (inlined by) z_impl_z_log_msg2_static_create at C:/Workspace/zephyrproject/zephyr/subsys/logging/log_msg2.c:59
0x400e7416: z_log_msg2_static_create at C:\Workspace\zephyrproject\zephyr\samples\subsys\mgmt\hawkbit-esp32\build/zephyr/include/generated/syscalls/log_msg2.h:37
0x400e7f4f: hawkbit_dump_base at C:/Workspace/zephyrproject/zephyr/subsys/mgmt/hawkbit/hawkbit.c:576
 (inlined by) hawkbit_probe at C:/Workspace/zephyrproject/zephyr/subsys/mgmt/hawkbit/hawkbit.c:1094
0x400e88cb: autohandler at C:/Workspace/zephyrproject/zephyr/subsys/mgmt/hawkbit/hawkbit.c:1273
0x4008e935: work_queue_main at C:/Workspace/zephyrproject/zephyr/kernel/work.c:668
0x400d7b5b: z_thread_entry at C:/Workspace/zephyrproject/zephyr/lib/os/thread_entry.c:36

Additional context
The error arises in the function hawkbit_dump_base in zephyr/blob/main/subsys/mgmt/hawkbit/hawkbit.c. I guess that it occurs due to the log_strdup function.
static void hawkbit_dump_base(struct hawkbit_ctl_res *r)
{
	LOG_DBG("config.polling.sleep=%s", log_strdup(r->config.polling.sleep));
	LOG_DBG("_links.deploymentBase.href=%s",
		log_strdup(r->_links.deploymentBase.href));
	LOG_DBG("_links.configData.href=%s",
		log_strdup(r->_links.configData.href));
	LOG_DBG("_links.cancelAction.href=%s",
		log_strdup(r->_links.cancelAction.href));
}

I tried to add CONFIG_LOG1_DEFERRED=y into the config file, however it is not possible since this variable cannot be set manually. Furthermore, I saw in the guiconfig that the LOG1_DEFERRED is deprecated and I couldn't set.
How can I set the debug log level in hawkbit?

@jeronimoagullo I have tested and confirm it is crashing. However, the root cause seems to be a NULL pointer at https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/mgmt/hawkbit/hawkbit.c#L575.
r->config.polling.sleep is null, which causes the crash. @ycsin, can check whether this null pointer happens in there as well?
So I am still not sure whether this is ESP32 issue or Hawkit implementaion.

How can I set the debug log level in hawkbit?

CONFIG_HAWKBIT_LOG_LEVEL_DBG / CONFIG_HAWKBIT_LOG_LEVEL_WRN for example.
The log_strdup was necessary for LOG1, which is the version that I was using (2.7 LTS), we had quite a bit of issues back then with the LOG2 and we were developing a product so we stayed on the LTS for the sake of stability. However I'm not sure what would happen if the arg passed into it happened to be a NULL ptr, maybe @nordic-krch have more insight in that regard.
@sylvioalves I don't really have anything to test now, didn't encounter this issue the last time I tested it.
From the log, it seems to be able to print the sleep string:
[00:00:14.268,000] <dbg> hawkbit: hawkbit_dump_base: config.polling.sleep=00:05:00

My understanding is that the HAWKBIT_PROBE request should either parse the links properly or it will error here, and when it does it will jump to cleanup, skipping the debug print.
@jeronimoagullo are you able to reproduce this error? If you could maybe you can breakpoint at here to check if there are indeed NULL pointers?

The only feedback that I can share currently is that the error arises in the function "hawkbit_dump_base" when the debug level of hawkbit module is debug.

that's because the function is ran only when the level is set to debug
Let say the level is not debug, would the hawkbit be able to proceed and do the upgrade?

hi @ycsin
yes, if the level is not debug (for example information), everything runs smothly. Thus, I think that it is just a matter of the debug messages.
Thank you very much

@jeronimoagullo would it be possible for you to test #49232 and approve if it fixes the issue?


EXSWHTEC-289 - Implement tests for remainder and rounding device math functions

Depends on: #233
Implement numerical accuracy, and negative tests for remainder and rounding math functions, including:

fmod
remainder
remquo
modf
fdim
trunc
round
rint
nearbyint
ceil
floor
lrint
lround
llrint
llround.

Please see my last comment in EXSWHTEC-284.

PR has been merged into develop branch via commit 111497351d4c87116fc54f143f3444668bda1199.


[Bug]: opentelemetry_operator - Certificate & Issuer kinds can't be recognize

Welcome to Amazon EKS Blueprints!

[X] Yes, I've searched similar issues on GitHub and didn't find any.

Amazon EKS Blueprints Release version
v4.0.8
What is your environment, configuration and the example used?
Terraform version:  v1.0.11
What did you do and What did you see instead?
enable_opentelemetry_operator = true
opentelemetry_operator_helm_config = {
  version = "0.7.0"
}

Those are the settings that I turned on.
And this is the error that I got:
 Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Certificate" in version "cert-manager.io/v1", unable to recognize "": no matches for kind "Issuer" in version "cert-manager.io/v1"] │ │   with module.eks_blueprints_kubernetes_addons.module.opentelemetry_operator[0].module.operator.helm_release.addon[0], │   on .terraform/modules/eks_blueprints_kubernetes_addons/modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon": │    1: resource "helm_release" "addon" {
Additional Information
No response

Hey, in which example where you deploying this?

fargate-serverless

Should be solved by https://github.com/aws-ia/terraform-aws-eks-blueprints/pull/627

closed in #627


Missing __construct method for setting FormType passed by params.

Missing __construct method for setting FormType passed by params.

That would force everyone to use the c'tor instead of the dedicated setter method setFormType mentioned in section "Register your form type and flow as services". And personally, I just don't like c'tor injection. ;) But I'm thinking about throwing an exception if no form type has been set.

@smoya: How about 6a3a0a7f3387eb4c082b83b90f9a09369ff0feac?

Okey, i think so.
My problem was that I did not see the call of the service and i thought that was passed as an argument. To transform the xml to yml i didn't realize.
Rectified.
Thank you ;)

Alright, thanks for making me aware of that glitch.


Updating Netty Logging to only display errors and default logging to debug

Signed-off-by: Sarat Vemulapalli<EMAIL_ADDRESS>Description
Updating Netty logging to only print out errors.
Netty is using reflective access which is denied by default for Java > 8.
See: https://github.com/netty/netty/issues/7817
As recommendation says, its just a warning but its not fatal problems for the application. For SDK we really dont care about Netty debug/trace logs, error should be good enough.
This PR also updates default logging to debug as trace is not really helping a human unless we really want to debug core problems.
Issues Resolved
Closes #180
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #181 (839d9a1) into main (8fbcc6e) will increase coverage by 0.93%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##               main     #181      +/-   ##
============================================
+ Coverage     66.00%   66.94%   +0.93%
- Complexity       96      103       +7
============================================
  Files            25       24       -1
  Lines           456      475      +19
  Branches         13       25      +12
============================================
+ Hits            301      318      +17
+ Misses          147      141       -6
- Partials          8       16       +8

Impacted Files
Coverage Δ

...main/java/org/opensearch/sdk/TransportActions.java
81.81% <ø> (ø)

...main/java/org/opensearch/sdk/ExtensionsRunner.java
70.83% <50.00%> (+7.59%)
:arrow_up:

src/main/java/org/opensearch/sdk/Extension.java
60.00% <100.00%> (+15.55%)
:arrow_up:

...rch/sdk/handlers/ExtensionsInitRequestHandler.java
100.00% <100.00%> (ø)

...ch/sdk/sample/helloworld/rest/RestHelloAction.java
70.96% <0.00%> (-29.04%)
:arrow_down:

...ain/java/org/opensearch/sdk/ExtensionSettings.java
88.88% <0.00%> (ø)

...java/org/opensearch/sdk/ExtensionRestResponse.java

...rch/sdk/handlers/ExtensionsRestRequestHandler.java
47.36% <0.00%> (+4.51%)
:arrow_up:

...nsearch/sdk/handlers/OpensearchRequestHandler.java
66.66% <0.00%> (+6.66%)
:arrow_up:

...c/main/java/org/opensearch/sdk/NettyTransport.java
100.00% <0.00%> (+7.14%)
:arrow_up:

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I'd even be happy with INFO level logging, with instructions how to change it in the developer guide.

+1 We'll start with debug and we could move over to info eventually overtime.


Move startup-probe from csi-server to csi-provisioner

Description
The csi-server does not do requests that care about DNS while the csi-provisioner does, so the startup-probe fits there better.
(also removes some deadcode)
How can this be tested?
Deploy operator, startup-probe is on the csi-provisioner and not the server
(otherwise everything should work as expected)
Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
Attention: Patch coverage is 0% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 67.02%. Comparing base (98be992) to head (33d6cc5).

Files
Patch %
Lines

pkg/controllers/csi/driver/server.go
0.00%
3 Missing :warning:

cmd/csi/server/builder.go
0.00%
1 Missing :warning:

...kg/controllers/csi/driver/volumes/app/publisher.go
0.00%
1 Missing :warning:

...g/controllers/csi/driver/volumes/host/publisher.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2823      +/-   ##
==========================================
+ Coverage   67.00%   67.02%   +0.01%
==========================================
  Files         250      250
  Lines       13649    13646       -3
==========================================
  Hits         9146     9146
+ Misses       3697     3694       -3
  Partials      806      806

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


License

What is the license of this project?

MIT

Thanks. It would be nice to have this in the canonical LICENSE file in the repository, so that others can find it easily.

License file has been added


[SPARK-10155][SQL]Change SqlParser to object to avoid memory leak

Since scala.util.parsing.combinator.Parsers is thread-safe since Scala 2.10 (See SI-4929), we can change SqlParser to object to avoid memory leak.
I didn't change other subclasses of scala.util.parsing.combinator.Parsers because there is only one instance in one SQLContext, which should not be an issue.

Merged build triggered.

Merged build started.

Test build #41369 has started for   PR 8357 at commit 4bc33e0.

Test build #41369 has finished for   PR 8357 at commit 4bc33e0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41369/
Test PASSed.

cc @marmbrus
This seems serious for SQL.

Does DDLParser have the same issue? Also, since  SI-4929's resolution is "out of scope", can you add a pointer of the comment saying parser combinator is thread safe in the description?

Does DDLParser have the same issue?

I think we only create one DDLParser in on SQLContext. Right? It does still leak one ThreadLocal, but I don't think people will create a lot of SQLContext. If so, I think we should change all subclasses of scala.util.parsing.combinator.Parsers in SQL to object.

since SI-4929's resolution is "out of scope", can you add a pointer of the comment saying parser combinator is thread safe in the description?

SI-4929 was set to out of scope because this comment here https://issues.scala-lang.org/browse/SI-4929?focusedCommentId=72968&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-72968 :
The parser combinators library is now community-maintained. Issues with it are now tracked at https://github.com/scala/scala-parser-combinators/issues/61 instead of here in the Scala JIRA.
Interested community members: if you consider this issue significant, feel free to open a new issue for it on GitHub, with links in both directions.

SI-4929 is really confusing because a lot of comments are about the memory leak rather that the original thread-safe issue.
scala.util.parsing.combinator.Parsers has only one field lastNoSuccessVar, which is DynamicVariable now. Of cause, scala.util.parsing.combinator.Parsers.Parser is not thread-safe, but it's created every time when parsing input, so that's safe.

Closed this one because this is not a correct fix. Although scala.util.parsing.combinator.Parsers is thread safe, SqlParser has some val Parsers which are not thread safe.

Merged build triggered.

Merged build started.

@marmbrus since SQLContext is thread-safe, I suppose SQLParser is thread-safe too. So I reopened it. Could you take a look at this one?

Test build #42663 has started for   PR 8357 at commit 4bc33e0.

Test build #42663 has finished for   PR 8357 at commit 4bc33e0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42663/
Test PASSed.

@zsxwing How serious is the leak? Under what condition(s) will we see a significant amount of memory occupied by leaked stuff?

@yhuai I've just encountered this with my application, so I can give an example of the conditions that cause this - here are some datapoints I hope might help:

My program reads and writes a parquet file about 2-3 times a minute
The write operation uses DataFrame.selectExpr with a list of ~70 expressions (renaming all columns before saving), these seem to be the expressions who's parsing creates the memory-consuming objects
After about 2 hours, heap contains ~25K scala.util.parsing.combinator.Parsers$$anon$3 instances taking up 1GB of heap (that can't be collected by GC)
Note that 2 (hours) * 60 (minutes) * 3 (queries per minute) * 70 (expressions) =~ 25K, which is the number of instances - might be a coincidence, but it might indicate that this is exactly the calculation needed to predict the severity of this issue

So I'd imagine this is a showstopper for any application that performs save/read operations often enough (i.e. multiple times a minute), with a large number of expressions to parse for each operation.
Hope this helps.

@tzachz Thank you for the information! Those are super useful!

Merged build triggered.

Merged build started.

Test build #42716 has started for   PR 8357 at commit 62703af.

Test build #42716 has finished for   PR 8357 at commit 62703af.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42716/
Test PASSed.

LGTM - I will let @yhuai merge this.

LGTM. Merging to master and branch 1.5.

Will this patch slowdown query parsing in case of concurrent requests?

Will this patch slowdown query parsing in case of concurrent requests?

I think so. Do you concern about the performance of parsing query? I assume executing query dominates the time.

In one of our project we have 25 requests/second that are coming in through
automated system.
Executor time per request is 50ms (as  it is just a look up and return one
or two rows only.)
Expected query response time is 500ms. We already have this project running
fine over spark-1.3.1. Since we are migrating to spark1.5.1 that's why I am
more concerned regarding it.
Regards
Pankaj
On 17 Nov 2015 23:38, "Shixiong Zhu"<EMAIL_ADDRESS>wrote:

Will this patch slowdown query parsing in case of concurrent requests?
I think so. Do you concern about the performance of parsing query? I
assume executing query dominates the time.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8357#issuecomment-157455774.

@pankajarora12 could you test in 1.5.1 and see if there is any performance regression?

@zsxwing - we ran into the same issue on our project, Apache Atlas here. I have looked up a few other references to this bug and this fix seemed clearer to me than others. I was planning to model the fix in this same manner. Just one question - why did you need to add a synchronized? Is it because it wasn't very clear whether the threading issue was fixed or not in SI-4929, or because you are clear that the threading issue still exists with the memory leak? In our case, we are a server side app, hence adding a synchronized could impact performance non-trivially. Any information you can provide would be of great help.

FYI we got rid of the parser combinator in Spark 2.0.


Remove unused environment variable PIP from tox.ini

Unused since b387e5e984f6fc593706e7fc51463924ac43a670.
Contributor checklist

[x] Provided the tests for the changes.
[ ] Gave a clear one-line description in the PR (that the maintainers can add to CHANGELOG.md on release). (n/a)
[x] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

AFAIK PIP env was used for Travis to show pip version in a build matrix:


[Azure Core] Centralised configuration API for internal client library configuration

We need to provide a centralised configuration API for all client libraries to make use of. This configuration API will make it possible for Java client libraries to pull in system settings, environment variables, application configuration files, etc in a consistent and cross-client-library fashion. It also removes the burden of each client library having to implement this individually, and finally, it helps to ensure that we can also have cross-language support for configuration.
This does not need to be a public API, it will only be used by service clients to configure themselves.
Two useful documents for reference (whilst this issue is being refined):

https://github.com/Azure/azure-sdk/pull/330/files
https://github.com/Azure/azure-sdk/pull/328/files

There are a few different things to consider:
1. Retrieving configurations
Configurations need to be retrievable from environment variables and run time parameters at minimum, additional locations such at configuration files may be supported in the future. The default order to find configurations should be run time parameters then environment variables, optionally this order may be configured.

[x] Retrieve configurations from required locations
[x] Be extensible to support additional configuration locations in the future
[x] Order of retrieval is configurable, or not required

2. Build clients using configurations
Clients should support using configurations during construction but allow for a consumer of the client to override these configurations with code. Sensible defaults should be used when a configuration and consumer setting is not passed. Additionally, clients should be able to take in a configurations object during construction to determine how it is constructed.

[ ] Use configurations during construction
[ ] Sensible defaults when a configuration is not set
[ ] Builders take a configurations object that determines construction

3. Additional requirements

[x] Log a message when a configuration is found in the run time parameters and environment variables
[x] Determine non-client defaults, such as logging and tracing configurations
[ ] Update documentation to explain the configurations that each client uses

Section 2, build clients using configurations, will be done on a client by client basis. #3732 will implement that for App Config.


Suggestion: Lookup should work with a link

~lookup should work even if ~lookup https://web.simple-mmo.com/user/view/323910 a link is used

Depending on how the new web app updates, this might be added.

If you have the link, the new web UI makes it easier to access and read than using lookup on discord. Will not implement


updated go-version

Updated .go-version file

If it is not necessary for editors or tools. We can remove the file.


Update known issues in release notes

Add recently discovered issues to the release notes.

/azp run mrtk_docs

/azp run mrtk_docs


Check for path-like objects rather than Path type, use os.fspath

This PR generally changes (e.g.) isinstance(filename, pathlib.Path) to isinstance(filename, os.PathLike), and uses os.fspath to convert it to (usually) str type.
(If it is vital these are always str, then should os.fsdecode be considered? bytes paths are not common, and only possible on some platforms).
If other path-like objects are used e.g. py.path used by the tmpdir pytest fixture, an error message is shown:

ValueError: can only read bytes or file-like objects with engine='scipy' or 'h5netcdf'

This PR allows other path-like objects to be used.
A few typing objects are also adjusted too.

Be aware there are file-like and path-like object terms used in the core Python glossary. In light of this, some "file-like" wordings may need to be adjusted, such as the error message described above. This can be done in this PR if anyone aggrees.

@martindurant exactly, os.PathLike just uses duck-typing, which fsspec matches.
This generally means you can't pass s3fs/gcsfs files into xr.open_dataset (from what I've tried so far).
In [32]: xr.open_dataset("s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr", engine="zarr")
Out[32]:
<xarray.Dataset>
Dimensions:         (feature_id: 5783, time: 367439)
Coordinates:
  * feature_id      (feature_id) int32 491 531<PHONE_NUMBER>04<PHONE_NUMBER>
    latitude        (feature_id) float32 ...
    longitude       (feature_id) float32 ...
  * time            (time) datetime64[ns] 1979-02-01T01:00:00 ... 2020-12-31T...
Data variables:
    crs             |S1 ...
    inflow          (time, feature_id) float64 ...
    outflow         (time, feature_id) float64 ...
    water_sfc_elev  (time, feature_id) float32 ...
Attributes:
    Conventions:                  CF-1.6
    TITLE:                        OUTPUT FROM WRF-Hydro v5.2.0-beta2
    code_version:                 v5.2.0-beta2
    featureType:                  timeSeries
    model_configuration:          retrospective
    model_output_type:            reservoir
    proj4:                        +proj=lcc +units=m +a=6370000.0 +b=6370000....
    reservoir_assimilated_value:  Assimilation not performed
    reservoir_type:               1 = level pool everywhere
    station_dimension:            lake_id

In [33]: xr.open_dataset(fsspec.open("s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr"), engine="zarr")
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<ipython-input-33-76e10d75e2c2> in <module>
----> 1 xr.open_dataset(fsspec.open("s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr"), engine="zarr")

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/api.py in open_dataset(filename_or_obj, engine, chunks, cache, decode_cf, mask_and_scale, decode_times, decode_timedelta, use_cftime, concat_characters, decode_coords, drop_variables, backend_kwargs, *args, **kwargs)
    493
    494     overwrite_encoded_chunks = kwargs.pop("overwrite_encoded_chunks", None)
--> 495     backend_ds = backend.open_dataset(
    496         filename_or_obj,
    497         drop_variables=drop_variables,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/zarr.py in open_dataset(self, filename_or_obj, mask_and_scale, decode_times, concat_characters, decode_coords, drop_variables, use_cftime, decode_timedelta, group, mode, synchronizer, consolidated, chunk_store, storage_options, stacklevel)
    797     ):
    798
--> 799         filename_or_obj = _normalize_path(filename_or_obj)
    800         store = ZarrStore.open_group(
    801             filename_or_obj,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/common.py in _normalize_path(path)
     21 def _normalize_path(path):
     22     if isinstance(path, os.PathLike):
---> 23         path = os.fspath(path)
     24
     25     if isinstance(path, str) and not is_remote_uri(path):

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/core.py in __fspath__(self)
     96     def __fspath__(self):
     97         # may raise if cannot be resolved to local file
---> 98         return self.open().__fspath__()
     99
    100     def __enter__(self):

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/core.py in open(self)
    138         been deleted; but a with-context is better style.
    139         """
--> 140         out = self.__enter__()
    141         closer = out.close
    142         fobjects = self.fobjects.copy()[:-1]

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/core.py in __enter__(self)
    101         mode = self.mode.replace("t", "").replace("b", "") + "b"
    102
--> 103         f = self.fs.open(self.path, mode=mode)
    104
    105         self.fobjects = [f]

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/spec.py in open(self, path, mode, block_size, cache_options, compression, **kwargs)
   1007         else:
   1008             ac = kwargs.pop("autocommit", not self._intrans)
-> 1009             f = self._open(
   1010                 path,
   1011                 mode=mode,

~/dev/dask-playground/env/lib/python3.9/site-packages/s3fs/core.py in _open(self, path, mode, block_size, acl, version_id, fill_cache, cache_type, autocommit, requester_pays, **kwargs)
    532             cache_type = self.default_cache_type
    533
--> 534         return S3File(
    535             self,
    536             path,

~/dev/dask-playground/env/lib/python3.9/site-packages/s3fs/core.py in __init__(self, s3, path, mode, block_size, acl, version_id, fill_cache, s3_additional_kwargs, autocommit, cache_type, requester_pays)
   1824
   1825         if "r" in mode:
-> 1826             self.req_kw["IfMatch"] = self.details["ETag"]
   1827
   1828     def _call_s3(self, method, *kwarglist, **kwargs):

KeyError: 'ETag'

"s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr" is a directory, right? You cannot open that as a file, or maybe there is no equivalent key at all (because s3 is magic like that).
No, you should not be able to do this directly - zarr requires a path which fsspec can turn into a mapper, or an instantiated mapper.
To make a bare mapper (i.e., dict-like):
m = fsspec.get_mapper("s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr", ...)

or you could use zarr's FSMapper meant specifically for this job.

"s3://noaa-nwm-retrospective-2-1-zarr-pds/lakeout.zarr" is a directory, right? You cannot open that as a file

Yeah correct. I oversimplified this from the problem I actually cared about, since of course zarr is not a single file that can be fsspec.open'd in the first place, and the zarr engine is doing some magic there when passed the plain string.
Here's a more illustrative example:
In [1]: import xarray as xr

In [2]: import fsspec

In [3]: import os

In [4]: url = "s3://noaa-nwm-retrospective-2-1-pds/model_output/1979/197902010100.CHRTOUT_DOMAIN1.comp"  # a netCDF file in s3

In [5]: f = fsspec.open(url)

In [6]: f
Out[6]: <OpenFile 'noaa-nwm-retrospective-2-1-pds/model_output/1979/197902010100.CHRTOUT_DOMAIN1.comp'>

In [7]: isinstance(f, os.PathLike)
Out[7]: True

In [8]: s3f = f.open()

In [9]: s3f
Out[9]: <File-like object S3FileSystem, noaa-nwm-retrospective-2-1-pds/model_output/1979/197902010100.CHRTOUT_DOMAIN1.comp>

In [10]: isinstance(s3f, os.PathLike)
Out[10]: False

In [11]: ds = xr.open_dataset(s3f, engine='h5netcdf')

In [12]: ds
Out[12]:
<xarray.Dataset>
Dimensions:         (time: 1, reference_time: 1, feature_id: 2776738)
Coordinates:
  * time            (time) datetime64[ns] 1979-02-01T01:00:00
  * reference_time  (reference_time) datetime64[ns] 1979-02-01
  * feature_id      (feature_id) int32 101 179<PHONE_NUMBER>803<PHONE_NUMBER>
    latitude        (feature_id) float32 ...
    longitude       (feature_id) float32 ...

Attributes: (12/18)
    TITLE:                      OUTPUT FROM WRF-Hydro v5.2.0-beta2
    featureType:                timeSeries
    proj4:                      +proj=lcc +units=m +a=6370000.0 +b=6370000.0 ...
    model_initialization_time:  1979-02-01_00:00:00
    station_dimension:          feature_id
    model_output_valid_time:    1979-02-01_01:00:00
    ...                         ...
    model_configuration:        retrospective
    dev_OVRTSWCRT:              1
    dev_NOAH_TIMESTEP:          3600
    dev_channel_only:           0
    dev_channelBucket_only:     0
    dev:                        dev_ prefix indicates development/internal me...

In [13]: ds = xr.open_dataset(f, engine='h5netcdf')
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-13-de834ca911b4> in <module>
----> 1 ds = xr.open_dataset(f, engine='h5netcdf')

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/api.py in open_dataset(filename_or_obj, engine, chunks, cache, decode_cf, mask_and_scale, decode_times, decode_timedelta, use_cftime, concat_characters, decode_coords, drop_variables, backend_kwargs, *args, **kwargs)
    493
    494     overwrite_encoded_chunks = kwargs.pop("overwrite_encoded_chunks", None)
--> 495     backend_ds = backend.open_dataset(
    496         filename_or_obj,
    497         drop_variables=drop_variables,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in open_dataset(self, filename_or_obj, mask_and_scale, decode_times, concat_characters, decode_coords, drop_variables, use_cftime, decode_timedelta, format, group, lock, invalid_netcdf, phony_dims, decode_vlen_strings)
    384     ):
    385
--> 386         filename_or_obj = _normalize_path(filename_or_obj)
    387         store = H5NetCDFStore.open(
    388             filename_or_obj,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/common.py in _normalize_path(path)
     21 def _normalize_path(path):
     22     if isinstance(path, os.PathLike):
---> 23         path = os.fspath(path)
     24
     25     if isinstance(path, str) and not is_remote_uri(path):

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/core.py in __fspath__(self)
     96     def __fspath__(self):
     97         # may raise if cannot be resolved to local file
---> 98         return self.open().__fspath__()
     99
    100     def __enter__(self):

AttributeError: 'S3File' object has no attribute '__fspath__'

Because the plain fsspec.OpenFile object has an __fspath__ attribute (but calling it raises an error), it causes xarray.backends.common._normalize_path to fail.
Because the s3fs.S3File object does not have an __fspath__ attribute, normalize_path doesn't try to call os.fspath on it, so the file-like object is able to be passed all the way down into h5netcdf, which is able to handle it.
Note though that if I downgrade xarray to 0.19.0 (last version before this PR was merged), I still can't use the plain `fssspec.OpenFile` object successfully. It's not xarray's fault anymore—it gets passed all the way into h5netcdf—but h5netcdf also tries to call `fspath` on the `OpenFile`, which fails in the same way.
In [1]: import xarray as xr

In [2]: import fsspec

In [3]: xr.__version__
Out[3]: '0.19.0'

In [4]: url = "s3://noaa-nwm-retrospective-2-1-pds/model_output/1979/197902010100.CHRTOUT_DOMAIN1.comp"  # a netCDF file in s3

In [5]: f = fsspec.open(url)

In [6]: xr.open_dataset(f.open(), engine="h5netcdf")
Out[6]:
<xarray.Dataset>
Dimensions:         (time: 1, reference_time: 1, feature_id: 2776738)
Coordinates:
  * time            (time) datetime64[ns] 1979-02-01T01:00:00
  * reference_time  (reference_time) datetime64[ns] 1979-02-01
  * feature_id      (feature_id) int32 101 179<PHONE_NUMBER>803<PHONE_NUMBER>
    latitude        (feature_id) float32 ...
    longitude       (feature_id) float32 ...

Attributes: (12/18)
    TITLE:                      OUTPUT FROM WRF-Hydro v5.2.0-beta2
    featureType:                timeSeries
    proj4:                      +proj=lcc +units=m +a=6370000.0 +b=6370000.0 ...
    model_initialization_time:  1979-02-01_00:00:00
    station_dimension:          feature_id
    model_output_valid_time:    1979-02-01_01:00:00
    ...                         ...
    model_configuration:        retrospective
    dev_OVRTSWCRT:              1
    dev_NOAH_TIMESTEP:          3600
    dev_channel_only:           0
    dev_channelBucket_only:     0
    dev:                        dev_ prefix indicates development/internal me...

In [7]: xr.open_dataset(f, engine="h5netcdf")
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/file_manager.py in _acquire_with_cache_info(self, needs_lock)
    198             try:
--> 199                 file = self._cache[self._key]
    200             except KeyError:

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/lru_cache.py in __getitem__(self, key)
     52         with self._lock:
---> 53             value = self._cache[key]
     54             self._cache.move_to_end(key)

KeyError: [<class 'h5netcdf.core.File'>, (<OpenFile 'noaa-nwm-retrospective-2-1-pds/model_output/1979/197902010100.CHRTOUT_DOMAIN1.comp'>,), 'r', (('decode_vlen_strings', True), ('invalid_netcdf', None))]

During handling of the above exception, another exception occurred:

AttributeError                            Traceback (most recent call last)
<ipython-input-7-e6098b8ab402> in <module>
----> 1 xr.open_dataset(f, engine="h5netcdf")

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/api.py in open_dataset(filename_or_obj, engine, chunks, cache, decode_cf, mask_and_scale, decode_times, decode_timedelta, use_cftime, concat_characters, decode_coords, drop_variables, backend_kwargs, *args, **kwargs)
    495
    496     overwrite_encoded_chunks = kwargs.pop("overwrite_encoded_chunks", None)
--> 497     backend_ds = backend.open_dataset(
    498         filename_or_obj,
    499         drop_variables=drop_variables,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in open_dataset(self, filename_or_obj, mask_and_scale, decode_times, concat_characters, decode_coords, drop_variables, use_cftime, decode_timedelta, format, group, lock, invalid_netcdf, phony_dims, decode_vlen_strings)
    372
    373         filename_or_obj = _normalize_path(filename_or_obj)
--> 374         store = H5NetCDFStore.open(
    375             filename_or_obj,
    376             format=format,

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in open(cls, filename, mode, format, group, lock, autoclose, invalid_netcdf, phony_dims, decode_vlen_strings)
    176
    177         manager = CachingFileManager(h5netcdf.File, filename, mode=mode, kwargs=kwargs)
--> 178         return cls(manager, group=group, mode=mode, lock=lock, autoclose=autoclose)
    179
    180     def _acquire(self, needs_lock=True):

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in __init__(self, manager, group, mode, lock, autoclose)
    121         # todo: utilizing find_root_and_group seems a bit clunky
    122         #  making filename available on h5netcdf.Group seems better
--> 123         self._filename = find_root_and_group(self.ds)[0].filename
    124         self.is_remote = is_remote_uri(self._filename)
    125         self.lock = ensure_lock(lock)

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in ds(self)
    187     @property
    188     def ds(self):
--> 189         return self._acquire()
    190
    191     def open_store_variable(self, name, var):

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/h5netcdf_.py in _acquire(self, needs_lock)
    179
    180     def _acquire(self, needs_lock=True):
--> 181         with self._manager.acquire_context(needs_lock) as root:
    182             ds = _nc4_require_group(
    183                 root, self._group, self._mode, create_group=_h5netcdf_create_group

~/.pyenv/versions/3.9.1/lib/python3.9/contextlib.py in __enter__(self)
    115         del self.args, self.kwds, self.func
    116         try:
--> 117             return next(self.gen)
    118         except StopIteration:
    119             raise RuntimeError("generator didn't yield") from None

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/file_manager.py in acquire_context(self, needs_lock)
    185     def acquire_context(self, needs_lock=True):
    186         """Context manager for acquiring a file."""
--> 187         file, cached = self._acquire_with_cache_info(needs_lock)
    188         try:
    189             yield file

~/dev/dask-playground/env/lib/python3.9/site-packages/xarray/backends/file_manager.py in _acquire_with_cache_info(self, needs_lock)
    203                     kwargs = kwargs.copy()
    204                     kwargs["mode"] = self._mode
--> 205                 file = self._opener(*self._args, **kwargs)
    206                 if self._mode == "w":
    207                     # ensure file doesn't get overriden when opened again

~/dev/dask-playground/env/lib/python3.9/site-packages/h5netcdf/core.py in __init__(self, path, mode, invalid_netcdf, phony_dims, **kwargs)
    978                     self._preexisting_file = mode in {"r", "r+", "a"}
    979                     self._h5py = h5py
--> 980                     self._h5file = self._h5py.File(
    981                         path, mode, track_order=track_order, **kwargs
    982                     )

~/dev/dask-playground/env/lib/python3.9/site-packages/h5py/_hl/files.py in __init__(self, name, mode, driver, libver, userblock_size, swmr, rdcc_nslots, rdcc_nbytes, rdcc_w0, track_order, fs_strategy, fs_persist, fs_threshold, fs_page_size, page_buf_size, min_meta_keep, min_raw_keep, locking, **kwds)
    484                 name = repr(name).encode('ASCII', 'replace')
    485             else:
--> 486                 name = filename_encode(name)
    487
    488             if track_order is None:

~/dev/dask-playground/env/lib/python3.9/site-packages/h5py/_hl/compat.py in filename_encode(filename)
     17     filenames in h5py for more information.
     18     """
---> 19     filename = fspath(filename)
     20     if sys.platform == "win32":
     21         if isinstance(filename, str):

~/dev/dask-playground/env/lib/python3.9/site-packages/fsspec/core.py in __fspath__(self)
     96     def __fspath__(self):
     97         # may raise if cannot be resolved to local file
---> 98         return self.open().__fspath__()
     99
    100     def __enter__(self):

AttributeError: 'S3File' object has no attribute '__fspath__'

The problem is that OpenFile doesn't have a read or seek method, so h5py doesn't think it's a proper file-like object and tries to fspath it here: https://github.com/h5py/h5py/blob/master/h5py/_hl/files.py#L509

So I may just be misunderstanding what an fsspec.OpenFile object is supposed to be (it's not actually a file-like object until you .open() it?). But I expect users would be similarly confused by this distinction.

Yeah, I guess I expected OpenFile to, well, act like an open file. So maybe this is more of an fsspec interface issue?
I'll open a separate issue for improving the UX of this in xarray though. I think this would be rather confusing for new users.


Regression: Points.events.data is no longer fired from the data setter

🐛 Bug
While investigating affinder CI failures, I found that #5967 broke affinder's tests. (btw if you've never heard of git bisect run you should try it! 😍) The reason is this line which removes the data event emitter from the setter but doesn't replace it with the new style.
It seems to have been simply missed. @melonora was this intentional? I can't imagine the reason for it other than an oversight! 😅
Fix incoming.
To Reproduce
import napari
import numpy as np

layer = napari.layers.Points(np.random.random((5, 3)))

layer.events.data.connect(lambda ev: print(ev))

print('adding a single point')
layer.add(np.random.random((1, 3)))  # prints ok

print('setting data')
layer.data = np.random.random((8, 3))  # nothing happens

print('done')

Result:
adding a single point
Event
setting data
done

Expected result (and result before 96516dad057aa8d31328f889ce73d40a800eb67d):
adding a single point
Event
setting data
Event
done

Environment
napari main / napari 0.4.18.

oops :astonished:, this I believe is indeed an oversight. For sure it was not intentional.


Update README.md

If you have time, please help me.
https://github.com/Issa-N/AttractingContributors-FavoriteBook.git
Thanks.

Please pull request again because of the confilct.
So, I cant' merge


PipelineRuns finished as Succeeded change to PipelineRunTimeout after some time

Properly closed PipelineRuns, set as 'Succeeded', should stay in this Status till deletion.
After some time (I don't know exactly how long it takes now) PR changes its status to Failed(PipelineRunTimeout). At the same time, all TaskRuns remain correctly set as Succeeded.
pr1   1 hour ago    5m56s      Succeeded
pr2   2 hours ago   26m34s     Succeeded
pr3   5 hours ago   3m59s      Succeeded
pr4   2 days ago    9h39m28s   Failed(PipelineRunTimeout)
pr5   2 days ago    5h3m2s     Failed(PipelineRunTimeout)

PR describe Message:
PipelineRun "pr3" failed to finish within "2h0m0s"

I set the timeout to 2 hours

Kubernetes version:
1.27

clientVersion:
  buildDate: "2023-05-17T14:20:07Z"
  compiler: gc
  gitCommit: 7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647
  gitTreeState: clean
  gitVersion: v1.27.2
  goVersion: go1.20.4
  major: "1"
  minor: "27"
  platform: linux/amd64
kustomizeVersion: v5.0.1
serverVersion:
  buildDate: "2023-04-14T20:40:28Z"
  compiler: gc
  gitCommit: abfec7d7e55d56346a5259c9379dea9f56ba2926
  gitTreeState: clean
  gitVersion: v1.27.1-eks-2f008fe
  goVersion: go1.20.3
  major: "1"
  minor: 27+
  platform: linux/amd64

Tekton Pipeline version:

Client version: 0.31.0
Chains version: v0.16.0
Pipeline version: v0.47.0
Triggers version: v0.24.0
Dashboard version: v0.35.0
Operator version: v0.67.0

@zalejus this is fixed in v0.47.1 or later

Adding a reference to the PR if anyone runs into this in future - https://github.com/tektoncd/pipeline/pull/6622


Project setup in IntelliJ working for you?

Hey everyone!
Are you able to pull/push and run the (test) application?
@jmueller95
for me it worked fine without the .iml file you provided. This is the one i use:

Network-Analysis-Tool.txt
had to change file extension

The test works for me!
Ok, I can take the iml file down again, I guess something was wrong in my IDE.

Working

Yup.
Suggestion of mine: since five people will be working on the project I suggest that we should settle on some coding conventions. Else this will become messy pretty soon ;)


Windows Support: Hadoop fails to load Loaded Libraries

Windows tries to load the native hadoop binaries which do not exist.  It tries to load them from a wide range of folder because Windows returns Windows-<Version> from os.name.  After changing this to use 'Windows' as the os.name for all Windows versions and the addition of the native libraries to /nativelib/Windows_amd64, HadoopNative correctly loads the libraries from the temp files that are created.  Unfortunately, when loadAllCodecs runs it subsequently fails with the following error:
java.lang.RuntimeException: failed to load Hadoop native library
        at com.facebook.presto.hadoop.HadoopNative.requireHadoopNative(HadoopNative.java:60)
        at com.facebook.presto.hadoop.TestHadoopNative.testCodecRoundTrip(TestHadoopNative.java:51)
Caused by: java.lang.RuntimeException: native snappy library not available: SnappyCompressor has not been loaded.
        at org.apache.hadoop.io.compress.SnappyCodec.checkNativeCodeLoaded(SnappyCodec.java:68)
        at org.apache.hadoop.io.compress.SnappyCodec.getDecompressorType(SnappyCodec.java:189)
        at com.facebook.presto.hadoop.HadoopNative.loadAllCodecs(HadoopNative.java:73)
        at com.facebook.presto.hadoop.HadoopNative.requireHadoopNative(HadoopNative.java:55)

Changing HadoopNative.requireHadoopNative to create a temporary directory and making loadLibrary copy the embedded files with the original names into this directory allows the libraries to correctly loaded.

Are Hadoop native libraries for Windows available anywhere? I did a quick search and couldn't find them.

For sure. Hadoop runs on Windows (HDInight), is available to be installed on Windows machine (Hortonworks), and there at instructions for building Hadoop with native libraries on Windows (http://www.srccodes.com/m/p/article/38/build-install-configure-run-apache-hadoop-2.2.0-microsoft-windows-os).

Did this answer your question?  I'm interested in getting Presto to work on Windows, but could use feedback so that the correct changes are made.

Do you know if the pre-built native libraries are available from Hortonworks or another official source? None of us have a Windows machine.

Yes, there are prebuilt native libraries available. I'll send the link when I get back from vacation.

On Feb 20, 2015, at 7:43 AM, David Phillips<EMAIL_ADDRESS>wrote:
Do you know if the pre-built native libraries are available from Hortonworks or another official source? None of us have a Windows machine.
—
Reply to this email directly or view it on GitHub.

It is available from Hortonworks at: http://hortonworks.com/products/releases/hdp-2-windows/

The pre-built binaries are missing bzip2 support which cause the NativeLibraryChecker to fail.  They will need to be re-built to support bzip2 or the code that calls NativeLibraryChecker will need to take over the check and special case Windows.

Either is fine.  bzip2 isn't widely used anyway.


Draft: Use new AWS sdk code

Still in progress, left here as reference to see more complex scenarios than the one written in tests for the items in https://github.com/grafana/grafana-aws-sdk/issues/28

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Can't load plugins in desktop

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
I can't load plugins using the desktop version.
To Reproduce
Steps to reproduce the behavior:

open desktop version
extras > plugins > add > https://jgraph.github.io/drawio/src/main/webapp/plugins/number.js
close app and reopen

Expected behavior
The numbers plugin should be loaded
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 13.0.3

Desktop (please complete the following information):

OS: [e.g. iOS] OSx
Browser [e.g. chrome, safari] desktop
Version [e.g. 22] 13.0.3

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Duplicate of https://github.com/jgraph/drawio-desktop/issues/276

oh man, i don't know how i didn't find that. sorry for the bother

It happens a lot because there are two projects, no biggie.


CustomCapability - C# - Invalid parameter passed to C runtime function.

Hi,
Regarding the RPC communication with the NT Service, C# version:
This is not a big issue, in the sense that the sample UWP app seems to be working correctly with the NT service through static dll.
However, every time I start the app, in DebugView I see this message prompted two times by the UWP app process:

Invalid parameter passed to C runtime function.

Any idea about what does cause it? Should I worry about it at all?
[ OS Win10 1709 (16299.192), Visual Studio 2017, provided solution and Debug - x64 configuration only]

Haven't heard from the feature team, but I cannot reproduce this. My DebugView doesn't display anything other than "Failed to initialize."


[Android] TypeError on SignaturePad

On Android, I am unable to use this extension due to the following type error when I try to register, then use the element in an Angular application.
ERROR Error: Uncaught (in promise): TypeError: Could not load view for: DrawingPad.TypeError: Cannot read property 'SignaturePad' of undefined
TypeError: Could not load view for: DrawingPad.TypeError: Cannot read property 'SignaturePad' of undefined

I am not referencing a property called SignaturePad anywhere in my application. Any clue what might cause this?

The same here.

I was able to fix this by executing tns update.
You can also try this https://bradmartin.net/2016/07/20/ahhh-this-nativescript-plugin-doesnt-work/
or by moving
import {registerElement} from 'nativescript-angular/element-registry'; registerElement('DrawingPad', () => require('nativescript-drawingpad').DrawingPad);
form specific component to main.ts file. In component you just use import {DrawingPad} from 'nativescript-drawingpad';
Hope this helps.

Demo seems to be working, @kobi84 comment should help. As the error indicates the native lib did not build into your executable.


split feed action into two

Rather than have one feed action that can service both Message Hub and Kafka instances, let's split it into two separate actions, one for each type of instance.
This will make not only the naming of the actions clear (MessageHubFeed and KafkaFeed) but it will also make describing the parameters much simpler as well.

Resolved by #33


Generic Module XML Setting Stops Working After Blank Value

Bug Report
System Information

Operating System - Windows 11 Pro 64-bit
AMP version and build date - v20220707.1, built 07/07/2022 03:00
Which AMP release stream you're using - Nightly

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms

What are you trying to do?
Put a blank value in a setting for Space Engineers.

What are you expecting to happen?
I should be able to then put a new value in.

What is actually happening? ('Nothing' is not an acceptable answer!)
AMP is not putting any value in the XML file and the line is getting split across two lines. Here is an example after blanking the MOTD input and then putting "TEST". After both actions, the XML shows the same below. I have also tried manually placing the MessageOfTheDay open/close on the same line manually and AMP produces the same output.

  <MessageOfTheDay>
  </MessageOfTheDay>

Reproduction
Create a Space Engineers instance, update, remove a value from any input, view the SpaceEngineers-Dedicated.cfg file.

Fixed - don't reference the text node, reference the node that contains it and AMP can now set its value properly.


Release dialogflow v0.8.2

This pull request was generated using releasetool.

Release is at https://github.com/googleapis/nodejs-dialogflow/releases/tag/v0.8.2

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Remove redunand test mongoid config

This silences the following warnings during test runs:
W, [2016-04-12T14:14:36.334219 #26791]  WARN -- : MONGODB | Unsupported client option 'max_retries'. It will be ignored.
W, [2016-04-12T14:14:36.334368 #26791]  WARN -- : MONGODB | Unsupported client option 'retry_interval'. It will be ignored.

:+1:


What about older SAC versions?

Can an older SAC version still in support be used after Jan 2020 on Windows 7 until it's natural end of support date, such as 1909, for instance?

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

ID: 48fc8b7e-ec90-1bf8-77b6-326d0c6edf0a
Version Independent ID: f9c1e74f-001e-e8f7-edc1-2d3a8efa8f5c
Content: Windows 7 end of support and Office 365 ProPlus
Content Source: DeployOffice/windows-7-support.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@lkuhn65  -- No version of Office 365 ProPlus will be supported on Windows 7 after 14 January 2020. But we won't block you from installing "older" versions (for example, Version 1902 of Semi-Annual Channel) on Windows 7. They just won't be supported.


Define Locale Override, Momentjs

Hi (again),
On the pages where I am using react-kronos, I get the following warning from Momentjs:
http://momentjs.com/guides/#/warnings/define-locale/
I'm using 1.2.3 of react-kronos and 2.13.0 of Momentjs
I assume this is something related to react-kronos' use of Momentjs? Perhaps you can confirm.
All the best,
Anders

Should be fixed in 1.2.4!


telink: b92: update ble lib

Update 2m/3m/3.5m flash protect interface .

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_telink
https://github.com/telink-semi/hal_telink/commit/34700f71d3c69326595484c631853ca61fabf0af (develop)
https://github.com/telink-semi/hal_telink/commit/445c736548c2cd0a0f2553942fcc569f93072b72 (develop_b92_prot)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.

OK, i have updated the latest west.yml and are waiting for CI completion. Thank you !


Concepts, like on the Golang track

Hi 👋 ,
I've got some minor contributions to the golang track. And was wondering as PHP does not have publicly accessible concepts if this is something being worked on, and if there is a place to track this effort?
I noticed a top-level concepts folder, so assume it is in the works.

It is in the works, just very slowly. :)

Is there a place where people that would like to help out can go and see how to help progress this?

Would be happy to help support this.

It's finally showing some results: https://github.com/exercism/php/commits/main

There are 6 now released in beta, closing this as done


Add lint checks to project

You can also run these commands locally

make pretty to format code
make validate to validate the code

See the Checks tab for some of the issues that have been detected.

In which branch should I make the formatting changes?

In which branch should I make the formatting changes?

If you've already got a branch that you're working on you can just use that. I know it might be not be easy to create a new branch now and then have to do a merge the one you're currently using, but up to you.

Closing this since the changes ended up being made in #6


Denmark marriage tool update - Content change request

Supersedes #2520
Trello card

125-denmark-marriage-tool-update-content-change-request

Description
This story is linked to this Zendesk ticket.
Updates outcomes copy where a citizen lives in Uk or in Denmark according to this document.
Factcheck
denmark-marriage-tool-update-content-change-request
Expected changes (1)

URL on GOV.UK

Before

After

Expected changes (2)

URL on GOV.UK

Before

After

It looks as though "outcome_ceremonies_in_denmark_when_residing_in_uk_or_denmark.govspeak.erb" could be simplified quite a bit. It looks as though there are quite a few conditionals that can be combined.

I've added a couple of comments but I don't think any of them should prevent this change from being merged. Good work, @pmanrubia!

I've just spotted a couple of changes to the artefacts that I'm not sure about.
The Google Doc linked from the Trello card says that the same sex outcomes for residents of the UK and Denmark should be identical to their opposite sex counterparts, with an additional "synonyms of civil partnership" section at the top. However, there are additional differences between them in this branch.
Residents of UK
The same sex outcomes all include the "Fees" table where the opposite sex don't. Is this correct?
diff test/artefacts/marriage-abroad/denmark/uk/partner_british/{opposite,same}_sex.txt
diff test/artefacts/marriage-abroad/denmark/uk/partner_local/{opposite,same}_sex.txt
diff test/artefacts/marriage-abroad/denmark/uk/partner_other/{opposite,same}_sex.txt

# Single diff representing the changes in the three files above:

> ## Fees
>
> Service | Fee
> -|-
> Issuing a CNI, Nulla Osta or equivalent | £65
>

Residents of Denmark
The same sex outcomes all include the address of the British embassy in Copenhagen, while the opposite sex outcomes have a link to "Make an appointment at the embassy". Is this correct?
diff test/artefacts/marriage-abroad/denmark/ceremony_country/partner_british/{opposite,same}_sex.txt
diff test/artefacts/marriage-abroad/denmark/ceremony_country/partner_local/{opposite,same}_sex.txt
diff test/artefacts/marriage-abroad/denmark/ceremony_country/partner_other/{opposite,same}_sex.txt

# Single diff representing the changes in the three files above:

< [Make an appointment at the embassy in Copenhagen.](https://www.consular-appointments.service.gov.uk/fco/#!/british-embassy-copenhagen/notice-of-marriage-or-civil-partnership/slot_picker)
---
> $A
> British Embassy Copenhagen
> Kastelsvej 36-40
> DK-2100  Copenhagen
> Denmark
> $A
>
> $C
> Consular / passport enquiries<EMAIL_ADDRESS>> Telephone : +45 35 44 52 00
>
> Email<EMAIL_ADDRESS>>
> [British Embassy Copenhagen - opening hours](https://www.gov.uk/government/world/organisations/british-embassy-copenhagen/office/british-embassy)
> $C

LGTM 👍
FCO are v keen for first available deploy if poss.

Superseded by https://github.com/alphagov/smart-answers/pull/2653


feat: reuse context for different chat session history

Issue description
So i am creating a question and answer bot i dont want to add my previous chat messages to session, due to adding my context limit get exausted
Expected Behavior
i want the ability to not saving anything to session or ability to clear session contexts
Actual Behavior
after some chat it quicky exhausted and throwing error
Steps to reproduce
after some chat it quicky exhausted and throwing error
My Environment

Dependency
Version

Operating System

CPU
Intel i9 / Apple M1

Node.js version
x.y.zzz

Typescript version
x.y.zzz

node-llama-cpp version
x.y.zzz

Additional Context
No response
Relevant Features Used

[ ] Metal support
[X] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
Yes, I have the time, and I know how to start.

@sooraj007 It'll be possible to do this in the next beta version

Until the next beta is ready, you can use this workaround.
The workaround consists of clearing the context sequence and creating a new ChatSession with the messages you want to have in it:

Relevant for the 3.0.0-beta.1 version

import {fileURLToPath} from "url";
import path from "path";
import {LlamaModel, LlamaContext, LlamaChatSession} from "node-llama-cpp";

const __dirname = path.dirname(fileURLToPath(import.meta.url));

const model = new LlamaModel({
    modelPath: path.join(__dirname, "models", "dolphin-2.1-mistral-7b.Q4_K_M.gguf")
});
const context = new LlamaContext({
    model,
    contextSize: Math.min(4096, model.trainContextSize)
});
const contextSequence = context.getSequence();
const session = new LlamaChatSession({
    contextSequence
});

const q1 = "Hi there, how are you?";
console.log("User: " + q1);

const a1 = await session.prompt(q1);
console.log("AI: " + a1);

const q2 = "Summerize what you said";
console.log("User: " + q2);

const a2 = await session.prompt(q2);
console.log("AI: " + a2);

// clear the context sequence
await contextSequence.eraseContextTokenRanges([start: 0, end: contextSequence.nextTokenIndex]);

// create a new chat session on the same context sequence
const newSession = new LlamaChatSession({
    contextSequence,
    conversationHistory: [] // restore your conversation history without the last message that you want to discard
});

@giladgd thanks , its works , please create a discord group if you got time it would be great. and node-llama-cpp is awesome great work.

@sooraj007 It's a great idea :)
I'll do that soon after I finish developing the next version


Tkakar/cat 673 create builder for seg mask

Creates the epic-builder to update the vitessce configuration of a parent dataset for the provided segmentation mask.

@NickAkhmetov not sure why the tests are failing, I removed the parts for epic_builder for now, is there a special setup that is needed?

@NickAkhmetov thanks for reviewing, do you think the Github workflow should be updated to use prod requirements?
Also, are you okay with providing the epic_entity as a parameter (json or url), so that I clean the unused code?

providing the epic_entity as a parameter (json or url)

I think that approach makes sense, i.e. updating the script's handling of this to match the other parameters?

I think that approach makes sense, i.e. updating the script's handling of this to match the other parameters?
@NickAkhmetov thanks for reviewing. I thought I added this, did I miss anything?

@tkakar You did add it to the script! I was replying to this piece of your previous message:

Also, are you okay with providing the epic_entity as a parameter (json or url), so that I clean the unused code?

I believe we should be able to provide the epic_entity json via the portal-ui back-end, i.e. extending the logic here to fetch the EPIC entity if an epic URL parameter is provided, same as the parent parameter: https://github.com/hubmapconsortium/portal-ui/blob/main/context/app/routes_browse.py#L121-L135


Project overlap, differences from lighttiger2505/lab

Hi, thanks for working on this gitlab CLI project! I find it very useful, especially the forking and git wrapping features.
I'm curious how the design or roadmap of this project compares to lighttiger2505/lab? I'd like to contribute to one of these projects but I'm not sure which one. Thanks again.
BTW, I opened a similar ticket in the other project: https://github.com/lighttiger2505/lab/issues/65

Sorry for the late reply here I've been battle with a nasty cold all weekend.
I can outline some of the differences and where this tool is headed.
Differences
Feature wise it looks like lighttiger's lab supports some operations with project variables and projects users that we don't
Over here it looks like we have forking, a CI pipeline interface, and job tracing.
Design
As @lighttiger2505 mentions, we have different command structure. We strictly use lab <noun> <verb> whereas lighttigers tool uses lab <verb> or lab <noun> as needed.
zaquestion/lab was initially designed to be a hub replacement for gitlab. We used to follow the conventions there much closer, but have since decided to move in our own direction. Firstly with our strict command structure, then by supporting origin or upstream remote schemes, now going beyond hub features to support more features like the CI pipeline interface which wouldn't make sense in hub.
zaquestion/lab is fundamentally workflow tool. We don't add features just to cover the API. We add them to support and improve our cli workflows.
Roadmap
For 1.0 there are a few things we'd like to do. The next "big thing" is an MR review workflow for the CLI. An outline can be seen here: https://github.com/zaquestion/lab/projects -- I see you're interested in supporting comments on MRs (and issues) thats going to be an early part of this project covered in https://github.com/zaquestion/lab/issues/83
We will also be removing the hub/git wrapper aspect of the project and moving to use git extensions in https://github.com/zaquestion/lab/issues/217
We may change the lab mr create syntax https://github.com/zaquestion/lab/issues/127
The config structure is very likely to change, at least to support https://github.com/zaquestion/lab/issues/151

Thanks for the detailed overview! Hopefully I can contribute in the near future.

It would be nice to mention the existance of lighttiger2505/lab in the README.md together with the differences.
And why you don't work together to produce an even more feature complete tool, because both have features that the other doesn't and that's a pity !

@varac what would detailing differences between the tools in the readme serve to achieve? I'm open to referencing lighttiger2505/lab in something like a similar tools section and evwn indicating briefly why one might prefer his their tool to this one, but that's about it.
No reason not to work together really, currently the tools take different approaches and I believe both started as hobby projects meant to serve the founders objectives.
lighttiger highlights some of the advantages of labs command structure (cobra),  it's possible lab could support both syntaxes with minimal work and functionality could be consolidated.
This is appealling to me as it would serve to unify the communities and pave way to the ultimate goal of becoming an officially regconized tool with GitLab

what would detailing differences between the tools in the readme serve to achieve?

I.e., if I would have known that this project currently doesn't support multiple instances (#151), and lighttiger2505/lab does, I would have taken lighttiger2505/lab. However, I'm super happy about lab ci trace, and there might be other features that are better in this project, so it would be just good for users to know what to choose.

I'm open to referencing lighttiger2505/lab in something like a similar tools section and even indicating briefly why one might prefer their tool to this one, but that's about it.

That's fine.

This is appealling to me as it would serve to unify the communities and pave way to the ultimate goal of becoming an officially regconized tool with GitLab

Woooo ! That would be really great !


Add modal weighting to NFC-HOA monochromatic

#77 added the ability of modal weighting of NFC-HOA orders to the time domain driving function of NFC-HOA.
This cannot be easily added to the current monochromatic implementation of NFC-HOA, but should be able to be added after implementing the new NFC-HOA structure as proposed in #63.

Added in #187.


Updating the URL to Anaconda in Installation notes

The url link to download Anaconda seems broken. This change does not require a new patch release and has no change to the code, only docs.

Good eye @behnam2015, thank you!


Connected to the DB in the heavens

Owner

I can add this file to the ignore, and just send the content in the chat 👍🏼


API for SAH to Call

Create an API endpoint that will be used by SAH to send user-specific notifications.
SAH will send PID to the API, along with message data.

This issue is being closed due to platform migration and may be revisited at a later date.


password prompt is broken in python3

[*] : Username : xxx
[*] : Password : Traceback (most recent call last):
  File "lynda-dl.py", line 433, in <module>
    main()
  File "lynda-dl.py", line 267, in main
    passwd  = getpass.getpass(prompt=password)
  File "/Users/xxx/xxx/lynda-dl/lynda/_getpass.py", line 36, in getpass
    password += c.decode('utf-8')
AttributeError: 'str' object has no attribute 'decode'

@cipy will fix it ASAP. thanks for the report.

@cipy its fixed now i 'm closing this issue. have a look.


Badge Position - Bottomleft

I would like to know how to place the bagde on the bottom left of the screen. Using the data-badge="bottomleft"
Tried something like:
Vue.use(VueReCaptcha, {    siteKey: '',   loaderOptions: {     renderParameters: {       badge: 'bottomleft'     }   } })
https://developers.google.com/recaptcha/docs/invisible#render_param

Duplicate to #154.


Update quotas.md

Corrected the quota based on internal discussion

@craigshoemaker
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

These changes were made in an internal PR. #please-close


Display logs from why-did-my-tx-fail for failed txs

:tada: This issue has been resolved in version 1.233.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add a wiki: Granblue Fantasy Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://granblue.fandom.com/wiki/Granblue_Fantasy_Wiki
Link to destination (independent) wiki: https://gbf.wiki/Main_Page

This has been added and will be released in v1.3.0


Add the TCP_FUNCTION_BLK and TCP_FUNCTION_ALIAS socket options

For FreeBSD only
Description
These two socket options are used to get and set a socket's TCP stack, on FreeBSD only.
Sources
https://man.freebsd.org/cgi/man.cgi?query=tcp
https://github.com/freebsd/freebsd-src/blob/976e1d36be688166e140cbaded01d433c61e6d47/sys/netinet/tcp.h#L229
Checklist

[x] Relevant tests in libc-test/semver have been updated
[x] No placeholder or unstable values like *LAST or *MAX are
included (see #3131)
[x] Tested locally (cd libc-test && cargo test --target mytarget);
especially relevant for platforms that may not be checked in CI

The error looks unrelated to my change.  For one thing, it was a Linux build that failed.  For another, this is the error:
rustc-LLVM ERROR: Cannot select: 0x7fe87eb15000: f32,ch = load<(load (s16) from %ir.0), anyext from f16> 0x7fe87eb15a10, 0x7fe87eaf6540, undef:i64, src/fmt/float.rs:238:30
  0x7fe87eaf6540: i64,ch = CopyFromReg 0x7fe87eabb468, Register:i64 %0
    0x7fe87eb15af0: i64 = Register %0
  0x7fe87eb155b0: i64 = undef
In function: _ZN4core3fmt5float50_$LT$impl$u20$core..fmt..Debug$u20$for$u20$f16$GT$3fmt17h9203c7e9bc0be64fE
error: could not compile `core` (lib)


Ash Wed collect special case

On Ash Wednesday, the collect displays twice:
https://www.commonprayeronline.org/en/daily-readings/2022-03-02
Feels like an off by one error.
I'll also note with amusement that I started to file an issue about the Ash Wed collect run amok! A project like this, it seems, is likely to attract "issues" that are not about your code, but about interpretation of the tradition. Case in point:
The Ash Wed collect continues throughout Lent in commonprayeronline/daily-readings. I thought this might be a bug. I see a rubric about this on BCP 217, but it seems ambiguous. Checking Hatchett, this ambiguity seems frustratingly purposeful: the 1928 BCP specified until Palm Sunday. But the earliest use of the the rubric (in 1892, following Scottish 1637) was only meant to cover the Thurs/Fri/Sat following Ash Wed. Why did the 1979 book refrain from being clear on this issue?

Thanks, Todd.
In terms of logic it's displaying once as the Collect of the Day, and once as the seasonal collect for Lent. The collects should be deduplicated, I've probably just messed that process up.
I agree with your sense that a plain reading of the 1979 BCP does not support the traditions of using the collects for Ash Wednesday and for the First Sunday of Advent as "seasonal collects" repeated on every day of those seasons, but know that I receive requests for them all the time! The rubrics in the 1962 Canadian BCP (which is the other one with which I'm very familiar) is much more helpful: This Collect is to be repeated every day after the other Collects in Advent, until Christmas Eve. and This Collect is to be read every day in Lent after the Collect appointed for the day until Holy Week. These are virtually identical to the 1662 rubrics, which suggests it's another of our American departures from that tradition that has, perhaps, been re-imported (or simply persisted).