2024.11.0 WebRTC stream not working

Version of the custom_component
5.4.0

Configuration

Describe the bug
After HASS upgrade to 2024.11, streams for cameras that exposed via Frigate/Frigate integration are stoped working, only static image. I'm not using Frigate card, only native HASS camera view.
Information about my steup:

frigate are up and running on a separate host (<IP_ADDRESS> in logs) from homeassistant
frigate proxy addon are configured on hass and connected to frigate instance

WebRTC is enabled in Frigate Integration. No errors in browser console.
Debug log

2024-11-07 23:02:06.445 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140568319030848] Error handling message: Unknown error (unknown_error) from <IP_ADDRESS> (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/camera/webrtc.py", line 263, in ws_webrtc_offer
    await camera.async_handle_async_webrtc_offer(offer, session_id, send_message)
  File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 634, in async_handle_async_webrtc_offer
    answer = await self.async_handle_web_rtc_offer(offer_sdp)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigate/camera.py", line 332, in async_handle_web_rtc_offer
    answer = await resp.json()
             ^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 80, in json
    return await super().json(*args, loads=loads, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1277, in json
    raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 500, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='http://<IP_ADDRESS>:5000/api/go2rtc/webrtc?src=cam_back'

Also, my cameras stream in h265, supposed, webrtc should not work(I may be wrong).
Probably, url in log not accessible (http://<IP_ADDRESS>:5000/api/go2rtc/webrtc?src=cam_back)

I seem to be having a similar issue.  After upgrade I am only seeing static images when I click my Frigate camera entities.  I prefer to use the native camera view but I tried in the Frigate card.  In the Frigate card the stream does work.

do you have webrtc enabled in the frigate integration configure menu?

Same issue (static image instead of stream). I just tried checking webrtc enabled and it did not affect the stream in picture entity card. This was working in previous 2024.10 fine with WebRTC integration. I deleted the WebRTC integration because I thought I didn't need it, but added it back now and the stream still doesn't work.

same issue after upgrated HASS to 2024.11

HASS stopped supporting WEBRTC, not it has native and I think integration must be updated

The same implementation still works the same, and multiple users confirmed during the beta that it works without issues

do you have webrtc enabled in the frigate integration configure menu?

Thanks!  Once I enabled WebRTC in the configure menu it started to work.  For others, perhaps WebRTC is not setup in your frigate config?
However, I thought it used to work with MSE and didn't require WebRTC for the Frigate integration.

Oh yeah, previously I must have been using MSE since HA didn't support Webrtc in native cards even with the HACs integration. The bigger problem here might be the fallback to MSE is not working correctly. (Although we also need to figure out WebRTC is not working for so many of us).

HA does not use MSE in native cards, in the past it used HLS

will try

HA does not use MSE in native cards, in the past it used HLS

Thanks, HLS is what I meant then.
I now have WebRTC working after following you instructions two posts up on enabling WebRTC in Frigate and its integration.
I think this issue can be closed but another issue is the HLS fallback is not working for the Go2RTC streams in a native home assistant card.

tried to enable webrtc - nothing helps.
From homeassistant GUI camera view works, but recordings - do not

From homeassistant GUI camera view works, but recordings - do not

that is an unrelated issue, and a bug in home assistant

A mi tambien me pasa desde que actualizaron ya no puedo ver los videos en la lovelace es un desastre.Me salen los iconos de las grabaciones pero no se reproducen se quedan cargando y no funcionan.

I don't know if this is related but after 24.11 a camera feed can mess up other things on the HA dash. The feeds are working both faster and more consistent but other, very unrelated, things are suffering.
Everything works fine until you ho to a tab with one or more camera feeds. After that this will happen!

If you are editing dash, gui for edit cards will come up blank, with just the header.
Trying to access "more information" page on a device, typically light or thermostat, that also will come up blank with just the header menu bar.
Trying to open device information will result in a completely blank screen. Without even the header.
Some cards will no longer be able to access any data. E.g. calendar card will show "no object found"
Trying to reload page will result in a timeout. Can not reach server. This happens both on web, ios&android companion apps. Only way out is to kill app and restart or on webb press stop and reload from start page.

After killing app/web page and restarting again, everything is back to normal again, until you go to a tab with camera feeds and the bug will reappear. Note you don't have to restart anything in the server end, just the client.
This is from the system/loggs
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found, rtsps://:@wework-3-eu.stream.iot-11.com:443/v1/bfb0007feb7325bde9ywiw/css6opnhbmf6r7ds32c0qU1BbaAij5hP?signInfo=jRfl7COIsQk_b44JRxkk4LNvnA-eHINxTUJayaH-K5a_FeL8NDLjMxp0HdKLkfNBPSBwLIIcxAUbxcbJSH3XA498i46qtgEcOH4GZhyfddpmCzBU9rjMuMl3fccohiK4cZp_KEScqR6PVIKAV7HTi5S2kffAKCoAY4-WUieOWSE)

tried to enable webrtc - nothing helps. From homeassistant GUI camera view works, but recordings - do not I can see images of existing recording - but playback - fails in Frigate GUI - everything works

I am experiencing the same problems.

I am experiencing the same problems.

According to Hass Core - frigate integration needs to be updated.
https://github.com/home-assistant/core/issues/129990#issuecomment-2493742120
@NickM-27 @blakeblackshear

@timota We see it too ;-)

tried to enable webrtc - nothing helps. From homeassistant GUI camera view works, but recordings - do not I can see images of existing recording - but playback - fails in Frigate GUI - everything works

Please note there are two issues tangled. I think what is described above (broken media) is a different bug in Home Assistant that is already fixed there (https://github.com/home-assistant/frontend/issues/22755). We just need to wait for a release.
For this issue (live streams):

It seems like the "fix" here is that instead of having both webrtc and hls support in a single camera entity, the HA stance is now to have two different cameras [one with the webrtc methods, one without, e.g. camera.office and separately camera.office_webrtc].
An alternative would be to only support webrtc (get rid of the option), but this would break for anyone without webrtc enabled in go2rtc

@NickM-27 @felipecrs
Seems like option 1?

@dermotduffy have you found any example of an integration that "implements" 1?

@dermotduffy have you found any example of an integration that "implements" 1?

The builtin Nest camera (code) appears to follow this pattern. Not really sure what the alternative is if they're going to remove frontend_stream_type. Open to ideas :-)
Probably the right thing to do would be to remove the enable_webrtc option entirely, and just have a FrigateWebRTCCamera class / entity that is disabled by default but can be enabled. That's a roughly equivalent user journey to the current enable_webrtc option and would be a pretty small code change.
Downside of all of this is that anyone with webrtc enabled will need to update anything that refers to their camera entity (e.g. automation, Frigate Cards, dashboards, etc).

Maybe the key is to only provide an RTSP link back to Home Assistant?
For example, Tuya integration wasn't changed (apparently) for 2024.11.
https://github.com/home-assistant/core/blob/dev/homeassistant%2Fcomponents%2Ftuya%2Fcamera.py#L82
The only thing this function does is to provide an RTSP link to the camera.
And then I guess HA decides the best way to stream it?
(Sorry, I am really just guessing, this may be completely useless)

For example, Tuya integration wasn't changed (apparently) for 2024.11.
https://github.com/home-assistant/core/blob/dev/homeassistant%2Fcomponents%2Ftuya%2Fcamera.py#L82

Does it actually support webrtc though? Does not have a async_handle_async_webrtc_offer method ...

@dermotduffy I believe Nest is an special case where some cameras can only be streamed over WebRTC, they have no RTSP interface.
Maybe for cameras which has an RTSP interface, providing a native WebRTC handling is unnecessary.

Maybe for cameras which has an RTSP interface, providing a native WebRTC handling is unnecessary.

i.e. there's magic in Home Assistant (via built-in go2rtc) that will have this work out of the box? Let me quickly edit the integration and test...

But option 2 (only provide WebRTC) also seems ok, because HA still manages to play it through HLS if necessary:
https://github.com/blakeblackshear/frigate-hass-integration/issues/759#issuecomment-2461009861

For example, Tuya integration wasn't changed (apparently) for 2024.11.
https://github.com/home-assistant/core/blob/dev/homeassistant%2Fcomponents%2Ftuya%2Fcamera.py#L82

Does it actually support webrtc though? Does not have a async_handle_async_webrtc_offer method ...

Not natively, but that's the thing: it does not need to. HA 2024.11 will feed its RTSP into HA's go2rtc, which then enables WebRTC stream.

But option 2 (only provide WebRTC) also seems ok, because HA still manages to play it through HLS if necessary:

... presumably not if the person doesn't have webrtc configured in their Frigate go2rtc instance, though.

... presumably not if the person doesn't have webrtc configured in their Frigate go2rtc instance, though.

Oh yeah, you're right. That's a good reason to avoid this option if the "simple" RTSP works.

Update: Myself and @felipecrs played around and think we have a fix. PR coming soon...

Thank you!
PS: @dermotduffy did everything. I was just giving guesses.

Please try out the new pre-release (v5.5.0) which includes this fix.

Thanks for the fix—it does work, but the video isn’t smooth, and the sound cuts off after the first second. Compared to how it worked previously, the difference is significant.

yeah it looks like it is using HLS now, not webrtc

@NickM-27, I found the same thing btw. I guess this is a bug in go2rtc.
I suppose the best for now is to not use Frigate's go2rtc inside HA.


Add trace-per-test option

Trace-per-run is not always great e.g. it's confusing to have a sequence of tests which are normally independent, and then the layout changes when xdist is involved as you get concurrent spans (one for each worker).
This also causes issues in the more bare-bone / simplistic frontends / final collectors (e.g. OpenTelemetry Desktop) as they might not have the most complex folding and filtering features. OTD for instance has little to no ability to manipulate spans, but it is possible to select individual traces and see just that trace's spans (in fact that's the only mode).
As a result, generating a separate trace per test per run allows easier classification, observation, and manipulation of the trace. I would also assume in the long term it allows comparing the traces of the same test in order to get insight into their evolution, something which is more difficult with trace-per-run.
Finally an other issue with trace-per-run, mostly in long suites, is that the trace remains incomplete (tools complain of missing parent spans) until the entire run has completed, making observation during run more difficult.
Fixes #33

@xmo-odoo I do like this idea, but would we really need a full new copy of the plugin?  Could this be done conditionally?

I'll buy that!  Just looks like we're missing one line of coverage for the item_parent property, should be easy to add.  Thanks!


[ATX V2] Make VRF nonce and coinbase required

Description
Make VRF nonce and coinbase required in ATX V2 to avoid having to do a costly search of the previous ATXs tree (potentially back to genesis) to find the ATX published by the same smesher ID.
Test Plan
Tests pass
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

Bors try

bors merge


Submitting a new blog post link

 Issue by peterjohnlightfoot
Monday Jul 31, 2017 at 10:38 GMT
Originally opened as https://github.com/Wyamio/Wyam.Web/pull/50

peterjohnlightfoot included the following code: https://github.com/Wyamio/Wyam.Web/pull/50/commits

 Comment by daveaglick
Monday Aug 14, 2017 at 17:53 GMT

Somehow missed this earlier, thanks!


Dispatch app is missing Utterances from few Qna's

Describe the bug
I am creating dispatch app with 1 luis and 4 faqs. Until the end everything work fine and I can see dispatch app created on luis.ai. But, there are few concerns

I am not able to see any utterances under 2 Intents in dispatch app which supposed to be fetched from 2 respective qna's.

Intent names as all follows.
q_ExperienceStrategistKb
q_ExperienceGeneralKb

Here are the logs from CMD that shows ExperienceStrategistKb and ExperienceGeneralKb was exported correctly.

What does these WARNINGs mean ??
Exporting services for dispatch...
Exporting CalendarAssistantDev LUIS application...
Exporting HRQnA QnA kb...
Exporting CEPKb QnA kb...
Exporting **ExperienceGeneralKb** QnA kb...
Exporting **ExperienceStrategistKb** QnA kb...
Creating dispatch LUIS model json...
Creating training data...
WARNING: Number of samples in '/Dispatch/data/_experiments/model_011/train.txt' that were used by multiple categories: 60
WARNING: Number of samples in '/Dispatch/data/_experiments/model_011/cv5/fold000/train.txt' that were used by multiple categories: 42
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold000/test.txt' that were used by multiple categories: 7
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold001/train.txt' that were used by multiple categories: 42
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold001/test.txt' that were used by multiple categories: 6
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold002/train.txt' that were used by multiple categories: 41
WARNING: Number of samples in Dispatch/data/_experiments/model_011/cv5/fold002/test.txt' that were used by multiple categories: 3
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold003/train.txt' that were used by multiple categories: 41
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold003/test.txt' that were used by multiple categories: 6
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold004/train.txt' that were used by multiple categories: 39
WARNING: Number of samples in 'Dispatch/data/_experiments/model_011/cv5/fold004/test.txt' that were used by multiple categories: 3
Updating GinaDispatchDev model...
Importing GinaDispatchDev model...
Training GinaDispatchDev model...
Publishing GinaDispatchDev model...
Writing summary file...
{
  "authoringRegion": "westus",
  "hierarchical": true,
  "services": [

To Reproduce
Steps to reproduce the behavior:
Just used this document to create dispatch app.
Expected behavior
All the questions from QnA's should be fetched under respective INTENT in Dispatch App.
Additional context
Not sure if this issue is related another issue I reported where dispatch takes over 3-4 hours to finish.

Hi @rjgmail88, from the Dispatch CLI  warning messages, your LUIS and QnA apps have some duplicate utterances. These duplicates will be de-duped by LUIS when the dispatch JSON model was uploaded to luis.ai, thus some intents may have zero utterances in them.
luis.ai will fail training an app with any zero-utterance intents. Dispatch CLI retries training LUIS models over transient failures, but early Dispatch CLI release will also retry for the zero-utterance failures -- this can lead to 3-4 hour training time that ends in failure.
Recent Dispatch CLI release checks if there is any intent with zero utterances and will end the process with an error message.


BUG: Stacked Tabs Not Sliding with Trackpad Gestures – Style Settings plugin

Hi,
I am loving the Border theme, but I've noticed when using stacked tabs I'm not able to "slide" between the tabs with the trackpad like I can in other themes.
I did a little digging and noticed when I turned off the Style Settings plugin, the sliding through the tabs/panes in the stacked tabs with the trackpad worked great. But when I turned the Style Settings plugin back on, I was not able to slide with the trackpad. So something in the Style Settings seems to be interfering with the trackpad gestures.
Let me know if you need anything else from me. Thanks!

Is this issue similar to the problem you encountered? If so, you may need to disable the card layout or import the code from the link:
https://github.com/Akifyss/obsidian-border/issues/47


Determine highest z-index

Origin logic to determine the 'z-index' to apply to the widget works only when elements are ordered by its z-indexes.
The datepicker did not show up when input element is in a foundation reveal box.
Now z-indexes are extracted and sorted.

Thanks!


Unable to install Maesh on AWS EKS v1.17 due to a CoreDNS issue

Bug Report
What did you do?
Installed traefik-maesh from Helm on a AWS EKS v1.17 (eks.3) cluster with Calico networing using
helm repo add traefik-mesh https://helm.traefik.io/mesh
helm repo update
helm install traefik-mesh traefik-mesh/traefik-mesh

What did you expect to see?
I was expecting the controller to start and maesh to be working.
What did you see instead?
The traefik-maesh-controller pod went into CrashLoopBackOff due to an issue with the traefik-maesh-prepare container. The issue seems to be linked to the "CoreDNS" version not being compatible with maesh though it should be (CoreDNS 1.3+).
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  13m                   default-scheduler  Successfully assigned default/traefik-mesh-controller-5f48ff8f69-vrbd9 to xxx.compute.internal
  Normal   Pulled     11m (x5 over 13m)     kubelet            Container image "traefik/mesh:v1.4.0" already present on machine
  Normal   Created    11m (x5 over 13m)     kubelet            Created container traefik-mesh-prepare
  Normal   Started    11m (x5 over 13m)     kubelet            Started container traefik-mesh-prepare
  Warning  BackOff    2m51s (x49 over 13m)  kubelet            Back-off restarting failed container

Output of prepare container log: (traefik/mesh:v1.4.0)
2020/10/28 19:16:35 command prepare error: unable to find suitable DNS provider: unsupported CoreDNS version "1.6.6-eksbuild.1"

What is your environment & configuration (arguments, provider, platform, ...)?

Kubernetes version: v1.17.9-eks-a84824
EKS version: v1.17-eks.3
Calico version: v3.16.4
Maesh version: v1.4.0

@0rax Thanks for your interest in Traefik Mesh!
It appears that the issue comes from one of our dependencies: https://github.com/hashicorp/go-version.
Before patching the DNS configuration we make sure CoreDNS is between >= 1.3 and < 1.8.  But go-version constrains considers that a version with a pre-release never matches with a constrain specified without a pre-release.
An issue is already open on their repository to understand why it behave like this: https://github.com/hashicorp/go-version/issues/59
Until this get sorted, we can replace the goversion.NewConstraint(">= 1.3, < 1.8") by a version.GreaterThanOrEqual and version.LessThan. In this type of comparison pre-releases are handled correctly.

Thank you for your quick answer, seems like an issue that could be easily fixed.
I will try to build a custom version of the docker-image with this fix to properly check Maesh compatibility with my setup.

@0rax Could you base your changes on v1.4? Since it's a bug fix it would be great to have it on this version.
Don't hesitate to ping me if you need help on this.

It looks like that using this patch on top of refs/tags/v1.4.0 I was able to start traefik-mesh successfully.
diff --git a/pkg/dns/dns.go b/pkg/dns/dns.go
index c62d46d..0416b87 100644
--- a/pkg/dns/dns.go
+++ b/pkg/dns/dns.go
@@ -39,7 +39,11 @@ const (
        traefikMeshBlockTrailer = "#### End Traefik Mesh Block"
 )

-var versionCoreDNS17 = goversion.Must(goversion.NewVersion("1.7"))
+var (
+       versionCoreDNS17 = goversion.Must(goversion.NewVersion("1.7"))
+       versionCoreDNS13 = goversion.Must(goversion.NewVersion("1.3"))
+       versionCoreDNS18 = goversion.Must(goversion.NewVersion("1.8"))
+)

 // Client holds the client for interacting with the k8s DNS system.
 type Client struct {
@@ -103,7 +107,7 @@ func (c *Client) coreDNSMatch(ctx context.Context) (bool, error) {
                return false, err
        }

-       if !versionConstraint.Check(version) {
+       if !(version.GreaterThanOrEqual(versionCoreDNS13) && version.LessThan(versionCoreDNS18)) {
                c.logger.Debugf("CoreDNS version is not supported, must satisfy %q, got %q", versionConstraint, version)

                return false, fmt.Errorf("unsupported CoreDNS version %q", version)

Quick note, I just had to create a namespace myself as the current helm chart seems to install it in the default namespace by default, this seams inconsistent with the documentation available here https://doc.traefik.io/traefik-mesh/install/#verify-your-installation where it says to check the installation using the traefik-mesh namespace.

For people interested about how I was able to deploy it after patching the code, I had to launch the following commands:
make
docker tag traefik/mesh:latest XXXXXXX.dkr.ecr.eu-west-3.amazonaws.com/traefik-mesh:v1.4.0-eks
docker push XXXXXXX.dkr.ecr.eu-west-3.amazonaws.com/traefik-mesh:v1.4.0-eks
echo "---
apiVersion: v1
kind: Namespace
metadata:
    name: traefik-mesh" | kubectl apply -f -
helm install traefik-mesh traefik-mesh/traefik-mesh \
    --set controller.image.pullPolicy=IfNotPresent \
    --set controller.image.name=XXXXXXX.dkr.ecr.eu-west-3.amazonaws.com/traefik-mesh \
    --set controller.image.tag=v1.4.0-eks \
    --namespace=traefik-mesh

@0rax This patch sounds good :+1:
Could you please open a Pull Request to contribute the changes upstream? We will make sure to release a patch version on the v1.4.
Thanks again for your time on this.

@jspdown Just pushed it, I took the liberty to rename global variables to something that better match what they do instead of what they are and added a test case reflecting this issue.

Closed by #774.


Monitoring v1 - v0.2.1 failed to install on an airgap setup

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

run Rancher v2.5.6-rc5 in airgap environment
add a custom cluster:

k8s v1.19.8-rancher1-1
1 etcd, 1 control plane, 3 workers
nodes run Ubuntu 18.04.3 LTS and Docker 19.3.5

enable monitoring v0.2.1 from Rancher UI

Result:
The app cluster-monitoring fails to install with the error
Wait helm template failed. Error: render error in "rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml": template: rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml:90:13: executing "rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml" at <include "kubelet.serviceMonitor.resourcePath" .>: error calling include: template: rancher-monitoring/charts/exporter-kubelets/templates/_helpers.tpl:3:14: executing "kubelet.serviceMonitor.resourcePath" at <.Values.kubelet.serviceMonitor.resourcePath>: nil pointer evaluating interface {}.serviceMonitor : exit status 1

wait for the next RC, maybe rc6, to validate the fix

confirmed with @aiyengar2 that the bug is not related to the air gap environment or k8s version.
The bug fix is validated on v2.5-head a85f4d1: the monitoring v1 0.2.1 is installed successfully into a k8s v1.20.4 cluster.


GrantAccess test

Will not work until Swagger is fixed for "grant_access" with LRO options.
@yugangw-msft FYI

(message created by the CI based on PR content)

@AutorestCI rebase

Rebase done and pushed to the branch

Codecov Report

Merging #3430 into restapi_auto_4004 will increase coverage by 0.01%.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##           restapi_auto_4004    #3430      +/-   ##
=====================================================
+ Coverage               37.6%   37.61%   +0.01%
=====================================================
  Files                   8679     8676       -3
  Lines                 263743   263740       -3
=====================================================
+ Hits                   99176    99208      +32
+ Misses                164567   164532      -35

Impacted Files
Coverage Δ

...-luis/azure/cognitiveservices/language/__init__.py

...-language-luis/azure/cognitiveservices/__init__.py

azure-mgmt-advisor/azure/mgmt/__init__.py

...compute/v2018_06_01/operations/disks_operations.py
31.02% <0%> (+6.41%)
:arrow_up:

.../mgmt/compute/v2018_06_01/models/access_uri_py3.py
63.63% <0%> (+18.18%)
:arrow_up:

...ompute/v2018_06_01/models/grant_access_data_py3.py
61.53% <0%> (+23.07%)
:arrow_up:

...zure/mgmt/compute/v2018_06_01/models/access_uri.py
100% <0%> (+28.57%)
:arrow_up:

...mt/compute/v2018_06_01/models/grant_access_data.py
100% <0%> (+37.5%)
: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 828c157...1e915e1. Read the comment docs.


I did not find the appendix mentioned in the Style Transfer paper in your open source materials

Hi!  :)
I have read your paper intensively these days, and it mentioned "A detailed description of the architecture layers and parameters is given in the Appendix." on the fourth page, but I did not find the appendix you mentioned.
Would you please provide it?I want to know more about the network structure and specific details of your article.
Thanks a lot!!!!

Hi :) Thanks for your interest in our work!
We're sorry that we didn't have the appendix either -- it was never written, and what you see in the paper is a typo we forgot to remove 😢
The architecture is defined in networks.py. The parameters can be found in config.py. We're sorry for the inconvenience.

Ok I see!
Thank you for your prompt reply!!!

Hi :) Thanks for your interest in our work! We're sorry that we didn't have the appendix either -- it was never written, and what you see in the paper is a typo we forgot to remove 😢 The architecture is defined in networks.py. The parameters can be found in config.py. We're sorry for the inconvenience.
大佬 救救 我给你邮箱发邮件了   我是个小白  关于风格化转移有些问题想要请教  比如我用自己的数据训练出的模型（重定向部分）然后使用该模型生成了一份重定向后的bvh  想将某个风格转移给该BVH时遇到困难


core: add OwnerReferencesADM

Added cluster config for OwnerReferencesPermissionEnforcement admission controller
Fixes #1162

Codecov Report

Merging #1205 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1205      +/-   ##
==========================================
+ Coverage    36.2%   36.25%   +0.05%
==========================================
  Files          63       63
  Lines        3823     3826       +3
==========================================
+ Hits         1384     1387       +3
  Misses       2224     2224
  Partials      215      215

Impacted Files
Coverage Δ

core/controlplane/config/config.go
62.12% <100%> (+0.13%)
: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 62f93cd...43eb020. Read the comment docs.

@luck02 LGTM. Thank you very much for your contribution, as always 🎉


fix dup Marketplace/Marketplaces industry typo

At the moment there is a Marketplace industry, and Marketplaces industry listed.

Fixed by setting Expert360's industry to Marketplaces - which seems to be the convention before it was added.

Submitting fix for this one, as I'm wanting to add my company, which fits in Marketplaces industry, and figured I'd fix that one first 😃


[e2e]: generic release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v24.0.59
Run: https://github.com/slsa-framework/example-package/actions/runs/2908762834
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.release.main.default.slsa3.yml
Trigger: release
Branch: v24.0.59
Date: Tue Aug 23 04:08:42 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/v24.0.60
Run: https://github.com/slsa-framework/example-package/actions/runs/2916369309
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.release.main.default.slsa3.yml
Trigger: release
Branch: v24.0.60
Date: Wed Aug 24 04:19:04 UTC 2022
Tests are passing now. Closing this issue.


Remove warning about broken integration tests in driver

I forgot to remove this in the integration test PRs. There are still some features missing (which are tracked in issues) but the input file is mostly functional.

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

Project coverage is 90.63%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1120      +/-   ##
===========================================
- Coverage    90.67%   90.63%   -0.05%
===========================================
  Files          163      162       -1
  Lines        14538    14462      -76
===========================================
- Hits         13183    13107      -76
  Misses        1355     1355

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


Feature: Modular Routers compat

I would like to see if compatibility for Modular Routers can be added. https://www.curseforge.com/minecraft/mc-mods/modular-routers
Currently the breaker module turns the blocks into air
Relayed from https://github.com/FTBTeam/FTB-Modpack-Issues/issues/1062 and will shortly report to Modular Routers as well, see below for the linked issue
Thanks for reading my suggestion :)

The fundamental problem here is that Bedrock Ores relies on Block#onDestroyedByPlayer() being called, which only occurs as  a result of a ServerBoundPlayerActionPacket being received from a client.
So this isn't just a Modular Routers compatibility question; it's about playing nice with any server-sided block breaker.

rewritten regen has fixed this, works wonderfully!


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 878 ms

Resolved: Bofrost.fr performance has improved in 2770824 after 27 minutes.


empty-object.md:5-8: Document motives and examples for...

The puzzle 19-ccc6357f from #19 has to be resolved:
https://github.com/objectionary/lints/blob/66933f94827e2a0fde84bb263625df22bf22d13a/src/main/resources/org/eolang/motives/errors/empty-object.md#L5-L8
The puzzle was created by @yegor256 on 27-Nov-24.
Estimate: 35 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 19-ccc6357f has disappeared from the source code, that's why I closed this issue.


Update DevNet revision number in Learn See what's new to 0.5.0

Over to Janet to make a decision on whether we push this.


Node tests to use QUnit

Description of the pull request:
Convert node tests to QUnit.

Less cognitive overhead when writing tests. You need not write tests in two different ways.
Consistent setup. Similar to the browser, test code can assume QUnit and Ractive are present already.
The qunit module has a very nice report format (tables, shows what blew up, etc.)

I could have gone the other way, write the browser tests in mocha. But QUnit is both runner and assertion lib, API is very consistent between node and browser... and there's lesser node tests to update. 😁
Is breaking:
Nope. But it is breaking some tests for some unknown reason.
Reviewers:
Anyone curious. The table formatting doesn't seem to play well with the CI's console output screen.

From Eric Elliott's article about the differences between Mocha and Tape:

Mocha is a $150k Porsche Panamera when the best tool for the job is a $30k Tesla Model 3. Don’t waste your resources on testing bells and whistles. Invest them in creating your app, instead.

Any thoughts about Tape? It's simple and efficient, for node and browsers.

Tape does look simple. But the premise for the change was to avoid overhead of writing tests in another setup. It could have gone with any test runner, but majority of the tests (browser tests) are already on QUnit which does the job pretty well.
Riding along with the quote, why get a luxury car when a $150 bike gets you to where you want without having to study for a driving exam? 😉

@evs-chris I just switched tests to use QUnit, but for some reason the csp parse test is failing. The output appears to have changed. Is there anything I'm missing? I see the skipPhantom: true in the samples but not sure if that's related.
Test output:
{
    "v": 4,
    "t": [
        {
            "t": 2,
            "x": {
                "r": [
                    "x"
                ],
                "s": "_0+1"
            }
        },
        {
            "t": 7,
            "e": "a",
            "m": [
                {
                    "t": 4,
                    "f": [
                        {
                            "n": "data-id",
                            "f": [
                                {
                                    "t": 2,
                                    "x": {
                                        "r": [
                                            "x"
                                        ],
                                        "s": "_0+3"
                                    }
                                }
                            ],
                            "t": 13
                        }
                    ],
                    "n": 50,
                    "x": {
                        "r": [
                            "x"
                        ],
                        "s": "_0+2"
                    }
                },
                {
                    "f": {
                        "n": "slide",
                        "d": [
                            {
                                "t": 2,
                                "x": {
                                    "r": [
                                        "x"
                                    ],
                                    "s": "_0+4"
                                }
                            }
                        ]
                    },
                    "t": 72,
                    "v": "t1"
                },
                {
                    "n": "click",
                    "f": {
                        "n": "proxy",
                        "d": [
                            {
                                "t": 2,
                                "x": {
                                    "r": [
                                        "x"
                                    ],
                                    "s": "_0+5"
                                }
                            }
                        ]
                    },
                    "t": 70
                },
                {
                    "n": "focus",
                    "f": {
                        "x": {
                            "r": [
                                "@this",
                                "x"
                            ],
                            "s": "[_0.method(_1+5)]"
                        }
                    },
                    "t": 70
                }
            ],
            "f": [
                {
                    "t": 2,
                    "rx": {
                        "r": "foo.bar",
                        "m": [
                            {
                                "r": [
                                    "x"
                                ],
                                "s": "_0+6"
                            },
                            "baz"
                        ]
                    }
                }
            ]
        }
    ],
    "e": {}
}

Expected from samples:
{
    "v": 4,
    "t": [
        {
            "t": 2,
            "x": {
                "r": [
                    "x"
                ],
                "s": "_0+1"
            }
        },
        {
            "t": 7,
            "e": "a",
            "m": [
                {
                    "t": 4,
                    "f": [
                        {
                            "n": "data-id",
                            "f": [
                                {
                                    "t": 2,
                                    "x": {
                                        "r": [
                                            "x"
                                        ],
                                        "s": "_0+3"
                                    }
                                }
                            ],
                            "t": 13
                        }
                    ],
                    "n": 50,
                    "x": {
                        "r": [
                            "x"
                        ],
                        "s": "_0+2"
                    }
                },
                {
                    "v": "t1",
                    "f": {
                        "n": "slide",
                        "d": [
                            {
                                "t": 2,
                                "x": {
                                    "r": [
                                        "x"
                                    ],
                                    "s": "_0+4"
                                }
                            }
                        ]
                    },
                    "t": 72
                },
                {
                    "n": "click",
                    "f": {
                        "n": "proxy",
                        "d": [
                            {
                                "t": 2,
                                "x": {
                                    "r": [
                                        "x"
                                    ],
                                    "s": "_0+5"
                                }
                            }
                        ]
                    },
                    "t": 70
                },
                {
                    "n": "focus",
                    "f": {
                        "x": {
                            "r": [
                                "@this",
                                "x"
                            ],
                            "s": "[_0.method(_1+5)]"
                        }
                    },
                    "t": 70
                }
            ],
            "f": [
                {
                    "t": 2,
                    "rx": {
                        "r": "foo.bar",
                        "m": [
                            {
                                "r": [
                                    "x"
                                ],
                                "s": "_0+6"
                            },
                            "baz"
                        ]
                    }
                }
            ]
        }
    ],
    "e": {
        "_0+1": "function (_0){return(_0+1);}",
        "_0+3": "function (_0){return(_0+3);}",
        "_0+2": "function (_0){return(_0+2);}",
        "_0+4": "function (_0){return(_0+4);}",
        "_0+5": "function (_0){return(_0+5);}",
        "[_0.method(_1+5)]": "function (_0,_1){return([_0.method(_1+5)]);}",
        "_0+6": "function (_0){return(_0+6);}"
    }
}

Ah! There's special code in the csp test that handles stringifying the functions. It just needs to be copied to the node test:
diff --git a/test/browser-tests/parse.js b/test/browser-tests/parse.js
index 3d3d6cf..e19fb57 100644
--- a/test/browser-tests/parse.js
+++ b/test/browser-tests/parse.js
@@ -42,7 +42,7 @@ export default function() {

                                if ( parsed.e && theTest.parsed.e ) {
                                        const expectedKeys = Object.keys( theTest.parsed.e );
-                                       t.deepEqual( Object.keys( parsed.e ),  expectedKeys );
+                                       t.deepEqual( Object.keys( parsed.e ), expectedKeys );
                                        expectedKeys.forEach( key => {
                                                // normalize function whitepace for browser vs phantomjs
                                                let actual = parsed.e[ key ].toString().replace( ') \{', ')\{');
diff --git a/test/node-tests/parse.js b/test/node-tests/parse.js
index 9a8182c..d815fad 100644
--- a/test/node-tests/parse.js
+++ b/test/node-tests/parse.js
@@ -24,6 +24,20 @@ parseTests.forEach( function ( test ) {
                        }, 'Expected ParseError');
                } else {
                        var parsed = Ractive.parse( test.template, test.options );
+
+                       if ( parsed.e && test.parsed.e ) {
+                               const expectedKeys = Object.keys( test.parsed.e );
+                               assert.deepEqual( Object.keys( parsed.e ), expectedKeys );
+                               expectedKeys.forEach( key => {
+                                       // normalize function whitepace for browser vs phantomjs
+                                       let actual = parsed.e[ key ].toString().replace( ') \{', ')\{');
+                                       assert.equal( actual, test.parsed.e[ key ] );
+                               });
+
+                               delete parsed.e;
+                               delete test.parsed.e;
+                       }
+
                        assert.deepEqual( parsed, test.parsed );
                }
        });


Add qtpy to our test suite for pyside6

things

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

why not wait for 6.8.1?

its hard to "merge red", i could downgrade the version, but it was "just as easy" to try the upstream patch.

The nice thing is that upstream seems to have added a similar test to the one I added to their automation.

its hard to "merge red", i could downgrade the version, but it was "just as easy" to try the upstream patch.

Ok, I was just curious.

The nice thing is that upstream seems to have added a similar test to the one I added to their automation.

Finally! Haha

For some reason the CIs didn't trigger.
I pushed directly to the pyside6  branch a cleanup commit to trigger things
https://github.com/conda-forge/pyside2-feedstock/commit/1e55e57a1e0744c98e02bad3a4ce3ab2114797f1


typo in explorer url

Describe the bug
When transaction is completed and clicking on "View on explorer" its redirects to explorer.helka.taiko.xyz instead of explorer.hekla.taiko.xyz

Steps to reproduce
just swap or add liqudity
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

Wrong repo, but has been fixed already. :) Thanks for noticing


Rebuild only when commit changes

I just built my project after including vergen, and then committed those changes to git.   I touched the source file and removed the binary, to no avail. rm target -rf helped, but that seems like overkill.
Our build script prints cargo:rerun-if-changed=build.rs, but not doing so triggers a rebuild every time, so that is not a solution either. Isn't there a way that vergen can make cargo rebuild things only if anything actually changed? I tried adding
println!("cargo:rerun-if-env-changed=VERGEN_SHA");

but that did not help.

$ cat .git/HEAD
ref: refs/heads/master
$ cat .git/refs/heads/master
086ff67cff3c9c3d2315252d1b05c91ad87e0fc0

Maybe use cargo:rerun-if-changed=.git/<put the trimmed content of .git/HEAD after the : here>

If @bjorn3's suggestion works, it may be worth adding this logic to vergen itself. Then a user could just say
let vergen = Vergen::new(ConstantsFlags::all())?;
// ...
vergen.rebuild_on_version_change();

It could also output those rebuild dependencies by default, which is what cc does.

It actually should probably be if either .git/HEAD or what it points to changes.

I'll try and work that in this weekend.   Day job is super busy right now.

I've added these changes into master.  However, I've also upgrade to the 2018 edition and the failure create so currently these only work in the beta and nightly channel.   I'm working to backport the changes to the 2.0 version for stable and when I've done that, I'll push out the official 3.0.


Unable to use Colab in GPU mode

Oddly only works in TPU and CPU mode. Worth investigating.

GPUs are now supported with Cloud Rendering!


HDDS-4503. Provide info on block size via FileSystem

What changes were proposed in this pull request?
Provide information about Ozone's configured block size via Hadoop-compatible file system implementations by overriding getDefaultBlockSize() from FileSystem.
Ozone does not make new files visible until they are closed.  This change allows Impala to query the actual configured block size and use this info during file write, instead of relying on the default block size, which can be overridden in config.
https://issues.apache.org/jira/browse/HDDS-4503
How was this patch tested?
Added unit test.

Thanks @arp7 for reviewing and committing it.  Thanks @ayushtkn for the review.


Update | reserved space for co-organizer, presenter and organizers

"The organizer will always be guaranteed space in the main meeting." - based on the latest update, the space is reserved for co-organizer, presenter and organizer,
FYI - @SamChung-MS

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

ID: 2bf705c2-1f24-bdb5-e712-e8408b941aca
Version Independent ID: ddedd7e0-7d85-06e0-7f20-8b83b3dccec7
Content: View-only meeting experience - Microsoft Teams
Content Source: Teams/view-only-meeting-experience.md
Service: msteams
GitHub Login: @mkbond007
Microsoft Alias: mabond

Thanks for your feedback

PR merged, closing


Change verbosity arguments from the base command to the upgrade related commands

Change verbosity arguments from the base command to the upgrade related commands
The verbose and debug options it's now only available in commands where make sense to
increase verbosity.

Can one of the admins verify this patch?

Tested it and it works fine. I'll take a look at the code later.

Thanks, Alex. We've created a new PR #590 for us to be able to finish it.


Instance creation and configuration api should be refactored

Oddities / annoyances:

K8s:Client.new should probably not require transport as an argument.
K8s::Client.config takes a config and passes it to Transport.config. I think it's a misleading method name.
K8s::Transport.config same as above, returns an instance of K8s::Transport, I would expect it to return a config instead of accepting one.
Transport.new takes auth token/username/password, but there's K8s::Config::UserAuthProvider, maybe Transport.new should actually take an instance of some kind of Authentication class
Transport is a mixture of abstraction for Excon and generic methods.
The ! methods such as api_groups! and api_resources! are unintuitive. Perhaps api_groups(force_refresh: true) or something would be better.
Method visibility in general has been ignored completely, there are no private methods. (I didn't find any methods that should be private except maybe the Util mixin should use module_function)
K8s::Resource.from_files reads a single file or all files in a directory. I would expect it to take an array of paths or IOs.
There's a million methods for creating a client instance.
The client is a bit cumbersome to mock/stub because of the long method chains. It should probably have some kind of test mode / mock transport.

Other than that, it's actually pretty great.

Also:
Do we actually need the Dry::Struct / Dry::Types for anything?  Couldn't everything just be K8s::Resource( which is < RecursiveOpenStruct).

Trying to think how it should work.
K8s::Config
This should actually be something like K8s::KubeConfig. It's not a configuration for K8s::Client. It's for parsing kubeconfig files and finding the necessary values for constructing options for a transport.
K8s::Transport

It's supposed to be an abstraction. It should be generic. The Excon backend should perhaps be K8s::Transport::Excon
K8s::Transport.config(<K8s::Config>) should be K8s::KubeConfig.new(...).context.transport
K8s::Transport.token_from_auth_provider(<K8s::Config::AuthProvider>) and K8s::Transport.token_from_exec(<K8s::Config::UserExec>) should come automatically from the above mentioned K8s::KubeConfig.new(...).context.transport
K8s::Transport#version (and K8s::Client.version) is the same as K8s::Client.new.api('version'). They should be removed, perhaps replaced with K8s::Client#api_version` which would return a string, not a resource.
K8s::Transport.new options should be something like: (server:, token: nil, ca: nil, username: nil, password: nil, client_cert: nil, client_key: nil, client_key_pass: nil, insecure_tls_skip_verify: false, logger: nil)

K8s::Stack
Should maybe be in another gem, such as k8s-client-stack as it's sort of custom.
K8s::Client

K8s::Client.config and K8s::Client.in_cluster_config should be dropped
K8s::Client.new should take (kubeconfig = nil, transport: nil, namespace: nil, insecure_tls_skip_verify: false, logger: nil,  **transport_options). If transport is set, non-empty transport_options should raise. If transport is nil and transport_options is empty, configuration autodiscovery (the current K8s::Client.autoconfig) should be attempted with `logger: logger, insecure_skip_tls_verify: insecure_skip_tls_verify). If autoconfig fails, it should raise.

The user should mostly have to do:
client = K8s::Client.new
client.api('version').gitVersion

client = K8s::Client.new('~/.kube/config', context: 'foo@foofoo')

client = K8s::Client.new(server: 'https://localhost:6443', ca: 'AbCFCFGH==', token: 'abcd')

begin
  client = K8s::Client.new
rescue K8s::Error::SSL
  client = K8s::Client.new(insecure_skip_tls_verify: true)
end

The user should not have to do anything like:
K8s::Client.new(transport: K8s::Transport.config(K8s::Config.load_file('/etc/kubernetes/admin.conf')))

K8s::Client.config(K8s::Config.load_file('/etc/kubernetes/admin.conf'))

The interface to create a client instance should be K8s::Client.new. Optionally, a shortcut for it could be K8s.client:
K8s.client(insecure_skip_tls_verify: true) do |client|
  puts client.api('version').gitVersion
end

Some points to remember About token_from_auth_provider, token_from_exec:

In some cases it's bearer token, in some it's a TLS client cert.  At least exec provider is generic, you don't know ahead of time which you'll get.  So shouldnt have token in name, and return type should admit both.
Lately I'm thinking whether auth providers can be modeled cleanly as a KubeConfig -> KubeConfig transform?

they might expire and require renewal.  Thus user should not be involved with obtaining a token once and passing it to Client, but Client could call a method on each request to obtain fresh credentials, renewing if necessary.
This will become more pressing with https://github.com/kubernetes/kubernetes/issues/70679.

Worse, some providers don't have expiration dates, so one gets an auth expired error and should renew and retry 😞

Is it useful to create multiple Clients with same config, sharing some single object that'll obtain / renew auth?
If yes, this might need Client.new(SomethingDoingAuth.nSomethingDoingAuth.new(...)) rather simple Client.new.Client.new.  (but it can be optional advanced use case)

See also notes on https://github.com/abonas/kubeclient/issues/393

Perhaps the authentication modules should be implemented as some sort of http client library middleware things.

Also, adding to https://github.com/kontena/k8s-client/issues/121#issuecomment-519513084

There's no sane way to use Transport.new that would actually work outside of specs. All of the cert configuration is done in Transport.config which builds the options hash.


Unverified HTTPS

Hi, how to repair this problem ?
Logger: py.warnings
Source: custom_components/proxmoxve/coordinator.py:72
Integration: Proxmox VE (documentation, issues)
First occurred: 09:45:37 (7 occurrences)
Last logged: 09:51:42
/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1056: InsecureRequestWarning: Unverified HTTPS request is being made to host '<IP_ADDRESS>'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings warnings.warn(

It's just a warning right?

It's just a warning right?

i think so, but there are maybe 7 messages and they keep repeating themselves

started getting it too with the latest home assistant update. i have thousands of warnings in my log already increasing my IO time

Same here since HA Update 2013.6.0

Same here, after update to 2023.6.0
They are only warnings, but they are continuously spamming the log.

Yeah, io/disc usage is my main concern here. Even if we raise the log level or hide the warnings, it is still being written constantly, and a lot compared to everything else in the logs

ΗΑ shouldn't be logging those messages continuously in the first place too.

I have added the proxmox CA certificate to my homeassistant, this way by checking the "Verify SSL" checkbox in the integration, it is able to validate the certificate and connect without any error or warning in the LOG.

I have added the proxmox CA certificate to my homeassistant, this way by checking the "Verify SSL" checkbox in the integration, it is able to validate the certificate and connect without any error or warning in the LOG.

Any thoughts on how best to do this with the docker version of HA? Thanks!

I have HAOS and have used this method:
https://community.home-assistant.io/t/let-home-assistant-trust-a-personal-certificate-authority/184917/22
I don't know if it will work in the docker version, I believe it does.

I have added the proxmox CA certificate to my homeassistant, this way by checking the "Verify SSL" checkbox in the integration, it is able to validate the certificate and connect without any error or warning in the LOG.

Any thoughts on how best to do this with the docker version of HA? Thanks!

Could you send me some instruction do do that ;)?

I have HAOS and have used this method:
https://community.home-assistant.io/t/let-home-assistant-trust-a-personal-certificate-authority/184917/22
I don't know if it will work in the docker version, I believe it does.

It worked under docker just fine! Thank you!

Hello everyone to solve the problem of the message in the logger here is a temporary fix!
https://github.com/dougiteixeira/proxmoxve/pull/94


Incorrect casting of url parameters

Introduction
When no type is specified, the casting of the url parameters passed to a query fails with DELETE FROM <table> WHERE id = CAST($1 AS TEXT) RETURNING 'resource deleted'.  DB is postgres hosted on supabase.
To Reproduce
-- Create todo table
CREATE TABLE
  public.todos (
    id BIGINT PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
    task TEXT
  );

-- Insert sample todos
INSERT INTO
  public.todos (task)
VALUES
  ('Complete project proposal');

INSERT INTO
  public.todos (task)
VALUES
  ('Prepare presentation slides');

create delete_todo.sql with
DELETE FROM public.todo
WHERE id = $id
RETURNING
   'resource deleted';

http://localhost:8080/delete_todo.sql?id=1
Actual behavior
Failed to execute SQL statement:
DELETE FROM public.todos WHERE Id = CAST($1 AS TEXT) RETURNING 'resource deleted'
                                     ⬆
line 1, character 37

Backtrace says :
error returned from database: operator does not exist: bigint = text

operator does not exist: bigint = text

Screenshots
If applicable, add screenshots to help explain your problem.
Expected behavior
I expected a deletion of the resource without the need the specify the id's type. If it's needed for some reason, maybe we should find a caveat in the documentation ?
Version information

OS: Pop!_OS 22.04 LTS
Database [e.g. SQLite, Postgres]: Postgres hosted on supabase
SQLPage Version [found when hovering the default footer of pages]: 0.24.0

Additional context
To fix this error, I had to specify the id's type with $id::int

Hello and welcome to SQLPage !
What you found is a common caveat with postgres. Other databases such as SQLite cast the values automatically. Unfortunately, I don't think there is much more to do than better documentation and better error messages.   HTTP URL parameters are not typed, and there is no easy way to automatically guess that $id should be an integer in this context...
Do you have a suggestion concerning the documentation ?

Thank you :)
I didn't understand that it was postgres that is responsible for type checking the url parameters. I tried to do the query with an int and text from psql and postgres was able to delete the resource so I assumed it was something with sqlpage.
I'm not sure for the documentation, maybe the examples could be categorized with the database behind ?

Yes, I would like to improve https://sql.ophir.dev/your-first-sql-website/
What could we have written that would have made it obvious to you how URL parameters binding work ? Can we change something in the existing tutorial or docs to make them less confusing ?
If you have suggestions, feel free to open a pr on https://github.com/lovasoa/SQLpage/blob/main/examples/official-site/your-first-sql-website/tutorial.md
And in general, I would love to know how you approached discovering sqlpage, getting started, and using the different features. It would help prioritize the work on the docs.


[Question][dev] Local dev environment error

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Use CreateDolphinScheduler to create a table error.t_ds_task_definition and t_ds_task_definition_log are not created in the sql\upgrade\1.4.0_schema\mysql\dolphinscheduler_ddl.sql file, but new fields are added.
DolphinScheduler Version
-dev
Additional context

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I'll try to fix it


use load-ip-set

Just wanted to let you know about load-ip-set which offers a superset of the current blocklist functionality.
Let's keep unifying torrent-stream and webtorrent code!

Hey.
I'm using a project based on torrent-stream (peerflix-server) and I'd like to implement blocklist support there. The way blocklist is currently implemented in torrent-stream requires the user to pass in a single range of IP on engine load on add IPs one by one to the set which is inconvenient in many cases.
Was thinking about implementing this at the application level, in my case Peerflix Server (as discussed there https://github.com/asapach/peerflix-server/issues/173) but reading about this and the best way of doing it, I think it would make a lot of sense to just upgrade torrent-stream to use load-ip-set. This way, the blocklist system is much more effective and user friendly (just throw in a blocklist URL or file and you're good to go).
I can work on it, it's really a minor update, and it would benefit peerflix / peerflix-server too.

I'm extremely strapped for time and can't implement this, so I'm closing this.


configure the number of cert interface

With this patch it is possible to access your boot2docker vm remotely.

stop you b2d
add bridge interface to you boot2docker vm
restart b2d
add this to your profile
$  sudo vi /var/lib/boot2docker/profile
CERT_INTERFACES='eth0 eth1 eth2'
restart docker daemon
$sudo /etc/init.d/docker restart

At your remote host you now can add certs and setup env
cd ~/.boot2docker/certs
cp -r boot2docker-vm boot2docker-vm-`hostname`
scp boot2docker-vm-`hostname` peter@mymaschine:/Users/peter/.boot2docker/certs
ssh user@myremotemachine
DOCKER_CERT_PATH=/Users/peter/.boot2docker/certs/boot2docker-vm-HOSTNAME
# IP des Interfaces.
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
docker images

Thanx
Peter

oh, very nice LGTM - @tianon ?

Seems fair and reasonable, thanks!
LGTM


Add support for hack lang @function.outer

Will add support for @function.inner, @class.outer, @class.inner in a subsquent diff

Looks good! Thank you!


[Website] Rename Support to Help, and re-style to better guide users to help themselves

Duplicate of #9552 which failed to land internally.

@facebook-github-bot shipit-ninja

By analyzing the blame information on this pull request, we identified @lacker and @vjeux to be potential reviewers.

Normally, hramos, someone else should review and ship your pull request. However, we will trust that you know what you are doing. Shipping!

Sorry, I can't do that @hramos - this feature is only supported for non-employees; you can land via the internal pull request dashboard.

@facebook-github-bot shipit

@hramos updated the pull request - view changes

@hramos updated the pull request - view changes - changes since last import


Amplify DataStore and DocumentDB ?

I need to fetch data from my backend and cache locally. And we have DocumentDB already set up.
Is it possible to use: DataStore > AppSync > Lamdas >  DocumentDB?
If that not supported by CLI, is it supported by using AWS interface at all?

Amplify CLI does not support Document DB out of the box. AppSync needs DynamoDB table to support DeltaSync.
DataStore is an uses GraphQL to as wire protocol and if you can implement DeltaSync and conflict resolution with your custom lambda and write appropriate resolver then this could be supported.

thank you, closing


[bst-1] bst build --track-all doesn't build anything

See original issue on GitLab
In GitLab by [Gitlab user @abderrahimk] on May 2, 2019, 07:22
Summary
Sometimes, running bst build with --track-all behaves as if I ran bst track. It tracks all element but doesn't try to build or pull anything.
Note
This issue is mostly fixed, but it seems to reproduce spuriously now, keeping this open to record any information pertaining to any further sightings of this issue.
Steps to reproduce
Using branch abderrahim/gnome-boot of gnome-build-meta, run
bst --no-strict --on-error continue build --track-all vm/desktop-vm-image-x86_64.bst

What is the current bug behavior?
Pipeline Summary
  Total:       613
  Session:     555
  Track Queue: processed 232, skipped 13, failed 0
  Pull Queue:  processed 0,   skipped 0,  failed 0
  Fetch Queue: processed 0,   skipped 0,  failed 0
  Build Queue: processed 0,   skipped 0,  failed 0
  Push Queue:  processed 0,   skipped 0,  failed 0

What is the expected correct behavior?
bst should try to pull/build things.
Other relevant information
This is using bst 1.2.6, in non strict mode.

BuildStream version affected: /milestone %BuildStream_v1.2

In GitLab by [Gitlab user @tristanvb] on May 2, 2019, 11:41
Oh my... time for more regression tests...

In GitLab by [Gitlab user @abderrahimk] on May 2, 2019, 11:43
btw, I forgot to mention this happened before, and I thought !1286 would fix it. But apparently not.

In GitLab by [Gitlab user @tristanvb] on May 3, 2019, 06:19
Marking critical since this is a very basic essential feature that is simply not working at all.

In GitLab by [Gitlab user @tristanvb] on May 7, 2019, 08:29
I've reproduced. Actually I'm having errors timing out while trying to track a few elements, but it shoudn't change anything, we should still be pulling and building but we seem not to be.
My results were:
Pipeline Summary
  Total:       613
  Session:     613
  Track Queue: processed 230, skipped 13, failed 3
  Pull Queue:  processed 0,   skipped 0,  failed 0
  Fetch Queue: processed 0,   skipped 0,  failed 0
  Build Queue: processed 0,   skipped 0,  failed 0

I'm having a hard time reproducing this in a test case though; I've adjusted tests/frontend/buildtrack.py to add a --track-all case, and added assertions that things actually get built in test_build_track(), those tests seem to pass fine, need to figure out what is different in the gnome-build-meta case.

In GitLab by [Gitlab user @tristanvb] on May 7, 2019, 09:45
Have to leave this for today, my findings so far are that:

This seems not to be related to dependency types
Modifying the test_build_track() case such that we run the tests with dependencies as runtime only, build only, or both, does not cause this issue to arise.

This seems not to be related to having pull queues active
Building your same branch with artifact servers disabled for both GNOME and freedesktop-sdk projects, causing no pull queue to be used in the scheduler, does not cause this issue to arise.

I will take another look tomorrow and perhaps start sprinkling in some trace logging statements, any other ideas of how this build scenario differs from the test cases in question is welcome.

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 06:58
I've been debugging this more today, and I found that currently I actually cannot reproduce the issue in the same way that [Gitlab user @abderrahimk] was able to.
Contrary to the initial report which shows that all elements were successfully tracked, when I run the test the following elements fail to be tracked, as they appear to refer to upstream sources which do not exist:

core-deps/liboauth.bst
core-deps/espeak.bst
core-deps/libwacom.bst

As [Gitlab user @abderrahimk] has pointed out, libwacom has moved to github.
I initially thought this was insignificant, and that we should see elements being built regardless of the failing 3 elements, but this is not true - so far the behavior I have been witnessing is correct behavior.
The logic by which the behavior I am seeing is correct is as follows:

BuildStream does not try to build elements which can instead be downloaded

This is specifically significant for an element like desktop-vm-image.bst, as the x86image has build only dependencies, and also depends on a compose element which of course also has build only dependencies
We make an effort to avoid fetching and building of elements found in build only dependency branches, if we can download the build-only dependency itself from the cache, then there is no need to process its dependencies

BuildStream however needs to determine the cache key of elements it intends to attempt to download
If an element is selected for tracking, it's cache key, and the cache keys of it's reverse dependencies must remain undetermined until tracking completes
The fact that 3 elements are unable to be tracked, causes the entire branch of build-only dependencies to never be processed.

We do not end up scheduling the processing of these elements found only in build-dependency branches of the graph until we have at least determined the cache key of the first build-only dependency, as that might result in our ability to download that element instead of processing the rest of the graph.
That said, this is only the behavior I have observed, I will try to reproduce this in a scenario where the tracking of build-only dependencies does not fail.
Furthermore, I wonder about my observation yesterday:

Building your same branch with artifact servers disabled for both GNOME and freedesktop-sdk projects, causing no pull queue to be used in the scheduler, does not cause this issue to arise.

Now that I've observed what is blocking elements from being processed, this leads me to question whether the logic which blocks elements from being processed until we know that we cannot download them from a remote, should not be active when there are no remotes configured.
If we know that there are no remotes where artifacts can be downloaded from, we could start processing elements more quickly, without blocking on the full build dependency branches to be tracked before fetching an building commences.
I think that this is a distinctly separate issue, though.

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 07:21
UPDATE: I have now reproduced the original issue, and it can be reproduced with the tristan/test-broken-track-all branch of the gnome-build-meta repository.
That branch is not expected to build successfully at all, but it will reproduce the issue so long as upstreams do not decide to vanish out of thin air...

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:17
mentioned in commit 23460139ce51c044bc5eb6d52858ca1f0c578a37

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:18
mentioned in merge request !1331

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:31
mentioned in commit d9d2ebfa97486a94b8080ef57f3b017f60efdc0e

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:44
mentioned in commit 848670e99fa0f301e0372ad74571d232734e9aeb

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:45
mentioned in merge request !1332

In GitLab by [Gitlab user @tristanvb] on May 8, 2019, 11:59
I have reduced this to a simplified test case and opened WIP merge requests:

bst-1.2 MR !1331 - currently adds isolated test case that fails
master MR !1332 - currently adds isolated test case that fails

In GitLab by [Gitlab user @tristanvb] on May 9, 2019, 07:32
mentioned in commit 210a4bfb9fa311ee256dc0cb7e44d52d73a2da86

In GitLab by [Gitlab user @tristanvb] on May 9, 2019, 09:20
mentioned in commit 223834422d12136879ea2840bd8c8270da87b657

In GitLab by [Gitlab user @tristanvb] on May 9, 2019, 09:20
mentioned in commit 70183d8274898701f4102a1581262807ca89f9ee

In GitLab by [Gitlab user @tristanvb] on May 9, 2019, 09:31
mentioned in commit 627502a63ab1e1cf1e878d33b9983df88f01e03f

In GitLab by [Gitlab user @tristanvb] on May 9, 2019, 09:31
mentioned in commit b17a5e071a5abc76f57aae1f7ab7194f55b40360

In GitLab by [Gitlab user @tristanvb] on May 10, 2019, 09:15
closed via merge request !1332

In GitLab by [Gitlab user @tristanvb] on May 10, 2019, 09:15
mentioned in commit 463ba24d1da14546a844b97fd6845aec4ce7b4cb

In GitLab by [Gitlab user @tristanvb] on May 11, 2019, 08:45
Looks like I was too quick on the trigger, and this issue was only partially fixed by !1332 and !1331
The test case seems to not reproduce the full issue, running the following command on the tristan/test-broken-track-all branch of gnome-build-meta:
bst --log-file --no-strict --on-error continue build --track-all vm/desktop-vm-image-x86_64.bst

Still gets me these results:
Pipeline Summary
  Total:       609
  Session:     609
  Track Queue: processed 229, skipped 13, failed 0
  Pull Queue:  processed 0,   skipped 0,  failed 0
  Fetch Queue: processed 0,   skipped 0,  failed 0
  Build Queue: processed 0,   skipped 0,  failed 0

In GitLab by [Gitlab user @tristanvb] on May 11, 2019, 08:45
reopened

In GitLab by [Gitlab user @tristanvb] on May 11, 2019, 08:52
Oh this is strange.

I ran it again and the bug didn't reproduce.
I verified the previous log, and it is the correct version 1.2.6+17.g92555c4e which includes the fix.
I completely deleted the local artifact cache and ran it again, and the bug again did not reproduce.

When the issue does not reproduce, it does exactly what I expect: It tracks everything first before starting to pull vm/desktop-vm-image-x86_64.bst, as it needs to derive a strict cache key to pull with. Then after failing to pull, it decides that build-only dependencies need to be built, and goes ahead to pull more things.
I am sure the issue happened right in front of me, so let me keep this open for a bit and see if I can reproduce it again.

In GitLab by [Gitlab user @tristanvb] on May 11, 2019, 08:56
changed the description

In GitLab by [Gitlab user @tristanvb] on May 11, 2019, 09:26
I'll remove critical from here for now, as it seems this is hard to reproduce and is not necessarily preventing anyone from getting work done.

In GitLab by [Gitlab user @tlater] on Nov 29, 2019, 17:03
The --track option has been removed from bst build in master now, so this is an exclusively 1.4 issue now.

In GitLab by [Gitlab user @tristanvb] on Nov 6, 2020, 07:40
changed title from bst build --track-all doesn't build anything to {+[bst-1] +}bst build --track-all doesn't build anything


Page crashes when navigating to DRep directory

Description: The page crashes when attempting to navigate to the DRep directory.
Affected Pull Request: #827
Screenshot

List of DReps
{
    "page": 0,
    "pageSize": 10,
    "total": 2,
    "elements": [
        {
            "drepId": "46a95c1337b27332131f3c1b9d8e7689edd2f593e7e69bf5dcf0c278",
            "view": "drep1g654cyehkfenyycl8sdemrnk38ka9avnulnfhawu7rp8skl824l",
            "url": "https://bit.ly/3zCH2HL",
            "metadataHash": "1111111111111111111111111111111111111111111111111111111111111111",
            "deposit": 500000000,
            "votingPower": null,
            "status": "Active",
            "type": "DRep",
            "latestTxHash": "aa0c6b06194839f38143662b634c5729127b01f0c72a0f5ea9ceaaecf79ee6d8",
            "latestRegistrationDate": "2024-04-22T10:52:22Z"
        },
        {
            "drepId": "4d52d1d178157ab4c5ab6f8cb109ff91f750b367830463ef8344007e",
            "view": "drep1f4fdr5tcz4atf3dtd7xtzz0lj8m4pvm8svzx8murgsq8u6dkmf4",
            "url": "https://bit.ly/3zCH2HL",
            "metadataHash": "1111111111111111111111111111111111111111111111111111111111111111",
            "deposit": 500000000,
            "votingPower": null,
            "status": "Active",
            "type": "DRep",
            "latestTxHash": "5c1167a9dce95ce009bf391f80bd93b6717ae5bdadbe1cfada693944ef984a3e",
            "latestRegistrationDate": "2024-04-22T10:52:22Z"
        }
    ]
}

Could we have a stable version for testing? The current issues are preventing us from proceeding with testing.

Thank you for the issue - it has been done with https://github.com/IntersectMBO/govtool/pull/830

Closed by https://github.com/IntersectMBO/govtool/pull/830


Auto corrected by following Format Ruby Code

Auto corrected by following Format Ruby Code
Click here to configure it on awesomecode.io

Coverage decreased (-0.005%) to 97.021% when pulling 5d6fbe86d907a4acde0dccd8d9953f7811a50dab on awesomecode-format-ruby-code-47828 into cd32a52b407596d75541c69b729af6b1d4bd7e99 on master.

Coverage decreased (-0.005%) to 97.021% when pulling 5d6fbe86d907a4acde0dccd8d9953f7811a50dab on awesomecode-format-ruby-code-47828 into cd32a52b407596d75541c69b729af6b1d4bd7e99 on master.


azure-openai streaming failure

Describe the bug
Within the last month or so, a deployment of gpt-4 or gpt-4o fail to stream, but work fine with -S to disable streaming.  However, -S to disable streaming is not honored after entering interactive mode, so I can only run single line chats with "aichat -S".  There is an APIM in front of the model but that should not be an issue, and the error reflects expected data is being returned but not handled properly.
To Reproduce
Have an Azure OpenAI gpt-4 or gpt-4o model deployed, and configured behind an APIM
Brew install aichat, currently version 0.18.0
Config model, type, api_base, api_key, name, etc.
run "aichat in a terse response give another name for a dog"
Returned error:
Failed to get answer

Caused by:
    Invalid response event-stream. content-type: , data: data: {"choices":[],"created":0,"id":"","model":"","object":"","prompt_filter_results":[{"prompt_index":0,"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}}}]}

    data: {"choices":[{"content_filter_results":{},"delta":{"content":"","role":"assistant"},"finish_reason":null,"index":0}],"created":1719359351,"id":"chatcmpl-9eACN6ilYpdNWtgqtFIYqTDaUDF1I","model":"gpt-4","object":"chat.completion.chunk","system_fingerprint":"fp_7ec89fabc6"}

    data: {"choices":[{"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}},"delta":{"content":"Can"},"finish_reason":null,"index":0}],"created":1719359351,"id":"chatcmpl-9eACN6ilYpdNWtgqtFIYqTDaUDF1I","model":"gpt-4","object":"chat.completion.chunk","system_fingerprint":"fp_7ec89fabc6"}

    data: {"choices":[{"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}},"delta":{"content":"ine"},"finish_reason":null,"index":0}],"created":1719359351,"id":"chatcmpl-9eACN6ilYpdNWtgqtFIYqTDaUDF1I","model":"gpt-4","object":"chat.completion.chunk","system_fingerprint":"fp_7ec89fabc6"}

    data: {"choices":[{"content_filter_results":{},"delta":{},"finish_reason":"stop","index":0}],"created":1719359351,"id":"chatcmpl-9eACN6ilYpdNWtgqtFIYqTDaUDF1I","model":"gpt-4","object":"chat.completion.chunk","system_fingerprint":"fp_7ec89fabc6"}

    data: [DONE]

Expected behavior
Same output as -S, but without streaming:
$ aichat in a terse response give another name for a dog
Canine
$

Screenshots/Logs
NA
Configuration
model               azure-openai:gpt-4
max_output_tokens   -
temperature         -
top_p               -
function_calling    false
compress_threshold  4000
dry_run             false
save                false
save_session        -
highlight           true
light_theme         false
wrap                no
wrap_code           false
auto_copy           false
keybindings         emacs
prelude             -
config_file         /Users/the.dude/Library/Application Support/aichat/config.yaml
roles_file          /Users/the.dude/Library/Application Support/aichat/roles.yaml
messages_file       /Users/the.dude/Library/Application Support/aichat/messages.md
sessions_dir        /Users/the.dude/Library/Application Support/aichat/sessions
functions_dir       /Users/the.dude/Library/Application Support/aichat/functions
Environment (please complete the following information):

os version: MacOS 14.5 (23F79)
aichat version: 0.18.0
terminal version: iTerm.app 3.5.2

Additional context
I don't expect this to be related to the APIM, there is no magic there, just routing by model name in the URL, OpenAI compatible.  I could have sworn this was working fine maybe a month or 2 ago, but could be wrong, and just experiencing the stream as default change recently made.  If aichat could persist the -S in an interactive session, then my alias aichat="aichat -S" would solve things well enough for me, but it always streams unless its a single shot command.  I know Azure can be a black box, but hoping this is enough to see what is up.

azure-openai should be openai-compatible. Does the APIM introduce any differences?
Please run the following argc command, then post the response.
 argc chat-openai-compatible --api-base <API-BASE> --api-key <API-KEY> --model <MODEL> [TEXT]...

This will help me pinpoint the issue.

I checked out the repo, I installed argc, and ran the command from inside the repo but it errors out:
$ argc chat-openai-compatible --api-base https://some-deployment-api.azure-api.net --api-key anapikeyadfadsf --model gpt-4 in a terse response give another name for a dog
HTTP/1.1 404 Resource Not Found
Content-Length: 54
Content-Type: application/json
Request-Context: appId=cid-v1:e7f6b297-31f9-4297-bf97-53cfb09ac120
Date: Wed, 26 Jun 2024 05:12:37 GMT

{ "statusCode": 404, "message": "Resource not found" }

Its odd that without streaming its fine, but with streaming, it has an issue.  I will have to circle back to pull out some more information, maybe an strace, or a packet capture or something along those lines.

Invalid response event-stream. content-type: ,

It seems the content-type is missing.

@git-jonathankinney
The azure-openai url is special. I added new argc command chat-azure-openai.
Please run the following argc command, then post the response.
 argc chat-azure-openai --api-url   https://YOUR_RESOURCE_NAME.openai.azure.com/openai/deployments/YOUR_DEPLOYMENT_NAME/embeddings?api-version=2024-02-01 --api-key <API-KEY> --model <MODEL>

If any of this seems malformed, and it really should not respond like this, or it is missing something in the response that a de-facto resource says should be there in this context, that would be good to know.  Boilerplate APIM code may be lacking, or something was lost in translation.

As I mentioned, Content-Type: text/event-stream is missing. This is the most crucial field.
This is not an AIChat bug, closing this issue.


Include automatic backup script

Objective : Using Windows Task Scheduler or similar to have backups generated automatically without user interaction.
Repetition to be determined (ideally every month? Bear in mind disk space...). Duration of the interval does not really matter, as i want the script to also be used manually.
Make use of application Oscar "SCMINFO" ?
Folders / items listed below should first be verified by the script for their existence.

CNC Machines

[ ] Using old PanelMac / Xilog software =
CFG
BIN
TLG
[ ] Using Maestro software =
Use the ".ps1" script made by Xavier to create a self-contained zip in format ".settingx"

Beamsaw machines

[ ] Using MaestroCut/ActiveCut software =
TO CHECK which files to include... Also analyse if ".xml" files for tools/materials/parameters can be generated without UI

Xavier script modified and added for creation of ".settingsx".
Added script to make backup of MaestroCut.


[19.09] imagemagick bumps

Motivation for this change
Backport imagemagick version bumps to 19.09. Contains CVE fixes.
See https://github.com/NixOS/nixpkgs/pull/71099 and https://github.com/NixOS/nixpkgs/pull/72098 for details. Might break gscan2pdf.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @veprbl

@GrahamcOfBorg build imagemagick6 imagemagick7 gscan2pdf

Not sure why this is 4 commits instead of 2...

These are previous version bumps not included yet in 19.09.

Hmm didn't realize I'd forgotten to backport...


autocomplete selected, Password box still shows placeholder text

Not a dealbreaker, but thought I'd mention this.
During development I leave autocomplete on my login page so I don't have to constantly retype my username/password for testing. Well, if I click in the username field and select a previous username I've used to login with before, it does actually fill in my password, however, the placeholder text 'Password' still remains. So I cantechnically hit login and it will log me in fine, but just visually speaking I would have liked it to have shown the dots for the password box and not the placeholder text since the field does in fact hold a value. If the cursor then focuses on the password box, the dots then show properly.
experienced this in IE8.
overall though, best placeholder plugin I've used (and I've tried at least a handful of them). thanks!

Closing as duplicate of #14


I would like to fork and update this package but I receive errors when trying to sfdx force:source:deploy using the package.xml included

I would like to customize the UI for additional usability but when I fork the project and attempt to deploy I receive the following error.
sfdx force:source:deploy -x ./src/package.xml -u fe-sb
*** Deploying v54.0 metadata with SOAP API v51.0 connection ***
ERROR running force:source:deploy:  No source-backed components present in the package.
Question 1:
Should I be able to fork and deploy this to a Dev Sandbox?
Question 2:
Any ideas on the error?  I ran the sfdx update command and have the latest CLI.
Thanks for any help that can be provided.

Hey @DrsMatt,
Could you try deploying this version?
https://github.com/SalesforceLabs/FileExplorer/tree/feature/inline-delete
ta
Paul


Notify the user if the editorconfig is working im/properly

atom-editorconfig should:

[ ] notify the user if config.tabType prevents editorconfig from controlling the tab-types in the current editor

This might be done by a simple notification or as a less disturbing gui-icon 🐭 , showing different states like:

not affected by editorconfig (the plugin is running, a editorconfig-file is present but the current file is not affected by any rules)
conformal (editorconfig is controlling the current file, the file seems conformal to the applied rules)
non-conformal (editorconfig is controlling the current file, but the file yet not conformal to the applied rules [f.e. mixed tab-characters]
non-working (editorconfig should control the current file, but any environmental influence prevents editorconfig to work properly)

I personally tend to introduce a little gui-icon (probably a 🐲 ?), since it is much less disturbing than hitting the mind with notifications all the time.

It could also work by adding a colour or icon to the editorconfig in the directory tree.

That's a good idea @ttsda - i guess implementing that would need to rearrange a lot of things to make it work properly.. i have to think about that.. 💭

I'd rather not rely on colour of the icon, how does that affect icon themes or packages like git that can change the colour of icon/text? It would not be immediately obvious to me if I have a large project that I'm adding the file to which is the case for me right now for process improvement.
A notification warning/error on top right like other packages do would be preferred. Let me know that editorconfig expects a setting to work when I have an unsupported setting such as tab. Alternatively status bar at bottom of editor might be another location to indicate editorconfig in use or warning issue.

Good point @polarathene, maybe adding a overlayed icon to the project drawer's file icons would be a good idea. It would at least allow to recognise any problems at a first view.
Adding an indicator to the status bar is in any case a proven way to show the package status.

#95 belongs to the unintentionally wrongly set tabType.

In my opinion the tabType setting (as well as other editorconfig-settings) should always override the editors default settings (if different). The notification should the notice the user, that his default settings is ignored.

I completely agree @nckappeler, unfortunately Atom does not allow to override that setting in the Editor-Instance. We did not consider changing the global Atom-setting because it would result in many unwanted side-effects.

Ah hah. So Settings (main) > Tab Type must be Auto. Otherwise atom-editorconfig cannot set the tab type at all. editor.setSoftTabs(false); does nothing.
Notwithstanding more elaborate solutions, this should be on the main README and in the config settings for atom-editorconfig.
It's the most essential use of atom-editorconfig: to set your tab type based on file type. It appears to simply not work.
Also you could check the main config and if tabType is not auto then post to console.
I had to open up the plugin and put in debugging statements to figure out why this doesn't work.

Thanks for your feedback @crucialfelix: for a quick win i'll add a hint to the Readme, in mid-term atom-editorconfig should be able to show its state to the user (in one way or another).

Exactly, do the quick win first. Thanks for working on this !

I like this idea. How about just a status icon in the status bar?

I have EVERYTHING set to auto, but it still doesn't work on JavaScript files.
To note that I have babel-language installed, but its tabs settings are set to auto as well...

@FezVrasta thanks for getting in touch. Atom-editorconfig should -- besides of a probably explicitly set tab-type -- work pretty stable. Please open a new issue and don't forget to attach your packages-list as well as your editorconfig-file.

https://github.com/sindresorhus/atom-editorconfig/issues/103

Happy News! 🎉

Although i am not happy with the Icon.. it would be nicer to have a small 🐭  there. Oh and of course the Tab Type issue is addressed, too.


Add upgrade documentation for helm repository based installation

 (0.5) Document how to upgrade the console via helm


Add sample SQL queries

#MVPHackaDoc

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

Looks good @Garthmj, thanks for sharing these samples!


Database is locked

Fatal error: 'try!' expression unexpectedly raised an error: database is locked (code: 5)
File Location :
Project ->Sqlite > Core > Statement.swift.
Build Information

Include the SQLite.swift version, commit or branch experiencing the issue.
Mention Xcode and OS X versions affected.
Xcode 9.4.1 , OS X high Sierra 10.13.6
How do do you integrate SQLite.swift in your project?

manual

General guidelines

Is there going to be any fix on this?
We are quite heavily affected by this issue as well where our app crashes on this exact same line upon startup.

Does anyone know anything about this error?

I have the same issue. This occurs with multiple connexion, even if I put the Thread-Safety code :
db.busyTimeout = 5

db.busyHandler({ tries in
    if tries >= 3 {
        return false
    }
    return true
})

Not sure if this is a good idea, but you can try:
db.busyHandler({ (_) in true })

This way I can execute expensive query in applications like DB Browser, while running my program, without causing the program complain about database being locked (of course, the thread writing the database would be blocked until the external application's query has been done)

@touee I do not know if it is a good idea. I just know that it works. Thanks

This is happening a lot. The app crashes. I am going to try to use a sync thread and if not I will have to use GRDB with WAL mode.

https://github.com/stephencelis/SQLite.swift/blob/master/Documentation/Index.md#thread-safety


number.eo:590-592: Fix "ln" and its tests. Since new...

The puzzle 105-5b662703 from #105 has to be resolved:
https://github.com/objectionary/eo-math/blob/e4098ee4f3f60d7a0d3fba0cda5d30b52ee4e58d/src/main/eo/org/eolang/math/number.eo#L590-L592
The puzzle was created by rultor on 19-Feb-23.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@maxonfjvipon please pay attention to this new issue.


Thank you @AskMeAboutDoom.
Ping @sinfonietta, can you evaluate this for inclusion?

Added in https://github.com/1boii/hosts/commit/1ed8086949c826de5825d449117477a7dfe10f6d

@StevenBlack this domain does not respond for me.

@StevenBlack this domain finally responded.  It's Japanese cartoons...

Thank you @Sinfonietta.
Closing.


Consider adding an RSS Feed to the blog

Description
RSS lives. In a beautiful world it would live on your blog. In an even better world release notes would end up there as well.
Alternatives Considered
No response
Additional Context
No response
Screenshots
No response

This issue belongs in the codeedit.app repository. Moving it there.


Support Carthage?

It would be helpful if you can support Carthage in parallel to cocoapod

Support Carthage. 084bee9ebfbc30c9b13c61e1fda825bdfdc18116


flashvars(stream and server) values

If i want to send source authentication mean send a stream to an rtmp server through swfobject with username and password then how to embed that with server URL or any other resource.
I am using wowza server to publishing my webcam stream, it requires source authentication and swfobject didn't carrying username and password with any thing(flashvars etc).
So, anyone know how to send username and password with swfobject (flashvars server:).

why do you want to use swfobject to broadcast a stream to the server?
makes no sense at all. Just send directly your stream to the server with your user and pass
and check if from your server application main.asc file.
Now if you want the users to play the stream pass an authentication so the best would be develop a web side like php or else script to restrict the video access.


DataMigration: Adding time based collection and support for installed-ir-path

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.

DataMigration

/azp run


Explore the use of xmap under the hood for vectorised chunks to prevent hitting RAM bottlenecks.

Currently vmap batches the whole computation as one which can result in hitting RAM bottlenecks, resulting in a pretty hard-core slow down. Looks like there are some long-term plans to implement this is jax: https://github.com/google/jax/issues/11319.
This issue is simply to track progress over time.

Batching can be done with jax.lax.map https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.map.html


myjenkins: Update plugins as of 2017-05-09

ant:1.5
delivery-pipeline-plugin:1.0.1
github-pullrequest:0.1.0-rc23

Signed-off-by: Gianpaolo Macario<EMAIL_ADDRESS>

Testing PR locally on itm-gpaolo-w10 (MS Windows 10 running Docker Toolbox v17.05.0-ce)

Successfully run https://github.com/gmacario/my-jenkins-pipelines
LGTM, merging


Deprecate Entity Apply

Since Entity.Stream is not a good default, because of the overhead of dealing with streams, we deprecate the Entity.apply method in favour of a explicit stream constructor.
We also add a explicit string constructor for strict entities.

Agree. I am kind of 👍 for getting rid of over-use of apply methods in favor of explicitly named static ones.

I advise getting one more like before getting this merged.


Support PID hosts with IPs

While playing around with https://github.com/mesosphere/playa-mesos and mesos-go I failed to connect the example framework to the master. The master identified itself as master@<IP_ADDRESS>:5050 which failed the parsing logic in detector/factory.go.
This PR fixes CreateMasterInfo() to support PIDs with IPs as the hostname.

wrong repository. should go upstream.


Update README.md

Add new API Gateway limitation

Great find! Have an official citation you can link against in the guide for when this invariably changes in the future? :-)

@lbailly Just checking up on this one. Thanks for the contribution; any luck finding a citation?

I think this limitation may have a workaround now that the API gateway can be configured without the Cloudfront distribution layer:

https://aws.amazon.com/about-aws/whats-new/2017/11/amazon-api-gateway-supports-regional-api-endpoints/

https://docs.aws.amazon.com/apigateway/latest/developerguide/create-regional-api.html

@lbailly - thanks for your submission. Can you confirm or disconfirm the original limitation based on the links in @cristim's comment?

Closing for now pending further review.