cy.getReact() returns Error: Component not found

Hi Abhinaba,
I'm trying to read the value of a prop from a component using:
cy.getReact('HomeWelcome').getCurrentState()
When I run it I get the following error in Cypress:
Error: Component not found **<HomeWelcome>**

  There can be multiple reasons for it.

  > Check the root is defined as a env parameter (cypress.json config file).

  > If the root is defined correctly, check other parameters - component name, props and state objects

My cypress.json looks like so:
{
    "chromeWebSecurity": false,
    "env": {
        "cypress-react-selector": {
            "root": "#root"
        }
    }
}

And after reading some other issues and your readme, I tried to add cy.waitForReact() to the before() but then I get the following error:
TypeError: require.resolve is not a function

Because this error occurred during a 'before all' hook we are skipping the remaining tests in the current suite: 'Home'

Some other things to note:

HomeWelcome is a nested component
Redux provider wraps the app
We're using BrowserRouter with Async react-code-splitting

Any ideas?

Hi, cy.waitForReact() should be executed successfully before proceeding with it. any other react-selector commands. This is appearing because of a recent change, can you try the version 2.0.4?
npm i --save-dev<EMAIL_ADDRESS>
Let me know that resolves your issue.

Hi Abhinaba,
I am also getting same error, while inspecting Component using React-Dev tool. Multiple reasons error.
cy.waitForReact();
const btn = cy.react('Anonymous*', { props: { name: 'abc' } });
//const btn = cy.react('CatalogGridItem*', { props: { name: 'xyz' } });
btn.click();
I am writing End to end tests and doesn't have access to source code, so is there any way to get the component name from React dev tool which I can use in my test scripts using Cyrpess-react-selector.

Hi @aditya-3008 , the error you are receiving because the component is not found. If you are sure that you are mentioning the react-root correctly in the configuration file, then the only reason is an exact match with the props is not found. It is like any other selection process. If you can provide a similar repository where I can reproduce the bug, it will be helpful. You don't need to have the access to the source code, but you need to know what the react-toot of the application. If the root is explicitly not provided, then cypress-reactselector` automatically figure it out. Now, the problem is there can be multiple roots. In that case, you need to provide the target one.
For a zoom jam, connect me here

Hi @jamesl1001 , use the cypress version 2.0.4. It should resolve your issue with the same code.

Yep, 2.0.4 is working, thanks.

Hey @jamesl1001 I am happy that it is working now. if this library making an impact on your development, you can consider supporting the project.


offline network errors

intentionally disconnected wifi to see more error states. We should implement some kind of graceful fallback UI that hides or disables features that rely on network connectivity, or maybe display an offline modal, or backfilling these components with loading skeletons instead of displaying loading errors?

Don't think we need a non-wifi-connected UI state for our components and we can just do https://github.com/penumbra-zone/dex-explorer/issues/211 to match what the error states should be rendered like.

missed that error states issue, that's more in the spirit of a resolution I had in mind.


OracleDB Invalid username and  password

The tool fails to log in to your oracle DB if your oracle user password has $ as a special character in it.

Do you get a similar error for postgres connections with a $ sign in the password?  I suspect the error results from a variable assignment in this file: https://github.com/visulate/visulate-ora2pg/blob/main/express/db_connection_check.pl.

I  did not try with Postgres but I guess it will be the same issue after looking at the assignment variables for the db_connection check


Merge

merge all together

Hello @steschuser
I compared everything with our master branch, and everything is included.
duplicate #944

Hello @steschuser
I compared everything with our master branch, and everything is included.
duplicate #944


fix fix assertion in test_broker_load_p2

