Miner 1.1.15/1.1.16.rc1 setup failed after HA Core update

Version of the custom_component
Found at 1.1.15 and 1.1.16.rc1
Configuration
Core
2024.10.0
Supervisor
2024.09.1
Operating System
13.1
User interface
20241002.2
Debug log
homeassistant.setup
Source: setup.py:269
Setup failed for custom integration 'miner': Requirements for miner not found: ['pyasic==0.60.7'].

homeassistant.util.package
Source: util/package.py:150
Unable to install package pyasic==0.60.6: × No solution found when resolving dependencies: ╰─▶ Because there is no version of betterproto==2.0.0b6 and pyasic==0.60.6 depends on betterproto==2.0.0b6, we can conclude that pyasic==0.60.6 cannot be used. And because you require pyasic==0.60.6, we can conclude that your requirements are unsatisfiable. hint: betterproto was requested with a pre-release marker (e.g., betterproto==2.0.0b6), but pre-releases weren't enabled (try: --prerelease=allow)

Same Problem

Same problem
Setup failed for custom integration 'miner': Requirements for miner not found: ['pyasic==0.60.6'].

In my case the log entry is Setup failed for custom integration 'miner': Requirements for miner not found: ['pyasic==0.60.5'].
Both miner were running with 1.1.14 before, but with last HA update not anymore. Also not running with 1.1.16.rc1.

I was going to open an issue for this as well. Latest HA Core update and pre-release miner version:

Ah.    That's not great, as I'm not sure the existing BOS+ schema actually complies with what betterproto wants.

"Betterproto was requested with a pre-release marker, but pre-releases were not enabled..."

"Betterproto was requested with a pre-release marker, but pre-releases were not enabled..."

I'm running HA Green so not really sure how to alter the code to enable pre-releases. I know others here are smart enough to figure this out. :)

same problem

"Betterproto was requested with a pre-release marker, but pre-releases were not enabled..."

I'm running HA Green so not really sure how to alter the code to enable pre-releases. I know others here are smart enough to figure this out. :)

I'll have to try to out on my instance when I get home, the good news is it's a HASS change, but I don't know how to deal with it or really what the did.

Same here.

I have the same problem. Please fix it.

Same here my friend.
Can you please try to fix it. Thanks !

I have asked the home assistant team about it, but it's an issue with home assistant, not this repo.

With version 1.1.12 on HA Core 2024.9.3 it´s runningwithout any problems.
If neccessary I can test the upcoming versions to see if it´s HA oder miner.

@ThorPrez Thanks for the pointer. I downgraded HA Core using the Terminal (ha core update --version 2024.9.3) and now Miner 1.1.16rc1 is working for me again.

Same Problem

Logger: homeassistant.setup
Källa: setup.py:269
Inträffade först: 10:05:57 (1 händelser)
Senast loggade: 10:05:57
Setup failed for custom integration 'miner': Requirements for miner not found: ['pyasic==0.60.6'].

Guys, downgrade HA core to 2024.9.3 and it will work.

Yes, downgrade worked also for me

Im running 2014.10.1 installed de missing package by hand in HA core (pip install pyasic). Restart HA and you're good to go with the latest HA version

pip install pyasic

Hello! I'm using HA Green. Would you happen to know how I could do that? Here is what I get when I tried within the terminal app:

@Ben-in-Chicago try python3 -m pip install pyasic

python3 -m pip install pyasic

python3 -m pip install pyasic

python rather than python3?

python3 -m pip install pyasic

python rather than python3?

Same result

Not exactly sure how to do that on the green. I run HA in a docker container and just exec into the container. Make sure you are in the Linux cli not the HA cli

Can't the repair be a downgrade???

Can't the repair be a downgrade???
You are not serious.

It's an issue with home assistant, and until they reply to me on the posts I've made, I can't do anything about it.

Can't the repair be a downgrade???
You are not serious.

It's an issue with home assistant, and until they reply to me on the posts I've made, I can't do anything about it.

Thank you for working on it.  You have my respect.

login with ssh, enter docker docker exec -it homeassistant bash
pip install pyasic==0.60.7
install / update  v1.1.16rc1 with HACS
works on core 2024.10.1

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

Can I do this with the Terminal?
The commands dont work. Maybe i am not a pro at this point..

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

Can I do this with the Terminal?
The commands dont work. Maybe i am not a pro at this point..

This will only work if you're running home assistant with docker.
User the Terminal and SSH add-on to get ssh access, the run the commands past the docker command.  The docker exec ... command is the docker deployment version of SSH.

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

2024.10.2 also confirmed working

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

2024.10.2 also confirmed working

Fixed in latest version of home assistant then.  Nice.

Are you sure this is fixed? I still have the error. Maybe you installed the dependency manually, which fixed it for you?
I'm running haos and just updated HA to 2024.10.2, and still get the same error when trying to add a miner.
I tried v1.1.16rc1:
homeassistant.requirements.RequirementsNotFound: Requirements for miner not found: ['pyasic==0.60.7'].

But also tried v1.1.15
homeassistant.requirements.RequirementsNotFound: Requirements for miner not found: ['pyasic==0.60.6'].

Yeah, like I said, it's actually an issue with home assistant, nothing has changed on the pyasic side that would cause it to be unable to install.

Can you please post a link to your posts. I would like to join the discussion an support you.

@spamferkel
https://community.home-assistant.io/t/home-assistant-24-10-0-issues-with-beta-package-versions/778656

Yeah, like I said, it's actually an issue with home assistant, nothing has changed on the pyasic side that would cause it to be unable to install.

I get that, but I think it's not fixed with the latest HA release. At least I can't confirm it.

My guess would be that the fix would come with Home Assistant Operating System update and not with a new version of Home Assistant, since pyasic would be part of the OS and not of HA

Not so sure about this, because the issue isn't actually with any dependency per-se, but with the way home assistant is installing dependencies.  They need to allow pre-release dependencies, which needs to be changed in core AFAIU.

Any news on the subject? Will the next version of this integration be able to work without any additional work?

Any news on the subject? Will the next version of this integration be able to work without any additional work?

Still waiting on a response from the devs.  This is an issue with home assistant, not with this integration.

Opened an issue on core, we shall see if that gets any response.

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

Seems I'm limited to the commands listed here. Any other suggestions?

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

Seems I'm limited to the commands listed here. Any other suggestions?

You need to get root-access. Look here https://developers.home-assistant.io/docs/operating-system/debugging/ . Be very careful with this. You can easily destroy your homeassistant. This is normally just for devs and die-hard-linux-nerds ;) . If you can execute a command like docker ps you should get a list of running containers. Then you're on the right way and can go on with the commands you mentioned...

login with ssh, enter docker docker exec -it homeassistant bash pip install pyasic==0.60.7 install / update v1.1.16rc1 with HACS works on core 2024.10.1

Seems I'm limited to the commands listed here. Any other suggestions?

You need to get root-access. Look here https://developers.home-assistant.io/docs/operating-system/debugging/ . Be very careful with this. You can easily destroy your homeassistant. This is normally just for devs and die-hard-linux-nerds ;) . If you can execute a command like docker ps you should get a list of running containers. Then you're on the right way and can go on with the commands you mentioned...

It appears limited to what I can do (within the GUI and my skillset) so it seems like I need to sit tight until this is resolved by the appropriate people.

This question makes me uneducated, but it is simple in other integrations - I install them, and they work. Is there a way for the developers to adapt the integration to the new system somehow?

This question makes me uneducated, but it is simple in other integrations - I install them, and they work. Is there a way for the developers to adapt the integration to the new system somehow?

The reason for this is because pyasic requires betterproto for managing BOS+ devices, because it's basically the only reasonable library for handling gRPC calls.  The problem is it has been in a beta version for about 2 years, and now home assistant is refusing to install it (probably because one flag needs to be set in their package manager, uv), which they updated from like 0.2.x to 0.4.x in 24.10.0.  Hence broken package, and I can't do anything about it since it is required for the integration to function at all.

This question makes me uneducated, but it is simple in other integrations - I install them, and they work. Is there a way for the developers to adapt the integration to the new system somehow?

The reason for this is because pyasic requires betterproto for managing BOS+ devices, because it's basically the only reasonable library for handling gRPC calls. The problem is it has been in a beta version for about 2 years, and now home assistant is refusing to install it (probably because one flag needs to be set in their package manager, uv), which they updated from like 0.2.x to 0.4.x in 24.10.0. Hence broken package, and I can't do anything about it since it is required for the integration to function at all.

Thank you for letting us know. We live in the hope of having this resolved. :)

