VPN Routing not working

Hello Maintainers,
I deployed recently a test instance of the wg-access-server. I did exactly the following steps that are documentated on the documentation: "https://www.freie-netze.org/wg-access-server/deployment/2-docker-compose/".

Is it possible to use my own DNS IP's with the env variable WG_DNS_UPSTREAM, because my resolv.conf contains <IP_ADDRESS> which is the local dns-resolver of ubuntu.

I can connect to the wireguard server, but i can only ping the wireguard server. It seems, that traffic is not routed correctly out of the container.

OS: Ubuntu 20.04 LTS
Package: Wireguard installed via "apt install wireguard"
docker-compose.yml
version: "3.0"
services:
  wg-access-server:
    image: ghcr.io/freifunkmuc/wg-access-server:latest
    container_name: wg-access-server
    cap_add:
      - NET_ADMIN
    sysctls:
      net.ipv6.conf.all.disable_ipv6: 0
      net.ipv6.conf.all.forwarding: 1
    volumes:
      - ./wg_data:/data
    #   - "./config.yaml:/config.yaml" # if you have a custom config file
    environment:
      - WG_ADMIN_USERNAME=admin
      - WG_ADMIN_PASSWORD=<censored>
      - WG_WIREGUARD_PRIVATE_KEY=<censored>
      - WG_LOG_LEVEL=info
      - WG_PORT=8080
      - WG_EXTERNAL_HOST=<censored>
      - WG_DISABLE_METADATA=false
      - WG_WIREGUARD_INTERFACE=wg0
      - WG_WIREGUARD_PORT=5938
      - WG_VPN_CIDR=<IP_ADDRESS>/24
      - WG_VPN_CIDRV6=0
      - WG_IPV4_NAT_ENABLED=true
      - WG_IPV6_NAT_ENABLED=true
      - WG_VPN_GATEWAY_INTERFACE=ens160
      - WG_VPN_ALLOWED_IPS=<IP_ADDRESS>/0
      - WG_DNS_ENABLED=true
      - WG_DNS_UPSTREAM=<IP_ADDRESS>,<IP_ADDRESS>
    ports:
      - "8080:8080/tcp"
      - "5938:5938/udp"
    devices:
      - "/dev/net/tun:/dev/net/tun"

docker logs
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="starting wireguard server on :5938" file="main.go:112"
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="wireguard VPN network is <IP_ADDRESS>/24" file="main.go:126"
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="starting dns server on :53 with upstreams: <IP_ADDRESS>,<IP_ADDRESS>" file="server.go:33"
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="storing data in SQL backend sqlite3" file="contracts.go:73"
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="serving website from ./website/build" file="website_router.go:37"
wg-access-server    | time="2022-01-12T16:55:53Z" level=info msg="web ui listening on :8080" file="main.go:214"
wg-access-server    | time="2022-01-12T16:56:08Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=Info grpc.service=proto.Server grpc.start_time="2022-01-12T16:56:08Z" grpc.time_ms=0.708 span.kind=server system=grpc trace.id=6c339c00-6d07-44fd-85f6-0946ae56ff88
wg-access-server    | time="2022-01-12T16:56:08Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=ListDevices grpc.service=proto.Devices grpc.start_time="2022-01-12T16:56:08Z" grpc.time_ms=0.653 span.kind=server system=grpc trace.id=fdcb70fb-42ca-4e30-939b-a12a6f9f370d
wg-access-server    | time="2022-01-12T16:56:13Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=AddDevice grpc.service=proto.Devices grpc.start_time="2022-01-12T16:56:13Z" grpc.time_ms=4.784 span.kind=server system=grpc trace.id=a639de18-2e8d-41d9-a2bd-34134ea29614
wg-access-server    | time="2022-01-12T16:56:14Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=ListDevices grpc.service=proto.Devices grpc.start_time="2022-01-12T16:56:14Z" grpc.time_ms=0.667 span.kind=server system=grpc trace.id=db32c264-54a3-4189-b3b2-89a60abb9c67
wg-access-server    | time="2022-01-12T16:56:38Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=ListDevices grpc.service=proto.Devices grpc.start_time="2022-01-12T16:56:38Z" grpc.time_ms=0.694 span.kind=server system=grpc trace.id=fd6f8c5d-4ce9-44bf-a864-6ce0b04411d0
wg-access-server    | time="2022-01-12T16:57:08Z" level=info msg="finished unary call with code OK" file="options.go:220" grpc.code=OK grpc.method=ListDevices grpc.service=proto.Devices grpc.start_time="2022-01-12T16:57:08Z" grpc.time_ms=0.715 span.kind=server system=grpc trace.id=c6d5f9b2-15c9-483d-ac11-773a9cf6e86c
wg-access-server    | time="2022-01-12T16:57:35Z" level=warning msg="DNS lookup failed for upstream <IP_ADDRESS>,<IP_ADDRESS>: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host" file="server.go:122"wg-access-server    | time="2022-01-12T16:57:35Z" level=error msg="failed lookup record with error: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host\n;; opcode: QUERY, status: NOERROR, id: 2650\n;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0\n\n;; QUESTION SECTION:\n;vault.bitwarden.com.\tIN\t A\n" file="server.go:76"
wg-access-server    | time="2022-01-12T16:57:35Z" level=warning msg="DNS lookup failed for upstream <IP_ADDRESS>,<IP_ADDRESS>: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host" file="server.go:122"wg-access-server    | time="2022-01-12T16:57:35Z" level=error msg="failed lookup record with error: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host\n;; opcode: QUERY, status: NOERROR, id: 4743\n;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0\n\n;; QUESTION SECTION:\n;sdk.split.io.\tIN\t A\n" file="server.go:76"
wg-access-server    | time="2022-01-12T16:57:35Z" level=warning msg="DNS lookup failed for upstream <IP_ADDRESS>,<IP_ADDRESS>: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host" file="server.go:122"wg-access-server    | time="2022-01-12T16:57:35Z" level=error msg="failed lookup record with error: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host\n;; opcode: QUERY, status: NOERROR, id: 54036\n;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0\n\n;; QUESTION SECTION:\n;www.msftconnecttest.com.\tIN\t A\n" file="server.go:76"
wg-access-server    | time="2022-01-12T16:57:35Z" level=warning msg="DNS lookup failed for upstream <IP_ADDRESS>,<IP_ADDRESS>: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host" file="server.go:122"wg-access-server    | time="2022-01-12T16:57:35Z" level=error msg="failed lookup record with error: dial udp: lookup <IP_ADDRESS>,<IP_ADDRESS>: no such host\n;; opcode: QUERY, status: NOERROR, id: 27188\

Regarding the DNS lookup, try to specify only one IP (e.g. WG_DNS_UPSTREAM=<IP_ADDRESS>)

Can you show us a generated client config (omit sensitive values)?

WG_VPN_GATEWAY_INTERFACE=ens160

This looks suspicious. You are running it inside Docker, and as far as I know, inside the container the default interface is always named eth0.
Try leaving this variable undefined to let the automated detection take care of it, and see if it works then.
And yeah, for the DNS upstream, it looks like the splitting when reading from environment variables doesn't work.
I'll look into a fix for that, but as a workaround you could either only specify one upstream address, or pass them as two command arguments:
command: wg-access-server serve --dns-upstream=<IP_ADDRESS> --dns-upstream=<IP_ADDRESS>

Thx for the fast answer. So misunderstanding on my site. I expected that the variable "WG_VPN_GATEWAY_INTERFACE" needs the physical Interface.
I'm Happy 👍
My actually Configuration that is working now. ->
docker-compose.yml
version: "3.0"
services:
  wg-access-server:
    image: ghcr.io/freifunkmuc/wg-access-server:latest
    container_name: wg-access-server
    cap_add:
      - NET_ADMIN
    sysctls:
      net.ipv6.conf.all.disable_ipv6: 0
      net.ipv6.conf.all.forwarding: 1
    volumes:
      - ./wg_data:/data
    #   - "./config.yaml:/config.yaml" # if you have a custom config file
    environment:
      - WG_ADMIN_USERNAME=admin
      - WG_ADMIN_PASSWORD=<censored>
      - WG_WIREGUARD_PRIVATE_KEY=<censored>
      - WG_LOG_LEVEL=info
      - WG_PORT=8080
      - WG_EXTERNAL_HOST=<censored>
      - WG_DISABLE_METADATA=false
      - WG_WIREGUARD_INTERFACE=wg0
      - WG_WIREGUARD_PORT=5938
      - WG_VPN_CIDR=<IP_ADDRESS>/24
      - WG_VPN_CIDRV6=0
      - WG_IPV4_NAT_ENABLED=true
      - WG_IPV6_NAT_ENABLED=true
      - WG_VPN_GATEWAY_INTERFACE=eth0
      - WG_VPN_ALLOWED_IPS=<IP_ADDRESS>/0
      - WG_DNS_ENABLED=true
      - WG_DNS_UPSTREAM=<IP_ADDRESS>
    ports:
      - "8080:8080/tcp"
      - "5938:5938/udp"
    devices:
      - "/dev/net/tun:/dev/net/tun"

Good to hear 😄  We're always happy to help. Don't forget to close this issue


Artifact type authoring

Address #8 by referencing existing OCI Artifact docs.
A more detailed option would be to pull in the OCI Artifact Authors doc, adjusting manifest.config.mediaType with manifest.artifactType.
I'd duggest we keep this more simplistic option for now, and we can add more details that don't impact the implementation of the spec at a later date.

This sets the expectation that the version WILL change in the future, and developers SHOULD code for that scenario.

What do we think that looks like in practice?

What do we think that looks like in practice?

@jonjohnsonjr, please see #42


