Can't create group 'Loxone Switches'

Which Model do you use from loxone? Miniserver? Gen1 or Gen2?
gen2
Which software version does your loxone use?
<IP_ADDRESS>
How did you install HomeAssistant? Over Hassio oder manual install?
home-assistant docker
Which Version do you use of HomeAssistant?
[2022.6]
Describe the bug
A clear and concise description of what the bug is.
error during the startup:
2022-06-12 20:39:10 ERROR (MainThread) [custom_components.loxone] Can't create group 'Loxone Analog Sensors' with error: 'group_registry'
2022-06-12 20:39:10 ERROR (MainThread) [custom_components.loxone] Can't create group 'Loxone Digital Sensors' with error: 'group_registry'
2022-06-12 20:39:10 ERROR (MainThread) [custom_components.loxone] Can't create group 'Loxone Switches' with error: 'group_registry'
2022-06-12 20:39:10 ERROR (MainThread) [custom_components.loxone] Can't create group 'Loxone Covers' with error: 'group_registry'
2022-06-12 20:39:10 ERROR (MainThread) [custom_components.loxone] Can't create group 'Loxone Lights' with error: 'group_registry'

my lights are missing (all dimmers/scenes), ventilation is missing.
I'd love to add them manually including scripts, e.g. setting ventilation to "2.0" or "3.0" but not sure what kind of command to issue via websocket event