Hey everyone
We fully understand the frustration of this, as @b-rowan said, this is a problem of homeassistant 2024.10.1 where the developers of homeassistant decided to not allow beta versions of specific python packages. hass-miner relies on pyasic (maintained by @b-rowan - so we would have control over this) which [itself relies on betterproto](https://github.com/UpstreamData/pyasic/blob/2b00e741caeed0ba1e617206c885ee0a65ef90e7/pyproject.toml#L18. No unfortunately the developer of beterproto only is releasing beta versions. So far this was not a problem, but since homeassistant now does not allow beta versions anymore (reasons currently unclear) we cannot install pyasic anymore, which also means hass-miner doesn't work anymore.
Fixes & Workarounds

The best possible fix is to have the homeassistant developers allow beta versions again - something which we trying to work with them here: https://github.com/home-assistant/core/issues/128981 if you want to help us, please comment on that issue that this is affecting you, the more people we have that report this affecting them the better.
The second fix is to force homeassistant to install pyasic manually (docker exec -it homeassistant bash and pip install pyasic==0.60.7) this works via only if you run homeassistant via docker and not if you have homeassistant running on a raspberry pi or any other standalone server - as there you cannot just connect to core and update packages.
A solution for any standalone server & raspberry pi users: Open the Terminal in the HomeAssistant UI and run ha core update --version 2024.9.3 - this will downgrade (!) your homeassistant to a version were we can still install beta versions. Keep in mind though that downgrading of homeassistant isn't usually something that is suggested as it could cause other issues, but in this specific case it seems to be the best solution.

As soon as we have a solution from the homeassistant devs we will then hopefully be able to upgrade again to 2024.10.x or newer.

Downgrading to 9.3 worked for me. Thank you all for you work on this and for continuing to push for a permanent fix.

Running HACS on UmbrelOS (so Docker) and not able to use anu of the work arounds.
Can any one list the commands to downgrade from terminal in Umbrel, please?

@saxtron3000 unfortunately I don't have an UmbrelOS around to test, but I assume there is a way to connect into the homeassistant container in Umbrel? there you should be able to run pip install pyasic==0.60.7 to fix this.

Is someone able to test out v1.1.17rc?  I tried putting the flag for --prerelease-allow into the manifest for that version after looking at how the install is done.

Just tested it and its not working. Even when I manual install the package I still get the same error

@saxtron3000 unfortunately I don't have an UmbrelOS around to test, but I assume there is a way to connect into the homeassistant container in Umbrel? there you should be able to run pip install pyasic==0.60.7 to fix this.

I run the pip install in the docker terminal and still get the same error:-
_Error
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble_

I've opened a PR on core that should fix this, https://github.com/home-assistant/core/pull/129641.

Looks like they added it to the 2024.11.0 milestone, meaning this should (hopefully) be fixed in the next release of home assistant.

I installed the new release today, reinstalled the integration and still no luck. I begin to think there is no solution to this.

Looks like they added it to the 2024.11.0 milestone, meaning this should (hopefully) be fixed in the next release of home assistant.

I installed the new release today, reinstalled the integration and still no luck. I begin to think there is no solution to this.

They declined my fix.  I don't know what to say at this point, I'm quite annoyed with the HASS dev team.  I have a couple more ideas and past that point this project is pretty much dead.
Try the latest pre-release version; it attempts to install them separately.  If that doesn't work then I don't know what else to try.

Looks like they added it to the 2024.11.0 milestone, meaning this should (hopefully) be fixed in the next release of home assistant.

I installed the new release today, reinstalled the integration and still no luck. I begin to think there is no solution to this.

They declined my fix. I don't know what to say at this point, I'm quite annoyed with the HASS dev team. I have a couple more ideas and past that point this project is pretty much dead.
Try the latest pre-release version; it attempts to install them separately. If that doesn't work then I don't know what else to try.

Unfortunately, I tried the new, pre-release 1.1.17rc5...

Definitely not the cleanest option but what if you fork the beta package and take your own fork out of beta?

Core: 2024.11.0
Supervisor: 2024.11.2
Operating System: 13.2
Frontend: 20241106.0
Miner: v1.1.17rc5
so i managed to install i just had to use like this:
first login to docker
docker exec -it homeassistant bash
and run in docker
pip install --root-user-action=ignore pyasic==0.62.1
after this install it works

How come there is no workaround for a standalone installation similar to the docker variant?

There should be, just run those same commands in the Terminal & SSH plugin that you used when installing HACS.

I don't think that works as the Terminal of HACS, as it is sandboxed and can't change actual stuff of HomeAssistant itself.

How come there is no workaround for a standalone installation similar to the docker variant?

There should be, just run those same commands in the Terminal & SSH plugin that you used when installing HACS.

I don't think that works as the Terminal of HACS, as it is sandboxed and can't change actual stuff of HomeAssistant itself.

Can confirm I've tried that approach and it doesn't work. Otherwise that would have been an easy workaround.

I FIXED IT!!!!!
All it took was taking my PR that was supposed to fix it, creating a patch.py file, copying my install function that doesnt suck, then every time I try to use pyasic, if it cant be found, it will just install it.  Thanks a lot to the absolutely garbage support from the home assistant team.

Fixed in 1.1.17.

I FIXED IT!!!!!
All it took was taking my PR that was supposed to fix it, creating a patch.py file, copying my install function that doesnt suck, then every time I try to use pyasic, if it cant be found, it will just install it. Thanks a lot to the absolutely garbage support from the home assistant team.

I knew it! Your personality trait won't allow you to accept that it's not doable. No project will ever die as long as there are people like you.
Big thank you from Serbia.

Woho! Good job @b-rowan 🙌 confirmed working on 2024.11.0 and 2024.10.4 both standalone versions. My spot price miners say thank you! 🙏 ❤

Can confirm it works with latest Home Assistant now. Thanks @b-rowan for hanging in and fixing this. I can imagine it has been a frustrating ride, glad you found an approach that works and doesn't depend on upstream changes. 🎉

Nice work mate =) Awesome!


stash step repeated many times

Description
Not sure why, but the following just happened (it repeated the stash step many times):
❯ git commit -m "remove a bunch unneeded dependencies"
husky > pre-commit (node v13.7.0)
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ✔ Running linters...
[webpack-5 06a09ee] remove a bunch unneeded dependencies
 1 file changed, 1 insertion(+), 31 deletions(-)

Steps to reproduce
I'm not sure, but it happens every time now. I'm in a proprietary repo so I can't share that unfortunately.
I'll report back if I find out.
Debug Logs
let me see...

TODO
COPY THE DEBUG LOGS HERE

Environment

OS:
Node.js:
lint-staged:  8.2.1

Hmmm, when I added --debug, the problem doesn't happen.

I wonder if maybe there's actually something wrong with my Terminal. I'll close this for now.


Contact form validation

Contact Form Validation

Added contact form validation using javascript JavaScript
Run linters for Errors

Thank you @cynthiainga


Twitter login broken in mobile mode

Hi,
I'm trying to use Twitter login in an ionic mobile app (with satellizer 0.11.2)  and ran into some issue. Facebook and Google login work just fine, though.
The error I get is:
TypeError: Cannot read property 'location' of undefined
    at satellizer.js:587
    at processQueue (ionic.bundle.js:21888)
    at ionic.bundle.js:21904
    at Scope.$eval (ionic.bundle.js:23100)
    at Scope.$digest (ionic.bundle.js:22916)
    at Scope.$apply (ionic.bundle.js:23205)
    at done (ionic.bundle.js:18358)
    at completeRequest (ionic.bundle.js:18548)
    at XMLHttpRequest.requestLoaded (ionic.bundle.js:18489)

The corresponding line is
 popupWindow.popupWindow.location.href = [defaults.authorizationEndpoint, oauth1.buildQueryString(response.data)].join('?');

and debugging further it seems to expect a popup object but instead gets a promise returned:
satellizer.js:639-642
          if (config.platform === 'mobile') {
            return popup.eventListener(redirectUri);
          }

          return popup;

Thanks, I will take a look at it. When I was refactoring Twitter authentication I was so focused on getting it  to work on desktop browsers that I completely forgot about that popup.eventListener flow on mobile.

I just pushed an update to master. Let me know if it works for you.

Thanks for the fix, it seems to work for me :fireworks:
I directly ran into the next issue, though, but I think it is already tracked at https://github.com/sahat/satellizer/issues/417.


TEST PR: verify that e2e CI fails when tests fail

/hold

/test-v1a5-e2e

/test-v1a5-e2e