Unable to cross-compile ARM plugin for RPI Buster  - fail 12 OpenVINO build failed

Hi :wave: I'm trying to cross-compile the ARM CPU plugin for Raspberry Pi Buster 32-bit using this tutorial https://github.com/openvinotoolkit/openvino_contrib/wiki/How-to-build-ARM-CPU-plugin#approach-1-build-opencv-openvino-and-the-plugin-using-pre-configured-dockerfile-cross-compiling-the-preferred-way.
The compilation got through the OpenCV successfully but stopped at OpenVino with the error:
make: *** [Makefile:163: all] Error 2
Last lines of the output:
cc1plus: warning: unrecognized command line option '-Wno-pessimizing-move'
cc1plus: warning: unrecognized command line option '-Wno-redundant-move'
arm-linux-gnueabihf-g++ -o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/libarm_compute_graph.so -Wl,--no-undefined -shared /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/DataLayerVisitor.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/Graph.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/GraphBuilder.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/GraphContext.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/GraphManager.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/INode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/INodeVisitor.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/PassManager.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/Tensor.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/TypeLoader.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/Utils.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/Workload.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/algorithms/TopologicalSort.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/BackendRegistry.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/detail/CrossLayerMemoryManagerHelpers.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/detail/ExecutionHelpers.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/frontend/Stream.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/frontend/SubStream.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/DepthConcatSubTensorMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/GroupedConvolutionMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/InPlaceOperationMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/MutatorUtils.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/NodeExecutionMethodMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/NodeFusionMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/SplitLayerSubTensorMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/mutators/SyntheticDataTypeMutator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ActivationLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ArgMinMaxLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/BatchNormalizationLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/BoundingBoxTransformLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ChannelShuffleLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ConcatenateLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ConstNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ConvolutionLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DeconvolutionLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DepthToSpaceLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DepthwiseConvolutionLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DequantizationLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DetectionOutputLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DetectionPostProcessLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/DummyNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/EltwiseLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FlattenLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FullyConnectedLayer.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FusedConvolutionBatchNormalizationNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FusedConvolutionBatchNormalizationWithPostOpsNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FusedConvolutionWithPostOpNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/FusedDepthwiseConvolutionBatchNormalizationNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/GenerateProposalsLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/InputNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/L2NormalizeLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/NormalizationLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/NormalizePlanarYUVLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/OutputNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PReluLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PadLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PermuteLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PoolingLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PrintLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/PriorBoxLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/QuantizationLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ROIAlignLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ReductionLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ReorgLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ReshapeLayer.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/ResizeLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/SliceLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/SoftmaxLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/SplitLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/StackLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/nodes/StridedSliceLayerNode.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/printers/DotGraphPrinter.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/NEON/NEDeviceBackend.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/NEON/NEFunctionFactory.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/NEON/NENodeValidator.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/NEON/NESubTensorHandle.os /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/src/graph/backends/NEON/NETensorHandle.os -L/arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty -L. -lpthread -ldl -larm_compute
arm-linux-gnueabihf-ar rc /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/libarm_compute_test_framework.a /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/DatasetModes.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/Exceptions.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/Framework.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/ParametersLibrary.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/Profiler.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/TestFilter.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/Utils.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/command_line/CommonOptions.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/printers/JSONPrinter.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/printers/PrettyPrinter.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/printers/Printer.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/printers/Printers.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/instruments/Instruments.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/instruments/InstrumentsStats.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/instruments/SchedulerTimer.o /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/instruments/WallClockTimer.o
arm-linux-gnueabihf-ranlib /arm_cpu_plugin/openvino/build/build-modules/arm_plugin/thirdparty/tests/framework/libarm_compute_test_framework.a
scons: done building targets.
[ 36%] Built target arm_compute_static_libs
make: *** [Makefile:163: all] Error 2
+ fail 12 OpenVINO build failed. Stopping
+ [ 2 -lt 2 ]
+ retval=12
+ shift
+ echo OpenVINO build failed. Stopping
OpenVINO build failed. Stopping
+ exit 12

openvino_contrib branch: master
openvino_contrib commit: 663dce6c73fe38a9bc7e02512807e5390c87db83

Thanks in advance!

Please, provide the actual error message. From the logs we can just see that build fails, but don't see the reason

oh, sorry, let me get back to you with the error message.

Error message:
Traceback (most recent call last):
  File "/arm_cpu_plugin/openvino/src/frontends/onnx/tests/onnx_prototxt_converter.py", line 26, in <module>
    import onnx
  File "/usr/local/lib/python3.7/site-packages/onnx/__init__.py", line 10, in <module>
    from .onnx_cpp2py_export import ONNX_ML
