ICU Rebuild

icu-70.1-1 is currently in testing, I will publish a new release once it gets to core

It's now live and have broken my setup.
/usr/lib/chromium/chromium: error while loading shared libraries: libicuuc.so.69: cannot open shared object file: No such file or directory
Can this package in the future be dynamically linked to "/usr/lib/libicui18n.so"? Or at least be packaged in a way to have version dependencies to be considered.
Thank.

Can this package in the future be dynamically linked to "/usr/lib/libicui18n.so"? Or at least be packaged in a way to have version dependencies to be considered.

This is more or less just a seperately maintained "mirror" of extra/chromium with ungoogled-chromium patches (of course) and usually I'll try to stay as close to arch upstream. If its just a simple change I will consider it tho

@yuannan that sadly can't be done as C++ uses name mangling and when icu updates the library name will be the same but the functions inside will have different names, otherwise just symlinking the new library version to the previous name would fix the issue but sadly it doesn't.
$ chromium
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: _ZN6icu_698TimeZone13createDefaultEv

You can try out the following projects to avoid further library issues:

https://github.com/ungoogled-software/ungoogled-chromium-portablelinux
https://guix.gnu.org/en/packages/ungoogled-chromium-96.0.4664.45-1/


Compatibility with React 17

Despite having React 17 listed as a supported peer dependency (see package.json), the Chat Ai Widget doesn't work in a React 17 app (we are getting a useSyncExternalStore is not a function error).
This seems to be due to the library depending on a recent version of react-query which only supports React 18

Hello, thank you for your report.
In the next version, we plan to improve by removing react-query.
Thank you.

@bang9 thanks for your reply. Do you have any tentative schedule for this new version ?
Also, is there any workaround you can recommend in the meantime ?

You do not necessarily need to use an npm module unless it is a special case.
We support widgets in the form of embed codes.
You can copy your code from the dashboard and paste it into your index.html or use something like react-helmet.

v1.5.10 has been released
Would you like to try it with the new version?

@bang9 yes, it works, thanks!


Implement Ambient Lighting

Add support for ambient lighting in the ray tracer to provide a base level of illumination to the scene.
Ambient Lighting (A): A <ratio> <R,G,B colors>

Ratio: Ambient lighting ratio in the range [0.0, 1.0]
Colors: R, G, B values in the range [0-255]

This is already implemented but as the ambient light can have RGB color, I have to change how it works


File Explorer renders so small it's hard to read