Triggering e2e tests to see if #234 helped with the bug that this PR was also hitting.
/test-v1a5-e2e

Seems to be working, and this time it failed intentionally as this patch expects.


Preloader does not work properly with page history

I created this issue to first discuss the fix I created.
Would a pull request have been the more appropriate choice here?
First, the fix:
window.onpagehide = function() {     $('#status').fadeOut('fast');     $('#preloader').delay(350).fadeOut('slow'); };
This code is compatible with the back/forward cache (bfcache) which is of course optimal.
Please help me now to understand if this is really the right solution. I myself have tested the fix throughout without giving the server the possibility to cache the page.

This prevents preloader stucking by press the browser back/forward buttons, correct? Tested it and works fine in my case, thank you.
I'm happy if you open a pull request.

Hey, I'm very sorry for the late reply but I'm not able to get to my desktop at the moment as my mom has been hospitalized and I'm with her. You can just use the code, would make me more than happy if you mention me.
Thank you.

Done, thank you. All the best for your mum.


MDGram has changed package name

Can you update the package name on MDGram in hooks? It has changed from org.telegram.mdgram to app.mdgram.android

Hey!
Yes sure i will note that


Support for CloudWatch SDK

I need to make some queries using CloudWatch Insight, would be great to have easy access and configuration of the SDK under the quarkus-amazon-services umbrella.

I will try to open PR with the CloudWatch module shortly


Toggle visibility on scroll

Hello!
I am trying to figure out how to use the modules effectively. There's one feature on this website that's puzzling me: http://boyntonyards.com/
The Expolre Somerville button is fixed on the screen. It hides when I scroll down, closer to the footer. I wanted to see how this was done because it would be nice to have control over any element if needed. In chrome's insepctor sources panel I was searching for StickyCtaToggler and there's almost nothing in the hide() function. I don't even see where the hide function was called. The "enter" that's in the hide function - where does it come from? I assume the setInView function dispatches dispatchCall and sticks the enter value somehow but I can't figure out how to use calls to create a similar trigger animation. I was hoping I could do this elegantly but I ran out of ideas.
Thanks

Hey, it's probably done with Locomotive Scroll data-scroll-target.
You can also do it with modularScroll data-scroll-call.


Exported ports does not match the ones in configuration

From netstat inside the container:

root@73c280d0b100:/etc/puppet# netstat -an |more
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 <IP_ADDRESS>:8280            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:51064           <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:10397         <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:9443            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:9763            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:11111           <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:39880           <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:9999            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:8243            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:10711        <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:42719        <IP_ADDRESS>:5865         TIME_WAIT
tcp        0      0 <IP_ADDRESS>:50168        <IP_ADDRESS>:11111        TIME_WAIT
tcp        0      0 <IP_ADDRESS>:42717        <IP_ADDRESS>:5865         TIME_WAIT
udp        0      0 <IP_ADDRESS>:42434           <IP_ADDRESS>:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ]         STREAM     CONNECTED     1490631
unix  2      [ ]         STREAM     CONNECTED     1488474

From /mnt/<IP_ADDRESS>/wso2am-1.10.0/repository/conf/api-manager.xml:

          https://am.wso2.com:32004/store
          https://am.wso2.com:32004/publisher

And docker mapping:

[developer@komarr wso2am]$ docker ps --no-trunc
CONTAINER ID                                                       IMAGE                  COMMAND                               CREATED             STATUS              PORTS                                                                                NAMES
73c280d0b1008739554a17e41e5e466962c583d05024997a3f8e7780daebd51b   wso2/am-1.10.0:1.0.0   "/bin/sh -c /usr/local/bin/init.sh"   About an hour ago   Up About an hour    <IP_ADDRESS>:32773->7711/tcp, <IP_ADDRESS>:32772->8243/tcp, <IP_ADDRESS>:32771->8280/tcp, <IP_ADDRESS>:32770->9443/tcp, <IP_ADDRESS>:32769->9763/tcp, <IP_ADDRESS>:32768->10397/tcp   wso2am-default

Thanks @gordillo-ramon for reporting this! Yes it looks like Thrift receiver in Key Manager is starting at port 10397, I will fix this in the Dockerfile:
[2016-03-11 20:27:42,046]  INFO - APIKeyMgtServiceComponent Started thrift key mgt service at port:10397

I only noticed this problem, did you see any other issues?

Fixed with commit https://github.com/wso2/dockerfiles/commit/75c598c7ec1fa2316f0230227be60d95cde4e279

The main problem I had was with port redirection to publisher login. It took me to port 32004, whereas the exposed one was 32769.

@gordillo-ramon, those port settings are configured in hieradata, https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/default.yaml#L79-L82, this is how those ports are set in api-manager.xml.
I believe you have used run.sh to start the container, there we have used -P flag for automatic port publishing, we are planning to update run.sh to expose ports accordingly, for eg
docker run -p 32004:9443 -p 32003:9763.. etc

Yes @sajhak that's the problem, we might need to use the same ports defined in hieradata otherwise proxy ports would not work properly.

That's the point. The automatic random exposition only works when the port is not referenced any place in the code. Otherwise, like in this case, it should be a particular number.

Fixed with new docker-run.sh support parameters.


Navigation menu appears in different font on different pages

The top level navigation ("AMPHTML", "AMPHTML ads", etc.) appears in a different font depending on which section is selected:
https://ampbyexample.com:

https://ampbyexample.com/stories/introduction/amp_story_hello_world/:

Interesting! were you able to debug what is the core reason? A css rule probably being overwritten somewhere?

I'm not sure, I haven't really investigated it, sorry!
But it looks like styles are missing, rather than being overwritten. (In the "bad" case, no font is set and the default font is used.)

It's not just navigation - the font of the whole doc is different on e.g. https://ampbyexample.com/amp-ads/introduction/hello_world/ compared to https://ampbyexample.com/stories/introduction/amp_story_hello_world/

Well, this was straightforward, I should've read the sample code first, it's overring font-family of the <body> tag:
https://github.com/ampproject/amp-by-example/blob/e98f6fb9c8b87c9931fb670c30e80138e5ed4b98/src/stories/10_Introduction/_AMP_Story_Hello_World.html#L23-L25
Same issue with Hotel sample:
https://github.com/ampproject/amp-by-example/blob/a7555868be23f1954ce9c32d55e7141c97d6d83b/src/60_Samples_%2526_Templates/Hotel.html#L54-L56
@ithinkihaveacat do you think we can drop the styling on body or narrow down the selector?

For the hotel sample you can remove the overriding of the font for sure!
On Fri, 13 Jul 2018 at 12:20, Filip Stanis<EMAIL_ADDRESS>wrote:

Well, this was straightforward, I should've read the sample code first,
it's overring font-family of the  tag:
https://github.com/ampproject/amp-by-example/blob/e98f6fb9c8b87c9931fb670c30e80138e5ed4b98/src/stories/10_Introduction/_AMP_Story_Hello_World.html#L23-L25
Same issue with Hotel sample:
https://github.com/ampproject/amp-by-example/blob/a7555868be23f1954ce9c32d55e7141c97d6d83b/src/60_Samples_%2526_Templates/Hotel.html#L54-L56
@ithinkihaveacat https://github.com/ithinkihaveacat do you think we can
drop the styling on body or narrow down the selector?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/amp-by-example/issues/1346#issuecomment-404804830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyGm3x4FGFavGjFGaLR5h9VKqcyAQbiks5uGIJ_gaJpZM4VK_aP
.


Happy Eyeball routines should not call sortAddress() in data path during creating connection

Title: Happy Eyeball routines should not call sortAddress() in data path during creating connection
Description:
Currently happy eyeball routine is calling sortAddress() in data. path when creating connection:
https://github.com/envoyproxy/envoy/blob/c9fb17a6fabd1d2030ce8f5192780e947a335e01/source/common/upstream/upstream_impl.cc#L531
https://github.com/envoyproxy/envoy/blob/c9fb17a6fabd1d2030ce8f5192780e947a335e01/source/common/network/happy_eyeballs_connection_impl.cc#L21
https://github.com/envoyproxy/envoy/blob/c9fb17a6fabd1d2030ce8f5192780e947a335e01/source/common/network/happy_eyeballs_connection_impl.cc#L103
If the address vector is relatively big, and rarely changes, which is normal, then this is very inefficient.
The code should try to sort the address in control plane, like DNS refreshing, when new addresses are added to the host, and store that sorted result in host.  And data plane just use that sorted result.

/assign @RyanTheOptimist @yanavlasov @adisuissa

/wait


loader: Log PIDs of compiler/linker on error