ImportError: libstdc++.so.6: cannot open shared object file: No such file or directory
make[2]: *** [CMakeFiles/test_model_zoo.dir/build.make:825: ../bin/armv7l/Release/test_model_zoo/core/models/ir/add_abc.onnx] Error 1
make[1]: *** [CMakeFiles/Makefile2:145: CMakeFiles/test_model_zoo.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Please, add cmake -DENABLE_REQUIREMENTS_INSTALL=OFF to other build options.
 Stopping"

but still got the error.
Please, let me know if I'm doing something wrong.

Please, provide error message.
The original error message should have gone.

Traceback (most recent call last):
  File "/arm_cpu_plugin/openvino/src/frontends/onnx/tests/onnx_prototxt_converter.py", line 24, in <module>
    from docopt import docopt
ModuleNotFoundError: No module named 'docopt'
make[2]: *** [CMakeFiles/test_model_zoo.dir/build.make:825: ../bin/armv7l/Release/test_model_zoo/core/models/ir/add_abc.onnx] Error 1
make[1]: *** [CMakeFiles/Makefile2:144: CMakeFiles/test_model_zoo.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Install requirements from file https://github.com/openvinotoolkit/openvino/blob/master/src/frontends/onnx/tests/requirements.txt:
python3 -m pip install -r src/frontends/onnx/tests/requirements.txt

I can suggest to turn of ONNX frontend using -DENABLE_OV_ONNX_FRONTEND=OFF
It turned out that ONNX is not available for armv7l (see https://pypi.org/project/onnx/1.11.0/#files), while OV build tries to use such module unconditionally.

UPDATE:
I had a look once again to the issue, since you are using cross-compilation - what is the architecture?
If it's x86_64 I suppose onnx can be installed.
In any case - there is a fix with check for ONNX first before its usage https://github.com/openvinotoolkit/openvino/pull/13069

Yes, it's x86_64.
Thank you.


Dead UDP listeners

Your environment.

Version: 2.0.9

What happened?
UDP listener works in s.readLoop by PacketConnConfigs.
https://github.com/pion/turn/blob/371fc35851d91a885a0621b295f8e9a3ed6af2d2/server.go#L67-L87
Finish readLoop when p.ReadFrom return error.
After that the UDP listener doesn't work.
https://github.com/pion/turn/blob/371fc35851d91a885a0621b295f8e9a3ed6af2d2/server.go#L161-L187
Log message:
exit read loop on error: BadFormat for attribute/message: buffer length 1600 is less than 3498 (expected message size)

@jaesung9507 It seems like you are receiving a packet larger than the configured InboundMTU.
Try setting a larger InboundMTU in the config struct when creating the server with NewServer().
Can you give some details about your environment? Are you testing locally? Or do you have a network supporting Jumbo frames?

On a second thought: This is a configuration issue.
See also #204


php81: init at 8.1.0

Motivation for this change
PHP 8.1 release
Things done
xmlreader and tokenizer cannot be built currently. If someone has an idea would be nice. Looking later again into it

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Duplicate of #147411?

whoopsie :sweat_smile:

I'm looking for help on that, it doesn't build on my local machine, do you have any idea why?

I am unfortunately travelling until Thursday. I can Look then into it if the issue is still there

Sure!


fix(web-app): query refactor

validate json object before parsing, introduce pretty object strategy
Closes #223
Addresses JSON parsing issues on query, validates filter before using and introduces new serializing query strategy for objects ( ?obj[key1]=value1&obj[key2]=value2... instead of JSON.stringify(object) )
Testing / reviewing
Pull changes and run application, test that applying and clearing filters in components page works as expected, test navigating to the app with filters described on #223 or any other unexpected filter value and assert app does not break

@jdharvey-ibm we're using URLSearchParams in our implementation. We're trying to solve for having to read an object from the query, didn't find a whole lot of options online so Matt & I settled for the brackets rather than JSON.stringify. I can definitely revert back to the old way if desired or happy to jump on a call to discuss other possible strategies

Ah, I see the usage of URLSearchParams you mentioned. I think the changes you've made are headed in the right direction because they do break up the filters into separate parameters, but I think you can go even further and rely almost entirely on the URLSearchParams class for its handling of objects, arrays, iteration, value type coercion, modification, sorting, and serialization.
The only logic on top of that base functionality would then just need to be ensuring that the filter params are valid catalog filters, which could either be done through a utility function or an extension of the URLSearchParams class to include a 'validate' method that can be called to perform all of that validation.
We can definitely chat more on the side about this though if you'd like.

@mattrosno per our conv with @jdharvey-ibm yesterday we agreed not to make changes to the filter logic until we make the refactor, which we pushed out to next sprint so I took #223 out of the scope of v0.1 and will work on this next sprint

@mattrosno merged, Thanks!🙏

@francinelucca the code smell error: https://sonarcloud.io/project/issues?resolved=false&sinceLeakPeriod=true&types=CODE_SMELL&pullRequest=260&id=carbon-design-system_carbon-platform&open=AX9meF3lDu2tD1MhHatF

@francinelucca does https://github.com/carbon-design-system/carbon-platform/pull/420 need merged before this?

@francinelucca does #420 need merged before this?

either or, doesn't really matter

@francinelucca can you resolve these conflicts then we get this PR reviewed and hopefully merged? Since this was carryover from last sprint, would be great to get in this sprint.


Strange issue with end portal

If you use end portals for a world that doesn't have an end setup, this message gets spammed like crazy in console and the player just glitches on the dirt screen (like the empty background)
http://pastebin.com/UFJ291Mi

This was fixed by https://github.com/Multiverse/Multiverse-NetherPortals/pull/117 but in the latest dev build the issue returned (https://ci.onarandombox.com/job/Multiverse-NetherPortals/) any word on if this will be fixed? @FernFerret / @dumptruckman

Duplicate of https://github.com/Multiverse/Multiverse-NetherPortals/issues/104


Enforce read-side and write-side query structure

Describe your changes
The current tag db is too lenient on how the buffs get added to a formula. Some formulas are added to et:self while others to et:selfBuff. This makes the system hard to design as it needs to accommodate both possibilities. This PR enforces more structure on et: as follows.
On the read side:

Final query (value that includes all applicable contributions) reads from et:self,

self.final.atk yields the final.atk from character/weapon/artifact/etc,

Contribution from a particular sheet reads from et:*Buff with appropriate sheet:,

selfBuff.final.atk.sheet("Nahida") yields Nahida's contribution to self.final.atk.
On the write side:

Queries with sheet:undefined or sheet:static write to et:self,
Queries in a sheet write to et:selfBuff/teamBuff/notSelfBuff (i.e., et:*Buff),
Queries outside of a sheet never write to et:*Buff,

This structure allows the buff system to be design as
`self:` stat <= "determine contributions" <= `et:*Buff` entries

It however requires linkage from self: <= et:*Buff at all time, so we also add noTeamData in case there is no team member (and so src:dst: are unnecessary).
Issue or discord link
https://discord.com/channels/785153694478893126/1189329506842984570/1272737073522278570
Testing/validation
Unit tests are added to enforce write-side entries.
Checklist before requesting a review (leave this PR as draft if any part of this list is not done.)

[x] I have commented my code in hard-to understand areas.
[x] I have made corresponding changes to README or wiki.
[x] For front-end changes, I have updated the corresponding English translations.
[x] I have run yarn run mini-ci locally to validate format and lint.
[x] If I have added a new library or app, I have updated the deployment scripts to ignore changes as needed

One change to consumption is that individual contribution is read from *buff, instead of the previously self. If we need contribution from all selfBuff/teamBuff/notSelfBuff together, I can add a new read-side et: too.


feat: Allow redefinition of names in guppy modules

closes #307

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.68%. Comparing base (6698b75) to head (9a04f63).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #326      +/-   ##
==========================================
+ Coverage   92.67%   92.68%   +0.01%
==========================================
  Files          45       45
  Lines        5105     5100       -5
==========================================
- Hits         4731     4727       -4
+ Misses        374      373       -1

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


Investigate creating a common error type in Azure Core

REST API guideline recommends services to return errors in a standard format - https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#errorresponse--object
Investigate creating an error type in Azure Core that all services that return errors in this format can use.

This is a thing already in azure-core:
https://github.com/Azure/azure-sdk-for-python/blob/2f8f5072e510862dd9f0905a59eba16b53e6d5f6/sdk/core/azure-core/azure/core/exceptions.py#L108
Keeping this issue for testing

Confirmed OdataV4Error works


There is no annotaton file

Thanks for your excellent work！
When I run your generate_csv.py, I found there is no annotation file. Can you release it?

Hi, annotation file is generated by user, you can use the script.generate_frame funciton in Maya to generate it.


What format would you like to see added to NeuroConv?
We should be able to handle a directory of Tiff files that are single frames. This could be input either by a long list of files, or by the directory that contains these files. The current Tiff interface example clearly states that it is not meant to be used for a sequence of tiff frames: https://neuroconv.readthedocs.io/en/main/conversion_examples_gallery/imaging/tiff.html
Does the format have any documentation?
No response
Existing APIs for format
No response
Do you have any example files you are willing to share?
No response
Do you have any interest in helping implement the feature?
Yes.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Have you ensured this bug was not already reported?

needed by @ucscbrianlee

The question is should this take a folder_path of a list of file_paths? The reason we can use folder for ScanImage and Bruker is because they follow very well established name patterns plus other organizational metadata to know how to order the frames
Programatically (through NeuroConv), file_paths should make the most sense here, but I assume there are an awful lot of files since there not multi-page at all? So in the GUIDE that would likely be unmanageable (might even cause performance issues with too many paths selected)
UNLESS; we mandate that the file name patterns in the folder be consistent with natsort, and we just rely on that to order things sequentially

Hi Cody,
If it is helpful, here is the organization from the lab submitting data for our group.  They did 4 calcium imaging recordings in 4 folders with  names like this:
20230412_105024_948
20230412_105933_147
20230412_110428_559
20230412_110936_767
And in each folder there is about 480 files of TIFFs with names like this:
Time00000_ChannelFITC-Penta_Seq0000
Time00001_ChannelFITC-Penta_Seq0001.tiff
...
Time00478_ChannelFITC-Penta_Seq0478.tiff
Time00479_ChannelFITC-Penta_Seq0479.tiff
where each Tiff represents a timepoint capture

Those indeed are compliant with natsort; the question is still which is the better policy or user experience across/between the low-code solution vs. the desktop application? Letting the user have full control over the order of files in sequence, or always assuming natsort is able to order things correctly?

What if we require a folder and allow for an optional argument for specifying the order of the files? If that is not provided, we use natsort. We could also allow a user to define a key which is a python function used to sort the files.

Hi Ben and Cody,
I'm still very new to NWB files and apologize for this question. I am about to contact the lab that has these files, I was going to request that maybe they can reformat the many TIFFs into a single TIFF -is that the right thinking?
Thanks for any advisement, and all your work building these tools!

@ucscbrianlee that might work

Thanks!

Hi @bendichter ,
This might not be the appropriate ticket/place for this question, but I have a follow-up about this data.  I can open a new ticket/issue if that is best.
I met with Loic who created this data and he is going to collapse the TIFFs to a single TIFF.   The issue is that beyond his unique approach of gathering input data with individual images (I think that is the reason this ticket exists)  Loic also did some unique steps in the follow-up steps.
For the cell-mask, he didn't use the raw images in the TIFFS that capture changes in fluorescence overtime.  Instead, at the same time in these microscope slides he was performing a MERFISH experiment.  The MERLIN software produces a Cell Mask for that data (different images).  Loic did some complex transformation steps to take that Cell Mask, made for MERFISH Spatial Transcriptomic analysis, to map onto his much smaller field of view for these Calcium fluorescence changes over time images.   He had to crop off a lot of the larger MERFISH mask to fit to this Ca+ image space, and rotate it from tilt to fit these TIFFs of Ca+ fluoresence.
This is just to say there is a lot of unique data processing going on and a cell mask for these raw TIFFs do not map as one would expect for a regular Ca+ imaging experiment where segmentation was generated from the original raw images.
This makes layering the mask onto the NWB raw data a little misleading -I would think as a novice, but maybe not?  Can NWB allow layering of additional processing data and final analsysis data with some kind of "This is not as it appears" note?  This would be to say, Loic could maybe Loic layer what he has onto the raw TIFF that will be the source level, and add annotations like, "some manipulation will be required to fully relate these."   In fact, that was his request, that he could layer those two levels, the cell mask and analysis, and include what I think he called a 3x3 matrix transformation (don't quote me) that would allow people to know how to work with what he has. He said otherwise it could take many days for realignment of mask, that is  a complicated process.
OK, I might not have expressed this all very clearly, but I wanted to communicate it to best figure out next steps. That might be opening a new ticket with these questions?  Or maybe communicate back to Loic guidance with this info.   For instance, if it is totally fine in NWB to layer a mask that doesn't make inherit sense (without an additional '3x3 matrix transformation') maybe that is great, and Loic can go about just layering his mask and analysis on the raw TIFFs he will collapse to a single TIFF. I apologize for the length of this note.
Best,
Brian

I apologize for the length of this note.

No problem!

I can open a new ticket/issue if that is best.

There's some pretty rich stuff here; I'd recommend reposting the generic NWB related bits (not TIFF collapsing or NeuroConv specific parts) to the NWB helpdesk so that other people can benefit from hearing about all this
There's definitely some recommendations that can be made for the best data representation to communicate what's going on

Thank you for input, I'll create a ticket in the NWB helpdesk.
On Mon, Mar 18, 2024 at 3:42 PM Cody Baker @.***> wrote:

I apologize for the length of this note.
No problem!
I can open a new ticket/issue if that is best.
There's some pretty rich stuff here; I'd recommend reposting the generic
NWB related bits (not TIFF collapsing or NeuroConv specific parts) to the NWB
helpdesk https://github.com/NeurodataWithoutBorders/helpdesk/discussions
so that other people can benefit from hearing about all this
There's definitely some recommendations that can be made for the best data
representation to communicate what's going on
—
Reply to this email directly, view it on GitHub
https://github.com/catalystneuro/neuroconv/issues/718#issuecomment-2005176058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY2ZD4RCJ4I6L6GSHRFFOA3YY5UWDAVCNFSM6AAAAABC3ALDRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVGE3TMMBVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

WIP started on https://github.com/catalystneuro/roiextractors/pull/323


Visualize the mutational sites

Currently on the base-pair-probability matrix and probability unpaired heatmaps, we visualize the boundary between constant regions, pads, barcodes, and region of interest using lines. We can add a feature to highlight the location of mutations from wildtype on these graphs.

Done, just like colorbar, room for beautification if requested.


BUG: Two app files cant be contained in one project

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[ ] I want to work on this issue

let me help with this


No Jellyscrub preview images in webOS-client despite latest Update

Jellyscrub works for me in the normal web UI and on my Android client, but unfortunately it won't do it's magic in the webOS-client on my LG TV.
Somehow nicknsy and I thought we would have a fix for that with the latest update, which merged the pull request from @NeroPcStation , but it didn't do the trick for me.
I previously asked about this issue on reddit so I know that nicknsy can't do much more about that.
But I hope that there is someone else, who could help me with this problem and maybe someday I will be able to see the glory of Jellyscrub working on my TV.
FYI:
I use the webOS-client v 1.1.2 from LGs content store.
My TV is a LG OLED55CX9LA and runs webOS version 5.4.2-25.
And other Plugins like the Intro Skipper or Custom CSS, as well as the native chapter preview images from Jellyfin indeed do work on my webOS-client.

I've tested the fix from @NeroPcStation and can happily confirm it's working flawlessly for me. It's awesome how fast this problem was solved. Thank you very very much!
Do I need to close this issue now or shall I wait until it is merged into the main branch? @nicknsy

You can leave it open. Glad you got it working!


Connection name is not used in 'Manage' tab name

Azure Data Studio Version: 1.0.0
Steps to Reproduce:

Create a connection profile and include a name for the connection.

Right click on that server in OE and choose manage

Observe the title used in the tab is the host name rather than the connection name.

This is fixed in the latest insiders builds and will be included in the Oct stable release.


.Net: [Microsoft.SemanticKernel.Connectors.Memory.Postgres.PostgresDbClient] - ORDER BY DESC prevents usage of ivfflat index

Describe the bug
The current command prevents the usage of an index optimized for vector search in postgres. As someone mentioned the Issue is that postgres only supports ASC order index scans. I'm not sure if this is true as I can't find any documentation and I'm everything but a postgres expert. But changing the command to the second one provided made postgres to use the created index. The performance difference is huge from 30s down to 41ms for a database with 134'000 records and 1.2G in Size (with index 2.4G).
Important: Running both queries without the index do provide the same results thats why I'm confident that my adjustment is correct. The difference after creating the index is the result of the trade off between recall and performance which is intended to happen.
Any chance that an expert can look into that? Maybe the conclusion is that we then have to use our own custom postgres client implementation but if my adjustments are correct (similarity only should be inverted) it would be a huge improvement if it can be provided out of the box.
Source:
cmd.CommandText = @$"
                SELECT * FROM (SELECT {queryColumns}, 1 - (embedding <=> @embedding) AS cosine_similarity FROM {this.GetFullTableName(tableName)}
                ) AS sk_memory_cosine_similarity_table
                WHERE cosine_similarity >= @min_relevance_score
                ORDER BY cosine_similarity DESC
                Limit @limit";

Get the query plan used by postgres for the source query:
    EXPLAIN (ANALYZE, VERBOSE, BUFFERS)   SELECT * FROM
                (SELECT key, metadata, timestamp,  1 - (embedding <=> '[]') AS cosine_similarity
                FROM public."bger-gpt-3-5-turbo-v1"
                ) AS sk_memory_cosine_similarity_table
                WHERE cosine_similarity >= 0.7
                ORDER BY cosine_similarity DESC
               limit 5;

Query plan for the source query (uses Seq. Scan):
Limit  (cost=7013.81..7014.39 rows=5 width=249) (actual time=29643.922..29669.955 rows=5 loops=1)
  Output: "bger-gpt-3-5-turbo-v1".key, "bger-gpt-3-5-turbo-v1".metadata, "bger-gpt-3-5-turbo-v1"."timestamp", (('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector)))
  Buffers: shared hit=1054213 read=179346
  ->  Gather Merge  (cost=7013.81..11330.07 rows=36994 width=249) (actual time=29643.920..29669.950 rows=5 loops=1)
        Output: "bger-gpt-3-5-turbo-v1".key, "bger-gpt-3-5-turbo-v1".metadata, "bger-gpt-3-5-turbo-v1"."timestamp", (('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector)))
        Workers Planned: 2
        Workers Launched: 2
        Buffers: shared hit=1054213 read=179346
        ->  Sort  (cost=6013.78..6060.02 rows=18497 width=249) (actual time=29612.273..29612.275 rows=4 loops=3)
              Output: "bger-gpt-3-5-turbo-v1".key, "bger-gpt-3-5-turbo-v1".metadata, "bger-gpt-3-5-turbo-v1"."timestamp", (('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector)))
              Sort Key: (('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector))) DESC
              Sort Method: top-N heapsort  Memory: 28kB
              Buffers: shared hit=1054213 read=179346
              Worker 0:  actual time=29599.614..29599.617 rows=5 loops=1
                Sort Method: top-N heapsort  Memory: 25kB
                Buffers: shared hit=343340 read=58498
              Worker 1:  actual time=29602.116..29602.118 rows=5 loops=1
                Sort Method: top-N heapsort  Memory: 29kB
                Buffers: shared hit=344656 read=58594
              ->  Parallel Seq Scan on public."bger-gpt-3-5-turbo-v1"  (cost=0.00..5706.55 rows=18497 width=249) (actual time=8.585..29585.711 rows=43412 loops=3)
                    Output: "bger-gpt-3-5-turbo-v1".key, "bger-gpt-3-5-turbo-v1".metadata, "bger-gpt-3-5-turbo-v1"."timestamp", ('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector))
                    Filter: (('1'::double precision - ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector)) >= '0.7'::double precision)
                    Rows Removed by Filter: 979
                    Buffers: shared hit=1054102 read=179345
                    Worker 0:  actual time=2.433..29569.297 rows=42423 loops=1
                      Buffers: shared hit=343284 read=58498
                    Worker 1:  actual time=2.923..29576.258 rows=42602 loops=1
                      Buffers: shared hit=344601 read=58593
Query Identifier: -3047525361828273587
Planning Time: 0.125 ms
Execution Time: 29670.000 ms

Adjustment:
    cmd.CommandText = @$"
        SELECT
                {queryColumns},
                1 - (embedding <=> @embedding) AS cosine_similarity
        FROM {this.GetFullTableName(tableName)}
        WHERE (embedding <=> @embedding) <= (1 - @min_relevance_score)
        ORDER BY (embedding <=> @embedding) ASC
        Limit @limit";

Adjustment Query-Plan in Postgres using index:

    EXPLAIN (ANALYZE, VERBOSE, BUFFERS)    SELECT
       			metadata,
				1 - (embedding <=> '[]')
     			FROM public."bger-gpt-3-5-turbo-v1"
               WHERE embedding <=> '[]' <= (1 - 0.7)
                order by embedding <=> '[]'
               	limit 5;

Query plan for the adjustmend (using the index):
Limit  (cost=1052.20..1052.35 rows=5 width=202) (actual time=2.147..2.248 rows=5 loops=1)
  Output: metadata, (('1'::double precision - (embedding <=> '[]'::vector))
  Buffers: shared hit=311 read=313
  ->  Index Scan using "bger-gpt-3-5-turbo-v1_embedding_idx" on public."bger-gpt-3-5-turbo-v1"  (cost=1052.20..2387.85 rows=44392 width=202) (actual time=2.145..2.245 rows=5 loops=1)
        Output: metadata, ('1'::double precision - (embedding <=> '[]'::vector)), (embedding <=> '[]'::vector)
        Order By: ("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector)
        Filter: (("bger-gpt-3-5-turbo-v1".embedding <=> '[]'::vector) <= '0.3'::double precision)
        Buffers: shared hit=311 read=313
Query Identifier:<PHONE_NUMBER>086523602
Planning:
  Buffers: shared hit=1
Planning Time: 0.136 ms
Execution Time: 2.289 ms

Index used:
CREATE INDEX ON public."bger-gpt-3-5-turbo-v1" USING ivfflat ("embedding" vector_cosine_ops)
WITH (lists = 134);

To Reproduce
Steps to reproduce the behavior:

Create a sample database with at least 1000 - 100'000 dummy records (ivfflat only works when dataset is large enough)
Do a memory recall => Query embedding
Wait 30s
Create a ivfflat index like above for the corresponding vector operation (similarity in this case)
Do a memory recall => Query embedding
Wait again 30s
Check plans using EXPLAIN => Recognize that index is not used
Adjust the query as provided above (second one)
Do a memory recall =>Query embedding
Wait 40ms
Check plans using EXPLAIN => See that the index now is used
Drop the index
Do a memory recall with the adjusted query as provided above => Query embedding
Wait 30s
Check plans using EXPLAIN => See that the Seq. Scan. is the issue as after dropping the index the adjusted query takes now the same amount of time as the one in the source

Expected behavior
Either a hint in the documentation that the query has to be tweeked to the needs or a default implementation that can make use of ivfflat index.
Platform

OS: Azure Database for PostgreSQL flexible server
IDE: DBeaver Enterprise 23.0.0
Language: C#
Source: PostgresDbClient

Additional context
I've have removed the vector as it would just clutter the whole description. If access is required hit me up in a PM and I try my best to provide access to the database in question.

It's still an issue. Currently I overcome this with a custom implementation.

Closing as we have new memory abstractions and will be obsoleting the old ones in the future.


[Test failure] Cancels_OnlySlow

Error message
Expected: False
But was:  True

Stack trace
   at Azure.Search.Documents.Tests.AsyncEventExtensionsTests.Cancels_OnlySlow() in /Users/runner/work/1/s/sdk/search/Azure.Search.Documents/tests/Batching/AsyncEventExtensionsTests.cs:line 450

https://dev.azure.com/azure-sdk/public/_build/results?buildId=572950&view=ms.vss-test-web.build-test-results-tab&runId=14102406&resultId=100472&paneView=debug

Timing-based tests are the worst. For this, I will just increase the "slow test" delay a little and hope that helps.
/cc @tg-msft

Still flaky https://dev.azure.com/azure-sdk/public/_build/results?buildId=630141&view=ms.vss-test-web.build-test-results-tab&runId=15139896&resultId=110779&paneView=debug

@tg-msft can you please take a look at this class of timing-related issues with batching?

Hasn't failed in a while, closing.


No english support for "a/an" or for pluralization

Currently the code just works with replacement, so replacing Hero Point with e.g. Antihero Points will cause sentences like "Reroll using a Antihero Point", using 'a' rather than the more correct 'an'.  Similarly, pluralization could be wrong if a user uses e.g. 'Benny' which becomes 'Bennys' rather than 'Bennies'.
I think the solution for this needs to be three settings:  simple singular, singular with indefinite article, and plural.
default to

Hero Point
`a Hero Point
Hero Points

and then expect e.g.

Antihero Point
an Antihero Point
Antihero Points

Sure, it's triple the amount of effort for users, but it's quick and only has to be done once.

Thanks for the suggestion. I've redesigned the settings and replacement logic to support this 🎉


ID not found

Hi,
I'm using your library to work with a custom parser, but for only a specific page (attached you have the full HTML) I have a strange behaviour.
Library seems unable to find the ID "buy-now-button" even if is present in the DOM
$dom = new Dom();

$dom->loadStr($htmlStr);
$button = $dom->find('#buy-now-button')[0];

$button is always empty.
Tested on PHP 7.4
I'm doing something wrong?
Thanks and regards.
Marco
page.html.zip

I am getting the same error.
php8.


Fix typo in warning

Thanks! Could you add a CHANGELOG entry please?

@probablyup Done!

Thank you so much for helping us improve styled-components! Based on our Community Guidelines every person that has a PR of any kind merged is offered an invitation to the styled-components organization—that is you right now!
Should you accept, you'll get write access to the main repository. (and a fancy styled-components logo on your GitHub profile!) You'll be able to label and close issues, merge pull requests, create new branches, etc. We want you to help us out with those things, so don't be scared to do them! Make sure to read our contribution and community guidelines, which explains all of this in more detail. Of course, if you have any questions just let me know!


SQLite/PGLite not fully compatible with NextJS

Firstly, not sure if this is something that Electric can resolve or if I should direct this to NextJS/Turbopack maintainers.
I've been successfully using ElectricSQL sqlite with NextJS and webpack. The build times and HMR are getting really slow in my project so I tried migrating to Turbopack. This is failing to build.
Also, I tried to use PGLite with and without Turbopack. It is not working within NextJS either way.
I've added a repo to reproduce these issues here: https://github.com/stratospark/turbopack-test

I've added an issue to the NextJS repo in case they have more clues: https://github.com/vercel/next.js/issues/66005

Turbopack maintainers found a probable cause and are working on a fix: https://github.com/vercel/next.js/issues/66005#issuecomment-2129250567
That would leave the pglite/webpack option the main thing to resolve at the moment.

👋 we've been working the last month on a rebuild of the Electric server over at a temporary repo https://github.com/electric-sql/electric-next/
You can read more about why we made the decision at https://next.electric-sql.com/about
We're really excited about all the new possibilities the new server brings and we hope you'll check it out soon and give us your feedback.
We're now moving the temporary repo back here. As part of that migration we're closing all the old issues and PRs. We really appreciate you taking the time to investigate and report this issue!


Brad/fix 8103 usability and errors ingestion notebook

Description
Developer Experience/Missing Steps

Add install dependencies
Add instructions to get Pinecone and OpenAI keys
Add environment variable loading that works with hosted notebooks
Add info/code to for deleting indexes on subsequent runs (for Pinecone Starter accounts)

Errors

Replaced PyMuPDF from Llama Hub with vanilla PyMuPDF package to avoid errors from fitz, frontend and Starlette packages

Fixes #8103
Type of Change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[X] I stared at the code and made sure it makes sense
[X] Notebook runs as expected

Suggested Checklist:

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

Thanks for catching that. Fixed the index_name.
I switched from the llama_hub loader because it was the cause of the errors I noted in the bug report.
To use from llama_hub.file.pymu_pdf.base import PyMuPDFReader in the original code, we have to install the llama-hub package. That's fine, but then when we run the code:

First it throws an error that the fitz package is not installed.
When fitz is installed and we run the code again, we get the error about frontend not being installed.
When frontend is installed, starlette throws errors that it cannot find the static/ folder

So the original code seems to be using fitz, but pulling in a bunch of other dependencies. By installing PyMuPDF at the beginning, we fitz and we can just use it directly.
It does remove one reference to our ecosystem, but it's a very minor one that doesn't relate to the core of the tutorial. So I figured it was a reasonable tradeoff.

Makes sense, thanks for the explanation!


random java.lang.NumberFormatException error with programmed position list

We are using pycromanager to program micromanager to do multi-dimensional acquisition and running into some randomly occurring error related to programmed position list and perhaps formatting issue with scientific notation.
Here’s the workflow:
We have a position list of 800 positions defined by x,y. It is initially created interactively by the micro-manager ‘create grid’ function. Then we start our python script. For every 16 positions, the program autofocuses on one of the positions, and applies the z-height found by autofocus to all the 16 positions. Then it creates a sub-position list of only those 16 positions, now with x, y, z defined, and then triggers acquisition.
There are multiple occasions that the script ran fine until somewhere down the 800 position list that micromanager will give this error randomly and not able to acquire:
java.lang.NumberFormatException: For input string: ".E4"
It looks like it’s something to do with conversion of string with scientific notation to number. The x, y position list does contain numbers >10,000, while the z height is usually around 3000. But we don’t understand how this error just occurs randomly for certain positions. We don't have a way to systematically reproduce the error. Not sure if this is micromanager issue or pycromanager issue. We would like to seek advice on how to fool-proof the code to prevent this error.
Our code:
`    numsubtile=16;
# get position list
xyStage = mmcore.get_xy_stage_device();
zStage = mmcore.get_focus_device();
posList=mmstudio.positions().get_position_list(); #get master position list
numpos = posList.get_number_of_positions()

ROInum=1;
for i in range(int(numsubtile/2-1)-1, numpos, numsubtile):
    msp=posList.get_position(i); # get position list
    ztemp=msp.get(zStage); # get z stage
    z=ztemp.get1_d_position(); # get z height
    xytemp=msp.get(xyStage); # get xy stage
    x=xytemp.get2_d_position_x(); # get x position
    y=xytemp.get2_d_position_y();  # get y position

    #move_stage_to_specific_XY_location
    mmcore.set_xy_position(x,y);

    #move_stage_to_specific_Z_location
    mmcore.set_position(z);

    #autofocus
    AfM=mmstudio.get_autofocus_manager();
    AfMM=AfM.get_autofocus_method();
    astart=time.time(); # autofocus start time
    AfMM.full_focus();
    aend=time.time(); # autofocus end time

    #get_z_position after autofocus
    new_z=mmcore.get_position();
    print('New z height after autofocusing:'+str(new_z));

    #apply new position to all tiles within ROI
    for j in range(i-(int(numsubtile/2-1)-1), i+(numsubtile-int(numsubtile/2)+2)):
        msp_each=posList.get_position(j);
        ztemp_each=msp_each.get(zStage);
        ztemp_each.set1_d_position(zStage, new_z);

    #make a new position list of a sublist
    pos_sublist=bridge.construct_java_object('org.micromanager.PositionList');
    for j in range(i-(int(numsubtile/2-1)-1), i+(numsubtile-int(numsubtile/2)+2)):
        msp_each=posList.get_position(j);
        pos_sublist.add_position(msp_each);`

handled on image.sc


Redeploy example contracts

Summary

Deploy zeta interactor
Redeploy examples

Is this one ready?

yes but keep it as draft until https://github.com/zeta-chain/zetachain/pull/34 is merged

It should be merged to #34 and then we merge both, otherwise we'll have merge conflicts because of squash.


Improvements to the examples tester

Now supports command line options:
--quiet: Only report failures
--example: Only run the given named example
--source: Only run examples from the named Markdown file
Other changes:

Briefer output when extracting examples (one line per Markdown file)
Detect and report duplicate examples names
Report actual warnings/errors when they don't match (with line numbers relative to the example)
Trim the end of actual output, to avoid having to include trailing spaces
Order errors/warnings by line number then error code, to make the ordering deterministic

Examples have been amended accordingly.

There are some larger changes to come here, but I wanted to get these small ones out of the way first.


[Refactor] Remove Expr serialization and deserialized logic in GsonUtils

Fixes #issue

[FE PR Coverage Check]
:heart_eyes: pass : 45 / 45 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
14
14
100.00%
[]

:large_blue_circle:
com/starrocks/persist/gson/GsonUtils.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ExpressionRangePartitionInfo.java
25
25
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 50 / 51 (98.04%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/Column.java
5
6
83.33%
[695]

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
14
14
100.00%
[]

:large_blue_circle:
com/starrocks/persist/gson/GsonUtils.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ExpressionRangePartitionInfo.java
25
25
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 55 / 56 (98.21%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/Column.java
5
6
83.33%
[695]

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
14
14
100.00%
[]

:large_blue_circle:
com/starrocks/persist/gson/GsonUtils.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ExpressionRangePartitionInfo.java
30
30
100.00%
[]


[BEAM-9615] Misc final schema cleanups.

Allow arbitrary number of fields for row headers. Turns out sometimes a struct can have more than 256 fields.
Error, not panic for unknown kinds when Row coding.
Handle time.Time for schema encoding. Not treated as a logical type.
Register Schema initialization.
Add schema registration to code generator.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @youngoli


No documentation coverage for Fault tolerance

I am not able to find any document reference for Fault tolerance in Helidon documentation. Am I missing something? Or is it hidden on my view?

Helidon MP fault tolerance:
https://helidon.io/docs/v2/#/mp/faulttolerance/01_overview
As this implements a specification and we do not add Helidon specific features, this docs is quite short.
There is no Helidon SE fault tolerance (yet) - we do have a new module in master - it was not yet released and it is now in experimental and "incubation" mode. We will add docs for it once we are confident it is ready for use.

Issue closed with 2399


Sign portable Windows binaries

Can this be closed? I seem to remember seeing recent commits that had to do with signing binaries.
See also #94 and #930


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 461 ms

Resolved: ClamAV performance has improved in c03e2ff after 5 minutes.


Add basic graphs to reports

Bar, Pie, Scatter, Line, and bubble charts

Graph supported added in commit 62f4129f40c3afd9fa15b152f78c011336c4dd89 in PR #10


规范代码，针对if判断后面只有一行的情况，也需要加大括号，不然以后修改容易发生错误

What's the purpose of this PR
规范代码
Which issue(s) this PR fixes:
Brief changelog
规范代码，针对if判断后面只有一行的情况，也需要加大括号，不然以后修改容易发生错误
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Read the Contributing Guide before making this pull request.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit tests to verify the code.
[ ] Run mvn clean test to make sure this pull request doesn't break anything.

Codecov Report

Merging #2868 into master will decrease coverage by 0.04%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master    #2868      +/-   ##
============================================
- Coverage      50.4%   50.35%   -0.05%
+ Complexity     2083     2082       -1
============================================
  Files           414      414
  Lines         12672    12682      +10
  Branches       1297     1297
============================================
- Hits           6387     6386       -1
- Misses         5831     5841      +10
- Partials        454      455       +1

Impacted Files
Coverage Δ
Complexity Δ

...o/adminservice/controller/NamespaceController.java
16.12% <0%> (-1.12%)
2 <0> (ø)

...lo/configservice/util/InstanceConfigAuditUtil.java
76.06% <0%> (-1.33%)
15 <0> (ø)

...ework/apollo/portal/controller/ItemController.java
7.31% <0%> (ø)
1 <0> (ø)
:arrow_down:

...rip/framework/apollo/common/entity/BaseEntity.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ctrip/framework/apollo/common/utils/BeanUtils.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../apollo/internals/RemoteConfigLongPollService.java
79.62% <0%> (-0.62%)
27% <0%> (-1%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24cc3da...afc7175. Read the comment docs.

Coverage decreased (-0.04%) to 53.943% when pulling afc717506ed861c8f67ff48e441cb344d1664d63 on laddcn:master into 24cc3da19cf90d01aebb21aa0ad7fcbee4843376 on ctripcorp:master.

It seems this pr has conflicted changes with current master branch, please help to solve this conflict and commit again.

I have resolved conflict with official master branch. @nobodyiam


Revert "Add analytics support for fluent bit"

Reverts wso2/apk#1248

Codecov Report
Patch coverage has no change and project coverage change: +49.59 :tada:

Comparison is base (ca7e452) 30.51% compared to head (5a551a5) 80.10%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1318       +/-   ##
===========================================
+ Coverage   30.51%   80.10%   +49.59%
===========================================
  Files         338        9      -329
  Lines       39196      548    -38648
  Branches    11620      246    -11374
===========================================
- Hits        11962      439    -11523
+ Misses      26976      109    -26867
+ Partials      258        0      -258

Flag
Coverage Δ

adapter
?

admin-domain-service
?

backoffice-domain-service
?

config-deployer-service
?

devportal-domain-service
?

idp-domain-service
80.10% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 303 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Proposal: Make Ecto.Repo.transaction/2 overridable

What?
Make Ecto.Repo.transaction/2 overridable, allowing App.Repo to perform after-transaction success callbacks.
Example (simplified)
defmodule App.Repo do
  use Ecto.Repo

  def transaction(fun_or_multi, opts) do
    fun_or_multi
    |> super(opts)
    |> case do
      {:ok, results} ->
        {:ok, do_something_with_results(results)}

      error ->
        do_something_with_errors(error)
    end
  end
end

Questions
Maybe there is a more mature way to wrap the transaction or built-in way to perform after-success callbacks, that I'm unaware of?
Ideas
We could wrap Ecto.Repo in one more macro and override the callback in there, but this seems to be a problem when having multiple implementations as some of those can be read_only and not expose transaction function at all. So the best place to put this seems to be here...?

Note you can defoverridable yourself, this works today:
defmodule Repo do
  use Ecto.Repo,
    adapter: Ecto.Adapters.Postgres,
    otp_app: :foo

  defoverridable transaction: 1, transaction: 2

  def transaction(fun_or_multi, options \\ []) do
    dbg(super(fun_or_multi, options))
  end
end

that being said I'm not against this change, I just don't think it's needed. Unless I'm missing something!

Yeah, we don't make any of the adapter callbacks overridable, I think folks should consider adding my_transaction first, making it overridable later. But if you  really want to do so, you can call it yourself as @wojtekmach suggests. :)

I had no idea defoverridable can be put that close to the overriding callback. This solves my problem in there, thanks!


Single-quote more pathological strings

See: https://github.com/dhall-lang/dhall-haskell/issues/1939

Hi Gabriel,
Unfortunately I merged this too quickly. Reverted it in https://github.com/clovyr/aeson-yaml/pull/10 for now.
The behavior of shouldSingleQuote is off given this change -- for example, a line containing \n (or other arbitrary symbols) but ALSO a trailing space is now single-quoted because any one of the conditions are sufficient to single-quote any string, including ones that may not be safe to single-quote.
The test cases didn't catch this because none of the double-quoted test cases meet any of the shouldSingleQuote ORs.
If you'd like, I can try to patch, but it may not be until later in the week.


[feature] Handle effects

Is your feature request related to a problem? Please describe.
Effects will render as melons
Describe the solution you'd like
We can't just blindly use the prop_dynamic stored in an effect, as the user may pass those entities explicitly.
The only possible solutions involve disabling rendering of an effect's model, then either requiring the user to explicitly pass the prop_dynamic (easy solution with obvious behaviour), or get the real entity off the effect and check whether the user already passed it explicitly (complex solution and the behaviour is inconsistent depending on whether you pass a dynamic prop along with an effect SENT.
I'll probably go with the former

Added in 1a061c27dddb24e60845dcedbc1e49b034c1d650


Fix #273 : save state.

Fix #273 : save state.

commented

Code style fixed.

+1 looks good, thank you

Great!

anything else coming or should i publish 2.1.1 to jcenter?

Nothing that come to mind right now ^^

it's up, thanks again sir!


Add directory watcher for tsserver and tsc

This PR contains the following changes:

Unify the file / directory watcher functions in tsc and tsserver;
For inferred projects, add the ability to detect newly added tsconfig.json files in from the same directory up to the root path;
For configured projects, add the ability to detect implicitly added/removed source files (e.g., when the tsconfig.json file doesn't have a files array, and source files are added to or removed from the directory) from the same directory down recursively. (Fix #5076, #4643)
For tsconfig.json file without a files array, also added support to detect file addition / removal under tsc --watch. (Fix #4553)

Points worth notice:
Inferred projects and configured projects have different kinds of directory watchers:

For inferred projects, the sole purpose of a directory watcher is to detect newly added tsconfig.json files; and the addition normally happens from the current path up. Also, it doesn't matter which project the watcher belongs to, all inferred projects can share one set of watchers if their root files happen to be in the same folder.
For configured projects, each project has a recursive directory watcher of the path where its config file is located at. It does matter which project the watcher belongs to.
Currently the recursive watchers are supported in Node 4.0 for both OSX and Windows. If the node version is before that, the recursive watcher might not work reliably.

:+1:

pinging @zhengbli, there are few comments, can you please address them (sorry for the delay)/

@vladima The code review is addresses at #5263.

This included a breaking API change by renaming parseConfigFile to parseJsonConfigFileContent and parseConfigFileText to parseConfigFileTextToJson
Random aside but a new function copyListRemovingItem is also being exported. Seems like an internal utility function to me but shrug


Langgraph visualization not working in streamlit

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangGraph/LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangGraph/LangChain rather than my code.
[X] I am sure this is better as an issue rather than a GitHub discussion, since this is a LangGraph bug and not a design question.

Example Code
The below code working fine in google colab and I am getting the graph visualization
from IPython.display import display, Image
from langchain_core.runnables.graph import MermaidDrawMethod
workflow = StateGraph(State)
workflow.add_node("categorize", categorize)
workflow.add_node("analyze_sentiment", analyze_sentiment)
....other nodes....
workflow.add_edge("categorize", "analyze_sentiment")
.....other edeges........
# Set entry point
workflow.set_entry_point("categorize")
# Compile the graph
app = workflow.compile()
display(
    Image(
        app.get_graph().draw_mermaid_png(
            draw_method=MermaidDrawMethod.API,
        )
    )
)

But the same visualization not working in streamlit UI
from IPython.display import display, Image
from langchain_core.runnables.graph import MermaidDrawMethod
display(
    Image(
        app.get_graph().draw_mermaid_png(
            draw_method=MermaidDrawMethod.API,
        )
    )
)

So how to visualize a langgraph in streamlit UI?

### Error Message and Stack Trace (if applicable)

_No response_

### Description

The below code working fine in google colab and I am getting the graph visualization

from IPython.display import display, Image
from langchain_core.runnables.graph import MermaidDrawMethod
workflow = StateGraph(State)
workflow.add_node("categorize", categorize)
workflow.add_node("analyze_sentiment", analyze_sentiment)
workflow.add_edge("categorize", "analyze_sentiment")
Set entry point
workflow.set_entry_point("categorize")
Compile the graph
app = workflow.compile()
display(
Image(
app.get_graph().draw_mermaid_png(
draw_method=MermaidDrawMethod.API,
)
)
)
But the same visualization not working in streamlit UI

from IPython.display import display, Image
from langchain_core.runnables.graph import MermaidDrawMethod
display(
Image(
app.get_graph().draw_mermaid_png(
draw_method=MermaidDrawMethod.API,
)
)
)
So how to visualize a langgraph in streamlit UI?

### System Info

ubuntu OS
langchain==0.2.16
langchain-community==0.2.16
langchain-core==0.2.39
langchain-experimental==0.0.64
langgraph==0.1.14
langgraph-checkpoint==1.0.11

@pradeepdev-1995 this is not a langgraph issue, but a streamlit issue, i don't think you can visualize images in streamlit using IPython's display(Image(...)). i would recommend trying to wrap the mermaid png in https://docs.streamlit.io/develop/api-reference/media/st.image and see if this solves your issue


Decouple CostModel inputs from iterations; fit and extract model params

What
Mainly addresses https://github.com/stellar/rs-soroban-env/issues/734 and https://github.com/stellar/rs-soroban-env/issues/709, along with a few other improvements.
The cost model for cpu and mem budgeting has been enhanced to f(x) = N * (a + b * Option<x>) -- the input x is now optional, and iterations N is explicit and always present.
This split has major implication on the bench setup, which is the major part of this change set.
This PR also adds model fitting and parameter extraction:

For a constant model, simply take the average of the costs over the number of iterations.
For a linear model, fit a linear regression model over the (inputs, costs) measurement.

The cost parameters have been updated with the extracted results.
This PR also adds several "ease of life" improvements, such as

Adds comments explaining what HostCostMeasurement is doing and what different types of overheads are.
Adds a smoke test on the budget with some random input to prevent accidental change of model parameters.
Improve display of Budget (splits Debug from Display), improves the table display of the benchmark results.
Add command line filter to which wasm insns type to run calibration for.

See full output of the calibration: output8.txt
Why
This is to address the overloaded use of input previously

For a linear model, the input x is the characteristic representing the work's complexity, e.g. length of the buffer when doing a memcpy.
In a constant model, the work is a constant cost that is independent any the input. In other words, the input is undefined.
Unfortunately, previously the input was entangled with the number of iterations the const work is repeated (due to e.g. batching), and thus many cost types were mis-characterized (e.g VecEntry).

Known limitations
[TODO or N/A]

@graydon thanks for your review and detailed thoughts. Here is an overall reply to your three comments above, since they are all touching similar problems.
Regarding the model representation, the two issues you brought up:

Option<x> vs Option<b>: Should x be optional, or should b? I pretty strongly believe Option<x> is the more accurate form. What we are trying to do is: express all types of cost with a general model up to order 1. Which means

x should be optional, meaning the model is "up to order 1". Option<b> would mean the model is order 1 but its coefficient may or may not exist, which does not make sense.
Should N be part of the model? Initially I thought so. I thought of bulk charging as the use case, Whether bulk charging N constant costs (of the same type, e.g. WasmInsnExec), or bulk charging N linear costs (e.g. memcpy of N elements of the same type). I thought N should act as a constant scaling factor in the model that is associated with X -- we cannot bulk costs with different X together. I.e. the old input is now a tuple (N, X) However, this has turned out to be misused (as you correctly pointed out above), and is hard to use correctly. It turned out to be just an "accounting" factor that doesn't belong as part of the model. In terms of reporting, the tracker reduces {(N, X)} into a (sum({N}, sum({X})), destroying their connections. I will remove N out of the model and make it part of the cost charging.

In terms of the use cases. It is interesting you laid out case 2 and 3 as different cases. I just thought of them as "bulk charging", for both things that are identical (memcpy of N bytes) and things that are logically separate but governed by the same formula (under the same CostType and having the same X) such as WasmInsnExec. I don't feel it's worth to differentiate them too much as long as we make sure they are both done correctly (our model is not first-principle based but empirical based).
The "memcpy" use case is an interesting one, which I have missed and it was an oversight. I would have put n_elts as the "iteration" and Some(declared_size<T>) as the input had I not missed it. But as you pointed out, memcpy maybe more accurately expressed as a constant setup cost (setting up the loop, locating the memory) plus a linear component w.r.t. the num_of_bytes (copying the bytes). So it might be more accurate as a linear model with no bulk factor (N=1), which is what it is now.
If this in general sounds reasonable to you, let me update this PR to remove N out of the model, and make the "bulk" vs "single_charge" interfaces more clear and separate, and then let you judge if it all makes more sense to move forward or if bigger changes are required. What do you think?

@graydon I've pushed a change to remove iterations from cost model and splitted out the batch-charging case from normal charging, which retains the old interface and is the vast majority. I still retained the Option<X> as explained above. This should clean up the cost-charging interface quite a bit.
Let me know if this is something we can work with, or if you feel bigger changes are still necessary.

@jayz22 Yeah, ok, I .. don't feel strongly enough about the location of the Option to argue it further, and with these changes the ambiguity at call sites is limited to batched_charge sites, of which are few. I'll approve and merge, thanks!

Oh, actually @jayz22 it looks like @dmkozh has 2 remaining nits plus the issue we both noted concerning the remaining 0-cost cases. Can you take a look at those before we merge?

@graydon @dmkozh All comments have been addressed, thank you.


BREAKING CHANGE: Use std::unordered_map for Table

toml specification does not require table is ordered. In usual case,
std::unordered_map will have better performance
BUG=#21

I do not believe this is a bug - The specification does not mandate any order, thus keeping it insertion order allows one to output the keys of a table in a nonsensical way.

Note: Insertion order cannot be achieved with std::map (I mentioned it a bit in #21). std::map keeps alphabetical order. Though I wrote this, I don't want to break backward compatibility.
(If I break backward compatibility, I'd like to change Time type first)

abandoned.


chore: exponentially retry

It is better to retry not too often as we might annoy poor nodes by retrying to often. Additionally, the retry mechanism should happen less often than the check on the outside.
It's an attempt to make our connection handling a bit smarter.
I'm not sure it will change much though.

Can we try something like backoff? I can try to do this later.

Can we try something like backoff? I can try to do this later.

I'd still merge it though, it's a step forward compared to how we're doing it now....
can always make it pretty later ;)

bors r+

bors retry

bors retry


Make Vale easier for new contributors

Make a better how-to-contribute thing for the discord
Add non-core stuff to https://vale.dev/roadmap, and have little pop-up blurbs and links
Add READMEs to each dir in the repo to explain what the dir is for

It would be really nice to have some docs to browse rather than having to struggle my way through the source code, clicking on several different files and searching through every function trying to figure out where stuff is. I could also help with documenting stuff if need be

ideas:

a guide on how to add a new kind of region to midas. maybe provide an example barebones one (unsafe?)
a guide on how to add a metaprogramming function into valestrom?


basic accesibility

This is a very basic implementation for accessibility. With these two minor changes the screen readers can pick up every time a notification is dispatched. The reason why I have uses aria-hidden on dismiss button is because 'times' is read by screen readers, while for them whether the notification is on screen or not does not really matter for people who are using screen readers.

Coverage remained the same at 95.588% when pulling d8c4f2a0af0e3e6e31898d43b4bc3f1cb91d648f on danutzcodrescu:feature/accesibility into 61cf24362a59cf0446caafb53046c9c30b7bca2a on igorprado:master.


Sync with upstream

Member

fixed in https://github.com/catenax-ng/tx-item-relationship-service/pull/850


WIP: Out of the box ruleset for OKTA Falco Plugin

Creating out of the box rules for the new OKTA Faclo plugins
Opened PR: https://github.com/falcosecurity/plugins/pull/81
Signed-off-by: darryk10<EMAIL_ADDRESS>
What type of PR is this?
This PR introduce the out of the box ruleset for the new OKTA Falco plugin created.
Reference https://github.com/falcosecurity/plugins/pull/81

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
This PR add the out of the box ruleset for the new OKTA Falco plugin
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Depends on opened PR https://github.com/falcosecurity/plugins/pull/81
Does this PR introduce a user-facing change?:

WIP: Out of the box ruleset for OKTA Falco Plugin

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: darryk10
To complete the pull request process, please assign kaizhe after the PR has been reviewed.
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

9fc19b6 Update rules/okta_rules.yaml
eec0971 Update rules/okta_rules.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I see the last two commits have a Co-authored-by: ... but not a Signed-off-by: ..., which is breaking DCO. My guess is that this happened through a GitHub PR suggestion. I fell with this trick lots of times, please remember of always putting your Signed-off-by: ... before committing a suggestion! In this case you need to add it to those commits in order to unblock the DCO. Thank you! 😄

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

9fc19b6 Update rules/okta_rules.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: darryk10, Issif
To complete the pull request process, please assign kaizhe after the PR has been reviewed.
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: d4151df8e0b68fefcdc9678842cd5a92cc3d234f

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, Issif, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Failure to Install - RPi2 - Raspbian Jessie with node.js v4.4.5 and npm v2.15.5

Operating System and Hardware: Raspbian Jessie - RPi2
NodeJS Version: v4.4.5
Npm Version: 2.15.5
Serialport version: ?
Python Version (if you're having trouble building serialport): 2.7.3
(Run node -v && npm -v && python --version to get the version numbers.)
Expected behavior
should install with npm install serialport or sudo npm install serialport
Actual behavior
Lots errors. In particular:
"
node-pre-gyp ERR! Tried to download: https://github.com/voodootikigod/node-serialport/releases/download/3.1.2/serialport-v3.1.2-node-v46-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v46 ABI) (falling back to source compile with node-gyp)
"
Partial error log from terminal: http://pastebin.com/dfZ7sd1M
npm-debug.log as attachment: http://termbin.com/hbds or npm-debug.txt
Steps and/or code to reproduce the issue
install with npm install serialport or sudo npm install serialport

https://github.com/openhardwarecoza/LaserWeb3/wiki/Raspberry-Pi-Image-Build
On 9 Jun 2016 22:17, "Daniel Edwards"<EMAIL_ADDRESS>wrote:

Operating System and Hardware: Raspbian Jessie - RPi2
NodeJS Version: v4.4.5
Npm Version: 2.15.5
Serialport version: ?
Python Version (if you're having trouble building serialport): 2.7.3
(Run node -v && npm -v && python --version to get the version numbers.)
Expected behavior
should install with npm install serialport or sudo npm install serialport
Actual behavior
Lots errors. In particular:
"
node-pre-gyp ERR! Tried to download:
https://github.com/voodootikigod/node-serialport/releases/download/3.1.2/serialport-v3.1.2-node-v48-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and
<EMAIL_ADDRESS>(node-v48 ABI) (falling back to source compile with node-gyp)
"
Partial error log from terminal: http://pastebin.com/dfZ7sd1M
npm-debug.log as attachment: http://termbin.com/hbds or npm-debug.txt
https://github.com/EmergingTechnologyAdvisors/node-serialport/files/307835/npm-debug.txt
Steps and/or code to reproduce the issue
install with npm install serialport or sudo npm install serialport
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/844,
or mute the thread
https://github.com/notifications/unsubscribe/AHVr22RKAoGgxv26_HSaEVrMvjR1Z_sqks5qKHTQgaJpZM4IyXJA
.

Tried doing that already, while doing npm install, it throws the same error.

It looks like Raspbian Wheezy and gcc/g++ v4.6 are being used. In order to install native addons with Node.js v4+, gcc/g++ 4.8+ are required. See https://github.com/fivdi/onoff/wiki/Node.js-v4-and-native-addons

Wheezy?  @Daniel, why arent you on Jessie yet?  Goodness
On 10 Jun 2016 10:08, "Brian Cooke"<EMAIL_ADDRESS>wrote:

It looks like Raspbian Wheezy and gcc/g++ v4.6 are being used. In order to
install native addons with Node.js v4+, gcc/g++ 4.8+ are required. See
https://github.com/fivdi/onoff/wiki/Node.js-v4-and-native-addons
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/844#issuecomment-225119095,
or mute the thread
https://github.com/notifications/unsubscribe/AHVr20dIZJTW5tjX_Ro_ogYC_lpGc9T4ks5qKRt2gaJpZM4IyXJA
.

Hmm, odd, I thought it was Jessie. Granted I've not reinstalled said pi in
quite some time. (it was installed using a prebuilt image with octoprint)
Thanks though I'll try it out later.
On 10 Jun 2016 11:10, "Peter van der Walt"<EMAIL_ADDRESS>wrote:

Wheezy? @Daniel, why arent you on Jessie yet? Goodness
On 10 Jun 2016 10:08, "Brian Cooke"<EMAIL_ADDRESS>wrote:

It looks like Raspbian Wheezy and gcc/g++ v4.6 are being used. In order
to
install native addons with Node.js v4+, gcc/g++ 4.8+ are required. See
https://github.com/fivdi/onoff/wiki/Node.js-v4-and-native-addons
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/844#issuecomment-225119095
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AHVr20dIZJTW5tjX_Ro_ogYC_lpGc9T4ks5qKRt2gaJpZM4IyXJA
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/844#issuecomment-225119516,
or mute the thread
https://github.com/notifications/unsubscribe/AKQqY5eUBlbRTm34uuIXibjZFeFLJER-ks5qKRwDgaJpZM4IyXJA
.

Got it working, Thanks.


ARROW-4034: [Ruby] Add support :append option to FileOutputStream

@ismurray This solves #3175.

Codecov Report

Merging #3193 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3193      +/-   ##
==========================================
+ Coverage   86.42%   86.42%   +<.01%
==========================================
  Files         504      504
  Lines       69623    69623
==========================================
+ Hits        60172    60175       +3
+ Misses       9354     9351       -3
  Partials       97       97

Impacted Files
Coverage Δ

cpp/src/arrow/csv/column-builder.cc
97.4% <0%> (+1.94%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 715cba5...6240f4b. Read the comment docs.

@kou and @shiro615 and @ismurray
Quick follow about this pull request. I am currently testing through the red-parquet gem's test-arrow-table.rb unit test. In it, there is a high level call on L:45 that does:
@table.save(tempfile.path)

which will cascade to Arrow::Table#save and in that method, it will instantiate a new TableSaver domain object, that will provide an output wrapper that enables the eventual output in different instructed file format (raw, csv etc).
Looking at the Arrow::Table#save interface, looks like it allows for an optional option param to bind as the second parameter, which, for example, potentially can invoke a call like:
# just an example, not concrete and can be any other option key value pairing
# that will be digested internally by these domain classes via contracts as needed
#
@table.save(tempfile.path, { append: true })

In my opinion, that is good and flexible as it will eventually also cascade to bind onto TableSaver class's constructor when an object of that class is instantiated. That said, once it is in TableSaver object instance I don't think the saver will notify the eventual use of FileOutputStream.open interface to be able to bind into the new append parameter that is added to this changeset.  Specially, I am referencing the TableSaver#save_raw that current has this implementation:
def save_raw(writer_class)
  FileOutputStream.open(@path, false) do |output|
    writer_class.open(output, @table.schema) do |writer|
      writer.write_table(@table)
    end
  end
end

which has the 2nd parameter default to of the output stream, always default to false.
Maybe this is intended, as the Arrow::Table is instructed to always write to a persistence file (parquet file in my case) in non-append mode? But just want to start this conversation and explore whether that is a possible further extension that can be built on top of this changeset here.

It's a good idea.
Can you open a JIRA ticket for this? https://issues.apache.org/jira/projects/ARROW/issues/
Do you want to implement this?

@kou yes, I will open up a JIRA ticket for this and can also spend some time to tackle this via a PR.


textlines not displayed

I believe I found a bug in whether or not PageViewer enables the Lines button in the main toolbar.
When the only textlines of the document are on a non-toplevel region (e.g. a table), then the page will be shows as if it had none.
The cause seems to be that DISPLAY_TEXTLINES is only enabled when org.primaresearch.dla.page.layout.PageLayout.hasLowLevelTextObject() returns true for TextLine, but that function does not enter the recursive region hierarchy.

(So maybe this issue should be moved to prima-core-libs?)

Should work now, please test

Should work now, please test

It does (1.4.05) – thank you very much!


Create .env

Hey men, i can't merge this because it's your Open AI API keys

sorry dude,im a new user on git
On Tue, Apr 4, 2023, 01:05 Matheus Filype @.***> wrote:

Hey men, i can't merge this because it's your Open AI API keys
—
Reply to this email directly, view it on GitHub
https://github.com/Santosl2/wpp-chatgpt/pull/5#issuecomment-1494680866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZAXRS4KHMORGPK4H4DWOR3W7L7PHANCNFSM6AAAAAAWOD256U
.
You are receiving this because you authored the thread.Message ID:
@.***>

@fandirmadhan you've leaked your Open AI API Key, I would recommend you to delete this key on Open AI API Keys and create a new one.

@fandirmadhan you've leaked your Open AI API Key, I would recommend you to delete this key on Open AI API Keys and create a new one.

Exactly dude ...


Added cumulative hazard

This is a refactoring to allow the computation of the Nelson-Aalen estimator with the same machinery set up for Kaplan-Meier. This takes care of point 3 in #5 .
Nelson-Aalen estimates the cumulative hazard. Cumulative hazard H is linked to survival S via the formula:
exp(-H) = S
So it can also be used to estimate the survival. It has the advantage, compared to Kaplan-Meier, that it can be used also to get baseline cumulative hazard of a fitted Cox Model (whereas getting the survival function from a Cox model with Kaplan-Meier is somewhat convoluted in case of simultaneous events)

Nice refactoring, I like it! Though do you think it will be extensible to cumulative incidence, which also needs to track the number of competing events?

Not sure, maybe the best is to add some compute_competing variable defaulting to false and add compute_competing && before the lines that are exclusive to cumulative incidence/estimators that need the number of competing events. Compiler in 0.7 should be smart enough that there is no penalty at all for this right?

Compiler in 0.7 should be smart enough that there is no penalty at all for this right?

Perhaps, I'm not entirely sure.
One notable difference is that you need the vector of competing events as another argument to the estimating function, so branching on compute_competing won't get us all the way there.

Fair enough: It may actually be better to simply duplicate the code...

Keyword arguments in 0.7 are fast, since they're based on NamedTuples, so I wonder if we could get away with doing something clever hacky, e.g.
function f(; time=t, status=s, kwargs...)
    if haskey(kwargs, :compete)
        # do stuff
    end
    # more stuff
end

Not sure though.

Regardless, this refactoring and the addition look good to me.