Issue Type: Bug
On my Surface Book 2, when I try to open a file through the File Explorer via File->Open File, the File Explorer that is opened is rendered so small I can't actually read anything.
VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (5.44GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

dart-code
Dar
2.25.0

flutter
Dar
2.25.0

xml
Dot
2.4.0

tslint
eg2
1.0.43

chat
kar
0.12.0

vscode-cudacpp
kri
0.1.1

python
ms-
2019.3.6215

cpptools
ms-
0.22.1

csharp
ms-
1.18.0

powershell
ms-
1.12.0

vsliveshare
ms-
0.3.1403

vsliveshare-audio
ms-
0.1.48

vsliveshare-pack
ms-
0.2.10

xaml
ste
0.0.1

pdf
tom
0.5.0

Here's a screenshot of the issue. You can see how small the font in File Explorer is compared to the text document

This is likely similar to #72129, but this issue doesn't seem limited to an RDP session

We are building exploration builds that use a much newer version of our UI framework (Electron version 4.0.x). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux: Download
Windows: Download

As the person responsible for opening #72129 I should probably mention that I see this issue only during RDP sessions and not locally.


Switch to go1.16 images for GitHub actions

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This switched the GitHub actions workflows to use golang 1.16. The prow
jobs will be updated in test-infra.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Ref https://github.com/kubernetes/test-infra/pull/20878

Codecov Report

Merging #312 (6d3f68d) into master (f0f26af) will not change coverage.
The diff coverage is n/a.

 Click here to find out more.

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 f0f26af...6d3f68d. Read the comment docs.

@saschagrunert should we still have some coverage of go 1.15? at least in the test and build GH actions? Or do you think that's not worth it?

@saschagrunert should we still have some coverage of go 1.15? at least in the test and build GH actions? Or do you think that's not worth it?

I read the changelog and think we're fine to update to 1.16. I did not see anything specific which seems to be worth testing with the older version. :innocent:

/lgtm

/lgtm

Had to update go.mod/sum, this avoids breaking the CI when the test-infra PR merges. PTAL again.

/lgtm


Tre wants a #tech

Give Tre a tech, please
A description of the issue:
Tre is sad he doesn't get a #tech and when Tre's sad I'm sad and that's bad
Proposed Solution:
Give the man a #tech
Additional Comments:
Pretty please

:this:

Closed as duplicate of #233


TypeError: window.getComputedStyle(...) is null

Versions
css-element-queries version: 1.0.2
Browser: Firefox 59.0.1 (64-bit)
OS: MacOS High Sierra 10.13.3
Issue - ResizeSensor.js:150
var position = window.getComputedStyle(element).getPropertyValue('position');

Here window.getComputedStyle(element) can return null at least on Firefox, and then the subsequent call to .getPropertyValue('position') will throw an error.
Fix
var computedStyle = window.getComputedStyle(element);
var position = computedStyle ? computedStyle.getPropertyValue('position') : null;

Related Firefox bug report
https://bugzilla.mozilla.org/show_bug.cgi?id=548397

Can you provide a pull request please?

Don't have rights to open it directly. Do you want me to fork the repo and do it that way?


Add examples using label text to fined elements.

We found it really useful to use form labels as the selector for finding inputs. There were no examples of this in the Readme, but it works since the parameters are delegated down to Capybara.
I would consider submitting a PR to add those helpers to SitePrism::Page if there is a chance it would be accepted. I'm not sure if that additional API is desired.

Sorry I've taken a while to get to this...
Isn't this just normal capybara functionality? SitePrism will just pass any parameters down to capybara, so not sure what we're getting here...
Would an addition to the readme be enough? You're right that some people would use these features if they knew they existed :)

You're right that the readme would technically be enough. When I didn't see it mentioned I started looking in the specs as a second form of documentation. I didn't see it mentioned there either so I added it to make sure it would work.
I might suggest if it is going to be mentioned in the readme as a valid use that there should be a test supporting that claim.

On Mar 21, 2015, at 8:50 AM, Nat Ritmeyer<EMAIL_ADDRESS>wrote:
Sorry I've taken a while to get to this...
Isn't this just normal capybara functionality? SitePrism will just pass any parameters down to capybara, so not sure what we're getting here...
Would an addition to the readme be enough? You're right that some people would use these features if they knew they existed :)
—
Reply to this email directly or view it on GitHub.


Request: systray widget displays time in menubar

It'd be great if the MacOS systray widget displayed today's cumulative time in the menubar.
Could have an option to display all time, or just for a specific tag.

A few suggestions for what should be displayed:

if an open-ended range is present, it should be visualized somehow, eg. 2h40m...
if there is a should-total, that should (optionally) be visible, eg. 6h20m / 8h

There are most likely better ways to visualize these.
(I do not own a mac, so I can only comment on the functionality per se)

I’m currently considering to discontinue the widget, at least in the way it’s currently implemented:

I don’t think a lot of people are actually using it, including myself.
I’ve been using a 3rd-party library for the native UI, but that looks abandoned now. It uses deprecated Apple APIs, and it doesn’t compile on modern M1 / ARM Macs anymore.
The current approach to bundle the UI into the CLI executable is very limited, and it’s hard to add more powerful features. I can’t even add the klog icon, because that would require me to ship a proper application bundle instead of just a binary.

Overall I think the embedded widget is a dead end. For now, I don’t mind keeping the code as it is, but I probably won’t extend it anymore, or invest time into porting it to ARM. I still believe a native widget would be terrific, but then it should be more powerful and fun to use (e.g. a graphical panel), in which case it makes more sense to have a standalone application.


[TF:TRT] INT8 calibration in dynamic shape mode

This PR enables INT8 conversion with calibration in dynamic shape mode.

The profile collection logic is moved before the calibration step in TRTEngineOP, because TRT optimization profiles have to be defined before we can calibrate an engine.
INT8 test are now enabled in V2 mode both with and without dynamic shapes.

Tracker: #45481

Tagging @bixia1 for review. Thanks for @vict-guo for the initial implementation.
A follow up PR is planned to refactor trt_engine_op.cc: there are repetitive steps in GetEngine / BuildEngine / AllocateCalibrationResources. These shall be factored out into helper functions.

@tfeher Can you please check @bixia1's comments and keep us posted ? Thanks!

There are failing tests, here are the log
fail1.log
fail2.log
.

@tfeher Can you please resolve conflicts? Thank you!

@bixia1 The CI failure was caused by an issue in the algorithm selector in TRT 7.x. We had a workaround in place, but it was only active for TRT 7.1. I have adjusted it make it work with TRT 7.2 as well


your package needs a proper header

see here: https://www.gnu.org/software/emacs/manual/html_node/elisp/Library-Headers.html
Else emacs cannot build the package, this is necessary for quelpa installation and probably for putting it on melpa as well #1.

find it here


Failed to resolve domain/ silently failed to track within WSL2

I haven't been able to completely investigate this / understand the root causes, but I'm opening an issue here in case anyone else hits the same problem as I suspect its a common setup to use Go within WSL2 with Application Insights.
At first, I wasn't seeing any events make it to my Application Insights instance so I had to add a diagnostic listener via NewDiagnosticsMessageListener -- that showed the following message:
Failed to transmit telemetry: Post "https://dc.services.visualstudio.com/v2/track": dial tcp: lookup dc.services.visualstudio.com on <IP_ADDRESS>:53: cannot unmarshal DNS message

When outside the application dig dc.services.visualstudio.com would resolve the domain correctly. While researching this I came across the similar https://github.com/rclone/rclone/issues/4984 in which the project member @ncw created the upstream issue https://github.com/golang/go/issues/44135 (appears to have been automatically closed without research / assignment).
A work around for this issue is to set the environment variable GODEBUG=netdns=cgo when running/ building your application.
I'd be ok if this is seen as not related to this project, but given it seems there's no one pursuing the upstream fix, it will cause this library to fail silently without really giving any hints that the library isn't working which seems a noteworthy usability issue which at a minimum I would think should be documented here given the likelihood of this lib being used with WSL.

Thanks for this note.  As @jboelter has mentioned, this appears to be related to an upstream issue.  The silent failure is unfortunately a side-effect of asynchronous transmission, though I'm glad you were able to detect it from the diagnostic messages.


Select prompt

We need support for selecting from a list of options for backends.

Added single select, for multi-select, we can create an issue in the future if there will be a need for it.


Optional args instead of Record<string, never>

Hi, thank you for your cool library.
I was wondering if it is possible to make arg parameter optional when there are no arguments (or there may be none) instead of Record<string, never>.
Right now we have to write
const getMe = fetcher
    .path('/my')
    .method('get')
    .create();

getMe({}); // note {}

for typescript to not yell the error

I just stumbled upon this... would love to have this changed.


OCI Registry uses AppURL (ROOT_URL) no matter which address the client is connecting to (more Multi-Domain fallout)

Description
No matter what url the OCI client uses, at first connection Gitea responds with the appropriate www-authenticate header but with an incorrect token url hostname set to the AppURL instead of the hostname from the client's request.
https://github.com/go-gitea/gitea/blob/c660149a7079c2b06d4ee6dce2a45804d6d4d7f6/routers/api/packages/container/container.go#L118
This means that we cannot use OCI clients that target protocol://host:port combinations other than the one set in ROOT_URL as they are redirected by the www-auth header to the protocol://host:port in the ROOT_URL via it's use in the construction of the AppURL variable.
The use case is familiar to anyone who is using gitea to back an on-kubernetes-cluster registry to host images that are pushed from off-cluster but referenced for resources on-cluster.
Very often the ingress protocol://host:port combination that is fronting Gitea as a reverse proxy is inaccessible to on cluster resources or containerized resources (like the kubelet in a kind setup). So those resources will be configured to connect directly to the service bound to the Gitea deployment and the protocol://host:port combination that the kubelet connects to on cluster will not match the one used off cluster.
While much work was done in https://github.com/go-gitea/gitea/issues/19345 to fix the issues with multi-domain support in the gui, it did not make any effort to solve the same problem in the container registry. Therefore https://github.com/go-gitea/gitea/issues/22033 should probably not have been closed.
FWIW the docker registry project uses the request headers to set the authorization response header here I believe https://github.com/distribution/distribution/blob/51a72c2aef976bd55de3a7b8b0120f97b4169476/internal/client/auth/challenge/authchallenge.go#L119-L121 so there is precedent for this behavior.
Gitea Version
1.21.7 built with GNU Make 4.4.1, go1.21.7 : bindata, timetzdata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
KO pushing to Gitea from developer workstation
# Warning: 'bases' is deprecated. Please use 'resources' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
2024/03/04 10:58:00 Using base cgr.dev/chainguard/static:latest@sha256:67ed8ca8d99e12e8778c038cf88ef7c27d44f08247d317c7135a66ca9d8a7652 for ucp.adskeng.net/unified-control-plane
2024/03/04 10:58:00 Building ucp.adskeng.net/unified-control-plane for linux/amd64
2024/03/04 10:58:05 Publishing gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:latest
2024/03/04 10:58:05 pushed blob: sha256:dddad3d1675134ab45c0e954718630bd68921d716701511f0afb7ca2f37b61e0
2024/03/04 10:58:06 pushed blob: sha256:c28efc4d3128372f019baf58f3d4ccce238a4a5ebe583983f329875815f3796d
2024/03/04 10:58:06 pushed blob: sha256:250c06f7c38e52dc77e5c7586c3e40280dc7ff9bb9007c396e06d96736cf8542
2024/03/04 10:58:06 pushed blob: sha256:f254e377e71e3753dc3b88a86088ea46dc949f0ae3b50434e7a1f3b2608c8b73
2024/03/04 10:58:06 pushed blob: sha256:0d64d3736fe6666f37553b9deb11783bdbef4e63301b939dc3c51a8aa2eb5a6d
2024/03/04 10:58:06 gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:sha256-9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e.sbom: digest: sha256:7bbe466320ab724e1e7a0e83bb8be736fae0769ca9d9399a000af66ab5d5bee9 size: 375
2024/03/04 10:58:06 Published SBOM gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:sha256-9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e.sbom
2024/03/04 10:58:06 pushed blob: sha256:9a6dad177a5c7758bc5ebba82a4dfeca298cd068b29c0cfb3641264e42bf500e
2024/03/04 10:58:06 gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:latest: digest: sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e size: 1211
2024/03/04 10:58:06 Published gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e

Pod referencing Gitea Image on Kind cluster that is also hosting Gitea
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  34s                default-scheduler  Successfully assigned unified-control-plane-system/unified-control-plane-controller-manager-59645d95b8-w2bg8 to localdev-control-plane
  Normal   Pulling    33s                kubelet            Pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1"
  Normal   Pulled     31s                kubelet            Successfully pulled image "gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1" in 1.920296393s (1.920351294s including waiting)
  Normal   Created    31s                kubelet            Created container kube-rbac-proxy
  Normal   Started    31s                kubelet            Started container kube-rbac-proxy
  Normal   Pulling    17s (x2 over 31s)  kubelet            Pulling image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e"
  Warning  Failed     17s (x2 over 31s)  kubelet            Failed to pull image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e": rpc error: code = Unknown desc = failed to pull and unpack image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e": failed to resolve reference "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e": failed to authorize: failed to fetch anonymous token: Get "https://gitea.cnoe.localtest.me:8443/v2/token?scope=%2A&scope=repository%3Agiteaadmin%2Funified-control-plane-856ee3c8576196fe1db39ad1b44799b5%3Apull&service=container_registry": dial tcp <IP_ADDRESS>:8443: connect: connection refused
  Warning  Failed     17s (x2 over 31s)  kubelet            Error: ErrImagePull
  Normal   BackOff    2s (x3 over 30s)   kubelet            Back-off pulling image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e"
  Warning  Failed     2s (x3 over 30s)   kubelet            Error: ImagePullBackOff

Git Version
No response
Operating System
No response
How are you running Gitea?
Deployed with Helm on Kind
% helm install --dry-run my-gitea gitea-charts/gitea --values pkg/controllers/localbuild/resources/gitea/values.yaml > pkg/controllers/localbuild/resources/gitea/k8s/install.yaml

% cat pkg/controllers/localbuild/resources/gitea/values.yaml
redis-cluster:
  enabled: false
postgresql:
  enabled: false
postgresql-ha:
  enabled: false

persistence:
  enabled: false

test:
  enabled: false

gitea:
  admin:
    existingSecret: gitea-admin-secret
  config:
    database:
      DB_TYPE: sqlite3
    session:
      PROVIDER: memory
    cache:
      ADAPTER: memory
    queue:
      TYPE: level
    server:
      DOMAIN: gitea.cnoe.localtest.me
      ROOT_URL: 'https://gitea.cnoe.localtest.me:{{ .Port }}'

service:
  ssh:
    type: NodePort
    nodePort: 32222
    externalTrafficPolicy: Local

ingress:
  enabled: true
  apiVersion: 'networking.k8s.io/v1'
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 100m
  className: nginx
  hosts:
    - host: gitea.cnoe.localtest.me
      paths:
        - path: /
          pathType: Prefix

Relevant containerd config.toml from the Kind node with rewrite to make kubelet pull from the container port rather than the host port of the ingress:
version = 2

[plugins]
  [plugins."io.containerd.grpc.v1.cri"]
    [plugins."io.containerd.grpc.v1.cri".registry]
      [plugins."io.containerd.grpc.v1.cri".registry.configs]
        [plugins."io.containerd.grpc.v1.cri".registry.configs."gitea.cnoe.localtest.me"]
          [plugins."io.containerd.grpc.v1.cri".registry.configs."gitea.cnoe.localtest.me".tls]
            insecure_skip_verify = true
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
        [plugins."io.containerd.grpc.v1.cri".registry.mirrors."gitea.cnoe.localtest.me:8443"]
          endpoint = ["https://gitea.cnoe.localtest.me"]

Solution Proof of Concept
As a proof of concept I created a branch over here to test if I could influence the current behavior:
https://github.com/jessesanford/gitea/blob/c2fffabcd5122d258360d4443b6e583fc62e28f1/routers/api/packages/container/container.go#L119-L131
ko pushing container image to gitea.cnoe.localtest.me:8443 from local workstation to on-cluster gitea:
% export KO_DOCKER_REPO=gitea.cnoe.localtest.me:8443/giteaadmin/ && kustomize build config/overlays/local | ko resolve --insecure-registry -f - | kubectl apply -f -
# Warning: 'bases' is deprecated. Please use 'resources' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
2024/03/04 18:02:42 Using base cgr.dev/chainguard/static:latest@sha256:67ed8ca8d99e12e8778c038cf88ef7c27d44f08247d317c7135a66ca9d8a7652 for ucp.adskeng.net/unified-control-plane
2024/03/04 18:03:05 Building ucp.adskeng.net/unified-control-plane for linux/amd64
2024/03/04 18:03:09 Publishing gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:latest
2024/03/04 18:03:10 existing manifest: latest@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e
2024/03/04 18:03:10 existing manifest: sha256-9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e.sbom@sha256:7bbe466320ab724e1e7a0e83bb8be736fae0769ca9d9399a000af66ab5d5bee9
2024/03/04 18:03:10 Published SBOM gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5:sha256-9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e.sbom
2024/03/04 18:03:10 Published gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e
namespace/unified-control-plane-system unchanged
customresourcedefinition.apiextensions.k8s.io/certificates.tls.ucp.adskeng.net unchanged
customresourcedefinition.apiextensions.k8s.io/gitops.registry.ucp.adskeng.net unchanged
customresourcedefinition.apiextensions.k8s.io/sloes.observability.ucp.adskeng.net configured
serviceaccount/unified-control-plane-controller-manager unchanged
role.rbac.authorization.k8s.io/unified-control-plane-leader-election-role unchanged
clusterrole.rbac.authorization.k8s.io/unified-control-plane-manager-role configured
clusterrole.rbac.authorization.k8s.io/unified-control-plane-metrics-reader unchanged
clusterrole.rbac.authorization.k8s.io/unified-control-plane-proxy-role unchanged
rolebinding.rbac.authorization.k8s.io/unified-control-plane-leader-election-rolebinding unchanged
clusterrolebinding.rbac.authorization.k8s.io/unified-control-plane-manager-rolebinding unchanged
clusterrolebinding.rbac.authorization.k8s.io/unified-control-plane-proxy-rolebinding unchanged
service/unified-control-plane-controller-manager-metrics-service unchanged
deployment.apps/unified-control-plane-controller-manager configured

Pod events from deploy of pod referencing the container image at gitea.cnoe.localtest.me:8443 pushed by ko:
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  76s   default-scheduler  Successfully assigned unified-control-plane-system/unified-control-plane-controller-manager-59645d95b8-65zk7 to localdev-control-plane
  Normal  Pulling    75s   kubelet            Pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1"
  Normal  Pulled     73s   kubelet            Successfully pulled image "gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1" in 1.891202544s (1.891260145s including waiting)
  Normal  Created    73s   kubelet            Created container kube-rbac-proxy
  Normal  Started    73s   kubelet            Started container kube-rbac-proxy
  Normal  Pulling    73s   kubelet            Pulling image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e"
  Normal  Pulled     72s   kubelet            Successfully pulled image "gitea.cnoe.localtest.me:8443/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5@sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e" in 1.408522344s (1.408531044s including waiting)
  Normal  Created    71s   kubelet            Created container manager
  Normal  Started    71s   kubelet            Started container manager

NOTE: the kubelet thinks that it is getting the container from gitea.cnoe.localtest.me:8443 but containerd is pulling it from gitea.cnoe.localtest.me:443
From gitea logs during pull (See the X-Forwarded-Host:[gitea.cnoe.localtest.me] X-Forwarded-Port:[443] in the debug log message)
2024/03/04 22:46:00 ...ntainer/container.go:118:apiUnauthorizedError() [E] Request looks like: &{GET /v2/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5/manifests/sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e?ns=gitea.cnoe.localtest.me%3A8443 HTTP/1.1 1 1 map[Accept:[application/vnd.oci.image.manifest.v1+json, */*] Accept-Encoding:[gzip] User-Agent:[containerd/v1.7.1] X-Forwarded-For:[<IP_ADDRESS>] X-Forwarded-Host:[gitea.cnoe.localtest.me] X-Forwarded-Port:[443] X-Forwarded-Proto:[https] X-Forwarded-Scheme:[https] X-Real-Ip:[<IP_ADDRESS>] X-Request-Id:[becf1c5a6a65a6ca507217c9e135639a] X-Scheme:[https]] {} <nil> 0 [] false gitea.cnoe.localtest.me map[] map[] <nil> map[] <IP_ADDRESS>:54542 /v2/giteaadmin/unified-control-plane-856ee3c8576196fe1db39ad1b44799b5/manifests/sha256:9c6a4c54450cc8dd93c445d473da318a037b9535d98f76567d144458b1572a4e?ns=gitea.cnoe.localtest.me%3A8443 <nil> <nil> <nil> 0xc0062ab140 <nil> [] map[]}

Database
None

Added the packages label because of the specific topic but this issue is not really package related. Gitea simply does not have multi-domain support at the moment.

The solution for this case is pretty simple @KN4CK3R. See my POC: https://github.com/jessesanford/gitea/blob/c2fffabcd5122d258360d4443b6e583fc62e28f1/routers/api/packages/container/container.go#L119-L131 Would it be worth crafting a PR for this? What are the chances of this getting approved and merged without a broader multi-domain solution. Given the incremental solutions so far: https://github.com/go-gitea/gitea/issues/19345 it would seem like we should be able to get this going right?

@KN4CK3R Sorry to ping you directly, is there another maintainer I should be working with on this? Thank you for your help!

Maybe AppURL is the fallback URL. We don't know the address the docker/podman client requested because maybe there is a proxy between Gitea and client. This is different from web browser, we can know the web browser's request domain.

Maybe AppURL is the fallback URL.

FYI for those following this: https://github.com/jessesanford/gitea/pull/1/files#diff-36426f1aaff58f9b2084f7fc13593b237474e1d75a4e2883e0a44351e367ff76R125
Do you think that we would check for X-Forwarded-* headers and if they are not available then fall back on setting.AppURL rather than ctx.Req.URL.Host ? I am fine with that. I think in most instances they will be the same thing, as the proxy SHOULD have its origin for gitea is configured to the same setting.AppURL address. As long as we can use  the X-Forwarded-* headers when present I am happy. They are pretty standard for most reverse proxy and api firewalls at this point.

@wxiaoguang You did some work removing root url occurences. I don't know what other multi url systems do and what are best practices. For example I don't know if it is a good idea to allow every url the client passes in or if we need an allow list or something.

The "X-Forwarded-* header" approach works for many cases, I didn't use it because the FAQ there: https://github.com/go-gitea/gitea/pull/22861

Why not use {{.GuessCurrentOrigin $.ctx ...}} to let backend decide the absolute URL?
It's difficult for backend to guess the correct protocol(scheme) correctly with zero configuration. Generating the absolute URL from frontend can guarantee that the URL is 100% correct -- since the user is visiting it.

According to MDN, the X-Forwarded-Proto is not standard and there are many alternatives (Front-End-Https / X-Forwarded-Protocol /  X-Forwarded-Ssl /  X-Url-Scheme). Gitea should be able to be easy to setup and use out-of-box.

So, for advanced users who could configure their system correctly, I think it is feasible and useful to use X-Forwarded-* headers, the only thing need to do is to introduce some config options and help end users to use them correctly.

Ok I will craft a PR based on this feedback and then we can continue the discussion there.

I proposed a solution:  Refactor AppURL usage #30885


Layout of iOS tab has overlap on iPad 2 Sim (iOS 8.3)

The date picker overlaps the text just after it on the iOS tab when using an iPad 2 sim (iOS 8.3)

Also the app does not fill the entire simulator...perhaps a splash screen is missing.
Tested using:
MacOS 10.11.2 (15C40a)
Studio <IP_ADDRESS>511130407
Ti SDK 5.1.0.v20151118214427
Appc NPM 4.2.2-1
Appc CLI 5.1.0-60
Ti CLI 5.0.5
Alloy 1.7.26
Arrow 1.3.22
Xcode 7.1 (7B91b)
Node v0.12.7
Java 1.7.0_80

The app is iPhone only as you can see in the tiapp.xml
I wonder why the height of the picker is not the 50 it is set to. Perhaps that only works on ios9. Will check that but don't think it's a blocker

Ah, then we may have a different issue where I am still able to deploy to 'unchecked' targets. Updating ticket to be an iPhone sim.

You've found a bug
https://jira.appcelerator.org/browse/TIMOB-20028


[main] Update community files

Cron -knative-prow-robot
Produced by: knative-sandbox/knobots/actions/update-community
Details:

closing and letting the bot create a new one. The failures have been fixed in https://github.com/knative-sandbox/eventing-rabbitmq/pull/986
/close


Pure JS version

Could you create a "pure" javascript version?
I love drinking coffee but not coding in it!
(Haven't been able to convert it to JS)

They have linked the JavaScript version on the README:
https://github.com/downloads/osuushi/Smooth.js/Smooth-0.1.7.js

decaffeinated fork: https://github.com/LearnWithHomer/Smooth.js


improve ut for ip.go

improve ut for ip.go
Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

@my-git9 Could you elaborate on why these tests are needed? MustAddrFromIP() should just be a panic wrapper around AddrFromIP(), which is already covered by tests.
@christarazi Why does MustAddrFromIP() directly call netip.AddrFromSlice() instead of wrapping AddrFromIP() with panic()?

@ti-mo Good point, filed https://github.com/cilium/cilium/pull/21598.

OK, I will close this


TypeError: Object div has no method 'apply'

hi all,
i'm trying to use jest with the yo flux project template.
i have a basic component which renders simple static text in a div.
var app = TestUtils.renderIntoDocument(       <App />     );
but when i try to render the component in the test i got this error.
TypeError: Object div has no method 'apply'
any ideas would be helpful.

ok, i've figured this error has nothing to do with Jest.
its interesting, i set my project up manually by installing flux and react and all dependencies and error has gone.


{rdbms-connect} Add support to read UTF-8 files with and without BOM

If a sql file with UTF-8 BOM encoding is passed to the command az postgres flexible-server execute it will fail because its contents are read assuming that the encoding is utf-8. We need to change to utf-8-sig to be able to handle both cases (UTF-8 with/without BOM).

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

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

rdbms-connect

If you want to release a new version, please update setup.py and history.rst


Errors when running development server: Failed to log H2O event, SyntaxError: Unexpected end of JSON input

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
2023.7.9
What version of Remix are you using?
1.19.1
Steps to Reproduce

npm create @shopify/hydrogen@latest,
then connect your store and
run yarn or npm install, h2 setup,
finally, npm run dev or yarn dev and
browse http://localhost:3000,

Expected Behavior
no errors in terminal
Actual Behavior
Several blocks of the following error in the terminal, each time a page is rendered. This is only happening on the dev server, doesn't happen if building and previewing. No visible issue with the pages' rendering though.
Failed to log H2O event
SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at parseJSONFromBytes (/home/user/test-store-latest/node_modules/undici/lib/fetch/body.js:572:15)
at successSteps (/home/user/test-store-latest/node_modules/undici/lib/fetch/body.js:512:23)
at specConsumeBody (/home/user/test-store-latest/node_modules/undici/lib/fetch/body.js:521:5)
at Request.json (/home/user/test-store-latest/node_modules/undici/lib/fetch/body.js:360:14)
at Request.json (/home/user/test-store-latest/node_modules/@miniflare/core/src/standards/http.ts:353:38)
at Object.fetch (file:///home/user/test-store-latest/node_modules/@shopify/cli-hydrogen/dist/lib/mini-oxygen/node.js:29:30)
at /home/user/test-store-latest/node_modules/@shopify/remix-oxygen/src/event-logger.ts:26:5
at logSubRequestEvent (/home/user/test-store-latest/node_modules/@shopify/hydrogen/src/cache/fetch.ts:70:5)
at runWithCache (/home/user/test-store-latest/node_modules/@shopify/hydrogen/src/cache/fetch.ts:131:67)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at fetchStorefrontApi (/home/user/test-store-latest/node_modules/@shopify/hydrogen/src/storefront.ts:336:7)
Failed to log H2O event

Same here when I upgraded from 2023.7.8 to 2023.7.9

same for me, I first noticed it when updating an existing site from 2023.7.8 to 2023.7.9 - but it is also an issue on fresh builds

Same here - just updated on what is very close to a demo-store project...I keep going back and updating the whole project because i keep stopping and starting my Hydrogen upgrade project but want the best version of the demo store - a laborious job but that's my scenario.
Tried to update packages to the Hydrogen / demo-store app (very minor update to hydrogen but then updated everything else in package.json while I was there - not that many tbh) - a few npm issues with cross dependencies relating to Tailwind but I don't think it's relevant.  Tried to downgrade back using undo and npm install.  Then tried to run and now I'm getting the above error!!  So flakey.
From 2023.7.4 to 2023.7.9 for me.
Hope this is fixed soon because I don't have a clue on how to fix.
I can't know everything and I barely understand remix as it is :-)
Also, had a bad time with the new Content security Policy - had to add a policy override with loads of local dev overrides connecting to live server and was forced to add 'unsafe-inline' but that's another story / bug.

Also getting this error on Version 2023.7.7

Also getting this error on upgrading to 2023.7.9


[Redshift] Constraint doesn't work

Description
Created constraint doesn't work
DBeaver Version
Version <IP_ADDRESS>406181653
Operating System
Win11
Database and driver
Redshift JDBC Driver <IP_ADDRESS>
Steps to reproduce

Create a table and a constraint for it via the Navigator
Open the created table and go to DDL  tab

Expected: the DDL is displayed correctly
AR:

the error is displayed
the schema ERD shows the same error and doesn't show tables
a foreign key can't be created for using such primary key

Additional context
1.log

verified


Zigbee devices working, but the front end not

Description of the issue
When I access the ADD-ONS page, I see Z2M as "not running", but checking the log and my dashboards all devices are working fine. It sounds good, but I can't add a new device since I can't access the Z2M page.
Again, the Z2M log is fine, I can see all devices and the state of each one initialized.
Thanks.
Addon version
1.28.4-1
Platform
Home Assistant 2022.11.5
Supervisor 2022.11.2
Frontend 20221108.0 - latest
Logs of the issue (if applicable)
No response

I had the same issue. Adding frontend: true in the configuration.yaml file fixed the issue for me.

I'm sorry but I couldn't understand it.
Just a new line with this content? It shows me a syntax error for that.

This is my zigbee2mqtt configuration file:
data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt: {}
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2599763-if00
  adapter: deconz
frontend: true
advanced:
  network_key: [] # omitted

As you can see, above advanced there is the settingfrontend: true

It hasn't worked...
I don't know how to add new devices, since I can't access the Z2M page.
Thanks.

@Koenkk , any idea here? Do you know if this is an HA or Z2M issue? I have seen this issue with other people here and the same in our Brazilian telegram's group.
Thanks.

@gregolin how you're accessing your HA instance? via local IP or outside url/domain?
I'm asking because after last update of the addon I've noticed that my zigbee2mqtt dashboard is available only when I open HA via local IP. but if I try to open "from the outside" (I use cloudflare tunnel), my HA dashboard works fine but zigbee2mqtt panel doesn't (devices work normally).
and now I'm guessing if there's something wrong with my network (it worked without problems earlier tho) and the issue accidentally popped up after update, or it is the update that triggered this.

The same behavioral for both... I can access the HA with no problems locally or over the internet, and in both I can't access the Z2M.

Thanks.

ok, so my issue is definitely different.
unfortunately I don't know what to do with your problem, but maybe try to add log_level: error in the advanced block - there is a chance than something will show in the log.

The same behavioral for both... I can access the HA with no problems locally or over the internet, and in both I can't access the Z2M.

Thanks.

I have the same issue

Problem solved for me.  I rebooted the whole system (settings - hardware - [3 dots] reboot system) and all started working properly again.
Hope this helps the others on this issue - it only took me not much more than 4 hours to discover!

Same issue here with 1.29.1-1 and HA 2023.1.0


test: add invalidate query tests

:tada: This PR is included in version 2.22.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"Waypoint Mobile Responsive Images" lesson is badly broken

Lesson: http://www.freecodecamp.com/challenges/waypoint-mobile-responsive-images

Instructions are the wrong way around, should assign the class after instructing you to make the new img tag
Switches from https:// to http:// requirement for second img
If you add img-responsive to the existing img tag you are then unable to complete the lesson even if you add another image below it with the correct src and class
Lesson accepts itself as complete before you have to close the image tag eg: <img class="img-responsive" src="http://bit.ly/fcc-kittens2" is accepted (missing > on the end)
Don't think the notes should have the words responsive design wrapped in a code tag, previously only seen it used to describe markup.
Don't think this needs the caps either: Fortunately, we have access to a Responsive CSS Framework called Bootstrap. should just be responsive CSS framework

Thanks @rtpHarry, It looks like the URL for this challenge has changed to: http://www.freecodecamp.com/challenges/waypoint-make-images-mobile-responsive
I was only able to replicate number 4.  I'll leave this issue open for that

I was able to replicate 3 and 4.
3 should be a non-issue, because the instructions do not ask you to add img-responsive to the first image. The tests have limited power :)

Also, 4 is a duplicated of #1021
Not sure if 3 is going to be fixed so I'll keep the issue open

@rtpHarry thanks for reporting all these issues. Some of them have since been resolved, and I'm accepting @joel-bently's PR to close the remaining ones.


ARTEMIS-2910: consider routing type annotations during auto-creation

Inspects messages sent via anonymous-producers for routing type details to use in auto-creation of the appropriate type of address/queues, instead of just the address name (similar to the additional terminus detail that can be considered when fixed-destination senders are in used). Adds or enhances various tests around auto-creation and anonymous producers.
More detail at https://issues.apache.org/jira/browse/ARTEMIS-2910

+1 lgtm


Fix Windows build

This addresses #6.
More fixes are needed.

is this ready to merge @julianoes ?

No, I have more commits but couldn't push them this morning. 😉 Will do once I'm at home.

@mrpollo ok this builds again in VS2015, good to merge.


upd(bat): 0.21.0 -> 0.22.1

Any way to get this working on Debian?

According to https://github.com/rust-lang/git2-rs/issues/838, debian has much too old version of rust (1.47 on stable afaics)


Monitoring data from IoT devices with Go and Grafana and ESP32

Monitoring data from IoT devices with Go and Grafana
https://cloud.google.com/community/tutorials/monitoring-iot-data-grafana
Author(s): @leozz37 ,   Published: 2020-10-30
Leonardo Lima
Contributed by the Google Cloud community. Not official Google documentation.
In this tutorial, you set up a monitoring environment for IoT devices with an Arduino-based board (ESP32), Grafana, and Google Cloud.
Objectives
Send temperature data from an ESP32 built-in sensor to a temperature topic.
Create a Pub/Sub queue to receive data.
Host a Go service, Prometheus, and a Grafana container on Cloud Run.
Collect temperature data, send it to Prometheus, and show it on Grafana.
Create a Grafana dashboard.
Costs
This tutorial uses billable components of Google Cloud, including the following:

Cloud Run
Pub/Sub
IoT Core

This tutorial should not generate any usage that would not be covered by the free tier, but you can use the pricing calculator to generate a cost estimate based on your projected production usage.
Prerequisites
This tutorial assumes that you're using a Unix-like operating system.
This tutorial requires an ESP32 board.
This tutorial requires the Arduino IDE, so make sure that you have it installed and set up for ESP32 usage. If you need help, you can follow this tutorial.
The instructions in this tutorial use the Cloud SDK command-line interface to set up the environment, but you can use Cloud Console.

Using Prometheus and Grafana for IoT monitoring
https://cloud.google.com/community/tutorials/cloud-iot-prometheus-monitoring
This tutorial walks you through setting up a running stack for IoT monitoring using Prometheus and Grafana with integrations with IoT Core. For a more thorough discussion of the background and concepts, see Remote monitoring and alerting for IoT.
Objectives
Deploy Prometheus and Grafana in Google Kubernetes Engine (GKE).
Examine sample dashboards and Prometheus queries to understand how these tools relate to IoT monitoring use-cases.
Deploy a Cloud Function that responds to alerts.


chore: migrate IoT subscription to CDK

Migrate IoT subscription to CDK (alpha module)

Codecov Report

Merging #22 (b50a7d0) into main (4958138) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #22   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           27        26    -1
=========================================
- Hits            27        26    -1

Impacted Files
Coverage Δ

src/backend-stack.ts
100.00% <100.00%> (ø)

src/lambda/process-metrics-function.ts
100.00% <100.00%> (ø)

src/stateful-stack.ts
100.00% <100.00%> (ø)

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 b7c4370...b50a7d0. Read the comment docs.


Field name in Unicode problem.

Versions:

VueJs: 2.5.9
Vee-Validate: 2.0.0

Description:
The Field Name can't validate with Unicode characters.
Steps To Reproduce:

sorry about the late response. please submit a working example to demonstrate the issue

hi i have an issue with this too. i just tried
return { required: true, regex: /[\u0021-\u007E\u00A1-\u00AC\u00AE-\u00FF\u4E00-\u9FA5\u0E01-\u0E5Ba-z\ ]{2,}/ig}
with this regex and it doesnt work

Hi, in Persian standard keyboard we have
ی
but vee-validate can't get it in alpha rule or anythings like that.
also we have چ and گ
I think it's because of Arabic keyboard
they have ي but Persian keyboard has ی
they are different
thanks

Hi, sorry for comment again, do you want to open this issue? i'm using this validator and i have problem with fa keyboard, thank you :)
@lambdalisue


Linux cuda crash

I'm getting a crash using LLamaSharp.Backend.Cuda11
This problem occurs in 0.6.0 and 0.7.0, and is normal in 0.5.1

Env:
Ubuntu 22.04

We have a new set of binaries ready to release in the next version (very soon). Could you try pulling the master branch and testing if it fixes this issue?

Same error

What CPU and GPU are you using?

CPU: I7-8700
GPU: Titan RTX 24G

It's quite weird because the only difference on compilation of native library since v0.6.0 is avx.
We've published v0.8.0 just now, with a fix for cuda library (but not sure if it's helpful for this issue) and the cuda feature detection in #275. Could you please have a try with it?
If it still doesn't work, you could add NativeLibraryConfig.WithLibrary({Your_DLL_PATH}) at the very beginning of your code, to load a cuda library compiled yourself. That could be a temporary fix.

Oh, it’s normal
Another question, how should I stop printing logs?

Oh, it’s normal

Is the v0.8.0 normal or your self-compiled library normal?

Another question, how should I stop printing logs?

Stopping logs from llama.cpp is an another issue. Currently you could try to redirect the outputs to other where.

Update: this comment will allow you to capture the outputs from native library and output them anywhere else.

Oh, it’s normal

Is the v0.8.0 normal or your self-compiled library normal?

Another question, how should I stop printing logs?

Stopping logs from llama.cpp is an another issue. Currently you could try to redirect the outputs to other where.

v0.8.0

Update: this comment will allow you to capture the outputs from native library and output them anywhere else.

Thank you.


cni: Reserve local ports for DNS proxy even if IPv6 is disabled

This fixes a bug where the port reservation of ports which can conflict with transparent DNS proxy where only reserved if IPv6 was enabled.
The call to reserveLocalIPPorts was accidentally added in the "IPv6-only" branch. This commit fixes that by unconditionally reserving local ports.
Fixes: https://github.com/cilium/cilium/commit/11fe7cc144aaff1a44b6ed9c733a9025c674e683 ("cilium-cni: Reserve ports that can conflict with transparent DNS proxy")

/test


Fix typo in struct HealthCheck

Source code
Branch: master
Commit: latest one 1b9c2582
Issue
In file health.go, Line 30, there is a type error in struct HealthCheck
type HealthCheck struct {
	// ...
	IgnoreHTTP1xx          *bool    `json:"ignoreHttp1xx,ommitempty"`
}

Expectation
The tag ommitempty should be omitempty

Good catch, @zyfdegh!
Would you mind submitting a pull request?

Yeah, I'm on it @timoreimann

Fixed.


Error setting index on variable in @onready var'd node with a custom class when running inside the editor

Godot version
4.0.dev (006cb7def4918ec61df8bfb7d5e672eb8ee71258)
System information
Windows 10
Issue description
I create a main control plugin like I would on 3.x and the scene has an error when accessing one of the child nodes, it's as if the property never existed.
In my case the error is:
SCRIPT ERROR: Invalid set index 'test' (on base: 'Sprite2D (TestThing)') with value of type 'int'.
          at: _ready (res://addons/test_plugin/TestScene.gd:8)

The same code works when running the scene independently (aka F6ing it)
Steps to reproduce
Load the MRP and toggle on and off the test plugin, a strange error will be output into the console.
Minimal reproduction project
EditorInstanceBug.zip

Confirmed the bug is still preset on Godot 4.3
NOTE: The MRP requires two changes in _enter_tree in plugin.gd: instance() -> instantiate() and get_editor_main_control() -> get_editor_main_screen()
You can copy/paste this updated function into plugin.gd:
func _enter_tree():
	main_panel_instance = TestPanel.instantiate()
	get_editor_interface().get_editor_main_screen().add_child(main_panel_instance)

To illustrate the bug, here are the two relevant files:
TestScene.gd:
@tool
extends Control

@onready var test_thing: TestThing = get_node("AnimatedSprite2D")

func _ready():
	print("TEST!!")
	test_thing.test = 2
	print(test_thing.test)

TestThing.gd:
extends Sprite2D

class_name TestThing

var test = 1

func _ready():
	pass

Note that TestThing.gd is missing @tool. That combination of tool script modifying a property on a non-tool script appears to be the cause of this bug in the editor.

Note that TestThing.gd is missing @tool. That combination of tool script modifying a property on a non-tool script appears to be the cause of this bug in the editor.

In which case this is a duplicate of at least one other bug report

(Godot 4.3.stable)
Here is a much more "minimal" MRP: tool-script-error-mrp.zip
When trying to set a node's property in a tool script...
- Node is built-in class -> No error.
- Property is defined in a built-in class -> No error.
- Node was not taken from the scene tree -> No error.
- Node is custom class, from the scene tree, and property is custom -> Error!
Also, the error happens anywhere in a script, not just in _ready().
Title should be changed to something like "Error setting custom variable in custom node when running inside the editor".


Add a new export process.

The new process copies the files from the clean bucket to a new export bucket and then reads the metadata from the database and writes that to a sidecar file.
The original export is unchanged apart from being moved to a sub module.
The release process now publishes a tar.gz file for each submodule. These are released to GitHub together. When the image builds, it pulls both export processes into the image.
When we come to run this, there is a seperate step in the step function for each export process but they're running the same task but with a different command. This should make it fairly easy to retire the old process if we need to.

@TomJKing  This is all up to date now with master, with your comments and with a couple of changes to add the FFID and AV metadata and the redacted file ZREF.


add test for cert rotation type stomping

I would have sworn my original PR had this test....

/lgtm


Add master_org argument/config setting

This is purely for setup and migration. It should be possible to have a master organisation somewhere on the GitHub instance from which master repos can be pulled. This would allow one to keep a persistent master organisation that does not change with new course rounds.
For example, repomate setup --org_name inda-18 --master_org_name inda-master -mn week-1 -s ham spam eggs would set up week-1 repos for ham, spam and eggs based on the repo inda-master/week-1.

This will also require an update to verify_settings


HHH-18737 Introduce util methods for get bean from BeanContainer

[Please describe here what your change is about]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

https://hibernate.atlassian.net/browse/HHH-18737

Ready for review @gavinking

Thanks @quaff, appreciated.

Also appreciate your patience on all this.

Thanks @quaff, appreciated.

Also appreciate your patience on all this.

It’s my honor to participate in this great project.

Thanks again.


add cli support for --transform-key to support mode's like production…

…/staging/etc..

Can this be merged anyway even though tests are failing?
This seems to be not related to my pull request at all.
Only bin/advanced.txt, readme.markdown and bin/args.js were touched.
In bin/args.js it's just one more command line option - so i don't see how this can possibly responsible for the breaking test.

Maybe it would be even better to name it --mode or short -m instead, because --transform-key is kind of long.

@substack another 2 pull request to fix a problem with dependencies that do not specify the alternative --transform-key. They affect browserify and module-deps.

https://github.com/substack/node-browserify/pull/1721
https://github.com/substack/module-deps/pull/131


[ADD ME TO THE ORGANIZATION]

Name: Kaleem Qasim
Location: Pakistan
Interest: Gaming/Learning new technologies
Discord username(optional):- TempeR#1924
Why do you want to join?

I want to join because I want to enhance my skills as well as contributing to open source platform

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@kaleemqasim Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.


Typora update to 0.10.6

The versioning in the filename seems a bit strange at first glance, but installing it updated my installation to 0.10.6.
Please note that the installers on the homepage have different checksums for reasons unknown. I took the download urls from the changelog.

Hello! Sorry for missing this pull request. Note that the package has been taken over, and the package source is now hosted at https://github.com/jtcmedia/chocolatey-packages/tree/master/typora. The package seems pretty up-to-date now. That said, I appreciate your attempt here!


Android Basics: Introduction to Room and Flow

recyclerView = binding.recyclerView
recyclerView.layoutManager = LinearLayoutManager(requireContext())
val busStopAdapter = BusStopAdapter({})
recyclerView.adapter = busStopAdapter
busStopAdapter.submitList(viewModel.scheduleForStopName())

last string replace for
usStopAdapter.submitList(viewModel.scheduleForStopName(stopName))

Thanks for pointing this out! We'll be closing this issue in favor of this issue that describes the same error:
https://github.com/google-developer-training/android-basics-kotlin-bus-schedule-app/issues/32


Date of Birth format wrongly mentioned

Date of Birth format should be Day/ Month/ Year  as Date of Birth in the input field is given in this format only.

Please assign this issue to me under LGM-SOC.
@QAZIMAAZARSHAD

Go ahead

Do changes in both english and hindi page.


OxRDF: Add extra literal escaping to generate canonical N-Triples and N-Quads

Hi @Tpt, thank you for your excellent work!
I recently utilized your oxigraph.io and oxrdf as an N-Quads parser and RDF data structure for my Rust implementation of the W3C RDF Dataset Canonicalization specification.
In this PR, I've introduced additional literal escaping to ensure compliance with the canonical N-Triples and canonical N-Quads specifications. Although these canonical specifications are still in Editor's Draft status, I believe that appropriately escaping these C0 control characters will contribute to a more secure and stable serialization across various use cases.
All tests have passed. If my understanding or usage of Oxigraph is incorrect in any way, please feel free to leave comments on this PR.

I am also asking myself a question: should we ship this change in a minor release (0.3.15) or consider it breaking and wait for 0.4? This change might break some usages already relying on a stable serialization, especially because of the commonly used \t character.

This change might break some usages already relying on a stable serialization, especially because of the commonly used \t character.

Yes, if there exists some quads including horizontal tab (U+0009) for their visual representation in N-Quads layer, such as:
<urn:ex:s> <urn:ex:p> "a    literal    with    tabs" .

(here four whitespaces should be intepreted as a single tab(U+0009))
Then, after this PR it will be breaking-changed to:
<urn:ex:s> <urn:ex:p> "a\tliteral\twith\ttabs" .

However, the application can obtain the former bytes ("a      literal      with       tabs") by parsing the latter N-Quads string ("a\tliteral\twith\ttabs") just using RDF 1.1 N-Quads - 5. Parsing rule. Hence, the impact could be not so huge if I understand correctly...

@yamdan Thank you for your reply! I believe the breaking use cases would be people serializing to NTriples and send using shell scripts to parse the RDF output or people using the serialization for hashing (oxrdf already provides a canonicalization implementation). I plan to do a 0.4 release soon so I would feel better to ship this change as part of it. Is it fine with you?

I am merging into the next branch that will become the 0.4 release. Thank you so much for this PR!


fix(tooltip): set max width for the tooltip

Closes: https://github.com/tremorlabs/tremor/issues/454#issue-1707959713

Hmm I would say it is the responsibility of the end user to avoid tooltips of that size. Setting a max width feels a bit hacky / restrictive, wdyt?

I think the library should be prepared for long tooltips. It may not be very popular but sometimes it's needed.
Another question is that how much is too long? A small text on desktop might be too long for mobile and if we don't limit the width, mobile users will potentially experience the bug. So I think it's better to be fixed on the Tremor side.
I also checked the Tooltip component of Chakra-UI and they also limit the tooltip width: https://github.com/chakra-ui/chakra-ui/blob/38acfe89c5d1f1edc67bbc44e2edd38980ca3e08/packages/components/theme/src/components/tooltip.ts#LL24C10-L24C10

It also makes tooltips look nicer and more readable in my opinion. Compare this:

With this:

Fair point, agree!


Several warnings and errors displayed in console

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.1
OS Version: Ubuntu 23.04

Steps to Reproduce

Open console
Several warnings and errors are displayed

Expected behaviour
Only the git error is displayed.
Actual behaviour
Several other errors/warnings are displayed in addition to the git error.
WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-dotnettools.dotnet-interactive-vscode' wants API proposal 'languageConfigurationAutoClosingPairs' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
WARN Via 'product.json#extensionEnabledApiProposals' extension 'github.copilot-chat' wants API proposal 'terminalContextMenu' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
ERR [ms-vscode.vscode-js-profile-flame]: Menu item references a command `extension.js-debug.startProfile` which is not defined in the 'commands' section.
[Extension Host]  Quokka.js Live Share integration disabled, VSLS not found.
INFO Invalidating Cache Array(16) Array(15)
ERR Error: Unable to delete nonexistent file 'vscode-userdata:/home/simon/.config/Code/CachedProfilesData/__default__profile__/extensions.user.cache'
INFO [perf] Render performance baseline is 101ms
[Extension Host] [vscode-icons] v12.5.0 activated!
[Extension Host] rejected promise not handled within 1 second: Failed to execute git {
  "exitCode": 128,
  "gitErrorCode": "RemoteConnectionError",
  "gitCommand": "push",
  "stdout": "",
  "stderr": "ssh: connect to host github.com port 22: Connection timed out\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n"
}
ERR Failed to execute git

Do these errors still happen if you disable the Javascript Debugger (ms-vscode.js-debug)? If they disappear, it'd be best to file an issue there instead.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Error - 404

Version
1.8.0
Details
Copied link to a video by right clicking on video and copying url.

Thank you for your continued efforts
Steps to reproduce
Just try to download a video. It is a video uploaded on april 30, 2021.

This does not affect all videos. I do not know of a pattern.

Able to reproduce error with the following URL: https://www.youtube.com/watch?v=d7riL6IXi5o

With all the links I tested to download gave this same error.

same error here, no idea what causes it although I'm pretty certain that the video or link doesn't matter... probably some sort of firewall or network error

Getting the same error here on all videos. Yeah I think YouTube changed their website again.  We need to wait for @Tyrrrz to reverse-engineering whatever they changed yet again...

YouTube changed the get_video endpoint.
I have done a fix here. https://github.com/thisistorsten/YouTubeApiSharp
You need to add html5=1 to the url.

Yep, can confirm it works now with latest that adds &html5=1. Thanks a lot for the quick turn around and in describing the fix.


R2SCAN-3c

Feature request for R2SCAN-3c. The Summary and Conclusions of the paper makes the case pretty well.
https://doi.org/10.1063/5.0040021
Requires D4, gCP and a tailored basis set.
R2SCAN is used unaltered, and I see there is a pull request for libxc 5.1.0 which contains that DFA.

@hebrewsnabla are there still plans to implement b97-3c?

@hebrewsnabla are there still plans to implement b97-3c?

Yes. I will continue the progress of #1358 in pyscf-forge. But, still, it will be much more comfortable if we can have a python api for gcp, which may be coming soon according to https://github.com/grimme-lab/gcp/issues/5.

But, still, it will be much more comfortable if we can have a python api for gcp, which may be coming soon according to https://github.com/grimme-lab/gcp/issues/5.

The gcp development currently has pretty much halted as far as I can tell, maybe it is worth to reach out to the people in the Grimme group to get this project of the ground again.


how to set Cost variable?

I am trying to input cost of charging and the link under charges tries to take me to a url that is blank. I see the Json for charges but I don't see where to set the cost per kWh?

Also experiencing this, the 'Set Cost' link is directing to http://teslamate:3000:/charge-cost/1 which does not exist.

I don't even see the option to enter this - where in charges do you see this? I can see this is in the charging_processes table, but where does one enter the cost?

There isn't the ability to set the cost, if you check the queries you'll see there is no variable referenced. Looks like this part is a work in progress.
You can however edit the query and make a custom dashboard and hard code your cost to make it render correctly.
For example, in charging stats, you can edit the query and replace the select with this:
SELECT
COALESCE(geofence.name, CONCAT_WS(', ', COALESCE(address.name, CONCAT_WS(' ', address.road, address.house_number)), address.city)) AS location,
sum(charge_energy_added) as charge_energy_added, (sum(charge_energy_added)*0.13) as Cost
(change 0.13 to however much it costs per kwh)
The chart will now display 3 columns, including cost.

Field is there for future use, up to now you need to set the costs by database query, see #185

Thanks guys I got he cost to show up using the following query under the Charging stats dashboard
SELECT
sum(charge_energy_added) as charge_energy_added, (sum(charge_energy_added)*0.11) as Cost
FROM
charging_processes
WHERE
car_id = $car_id;

Thanks. I was also able to change the query to show cost.
@JakobLichterfeld just for understanding the cost field  in the table is currently the total cost  for that session.
ie charged*cost/kWh. This needs to be calculated everytime based on the cost/kWh.
It will be null by default.
What is the charge_energy_used?

@JakobLichterfeld just for understanding the cost field in the table is currently the total cost for that session.
ie charged*cost/kWh. This needs to be calculated everytime based on the cost/kWh.
It will be null by default.
What is the charge_energy_used?

Yes, this is for logging the costs of the charge. Sometimes you pay per charge sometimes per kWh added. So manual input needed. The field is in the database scheme already, but the UI part to set the total cost for this charge is not yet implemented. If you want to track them anyway, you need to set it with a query, see #185

Thanks. I was also able to change the query to show cost.
@JakobLichterfeld just for understanding the cost field in the table is currently the total cost for that session.
ie charged*cost/kWh. This needs to be calculated everytime based on the cost/kWh.
It will be null by default.
What is the charge_energy_used?

I get it to show on the dashboard but it will not let me save the dashboard or the query using gafana even though I am logged in as admin? It says "This dashboard cannot be saved from Grafana's UI since it has been provisioned from another source. Copy the JSON or save it to a file below. Then you can update your dashboard in corresponding provisioning source." the source is the TeslaMate DB so the queries are in the DB as well?

You save it as a new dashboard. You cant overwrite the defaults.

the source is the TeslaMate DB so the queries are in the DB as well? I have no idea how to access the DB inside a Docker :)

Yeah. If you use the docker-compose file you have set up a volume for the DB, so it is not inside the docker :)

Can someone help how this can be done if my metering is set to Time-Of-Use? The cost is different based on time it was charged. Thanks in advance.


buildEnv: respect user-chosen output even with extraOutputsToInstall

Motivation for this change
When user gives an explicit output for buildEnv, for example gcc.cc.lib, if extraOutputsToInstall is specified gcc.cc.lib.foo would also be included, even though this might not be what the user wanted. This reverses the behaviour, so if an output is explicitly specified no additional ones would be installed.
For example of when this is useful: this removes gcc.out references from buildFHSEnv environments.
Not mass-rebuildy as far as I can see.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @vcunat -- was there a purpose for the initial design?

Well, this depends on what the option is supposed to mean, as the user explicitly passed extraOutputsToInstall, too. I can't see a clear winner ATM.
Note that this is set by nixos config for the system env, and this PR may e.g. exclude some man pages in some configs (when modules put foo.out or foo.bin into systemPackages). It would seem better to me to include them in those cases, but maybe that should be expressed in some other way...

Hmm, indeed. Maybe this should be rather documented with some workaround... maybe toString would help. I'll test later.

removeAttrs gcc.cc.lib ["foo"] should certainly work in your case, but it utilizes knowledge about buildEnv implementation...

After more thinking, it does seem to me that not respecting extraOutputsToInstall when an output is chosen is more logical, because one can guess that without knowing our "outputs are recursively available in outputs" thing. That is, one might more likely expect that when he specifies foo.lib, foo.bin won't be used because it's not exposed at all.
However, I feel too biased to make any conclusions, and also completely skip the question of convenience (current way may make some patterns easier) and cost of changing vs benefits (it seems we don't use that corner case much, but I cannot testify). So I'm unsure how to proceed with this...

Let's just document this behavior for now, I think.

@abbradar so are you going to document this? Should this be merged? closed? I guess you can merge it youself…

I forgot about this completely D:
As I've said this is a controversial change without much benefit -- I'm personally for it but unless there is strong support I say let's just close it. I'll write documentation (and try not to forget this time :D) if workarounds listed in it would seem too awful we might return to this question ~_^


app scrobbles on its own, always the same song

Hi. For a few months my phone (galaxy s5) puts up to three different songs in its cache and submits it seemingly on random, resulting in one or two songs being scrobbled up to a dozen times in a row with irregular time between submitting. All while I'm not listening to music on this device or at all.
I just noticed this recently but like I said, it's been going on for at least two or three months. One song has been submitted about a hundred times since June. Another one is on a good way for doing the same.
My profile is
last.fm/user/oo-
Some of the songs are:
The Devil's Blood - She
Year of the Goat - Riders of Vultures
Dødheimsgard - Blue Moon Duel
Blind Guardian - Under the Ice
At least those are some I noticed. I also started deleting some submissions yesterday already.
Any idea?
Thanks

Could what music player(s) you use?
Is this problem the same as yours #79 ?

Hi and thank you for your reply.  It reads similar, but as I said it happens with more than one song as the other guy described.
I'm using the built-in music app on my galaxy s5. It's simply called 'Musik' (german),  can't seem to find much about it

https://www.safaribooksonline.com/library/view/galaxy-s5-the/9781491905098/ch04.html

Duplicate #79


How to use this plugin. Merge branches?

How to use this plugin. Merge branches?
I use it for errors

[Error-17:59:14.131] Error while mergning
[Error-17:59:14.131] merge: ' - not something we can merge

You run the command "Git: Merge From" and select the branch you want to merge into your current branch.
Can you give me some more info? like the name of the branch you tried merging.
Does this error happen with every branch you try to merge?

Thank you for your answer. Yes, bug can not be merged after the update, and thank you for developing the plug-in for vscode


Add event system revised

Can we still submit PR's?

@sriking1783, yeah you can still submit PR's!

Great job!  There's a lot of unused files or generated comments that you could do without.  Otherwise, though, this looks pretty clean.  No need for a resubmission.


Transactions with FT are displaying differently

Describe the bug
Transactions with FT are displaying differently for Spend In and Spend Out Txs
To Reproduce
Steps to reproduce the behavior:

Go to Tx list
Compare Txs for FT - Spend In and Spend Out
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Browser  chrome, safari, FF
Version 123, 122

Additional context
reproducible on product.
https://github.com/superhero-com/superhero-wallet/assets/69896204/61c6a7af-dff8-4cd3-8a68-728805e31af6

fixed by #2895


Added search model API

Description
User can search by providing fields of API_BODY one by one or user can search by providing json manually. Tests with passing arguments and by passing manually json are created. In test's try block I am checking if response does not contain "status" field  because "status" field is returning only when there are errors.
Issues Resolved
https://github.com/opensearch-project/opensearch-py-ml/issues/104
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@2c73825). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #142   +/-   ##
=======================================
  Coverage        ?   90.00%
=======================================
  Files           ?       29
  Lines           ?     3503
  Branches        ?        0
=======================================
  Hits            ?     3153
  Misses          ?      350
  Partials        ?        0

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


Bug: Fix Railway Deploy

Description
Get the Railway deploy up and working
URL to code causing the issue
https://railway.app/project/6f1f252f-a6f4-42ab-a5c7-6ba05c3f74de/service/944db6ab-1591-48f8-84f3-203c66e234e1?id=492a5cfa-7abf-415b-870d-d17a82989a45
MCVE
No response
Steps to reproduce
No response
Screenshots
No response
Logs
engine = create_async_engine(
^^^^^^^^^^^^^^^^^^^^
File "/opt/venv/lib/python3.11/site-packages/sqlalchemy/ext/asyncio/engine.py", line 117, in create_async_engine
sync_engine = _create_engine(url, **kw)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "<string>", line 2, in create_engine
File "/opt/venv/lib/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned
return fn(*args, **kwargs)  # type: ignore[no-any-return]
^^^^^^^^^^^^^^^^^^^
File "/opt/venv/lib/python3.11/site-packages/sqlalchemy/engine/create.py", line 601, in create_engine
dbapi = dbapi_meth(**dbapi_args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi
import psycopg2
ModuleNotFoundError: No module named 'psycopg2'

### Package Version

Current

### Platform

- [X] Linux
- [ ] Mac
- [ ] Windows
- [ ] Other (Please specify in the description above)

Closed by latest PR


Fix TreeView.SelectionModeProperty not working via styles

What does the pull request do?

Makes TreeView.SelectionModeProperty public and registers it correctly on a TreeView type.
What is the current behavior?

If you use a style to set SelectionMode on a TreeView you will get an exception, since it is not registered.
What is the updated/expected behavior with this PR?

You can use styles to set SelectionMode on a TreeView.
How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Fixed issues

Thanks @MarchingCube !


Fix extension load issues on insider build

There are issues loading the import extension due to vscode version check and azurecore due to inability to find npm module.  This fixes these issues in the packaged insider build.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 37.409%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14132

Relevant Lines:
34731

💛  - Coveralls


add tests for public and logged_in

I read-public.test.ts I had to replace some 403 with 4xx. NSS is returning 401 and I don't know what the good result is.

Yes, I think if no Authorization header is sent then the response would be 401, and if the Authorization header that was sent is insufficiently powerful, then it would be 403.


Clean up influx_inspect export command and improve performance

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated

I cleaned up and reorganized the influx_inspect export command code and added tests and benchmarks, and then I made exports go quite a bit faster.
(This benchmark is updated from a commit message to include the EscapeStringField optimization.)
benchmark                                   old ns/op     new ns/op     delta
BenchmarkExportTSMFloats_100s_250vps-4      23206480      10279106      -55.71%
BenchmarkExportTSMInts_100s_250vps-4        17995000      5762310       -67.98%
BenchmarkExportTSMBools_100s_250vps-4       17067605      4235467       -75.18%
BenchmarkExportTSMStrings_100s_250vps-4     51858849      27720601      -46.55%
BenchmarkExportWALFloats_100s_250vps-4      23459937      10436297      -55.51%
BenchmarkExportWALInts_100s_250vps-4        18747150      6236062       -66.74%
BenchmarkExportWALBools_100s_250vps-4       17988273      4814358       -73.24%
BenchmarkExportWALStrings_100s_250vps-4     55168996      29045761      -47.35%

benchmark                                   old allocs     new allocs     delta
BenchmarkExportTSMFloats_100s_250vps-4      201442         51738          -74.32%
BenchmarkExportTSMInts_100s_250vps-4        201442         51728          -74.32%
BenchmarkExportTSMBools_100s_250vps-4       201441         51638          -74.37%
BenchmarkExportTSMStrings_100s_250vps-4     404067         76938          -80.96%
BenchmarkExportWALFloats_100s_250vps-4      250322         75627          -69.79%
BenchmarkExportWALInts_100s_250vps-4        250323         75617          -69.79%
BenchmarkExportWALBools_100s_250vps-4       250321         75527          -69.83%
BenchmarkExportWALStrings_100s_250vps-4     452830         100729         -77.76%

benchmark                                   old bytes     new bytes     delta
BenchmarkExportTSMFloats_100s_250vps-4      5170539       2351789       -54.52%
BenchmarkExportTSMInts_100s_250vps-4        5143189       2331276       -54.67%
BenchmarkExportTSMBools_100s_250vps-4       3724951       2143780       -42.45%
BenchmarkExportTSMStrings_100s_250vps-4     17136727      6062059       -64.63%
BenchmarkExportWALFloats_100s_250vps-4      4487868       1468109       -67.29%
BenchmarkExportWALInts_100s_250vps-4        4458395       1452359       -67.42%
BenchmarkExportWALBools_100s_250vps-4       2838719       1258755       -55.66%
BenchmarkExportWALStrings_100s_250vps-4     16714986      5286940       -68.37%

Also, after improving those benchmarks, I did a time-filtered export on
a 450MB TSM file to a 21GB plain text output, with and without the
bufio.BufferedWriter.
Without buffering, it took about 263s, and with buffering, it took about
60s, for a delta of about -77%.

w needs to be typed as an IO Writer so the gzip writer can be conditionally
assigned to w later.
In fact I need to double check whether it performs better with the buffered
writer in front of the gzip writer. I suspect it will.
On Mon, Dec 19, 2016 at 4:30 AM Edd Robinson<EMAIL_ADDRESS>wrote:

@e-dard approved this pull request.
Just a small nit, otherwise LGTM 👍
In cmd/influx_inspect/export/export.go
https://github.com/influxdata/influxdb/pull/7741#pullrequestreview-13542021
:

if err != nil {

  return err

}

defer w.Close()

defer f.Close()

// Because calling (*os.File).Write is relatively expensive,

// and we don't need to sync to disk on every written line of export,

// use a sized buffered writer so that we only sync the file every megabyte.

bw := bufio.NewWriterSize(f, 1024*1024)

Can this not just be w := bufio.... and then we don't need the var w = bw
below?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/pull/7741#pullrequestreview-13542021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARvV1bBrt_w4KrcOlX4z1Bt85i1rxuaks5rJnjtgaJpZM4LQC9j
.

Using my earlier test case of a 450MB TSM file that, when time-filtered, exports to a 21GB plain text file or a 650MB gzipped text file, I found:
time influx_inspect export -datadir . -waldir . -start '2016-12-13T10:59:49Z' -compress -out ./s4.2.txt.gz

# 1.1.1
real	5m7.206s
user	5m8.761s
sys	0m7.027s

# buf -> gzw -> f
real	3m53.893s
user	3m51.619s
sys	0m5.935s

# gzw -> buf -> f (behavior as committed in PR)
real	3m52.385s
user	3m54.782s
sys	0m1.984s

So the real time is about the same whether the buffer writer is before or after the gzip writer, but putting the gzip writer before the buffered writer seems to result in fewer file writes, which seems like the better win.

Nice speedup!


Added big nav-bar on hover

Closes #223
FEATURE
New navbar design, big navbar on hover
Screenshots

Code of Conduct

[x] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

If you have any questions or doubts, you can ask

Sir i was in a exam will soon get back to the issue

Sir i was in a exam will soon get back to the issue

No worries, I will manage my self 😄


Updating package dependencies

Hi! Is there a possibility to upgrade lodash dependency form 4.17.11 to >= 14.17.12?
It cause the issue during performing a vulnerability audit against the installed packages.

Maybe straight to 14.17.20?
See CVE: https://nvd.nist.gov/vuln/detail/CVE-2020-8203


Add relative time concepts to the core TimeSkill component

I have found that the SequentialPlanner regularly becomes confused when it is asked to deal with relative time concepts like "last wednesday" or "5 days ago". It will often try and make use of the supplied date() skill, adding a parameter to offset it (which is not supported). I propose that we add two new skills - one to find the date of the last instance of a given day name, and another to provide the date x days in the past.
Pull request adding these will be sent soon.

@tim-gill can't wait to see the PR come in!

It is up at https://github.com/microsoft/semantic-kernel/pull/927 - would love feedback

The one for day names worries me a little as it is currently locked to English day names. Suggestions on making it more general purpose would be great.


Option to copy rather than dump?

In order to help us troubleshoot issues with this project, you must provide the following details:

ElasticDump version: 3.1.0
Elasticsearch version: 2.3.2
Node.js version (note that nodejs v8+ is required for this tool): v10.13.0
Full command you are having issue with (with inputs and outputs): n/a
A data set you can share publicly which reproduces the problem: n/a

Is there a way to perform an 'copy' operation when the input host and output host are the same?
Am I incorrect is assuming that when running this from my localhost creates temp files on my machine?
elasticdump --input=host1:9200/index1 --output=host1:9200/index2

copy/dump/move/re-index.. Different name for the same thing. Your assumption is incorrect.
All data is streams, elasticdump has what are call transports. The transports are responsible for directing where input/output goes. So in essence the above command is valid.
There's an example section of the README. Check it out, thanks. https://github.com/taskrabbit/elasticsearch-dump
# copies index1 data to index2
elasticdump --input=host1:9200/index1 --output=host1:9200/index2

So should it be faster to run that command or this one?
ssh host1 && elasticdump --input=localhost:9200/index1 --output=localhost:9200/index2

The first command you’re connecting running esdump on the box, the second I assume your sshing then running it ? Shouldn’t be different once you’re connected

from my local, i.e.: running esdump locally, took about 2.5 hours:
elasticdump --input=host1:9200/index1 --output=host1:9200/index2
sshing to the es host then running esdump on that host took about 1.3 hours:
ssh host1 && elasticdump --input=localhost:9200/index1 --output=localhost:9200/index2
It seems that running locally vs running on the host does make a difference.
My question is about the apparent bottleneck here.  I guess the best answer is to just run the esdump operation on the ES host itself rather than from remote.

It would, but that’s a network issue, not a elasticdump issue


Add kuberlr

https://github.com/flavio/kuberlr
Might be useful in regards to differing kubectl versions

not relevant at the moment


[SDK] Add tests for chain utils

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on enhancing the functionality and testing of chain definitions in the thirdweb library. It exports certain functions for testing and introduces a legacyChain object to facilitate conversions and validations regarding blockchain chains.
Detailed summary

Exported CUSTOM_CHAIN_MAP and convertLegacyChain functions with internal documentation.
Introduced a legacyChain object representing Ethereum Mainnet.
Added tests for:

getChainSymbol and getChainDecimals handling chains without symbols/decimals.
Conversion of legacyChain using convertLegacyChain.
Usage of defineChain with legacyChain.
Proper caching of chains with cacheChains.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5280  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kien-ngo and the rest of your teammates on  Graphite

Merge activity

Nov 4, 3:05 PM EST: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.