When there's an error, it may be useful for debugging purposes to have
the PID of the compiler and linker processes available. Log them.
I believe that these will be the PID of the shell that executes the commands, so the actual PIDs of the related processes may be off by one or so.

This change is

test-me-please


findDOMNode is deprecated in StrictMode

I am getting this error using CTooltip with @coreui/react 4.10.0 and react 18.2.0
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition2 which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node

After some investigation, it looks like the issue comes from this specific part of the implementation. The CTooltip component is not passing the nodeRef prop as required by the Transition element to not use findDOMNode.
Although I found the cause of the error, I don't have enough knowledge about the project's architecture to open a pull request. Thanks for the support.

@Alan-Gomes fixed. Upgrade @coreui/react 4.10.1


static-marks returns no error when it failed to parse the yml-file

Given the following bookmarks-yaml-file:
test:
  - duckduckgo: https://duckduckgo.com/
    - more duck: https://duckduckgo.com/

static-marks will output an error (which is absolutely fine), but the return value is still '0':

Further information: Within an automatic build, this will result in a html-file containing no links whereas the build just runs fine. This finally results in overwriting a fine version of a page with an empty one.

Thanks for the report!
My reasoning behind this: when multiple files are being used, one malformed file should not prevent the tool from building all other (valid) files. But I am not sure about this decision anymore. I think a stricter handling might indeed outweigh the pros of trying to have a graceful degradation.
The following flow should address the issues:

Keep the current output for every malformed file.
Abort the build command if at least one file is malformed. This includes not overwriting an existing output file (both with -o and >).
Exit with code 1.

If you fear this to be a breaking change, maybe introduce an option "--strict"? This would also fine be me.

Implemented in 2.2.0.

awesome


The one time password is not working

In current develop version, the totp for login is not working. If the username and password is correct and totp's length is 6, it can login whatever totp is.

As explained by @nguyentb this is done in dev environment for convenience, but this applies correctly in production

As explained by @nguyentb this is done in dev environment for convenience, but this applies correctly in production


Urls.py contains wrong value for urlpatterns

Looks like should be     url(r'^fail/?$', views.FailPageView.as_view(), name='kassa_fail') instead of     url(r'^fal/?$', views.FailPageView.as_view(), name='kassa_fail')

What is the difference? We are have not many url's patterns for confuse it, but I'll make this changes

Issue is fixed now.


Fix the hypelink to shimplify.py [skip ci]

Addresses https://github.com/NVIDIA/spark-rapids/issues/7812#issuecomment-1443715623_
Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build


MudDataGrid: Custom comparer

Description
Adds a Comparer property to MudDataGrid and update selection methods

Add Comparer property of type IEqualityComparer<T> to MudDataGrid
Update SetSelectedItemAsync and SetSelectAllAsync methods to use Comparer for row selection
Update Selected property in CellContext to use Comparer for checking if a cell is selected

Resolves #10139
How Has This Been Tested?
Unit test created and test viewer component added
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

LGTM. I will do some manual testing later and merge it.

Thanks


Addition of handling of qualified attribute names.

Attribute names with a colon in the name broke the code; the WriteAttributeString(name, value) verified that the name parameter did not have colon in its name. By handling this with prefixes, this is now supported.
Typically xmlns:xlink="uri to named namespace here" and xlink:type="resource" now works.
Also, a presumed bug was found; a XmlElement was newed up at one place in the code and not assigned to a variable, hence promptly discarded. It is now saved in the element-variable.

Thanks for you request I will review them and merge them


clean, test and lint:types scripts shouldn't be delegated to packages

clean, ``test and lint:types scripts should be handled by the monorepo root scripts instead of being delegated to packages.
Since PNPM is not hoisting packages, it would be expected to add jest and typescript as devDependencies to every package otherwise.
Furthermore, it's repetitive and can be avoided by using pnpm exec.
In the monorepo root scripts you could have:

"test": "jest" and use filters when you want to filter to a specfic packages, file or test with either --ignoreProjects, --testNamePattern, --testPathIgnorePatterns or --testPathPattern
"lint:types": "tsc",
"clean": "pnpm -r --include-workspace-root --parallel exec pnpm dlx rimraf dist node_modules/.cache"

Additionally, packages use the following script: "lint:types": "tsc --noEmit". I don't think --noEmit is still required because our TypeScript configuration are now strictly used for linting purpose and should not emit by default.


Cannot apply filters over computed properties

Using the dummy app, if you try to apply a filter over voteCount on the article resource, it'll fail because it tries to run the filter over the database.

and... what should be the expected behaviour?

We can implement this in two stages, depending on other priorities and needs:

At the very least, don't mislead the user with a confusing error.

A great solution would be to have a native implementation of each comparer to enable the same behaviour databases offer on computed properties.

Since #212, a more expressive and clear error is returned now.


WIP: tfvars files should be ignored during *-all commands if they have no source setting and no .tf file is present

Bit of a fresh GO programmer, but this change should do the trick.  The outstanding issue is that since the test data used is mostly just blank .tfvars files, any attempt to resolve these is now ignored so a ton of tests are failing.  Any advice on how to proceed or comments on the code would be welcome :)
Fix for issue https://github.com/gruntwork-io/terragrunt/issues/208

Hey!  So, I made changes around your recommendations in the code.  The logic looks much cleaner overall now.  Also changed the tests so they don't all get caught by this addition, had to both edit the files in the test/fixture-modules/ directories and the expected values in the tests.  Finally, added a new test case and data in test/fixture-modules/module-l/ to check that a .tfvars file with no Terragrunt block and associated source, and no .tf file in the directory, will be skipped.  All tests are passing locally.
Let me know what you think!

Thank you, merging now!

If the tests pass, the new binaries should show up here soon: https://github.com/gruntwork-io/terragrunt/releases/tag/v0.12.25


[AppCheckCore] Skip local cache when making network requests

All of the URL sessions within used App Check are ephemeral. While they don't write a cache to disk, they do persist one to RAM. Cache policy can be controlled at the NSURLRequest level, and by default, the cache may be read from in some scenarios.
The SDK is intentional about making requests and hitting the cache may cause successive requests to send outdated artifacts. Therefore, we should try setting the cache policy to skip the local cache.

Will do, @paulb777. Will also send a changelog entry update. Does v11.2.0 sound good to you?


Starborn

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
**
starborn (1).zip
**
starborn.zip

P

starborn (1).zip

what

what

Is this a custom pack or something?


Training the tICs instead of the features

I generated 4 tICs from the 4 dihedral features presented in the attached notebook. Now I want to train the tICs to see which tIC is more dominant over the other. And in this regard I want to generate a plot similar like SVM co-efficients vs Feature index mentioned in this notebook https://github.com/msultan/SML_CV/blob/master/alanine_example/01-svm_example.ipynb .
First question:
I tried something like that just substituting the original script a bit to train the tICA features

X=np.vstack(plot_feat)
train_X=np.vstack(tica_features)

y=np.concatenate([np.zeros(len(plot_feat[0])),
            np.ones(len(plot_feat[0]))])

if train:
    clf.fit(train_X,y)

train_X.sum(axis=1)[300:].std()
What is the meaning of this line train_X.sum(axis=1)[300:].std() and the output 2.2081068901447987
The I plotted the tIC0 vs SVM co-efficient using the following script and got an output like following
plot([0,1,2,3],clf.coef_[0],color=sns.color_palette("colorblind")[0],marker='o',label=r'$\alpha_L$ vs $\beta$')
xticks([0,1,2,3],[r'tic0',r'tic1',r'tic2',r'tic3'],size=20)
xlabel("tICs Index")
ylabel(r'$SVM_{cv}$ Coefficients')
legend()

Simple question: How do I get the exact value of SVM coefficient for each tICs. It is a bit hard to see from the plot. Any script?

Simple question: How do I get the exact value of SVM coefficient for each tICs. It is a bit hard to see from the plot. Any script?

I am confused here. Have you tried printing out the coefficients instead of plotting them?

What is the meaning of this line train_X.sum(axis=1)[300:].std() and the output 2.2081068901447987

I was calculating the standard deviation of each feature after summing them together. I am not sure I remember why exactly tbh.


APEXCORE-785 Cleanup unit tests log4j.properties (Review only)

@PramodSSImmaneni @tweise Please review.

retest this please

Jenkins retest this please

test this please

SUCCESS
--none--

@PramodSSImmaneni Please review and merge

Will look into it soon

@PramodSSImmaneni rebased, please merge.

@PramodSSImmaneni Please update JIRA.


New version: Unity.Unity.2023 version 2023.2.9f1

