Attach external Data in the Hierarchy

This can be labelled as Need Help or NEW FEATURE
Is that possible to fetch some data from another source using an API when we generating the Heirarchy by calling findAll() method? for an example let's say I have a model like below,
const Category = db.define('categories', {
  title: {
         type: Sequelize.STRING
  },
});

and if I use the findAll() method like below,
Category.findAll({
hierarchy: true,
}).then...
it returns the Hierarchy as blow,
        [
            {
                "id": 1,
                "title": "Furniture",
                "hierarchyLevel": 1,
                "parentId": null
            },
            {
                "id": 2,
                "title": "Fashion",
                "hierarchyLevel": 1,
                "parentId": null
            },
            {
                "id": 3,
                "title": "Mobile Phones",
                "hierarchyLevel": 1,
                "parentId": null,
                "children": [
                    {
                        "id": 4,
                        "title": "Apple",
                        "hierarchyLevel": 2,
                        "parentId": 3
                    },
                    {
                        "id": 5,
                        "title": "Sony",
                        "hierarchyLevel": 2,
                        "parentId": 3
                    },
                    {
                        "id": 6,
                        "title": "Blackberry",
                        "hierarchyLevel": 2,
                        "parentId": 3
                    }
                ]
            }
        ]

Now the important part is that I need to attach some additional Data from another Database (from CouchDB running in an separate application by calling an API endpoint). Those data is stored based on the Category ID so that the final result should be as below,
[
    {
        "id": 1,
        "title": "Furniture",
        "hierarchyLevel": 1,
        "parentId": null,
        "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
    },
    {
        "id": 2,
        "title": "Fashion",
        "hierarchyLevel": 1,
        "parentId": null,
        "another_data" : {"referance_ID" : 1, .......},  // <= Data from CouchDB using API call
    },
    {
        "id": 3,
        "title": "Mobile Phones",
        "hierarchyLevel": 1,
        "parentId": null,
        "children": [
            {
                "id": 4,
                "title": "Apple",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            },
            {
                "id": 5,
                "title": "Sony",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            },
            {
                "id": 6,
                "title": "Blackberry",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            }
        ]
    }
]

Hi @mapmalith.
I understand what you're trying to do. However, Sequelize doesn't support CouchDB, and this feature is outside the scope of this module, so I'm afraid it's not something I'm willing to add as an API.
What I'd suggest is this:

The problem isn't specific to hierarchical structures, it's really about joining data from Sequelize with data from other sources like CouchDB.
Therefore, have a look on Stack Overflow for any questions related to that subject. Someone may have come up with something already that you can build on.

Sorry I can't be more help.

@overlookmotel Thanks for your response. Even though we can not communicate with CouchDb with this package, my current requirement is to call an API endpoint by sending the ID so that the end point can send relevant data by fetching from the Couch DB.
and thanks again

@overlookmotel Thanks and appreciate your concern on this.

Posting this even after closed this thread, hoping this will help for someone as I could find a solution for this with following steps,
I have added a ned column as below,
const Category = db.define('categories', {
  title: {
         type: Sequelize.STRING
  },
  another_data : {
         type: Sequelize.STRING
 }
});

and I have used a sequelize hook - afterFind and the code is as bellow,
Category.afterFind((cats, options) => {
  for( let [key, value] of cats ){
    // get data from another DB using value.id
    // assign that value to the value.another_data
  }
  }).then(function(categories){
    cat.title_key = categories[0].title_key + 1;
  });
});

so that the final result will be following as expected:
[
    {
        "id": 1,
        "title": "Furniture",
        "hierarchyLevel": 1,
        "parentId": null,
        "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
    },
    {
        "id": 2,
        "title": "Fashion",
        "hierarchyLevel": 1,
        "parentId": null,
        "another_data" : {"referance_ID" : 1, .......},  // <= Data from CouchDB using API call
    },
    {
        "id": 3,
        "title": "Mobile Phones",
        "hierarchyLevel": 1,
        "parentId": null,
        "children": [
            {
                "id": 4,
                "title": "Apple",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            },
            {
                "id": 5,
                "title": "Sony",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            },
            {
                "id": 6,
                "title": "Blackberry",
                "hierarchyLevel": 2,
                "parentId": 3,
                "another_data" : {"referance_ID" : 1, .......}, // <= Data from CouchDB using API call
            }
        ]
    }
]


