sync/map: misleading documentation about the map.LoadOrStore functions

What version of Go are you using (go version)?

$ go version
1.20.1

Does this issue reproduce with the latest release?
Yep
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

Not super relevant, this is an issue with the documentation
What did you do?

What did you expect to see?
The documentation for LoadOrStore says the following:

LoadOrStore returns the existing value for the key if present. Otherwise, it stores and returns the given value.
The loaded result is true if the value was loaded, false if stored.

However, this is very misleading: while TECHNICALLY this is correct, it's very easy to understand it backwards. look at this test:
func Test(t *testing.T) {
   exampleMap := new(sync.Map)
   val, x := policyEnablement.LoadOrStore("key1", true)
   fmt.Println(val, x)
   val, x = policyEnablement.LoadOrStore("key1", false)
   fmt.Println(val, x)
}

The output is:
=== RUN   Test
true false // <--------- "false if stored"
true true  // <--------- "true if the value was loaded"

I think that clarifying the documentation with slightly more verbose explanation would help.
What did you see instead?

It looks correct, "loaded" refers to the return value named "loaded".
The backwards interpretation doesn't really make any sense.


I can't open  https://github.com/yourusername/Ultra-Fast-Lane-Detection.git.

Dear rusano,
I can't open  https://github.com/yourusername/Ultra-Fast-Lane-Detection.git.Can you offer a new repositories included your codes?
Thank you .

Thank you for paying attention to my repository. This is actually my mistake in the README file. I'll fix it right now.
My repository URL is: https://github.com/rusano1612/Ultra-Fast-Lane-Detection-Carla-Implementation
You can clone it with this command:
git clone https://github.com/rusano1612/Ultra-Fast-Lane-Detection-Carla-Implementation.git
About my UFLD repository, I dropped it a while ago. But if there's any problem with it, you can tell me, and I'll fix it when I have time.
Hope this information helps you.

UFLD has two version, v1 and v2.     I want to know which version you used.    Can you offer your pretraining-model to me?
Thank you.