This pull request is automatically generated by 🥟 Dumplings in #3337
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run


about msf localization mode

I met a problem when I tried to get the dataset mentioned in this howto: [(https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_run_MSF_localization_module_on_your_local_computer.md)]
I want to konw where I can get the dataset.
Thanks a lot !

@HongweiSunny if you are within the US, you can follow the steps mentioned on the document. If you aren't currently in the US, we do not provide a sample data set.


Fix use cases and add new use cases

Please check if anything needs change apart from the indexing of use cases

Codecov Report

Merging #255 (3e1fd0c) into master (33520f1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #255   +/-   ##
=========================================
  Coverage     78.78%   78.78%
  Complexity     1346     1346
=========================================
  Files           167      167
  Lines          3860     3860
  Branches        515      515
=========================================
  Hits           3041     3041
  Misses          673      673
  Partials        146      146

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 33520f1...3e1fd0c. Read the comment docs.

Can check using this https://pbthang.github.io/tp/DeveloperGuide.html#use-cases


App crashes after adding GoogleTagManager to project which is using Firebase Analytics

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.3.1
Firebase SDK version: 6.3.2
Firebase Component: GoogleTagManager
Component version: 7.1.2
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
I have project using Firebase Analytics. I have added Google Tag manager pod. Then, after I add GTM container to the project it crashes at start.

2020-03-11 08:37:53.405384+0100 10min4beauty[4002:72827] GoogleTagManager info: Loading container: GTM-TJXGVQQ

2020-03-11 08:37:53.406936+0100 10min4beauty[4002:72857] GoogleTagManager info: Attempting to load container GTM-TJXGVQQ from network
2020-03-11 08:37:54.004787+0100 10min4beauty[4002:72819] GoogleTagManager info: Processing logged event: gtm.load with parameters: (null)
2020-03-11 08:37:54.008475+0100 10min4beauty[4002:72819] GoogleTagManager info: Processing logged event: _vs with parameters: {
"_o" = auto;
"_sc" = UIViewController;
"_si" = "-6942184988013378461";
}
2020-03-11 08:37:54.023672+0100 10min4beauty[4002:72819] GoogleTagManager info: Sending universal analytics hit: {
"&t" = screenview;
"&tid" =     {
collectAdid = 0;
enableFirebaseEcommerce = 0;
enableRecaptchaOption = 0;
enableUaRlsa = 0;
enableUseInternalVersion = 0;
trackingId = "UA-148523509-1";
};
}
2020-03-11 08:37:54.024196+0100 10min4beauty[4002:72819] GoogleTagManager info: Processing logged event: _vs with parameters: {
"_o" = auto;
"_sc" = UIAlertController;
"_si" = "-8014389997127696758";
}
2020-03-11 08:37:54.027343+0100 10min4beauty[4002:72924] [error] fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
2020-03-11 08:37:54.027525+0100 10min4beauty[4002:72924] [error] CoreData: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
CoreData: warning: Property 'parameters' on Entity 'GAIHit' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
2020-03-11 08:37:54.039587+0100 10min4beauty[4002:72924] -[__NSDictionaryM length]: unrecognized selector sent to instance 0x600000495ae0
2020-03-11 08:37:54.041398+0100 10min4beauty[4002:72819] GoogleTagManager info: Sending universal analytics hit: {
"&t" = screenview;
"&tid" =     {
collectAdid = 0;
enableFirebaseEcommerce = 0;
enableRecaptchaOption = 0;
enableUaRlsa = 0;
enableUseInternalVersion = 0;
trackingId = "UA-148523509-1";
};
}
2020-03-11 08:37:54.060328+0100 10min4beauty[4002:72924] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSDictionaryM length]: unrecognized selector sent to instance 0x600000495ae0'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff23c7127e __exceptionPreprocess + 350
1   libobjc.A.dylib                     0x00007fff513fbb20 objc_exception_throw + 48
2   CoreFoundation                      0x00007fff23c91fd4 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
3   CoreFoundation                      0x00007fff23c75c4c forwarding + 1436
4   CoreFoundation                      0x00007fff23c77f78 _CF_forwarding_prep_0 + 120
5   10min4beauty                        0x000000010cc2b61f -[GAIBatchingDispatcher queueDispatch:] + 385
6   10min4beauty                        0x000000010cc2b484 -[GAIBatchingDispatcher queueModel:] + 125
7   Foundation                          0x00007fff25781c30 __NSThreadPerformPerform + 259
8   CoreFoundation                      0x00007fff23bd4471 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
9   CoreFoundation                      0x00007fff23bd439c __CFRunLoopDoSource0 + 76
10  CoreFoundation                      0x00007fff23bd3b74 __CFRunLoopDoSources0 + 180
11  CoreFoundation                      0x00007fff23bce87f __CFRunLoopRun + 1263
12  CoreFoundation                      0x00007fff23bce066 CFRunLoopRunSpecific + 438
13  Foundation                          0x00007fff2576b86f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 211
14  Foundation                          0x00007fff2576ba87 -[NSRunLoop(NSRunLoop) run] + 76
15  10min4beauty                        0x000000010cc18d59 +[GAI threadMain:] + 62
16  Foundation                          0x00007fff257817a7 NSThread__start + 1047
17  libsystem_pthread.dylib             0x00007fff52466e65 _pthread_start + 148
18  libsystem_pthread.dylib             0x00007fff5246283b thread_start + 15
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Steps to reproduce:

Run the app
Crash

What am I missing? Looks like everything should work fine.
Thanks for help

Thanks for the report. I'm not sure if this will make a difference or not at the moment but can you please update to the latest Firebase SDKs and see if that helps? 6.19.0 was just released yesterday. If it's still causing issues we can take another look!

Also GoogleTagManager 7.1.3 has been recently released.

Thanks for the report. I'm not sure if this will make a difference or not at the moment but can you please update to the latest Firebase SDKs and see if that helps? 6.19.0 was just released yesterday. If it's still causing issues we can take another look!
Also GoogleTagManager 7.1.3 has been recently released.

I have updated Firebase SDKs to 6.19.0 and GoogleTagManager to 7.1.3. Still same issue.

This is a duplicate of #200. There aren't any Firebase symbols in the crashing stack trace, so please file feedback at the Google Analytics tracker instead: https://issuetracker.google.com/issues?q=componentid:187400


Implement 2^k for FieldElement

Since we are working on the implementation of McIvor, Corinne & Mcloone, Maire & Mccanny, J.V.. (2004). Improved Montgomery modular inverse algorithm. Electronics Letters. 40. 1110 - 1112. 10.1049/el:20045610.
We realized on #9 that we needed to implement the operation 2^k for FieldElement where k is a u64 on the range: 0 .. 253.
Once this is done, we will be able to conclude the implementation started on: 457ef6e

I'm gonna go for a simple and working version of it, we can once #9 is closed, think on most performant ways of implementing it.

The function was corrected and successfully tested on 2a563d3 .
Now we can go for #9 .
The should perform fast enough, anyways, we can search for more performant implementations once #9 is solved.


google cloud spanner is closing connection

