Patch/update with dependencies, How to avoid duplicated arguments in query

First check

[x] I added a very descriptive title to this issue.
[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.
[x] I already read and followed all the tutorial in the docs and didn't find an answer.
[x] I already checked if it is not related to FastAPI but to Pydantic.
[x] I already checked if it is not related to FastAPI but to Swagger UI.
[x] I already checked if it is not related to FastAPI but to ReDoc.
[x] After submitting this, I commit to one of:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Example
Here's a self-contained, minimal, reproducible, example with my use case:

from typing import Optional

from fastapi import Depends, FastAPI
from pydantic import BaseModel

# Models as shown in https://fastapi.tiangolo.com/tutorial/extra-models/
class Command(BaseModel):
    name: str
    game: int = 0
    template: str
    cooldown: int

class UpdateCommand(BaseModel):
    name: str
    game: int = 0
    template: Optional[str]
    cooldown: Optional[int]

app = FastAPI()

async def get_cmd_from_db_dep(name: str, game: Optional[int] = 0) -> Command:
    pass

async def get_cmd_from_db_by_update_cmd(update_cmd: UpdateCommand) -> Command:
    return await get_cmd_from_db_dep(update_cmd.name, update_cmd.game)

# Expects query args name and game, perfect for a get call
@app.get("/command", response_model=Command)
async def get_command(cmd: Command = Depends(get_cmd_from_db_dep)):
    pass

# Expects query args name and game as well as a UpdateCommand in the body which will
# contain the name and game as well. Less desirable.
@app.post("/command", response_model=Command)
async def update_command(
    update_cmd: UpdateCommand, cmd: Command = Depends(get_cmd_from_db_dep)
):
    pass

# Expects a UpdateCommand in the body but requires an extra wrapper around
# `get_cmd_from_db_dep`
@app.post("/command_2", response_model=Command)
async def update_command_also(
    update_cmd: UpdateCommand, cmd2: Command = Depends(get_cmd_from_db_by_update_cmd)
):
    pass

Description

I am making a simple CRUD api, but I am hitting a weird pattern I feel like I am doing something wrong.
The above example will make a get api call that wants name and game ( My two pieces of my primary key essentially) which is perfect.

However, the update post wants both the name and game defined as query args AND the body to contain a name and game as well as the fields that are changing.

The only way I had found to get around this was defining "wrapper" dependencies such as get_cmd_from_db_by_update_cmd, which looks how I would like:

Is there a different way to define the dependency or the arguments to make it so that if I get a model that contains the arguments it will pass them to the dependency instead of expecting them as separate query args?
Environment

OS: [e.g. Linux / Windows / macOS]: Windows 10
FastAPI Version [e.g. 0.3.0]: 0.61.1
Python version: 3.7.9

Additional context
Obligatory, my model is actually a little more complicated than that, but the ideas conveyed are what I am after. Also, I LOVE the project, I just want to make sure I am doing things right with it!

Is something like this workable?
async def get_cmd_from_db_by_update_cmd(update_cmd: UpdateCommand) -> Tuple[UpdateCommand, Command]:
    return [
        update_cmd,
        await get_cmd_from_db_dep(update_cmd.name, update_cmd.game)
    ]

@app.post("/command", response_model=Command)
async def update_command(
    cmd: Tuple[UpdateCommand, Command] = Depends(get_cmd_from_db_dep)
):
    pass

You could also replace the tuple with another model

Hmm, I think I don't understand the use case yet, why are you using the get_cmd_from_db_dep dependency in the path operations where you don't want to extract that info from query parameters?

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Add root password validation regex for Azure dialog

This attempts to add password validation for Azure VM admin/root passwords. The password for a VM must be 12-72 characters long, and contain at least one uppercase character, one lowercase character, and one number.
https://bugzilla.redhat.com/show_bug.cgi?id=1377890
Marked as a WIP for now since the UI doesn't seem to honor the required restrictions, even without this PR.

@miq-bot add_label wip

@lfu Please take a look.

@miq-bot remove_label wip

Thanks to some diligent work by Lucy, we discovered that the update_field_visibility method in provision_workflow.rb was disabled. By enabling it, the validation works.

@miq-bot add_label euwe/yes

@miq-bot add_label blocker

Euwe BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1402059

Euwe Backport details:
$ git log -1
commit 0154c024f1e767d189760b305cd4d4dd18f9f1c8
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Mon Dec 5 11:37:13 2016 -0500

    Merge pull request #12967 from djberg96/service_dialog_root_password

    Add root password validation regex for Azure dialog
    (cherry picked from commit 3fe2410491c51f6953c2c282cf508c39552f4274)

    https://bugzilla.redhat.com/show_bug.cgi?id=1402059


Incorrect app groups

E.g. https://flathub.org/apps/com.adobe.Reader mentions "other apps in the KDE group, implying that the adobe reader is made by KDE.
Looking at https://flathub.org/apps/collection/project-group/KDE/1 it is also listed there, alongside some other apps that are also not related to KDE

Closing as duplicate of https://github.com/flathub/website/issues/1356


[Bug] 'Cannot connect to the Chroma SDK', None

The problem
I had this working some time ago but recently it has stopped. Unfortunately I did not notice how or why it stopped working. It has perhaps stopped working after updating the integration or HA version
The integration has started showing Failed Setup, will retry with the above error when hovered over.
I have followed the instructions and uninstalled chroma connect and reinstalled it. I even reinstalled Synapse 3
Your device(s) with a problem
No response
Firmware version
<IP_ADDRESS>00
Integration version with the issue
3.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Core 2024.2.5
Is there anything useful in the logs?
2024-03-08 01:16:07.821 DEBUG (MainThread) [custom_components.chroma.chroma] Connecting to Chroma SDK on 192.x.x.x
2024-03-08 01:16:10.909 DEBUG (MainThread) [custom_components.chroma.chroma] Connecting to Chroma SDK on 192.x.x.x

Additional information
No response

Hello. Sorry for the late reply.
Can you connect to the chroma SDK from the device running it (Synapse) using the address https://chromasdk.io:54236/razer/chromasdk (or its own IP address instead of chromasdk.io, but be sure to keep the correct port and https)
It should show chroma versions:
{
    "core": "3.34.02",
    "device": "3.34.02",
    "version": "3.34.02"
}

But it might be that your Synapse / Chroma instance has troubles with the SSL - not only a certificate from an untrusted issuer (which is not a problem), but rather a protocol error. Your browser will tell you that with a ERR_SSL_PROTOCOL_ERROR message in this case.
Let me know what you find

I do have the same issue and I get the this error when trying both with https://chromasdk.io:54236/razer/chromasdk or the IP address - NET::ERR_CERT_INVALID
On the other hand, when trying with https://localhost:54235/razer/chromasdk the Chroma versions show up.

I have the exact same circumstances as @Tomanic-glitch. My Chroma was working before I updated Home Assistant. I was about a year behind on updates and it worked flawlessly. After the update to 2024.3.1, it started exhibiting this behavior.

Same problem here, problem comes from synapse or integration?

Same issue. I am able to connect to the SDK using http://localhost:54235/razer/chromasdk and get the following for the SDK version. I am running the most recent version of Synapse on the machine.
One note, I did try to access it from a separate machine using the IP of my gaming machine and it will not allow me to connect. I have all the Windows firewalls turned off on the gaming machine.

Seeing the same issue, assuming this is no longer supported.

Hey, I’m running into the same issue too. I’m wondering if it is that I am using the New Synapse Beta and that it might not work with it. Is there anyone that can confirm that it is unavailable or provide me with a fix?

Also got the same issue.
Still no fix/workaround?


[WIP] spark3.0 changes

Why is this PR needed?
What changes were proposed in this PR?
Does this PR introduce any user interface change?

No
Yes. (please explain the change and update document)

Is any new testcase added?

No
Yes

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3380/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5131/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3386/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5137/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5138/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3387/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5153/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3401/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3404/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5156/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5159/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3407/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5160/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3408/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5161/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3409/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5162/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3410/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3411/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5163/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5164/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3412/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3413/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5165/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3414/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5166/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5167/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3415/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3416/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5168/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3418/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5170/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3419/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5171/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3420/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5172/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5174/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3422/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5175/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3423/


Minor Adjustments

Add a Favicon
Adjust the breakpoints
Use the logo as home link
Reset the form after submit
Adjust the spacing between the elements

LGTM!


Use https instead of git URLs for submodules.

This simplifies dockerized builds with git submodules as needed in this PR:
https://github.com/wmitsuda/erigon/pull/1

yes this is a must for my package to build as well,

Out of curiosity, why do you guys prefer https? Does it have something to do with certain network restrictions were you work?

no its because there are no ssh keys to pull content in the build envs.

That was the easiest solution to the problem where no SSH keys are available inside the docker image when building it. AFAIK git requires you to have SSH keys to clone from git:// URLs and I thought that's a bit overkill to generate SSH keys into the docker image just to achieve a checkout. Maybe there's an option in git to be less strict on that however which I'm not aware of. Using https:// based cloning doesn't require SSH keys but just requires host key verification which is fine.

It makes sense, thanks for the explanation!


Missing dependencies nbconvert

Opening the Spyder activates error:
missing dependencies nbconvert => 4.0
Although version 5.6 is already installed through conda console. It seams like nbconvert is not recognized by Spyder.

Sorry but this is something you need to solve in your side. We can't help you with it because it's an installation issue.


Preserved routes support for connect

Currently routes preserved in useradmin do not show up in connect routes list when choosing custom timeframe (eg last 6 months). Also, when opening preserved route using connect link in useradmin, the route does not load in connect and clicking View in Cabana does nothing. My main usecase is reviewing preserved routes in cabana, so adding link to useradmin to open route directly in cabana would be also ok if that is easier to implement.

I looked into it a bit and it looks like this has to be fixed on api side, since curl 'https://api.commadotai.com/v1/devices/05bca04dfbdca165/segments?from=1622505600000'... does not currently return preserved routes either


Add missing Eq derivations

The derivation on Header is correct because comparisons of string slices and byte slices meet the requirements. The derivations on Request and Response are correct because they contain only string slices, byte slices, slices of Header objects (which are now Eq), primitives, and options (which are Eq if their contents are). Finally the derivation on Status is correct because #[derive(Eq)] on a generic only actually implements Eq if all generic parameters are Eq, which for Status is sufficient.

I agree they're correct, I just have one question: why would we want these implementations? What case does this help solve?

Given that Eq is an empty trait, AFAICT there is no downside to adding it. Rust API Guidelines recommends eagerly implementing Eq where it is appropriate. It means that other people will then be able to #[derive(Eq)] on their own types that contain e.g. a Request object, which would not otherwise work; without this, those other people would have to impl Eq for MyType {} explicitly, which is significantly more verbose and also a little bit error-prone given that it leaves open the possibility that Request might stop being effectively Eq sometime and the other person not notice.

Yea, thats true. Thanks, I'll merge!


Addon stopped

Successfully installed and configured. Working for a while and stopped.
Found in logs as below:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[03:47:23] INFO: Fetching configuration...
[03:47:24] INFO: Using MQTT host: core-mosquitto
[03:47:24] INFO: Using MQTT port: 1883
[03:47:24] INFO: Using MQTT username: addons
[03:47:24] INFO: Using MQTT password: REDACTED
[03:47:25] INFO: Starting Ecowitt2MQTT
2022-08-22 03:47:26,514 | ecowitt2mqtt | INFO | Starting ecowitt2mqtt (version 2022.08.3)
2022-08-22 03:47:34,156 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:47:39,693 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:47:50,727 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:48:06,158 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:48:22,162 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:48:32,174 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:48:38,162 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:48:54,762 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:49:10,131 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:49:26,170 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:49:32,133 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:49:42,152 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:49:58,744 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:50:14,154 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:50:30,165 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:50:35,654 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:50:46,149 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:51:02,783 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:51:18,132 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:51:34,572 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:51:39,655 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:51:50,146 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:52:06,717 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:52:22,156 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:52:32,132 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:52:38,154 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:52:54,168 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:53:10,898 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:53:26,116 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:53:32,182 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:53:42,153 | ecowitt2mqtt | INFO | Published to Home Assistant MQTT Discovery
2022-08-22 03:53:57,919 | ecowitt2mqtt | ERROR | too many values to unpack (expected 1)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

something misconfigured?

Try enabling verbose logging (it's one of the configuration options) and restart it; if it drops again, post that whole log.

I'm back :(

2022-08-23 17:08:03,532 | ecowitt2mqtt | DEBUG | Received data from the Ecowitt device: {'PASSKEY': '9B3609D12F1B8E485B770C257C95F5D3', 'stationtype': 'EasyWeatherV1.6.4', 'dateutc': '2022-08-23 15:08:01', 'tempinf': '72.3', 'humidityin': '74', 'baromrelin': '30.039', 'baromabsin': '29.156', 'tempf': '72.1', 'humidity': '85', 'winddir': '71', 'windspeedmph': '4.0', 'windgustmph': '4.5', 'maxdailygust': '8.1', 'rainratein': '0.000', 'eventrainin': '2.787', 'hourlyrainin': '0.000', 'dailyrainin': '0.157', 'weeklyrainin': '2.807', 'monthlyrainin': '4.878', 'yearlyrainin': '92.020', 'totalrainin': '92.020', 'solarradiation': '275.01', 'uv': '2', 'wh65batt': '0', 'freq': '868M', 'model': 'WS2900_V2.01.08'}
INFO:     <IP_ADDRESS>:9628 - "POST /data/report HTTP/1.1" 204 No Content
2022-08-23 17:08:03,534 | ecowitt2mqtt | DEBUG | Publishing payload: {'PASSKEY': '9B3609D12F1B8E485B770C257C95F5D3', 'stationtype': 'EasyWeatherV1.6.4', 'dateutc': '2022-08-23 15:08:01', 'tempinf': '72.3', 'humidityin': '74', 'baromrelin': '30.039', 'baromabsin': '29.156', 'tempf': '72.1', 'humidity': '85', 'winddir': '71', 'windspeedmph': '4.0', 'windgustmph': '4.5', 'maxdailygust': '8.1', 'rainratein': '0.000', 'eventrainin': '2.787', 'hourlyrainin': '0.000', 'dailyrainin': '0.157', 'weeklyrainin': '2.807', 'monthlyrainin': '4.878', 'yearlyrainin': '92.020', 'totalrainin': '92.020', 'solarradiation': '275.01', 'uv': '2', 'wh65batt': '0', 'freq': '868M', 'model': 'WS2900_V2.01.08'}
2022-08-23 17:08:03,535 | ecowitt2mqtt | DEBUG | Calculator found for tempinf: calculate_temperature (key: tempin, value: 72.3)
2022-08-23 17:08:03,535 | ecowitt2mqtt | DEBUG | Calculator found for humidityin: calculate_relative_humidity (key: humidityin, value: 74)
2022-08-23 17:08:03,536 | ecowitt2mqtt | DEBUG | Calculator found for baromrelin: calculate_pressure (key: baromrel, value: 30.039)
2022-08-23 17:08:03,536 | ecowitt2mqtt | DEBUG | Calculator found for baromabsin: calculate_pressure (key: baromabs, value: 29.156)
2022-08-23 17:08:03,536 | ecowitt2mqtt | DEBUG | Calculator found for tempf: calculate_temperature (key: temp, value: 72.1)
2022-08-23 17:08:03,537 | ecowitt2mqtt | DEBUG | Calculator found for humidity: calculate_relative_humidity (key: humidity, value: 85)
2022-08-23 17:08:03,537 | ecowitt2mqtt | DEBUG | Calculator found for winddir: calculate_wind_dir (key: winddir, value: 71)
2022-08-23 17:08:03,537 | ecowitt2mqtt | DEBUG | Calculator found for windspeedmph: calculate_wind_speed (key: windspeed, value: 4.0)
2022-08-23 17:08:03,538 | ecowitt2mqtt | DEBUG | Calculator found for windgustmph: calculate_wind_speed (key: windgust, value: 4.5)
2022-08-23 17:08:03,538 | ecowitt2mqtt | DEBUG | Calculator found for maxdailygust: calculate_wind_speed (key: maxdailygust, value: 8.1)
2022-08-23 17:08:03,538 | ecowitt2mqtt | DEBUG | Calculator found for rainratein: calculate_rain_rate (key: rainrate, value: 0.0)
2022-08-23 17:08:03,539 | ecowitt2mqtt | DEBUG | Calculator found for eventrainin: calculate_rain_volume (key: eventrain, value: 2.787)
2022-08-23 17:08:03,539 | ecowitt2mqtt | DEBUG | Calculator found for hourlyrainin: calculate_rain_volume (key: hourlyrain, value: 0.0)
2022-08-23 17:08:03,539 | ecowitt2mqtt | DEBUG | Calculator found for dailyrainin: calculate_rain_volume (key: dailyrain, value: 0.157)
2022-08-23 17:08:03,540 | ecowitt2mqtt | DEBUG | Calculator found for weeklyrainin: calculate_rain_volume (key: weeklyrain, value: 2.807)
2022-08-23 17:08:03,540 | ecowitt2mqtt | DEBUG | Calculator found for monthlyrainin: calculate_rain_volume (key: monthlyrain, value: 4.878)
2022-08-23 17:08:03,540 | ecowitt2mqtt | DEBUG | Calculator found for yearlyrainin: calculate_rain_volume (key: yearlyrain, value: 92.02)
2022-08-23 17:08:03,541 | ecowitt2mqtt | DEBUG | Calculator found for totalrainin: calculate_rain_volume (key: totalrain, value: 92.02)
2022-08-23 17:08:03,541 | ecowitt2mqtt | DEBUG | Calculator found for solarradiation: calculate_solar_radiation_wm2 (key: solarradiation, value: 275.01)
2022-08-23 17:08:03,542 | ecowitt2mqtt | DEBUG | Calculator found for uv: calculate_uv_index (key: uv, value: 2)
2022-08-23 17:08:03,542 | ecowitt2mqtt | DEBUG | Calculator found for wh65batt: calculate_battery (key: wh65batt, value: 0)
2022-08-23 17:08:03,543 | ecowitt2mqtt | DEBUG | Sending DISCONNECT
2022-08-23 17:08:03,544 | ecowitt2mqtt | ERROR | too many values to unpack (expected 1)
2022-08-23 17:08:03,549 | ecowitt2mqtt | DEBUG |   File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/helpers/logging.py", line 47, in wrapper
return func(*args, **kwargs)
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/cli.py", line 229, in main
loop.run_until_complete(ecowitt.async_start())
File "uvloop/loop.pyx", line 1501, in uvloop.loop.Loop.run_until_complete
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/core.py", line 46, in async_start
await self._runtime.async_start()
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/runtime.py", line 157, in async_start
await asyncio.gather(*self._runtime_tasks)
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/runtime.py", line 91, in _async_create_mqtt_loop
await self._publisher.async_publish(
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/helpers/publisher/hass.py", line 483, in async_publish
processed_data = ProcessedData(self.ecowitt, data)
File "", line 6, in init
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/data.py", line 297, in post_init
self.output[payload_key] = calculator(
File "/usr/lib/python3.9/site-packages/ecowitt2mqtt/helpers/calculator/meteo.py", line 581, in calculate_beaufort_scale
[rating] = [
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Thanks, @skipper-hqst! I'm investigating.

@skipper-hqst I don't see from your logs: what unit systems (input and output) are you using?


fix up ruamel.yaml/pyyaml no-member lint errors

Closer, still a few test failures.

Okay, tests are passing again.
I'm not overly excited about setting the value of self.__yaml_dict to content in the constructor, since content isn't necessarily a dict.

@detiber I feel like that can be cleaned up later if it trips folks up.


fix(ecmascript/codegen): TsQualifiedName has trailing dot

Fixes #1266

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

Thanks!


I want submit form by button from modal window in react-formio using

I want submit form by button from modal window instead of form submit button. is it possible if yes then how?

Working for me Thanks :)

When you create a form component, you can get the form instance from the formReady hook.
let myform;
ReactDOM.render(
  <Form src="https://example.form.io/example" formReady={form => myform = form} />
  , document.getElementById('example')
);

// Trigger the submit
form.submit();

// Get the submission object
const submission = form.submission


[ITensors] [BUG] Compilation using ITensors.compile() doesn't work; "No method is defined..."

Description of bug
When running ITensors.compile(), as detailed here, I get an error: the method doesn't seem to be found. The code in compile.jl seems to be missing: see here
Minimal code demonstrating the bug or unexpected behavior
Minimal runnable code
using ITensors
ITensors.compile()

Expected output or behavior
ITensor compiles without issue.
Actual output or behavior
Output of minimal runnable code
julia> ITensors.compile()
ERROR: MethodError: no method matching compile(::NDTensors.BackendSelection.Algorithm{:PackageCompiler, @NamedTuple{}})
The function `compile` exists, but no method is defined for this combination of argument types.

Closest candidates are:
  compile(; backend, kwargs...)
   @ ITensors ~/.julia/packages/ITensors/HwzqQ/src/packagecompile/compile.jl:39

Stacktrace:
 [1] compile(; backend::NDTensors.BackendSelection.Algorithm{:PackageCompiler, @NamedTuple{}}, kwargs::@Kwargs{})
   @ ITensors ~/.julia/packages/ITensors/HwzqQ/src/packagecompile/compile.jl:40
 [2] compile()
   @ ITensors ~/.julia/packages/ITensors/HwzqQ/src/packagecompile/compile.jl:39
 [3] top-level scope
   @ REPL[7]:1

Version information

Output from versioninfo():

julia> versioninfo()
Julia Version 1.11.2
Commit 5e9a32e7af2 (2024-12-01 20:02 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 48 × Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, broadwell)
Threads: 48 default, 0 interactive, 24 GC (on 48 virtual cores)

Output from using Pkg; Pkg.status("ITensors"):

julia> using Pkg; Pkg.status("ITensors")
Status `/storage/slow_raid5/SYSTEM/localhome/phyjj/[redacted]/Project.toml`
  [9136182c] ITensors v0.7.8

Please try loading ITensorMPS.jl before running ITensors.compile(), the compilation relies on running DMRG which is now in ITensorMPS.jl. See https://itensor.github.io/ITensors.jl/dev/#News.

Thanks, I’ll try that.
Can you update the documentation to reflect that please, since it’s currently not clear? (A quick google for the error I had wasn’t helpful either)

Sure, will do.

This actually still doesn't work for me. I'm doing exactly what you've put in the new docs, i.e.
using ITensors, ITensorMPS
ITensors.compile

but I get the same error.

Oops, sorry about that. I forgot you also have to install and load PackageCompiler.jl since the functionality was moved to a package extension so that we don't force everyone to install PackageCompiler.jl even if they don't want to use ITensors.compile().
So this should work:
using ITensors, ITensorMPS
using PackageCompiler
ITensors.compile()

I'll clarify that in the docs.

Thanks, seems to be working now!


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 251 ms

Resolved: ClamAV performance has improved in 15ea901 after 1 hour, 17 minutes.


clangd crashes on trivial constexpr declaration (windows)

clangd crashes on the camera_option_default_value variable. Interestingly enough, it does not crash if the constant is renamed to (for example) default_value. Just from playing around it appears to be somewhat related to the length of the line (or name?).
// header1.hxx
#pragma once

constexpr const char* const camera_option_default_value = "-";

// header2.hxx
#pragma once

#include <header1.hxx>

Logs
[11:50:02.821] Building preamble...
Exception Code: 0xC0000005
 #0 0x00007ff696d19efc (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e49efc)
 #1 0x00007ff696d19c6b (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e49c6b)
 #2 0x00007ff696d19c0b (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e49c0b)
 #3 0x00007ff696d19c6b (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e49c6b)
 #4 0x00007ff696d19c6b (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e49c6b)
 #5 0x00007ff696d0e928 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e3e928)
 #6 0x00007ff696d0fe05 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e3fe05)
 #7 0x00007ff696d163b1 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e463b1)
 #8 0x00007ff696cf00eb (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e200eb)
 #9 0x00007ff696cee01e (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e1e01e)
#10 0x00007ff696cd432e (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1e0432e)
#11 0x00007ff696b947fe (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1cc47fe)
#12 0x00007ff696c18fa7 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1d48fa7)
#13 0x00007ff696b6aed7 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1c9aed7)
#14 0x00007ff696b6a9cb (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1c9a9cb)
#15 0x00007ff696b92d42 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1cc2d42)
#16 0x00007ff695d7d4f3 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0xead4f3)
#17 0x00007ff694f803e9 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0xb03e9)
#18 0x00007ff694f82177 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0xb2177)
#19 0x00007ff694f774ba (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0xa74ba)
#20 0x00007ff696a95af0 (C:\Users\fho\AppData\Local\Microsoft\WinGet\Links\clangd.exe+0x1bc5af0)
#21 0x00007ff9f48d26ad (C:\WINDOWS\System32\KERNEL32.DLL+0x126ad)
#22 0x00007ff9f63ea9f8 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x5a9f8)
Segmentation fault

System information
Output of clangd --version:
clangd version 16.0.2

Editor/LSP plugin:
Operating system:
Windows 11

Does the crash happen as soon as you open the file containing the variable? Or do you have to perform any particular editor action to trigger the crash?

Can you also show the contents of any relevant config files that are present (compile_commands.json, .clangd, .clang-tidy, compile_flags.txt)?
(With the default configuration, the include in header2.hxx cannot be resolved because the compiler does not search the current directory when the #include <...> syntax is used.)

I distilled it down to this same setup, albeit in a project I'm working on. I've tried to set it up the same (copying my .clangd & compile_commands.json, then modifying for these headers above), but can't get the same error.
Is there anyway I can debug this locally and share some logs, dump etc?

A few ideas:

Can you try disabling clang-tidy checks by adding --clang-tidy=false to clangd's command line? Sometimes a crash is in a checker and can be worked around by disabling the checker.
Can you try the latest weekly snapshot release at https://github.com/clangd/clangd/releases? Maybe the issue has been fixed on trunk.

For further diagnosis it would be helpful to get a symbolicated backtrace (so it shows where in the code the crash is). I'm not sure how to do that on Windows, maybe someone else who is more familiar with Windows can chime in.

@HighCommander4

Adding --clang-tidy=false didn't help, still crashes.
Tried the snapshot, still crashes.

I'll look into building from source, though isn't it possible to build clangd as a standalone? I only found this. Building the full monstrosity LLVM just to try this out seems excessive. I mean just cloning the repository is a big pain and I recon building will take possibly and hour or more.
Anyways, thanks for the suggstions!

Alright, it sure took a while but here is the symbolized callstack:
Assertion failed: isa<T>(*this) && "Invalid accessor called", file C:\git\thirdparty\llvm-project\llvm\include\llvm/ADT/PointerUnion.h, line 156
Exception Code: 0x80000003
 #0 0x00007ff6695e761c HandleAbort C:\git\thirdparty\llvm-project\llvm\lib\Support\Windows\Signals.inc:419:0
 #1 0x00007ffe60558e05 (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xa8e05)
 #2 0x00007ffe6055ab29 (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xaab29)
 #3 0x00007ffe60561025 (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xb1025)
 #4 0x00007ffe605608b7 (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xb08b7)
 #5 0x00007ffe6055e881 (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xae881)
 #6 0x00007ffe6056158f (C:\WINDOWS\SYSTEM32\ucrtbased.dll+0xb158f)
 #7 0x00007ff6717473b1 llvm::PointerUnion<class clang::ValueDecl const *, class clang::Expr const *, class clang::TypeInfoLValue, class clang::DynamicAllocLValue>::get<class clang::ValueDecl const *>(void) const C:\git\thirdparty\llvm-project\llvm\include\llvm\ADT\PointerUnion.h:156:0
 #8 0x00007ff6717473f7 clang::APValue::LValueBase::get<class clang::ValueDecl const *>(void) const C:\git\thirdparty\llvm-project\clang\include\clang\AST\APValue.h:164:0
 #9 0x00007ff671fe567d clang::serialization::BasicWriterBase<class clang::ASTRecordWriter>::writeAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:920:0
#10 0x00007ff671fe0a1e clang::serialization::WriteDispatcher<class clang::APValue>::write<class clang::ASTRecordWriter, class clang::APValue const &>(class clang::ASTRecordWriter &, class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:30:0
#11 0x00007ff671fe0b9f clang::serialization::DataStreamBasicWriter<class clang::ASTRecordWriter>::writeArray<class clang::APValue>(class llvm::ArrayRef<class clang::APValue>) C:\git\thirdparty\llvm-project\clang\include\clang\AST\AbstractBasicWriter.h:146:0
#12 0x00007ff671fe52a5 clang::serialization::BasicWriterBase<class clang::ASTRecordWriter>::writeAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:871:0
#13 0x00007ff671fe0a1e clang::serialization::WriteDispatcher<class clang::APValue>::write<class clang::ASTRecordWriter, class clang::APValue const &>(class clang::ASTRecordWriter &, class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:30:0
#14 0x00007ff671fe0b9f clang::serialization::DataStreamBasicWriter<class clang::ASTRecordWriter>::writeArray<class clang::APValue>(class llvm::ArrayRef<class clang::APValue>) C:\git\thirdparty\llvm-project\clang\include\clang\AST\AbstractBasicWriter.h:146:0
#15 0x00007ff671fe5228 clang::serialization::BasicWriterBase<class clang::ASTRecordWriter>::writeAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:869:0
#16 0x00007ff671fe0a1e clang::serialization::WriteDispatcher<class clang::APValue>::write<class clang::ASTRecordWriter, class clang::APValue const &>(class clang::ASTRecordWriter &, class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:30:0
#17 0x00007ff671fe0b9f clang::serialization::DataStreamBasicWriter<class clang::ASTRecordWriter>::writeArray<class clang::APValue>(class llvm::ArrayRef<class clang::APValue>) C:\git\thirdparty\llvm-project\clang\include\clang\AST\AbstractBasicWriter.h:146:0
#18 0x00007ff671fe52a5 clang::serialization::BasicWriterBase<class clang::ASTRecordWriter>::writeAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:871:0
#19 0x00007ff671fe0a1e clang::serialization::WriteDispatcher<class clang::APValue>::write<class clang::ASTRecordWriter, class clang::APValue const &>(class clang::ASTRecordWriter &, class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:30:0
#20 0x00007ff671fe0b9f clang::serialization::DataStreamBasicWriter<class clang::ASTRecordWriter>::writeArray<class clang::APValue>(class llvm::ArrayRef<class clang::APValue>) C:\git\thirdparty\llvm-project\clang\include\clang\AST\AbstractBasicWriter.h:146:0
#21 0x00007ff671fe52a5 clang::serialization::BasicWriterBase<class clang::ASTRecordWriter>::writeAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\AbstractBasicWriter.inc:871:0
#22 0x00007ff671fe1f8e clang::ASTRecordWriter::AddAPValue(class clang::APValue const &) C:\git\thirdparty\llvm-project\clang\include\clang\Serialization\ASTRecordWriter.h:175:0
#23 0x00007ff671fd3866 clang::ASTDeclWriter::VisitLifetimeExtendedTemporaryDecl(class clang::LifetimeExtendedTemporaryDecl *) C:\git\thirdparty\llvm-project\clang\lib\Serialization\ASTWriterDecl.cpp:1200:0
#24 0x00007ff671fe273f clang::declvisitor::Base<struct std::add_pointer, class clang::ASTDeclWriter, void>::Visit(class clang::Decl *) C:\git\thirdparty\llvm-project\build\tools\clang\include\clang\AST\DeclNodes.inc:95:0
#25 0x00007ff671fcb7f8 clang::ASTDeclWriter::Visit(class clang::Decl *) C:\git\thirdparty\llvm-project\clang\lib\Serialization\ASTWriterDecl.cpp:281:0
#26 0x00007ff671fcaf0f clang::ASTWriter::WriteDecl(class clang::ASTContext &, class clang::Decl *) C:\git\thirdparty\llvm-project\clang\lib\Serialization\ASTWriterDecl.cpp:2471:0
#27 0x00007ff671f289dd clang::ASTWriter::WriteASTCore(class clang::Sema &, class llvm::StringRef, class clang::Module *) C:\git\thirdparty\llvm-project\clang\lib\Serialization\ASTWriter.cpp:4997:0
#28 0x00007ff671f2a70f clang::ASTWriter::WriteAST(class clang::Sema &, class llvm::StringRef, class clang::Module *, class llvm::StringRef, bool, bool) C:\git\thirdparty\llvm-project\clang\lib\Serialization\ASTWriter.cpp:4547:0
#29 0x00007ff671f0da90 clang::PCHGenerator::HandleTranslationUnit(class clang::ASTContext &) C:\git\thirdparty\llvm-project\clang\lib\Serialization\GeneratePCH.cpp:68:0
#30 0x00007ff6718eb7ae `anonymous namespace'::PrecompilePreambleConsumer::HandleTranslationUnit C:\git\thirdparty\llvm-project\clang\lib\Frontend\PrecompiledPreamble.cpp:297:0
#31 0x00007ff671d700e1 clang::ParseAST(class clang::Sema &, bool, bool) C:\git\thirdparty\llvm-project\clang\lib\Parse\ParseAST.cpp:203:0
#32 0x00007ff671893dba clang::ASTFrontendAction::ExecuteAction(void) C:\git\thirdparty\llvm-project\clang\lib\Frontend\FrontendAction.cpp:1167:0
#33 0x00007ff6718936ce clang::FrontendAction::Execute(void) C:\git\thirdparty\llvm-project\clang\lib\Frontend\FrontendAction.cpp:1062:0
#34 0x00007ff6718e706a clang::PrecompiledPreamble::Build(class clang::CompilerInvocation const &, class llvm::MemoryBuffer const *, struct clang::PreambleBounds, class clang::DiagnosticsEngine &, class llvm::IntrusiveRefCntPtr<class llvm::vfs::FileSystem>, class std::shared_ptr<class clang::PCHContainerOperations>, bool, class clang::PreambleCallbacks &) C:\git\thirdparty\llvm-project\clang\lib\Frontend\PrecompiledPreamble.cpp:522:0
#35 0x00007ff66c9d26bd clang::clangd::buildPreamble(class llvm::StringRef, class clang::CompilerInvocation, struct clang::clangd::ParseInputs const &, bool, class std::function<(class clang::ASTContext &, class clang::Preprocessor &, class clang::clangd::CanonicalIncludes const &)>, struct clang::clangd::PreambleBuildStats *) C:\git\thirdparty\llvm-project\clang-tools-extra\clangd\Preamble.cpp:545:0
#36 0x00007ff6690beeb8 clang::clangd::`anonymous namespace'::Checker::buildAST C:\git\thirdparty\llvm-project\clang-tools-extra\clangd\tool\Check.cpp:209:0
#37 0x00007ff6690c18d3 clang::clangd::check(class llvm::StringRef, class clang::clangd::ThreadsafeFS const &, struct clang::clangd::ClangdLSPServer::Options const &) C:\git\thirdparty\llvm-project\clang-tools-extra\clangd\tool\Check.cpp:462:0
#38 0x00007ff6690637a8 main C:\git\thirdparty\llvm-project\clang-tools-extra\clangd\tool\ClangdMain.cpp:993:0
#39 0x00007ff6714d1c69 invoke_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:79:0
#40 0x00007ff6714d1b4e __scrt_common_main_seh D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288:0
#41 0x00007ff6714d1a0e __scrt_common_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:331:0
#42 0x00007ff6714d1cfe mainCRTStartup D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp:17:0
#43 0x00007ffedcea26ad (C:\WINDOWS\System32\KERNEL32.DLL+0x126ad)
#44 0x00007ffede28a9f8 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x5a9f8)

Further digging:
If I change line 920 above to just call lvalueBase.getType() instead of doing the casting first, then it ends up evaluating is<DynamicAllocLValue>() to true here:

and things move along for a bit, but then in some other part of the codebase it'll do the same const ValueDecl* cast and crash in the same way as before.

isn't it possible to build clangd as a standalone?

Just to address this point: no, clangd cannot currently be built standalone, though I've suggested this in https://github.com/clangd/clangd/discussions/1375.
However, even if that were possible, it would not have been very helpful in this case, since the crash is not directly in clangd code, but in clang code invoked by clangd code (in the stack trace you posted, everything above frame 34  is clang code). With a hypothetical standalone build, those frames would be in a prebuilt clang library and so presumably wouldn't be symbolized.
That said, it shouldn't be necessary to do a local build to get a symbolized stack trace; having llvm-symbolizer in the PATH should be sufficient (though I've heard users report this not working on Windows; I'm not sure why).

Anyways, it's great for debugging purposes that you have a local build! I'll have a look at your findings and see if I can suggest something to try.

It looks like, when DynamicAllocLValue was added as a fourth possible type of the variant in LValueBase::Ptr, adding serialization support for this option was overlooked.

@helmesjo could you try applying the patch at https://reviews.llvm.org/D154471 locally, and see if it fixes the crash for you?

isn't it possible to build clangd as a standalone?

Just to address this point: no, clangd cannot currently be built standalone, though I've suggested this in https://github.com/clangd/clangd/discussions/1375.
However, even if that were possible, it would not have been very helpful in this case, since the crash is not directly in clangd code, but in clang code invoked by clangd code (in the stack trace you posted, everything above frame 34  is clang code). With a hypothetical standalone build, those frames would be in a prebuilt clang library and so presumably wouldn't be symbolized.
That said, it shouldn't be necessary to do a local build to get a symbolized stack trace; having llvm-symbolizer in the PATH should be sufficient (though I've heard users report this not working on Windows; I'm not sure why).

Anyways, it's great for debugging purposes that you have a local build! I'll have a look at your findings and see if I can suggest something to try.

Thanks for the detailed reply!

@helmesjo could you try applying the patch at https://reviews.llvm.org/D154471 locally, and see if it fixes the crash for you?

Sure, will do!

@HighCommander4
I applied the patch to 16.0.2 with but still a crash, though not in the same location... I'll try it on master as well.

I applied the patch to 16.0.2 but still a crash... Still "Invalid accessor called" but a different callstack.

Could you post the stack please? It should allow us to determine whether it's the same issue cropping up somewhere else, or a different issue.

I applied the patch to 16.0.2 but still a crash... Still "Invalid accessor called" but a different callstack.

Could you post the stack please? It should allow us to determine whether it's the same issue cropping up somewhere else, or a different issue.

        clangd.exe!HandleAbort(int Sig) Line 419	C++
 	[External Code]
 	clangd.exe!llvm::PointerUnion<clang::ValueDecl const *,clang::Expr const *,clang::TypeInfoLValue,clang::DynamicAllocLValue>::get<clang::ValueDecl const *>() Line 156	C++
 	clangd.exe!clang::APValue::LValueBase::get<clang::ValueDecl const *>() Line 164	C++
 	clangd.exe!clang::serialization::BasicWriterBase<clang::ASTRecordWriter>::writeAPValue(const clang::APValue & node) Line 972	C++
 	clangd.exe!clang::serialization::WriteDispatcher<clang::APValue>::write<clang::ASTRecordWriter,clang::APValue const &>(clang::ASTRecordWriter & W, const clang::APValue & <args_0>) Line 30	C++
 	clangd.exe!clang::serialization::DataStreamBasicWriter<clang::ASTRecordWriter>::writeArray<clang::APValue>(llvm::ArrayRef<clang::APValue> array) Line 146	C++
 	clangd.exe!clang::serialization::BasicWriterBase<clang::ASTRecordWriter>::writeAPValue(const clang::APValue & node) Line 871	C++
 	clangd.exe!clang::serialization::WriteDispatcher<clang::APValue>::write<clang::ASTRecordWriter,clang::APValue const &>(clang::ASTRecordWriter & W, const clang::APValue & <args_0>) Line 30	C++
 	clangd.exe!clang::serialization::DataStreamBasicWriter<clang::ASTRecordWriter>::writeArray<clang::APValue>(llvm::ArrayRef<clang::APValue> array) Line 146	C++
 	clangd.exe!clang::serialization::BasicWriterBase<clang::ASTRecordWriter>::writeAPValue(const clang::APValue & node) Line 869	C++
 	clangd.exe!clang::serialization::WriteDispatcher<clang::APValue>::write<clang::ASTRecordWriter,clang::APValue const &>(clang::ASTRecordWriter & W, const clang::APValue & <args_0>) Line 30	C++
 	clangd.exe!clang::serialization::DataStreamBasicWriter<clang::ASTRecordWriter>::writeArray<clang::APValue>(llvm::ArrayRef<clang::APValue> array) Line 146	C++
 	clangd.exe!clang::serialization::BasicWriterBase<clang::ASTRecordWriter>::writeAPValue(const clang::APValue & node) Line 871	C++
 	clangd.exe!clang::serialization::WriteDispatcher<clang::APValue>::write<clang::ASTRecordWriter,clang::APValue const &>(clang::ASTRecordWriter & W, const clang::APValue & <args_0>) Line 30	C++
 	clangd.exe!clang::serialization::DataStreamBasicWriter<clang::ASTRecordWriter>::writeArray<clang::APValue>(llvm::ArrayRef<clang::APValue> array) Line 146	C++
 	clangd.exe!clang::serialization::BasicWriterBase<clang::ASTRecordWriter>::writeAPValue(const clang::APValue & node) Line 871	C++
 	clangd.exe!clang::ASTRecordWriter::AddAPValue(const clang::APValue & Value) Line 175	C++
 	clangd.exe!clang::ASTDeclWriter::VisitLifetimeExtendedTemporaryDecl(clang::LifetimeExtendedTemporaryDecl * D) Line 1200	C++
 	clangd.exe!clang::declvisitor::Base<std::add_pointer,clang::ASTDeclWriter,void>::Visit(clang::Decl * D) Line 95	C++
 	clangd.exe!clang::ASTDeclWriter::Visit(clang::Decl * D) Line 281	C++
 	clangd.exe!clang::ASTWriter::WriteDecl(clang::ASTContext & Context, clang::Decl * D) Line 2471	C++
 	clangd.exe!clang::ASTWriter::WriteASTCore(clang::Sema & SemaRef, llvm::StringRef isysroot, clang::Module * WritingModule) Line 4997	C++
 	clangd.exe!clang::ASTWriter::WriteAST(clang::Sema & SemaRef, llvm::StringRef OutputFile, clang::Module * WritingModule, llvm::StringRef isysroot, bool hasErrors, bool ShouldCacheASTInMemory) Line 4547	C++
 	clangd.exe!clang::PCHGenerator::HandleTranslationUnit(clang::ASTContext & Ctx) Line 68	C++
 	clangd.exe!`anonymous namespace'::PrecompilePreambleConsumer::HandleTranslationUnit(clang::ASTContext & Ctx) Line 297	C++
 	clangd.exe!clang::ParseAST(clang::Sema & S, bool PrintStats, bool SkipFunctionBodies) Line 203	C++
 	clangd.exe!clang::ASTFrontendAction::ExecuteAction() Line 1167	C++
 	clangd.exe!clang::FrontendAction::Execute() Line 1062	C++
 	clangd.exe!clang::PrecompiledPreamble::Build(const clang::CompilerInvocation & Invocation, const llvm::MemoryBuffer * MainFileBuffer, clang::PreambleBounds Bounds, clang::DiagnosticsEngine & Diagnostics, llvm::IntrusiveRefCntPtr<llvm::vfs::FileSystem> VFS, std::shared_ptr<clang::PCHContainerOperations> PCHContainerOps, bool StoreInMemory, clang::PreambleCallbacks & Callbacks) Line 522	C++
 	clangd.exe!clang::clangd::buildPreamble(llvm::StringRef FileName, clang::CompilerInvocation CI, const clang::clangd::ParseInputs & Inputs, bool StoreInMemory, std::function<void __cdecl(clang::ASTContext &,clang::Preprocessor &,clang::clangd::CanonicalIncludes const &)> PreambleCallback, clang::clangd::PreambleBuildStats * Stats) Line 545	C++
 	clangd.exe!clang::clangd::`anonymous namespace'::Checker::buildAST() Line 209	C++
 	clangd.exe!clang::clangd::check(llvm::StringRef File, const clang::clangd::ThreadsafeFS & TFS, const clang::clangd::ClangdLSPServer::Options & Opts) Line 462	C++
 	clangd.exe!main(int argc, char * * argv) Line 993	C++
 	[External Code]

Thanks. The stack trace suggests underlying issue is the same, i.e. my patch is incomplete. I'll take another crack at it.

Ok, I believe I found the issue and updated the patch at https://reviews.llvm.org/D154471 to fix it.
@helmesjo could you give it another try with the updated version of the patch?

Thanks for checking! I submitted the patch for review.

This was fixed in clangd 17.


Stack overflow?

I've tried several ways to close the cycle with Proxy and they all seem to result in a stack overflow.  Perhaps this sets up an infinite loop in the stream control logic?
This example counts to 5 the hard way, but it's a good example of the process I'm trying to model (shutting down a harmonic oscillator when it comes to rest).  y$ emits a single true when the accumulated sum reaches 15.  Closed-loop this would shut x$ down.
When the attach line is commented out you can see this in the console log.  When it not commented out Chrome just sits there for a few seconds until devtools disconnects. I presume this crash is from the stack filling up with an endless stream of handshaking.
import { proxy }     from 'most-proxy'
import { periodic }  from 'most'

const trigger$ = periodic(1000, 1)
  .scan( (s, t) => s + t, 0)
  .take(10)

const { stream: yProxy$, attach: attachY } = proxy()

const x$ = trigger$.until(yProxy$)

const y$ = x$
  .scan( (s, x) => s + x, 0 )
  .map( sum => sum >= 15)
  .filter( b => b )
  .skipRepeats()

attachY(y$)

x$.observe( x => console.log(x))
y$.observe( x => console.log(x))

[edit] - Perhaps some sort of air-gap or break in the handshaking protocols is needed in the proxy stream to make the stream graph appear acyclic to the scheduler?

This is probably related to #4

Hi @tdsfugal sorry it's been a while, but there is a fix for #4 now, and that was indeed the issue here.
http://www.webpackbin.com/Nk5JUo1WG
Feel free to reopen if that's not the correct output.


Make Backup Status Available

Issue by vlerenc
Tuesday Oct 24, 2017 at 00:35 GMT
Originally opened as https://git.removed/kubernetes-attic/garden-operator/issues/161

Right now, the user (nor operator for that matter) has access to the status (success or failure) of the backups, their full list with date/time (taken, took) or the size. As a first step towards on-demand restore, this would be helpful.
It is not clear, whether this should be handled within the operator (as additional status information) or put into additional CRD "backup" resources that are then read from the seed cluster/shoot namespace. Other implementation proposals are welcome.

This ticket makes no sense anymore after we have learned that there is no infrastructure reconciler, i.e. we could end up with backups that shows infrastructure resources that do no longer exist (e.g. an LB service was deleted after the backup was taken) or vice versa, that lacks infrastructure resources that exist, but the cluster has forgotten about (e.g. an LB service was created after the backup was taken). Furthermore, after being made aware of this shortcoming, it becomes apparent that all kinds of other scenarios are also broken with old backups as long as the restore is no intrinsic part Kubernetes, e.g. CRDs could carry any meaning and reflect any state in the physical world outside the Kubernetes cluster itself (e.g. something similar like infrastructure resources). As long as Kubernetes becomes not fully aware of a restore and can inform all involved parties, there is no point in restoring old backups or PiTR. It is simply not possible without rock-solid reconcilers and even then it would be dangerous and potentially stupid to reconcile data loss. ;-)
Therefore we discussed in our cross-location syncs to drop this idea and instead follow up on continuous etcd backups, so that we can shorten the timespan between backups respectively always have up-to-date backups to reduce the likelihood of restoring an outdated backup that could bring the above problems.


Windows Xp Crash

Describe the bug
Installed successful on windows xp sp3, but when i use the menus, then i choose command menu > 1.make double jump, then the game isnt responding, i had to close from task manager
Expected behavior
Make double jump like normally the bot doe
Video
Later?..
Environment details:

OS: Windows Xp Sp3
Engine: regame/vanilla? ( i forgor)
GameDLL: regame/vanilla? ( i forgor too)
Metamod: an metamod (forgor)
Bot Version: newest
Game mode: de_

Additionally, please provide list of AMX Mod X plugins: amxx plugins and list of Metamod plugins: meta plugins.
Amxx plugins:
(too many, i forgor all of em, ill add later)
Meta plugins:
Some default amxx libraries (like hamsandwich, etc)
The metamod itself
& obviously, Yapb
Additional context
Im not using my notebook right now, soo ill add some info later..
I also has feature request, ill describe here cuz i dont want to open new issue, its just simple, can you add a feature that make the bots can reply to player chat like "realbot" feature, example:
Player: "f*ck"
Bots: "watch your mouth, Player!"
Another bots: "someone is being toxic here!"
Thanks @jeefo for making the bots compatible with the old windows xp

Can you write a specific version of the bot, not the "newest" one?

And you did not add other bots to the game in parallel with yapb?
I literally wrote about this bug yesterday, and it was fixed (did not check yet).
Download the latest binary from GitHub Actions

Can you write a specific version of the bot, not the "newest" one?

V.4.2.637

And you did not add other bots to the game in parallel with yapb?

Well, i did, i add zbot bots separately with yapb (:

The YaPB command menu from the latest build from GitHub Actions works good for me, with other bots

I also has feature request, ill describe here cuz i dont want to open new issue, its just simple, can you add a feature that make the bots can reply to player chat like "realbot" feature, example:
Player: "f*ck"
Bots: "watch your mouth, Player!"
Another bots: "someone is being toxic here!"

In the yapb chat config, there are already replies for this word, if you want, you can edit the en_chat.cfg file yourself

The YaPB command menu from the latest build from GitHub Actions works good for me, with other bots

Did you use windows xp?, cuz the problem is on my windows xp

In the yapb chat config, there are already replies for this word, if you want, you can edit the en_chat.cfg file yourself

Ok, ill try it

try latest build from GHA

What is GHA?, is that the "config" folder from master branch?

Did you use windows xp?, cuz the problem is on my windows xp

I'm using Windows 10, but the problem is not in the version of Windows, you need to update the bot.

What is GHA?

I have already said several times, this is GitHub Actions. Find the Actions tab in this repository

is that the "config" folder from master branch?
No, you are talking nonsense. This folder contains configs

try latest build from GHA

Already tried, now it works, thanks

Assume everything is fine!


[Errno 13] Permission denied even I tried used  windows terminals with administrator privileges

Please first make sure you have looked at:

Documentation: https://github.com/mkleehammer/pyodbc/wiki
Other issues

Environment
Win10 21H2 Professional + VS 2015 CE
Python 3.10.4
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python:
pyodbc:
OS:
DB:
driver:

Issue
I tried used  windows terminals with administrator privileges, it doesn't work, it always say "Permission denied", I totally have no clues
D:\opensourcelibrary\python\pyodbc-master>python setup.py install
fatal: Not a git repository (or any of the parent directories): .git
WARNING: git describe failed with: 128
WARNING: Unable to determine version.  Using <IP_ADDRESS>
running install
C:\Users\redmond\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
C:\Users\redmond\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\setuptools\command\easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
error: can't create or remove files in install directory
The following error occurred while trying to add or remove files in the
installation directory:
[Errno 13] Permission denied: 'C:\\Program Files\\WindowsApps\\PythonSoftwareFoundation.Python.3.10_3.10.1264.0_x64__qbz5n2kfra8p0\\Lib\\site-packages\\test-easy-install-7464.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.1264.0_x64__qbz5n2kfra8p0\Lib\site-packages\

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.
For information on other options, you may wish to consult the
documentation at:
https://setuptools.pypa.io/en/latest/deprecated/easy_install.html
Please make the appropriate changes for your system and try again.

any idea? any helps would be appreciated

That is an unusual place to install Python, check that you have write access to it? You can try installing somewhere else too.

That is an unusual place to install Python, check that you have write access to it? You can try installing somewhere else too.

thank you so much sir, really appeciated


feat: add script to update code owners

Description
Support codeowners.yaml file by update-codeowners-from-packages action . See https://github.com/autowarefoundation/autoware-github-actions/issues/236 for details.
Related links
None.
Tests performed
https://github.com/isamu-takagi/autoware.universe/pull/6
https://github.com/isamu-takagi/autoware.universe/pull/7
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

https://github.com/autowarefoundation/autoware-github-actions/issues/236#issuecomment-1529346302


Fix build errors caused by deprecated enums on macOS

@romainguy How's about this approch?

What is the value of CMAKE_OSX_DEPLOYMENT_TARGET inside your CMakeCache.txt? It should be 10.15. I'm not sure how you'd be seeing the errors you mentioned in #6580 unless that was set to 13.0.

@bejado CMAKE_OSX_DEPLOYMENT_TARGET is empty.
//Minimum OS X version to target for deployment (at runtime); newer
// APIs weak linked. Set to empty string for default value.
CMAKE_OSX_DEPLOYMENT_TARGET:STRING=
``
`

@daemyung Try setting it to 10.15. It should be getting set to 10.15 in our build.sh script here.

@bejado It's fine now. Do you want to close this PR? I think it's worth to merge.

@daemyung I'd prefer not to have unnecessary#if checks.


Show the /debug result of a TX in a collapsible way

When sending a TX on the /debug page, the result looks like this:

Maybe we can show the result in a similar way as we do in abi ninja.

Couldn't assign myself, but I'm on this.

https://github.com/scaffold-eth/se-2/pull/90


Fix writeup on kernelised linear regression

Use Moore-Penrose pseudoinverse for niceness.
Add regularisation

Completed in fdb1e83.

Found a bug in your derivation.
f = phi(x)^\top w
and in your least squares error you say
f = Kw
The second is not correct. To go from the first to the second, you need to know that
K = \phi^\top \phi
The kernel trick:
k(x_i, x_j) = < \phi(x_i) , \phi(x_j) >

Finished in 032cca0.


Added parsing and indexing markdowns to algolia index

I need to set up right env vars on travis and added npm command to travis config after we released new doc.

I parse documentation from HTML in the end.
I will change this code to just parse markdowns to check if all files are valid.


Scan Image doesn't work in Android 13

Hi,
Image scanning doesn't work in Android 13: a black screen appears with the rotate buttons and image icons, on the top right corner; a blue rotating arrow appears on the bottom of the screen, but nothing happens.
Clicking the image button doesn't do anything.
Clicking the rotate buttons doesn't do anything.
Waiting doesn't do anything.
Nothing appears on the screen.
It apparently doesn't just work.
See screenshot

I'm having the same issue. If the Dev doesn't respond I think I'll fork this app as there seems to be some interest.

There is a fork that fixes this issue is actively maintained.
https://f-droid.org/en/packages/com.atharok.barcodescanner/


Add dependabot configuration for GitHub Actions

As discussed in #228, this adds a basic dependabot configuration file to keep the actions inside the GitHub Action workflows up-to-date and avoid Node deprecation warnings for example.

Thanks @FriedrichFroebel and @Rotzbua!


Doesn't work after recent Muzei update

There was a Muzei app update from June 25, 2018

Now switching to muzei-earth-view source in Muzei app doesn't have any effect (background image on screenshot stays the same)

I rechecked it, and it works now. Weird, probably some connectivity issues. Sorry for the noise.


bug: Lazy loading telescope

Did you check docs and existing issues?

[X] I have read all the lazy docs
[X] I have searched the existing issues of lazy
[X] I have searched the exsiting issues of the plugin I have a problem with

Neovim version (nvim -v)
NVIM v0.9.0-dev-535+gec1738a6e
Operating system/version
Macos Ventura 13.0.1
Describe the bug
I have my telescope lazy loaded on cmd = 'Telescope' and on event = 'Later'.  But event lazy loading doesn't work. Lazy shows that the plugin is loaded, but after adding some notify calls in the config function, found out the config function was not being called.
Steps To Reproduce
install telescope with cmd and event both set to something
Expected Behavior
Telescope loads fine for all and for all combinations of lazy loading handlers.
Repro
No response

Later isn't an event

it's an autocmd I created

could you show the code of how you do it?
if possible a minimal config

I'll figure out a minimal config and get back to you

If that's a user event, it should be event = "User Later"

If that's not the issue, then provide a repro as specified in the issue template


admiral domains

Find in the attached file admiral tracking and anti adblock domains.
for .input_sources/_SMed79/admiral/domains.txt
(source https://forums.lanik.us/viewtopic.php?f=62&t=39468)

Hi @smed79,
As we updated our repository structure, all our input sources are now represented as repository into Ultimate-Hosts-Blacklick.
Therefore, I invite you to join our team (already send the invitation) there so you can update your input sources yourself!
Have a nice day/night.
Cheers,
Nissar

Closing as every discussions around this input source should be now made from under the organisation.


False AS0024 when removing obsolete overloaded procedure

Describe the bug
If I remove an overloaded procedure that is marked as obsolete (either obsolete attribute on procedure, or ObsoleteState Pending on object) I get AS0024 error
To Reproduce
Steps and to reproduce the behavior:
Create a codeunit with a couple of procedures that are overloaded (same name, different signatures)
Set Obsolete attribute on one of the procedures
Compile to get an app file
Copy the app file to the .alpackages folder
Configure appsourcecop.json for that version
Increase version in app.json
Delete the obsoleted procedure or set it as internal and compile
Now AS0022 will appear. error AS0024: The number of parameters in the external procedure 'MyOverloadedProcedure' has changed from '1' to '0'. This will break dependent extensions.
If I set the procedure to internal, instead of deleting, I also get AS0022, reported in #5870
v1.0
codeunit 50100 "asdf MyCodeunit"
{
    procedure MyOverloadedProcedure()
    begin
        Message('repro');
    end;

    [Obsolete('will be removed', '15.0')]
    procedure MyOverloadedProcedure(param: Integer)
    begin
        Message('now');
    end;
}

v1.1 -> AS0024
codeunit 50100 "asdf MyCodeunit"
{
    procedure MyOverloadedProcedure()
    begin
        Message('repro');
    end;
}

v1.1 with internal -> AS0024 + AS0022
codeunit 50100 "asdf MyCodeunit"
{
    procedure MyOverloadedProcedure()
    begin
        Message('repro');
    end;

    internal procedure MyOverloadedProcedure(param: Integer)
    begin
        Message('now');
    end;
}

Expected behavior
We should be able to delete or change the scope of a procedure if the procedure was obsoleted
Screenshots
N/A
5. Versions:

AL Language: 5.0.270354

Business Central: N/A

@jwikman we just published a new version of the AL extension 5.0.271898, it should fix issues related to the obsoletion of overloaded methods, can you give it a try?

@qutreson I can confirm that this one is fixed in 5.0.271898
Thanks!


Possibility to export mesh animations

Hey there!
Is it possible to export mesh animations created via AnimateAll in blender?
Best regards, Sebi

Hello,
glTF specification can handle:

Object TRS animations
Bones TRS animations
Shapekeys animations on mesh object.

I am not a user of animall addon. Can you please share an example .blend file that you wish to export?

Hello,
More than a month without any answer.
I am going to close this ticket.
Feel free to comment again if you have some information I requested, I will open the ticket again


global: minor fixes

displays 404 page when literature or series is not found on the frontsite (closes #42)
removed "Restricted" facet from the frontsite search (closes #108)
support for configurable search filters labels, renamed the "Relation" filter (closes #109)
repaired link to location editor

About the 404 error patch, I realized that hasError === true does not always imply that error.response is defined (for instance if server is down or if host cannot be resolved).


Last non direct session attribution

Description & motivation
In progress, related to #110

The current PR demonstrates a working last non-direct session attribution model for the default channel grouping only. A few items to address:

For the ignore nulls clause to work properly, we need the (none) values in stg_ga4__sessions_traffic_sources_daily to be set to null. They can be changed to (none) downstream.
Combining incremental models + window functions is very difficult. I set a 30 day lookback window, but any incremental load would be missing data in that window. (Edit: this may not be so hard. Just need to pull 3 + 30 days of data during incremental runs but only append the rows from the last 3 days)

Creating draft for discussion purposes.
Checklist

[ ] I have verified that these changes work locally
[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have run dbt test and python -m pytest . to validate existing tests

I'm thinking the solution here is to build a minimal session table partitioned by day that contains session data possibly with no window functions and certainly with no lookback period. I'll call it int_ga4__sessions_daily.
If we aim for no window functions, we also add a partitioned page_view event table, fct_ga4__event_page_view.
On top of these two tables will build a daily sessions table dim_ga4__sessions or dim_ga4__sesssions_daily that uses a configurable lookback window (30 days is a good default, but this is really a business decision, so it should be in a variable. Since we have the lookback window configured here, we also reconcile cross-partition sessions in this query when hitting int_ga4__sessions_daily and get first_last page_view data from fct_ga4__event_page_view with only a one-day lookback while also resolving last_non_direct.
The goal of this architecture is to have all window functions hitting smaller tables.
Another issue that I've ran into when I set this up for a client on an old fork of the project is sessions with only first_visit and session_start events. Because we filter these events out from our session attribution, we end up failing to include those session keys in our session attribution queries, so when we join attribution data later, there's no data to join against.
We need downstream models to change null to direct or we need to decide to that we want to filter out these sessions. I think changing null to direct to be safer because it's hard to anticipate how people will use GA4. In my client's case, removing those sessions was the right call, but I'm not ready to make that generalization.


As a NUSSU Exco Member, I should be the only person allowed to execute the calculatebudget command and subsequently view all the allocated budgets

completed in #80


Add support for simple resolve of ODSP URLs to odsp-driver

The ODSP driver recently took code from an internal repo that was widely used for resolving ODSP urls to enable some new sharing performance optimizations. This code was put in the ODSPURLResolver2. As part of this code move, the code in this repo, ODSPUrlResolver2 now takes in a required argument to the constructor around sharing link tokens. This breaks a common flow where hosts try to resolve the ODSP url and do not need to do anything with respect to sharing.
Here is an example of code that Teams used to have with the internal resolver that now is broken with the FF resolver.
const resolver = new OdspUrlResolver();
const details = await resolver.resolve({ url: fileUrl });
if (!details || !details.driveId || !details.itemId) {
throw new Error(Couldn't parse fluid file url: ${fileUrl});
}

Duplicate of https://github.com/microsoft/FluidFramework/issues/4338


Question regarding to the difference between http and http/2 client API

Hi, I have a question regarding to the difference between http and http/2 client API.
From the documentation of Host-Level Client-Side API, the library gives me a flow in type [Flow[(HttpRequest, T), (Try[HttpResponse], T), HostConnectionPool]]. To my understanding, the Try[HttpResponse] means that the request will not necessarily be processed by the library successfully, and I'll need to catch exceptions, which does make sense to me.
However, the documentation of Client-Side HTTP/2 says that the library gives me a flow in type Flow[HttpRequest, HttpResponse, Any]. Does that mean a request is guaranteed to obtain a response, and all the exceptions are somehow handled from the library side?
Thank you!

I think it is sensible to assume HTTP requests can fail. The sample code in those 2 doc pages use different approaches. I would suggest that you try using valid and invalid URLs when testing your code to verify that you handle failure cases.

On the HTTP/2 side, there's much less infrastructure available, in particular, there's only a connection level API, which for both HTTP/1.1 and HTTP/2 has the given signature without the extra Try wrapping because if anything goes wrong on the connection, the whole connection is brought down.
For the host-level (pool) API, the extra failure possibility is more a detail of the API.

Thanks for your clarification! I had tested my application with an invalid url, and it got response with status code 502 and body "The server closed the connection before delivering a response." So it looks like if I anything goes wrong on the library side, I would just get a 502 response.
My question in this issue has been answered. Appreciate your help!
But I've another question regarding to "The HTTP/2 connection was shut down while the request was still ongoing". Should I open another issue or it is okay to continue with this issue?

It makes more sense to create an issue but please provide some code to help demo the issue. Stack trace or logging too, if you have them.


Range items overflowing the timeline start and end dates are initially hidden

Hi,
There seems to be a problem with range and background items where they are not initially visible in the timeline if the item(s) start and end range overflows the timelines visible window.
For example having a range item starting from 2019-03-15 to 2019-03-21 is not visible in a timeline initiated with start date of 2019-03-17 and end date 2019-03-19. Once the window is scrolled enough to the future and the item becomes visible it will then stay visible even when scrolling back to the said dates of 2019-03-17 to 2019-03-19.
The hidden items are also not found with timeline.getVisibleItems()
I can see how this could possibly cause long events to never be seen. Any idea what might be causing this?

Did some digging and it seems to be caused by a block of code in Group.js which was added back after being removed from vis.js and being discussed in #81 :
if (!this.isVisible && this.groupId != "__background__") {       for (let i = 0; i < oldVisibleItems.length; i++) {         var item = oldVisibleItems[i];         if (item.displayed) item.hide();       }       return visibleItems;     }
Removing this block seems to remove the problem but performance suffers greatly. Any ideas?
It was mentioned to have been removed because of an issue with an old vis.js version. What issue might that have been? And what was the different fix for that issue in timeline-plus?

Here is something to help out if anyone is looking into this. The problem appears to be the item.hide(); call hiding all previously visible items without checking if they actually should be hidden. Causing the next call to Group._updateItemsInRange() to completely miss these items. Replacing
var item = oldVisibleItems[i];
 if (item.displayed) item.hide();

with
this._checkIfVisibleWithReference(oldVisibleItems[i], visibleItems, visibleItemsLookup, range);
seems to do the trick and scrolling performance with hidden groups still seems much better than without the whole block.

I have the same problem but the block @taavi-halkola mentioned is IMO unrelated to the problem of such items not appearing (it's about hiding all items of invisible groups). Removing the block did not solve the problem.
I'm currently working on a fix.

Hi, is there any progress here or is there something i can help with? I really need this.

@jaytrepka I have a working fix, but with the downside of losing some optimisations regarding large item sets. That's why I didn't push a PR yet...
I'm considering to start such a PR but marked as "not ready to be merged" to start a discussion how this could be merged by @yotamberk. I hope I can continue to work on it soon, maybe in the next few days.

@sbusch I've come to the same conclusion. There are two occasions where this is affected and both seem to affect performance...
@jaytrepka There seems to be a possible workaround but i am not sure what negative side effects it may or may not have. When you are initializing your timeline start with empty groups and items. Then first add items through timeline.setItems() and finally the groups with timeline.setGroups(). Also i do not know if this also has the negative effects of losing performance or not. You should probably test that first if running a performance critical application.
timeline = new Timeline(container, [], [], options) timeline.setItems(dataset) timeline.setGroups(groups)
The main difference here is when initializing the timeline with groups and items the order is the other way around and for some reason this makes the difference. Although drawing the groups first is the correct way to go and commented as important in Timeline.js.
// IMPORTANT: THIS HAPPENS BEFORE SET ITEMS!
  if (groups) {
    this.setGroups(groups);
  }

  // create itemset
  if (items) {
    this.setItems(items);
  }

Et voila, here's the draft PR #157
Appreciating any comments

@jaytrepka If you're making your own builds, you can safely merge this PR into your fork. The scope of changes is quite small and besides the performance drawback it should just work.


Choose archive type per-backup target

Previously, we picked a single archive type for all backup targets. This
results in simpler backups, but means if you add a new backup target you
might have to wait 364 days for your first "yearly" backup to be
created. And really, the first backup of any target should be kept
forever.
Fixes #20.

Actually, this won't work. I need to update the backup deletion logic to also run per-backup-target. Leaving this for another day...


[Fix #362] Fix sign extension bug in next_table_address

Fix an issue where the left shift of the old table address would overwrite the sign extension, making the
address non-canonical and leading to #GPs. This calculates the correct sign extension for the new table
address.

I chose to call it make_address_canonical instead, as it's specialised to address canonicalisation, rather than generic sign extension. Hope that is more readable.
Also, just something I was thinking about while implementing this, I think someone at some point mentioned the idea of replacing the aliases used in VirtualAddress and PhysicalAddress with the newtype pattern. I noticed that the addresses in the table methods use usize, which imo shouldn't be possible. If at some point you supported moving to a stricter use of the address types, I think that would increase safety and give a home to methods like make_address_canonical, and I'd be happy to do some of that legwork.

Awesome, thanks! I like the function name.
Regarding the newtypes for VirtualAddress and PhysicalAddress: I definitely plan to do it for the upcoming second edition (#360). The plan is to move a lot of code to the x86_64 crate and define the newtypes there. The canonical address function would fit in there pretty well, too.
Changing the first edition would be a lot of work, since it touches a lot of code and we would need to adjust almost all posts. So I think it's a better idea to focus on the second edition instead.


Changing Alerting to HA does not work as expected

Not sure if this was actually caused by HA but initially set cluster up as HA then updated to Standalone.  Alerts did not change out of pending mode.
Tried deleted the pvc and recreating the pod but this did not help.  After restarting the gateway the alerts then changed as expected.

note : this can be a symptom of https://github.com/rancher/opni/issues/1583
For the time being, like you mentioned restarting the gateway should fix this


Reddison tries to connect to a slave which is down

Redisson library version: 1.2.1
Hi,
We are using SentinelServersConfig and during the tests we observed that if a slave is down, and sentinel properly reports this by putting the s_down flag, Redisson still considers it at initialization and during the operation tries to connect to it.
This affects badly the performance, since RoundRobin tries periodically send though that slave.
WARN  o.r.c.RoundRobinLoadBalancer - Can't connect to /<IP_ADDRESS>:6379, trying next connection!
As I see, the SentinelConnectionManager constructor does not check for the "s_down" flag when initializes the list of available slaves, thus the Redisson snapshot of slave status does not reflects the status of slave servers.

could you write a full redis slave state string in this case?

at SentinelConnectionManager:72 could you print a map object state?

Hi,
this is the value returned by get(connection.slaves(cfg.getMasterName())) at line 72
[{
role-reported=slave,
info-refresh=8386,
last-ping-sent=0,
role-reported-time=366955099,
ip=<IP_ADDRESS>,
flags=slave,
slave-repl-offset=1351448313,
master-port=6379,
master-host=<IP_ADDRESS>,
slave-priority=100,
port=6379,
pending-commands=0,
name=<IP_ADDRESS>: 6379,
last-ok-ping-reply=253,
last-ping-reply=253,
runid=144ccbb9dcf0a4e6fbda621c3e1e40d7cbab1194,
master-link-status=ok,
master-link-down-time=0,
down-after-milliseconds=60000
},
{
role-reported=slave,
info-refresh=16311645,
last-ping-sent=16304036,
role-reported-time=366955099,
ip=<IP_ADDRESS>,
flags=s_down,
slave,
disconnected,
slave-repl-offset=1328665522,
master-port=6379,
s-down-time=16243978,
master-host=<IP_ADDRESS>,
slave-priority=100,
port=6379,
pending-commands=0,
name=<IP_ADDRESS>: 6379,
last-ok-ping-reply=16304246,
last-ping-reply=16304246,
runid=6bca78e731a66ae4dc0b72053fb7f1318e2d2c45,
master-link-status=ok,
master-link-down-time=0,
down-after-milliseconds=60000
}]

fixed.

WOW, that was quick. We will try then the bleeding edge.
Thank you!


CASSANDRA-16999 covering ssl port

CASSANDRA-16999 is now marked as "Won't Fix" as the single port for encrypted and unencrypted traffic is the answer going forward.  Closing this for now; we can always revisit if attitudes change.


Fix UI : #4124 Remove Save and Discard button from manage tab

Closes #4124
Describe your changes :

I worked on the manage to remove Save and Discard button.

Type of change :

[x] Improvement

Frontend Preview (Screenshots) :
https://user-images.githubusercontent.com/59080942/164225033-2f74df1f-a6d3-4e9b-829e-006d01ebdc81.mov

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
@open-metadata/ui

@Sachin-chaurasiya Can you please take care of the code smells in the next patch?

@Sachin-chaurasiya Can you please take care of the code smells in the next patch?

@vivekratnavel , Sure.


Set RUNVCPKG_NO_CACHE on configure failure

To prevent a partial cache store, the RUNVCPKG_NO_CACHE needs to be set if the run is cancelled or fails. The docs for run-vcpkg mention doing it as an additional step, however this means that any failure at any stage of the job results in no cache being saved, which is less than ideal.
run-cmake should set this environment variable automatically iff the configure preset fails.

@quyykk thanks for the suggestion, indeed setting that variable when cmake --preset configure fails makes perfectly sense.


Search icon of Dashboard template not aligned vertically in 1.2.0

Search icon in header of dashboard template is not aligned vertically.

When the icon is clicked to expand the text field, the text field itself is aligned correctly. The icon moves horizontally in the expected way, but is still much too low vertically.
MDL version 1.2.0, Chrome 52.0.2743.116 (64-bit), OS X 10.11.6

Duplicate of #4690


Uncaught Error: ENOENT: no such file or directory, open '$ATOM_HOME/packages\sync-settings\README...

[Enter steps to reproduce:]

...
...

Atom: 1.46.0 x64
Electron: 4.2.7
OS: Microsoft Windows 10 Home Single Language
Thrown From: Atom Core
Stack Trace
Uncaught Error: ENOENT: no such file or directory, open 'C:\Users\heman.atom\packages\sync-settings\README.md'
At fs.js:115

Error: ENOENT: no such file or directory, open 'C:\Users\heman\.atom\packages\sync-settings\README.md'
    at Object.openSync (fs.js:436:3)
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:160:31)
    at Proxy.readFileSync (fs.js:341:35)
    at Proxy.fs.readFileSync (ELECTRON_ASAR.js:580:40)
    at PackageDetailView.renderReadme (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:826156)
    at PackageDetailView.updateInstalledState (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:825916)
    at PackageDetailView.populate (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:824468)
    at PackageDetailView.completeInitialization (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:819808)
    at PackageDetailView.loadPackage (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:820020)
    at ~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:826771
    at Function.simpleDispatch (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:11:1215907)
    at Emitter.emit (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:11:1217348)
    at PackageManager.emitPackageEvent (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:11:946501)
    at ~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:11:943633
    at r (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:11:938163)
    at o (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:1122275)
    at ChildProcess.n.process.on.e (~/AppData/Local/atom/app-1.46.0/resources/app/static/<embedded>:14:1122481)
    at ChildProcess.emit (events.js:182:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)

Commands
  3x -1:40.1.0 core:backspace (input.hidden-input)

Non-Core Packages
sync-settings 4.3.5

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀


monyx,please don't be one of those lending platforms

Hello, Myx.Please open withdrawals today, I need my money back, do not scam ,I believe that U will find a better way to earn more,oh pls.Hype surrounding your platform is tremendous, so try to benefit from this by creating something revolutional,that's trully possible with funds u have from ICO.

@aid0123 we're going to put the platform in maintenance mode in few hours and withdrawals will be enabled.

Thnaks so much


UI: Good contrast / WCAG compatibility

https://github.com/woodpecker-ci/woodpecker/issues/468#issuecomment-1075089963,

@tecosaur:
This seems like the place to plop UI feedback? I've just started using Woodpecker and I'm sorry to say that the dark mode contrast is atrocious.

Let alone WCAG AAA, this fails WCAG AA standards of accessibility.

I recommend https://accessible-colors.com/ for checking that there's sufficient contrast between foreground and background colours.
Here's what #CCCFD4 looks like:

Copying Gitea's default foreground #bbc0ca is probably another decent option (it's 2/3 of the way to AAA from AA).
On a more stylistic note, I don't think the dark borders do the design any favours either. Here's a lighter version:

There are other improvements that can be made, but this would be a good starting point I think :slightly_smiling_face:.

https://github.com/woodpecker-ci/woodpecker/issues/468#issuecomment-1207138477

https://wave.webaim.org/


Integrate PyUAVCAN

From @Zarkopafilis :

Pyuavcan should start to be exposed in quart. I’m sure that my stubbed out controllers / modules are not a 100% best fit for this, so it could use some refactoring / prototyping

Difficulty: Normal and Architect level
Very early stage PyUAVCAN docs (I am still working on these): https://pyuavcan.readthedocs.io/

This is now done, but a continuous progress is required to bring more features. Being tracked in https://github.com/UAVCAN/Yukon/projects/5 and https://github.com/UAVCAN/Yukon/projects/1.


npm install hangs on Windows 11, clean node install

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
npm install hangs and remains in console without apparent reason.
Steps to reproduce:

Uninstall nodejs, npm.
git clone bootstrap
install nodejs version v20.11.0
npm version is 10.2.4
Windows version is  Microsoft Windows [Version 10.0.22631.3085]
npm install
Installation starts and stops at:

[#########.........] - reify:fsevents: timing reifyNode:node_modules/@rollup/rollup-android-arm-eabi Completed in 189ms

Reduced test cases

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
No response
What version of Bootstrap are you using?
v5.3.2

Perhaps an issue on that package then?


Minimalistic Notebook cell styling

first easy step towards a normal UI :)

less intrusive styles for cell and editor borders (thiner, less noticable colors)
add shadow to selected
hide cell progressbar when not used (it has no info there, just polutes the UI)

see this animated GIF:

@maasg
cc @andypetrella

beautiful :-)


Question about MultiGPULossCompute

It fails to work when I use the multi-gpu-loss-compute version. It appears AssertionError with "  assert len(modules) == len(inputs)  ". I guess it relates to the set of batch size?