Setting up HA first time fails to detect location

The problem
Setting up a brand new HA instance first boot when it asks for your location fails if you hit "detect" for automatic detection. It finds the proper time zone, but not on the map. If you then click on next it errors out completely. You can only manually find your location on the map and then it will allow you to continue with setup.
Environment

Home Assistant release with the issue: 0.104.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):  Docker
Integration causing this issue:
Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

2020-02-05 10:58:40 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140563210791568] Error handling message: invalid latitude for dictionary value @ data['latitude']. Got None
invalid longitude for dictionary value @ data['longitude']. Got None

20-02-05 19:43:51 INFO (MainThread) [hassio.bootstrap] Create Hass.io share folder /data/share
20-02-05 19:43:51 INFO (MainThread) [hassio.bootstrap] Create Hass.io Apparmor folder /data/apparmor
20-02-05 19:43:51 INFO (MainThread) [hassio.bootstrap] Create Hass.io DNS folder /data/dns
20-02-05 19:43:52 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 198
20-02-05 19:43:52 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network
20-02-05 19:43:53 INFO (MainThread) [__main__] Setup HassIO
20-02-05 19:43:53 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-02-05 19:43:53 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-02-05 19:43:53 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-02-05 19:43:53 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.
20-02-05 19:43:53 INFO (MainThread) [hassio.host.info] Update local host information
20-02-05 19:43:53 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-02-05 19:43:53 INFO (MainThread) [hassio.host.services] Update service information
20-02-05 19:43:53 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-02-05 19:43:53 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()
20-02-05 19:43:53 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
20-02-05 19:43:53 INFO (MainThread) [hassio.dns] No CoreDNS plugin Docker image homeassistant/amd64-hassio-dns found.
20-02-05 19:43:53 INFO (MainThread) [hassio.dns] Setup CoreDNS plugin
20-02-05 19:43:53 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-02-05 19:43:54 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-dns tag 1.
20-02-05 19:44:00 INFO (MainThread) [hassio.dns] CoreDNS plugin now installed
20-02-05 19:44:01 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to <IP_ADDRESS>
20-02-05 19:44:01 INFO (MainThread) [hassio.dns] Start CoreDNS plugin
20-02-05 19:44:03 INFO (SyncWorker_3) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - <IP_ADDRESS>
20-02-05 19:44:03 INFO (MainThread) [hassio.homeassistant] No Home Assistant Docker image homeassistant/qemux86-64-homeassistant found.
20-02-05 19:44:03 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant landingpage
20-02-05 19:44:03 INFO (SyncWorker_7) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag landingpage.
20-02-05 19:44:06 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/hassio-addons/repository repository
20-02-05 19:44:06 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/home-assistant/hassio-addons repository
20-02-05 19:44:08 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 62 new - 0 remove
20-02-05 19:44:08 INFO (MainThread) [hassio.addons] Found 0 installed add-ons
20-02-05 19:44:08 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
20-02-05 19:44:08 INFO (MainThread) [hassio.discovery] Load 0 messages
20-02-05 19:44:08 INFO (MainThread) [hassio.ingress] Load 0 ingress session
20-02-05 19:44:08 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 0
20-02-05 19:44:08 INFO (MainThread) [__main__] Run Hass.io
20-02-05 19:44:08 INFO (MainThread) [hassio.api] Start API on <IP_ADDRESS>
20-02-05 19:44:08 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-02-05 19:44:08 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons
20-02-05 19:44:08 INFO (MainThread) [hassio.addons] Phase 'services' start 0 add-ons
20-02-05 19:44:09 INFO (SyncWorker_8) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version landingpage
20-02-05 19:44:14 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-02-05 19:44:14 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
20-02-05 19:44:14 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-02-05 19:44:14 INFO (MainThread) [hassio.core] Hass.io is up and running
20-02-05 19:44:14 INFO (MainThread) [hassio.homeassistant] Setup Home Assistant
20-02-05 19:44:14 INFO (SyncWorker_0) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:landingpage to homeassistant/qemux86-64-homeassistant:0.104.3
20-02-05 19:44:14 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.104.3.
20-02-05 19:45:35 INFO (SyncWorker_0) [hassio.docker.interface] Stop homeassistant application
20-02-05 19:45:37 INFO (SyncWorker_0) [hassio.docker.interface] Clean homeassistant application
20-02-05 19:45:38 INFO (MainThread) [hassio.homeassistant] Home Assistant docker now installed
20-02-05 19:45:38 INFO (MainThread) [hassio.homeassistant] Start Home Assistant
20-02-05 19:45:38 INFO (SyncWorker_2) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.104.3
20-02-05 19:45:53 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-02-05 19:45:54 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:landingpage']
20-02-05 19:47:31 INFO (MainThread) [__main__] Stopping Hass.io
20-02-05 19:47:31 INFO (MainThread) [hassio.api] Stop API on <IP_ADDRESS>
20-02-05 19:47:31 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding
20-02-05 19:47:31 INFO (MainThread) [hassio.core] Hass.io is down
20-02-05 19:47:31 INFO (MainThread) [__main__] Close Hass.io
20-02-05 19:47:56 INFO (MainThread) [__main__] Initialize Hass.io setup
20-02-05 19:47:59 WARNING (MainThread) [hassio.utils.dt] Can't fetch freegeoip data: Cannot connect to host ip-api.com:80 ssl:None [Address not available]
20-02-05 19:47:59 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 198
20-02-05 19:47:59 INFO (MainThread) [__main__] Setup HassIO
20-02-05 19:47:59 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-02-05 19:47:59 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-02-05 19:47:59 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-02-05 19:47:59 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.
20-02-05 19:47:59 INFO (MainThread) [hassio.host.info] Update local host information
20-02-05 19:47:59 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-02-05 19:47:59 INFO (MainThread) [hassio.host.services] Update service information
20-02-05 19:47:59 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-02-05 19:47:59 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()
20-02-05 19:47:59 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
20-02-05 19:47:59 INFO (SyncWorker_0) [hassio.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1
20-02-05 19:47:59 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to <IP_ADDRESS>
20-02-05 19:47:59 INFO (MainThread) [hassio.dns] Start CoreDNS plugin
20-02-05 19:47:59 INFO (SyncWorker_1) [hassio.docker.interface] Clean hassio_dns application
20-02-05 19:48:02 INFO (SyncWorker_1) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - <IP_ADDRESS>
20-02-05 19:48:02 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.104.3
20-02-05 19:48:03 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-02-05 19:48:03 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
20-02-05 19:48:03 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 62 new - 0 remove
20-02-05 19:48:03 INFO (MainThread) [hassio.addons] Found 0 installed add-ons
20-02-05 19:48:03 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-02-05 19:48:03 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
20-02-05 19:48:03 INFO (MainThread) [hassio.discovery] Load 0 messages
20-02-05 19:48:03 INFO (MainThread) [hassio.ingress] Load 0 ingress session
20-02-05 19:48:03 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 1
20-02-05 19:48:03 INFO (MainThread) [__main__] Run Hass.io
20-02-05 19:48:03 INFO (MainThread) [hassio.api] Start API on <IP_ADDRESS>
20-02-05 19:48:03 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-02-05 19:48:03 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons
20-02-05 19:48:03 INFO (MainThread) [hassio.addons] Phase 'services' start 0 add-ons
20-02-05 19:48:03 INFO (SyncWorker_1) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant
20-02-05 19:48:23 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-02-05 19:48:23 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
20-02-05 19:48:23 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-02-05 19:48:23 INFO (MainThread) [hassio.core] Hass.io is up and running
20-02-05 19:59:37 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json

Additional information
Installed via Hassio install script: https://github.com/home-assistant/hassio-installer (without optional components installed)
Also noticed v.105 just came out, and it's not showing up to be able to update to it. (in case this issue is fixed in latest stable) https://version.home-assistant.io/stable.json seems to not be updated to v.105?

Fixed in 105 that we released today!

Just tried from scratch again with v.105 installed and it now doesn't error out, but also still doesn't detect anything (not even region now). And unable to edit Home area after if I leave it on default map setting by accident. (greyed out edit button)

Hm weird. Maybe your IP isn't in the geo databases out there. Using a VPN or tor?
To edit the home, go to config -> General.

Are you blocking ip-api.com via hosts/piHole?

@vladc Ah, that might be it! I am using Pi-Hole on same machine as HA. It's running default blocklists. Is Ip-Api.com blocked by default?

@Hukuma1 It's listed in this default Pi-hole list:

list.2.sysctl.org.domains (http://sysctl.org/cameleon/hosts)

We've emailed the list maintainer asking for an explanation, but we haven't received any response.
That list hasn't been updated since 2018-03-17.

It's not a severe issue, and as @balloob showed can easily be edited. But I was going to suggest to maybe have an address lookup field? The very first time I saw that screen (new user to HA) I had typed in my address (into Home name field) when I saw the map thinking it would auto home to it. Guess I've been conditioned by Google Maps when I see input box over map screen. :P


Unable to save in Deployment Center

The "save" button in Deployment Center is not clickable no matter what I do. I tried changing source and typing in all the input fields:

I recently changed the app service type from Code to Container using Azure CLI, as I wanted to start using custom container instead of zip deployment. I can configure my container settings from the Azure CLI and the web app is running fine, but it is a little bit annoying that I am not able to manually change the image name and tag from Deployment Center.
Surely this must be some kind of bug?
Don't know if this is the right place to report bugs, but I don't know where else to post it.

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

ID: ddc210db-9bbc-1787-8842-0dd29ca2919e
Version Independent ID: d34bf633-bee3-c1ce-72dd-0c80f17f84ad
Content: CI/CD to custom containers - Azure App Service
Content Source: articles/app-service/deploy-ci-cd-custom-container.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

@pettermoe95 Thanks for the feedback! We are currently investigating and will update you shortly.

@pettermoe95 Thanks for reaching here! I tried to repro and was able to change image name and tag from deployment center also, Save is enabled. Could you please try opening Azure Portal in different browser and then try.

@pettermoe95 Thanks for reaching here! I tried to repro and was able to change image name and tag from deployment center also, Save is enabled.

Could you please try opening Azure Portal in different browser and then try.

I testet in different browsers ands till get the same issue. I was able to reproduce this a totalt of 6 times, with different web apps. It only happens after I swap deployment type from code to container using these commands in az:
Swapping App Service from code to container
az webapp config set --name app-myapp --resource-group rg-myrg --linux-fx-version "DOCKER|image/name:tag"

Setting App Service to use managed identity to pull image
az resource update --ids /subscriptions/<subscription>/resourceGroups/rg-myrg/providers/Microsoft.Web/sites/app-myapp/config/web --set properties.acrUseManagedIdentityCreds=True

Activating CI/CD
az webapp deployment container config --enable-cd true --name app-myapp --resource-group rg-myrg

Each time I used these three commands I ended up not being able to use the save button anymore. In the deployment center it shows like this:

But if I go to the Source: Container Registry, I can see the image name etc. that got put with the az command.

@pettermoe95 Thanks for reply! Could you Please reach out to us by sending an email with subject line “Attn:Sneha |thread title” to AzCommunity[at]microsoft[dot]com referencing this thread, would require deeper investigations.
Since we will working offline closing this out but if you feel you need more information please just let us know.


umap axes rotated

Hello,
I am not sure if it is a bug or not. Is it possible that the umap plots can be rotated running scanpy with the same parameters?
Thank you.

I shouldn't think so. Can you give an example?

I do not have a small example, I just wanted to know if it is something that you knew. I noticed it because I run many times the same script, I also noticed few cells located in different positions but very small differences. Maybe it is due tho the umap algorithm.
Thank you.

With the same seed? If you don’t specify a seed, nondeterminism is to be expected.

Yes same seed, I used the default one.

If you don’t specify a seed, nondeterminism is to be expected.

In general, I thought we went for determinism with default arguments in scanpy. I believe pynndescent faster, if non-deterministic, but I get constant output from scanpy.

 Test case
import scanpy as sc
import numpy as np

pbmc = sc.datasets.pbmc3k()

sc.pp.filter_genes(pbmc, min_counts=1)
sc.pp.normalize_total(pbmc)
sc.pp.log1p(pbmc)

adatas = [pbmc.copy() for _ in range(10)]
for adata in adatas:
    sc.pp.pca(adata)
    sc.pp.neighbors(adata)
    sc.tl.umap(adata)

umap_coords = [adata.obsm["X_umap"] for adata in adatas]
assert all([np.array_equal(umap_coords[i], umap_coords[i+1]) for i in range(9)])

I got slight differences many times in the UMAP outputs when updating the single-cell-tutorial notebook for new versions of scanpy/anndata.

At the moment I am saving the adata and I am generating the plots loading it. In this way the coordinates are always the same.


(fixed) - Improve the Email templates

Purpose

The purpose of this PR is to fix #379
Goals
update the mentor acceptance/rejection emails

Approach

Screenshots

Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs
https://github.com/sef-global/scholarx/issues/379

Test environment

Learning

@anjula-sack This was merged into the development branch. I'll open a new PR to merge from development to scholarx-2023


Friendly error message for non-existent file/directory

Fixes https://github.com/helm/helm/issues/6713
Have updated the error message for the missing Chart.yaml
PS - This is my first PR here. Do let me know if I need to make any further changes.
cc @karuppiah7890

Hi Matthew,
I am sorry, I messed it up on this one, I am closing this one to create a fresh clean one.
Sorry again.


Build failure

Trying to build from scratch using commit  5bfaab48f3dc022364f8c636c8e26ba78552ed7b
error: failed to sync

Caused by:
  found duplicate version of package `libc v0.2.139` vendored from two sources:

  	source 1: https://github.com/wasix-org/libc.git?branch=master#4c0c6c29
  	source 2: https://github.com/wasix-org/libc.git#4c0c6c29

Weird. Both sources point to the exact same commit 4c0c6c29. We'll take a look


Allow passing variables via raw YAML

Fixes #350.

Description

This pull request:

is a companion PR to https://github.com/conda-incubator/conda-store/pull/721
allows passing variables via raw YAML, see:
https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-virtual.html#overriding-detected-packages
doesn't create new GUI elements (like the ones we have for channels and dependencies) because the conda-store server currently supports only CONDA_OVERRIDE_CUDA due to a conda-lock limitation (GUI elements can be added later once we have a chance to discuss how that should look like).

Tested manually:

[x] variables is present and equal to {} when creating an environment
[x] variables can be edited when creating an environment and the result can be later seen again via the new or admin UI
[x] variables can be edited after the environment was created, the new result is saved and can be seen again via the new or admin UI (as part of the new build)
[x] the server receives the provided variables value in action_solve_lockfile (in all of the above cases).

Pull request checklist

[x] Did you test this change locally?
[ ] Did you update the documentation (if required)?
[ ] Did you add/update relevant tests for this change (if required)?

Additional information

But I also have a more general question. Are we sure about the word choice for variables? I'm concerned that the name might be a little too generic, and we may come to regret the word choice later.

Agree with you here @gabalafou we should be favouring descriptive variable names, so I suggest something like conda_env_variable or the such @nkaretnikov

This is now blocked because CI is failing (unless this is urgently needed and we want to revert to my original version and merge without CI). The reason is explained in https://github.com/conda-incubator/conda-store-ui/pull/360#issuecomment-1923360060.

@trallard @gabalafou I renamed variables where possible and added new tests. PTAL.
About variable names: the choice of names matter or it can result in subtle bugs due to serialization. We want to make sure that we always generate variables when we serialize.
I ended up following the conventions of existing code: essentially, we need to use variables where dependencies is used and can use a more verbose name in places where requestedPackages is used. This is a good rule of thumb because it's not often clear that a certain object may be serialized later.
This is due to how JavaScript objects are serialized. Note how the key is created automatically here based on the variable name:
> var foo = 'bar'
undefined
> JSON.stringify({foo})
'{"foo":"bar"}'

The test code needs to be rewritten (there are many things wrong with the added tests, it will save me a lot of time if we could review them together synchronously)

Scheduled a meeting to discuss this.

Thanks for your review @gabalafou, as usual it is a critical and in depth one
I agree with having the code and tests fixed before merging.

We had a call about tests in this PR. The comments above are from that call, but there's one issue we didn't have time to get to:
@gabalafou raised an issue about us comparing textContent to raw strings in the testsuite, because it might potentially break later when the rendering logic changes (such as when we update a dependency or refactor the code), since the strings include whitespace. Gabriel wanted to see the code that generates these on the UI side to better understand how this should be checked instead.
My answer to this is as follows: checking the raw output is the whole point of the test! From this standpoint, it's irrelevant how the current code is written. What I'm trying to avoid is potential future problems when someone updates the logic in the codebase or some dependency breaks (someone might add a new field or remove a field or change a list to a dict or something else). This format is what the users will see and it needs to match the conda format as well. Ideally, I'd like this tests to include newlines as well, but it's not possible when using textContent because newlines are rendered via CSS (the entries in the YAML text field are div and span elements with attributes).
As for these tests breaking because some dependency started to format lists with 4 spaces by default instead of 2, I'm not really worried about that. It'd be easy to update. However, I think there's real value in detecting formatting/generation errors early as opposed to checking other parts of the system (the formatting issue here might manifest as an input issue in conda or it might just be ignored, but the users will see strange output in the UI, which doesn't really match the conda spec). And yes, ideally, I'd include newlines as well, but it's tricky to do because of how this is rendered (see the comment about CSS above). So the current approach is the second best thing to getting 1-to-1 raw YAML output out of the system. I'll also add that this is how the current playwright tests are written as well, see test/playwright/test_ux.py:
page.get_by_text("channels: - conda-forgedependencies: - rich - pip: - nothing - ipykernel").fill("channels:\n  - conda-forge\ndependencies:\n  - rich\n  - python\n  - pip:\n      - nothing\n  - ipykernel\n\n")

That said, I'd be happy to reconsider and welcome suggestions! I'm just not sure how else we can write these to catch potential future changes to the generated YAML.

I had another meeting about this with @gabalafou. We discussed tests comparing against raw strings.
I think I'll just try to rewrite these tests such that we check: if <key>, then <value> == <expected> and try to do it in a way that ignores newlines/whitespace.
This will address the point that Gabriel made about this potentially breaking for unrelated reasons, while satisfying what I want to test for, which is that variables have very specific names.
I still think we should find a way to capture the entire output, newlines included, and test that as well, somewhere. But it's something we can postpone for later.

@gabalafou
Note: I still need to fix the issue where variables are not saved when you switch from/to YAML. I'll do so shortly.
But I've updated the tests based on our discussions. PTAL.
The reason I'm using textContent ... toBe is because it matches the string end-to-end. If you prefer strings not to have leading whitespace at all, another option is to use .toHaveTextContent.
Compared with before, these tests now print the HTML node value when it fails to match. They also look at a single component instead of searching through the entire page.
I'm also attaching a screenshot, which shows how the HTML looks like when the YAML file has dependencies. It explains why I'm using nextElementSibling and closest. If you can think of a better way to access this information, I welcome your feedback.

The commits I pushed yesterday add support for (temporary) saving the state of variables when switching between GUI/YAML, which is another issue that was highlighted as part of this review. I think this addresses all the feedback I've received so far.

Gabriel and I had a very productive discussion about this. To get this accepted:

Remove all changes to tests because these will be flaky and we don't have good testing infrastructure for those types of tests
Remove extraneous dispatch calls (only a couple of those actually matter for saving the state).

@gabalafou PTAL. I'll rebase before landing. Do not want to rebase right now to avoid making the diff hard to read.

@trallard this is ready, but it needs your approval before I can merge.


Release/v3.0.0alpha2

Pull Request Test Coverage Report for Build 629

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

Totals

Change from base Build 626:
0.0%

Covered Lines:
3934

Relevant Lines:
4314

💛  - Coveralls

If you're wondering what the deal is here, after #141 was already merged, the truth is I screwed up by rebase/merging #141. The "v3.0.0alpha2" tag wasn't fully preserved because the commit to which it was pointing was "erased" from the master branch by the rebase.
I decided it was important to keep the tag, so I re-merged the branch in standard fashion, hence the two duplicated commits and this duplicate PR. I apologize for the confusion.


RuntimeError: Error(s) in loading state_dict for ResNet:

I add the lines:
def eca_resnet50(k_size=[3, 3, 3, 3], num_classes=1000, pretrained=True):
    """Constructs a ResNet-50 model.

    Args:
        k_size: Adaptive selection of kernel size
        num_classes:The classes of classification
        pretrained (bool): If True, returns a model pre-trained on ImageNet
    """
    print("Constructing eca_resnet50......")
    print(pretrained)
    model = ResNet(ECABottleneck, [3, 4, 6, 3], num_classes=num_classes, k_size=k_size)
    model.avgpool = nn.AdaptiveAvgPool2d(1)
    if pretrained:
        model.load_state_dict(torch.load('eca_resnet50_k3557.pth.tar'))
    return model

When I torch.load the model, it shows:
Traceback (most recent call last):
  File "/home/ubuntu/bigdisk/part2/ECANet/main.py", line 414, in <module>
    main()
  File "/home/ubuntu/bigdisk/part2/ECANet/main.py", line 107, in main
    model = models.__dict__[args.arch](k_size=args.ksize)
  File "/home/ubuntu/bigdisk/part2/ECANet/models/eca_resnet.py", line 200, in eca_resnet50
    model.load_state_dict(torch.load('eca_resnet50_k3557.pth.tar'))
  File "/home/ubuntu/anaconda3/envs/augment/lib/python3.6/site-packages/torch/nn/modules/module.py", line 1045, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for ResNet:
	Missing key(s) in state_dict: "conv1.weight", "bn1.weight", "bn1.bias", "bn1.running_mean", "bn1.running_var", "layer1.0.conv1.weight", "layer1.0.bn1.weight", "layer1.0.bn1.bias", "layer1.0.bn1.running_mean", "layer1.0.bn1.running_var", "layer1.0.conv2.weight", "layer1.0.bn2.weight", "layer1.0.bn2.bias", "layer1.0.bn2.running_mean", "layer1.0.bn2.running_var", "layer1.0.conv3.weight", "layer1.0.bn3.weight", "layer1.0.bn3.bias", "layer1.0.bn3.running_mean", "layer1.0.bn3.running_var", "layer1.0.eca.conv.weight", "layer1.0.downsample.0.weight", "layer1.0.downsample.1.weight", "layer1.0.downsample.1.bias", "layer1.0.downsample.1.running_mean", "layer1.0.downsample.1.running_var", "layer1.1.conv1.weight", "layer1.1.bn1.weight", "layer1.1.bn1.bias", "layer1.1.bn1.running_mean", "layer1.1.bn1.running_var", "layer1.1.conv2.weight", "layer1.1.bn2.weight", "layer1.1.bn2.bias", "layer1.1.bn2.running_mean", "layer1.1.bn2.running_var", "layer1.1.conv3.weight", "layer1.1.bn3.weight", "layer1.1.bn3.bias", "layer1.1.bn3.running_mean", "layer1.1.bn3.running_var", "layer1.1.eca.conv.weight", "layer1.2.conv1.weight", "layer1.2.bn1.weight", "layer1.2.bn1.bias", "layer1.2.bn1.running_mean", "layer1.2.bn1.running_var", "layer1.2.conv2.weight", "layer1.2.bn2.weight", "layer1.2.bn2.bias", "layer1.2.bn2.running_mean", "layer1.2.bn2.running_var", "layer1.2.conv3.weight", "layer1.2.bn3.weight", "layer1.2.bn3.bias", "layer1.2.bn3.running_mean", "layer1.2.bn3.running_var", "layer1.2.eca.conv.weight", "layer2.0.conv1.weight", "layer2.0.bn1.weight", "layer2.0.bn1.bias", "layer2.0.bn1.running_mean", "layer2.0.bn1.running_var", "layer2.0.conv2.weight", "layer2.0.bn2.weight", "layer2.0.bn2.bias", "layer2.0.bn2.running_mean", "layer2.0.bn2.running_var", "layer2.0.conv3.weight", "layer2.0.bn3.weight", "layer2.0.bn3.bias", "layer2.0.bn3.running_mean", "layer2.0.bn3.running_var", "layer2.0.eca.conv.weight", "layer2.0.downsample.0.weight", "layer2.0.downsample.1.weight", "layer2.0.downsample.1.bias", "layer2.0.downsample.1.running_mean", "layer2.0.downsample.1.running_var", "layer2.1.conv1.weight", "layer2.1.bn1.weight", "layer2.1.bn1.bias", "layer2.1.bn1.running_mean", "layer2.1.bn1.running_var", "layer2.1.conv2.weight", "layer2.1.bn2.weight", "layer2.1.bn2.bias", "layer2.1.bn2.running_mean", "layer2.1.bn2.running_var", "layer2.1.conv3.weight", "layer2.1.bn3.weight", "layer2.1.bn3.bias", "layer2.1.bn3.running_mean", "layer2.1.bn3.running_var", "layer2.1.eca.conv.weight", "layer2.2.conv1.weight", "layer2.2.bn1.weight", "layer2.2.bn1.bias", "layer2.2.bn1.running_mean", "layer2.2.bn1.running_var", "layer2.2.conv2.weight", "layer2.2.bn2.weight", "layer2.2.bn2.bias", "layer2.2.bn2.running_mean", "layer2.2.bn2.running_var", "layer2.2.conv3.weight", "layer2.2.bn3.weight", "layer2.2.bn3.bias", "layer2.2.bn3.running_mean", "layer2.2.bn3.running_var", "layer2.2.eca.conv.weight", "layer2.3.conv1.weight", "layer2.3.bn1.weight", "layer2.3.bn1.bias", "layer2.3.bn1.running_mean", "layer2.3.bn1.running_var", "layer2.3.conv2.weight", "layer2.3.bn2.weight", "layer2.3.bn2.bias", "layer2.3.bn2.running_mean", "layer2.3.bn2.running_var", "layer2.3.conv3.weight", "layer2.3.bn3.weight", "layer2.3.bn3.bias", "layer2.3.bn3.running_mean", "layer2.3.bn3.running_var", "layer2.3.eca.conv.weight", "layer3.0.conv1.weight", "layer3.0.bn1.weight", "layer3.0.bn1.bias", "layer3.0.bn1.running_mean", "layer3.0.bn1.running_var", "layer3.0.conv2.weight", "layer3.0.bn2.weight", "layer3.0.bn2.bias", "layer3.0.bn2.running_mean", "layer3.0.bn2.running_var", "layer3.0.conv3.weight", "layer3.0.bn3.weight", "layer3.0.bn3.bias", "layer3.0.bn3.running_mean", "layer3.0.bn3.running_var", "layer3.0.eca.conv.weight", "layer3.0.downsample.0.weight", "layer3.0.downsample.1.weight", "layer3.0.downsample.1.bias", "layer3.0.downsample.1.running_mean", "layer3.0.downsample.1.running_var", "layer3.1.conv1.weight", "layer3.1.bn1.weight", "layer3.1.bn1.bias", "layer3.1.bn1.running_mean", "layer3.1.bn1.running_var", "layer3.1.conv2.weight", "layer3.1.bn2.weight", "layer3.1.bn2.bias", "layer3.1.bn2.running_mean", "layer3.1.bn2.running_var", "layer3.1.conv3.weight", "layer3.1.bn3.weight", "layer3.1.bn3.bias", "layer3.1.bn3.running_mean", "layer3.1.bn3.running_var", "layer3.1.eca.conv.weight", "layer3.2.conv1.weight", "layer3.2.bn1.weight", "layer3.2.bn1.bias", "layer3.2.bn1.running_mean", "layer3.2.bn1.running_var", "layer3.2.conv2.weight", "layer3.2.bn2.weight", "layer3.2.bn2.bias", "layer3.2.bn2.running_mean", "layer3.2.bn2.running_var", "layer3.2.conv3.weight", "layer3.2.bn3.weight", "layer3.2.bn3.bias", "layer3.2.bn3.running_mean", "layer3.2.bn3.running_var", "layer3.2.eca.conv.weight", "layer3.3.conv1.weight", "layer3.3.bn1.weight", "layer3.3.bn1.bias", "layer3.3.bn1.running_mean", "layer3.3.bn1.running_var", "layer3.3.conv2.weight", "layer3.3.bn2.weight", "layer3.3.bn2.bias", "layer3.3.bn2.running_mean", "layer3.3.bn2.running_var", "layer3.3.conv3.weight", "layer3.3.bn3.weight", "layer3.3.bn3.bias", "layer3.3.bn3.running_mean", "layer3.3.bn3.running_var", "layer3.3.eca.conv.weight", "layer3.4.conv1.weight", "layer3.4.bn1.weight", "layer3.4.bn1.bias", "layer3.4.bn1.running_mean", "layer3.4.bn1.running_var", "layer3.4.conv2.weight", "layer3.4.bn2.weight", "layer3.4.bn2.bias", "layer3.4.bn2.running_mean", "layer3.4.bn2.running_var", "layer3.4.conv3.weight", "layer3.4.bn3.weight", "layer3.4.bn3.bias", "layer3.4.bn3.running_mean", "layer3.4.bn3.running_var", "layer3.4.eca.conv.weight", "layer3.5.conv1.weight", "layer3.5.bn1.weight", "layer3.5.bn1.bias", "layer3.5.bn1.running_mean", "layer3.5.bn1.running_var", "layer3.5.conv2.weight", "layer3.5.bn2.weight", "layer3.5.bn2.bias", "layer3.5.bn2.running_mean", "layer3.5.bn2.running_var", "layer3.5.conv3.weight", "layer3.5.bn3.weight", "layer3.5.bn3.bias", "layer3.5.bn3.running_mean", "layer3.5.bn3.running_var", "layer3.5.eca.conv.weight", "layer4.0.conv1.weight", "layer4.0.bn1.weight", "layer4.0.bn1.bias", "layer4.0.bn1.running_mean", "layer4.0.bn1.running_var", "layer4.0.conv2.weight", "layer4.0.bn2.weight", "layer4.0.bn2.bias", "layer4.0.bn2.running_mean", "layer4.0.bn2.running_var", "layer4.0.conv3.weight", "layer4.0.bn3.weight", "layer4.0.bn3.bias", "layer4.0.bn3.running_mean", "layer4.0.bn3.running_var", "layer4.0.eca.conv.weight", "layer4.0.downsample.0.weight", "layer4.0.downsample.1.weight", "layer4.0.downsample.1.bias", "layer4.0.downsample.1.running_mean", "layer4.0.downsample.1.running_var", "layer4.1.conv1.weight", "layer4.1.bn1.weight", "layer4.1.bn1.bias", "layer4.1.bn1.running_mean", "layer4.1.bn1.running_var", "layer4.1.conv2.weight", "layer4.1.bn2.weight", "layer4.1.bn2.bias", "layer4.1.bn2.running_mean", "layer4.1.bn2.running_var", "layer4.1.conv3.weight", "layer4.1.bn3.weight", "layer4.1.bn3.bias", "layer4.1.bn3.running_mean", "layer4.1.bn3.running_var", "layer4.1.eca.conv.weight", "layer4.2.conv1.weight", "layer4.2.bn1.weight", "layer4.2.bn1.bias", "layer4.2.bn1.running_mean", "layer4.2.bn1.running_var", "layer4.2.conv2.weight", "layer4.2.bn2.weight", "layer4.2.bn2.bias", "layer4.2.bn2.running_mean", "layer4.2.bn2.running_var", "layer4.2.conv3.weight", "layer4.2.bn3.weight", "layer4.2.bn3.bias", "layer4.2.bn3.running_mean", "layer4.2.bn3.running_var", "layer4.2.eca.conv.weight", "fc.weight", "fc.bias".
	Unexpected key(s) in state_dict: "epoch", "arch", "state_dict", "best_prec1", "optimizer".

Hi, I have met the same trouble as you. So did you fix this problem? Thanks!


Some thoughts on DRAM throughput benchmarking

As previously discussed, I think that the current implementation of the DRAM microbenchmark is not ideal, if our goal is to simply measure throughput. The benchmark is currently based on the paper "GPGPU Power Modeling for Multi-Domain Voltage-Frequency Scaling" (Guerreiro18), in which they used it to characterize the power consumption of GPUs when stressing device memory. However, the kernel itself doesn't just do a memory copy, but also includes a parameter N to introduce a certain level of arithmetic intensity. I'm not certain why they have that in there, but I would assume they have their reasons. For us however this means adding another dimension to the benchmark, which makes it harder to evaluate and compare results.
To further complicate things, the actual implementation of the DRAM benchmark used in Guerreiro18, which can be found on GitHub (here), appears to be completely different. In this version, the arithmetic operations are gone, and the kernel mostly consists of copy instructions. However, it still does some strange things I'm not entirely clear about.
Here's my SYCL implementation of this kernel:
cgh.parallel_for<DRAMKernel>(global_size, [=](s::id<1> gid) {
  for(size_t j = 0; j < COPY_ITERATIONS; j += UNROLL_ITERATIONS) {
    for(size_t i = 0; i < UNROLL_ITERATIONS; ++i) {
      DataT r0 = in[gid[0] + STRIDE * i];
      out[gid[0] + STRIDE * i] = r0;
    }
  }
});

As you can see, since the loop variable j is not being used inside the loop body, this kernel repeatedly copies the same chunk of memory from one buffer into the other; by default COPY_ITERATIONS is 1024. In each iteration UNROLL_ITERATIONS (default 32) copies are made. To allow for memory coalescing, each thread accesses the buffer based linearly on its global id. Each subsequent copy is offset by a multiple of STRIDE. This parameter is sensitive to cache sizes: If chosen too small, caching can occur. In the implementation of Guerreiro18, they use an offset of 64 * 1024, and profiling reveals a 0% L2 hit rate on my GTX 2070. If I change this to 32 * 1024 however, I already get a 11% L2 hit rate. How large this stride has to be exactly depends on the number of work items, cache sizes and so on. All in all, this version of the benchmark essentially introduces three additional parameters, greatly increasing its complexity, without a clear benefit.
Furthermore, in order to achieve the highest throughput with this benchmark, it weirdly needs to be compiled without any assembly-level optimizations (by passing -O0 to ptxas). This is of course hard to replicate with hipSYCL, and my SYCL implementation of Guerreiro18 thus also only achieves around ~300 GiB/s, i.e., 67% of the GTX 2070's 448 GiB/s theoretical maximum. This is a bit less than the CUDA version achieves with optimizations (311 GiB/s), and substantially less than it when compiled without optimizations (325 GiB/s).
Long story short, instead of implementing Guerreiro18, I would suggest to instead go for the simplest possible memcopy kernel, i.e.:
cgh.parallel_for<DRAMKernel>(global_size, [=](s::id<1> gid) {
  out[gid] =  in[gid];
});

With this, I'm able to get ~358 GiB/s, which is about 80% of the theoretical maximum, and probably quite close to what we can reasonably expect to achieve.
Note that to get good results, the buffer size needs to be large enough, i.e. at least several hundred megabytes. If we do a plain mapping of --size to buffer size, this means that the specified sizes need to be rather large. For example I used --size=939524096 (which equals 3.5 GiB).
This is of course quite a large number, and a much larger size than many other benchmarks can support (if e.g. it is used as the range in both dimensions of a 2D buffer). One possible solution would be to always multiply the size by some fixed factor, e.g. 1024. However, I generally feel like the mapping of the --size parameter to the actual workload is too arbitrary already. It might be convenient for running lots of benchmarks in batch, but in reality I think we'll have to hand tune these values (as well as any additional parameters a benchmark might have) for each individual platform anyways. I'm thus thinking whether maybe having individual parameters for each benchmark would make more sense (e.g. having a buffer-size= for this one).
In the same vein, having the ability to compute custom metrics would also be great. For example, it would be cool if this benchmark could actually print its achieved throughput, instead of having to manually compute it.
What do you guys think?

I agree with your analysis. Your proposal is much closer to the classical stream workload. For measuring throughput, I think we should rather follow stream.

This is of course quite a large number, and a much larger size than many other benchmarks can support (if e.g. it is used as the range in both dimensions of a 2D buffer). One possible solution would be to always multiply the size by some fixed factor, e.g. 1024. However, I generally feel like the mapping of the --size parameter to the actual workload is too arbitrary already. It might be convenient for running lots of benchmarks in batch, but in reality I think we'll have to hand tune these values (as well as any additional parameters a benchmark might have) for each individual platform anyways. I'm thus thinking whether maybe having individual parameters for each benchmark would make more sense (e.g. having a buffer-size= for this one).

The run-suite script starts with a very small --size parameter (I think something like 64) and then doubles the problem size until the runtime has achieved a minimum runtime that is determined by the test profile in run-suite. I image this could already work well for many cases. If this is not the case here, the test profiles can override the tested problem sizes for individual benchmarks. We could simply edit the test profile to start with larger values if necessary.

In the same vein, having the ability to compute custom metrics would also be great. For example, it would be cool if this benchmark could actually print its achieved throughput, instead of having to manually compute it.

Yes, I agree. The main challenge is that the benchmarks are individual applications, that don't know which results the other benchmarks will emit to the csv file. If the benchmarks emit different columns to the csv, this prevents a correct formatting. A solution could be adding a standard field for all benchmarks that will be present in the result of every benchmark, say, metric, and benchmarks can choose to implement this or return N/A, similar to the verification.

Yes, I agree. The main challenge is that the benchmarks are individual applications, that don't know which results the other benchmarks will emit to the csv file. If the benchmarks emit different columns to the csv, this prevents a correct formatting. A solution could be adding a standard field for all benchmarks that will be present in the result of every benchmark, say, metric, and benchmarks can choose to implement this or return N/A, similar to the verification.

That could work, yes. It is of course a bit limiting and not very descriptive. Hypothetically, if the various benchmarks were to emit additional metrics/columns -- how useful is it really to have all results for all benchmarks in a single file? Couldn't we just generate separate CSVs for each executable?
Additionally, to compute e.g. throughput, the benchmark would need to have access to the timing results, which, given the current plugin/hook architecture seems a bit messy. Maybe timing should be considered a "core" functionality of the framework instead, much like verification?

That could work, yes. It is of course a bit limiting and not very descriptive. Hypothetically, if the various benchmarks were to emit additional metrics/columns -- how useful is it really to have all results for all benchmarks in a single file? Couldn't we just generate separate CSVs for each executable?

The run-suite script invokes each benchmark a dozen times with different combinations of problem size and local size, so we would have a looot of very small csv files, each with only 1 or a couple rows. For every meaningful analysis, those files would need to be aggregated into one file again anyway. It could be done, but it won't be pretty I think.

Additionally, to compute e.g. throughput, the benchmark would need to have access to the timing results, which, given the current plugin/hook architecture seems a bit messy. Maybe timing should be considered a "core" functionality of the framework instead, much like verification?

Hm. Good point. There may be more metrics than just bandwidth that require access to one or multiple measurements (e.g. once we can measure power consumption, flops/s/watt). This makes me think that maybe metrics that represent transformations of actual measurements should maybe better be implemented in a post processing step (e.g. in run-suite) for the most flexibility?

The run-suite script invokes each benchmark a dozen times with different combinations of problem size and local size, so we would have a looot of very small csv files, each with only 1 or a couple rows. For every meaningful analysis, those files would need to be aggregated into one file again anyway. It could be done, but it won't be pretty I think.
Do we need so many different configurations? If we can restrict the number of configurations, then it will not be that messy in one CSV file. For example, we do not need to vary the problem size and local size for every experiment.

Hm. Good point. There may be more metrics than just bandwidth that require access to one or multiple measurements (e.g. once we can measure power consumption, flops/s/watt). This makes me think that maybe metrics that represent transformations of actual measurements should maybe better be implemented in a post processing step (e.g. in run-suite) for the most flexibility?

The problem I see with this is that e.g. in this case, for DRAM bandwidth, we also need to know the amount of bytes copied. If we go with the mapping from --size to 1/2/3D ranges as you proposed on my PR, the number of bytes might depend on that parameter, the dimensionality of the kernel and the data type being copied. So either we have the benchmark log this information somewhere (coming back to the issue of per-benchmark metrics), or we hardcode this somehow into run-suite, which seems like a bad idea to me.

The run-suite script invokes each benchmark a dozen times with different combinations of problem size and local size, so we would have a looot of very small csv files, each with only 1 or a couple rows. For every meaningful analysis, those files would need to be aggregated into one file again anyway. It could be done, but it won't be pretty I think.

Since the script knows which runs belong to the same benchmark, it could just concatenate those outputs into a single CSV. Then we'd have one file per benchmark - that sounds manageable to me.

Closing this as we have merged the simpler version of the DRAM benchmark in #26 and added throughput metrics in #30. Thanks everyone!


Not removable

The application is not removable from my System
Environment
Windows build number: Microsoft Windows [Version 10.0.18363.720]
PowerToys version: V0.15.2
Steps to reproduce
Try to deinstall the application
Expected behavior
deinstalling itself
Actual behavior
nothing

Hi @Fischchen
did you install PowerToys using the MSI?
In order to uninstall it, you can run the same MSI that you used to install it or go to the Windows 10 Settings -> Apps, but don't use the legacy Control Panel.

@Fischchen how are you trying to uninstall?  can you take a screenshot?  Maybe under a different user?  We need more info
From like this screen?

or this method?

Did you do something different?


feat: MemoryTree: A new data structure for improving simp_mem's complexity

We add a data structure, MemoryTree, that keeps track of the current information we have about memory spans. This should allow us to more efficiently exploit e.g. PairwiseSeparate proofs, by lazily unfolding the PairwiseSeparate proof as necessary, instead of the current way, where we explode the full state.

I like where this may be going. For now, all I'll say is that remember this issue in case that affects design decisions:
https://github.com/leanprover/LNSym/issues/162


Non tested components are not considered in calculating total coverage

Describe the bug
Hi,
I'm using Quasar (built on Vue) and when I run component tests, the total coverage is calculated only from tested components. All the other files are in final report (e.g. with 'text-summary' reporter) but with zeros.
I use  Quasar testing which wraps all the necessary tools.
I described my issue in Quasar testing repo ^^ and I was pointed to this repo.

I can see not instrumented files in ./nyc_output/out.json
"component.vue": {
  "path": "component.vue",
  "statementMap": {},
  "fnMap": {},
  "branchMap": {},
  "s": {},
  "f": {},
  "b": {}
}

My app is not important in this case, I cloned Quasar testing and played with it and the result is the same.
I tried almost every suggestion I found, but nothing is working and I can't get real coverage for whole project.
Thanks
Reproduction
https://github.com/quasarframework/quasar-testing
Steps to reproduce
git clone https://github.com/quasarframework/quasar-testing.git
cd quasar-testing
cd test-project-vite
add to .nycrc:

"all": true (it should extend config, but it's not working for me)
"reporter": ["clover", "json", "text", "lcov", "cobertura", "text-summary", "json-summary"] (text-summary shows non tested files with zeros in terminal)

yarn sync:cypress && yarn test:component:ci
System Info
System:
    OS: macOS 13.2
    CPU: (8) arm64 Apple M1
    Memory: 66.98 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.13.0/bin/yarn
    npm: 9.4.1 - ~/.nvm/versions/node/v18.13.0/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Safari: 16.3

Used Package Manager
yarn
Logs
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a vite-plugin-istanbul issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hello @Radik24, thanks for the issue.
Sorry for the wait, but i will look into this a bit further as it relates to other issues in the past. The root case us that the code coverage reporter does not look at all the included files. Only the files in the coverage report.
Why the uncovered files are not in the report is that we hook into vite transform process, which only transforms files that are imported. Which is one of the main features of Vite.
I have not found a way to include the uncovered files in the report but will look into a way to somehow add them asfterhand. Maybe there is a way to "prepare" a report in a way.

Closed due to inactivity.


orderly-json.org is down

The website http://orderly-json.org is not accessible anymore.
Does someone know its new location or perhaps if some has its cached contents?

FWIW http://web.archive.org/web/20160310104230/http://orderly-json.org/

Website is open source too. The markdown source is here https://github.com/lloyd/orderly/blob/website/data/docs.md


Notso Jenkins server setup 1

The rest of the setup appears to need to be manual through the UI. The scripts included can be used for any Linux setup of Jenkins including slave or master.

this request is so old I am either going to have to start over or start from here anew. I will merge it to start "new" from here and make any fixes or adjustments needed in a future pull request.


[FancyZones] don't allow negative hightlight distance

specifying negative distance breaks zoning and generally isn't useful

@SeraphimaZ It might make sense to swap out the Distance and Spacing TextBoxes with a ModernWpf.NumberBox. We can then very easily set the minimum to 0 to resolve this issue. That should also resolve #9065

@SeraphimaZ It might make sense to swap out the Distance and Spacing TextBoxes with a ModernWpf.NumberBox. We can then very easily set the minimum to 0 to resolve this issue. That should also resolve #9065

Let's make sure we only force 0 as minimum value for Distance, and allow negative numbers for Spaces around zones.

Let's make sure we only force 0 as minimum value for Distance, and allow negative numbers for Spaces around zones.

Any upper limit too?

Any upper limit too?

Great news!  This was resolved in the newly released 0.33 version of PowerToys!  Head to https://aka.ms/installpowertoys to grab latest.


Tic-Tac-Toe

🎮 Game Request
Description 📃
X and O have to play turn by turn.
whose ever turn it is, it will be displayed on screen.
Functionalities 🎮
There is sound on each and every turn.
The screen will appear if anyone wins or draw the match.
The game can also restart in between if required.
How to play? 🕹
X player always plays first. He can click on any 9 of the boxes.
Next is O's turn he can click in any 9 of the boxes.
If any 3 appear the same either X or O in row, column or diagonally then he wins.
Point down the features
This is a simple Tic-Tac-Toe game can be played within the two players. It has the best UI interface having good background animation, user feel the best experience during playing the game.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Ash0807 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Ash0807 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add [Parameter.asUrl] and [Parameter.asDate] to json_rpc_2

dart:core has a built-in Date and Uri classes, so it makes sense to support parsing them automatically in json_rpc_2.

This issue has been moved to dart-lang/json_rpc_2#6.


Protect against spurious wakeups

I have seen that no loop is used around a call of the function "pthread_cond_wait".
Would you like to reuse anything from my message on the topic "spurious wakeup"?

Thanks! I think it should use while loop, so I'll modify.

Would you like to reconsider also the checking of corresponding predicates?

Sure.

Thanks for your small source code improvement.


Failed to decode downloaded font

After installing the npm package and creating a component of a Map I am getting this error:
Failed to decode downloaded font: http://localhost:3000/fonts/roboto/Roboto-Regular.woff2 OTS parsing error: invalid version tag
Someone know how to fix this?

Please refer to Getting Help section in the README (or #469).


Error

SonarQube analysis reported 1 issue

 1 blocker

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 major

Watch the comments in this conversation to review them.


Failed to resolve: com.github.amlcurran.showcaseview:library:5.4.0

I was trying to build the project after taking fresh pull and following error has risen.
The showcase library is not getting resolved.
I tried adding other dependencies but they worked fine.
I also tried adding this library on a fresh project, it failed there too.
I guess there might be some issue with the library.
Can anyone try building the project and validate this?

@priyankvex Try building it now. The changes weren't committed after removing the ShowcaseView Library.

@souljaboy764 It built successfully now.

Closing the issue.


Read table options

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Patch coverage: 50.30% and project coverage change: -0.38% :warning:

Comparison is base (4043e54) 66.37% compared to head (6452c19) 65.99%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #797      +/-   ##
==========================================
- Coverage   66.37%   65.99%   -0.38%
==========================================
  Files         232      232
  Lines       22954    22545     -409
==========================================
- Hits        15235    14879     -356
+ Misses       6924     6878      -46
+ Partials      795      788       -7

Flag
Coverage Δ

53.28% <42.94%> (-0.57%)
:arrow_down:

go-1.17.x
66.13% <50.30%> (+0.03%)
:arrow_up:

go-1.19.x
41.26% <14.46%> (-24.89%)
:arrow_down:

go-1.20.x
41.25% <14.46%> (-24.92%)
:arrow_down:

integration
53.28% <42.94%> (-0.57%)
:arrow_down:

macOS
41.21% <14.46%> (+0.06%)
:arrow_up:

ubuntu
?

unit
41.26% <14.46%> (+0.06%)
:arrow_up:

windows
40.98% <14.46%> (-0.18%)
:arrow_down:

ydb-22.5
52.79% <38.03%> (-0.80%)
:arrow_down:

ydb-23.1
52.76% <36.80%> (-0.88%)
:arrow_down:

ydb-23.2
52.81% <37.42%> (-0.68%)
:arrow_down:

ydb-23.2-slim
52.91% <38.34%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

log/retry.go
0.00% <0.00%> (ø)

log/topic.go
5.03% <0.00%> (ø)

log/scripting.go
38.93% <15.38%> (ø)

log/discovery.go
35.41% <16.66%> (ø)

log/sql.go
39.79% <38.88%> (ø)

internal/table/session.go
82.76% <40.00%> (-1.37%)
:arrow_down:

table/options/options.go
56.42% <41.66%> (-2.44%)
:arrow_down:

log/driver.go
68.10% <59.09%> (ø)

log/table.go
83.53% <71.42%> (ø)

internal/version/parse.go
76.92% <76.92%> (ø)

... and 2 more

... and 12 files with indirect coverage changes

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


Usability improvement

Hello guys,
Just started to use this component as MDL is missing a dropdown.
Commmented this

Start at 1 instead of 0

This way, the control is not dirty until a choice is made (so you always see the label or a choice, never an empty control), and you do not see the empty first choice in the dropdown.
I would suggest those modifications to your base code,
Thanks a lot for this component
JF

I tried this out, however there's a bug: The selected value won't be highlighted as the first selection in the drop down.
Example: On a List A,B,C,... when selecting item A, and then clicking again on the dropdown to bring up the list with the selected item on top, not A is scrolled to, but B.


Associate TestExec to Test Plan

Hello ,
I want to associate the testExec to testPlan after an execution of automation tests .
It works with a reportFormat (Junit , Testng) but not works with a reportFormat (Cucumber) .
PS: with the format Junit and testNg the information in not clean , can't import all of steps of scenario Outline.
This my configuration 👍

As mentioned on the README, it's not possible to associate the  cucumber resuts to an existing Test Plan, among other, using the "standard" cucumber format. This has to be with the nature of the underlying Cucumber REST API endpoint that doesnt support it.

You need to use the multipart endpoint instead and provide an auxiliary JSON file to customize the target Test Execution that will be created.
You can see an example of the JSON content on this Python script and adapt it aacordingly.

Thank you for your response , can you please show me an example of the multipart endPoint because when using an example in the doc for xray i can't associate the testExec with testPlan we have a lot of URL and all of this URL doesn't works.I saw two version api/v1 and api/v2 .

On the Xray docs you have another example
You can use a testExecInfo.json similar to:
json
{
    "fields": {
        "project": {
            "key": "CALC"
        },
        "summary": "Brand new Test execution",
        "issuetype": {
            "name": "Test Execution"
        }
    },
    "xrayFields": {
        "testPlanKey": "DEMO-15",
        "environments": ["Chrome"]
    }
}

the environments field on the previous JSON is optional.
Then on your maven configuration use the testExecInfoJson property with the name of the file containing the previous JSON.

Thanks 😊 , it works fine now

Updated the main README.md file with info on this


Consider CounterService#decrement(name, amount) in parallel by spawning multiple threads.

The algorithm for deprecating each shard is a serial one, so for counters with many shards, decrementing by more than one may take a long time in cases where a single shard does not have enough "count" to process the entire decrement.  A potential performance improvement would be to somehow decrement in parallel, though it's ambiguous if this would yield a speedup in most cases.  For example, imagine a decrement by 10 on a 3-shard counter.  If the first shard has 10 in its count, then loading the other two shards in parallel would be a net-performance loss.

Closing for now.  It's not clear that this would yield a performance increase in the typical case.


Error in tstune init container

I'm using chart version v0.8.2. Using timescale/timescaledb:2.1.0-pg13 there is an error in the tstune init container which prevents the complete stateful set to not start up:
Using postgresql.conf at this path:
/var/run/postgresql/timescaledb.conf

Writing backup to:
/tmp/timescaledb_tune.backup202102281601

Recommendations based on 1.00 GB of available memory and 1 CPUs for PostgreSQL 11
success: all settings tuned, no changes needed
Saving changes to: /var/run/postgresql/timescaledb.conf
sh: numfmt: not found

As a workaround I disabled tstune by setting timescaledbTune.enabled=false

OK, thanks for the clarification.


add securityDefinitions and security config

swagger ui version 3.x works fine with current JSON output. but they drop supporting authentication_*** keys and brings two new option to achieve secure api authentication.

securityDefinitions
security

with this two configuration we can use swagger ui 3 authentication without any problem.

Hey would this work with the version 2.x of swagger ui?

let me check :)

@intuxicated thanks!


Handle security exception thrown when accessing store

In some situations a security exception will be thrown by the browser when trying to access window.localStorage or window.sessionStorage.
One situation is if your vue app is inside an iframe on a page viewed in incognito mode.
When this exception is thrown it prevents the entire vue app from booting.
Here is an example from the developer tools console in the context of the iframe.

@bentleyo thank you


Occasionally AvailabilityRecords don't update in DynamoDB

Looking at the BBC url https://www.bbc.co.uk/sport/articles/ce4wjq42p0yo

First published at 10:41:59 UTC, and recorded missing at 12:57:00 UTC, the dynamoDB record says the url was never found in Google Search by the observatory (there is no found field on the record):

There are two things wrong with this:

The logs show that there was another scan (again, scanned as 'missing') done at 14:34:00 BST, 13:34:00 UTC - but that was not recorded in the DynamoDB table (which shows a last updated date of 12:57:00 UTC):

The result actually is in Google Search (I suppose it's possible it arrived recently, after 13:34:00 UTC):

There does not seem to be anything obviously wrong with the DynamoDB metrics:

The logs show there's now been another scan:

...and mercifully, this did update the DynamoDB record, even if it was only to show that the article was still missing in CSE as of 14:20:01 UTC:

Great detective work on this

@guardian/teamcity


[stdlib] Fix bug in Substring's _persistentContent

Substring's _persistentContent has a fast path that avoids a copy when
the Substring represents the entire outer String. It correctly
detected situations where the wrapped _StringCore was not itself a
slice, but was omitting the extra checks to make sure the Substring's
own range covered the entire String.
Test added.

@swift-ci please test


Feat: Interactive quizzes and challenges

Describe the feature
Include Interactive quizzes on various literary topics to engage users for an engaging platform and learning community.
Add ScreenShots

Record

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

Assigned @Vin205


Authentication Question

What type of headers would I need to set for authentication with this?  Do I just need to pass a users.id?
client.headers = [
    "Authorization": "sometoken"
]

Rails Log:
Started GET "/cable/" [WebSocket] for <IP_ADDRESS> at 2016-04-14 18:47:13 +0000
Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
  ESC[1mESC[36mUser Load (1.3ms)ESC[0m  ESC[1mESC[34mSELECT  "users".* FROM "users" WHERE "users"."id" IS NULL LIMIT $1ESC[0m  [["LIMIT", 1]]
An unauthorized connection attempt was rejected
Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)

XCode Log:
ActionCableClient.TransmitError.NotConnected
Connected!
Disconnected!

This is my preferred approach in using the Authorization header, but it is entirely up to you. ActionCable does not provide any built in ways to authenticate, so you need to create your own.

@danielrhodes Could you provide me with some sample code on the server side.  Right now in my app/channels/application_cable/connection.rb I have this:
def connect
      self.current_user = find_verified_user
      logger.add_tags 'ActionCable', current_user.name
    end

    protected
      def find_verified_user
        if verified_user = User.find_by(id: cookies.signed['user.id'])
          verified_user
        else
          reject_unauthorized_connection
        end
      end

That is for my webapp It look like I need to modify something for this ios app to get the user id?

So first of all, in the above code snippet you are using cookies, but the WebSocket request is not going to contain any cookies.
Although you can use the user ID, I would highly recommend at the very least passing something like a generated token in the Authorization header and not the user ID as it's quite insecure the way you have it.
Nonetheless, here's how you would do it with a user ID:
def connect
      self.current_user = find_verified_user
      logger.add_tags 'ActionCable', current_user.name
end

protected
def find_verified_user
    user_id = request.headers['HTTP_AUTHORIZATION']
    if verified_user = User.find_by(user_id)
       verified_user
    else
       reject_unauthorized_connection
    end
end

For example for how you would handle this in Rails with a token, reference the following:
https://www.codeschool.com/blog/2014/02/03/token-based-authentication-rails/
Thus, I think that would turn into something like:
include ActionController::HttpAuthentication::Token::ControllerMethods

def connect
    self.current_user = find_verified_user
    reject_unauthorized_connection if self.current_user.nil?
end

protected

def find_verified_user
    authenticate_or_request_with_http_token do |token, options|
      User.find_by(auth_token: token)
    end
end

Yes, I agree with you. I currently login on the iOS app using OAUTH2 there i generate a token.  I just need to modify the code abit and I didnt realize I was only using a user id I guess because when I first started implementing this this I missed that, so thanks for pointing that out for me.

@danielrhodes Thanks for your help I am all set!

Sorry to bring back a dead thread, but would I need to do anything extra to my sessioncontroller or applicationcontroller if i wanna use this code in my connection.rb
include ActionController::HttpAuthentication::Token::ControllerMethods
def connect
    self.current_user = find_verified_user
    reject_unauthorized_connection if self.current_user.nil?
end

protected

def find_verified_user
    authenticate_or_request_with_http_token do |token, options|
      User.find_by(auth_token: token)
    end
end

My sessionscontroller is relatively simple right now.
class SessionsController < ApplicationController
  def new
    @disable_nav = true
  end

  def create
    user = User.find_by(email: session_params[:email].downcase)
    respond_to do |format|
      if user && user.authenticate(session_params[:password])
        session[:user_id] = user.id
        cookies.permanent[:user_id] = user.id
        format.html { redirect_to conversations_path }
        format.json { render json: { success: true, user: user }, status: :ok }
      else
        format.html {
          flash[:notice] = 'Incorrect user or password'
          render 'new'
        }
        format.json {
          render json: { success: false, error: 'Incorrect user or password' }, status: :unprocessable_entity
        }
      end
    end
  end

  def destroy
    session.delete(:user_id)
    cookies.delete(:user_id)
    reset_session
    redirect_to root_path
  end

  private

  def session_params
    params.require(:session).permit!
  end
end


Update Stanford iOS course to latest (iOS 11)

Replace an outdated course in the same Stanford series.

Thanks, and welcome to free-programming-books!


Move remaining C linked constants over to libc crate constants

Due to a recent pull request, the rest of the netlink constants used in this library should now be in libc. Move these all over to the libc crate and rip out the C dependency.

Resolved by b8c8130efa67004ba3d696cb0f453f7d862d3beb


wicd: fix wicd-curses with new urwid

See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=894646 — without
this patch, wicd-curses throws an AttributeError on startup. The patch
is a cut-down version of the one added there by Pavel Zhukov.

LGTM ! Merged :+1:


Clicking a link to open a modal that is inside of a modal doesn't do anything

Ideally the linked modal would open and the current modal would close so that a modal stack wasn't created.
Error when I try this setup:
VanillaModal: VanillaModal target must exist on page.

PR #32 fixes this issue!


⚠ GitLab Server has degraded performance

In 790241b, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6951 ms

Resolved: GitLab Server performance has improved in 7d429d3.


how to add quality selector in plyr with hls?

i am looking for quality selector feature in plyr with hls . But, i was not able to kindly guide me through this, any kind of suggestion would be appreciated.
TIA

Duplicate of https://github.com/sampotts/plyr/issues/1118 - Please search next time 👍


QEMU debugging updates

Addressing a few issues:
Fixes#237, Fixes #234, Fixes #217
The biggest issue this PR is addressing is correcting the "debugging QEMU with GDB" section that really didn't work with latest ARM toolchain (on my setup), because of two things:

gdb didn't map the rust libcore functions properly.  For example, after connecting to a QEMU instance, it did not show the current PC to be on the Reset function, but some random method.
gdb didn't step over (next), after breaking at main. It just ran to the end of the program.

The user is now instructed to disable the LDD and use the GNU ARM linker instead, which addresses the issues with the mapping.
And instead of doing a simple, break main  which did not allow the user to step over after hitting the breakpoint, the user is now guided to do a more complicated,
break hello::__cortex_m_rt_main. After hitting that breakpoint, the next and step commands are working as one would expect.
I am no expert in embedded rust, so the proposed solution may not be optimal, but I think they are better than the current instructions provided by the book which are not working at all on my setup. (Windows 10, with latest versions of QEMU, ARM toolchain, Rust)

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @thejpster (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for this PR! Generally your changes look good but I want to be sure of what's going on before merging the recommendation to use GCC LD or that specific breakpoint name. Others from @rust-embedded/cortex-m might have a better idea...


Added coefficients for CIGS and a-Si modules types.

Hi PVLib,
I added coefficients for CIGS and a-Si modules types. I also provided references to document with Spectral Reponses (SRs) of the CIGS and a-Si modules. Reference also includes additional testing and field validation of the model.

Thanks Mitch, the tests look great. Still need to remove the tab from the 'asi' line in the documentation, though. It currently reads...
(tab)(4 spaces)* 'asi' - anonymous amorphous silicon PV module

but needs to read...
[12 spaces]* 'asi' - anonymous amorphous silicon PV module

If you can make this change in the next day or two then we can include it in the 0.4.4 release.

Hi Will. I changed the tab to spaces. Sorry about that. I modified the settings in my text editor, so this should no longer be an issue.
Quick question. For the cdte, monosi, and polysi coefficients fed into test_first_solar_spectral_correction, why don't they perfectly match what I get when running the provided ams and pws inputs?

No worries, I think everyone gets tripped up by tabs vs. spaces in Python at some point.
I think the discrepancy is due to the fact that I implemented the algorithm with a preliminary set of coefficients in commit 28cc9fb, then you updated the coefficients in 58d77ea2 but did not update the expected output. The changes to the coefficients must have been small enough that they did not change the output by more than the test's tolerance allowed. Do you want to update them or should we go ahead and merge this? Either way is fine with me.

Thanks for being patient with my tab issues.
I will update the coefficients. I should commit those by the end of the day.

Updated M values for unit testing of first_solar_spectral_correction. Hopefully things are good to go. Let me know if any more changes need to be made.

Thanks Mitch!


Added Kotlin file

Hello @shreyamalogi ,
This is my contribution to this repository.
Thanks!!

Sorry closing my PR due to following reasons.

Bad repositories will be excluded.
We've seen many repositories that encourage participants to make simple pull requests – such as adding their name to a file – to quickly gain a pull request towards winning. While this may be a learning tool for new contributors, it goes against one of our core values for Hacktoberfest.


Edit Posting Details

Sellers should be able to edit their existing postings

edit posting view accessed through /#/posting/:id/edit

posting details will be viewed through /#/posting/:id/view instead of /#/posting/:id
sellers can access the edit view via the posting details view

The following fields are editable

title
description
category

sellers can save their changes via a "Save Posting" control

if the save operation is successful, they will be returned to the posting details view

sellers can cancel their changes via "Cancel" control

if any part of posting has been modified, a confirmation dialog will be displayed

"Are you sure you want to discard your changes?"
dialog controls include "Save Changes", "Discard Changes", "Return to Editing"

for editable fields there should also be pictures (title and thumbnail) and price range

Editing pictures is a complex features, so it's an entirely different issue #26, I'll have to add in price range field to posting


Your Usage is Wrong？

// Your Usage
import SwapArray from 'swap-array';
var SomeArray = ['thats','cool','dude'];
SwapArray(SomeArray, 0, 2);
// ['dude','thats','cool'];    -------->  expect ['dude','cool','thats'] ???

Oh, you're right.. 👍
But it's just in the README, so the module works well.. :)
Thank you anyway, i will update this tonight


Apply attributes to entire tab, rather than tab's inner title

Thanks for supercharging tabs!
Would it be possible to move the attributes to . workspace-tab-header instead of . workspace-tab-header-inner-title? This would allow us to write rules to style .workspace-tab-header-inner-icon.

Hey! Hmm, I've been playing with this but I don't think it's a great idea for now. We try to keep to the philosophy that users should rarely need to look at specific CSS classes to target when creating their CSS, otherwise maintaining peoples CSS files throughout different versions will be quite hard. Adding it to the superclass looks like this:

ie it will also colour the cross (which IMO is not desirable). And the colour does not seem to apply? But for some reason, it does apply when Obsidian loses focus (not sure what's up with that). I'm sure this can be fixed with good CSS, but it makes the end-user experience much harder. I'm not sure if what you're after is possible with the current setup though.
Alternatively I can apply it also to the inner icon, but I think that creates issues with double added icons.


Add PrismaTypesFromClient utility type

Solves: https://github.com/hayes/pothos/discussions/1193
PrismaTypesFromClient utility type that infers types from PrismaClient.
Example:
import SchemaBuilder from "@pothos/core"
import type { PrismaTypesFromClient } from "@pothos/prisma-plugin"
import { BigNumberExtension } from "~/lib/prisma-extensions"

const db = new PrismaClient().$extend(BigNumberExtension)

export const builder = new SchemaBuilder<{
  PrismaTypes: PrismaTypesFromClient<typeof db>
}>()

This great, thanks for adding this, I'll get it out as part of 4.0!


[BUG] The scheduling section in the page setting is appearing at the last.

Describe the bug
The scheduling section in the page setting is appearing at the last.
To Reproduce
Steps to reproduce the behavior:

Deploy longhorn master - 10/19/2020
Go to the setting page.
The scheduling section in the page setting is appearing at the last.

Expected behavior
The danger zone section should appear at the last of the page.

Verified with longhorn UI - b2b58d0
Validation - Pass


Move GeoRegion endpoint to AppSetting

Can we make the internal-applens flag configurable in the app settings as well?


"aroma" missing

word is not in your list

😄  that's a bit of a spoiler ... maybe wait till the end of the day to open an issue like this. 💭
(but thanks for opening it. seems like we have a few words to add ...)

😄 that's a bit of a spoiler ... maybe wait till the end of the day to open an issue like this.

aha yeah I didn't think of that!
I have edited the issue to make it not immediately obvious!

Should I try to work on this?

Aroma is present in the list. I confirmed by running:
grep -i "^aroma$" words.txt


Fix Tagging.find_all_by_tag_id call

Address 1 issue in https://github.com/ManageIQ/manageiq/issues/6754

@Fryguy @matthewd please review


Update question.json

Fixes Issue
This PR fixes the following issues:
#example

Changes proposed
Here comes all the changes proposed through this PR

Check List (Check all the boxes which are applicable)

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

Screenshots
Add all the screenshots which support your changes

New format of data is being introduced today. So you will have to make PR with that in mind. So I will be closing this issue now.


setBody() + addPart() with embedded images doesn't correctly add multipart/alternative entity

The following code:
@@@ php
 setSubject('See my image');
$msg -> setFrom(array('swift@example.com'));
$msg -><EMAIL_ADDRESS>Client'));

$msg -> setBody("This is the plain text you'll see when I try and embed an image.");

//Image to embed
$cid = $msg->embed(Swift_Image::fromPath('logo.png'));
$img = '';

// HTML body
$msg -> addPart(
    "See my logo" .
    "Outlook works, Thunderbird will fall back to plain text and show the " .
    "HTML body (as Part 1.2) and the image as attachments" .
    $img,

```
'text/html'
```

);

//Transport and Mailer
$transport = Swift_MailTransport::newInstance();
$mailer = Swift_Mailer::newInstance($transport);

if($mailer->send($msg)) {
    echo "Message Sent";
}
@@@

Creates a structure similar to the following:

@@@
Content-Type: multipart/related; boundary="relbound"

--relbound
Content-Type: text/plain

Plain text here

--relbound
Content-Type: text/html

HTML here

--relbound
Content-Type: image/png

--relbound--
@@@

There should be a multipart/alternative entity wrapping this:

@@@
Content-Type: multipart/alternative; boundary="altbound"

--altbound
Content-Type: text/plain

Plain text here

--altbound
Content-Type: multipart/related; boundary="relbound"

--relbound
Content-Type: text/html

HTML here

--relbound
Content-Type: image/png

--relbound--

--altbound--
@@@

Probably a simple fix (I seem to remember fixing a similar bug which should have test coverage now).  Hopefully there's no conflict of logic between the two.

Original creation date: 2009-03-23T09:06:36Z
Original reporter: Ben
Original ticket: http://swiftmailer.lighthouseapp.com/projects/21527/tickets/77

It's almost 2017 and this bug still exist.
Is there any possibility to fix it at last?

Doesn't work in 2016 ....
I can't use embedded images and plain text together ....

@EdvinasBilius and @mansoff  does it work with the workaround in #184 ?
May be this should be closed as a duplicate of #184?

@TerjeBr, no this is not working. Check in Thunderbird and use different text messages for HTML, PLAIN versions with embedded imges

Thunderbird has some known issues. Look at the email source, and see if the error is with thunderbird or the email that is being sent out.

@TerjeBr it seems you're right, it is thunderbirds problem, other mail clients which can show plain text version of email (not source, but the actual message) works just fine.

I'm closing this issue as it's going to be fixed by Symfony Mailer/Mime, which will replace Swiftmailer eventually.


Resolves #848: Fixing module resolution with nonstandard filenames

@slawekjaranowski
Please review.

A very valid remark, applied the necessary fix. Thanks again.

Forgot to check the site goal 🤦


FCREPO-3752: Altering the external content URL does not update the binary metadata's last-modified date

JIRA Ticket: https://fedora-repository.atlassian.net/browse/FCREPO-3752
What does this Pull Request do?
This updates the metadata handling for server managed properties to be applied to the binary headers rather than the binary description. This allows for the ManagedPropertiesService to resolve all managed properties from the binary.
Changes

Create a new operation for updating only the binary headers
Create a new persister for updating the binary headers
When updating a description, create two operations for managed and unmanaged properties
Resolve managed properties from the Binary when possible

How should this be tested?
There are two things to test here - the binary metadata being pulled from the correct source and that updates to server managed properties are done to the correct file.
Binary Metadata

Start fedora
Create a binarycurl -X PUT -H "Content-Type: text/plain" --data "somedata" -H "Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel=\"type\"" --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/test1

Get the metadatacurl --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/binary/fcr:metadata

Do a second put over top of the binarycurl -X PUT -H "Content-Type: text/plain" --data "somemoredata" -H "Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel=\"type\"" --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/test1

Check that the metadata is updated properly

Server Managed Properties

Start fedora with relaxed properties mode
Create a binarycurl -X PUT -H "Content-Type: text/plain" --data "somedata" -H "Link: <http://www.w3.org/ns/ldp#NonRDFSource>; rel=\"type\"" --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/binary

Get the metadata for the binary and see that it matches what is the in the binary headerscurl --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/binary/fcr:metadata

Update the server managed properties on the binarycurl -X PATCH --data "PREFIX fedora: <http://fedora.info/definitions/v4/repository#>
INSERT {
    <> fedora:createdDate "2021-08-26T15:04:43.517Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
    fedora:lastModified "2021-08-26T15:04:43.517Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
}
WHERE  { }" -H "Content-Type: application/sparql-update" --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/descupdate/fcr:metadata

Get the metadata for the binary and see that it matches the update + what is the in the v2 binary headerscurl --user fedoraAdmin:fedoraAdmin http://localhost:8080/rest/binary/fcr:metadata

Interested parties
@fcrepo/committers

@pwinckles Thanks for the review, I just got to it this morning. I added an integration test for checking the LastModified of the binary description after an update to a binary. The FedoraRelaxedLdpIT has one for server managed predicates so I opted not to add another for that.


Tiny changes to signature stuff

Normally I wouldn't PR this but I want to make sure I'm saying true things in the documentation :) I also fixed two small bugs

excellent, thank you very much for this! I have made a few little suggestions; other than that, it's good to go!

Okay cool, I've fixed them!

great, thanks!!


Update Publishing images to Docker Hub

Tool name
Docs
Tool license
Public
Add or update?

[ ] Add
[X] Update

Desired version
As per test case or later
Approximate size
No response
Brief description of tool
Example YAML from link needs updating:
https://docs.github.com/en/actions/publishing-packages/publishing-docker-images#publishing-images-to-docker-hub
Annotation from post successful action:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/build-push-action@3b5e8027fcad23fda98b2e3ac259d8d67585f671. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

### URL for tool's homepage

https://docs.github.com/en/actions/publishing-packages/publishing-docker-images#publishing-images-to-docker-hub

### Provide a basic test case to validate the tool's functionality.

```bash
# This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support
# documentation.

# GitHub recommends pinning actions to a commit SHA.
# To get a newer version, you will need to update the SHA.
# You can also reference a tag or branch, but the action may change without warning.

name: Publish Docker image

on:
  push:
    branches:
      - master

jobs:
  push_to_registry:
    name: Push Docker image to Docker Hub
    runs-on: ubuntu-latest
    permissions:
      packages: write
      contents: read
      attestations: write
      id-token: write
    steps:
      - name: Check out the repo
        uses: actions/checkout@v4

      - name: Log in to Docker Hub
        uses: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}

      - name: Extract metadata (tags, labels) for Docker
        id: meta
        uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
        with:
          images: rustynox/linode-deploy

      - name: Build and push Docker image
        id: push
        uses: docker/build-push-action@3b5e8027fcad23fda98b2e3ac259d8d67585f671
        with:
          context: .
          file: ./Dockerfile
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}

Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Hello @noxidsoft, please report to the GitHub support .
If you have any other questions feel free to reach us.


Quota management

Merge quota management functionality

Testing this PR to merge quota management into the base. Tests focus was on testing existing features with the quota management feature turned off and looking for regressions if any.

All scale tests and manual tests pass.
Two test cases that are failing in Travis are mostly due to Travis VM resource jitter, these tests need to be modified to not rely on VM resources down to the millicores to pass. On local env, one out of the two of the test passed, and one fails due to a mismatch in resource assignment.

I think we can merge this PR into the main with the quota management feature turned off.


Add config_path param for unicorn resource

Can this be merged ?

@coderanger can this be merged please ?
You can see here the config file being passed as an argument to the cli unicorn command: https://unicorn.bogomips.org/unicorn_1.html
I cannot use unicorn (and therefor this cookbook) without passing it the config file.

+1 I'm running into the same issue.

As a reminder: you can always make subclasses. No one should be blocked on this, just subclass my unicorn resource and make whatever changes you need. You can also use the poise_service_options helper to more explicitly override the command line for the generated service. +1s don't magically give me more time, and are not needed.

@coderanger as I asked before here and/or in the halite repo - since you're not using the normal/regular chef way of writing cookbooks, it's not that easy to make changes.
I've asked before - can you explain how will the subclassing work ? Don't I need Berkshelf to use the halite extension ?
If so - as I wrote in the halite repo - after following all the instructions and adding the `extension 'halite' to the berkshelf file, I'm getting an exception about the extension.

I apologize @coderanger if I came across as impatient. I appreciate the work you have done on these cookbooks. I wasn't able to figure out how the subclassing would work, but your poise_service_options clue helped, so thank you.
@dorongutman, this is what I ended up doing to get it to work:
  unicorn
  poise_service_options '/srv/myapp' do
    command '/opt/ruby_build/builds/2.3/bin/ruby /opt/ruby_build/builds/2.3/bin/bundle exec /opt/ruby_build/builds/2.3/bin/ruby /srv/myapp/vendor/bundle/ruby/2.3.0/bin/unicorn -c config/unicorn.rb --port 8000 /srv/myapp/config.ru'
  end

Only semi-related but I wrote up a full example of using subclassing to fix this kind of issue without waiting for me https://gist.github.com/coderanger/962627150d3f3bd17bd2c8014260cee9


Time support in Expressions

This adds proper support for time in both the Python and OSL expression engines (previously we only supported the current frame in python, and nothing in OSL).

Does OSL have frame and framesPerSecond as well, or just time?

As a native global variable, OSL just has time, but you can still access frame and frames per second via context( "frame" ) and context( "framesPerSecond" ).


Added requestConnectionPriority methods.

I've tried to implement requestConnectionPriority support.
Thank you for an awesome library.

Hello @svangsgaard
Thank you for your pull request - this is a great idea! Unfortunately I cannot merge it yet, there are few things that need to be clarified:

Setting the connection priority may fail and your code does not inform the user about the result
Have you tested wether requesting connection priority may be called at any time or does it have to be called when no bluetooth operation is executed at that time? If it is the case we would need to make the request asynchronous and create a RxBleRadioOperationRequestConnectionPriority and related tests
It may be also worth to discuss if a High Priority or Low Priority connection would have a lifecycle similar to normal connection and / or notifications. I.E. when user will request high priority connection it will be returned in Observable<RxBleConnectionHighPriority> which would have almost the same interface as RxBleConnection but would not be able to change the priority. When the user would unsubscribe from the Observable<RxBleConnectionHighPriority> the priority would be brought back to balanced state. What is your use-case?
Your commit introduces formatting changes in JavaDoc which are not related to the topic and should be reverted.

After all I am looking forward to have this feature after we will discuss and implement it in a proper way.
Best Regards

Hi @dariuszseweryn
You're right. I need to change those things in the code.
I have thought about how to implement it, maybe a better solution is to provide an extra parameter to setupNotification aka setupNotification(MY_UUID, CONNECTION_PRIORITY_HIGH), then the priority is automatically reverted when the notification is released.
That will solve my current problem. What do you think?
Regards.

I don't think that binding connection priority to setting up notifications is a good idea. I can imagine at least a situation where user would like to transmit data to the peripheral at increased rate.
Could you describe your use case in greater detail? Does your peripheral transmit a lot of data via notifications to the phone?
I am on the fence if introducing state to the connection via setting the connection priority is a good idea. Maybe it would be better to emit RxBleConnectionHighPriority but what if at the same time the user would also request low priority? Then an error should be emitted.
Either way - if you could confirm the point number 2 from my previous post - it would be clear if we need a separate operation.

@svangsgaard Any hints you can provide?

Now implemented. https://github.com/Polidea/RxAndroidBle/issues/111


[BUG]: Fix & make the current CI/CD pipeline more robust

What happened?
Currently the CI/CD pipeline isn't only inefficient but it doesn't work as expected either. Following are the intended behaviour but for whatever reason it doesn't work:

Deploy to Netlify using GitHub Actions (causes an authentication issue even the auth tokens exists)
Make a comment on the PR with a preview URL

The expected behaviour is basically to deploy the static contents to Netlify after they've been generated on the GitHub Actions environment. Once the deployment is successful, comment on the PR with a preview URL.
Relevant log output
See https://github.com/developersIndia/website/runs/5703328348?check_suite_focus=true
Code of Conduct

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

Here's an official blog from GitHub which might share a clue towards fixing this issue; GitHub Actions improvements for fork and pull request workflows


deploy to training.plone.org

@svx how does the deployment process work?
is it automatic?
what's the schedule?

Not yet, I had no time to work on this, it is still on my list, for the moment just send a pull request and I push it to the server.

Thanks, @svx, good to know!
@pbauer, FYI


Bitsy-Bye / ProDOS 2.4.0: Occasional crash during boot

Sometimes when booting, after the ProDOS title screen is shown, there is a crash into the monitor around 0x2000.
Interestingly, if you CTRL-B, then run PR#6, the software boots as expected.
It also appears this crash only occurs if Auto ROM loads it. Resetting before ProDOS has a chance to load and then loading with PR#6 seems to work. (Not fully tested yet.)

Related to #43. Doing a quick fix allows Bitsey-bye to work correctly. Also, can now change drives without crash happening.