I running my api based on swagger and node.
When my api is running for few minutes without a request and then i send an api request to it, I got this error:
{ Error: {"created":"@1488097564.272436000","description":"Delayed close due to in-progress write","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":406,"grpc_status":14,"referenced_errors":[{"created":"@1488097564.272434000","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"occurred_during_write":1,"referenced_errors":[{"created":"@1488097564.272350000","description":"Secure read failed","file":"../src/core/lib/security/transport/secure_endpoint.c","file_line":166,"referenced_errors":[{"created":"@1488097564.272347000","description":"Socket closed","fd":24,"file":"../src/core/lib/iomgr/tcp_posix.c","file_line":249,"target_address":"ipv4:<IP_ADDRESS>:443"}]}]}]}
    at ClientReadableStream._emitStatusIfDone (/Users/aronsuarez/Code/asate/admin-apis/wiki-admin-api/node_modules/grpc/src/node/src/client.js:201:19)
    at ClientReadableStream._readsDone (/Users/aronsuarez/Code/asate/admin-apis/wiki-admin-api/node_modules/grpc/src/node/src/client.js:169:8)
    at readCallback (/Users/aronsuarez/Code/asate/admin-apis/wiki-admin-api/node_modules/grpc/src/node/src/client.js:242:12) code: 14, metadata: Metadata { _internal_repr: {} } }

I think google spanner is closing the connection, why and how can prevent it from to that?
The only way that i see in the docs is to send periodically a SELECT 1 request to spanner.
Is this correct?
System Info:
node. 6.10.0
os: macOS latest
package: latest
Thanks for help

You should not need to periodically sent Select 1 to spanner. This seems like underlying socket closing.
@callmehiphop @stephenplusplus Any ideas whats going on here.

Possibly related to https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2039

@murgatroid99 any ideas about grpc options in this situation?

Any updates on this?

Actually, we just released gRPC 1.2.0, which should fix this problem

Closing as fixed in GRPC.

I have tested with the "@google-cloud/spanner" - 0.1.2 package and it dosen't work. This is the error
(node:74588) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: {"created":"@1490192388.326156000","description":"Transport closed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1072}

What version of GRPC do you have installed?

How can i check this, i have only installed the spanner package for node.

npm list | grep grpc

Version 1.1.2, this is the problem, i think this is installed with the spanner package correct?

The Spanner package uses ^ to tag its dependencies; grpc is a dependency of<EMAIL_ADDRESS>and a new install correctly installs grpc 1.2.0.
Basically: Update your dependencies. :-)


VideoKit 0.0.15 crashes on launch in Windows Release build

Getting ready to release with VideoKit 0.0.15 integrated for the first time.
- VideoKit is working perfectly on Windows in the Unity Editor 2021.3.31f.

- I have loaded my access key in the Preferences

- In a Windows release build, I receive the following error in the log, and VideoKit 0.0.15 does not function in either Mono or IL2CPP builds for me when running on Windows 11:

Uploading Crash Report
NullReferenceException: Object reference not set to an instance of an object.
at VideoKit.Internal.VideoKitSettings.CheckSession () [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[TResult].Start[TStateMachine] (TStateMachine& stateMachine) [0x00000] in <00000000000000000000000000000000>:0
at VideoKit.Internal.VideoKitSettings.CheckSession () [0x00000] in <00000000000000000000000000000000>:0
at VideoKit.Internal.VideoKitSettings.Awake () [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x00000] in <00000000000000000000000000000000>:0
at VideoKit.Internal.VideoKitSettings.Awake () [0x00000] in <00000000000000000000000000000000>:0
--- End of stack trace from previous location where exception was thrown ---
at VideoKit.Internal.VideoKitSettings.Awake () [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x00000] in <00000000000000000000000000000000>:0
at VideoKit.Internal.VideoKitSettings.Awake () [0x00000] in <00000000000000000000000000000000>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__7_0 (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.UnitySynchronizationContext.Exec () [0x00000] in <00000000000000000000000000000000>:0

Just tested running the camera to a Camera View on an empty URP project release build.
Works fine.
So the issue could be project related - I wonder if it could have anything to do with the fact that my repository on Windows was cloned from git?

I tried to replicate the set up of VideoKit in my app's scene in the test scene exactly...  Can't get the test scene to throw the error in the release build.
Can't possibly think of what would cause this in my app's release build...
I really hope you may possibly have a solution on Monday...
Thank you

Fix confirmed and coming in 0.0.16.

Fixed in VideoKit 0.0.16.


handleUncaughtError called twice if Future has two listeners

If you have a Future with two listeners that completes with an error inside a Zone with a handleUncaughtError handler, the handler gets called twice.
import 'dart:async';

Future<Null> test() async {
  throw 'error';
}

void main() {
  Zone zone = Zone.current.fork(
    specification: new ZoneSpecification(
      handleUncaughtError: (Zone self, ZoneDelegate parent, Zone zone, dynamic error, StackTrace stackTrace) {
        print('handleUncaughtError called');
      }
    )
  );
  zone.run(() {
    Future<Null> f = test();
    f.whenComplete(() { });
    f.whenComplete(() { });
  });
}

@iposva-google suggested that I should cc @floitschG on this.

Yes. That's working as intended.
When you have two listeners on a future, you create two new futures which are completed with the result of the listener. That means that the  error effectively gets split into two independent errors in two separate futures. So you have to catch both to avoid having an uncaught error, and that's also why you get two uncaught errors if you don't catch either of them. You still only get one error per future that completes with an error without having any listeners (at the time of the completion - adding one later doesn't go back and prevent the error from being uncaught, which is why you should add listeners soon after creating the future).
Write your code as:
Future<Null> f = test();
Future f1 = f.whenComplete((){});
Future f2 = f.whenComplete((){});

and it might be easier to see why that both f1 and f2 complete with unhandled errors. If you rewrite as:
Future<Null> f = test();
Future f1 = f.whenComplete((){});
Future f2 = f1.whenComplete((){});  // <-- chainining instead of parallelizing.

then you only have one unhandled error.
In general, it's a good idea to only have one listener on a future, if at all possible. Makes everything so much simpler. If you use async/await syntax, that very easily becomes the default way of writing things - awaiting the same future twice really stands out as silly since you can just bind the result to a variable the first time.

The unhandled error is in f, not in f1 or f2. Having it reported twice just leads to bad output when I print the error in the unhandled error handler. I don't have any control over how many handlers the chain of futures has -- it could easily be dozens. That's all in user code.
What should I do instead? Cache pointers to all the reported exceptions and only report them if I haven't seen them before?
Is there some way to mark the error as "handled" for all branches?
(This bug is visible e.g. in the test harness. The test harness dumps the exception from an uncaught error handler on the zone for the test. If the test is async and the returned future is part of a tree of future handling, it can easily end up dumping the same error multiple times.)

The unhandled error is most certainly in both f1 and f2. You can see that if you later add a catch handler to either f1 or f2, that catch handler will see the error. Example:
import "dart:async";
main() {
  runZoned(() async {
    var f = new Future.error("BAD");
    var f1 = f.whenComplete(() {});
    await new Future.delayed(const Duration(seconds: 2), (){});
    var f2 = f.whenComplete(() {});
    await new Future.delayed(const Duration(seconds: 2), (){});
    f1.catchError((e) { print("f1: $e"); });
    f2.catchError((e) { print("f2: $e"); });
  }, onError: (e) {
    print("Zone uncaught: $e");
  });
}

I guess I'll make my exception handler catch all the exceptions and compare them before reporting them. Thanks for the explanation.


Lenovo devices correctly selecting driver package but not applying.

I've been battling with some Lenovo laptops which have not been having drivers applied to them successfully using the Invoke-CMApplyDriverPackage.ps1 script. The "ApplyDriverPackage.log" file shows the following:
[ApplyDriverPackage]: Apply Driver Package process initiated	ApplyDriverPackage	26/01/2022 15:43:01	952 (0x03B8)

Apply driver package deployment type: BareMetal	ApplyDriverPackage	26/01/2022 15:43:01	952 (0x03B8)
Apply driver package operational mode: Production	ApplyDriverPackage	26/01/2022 15:43:01	952 (0x03B8)
[PrerequisiteChecker]: Starting environment prerequisite checker	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Supported computer platform detected, script execution allowed to continue	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer manufacturer determined as: Lenovo	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer model determined as: ThinkPad T14s Gen 2i	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer SystemSKU determined as: 20WM	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer model detection was successful	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer SystemSKU detection was successful	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Computer details successfully verified	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Determined primary computer detection method: SystemSKU	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
[PrerequisiteChecker]: Completed environment prerequisite checker	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
[AdminService]: Starting AdminService endpoint phase	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Detected that script was running within a task sequence in WinPE phase, automatically configuring AdminService endpoint type	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Determined AdminService endpoint type as: Internal	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Successfully read service account user name from TS environment variable 'MDMUserName': ea*v*_mn*a	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Successfully read service account password from TS environment variable 'MDMPassword': ********	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Setting 'AdminServiceURL' variable to: https://FQDN.local/AdminService/wmi	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
[AdminService]: Completed AdminService endpoint phase	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
[DriverPackage]: Starting driver package retrieval using method: AdminService	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Querying AdminService for driver package instances	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
Calling AdminService endpoint with URI: https://FQDN.local/AdminService/wmi/SMS_Package?$filter=contains(Name,'Drivers')	ApplyDriverPackage	26/01/2022 15:43:02	952 (0x03B8)
The remote AdminService endpoint certificate is invalid according to the validation procedure. Error message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.	ApplyDriverPackage	26/01/2022 15:43:03	952 (0x03B8)
Will attempt to set the current session to ignore self-signed certificates and retry AdminService endpoint connection	ApplyDriverPackage	26/01/2022 15:43:03	952 (0x03B8)
Retrieved a total of '4' driver packages from AdminService matching operational mode: Production	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Target operating system name configured as: Windows 10	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Target operating system architecture configured as: x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Target operating system version configured as: 21H1	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage]: Starting driver package matching phase	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Initial count of driver packages before starting filtering process: 4	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Filtering driver package results to detected computer manufacturer: Lenovo	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Count of driver packages after filter processing: 4	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Filtering driver package results to only include packages that have details added to the description field	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Count of driver packages after filter processing: 4	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100056]: Processing driver package with 4 detection methods: Drivers - Lenovo ThinkPad T14S Gen 2 Type 20WM 20WN - Windows 10 21H1 x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Matched SystemSKU: 20WM	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Matched operating system name: Windows 10	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Matched operating system architecture: x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Matched operating system version: 21H1	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100056]: Driver package was created on: 2022-01-26T13:47:22Z	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100056]: Match found between driver package and computer for 4/4 checks, adding to list for post-processing of matched driver packages	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100057]: Processing driver package with 4 detection methods: Drivers - Lenovo ThinkPad T14 Gen 2 Type 20W0 20W1 - Windows 10 21H1 x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100054]: Processing driver package with 4 detection methods: Drivers - Lenovo ThinkPad T480S Type 20L7 20L8 - Windows 10 21H1 x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage:P0100055]: Processing driver package with 4 detection methods: Drivers - Lenovo ThinkPad T470S - Windows 10 21H1 x64	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackage]: Completed driver package matching phase	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackageValidation]: Starting driver package validation phase	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Amount of driver packages detected by validation process: 1	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
Successfully completed validation with a single driver package, script execution is allowed to continue	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackageValidation]: Completed driver package validation phase	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[DriverPackageFallback]: Starting fallback driver package detection phase	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)
[ApplyDriverPackage]: Apply Driver Package process failed, please refer to previous error or warning messages	ApplyDriverPackage	26/01/2022 15:43:05	952 (0x03B8)