Proposed changes
Fix assertion failure due to comparing wrong columns.
expected: [INTERNAL_ERROR]failed to find default value expr for slot: x1
actual: type:LOAD_RUN_FAIL
    2024-09-22 11:13:43.771 INFO [suite-thread-3] (test_broker_load.groovy:337) - Load result: [838879, L14_5c0d84b80e121044a5091fc065ee763c8e0e, CANCELLED, 0.00% (0/4), BROKER, null, cluster:oss-cn-beijing-internal.aliyuncs.com; timeout(s):14400; max_filter_ratio:0.0; priority:NORMAL, type:LOAD_RUN_FAIL; msg:errCode = 2, detailMessage = (<IP_ADDRESS>)[INTERNAL_ERROR]cur path: s3://qa-build/regression/load/data/part0.parquet. failed to find default value expr for slot: x1, 2024-09-22 11:13:41, 2024-09-22 11:13:43, 2024-09-22 11:13:43, 2024-09-22 11:13:43, 2024-09-22 11:13:43, null, {"Unfinished backends":{"e15fe3f045a94ab2-bb62fae396495ffd":[]},"ScannedRows":0,"TaskNumber":1,"LoadBytes":0,"All backends":{"e15fe3f045a94ab2-bb62fae396495ffd":[10009]},"FileNumber":2,"FileSize":6312557}, 30085, {}, root, ]

run buildall


AutoroutePart.SetHomepage set to false for homepage

When I access Model.ContentItem.Content.AutoroutePart.SetHomepage in a Content.chstml template or do a content export, the homepage's value for that field is false.
I tried changing the homepage and also disabling and reenabling the Home Route module, neither fixed the problem. I also tried refreshing the path which also did not fix the problem.
I am using the latest 1.5.0 release.

Oops, this is for Orchard Core, didn't mean to put it here.


Publish function result as kafka message

Currently, it is possible to make a function to be triggered by listening to a Kafka topic by providing the -trigger-topic <topic_name> flag on creation.
It might be interesting to be able to tell the result of the function to be published into an specific topic as well. This will enable chaining/pipeline capabilities.
From the user perspective this might mean to add an extra flag like for example trigger-topic-result (I do not like this specific naming).
kubeless function create test --runtime python27 \
                              --handler test.foobar \
                              --from-file test.py \
                              --trigger-topic <topic_name>

I like this idea. A good flag name could be simply --result-topic.

we need to look more into function chaining in other solutions. Not sure how it is done in them (e.g lambda, azure functions etc).

I wanted to follow up on this discussion. We have a use case where we are looking to chain a bunch of kubeless functions and I was wondering what the community approach was to solve this problem.
From what I see for Azure they seem to use the Azure Service Bus for this ( https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus )
Amazon has 2 approaches

Simpler approach to use Amazon SNS as the queue to publish to and read from ( http://docs.aws.amazon.com/sns/latest/dg/sns-lambda.html )
The new approach of creating state machines which they call Step Functions ( https://aws.amazon.com/blogs/aws/new-aws-step-functions-build-distributed-applications-using-visual-workflows/ )

In Kubeless today, do we have the following capabilities? ( I couldn't glean it from the documentation/open issues )

Ability to publish to a Kafka queue topic from a serverless function that is triggered via pub-sub ( so that the next function can be triggered via pub sub )
External process ( outside of kubeless but inside the same k8s cluster ) to populate a kubeless topic so it can trigger a pub-sub function.

Also you can do basic chaining with the serverless plugin, check out this example:
https://github.com/serverless/serverless-kubeless/tree/master/examples/node-chaining-functions

Is this issue/feature still in development or in consideration for development?  I'm looking to do some non-trivial workflow with kubeless and it does require a bit more logic than simple function chaining.

this is definitely needed even though there is a need to publish back to various types of eventing system.
@deissnerk had a proposal in the works maybe he can share ?

Any update on this? Missing of this one feature in Kubeless is currently big plus for Fission.

Not right now @LudovitVarga, what you can do is to add the code in your function to send messages to Kafka. See this conversation: https://github.com/kubeless/kubeless/issues/881#issuecomment-421224305

I know about this workaround but with direct support in trigger, functions can be less coupled to Kafka itself. Also if you have consumer and publisher in same place, you can use Kafka transactions what is big plus.


Refactors + Fixes + Legacy Code Removal

[x] Update counting the lines of code to include subdirectories and SQL files

[x] Remove code related to accessing mkwx via multithreaded browsers (see #91)

[x] Remove "Bad Wolf Facts"

[ ] Core Code refactor, logical, readability, type hinting

[ ] Combine Room.py and War.py into Table.py
[x] Refactor War.py

[x] Standardize variable names
[x] Standardize wording used
[x] Standardize naming convention (underscores)
[x] Privatize direct access to variable, use getters and setters
[x] Add hint typing where possible, for return types and parameters
[x] Clean up messy functions
[x] Remove unnecessary functions
[x] Add docustrings (descriptions) to functions
[ ] Move non-tabling variables and functions to TableBot.py

[ ] Refactor Room.py

[ ] Standardize variable names
[ ] Standardize wording used
[ ] Standardize naming convention (underscores)
[ ] Privatize direct access to variable, use getters and setters
[ ] Add hint typing where possible, for return types and parameters
[ ] Clean up messy functions
[ ] Remove unnecessary functions
[ ] Add docustrings (descriptions) to functions
[ ] Inherit from List for easier race accessing
[ ] Move non-tabling variables and functions to TableBot.py

[ ] Refactor TableBot.py

[ ] Standardize variable names
[ ] Standardize wording used
[ ] Standardize naming convention (underscores)
[ ] Privatize direct access to variable, use getters and setters
[ ] Add hint typing where possible, for return types and parameters
[ ] Clean up messy functions
[ ] Remove unnecessary functions
[ ] Add docustrings (descriptions) to functions
[ ] Move tabling variables and functions to Table.py

[ ] Overhaul HTML Parsing

[x] Create single, centralized parser for front page
[ ] Create single, centralized parser for room pages
[ ] Update impacted functions to work with new parsers

[ ] Refactor Race.py

[ ] Standardize variable names

[ ] Standardize wording used
[ ] Standardize naming convention (underscores)

[ ] Add type hinting
[ ] Clean up & refactor methods (make more readable)

[x] Refactor Player.py

[x] Standardize variable names

[x] Standardize wording used
[x] Standardize naming convention (underscores)

[x] Privatize variables

[x] Getters and setters
[x] Update all references to use getters and setters

[x] Add type hinting for args and return types
[x] Clean up & refactor methods (make more readable, better names)
[x] Strongly enforce data types

[ ] Refactor Placement.py

[ ] Standardize variable names

[ ] Standardize wording used
[ ] Standardize naming convention (underscores)

[ ] Add type hinting
[ ] Clean up & refactor methods (make more readable)

[ ] Only return races for races that are displayed on the table

[ ] Only pull miis for races that are displayed on the table
Will add more as it continues...

Make note of last commit d719f61de59de023cbb76a67f1b2dc2728306e37:
"Strong enforcement of data types for (Player) class. If the data types given are not of the expected type, an informative TypeError is thrown. Additionally, minor updates to Wiimmfi data parsing were made to ensure data types are consistent. Data types were originally all over the board. This will simplify things greatly."

This refactor will be based off of #82 instead.


Use instructor-note directive where appropriate

Don't make them headings
Requires new enough sphinx-lesson

Thanks!


Add seven_zip_tool resource to simplify setup

Having a simple resource to setup 7-zip allows other resources (since including a recipe inside a resource is not a good pattern) to use it to ensure that their prerequisites are installed before-hand.
This resource leverage existing attributes as default values to keep backward compatibility.
The seven_zip::default recipe's code has been refactored to just use this resource.

@linusruth any interest about this PR?

Maybe @sneal ?

I'll try and take a look at this soon.  I'm surprised there's no build pass/fail showing for the PR so I should probably fix that first.

@Annih Please merge the current master branch into this PR to get a proper build check via AppVeyor.

@heathsnow done :)
What about #21 which PR do you prefer?

LGTM :shipit:


Feature Request: Threading for faster account processing

Title: Allow Multithreading for faster AWS account processing
Description:
Currently I have a lot of AWS accounts to correlate.  Dozens and dozens.  New ones come online every day, and we need to see how permissions are shared between them all.  Our last Cartography run clocked in at about 3.5 hours.  It's survivable, but it got me wondering if there was any way of scaling wide with account population without running afoul of any relevant AWS api request limits (which I believe are per-region-per-account, but I could be wrong, see link below).
The other obstacle to this would be some of cartography's ingest mechanisms - you'd need to wait until all info has been pulled to start building relationships, and I'm not familiar enough to know if this would require a large behavioral change.  Is this at all possible?
[optional Relevant Links:]
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#api-request-rate

Hi there, thanks for filing this issue.  Sync speed is absolutely a pain point we feel as well.  I'm going to write broadly on perf problems.
Parallelism within the AWS sync
Multithreading amongst AWS accounts is something we've considered but have held off on for this reason: If one thread runs into a problem and fails, even if the other threads succeed you still end up with partial data.  You will having missing assets, and relationships connecting one account to another account will be incorrect.
As you pointed out, a sync of multiple hours is a crappy situation because you can't rely on the data being 100% accurate if you query the graph in the middle of a sync while it's being updated.  One way to get around this is to have Neo4j replicas that can be used when data is being synced on the DB instance being written to.
DAGs for parts that don't have data dependencies
One idea we have planned within the next 3 months (see our meeting minutes and roadmap doc) is to implement DAGs for parts of the sync that don't have data dependencies; if the AWS sync fails then there is no reason for the GCP sync to fail as well.  These DAGs could run in parallel and improve perf, but this doesn't solve your problem of having dozens of AWS accounts and keeping those in sync.
All that said, there are some key bottlenecks within any given sync (credit to Evan Davis for the list).

Time spent pulling data from various APIs.
Time spent transferring data to neo4j (NOT query execution, the actual transfer of data from the Python process to the Neo4j process via the kernel’s networking stack)
Misconfigured queries (e.g. merges with no indexes)

We need to emit metrics on each phase of the sync to better prioritize the bottlenecks.
Addressing these items could help with syncing dozens of AWS accounts in a timely manner.  There are probably lots of low hanging fruit.

you'd need to wait until all info has been pulled to start building relationships, and I'm not familiar enough to know if this would require a large behavioral change. Is this at all possible?

Correct, although I am not 100% sure if the API is the biggest bottleneck and we need to measure that to know for sure.
Yet another approach
Another way that would be a very big change would be to consume event streams from something like AWS Cloudtrail.  This way, you could seed a Cartography deployment with one big sync, and then set up subscribers to Cloudtrail events that would update the graph whenever a create, delete, or relationship change event happens.
Anyway, clearly there is lots of work to do :)  I don't have a straightforward answer for you at the moment but we are open for suggestions and please definitely feel free to get involved as much as you want (perhaps joining in on Slack or talking more on this at our monthly meeting :)).  Definitely want to hear more about how you are using the tool, and hope we can help.

@achantavy I've been looking into this recently, and I think in terms of incorrectness of data, this is an issue whether or not the accounts are multi-threaded. If any one account fails, it may fail after other successful account syncs and you'll end up with data that's partially filled in. For correctness here, rather than exiting immediately on a failure, error handling should be wrapped at the thread pool level, and when an exception is caught in one account sync, it should stop that thread, wait for all other threads to finish, then exit. In that situation, it would be similar to a single account failing in a synchronous sync.
There's the possibility of more cross-account data being incorrect when that fails, but in the current situation if a sync fails, it may be a day or two before the sync is successful, and during that time, the data can't really be trusted anyway. Being able to bring the graph into a trustworthy state faster may be more desirable than having less data in an untrustworthy state.
In terms of speed, I think a considerable amount of time is spend waiting on IO from calls to AWS. I did a quick test of adding async to per-account syncs and it shaved over 5 minutes off my sync for just a couple small accounts (and I didn't put any effort into adding yields to sub-resources). If we were to add async per-account, and yields to sub-resources, we could likely shave hours off most syncs without any ratelimiting issues.

Has there been any further discussion of this feature? I'm currently trying to map an organization with about 2 dozen accounts and the processing time is incredibly painful. I agree with @ryan-lane regarding the issue of data inconsistency, and that it will be more important to update state quickly.
@ryan-lane do you still have your POC asynch code? I'd like to try it for my use case and see if it helps. Otherwise I think I can guess where the asynch processing would need to go (inside of the job runner)

Was there any actual work done on this? For the same account, are there issues with doing parallel resource discovery across regions?
I have done a little bit of experimentation. Besides needing separate neo4j sessions per thread, it appears to be working fine and shaving wall clock time meaningfully. Happy to put it up as a PR if it helps for discussion.

For the same account, are there issues with doing parallel resource discovery across regions?

Syncing resources in the same account in parallel can be problematic because some jobs assume that some other resources are already present in the graph, so they do a MATCH and then MERGE. If the resource being matched on does not exist yet, then no graph update will happen.
For this reason, we decided on that Slack thread that @ryan-lane mentioned (blah Slack only persists previous 90 days) that it would make more sense to do accounts in parallel.

I have done a little bit of experimentation. Besides needing separate neo4j sessions per thread, it appears to be working fine and shaving wall clock time meaningfully. Happy to put it up as a PR if it helps for discussion.

We haven't had time to work on it and haven't received a PR yet and absolutely would welcome help. How much time savings are you seeing?

I have made a PR https://github.com/lyft/cartography/pull/1053. It is not ready to be merged yet. I want to know how you want to handle exceptions when they occur in worker threads (the threads which are running for each region).

How much time savings are you seeing?

For each resource, the mean time to run the sync takes approximately 10 times less if we parallelly update the data across regions.


Add static keyword

Add static keyword to align with the Razor example.

Do we want to add a build.cmd on this branch?

@kendaleiv I don't think it's necessary to build the gh-pages branch. I can configure TeamCity to ignore it.

Actually, I'm not sure that I can configure TeamCity to ignore PRs based on their target branch. This may just be something we have to live with.


Uncaught Error: Syntax error, unrecognized expression

Hallo, I tried to insert the scroll code into the footer.php of a wordpress site.
First of all I had to change the dollar sign with jQuery, because of conflict problem. The problem seems to reman, though.
The code in the attachment:
footer.txt

You should inspect what are you passing to the plugin, in other words, what's in the href variable.
console.log(href); // or alert(href)

You could try to replace:
var href = jQuery(this).attr('href');

for
var href = this.hash;

The var href is "http://mywebsite.com/#real-title" ... it seems ok but it comes that error.


02_pytorch_classificatio_video odd make_circles behavior

OK sorry. I went on working and had reason to rerun the whole thing and then the X_train was an array. I still don't know why the below did that, but it does not once I rerun everything.
Maybe this is a reasonable thing to do now and then anyway. Just run all, especially when something doesn't make sense.
In the video (at about 9:12) you create the data using make_circles and it returns a numpy array for X and y.
Later this is converted to tensors.
But what I see is make_circles is returning a tensor.  I don't know if something in the make_circles is changed. But the documentation still says it returns a numpy array. Below is code and output.
torch.version
'2.0.0'
from sklearn.datasets import make_circles
n_samples = 1000
X, y = make_circles(n_samples,
noise=0.03,
random_state=12)
len(X), len(y)
X, y
(tensor([[ 0.7629,  0.2129],
[-0.0135, -0.7828],
[-0.6789, -0.4260],
...,
[ 0.2143, -0.9870],
[-0.4084,  0.7029],
[-0.3432, -0.7142]]),
tensor([1., 1., 1., 0., 0., 1., 1., 1., 1., 0., 1., 0., 1., 1., 0., 1., 0., 1.,

I commented the output lines .
What was happening was that I called make_circles.
Then I  output X, y to see them. And they were already tensors.
I still do not know why that happened, but once I re-ran the whole program from the start, I did not see this happen again.
Now any time I see an unexpected result I first re-run everything to see if that clears it.
My environment is probably different. I use jupyter notebook, And the versions of sklearn and pytorch are newer than what is in the course. I don't know what versions Colab has now.
Mine is:
pytorch - 2.0.0
sklearn - 1.2.1

Hi @RayWagner ,
You're likely see an example of Jupyter Notebook state.
For example, when you run a particular cell, the notebook will often keep the "state" of that cell for as long as possible.
This includes when running new cells above/below the original cell.
To remove the state, you can either:

Restart the notebook (like you have)
Override the state by running a similar cell/the same original cell with changed information

Hi Daniel,
Yes, I have seen that and usually I go back and run all the cells. Now and then I also restart it and clear everything.
What I have seen recently is the model seems to keep its state when run more times as I change parameters. So I see the loss curve start where it is already pretty low.
Great video. I have really enjoyed working on pytorch.
I am trying to work on a stock predicting model now and all the examples I found for LSTM and GRU were in tensorflow. I have had to try my best to work with it. Same theories, but the syntax for the model is very different. But it has been fun. Being retired allows me to just have a good time with it.
My new strategy I have been preparing will go back to pytorch because I want to use the stock chart data more as a visual image. I think I can use some of the things you presented in the video. I am thinking of using dense, and CNN and see how that works.
I just have to prepare the data. That is time consuming. I will also use the idea from the video of the files being in a directory that is the label name. That was cool, and I can use that.
Well, I would have a million things to chat about but I understand this is not the way to do that.
Best wished and thanks so much for such a great video tutorial.
Best Regards,
Ray
From: Daniel Bourke @.>
Sent: Thursday, June 1, 2023 9:13 PM
To: mrdbourke/pytorch-deep-learning @.>
Cc: RayWagner @.>; Mention @.>
Subject: Re: [mrdbourke/pytorch-deep-learning] 02_pytorch_classificatio_video odd make_circles behavior (Issue #401)
Hi @RayWagner https://github.com/RayWagner  ,
You're likely see an example of Jupyter Notebook state.
For example, when you run a particular cell, the notebook will often keep the "state" of that cell for as long as possible.
This includes when running new cells above/below the original cell.
To remove the state, you can either:

Restart the notebook (like you have)
Override the state by running a similar cell/the same original cell with changed information

—
Reply to this email directly, view it on GitHub https://github.com/mrdbourke/pytorch-deep-learning/issues/401#issuecomment-1572985106 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A7FWYCMHEPE4JZRVJF2LCN3XJE4YZANCNFSM6AAAAAAW6QCO6A .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A7FWYCNUSEA7D2XOAATI62LXJE4YZA5CNFSM6AAAAAAW6QCO6CWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS5YHMRE.gif Message ID: @.*** @.***> >


Reorganizing words after redirects.

example:
< in | < <
As the second redirect waits only WORD, the result is: syntax error


Cpp - Wtp interfaces connection

I kind dont understand the deployment of empower ( cpp-wtp connection).
You mention that eth0 of both 2 wtps must be connected to the cpp.
But if eth1 of both wtps is not connected with the switch , the wtps dont connect to the controller.
I followed your instructions as you describe in the wiki .
Beside that connecting eth1 of both wtps to the switch and the eth0 to cpp , they connect with the controller.The wtps emmit wifi  but when if i try to connect a client to the empower network, the client does not get IP.

I said eth0 because in my case (alix wtps) the eth0 is the WAN interface
which is bridged
with the OVS. If in you case it is the eth1 to be bridged with the ovs then
you must connect
the wtps to the cpps using the eth1.
Basically the port used to delivere connectivity to the WTP must be
connected to the CPP
and everything should be a single L2 domain.
R.
On 26 April 2017 at 13:52, Georgios Tsiatsios<EMAIL_ADDRESS>wrote:

I kind dont understand the deployment of empower ( cpp-wtp connection).
You mention that eth0 of both 2 wtps must be connected to the cpp.
But if eth1 of both wtps is not connected with the switch , the wtps dont
connect to the controller.
I followed your instructions as you describe in the wiki .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/2, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAdzTO5UDeEwjo5NgTWDEzN8IhBy9VrUks5rzy_sgaJpZM4NIwEU
.

I followed exactly your instructions in the wiki.The config files of both wtps and cpp are exactly the same with yours (but obviously with my custom IPs).But if I connect  only the eth0 with the cpp ,the wtp does not connect to the controller. So whats the point of eth1 in configuration file of wtp ?

It is an ALIX WTP right?
The eth1 is running a local dhcp server. Basically it allows you to connect
to the eth1 port with a laptop
for example and to login in the wtp for management purposes. It is not
really needed for empower, so
you can also remove it.
Can the WTP ping the ip of the controller? You need L3 connectivity between
wtp and controller in order
for this to work. Also this setup assumes that there is a DHCP server on
the network where WTP and
CPPs are located.
R.
On 27 April 2017 at 10:39, Georgios Tsiatsios<EMAIL_ADDRESS>wrote:

I followed exactly your instructions in the wiki.The config files of both
wtps and cpp are exactly the same with yours (but obviously with my custom
IPs).But if I connect only the eth0 with the cpp ,the wtp does not connect
to the controller. So whats the point of eth1 in configuration file of wtp ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/2#issuecomment-297650916,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdzTKlh6agjyHj9Nyiy90r_2aD2tzuSks5r0FRMgaJpZM4NIwEU
.

Yes its a soekris net5501.
If I remove eth1 from the wtp it dont connect to the controller and cant ping.
The only way for me to connect  WTP with the controller is to connect eth1 of wtp with my local switch  and eth0 with the cpp , if I remove the cpp from my deployment in order to connect the wtp with the controller both eth1 and eth0 must be connected with my local switch.

Hi,
check this for example:
https://github.com/5g-empower/5g-empower.github.io/wiki/Network-setup#wtpscpps
Is this the configuration you have in your lab?
That is the setup I have in my lab. The two wtps in the picture are
connected from their eth0 port to ports eth1 and eth2 of the CPP.
Also ports eth1,2,3 of the CPP are bridged together in an OVS bridge, while
eth0 of the CPP is not bridged with the other and is used
for out of band signalling.
The legacy switch in the picture is a distribution switch.
Do you have a dhcp server in your network? Even a simple home router would
work here.
R.
On 27 April 2017 at 11:14, Georgios Tsiatsios<EMAIL_ADDRESS>wrote:

Yes its a soekris net5501.
If I remove eth1 from the wtp it dont connect to the controller and cant
ping.
The only way for me to connect WTP with the controller is to connect eth1
of wtp with my local switch and eth0 with the cpp , if I remove the cpp
from my deployment in order to connect the wtp with the controller both
eth1 and eth0 must be connected with my local switch.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/2#issuecomment-297659451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdzTC7FVJujFAUIXFvLzXH5g3uw8DGVks5r0FxvgaJpZM4NIwEU
.

Hi,
Lets start from the beginning. We have two WTPs, one CPP, one Controller on our network with DHCP Server. The WTPs work fine without the CPP, hence connected with their eth0 directly on the network's switch.On the CPP now,it has its eth0 connected to the switch and gets IP just fine, when running the lvnf agent, the controller sees the CPP normally and it is therefore connected. The problem starts when we connect the WTPs to the CPP (both WTP eth0 to CPP's eth1 and eth2), as they dont connect to the controller at all. I believe that the problem is on the CPP side regarding the bridge, because when we restart the network on the CPP it says "Ignoring unknown interface allow-ovs=allow-ovs. done. ". The CPP runs on Debian Wheezy 7.11, with openvswitch 2.4.0 and Python 3.6.

could you copy paste the content of /etc/network/interfaces and the output
of ifconfig?
R.
On 28 April 2017 at 16:06, Nikos Maroulis<EMAIL_ADDRESS>wrote:

Hi,
Lets start from the beginning. We have two WTPs, one CPP, one Controller
on our network with DHCP Server. The WTPs work fine without the CPP, hence
connected with their eth0 directly on the network's switch.On the CPP
now,it has its eth0 connected to the switch and gets IP just fine, when
running the lvnf agent, the controller sees the CPP normally and it is
therefore connected. The problem starts when we connect the WTPs to the CPP
(both WTP eth0 to CPP's eth1 and eth2), as they dont connect to the
controller at all. I believe that the problem is on the CPP side regarding
the bridge, because when we restart the network on the CPP it says
"Ignoring unknown interface allow-ovs=allow-ovs. done. ". The CPP runs on
Debian Wheezy 7.11, with openvswitch 2.4.0 and Python 3.6.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/2#issuecomment-298007222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdzTImo7CbXMlUFpQhnqJpcxNcIyqvyks5r0fJvgaJpZM4NIwEU
.

The "ifconfig -a" command has the output:
"""
br0       Link encap:Ethernet  HWaddr 00:00:24:cd:7a:f9
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
eth0      Link encap:Ethernet  HWaddr 00:00:24:cd:7a:f8
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::200:24ff:fecd:7af8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:1120 errors:0 dropped:0 overruns:0 frame:0
TX packets:451 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:108099 (105.5 KiB)  TX bytes:56649 (55.3 KiB)
Interrupt:11 Base address:0xe100
eth1      Link encap:Ethernet  HWaddr 00:00:24:cd:7a:f9
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Interrupt:5 Base address:0xe200
eth2      Link encap:Ethernet  HWaddr 00:00:24:cd:7a:fa
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Interrupt:9 Base address:0xe300
eth3      Link encap:Ethernet  HWaddr 00:00:24:cd:7a:fb
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Interrupt:12 Base address:0xe400
lo        Link encap:Local Loopback
inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
ovs-system Link encap:Ethernet  HWaddr 22:b7:a3:2a:3d:8d
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
wlan0     Link encap:Ethernet  HWaddr 00:1b:b1:04:56:d6
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
"""
, the "ifconfig" command only shows the lo and eth0 interfaces, the "ifconfig br0 up" etc works but nothing really changes. The interfaces file is exactly the same as your CPP wiki. (Our soekris also has 4 ethernet ports)

strange, it seems that the other interfaces are not brought up at boot and
then maybe for this reason they cannot be added to the OVS.
There should be a command in the ovs CLI suite for listing the ports
attached to a bridge, it should be somthing like:
ovs-ofctl show br0
Could you check it?
R.
On 2 May 2017 at 13:12, Nikos Maroulis<EMAIL_ADDRESS>wrote:

The "ifconfig -a" command has the output:
"""
br0 Link encap:Ethernet HWaddr 00:00:24💿7a:f9
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:00:24💿7a:f8
inet addr:<IP_ADDRESS> Bcast:<IP_ADDRESS> Mask:<IP_ADDRESS>
inet6 addr: fe80::200:24ff:fecd:7af8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1120 errors:0 dropped:0 overruns:0 frame:0
TX packets:451 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:108099 (105.5 KiB) TX bytes:56649 (55.3 KiB)
Interrupt:11 Base address:0xe100
eth1 Link encap:Ethernet HWaddr 00:00:24💿7a:f9
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:5 Base address:0xe200
eth2 Link encap:Ethernet HWaddr 00:00:24💿7a:fa
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:9 Base address:0xe300
eth3 Link encap:Ethernet HWaddr 00:00:24💿7a:fb
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:12 Base address:0xe400
lo Link encap:Local Loopback
inet addr:<IP_ADDRESS> Mask:<IP_ADDRESS>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ovs-system Link encap:Ethernet HWaddr 22:b7:a3:2a:3d:8d
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:1b:b1:04:56:d6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
"""
, the "ifconfig" command only shows the lo and eth0 interfaces, the
"ifconfig br0 up" etc works but nothing really changes. The interfaces file
is exactly the same as your CPP wiki. (Our soekris also has 4 ethernet
ports)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/2#issuecomment-298606996,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdzTCU3v_7Xp3RANLSpMxkAVT3bTBNyks5r1w-cgaJpZM4NIwEU
.

the output of "ovs-ofctl show br0" is:
"""
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000000024cd7af9
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
1(eth1): addr:00:00:24:cd:7a:f9
config:     0
state:      0
current:    100MB-FD AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG AUTO_PAUSE
supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG
speed: 100 Mbps now, 100 Mbps max
2(eth2): addr:00:00:24:cd:7a:fa
config:     PORT_DOWN
state:      LINK_DOWN
current:    10MB-HD AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG AUTO_PAUSE
supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG
speed: 10 Mbps now, 100 Mbps max
3(eth3): addr:00:00:24:cd:7a:fb
config:     PORT_DOWN
state:      LINK_DOWN
current:    10MB-HD AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG AUTO_PAUSE
supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD COPPER AUTO_NEG
speed: 10 Mbps now, 100 Mbps max
LOCAL(br0): addr:00:00:24:cd:7a:f9
config:     0
state:      0
speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
"""
, so i guess the ports are attached to the bridge. Could it be the WTP's fault for not connecting? In order to connect to the controller via a CPP, do I need to change anything in the /etc/config/files of the WTP?


Fix covers extending outside the boundary in Chrome

For example: https://vglist.co/games/29115 or https://vglist.co/games/28616

This only happens in Chrome, of course. 🙄  It also extends outside its normal space on smaller viewport widths.

Example on small screen:


Feature: multilevel progressbar

It would be great to be able to wrap several nested iterables like
for i in progressbar.progressbar(range(20)):
    for j in progressbar.progressbar(range(5)):
        time.sleep(0.1)

As for now this results in multiple progress bars appearing one after another. It could look like this instead
20% (1 of 5) |#####                     | Elapsed Time: 0:00:02 ETA:   0:00:03
30% (6 of 20) |#####                    | Elapsed Time: 0:01:02 ETA:   0:06:01

Also, it looks like this could be a possible step on the way to that one https://github.com/WoLpH/python-progressbar/issues/176

It's indeed very similar to #176 and I'm guessing the solution will be the same. Although the threading versions might take slightly more effort.
It's been on my to-do list for a while but it's going to be a bit of work to do it right.

Not quite the same, but I implemented a multi-bar: #208

@paulo-raca it looks like something that solves it and even looks gorgeous. Thanks for your work!

@WoLpH I'm happy with #208.
Feel free to close this one if it looks redundant to you now.

I love the multibar hack but I still think there is a need for a good multi progressbar solution. There are several limitations to this implementation which makes it hard/impractical to use in some cases.
That doesn't make this any less useful, it could be an addition to this feature. Once the multiple progressbars are working this one could be the "global" progressbar between them :)

As a reasonable workaround, I've wrote this little bit of script:
import sys
import time

import progressbar

class LineOffsetStreamWrapper:
    UP = '\033[F'
    DOWN = '\033[B'

    def __init__(self, lines=0, stream=sys.stderr):
        self.stream = stream
        self.lines = lines

    def write(self, data):
        self.stream.write(self.UP * self.lines)
        self.stream.write(data)
        self.stream.write(self.DOWN * self.lines)
        self.stream.flush()

    def __getattr__(self, name):
        return getattr(self.stream, name)

bars = []
for i in range(5):
    bars.append(progressbar.ProgressBar(
        fd=LineOffsetStreamWrapper(i),
        max_value=1000,
    ))

    if i:
        print('Reserve a line for the progressbar')

for i in range(100):
    for j, bar in enumerate(bars, 1):
        bar.update(i * j)
    time.sleep(0.1)

It's certainly not as foolproof and well-tested as the rest of the progressbar code, but I think it should do the trick for the common use-cases :)

I've properly added the feature of multiple progressbars now.
The approach is a bit different from tqdm but I personally think this is a more obvious (although slightly more verbose) approach.
The MultiBar can be used both using a with MultiBar() as multibar: and using a regular instance. You can manually render on demand using multibar.render() if you already have a display loop. If you want to have it render in the background you can use multibar.start() to run it as a background thread.
I'm still testing with it but I believe it works quite well. Usage: https://github.com/wolph/python-progressbar#multiple-threaded-progressbars
import random
import threading
import time

import progressbar

BARS = 5
N = 50

def do_something(bar):
    for i in bar(range(N)):
        # Sleep up to 0.1 seconds
        time.sleep(random.random() * 0.1)

        # print messages at random intervals to show how extra output works
        if random.random() > 0.9:
            bar.print('random message for bar', bar, i)

with progressbar.MultiBar() as multibar:
    for i in range(BARS):
        # Get a progressbar
        bar = multibar[f'Thread label here {i}']
        # Create a thread and pass the progressbar
        threading.Thread(target=do_something, args=(bar,)).start()

You can add your custom progressbars to a MultiBar instance like this:
multi['Some label'] = your_progress

The new version with this feature has been released :)

You did not add an example in the examples.py file from what I can see. Would be nice to have one!

The issue is that the threaded example, opposed to all other examples, doesn't work in all environments so I'm not a 100% sure where I should enable/disable it. But I'll add it to the examples at least for where I can detect an ANSI terminal :)


Unable to determine a difference between solid colored images

This library returns a 100% match for these two images.

It also returns a 100% match for these two images.

If you shrink them to a single pixel, the red and blue still match with a value of 100, but the black and white match with 98.4.

Hello @earthiverse ! Thanks for opening the issue, I was able to reproduce it - will investigate and work on the solution

Changed the composer.lock file to update dependencies. Developed methods to calculate the distance between colors and compute the average RGB color value of an image based on Euclidean distance. This allowed for considering color similarity when comparing images, thus providing a more accurate similarity assessment. Additionally, color similarity was incorporated into the comparison of image hashes, helping to adjust the comparison result. Tests were added to verify the correctness of the image comparison method, and existing tests were fixed. These changes improved the accuracy of image comparison, preventing unjustified 100% matches between similar but not identical images.


codimd: build with nodejs-8_x

Motivation for this change
This diff regenerates the package sets for codimd and codemirror
using NodeJS 8 to get rid of the deprecated[1] nodejs-6_x.
Additionally the following issues had to be fixed during the update:

The package js-sequence-diagram has been removed from the NPM
registry and was replaced by a security holding package[2]. The
package was published by a third-party (upstream only supports bower
builds), so it's unclear whether the package will re-appear[3].
As the tarballs still exist (and the hash didn't change), the package
will be loaded manually into the build env.

For the babel-related packages, dontNpmInstall will be set for
node2nix installs as some of those packages bundle a
package-lock.json that triggers ENOTCACHED errors for optional
dependencies[4].

For now it should be sufficient to use NodeJS 8 (codimd v1.2.x doesn't
support NodeJS 10), in the long term we probably want to use yarn2nix
here with NodeJS 10. This is much rather a fix to get rid of another
NodeJS 6 dependency.
[1] nodejs-6_x is about to be deprecated, see #58976
[2] https://www.npmjs.com/package/js-sequence-diagrams,
https://github.com/npm/security-holder
[3] https://github.com/bramp/js-sequence-diagrams/issues/212
[4] https://github.com/svanderburg/node2nix/issues/134
Things done

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

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

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

/cc maintainer @WilliButz.

@GrahamcOfBorg test codimd


can suppress command execution

When handling diagnostics request command execution is suppressed

So does this fix #633?

So does this fix #633?

yes, it seems


[bug]: Not choosing a value in a select nested in a popover closes the popover.

Describe the bug
if a select is placed in a popover the popover closes if you click out of the select without choosing a value.
Affected component/components
Popover
How to reproduce
click on popover
enter select
click back into the popover
popover closes

Codesandbox/StackBlitz link
https://v0.dev/r/TOP7DD1xxY1?share=QI8DlC6dERDKeXgz36iMHglr
Logs
No response
System Info
v0

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Installation Instructions for Dropdown Menu
If you encounter issues installing the dropdown menu using the command:
npx shadcn@latest add dropdown-menu
You can follow the manual installation process outlined in the documentation. This method is guaranteed to work.
Feel free to ask if you still have any problems; I'm happy to help!

I encountered this bug too, and can't find a workaround to it :(

Faced the same issue today, funnily enough the v0.dev link shows the correct behaviour now 🤔. I'm using "@radix-ui/react-popover": "1.1.1" (also tried 1.1.0 and 1.1.2) and "@radix-ui/react-select": "2.1.2".
In case this helps anyone else, my workaround was to control the open state on both the Popover and Select, and prevent the Popover from closing if the Select is currently open. Something like:
  const [open, setOpen] = useState(false);
  const [selectOpen, setSelectOpen] = useState(false);

  <Popover open={open} onOpenChange={(v) => !selectOpen && setOpen(v)}>
    {/* ... */}
    <Select open={selectOpen} onOpenChange={setSelectOpen}>
      {/* ... */}
    </Select>
    {/* ... */}
  </Popover>


Include originating MapBrowserEvent in ol.DragBoxEvent

Fixes #4564

Looks good, please merge.

Thanks for the review


[mock] bring back headerContains()

For some reason it is in the docs but was taken out of the current code.
Refer: https://stackoverflow.com/q/59314890/143475
And current doc screenshot:

I dare say this is useful and should be available.

released 0.9.5


Produce Lyra builds (via Travis)

Enable and configure Travis to build (and optionally store) builds of Lyra for Linux and macOS

#26

I'm gonna remove this from 0.1 - but we do need to come up with a packaging/release strategy.

In #242 we're changing the build dir structure to support this work:
build
 └─ bin
     └─ lyra
 └─ goplugins
     └─ aws
     └─ puppetdsl
     └─ ...

That aligns with the separation of bin from plugins that we're looking for in brew. We also need workflows and types. Ultimately the brew installation should look like this:
lyra/0.0.1
 └─ bin
     └─ lyra
 └─ goplugins
     └─ aws
     └─ puppetdsl
     └─ ...
 └─ workflows
     └─ aws_pp.pp
     └─ aws.yaml
     └─ ...
 └─ types
     └─ aws.pp
     └─ ...


[Bug] Template variable failed to work when add column

Try add a variable with demo data in online demo.
https://grafana-infinity-datasource.herokuapp.com/d/try/try

What manual edit is needed here? I can't see it in the linked issue

Manually edit the dashboard json will help.

Thank you for the reply. I realise it's a dashboard JSON edit but I'm not sure where in the JSON to make the edit. Is it the nulls reported by abferm that are the issue? I tried removing those lines and upon saving it just refreshed with all the nulls returned. Setting them to 0 did nothing either. I'm lost about what the actual workaround is


Fix timeseries publish logic

Add timeseries storage struct
Modify publish request/response logic about time series
Modify ack timestamp interval value

Closes: #191

Codecov Report
Base: 80.92% // Head: 80.99% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (b94e2e7) compared to base (0621b3c).
Patch coverage: 95.65% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #192      +/-   ##
==========================================
+ Coverage   80.92%   80.99%   +0.06%
==========================================
  Files          13       13
  Lines        2281     2299      +18
==========================================
+ Hits         1846     1862      +16
- Misses        435      437       +2

Impacted Files
Coverage Δ

src/publish.rs
81.79% <95.31%> (+0.47%)
:arrow_up:

src/ingestion.rs
74.28% <100.00%> (-0.08%)
:arrow_down:

src/publish/tests.rs
99.14% <100.00%> (-0.01%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix(select): stop passing value to menu on input blur #29

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #29
Summary:
Removes the functionality to pass the input value to menu on blur.
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 1.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Integration tests against dockerized PostGIS database

Hey @K4ST0R would you be open to me trying to accomplish this? I think this could add some value by ensuring the SQL statements created run against an actual PostGIS database. I think that would be a stronger validation method than just checking the SQL matches an expected value.


Packages in Preview not being queued for harvesting

These two packages are not being queued for harvesting.  @geneh identified the issue as "As for the packages below, these are preview versions, so these versions are not displayed in https://clearlydefined.io/harvest page when trying to pick a version."
https://www.nuget.org/packages/Microsoft.NETCore.Platforms
https://clearlydefined.io/definitions/nuget/nuget/-/microsoft.powershell.native/7.0.0-preview.1

Sorry @ariel11 , i don't get what is the issue on the website here. Maybe an extended explanation of the problem would help. Thanks!

The specific versions are nuget/nuget/-/Microsoft.PowerShell.Native/7.0.0-preview.1 and nuget/nuget/-/Microsoft.NETCore.Platforms/3.0.0-preview5.19224.8
I assume the user has tried to harvest these components from https://clearlydefined.io/harvest but the preview options do not show up. I wonder if it's by design. If so, should we be fetching all the versions here including the preview ones.

It looks like the packages have been harvested using /harvest API:
{
	"tool": "package",
	"coordinates": "nuget/nuget/-/Microsoft.PowerShell.Native/7.0.0-preview.1"
}

It seems like the crawler has ignored these package versions possibly due to preview version. Moving this work item to crawler to investigate.


fix(sec): upgrade gopkg.in/yaml.v3 to 3.0.0

What happened？
There are 1 security vulnerabilities found in gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b

CVE-2022-28948

What did I do？
Upgrade gopkg.in/yaml.v3 from v3.0.0-20210107192922-496545a6307b to 3.0.0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

Coverage: 74.182% (+0.0%) from 74.182% when pulling e9d93b4439ce9b04375684c73666b0c7995a9fb7 on wjl110:oscs_fix_cf81mc8au51vh2d7rhj0 into c7e0172e0fd176bdc521afb5186818a7db6b77ac on go-playground:master.


The specified log group does not exist message

I can't get this to work.
The thing is that the log-group DOES exist, BUT
running node_modules/.bin/smoketail -f /aws/lambda/lambda-experts-form gives me a
The specified log group does not exist.

while running aws logs filter-log-events --log-group-name /aws/lambda/lambda-experts-form
shows me the logs.
Any ideas?

hi, had the same problem at first, setting the region got it working for me
-r eu-west-1

@thebarty - Apologies for the delayed response.  I wasn't getting emails from github for issues.  Not sure if @ThomasAndrewMacLean 's suggestion helped you out.  Another potential cause could be authentication, particularly if you are accessing more than one AWS account, or using multiple credentials.  I'm working on an update now that will allow a named profile (as found in ~/.aws/credentials) to be used when running the cli.


feat: added number of open issues

Fixes #153
I've noticed that the GitHub API's open_issues_count field currently includes both the count of open Issues and open Pull Requests. This is because GitHub counts PRs as issues in their system. I hope this would not be a problem?

Also can you fix this problem? And also show the open PRs

Alright, I'll work on the tooltip.
For the open PRs, GitHub's API does not provide the number of open PRs

@max-programming I've adjusted the tooltip

Alright, I'll work on the tooltip.
For the open PRs, GitHub's API does not provide the number of open PRs

Then I think it's better to put the number of issues in the center as there's nothing beside it

Do you mean putting the three buttons in one line? Doing that would make it unresponsive and it's not going to look nice on small screens.

@Keith-Web3 No. Make it like this

@max-programming Done.

@Keith-Web3 Looks good! Just a few more changes. There is too much margin around the first two boxes and the last box looks a lot compressed

Sadly, there's no way to get rid of the extra margin as the browser has no way of knowing when items are wrapping. Also, the buttons adjust to the size of their content. This is the best way to ensure responsiveness and it's why the issues button appears small.

@Keith-Web3 Maybe you can increase the width or min width of that card.
That might fix it and reduce the whitespace

Alright then, I'll make another pull request. Using grid won't work but I've got one last idea.

Hey! It all looks good. Imo, it's better to have it this way though.

And the current font size when hovered doesn't really go with it. Making it centered + a bit small would be better with it.

@janaSunrise Having all three side by side will increase the width of the card significantly, won't it?

@max-programming Yes it would. There's been a lot of back and forth on just the button alignment 🥲

@all-contributors please add @Keith-Web3 for ideas, code

@janaSunrise Having all three side by side will increase the width of the card significantly, won't it?

Yup, but we can make it smaller, don't you think?


Error writing file (cl 1067) seems to be result of g++ version

I was getting the dreaded [ERROR] Error writing output data/reads/SRR15089604/r2.proc.gtpro_raw.gz.tsv.gz cl 1067 with some of my Docker/Singularity images for GT-Pro but not others.
I seem to have solved the issue by switching from the mambaforge base image condaforge/mambaforge:4.11.0-4 to ubuntu:18.04, suggesting that it may be the g++ version that matters.
old-image > g++ --version
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

new-image > g++ --version
g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

Any idea why?

Hey Byron, thanks for reporting this issue. I have seen other reports on cl 1067 error, which is seemingly HPC and gxx related. I also found using -C flag to specify a writable location could consistently solve the problem on my side. Please see a previous thread for more details: issue #44 . Sorry for missing your comment. Github (or I) messed up my notification for this repo somehow. If I haven't got back to you next time, please pin me at<EMAIL_ADDRESS>

Closing it for now, please feel free to reopen it if the problem emerges again.


Certificate verification failing when Digital signature and TLS1.3 enabled (IDFGH-14097)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5.3.1
Espressif SoC revision.
ESP32-C3 QFN32(Rev v0.3)
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-C3-MINI-1
Power Supply used.
USB
What is the expected behavior?
It looks like MBEDTLS_PK_RSA is the appropriate key type when digital signing peripheral is in use.
But device chooses MBEDTLS_PK_RSASSA_PSS option and finally failing to sign/verify in the MBEDTLS_SSL_CLIENT_CERTIFICATE_VERIFY state.
It seems ssl_preset_default_sig_algs is containing
MBEDTLS_TLS1_3_SIG_RSA_PSS_RSAE_SHA512
MBEDTLS_TLS1_3_SIG_RSA_PSS_RSAE_SHA384
and
MBEDTLS_TLS1_3_SIG_RSA_PSS_RSAE_SHA256
which is not really supported by DS peripheral.
What is the actual behavior?
See the logs below for more details:
The device is rejecting the certificate signature and sending alert to the server.
I tried by disabling MBEDTLS_X509_RSASSA_PSS_SUPPORT macro from mbedtls_config.h. But the error is still happening.
Steps to reproduce.
Perform the TLS 1.3 handshake with certificates(RootCA and temporary cert).
Debug Logs.
Standard setting
----------------
I (8944) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls.c:4525 client state: MBEDTLS_SSL_CLIENT_CERTIFICATE_VERIFY

I (8954) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1132 => write certificate verify

I (8964) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1093 CertificateVerify signature failed with rsa_pss_rsae_sha256

I (8984) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1095 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

I (8994) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1093 CertificateVerify signature failed with rsa_pss_rsae_sha384

I (9004) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1095 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

I (9024) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1093 CertificateVerify signature failed with rsa_pss_rsae_sha512

I (9034) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1095 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

W (9044) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1112 no suitable signature algorithm

I (9064) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1150 <= write certificate verify

I (9074) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:5168 => send alert message

I (9084) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2943 => write record

I (9084) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:935 => encrypt buf

I (9094) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:1474 <= encrypt buf

I (9104) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2353 => flush output

I (9114) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2367 message length: 37, out_left: 37

I (9124) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2374 ssl->f_send() returned 37 (-0xffffffdb)

I (9134) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2401 <= flush output

I (9144) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:3080 <= write record

I (9154) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:5180 <= send alert message

I (9164) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls.c:4617 <= handshake

E (9174) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x6E00
I (9174) esp-tls-mbedtls: Certificate verified.
E (9184) esp-tls: Failed to open new connection
E (9194) transport_base: Failed to open a new connection
E (9194) HTTP_CLIENT: Connection failed, sock < 0

------------------------------------------------
MBEDTLS_X509_RSASSA_PSS_SUPPORT disabled setting
------------------------------------------------
I (8814) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls.c:4525 client state: MBEDTLS_SSL_CLIENT_CERTIFICATE_VERIFY

I (8824) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1140 => write certificate verify
I (8864) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1100 CertificateVerify signature failed with rsa_pss_rsae_sha256

I (8874) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1102 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

I (8944) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1100 CertificateVerify signature failed with rsa_pss_rsae_sha384

I (8954) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1102 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

I (9024) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1100 CertificateVerify signature failed with rsa_pss_rsae_sha512

I (9034) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1102 mbedtls_pk_sign_ext() returned -16128 (-0x3f00)

W (9094) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1120 no suitable signature algorithm

I (9104) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls13_generic.c:1158 <= write certificate verify

I (9114) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:5168 => send alert message

I (9124) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2943 => write record

I (9134) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:935 => encrypt buf

I (9144) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:1474 <= encrypt buf

I (9154) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2353 => flush output

I (9164) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2367 message length: 37, out_left: 37

I (9174) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2374 ssl->f_send() returned 37 (-0xffffffdb)

I (9184) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:2401 <= flush output

I (9194) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:3080 <= write record

I (9204) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_msg.c:5180 <= send alert message

I (9214) mbedtls: IDF\components\mbedtls\mbedtls\library\ssl_tls.c:4617 <= handshake

E (9214) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x6E00
I (9224) esp-tls-mbedtls: Certificate verified.
E (9234) esp-tls: Failed to open new connection
E (9234) transport_base: Failed to open a new connection
E (9244) HTTP_CLIENT: Connection failed, sock < 0

More Information.
No response

We figured out the root cause of this issue.
In certificate verify stage the hash must be encoded with pkcs1 v21 standard for TLS1.3.
DS(Digital siging) peripheral is not supporting this instead it is encoding with PKCS1 v1.5 using rsa_rsassa_pkcs1_v15_encode
This issue is now fixed in these PR by introducing rsa_rsassa_pkcs1_v21_encode()
https://github.com/cryptoquantique/esp-idf/pull/1
https://github.com/cryptoquantique/mbedtls/pull/2

@msivanesancq Thanks for the issue.
I see that the issue is that TLS 1.3 expects v21 encoding instead of the v15 encoding used for TLS 1.2.
I saw the changes in your fork, instead of defining it on compile option, I think we should select it dynamically based on the signing algorithm used.
I will make the relevant changes in esp-idf.


Sensors unavailable

Describe the bug
Sensors unavailable, despite being able to see state change in add-on > texecom2mqtt > Logs
Application version
1.1.6
Texecom alarm type
Premier Elite 24 (V5.04.01LS1)
Home Assistant version
core-2021.11.4
Debug log
No read debug.... log updates when event has triggered.
2021-11-17 16:31:08 - INFO: Kitchen PIR status changed to Active
2021-11-17 16:31:08 - DEBUG: Publishing to texecom2mqtt/zone/kitchen_pir: {"name":"Kitchen PIR","number":4,"areas":["A"],"status":1,"type":"Guard"}
2021-11-17 16:31:12 - INFO: Kitchen PIR status changed to Secure
2021-11-17 16:31:12 - DEBUG: Publishing to texecom2mqtt/zone/kitchen_pir: {"name":"Kitchen PIR","number":4,"areas":["A"],"status":0,"type":"Guard"}
2021-11-17 16:31:14 - DEBUG: Updating system power...
2021-11-17 16:31:14 - DEBUG: Publishing to texecom2mqtt/power:

Believe I have the same issue.  Log appears to update on zone status change but no entries created for the sensors under the texecom2mqtt device?
2021-11-17 23:48:41 - INFO: Starting texecom2mqtt v1.1.6...
2021-11-17 23:48:41 - INFO: Connected to alarm, sleeping for 1 second...
2021-11-17 23:48:42 - INFO: Connection ready
2021-11-17 23:48:42 - INFO: Fetched serial number: *******
2021-11-17 23:48:42 - INFO: Logging in
2021-11-17 23:48:42 - INFO: Successfully logged in
2021-11-17 23:48:43 - INFO: Connected to MQTT
2021-11-17 23:48:43 - INFO: Fetched panel info: Premier Elite 24 (V4.03.00LS1)
2021-11-17 23:48:44 - INFO: Fetched Area A: House Area
2021-11-17 23:48:44 - INFO: Fetched Area B: Shed Area
.........
2021-11-17 23:48:53 - INFO: Updating all area states...
2021-11-17 23:48:53 - INFO: Application ready
2021-11-18 00:01:30 - INFO: 1st Floor PIR status changed to Active
2021-11-18 00:01:38 - INFO: 1st Floor PIR status changed to Secure

Interestingly if I listen to texecom2mqtt/status I get the following.... despite everything being online and functioning via the app, and receiving status messages frm the "log"
Message 0 received on texecom2mqtt/status at 14:05:
offline

I believe I also have this problem
I've just got this installed and working (after adding a ComWIFI to my panel to defeat the single-tcp-connection farce of the SmartCom). All was working gloriously and then it stopped. Can't say that I did anything other than maybe restarted HA as part of some unrelated config changes

2021-11-26 20:49:20 - INFO: Starting texecom2mqtt v1.1.6...
2021-11-26 20:49:21 - INFO: Connected to alarm, sleeping for 1 second...
2021-11-26 20:49:22 - INFO: Connection ready
2021-11-26 20:49:22 - INFO: Fetched serial number: XXXXXX
2021-11-26 20:49:22 - INFO: Logging in
2021-11-26 20:49:22 - INFO: Successfully logged in
2021-11-26 20:49:22 - INFO: Connected to MQTT
2021-11-26 20:49:23 - INFO: Fetched panel info: Premier Elite 64 (V5.00.03LS1)
2021-11-26 20:49:27 - INFO: Fetched Area A: Whole house
2021-11-26 20:49:27 - INFO: Fetched Area B: Area B
2021-11-26 20:49:27 - INFO: Fetched Area C: Area C
2021-11-26 20:49:27 - INFO: Fetched Area D: Area D
2021-11-26 20:49:40 - INFO: Fetched Zone 9: Front Door (Type: Entry/Exit 1; Areas: A)
2021-11-26 20:49:41 - INFO: Fetched Zone 10: Office (Type: Guard; Areas: A)
...
2021-11-26 20:50:11 - INFO: Updating all zone states...
2021-11-26 20:50:12 - INFO: Updating all area states...
2021-11-26 20:50:12 - INFO: Application ready

All devices showing as Unavailable....

I am glad it’s not just me, my addon also struggles to connect to the unit first time and sometimes fails to retrieve the serial number and exits out - not sure if some timeout setting needs to be adjusted here.
Just to be clear my HA server is hard wired into same switch as texe connect unit and I have no issue with the texecom unit establishing a connection.

I'm happy to help debug this, where is the actual code?

I think the problem is that the texecom API is under NDA so not publicly available, but guess nothing stopping you from pulling the docker image and having a poke.
Maybe worth signing the NDA so original author can share code code with you if the agreement allows.

Oh yeah, I remember reading that on a thread somewhere.
Do you know how to get mqqt explorer to show what's going on? I've connected it to my ha instance and I see it connect in the mqtt logs, but nothing ever shows in it

Unsure outside of the topic listener in the mqtt plug-in.
I expect there is some code that is conditionally ran when texecom2mqtt/status is “online” and shows sensors as unavailable when showing “offline”.
maybe something has changed in the texecom API recently.

Could you both kindly post your config? It might help to debug the issue

texecom:
  host: 192.168.XXX.XXX
  udl_password: 'XXXX'
mqtt:
  host: core-mosquitto
homeassistant:
  discovery: true
areas: []
zones: []

Not sure if its related but on restarting the add-on I occasionally get this:
2021-11-28 12:58:05 - INFO: Starting texecom2mqtt v1.1.6...
2021-11-28 12:58:05 - INFO: Connected to alarm, sleeping for 1 second...
2021-11-28 12:58:06 - INFO: Connection ready
2021-11-28 12:58:06 - INFO: Fetched serial number: 48
2021-11-28 12:58:06 - INFO: Logging in
/snapshot/app/dist/texecom/texecom.js:81
            throw new Error(`Unexpected start, expected 't', got 0x${headerStart.toString(16)}`);
            ^
Error: Unexpected start, expected 't', got 0x41
    at Texecom.parseBuffer (/snapshot/app/dist/texecom/texecom.js:81:19)
    at Socket.<anonymous> (/snapshot/app/dist/texecom/texecom.js:32:18)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:186:23)

Also notice "48" is not my panels serial number

Yeah that's a known issue where the panel sometimes sends corrupt data when re-connecting. I'm hoping to fix at some point but it's unrelated.
Could you try adding a clientId to your config? So it will be:
texecom:
  host: 192.168.XXX.XXX
  udl_password: 'XXXX'
mqtt:
  host: core-mosquitto
  clientId: texecom2mqtt
homeassistant:
  discovery: true
areas: []
zones: []

If you could add that and then let me know if that fixes it, that would be much appreciated.

Updated config as above, restarted Add-On, get positive logs.
Everything still unavailable.
Restarted whole of HA

my config pretty much the same. Is there any higher level of debug logging available?

@dchesterton  I've added log: debug to mine also, and the "successful" logs are now full of debug intel - is this of any use to you? Will DM if so to avoid posting publically if thats ok

Yeah, it definitely could be useful. Please feel free to DM it

Emailed you some logs. LMK how else I can be useful. Cheers!

How’s things looking with this issue ? Can be of any assistance testing, providing more debug logs?

I've had a look at the logs and I can't figure out anything immediately wrong.
I believe the root problem is that the texecom2mqtt/status topic is getting set to offline which causes Home Assistant to show the sensors/alarms as unavailable.
When the app connects to the MQTT broker it configures a "last will" message which sets the topic to offline if/when the app disconnects unexpectedly.
My assumption is that the app might be losing connection to MQTT, the MQTT broker publishes the last will message, the app then recovers the connection but it doesn't re-publish the status. Unfortunately, I can't replicate this behaviour so I'm somewhat guessing.
I've pushed an update which adds some additional logging around the MQTT connection. If you could kindly send the new debug logs when the issue happens again it'd be much appreciated. Also, if you can let me know what the value of the texecom2mqtt/status topic is at the time (I normally use MQTT Explorer for this sort of thing) that'd help.

Installed the update and its working. (interestingly i tried uninstalling and reinstalling the previous version and that didn't cure it)
Ive saved the boot logs, I'll supply them and logs of a broken boot when it happens.
Thanks for your efforts!

Not working for me I’m afraid still.
One thing I do notice is that it never connects first time for me.

Could it be possible that it’s setting the status to offline but then never setting it back to online?
I’ll send you over my debug logs, currently running in trace logging level.

Mutliple restarts later and its still working for me 🤷
Will report back (presumably immediately after posting this knowing my luck) when it breaks

I’ve made some configuration changes, replaced “core-mosquitto” with the IP of my HA install and also declared the credentials stored in the mosquitto addon in the texecom2mqtt config and seems to be a little more stable and has endured a number of reboots perhaps there was some race conditions.
Will monitor over next few days.

If you are building the docker image from alpine, please consider buster-slim.
There’s been a spate of recent issues with alpine over the last 12 months with DNS issues.

Seems to be running stable since my configuration changes.

Just to update from me, I think this is working now (having done nothing except installing the debug build).
However, Its currently offline for me but I think thats due to some unrelated network changes I made. I don't have time to investigate this for a few weeks due to Christmas but I shall report back asap with an update.

OK, had a moment to look at this and its definitely still broken :(
Logs look like this:
2021-12-12 12:52:58 - DEBUG: Updating system power...
2021-12-12 12:52:58 - DEBUG: Publishing to texecom2mqtt/status: online
2021-12-12 12:52:58 - DEBUG: Publishing to texecom2mqtt/power: {"battery_charging_current":9,"battery_voltage":13.63,"panel_current":261,"panel_voltage":13.7}

but all the sensors are Unavailable :(

My logs now look like this:
2021-12-17 14:42:17 - INFO: Starting texecom2mqtt v1.1.8 (Node v16.13.0)...
2021-12-17 14:42:17 - INFO: Connected to alarm, sleeping for 1 second...
2021-12-17 14:42:18 - INFO: Connection ready
2021-12-17 14:42:18 - DEBUG: Executing serial number command
2021-12-17 14:42:18 - INFO: Fetched serial number: XXXXXXXX
2021-12-17 14:42:18 - INFO: Logging in
2021-12-17 14:42:19 - ERROR: Could not log in
2021-12-17 14:42:19 - DEBUG: Ending socket connection to panel
2021-12-17 14:42:19 - DEBUG: Socket connection to panel ended
2021-12-17 14:42:19 - DEBUG: Panel socket closed
2021-12-17 14:42:19 - DEBUG: Publishing to texecom2mqtt/status: online
2021-12-17 14:42:19 - INFO: Connected to MQTT: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0)
2021-12-17 14:42:22 - DEBUG: Command 22 timed out (attempt 1, id: 1).
2021-12-17 14:42:26 - DEBUG: Command 22 timed out (attempt 2, id: 1).
2021-12-17 14:42:29 - DEBUG: Command 22 timed out (attempt 3, id: 1).
2021-12-17 14:42:33 - DEBUG: Command 22 timed out (attempt 4, id: 1).
2021-12-17 14:42:36 - DEBUG: Command 22 timed out (attempt 5, id: 1).
2021-12-17 14:42:36 - ERROR: Unhandled rejection - Command 22 timed out 5 times and could not be completed
2021-12-17 14:42:36 - DEBUG: Publishing to texecom2mqtt/status: offline

Logs are back to this, having done nothing:
{"battery_charging_current":0,"battery_voltage":13.63,"panel_current":261,"panel_voltage":13.7}
2021-12-18 15:06:17 - DEBUG: Updating system power...
2021-12-18 15:06:18 - DEBUG: Publishing to texecom2mqtt/status: online
2021-12-18 15:06:18 - DEBUG: Publishing to texecom2mqtt/power: {"battery_charging_current":0,"battery_voltage":13.63,"panel_current":261,"panel_voltage":13.7}
2021-12-18 15:07:07 - DEBUG: Updating system power...
2021-12-18 15:07:08 - DEBUG: Publishing to texecom2mqtt/status: online
2021-12-18 15:07:08 - DEBUG: Publishing to texecom2mqtt/power: {"battery_charging_current":0,"battery_voltage":13.63,"panel_current":261,"panel_voltage":13.7}
2021-12-18 15:07:57 - DEBUG: Updating system power...
2021-12-18 15:07:58 - DEBUG: Publishing to texecom2mqtt/status: online
2021-12-18 15:07:58 - DEBUG: Publishing to texecom2mqtt/power: {"battery_charging_current":0,"battery_voltage":13.63,"panel_current":261,"panel_voltage":13.7}

All sensors still unavailable

Can you update to the latest version v1.1.9 released yesterday (if you haven't already) and send me the full log from restarting the container until there's a problem? I fixed a couple of bugs and added some additional logging so I'm hoping it might shed some more light on the problem 🤞

Fantastic will try tomorrow, cheers

I've emailed you 👍

I've also uninstalled and reinstalled both mosquitto and texecom2mqtt and get the same "unavailable"ness.
Am I being daft in some other way?  (Quite likely)

I've maybe got somewhere with this, or at least got some more information.
So I updated the firmware on my panel, but noticed it was still showing the old version in HA.
Under Integrations the Mosquitto card was showing the texecom device/entities:

Viewing these showed the old version, hoping it would force some refresh I deleted these using the delete button previously shown on that card.
I then updated to the latest texecom2mqtt and restarted everything.
MQTT Explorer is now showing this:

which agrees with the texecom2mqtt logs.
So why isn't mqtt discovery working? I've set
mqtt:
  discovery: true

in the main HA config to try and force it on but I still don't have any alarm entities or devices.
Is this a clue or have I gone down some rabbit hole?
Which rocks should I lift up next?
Thanks

Sorry, wasnt super clear with my inference there, what I meant to suggest was:
I think my "offline" entities might have been legacy ones from some previous time where they were really offline, and that some combination of uninstalling/reinstalling MQTT/T2MQTT disconnected/lost/didnt-reinstate the entities, so the published MQTT values were probably always right throughout the duration of this thread, but HA wasn't picking up the new/current entities.
Does that make sense?
I'm trying to see why that might be, but im new to this area, I'll keep digging.
Hopefully @dchesterton you know where the "discovery" messages are supposed to be/need to be, maybe thats where this bug really lies

So, it seems my HA instance hasnt been reliably talking to Mosquitto. Despite not touching this aspect, it obviously once worked as the entities were once discovered, and it periodically worked, as the alarm was randomly "online" every now and then.
Sigh
I shall donate time-wasting beers as well as great-project beers.
I'll not close this just yet as the issue may remain, but i suspect for me that this was the problem....

With each release this has become more stable.
Hope this last bug that you squashed (Fix issue where keepalive fails causing the app to hang) fixes the minor issue of it hanging every couple of days requiring the addon needing to restarted

I'm going to close this issue as I think it was a combination of your MQTT/HA issues and the keepalive bug which has now been fixed. Please feel free to re-open if you have any further issues.

I'm going to close this issue as I think it was a combination of your MQTT/HA issues and the keepalive bug which has now been fixed. Please feel free to re-open if you have any further issues.

Perfectly reasonably. Its been stable so far, I'll report back if anything happens

Just to feed back on this, been continuously up for days now, looks fixed 👍

Again, been up for weeks now, no issues

trullock, sorry for bringing this thread back to life. I've been at this for days now and just cant understand why I can only see the first six of my binary sensors! I get a clean start up
2024-04-10 19:42:01 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
2024-04-10 19:42:02 - INFO: Connected to alarm, sleeping for 2 seconds...
2024-04-10 19:42:04 - DEBUG: Executing serial number command
2024-04-10 19:42:04 - INFO: Connection ready
2024-04-10 19:42:04 - INFO: Logging in to panel
2024-04-10 19:42:04 - INFO: Successfully logged in to panel
2024-04-10 19:42:04 - INFO: Connected to MQTT broker: xx.xx.xx.xx+:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 2)
2024-04-10 19:42:04 - DEBUG: Publishing to texecom2mqtt/status: online
2024-04-10 19:42:04 - INFO: Serial number: xxxxxxx
2024-04-10 19:42:04 - INFO: Panel: Premier Elite 64 (V5.06.00LS1)
2024-04-10 19:42:05 - INFO: Fetched Area A: Entire House
2024-04-10 19:42:05 - INFO: Fetched Area B: Area B
2024-04-10 19:42:05 - INFO: Fetched Area C: Area C
2024-04-10 19:42:05 - INFO: Fetched Area D: Area D
2024-04-10 19:42:08 - INFO: Fetched Zone 10: Garage Door (Type: Guard; Areas: A)
2024-04-10 19:42:08 - INFO: Fetched Zone 11: Front Room Patio Door (Type: Guard; Areas: A)
2024-04-10 19:42:08 - INFO: Fetched Zone 12: Family Room Patio Door (Type: Guard; Areas: A)
2024-04-10 19:42:09 - INFO: Fetched Zone 13: Back Door (Type: Guard; Areas: A)
2024-04-10 19:42:09 - INFO: Fetched Zone 14: Family Room PIR (Type: Guard; Areas: A)
2024-04-10 19:42:09 - INFO: Fetched Zone 15: Garage PIR (Type: Guard; Areas: A)
2024-04-10 19:42:10 - INFO: Fetched Zone 16: Landing PIR (Type: Guard; Areas: A)
2024-04-10 19:42:10 - INFO: Fetched Zone 17: Front Door (Type: Entry/Exit 1; Areas: A)
2024-04-10 19:42:10 - INFO: Fetched Zone 18: Hall PIR (Type: Entry/Exit 1; Areas: A)
2024-04-10 19:42:11 - INFO: Fetched Zone 19: Master Bedroom Patio Door (Type: Guard; Areas: A)
2024-04-10 19:42:11 - INFO: Fetched Zone 20: Front Sounder (Type: Custom; Areas: A)
2024-04-10 19:42:11 - INFO: Fetched Zone 21: Garage Sounder (Type: Custom; Areas: A)
I can then see the MQTT messages in the log - 2024-04-10 19:42:26 - DEBUG: Publishing to texecom2mqtt/zone/landing_pir: {"name":"Landing PIR","number":16,"areas":["A"],"status":0,"type":"Guard"}
But still I only see 6 of the 11 sensors created as part of the discovery in HA.
Zone 10: Garage Door (Type: Guard; Areas: A)
Zone 11: Front Room Patio Door (Type: Guard; Areas: A)
Zone 12: Family Room Patio Door (Type: Guard; Areas: A)
Zone 13: Back Door (Type: Guard; Areas: A)
Zone 14: Family Room PIR (Type: Guard; Areas: A)
Zone 15: Garage PIR (Type: Guard; Areas: A)
Any Ideas?

I don't know sorry, I was simply a victim of an earlier bug.
This project seems abandoned.

ah thanks, appreciate the response.. Ill get to the bottom of this :0)


Re-export categories from sparseconverter

Avoid interacting with sparseconverter directly in UDFs. See https://github.com/Ptychography-4-0/ptychography/pull/68#discussion_r1236883612 for rationale!
Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[N/A] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed
[x] No import of GPL code from MIT code

/azp run libertem.libertem-data

/azp run libertem.libertem-data


pkgsite: showing incorrect LATEST version

What did you do?

Tagged and pushed v0.0.2 and v0.0.3
Navigated to<EMAIL_ADDRESS>
What did you expect to see?
I expected to see version v0.0.3 as the LATEST
What did you see instead?
"GO TO LATEST" link takes me to v0.0.2

CC @julieqiu @jba @jamalc via https://dev.golang.org/owners

I'll hold off pushing any new tags to this repo until this issue can be investigated.

Seems to be fixed now. Probably just a transient state due to processing order.

Probably just a transient state due to processing order.

Commonly known as a design flaw.


[65318] JSON Assertion: Use correct number format

Description
See https://bz.apache.org/bugzilla/show_bug.cgi?id=65318
Motivation and Context
This PR fixes the issues with JSON Assertions mentioned here: https://bz.apache.org/bugzilla/show_bug.cgi?id=65318
How Has This Been Tested?
Tested with the example testplan provided in the issue.
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.

This was created to address #5539, but the attached test case does not fail any more (tested on current branch). Is this PR still needed?

This was created to address #5539, but the attached test case does not fail any more (tested on current branch). Is this PR still needed?

For me the attached test case still fails - please see https://github.com/apache/jmeter/issues/5539#issuecomment-1520035988

PR has been merged.
Thanks for your PR and your insistence :)
Could you test the current trunk or next nightly?

Thanks for merging the PR @FSchumacher.
I've tested it with the current nightly and it works like a charm :)


decomposedfs: in spacetypes/{spacetype}/{spaceid} spaceid is unsharded

tree ~/.ocis/storage/users/spacetypes/personal/
/home/vscode/.ocis/storage/users/spacetypes/personal/
├── 4c510ada-c86b-4815-8820-42cdf82c3d51 -> ../../spaces/4c/510ada-c86b-4815-8820-42cdf82c3d51/nodes/4c/51/0a/da/-c86b-4815-8820-42cdf82c3d51
├── f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c -> ../../spaces/f7/fbf8c8-139b-4376-b307-cf0a8c2d0d9c/nodes/f7/fb/f8/c8/-139b-4376-b307-cf0a8c2d0d9c
└── some-admin-user-id-0000-000000000000 -> ../../spaces/so/me-admin-user-id-0000-000000000000/nodes/so/me/-a/dm/in-user-id-0000-000000000000

In /home/vscode/.ocis/storage/users/spacetypes/personal/ the spaceids should be segmented, as under spaces/ this would make the directories more manageable when listing them.

@butonic Is this a GA release blocker for you? I would induce a later storage migration.

No longer relevant, since we moved to messagepack.


Added option to render as markdown instead of with ansi escape codes.

This is useful for when you want to open it up in a pager which doesn't
support ansi escape codes by default. In my use case it allows me to
open it inside vim without having to use an addon to convert ansi escape
codes to colours.

Thanks!
Hmm, that would make tealdeer a glorified cat, right? :smile:

Hi,
Yes essentially in that case it's only for finding the right file and displaying it. But I think that has it's value too, in my use case of tldr I use it normally in the terminal but if I want to copy something from the output that becomes quite awkward, or if I already have vim up then it would be nice to be able to just render it in a vim buffer.
It's a pretty minor change, but at least for me it allows me to not have to use more than one tool to view the tldr-pages. I'm sure other people could find it useful as well. :)


Cannot use @OneToMany relations to entities having jsonb columns when using TABLE_PER_CLASS inheritance

I have a project where I have two related entities, let's say A and B, using the TABLE_PER_CLASS inheritance strategy. In this case B extends A. Another entity C has a @OneToMany relation to the base class A. When trying to retrieve the items for the collection of A in C Hibernate performs a query with a UNION ALL clause between A and B.
In the above situation when should B contain a jsonb type column, the union query fails with the following error:
org.postgresql.util.PSQLException: ERROR: UNION could not convert type jsonb to uuid.
In the union Hibernate selects null constants for the columns that are not present in either table, each cast to its type. But for the jsonb column it selects null:uuid.
Probably something needs to be done with the PostgresDialect so that Hibernate recognizes the correct type and does the cast correctly?
I created a test class to reliably reproduce the issue, please see the attachment.
PostgreSQLJsonInheritanceTest.java.zip

As I explained in my High-Performance Java Persistence book, the TABLE_PER_CLASS inheritance strategy is a terrible idea. You should never use it.
Therefore, I don't think it's worth fixing a use case you should never use.
What you describe is probably a Hibernate issue than a issue in this framework. Therefore, you should investigate it and open a Jira issue for Hibernate if that's the case.

This article can help you as well.

Thanks! I'll definitely try overriding the Dialect, hopefully it helps with my case. I'd rather avoid changing the inheritance at this time.
I understand your position regarding this particular issue, but I still have concerns that there might be some mapping missing in your framework.
The root cause is that Hibernate somehow "thinks" that the native type for jsonb columns is "uuid", which sort of makes sense since that is the only thing registered in the dialect to handle Types.Other. In my example the column field is a String, that could be why it made that match.
Please correct me if I'm wrong, but I don't see anywhere in the framework were we map the Json hibernate types to native "jsonb" data type. The closest thing I see is the columnDefinition , but that should only be used to create the table. I don't know if there is some other process in Hibernate that requires using the data type directly; from the article you linked it looks like native queries might be another one.
Perhaps the custom dialect in the article should be part of this framework? At least one advantage could be to avoid having to use columnDefinition, which makes the code less portable in my view.

The problem is not in this framework. It's due to how Hibernate maps Types.OTHER for PostgreSQL. I had one proposal to the Hibernate IRM project, but if was postponed for 6.0. So, either it will be fixed in Hibernate ORM or you will have to take care if it in your application.

Yes, I get your point. Customizing the dialect does feel like a workaround to me, so I can understand why you don't want such a thing in your framework.
I've also been having trouble with Hibernate's mappings for Oracle. Then too I had to create a custom dialect. There is definitely some room for improvement in how Hibernate does its mappings.
I do use FlywayDB actually :) I was following your article [https://vladmihalcea.com/how-to-map-json-objects-using-generic-hibernate-types/] and there you do mention specifically to use different values for the columnDefinition, which led me to believe that was somehow important to use. Good to know that's not the case.
Anyway, thanks again very much for your help! I'm actually curious about your book, you might have a new customer soon ;)

You're welcome and enjoy reading it. You're going to love it.


CSS correct, but not allowing me to continue

Challenge Use CSS Selectors to Style Elements has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
It has instructed me to create a style element using CSS that defines the h2 element as being blue. I have done this, but it says otherwise, which prevents me from fully completing my course.
My code:
<style>
  h2 {color: blue;}
</style>

@Laurensly, did you delete h2 element?  there suppose to have more code. I dont see other code in there.

wow, I'm oblivious. I accidentally deleted my greater than sign. Fixed it though. Thanks! @dwd2010

Next time, use the Help chat room for getting challenge related help.
Happy Coding!

Yes, I did. Since I thought it was a bug issue, I came here. The other chatters also thought the same thing. But, thank you for your suggestion. @dwd2010

@Laurensly, yeah. It is fine. all good.


Remove GenAI pipeline yaml files from OneClick

Such as chaqna-xeon-backend-server.yaml.
These will be auto generated by the microservice-connector tool, which will be versioned based on the pipeline specification language version.

Such as chaqna-xeon-backend-server.yaml. These will be auto generated by the microservice-connector tool, which will be versioned based on the pipeline specification language version.

Hi @mkbhanda , as we discussed, we plan to have a pre-built K8s config file for May milestone, since it would give the simple UX if users just want to deploy the chatqna with native K8s.  While we agreed to provide an advanced option to enable microservice-connector tool, let's together plan in Jun's milestone.

@mkbhanda can this issue be closed?


MongoAdapter now implement BatchAdapter

Hello,
MongoAdapter was implementing org.casbin.jcasbin.persist.Adapter interface.
For our usecase, we needed to implement org.casbin.jcasbin.persist.BatchAdapter interface in order to batch insert/delete commands.
I also upgraded jcasbin dependency to latest version available and fed the model's assertion policyIndex (available since 1.25.0).
And I used flapdoodle embed MongoDB instance in order to run the tests.

@zzl221000 plz review


[Web] Stop images

"Stop batch" will now instantly cancel images generation for txt2img, img2img, inpaint and outpaint.
Sorry about the long PR, to avoid adding more, I have reported the implementation for the LoRA training and the upscaler tabs.
Principle:
A pipeline status variable had been added with only two possible state for now (IDLE, CANCEL)
When the UI send a cancel signal, the pipeline stop iterating and return immediately.
The canceled image is skipped (not saved on disk and not displayed in the ui) as it is incomplete.
This is just an entry step, more work will be needed to finish a fully working "stop" feature.
If this is accepted, here is a list of possible updates I would like to add later:
* Implement Upscaler and LoRa training tabs.
* Manage more pipeline states: EXPORT_DIFFUSER, COMPILE_MODEL, LOAD_MODEL (set on first model load or when switching models), GENERATE_IMAGES.
* Add a status message textfield in the UI header, and refresh it with a user friendly message depending on the current pipeline status.
* Report the currently processed batch in the message textfield (Generating image x from y)
* As instant cancel is not possible or recommended on some state (EXPORT_DIFFUSER, COMPILE_MODEL, LOAD_MODEL): Report a "Canceling please wait" in the status message textfield.
* Move back the "Stop batch" button and rename it to "Stop" when all it ok.

Identified bug:
Spamming at a crazy pace Generate and Stop buttons can report an error, or even save the last partially generated image on disk. This is not fatal and the app will continue to work, but further debugging will be needed to fix it.

Thank you. I like this since it builds on GC and doesn't need to plumb into the low level interfaces. Would be good to keep testing to make sure the clean up happened correctly

Same, that's really cool to avoid touching the low level , it's all thanks to the global_obj and GC introduced by @jinchen62, mega kudos to him 👍
I agree too with testing more before landing, clearly more than one commit will be needed to finish this.
I will continue next week to tackle the annoying bug.
See you.

Sorry, it should be ok for this one.