This repository was adapted from the v1 of UFLD (https://github.com/cfzd/Ultra-Fast-Lane-Detection.
As for the pretrained model. Since I dropped this project long ago, I've deleted it. So, I can't send you the model. You can combine the original codes and my codes to train the model again.
Hope this can help you.

This repository was adapted from the v1 of UFLD (https://github.com/cfzd/Ultra-Fast-Lane-Detection.
As for the pretrained model. Since I dropped this project long ago, I've deleted it. So, I can't send you the model. You can combine the original codes and my codes to train the model again.
Hope this can help you.

OK,thank you

Can you tell me how to generate carla dataset?


Not working for Public IP(GPRS Time attendance Machines)

Hi , Im using thease Libray file and LAN connected machine and its works fine.but when i try to connect to GPRS mobile machine via its Public Ip i cant connect. Please give me a answer

i have same issue, please give me detail guide

I can connect through public ip but it only works with port 80, whenever i change the different port or close port 80, i cannot connect the fingerprint

I can connect through public ip but it only works with port 80, whenever i change the different port or close port 80, i cannot connect the fingerprint

can we connect with out public ip at server ?

Hi,
Please, Could you let me know if there is any update of the TAD-PHP libraries?
How I can connect a ZK device through Public IP?
Thank you in advance


Intermittent GLib-CRITICAL crashes

Hi, I'm looking into using sharp in production for my company's image renderer. I'm able to regularly reproduce a (sharp:46231): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed crash that kills everything.
Environment is a MacBook Pro w/ manual homebrew install and the latest Node 0.10.x. Code is literally just sharp(path).toFormat(...).toBuffer(...) running in cluster workers. Four workers run at once, each processing one image at a time. Running this at high load for less than a minute always causes this crash.
The scary part is it doesn't just crash the workers, it crashes the entire master process...

Hi Teddy, the GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed message is most likely to be a symptom rather than a cause. Kill any node process whilst one or more libvips' threads are still processing an image and you'll see it.

"Four workers run at once, each processing one image at a time."

Each worker will process process.env.UV_THREADPOOL_SIZE (default=4) images at a time. Every image being processed spawns nCPU threads. https://github.com/lovell/sharp#sharpconcurrencythreads
What were the circumstances that led you to use the cluster module? Typically it's used to get around the single-threaded limitation of JavaScript running V8, spawning multiple single-threaded workers. sharp already contains multi-threaded behaviour via libuv and libvips, so you may see slightly worse performance and increased memory consumption with cluster.
If you're not already doing so, try logging which images you're processing to see if there's a pattern in behaviour just before a crash, e.g. the same image is always "in-flight".
Are you able to generate a backtrace at the point of failure via a tool such as catchsegv? (Could be tricky due to the use of child processes.)
Might you be using any sort of max-requests-per-child logic that could process.kill or process.exit a worker?
Does Node.js 0.12 improve the situation?
Are you allocating enough memory and file descriptors for the given task?

@tkazec have you been able to make any progress with this problem?

@lovell Sorry for the delay - had to switch project focus to meet a deadline. This is on my todo and I'll get back to you within a couple weeks.
The reason I'm using cluster is because of PhantomJS (see https://github.com/buzzvil/ghost-town) and it's definitely possible it's running into one of the conditions you describe. I'll figure out exactly which one and let you know, and see if it's possible to just run sharp in the master process.

"Might you be using any sort of max-requests-per-child logic that could process.kill or process.exit a worker?"

It looks like you are doing this here https://github.com/Buzzvil/ghost-town/blob/master/index.js#L199
if (this._pageClicker >= this._workerDeath) {
    process.exit();
}

Your child processes could listen for this event and block the V8 thread until all their running libvips threads have joined/completed, perhaps something like:
process.on('exit', function() {
  while (sharp.counters().process !== 0);
});

I'm pretty sure the use of process.exit() is causing this problem as it will kill any in-flight async tasks.
I'm closing this three-month old question but please do feel free to reopen if there are still problems.


Embeding Viewer to Metacity

Embeding viewer is no longer planned, instead the viewer will be implemented as solo NPM package, closing.


get_related_topics is returning nothing

Structural changes in the website caused this issue. Need a fix.

commit 3d34551 fixes this.


[Question]: For ERNIE-Layout, how should we get the segment bboxes? For inference purposes, should we do some form of image segmentation or clustering during preprocessing?

@waynemystir Hi, Thanks for your interest on ERNIE-Layout!
Segment boxes can be obtained through OCR Inference, you can refer to the example of PaddleOCR


Any help needed?

Good morning!
I spent a few hours trying to make the rules_nodejs Cypress work with Aspect's rules_js and, just like it's stated in the documentation, they're not really compatible 😀.
Is there anything that the team can be helped with? Documentation, code, examples, beta testing... ? I'd be glad to help/contribute to this package!
Cheers

HI @VinceOPS. Thanks for the offer. @mrmeku has got this one started here https://github.com/mrmeku/rules_cypress and is planning to upstream it to this repo. Need any help Dan?

Hi @VinceOPS happy to have some help with this! My intentional was not to make the rules one to one compatible for a couple of different reasons. The most notable one is that the old rule set relied on using Cypress plugins to boot a dev server / do configuration and Cypress 10 no longer supports plugin files (see https://docs.cypress.io/guides/references/migration-guide#Plugins-File-Removed).
Secondly, now that rules_js uses ES modules, we can no longer use require to bootstrap the cypress CLI as the old rule set did since the CLI entry point is not exported by Cypress's package.json. Between Cypress 10's new .js/.ts configuration files and the node api, I don't think we really need to use the CLI directly anymore. I think the node api is just as capable and more powerful in some meaningful respects. That being said, if we wanted to expose a separate bazel rule to run cypress via the CLI rather than the node api, I think that might be better for your use case of wanting a new rule that functions more like the old rule. That would be a welcome contribution to the repo :)
As far as contributing to the new rule set, feel free to! The basic rule works just fine but I was planning on adding support for a more simple use case where a user doesn't want to interact with the cypress node api. In that use case we would just have the user specify a config file and we would auto generate the entry point to interact with the node api. If you wanted to hack together on that, I think that would be fun and also a welcome contribution :)

'morning @mrmeku
Thanks for your answer, and sorry for the delay. I'm still a bit new to Bazel but I think it's okay for me to build upon the current repo! (definitely eager to learn & contribute more, to see Bazel spread across my fav. stack 😜)
Also, has this rule been published already? If so, shall we create a release and offer a WORKSPACE?
Cheers

I'll publish this once this initial PR is merged: https://github.com/aspect-build/rules_cypress/pull/14
Thanks for you patience @VinceOPS !

@VinceOPS Planning on a 0.0.1 tag shortly. Are you using this rule set at Jellyfish? We're going to be deploying it at a client this quarter so we'll put some miles on it and land fixes for any issues we hit.

Any ETA on a release?

There's not actually an issue here, so I'm closing this. We can use GH Discussions feature if there's more chat to be had :)


Make the IH accumulation curve a constant

Remove the predicted hours slider, but keep the param.Number on the code, so we can change it later.


[Docs][Meshery.io] Update Link to meshery releases on meshery.io for windows user

Desired State:
Currently, the link redirect us to- https://github.com/layer5io/meshery/releases/tag/v0.3.9
Change it to (https://github.com/layer5io/meshery/releases/)
Plus also update the command to mesheryctl system start from ./mesheryctl system start

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

working on it

This issue is already resolved


Rewrite repo in typescript

TODO

[x] Export all types from index.ts
[x] Fix component imports
[x] Rework animation validation in TypeScript
[x] Remove prop-types dependency
[x] Remove react-create-class dependency
[x] Create an example in Bobby's Starter App for each of the documented components

[x] Viro360Image
[x] Viro360Video
[x] Viro3DObject
[x] ViroAnimatedImage
[x] ViroAmbientLight
[x] ViroAnimatedComponent
[x] ViroAnimations
[x] ViroARImageMarker
[x] ViroARObjectMarker
[x] ViroARTrackingTargets
[x] ViroARPlane
[x] ViroARPlaneSelector
[x] ViroARScene
[x] ViroARSceneNavigator
[x] ViroBox
[x] ViroButton
[x] ViroCamera
[x] ViroConstants
[x] ViroController
[x] ViroDirectionalLight
[x] ViroFlexView
[x] ViroGeometry
[x] ViroLightingEnvironment
[x] ViroImage
[x] ViroMaterials
[x] ViroMaterialVideo
[x] ViroNode
[x] ViroOmniLight
[x] ViroOrbitCamera
[x] ViroParticleEmitter
[x] ViroPolygon
[x] ViroPolyline
[x] ViroPortal
[x] ViroPortalScene
[x] ViroQuad
[x] ViroScene
[x] ViroSceneNavigator
[x] ViroSkyBox
[x] ViroSound
[x] ViroSoundField
[x] ViroSpatialSound
[x] ViroSphere
[x] ViroSpinner
[x] ViroSpotLight
[x] ViroText
[x] ViroVideo
[x] ViroVRSceneNavigator
[x] Viro3DSceneNavigator
[x] Styles
[x] PolarToCartesian
[x] IsARSupportedOnDevice

Possible TODO Items

[x] Create a Scene superclass
[x] Create a Navigator superclass
[ ] Determine the types of all the events (when an event fires, what is passed?)

Lingering Questions
The following list is things which I was not sure about when I came across them, or were not intuitive types for me to figure out.

Status
Component
Item

Viro3DObject
What is morphTargets? What does it do?

Viro3DSceneNavigator
viroAppProps?: any; // TODO: what is the type of this?

Viro3DSceneNavigator
exitViro: this.exitViro, TODO: this was unused

Viro3DSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

Viro3DSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

Viro3DSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroButton
// TODO: rather than manually expanding/setting props, we should do {...this.props} which will save us time when adding new properties

ViroButton
// TODO: This was different than the other onHover callbacks

ViroScene
// TODO: types for closest

ViroSceneNavigator
viroAppProps?: any; // TODO: what is the type of this?

ViroSceneNavigator
exitViro: this.exitViro, TODO: this was unused

ViroSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroSound
soundSrc = { name: soundSrc }

ViroSoundField
soundSrc = { name: soundSrc }

ViroSpatialSound
soundSrc = { name: soundSrc }

ViroVRSceneNavigator
viroAppProps?: any; // TODO: what is the type of this?

ViroVRSceneNavigator
exitViro: this.exitViro, TODO: this was unused

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroARScene
anchor functions are in a different format than everywhere else

ViroARSceneNavigator
viroAppProps?: any; // TODO: what is the type of this?

ViroARSceneNavigator
exitViro: this.exitViro, TODO: this was unused

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroVRSceneNavigator
@todo: use Typescript function overloading rather than this inaccurate solution

ViroARSceneNavigator
Error codes types for screen recording through viro

@doranteseduardo I've considered this complete. I've tested everything in my starter kit, but I think it's ready to go. The issues I've found (#74 and #75) were replicated in my typescript repo and in the latest released version of viro.

[ ] ViroVideo was broken as part of this #75 is not reproducible with the current latest NPM version.


Add paishare document

Coverage decreased (-8.7%) to 51.571% when pulling 8675adae2354c57231164389141e0c0b5a74d9df on huangrong/paishare into bda1639b1df437692365d766b31b69a9aec3f698 on master.


Fix: Use of res.json(status, obj) is deprecated

http://expressjs.com/en/4x/api.html#res.json

@bybrunobarros Thanks for contributing! You can get tests to pass again by adding the status() method resMock in https://github.com/FredKSchott/fflip-express/blob/master/tests/fflip-express-test.js

@bybrunobarros Thanks for contributing! You can get tests to pass again by adding the status() method resMock in https://github.com/FredKSchott/fflip-express/blob/979455c6425e6ccc2745eecbd5c708de26d9b1e4/tests/fflip-express-test.js#L259

Closing as inactive


JetBrains Products for Learning / Add your school

Gisma University of Applied Sciences
website: https://www.gisma.com/

@ozkoc Please fork SWOT repository, copy file.zip in the root folder of your forked SWOT repository. Then unzip file.zip there with no changes to the directory structure. Then make a new pull request. If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message. I have to close this request without merging. Thank you for your understanding.


invalid auth out of nowhere

Failed to setup, invalid auth
Was working fine today, all of a sudden my setup stopped connecting to my bulbs as another user seems to have posted.
https://github.com/petretiandrea/home-assistant-tapo-p100/issues/447
Thought i'd try re-installing but now getting this.
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 176, in _try_setup_api
return value_or_raise(
^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/helpers.py", line 12, in value_or_raise
raise value_or_error
plugp100.responses.tapo_exception.TapoException: Returned error_code: TapoError.INVALID_CREDENTIAL: Invalid credentials
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 91, in async_step_user
api = await self._try_setup_api(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/config_flow.py", line 180, in _try_setup_api
self._raise_from_tapo_exception(error)
File "/config/custom_components/tapo/config_flow.py", line 187, in _raise_from_tapo_exception
raise InvalidAuth from exception
custom_components.tapo.errors.InvalidAuth

Same here

I'm glad it's not just my end!

Same here. In the loggs it tells me that the device is not supported but i did not do a device update. Was working fine this morning, now ir is broken
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/init.py", line 48, in async_setup_entry
raise error
File "/config/custom_components/tapo/init.py", line 37, in async_setup_entry
coordinator = value_or_raise(
^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/utils.py", line 15, in value_or_raise
raise value_or_error
custom_components.tapo.common_setup.DeviceNotSupported: Device <IP_ADDRESS> not supported!

2.3.0 is still broken

What do you mean with 2.3.0? Was there an update on tapo hacs?

What do you mean with 2.3.0? Was there an update on tapo hacs?

8 hours ago it seems

I am running 2.0.1
maybe he is running an proxy server and it has a problem..

I am running 2.0.1
maybe he is running an proxy server and it has a problem..

I was finishing a disco script for my lights, does dawn on me now, it says this communicates via LAN and I hope it does otherwise his server may have got flooded by me (if there is one and) (this wouldn't exactly be my fault though as I see 0 mention of this anywhere and am led to believe it's only MY network I'd be spamming..)

Same here. In the loggs it tells me that the device is not supported but i did not do a device update. Was working fine this morning, now ir is broken
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/init.py", line 48, in async_setup_entry
raise error
File "/config/custom_components/tapo/init.py", line 37, in async_setup_entry
coordinator = value_or_raise(
^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/utils.py", line 15, in value_or_raise
raise value_or_error
custom_components.tapo.common_setup.DeviceNotSupported: Device <IP_ADDRESS> not supported!
Reinstalling brings me the same error:invalid auth. email has no capital letters

What type of device?

Same here. In the loggs it tells me that the device is not supported but i did not do a device update. Was working fine this morning, now ir is broken
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/init.py", line 48, in async_setup_entry
raise error
File "/config/custom_components/tapo/init.py", line 37, in async_setup_entry
coordinator = value_or_raise(
^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/utils.py", line 15, in value_or_raise
raise value_or_error
custom_components.tapo.common_setup.DeviceNotSupported: Device <IP_ADDRESS> not supported!
Reinstalling brings me the same error:invalid auth. email has no capital letters

What type of device?

I have Bulbs: L530 and L630 and plug P110, was working fine, got the same error as this person did initially. then invalid auth on re-install attempt.
Weird as they were working absolutely fine.

@petr If there's anything I can run for you to help diagnose please let me know, I'd like to contribute but am fairly new to this home-assistant game.

Same here, I have two P110 and four P100.
P110 are working, P100 throw the "custom_components.tapo.common_setup.DeviceNotSupported".
Deleted and tried to re-add them, and now I get the invalid credentials error.
All of them are working just fine on the android Tapo app.

Same here, I have two P110 and four P100. P110 are working, P100 throw the "custom_components.tapo.common_setup.DeviceNotSupported". Deleted and tried to re-add them, and now I get the invalid credentials error.
All of them are working just fine on the android Tapo app.

Interesting how some of your devices are working, all of mine simply seemed to die (except from Tapo app), perhaps TP-Link rolled out a new firmware, are you also located in the UK? Sometimes they roll out by country.
None of my L530 or L630 bulbs work with home-assistant anymore and neither does my P110. :(

Same here, I have two P110 and four P100. P110 are working, P100 throw the "custom_components.tapo.common_setup.DeviceNotSupported". Deleted and tried to re-add them, and now I get the invalid credentials error.
All of them are working just fine on the android Tapo app.

Interesting how some of your devices are working, all of mine simply seemed to die (except from Tapo app), perhaps TP-Link rolled out a new firmware, are you also located in the UK? Sometimes they roll out by country.
None of my L530 or L630 bulbs work with home-assistant anymore and neither does my P110. :(

Located in Spain,
I dont think It has anything to do with any new firmware. Mine are down on Homeassistant since 2 hours ago, and they are scheduled to autoupdate at night, so I discarded that
In my opinion it has something to do with TP-Link cloud, something has changed on their side.

Same here, I have two P110 and four P100. P110 are working, P100 throw the "custom_components.tapo.common_setup.DeviceNotSupported". Deleted and tried to re-add them, and now I get the invalid credentials error.
All of them are working just fine on the android Tapo app.

Interesting how some of your devices are working, all of mine simply seemed to die (except from Tapo app), perhaps TP-Link rolled out a new firmware, are you also located in the UK? Sometimes they roll out by country.
None of my L530 or L630 bulbs work with home-assistant anymore and neither does my P110. :(

Located in Spain,
I dont think It has anything to do with any new firmware. Mine are down on Homeassistant since 2 hours ago, and they are scheduled to autoupdate at night, so I discarded that
In my opinion it has something to do with TP-Link cloud, something has changed on their side.

I'd reluctantly have to agree with you, I saw there was a big fuss about TP-Link KASA and TP-Link disabling the Local API a few years back, think they restored it in the end because so many people were rightly peed off about it.
I've left feedback in the Tapo app for every one of their product categories suggesting they make an integration to home-assistant and that thousands of their users are already using an un-official integration. (you should too, we should try make some noise about this).

Now my P110 went down with same error
Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup     result = await component.async_setup_entry(hass, self)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/tapo/__init__.py", line 40, in async_setup_entry     raise error   File "/config/custom_components/tapo/__init__.py", line 38, in async_setup_entry     return await device.initialize_device(hass)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/tapo/tapo_device.py", line 32, in initialize_device     raise DeviceNotSupported(f"Device {host} not supported!") custom_components.tapo.errors.DeviceNotSupported: Device <IP_ADDRESS> not supported!
I found the next error on logs from 9 hours ago, I think it has something to do with Tapo API, maybe it's related to the invalid auth error:
Logger: custom_components.tapo.config_flow
Source: custom_components/tapo/config_flow.py:91
Integration: TP-Link Tapo ([documentation](https://github.com/petretiandrea/home-assistant-tapo-p100)[issues]
(https://github.com/petretiandrea/home-assistant-tapo-p100/issues))
First occurred: 00:30:06 (1 occurrences)
Last logged: 00:30:06
Tapo exception -1501
No way to add any Tapo smart plugs on Homeassistant now for me. Everything works fine on the Tapo app

Random one, but I noticed I have 2FA (two factor authentication) enabled on my Tapo app, it wasn't a problem before and I'm pretty sure it's always been enabled, but could this be the issue if they implemented it into their API?
Just a thought.

Random one, but I noticed I have 2FA (two factor authentication) enabled on my Tapo app, it wasn't a problem before and I'm pretty sure it's always been enabled, but could this be the issue if they implemented it into their API?
Just a thought.
Edit: Tested with 2FA disabled, still invalid auth. (Tapo app works fine, and nothing has changed in my setup since it was working before)

I think could be a problem, I've 2FA disabled and I'm able to connect without any issue

Random one, but I noticed I have 2FA (two factor authentication) enabled on my Tapo app, it wasn't a problem before and I'm pretty sure it's always been enabled, but could this be the issue if they implemented it into their API?
Just a thought.
Edit: Tested with 2FA disabled, still invalid auth. (Tapo app works fine, and nothing has changed in my setup since it was working before)

I think could be a problem, I've 2FA disabled and I'm able to connect without any issue

Hey, I disabled 2FA to test and still got the invalid credentials error, was working fine before.

Your tapo device has access to internet connection?

Your tapo device has access to internet connection?

Yeah, I can control them over 4G using Tapo app (just tested).

Try to remove and re-add to tapo app

Try to remove and re-add to tapo app

Okay, will post back results.

Try to remove and re-add to tapo app

Interestingly, my removed and re-added device in Tapo app now shows up in Home-Assistant, god knows why that's the case, but thank you! I will buy you a coffee at some point.

Coffee is always welcome ;)
General warning: The Tapo device needs to be synchronized with the cloud, so when you do account-related operations: activate/deactivate 2FA, change password or something similar, then you experience some problems logging in again.

got the same issues every time when i have to reboot my hass installation. And the issue comes when there was a power outage in my server room.
No power outage in the rooms where all my P110 plugs are installed.
So i deleted all my plugs in the Tapo app...there are many plugs...and put it back in the app...and after that they were able to show up in HomeAssistant. No upper case in the email, even in the password...and no 2FA.
This procedure was 7 times in the last few days, sometimes because of reboot, one time power outage. After every event, all entities of the Tapo devices are gone, and every time i have to delete and re-add them to the app, and then to HA...this behaviour is since 2 weeks...before power outages or reboots had no effect to the HA.
Just for your interest...

got the same issues every time when i have to reboot my hass installation. And the issue comes when there was a power outage in my server room.
No power outage in the rooms where all my P110 plugs are installed.
So i deleted all my plugs in the Tapo app...there are many plugs...and put it back in the app...and after that they were able to show up in HomeAssistant. No upper case in the email, even in the password...and no 2FA.
This procedure was 7 times in the last few days, sometimes because of reboot, one time power outage. After every event, all entities of the Tapo devices are gone, and every time i have to delete and re-add them to the app, and then to HA...this behaviour is since 2 weeks...before power outages or reboots had no effect to the HA.
Just for your interest...

The integration is based from ip address, so be sure your router don't change the ips of your device when the events you describe happens

Try to remove and re-add to tapo app

Interestingly, my removed and re-added device in Tapo app now shows up in Home-Assistant, god knows why that's the case, but thank you! I will buy you a coffee at some point.

Thank You for posting the fix, same thing happened to myself with the P100 plugs. Removing and re adding them in the tapo app fixed the issue.

I did a reconnect, device (P115) was working yesterday and this morning same error again.

Am 24.07.2023 um 21:24 schrieb MuddyLoggins @.***>:
Try to remove and re-add to tapo app
Interestingly, my removed and re-added device in Tapo app now shows up in Home-Assistant, god knows why that's the case, but thank you! I will buy you a coffee at some point.
Thank You for posting the fix, same thing happened to myself with the P100 plugs. Removing and re adding them in the tapo app fixed the issue.
—
Reply to this email directly, view it on GitHub https://github.com/petretiandrea/home-assistant-tapo-p100/issues/448#issuecomment-1648483643, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRE25D6TQNOSP4JQW2UKOTXR3DXBANCNFSM6AAAAAA2QFPKL4.
You are receiving this because you commented.

Same here, removed from app and re-added to app worked...but only for a few hours...the game starts every few hours....re-add all my plugs to the app....then reload all plugs in hassio...wait a few hours, and repeat...
it is like in the move edge of tomorrow: remove - re-add - repeat
in the Tapo-App and in the app "Watt" on iOS everything works fine.
2023-07-26 07:41:00.003 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Gefriertruhe for tapo Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/__init__.py", line 40, in async_setup_entry raise error File "/config/custom_components/tapo/__init__.py", line 38, in async_setup_entry return await device.initialize_device(hass) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/tapo_device.py", line 32, in initialize_device raise DeviceNotSupported(f"Device {host} not supported!") custom_components.tapo.errors.DeviceNotSupported: Device <IP_ADDRESS> not supported! 2023-07-26 07:41:00.006 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Trockner for tapo Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/__init__.py", line 40, in async_setup_entry raise error File "/config/custom_components/tapo/__init__.py", line 38, in async_setup_entry return await device.initialize_device(hass) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/tapo_device.py", line 32, in initialize_device raise DeviceNotSupported(f"Device {host} not supported!") custom_components.tapo.errors.DeviceNotSupported: Device <IP_ADDRESS> not supported! 2023-07-26 07:41:00.008 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Kaffeemaschine for tapo Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/__init__.py", line 40, in async_setup_entry raise error File "/config/custom_components/tapo/__init__.py", line 38, in async_setup_entry return await device.initialize_device(hass) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tapo/tapo_device.py", line 32, in initialize_device raise DeviceNotSupported(f"Device {host} not supported!") custom_components.tapo.errors.DeviceNotSupported: Device <IP_ADDRESS> not supported!

I can confirm all but 4 of my devices have lost connection to home-assistant @petretiandrea I've not changed any settings in tapo app or account, when I try to re-add the devices I get invalid credentials again. This issue is not solved. :-(
Another coffee if it gets fixed?

Cant connect my P110. Invalid creds
All has static IP
I can see and control them on tapo mobile app
reinstalled hacs and tapo integration. no luck
I dont know what to do next


Coffee script - Weird syntax highlighting

When color theme that highlights property name definition is selected and property name starts with ‘it’ and is indented, color highlighting is broken, see printscreen.
http://prntscr.com/csf61j

VSCode Version: Version 1.6.0 (1.6.0)
OS Version: OS X El Capitan Version 10.11.6

Steps to Reproduce:

Create coffee file
Write following code

item = yes
if item
  itemText = 'Yeah'

I'm not able to reproduce this in the latest:


Updating mocha to 5.0.5

Please update mocha to version 5.0.5.
If this passes your tests you can merge it in.  If not please use this branch for changes.

c11e1e2 Release v5.0.5
b5a556e add changes for v5.0.5 [ci skip]
424ef84 increase default timeout for browser unit tests
19104e3 fix debug msg in Runnable#slow; closes #2952
f4275b6 extract checking AMD bundle as own test
19b764d Addressed feedback
2c19503 Fixed linting
ab84f02 chore(docs): rewording pending tests
6383916 fix to bail option works properly with hooks (#327…
0060884 keep hierarchy for skipped suites w/o a callback
39df783 docs: Fix typo in an emoji
27af2cf fix(changelog): update links to some PRs
d76f490 chore(ci): Remove PHANTOMJS_CDNURL, nit
86af6bb fix my carelessness in e19e879
e19e879 ensure lib/mocha.js is not ignored by ESLint

See the full change log for everything that changed in this release.

Coverage remained the same at 97.382% when pulling<PHONE_NUMBER>352bef4081c65ca70e45976df8d92a on bithound.mocha.5.0.5 into f547076bfc25f30d7e569dde4f1ef893bc3ee6fa on master.


dxvk: 2.0 -> 2.1

Description of changes
This updates DXVK on Linux and refactors the derivation to allow both native builds (2.x only, supporting both SDL2 and GLFW) and cross builds (Win32 and Win64 for use with Wine directly). It also provides a replacement setup_dxvk.sh script to avoid breaking users of the dxvk derivation (closes #202865).
I confirmed that it builds on Linux and DXVK 1.10.3 continues to work on Darwin. I don’t have a Linux machine capable of actually running games to test on Linux beyond confirming that it builds and the script works.
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

dxvk
dxvk_2

I pushed a fix for the DXVK 1.10.3 build. The script modification is only needed for DXVK 2.1. Unfortunately, it looks like there is a problem with the MingwW64 cross compiler now on Darwin.

Result of nixpkgs-review pr 213026 run on x86_64-darwin 1

1 package built:

dxvk

Just tested on linux with recent AMD card - works fine.

Squashed the fixups and did a force push.


How to not auto-assign null to nullable properties?

I want to differentiate between user not supplying a property, and supplying null.
class Payload {
    // Must always be provided
    public int $id;

    // Can be null, or string,
    public string|null $note;
}

The source ['id' => 1] will set Payload::$note to null. But user
did not supply null as value. I want to handle this a MappingError and ask
user to supply either null or string. Is this possible somehow?

Hi @eigan, thanks for the report!
It looks like a valid usecase indeed; I'd link it to #3 which is next on my todo list.

Hi @eigan, #159 should fix this. Can you take a look and see if this is solved on your side?

Fixed with #159.


Research Workgroup Objective Management

Research Workgroup Objective Management
Description
The Outreach Team - Research Workgroup is responsible for researching important topics that advance the Baseline Protocol. To accomplish this goal, research topics and related deliverables must be identified to provide workgroup participants a jumping off point from where research can begin. Research will be continuously conducted by current and future individuals in the Research Workgroup to pursue and collaborate on with other workgroup members. The setup of this WG will enable research around the Baseline Protocol to take place for years to come.
Definition of 'Done'

[x] Begin effort to identify and outline research topics/prompts
[ ] Identify and outline research deliverables
[ ] Implement effort for collecting research pieces related to Baseline Protocol

Steps

[ ] Research Topics Doc is filled out by team and reviewed iteratively
[ ] Resources List Doc is added to iteratively by team
[ ] Get current WG members to identify scope for their desired research work, and commit to work (by submitting a grant and/or adding an outreach item in the repo)

Updates
Issue comments will be used for logging updates and labels will be used for current status and work group responsible for current stage.
Grants
Outreach work items that are related to an approved grant project require updates by the 1st of each month by adding a comment on this issue with a detailed update on progress, roadblocks, and any comments.

5/9/22:

Group is kicked off and focused on these objectives

5/23/22:

Sessions occurring bi-weekly
Lists of research topics and resources have started
Next session will cover the research that participants will take on

6/6/22:

Group deliverable being started for covering alternate solutions to Baseline

7/5/22:

Matrix being worked on as first step, once fleshed out will be transferred into one-pager or infographic
Research grant submitted by Jamil for researching

8/1/22:

Group will decide next steps for group effort
Individual members took on topics

8/15/22:

BLIP-1 is becoming a main focus of the research workgroup

9/26/22:

Group is moving forward on user story

10/24/22:

Group completed grooming international supply chain use case
Team started planning SSI layer for use case
Discussed purpose of workgroup, plan is to have the use case ready to be used with the SRI
Create more collateral, diagrams, req docs for future product/outreach needs

12/5/22:

Team transforming User Journey Doc to Advancement Predicate Doc, the goal will be to turn the document into user stories moving forward that development work can be done on

1/30/23:

WG finished grooming trustless supply chain demo
https://github.com/eea-oasis/baseline-blips/issues/1
Connect with university clubs to share info on research that can be done (for real enterprises to use blockchain, etc)
Ryan working on piece about Shuttle and use case with vendor bank acct. verification

4/10/23:

Now being tracked as https://github.com/eea-oasis/baseline-blips/issues/35
Mehran mentioned writing his TSC blog on this work


WSL with Docker Windows only uses less than 10% CPU

Windows Version
10.0.19045.3324
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
Docker Windows 4.21.1
Repro Steps
When I run a CPU-task in WSL (per Docker f. Windows), it only uses a fractal of the available cpu resources.
Settings are pretty much default everywhere (no resource limitation etc.)
In the distro all cores are detected...20.04
Expected Behavior
task uses up to 100% CPU
Actual Behavior
task only uses <10% CPU
Diagnostic Logs
No response
### Tasks

What kind of utilization do you get when running stress --cpu $(nproc) --timeout 20?

Hi thank you for your fast reply and the helpful tool. I was able to debug, and it seems the problem stems from the docker configuration. There seems to be a bottleneck somewhere but it's not hardware.
The stress test runs at the expected 100%, directly in the distro, as well as in a docker container.


⚠ Panel - Hydeos has degraded performance

In b2a84ad, Panel - Hydeos (https://pterodactyl.hydeos.fr) experienced degraded performance:

HTTP code: 200
Response time: 1323 ms

Resolved: Panel - Hydeos performance has improved in db39fe8 after 13 minutes.


Tab order update delay of 0 ms is not respected

Tab order update delay is parsed with parseInt(s, 10) || 1500 which returns 1500 if s is 0, because JavaScript ¯\_(ツ)_/¯
This fixes it.

Thanks for taking the time to submit this, while I can't reproduce the issue I've beefed up the code there just to be sure, I changed the implementation a little because "" would return have returned NaN.


Faucet

https://github.com/paritytech/substrate-matrix-faucet

Using telegram faucet: @kylin_pchu_bot
https://github.com/Kylin-Network/PCHU-faucet


fix: rename README extension to lowercase md

Overview
(Hopefully) Closes #36
This pull request renames the README file extension from MD to md.
Generally, it doesn't fix anything for the devs. However, all-contributors is case-sensitive so it doesn't detect MD as md

@all-contributors please add @Namchee for code

@all-contributors please add @Namchee for doc

@all-contributors please add @smutel for bug


Python 3.10

Port arigram to python 3.10 when it becomes more "mainstream"

UPDATE: it works fine with python 3.10


(PUP-7753) Ensure that timestamps using space separator can be parsed.

This commit adds default formats to enable parsing of timestamps where
the date and time part are separated by space. It also adds tests to
assert that such timestamps are fully parsed.
An attempt was made to check if a string is fully parsed so that partly
parsed strings would raise an error. Unfortunately, the parser in
DateTime#strptime that Puppet currently relies on, does not make this
possible. It parses up to the point where a format is fully satisfied
and then returns the result without detecting trailing garbage.
A test to detect such garbage is added in this commit, but since it
would require a complete rewrite of the parser, it's currently set
to "pending".

CLA signed by all contributors.


removed superfluous whitespaces

Thank you for submitting this pull request

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

The aditional test was failing for community releases but nor for daily buils.
Main difference, there was an mvn execution that was removed so tis test is synced with the test in daily builds.


No RTO listed.

The section "What is the RPO and RTO with GRS? Explains what RTO is, but doesn't list a number.

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

ID: 2cf36d7c-e840-2e12-07d2-c8f31ebf2147
Version Independent ID: d0eeb3fe-4b55-6ee4-0288-70c441a0d7db
Content: Geo-redundant storage (GRS) for cross-regional durability in Azure Storage
Content Source: articles/storage/common/storage-redundancy-grs.md
Service: storage
GitHub Login: @tolandmike
Microsoft Alias: jeking

@sercast In most cases, a number is not listed intentionally.
@tolandmike are you able to provide any insight on this?

RTO isn't in our SLA. We strive for 99.9% with a 15-minute RTO but we can't commit to that, contractually speaking. Hence why we don't provide a number.

#please-close

@sercast We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


PushStyleColor and some other push/pop methods

Hey :)
Another batch - Includes PopStyleColor with the flags and some other push/pop utils.
Cheers,
S.

Sorry, I did not notice that you have included missing flag descriptions in this PR and I have introduced a conflict by fixing this in master branch. Can you rebase your branch so I will be able to merge through GitHub UI? Also we will see if tests pass.

Resolved it via the web interface, let's see if i got it right.
S.

I'm gonna wait for any new changes until i resolve all those git issue and everything is good and merged :)
S.

OK. Let's wait until you fix your git issues.
Now I have idea that we could also add some more extra context managers similar to the styled function, so we won't have to manually do color/wrapping/width pops and pushes. But maybe let's leave it as a separate issue to solve because I would like to have a consistent naming of such context managers and now I'm not sure if styled/istyled are good names. For color it is not a problem because we can have colored/icolored. Item width is more problematic. Also the i suffix may not be intuitive enough. I wonder if the following api would be better:

style/styles,
color/colors
item_width

Also we may want to move all extra utility functions and context managers to the separate module. The  core.pyx file is already huge.

Fixes are pushed.
Not sure how it will fit the general idea of the API, but we could split as you said the public functions and the utilities, so that all functions that are usable by a user like begin(), combo(), etc. are in one file and the rest of the stuff like wrappers and helper function in another. This will break a bit the ImGui general architecture and porting, but might be better when used as source code.
Cheers,
S.

Coverage increased (+3.1%) to 43.375% when pulling 61d1a1c9c3399e74087e4f665f59c7cda9eb1cf9 on supudo:StylesUtils into eeb616b9f1fcf96f74c8e5203a75047e292bc3c3 on swistakm:master.

Oh I was referring only to these functions:
styled(cimgui.ImGuiStyleVar variable, value)
istyled(*variables_and_values)
vertex_buffer_vertex_pos_offset()
vertex_buffer_vertex_uv_offset()
vertex_buffer_vertex_col_offset()
vertex_buffer_vertex_size()
index_buffer_index_size()

These functions are not the part of core C++ library. They are just some extra utilities or high level interfaces that are meant to make working with imgui easier and/or more pythonic. If we had some extra module for such utilities we could e.g. add more utilities to make some tedious C-style convetions more "pythonic".
For instance the:
if imgui.begin_menu('File', True):
    imgui.menu_item('New', 'Ctrl+N', False, True)
    imgui.menu_item('Open ...', 'Ctrl+O', False, True)

    if imgui.begin_menu('Open Recent', True):
        imgui.menu_item('doc.txt', None, False, True)
        imgui.end_menu()

    imgui.end_menu()

Could be:
with imgui.menu('File', True):
    imgui.menu_item('New', 'Ctrl+N', False, True)
    imgui.menu_item('Open ...', 'Ctrl+O', False, True)

    with imgui.menu('Open Recent', True):
        imgui.menu_item('doc.txt', None, False, True)

Such approach makes the code shorter, more readable and less error prone. I'm not a fan of complex package and module hierarchies and definitely don't want to split any of C++ mapping module. The content of such "extra" submodule would be of course imported in imgui/__init__.py so from the user's perspective nothing will change. We will at least separate the core mapping code from anything extra we would like to add.


getting "build constraints exclude all Go files in"

running go test on azure example getting the error
"build constraints exclude all Go files in"
can you provide some guidance on this error?

Please see https://github.com/gruntwork-io/terratest/issues/89 for the status on Terratest with Azure. In particular, we're starting some work around it, and when that work is done, we'll be able to come back to this question!

Hi,
I've been having this issue, any update on it please? @brikis98

Could you provide more details? What commands are you running, exactly?

Does it work if you run go test -tags azure .?

@yorinasub17.  It does not work still.

@robcamer which folder are you running the command in? Note that we moved all azure tests to /test/azure, so you need to run that go test call there.

Actually, I was able to resolve the build tags issue.  Thanks!

Thanks for closing the loop! Given that this ticket has the sufficient info now, will be closing as resolved.


Buildkite artifact upload/download documentation and glob patterns are confusing

This page in particular: https://buildkite.com/docs/pipelines/artifacts
Let's start with upload: it uses a glob pattern, which is great as it makes it easier to upload a bunch of stuff, however the documentation is all over the place.  In the text it says you can upload everything under a directory using some-directory/**/* which is correct and it does work, however it doesn't specify that it also stores the whole directory path associated with it. ie. the directory prefix some-directory.  There's also the problem of the supporting image showing 2 glob patterns that include each other: https://buildkite.com/docs/assets/pipelines/artifacts/artifact_pattern-34f72b531b2f55bd1c9018b9998a991fdba52ff35c1720a9b375f218ae5af366.png
This image confused me as it was hinting that the glob pattern didn't work as expected, where the user would need to specify a glob for the first level of the directory and another for all other levels. ie. some-directory/*;some-directory/**/* as shown in the image.
This document also shows a lot of usage of the CLI but not the YML.  Does the ; separator work in yml? This is not mentioned.
It also doesn't explain the mechanism as to how it stores it, where it stores it and what's the idea behind the download, which leads to the next problem; the download completely departs from the example given in the upload!
The download changes to downloading a zipped file, not a directory.  At first this made me thought that this was because the artifact uploaded was converted to a zip, but that didn't seem to make sense.  Then it was kinda alluding that the glob pattern was the 'id' of the thing you wanted to download, so I added a command of buildkite-agent artifact download 'some-directory/**/*' . to download my artifacts but just to learn after digging through code and documentation that the glob pattern isn't an id, it's used as a glob for the remote store, and then that the glob is not the same between upload and download!
Also, why isn't the artifact download a part of the yml spec?  Seems weird.
In the end, I lost at least a day of work trying to debug this issue because of confusing documentation and lack of coherency in the examples.  Please explain this feature is a clearer way,  hopefully with some consistent examples and some images to show what happens to the files and how they're stored/queried.  And please fix the globbing between the two, there's no reason not to have both working the same way.

Hey @mboudreau - thanks for the helpful report.
I'll dig a little deeper into this and get some better examples up. I'll see if I can someone to address the different globbing styles also - but no promises on that front.


Add e-itesca.edu.mx domain

Added e-itesca.edu.mx domain that that belongs to ITESCA (INSTITUTO TECNOLÓGICO SUPERIOR DE CAJEME)

@JulioLopezN Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[help] How do you access the changeset in the template?

Hi there - am new to Ember and struggling with this concept.  I want to access the changeset inside my handlebars template ... like so
{{#bs-form model=(changeset person PersonValidations) onSubmit=(action "submit") as |form|}}

  {{#if changeset.isInvalid}}  invalid ! {{else}}  well done. {{/if}}

  {{form.element controlType="text" label="First Name" placeholder="First Name" property="firstName"}}
  {{form.element controlType="text" label="Last Name" placeholder="Last Name" property="lastName"}}
  {{form.element controlType="email" label="Email" placeholder="Email" property="email"}}
  {{bs-button defaultText="Submit" type="primary" buttonType="submit"}}
{{/bs-form}}

Obviously, changeset isn't populated cuz it's being passed dynamically.
I tried to create the changeset at the component level ... but even though it appears to do the same thing on the console the actual validations aren't working.
import Ember from 'ember';
import Changeset from 'ember-changeset';
import PersonValidations from '../../../validations/person';

export default Ember.Component.extend({
  init(...args) {
    this._super(...args);
    const model = this.get('person');
    this.changeset = new Changeset(model, PersonValidations);
  },
  PersonValidations,
});

Can you help point me in the right direction?

I think you need to call the lookupValidator manually when creating changeset in js, as shown in https://github.com/DockYard/ember-changeset-validations
For example,
`
import Ember from 'ember';
import Changeset from 'ember-changeset';
import lookupValidator from 'ember-changeset-validations';
import PersonValidations from '../../../validations/person';
export default Ember.Component.extend({
PersonValidations,
init(...args) {
this._super(...args);
const model = this.get('person');
this.changeset = new Changeset(model, lookupValidator(PersonValidations));
}
});
`

I think @jimmyjlli's comment (thanks for chiming in!) should fix your problem. If not, feel free to reopen this issue! Closing for now...

Thanks for your help @jimmyjlli - I have been traveling but will implement soon.


My bot not enter in chat room

I checked out the credentials.json and api.ai integration with Twilio.
The chat work for me as a guest, but bot is not there.
Can you clarify for me?
Thank you!

Do you mean this api.ai integration? https://api.ai/docs/integrations/twilio

No! I followed this guide:
https://api.ai/docs/integrations/twilio-programmable-chat
But the bot is not in the chat room, like we see in this tutorial.

Ah, my apologies!
Have you double checked that all the credentials are correct and in the correct fields within API.ai as well as your demo application configuration?
Are there any errors in the API.ai console?

Same issue here. But I followed mine from this guide coz I'm using Watson Conversation: https://github.com/watson-developer-cloud/botkit-middleware/tree/master/examples/multi-bot

Hey @kkarlallan do you have any specific error messages?
Cheers,
Dominik

Please remove my comment. I found a way for it. Thanks for trying @dkundel .
Cheer,
Karl

Alright cool! Have a great day!
Cheers,
Dominik

Hey @DanielMaceira, I'm going to close this as I haven't heard from your for a while. If you're still having trouble, please open it up again and let me know what's going on.

Hi, I follow this tutorial
https://api.ai/docs/integrations/twilio-programmable-chat
But I have the same problem as @DanielMaceira when I start the chat, the bot is not in the chat room as we see in this tutorial.
Thanks!

Hi @toniGallardo! I'm sorry this integration seems to be broken on their side. We tried to tell them multiple times but haven't heard back from them.
Have you had a look at twilio.com/autopilot? It supports Chat and might be helpful for you. And the Autopilot CLI supports pulling in Dialogflow backups from what I know.


手动设置 lora_r=8  出现维度不匹配

麻烦看看，谢谢
shape in current model is torch.Size([8, 320]).
        size mismatch for layers.2.to_v_lora.up.weight: copying a param with shape torch.Size([320, 4]) from checkpoint, the shape in current model is torch.Size([320, 8]).
        size mismatch for layers.2.to_out_lora.down.weight: copying a param with shape torch.Size([4, 320]) from checkpoint, the shape in current model is torch.Size([8, 320]).
        size mismatch for layers.2.to_out_lora.up.weight: copying a param with shape torch.Size([320, 4]) from checkpoint, the shape in current model is torch.Size([320, 8]).
        size mismatch for layers.3.to_q_lora.down.weight: copying a param with shape torch.Size([4, 320]) from checkpoint, the shape in current model is torch.Size([8, 320]).
        size mismatch for layers.3.to_q_lora.up.weight: copying a param with shape torch.Size([320, 4]) from checkpoint, the shape in current model is torch.Size([320, 8]).
        size mismatch for layers.3.to_k_lora.down.weight: copying a param with shape torch.Size([4, 768]) from checkpoint, the shape in current model is torch.Size([8, 768]).
        size mismatch for layers.3.to_k_lora.up.weight: copying a param with shape torch.Size([320, 4]) from checkpoint, the shape in current model is torch.Size([320, 8]).
        size mismatch for layers.3.to_v_lora.down.weight: copying a param with shape torch.Size([4, 768]) from checkpoint, the shape in current model is torch.Size([8, 768]).
        size mismatch for layers.3.to_v_lora.up.weight: copying a param with shape torch.Size([320, 4]) from checkpoint, the shape in current model is torch.Size([320, 8]).
        size mismatch for layers.3.to_out_lora.down.weight: copying a param with shape torch.Size([4, 320]) from checkpoint, the shape in current model is torch.Size([8, 320]).

我在huggingface上的脚本训练没有发现类似的问题，请问是facechain的训练使用的 hf修改脚本比较旧嘛，还是说针对hf的训练脚本有了一些不可避免的大改动呢，谢谢！

是的以前支持这个功能 后来删掉了~ 可以用release v1.0.0 的版本还支持这个功能


Meaning of _o and _l in residual_encoder

Hi @Jeevesh8 thanks a lot for your code!
I am trying to understand the paper more. Can you please clarify the meaning of the subscripts _o and _l in residual_encoder.py? I see that you are using two residual encoders and concatenating them, and they serve different purposes.
Thanks a lot!
Tim

They mean observed and latent respectively @tshmak . You can read this paper .


Fix #375: add nodir option to exclude directory for *.js matcher

Coverage decreased (-0.05%) to 97.79% when pulling b8a5227803ebbe58553dd555f95e4235317288c6 on yurenju:fix-375 into c87ada03cb485e4f9110224899b68d8dc27e4bf3 on gotwarlost:master.


Worker process panic during sampling

Sampling with nutpie via the following:
compiled_model = nutpie.compile_pymc_model(model)
trace_pymc = nutpie.sample(
        compiled_model,
        draws=1000,
        tune=2000,
        chains=4
)

Results in a failure, apparently during the adaptation phase?
thread '<unnamed>' panicked at 'assertion failed: val.is_finite()', /Users/cfonnesbeck/.cargo/registry/src/github.com-1ecc6299db9ec823/nuts-rs-0.3.0/src/adapt_strategy.rs:259:25
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'assertion failed: val.is_finite()', /Users/cfonnesbeck/.cargo/registry/src/github.com-1ecc6299db9ec823/nuts-rs-0.3.0/src/adapt_strategy.rs:259:25
thread '<unnamed>' panicked at 'assertion failed: val.is_finite()', /Users/cfonnesbeck/.cargo/registry/src/github.com-1ecc6299db9ec823/nuts-rs-0.3.0/src/adapt_strategy.rs:259:25
thread '<unnamed>' panicked at 'assertion failed: val.is_finite()', /Users/cfonnesbeck/.cargo/registry/src/github.com-1ecc6299db9ec823/nuts-rs-0.3.0/src/adapt_strategy.rs:259:25
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/Users/cfonnesbeck/Downloads/level_conversions_temp.py in <cell line: 5>()
      [437](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=436)         # trace = sample_numpyro_nuts(
      [438](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=437)         #     draws=1000,
      [439](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=438)         #     tune=9000,
   (...)
     [442](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=441)         #     chain_method='vectorized',
     [443](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=442)         #     postprocessing_backend='cpu')
     [444](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=443)     compiled_model = nutpie.compile_pymc_model(model)
---> [445](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=444)     trace_pymc = nutpie.sample(compiled_model,
     [446](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=445)         draws=1000,
     [447](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=446)         tune=2000,
     [448](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=447)         chains=4)
     [449](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=448) else:
     [450](file:///Users/cfonnesbeck/Downloads/level_conversions_temp.py?line=449)     model = instantiate_model(data_model, use_gaussian=False)

File ~/GitHub/nutpie/nutpie/sample.py:143, in sample(compiled_model, draws, tune, chains, seed, num_try_init, save_warmup, store_divergences, progress_bar, init_mean, store_unconstrained, **kwargs)
    [140](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=139)     return draws_data, infos
    [142](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=141) try:
--> [143](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=142)     draws_data, infos = do_sample()
    [144](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=143) finally:
    [145](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=144)     try:

File ~/GitHub/nutpie/nutpie/sample.py:120, in sample.<locals>.do_sample()
    [118](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=117) num_divs = 0
    [119](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=118) chains_tuning = chains
--> [120](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=119) for draw, info in bar:
    [121](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=120)     info_dict = info.as_dict()
    [122](file:///Users/cfonnesbeck/GitHub/nutpie/nutpie/sample.py?line=121)     if store_unconstrained:

File ~/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py:47, in ProgressBar.__iter__(self)
     [45](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=44) except Exception as e:
     [46](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=45)     self.on_interrupt()
---> [47](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=46)     raise e

File ~/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py:41, in ProgressBar.__iter__(self)
     [39](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=38) if self.total != 0: self.update(0)
     [40](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=39) try:
---> [41](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=40)     for i,o in enumerate(self.gen):
     [42](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=41)         if i >= self.total: break
     [43](file:///Users/cfonnesbeck/miniforge3/envs/pymc_env/lib/python3.10/site-packages/fastprogress/fastprogress.py?line=42)         yield o

ValueError: Worker process paniced.

Running on macOS, Python 3.10.4, PyMC 4.2.2, and nutpie built from current main branch.

Thought it might have been the progress bar, but disabling it results in the same error.

Thanks for the report!
This looks like for some reason we end up with a nan on the mass matrix. This PR makes sure that in those cases we don't panic at least: https://github.com/pymc-devs/nuts-rs/pull/1
But I'd still like to know where that nan is coming from. Can you share the model and data for debugging, or is that difficult?

I can share it with you privately. Will send a link on Slack. Thanks!

Additional context: runs fine with sample_numpyro-nuts on GPU.

The NaNs seem to have been because the variance of the gradients was zero in one window (all gradients for a variable were exactly 1). This should be handled correctly now, after #13.


Invalid function argument error when using merge method

Description
To conditionally create an endpoint, we plan to use a merge method combined with a ternary expression. However, this approach may lead to an 'Invalid function argument' error because the lookup function might return a null value, which differs from the expected default type [].

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Terraform version:
1.5.7
Provider version(s):
hashicorp/aws v5.48.0

Reproduction Code [Required]
locals {
  is_additional_task_needed = true
}

module "dms_aurora_postgresql_aurora_mysql" {
  # Endpoints
  endpoints = merge({
    postgresql-destination = {
      ...
    },local.is_additional_task_needed ? {
    mysql-source = {
      database_name = "foo"
      ...
    } } : {}
  )

Expected behavior
Endpoints should be created successfully
Actual behavior
Invalid function argument errors were raised when trying to lookup settings of each value
Terminal Output Screenshot(s)

Additional context
I've created a PR and added the conditional endpoints in example

Hi @bryantbiggs , it would be great if you could review this when you have a chance. Thanks!

Just re-opened the PR, waiting for review

this looks like a dynamic workspace use issue, not a module issue. if you want to do this sort of dynamic "if this, then that", then you should use map comprehension instead of a conditional on the map object


Rewrite Flask API with AWS Ruby SDK for the new version of the streamer

🎉

@mar-muel Thanks! Still not building on Heroku staging though:
ERROR in ./app/javascript/custom/rollbar.js.erb
       Module build failed (from ./node_modules/rails-erb-loader/index.js):
       Error: rails-erb-loader failed with code: 1
           at ChildProcess.<anonymous> (/tmp/build_a91e964b/node_modules/rails-erb-loader/index.js:128:16)
           at ChildProcess.emit (events.js:310:20)
           at maybeClose (internal/child_process.js:1021:16)
           at Socket.<anonymous> (internal/child_process.js:443:11)
           at Socket.emit (events.js:310:20)
           at Pipe.<anonymous> (net.js:672:12)
        @ ./app/javascript/custom/index.js 2:0-18
        @ ./app/javascript/packs/application.js

Weird, I didn't even change the file.

hmm feels familiar. You might want to completely ditch Rollbar and move to Sentry like the rest of the team? @noefroidevaux

I'll look into it, thanks!

Actually, now it's worked, a completely unrelated thing fixed it somehow.


Bake blend shape to skeleton animation

Proposal Title
Bake blend shape to skeleton animation
Context and Problem Statement
Blend shapes are expensive and hard to interpolate
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Want to bake blend shapes to animations.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
./DemBones -i="Face_Geom.fbx" -a="Face_Anim.abc"  --bindUpdate=2 -o="Decomposition_20_grouped_face.fbx" --nnz=8 -b=256
Note that the corresponding fbx is 0.01 scale while the alembic is in meters.
The RMSE = 0.00433256 must be this low.
Do not pass DemBones if the RMSE is like 3.5.
Next step is to integrate an existing 3d skeleton.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not a few lines of script.
Positive Consequences
No response
Negative Consequences
No response
Is there a reason why this should be core and done by us?
We control the default skeleton controller.
References
No response
Derivative License
Copyright (c) 2020-2021 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Just keep in mind that SBS exists because LBS causes volume loss on twisting joints, so LBS with the same skeleton may produce low-quality results. It may be possible to use blend shapes or additional bones (twistbones?) to mitigate the problem.

@fire should we move this to V-Sekai/godot-pmx since this problem is mostly specific to PMX models?

b1bfb5f0595827187174397f2753e57badb1a23d


Upgrade PostgreSQL 13 in development and staging

The app currently is on PostgreSQL 12.4 with PostGIS 3. AWS marked this version as deprecated.
We recently have had successful upgrades to version 13 for other projects/apps on staging and production. We should do the upgrades for this app too, which would have benefits of reducing the number of DB versions we maintain.
Similar to how we performed such an upgrades elsewhere, this issue covers the upgrades in development and staging environments.

Thinking it might make sense to just drop having a custom paramater group. Very similar to defaults and we are unlikely to optimize them?

log_autovacuum_min_duration
250
10000

log_connections
0
engine-default - afaict off

log_disconnections
0
engine-default - afaict off

log_lock_waits
1
engine-default - afaict off

log_min_duration_statement
500
engine-default off/-1

log_temp_files
500
engine-default off/-1

random_page_cost
1
engine-default - 4

seq_page_cost
1
engine-default - 1

Staging is upgraded.
Left it at the previous parameter's because that was actually easy to do with no terraform changes.  - Updated prod plan in #1235
May look at the page_cost bits later as that could be negatively impacting our performance.


Added BoundingBox2DArray message

Added BoundingBox2DArray message to allow usage like BoundingBox3DArray. The message can be used for 2D images.

Also cherry-picked into the ros2 branch. Thanks for the code!


Optimize PNG files

I've applied FileOptimizer on PNG files. In result overall size has been decreased from 88 502 bytes to 15 013:

Additional info: FileOptimizer uses a set of different utilities such as OptiPNG or PNGOUT. It can recompress images to smaller sizes without losing any information.

Nice, LGTM!


This is my second structure suggestion. I propose to create a module …

This is my second structure suggestion. I propose to create a module folder, because we can have another modules (domains) that we communicate in our main domain.
I like the @mariorez approach. But, reading more about DDD, i guess that, this structure, is better for this project.
What you guys @ddd-fellowship/owners, think about it?

:+1:

@ddd-fellowship/owners i'll approve this PR, and will propose new things for this project.
Lately i have no time to make changes here.


[Feature] Added new measures in the length calculator

Fixes Issue🛠
Closes #340
Description👨💻
I added new measures in the Length Calculator:

Hectometre
Decametre
Decimetre

I added new options with those measures for both "unitFrom" and "unitTo" in the html code.
<select id="unitTo">
          <option value="km">Kilometers</option>
          <option value="hm">Hectometers</option> NEW
          <option value="dam">Decameters</option> NEW
          <option value="m" selected>Meters</option>
          <option value="dm">Decimeters</option> NEW
          <option value="cm">Centimeters</option>
          <option value="mm">Millimeters</option>
        </select>
Same goes for the unitFrom tag.

And for this to work I added the conversion factors for hm , dam and dm.
let conversionFactors = {
      km: 1000,
      hm: 100,
      dam: 10,
      m: 1,
      dm: 0.1,
      cm: 0.01,
      mm: 0.001,
    };

The code works the same, but I added new options and new values.
Type of change📄

[] New feature (non-breaking change which adds functionality)

How this has been tested✅
I tested it in my localhost. Everything works fine.
Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷

Merged 🥳 @SilviuPe


Update getAllDatasets.py with additional cancer sets

It appears there's a discrepancy between the datasets that have been loaded onto the Docker image and what can be saved to file.
I noticed that protDataSetsCLI.py can accept the following values for cancerType:
brca
ccrcc
colon
ovarian
endometrial
gbm
hnscc
lscc
luad
However, getAllDatasets.py only installs the data for ['brca', 'ccrcc', 'endometrial', 'colon', 'ovarian', 'luad'].
It looks like this list should be updated to:
['brca', 'ccrcc', 'endometrial', 'colon', 'ovarian', 'luad', 'gbm', 'hnscc', 'lscc']

At the time of this comment, the CPTAC dataset availability is as follows:

Dataset name
Description
Data reuse status
Publication link

Brca
breast cancer
no restrictions
https://pubmed.ncbi.nlm.nih.gov/33212010/

Ccrcc
clear cell renal cell carcinoma (kidney)
no restrictions
https://pubmed.ncbi.nlm.nih.gov/31675502/

Colon
colorectal cancer
no restrictions
https://pubmed.ncbi.nlm.nih.gov/31031003/

Endometrial
endometrial carcinoma (uterine)
no restrictions
https://pubmed.ncbi.nlm.nih.gov/32059776/

**Gbm
glioblastoma
password access only
unpublished**

Hnscc
head and neck squamous cell carcinoma
no restrictions
https://pubmed.ncbi.nlm.nih.gov/33417831/

**Lscc
lung squamous cell carcinoma
password access only
unpublished**

Luad
lung adenocarcinoma
no restrictions
https://pubmed.ncbi.nlm.nih.gov/32649874/

Ovarian
high grade serous ovarian cancer
no restrictions
https://pubmed.ncbi.nlm.nih.gov/27372738/

**Pdac
pancreatic ductal adenocarcinoma
password access only
unpublished**

As such, datasets have been updated to following:
['brca', 'ccrcc', 'endometrial', 'colon', 'ovarian', 'hnscc', 'luad']

Awesome, i cut and paste this and put it into the READMEs (main, mRNAdata, protData). Still testing them all with all the algorithms.

Reopening because HNSCC is failing on Circle (although it works locally with CWL). I think this is an issue with permissions in the virtual environment.
Going to troubleshoot.

Interesting I think this works for me as well. I wonder if it's a Docker image/build issue?

I think I found it - hnscc wasn't added to the getAllDatasets.py in the mrna folder, just the protein folder. Testing now in pr #105


'Sign in via Github' Button sometimes not visible after logout

Could be due to the broken fetch wrapper I built back then which considers all non 200 requests as errors and throws which prevents further JS execution. This is all super broken 🙈


Modifies simulation config to have a selection option

Quick patch that adds configuration for considering all alleles to have equal chance of survival (no selection)

 Evo: Add no selection option to simulation


Add note about error in React 18

I just wasted a lot of time setting up new project trying to figure out where the error was coming from, thought I was setting up createRoot wrong, then thought maybe it was a suspense thing, then thought it was an r3f thing, then finally figured out it was leva. Might be a good idea to add to the  readme/getting started that you will get an error in react 18, and how to fix. Great project and I appreciate it though!

Thanks !


feat: add /good-morning

Similar to /good-night, but for the morning.
#50 in #suggestions

This will can be included in /gifs.


PP-10204 A salute to David Heath

WHAT
David Heath has left GOV.UK Pay to become head of software engineering at GDS. This is a small tribute to his efforts on Pay. Thanks David!
HOW
Humans.txt at https://www.payments.service.gov.uk/humans.txt should read 'Thanks for everything, David.'

Closing in favour of https://github.com/alphagov/pay-frontend/pull/3110


[feat]: enable multiple GPU UUID

1. Issue or feature description
In case using one Pod with many GPUs and specific GPUs are needed to be allocated, the current single UUID in annotation may be insufficient since one single uuid can be provided. This feature aims to enable schedule a Pod with a list of GPU UUID submitted in its annotation.
e.g.
apiVersion: v1
kind: Pod
metadata:
  name: gpu-pod
  annotations:
    nvidia.com/use-gpuuuid: "GPU-123456,GPU-ABCDEFG"
spec:
  containers:
    - name: ubuntu-container
      image: ubuntu:18.04
      command: ["bash", "-c", "sleep 86400"]
      resources:
        limits:
          nvidia.com/gpu: 2 # requesting 2 vGPUs

2. Methodology
There are many cases needed to be considered.

Multiple GPU with multiple UUID, and the numbers match

Find the very node or mark it as not schedulable

Multiple GPU with less UUID than GPU number

Mark it as not schedulable

Multiple GPU with more UUID than GPU number

Choose any node meets its request

Single GPU

No change between the current code and the purpose

In order to enable this feature, changes will be taken place on function fitInCertainDevice
https://github.com/Project-HAMi/HAMi/blob/7ffc4daedd291543a1fab70db512b887512c0830/pkg/scheduler/score.go#L64

Using map[DeviceType][]*DeviceListScore instead of original simple DeviceUsageList
Putting function checkType and checkUUID out of the loop
Changing function checkUUID

3. Information to [attach]
Design draft in Chinese: link

Already supported

@JasonHe-WQ If it's already supported, how we can provide multiple UUIDs for "nvidia.com/use-gpuuuid" ?
UUIDs must be comma separated ?

Already supported

Is this feature already supported? Have you completed the support? I would like to know the support status of this feature. Could you please answer my question? ths

Already supported

@JasonHe-WQ Is this feature already supported? Have you completed the support? I would like to know the support status of this feature. Could you please answer my question? ths

e.g.
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/examples/nvidia/specify_uuid_to_use.yaml#L1
Internal logic:

const:
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/pkg/device/nvidia/device.go#L46

Test:
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/pkg/device/nvidia/device_test.go#L151

Already supported

@JasonHe-WQ Is this feature already supported? Have you completed the support? I would like to know the support status of this feature. Could you please answer my question? ths

I am pretty sure even though this feature didn't come from my PR. Thanks to the community members.

Already supported

@JasonHe-WQ Is this feature already supported? Have you completed the support? I would like to know the support status of this feature. Could you please answer my question? ths

I am pretty sure even though this feature didn't come from my PR. Thanks to the community members.

Thanks for your reply. I have looked into it in detail and found that the gpuuuid support list can be separated by ",".

Already supported

@JasonHe-WQ Is this feature already supported? Have you completed the support? I would like to know the support status of this feature. Could you please answer my question? ths

e.g.
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/examples/nvidia/specify_uuid_to_use.yaml#L1
Internal logic:

const:
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/pkg/device/nvidia/device.go#L46

Test:
https://github.com/Project-HAMi/HAMi/blob/65454721774306c2d3ee2e81634e3eb51ad7f9a8/pkg/device/nvidia/device_test.go#L151

Thanks for your reply. I have looked into it in detail and found that the gpuuuid support list can be separated by ",".


Adds debug logs, removes redundant deps, enhances intellisense, aligns node requirements, various code enhancements

CF #15 request to show PR's

What's your opinion on dropping the bytes package?


Stock sync fail

Can you reproduce this issue on default Wordpress theme (eg Storefront)?
yes
Can you reproduce this issue when all other plugins are disabled except WooCommerce, Polylang and Hyyan WooCommerce Polylang Integration?
yes
What product versions and settings are you using when this issue occurs?

PHP: 5.6
WordPress: 4.9.5
WooCommerce: 3.3.5
Polylang: 2.3.4
Hyyan WooCommerce Polylang Integration: 1.0.4
Browser: Chrome 66.0.3359.117

Steps to Reproduce
We have 3 langs: Spanish, English and Portuguese and sync stock activated (with all checks on meta too). The item has 1 in stock, the default lang is ES and in the other langs we can't edit the quantity.
The item is sold in ES version, then the stock in EN and PT is 1 and in ES is 0. The Stock has not been synced.
What I Expected
The sync of the stock.
What Happened Instead
The stock hasn't synced. If we open the product at backend and press Update button, then the stock is sync.
WordPress Environment
no errors

this appears to be a duplicate of an issue with a proposed fix, please try the fix and comment on that issue,
see #299 with fix #300

solved with 1.1.0 version. thanks!


Alway show that  Please set an HEXO_ALGOLIA_INDEXING_KEY environment variable to enable content indexing when the computer startup.

I set the environment variable and it work.
But when i shutdown and restart the computer.
it show that Please set an HEXO_ALGOLIA_INDEXING_KEY environment variable to enable content indexing.
Is this normal? need to set an HEXO_ALGOLIA_INDEXING_KEY environment variable when the computer start ?

Hi @jerryc127,
Indeed, the environment variable set with export is tight to the lifetime of your shell session. So it's normal.
Environment variables are made available to any program which run on a computer a given time (from within the same shell session) so it depends how much you trust the other programs you run. A rogue npm module could scan the env variables and leak them to someone else.
Personally, I add an environment variable at the system level only if I use them so often I'm bored to type them again.
I suspect there is a way to use the operating system "keyring" to store and prompt the key content securely but I have not looked into that yet.
If you use continuous integration, then I'd recommend to run the indexer there, and to store the key as an encrypted environment variable. This is how I do on my blog.
Does it answer your question? Do you think of something else?

thx. i choose to add an environment variable at the system level

Cool 🙂 let me know if you encounter any problem or wonder about something else.


Doc 2646 streams tutorial code examples in C#

My first PR at Redis :-)
The code seems to display OK in the doc page but no doubt my coding style isn't quite right yet :-)

Closes #221

Why the title is in 'c'? you meant C#?

@andy-stark-redis , Why the title is in 'c'? you meant C#?

Yes, it was auto-generated by JIRA and I forgot to edit it! I've changed it now :-)


Add more specific error message when attempting to parse empty input

Addresses #4037
Modifies the sax parser to create an exception with a more specific error message when attempting to parse an empty input string or stream.
Modifies corresponding tests to expect the new error message.

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header files single_include/nlohmann/json.hpp and single_include/nlohmann/json_fwd.hpp. The whole process is described here.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for this kind of bug). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

coverage: 100.0%. remained the same when pulling cca9375c18eda238e695e01ccbba7ef072203103 on colbychaskell:fix-parse-error-wording into edffad036d5a93ab5a10f72a7d835eeb0d2948f9 on nlohmann:develop.

Can you please try to amalgamate with an older version of astyle, like astyle 3.2? There was a breaking change in astyle which makes the output differ unfortunately.

@nlohmann amalgamated with astyle 3.1 and it seems to have worked correctly now

Thanks!


onClose

onClose event dose not work !

Thanks for letting me know, does it not work on a particular platform, or all of them? Cheers


Bed Buckling into Crematorium exploit

Description

If you place a bed in front of a crematorium, you can use it to buckle someone into place long enough to instakill them in the crematorium. When combined with any kind of stun mechanic + being bound (handcuffs, makeshift cuffs, etc.), you are essentially dead from the moment you have been cuffed unless stopped.
Steps to repro exploit:

build bed in front of crematorium
find target, cuff them
buckle them to bed, they cannot escape
toggle cremation tray
ignite crematorium

Screenshots

Something better than screenshots. Video: https://www.youtube.com/watch?v=_Hze0GuydMc
Additional context

** Originally sent in an ahelp regarding this b/c powergaming, tried reaching out to admins directly, got told it was a github issue so here **
The player (Character name: White // Username: White) showcased in this video did it about a half dozen times. He did not use a bed the first time but was using a stun baton/cuffing to keep people still while he shifted them around in front of the crematorium, then evolved to using a bed which is what prompted the recording. I was a spectator only in this round, did not participate in any capacity other than observing. After watching him do this multiple times, I asked in Discord if it something along these lines was powergaming, and that's when a trialmin (Todd Howard) reached out via DM since he saw the ahelp I filed about it.

I don't think this is an exploit since you can also just push the person over/stun baton/whatever else then pull them in. Which seems intended. There are infinite ways to murder someone you have cuffed.
The reason to do this is it is faster than shift right-click dragging them into the position in the narrow area. It isn't less foolproof though since they can unbuckle instantly if they prepare to to click unbuckle, and become undragged. I haven't watched the video yet but the chaplain for example nearly escaped 3 times this way.
If anything the problem is cuffs are too foolproof? And stun batons can stun lock people while down and being dragged? Iirc the CE didn't even get cuffed was just stunned a bunch. And in at least a case or two the bed wasn't even used.

The issue isn't the cuffs being a death sentence, it's more the fact that the bed being used as a force-to-prone method, then being pulled into the crematorium with the tray despite being buckled to the bed. The cuffs really just guarantee that you aren't breaking out of it for about 90 seconds.

But you can do it without the bed. If the person is cuffed you can just move them in front of it, push them down then cremate them. No counterplay there either.

Could counter this by claiming making crematoriums detect living players and refuse to cremate unless it's emagged.

This no longer seems to be reproducable. I couldn't find why, but buckled mobs are not picked up by the crematorium when it closes

Indeed I can't seem to reproduce this anymore. Feel free to re-open if you find a way to exploit this again.


[LOW] [Performance] Improve Crashlytics reports with more breadcrumbs

Problem
Recently our team has been investigating crashes reported in Firebase Crashlytics, but the crash reports lack detailed information, such as user actions. This lack of context makes it difficult to identify and fix the root causes, turning the debugging process into a trial-and-error exercise that is inefficient and time-consuming.
Solution
To enhance our understanding of these crashes, we propose implementing Crashlytics logging within the app navigation and during user interactions across critical processes. By doing so, we can capture a sequence of user interactions leading up to a crash, providing valuable insights into potential causes.
Navigation logs should contain:

time of the log
name of the screen
params passed to the screen

User interaction logs should contain:

time of the interaction
name of the interaction

By implementing it, we aim to gain a view of user interactions within the app. This additional context will significantly aid in diagnosing and fixing crashes, ultimately improving app stability.
Attaching a screenshot of how crash logs could possibly look like in a Firebase panel.

@TMisiukiewicz cc

I guess this is all done now with the PR merged and deployed @TMisiukiewicz correct me if I am wrong

@mountiny that is correct, all done here


How to deploy a fine grained authorization model?

The application requirements

Offline first (browser storage ideally IndexedDB, synchronization, conflict detection/resolution)
Fine grained authorization system (user management)

Having organization that contains members & teams
A team have some access to company data (read, write, admin)
A user inside a team inherits it's right from the team but can be also overwritten
A instance is attached to a organization
The team rights for a instance is inherited from the company right and can be overwritten
(same for user)

There is a sample GraphQL schema:
type User
@model
{
    id: ID!
    firstName: String!
    lastName: String!
    avatarUrl: Url
}

type Team
@model
{
    id: ID!
    name: String!
}

union Entity = User | Team

type Organisation
@model
{
    id: ID!
    name: String!
}

enum OrganisationRoleEnum {
    NO_ACCESS
    READ_ACCESS
    WRITE_ACCESS
    ADMIN_ACCESS
}

type OrganisationRole
@model
@key(fields: ["entityID", "organisationID"])
{
    entityID: ID!
    entity: Entity! @connection(fields: ["entityID"])
    organisationID: ID!
    organisation: Organisation! @connection(fields: ["organisationID"])
    teamID: ID
    team: Team @connection(fields: ["teamID"])
    role: OrganisationRoleEnum
}

type ObjectTypeA
@model
{
    id: ID!
    name: String!
}

type ObjectTypeB
@model
{
    id: ID!
    name: String!
}

type ObjectTypeC
@model
{
    id: ID!
    name: String!
}

# Take in consideration that each object types has different configurations and relations
union Instance = ObjectTypeA | ObjectTypeB | ObjectTypeC

enum InstanceRoleEnum {
    NO_ACCESS
    READ_ACCESS
    WRITE_ACCESS
    ADMIN_ACCESS
}

type InstanceRole
@model
@key(fields: ["instanceID", "entityID"])
{
    instanceID: ID!
    instance: Instance! @connection(fields: ["instanceID"])
    entityID: ID!
    entity: Entity! @connection(fields: ["entityID"])
    organisationID: ID
    organisation: Organisation @connection(fields: ["organisationID"])
    role: InstanceRoleEnum
}

Investigations
From what I've seen in the web we have two worlds, the first one is Apollo Client and the second one is DataStorage.
Apollo Client comes with lot of issues, if you use the out of the box appsync client you are stick to Apollo 2.X and can't use react hook. If you migrates to Apollo 3.X to have hooks support you only takes the two links from appsync (HTTP & WebSocket) but you face to offline capabilities issues.
DataStorage is relatively new but really promissing. It comes with a new way to sync data with the appsync, use IndexedDB as local storage and have a really easy syntax to use.
In terms of backend deployment we have AWS CDK and Amplify CLI.
AWS CDK you can programmatically generates the cloudformation stuff.
Amplify CLI come with GraphQL transformations that take the job of generating the stuff for you. A good collection of directives but a very basic authorization system.
The two solution that I really like and would use for our team because it's easier to use would be DataStorage with Amplify CLI because once you setup your stuff you don't need to care about the needed stuff for deployment but I encounter some lack in terms of authorization.
How to deploy a fine grained authorization model?
From what I've seen I can use either a Lambda authorizer or a Pipeline resolver for doing the needed check for the authorization.
The use case is I need to check the access right for each items in a query list, for a desired mutation and provide the uacpdate to only the subscribers that have the right to see the object.
My question is how do I do that with Amplify CLI? can I use the actual @auth? can I write a custom one? how do I do for the subscriptions? and which of Lambda authorizer or pipeline resolver is the most optimized with appsync?

@Hideman85 @josefaidt
Hi,
Just so I, and others who may tread along this path understand this correctly, please correct me if I'm wrong.
Currently as of 2023, there is now way to applying fine, dynamic, multi-layer authorization with AWS Amplify DataStore.
As per the following example:
User, creator of:
[RandomGroup1 .... RandomGroup n]
Cannot give fine access to:
[User1 .... User n]
To access the following protected content:
[RandomGroupContent1 ... RandomGroupContent n]
AWS Amplify does support the usage of IAM groups, but size and user defined granularity is limited.
AWS Amplify does support the usage of ownerField, but this is limited to one modal, and cannot be passed down to children.
If anyone wants to create the above functionality, you have to use a custom Lambda function, using an AuthToken.
https://docs.amplify.aws/lib/datastore/setup-auth-rules/q/platform/js/#configure-custom-authorization-logic-with-aws-lambda
Is useful.

import { DataStore } from 'aws-amplify';

DataStore.configure({
  authProviders: {
    functionAuthProvider: async () => {
      const authToken = await refreshAuthToken(); // refreshAuthToken

      return {
        token: authToken
      }
    },
  }
});


nlu.yml and domain.yml look like not working

nlu.yml:
nlu:
- intent: greet
  examples: |
    - hey
    - hello
    - hi
    - hello there
    - good morning
    - good evening
    - moin
    - hey there
    - let's go
    - hey dude
    - goodmorning
    - goodevening
    - good afternoon

domain.yml
responses:
  utter_greet:
  - text: "Hi, what i can help you?"

i did make rasa-train and make restart but why when i send hi, it go to chatgpt api? and not direct reply Hi, what i can help you??

Add code below to rules: solved the issue
- rule: greet
  steps:
  - intent: greet
  - action: utter_greet

Add code below to rules: solved the issue
- rule: greet
  steps:
  - intent: greet
  - action: utter_greet


Add ability to get error response from cloudinary

There is no way to get the response status code and message from upload failure

I suppose this could be done. Currently when an error occurs it is reported to multer which removes the file (if it was already uploaded). The multer storage engine docs don't specify a way of getting this error to the user directly but I suppose it could be done using express error callbacks.


For encrypted drives, report the name:root specified by the user

For encrypted drives, report the name:root specified by the user,
rather then the underlying Fs root (which may be unreadable
when filename_encryption is set).  See enhancement issue #1305

I've merged this now - thank you very much