Run cross-version CI on JRE 8 and 11 to verify compatibility

Just a suggestion that I thought might be beneficial for CI builds:
considering running CI builds on JRE 8 and JRE 11 explicitly.
This reduces the risk of missing differences between older JREs and
JRE 17 which CI currently runs on. The main risk by avoiding this
is coming across bugs that were fixed in newer JRE versions.
One of the things this can impact is the differences in default
classloaders in newer versions.

Closed since this causes additional issues with --release under JRE 8


Enhancements to module exports

Enhance exports
Currently modules/classes can only be imported from the single file they are exported from.
Users may benefit from importing the whole library:
import ol from 'ol';
const layer = new ol.layer.Tile();

... or a single namespace:
import control from 'ol/control';
const OverviewMap = new control.OverviewMap();

Also the naming of default exports could be improved (i.e. append the name of the containing directory') so IntelliSense finds them more easily, e.g.

class OSMSource extends XYZ {}; // instead of `class OSM extends XYZ`
export default OSMSource

See suggestion of @ahocevar for reference: https://github.com/openlayers/openlayers/issues/9358#issuecomment-475170787

From https://github.com/openlayers/openlayers/issues/9358#issuecomment-476391827:

Ok and as import control from 'ol/control';  could be written as import * as control from 'ol/control' the exports are fine as is?
Renaming the classes is the remaining TODO here right?

the exports are fine as is?

A quick sanity check could not hurt, to make sure that all exports that are marked @api are re-exported.

Renaming the classes is the remaining TODO here right?

Right.

@ahocevar should the classname be changed too? Or only the default export?
// export
class BingMapsSource extends TileImage
[...]
export default BingMapsSource;

// import
import {BingMapsSource} from '../src/ol/source.js';
import BingMapsSource from '../src/ol/source/BingMaps.js';

vs
// export
[...]
const BingMapsSource = BingMaps;
export default BingMapsSource;

// import
import {BingMaps} from '../src/ol/source.js';
import BingMapsSource from '../src/ol/source/BingMaps.js';

Renaming the default export name is just relevant for intellisense, while renaming the whole class will have a big impact on existing code.

Only the default export. But the change is simpler than what you have above:
diff --git a/src/ol/source/BingMaps.js b/src/ol/source/BingMaps.js
index 3d4ea68ab..24abe7a74 100644
--- a/src/ol/source/BingMaps.js
+++ b/src/ol/source/BingMaps.js
@@ -117,7 +117,7 @@ const TOS_ATTRIBUTION = '<a class="ol-attribution-bing-tos" ' +
  * Layer source for Bing Maps tile data.
  * @api
  */
-class BingMaps extends TileImage {
+class BingMapsSource extends TileImage {
   /**
    * @param {Options} options Bing Maps options.
    */
@@ -300,4 +300,4 @@ class BingMaps extends TileImage {
   }
 }

-export default BingMaps;
+export default BingMapsSource;

Ah ok. Got it. I just have to keep /src/ol/source.js as it is.


Shared behavior trees

When using the same behavior tree in many objects is a waste of resources to have the tree instantiated for all of them. Instead, it could be great to have them updated like:
public void start(T object);
public Status execute(T object);
where the object is the blackboard object being updated like:
tree.step(object);
This way, the same tree could be used for as many objects as they are needed. In lot of games it is normal to use the same ai tree for lot of entities instead of having a different one for every of them.
This is an easy enhancement that I think is very useful.

I believe that BehaviorTree has a setObject(T) method to set the instance of your BlackBoard. You generally would do something like the following;
public void updateAI()
{
    for(GameObject obj: objects)
    {
        tree.reset();
        tree.setObject(obj);
        tree.step();
    }
}

This way you can use the same tree for multiple objects. Does this achieve what you want? If not could you clarify?

Not exactly. If this is done and the AI's are executed on multiple threads this would lead to unexpected bugs.

Yes, setObject does not allow you to share trees properly and that's not its purpose.
Sharing the tree model means that there's a shadow tree for the status of each execution of the model, so memory saving is not so big as you would expect.
Also, this would involve huge API-breaking changes and I'm not sure they are worthwhile.


Why this project is not a fork ? -> newbreedofgeek/react-stepzilla

Hi,
I  found another project that is really like yours (and in the code there is similarity).
It's more advanced, but it's not a fork, why ?

ha! interesting, thanks for pointing out.
Of course that is fine, for a project like this, happy to share and happy that is used in anyway.
"Imitation is the sincerest form of flattery"

@newbreedofgeek cheers!
closing


feat: ignore external imports

fixes #3
Do you want this at all? Should I put it behind a flag?
p.s. I have no idea what I'm doing.

ping

Thanks for the PR! I finally got round to addressing this issue, albeit in a slightly different way — using Acorn to generate an AST, then checking there are no nodes that aren't of the type ImportDeclaration. It's a bit more heavy handed, but eliminates any possible edge cases.


Adding Selective WARP [SUGGESTION]

Thanks for Linux-Optimizer
Would be wonderful if you could add selective WARP to your wonderful script in the next update
Thank you in advance and keep up the good work✌🏽

This script is for optimizing Linux. I think WARP is out of scope.
Also, for Using warp, xray-core supports wireguard protocol in itself. you don't need any warp script for that.
https://github.com/chika0801/Xray-examples/blob/main/wireguard.md


Bottom axis label can be cut off depending on window size in graph tab.

Due to issue with initialisation of embedded graph widget over filling the assigned space.

Toolbar doesn't move all the way to the top of the parent widget.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64914

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67908

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101521


Issue when PVC is mounted to weaviate container

Description

Installation

Docker installation on kubernetes pod

Weaviate Deployment

Docker Deployment on kubernetes pod

Details
Have installed Verba and Weaviate containers on a single pod in kubernetes. When I set PERSISTENCE_DATA_PATH to '/var/lib/weaviate' and mount a pvc on that path, Verba is unable to connect to Weaviate. (I am selecting Docker instance to connect to from Verba UI).
When I don't mount a pvc to the weaviate container, everything is working fine. But when I am mounting a PVC, I am getting below error:
Failed to connect to Weaviate object existence! Unexpected status code: 500, with response body: None.
When I checked the weaviate container logs, I can find below,
{"build_git_commit":"64457c2","build_go_version":"go1.22.9","build_image_tag":"v1.27.2","build_wv_version":"1.27.2","error":"init shard "verba_config_8tB2n31NCSSP": init shard "verba_config_8tB2n31NCSSP": init prop "config": value index: init disk segments: init segment segment-1731316996864028994.db**: unexpected error loading segment** "/var/lib/weaviate/verba_config/8tB2n31NCSSP/lsm/property_config/segment-1731316996864028994.db": runtime error: slice bounds out of range [:419430404] with capacity 12748","level":"error","msg":"Unable to load shard 8tB2n31NCSSP: init shard "verba_config_8tB2n31NCSSP": init shard "verba_config_8tB2n31NCSSP": init prop "config": value index: init disk segments: init segment segment-1731316996864028994.db: unexpected error loading segment "/var/lib/weaviate/verba_config/8tB2n31NCSSP/lsm/property_config/segment-1731316996864028994.db": runtime error: slice bounds out of range [:419430404] with capacity 12748","time":"2024-11-12T09:34:21Z"}
{"action":"requests_total","api":"rest","build_git_commit":"64457c2","build_go_version":"go1.22.9","build_image_tag":"v1.27.2","build_wv_version":"1.27.2","class_name":"VERBA_CONFIG","error":"msg:repo.exists code:500 err:get/init local shard "8tB2n31NCSSP", no shutdown: LazyLoadShard::preventShutdown: Unable
to load shard 8tB2n31NCSSP: init shard "verba_config_8tB2n31NCSSP": init shard "verba_config_8tB2n31NCSSP": init prop "config": value index: init disk segments: init segment segment-1731316996864028994.db: unexpected error loading segment "/var/lib/weaviate/verba_config/8tB2n31NCSSP/lsm/property_config/segment-1731316996864028994.db": runtime error: slice bounds out of range [:419430404] with capacity 12748","level":"error","msg":"unexpected error","query_type":"objects","time":"2024-11-12T09:34:21Z"}

Hey, thanks for the issue! Can you share a bit more info about your current setup? Are you deploying the Weaviate instance separately through docker or are you deploying the whole verba application with a weaviate instance inside one container?


lenovo 16ach6h: add amd cpu pstate

Description of changes
lenovo 16ach6h: add amd cpu pstate
Things done

[x] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

bors merge


using as a normal chat

can be used the  as rendere for  a normal chat?

No. The chat is just between user and bot.


ci: create a env running in development mode for cypress test

Since development is not running i development mode, code coverage will not work. We need a seperate environment running with "npm start" so we can create code coverage from it. This is because the code is not instrumeted in production mode

There is a solution on the way. Christer will create environments with every PR that cypress and code coverage should run against


is it some hack for it

In requirments there is :
Your app doesn't use named anchors (#). Named anchors can't be correctly represented in the fallback hash based url scheme.
Is it some hack for it ?

You might be able to program your own solution in js, but you cannot use '#' in your url. I don't really think it's worth it.
Actually these days I recommend to use Turbolinks instead of Ajaxify. It brings almost the same speed improvements and is easier to use and less intrusive than Ajaxify - and very well maintained.


Python lambda is 2.6mb when there is 0 dependencies

Describe the bug
When create a function with a very simple Python lambda, the generated lambda is 2MB
Amplify CLI Version
4.30.0
To Reproduce
Take pointless lambda like this and build it.
def handler(event, context):
     print("event:", event)

Expected behavior
The deployed lambda should only be a couple bytes not 2.6mb
Screenshots

Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]
Mac
Node Version. You can use node -v to check the node version on your system
v14.13.1

Additional context
Add any other context about the problem here.

Amplify CLI uses pipenv to bundle the resources to the cloud. Pipenv brings in virtual env, which adds size to the bundle.

@yuth
What is the benefit of this?
Why not just use AWS Sam to handle the bundling of the lambda? even CDK does not inflate the lambda by 2.6mb with zero benefits.
And FYI, Amplify does not even support Python 3.8

@michaelbrewer You're right that pipenv is overkill for small functions that only have a couple dependencies, but it is good for managing functions with lots of dependencies. It is also a well adopted package management tool in the python ecosystem: https://packaging.python.org/tutorials/managing-dependencies/. We don't use AWS SAM because many of our customers don't use / have SAM installed.
We do support Python 3.8, so if you are having trouble there please open an issue with details of the problem.

@edwardfoyle  -
amplify console does not support Python 3.8
https://github.com/aws-amplify/amplify-console/issues/595
Most lambdas don't need many dependencies (and some have none at all outside of AWS SDK)
So in most cases just have a requirements.txt should be all that you would need.
Larger projects can use poetry.

@edwardfoyle
i don't quite understand why the actual deployed lambda needs to be 2.6mb, these are not runtime dependencies but build time dependencies?
Here is the example lambda for python function for a cognito auth challenge:
def handler(event: dict, _):
    print("event", event)

    if len(event["request"]["session"]) == 0:
        event["request"]["challengeMetadata"] = "COOKIE_CHALLENGE"
        event["request"]["publicChallengeParameters"] = {}
        event["request"]["publicChallengeParameters"]["cookieName"] = "source"
        event["request"]["privateChallengeParameters"] = {}

    return event

I would expect the deployed lambda to be tiny

Note how AWS-CDK does this without bloating the lambda with unused libraries : https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/aws-lambda-python
As a develop you just need to have Docker installed.

@edwardfoyle @yuth - will anyone look into fixing this?
I can see that AWS does care about the cost of cold starts (https://aws.amazon.com/blogs/developer/modular-aws-sdk-for-javascript-release-candidate/), and this seems to be inconsistent.

@michaelbrewer We'll look into this. Sorry for the late response.

Maybe @heitorlessa has some input on how to support Python lambdas in a clean way. It would be nice to support SAM or do what CDK does when building Lambda functions (while keeping the size down)

Maybe @heitorlessa has some input on how to support Python lambdas in a clean way. It would be nice to support SAM or do what CDK does when building Lambda functions (while keeping the size down)

Hopefully the tools improves soon. As we are planing to build all of our lambdas in Python

Hopefully the tools improves soon. As we are planing to build all of our lambdas in Python

@kaustavghosh06 while I don't have the bandwidth to contribute code I'm happy to review or chat
You can keep pipenv but only extract the dependencies themselves instead of bringing the whole virtual env - it's not necessary.
pipenv here will also break when customers bring dependencies that rely on C, as it needs to build within a Linux env -- hence Docker suggestion by Michael (a flag would do).

@kaustavghosh06 while I don't have the bandwidth to contribute code I'm happy to review or chat
You can keep pipenv but only extract the dependencies themselves instead of bringing the whole virtual env - it's not necessary.
pipenv here will also break when customers bring dependencies that rely on C, as it needs to build within a Linux env -- hence Docker suggestion by Michael (a flag would do).

Thanks @heitorlessa for offering an ear for this.
I do like how sam can bootstrap a lambda with the build tools and sample code:
sam init --location https://github.com/aws-samples/cookiecutter-aws-sam-python

Maybe this can be an option @kaustavghosh06 . When can we expect to at least not bring the whole virtual env with the lambda?

@kaustavghosh06 what is the timeline on this? Otherwise amplify function build does not seem to work, it just hangs without completing.

Oh i see that this is a separate issue (which is NOT being fixed):

https://github.com/aws-amplify/amplify-cli/issues/6159

@eddiekeller @kaustavghosh06  - is anyone looking into this? How easy would it be to fix this ourselves in the CLI?

How about doing something along the lines of :
# Create an requirements.txt in src/ (which can be gitignored)
pipenv lock -r > src/requirements.txt

Then build/download the dependencies using docker image lambci/lambda:build-python3.8
# Download the vendored deps
pip install -r requirements.txt -t /vendored && cp -au . /vendored

Found a hack to make amplify stop building all these nondependent-dependencies into my Python functions. This will only work for functions that do not have any dependencies that aren't already provided in lambda layers, as it just completely stops the function build process. There is an amplify.state file inside of each function. If you don't want amplify to build your function, modify the amplify.state file to make amplify "think" its a nodejs function.
amplify.state (original, will build virtualenv into the deployed package)
{
  "pluginId": "amplify-python-function-runtime-provider",
  "functionRuntime": "python",
  "useLegacyBuild": false,
  "defaultEditorFile": "src/index.py"
}

amplify.state (new -  will NOT build any python packages but otherwise the Lambda function will work the same in AWS)
{
  "pluginId": "amplify-nodejs-function-runtime-provider",
  "functionRuntime": "nodejs",
  "useLegacyBuild": false,
  "defaultEditorFile": "src/index.py"
}

Same Issue Here

There is a comment on an alternative way to run pipenv in the following comment which allows installation of dependencies without copying the virtualenv. Ideally the amplify project may use this method instead:
https://github.com/pypa/pipenv/issues/746#issuecomment-416475131

Amplify is still including the pipenv venv bundle in function deployments?  Is this a joke?


[Docs]: Mismatching tags in "Why Is Apache APISIX the Best API Gateway?" blog

Current State
Description of the current state/issue:
Tags should be one or more of the following values

Case Studies
Ecosystem
Authentication
Plugins
Community
Vulnerabilities

Yet the current tags for this page are not on the list.
Link to the page:

https://apisix.apache.org/blog/
https://apisix.apache.org/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway/
https://github.com/apache/apisix-website/pull/1320/files line 15

Screenshots (if relevant):

Desired State
Description of the change you are proposing:

Find the best fit tag(s) from the current list and replace the current ones in blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md. Update the zh-cn file as well.
(Optional) Update the tags list after discussion.

This this a pretty easy change, good first issue.
Would you like to fix this issue?
No. Please assign another contributor

I am interested in contributing to your project and would like to request to be assigned to the project. I believe I have the necessary skills and expertise to make meaningful contributions to the project.

I am interested in contributing to your project and would like to request to be assigned to the project. I believe I have the necessary skills and expertise to make meaningful contributions to the project.

Go for it, this shouldn't take you too long.


APPID issue

Where can I get APP_ID for this app?
You have used "283/VGiScM9Wiw2HJg" but where can I get this one?

ya same problem here @buhe @aderan @aderan @alwaysmavs @leavesster
Where can i get app_id

@27ksandip @Muhammad-Ullah
You need register a agora account to get App ID. Here is agora's document : interactive-whiteboard

I/flutter (26373): [InAppWebView] consoleMessage [White] join room fail
I/flutter (26373): [InAppWebView] consoleMessage [White] Error: connect failed: room "076ef9b0b8dd11ed85245975e226531a" not found

I/flutter (26373): [InAppWebView] consoleMessage [White] join room fail I/flutter (26373): [InAppWebView] consoleMessage [White] Error: connect failed: room "076ef9b0b8dd11ed85245975e226531a" not found

use your own white room uuid and set the right region which you request to whiteboard server.
this issue will be closed to avoid no relation issue report, please open a issue if you have different issues


Adding CI badge to Readme

Added a badge for the AppVeyor build.

Summary
One more fancy badge for the Readme.
Details
This one links to the Windows build in AppVeyor.
Motivation and Context
We build on Windows now and we use badges.
How Has This Been Tested?
I clicked on the badge and it went to the correct place.

Types of changes

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

Checklist:

[ ] I've added tests for my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@enkessler AppVeyor's Windows build is on the enkessler account. You set it up, and it's your thing, right now.
It seems appveyor has an GitHub org account concept implemented: https://www.appveyor.com/docs/team-setup/#setting-up-appveyor-account-for-github-organization What would it take for us to go there?

It sounds like we'd need a new email with cucumber.io that can be used for the admin account on AppVeyor.
@aslakhellesoy Do we have an email account handy for this purpose?

It looks that @mattwynne has an organization account on AppVeyor.

Oh, well, in that case...hey, @mattwynne! Can you add the cucumber-ruby project to that account and update the badge URL?

@enkessler I've just added you as a collaborator for Cucumber's appveyor account. Can you see if you can get in and do it yourself?

I also added various cucumber GitHub teams too

@olleolleolle @mattwynne The badge URL is now fixed. Good to go?

@enkessler Well struggled!


Can't send message to group

I am testing via command line, but the message is not sent and returns the error below.
" zbxtg.py: You need start a conversation with your bot first in 'testebotarq' group chat, type '/start@copnetarq_bot' "
I already sent the command '/start @ copnetarq_bot' in the group, but it did not solve.

works!


MiBoxer - WL-Box1 2.4GHz Gateway

Prerequisite

[X] Yes

Version
v1.7.0-beta.39
Device Infomation JSON File
No response
Device Control Mode
Standard Instruction
Logs
No response
Other Infomations
Hello, I have Miboxer lights at home which I control via a MiBoxer - WL-Box1 2.4GHz Gateway, I paired it with the smartlife / tuya app and via the tuya platform and control via your plugin via homebridge on a raspberry pi4.
Unfortunately, the problem is that when I turn off the lights via homekit or in the tuya / smartlife app, they turn on by themselves in less than 1 minute.
Is there a way to set it so that the device does not turn on by itself?

is it related to adaptive lighting?

It seems to be same behavior for me!

Yes, probably yes, if I leave the adaptive function on, the lights come on. If I select any color and turn off the lights they don't turn on by themselves. So it's really a very adaptive feature and it's annoying. :(

I’m not sure if this relates to the problem I was having previously. I decided to recently rebuild homebridge from scratch, and when I began adding items back in, I did decided to not enable adaptive lighting against that motion sensing outdoor driveway light, I’m not sure if that really was tied to my original  issue (of that motion light remaining on), but I’m now, no longer having the problem of that light remaining always on once triggered.I know this is not directly related to this issue, but I saw reference to adaptive lighting, so I did want to follow up.  I stayed frozen in a prior plug-in version (v33) for a while, but as I rebuilt homebridge, when I added everything back, this time I chose not to enable adaptive lighting for the Tuya driveway lights & so far so good.My best guess, is that with adaptive lighting against the pir light, whenever the motion sensor detected motion, the light would continue to remain on afterwards. It seemed to no longer follow the rules set in the Tuya app as far as the number of minutes to switch off.I have not fully tested that supposition, so it is a best guess, but that is my best guess based on observations to present…RandySent from my iPhoneOn Apr 20, 2023, at 8:18 AM, gaosen @.***> wrote:
haven't decided yet how to solve this issue properly. different lights(with tuya module) may have different behavior, that's the most trouble part for me, if a solution solves lights A, but make lights B failed, that's not perfect. so... annoying. :(
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thanks for the update @randymassey!
@ANDiiikk you can check out below some findings on my original issue. Does MiBoxer - WL-Box1 2.4GHz Gateway have the same below feature?
https://github.com/0x5e/homebridge-tuya-platform/issues/212#issuecomment-1520513346

I tested with another lightbulb and it's everything ok until now! :)
The original ceiling light I have posted before has the issue. The thing that stood me out is that the ceiling light has a power-on behavior which could be the original source of the problem:

Besides that, there is a documentation by Tuya called Why does my light turn on by itself? which called my attention about the power supply voltage of the device could be unstable.
I will review the power stuff and if I find any new issue, I'll post here!

I don't know that miboxer Wl-box has any such function. so far I'm solving it by not using the adaptive lighting function. I'm not an expert and I don't understand much. :(


Index _field_names only if the column is indexed and doc-values are off

Summary of the changes / Why this improves CrateDB
Checklist

[ ] Added an entry in the latest docs/appendices/release-notes/<x.y.0>.rst for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in the latest docs/appendices/release-notes/<x.y.0>.rst
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

This should be done after removing the duplication of FieldMapper.parseCreateField and ValueIndexer.indexValue


Fix listening on multiple different consumer groups

Fix #570
Each consumer group needs its own EventProcessorHost instance.

:ship: Of course you'll have to pull in the updated SDK before checking in.

:ship:

Hasn't this been merged?


Researching existing approaches and join forces

We should compare existing approaches and try to join forces on building "the drupal packagist", performant, complete, just awesome:
Existing projects and related issues

Drupal Org issue
https://github.com/reload/drupal-packages-generator
Will Milton's packagist fork: https://github.com/winmillwill/packagist/tree/drupal
https://github.com/winmillwill/drupal-parse-composer
http://static.drupal-packagist.org/v0.2.0/packages.json

Sources for getting release information

update.xml per project: http://updates.drupal.org/release-history/views/all
All releases: https://drupal.org/files/releases.tsv (updated 4 times a day)
https://www.drupal.org/api-d7/node.json?type=project_release
Commit log: https://www.drupal.org/commitlog/feed (does not support ?page=...)
Releases tagged 8.x: https://www.drupal.org/taxonomy/term/7234 (there's a feed as well)
Releases tagged 7.x: https://www.drupal.org/taxonomy/term/103
Module Index https://www.drupal.org/project/project_module/index

General ideas

Parse commit log
Listen to SAs to react as fast as possible!

I am happy with the changes that @webflo has made to the packagist fork, and I'm happy to be available to help and glad for the interest. There is ongoing discussion about the details of representing package dependencies in drupal/parse-composer#.
The thing is that the drupal-packagist.org domain is just an AWS Route 53 DNS entry that doesn't point anywhere. Only static.drupal-packagist.org actually points at a service, and that's just an S3 bucket. If someone wants to pay for a server to run the packagist fork in this organization, I'm happy to hand over the domain.
I think we should just have a few http server rewrites for the front page and other potentially confusing paths so that it's clear that we don't support the normal packagist.org workflow (register, login, add a repo). This way we can leave it on and use the experimental auto update functionality.
Longer term, I think we can do as @kasperg suggests and write some pull-requests for upstream packagist so that our code can be a separate repo instead of a fork, and like @dawehner said, I think we should see about getting someone from drupal.org and/or the Drupal Association interested so that this can become the official way to manage drupal packages.
In any case, I think this issue is resolved unless there are more projects/approaches that we need to consider?

@webflo just pushed that code to this project. So we have no github fork anymore and can use the repo search :) We hope to get some more visibility from that too.
@winmillwill, If you want we could move drupal-parse-composer too to the org, as it is a crucial part for the packagist. I'd add you to the organisation as well, if you are interested in that too :)
I agree with you on the other points and therefore should create separate issues for those.

@winmillwill ++ :)


OpenAPI generator - array type for property in schema not correctly generated

Describe the bug
There is a small error in the generated types affecting "nested array objects". E.g. when generating the type for an object of this shape:
{
  content: [{ name: "foo" }]
}

To Reproduce
Steps to reproduce the behavior:

Use this OpenAPI schema and save it to minimal-example-api.yaml:

openapi: "3.0.3"
info:
  description: minimal example
  version: "0.0.1"
  title: "sample api"
paths:
  /my-path:
    get:
      summary: do something crazy
      operationId: myOperation
      responses:
        "200":
          description: "yay it worked"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/MySchema"
components:
  schemas:
    MySchema:
      type: object
      required:
        - content
      properties:
        content:
          type: array
          items:
            type: object
            required:
              - name
            properties:
              name:
                type: string

Generate the OpenAPI client with

npm init -y && npm i<EMAIL_ADDRESS>npx openapi-generator --input minimal-example-api.yaml --outputDir gen --overwrite

check the generated schema for #/components/schemas/MySchema which looks like this:

// ...
export type MySchema = {
  content: {
    name: string;
  } & Record<string, any>[];
} & Record<string, any>;

The type for .content is incorrect as []/array only applies to Record<string, any> but should actually wrap the whole object type for the content property aka { name: string } & Record<string, any>. So the full type should look like this:

// ...
export type MySchema = {
  // note the surrounding "( ... )" and that the [] is after the closing ")"
  content:  ( {
    name: string;
  } & Record<string, any> ) [];
} & Record<string, any>;

Expected behavior
The content should be properly typed as an array.
Used Versions:

node version 20.11.1
npm version 10.2.4
SAP Cloud SDK version 3.13.0

Impact / Priority
The generated types are incorrect making it necessary to use as any or as unknown type casts defeating the purpose of this feature.
Affected development phase: e.g. Development
Impact: Impaired

Hi @sven-petersen ,
Thanks for raising this. We are working on a fix and will update you once it's available.

Hi @sven-petersen ,
We released a new version 3.14.0 with the fix.


I need a proper Helm chart how to edit the Kafka cluster Endpoint in that

Needed in a three to four commands

It is already possible to configure the bootstrap brokers with the existing Helm chart, see here: https://github.com/redpanda-data/kminion/blob/5425c6203c957ad1688bb60d5e8eb9bb2bdaaa63/charts/kminion/values.yaml#L144


nwjs-wrapped version

This version is nwjs-wrapped to run in Windows and macOS beyond Chrome v109 or v110 when Google has ended support for Chrome App execution on those platforms.

Closed this PR because the intention is not to merge into master at this point in time; perhaps later.  Can not determine how to PR into a new parallaxinc branch of the same name: jwjs-wrapped (which doesn't yet exist).


[WIP] Building a reach-threaded parallel test (2.0)

This is a work in progress do not merge
This pull request builds on #153
The new reach ordering designed by @jameshalgren is implemented on the most recent initial conditions enabled version of mc_reach.pyx. A parity test is conducted to ensure that the new reach ordering scheme produces identical output to the original reach ordering scheme, and ultimately WRF hydro routing results.
Once we are confident that the new reach ordering scheme is functionally equivalent to the original v02 formulation, we will experiment with multithreading reaches of in the same reach ordering group.
For additional context - see #153. Here, @jameshalgren has documented his thinking in designing a strategy for reach-threaded parallelization of v02.

For WRF parity, see pocono1_warmstart_v2.ipynb
This notebook should prove that the new ordering scheme works.

Update

A new function has been added to mc_reach.pyx, named compute_network_multithread. This function produces the same result as compute_network but does so using a multithreaded approach based on a new reach grouping concept.
pocono1_warmstart_v2.ipynb has been updated to show that the compute_network_multithread and compute_network functions produce identical output and very nearly reproduce WRF Hydro routing results.
nhd_network_utilities_v02.py has been updated with the current (v2.0.4) version of NWM.

Suggested Review Actions

Run pocono1_warmstart_v2.ipynb via Google Colab to prove to yourself that the multithreaded version of compute_network works as it is intended.
Look at mc_reach.compute_network_multithread to see how it differes from the original mc_reach.compute_network. Are there any efficiencies we can capitalize on? Any variables that are initialized but unused? Is the overhead too burdensome?
Suggestion welcome on how to fix broken compute-network-v2.ipynb notebook.

BEFORE MERGE...
Make sure to change the git clone commands in the demo notebook

PROFILE needed
A quick look at applying the multithreaded compute_network on a large network shows that it is actually much SLOWER (?!) than the original. This is likely because I have introduced an unacceptable amount of overhead. I would appreciate some help in profiling the multithreaded function to see why it takes much longer than expected.


add uploadspeed and shareratio at task list page

add uploadspeed and shareratio at task list page

duplicated
#21


DB migration Tools related

Its nice to have the  bat file tool but i noticed little more improvement as here,
1>
To fix the red error,
After modifying the .bat "source" to "CleanArchitecture" its working fine(mine name is default)

May be a slight improvement needed I guess
2>Also after add-migration, 1-2 more step like verify in VS/code then show the command for update-database also, either execute here itself in CLI or copy & paste to package manager console also makes smooth & attactive...
ex: update-database -Context ApplicationDbContext .........

Unfortunately, the name of the project(in bat file) is taken from the name of the folder where the project is located.
This problem does not exist when creating a new project.
And I will also solve this problem in the next version

This problem is completely solved, you can and it can be used in the next version of the package
AddMigration.Persistence.bat
AddMigration.Identity.bat
AddMigration.FileManager.bat