I cannot see any previous error or warning messages which would relate to this failing. Any ideas why this could be failing to apply?
Thanks

Add this to the catch [System.Exception] block on line 2323.
Write-CMLogEntry -Value "[ApplyDriverPackage]: Dumping last error $Error[0].Exception.Message" -Severity 3
Update the content and try to run your task sequence again.

i was going to also add that line but the 4.2.0 script only goes to line 2293, where in teh new code should it go?

think i found the spot, line 2280.


Change the default folder that plugins are found in for consistency

Godot version:
3.0 Stable
OS/device including version:
Windows 10
Issue description:
Currently, plugins are found inside of the 'addons' folder. This is inconsistent with the name of the tab 'Plugins' in project settings menu. It would be great to rename one or the other in order to keep things consistent. Even better would be to be able to define a custom location for where plugins are found.
Steps to reproduce:
Try to add plugins into any other folder than 'addons' and they won't be found.

Related #4279

Note: We consider that not all add-ons are plugins, so the current name is most likely fine as it is. (This is because we recommend containing third-party resources into an addons/ folder, even if they're not editor plugins.)

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!

@Calinou Please reopen this, my main issue is this...
I am using C# and C# requires that files names are the same as class names...
but then my scripts start with a capital letter and my folder's don't...
unless I capitalize my folder's first letter but then plugin's folder name is hard coded.


Generated Powershell client case sensitivity

The current behaviour for the generated Powershell client is to have case sensitive object property names.
For example, if the swagger spec defines a title cased property in an object, the property will be ignored if the returned object has property names in camel case (or any other unexpected case).
Is this expected behaviour?

@jeremy-collette Would you please provide a sample swagger file?

@jeremy-collette - did you get a solution for this? I'm hitting the same issue.

@imjuststeve From memory I changed the casing of the swagger spec as a workaround

It looks like an issue of swagger.


Auto-closing quotes are doubled-up when user closes manually

In the playground UI, a closing quote is automatically added when the user begins a string literal. When they eventually get to the end, manually typing the closing quote causes the editor to skip over the auto-inserted one, completing the string.
In the new embed UI, however, if the user manually closes the string, CodeMirror acts as if they're starting a new literal, and inserts another pair of quotes.
There is likely to be some setting in use in the playground UI that just needs to be moved over.
Original user report:

The first code example, when you type a quote (") it auto inserts the closing quote, so you get "". If you then type out the string and manually type the closing quote (instead of removing your hands from the home keys to press arrow keys to get past the auto-inserted closing quote) then it inserts another two quotes.
If you just type out the line: 'return "$x $y";' in the editor without doing anything, you end up actually getting this: 'return "$x $y";""'
It would be preferable if, when the cursor is to the left of a quote (assuming LTR language) and the previous character is not an escape character that typing a quote just moves the cursor to the right of the existing quote without adding any characters.

OK, narrowed this down a little more.
This bug is caused when an interpolated variable followed by 0 or more whitespace characters is the last part of the string.
Thing strings "$x $y" and "$x $y   " will have the issue with typing the last " inserting another double quote, but the string "$x $y a" will work as expected.

The latest implementation of the playground and embed layout are now shared and it seems a second closing quote is not introduced in either layout.
If anyone is still experiencing this though, please open a new issue with reproduction and device/browser details. Thanks so much!


Tablet no longer maps to area correctly

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 494b9415a1157279a1e1782ba635fc2ef6a18155  (layersurface: avoid restack on identical layers).
Tag: v0.40.0-62-g494b9415, commits: 4668

flags: (if any)

System Information:
System name: Linux
Release: 6.8.9-273-tkg-eevdf-llvm
Version: #1 SMP PREEMPT_DYNAMIC TKG

GPU information:
0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c5) (prog-if 00 [VGA controller])

Bug or Regression?
Regression
Description
Caused by #5902 I'm assuming.
Tablet area and display area in OpenTabletDriver no longer map correctly, neither the tablet area or display area seem to work correctly.
Possible reason this might not have been reported in the PR is that I'm using two displays?
Crash reports, logs, images, videos
Video showing cursor stopping near the middle of the screen:
https://github.com/hyprwm/Hyprland/assets/58333920/450745f4-41ec-4898-a879-1fdd1cdccb0e
Screenshot of the display area in OpenTabletDriver:

Yeah, I can replicate. Hyprland ignores what opentabletdriver is mapped to and automatically maps to the display your cursor is on. You can leave the opentabletdriver mapping to default (whole area) and Hyprland will do it's thing. You can set which monitor to map your tablet to in input:tablet:output=

Hyprland ignores what opentabletdriver is mapped to

Is this the way planned forward or just an oversight? I don't think that ignoring the drivers configuration is the best way of handling multiple displays?

"Be the change you want to see". I'll look at the code and see if there's a better way to manage this (add a config maybe?). Stock behaviour has definitely changed from before #5902 and vaxry doesn't even have a tablet to test with :stuck_out_tongue_closed_eyes:

correct, I don't

I have the same problem with two monitors. A weird thing worth mentioning is that I don't know if it's related to this issue or should be in another issue, but it seems like my monitors are placed at weird coordinates.
Running hyprctl monitors will give:
Monitor HDMI-A-1 (ID 0):
<EMAIL_ADDRESS>at 0x0
	...

Monitor HDMI-A-2 (ID 1):
<EMAIL_ADDRESS>at -1920x0
	....

I'm using the new auto positions introduced in #5670
monitor=HDMI-A-1,1920x1080@74.97Hz,auto,1
monitor=HDMI-A-2,preferred,auto-left,1

Apparently this is an open issue on the OpenTabletDriver github issue tracker concerning this behaviour in KDE Plasma as well. :thinking: They describe the workaround being to let the compositor decide how to map things just like I've said here https://github.com/hyprwm/Hyprland/issues/6023#issuecomment-2105995314. I've been having my fair share of obscure bugs with OTD so I don't know if it's even worth trying. Mapping in the driver is broken on wayland compositors that automatically map to monitors by default (Kwin, Hyprland, etc) and the behaviour of the mapping isn't even consistent on the different modes that OTD offers.

I would still think having an option would be a preferable? Breaking configuration compatibility which works nearly everywhere else OOTB is probably not the best option in my opinion, especially when "nearly everywhere" includes other operating systems. If an option is off the table then makes more sense to me to control externally managed drivers such as OTD on their driver and to have those built into hyprland (libwacom?) to be configured in the configuration file? It just leads to less problems on the users side in my eyes.

libwacom and digimend-kernel-drivers are the gold standard for graphics tablet support across the Linux landscape. OTD seems to be having some trouble with wayland support in regards to their own driver implementation, I'd wait until they fix up their many issues regarding mapping on wayland compositors in general (they have an issue on Gnome monitor mapping as well if you look through their issue tracker). The previous behaviour was at best undocumented (I didn't even have a tablet back then).