e.g. this is the ventilation config
            "name": "Ventilatie",
            "type": "Radio",
            "uuidAction": "0e9a7357-03a5-d1b8-ffff58dbabe525cb",
            "room": "0c4bc0a8-0270-03ba-ffff58dbabe525cb",
            "cat": "0c4bc0a8-0261-02fc-ffff58dbabe525cb",
            "defaultRating": 0,
            "isFavorite": false,
            "isSecured": false,
            "defaultIcon": null,
            "details": {
                "jLockable": true,
                "allOff": "",
                "outputs": {
                    "1": "Stand 1",
                    "2": "Stand 2",
                    "3": "Stand 3"
                }
            },
            "states": {
                "jLocked": "8e9a7357-03a5-d1aa-ffff04c72879d5c2",
                "activeOutput": "0e9a7357-03a5-d1b7-ffff04c72879d5c2"
            }
        },```

1 part of lights that are not appearing in HA at all
"0e9267b6-0092-d9bf-ffff58dbabe525cb": {
            "name": "Lichtscenes sl. kamer 2",
            "type": "LightController",
            "uuidAction": "0e9267b6-0092-d9bf-ffff58dbabe525cb",
            "room": "0c4bc0a8-0275-03e8-ffff58dbabe525cb",
            "cat": "0c4bc0a8-025c-02d8-ffff58dbabe525cb",
            "defaultRating": 0,
            "isFavorite": false,
            "isSecured": false,
            "details": {
                "jLockable": false
            },
            "states": {
                "activeScene": "0e9267b6-0092-d9bc-ffff2b14af86fbdf",
                "sceneList": "100df4b0-0328-1e93-ffff58dbabe525cb"
            },
            "subControls": {
                "0e9267b6-0092-d9bf-ffff58dbabe525cb/AI1": {
                    "name": "Spots raam",
                    "type": "Dimmer",
                    "uuidAction": "0e9267b6-0092-d9bf-ffff58dbabe525cb/AI1",
                    "defaultRating": 0,
                    "isFavorite": false,
                    "isSecured": false,
                    "states": {
                        "position": "0e9267b6-0092-d9b0-ffff2b14af86fbdf",
                        "min": "0e9267b6-0092-d9a4-ffff2b14af86fbdf",
                        "max": "0e9267b6-0092-d9a5-ffff2b14af86fbdf",
                        "step": "0e9267b6-0092-d9a2-ffff2b14af86fbdf"
                    }
                },
                "0e9267b6-0092-d9bf-ffff58dbabe525cb/AI2": {
                    "name": "Lamp sl. kamer 2",
                    "type": "Switch",
                    "uuidAction": "0e9267b6-0092-d9bf-ffff58dbabe525cb/AI2",
                    "defaultRating": 0,
                    "isFavorite": false,
                    "isSecured": false,
                    "states": {
                        "active": "0e9267b6-0092-d9b1-ffff2b14af86fbdf"
                    }
                }
            }
        },

Radio and light controllers are not supported.
And because of the start up errors which version of pyloxone do you use? If you not use the latest version please update.

thank you for your response.
It is the latest version of pyloxone.
do you think there will be radio controllers supported in future? do you have any hints how to send a manual command maybe? I was sending 2.0 to my ventilation uuid via websocket event but I got 404

I would first get rid of the error messages for the group creation. It is strange because I get no errors. I know there where a issue in the past but it should already fixed.
Because of the radio button: how can I configure a radio button in loxone? What device is it? I maybe I can add it and have a look how your command should look to switch between the states.

alright, when I enabled debug yesterday and tried to change modes of the ventilation, I could actually see it in the pyloxone debug output, so, I am going to get that log out and put it here in the coming days (can't reach it remotely yet).
in fact I see the same for lights but perhaps let's focus on one thing first.
do you think I can provide anything for you to dig into the errors? i tried increasing the generation from 3s to 15s but it didn't affect anything, the error was still there. the debug logging didn't provide anything extra I could think of relevance

Maybe I try it today an come back to you. How can I add  radio buttons?

if you mean in loxone, I think it's this one: https://www.loxone.com/enen/kb/radio-buttons/
i'm really new to this thing and I didn't configure it myself. trying to put home assistant in front of it so that I don't even need to touch this beast 😆

@huliz Regarding the radio buttons try this:

The uuid is your action uuid of your radio entity. And in your example 1 means "Stand 1" and 2 "Stand 2" etc.
And for "all off" you must sent a reset. Hope this helps.
Did you already converted the light controller to light controllerV2 ?

oh man, it worked, I saw 2.0 in the logs yesterday and it didn't occur to me to try just 2 or 3, was trying 2.0 in various ways. that will be easy for me to create buttons on HA for these.
for the light controllerV2 - is it something I can do myself? I had an impression that it is a hardware thing or is it pure configuration via loxone config?

ok, I found the way to convert but I have a warning about I5 inputs being not supported, I think I will need a Loxone support to help with that.
is there anything I can provide you with regards those errors? do you think they are because of light controller v1?
I also have heating connected that is not appearing on HA. I assume it is not yet supported
thank you for your help, amazing

@huliz thanks for the coffee.
The errors are only for the group creation. I think all devices which are supported are created although this error occurs. I do not know why. Do you really have the latest pyloxone? Or maybe it is a gen2 thing. I have only a gen1.
Because of the light controller v1: the controller v2 is more powerful but also some things are not compatible. So it could be that some things are not working properly if you convert it. But with this I can not help you. You can control it also with a websocket command if you have not to many.
As I started with this binding the light controller v1 was already deprecated. Maybe I can look to integrate it if I have time.

thank you, no worries, I will play around with websocket commands for the lights.

@huliz I tried to add a lightcontroller v1 to my project but I can not find it. I only can add a v2 controller. Can you tell me how I add a v1 to my project. Maybe I must set something to a v2 to behave like a v1?

FYI, I managed to convert some of the light controllers to V2, now the scenes and switches are generated. Unfortunately I'll have to play around a bit longer with the 2 other rooms, it looks like there are some KNX components configured as inputs that prevent migration to V2. Almost there :-)
the number of group errors is still the same at the startup. I imagine it might be related to the KNX analog inputs

Was there any solution for this error: ?
custom_components.loxone] Can't create group 'Loxone Group' with error: 'group_registry'
I see this in my logs with current pyloxone and Ha version with Gen1 miniserver

@rolandpj no. We couldn't figure out what causes the error. If you see all entities it should not a big problem for the functionality for your system.

Indeed, after one year it's still there and there is nothing wrong with the
integration apart from this startup error message.
On Mon, Nov 13, 2023 at 7:12 AM Joachim D. @.***> wrote:

@rolandpj https://github.com/rolandpj no. We couldn't figure out what
causes the error. If you see all entities it should not a big problem for
the functionality for your system.
—
Reply to this email directly, view it on GitHub
https://github.com/JoDehli/PyLoxone/issues/120#issuecomment-1807530530,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYMU6CAYMRQH4POYDLGKVDYEG23TAVCNFSM5YSEYKDKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQG42TGMBVGMYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Was there any solution for this error: ?
custom_components.loxone] Can't create group 'Loxone Group' with error: 'group_registry'
I see this in my logs with current pyloxone and Ha version with Gen1 miniserver

Hi. I had the same problem. Tried everything to make it running. Only comment out affected lines in custom_components\loxone_init_.py file helped. I'm newbee in HA and do not know impact of this modification to the system. But it works ;-)

@radosek21 @huliz I can catch the error so that the error message is not thrown but I would personally know what the error causes. I mean which devices. I do never get this error but I have the smallest system of all users of pyloxone I think.


Draft to Show Break From 0.68 Upgrade

Draft to Show Break From 0.68 Upgrade

Great thanks @JunielKatarn!

Closing 0.68 now validated.


DF-1607: Processor update and tests

This PR addresses DF-1607 by fixing the content processors to match the WordPress API output. It also adds the basis for unit tests for the content processors along with some basic tests for the changes made in this PR. The unit tests are very, very, very far from complete, and only test the changes this PR makes, but they're a start.
Additions

Test runner and unit tests for content processors

Changes

Changed wordpress_orgmember_processor.py, wordpress_post_processor.py, and wordpress_view_processor.py to match WordPress API output for custom fields.

Testing
From the _tests/processor_tests directory,

Run pip install -r requirements.txt (installs Mock if it is not already installed the current virtualenv).
Run python test_processors.py

It would also probably be a good idea to run a Sheer reindex with these processors. From the cfgov-refresh root:

sheer index --reindex

And then browse to relevant pages on the site. These are:

http://localhost:7000/the-bureau/bureau-structure/ (Look for single and multiple titles under names)
http://localhost:7000/blog/ (The hero should display as normal)
http://localhost:7000/newsroom/ (Look for links in the "Featured Topic")

Review

@dpford
@kurtw
@jimmynotjim
@anselmbradford
@sebworks

Notes
Prior to this change, the cfpb_hero type had only one related_post being indexed in Elasticsearch by the content processor, meaning any additional related_post values were being lost in indexing. This PR changes that, so that all possible related_post values are being indexed.
To preserve existing behavior, _includes/hero.html is now selecting the first related_post from the related_posts list. However, given that heros can potentially have multiple related posts, it might be worth reconsidering the way the hero macros handle related posts.

This is very exciting! :heart_eyes:

Everything looks good to me!  Great job with the new tests

LGTM

Thanks. Changes from flapjack merged.

:+1:


Set ownReference for clusterOperation releated with cluster

What type of PR is this?

/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes # https://github.com/kubean-io/kubean/issues/890
Special notes for your reviewer:

/lgtm

/lgtm


charged-ieee: Allow passing arbitrary content as author email

The README for charged-ieee states that "All keys accept content." However, the email key currently only accepts strings. With this PR, I made it possible to pass any content. If a string is specified, a mailto: link is created. Otherwise, the content is used as is.

I am not sure in which case you may want to pass arbitrary content here? Do you have a real world use case for that? I feel like it would be better to fix the documentation than changing the code in that case.

It's just more permissive, but I understand if you prefer to disallow niche edge-cases.
I happen to have a weird use-case for this: I have a document that I want to make available publicly without leaking email adresses. The easiest way to do it without changing the layout compared to the version with the email adresses is to simply replace the email adresses with empty content (or hide them) based on some condition.

Okay that makes sense.


Investigate adding PreferredHologramPerspective option for HoloLens 2

MRC on HoloLens 2 has a new option to select the preferred hologram perspective : PreferredHologramPerspective. This allows changing the perspective from the screen point of view to the PV camera point of view, for better alignment with the camera video. This is currently left by default to 0 (screen; the docs linked has a bug) when configuring the MRC video effect inside WebRTC UWP, but could be exposed to the user to benefit from this quality improvement.

Hi Jerome.  It just so happens I was experimenting with this myself today (after a few weeks of preparation for handling multiple holographic cameras correctly and ensuring I can use the PV camera for MRC in a sample app).  It is currently behaving differently than when I begin a MediaCapture session with MRC in a sample app, so there may be additional details to tend to.  Optimistically assuming I will get it figured out, I can post any non-obvious details here for reference.
If this property was added to the API as a configuration option we would certainly use it.  In the meantime (again assuming I figure it out) we will go with a custom build of v1.0.3 to enable it.
For the record, my starting point for a simple test was to add the property with a default value of 1 (PV camera) to external/webrtc-uwp-sdk/webrtc/xplatform/webrtc-apis/windows/wrapper/impl_webrtc_MRCVideoEffectDefinition.{cpp,h} and to use a version of our app that explicitly opts-in to the PV view configuration as described in the doc you reference.  I am currently seeing two new holographic cameras being added where I expect only one, and the rendering result is incorrectly scaled -- likely due to a mix up in render target dimensions -- but I suspect that is caused by errors on my part.

Thanks for the details @kspark-scott. Yes I was talking with folks internally about your use case, that's no coincidence 😉 It seems this is not very difficult to expose, however if there's no blocker we'll wait for now, as we are trying to undock from WebRTC UWP and consume the Google repository directly, which would make use of some refactored UWP code from WinRTC, so the change would likely have to be done a second time if we do it now in WebRTC UWP (which we're trying to deprecate). However if you or anyone else has a blocker on this feature we can consider reprioritizing.

@djee-ms the experiments went well and hard-coding PreferredHologramPerspective=1 in the video effect definition was sufficient. The other problems I alluded to were indeed my own.
While we do want to get back to an unmodified version of mr-webrtc eventually, I think there is no urgency now.  I see no great benefit in doing the work twice to make this property configurable, so we are happy to wait for the WinRTC-derived version.


Support reading workspace config from pnpm-workspace.yaml

First of all, knip is an amazing tool and I can see this becoming really useful!
We use https://pnpm.io/ as package manager and it took me a while to go through all error messages when executing knip until I was able to make it work. In the end, I had to copy over our workspaces config from  pnpm-workspace.yaml to package.json and update the format.
It would be cool to support pnpm out of the box, or at least put a note into the readme for now, so these users are not excluded and can get started with knip.

Sorry you had to go through this. I'm happy to look into supporting pnpm-workspace.yaml as well. Do you happen to have such a repo or know about one?

I found this through a quick search online: https://github.com/DavidWells/pnpm-workspaces-example
Note that the lockfile format in this project is outdated though, not sure if it matters. I assume a simple pnpm i with the latest version of the package manager would update it accordingly.

Thanks! Got it.

and it took me a while to go through all error messages when executing knip until I was able to make it work

What kind of errors do you mean here? Anything I could use to reproduce issues?

Hmm, I think the issue was all on my side actually, my bad.
What I did was copy over the knip.json content from https://github.com/webpro/knip#usage and only further realized that there is a guide for monorepos further down below.
So although it's clear that it can't work then, it should display a useful error message. This is what I got repeatedly:
$ npx knip
  92% of files processed (195 of 210)
   95 Unlisted or unresolved dependencies

Processing: libs/shared/ui/src/lib/MultiSelectWithAdd/MultiSelectWithAdd.spec.tsx
file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:123
                if (referencedDependencies?.has(dependency))
                ^

RangeError: Maximum call stack size exceeded
    at isUnreferencedDependency (file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:123:17)
    at file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:70
    at Array.find (<anonymous>)
    at isUnreferencedDependency (file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:46)
    at file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:70
    at Array.find (<anonymous>)
    at isUnreferencedDependency (file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:46)
    at file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:70
    at Array.find (<anonymous>)
    at isUnreferencedDependency (file:///home/user/Webdevelopment/Freelancing/org/repo/node_modules/.pnpm/knip@1.7.0/node_modules/knip/dist/dependency-deputy.js:138:46)

Node.js v18.12.1

I have released v1.8.0 that reads pnpm-workspace.yaml (and updates the docs). Note that only workspaces in the Knip config are part of the analysis.
Without any configuration, this is the default: https://github.com/webpro/knip/blob/06220bc336e912cda3f9589004f97280b4b7e1e9/src/constants.ts#L8-L13
When the default project glob is applied that might be the issue causing the RangeError , although 210 files isn't that much. After configuring the workspace packages in knip.json, do you still see this error?

Thanks for the update, it works really well now without any config for us!
I don't see the error at all anymore, it was just due to custom bad config. So the only thing you can do is provide a custom error message instead of it running into out of range.

Thanks for reporting back.

it works really well now without any config for us!

Just saying, Knip does not take workspaces into account if there is no workspaces: {} in a knip.json file, so it analyzes the codebase as a single workspace/package.


Install epel-release on CentOS

This allows opam projects to depend on packages in the extra packages repository (e.g. capnproto).

Mh, I'm not sure this should be there. Opam already has a special case for installing epel-release: https://github.com/ocaml/opam-depext/blob/master/depext.ml#L216. Why is this needed?

Ah thanks! I've made a PR to use that instead: https://github.com/ocaml/opam-repository/pull/16447


AttributeError: 'float' object has no attribute 'replace'

Lately I've started seeing this error every 15 minutes:
2023-01-15 18:46:36.922 ERROR (MainThread) [custom_components.watchman.coordinator] Unexpected error fetching Watchman data: 'float' object has no attribute 'replace'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 225, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/watchman/coordinator.py", line 31, in _async_update_data
    entities_missing = check_entitites(self.hass)
  File "/config/custom_components/watchman/utils.py", line 221, in check_entitites
    state, _ = get_entity_state(hass, entry)
  File "/config/custom_components/watchman/utils.py", line 185, in get_entity_state
    state = "missing" if not entity else entity.state.replace("unavailable", "unavail")
AttributeError: 'float' object has no attribute 'replace'

Any suggestions to what the problem is? This is HASS 2023.1.4

Hi @aherbjornsen, it looks weird. I've just tested it against 2021.2 and all tests passed successfully. Nevertheless, I've added some additional checks for this piece of code, now it should write error message to the HA log instead of crashing.
Could you please install last version from the main branch and check HA logs for Watchman errors?
In order to do this:

Go to HACS->Integrations, click Watchman, three dots menu on the right and select Redownload.
The dialog appears with the version selector, you have to choose "main", then click "Download"
Restart HA to apply new version of Watchman

In order to check if new version was installed, go to Settings->Devices&Services and click "1 service" link under Watchman tile. You should see version 0.6.1 under Service Info.
Then, please, check HA logs and paste here the error message from Watchman for further investigations. Thanks!

Thanks for the detailed response.
I've tried to update Watchman from HACS, as per your instructions, but is unable to see a higher version than 0.6.0. I even checked for beta versions, but I seem to be stuck with 0.6.0.

This is correct, 0.6.1 will not be shown in the HACS versions list. You should select "main" in the list of versions as per attached screenshot:

Sorry, I missed the "main" part.
Redownloaded once again and now I see 0.6.1 and the error messages seems to have gone.
Thanks for your patience and fast response.

@aherbjornsen Could you please check HA logs now and post here the relevant error message(s) from Watchman (Unable to get state for...)? I hope it helps to find out the reason of this error.

The messages I saw before the upgrade has gone. Then I saw them at regular 15 minute intervals.
After the upgrade I see two errors:
2023-01-17 11:51:25.271 ERROR (MainThread) [custom_components.watchman.utils] Unable to get state for sensor.nordpool_kwh_oslo_nok_3_095_025: 'float' object has no attribute 'replace'. Type: <class 'float'>
2023-01-17 11:52:32.999 ERROR (MainThread) [custom_components.watchman.utils] Unable to get state for sensor.nordpool_kwh_oslo_nok_3_095_025: 'float' object has no attribute 'replace'. Type: <class 'float'>

This a sensor created by the Nordpool custom integration:
https://github.com/custom-components/nordpool/releases

Thanks, this confirms my speculation about a custom integration which, probably, does not follow HA development guidelines. I'll check it. So far (in 0.6.1) these two sensors will be present in your Watchman report with error state. In the next Watchman release these sensors will be processed as a regular sensor with no errors.


Bump version to 1.5.1 and 0.22.1 for release

LGTM

Codecov Report

Merging #347 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #347   +/-   ##
=========================================
  Coverage     76.66%   76.66%
  Complexity      478      478
=========================================
  Files           105      105
  Lines          2503     2503
  Branches        185      185
=========================================
  Hits           1919     1919
  Misses          513      513
  Partials         71       71

Continue to review full report at Codecov.

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


#159 Adds Console Component for rendering of output

Uses console-feed for rendering of output and allows searching, filtering and ordering of output. Resolves #159
TODO:

[x] Linting/formatting
[x] Reset output on integration change and add clear button
[x] Resolve ordering issue
[x] Resolve resubmission of warning messages upon ordering change

Looks cool! Ping me when you want me to review.

@corradio should now be ready for review. Could do further improvements, e.g. storing selected filter categories in LocalStorage? Or maybe later once requirements of #160 is more clear?

I'll review asap

is it possible to sort ASC by default and show all output by default (i.e. warn and debug by default?)

is it possible to sort ASC by default and show all output by default (i.e. warn and debug by default?)

Like so? In the ASC case however, then probably it should always scroll to bottom, so the whole console output should be wrapped in a scrollable container?

This looks good for now! I suggest we merge and then we can make additional UX changes later on.


How to delete the oldest entry in the box while using a custom key with put()

I have a box where I save a custom object, and I use put with a key. The problem is that I want to make the box max limit as 50, for example, when I add one, I want the oldest one to be deleted after it reaches 50. Is there a way to this? I was able to do this when I was saving with add with the incremental key, but I had to change use put and a key I generate.
/// Save past affirmations until 50 keys, then delete the first
  Future<void> savePastAffirmations(int index) async {
    var affirmationBox = Hive.box<Affirmation>(HiveBoxKey.pastAffirmations);
    final Affirmation affirmation = todayAffirmations[index];

    if (affirmationBox.containsKey(affirmation.key)) return;

    if (affirmationBox.length > 50) {
      //TODO delete oldest entry
    }

    if (!affirmationBox.containsKey(todayAffirmations.first.key)) {
      await affirmationBox.put(
          todayAffirmations.first.key, todayAffirmations.first);
    }

    await affirmationBox.put(affirmation.key, affirmation);

    print("Past affirmations: ${affirmationBox.values}");
  }

I have a similar situation, I suggest instead of using an Affirmation hivebox such as Hive.box<Affirmation>, use a list or a map of Affirmation hive box such ad Hive.box<List> or Hive.box<Map<String, Affirmation>> and then use only one key to fetch the whole list/map, like "affirmations", then you can do whatever you want with this list and save it again in its new state. I believe in Map you can iterate over the entries but I'm not sure if the order is guaranteed.
Good luck,
Hassan

Thanks for the option! do you know if I save a List like that, when I retrieve to update it and the save it again, it will write the list again completely to the box? I ask because this save happens like one every sec

Thanks for the option! do you know if I save a List like that, when I retrieve to update it and the save it again, it will write the list again completely to the box? I ask because this save happens like once every sec

Normally it will write the list  again, I believe it's not a good idea if you're storing at this rate.

Still having issues with this. Is there anyway to preserve box order while using a custom key? I can save a single list because it will be updated almost every few seconds

You can have this by doing the following steps:

Declare a new variable inside of Affirmation class called nextKey as example.
Keep tracking the oldest and the newest Affirmation object in hiveBox by storing them with special hiveBox keys like "oldest" and "newest".
every time you put a new affirmation in the box, take extra steps by fetching the affirmation on "newest" and assign the new key to its nextKey attribute, then store your new item in "newest" slot as well.
In this way you'll get a linked-list-fashion structure
now when the size is larger than 52, you know where to find the oldest item, fetch it, read its nextKey, remove the oldest item from the box, fetch the nextKey item and store it in your special slot "oldest". Now you have a new oldest object.

I hope this will help you. Otherwise I would suggest to ask on stackoverflow you'll get responses very quickly.


Incorrectly rendered transparent surfaces from some viewpoints

We seem to have an issue rendering two parallel surfaces with transparency, but only at some angles. See the attached image, which shows a couple broken triangles at the top left and bottom right. If one simple rotates the view a bit, the planes appear correctly. This occurs regardless of OpenGL settings, i.e. Mesa or my nvidia card, display lists or not, etc. I suspect the triangle sorting, but that's all VTK code, and am therefore not sure.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 787
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Incorrectly rendered transparent surfaces from some viewpoints
Assigned to: -
Category: -
Target version: -
Author: Tom Fogal
Start: 07/15/2011
Due date:
% Done: 0%
Estimated time:
Created: 07/15/2011 04:43 pm
Updated: 08/05/2011 07:35 pm
Likelihood: 3 - Occasional
Severity: 3 - Major Irritation
Found in version: trunk
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
We seem to have an issue rendering two parallel surfaces with transparency, but only at some angles. See the attached image, which shows a couple broken triangles at the top left and bottom right. If one simple rotates the view a bit, the planes appear correctly. This occurs regardless of OpenGL settings, i.e. Mesa or my nvidia card, display lists or not, etc. I suspect the triangle sorting, but that's all VTK code, and am therefore not sure.
Comments:
Attaching a python script which exhibits the problem. These data are needed for the python script.The issue came up from a delaunay triangulation of two point sets. I have found the issue to be reproducible even if I save the delaunays out to two separate files, and then create a fresh VisIt session with those separate files. It is also reproducible with both surfaces in a single file, as they are here.

0798_sort.py.zip

0798_saved-sort.vtk.zip


Feature add CI test steps for previews in and dip1000 combined with in

https://github.com/andrey-zherikov/argparse/pull/85#issuecomment-1397852092

This is most likely to fail due to issues in #85


add @angular/cdk/testing in the released package

Bug, feature request, or proposal:
request
What is the expected behavior?
There are many useful test utils in @angular/cdk/testing, and we want to use them in our project.
please add @angular/cdk/testing in the the released package, thanks!
What is the current behavior?
there is no @angular/cdk/testing in the released package
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/uDmqyY
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

@jelbourn I don't understand. I thought the CDK was a development kit intended to enable creation of our own components? How can we test those components properly if the testing infrastructure that you require to test your own components isn't made public?
E.g the CDK provides a FocusMonitor service for managing focus, and all the focus related tests in the CDK rely on a patchElementFocus helper method to work properly. If you can't test your components focus-handling capabilities without this, then how can anybody else hope to?
Unless your argument is that testing of components is unnecessary, then aren't these helper methods just as vital to CDK end-users as the actual services they help test?

Like I said, it's something we definitely want to do, but nobody has had the resources yet to turn this into a fully fledged subpackage with tests, documentation, and polished APIs.

Again, how can we test CDK components properly if the testing infrastructure that you've found necessary to test your own components isn't made public?
Are we just supposed to copy and paste everything from the CDK? How it that better than just including this code in the release? I don't care about a fully fledged subpackage with tests, documentation, and polished APIs.


Fix broken links

Just fixes for some broken links.

@LauraLangdon if you're ready I can approve and merge these changes in

Sounds good!


Fix: Slider default step causes crash on Windows OS

This pull request fixes #256
Summary:
This PR provides the Slider with the fix for an application crashing when moving the Slider with a default value set for <Step/>.
The implementation introduces the similar approach to step's calculations as is already done for other platforms
(see implementation for iOS and for Android).
The calculations done on Windows implementation returns the default step as 1% of available range: minimum to maximum.
NOTE: The implementation returns the calculated percentage value in case of original step being set to 0. This considers not only the default value, but also custom user value set to 0. This is intentional - during the analysis it turned out, that setting the value of slider's step to custom 0 the application also crashes with the same error.
For more information please see the commit messages.
Test Plan:
Changes were tested manually with following scenarios:
1. Default step, minimumValue = 20, maximumValue = 140:

2. Default step, default minimum and maximum values:

3. Regression tests - step set at custom value of 1.234, minimumValue = 34, maximumValue = 153

@BartoszKlonowski It looks like you have conflicts

@BartoszKlonowski It looks like you have conflicts

Imo I like this solution more than MR

Imo I like this solution more than MR

@wojteg1337 Thanks!  I will solve the conflicts tomorrow, by rebasing my changes and I will keep the type conversion fix implemented in the merged solution,

@wojteg1337 Thanks!  I will solve the conflicts tomorrow, by rebasing my changes and I will keep the type conversion fix implemented in the merged solution,

It's probably a good idea to parametrize the default step value! However, since it relies on defaults for min/maxValue, you could consider providing defaults for those 2 props as well. Otherwise, for cases when they're not specified by the user, you end up returning 0, which crashes the app, and is what you're trying to fix here in the first place.

It's probably a good idea to parametrize the default step value! However, since it relies on defaults for min/maxValue, you could consider providing defaults for those 2 props as well. Otherwise, for cases when they're not specified by the user, you end up returning 0, which crashes the app, and is what you're trying to fix here in the first place.

@rectified95 Thanks for the review!
You've got the point about the default min & max values - this should be covered.
I'll file an issue about it, so it will be handled ASAP.
That issue I'll file can also be the place to cover some of your comments.

As for the:

I don't have the privileges to assign issues in this repo, so couldn't self-assign, but still wanted to fix the initial implementation I contributed here :)

You can always ask the owners to assign you to the item, or at least write a comment saying "I'll work on this". There will be no problems assigning you to it 👍🏻

@rectified95 Thanks for the review!
You've got the point about the default min & max values - this should be covered.
I'll file an issue about it, so it will be handled ASAP.
That issue I'll file can also be the place to cover some of your comments.

As for the:

I don't have the privileges to assign issues in this repo, so couldn't self-assign, but still wanted to fix the initial implementation I contributed here :)

You can always ask the owners to assign you to the item, or at least write a comment saying "I'll work on this". There will be no problems assigning you to it 👍🏻

Cool, so I double checked it and it doesn't crash. I remember there being issues with using the static .defaultProps on RN components in the past - must have been fixed since then.
And I agree that if someone misused the component without it crashing that's probably alright.

Cool, so I double checked it and it doesn't crash. I remember there being issues with using the static .defaultProps on RN components in the past - must have been fixed since then.
And I agree that if someone misused the component without it crashing that's probably alright.


Remove countdown latch from the implementation

Description:
https://github.com/ballerina-platform/module-ballerinax-rabbitmq/blob/master/rabbitmq-native/src/main/java/org/ballerinalang/messaging/rabbitmq/RabbitMQResourceCallback.java#L72

Closed since after having a discussion on this, it was decided that we will keep this as it is. The countdown latch is kept to ensure the order of the messages dispatched and removing it will not preserve the message order.


Database won't select

Even though it says the database is active after selecting it, whenever I run code "no database selected" error pops up.
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

This started happening immediately after updating the Cengage extension.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


ChromiumView is empty when start the window by sapp.untill resized the window.

A bug in ChromiumView on mac.
I was added ChromiumView into linear in sapp.
but webview can not show in window,untill I have been resized the window.
It's normal without sapp(example  project).
[SAPP]

[CPP]
void MainWindow::onCreate()
{
Ref m_webView;
this->setResizable(true);
m_webView = new ChromiumView;
m_webView->setWidthFilling();
m_webView->setHeightFilling();
m_webView->loadURL("https://bing.com");
mainLinear->addChild(m_webView);
}

Fixed at https://github.com/SLIBIO/SLib/commit/51af198ed5dc2d1a709d612ec229ef76f0f67e91


Noisy/grainy output

I am trying to train pix2pix to correct contrast on an image. However, I am getting blurred and grainy images. There is lot of black noise in the image(examples below). Is it because of the loss?
Note: I have made no change to pix2pix-tensorflow and used it as is.
The losses I see at the end of my training are:
discriminator loss: around 0.7
generator_loss_GAN: around 2.2
generator_loss_L1: around 0.16
Sample outputs: (Input-Output-Target)

Loss information from tensorboard:

My questions are:

Am I first of all using correctly for my usecase?
How can I make sure there is no loss of data in the image at all and only the light amount changes in the target picture?
If GAN isn't right way, can you let me know how to achieve this?

I also have a similar issue... any updates ?

Maybe you could try identity mapping loss to add to your loss function, like cycle gan. Just have a try.

@karims did you end up figuring out your issue? I run into the same grainy/blurry output, even when I ran an experiment training on a single image and evaluating that same image.


Rename combineDensityMatrices and have it accept one probability

What is currently
combineDensityMatrices(0.3, targQureg, 0.7, otherQureg);
should become
addDensityMatrix(targQureg, 0.7, otherQureg);
or something

Done


Missing implementation for updatePassword in firebase_auth plugin

The method updatePassword is not implemented in firebase_auth.
It is a critical function in my flutter application, could the team arrange to implement this function?
Thanks a lot.

Moreover, are there any workaround to update current user password?
Is it possible to use firebase web plugin in a webview to perform this action?

Closing as dup of #16775

@felixng1028
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/780. Any further collaboration will be done there.


Burning the M5Tools firmware permanently disables the touch capability

Running the official M5Tools example (https://github.com/m5stack/M5Tools) on an AWS-IoT-EduKit first displays the message "upgrading Core2 Touch Firmware" followed by the screen no longer responding to any touches in any projects. Effectively it renders the screen unusable.
Looking at the code in the M5Tools project, it appears to upgrade the screen firmware to v17, thus causing the issue.
Tested on two AWS units same result. Several others have reported the same issue on the M5 community forums. Only solution so far has been to return the units to Amazon.

Note a fix has been released and is discussed here:
https://github.com/m5stack/M5Tools/issues/2


Uncalled function checks don't work when the variable is referenced in the block

Bug Report

🔎 Search Terms
uncalled function checks, conjunction, &&
🕗 Version & Regression Information
This is the behavior in every version I tried
⏯ Playground Link

Playground link with relevant code
💻 Code

// @strictNullChecks: true

declare function isFoo(): boolean;
declare function isBar(): boolean;

if (isFoo) {
    // uncalled function checks already work well here
}

if (isFoo && isBar()) {
    // uncalled function checks already work well here
}

if (isFoo && isFoo()) {
    // uncalled function checks should cover this case too
}

if (isFoo && isBar()) {
    isFoo;
    // uncalled function checks should cover this case too
}

🙁 Actual behavior
In the last two cases we didn't detect that the first occurrence of isFoo in the condition is uncalled.
🙂 Expected behavior
When isFoo cannot possibly be a falsy value (i.e. undefined) we should highlight this as an error even if isFoo occurs again later on. This is a follow-up to a conversation in https://github.com/microsoft/TypeScript/pull/42835#discussion_r590868388.
I would be happy to enable this check, then we could run this against some user tests and decide whether there are too many false positives 🙂

A reference should be sufficient here to not complain, since you might write something like
if (isFoo) {
  invokeThisPlease(isFoo);
}

@RyanCavanaugh I'm probably misunderstanding your example, but if isFoo cannot possible be undefined, isn't the condition in the example you gave above redundant?

It's intentional that the rule is not ironclad. This is because there are some places in the language where TS thinks something is always not-undefined, but it's not necessarily the case.


Add missing methods for CursorPaginator interface

This pull request adds missing methods for the Illuminate\Contracts\Pagination\CursorPaginator interface.

This will break existing implementations.

Sorry but would like to know whether all these methods be added into the interface will break existing implementations?
I'd like to know how to use onFirstPage() and hasMorePages() on a CursorPaginator instance.
Thanks!

@TundraWork this code has already shipped so any new methods on an interface will break people's implementation of it.


rootless: automatically create a systemd scope

when running in rootless mode and using systemd as cgroup manager create automatically a systemd scope.
This solves a couple of issues:
on cgroup v2 it is necessary that a process before it can moved to a different cgroup tree must be in a directory owned by the unprivileged user.  This is not always true, e.g. when creating a session with su -l.
Closes: https://github.com/containers/libpod/issues/3937
Also, for running systemd in a container it was before necessary to specify "systemd-run --scope --user podman ...", now this is done automatically as part of this PR.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

LGTM

@msekletar  PTAL

LGTM assuming happy tests

tests are finally passing

I don't like increasing our dependency on systemd; I'd like to still be able to run in environments where it's not available. Still, this doesn't seem harmful... LGTM

I've addressed the comments and pushed a new version.

I don't like increasing our dependency on systemd; I'd like to still be able to run in environments where it's not available. Still, this doesn't seem harmful... LGTM

I agree, Podman should work fine without systemd.  If it fails to create the scope we only give a warning (if the cgroups manager is systemd) or a debug message (with cgroupfs).

@giuseppe needs a rebase.


Create home page

Home page should display the user's name and picture. There should also be a button to navigate to the ingredients page.

Create user home page
Setup Vue Routing with route guards
Create home page design in Figma
Develop home page

Only allow user to navigate to user home if logged in

Keep following this tutorial


MissingContent when trying to login

>>> from keyrings import firefox
>>> cl = firefox.Client()
>>> cl.login()
Firefox email<EMAIL_ADDRESS>Firefox password:
Please click through the confirmation email.
Hit enter when done, or type 'resend':
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/jaraco/code/main/keyrings.firefox/keyrings/firefox.py", line 69, in login
    self._build_keys()
  File "/Users/jaraco/code/main/keyrings.firefox/keyrings/firefox.py", line 77, in _build_keys
    keys_bso = self.client.get_record("crypto", "keys")
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/syncclient/client.py", line 228, in get_record
    return self._request('get', '/storage/%s/%s' % (collection.lower(),
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/syncclient/client.py", line 116, in _request
    self.raw_resp = requests.request(method, url, auth=self.auth, **kwargs)
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests/sessions.py", line 573, in request
    prep = self.prepare_request(req)
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests/sessions.py", line 484, in prepare_request
    p.prepare(
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests/models.py", line 372, in prepare
    self.prepare_auth(auth, url)
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests/models.py", line 603, in prepare_auth
    r = auth(self)
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/requests_hawk/__init__.py", line 81, in __call__
    sender = mohawk.Sender(
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/mohawk/sender.py", line 103, in __init__
    self.req_resource.gen_content_hash())
  File "/Users/jaraco/code/main/keyrings.firefox/.tox/python/lib/python3.10/site-packages/mohawk/base.py", line 284, in gen_content_hash
    raise MissingContent(
mohawk.exc.MissingContent: payload content and/or content_type cannot be empty when always_hash_content is True

In IRC, Kane has suggested:

I have done something in this regard with our fork of the old Python client (also includes the de-/encryption of BSOs apart from sync with OAuth) - was a nice experiment: https://github.com/eNote-GmbH/syncclient
Please excuse the horrific code style. Stuff just added, never refactored/cleaned.
...more specifically, you just need the correct OAuth scope for the tokenserver to pass the auth checks and make sure to use an OAuth client-id that is allowed for that scope: https://github.com/eNote-GmbH/syncclient/blob/enote/syncclient/client.py#L374-L393

and

to "fake" a browser OAuth flow for FxA, the only thing that is needed is a real flow ID, which you can extract from almost any HTML: https://github.com/eNote-GmbH/syncclient/blob/enote/syncclient/client.py#L332-L360
But this is only required for the actual login. Once you have a verified session, you can get OAuth tokens without any of these quirks.


Chroma VectorBase Use "L2" as Similarity Measure Rather than Cosine

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
vectorstore = Chroma(
persist_directory=persisit_dir,
embedding_function=embeddings
)
docs_and_scores = vectorstore.similarity_search_with_score(query=user_query)
for doc, score in docs_and_scores:
print(score)
Error Message and Stack Trace (if applicable)
No response
Description
In the doc of langchain, it said chroma use cosine to measure the distance by default, but i found it actually use l2 distence, if we debug and follow into the code of the chroma db we can find that the default distance_fn is l2
System Info
langchain==0.1.17
langchain-chroma==0.1.0
langchain-community==0.0.37
langchain-core==0.1.52
langchain-text-splitters==0.0.1
chroma-hnswlib==0.7.3
chromadb==0.4.24
langchain-chroma==0.1.0

The distance function is decided by the metadata, and if the collection already exists(when loading from disk), the metadata is same as the metadata when we save to disk. So to use cosine distance we need to specific the metadata like this
db = Chroma.from_documents(documents, embeddings, persist_directory=persist_dir, collection_metadata={"hnsw:space": "cosine"})

@DragonMengLong I don't think that adding collection_metadata={"hnsw:space": "cosine"} solves the issue. Please take a look on this example:
docs_txt = [
    "what is parameterized complexity theory?",
    "what is the complexity of parameterized complexity theory?",
    "what is parameter?",
    "I like cats!",
    "what is universe?"
]
docs = [Document(page_content=doc, metadata={}) for doc in docs_txt]

db = Chroma.from_documents(
    docs,
    model,
    persist_directory="data/test",
    collection_name="docs",
    collection_metadata={"hnsw:space": "cosine"}
)

docs_and_scores = db.similarity_search_with_score(query="Parameters", k=1)

for doc, score in docs_and_scores:
    print(score)
    print(doc)

output:
0.2922315249599653
page_content='what is parameter?'

On the other hand, calculating cosine similarity with sentence_transformers return other value:
from sentence_transformers.util import cos_sim

query = model.embed_query("Parameters")
text = model.embed_query('what is parameter?')

cos_sim(query, text)

output:
tensor([[0.8539]])

@DragonMengLong I made as you suggested. The results is the same:
from sentence_transformers.util import cos_sim
query = model.embed_query("Parameters")
text = model.embed_documents(['what is parameter?'])

cos_sim(query, text)

output: tensor([[0.8539]])

Meanwhile I've made one more test with ChromaDB library:
import chromadb
from chromadb.utils import embedding_functions

embedding = embedding_functions.SentenceTransformerEmbeddingFunction(model_name="gtr-t5-base")
chroma_client = chromadb.Client()

collection = chroma_client.create_collection(
    name="my_collection",
    embedding_function=embedding,
    metadata={"hnsw:space": "cosine"}
)

collection.add(
    documents = [
        "what is parameterized complexity theory?",
        "what is the complexity of parameterized complexity theory?",
        "what is parameter?",
        "I like cats!",
        "what is universe?"
    ],
    ids=["id1", "id2", "id3", "id4", "id5"]
)

results = collection.query(
    query_texts=["Parameters"],
    n_results=1
)
print(results)

{'ids': [['id3']], 'distances': [[0.14611518383026123]], 'metadatas': [[None]], 'embeddings': None, 'documents': [['what is parameter?']], 'uris': None, 'data': None}

The distance calculated with Chroma makes sense, as it returns cosine distance, while sentence transformers cosine similarity (1 - 0.8539 = 0.1461).
The above code is basically copied from Chroma documentation.
Resources: https://docs.trychroma.com/guides#changing-the-distance-function, https://docs.trychroma.com/guides/embeddings,

I would be more then happy to resolve the bug as my first PR to langchain :)

@klaudialemiec :)

Now I see where was the problem!
The implementation is fine - I handle the problem before of caching.
What happened:
The first time when I created collection, I didn't define distance metric, so the default Chroma metric was assigned (l2). Later, I create the collection with the same once again and set different metric. But the collection already existed, in result the new documents were added to the existing collection and new value of distance was ignored.
The correct way of testing should include deleting collection, to create it once again.
Nevertheless, I believe it would be helpful for new users to add to the documentation information how to set up distance metric (DragonMengLong first reply to this issue)


Safari 16 (release version) still broken

VoiceOver announces the wrong column and row count for each table; VoiceOver does not announce column headers when moving between columns in a table; VoiceOver table navigation commands do not work (Ctrl + Option + ⌘ + ← ↑ → ↓).
As of Safari TP 151, buttons can be navigated with VoiceOver button command (Ctrl + Option + ⌘ + J) but its accessible name is not announced.
As of Safari TP 152, a button's accessible name is announced.
Safari 16 has regressed from Safari TP 152 for buttons; a button's accessible name is not announced and it has none in the accessibility tree.

Ref: https://adrianroselli.com/2022/07/its-mid-2022-and-browsers-mostly-safari-still-break-accessibility-via-display-properties.html#D-Safari

Thanks @aardrian, just want to confirm these deficiencies seem bad enough to still treat the feature as being partially supported vs listing them under "Known Issues"?

Yes. Tables are unusable for VoiceOver users, which means de facto WCAG violations. A button without AC accessible name (itself a WCAG violation) will require the user to switch modes and navigate differently (not to mention use a different trigger). So the issue is both known and unsupported to the extent it breaks valid markup and creates barriers.

Oh and keyboard-only non-Safari users cannot put focus on the button (big WCAG issue there, if browsers acted as if they were on the hook for WCAG).

Yeah, sounds reasonable, thank you. @jensimmons FYI

We strongly disagree with the judgement that display: contents should not be used by web developers because of the accessibility of the implementation in Safari 16. We’ve been working hard to resolve the main issues with display: contents and the accessibility tree so that web developers can begin to use this value.
Please remove the note “Partial support refers to severe implementation bug that renders the content inaccessible.” It no longer applies to Safari 16.
Adrian’s arguments can be summarized into three items. Let’s address each one.

VoiceOver announces the wrong column and row count for each table; VoiceOver does not announce column headers when moving between columns in a table; VoiceOver table navigation commands do not work (Ctrl + Option + ⌘ + ← ↑ → ↓). Tables are unusable for VoiceOver users, which means de facto WCAG violations.

As stated elsewhere, our team is still working on display: contents accessibility support for HTML tables.

Bug 239479: Support display:contents for table elements
Bug 239478: Support display:contents for elements with role attributes equal to: directory, grid, treegrid, table, row, gridcell, cell, columnheader, tree, treeitem

Web developers should not apply display: contents to an HTML table because it will not be accessible in WebKit.
It makes sense to list this limitation under known issues. But the need for more work to support HTML tables does not prohibit web developers from using display: contents everyplace else. The generic “severe implementation bug that renders the content inaccessible” does not empower web developers with the information they need to understand what’s happening, or to know that they can now safely use display: contents for the majority of their usecases.

As of Safari TP 151, buttons can be navigated with VoiceOver button command (Ctrl + Option + ⌘ + J) but its accessible name is not announced. As of Safari TP 152, a button’s accessible name is announced. [In] Safari 16, a button’s accessible name is not announced and it has none in the accessibility tree… A button without AC accessible name (itself a WCAG violation) will require the user to switch modes and navigate differently (not to mention use a different trigger).

This is clearly a bug in Safari 16.0. One that we have resolved. The fix is currently in Safari 16.1 beta.
This bug only affects buttons that have display contents applied directly to them, like  button { display: contents }, which is a rare use of this value. Again, this bug does not prevent web developers from safely using display: contents for the majority of their usecases.

Keyboard-only non-Safari users cannot put focus on the button.

No button can be focused via keyboard on our platforms. This has nothing to do with display: contents.  The reasons are explained in this comment.

For confirmation, the Safari 16.1 beta release notes are at https://developer.apple.com/documentation/safari-release-notes/safari-16_1-release-notes

Fixed display:contents buttons failing to expose their accessible name.

Web developers should not apply display: contents to an HTML table because it will not be accessible in WebKit.

This is also true for tables with flex, grid, block, and inline-block. These all exist in the wild because I have encountered them in accessibility reviews.

This is clearly a bug in Safari 16.0. One that we have resolved. The fix is currently in Safari 16.1 beta.

If it corresponds to what I see in TP 152, then yes, its accName will be announced. I look forward to it.

This bug only affects buttons that have display contents applied directly to them, like button { display: contents }, which is a rare use of this value.

I have encountered it enough in accessibility reviews that it was one of four common elements of HTML that I used in my own support testing. So while you may suggest it is rare, I have encountered end users who are fundamentally blocked and sites that effectively fail WCAG SC 2.1.1 (and all the risk that comes with it).

Again, this bug does not prevent web developers from safely using display: contents for the majority of their usecases.

I am pointing out the use cases that leave disabled users stranded. A full barrier in a few core elements, IMO, outweighs support for more generic elements whose function and semantics are not as critical to users.

No button can be focused via keyboard on our platforms. This has nothing to do with display: contents. The reasons are explained in this comment.

That is demonstrably not true. Mobility impaired users enable full keyboard access, described in Apple's own documentation. It is a well documented feature outside of Apple's materials.
What that means is for a mobility-impaired user who relies on the keyboard via that macOS feature, the button with display: contents is inaccessible to them. The users most at risk are those most harmed by this bug.

For confirmation, the Safari 16.1 beta release notes are at https://developer.apple.com/documentation/safari-release-notes/safari-16_1-release-notes

That is awesome, and I look forward to testing it. However, release notes are not confirmation. Test cases are. Based on prior release notes getting it wrong (1, 2), until this is tested and demonstrated that is not evidence but simply an assertion.
I maintain the note “Partial support refers to severe implementation bug that renders the content inaccessible” applies to Safari 16. Whether it applies to Safari 16.1 is yet to be seen.

No button can be focused via keyboard on our platforms.

That is demonstrably not true.

@aardrian you are correct. Jen was handed that line on an internal thread. Someone misspoke, and I was busy with TPAC and didn’t see it in time to correct it. @jensimmons was just the messenger. (In hindsight, that comment may have been intended in the context of the click-focusability issue mentioned elsewhere.)
I’m addition to the system FKA feature you mentioned, all controls (including buttons) can be focused by default by using Option+Tab in Safari. If you change the setting in Safari Prefs, you can focus all controls with Tab similar to other browsers.
Users can also focus web buttons with dozens of built-in assistive technologies (VoiceOver, etc.) and third-party utilities (like “Shortcat”).

FWIW, Chrome has the opposite default, but also has a setting to more closely match the Mac focusability defaults. I don’t recall if Firefox does.

I also agree with Jen that the majority of display:contents usage is unblocked for authors by the hard work @twilco and others put into this Safari 16 release.
The table bug is should absolutely be referenced, but it is not blocking most authoring use cases.

I see responding here is mostly moot since @jensimmons did an end-run around this and filed a PR to undo some of this: https://github.com/Fyrd/caniuse/pull/6458
Regardless, "not blocking most authoring use cases" is a weird statement since this is about users. And for users who are impacted there is little option (other than asking them to get add-ons, rely on workarounds, or otherwise tell them they are holding it wrong).

After @aardrian and I solicited feedback (here and here) from the community the consensus seems pretty clear that developers and other accessibility experts agree that "partial support" is the more appropriate description given the deficiencies (some even arguing for "no support").
I'll further add that originally I made the assumption that not many developers would be interested in using display: contents on button and table elements, however after just a little searching I found at least one blog post discussing using it on buttons and another for table elements which to me demonstrates that there's real world use cases for doing so.
As a result I will restore the value to "partial" to ensure developers are more clearly made aware of the issue.


Allow Keras Callbacks to access predictions on_batch_end, on_epoch_end

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: n/a
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v1.9.0-rc0-35-g17d6639b55 1.9.0-rc1
Python version: 3.5.2
Bazel version (if compiling from source): n/a
GCC/Compiler version (if compiling from source): n/a
CUDA/cuDNN version: n/a
GPU model and memory: n/a
Exact command to reproduce: n/a

Describe the problem
I wanted to call attention to an issue and a PR on the keras-team/keras project so that TF could track and integrate with TF-core Keras. I believe these issues are of high importance to the community; for my project at least they are just short of critical. In summary:

PR: Keras Callbacks should be able to access predictions made during training in on_batch_end() and on_epoch_end() to eliminate expensive duplicate calls to predict() in Callbacks that require prediction results -- https://github.com/keras-team/keras/pull/10513
Writing a Keras metric should not require a graph -- https://github.com/keras-team/keras/issues/4506#issuecomment-405452870

The reason these are related is because a viable solution to the second issue depends on the first; in particular, if you wanted to write a "fancy" metric function that did calcs in Python, for example, you could leverage already-made predictions from the API described in issue 1 and circumvent having to predict() all over again, which is prohibitively expensive in all but the simplest models.

@fchollet PTAL.

Nagging Assignee @fchollet: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @fchollet: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @fchollet: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @fchollet: It has been 89 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @fchollet: It has been 104 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Accessing true and predict data on_epoch_end callback will probably not  be possible (tf is not storing them and size will be number_batchesbatch_sizesize_sample).
Easy way to access the tf predicted and targets stored in model_targets and model.outputs should be considered. See also  #32981

@doiko Preds are at least already available without extra overhead for on_batch_end, see linked line: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/keras/engine/training_arrays.py#L304
When I get a free few minutes I will submit a PR exposing these to on_batch_end; it is a trivial change now that I am looking at the code.
I can see what you mean re: not exposing to on_epoch_end, which would require accumulation of outputs. Perhaps that could be an opt-in flag in Callback. I know at least for my use case, though predict itself requires tons of resources, the predictions themselves are small and an epoch's worth will make negligible impact on memory.

Would be a cool function - also her predictions are a small overhead compared to the overhead of prediction time.

Just having the predictions and truth in the callback's on_batch_end as @evictor suggests would be a great start.  The callback can accumulate them if desired, and it wouldn't be hard for users to put this logic into a parent MetricCallback class if they desire.  The current solution of instantiating the callback with the training data and truth is much more awkward.
Also, @evictor you linked to a line number in Master, and since master has been updated since your post, I don't think that line is what you meant anymore.

@evictor,
Can you please confirm if on_predict_batch_begin  and on_predict_batch_end are what you are looking for?
Thanks!

It's been a while since I worked on that project, but yes this appears to solve the original problem we faced.

@evictor,
Thank you for your confirmation. Closing the issue.


Absoluteness of instrument should not be configurable through options.

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

The properties of monotonicity and absoluteness are encoded in the instrument itself, rather than passed in as a descriptor by the user. Currently, instruments allow for absoluteness to be configured by the user upon instantiation.

It appears this is currently only done through the ValueRecorder? As such, will likely naturally take care of this at the same time as allowing negatives for ValueRecorder.


Persistenz im Backend

Implement User model CRUD.

15.05.
crud working
todo: error responses

Implement Offers model CRUD.
Implement Schools model R


jakttest: Remove run-all.sh from Jakttest

This PR implements a series of steps to remove the jakttest/run-all.sh script
and make jakttest the entrypoint. These are the things that jakttest should
do by itself:

[x] Discover tests by itself if not given explicitly
[x] Discover the number of jobs if not given explicitly
[ ] Make a temporary directory and clean it up unless given explicitly
[ ] Re-compile selfhost if it's out of date

After looking at the docs, seems like sched_getaffinity (what I've used so that jakttest knows the number of CPUs) is only available in Linux.

how about sysconf(_SC_NPROCESSORS_CONF) ?

oh, that's a good one. Thanks!

@cybergsus - trying this out locally and I see this:
     Running `/home/jt/Source/jakt/target/debug/jakt -o build --emit-cpp-source-only jakttest.jakt`
fs
fs
fs
fs
fs
fs
fs
fs
fs
fs
fs

Any idea what that's coming from?

I traced it back a while ago: https://github.com/SerenityOS/jakt/blob/3c81d4018b75ab52731286e2c9b58650f877e359/src/codegen.rs#L2001

You might have not stumbled upon it while developing selfhost because selfhost doesn't use namespaces to declare external C++ stuff. It just uses modules to organize the Jakt code.


Apple Pass requires Dev Account?

I was just wondering whether when converting a google pass to an apple pass, if there's also an Apple Dev Account and certificate required?
Can Google Passes also be used on Apple devices with another app?

Hi there,
I can't comment on what Apple devices support, you'll need to consult Apple documentation for that.
As for Apple certificates when converting, you can convert Google to Apple passes without a certificate, but the resulting pass will not be signed, and you'll need to programatically do that yourself separately. This is covered in detail in the README, so please consult it for clarity.


VDS-1857: Update webstore

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.6 out of 8 committers have signed the CLA.:white_check_mark: ilyawzrd:white_check_mark: mvktsk:white_check_mark: AleksandraBalabanova:white_check_mark: asvishnyakov:white_check_mark: pushnitsa:white_check_mark: trueboroda:x: vc-ci:x: Eka-Savvc-ci seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix GH action typos

This is a quick fix for a typo in the gh action. The path trigger for pyproject.toml was listed as pyproject.yoml.
Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

is this ready for merge? if so can either @kcpevey or @iameskild merge?


chore(doc): fix typo

@googlebot I signed it

Review in https://dart-review.googlesource.com/c/sdk/+/123061
Thanks for contributing!


Arduino Input Node - State change for digital not working?

Hi,
When running the following:

[{"id":"71664c2f.8e99b4","type":"arduino-board","repeat":"1000","device":"/dev/ttyACM0"},{"id":"54431023.abbcf","type":"arduino in","name":"","pin":"4","state":"INPUT","arduino":"71664c2f.8e99b4","x":251,"y":200,"wires":[["ce99b356.31665"]]},{"id":"254c9827.dab368","type":"arduino out","name":"","pin":"4","state":"OUTPUT","arduino":"71664c2f.8e99b4","x":403,"y":338,"wires":[]},{"id":"9adaa94d.652558","type":"inject","name":"","topic":"","payload":"1","repeat":"","crontab":"","once":false,"x":162,"y":312,"wires":[["254c9827.dab368"]]},{"id":"c68ba83.f397458","type":"inject","name":"","topic":"","payload":"0","repeat":"","crontab":"","once":false,"x":171,"y":377,"wires":[["254c9827.dab368"]]},{"id":"ce99b356.31665","type":"debug","name":"","active":true,"complete":"true","x":481,"y":189,"wires":[]}]

I do not see anything in the debug window when clicking the inject nodes. I am running an LED from the pin which is turning off and on but the arduino input node is not giving me a value in the debug window.
This seems to only be affecting digital as reading values to the debug window on analogue pins works fine for me.
I would expect to be seeing 1's and 0's depending if the pin is going high or low.

Node has been re-written several times since original problem - nor re-reports. Closing for now.


Cannot install 1.3.3 on docker node:20-alpine image

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

SDK Version
1.3.3
What environment is your node script running in?
Docker container with node:20-alpine
Are you using an alpine based docker image?

[X] Yes (please specify the version)
[ ] No (please describe your environment)

Does the failure occur on a remote environment only?

[ ] Yes (please describe your environment)
[X] No (please describe your local environment)

Are you using alpine based node docker image. If so, what version are you using? e.g node:16-alpine3.12
node:20-alpine
If you are using alpine, have you tried using latest version of alpine or (currently alpine3.16 or alpine3.17)?

[X] Yes (please specify the version)"
[ ] No, and I cannot upgrade

Have you tried using the latest minor version of node (currently 16.20 or 18.15)?

 A complete log of this run can be found in: /root/.npm/_logs/2024-01-11T09_41_50_503Z-debug-0.log
 ERROR: executor failed running [/bin/sh -c npm install --verbose --foreground-scripts @sentry/profiling-node]: exit code: 1

Crash report
We get an SIGSEGV error when trying to install it. Our dockerfile is the following:
FROM node:20-alpine as builder
WORKDIR /usr/src/build
RUN npm install --verbose --foreground-scripts @sentry/profiling-node

Also on MacOS 14.2.1 when installing<EMAIL_ADDRESS>Reverting back to<EMAIL_ADDRESS>works.
❯ npm i<EMAIL_ADDRESS>npm ERR! path /Users/lhermann/htdocs/stagetimer/server/node_modules/@sentry/profiling-node
npm ERR! command failed
npm ERR! signal SIGABRT
npm ERR! command sh -c node scripts/check-build.mjs
npm ERR! @sentry/profiling-node: Precompiled binary found, attempting to load<EMAIL_ADDRESS>npm ERR! @sentry/profiling-node: Precompiled binary found, skipping build from source.
npm ERR! Assertion failed: (handle->flags & UV_HANDLE_CLOSING), function uv__finish_close, file core.c, line 301.

npm ERR! A complete log of this run can be found in: /Users/lhermann/.npm/_logs/2024-01-11T11_36_25_577Z-debug-0.log

Do you mind bumping to v1.3.4 and letting me know if the issue persists?

@JonasBa can confirm installation with npm i @sentry/profiling-node@latest works now 👌

@lhermann thank you so much and sorry for the issue. I'll investigate why CI did not catch this

This is happening again on node:lts-alpine and "@sentry/profiling-node": "^8.30.0"

This is a duplicate of https://github.com/getsentry/profiling-node/issues/247 (we've moved this repo to the sentry JS monorepo). There should be a fix going out with the next release, I will update you on that.

I linked the wrong issue in the reply above, the correct link is https://github.com/getsentry/sentry-javascript/issues/12169


Unable to install extension 'ms-toolsai.jupyter' as it is not compatible with VS Code

When I download the python extension to a remote server, it will report an error.
Does anyone know why？

/duplicate
#117986


image-level中scale1和scale2是怎么来的

我看到image-level中的推理用到了verb和object的加强，分别乘以scale1和scale2，我想问问这个系数是怎么来的，谢谢。

Do you mean the 117 and 80 classification scores from two separated classifiers?
These two classifiers are additional tasks to help the 600 classification, we found they can boost the performance sometimes. And after transferring the 117 or 80 to 600 scores via the prior relation matrix from Hico-det, the performance would be further boosted.
The fusing factors can be obtained via grid search on Val set, another way is to build a dynamic way to learn the factors, i.e., use the verb and object features -->MLP-Softmax-->factors, and then operate fusion. These two ways work depend on different scenarios, you may need trail-and-error to find the best way.

OH. I see. The dynamic way seems cool.  Thanks a lot.


[Installation] Steps to install

Please mention the steps to install it on ubuntu

updated the readme. please check it out.

Also the locking and recycle bin feature won't work on Ubuntu

Nope, not working in Ubuntu, atleast not in Python2.7. You are using winshell which requires _winreg which is windows registry access thus can't work with winshell, but it has been used in code(daily.py) and further more espeak not installing in Ubuntu

I've not tested it on ubuntu. I guess some features won't work in ubuntu.


A creators field in ERC1155Lazy is public

A field creators in ERC1155Lazy is public. However, ERC721Lazy declares this field private. I couldn't find any other reason why this field is declared as public so I believe this field should be private. Is there any reason this field doesn't match with ERC721Lazy?

yeah, thanks, it can totally be private!


Can't connect to: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/

Hello,
Thanks for developing this great tool!
I am unable to connect to your server: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/
I also can't connect when trying to download some of the software dependencies, such as: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/datadir/api.23andme.com
Thanks in advance for your advice.

Hi Oliver,
Thanks for your message and sorry that the server is not working. Unfortunately, it’s currently out of my hands to get it back on. I’m going to upload the datadir files into Zenodo.
Best wishes
Chang
From: Oliver Pain @.>
Date: Wednesday, 29 May 2024 at 12:00
To: changlubio/GenomePrep @.>
Cc: Subscribed @.***>
Subject: [changlubio/GenomePrep] Can't connect to: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/ (Issue #4)
Hello,
Thanks for developing this great tool!
I am unable to connect to your server: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/
I also can't connect when trying to download some of the software dependencies, such as: https://supfam.mrc-lmb.cam.ac.uk/GenomePrep/datadir/api.23andme.com
Thanks in advance for your advice.
—
Reply to this email directly, view it on GitHubhttps://github.com/changlubio/GenomePrep/issues/4, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASXWUZ7VPRZN6Z5RKB6S7WLZEWYMDAVCNFSM6AAAAABIOWCGQ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDGMBSGUYTQMA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi, The dependencies are uploaded to Zenodo and links updated in the ReadMe file.


Introduce a --registry-insecure flag

fix env var casing otherwise flags with hyphens will continue to have hyphens
Introduce an --registry-insecure flag

/hold
Deploy is still broken.
Tthough I'm noticing 'insecure' in oci.Pusher code is being confused with anonymous user so I'm unsure what's best to do here

/hold cancel

All good now - anon is still disabled by default (like it was before).
Insecure flag changes the registry scheme


⚠ Mobitopup has degraded performance

In 9d228c6, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 7763 ms

Resolved: Mobitopup performance has improved in 1383d6a after 7 minutes.


bug: @RequestHeader/@RequestParam/@InputArgument don't respect name alias and default value

If you use the "name" field of the RequestHeader annotation, it will not be read. Spring uses them as Alias' for each other, but DGS looks at the value only.
Similarly, DGS doesn't respect the defaultValue.

Example:
...
@RequestHeader(name="User-Agent", defaultValue="some example user agent value") final String userAgent
...

Good catch!

@paulbakker It looks like DGS still doesn't respect defaultValue.
Also it's worth pointing out that it doesn't respect required either, although that wasn't mentioned in this ticket.

It's not released yet, so did you test with a locally build snapshot?

It's not released yet, so did you test with a locally build snapshot?

Yes, I tested with the current master (commit abc57436766486d93cd82497fb8fda9341eb4fbc)

I understand the issue now. What's fixed is the default value (a value without a name), but not the defaultValue argument. I hadn't even looked at the latter and wasn't aware of it being an issue, so thanks for reporting that.
I'll create a separate issue for this for clarity.

Awesome, thank you @paulbakker!


Bdv frame settings are only saved to rove with Bdv frame open

Big Data Viewer settings are only saved when a BdvFrame is open. If you save the archive afterward with no BdvFrame open the settings are overwritten. It would be nice if the settings were retained even if a bdv frame is not currently open. This would require reloading the settings form the rover file and and resaving. Currently the settings are only stored in the active frame objects so this would require a new object or perhaps using the Jackson object mapper to load and resave those settings. Perhaps that would be the best solution.

Maybe it would be possible to use the jackson json ObjectMapper and read the rover file using readTree and work with it in the form of JsonNodes. Get the JsonNode for the bdv settings object and then directly write out the JsonNode ? a TreeNode can we written directly on a jGenerator

This has been addressed by holding a bye array copy of the rover file and restoring bdvFrame settings that were in the file in case no bdvFrames are currently open. This way the bdvFrame settings are kept even if you work with an archive without opening the videos and perform several saves. This is all added in commit ae2493dc58c74541d8fec9319f1014e6dfbbe024


POST the JSON new nested collection

Hi, this is very nice, when I try to POST a nested collection,

I am not getting uniquely identified attribute values with Id, this is confusing the server side while trying to bind to a model object for saving/add new and deleting.
Also is there a template on the div row or table row, I can use to clone/append where the repeater assigns hidden attribute values to the new row, so the collection rows are uniquely indexed when POST

Thanks

Not sure if I understand completly.
If you need to add custom behavior, the "show" callback might help with your use case.
$('.my-repeater').repeater({
  show: function () {
    // the value of "this" is set to the newly created html element
    setNewElementWithMyCustomBehavior(this)
  }
})

The library creates a template internally by cloning the first list item. The library isn't really set up to do this more explicitly.

Its cloning fine, but when POST for the new rows, inside this, the id of the the new row does not seem unique and having trouble saving at server

[ ] What should I query to get the unique values, How to ensure unique values also append to any child rows of the new row (nested collection/rows)
[ ] Second my rows have a button like approve , reject, when clicked how to ensure they pass the correct Id/value of the clicked row?


[Authenticator] The library should declare the needed consumer proguard rules

Before creating a new issue, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.

Which UI component?
Authenticator
Gradle script dependencies
// Put output below this line
authenticatorVersion = "1.1.0"

Environment information
# Put output below this line
Gradle 8.5

Please include any relevant guides or documentation you're referencing
No response
Describe the bug
When I'm doing a release build of my App that uses Amplify UI I get the following:
> Task :app:minifyReleaseWithR8 AGPBI: {"kind":"warning","text":"Missing class kotlinx.parcelize.Parcelize (referenced from: com.amplifyframework.notifications.pushnotifications.NotificationContentProvider$FCM and 2 other contexts)","sources":[{}],"tool":"R8"}
I can get around this by including the following in my proguardrules.pro
-dontwarn kotlinx.parcelize.Parcelize*
But the needed rules should really come with the library
Reproduction steps (if applicable)
No response
Code Snippet
// Put your code below this line.

Log output
// Put your logs below this line
AGPBI: {"kind":"warning","text":"Missing class kotlinx.parcelize.Parcelize (referenced from: com.amplifyframework.notifications.pushnotifications.NotificationContentProvider$FCM and 2 other contexts)","sources":[{}],"tool":"R8"}

amplifyconfiguration.json
No response
Additional information and screenshots
No response

This appears to be coming from the underlying Amplify library, not from Authenticator. Authenticator does not use push notifications. Transferring the issue there.


Filtering tables before fetching their details in Entity Generator

Is your feature request related to a problem? Please describe.
The database I am currently working on has a lot of tables. I am using the takeTables option to generate entity models for only some of them, but currently the filtering is done after retrieving the details of each table, making the generation take a very long time.
Describe the solution you'd like
I would like it to be possible to filter tables before retrieving its details, i.e. columns, constraints etc.
Describe alternatives you've considered
I am currently using a patch that adds the takeTables and skipTables parameters to the DatabaseSchema::create method in the @mikro-orm/knex package and moves isTableNameAllowed from EntityGenerator there. This allows to load schema information only for the corresponding tables.
Then in EntityGenerator::generate, for references for which no entity model will exist, I substitute the type for the column type.
Additional context
I could work on PR implementing these changes if you think what I described is correct or change the approach if something doesn't seem right to you.

Makes sense to me, thoughts @boenrobot?


Expose number of active TCP connections

New func (*Server) ActiveConns to expose to the application the number of active TCP connections in use at any given moment

I don't think this should be added.
There are other ways to extract this (and much more data) from the OS level.
This only exposed a tiny bit of information.
Coredns shows how to do this without any changes to this library.
/Miek

I don't think this should be added. There are other ways to extract this (and much more data) from the OS level. This only exposed a tiny bit of information. Coredns shows how to do this without any changes to this library. /Miek

Where can I find it?


ToIP RFC update

Incorporated feedback and comments on the original RFC. Added a section on governance framework structure. Modified the last section to make it more general and inclusive.

I don't think anything in this is controversial; it consists of some wordsmithing, some improved references, and some clarifications.


Suppress warning already initialized constant

Description
This PR will suppress following warning while running chefspec for cookbook which includes compat_resource cookbook as dependency.
/tmp/chefspec20161229-27198-1do3odsfile_cache_path/cookbooks/compat_resource/files/lib/chef_upstream_version.rb:2: warning: already initialized constant ChefCompat::CHEF_UPSTREAM_VERSION
/tmp/d20161229-27198-ul2nvd/cookbooks/compat_resource/files/lib/chef_upstream_version.rb:2: warning: previous definition of CHEF_UPSTREAM_VERSION was here

Issues Resolved
[List any existing issues this PR resolves] no issue submitted for this PR
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing. (this is fix for a test case)
[x] New functionality has been documented in the README if applicable (not applicable as it's not a functionality)
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

A build is failing because of nokogiri dependency
nokogiri-1.7.0 requires ruby version >= 2.1.0, which is incompatible with the current version, ruby 2.0.0p598

@lamont-granquist Is there anything I can improve this PR?


Add estimateGas to DeferredTransactionWrapper

It would be great to have a way to call estimateGas through this interface. Ideally this would be called in the send process but for now this could be a good start to assist people pass more specific gas estimates instead of standard gas limits per the example.

Thanks @myspivey, this looks good!
Could you run yarn test:fix to fix autofixable problems? (linting failed)

Closing in favor of https://github.com/krzkaczor/TypeChain/pull/70 Thanks!


xtensor refactoring

I am currently working on a refactoring that will make features already implemented in #1430 and #1444 available to any kind of expression. It will also implement #1431.
Just to avoid potential duplication of effort.
cc @tdegeus

Nice, thanks!


Specify branch/tag used for git submodule

Fix #92
Fix #85 <= this adds title to show it's search.
Fix #91 <= I added client installs to its own section under intro so its easier to find
Fix #90 <= @mcupak I think you wanted Applications and Use Cases to be combined. Let me know if this wasn't the case.

A note about the submodules. The main repository(ga4gh-search) refers to a commit of the nested submodule repository. If we don't pull the submodule manually, then commit that change to the main repository, git will always try to update the submodule to the commit specified in the main repository. We don't have to worry about breaking Travis because the submodules have new commits upstream.

A note about the submodules. The main repository(ga4gh-search) refers to a commit of the nested submodule repository. If we don't pull the submodule manually, then commit that change to the main repository, git will always try to update the submodule to the commit specified in the main repository. We don't have to worry about breaking Travis because the submodules have new commits upstream.

Thanks @gewenyu99, looks good! A couple of comments/questions:

The PR says if fixes #92, which is this PR. Was there a different issue number?
Can you elaborate on what https://github.com/ga4gh-discovery/ga4gh-search/pull/92/files#diff-6ac3f79fc25d95cd1e3d51da53a4b21b939437392578a35ae8cd6d5366ca5485R15 does? Why do we need this?
I added a clarification to #90 if we can adjust.

Thanks @gewenyu99, looks good! A couple of comments/questions:

The PR says if fixes #92, which is this PR. Was there a different issue number?
Can you elaborate on what https://github.com/ga4gh-discovery/ga4gh-search/pull/92/files#diff-6ac3f79fc25d95cd1e3d51da53a4b21b939437392578a35ae8cd6d5366ca5485R15 does? Why do we need this?
I added a clarification to #90 if we can adjust.

In general, we should link commits to issues in commit messages, if you want to squash them and adjust (e.g. issue #90, fix #90).
I've cleaned up my commits :P, hope that much easier to view.

The PR says if fixes #92, which is this PR. Was there a different issue number?
Can you elaborate on what https://github.com/ga4gh-discovery/ga4gh-search/pull/92/files#diff-
There is a branch v1.1.1 which will only get bug fixes. The file .gitmodules specifies the branch the submodule uses. When tracking branches in your submodules, --remote will allow the submodule to stay up to date with the branch specified.

I added a clarification to #90 if we can adjust. < I will get this fixed

In general, we should link commits to issues in commit messages, if you want to squash them and adjust (e.g. issue #90, fix #90).
I've cleaned up my commits :P, hope that much easier to view.

The PR says if fixes #92, which is this PR. Was there a different issue number?
Can you elaborate on what https://github.com/ga4gh-discovery/ga4gh-search/pull/92/files#diff-
There is a branch v1.1.1 which will only get bug fixes. The file .gitmodules specifies the branch the submodule uses. When tracking branches in your submodules, --remote will allow the submodule to stay up to date with the branch specified.

I added a clarification to #90 if we can adjust. < I will get this fixed

Merged to develop.


Add missing DynamicFindBy to the Rails cop list

This is a documentation change only (in the manuals).
This cop can be found at http://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Rails/DynamicFindBy.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
(N/A) Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
(N/A) Added tests.
(N/A) Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
(N/A) Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

This list is generated automatically, so I'm guess something's wrong with the cop's config or something if our rake task didn't pick it up.

@bbatsov, damn, didn't know that. Do you want me to investigate on the reason why?

@sihu can you look into this?

@bbatsov yes i will 👍

@astorije very good point! No the overview of all cops is not updated. But the docs details for each cop is generated . We have to fix that for sure.
@bbatsov i suggest we also automate that list or add a spec so the CI fails if it's not added to the overview. A reason why it is not yet done is because we have also content which might change in the *.md file. I see some options:

complete the task of updating documentation with a subtask to link the generated bot in the overview (fastest and easiest solution)
add a list generator which generates the TOC. So we replace a part of the cops.md on every call of the task.

Maybe we could also automate the generation of the task so the contribution is easier? We could also take some more points into it so it would for example add an entry to the contribution file ...

Maybe we could also automate the generation of the task so the contribution is easier? We could also take some more points into it so it would for example add an entry to the contribution file ...

Ideally, this would be automated, but I'm guessing we'll need some bot automatically committing the docs changes or something like this. I never had to deal with adding commits automatically after merging code changes.

One more thing - this PR should be updated and rebased I guess.


Third branch - Week 3: JSON

lgtm.

Make sure to resolve the conflicts
Make sure that GSON is working fine I didn't see you importing it in XML file.

I deleted the gson because i didn’t use it so there was no need


WIP: Fix generated sub name

Fixes https://github.com/operator-framework/operator-lifecycle-manager/issues/1559

closing due to staleness


docs: glob and regexp related improvements

Closes # (issue)

:zap: Summary

Per the subject.
:ballot_box_with_check: Checklist

[x] Check locally
[ ] Add tests
[x] Add documentation

Thank you very much!


gamescope: patch gamescopereaper path

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/326591

Replace relative gamescopereaper path with absolute
Bump version: https://github.com/ValveSoftware/gamescope/compare/3.14.23...3.14.24

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 326868 run on x86_64-linux 1

4 packages built:

bottles
bottles-unwrapped
gamescope
gamescope-wsi

Confirmed this fixes programs.gamescope.enable without adding gamescope to environment.systemPackages

@K900 there aren't right now but fair that there could be later -- my only thought on patch is that could require refreshing later.

That's part of the point, yes.

Yeah, totally makes sense -- updated with a patch and variable substitution instead of straight replacement.


Trainer train simplified, tests for load

the arguments of Trainer.train now are passed to the fit
unittest for load/restoring from checkpoint

Perfect for me.

Checks are failing. I don't think is due to the PR... The PR looks ok for me.


Document spin plugin

Since plugins are now used to install js2wasm for the JavaScript SDK, we should have some documentation on how spin plugins work.

cc/ @kate-goldenring