I agree that it would be nice to have the option but I can't seem to make use of OTD without encountering some serious driver issues when iterating so I won't be continuing the debugging process on my end.

Tablet is being restricted to output only on monitor currently focused on, even when set to unbound.
It should instead be that the tablet maps to the entire layout of all active outputs. This matches the behavior of other desktops (xorg, kde, gnome, sway, hyprland <= 0.40.0)

This is the issue I made before being directed to this issue. I discovered this issue trying to play vr and use wlx-overlay-s, and was told:

i'd make a ticket that the absolute pointer input should by default be mapped like on other desktops (xorg, kde, gnome). to the rectangle that encapsulates all screens

Would that fall under this issue or should it be its own?

@Stoppedpuma check out #7586


[ISSUE] Clusters listing not working

Description
The Paginator for Clusters (and other APIs) never ends when iterated over.
The reason is the line if (token == null) { in api.java.tmpl. It should be if ("".equals(token)) { instead. According to the REST documentation (and my experiments) the last page has next page token equal to empty string.
Reproduction
@Slf4j
class DatabricksErrorTest {

  @Test
  void testNotWorking() {
    DatabricksConfig config =
        new DatabricksConfig()
            .setHost("xxx.azuredatabricks.net")
            .setToken("mytoken");

    WorkspaceClient workspace = new WorkspaceClient(config);
    Iterable<ClusterDetails> clusterDetails = workspace.clusters().list(new ListClustersRequest());
    int iteration = 0;
    for (ClusterDetails clusterDetail : clusterDetails) {
      // This prints forever and the application never ends. It loops over the clusters over and over again.
      log.info("Iteration {}", iteration++);
    }
  }
}

Expected behavior
The Iterable should iterate over every catalog once and let the program continue instead of iterating again.
Is it a regression?
It used to work on 0.4.0 but it was long time ago (when the SDK didn't use Paginator)
Debug Logs
Not important
Other Information

OS: macOS
Version: 0.30.0

Additional context
No

I could fix it but I don't know what tool I should use to regenerate the classes. If someone could teach me, then I can do it.

@mgyucht Maybe you can instruct me how to regenerate the classes? I know the generator can be found in https://github.com/databricks/databricks-sdk-go/blob/main/openapi/gen/main.go, but can't find the OpenAPI document for Databricks API. There used to be possibility to download it from Databricks API Reference, but it seems gone.

Hi @arturowczarek
Thanks for raising this.
The OpenAPI documentation and the generator are not public (https://github.com/databricks/databricks-sdk-go/blob/main/openapi/gen/main.go is only a part of it).
I have opened a PR to fix this
https://github.com/databricks/databricks-sdk-java/pull/343


fix: "Remove member" modal should display the right message when the removed user is not approver

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/45510
PROPOSAL: https://github.com/Expensify/App/issues/45510#issuecomment-2231632139
Tests

Go to staging.new.expensify.com
Create a new workspace/ Open an existing workspace
Go to workspace settings > Members
Add some members
Click on any member
Click Remove from workspace

[x] Verify that the modal displays 'Are you sure you want to remove userEmail'
[x] Verify that the modal doesn't display 'User is an approver in this workspace. When you unshare this workspace with them, we’ll replace them in the approval workflow with the workspace owner'
[x] Verify that no errors appear in the JS console

Note: If you try to remove an approver, you won't see a message saying 'User is an approver'. This because there is a known issue that members details page is not getting the correct approver role for a user.
Offline tests

Same as Test steps.
QA Steps

Same as Test steps.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/3f1a57dd-8e56-43e2-ab01-5a1dbb3ea87d

Android: mWeb Chrome

https://github.com/user-attachments/assets/94efba9d-fdd2-41bc-80f0-4099d27e6e5f

iOS: Native

https://github.com/user-attachments/assets/35072749-2aee-4088-9501-4380920d1d63

iOS: mWeb Safari

https://github.com/user-attachments/assets/e4aca5d6-33e4-4976-8762-8f5769904327

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/ff7a7264-9103-43bb-841d-ae58ae78ae16

MacOS: Desktop

https://github.com/user-attachments/assets/f44e23e0-be5b-42af-a6dc-faa70103a579

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/francoisl in version: 9.0.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/francoisl in version: 9.0.13-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Git Graph not working on

Does this issue occur when all extensions are disabled?: Yes
The only extension installed is Git Graph. Git Graph broken in the standard VSCode install and I wanted to try if this was fixed in the insider version, but no luck :-(

VS Code Version: 1.60.0-insider
OS Version: Windows 10 Enterprise 10.0.19042 Build 19042

Steps to Reproduce:

Install VSCode insider
Install Git Graph extension
Open extension on repository

/causedByExtension


activeClass doesn't override itemClass?

When I use:
itemClass: "text-muted",
and then add:
activeClass: ["bg-primary", "text-white"],
The text inside bg-primary is still muted, not white ...

that is expected, text-muted add this .text-muted {
--bs-text-opacity: 1;
color: var(--bs-secondary-color)!important;
}
and therefore, it's not white
activeClass is added on top of the itemClass

closing this, let me know if you need further help


[SPARK-42190][K8S][FOLLOWUP] Fix to use the user-given number of threads

What changes were proposed in this pull request?
This is a follow-up PR to fix to use the user-given number of threads.
Why are the changes needed?
Previously, it always uses 1 core due to this bug.
After this fix, the users can see.
23/01/27 08:42:45 INFO KubernetesClusterManager: Running Spark with local[10]

Does this PR introduce any user-facing change?
No. This is not released yet.
How was this patch tested?
Pass the CI with newly added test case.

Could you review this follow-up, @viirya and @HyukjinKwon ?

Thank you so much, @HyukjinKwon !
All tests passed. Merged to master/3.4.

Thank you, @viirya .


want to improve the footer section using different hover and box sadow properties

which I observe there are some issues in the footer section

I would like to add Box shadow and different hover effects in the Given (card) and social media icons  button so that it looks more attractive and change the color whenever the cursor moves there.
Pls add GSSOC EXTD'24 and HACKTOBERFEST Badge and level .
@codervivek5
Thank you, looking forward to contribute .

@codervivek5  pls assign appropriate  level .

Hi @codervivek5 I would like to work on this issue. Please assign me this issue

I would like to work on it. I have worked on such effects at Reimagine 2024 competition. Could you assign this issue to me?


feature support ip functions named ipv4_to_ipv6 and cut_ipv6

Proposed changes
Issue Number: close #xxx

ipv4_to_ipv6: accept an IPv4 type address and return the converted IPv6 type address.
cut_ipv6: accept an IPv6 type address and return a string containing the address of the specified number of bytes removed in text format.
improve ut framework to support parsing of IPv4 and IPv6 types.
add some uts and regression tests for these two functions.

run buildall

run p0

run p0

run p0

run buildall

run buildall


Stable Diffusion?

What are your thoughts on adding stable diffusion image generation to the bot?

What service would you want stable diffusion to be served with ? bc idk if you are missunderstanding with dalle which is served by openAI. Stable diffusion is an open source image generation model, it can be served from many services but not from openAI
Talking about dalle, I had a working PR for image generation hanging for some time: https://github.com/karfly/chatgpt_telegram_bot/pull/111

DALLE-2 will be added soon


M00-LAB03: Duplicate instructions

Contact Details
<EMAIL_ADDRESS>What happened?
Exercise : 01
Task: 00
Step: 00
Description of issue: Duplicate instructions
The entire first exercise of the lab is the same as in lab 2. This can't be repeated and a note should be made that it's a continuation from the previous lab.
Lab
Lab 03 Version controlling with Git in Azure Repos
Relevant screenshots
The entire first exercise of the lab is the same as in lab 2. This can't be repeated and a note should be made that it's a continuation from the previous lab.
Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

each lab is designed to be completely independent.
On this one, there is a warning if you want to make it a continuation on previous one:


Inconsistency between code and comment

In auto-palette/src/math/number.rs, the comment Panics if min is greater than or equal to max indicates that the constraint is min < max while the code check min <= max.
/// # Panics
/// Panics if `min` is greater than or equal to `max`.
#[inline]
#[must_use]
pub fn normalize<T>(value: T, min: T, max: T) -> T
where
    T: FloatNumber,
{
    debug_assert!(min <= max, "min must be less than or equal to max");
    (value - min) / (max - min)
}

This issue is fixed in the commit.


New Gambit and Gerbil releases

Motivation for this change
Significant upstream update.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@7c6f434c would you be interested in merging this PR ?

I do not always pay enough attention not to miss anything… Thanks for the reminder.