⚠ Bofrost.be has degraded performance

In b6c61c7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 909 ms

Resolved: Bofrost.be performance has improved in eaa0583 after 7 minutes.


Add On Demand Broker to Getting Started page.

Co-authored-by: Jack Newberry<EMAIL_ADDRESS>@mattmcneeney @jacknewberry

LGTM

LGTM


False positive on ec2_securitygroup_allow_ingress_from_internet_to_any_port

Hi,
I can see this was fixed in 3.6.0 last year but I'm seeing the same issue in Prowler version 4.3.5.
I have a security group with ports 80 and 443 open for ingress, and all egress traffic is allowed:
{
    "SecurityGroups": [
        {
            "Description": "Foo",
            "GroupName": "<redacted>",
            "IpPermissions": [
                {
                    "FromPort": 80,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 80,
                    "UserIdGroupPairs": []
                },
                {
                    "FromPort": 443,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 443,
                    "UserIdGroupPairs": []
                }
            ],
            "OwnerId": "<redacted>",
            "GroupId": "sg-<redacted>",
            "IpPermissionsEgress": [
                {
                    "IpProtocol": "-1",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "UserIdGroupPairs": []
                }
            ],
            "Tags": [
                {
                    "Key": "Name",
                    "Value": "<redacted>"
                }
            ],
            "VpcId": "vpc-<redacted>"
        }
    ]
}

which is the same as the one above.
which results in a Prowler finding off:
Details

ResourceUid:
arn:aws:ec2:eu-west-2:<redacted>:security-group/sg-<redacted>

FindingUid:
prowler-aws-ec2_securitygroup_allow_ingress_from_internet_to_any_port-<redacted>-eu-west-2-sg-<redacted>

CheckId:
ec2_securitygroup_allow_ingress_from_internet_to_any_port

Type:
AwsEc2SecurityGroup

Details:
<redacted>

StatusExtended:
Security group <redacted>- (sg-<redacted>) has at least one port open to the Internet and neither its network interface type (interface) nor its network interface instance owner (<redacted>) are part of the allowed network interfaces.

Risk:
If Security groups are not properly configured the attack surface is increased.

Notes:

Provider:
aws

Recomendation:
Use a Zero Trust approach. Narrow ingress traffic as much as possible. Consider north-south as well as east-west traffic.

RecomendationUrl:
https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html

Scan Day:
2024-09-20

Originally posted by @dazzag24 in https://github.com/prowler-cloud/prowler/issues/2442#issuecomment-2367935825

Hi @dazzag24, I was able to reproduce your finding.
What are you expecting to get?
If the security group is not attached to any network interface, Prowler gives a PASS.

Hi,
I have tested with Prowler 4.3.6.
prowler aws -f eu-west-2 --mutelist-file mute_list.yaml --checks ec2_securitygroup_allow_ingress_from_internet_to_any_port --verbose
returns:
FAIL eu-west-2: Security group <REDACTED_DESCRIPTION (REDACTED_SG_ID) has at least one port open to the Internet and neither its network interface type (interface) nor its network interface instance owner (<REDACTED_AWS_ACCOUNT_ID>) are part of the allowed network interfaces.

my confusion is that in #2442 there is an identical SG config that was triggering the same issue and it was flagged as a bug and fixed.
Furthermore I have 2 identical SGs, one that passes while the other fails:
Failing SG:
{
    "SecurityGroups": [
        {
            "Description": "Foo,
            "GroupName": "<redacted>",
            "IpPermissions": [
                {
                    "FromPort": 80,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 80,
                    "UserIdGroupPairs": []
                },
                {
                    "FromPort": 443,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 443,
                    "UserIdGroupPairs": []
                }
            ],
            "OwnerId": "<redacted>",
            "GroupId": "<redacted>",
            "IpPermissionsEgress": [
                {
                    "IpProtocol": "-1",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "UserIdGroupPairs": []
                }
            ],
            "VpcId": "<redacted>"
        }
    ]
}

this is attached to a Network Interface that has the instance owner set to the AWS Account ID.
Passing SG:
{
    "SecurityGroups": [
        {
            "Description": "Goo",
            "GroupName": "<redacted>",
            "IpPermissions": [
                {
                    "FromPort": 80,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0",
                            "Description": ""
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 80,
                    "UserIdGroupPairs": []
                },
                {
                    "FromPort": 443,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0",
                            "Description": ""
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 443,
                    "UserIdGroupPairs": []
                }
            ],
            "OwnerId": "<redacted>",
            "GroupId": "<redacted>",
            "IpPermissionsEgress": [
                {
                    "IpProtocol": "-1",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "UserIdGroupPairs": []
                }
            ],
            "VpcId": "<redacted>"
        }
    ]
}

this is attached to a Network Interface that has the instance owner set to "amazon-elb".
Why would one be considered OK while the other triggers a FAIL?
Many thanks

Hi @dazzag24, in this check, Prowler alerts a FAIL if the security group has any open ports and it is attached to a network interface where either the instance owner or the type are not in the configurable variables:

ec2_allowed_interface_types
ec2_allowed_instance_owners

Those variables can be found here.
By default, the Network Interface types that are allowed are: api_gateway_managed and vpc_endpoint, and amazon-elb as the instance owner. But you can change them in the config file.
What do you think about this logic?
However, I am going to document more this check so the logic is more understandable.

Thanks for the explanation. I have added the org ID to the config.  Adding more docs to make this clearer would be much appreciated.


Corrects strings in json error responses

Addresses #1037

Looks like this is breaking on some platforms.  Investigating...

It looks better, squash it.

Merged via https://github.com/ruby-grape/grape/commit/844b6ace4f2298db8892bd79954d1ac64d9d59da.


feat(error): report the error's source chain through psql

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Follow-up of #13248. Visit the error's source chain and get it printed through psql interface. This is achieved by thiserror_ext::Report.
Note that we now interpolate the inner error message into the outer one, so the most of time, printing the out-most error should include all information. However, this is not a good practice that the community will follow (examples: https://github.com/awslabs/aws-sdk-rust/issues/657, https://github.com/EmbarkStudios/rust-ecosystem/issues/20). As a result, we lose the opportunity to visit the source of errors from 3rd-party libraries (like tonic::transport::Error), which leads to issues like #13163.
As discussed in https://github.com/risingwavelabs/risingwave/issues/11443#issuecomment-1786441591, snafu provides a clever way to handle these two conventions together by trimming out the duplicated suffixes in the error message. thiserror-ext adapts it to better suit our needs.
Preview
Unsure about which format is preferred, I introduce a env variable RW_PRETTY_ERROR to switch between these two formats:

Compact:

The experience will be majorly the same, except that we're now correctly visiting the source chain to avoid losing any context.

Pretty:

The sources will be printed line by line. The * symbol indicates that the suffix of the message (i.e., the message of the inner error) has been cleaned up.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Similar concern, I think the * symbol is somehow confusing to users.

I copied * from snafu. Then let's remove it. 😄


Kong won't start without a database

I'm trying to get docker compose working but it always brings up the kong container before the postres one... Apparently it's bad design for microservices to die if their dependencies are not up, they should keep trying to connect. Can you make Kong behave like this please?
In any event, this is all making it impossible for me to make this docker-compose work.  Can you please fix/provide workaround/comment.
thanks

A common way of doing this is to use dockerize. The following Dockerfile will extend the kong image and makes Kong wait for Postgres:
FROM mashape/kong:latest

ENV DOCKERIZE_VERSION v0.2.0

RUN yum install -y epel-release && yum install -y wget \
    && yum clean all

RUN wget -nv https://github.com/jwilder/dockerize/releases/download/$DOCKERIZE_VERSION/dockerize-linux-amd64-$DOCKERIZE_VERSION.tar.gz \
    && tar -C /usr/local/bin -xzvf dockerize-linux-amd64-$DOCKERIZE_VERSION.tar.gz

COPY config.docker/kong.yml /etc/kong/kong.yml

#CMD [ "kong", "start" ]
CMD dockerize -wait tcp://kong-database:5432 kong start

For 0.9 we have released an official Docker Compose template: https://github.com/Mashape/docker-kong/tree/master/compose


Introduce Source Repo Url for releases

For more context, please see: https://github.com/cloudfoundry/bosh/issues/1525

@petergtz may be making this a bit more generic would be better? something like metadata hash that would be sibling to name and version. inside of it could have source_url, i could see also may be adding an author and other misc data?
name: foo
version: 123
metadata:
  source_url: https://github.com/cloudfoundry/foo

@dpb587-pivotal you've thought i think a little bit about this before. wdyt?

@cppforlife Makes sense. In the code, would you treat metadata as a typed struct, something along the lines of:
type ReleaseMetadata struct {
    SourceUrl string
    Author string
}

Or would you treat it as a map[string]string?
I can see both possibilities, but I'd like us to consider it in the broader context of https://github.com/cloudfoundry/bosh/issues/1525, i.e. in the end I'd like us to be able to do:
$ bosh -d my-deployment diff-deployment-revisions --include-git-diff 3 4

# manifest-diff would go here...

diff --git a/jobs/bits-service/spec b/jobs/bits-service/spec
index 4aab31f..0b4cba3 100644
--- a/jobs/bits-service/spec
+++ b/jobs/bits-service/spec
@@ -26,7 +26,7 @@ packages:

 properties:
   request_timeout_in_seconds:
-    description: "Timeout for requests in seconds."
+    description: "The changed description"
     default: 900

   bits-service.public_endpoint:

And to be able to do that, the bosh CLI would have to extract source_url and commit_hash and do a git diff (obviously it will refuse to do that when the release wasn't created with these values in the first place). So I'm wondering if we should make these values a first class concept, or if we can still live with them being an untyped hash.
What do you think?

I like the metadata idea (and having repository URI accessible somewhere).
I don't think the repository URL should be committed based on the local repo creating the final release though. Releases might often be committed in local forks before being pushed externally, and that would result in releases having a possibly incorrect/file:// repo.
In prior experiments, I've used config/final.yml as a place to commit additional metadata. For example, if there was a metadata field in there, create-release could potentially copy that into the finalized manifest. This would allow for arbitrary metadata to be committed and versioned like other release configuration items (I've also used it for URLs, license summary, meta-resources for other tooling, and signing information).
Naming it metadata in config/final.yml might be a bit too generic, but I think metadata would fit inside a final release YAML. Perhaps there's a different name which could be shared in both places. I'd imagine it more of a generic map[string]interface{}.
From the CLI, perhaps metadata information could be exposed as part of the inspect-release command. Maybe using --metadata. It'd require a new field in the database for recording the new metadata.
If core director starts depending on the repository value, it might be better to make it a more official property (rather than in metadata; I still think it should be derived from a config/final.yml rather than from local create-release env).
Regardless, I think a generic metadata feature would be useful and it makes it easier to prototype these sorts of experimental ideas to see if they should become more official "data".
Not sure what @cppforlife thinks.

@dpb587-pivotal I understand your concern with deriving the source URL automatically from the git remote. But I think we are looking at it from two different perspectives. From my perspective, the main use case of this is that Concourse (or any other automation pipeline) clones the git repo, creates a release and uploads it somewhere.  Of course (and my PR does not include that), the create-release command could have a new option to override that source URL in case the git remote for whatever reason is non-sensical.
The good thing about this approach is that you only need a new version of the BOSH CLI, and to actually store it a new version of the bosh director. Both happens sooner or later in any environment, and you'd consume this new feature automatically, whereas your suggestion requires you to do this to every existing BOSH release individually. So I think adoption rate would suffer a lot. In fact, I doubt it would ever be used in certain environments (despite the fact that it would benefit those environments).
Also, I think when having a local fork that points to file:/// at the time of release creation, it really just manifests your release creation process in the manifest which I believe is a good thing. Maybe it's a motivator to automate that step. If not, you can still override it using an option during create-release.
I was also wondering: if this value lives in final.ym, isn't there a real danger that this value gets stale and eventually the commit hash might not even be existent in the repo pointed to by the source URL? Or the URL simply doesn't exist anymore. I'm having moves in mind, like from github.com/cloudfoundry-incubator to github.com/cloudfoundry.
In your suggestion, would dev_releases also grab the source URL from final.yml? (I think dev_release should also contain a source URL in their manifest, because in dev environment it's just as useful to see which diff broke the acceptance tests.)
As you can see, my main concern is about actually having a working source URL in every BOSH release, so we could introduce release diffs as I described in my earlier comment. I want us to be able to push several new releases into Production a day, while still maintaining full control of what changed when.
So in summary, I think git remote origin would provide a sane default and could be easily overridden when there's need. What do you think?
/cc @cppforlife

@petergtz hey, ive chatted with @dpb587 and @tjvman more. let's expand this pr to do following things:

allow repository, license, description as top level keys in final.yml and release.MF (similar to https://github.com/lynnux/xpsupport/blob/master/Cargo.toml#L8)
fill in repository automatically if not present

separately director should add 3 columns to release_versions (next to commit_hash).
wdyt?

@cppforlife Sounds good! Will start working on it.

@cppforlife I realized there is already logic that copies any LICENSE or NOTICE file that exists in the release dir into release itself. Does it still make sense to have an extra field in the manifest for license? How will we deal with conflicting data? Is that simply the release-authors responsibility?

Is that simply the release-authors responsibility?

yeah, let's go with that for now.

@cppforlife Updated this PR with what we've discussed. Is this what you had in mind?

@cppforlife sure, will make the changes.

@cppforlife did you have in mind using this struct everywhere then where these 3 fields appear, or just specifically in functions,  where the fact that parameters are not named make it kind of unreadable?

did you have in mind using this struct everywhere then where these 3 fields appear

i was thinking using it in places where these 3 fields appear. dont think should use that anywhere else since that would imply that extraneous info could be passed to functions.

merge story #152973983

Closing this issue due to inactivity.
This doesn't seem to be a priority. Feel free to open a new issue if you would like to discuss this feature further.
Best,
@jfmyers9


Mail Archiving

In business context, there is often the requirement to archive all mails and prevent deletion and manipulation. (At least in Germany it's required by law from the beginning of this year, so that mails can be treated the same as paper documents)
I'm not sure if there's any existing Open Source solution to this, but I'd love to see one integrated in hardware/mailserver. If you are open to this suggestion, I would do a bit research about existing solutions and make a proposal.

Mailman 3
Mlmmj
Ezmlm
Majordomo
…

Thanks for your research!
I think the mailing list archives serve another purpose, which could be discussed as a separate thread. Mail   Piler looks good to me, based on a first glance at the feature list. I guess we should try it first before integrating it.
From the architectural point of view:  Do you think it's generally a good idea to integrate it in this project? Another way could be to create a new docker project for mailpiler and write an integration manual.

Such decisions are better integrated in individual containers that would be possible could limit the use of resources.
/cc @hardware

Such decisions are better integrated in individual containers that would be possible could limit the use of resources.

I agree, Mail Piler must be in a separate container like rainloop and postfixadmin. It is an optional dependency, not everyone will use it.

@msander Did you have time to test mailpiler?
There is a (rudimentary?) docker container for mailpiler: https://hub.docker.com/r/heri16/piler-mail/
Haven't tested it. Still integration with the mail server would require changes to the postfix config:

/etc/postfix/main.cf:
   smtpd_recipient_restrictions = reject_non_fqdn_recipient, ..., \
                     check_recipient_access pcre:$config_directory/x-add-envelope-to, ...
   always_bcc =<EMAIL_ADDRESS>
/etc/postfix/x-add-envelope-to:
   /(.*)/   prepend X-Envelope-To: $1
(http://www.mailpiler.org/wiki/current:installation)
This requires at least using the custom.conf method as the x-add-envelope-to file could be stored next to the custom.conf so we don't have to add it to the rootfs of the container.

looks nice ill look at this also

Any news on this?
Anyone using some good software? Any tips?
I'm also interested on it.

I am using a bash script that archive each domains then upload to my S3. I don't think I need additional application for this, do I?

@sknight80 I don't think this work as @msander has described.

In business context, there is often the requirement to archive all mails and prevent deletion and manipulation.

Is anybody using Mail Piler successfully or has anything else in use?

@neuffer not yet, but I am planning to try this out in one of my mail servers.


Cannot Connect My Oracle Database from My Main Machine.

Hello,
Problem,
I'm using Oracle Linux 7.4 operation system on VirtualBox. And my Main Machine's OS is Windows. I can connect my Oracle Database from my Virtual machine.
I can ping to my Virtual Machine from my Main Machine. But i cannot connect my database from my Main Machine.
Thats my error;

Can you make telnet <IP_ADDRESS> 1521?

Can you make telnet <IP_ADDRESS> 1521?

How can i do that ?

Test your network connection

i can access my virtual machine with telnet. But still cannot access my Oracle-DB with DBEAVER.

cannot reproduce.
if it is still actual - feel free to reopen

This problem is happening to me now. I have used bridged network adapter in Virtualbox. The problem was exactly as @aiak0s described, but I've Oracle XE 21c on Windows 10 in VM. I've run lsnrctl then start too. @uslss please tell me how can you connect Dbeaver to Oracle XE in Virtualbox?


.NET Standard support for new VS2017 project format

Created independent solution and project files demonstrating .NET Standard support and targeting multiple frameworks in the new project format. Have not attempted to support additional targets such as .NET 35 and Portable.

@cdrnet Is there anything else you would like incorporated into this pull request? Ryan and I are on the same team and we can work together to make some progress while we're motivated.

Just wanted to leave a word that I can load this successfully on ArchLinux with the JetBrains Rider IDE. Thanks!
I also tried to build it using:
dotnet restore Math.Numerics.2017.sln
dotnet build Math.Numerics.2017.sln -f netstandard1.6

The projects build did not work, but it is highly likely to be a setup issue. I can help debugging this if someone is interested, but I do not think that this PR should be affected in any way due to my "build on Linux" issue.

Hi
Is there an ETA on when this will get merged and put up into nuget?
I'd really like to use this library in a netstandard project i'm building
Thanks

@lennoncork @ryanblackwell Just out of curiosity, is there any reason you are aiming as high as 1.6? It has always been my assumption that one should target as low as possible with .NETStandard and given that until the 2.0 tooling is RTM 1.6 is only compatible with .NET4.7+ (and at which point it might make sense to jump straight to .NETStandard2.0 as has been suggested by Christoph) it would seem to make sense to reduce the level as much as possible. 1.0/1.1 might be unreasonable but 1.4 could be a good compromise given that it's the current level which will be compatible with the same .NET Framework as 2.0. I'm obviously not taking into account the potentially numerous frameworks pre 4.5 which aren't compatible with any .NETStandard but hopefully that's by the by.

Since portable libraries (that exists today) is more or less the same as .NETStandard 1.0 that should be the easiest to target. My guess is that it is the native providers that will create problems but just like they are missing from the portable libraries (if I understand things correctly) those could be left for later releases. Multi-targeting different versions of .NETStandard is quite easy once the first is set up.

Just out of interest, I have rebased @ryanblackwell's changes on the latest master and added cryptographic PRNG support for netstandard1.6. It is here: https://github.com/aignas/mathnet-numerics/tree/feature/vs2017. Please feel free to cherry pick the changes. :)

I have also completed the unit-test porting to necoreapp1.1/2.0.
I was using NodaTime as a model on how to have the tests suitable for running with multiple frameworks.
Link: https://github.com/nodatime/nodatime/tree/master/src/NodaTime.Test
In order to run the tests (works under Linux):
dotnet run -f netcoreapp1.1 -p UnitTests-2017.csproj

The output from the initial run:
https://gist.github.com/aignas/cae21fa4b0b5258020c7960d489e5295
Summary:

4 Failures
9 Errors

And I got all of the tests passing on my local branch. Some notes about what I have discovered about netstandard.
In case you would like to run a single test instead of all the unit tests, use the following shell command(nunit docs):
$ dotnet run -f netcoreapp1.1 -p Test.csproj --where "method == METHODNAME"

I had the following classes of failing tests:

Matrix<Complex64>: Serialization tests.
RandomNumberSource: DataContract tests.
Complex32: TextHandling tests.

Matrix Complex64 failure
It seems that this failure is because the serialization support for Complex in System.Runtime.Numerics got cleaned up a while ago.  It is reintroduced in netstandard2.1 and this PR is already merged.
One solution to this would be to back-port the changes in the compatibility layer and once 2.1 is released, add that as a targeted platform as well and for 2.1 upwards use the upstream version of Complex.cs.
I chose to define NOSYSNUMERICS flag for the netstandard target.  If this is not satisfactory, let me know.
Serialization of the RandomSources
It seems that the tests fail because the [DataContract] cannot be applied to System.Random class because they removed quite a lot of serialization stuff at some point and they added it later and then removed it again.  IMHO, the best approach would be to deprecate serialization for these types altogether because in the last PR the dotnet people say that these types are not meant to be serializable anyway and this is the position of dotnet developers.
The locale test failures
These were failing because of missing string comparison APIs compared to .NET framework.  I am not too familiar with that side of things, so I disabled the running of the tests.

@sebandraos, @eriove and @aignas this was our first real attempt to netstandard something as it was one of the baseline dependencies. We haven't done any work since and @ryanblackwell has returned to his studies so we weren't planning on any additional work just yet. However we're very keen to see this go in, so let me know what you need and I'll see if I can find someone on the team to make it happen.

@lennoncork, I think that the branch in which I developed is complete (or should be almost there) so if there is any desire from the maintainers to get this into master, I could open a different PR and we could review the changes I made and hopefully get it merged.

Any progress?
Absence of  .netstandard in Math.Net is the only stop factor for our Linux deployment.

Closing this, since this has been covered by another PR in the meantime and the first alpha releases of v4 with .Net Standard 1.3/2.0 support are out. Please let me know if you have any issues. Thanks a lot for your contributions!


how do you delete triggers from adf v2 environment

Not seeing anything in schedule [ or tumbling window trigger ] document covering how you delete a trigger you have created that is no longer in use or wanted.

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

ID: 89177180-caeb-e2e1-5614-60719f593672
Version Independent ID: a3352be5-2343-ae87-38d0-32312a62d2b1
Content: Create schedule triggers in Azure Data Factory
Content Source: articles/data-factory/how-to-create-schedule-trigger.md
Service: data-factory
GitHub Login: @sharonlo101
Microsoft Alias: shlo

Thanks for your feedback! We will investigate and update as appropriate.

@myusrn
I do not see a way to do that in the UI, however you can list and delete triggers with Powershell.  Here is the Powershell cmdlet reference for ADFv2:
https://docs.microsoft.com/en-us/powershell/module/azurerm.datafactoryv2/?view=azurermps-4.4.1
Here are the pages for the list and delete cmdlets:
https://docs.microsoft.com/en-us/powershell/module/azurerm.datafactoryv2/Get-AzureRmDataFactoryV2Trigger?view=azurermps-4.4.1
https://docs.microsoft.com/en-us/powershell/module/azurerm.datafactoryv2/Remove-AzureRmDataFactoryV2Trigger?view=azurermps-4.4.1
I will assign this issue to the content author to evaluate any changes to the document.

Thanks for the followup.  Using the powershell cmdlet references I was able to review Triggers and delete unwanted ones using following steps.  So at minimum the documentation associated with this issue may want to include a note outlining that this is where you have to go currently in order to delete unwanted trigger definitions.
Login-AzureRmAccount  // not sure how you specify which of your subscriptions to set focus on
Get-AzureRmDataFactoryV2Trigger -ResourceGroupName <my rg name> -DataFactoryName <my adfv2 name>
Remove-AzureRmDataFactoryV2Trigger -Name <unwanted trigger to remove> -ResourceGroupName <my rg name> -DataFactoryName <my adfv2 name>

I looks like it's possible with the GUI. However, I did delete a trigger with the  UI that was previously connected to a pipeline.  But after the pipeline kept triggering at the time of the deleted trigger. With powershell it showed that teh trigger was not deleted and still active

Thank you for taking the time to share your product and documentation feedback with us. Your input is valued because it helps us create the right documentation for our customers. Due to the volume of issues in our queue, we are closing open issues older than 90 days. We hope to continue hearing from you. Thank you.

This still happens when you rename a trigger, that will not stop nor delete the trigger with the old name. Even it doesn't appear on the UI it keeps triggering with the old and new name


Improving Read-Me

Checklist

[x] I have followed the Contributor Guidelines.
[x] The code has been thoroughly tested in my local development environment with flake8 and pylint.
[x] The code is both Python 2 and Python 3 compatible.
[x] The code follows the PEP8 styling guidelines with 4 spaces indentation.
[x] This Pull Request relates to only one issue or only one feature
[x] I have referenced the coresspoinding issue number in my commit message
[x] I have added the relevant documentation.
[x] My branch is up-to-date with the Upstream master branch.

Changes proposed in this pull request
Your development environment

OS: x
OS Version: x
Python Version: x

But why?

Looks like a test PR from someone who has just recently joined GitHub and is still learning how to use it. Closing this PR


onclite ( Lineage FE ) [Trees Links fixed]

please dont use personal manifest, use rom manifest, and use local manifest for cloning personal things


Fixed a bug parsing URLs with both hash and search

Since # always comes before ? in a URL, the code starting "const searchIndex" should come before "const hashIndex".
Currently the URL "/#foo?bar" is parsed to { pathname: "/", hash: "#foo?bar", search: "" }, not the desired { pathname: "/", hash: "#foo", search: "?bar" }.
I am such a newbie that I don't really know how to test my patch, but I'm pretty confident that it should work.
Here is a codesandbox illustrating the problem: https://codesandbox.io/embed/failing-history-rnqzu
Add "#foo?bar" in the demo browser address bar and hit enter. Then look at the console output.
Thanks!

My mistake is explained in the issue, thank you. https://github.com/ReactTraining/history/issues/714

My error is explained here: https://github.com/ReactTraining/history/issues/714
Thanks.


examples/bcc/perf/perf.go needs refactoring

$ go version
go version go1.14.2 linux/amd64

The error:
$ go run examples/bcc/perf/perf.go
# github.com/iovisor/gobpf/bcc
bcc/module.go:98:40: too many arguments in call to _Cfunc_bpf_module_create_c_from_string
        have (*_Ctype_char, number, **_Ctype_char, _Ctype_int, _Ctype__Bool, nil)
        want (*_Ctype_char, _Ctype_uint, **_Ctype_char, _Ctype_int, _Ctype__Bool)
bcc/module.go:230:28: too many arguments in call to _C2func_bcc_func_load
        have (unsafe.Pointer, _Ctype_int, *_Ctype_char, *_Ctype_struct_bpf_insn, _Ctype_int, *_Ctype_char, _Ctype_uint, _Ctype_int, *_Ctype_char, _Ctype_uint, nil)
        want (unsafe.Pointer, _Ctype_int, *_Ctype_char, *_Ctype_struct_bpf_insn, _Ctype_int, *_Ctype_char, _Ctype_uint, _Ctype_int, *_Ctype_char, _Ctype_uint)

Looks like it is related to the change https://github.com/iovisor/gobpf/pull/210

It looks like bcc/module.go needs to be adjusted to work with older kernels. I am running it on 3.10.0-1127.18.2.el7.x86_64 (CentOS 7) and it does not work because of the function change.
https://github.com/iovisor/gobpf/blob/e6b321d3210387d6a09bde4feba22a09e8c6f4ae/bcc/module.go#L98

Could you check the BCC version you have installed? IIRC it's not related to the kernel version but to the BCC. It should work with BCC >= 0.11.0.

@mauriciovasquezbernal , thank you for your response! Greatly appreciated!
I am using  0.10 on CentOS 7.
# rpm -qa | grep bcc
bcc-tools-0.10.0-1.el7.x86_64
python-bcc-0.10.0-1.el7.x86_64
bcc-devel-0.10.0-1.el7.x86_64
bcc-0.10.0-1.el7.x86_64

@greenpau you're welcome!
In order to use gobpf you'll have to either update your BCC version (>= 0.11) or use an old version of gobpf (previous to this commit).
I highly recommend to update your BCC version so you don't get stuck with an old version that doesn't receive any update.


Fix relative uri detection to be cross-platform compatible

Fixes #428.

Thanks!

Yeah it's sad that these choices were made for Uri at the start that now lock us into not ideal behavior.


UID 1000 not found in xenial

Please paste the output of the following command here: sudo edit-chroot -all :name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
Creating hwaudio group with GID 18...
su: pam_start: error 26
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...```

#### Please describe your issue: i was following the guide laid out by you guys on installing this but every time i go through the process i keep getting UID 1000 not found even after following the troubleshooting guide here https://github.com/dnschneid/crouton/wiki/Common-issues-and-reportingprovided

#### If known, describe the steps to reproduce the issue:followed the exact guide provided by you guys to set it up ive even downloaded deleted and re downloaded the crouton provided i'm extremely baffled.

Please try the latest release of crouton and re-open if it doesn't fix the failure.

I ended up just getting a new laptop but that was tried
On Fri., Jul. 9, 2021, 9:12 p.m. David Schneider, @.***>
wrote:

Closed #4509 https://github.com/dnschneid/crouton/issues/4509.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/4509#event-5002631525, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUMSHTHIKAZXFG2BAXJASEDTW6GALANCNFSM46I2YT6Q
.


[WIP] Feat: Added support to get vtex_segment cookies from the validateSession

What's the purpose of this pull request?

[X] - Added support to get cookies from the Session
[x] - Added support to include and get public fields from the session

With that, we will be able to use utm campaign promotions in the purchase flow.
So we will be able to see the list and sellingPrice inside the shelf.

How it works?
Implementation steps:

[x] - Added support to send public fields in the validateSession mutation
[x] - Return the cookie property in the validateSession body
[x] - Added support to send the cookie property value do search query

When we pass the vtex_segment cookie to the search api, it will be able to know the session context, so if we are in a utm_campaign active, the search api  will considerer  that and responded the product list up to date

How to test it?

[x] - Clone this branch into your local machine
[x] - Run the API locally
[x] - Clone the trescoracoesfaststore.store repository in this branch: https://github.com/vtex-sites/trescoracoesfaststore.store/tree/feat/integrate_faststore_utm
[x] - In the package.json file of the trescoracoesfaststore.store replace the faststore api and sdk path to use the source code of this PR
[x] - Run tresCoracoes locally

In the trescoracoesfaststore environment, we have a utm promotion created: https://trescoracoesfaststore.myvtex.com/admin/rnb/#/benefit/5193f288-3319-4365-9e22-202a130908ad?page=1&perPage=20

[x] - into your local server of the theme, access the home page with queryString params: ?utm_campaign=outlet_5.

The theme source code is responsible for:

[x] - Listening this queryString
[x] - Inject this queryString in the orderForm inside the marketingData
[x] - call de validateSession passing the public fields, in this case, the utm_campaign with their value
[x] - Store the cookie returned from the validateSession mutation into the local cookies
[x] - Use this cookie to pass in the the search query to get the products with price promotion

Starters Deploy Preview

References

Extra tip
With this PR, all the stores using faststore will be able to use the utm promotion into the purchase flow and see the discounts in the shelf, like any VTEX IO or CMS Legacy store is

we do not support cookies yet, that being said, this PR can't be merged, however, we are looking into how to support cookies in the future.

we do not support cookies yet, that being said, this PR can't be merged, however, we are looking into how to support cookies in the future.

Hey @emersonlaurentino  how are you? : )
I know that Faststore doest not support cookies, so this is why I created this PR.
The mercafe team wants to be able to see the UTM promotion campaigns in the shelf, like works in the VTEX IO and CMS legacy. So I created this support here.
All Faststore customers needs this feature asap, is an essencial feature.
I'm copying here @Poowerllz that is from the tecnical mercafe team  and @v-hansen that supported us during the project time.

we know that, however, we make it clear that we don't support it, exactly because we need to understand how to implement it later.


Select field not bind an scope object but only an inner object (angular 1.3.9)

Hello everybody,
I found this bug with follow code:
$scope.myObject = {};

<select name="myObject" ng-model="myObject" ng-options="item as item.field for item in myData" required></select>

This is a workaround:
$scope.myObject = {
 innerObj: {}
};

<select name="myObject" ng-model="myObject.innerObj" ng-options="item as item.field for item in myData" required></select>

Can you resolve it?

Can you please post an example in a plnkr.co etc.? It's not possible to assess the problem from these code snippets.


Added a new beautiful patten written in python.

Contributing to Hacktoberfest @ 2021
Added a new beautiful pattern and named it siddharth.py

@siddharthdeo99 I'm closing the PR as it is not fulfilling the requirement...you can send a PR again after maintaining all the steps and eligibility criteria for a valid PR...


Fix $ref value as properly percent-encoded.

Hello everyone.
This PR is for fixing the issue #261 .
All test schemas for Draft-07, -06, and -04 after the modification, are tested by the validator of Justify with the schema validation against metaschema enabled.
Thank you.

Thanks both!


Maven-Docker Build cannot create docker image

Hello, I have the following problem. When building a Docker image with dockerfile, I get the following error message. Docker plugin is used in maven. Strangely enough i can build a docker image in other spring boot applications and there i do not get such an error message. I use docker for windows. I would be pleased if I could help me.
[INFO] Building image portal-appJSF
Nov 20, 2017 6:18:37 PM org.apache.http.impl.execchain.RetryExec execute
INFORMATION: I/O exception (java.net.SocketException) caught when processing request to {}->http://localhost:2375: Connection reset by peer: socket write error
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.721 s
[INFO] Finished at: 2017-11-20T18:18:37+01:00
[INFO] Final Memory: 30M/507M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.spotify:docker-maven-plugin:1.0.0:build (default-cli) on project portal-appJSF: Exception caught: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: org.apache.http.client.ClientProtocolException: Cannot retry request with a non-repeatable request entity: Connection reset by peer: socket write error -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Process finished with exit code 1

I encounter the same problem. Did you find a solution?
Output of docker version:
Client:
Version:      17.09.0-ce
API version:  1.32
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:40:09 2017
OS/Arch:      windows/amd64
Server:
Version:      17.09.0-ce
API version:  1.32 (minimum version 1.12)
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:45:38 2017
OS/Arch:      linux/amd64
Experimental: true

The error message in the original issue indicates that the docker daemon is not listening at the address the plugin is trying to communicate with it at. See the “Setup” section of the readme for how you can customize the address to reach docker at.

echo %DOCKER_HOST%
tcp://localhost:2375

During the build i get this:
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.6:build (default) on project bcc-config-service-standalone: Execution default of goal com.spotify:dockerfile-maven-plugin:1.3.6:build failed: Illegal char <:> at index 3: tcp://localhost:2375 -> [Help 1]

I solved the problem by using the new plugin dockerfile-maven. Was not the deamon as previously mentioned but the plugin.

For me the issue was Capital letter in image name while building the Image .
For example following plugin configuration was giving me error .
<plugin>
           <groupId>com.spotify</groupId>
           <artifactId>dockerfile-maven-plugin</artifactId>
           <version>1.3.6</version>
           <configuration>
           <useConfigFile>false</useConfigFile>
           <useMavenSettingsForAuth>true</useMavenSettingsForAuth>
               <repository>${docker.image.prefix}/dockerAgent</repository>
           <buildArgs>
   	<JAR_FILE>target/${project.build.finalName}.jar</JAR_FILE>
   		</buildArgs>
           </configuration>
   <executions>
   <execution>
   	<id>default</id>
   	<phase>install</phase>
   	<goals>
   		<goal>build</goal>
   	</goals>
   </execution>
   </executions>
       </plugin>

The Issue got resolved by changing the "dockerAgent" to dockeragent (all letters in small cases).

I have the same issue running Docker and Maven on Windows. My configuration tag was

${docker.image.prefix}/${project.artifactId}
...
And the ${project.artifactId} resolved to a name that had capital letters.
This led to the error "Cannot retry request with a non-repeatable request entity: Connection reset by peer: socket write error -> [Help 1]".
Changing the docker image to lowercase fixed it.
Thanks abhisheknn

For me the issue was an extra / in the name. My configuration was ${docker.image.prefix}/${project.artifactId}, and the prefix itself already had a /.

I believe this issue should re-opened, there is totally no error message that indicates a problem with uppercase / lowercase. This should be fixed in the plugin.

I had the same issue running Docker and Maven on Windows. My configuration tag was
${docker.image.prefix}/${project.artifactId}
...
And the ${project.artifactId} resolved to a name that had capital letters.
This led to the error "Cannot retry request with a non-repeatable request entity: Connection reset by peer: socket write error -> [Help 1]".
Changing the docker image to lowercase fixed it.
Thanks abhisheknn

This fixed it for me. seems to be an issue with the plugin

I can confirm that changing the repository-name to my own value (instead of project.artifactId) fixed this. The ${project.groupId}/${project.artifactId} has upper-case chars.
<plugin>
  <groupId>com.spotify</groupId
  <artifactId>dockerfile-maven-plugin</artifactId>
  <version>1.4.10</version>
...
  <configuration>
    <repository>${project.groupId}/${project.artifactId}</repository>
    <tag>${project.version}</tag>
  </configuration>
</plugin>

to
<plugin>
  <groupId>com.spotify</groupId
  <artifactId>dockerfile-maven-plugin</artifactId>
  <version>1.4.10</version>
...
  <configuration>
    <repository>domain/my_project_name</repository>
    <tag>${project.version}</tag>
  </configuration>
</plugin>

For me the issue was Capital letter in image name while building the Image .
For example following plugin configuration was giving me error .
<plugin>
           <groupId>com.spotify</groupId>
           <artifactId>dockerfile-maven-plugin</artifactId>
           <version>1.3.6</version>
           <configuration>
           <useConfigFile>false</useConfigFile>
           <useMavenSettingsForAuth>true</useMavenSettingsForAuth>
               <repository>${docker.image.prefix}/dockerAgent</repository>
           <buildArgs>
   	<JAR_FILE>target/${project.build.finalName}.jar</JAR_FILE>
   		</buildArgs>
           </configuration>
   <executions>
   <execution>
   	<id>default</id>
   	<phase>install</phase>
   	<goals>
   		<goal>build</goal>
   	</goals>
   </execution>
   </executions>
       </plugin>

The Issue got resolved by changing the "dockerAgent" to dockeragent (all letters in small cases).

It worked for me as well. Thanks a ton :)

This solved the issue.Thanks.

Don't understand why we don't think such issues are a serious thread to open-source in contemporary software.

Work for me. It is very simple issue. check name of your project.
I have name in Uppercase like this name = Xyz. I change to lower case and every thing work fine. ${project.name} = xyz . Thank you  all

I too had the same problem
We need not remove the capital cases I belive
dockerfile plug in uses project version
my pom.xml was having  0.0.1-SNAPSHOT and i changed it to 0.0.1.SNAPSHOT  and images built succesfully


provide read access to carina CI

as it is open source we have to provide anonymous access to jobs/logs for community to analyze failures if any with PR, have access to javadocs etc

done: https://ci.qaprosoft.com/jenkins/job/carina/


PLEASE DO NOT APPROVE - bug bounty testing - please ignore. qsznkd

PLEASE DO NOT APPROVE - bug bounty testing - please ignore. qsznkd

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Rename TextInput prop "autoCompleteType" to "autoComplete"

PR https://github.com/facebook/react-native/pull/21575 added support for "autoComplete", based on the web standard, but implemented it under the prop name "autoCompleteType". We should rename this prop to "autoComplete"

@cassiozen could you please answer the question

The issue has not been fixed yet

Bump. What's the status of this, will it be aligned?

It looks like this was implemented in 27fec9569e08a04e0dbdbd5de063a599ad0416fa, and can be closed.

This should be closed as stated by @simon-abbott

Thanks!


support redact SHOW CREATE on demand

Is your feature request related to a problem? Please describe.
Sensitive properties of source/sink, e.g. s3.credentials.secret and schema.registry.password, should be redacted first before included in text that may be shared, e.g. show create source/sink/table, diagnostic report.
#12673
Describe the solution you'd like
Developers are responsible for tagging properties as redactable. When displayed, these tagged properties will be redacted first if required.
Describe alternatives you've considered
No response
Additional context
#7034

How is this related with https://github.com/risingwavelabs/risingwave/issues/7034?

How is this related with https://github.com/risingwavelabs/risingwave/issues/7034?

Pls ignore that. Previously I thought changes on persisted catalog was required, but it turns out to be wrong.

Hi, @zwang28 any progress?

Hi, @zwang28 any progress?

#14760 adds a helper function to redact a SQL string. It's under review.
With regards to its call site. I intended to:

Always redact in diagnostic report.
Because I think sometimes user does want to view the secrets, should show create be optionally redact, e.g. based on user role?

As SECRETS will be premium feature (https://docs.risingwave.com/docs/dev/manage-secrets/), can we reopen this?

I think we are not going to support this and you can use the premium edition.

@stefannegele Thanks for your feedback. Let me look into it.


Overview page should set link to search context

Who is this for?
Users of the overview page when searching should be able to return back to the search page when they click on a work.
now, the question is if I should expand this logic and feature to stories pages?
What is it doing for them?
simply ensuring the search result page (Overview) updates the SearchContext was enough for the stories page to acknowledge that there was a search happening.

now, the question is if I should expand this logic and feature to stories pages?

one for @jtweed or @jennpb ? 👀

Another question: Should we make it work for filters as well? It currently only works if there is a query, but if someone uses filters without a query (which might not be a thing, again, I'm just asking), it doesn't offer a Back to results link.

I'd vote for not doing for stories, as search isn't a primary journey for stories in the same way as it is for works and we don't have the design support right now to integrate the link into the header without it being distracting.
However it should work if there are applied filters, not just if there is a full text query.


account update - add indexable

https://docs.joinmastodon.org/methods/accounts/#update_credentials

check Account.noindex

updateCredentials with indexable set returns an Account with indexable but doesn't affect noindex, and indexable does not appear in future inspection of the Account


can't get it to work with gradle 4.x..

hi there.  thanks for this awesome work.  i noticed i can get it to work with gradle 3.5 but not 4.x, not sure why.

Hi @eitansuez,
Thanks for the heads up! I've pushed a fix (https://github.com/mdietrichstein/gradle-offline-dependencies-plugin/commit/ae28bb959fb32e530f3da64801f3107732d9de87) that should make the plugin compatible with gradle 4.x.

wonderful.  thanks.  i'll likely try it out next week.
/ eitan
On Fri, Sep 22, 2017 at 9:09 AM, Marc Dietrichstein <
<EMAIL_ADDRESS>wrote:

Hi @eitansuez https://github.com/eitansuez,
Thanks for the heads up! I've pushed a fix (ae28bb9
https://github.com/mdietrichstein/gradle-offline-dependencies-plugin/commit/ae28bb959fb32e530f3da64801f3107732d9de87)
that should make the plugin compatible with gradle 4.x.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mdietrichstein/gradle-offline-dependencies-plugin/issues/1#issuecomment-331457559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAY2UC0Br6nRque0V5KAOH1VTX2K7tMks5sk7-VgaJpZM4Pek9i
.

I think it still doesn't work. This is the result I have : (Windows + Cygwin)
./gradlew updateOfflineRepository -PofflineRepositoryRoot=./offline-repository
:updateOfflineRepository FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':updateOfflineRepository'.

Could not resolve all dependencies for configuration ':detachedConfiguration1'.
Cannot resolve external dependency gradle.plugin.io.pry.gradle.offline_dependencies:gradle-offline-dependencies-plugin:0.3 because no repositories are defined.
Required by:
project :

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Get more help at https://help.gradle.org

BUILD FAILED in 1s
1 actionable task: 1 executed
My build.gradle is :
buildscript {
repositories {
maven {
url offlineRepositoryRoot
}
maven {
url 'https://plugins.gradle.org/m2/'
}
mavenCentral()
jcenter()
google()
}
dependencies {
classpath 'gradle.plugin.io.pry.gradle.offline_dependencies:gradle-offline-dependencies-plugin:0.3'
classpath 'com.android.tools.build:gradle:3.0.1'
}
}
apply plugin: 'io.pry.gradle.offline_dependencies'

@omarbelkhodja I'm experiencing the same error. I'm running Gradle 4.2.1 on Linux. Did you manage to resolve this?


    docs: Removed an unwanted closing parenthesis

New updates on head repo.
https://github.com/vitejs/vite/commit/b010678f9de81ddbb5ee73d449f4f0a48f6b0958

対応します


Use nproc*2 instead of the older approach for CPU_NUM

The Ugly:
In this pull request, I am changing the CPU_NUM value back to nproc command which results the correct value of '4' in DC02, instead of the incorrect '12'
According to bitbake documentation here:

The maximum number of tasks BitBake should run in parallel at any one time. If your host development system supports multiple cores, a good rule of thumb is to set this variable to twice the number of cores.

Therefore, I am multiplying CPU_NUM by 2 for BB_NUMBER_THREADS.
However, for PARALLEL_MAKE and every other parallel setting, the documentation says they all default to the number of cores. So no need to override them.
The Good:

This will cause the bitbake command with cache to complete around 10% faster.
This will cause running multiple bitbake runs to add less pressure on the server.

I recall that the reported issue appeared on Windows 10 with WSL.

I don't think the failure in the execution of this command is significant. We can change the script to ignore it if it fails like this:
(NUM_CPU=$(nproc) && echo "BB_NUMBER_THREADS = \"$((NUM_CPU*2))\"" >> ${LOCALCONF}) || :

What do you think?

I recall that the reported issue appeared on Windows 10 with WSL.

I don't think the failure in the execution of this command is significant. We can change the script to ignore it if it fails like this:
(NUM_CPU=$(nproc) && echo "BB_NUMBER_THREADS = \"$((NUM_CPU*2))\"" >> ${LOCALCONF}) || :

What do you think?

Were you able to duplicate the problem? Mh, yes, ignore it.

Were you able to duplicate the problem?

It makes sense to get an error on WSL 1.
It is very common for WSL 1 to throw an error when a low-level command is executed. Microsoft tried to fix these errors one by one until they got tired and released WSL 2 which uses Hyper-V and a Linux kernel as opposed to their finicky translation layer.


fix an issue of Fan device type sending command

Issue Description: We onboarding Yeelight Fan(bridged device) device to ST App, but we are unable to control device by sending fan mode or speed.
Problem Analysis: Upon reviewing the logs, it was found that the command send to a wrong endpoint (endpoint 0 for the yeelight bridge instead of endpoint 68 for the yeelight fan). It was caused by the local function  "component_to_endpoint" in matter-thermostat/init.lua 158. We revised the edge driver by adding an "elseif" statement for returning Fan device type related endpoint. (As per Matter Device Library Spec, there are 3 device type in HVAC, including Thermostat, Fan and Air Purifier. However, It should be noted that the Fan device is currently absent from the function "component_to_endpoint".)

(endpoint 0 for the yeelight bridge instead of endpoint 68 for the yeelight fan) -> (endpoint 1 for the yeelight bridge instead of endpoint 68 for the yeelight fan)

@ctowns could you plz help to review for the updated driver？

Tagging @z-michel for awareness.

this is issues from Yeelight WWST

@pInksenberg this has been approved and I think this is ready to merge. Can you confirm that this change has been tested? If it has been tested and is working, it can be merged.

@ctowns I attached the test result in https://smartthings.atlassian.net/browse/MTR-780

So can this change be merged? It looks like things are working as expected


Capture window pop-up

Hi,
Can anyone please suggest me a way to capture window pop-up name in jmeter? Is the latest version of citrix plugin support this?
Something similar to below function in loadrunner ctrx_get_window_name(window_name).
I really appreciate any reply or suggestions on this.
Regards,
Madeppa

Hi @Madeppa
On JMeter the more common way to extract values is using "Extractors".
The Citrix plugin provide the "OCR Extractor", allowing to extract any type of text from a specific section of an active window
https://github.com/Blazemeter/CitrixPlugin/blob/master/MANUAL.md#citrix-ocr-extractor
Also, you can use the "Assessment extractor", a post processor for "End Clauses" allowing to you to get the value of the evaluated End Clause value from any type of Citrix Iteration
https://github.com/Blazemeter/CitrixPlugin/blob/master/MANUAL.md#citrix-assessment-extractor
You can create a Iteration without actions and use a End Clause like Windows Exist, Windows Close or Window Gets Foreground with different timeout and get the actual value of the active windows adding the "Assessment extractor".
https://github.com/Blazemeter/CitrixPlugin/blob/master/MANUAL.md#citrix-interaction
You need only to take in consideration the waiting time to make the check and the timeout used on the End Clause to coordinate the capture of the actual window.
Also, you can use the End Clause Text (OCR) if you know the relative position of the text in the title bar of the window, and get the value captured with "Assessment extractor".

Hi @3dgiordano,
Thank you for your prompt response!!
As you suggested above, we are able to validate window name using Window exists but in this case we are providing the window name and validating it. Here my concern is that, without giving window name is there any other method to capture the active window name?
At present in End Clause regarding window there are 3 options like Windows Exist, Windows Close and Window Gets Foreground.
Can we add another options like 'Current Window name' or 'Get Window name' or something. With this option we can add Interaction without actions and using a End clause as  'Get Window name' and not providing any Expected value. So whatever the window name we get we can store it in 'Assessment Extractor' variable. Like this we can get the current active window name.
Not sure whether this is possible or not but a suggestion.
Regards,
Madeppa


Define how "config endpoint" response looks

Suggestion:
{
    "global": {
        "allowedOrigins": ["https://some.service.no/"],
        "allowUndefinedChannels": true,
        "historyLength": 500
    },

    "channels": [{
        "path": "/some/path",
        "allowedOrigins": ["https://some.host"],
        "historyUrl": "https://some.url/which/talks/json",
        "historyLength": 50
    }, {
        "path": "/otherpath",
        "allowedOrigins": false
    }]
}

allowedOrigins is used in the CORS handling - false means do not allow any cross-origin requests, array of values means use those specific origins. If it's not set for a specific channel, use the global value.
allowUndefinedChannels sets whether the hub should allow connections on channels that are not in the channels array.
historyUrl specifies an HTTP endpoint where the hub can go to fetch the initial history it should preload into memory.
historyLength defines (on a global/channel level) how many messages it should keep in memory.

This looks like a format that covers what we need in a good way.
Let's stick to it.
I will start to implement it in the hub


Unable connect to any pod from master

Hi,
I'm trying to setup Kubernetes in Openstack + CoreOS.
I have master <IP_ADDRESS> and 2 minions .63 and .83. I also created 3 redis pods:
redis-gopher-gziey        <IP_ADDRESS>     <IP_ADDRESS>/<IP_ADDRESS>
redis-managed-oh43e   <IP_ADDRESS>     <IP_ADDRESS>/<IP_ADDRESS>
redis-primary-fplln          <IP_ADDRESS>     <IP_ADDRESS>/<IP_ADDRESS>

master's routing table looks like:
<IP_ADDRESS>     *               <IP_ADDRESS>   U     0      0        0 eth0
<IP_ADDRESS>     *               <IP_ADDRESS> UH    1024   0        0 eth0
<IP_ADDRESS>      *               <IP_ADDRESS>     U     0      0        0 flannel.1
<IP_ADDRESS>     *               <IP_ADDRESS>   U     0      0        0 docker0

and output of ifconfig -a is :
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::542f:6fff:fe4a:adf3  prefixlen 64  scopeid 0x20<link>
        ether 56:84:7a:fe:97:99  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1  bytes 90 (90.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::f816:3eff:fe89:e9a0  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:89:e9:a0  txqueuelen 1000  (Ethernet)
        RX packets 430706  bytes 559764129 (533.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 238519  bytes 116083693 (110.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601f:62ff:feed:1556  prefixlen 64  scopeid 0x20<link>
        ether 62:1f:62:ed:15:56  txqueuelen 0  (Ethernet)
        RX packets 20  bytes 1504 (1.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 79  bytes 7686 (7.5 KiB)
        TX errors 0  dropped 19 overruns 0  carrier 0  collisions 0

Flanneld config used for initialization is:
Master:
        - name: flanneld.service
          command: start
          drop-ins:
            - name: 50-network-config.conf
              content: |
                [Service]
                ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{"Network":"<IP_ADDRESS>/16", "Backend": {"Type": "vxlan"}}'
                ExecStart=
                ExecStart=/usr/libexec/sdnotify-proxy /run/flannel/sd.sock \
                    /usr/bin/docker run --net=host --privileged=true --rm \
                        --volume=/run/flannel:/run/flannel \
                        --env=NOTIFY_SOCKET=/run/flannel/sd.sock \
                        --env-file=/run/flannel/options.env \
                        --volume=${ETCD_SSL_DIR}:/etc/ssl/etcd:ro \
                        quay.io/coreos/flannel:${FLANNEL_VER} /opt/bin/flanneld --ip-masq=true --iface=eth0

Minion:
        - name: flanneld.service
          command: start
          drop-ins:
            - name: 50-network-config.conf
              content: |
                [Service]
                ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{"Network":"<IP_ADDRESS>/16", "Backend": {"Type": "vxlan"}}'
                ExecStart=
                ExecStart=/usr/libexec/sdnotify-proxy /run/flannel/sd.sock \
                    /usr/bin/docker run --net=host --privileged=true --rm \
                        --volume=/run/flannel:/run/flannel \
                        --env=NOTIFY_SOCKET=/run/flannel/sd.sock \
                        --env-file=/run/flannel/options.env \
                        --volume=${ETCD_SSL_DIR}:/etc/ssl/etcd:ro \
                        quay.io/coreos/flannel:${FLANNEL_VER} /opt/bin/flanneld -etcd-endpoints     http://<IP_ADDRESS>:4001 --ip-masq=true --iface=eth0

So the issue is that i can't ping any of the pods from master, as well as connect to any port, error is:
ncat -v -t <IP_ADDRESS> 6379
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: No route to host.

@ArtfulCoder

It happens again when i tried to re-create cloud from scratch.
I think this information will be helpful
minion - https://gist.github.com/roman-shuhov/819d26f402699d63edb0
master - https://gist.github.com/roman-shuhov/02432247fce7a9603fe7
additional information
https://gist.github.com/roman-shuhov/335ad0f54ce49bc84582

Your service iptables rules look right for the two built-services.  If you
run two docker containers on two nodes, can they ping each other?  That is
step 1.
On Apr 3, 2015 1:51 PM, "T3[rm]1T"<EMAIL_ADDRESS>wrote:

It happens again when i tried to re-create cloud from scratch.
I think this information will be helpful
minion - https://gist.github.com/roman-shuhov/819d26f402699d63edb0
master - https://gist.github.com/roman-shuhov/02432247fce7a9603fe7
additional information
https://gist.github.com/roman-shuhov/335ad0f54ce49bc84582
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/6311#issuecomment-89416053
.

They can't ping each other, here is some output https://gist.github.com/roman-shuhov/4acc09609a349b7becf0

So this is the root of the problem.  Please check your network install - I
think you said it was flannel?  I am out until Tuesday, but the other smart
folks here can help in the mean time :)
On Apr 3, 2015 2:16 PM, "T3[rm]1T"<EMAIL_ADDRESS>wrote:

They can't ping each other, here is some output
https://gist.github.com/roman-shuhov/4acc09609a349b7becf0
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/6311#issuecomment-89422627
.

thanks, do you have any thoughts what can be wrong with flannel?

On the master we can confirm that docker bridge sits correctly behind the flannel bridge.
The docker net address is within the flannel.1 net.
docker:    inet <IP_ADDRESS>  netmask <IP_ADDRESS>
flannel.1: inet <IP_ADDRESS>  netmask <IP_ADDRESS>
You can do the same check on the minions. If this check fails on the minions, obviously, that is the problem.
Though, I must that that I would be surprised if this were a problem, since it is a core setup that flannel strives to get right.
Also, all the docker subnets across the various kubernetes nodes must be unique.
You already did the connectivity test without using kubernetes service-ips, so we know its not a kubernetes service-ip problem.
A side-note: currently, your flannel uses etcd running on kubernetes master. As of friday afternoon, I have checked in code to make etcd of kubernetes, private to kubernetes-master, where it listens only on <IP_ADDRESS>:4001.  So, you will have to run on your own etcd for flannel to use.

We’re going through old support issues and asking everyone to direct your questions to stackoverflow.
We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs.
The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered.


swaglog: add test case

It seems that we should handle EAGAIN on zmq_send carefully to avoid losing messages


trim hostname in lucy input field

When entering a hostname starting or ending with a space, you get an error message, that there are invalid characters, but for a fast-paced person it is not really visible where.
This ist the same with many other input fields.
It would be handy if all field entries that don't allow the space or tap character would automatically be trimmed before validation on save so you only get an error message if you do something really wrong.

Can we add this?
Or which module would I have to modify, to achieve this myself?

You need to edit cbi.js and datatypes.lua

related: https://github.com/freifunk-gluon/gluon/issues/414#issuecomment-161831581

Personally, I am against auto-trimming inputs, especially due to the added complexity for fields that do accept spaces.
If someone proposes a clean and manageable change implementing this I might reconsider. As of now, I don't have plans to implement that.


The logpdf from ExponentialFamily.jl is slower then from Distributions.jl

I have such example for evaluating the multivariate normal log probability density function (logpdf):
using ExponentialFamily
using StableRNGs
using LinearAlgebra
using Distributions
using BenchmarkTools

rng = StableRNG(42)
n = 4
golden_μ = randn(rng, n)
L = randn(rng, n, n)
golden_Σ = L * L' + Matrix{Float64}(I, n, n)

golden_normal = Distributions.MvNormal(golden_μ, golden_Σ);
ef_mv_normal = ExponentialFamily.MvNormalMeanCovariance(golden_μ, golden_Σ)
ef = convert(ExponentialFamily.ExponentialFamilyDistribution, ef_mv_normal)

samples = rand(golden_normal, 1000);

@benchmark logpdf($golden_normal, $samples)
@benchmark logpdf($ef_mv_normal, $samples)

hybridlinearize(matrix::AbstractMatrix) = eachcol(matrix)

@benchmark map((x) -> logpdf($(ef), x), $(hybridlinearize(samples)))

The results:
BenchmarkTools.Trial: 10000 samples with 1 evaluation.
 Range (min … max):  125.000 μs …  1.147 ms  ┊ GC (min … max): 0.00% … 84.03%
 Time  (median):     140.000 μs              ┊ GC (median):    0.00%
 Time  (mean ± σ):   146.581 μs ± 62.614 μs  ┊ GC (mean ± σ):  2.80% ±  5.73%
 Memory estimate: 211.44 KiB, allocs estimate: 3003.

 BenchmarkTools.Trial: 10000 samples with 1 evaluation.
 Range (min … max):  287.125 μs … 945.667 μs  ┊ GC (min … max): 0.00% … 61.13%
 Time  (median):     299.459 μs               ┊ GC (median):    0.00%
 Time  (mean ± σ):   306.335 μs ±  57.800 μs  ┊ GC (mean ± σ):  1.88% ±  6.45%

 BenchmarkTools.Trial: 2539 samples with 1 evaluation.
 Range (min … max):  1.793 ms …   4.692 ms  ┊ GC (min … max): 0.00% … 59.40%
 Time  (median):     1.833 ms               ┊ GC (median):    0.00%
 Time  (mean ± σ):   1.968 ms ± 566.244 μs  ┊ GC (mean ± σ):  6.32% ± 12.40%

Clearly, the result from the ExponentialFamily.ExponentialFamilyDistribution comes from re-evaluating the log partition for each sample. However, should this be avoided? But even just ExponentialFamily.MvNormalMeanCovariance is considerably slower.

This is expected behaviour. Different parametrizations have different speed characteristics when evaluating logpdf or rand. The natural parameters space is far from being ideal for logpdf evaluation so it is indeed slower. The fact that MvNormalMeanCovariance is slower is also expected, because it requires extra inverses.
The idea is to use logpdf_optimized function defined in BayesBase.jl, which returns an optimal parametrization for repeated logpdf evaluation. However, we did not have time to implement it properly for ExponentialFamilyDistribution structure. I guess for now it works only for Distribution structures.
julia> optimised = logpdf_optimized(golden_normal); # should return MvNormalMeanPrecision

julia> @benchmark logpdf($golden_normal, $samples)
BenchmarkTools.Trial: 10000 samples with 1 evaluation.
 Range (min … max):  229.023 μs … 838.760 μs  ┊ GC (min … max): 0.00% … 65.07%
 Time  (median):     232.834 μs               ┊ GC (median):    0.00%
 Time  (mean ± σ):   242.893 μs ±  42.271 μs  ┊ GC (mean ± σ):  1.04% ±  4.62%

  ▂█▅▃▄▃ ▃▂▁▅▃ ▁▂▁    ▁  ▁                                      ▂
  █████████████████▇▇██████▆▄▇▆▄▄▆▅▅▃▆▆▅▄▆▆▆▆▆▆▅▅▅▄▆▇▃▄▁▃▄▃▄▃▄▃ █
  229 μs        Histogram: log(frequency) by time        352 μs <

 Memory estimate: 211.44 KiB, allocs estimate: 3003.

 julia> @benchmark logpdf($optimised, $samples)
BenchmarkTools.Trial: 10000 samples with 1 evaluation.
 Range (min … max):  147.888 μs …  1.122 ms  ┊ GC (min … max): 0.00% … 83.80%
 Time  (median):     152.977 μs              ┊ GC (median):    0.00%
 Time  (mean ± σ):   158.866 μs ± 43.102 μs  ┊ GC (mean ± σ):  1.91% ±  5.80%

  ▇▇█▇▃      ▁                                                 ▂
  ██████▆▅▅▇██▆▇▅▄▂▃▄███▇▆▇▆▄▆▆▅█▆▄▆▅▅▅▆▆▆▇▇▅▄▅▄▅▄▄▅▄▂▄▃▂▄▄▄▅▄ █
  148 μs        Histogram: log(frequency) by time       265 μs <

 Memory estimate: 289.19 KiB, allocs estimate: 2001.

Thus being said, there is still a lot of room for improvements. We can keep this issue open for future reference.

Yes, you are absolutely correct; different parametrizations exhibit varied speed characteristics when evaluating logpdf.
However, I didn't understand why we can't adopt a seemingly simplistic approach like the following: if we want to evaluate a container of samples for the same distribution, we will reuse the log-partition (which appears to be the primary issue).
For instance, something like this:
using ExponentialFamily
using StableRNGs
using LinearAlgebra
using Distributions
using BenchmarkTools

rng = StableRNG(42)
n = 4
golden_μ = randn(rng, n)
L = randn(rng, n, n)
golden_Σ = L * L' + Matrix{Float64}(I, n, n)

golden_normal = Distributions.MvNormal(golden_μ, golden_Σ);
ef_mv_normal = ExponentialFamily.MvNormalMeanCovariance(golden_μ, golden_Σ)
ef = convert(ExponentialFamily.ExponentialFamilyDistribution, ef_mv_normal)

samples = rand(golden_normal, 1000);

@benchmark logpdf($golden_normal, $samples)
@benchmark logpdf($ef_mv_normal, $samples)

hybridlinearize(matrix::AbstractMatrix) = eachcol(matrix)

@benchmark map((x) -> logpdf($(ef), x), $(hybridlinearize(samples)))

function _logpdf(ef, x::AbstractMatrix)
	stats_part = map(
		(s) -> begin
			stats = ExponentialFamily.sufficientstatistics(ef, s)
			sum(ExponentialFamily.pack_parameters(stats) .* ExponentialFamily.getnaturalparameters(ef))
		end,
		hybridlinearize(x)
	)

	basemeasure_part = map(
		(x) -> begin
			log(ExponentialFamily.basemeasure(ef, x))
		end,
		hybridlinearize(x)
	)

	logpartion_part = logpartition(ef)

	return stats_part .+ basemeasure_part .- logpartion_part
end

@benchmark _logpdf($(ef), $(samples))

For example for normals it's efficient enough:
BenchmarkTools.Trial: 10000 samples with 1 evaluation.
 Range (min … max):  126.709 μs …   1.958 ms  ┊ GC (min … max):  0.00% … 91.33%
 Time  (median):     130.125 μs               ┊ GC (median):     0.00%
 Time  (mean ± σ):   155.554 μs ± 187.075 μs  ┊ GC (mean ± σ):  14.23% ± 10.78%

  █▂                                                            ▁
  ██▇▆▄▅▃▃▄▁▁▁▁▃▁▁▁▁▁▁▁▁▁▃▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▅▇ █
  127 μs        Histogram: log(frequency) by time       1.65 ms <

 Memory estimate: 649.19 KiB, allocs estimate: 3005.

I think you are right, we definitely can (and should) do it. Would mine opening a PR for that?

yes, I can 👍

Can be closed?

Yes, I think so, we have a separate issue for MvNormalWishart https://github.com/biaslab/ExponentialFamily.jl/issues/148. For all other distributions: the approach is working.


Controller Triggers stay pressed on Android

Godot version
4.1.stable
System information
Android 12, OneUI 4.1, Galaxy S10e | Godot 4.1.stable
Issue description
Description
On Android, Controller Triggers once pressed, stay pressed until the game is restarted
Video:
On Windows - everything works as intended.
https://github.com/godotengine/godot/assets/78328941/ee7976ab-b35a-4f91-888b-f3774c42e1b0
On Android - Once a Trigger is pressed, it stays pressed (Inverted triggers is a separate issue).
https://github.com/godotengine/godot/assets/78328941/981b514a-1c17-4490-9313-f72d89dec4d4
The Setup
Input Map

Scene

Code

Steps to reproduce

Set up triggers in Input Map
Make them do anything...
Export to Android
Press the Trigger, and thing only happens once, even if pressed multiple times.

Minimal reproduction project
controller trigger test.zip

Which device model are you using on desktop and Android? Is it the same controller model on both platforms?

I've tested it using both an XBox Series controller, and the 8BitDo Pro 2. The staying-pressed issue persists with both controllers, however it seems only the XBox controller has the Inverted Triggers problem (LT being RT, and RT being LT).

The swapped triggers issue on an Xbox controller was already reported in https://github.com/godotengine/godot/issues/56181.

Thanks. I updated the post.

I've observed this bug on Android using an Xbox One X Bluetooth controller. The game in question was built with Godot 3.5.
I'd be interested in tackling this but I'm not sure where to start. I was looking around here but I couldn't discern if the triggers are being treated differently from the other buttons in some way.

I wrote a minimal sample project to supplement the original one that displays the numerical joystick axis value for the R2 trigger. On PC it goes from 0 to 1 as expected. On Android, after the initial event trigger, it stays stuck with both a continuous read in _process and motion events.
TriggerTest.zip

Found the culprit! The platform-agnostic input handler is indiscriminately adding 0.5 to the analog triggers: https://github.com/godotengine/godot/blob/75de1ca76871fdf7f5a9e081aa57ec0e33061107/core/input/input.cpp#L1120C7-L1120C7
Android's motion event for L2 and R2 already have a range from 0 to 1, so this conversion is not necessary on Android and ends up breaking the value.
https://developer.android.com/reference/android/view/MotionEvent#AXIS_RTRIGGER

For a joystick, reports the absolute position of the right trigger control. The value is normalized to a range from 0.0 (released) to 1.0 (fully pressed).

In the meantime, I was able to workaround this bug by changing the threshold value in the input map to something higher than 0.5 (I settled on 0.7 for my title).

I'm using Godot 4.3 and this issue seems to still exist. The triggers rest at 0.5 and go to 1.0 when pressed.


Linuxfs multi byte registers

multi-byte register
This work supports  register address of more than one byte.  Required for the large at24c512 SEEPROM and some controllers.   Pigpio does NOT support this. Digging in the Pigpio web site when asked about this support they point to something a user did and show a link to that code. I did not look into this.  I do not think Pi4j should pull in that code unless it was part of Pigpio.
This bring us to the new signature I added. The current pi4j implementation means this new signature is visible on linuxfs, pigpio mock and raspi.  I could not see how to this only in linuxfs, If there is a means to do this give me a pointer on how.   If separation is not possible, I did not see a means to make this signature invisible in Pigpio provider.  Again I welcome any ideas.   All that aside how should I tell the user the problem runtime ?
There is a device in my example devices that uses the new code.
AT24C512

@eitch   hey Robert.  We spoke about this several weeks back. Here is what I coded for your review.  I have several questions written into the PR comment.

@eitch    I made the changes mentioned in review comments.  I looked at the mock provider code, when I view the i2c test I find many are missing.  Maybe I failed to look in the correct files but I found no logical place to add the call to the new interface.
Also, I made the change suggested by Frank Harlan as it looks to be needed, but assume you will still integrate his work to show credit to his investigation.
Let me know your further suggestions.  thanks Tom

@taartspi Thanks for the changes. From what i understand, then we don't need require com.sun.jna, right? Can you remove that?

@eitch  I pushed the files that contained unneeded use of the JNA Sun code.   please review at your convenience.
thanks Tom.
PS after I complete work with a display I will review what testcases are required to complete the I2C MOCK

@taartspi merged


[Feature] Plain HTML/JS support

I really love the design and everything about the editor, but I don't use React or Vue in any of my projects.
Is there any plan or way to just implement it via a script tag into an existing framework independent project?
Thanks in advance and best regards,
Louis

You can just use the vanilla version like this:
https://codesandbox.io/s/milkdown-vanilla-setup-8xobc

Thank you so much!


ValueError: non-hexadecimal number found in fromhex() arg at position 4

Hey all,
I just installed this add-on (I used python). My Gateway is mosquitto.
Add-On Version is 0.4.6
The Sensors (HA Discovery) get created but after a while this error comes up and no values are pulled:
2024-01-27 00:03:53,097 [ ERROR  ] 'handle_vehicle_XXXXXXXXXXXXX' task crashed with an exception - __main__
Traceback (most recent call last):
  File "/usr/src/app/./mqtt_gateway.py", line 90, in handle_vehicle
    vehicle_status = self.update_vehicle_status()
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/app/./mqtt_gateway.py", line 110, in update_vehicle_status
    vehicle_status_rsp_msg = self.saic_api.get_vehicle_status_with_retry(self.vin_info)
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 193, in get_vehicle_status_with_retry
    return self.handle_retry(self.get_vehicle_status, vin_info)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 457, in handle_retry
    return self.__handle_retry_with_app_data(func, vin_info=vin_info, max_retries=max_retries)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 488, in __handle_retry_with_app_data
    rsp = func(vin_info)
          ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 188, in get_vehicle_status
    self.message_V2_1_coder.decode_response(vehicle_status_rsp_hex, vehicle_status_rsp_msg)
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/ota_v2_1/Message.py", line 12, in decode_response
    return super().decode_response(message, decoded_message)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/common_model.py", line 495, in decode_response
    buffered_message_bytes = io.BytesIO(bytes.fromhex(message[5:]))
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: non-hexadecimal number found in fromhex() arg at position 4

I am not a programmer but it seems like some variables have the wrong declaration of datatype - or the API sends information to the wrong places
I already tried reinstalling it as well as tested the Java Add-On - this gave me another error which I didnt really looked into as I planned to use python regardless.
My HA is on versions:
Core
2024.1.5
Supervisor
2023.12.1
Operating System
11.4
Frontend
20240104.0
Thank yall

Hi,
Same here, but my integration was working allready until yesterday 11:48.
Looks like there are problems with the API at SAIC site and maybe there are some changes comming as well?

Lucky me then timin wise :D
I read something about an API 2.0 or the new iSmart 2 App - tbh, my App got a big rework a few weeks ago so maybe they did some changes there and those brilliant people of this community need time to figure out :) I'm sure either way they will get it to work. THanks to everyone putting their time and effort in those things.

It is solved - you just have to refresh your car in the I smart app once. After that it works. Don't ask me why please^^

I think it is a server problem. I used the app yesterday evening, but also after that the gateway won't work.

Did you try a complete scan of the car?

Yes, to make sure the car was locked.

It is solved - you just have to refresh your car in the I smart app once. After that it works. Don't ask me why please^^

yes thanks, also it works here again.
And thanks developers ! for the good work to create this functionality for contact with the EV !

I constantly see in my logging errors from my Tyre pressure. It looks like i have an issue with my sensor. Don't think this has nothing to do with the API. @GamEased, Do you have also messages in the logging, like this?
2024-01-27 19:30:58,208 [  INFO  ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:31:57 CET)" executed successfully - apscheduler.executors.default
2024-01-27 19:31:57,493 [  INFO  ] Running job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" (scheduled at 2024-01-27 19:31:57.485003+01:00) - apscheduler.executors.default
2024-01-27 19:31:57,945 [  INFO  ] 5 messages received - main
2024-01-27 19:31:57,947 [  INFO  ] ID: 21845378, Time: 2024-01-17 15:53:03, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: LSJE24093NG115498 - main
2024-01-27 19:31:57,947 [  INFO  ] ID: 21842441, Time: 2024-01-17 15:17:23, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: LSJE24093NG115498 - main
2024-01-27 19:31:57,948 [  INFO  ] ID: 21839010, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: LSJE24093NG115498 - main
2024-01-27 19:31:57,949 [  INFO  ] ID: 21839009, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: LSJE24093NG115498 - main
2024-01-27 19:31:57,949 [  INFO  ] ID: 21008018, Time: 2024-01-09 15:03:46, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (***498) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: LSJE24093NG115498 - main
2024-01-27 19:31:57,950 [  INFO  ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" executed successfully - apscheduler.executors.default

I constantly see in my logging errors from my Tyre pressure. It looks like i have an issue with my sensor. Don't think this has nothing to do with the API. @GamEased, Do you have also messages in the logging, like this? 2024-01-27 19:30:58,208 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:31:57 CET)" executed successfully - apscheduler.executors.default 2024-01-27 19:31:57,493 [ INFO ] Running job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" (scheduled at 2024-01-27 19:31:57.485003+01:00) - apscheduler.executors.default 2024-01-27 19:31:57,945 [ INFO ] 5 messages received - main 2024-01-27 19:31:57,947 [ INFO ] ID: 21845378, Time: 2024-01-17 15:53:03, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXX - main 2024-01-27 19:31:57,947 [ INFO ] ID: 21842441, Time: 2024-01-17 15:17:23, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXX - main 2024-01-27 19:31:57,948 [ INFO ] ID: 21839010, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXX - main 2024-01-27 19:31:57,949 [ INFO ] ID: 21839009, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (***498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - main 2024-01-27 19:31:57,949 [ INFO ] ID: 21008018, Time: 2024-01-09 15:03:46, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (***498) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - main 2024-01-27 19:31:57,950 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" executed successfully - apscheduler.executors.default

The issue is I have this alarm active right now because of the cold my tire pressure on the tires are often a little  too low until I get going - so I guess I am not able to tell false positives apart, sorry about that.
Just a tip - next time better cover your VIN as this is the identification Number for your car.

@GamEased ok, thanks!

I just checked again because it is a little warmer right now. MG App on my phone says tire pressure is fine.
MQTT Log indeed says as well:
2024-01-27 20:18:00,368 [  INFO  ] ID: 22058415, Time: 2024-01-19 17:56:19, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (***367) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - __main__
So I guess it's some form of bug.


Devc mode: hot change in gradle extension not reflected on server

Use project https://github.com/OpenLiberty/demo-devmode
Run gradle libertyDevc
Modify build.gradle and change liberty.server.var.artifactId = "${rootProject.name}" to liberty.server.var.artifactId = "foo" The container restarts.
In a browser hit http://localhost:9080/ and the usual app demo-devmode-gradle will run instead of the Open Liberty splash screen. Expected app "foo" not to be found.

Are they liberty.server.var properties being monitored for changes?

That property would be in the generated liberty-plugin-config-variable.xml. Is that file copied to the container?


rtl mode must slide from right to left and slide 1 must be in right side

Guidelines for posting a new issue

Please replicate your issue with this CodeSandBox and provide a link to it along with the issue description

if you set  infinite to false in config you can see the problem,
thk

I encountered the same issue, try this package instead: https://github.com/ryangphan/react-slick-pnth . It is also react-slick, but with improved rtl support


shielded-pool(ics20): process truncated addresses in packet data

Describe your changes
This PR makes sure that truncated addresses are encoded correctly when ICS20 withdrawals are marshaled into fungible packet data.
In addition to that, it modifies pcli to (hazardously?) handcraft a return Address with an identity clue key and zero diversifier.
To test this PR, one can performa IBC roundtrip against a testnet chain with broken bech32m handling (e.g, grand-1).
Issue ticket number and link
#4950
Checklist before requesting a review

[x] I have added guiding text to explain how a reviewer should test these changes.

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

CB release branch.

Why can't the pcli command just use the`FullViewingKey::transparent_address()" method to create the address?

Good idea!


Difference between using a persistent storage like S3 vs Using a Vector DB to store data in LLAMA INDEX[Question]:

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
What is the difference between using a persistent storage like S3 vs Using a Vector DB to store data in LLAMA INDEX?
In either cases I'm loading the index from a persistent storage and running a query on top of it.
Using S3 or Local disk storage :
load documents
documents = SimpleDirectoryReader("./data/paul_graham/").load_data()
index = VectorStoreIndex.from_documents(documents)
save index to disk
index.set_index_id("vector_index")
index.storage_context.persist("./storage")
rebuild storage context
storage_context = StorageContext.from_defaults(persist_dir="storage")
load index
index = load_index_from_storage(storage_context, index_id="vector_index")
Using FAISS or any other Vector Store :
load documents
documents = SimpleDirectoryReader("./data/paul_graham/").load_data()
vector_store = FaissVectorStore(faiss_index=faiss_index)
storage_context = StorageContext.from_defaults(vector_store=vector_store)
index = VectorStoreIndex.from_documents(
documents, storage_context=storage_context
)
save index to disk
index.storage_context.persist()
load index from disk
vector_store = FaissVectorStore.from_persist_dir("./storage")
storage_context = StorageContext.from_defaults(
vector_store=vector_store, persist_dir="./storage"
)
index = load_index_from_storage(storage_context=storage_context)
Trying to understand how will one benefit over the other

@dosu Aren't we using the S3 to store the index which can help for larger datasets?


_has_connection('https://qvisualization.mybluemix.net/', port=443) returns False

Information

Qiskit Terra version: master
Python version: 3.7
Operating system: OSX

What is the current behavior?
Interactive visualizations do not work because _has_connection('https://qvisualization.mybluemix.net/', port=443) is returning False.
Steps to reproduce the problem
Try it.
What is the expected behavior?
Suggested solutions

@filemaster

This is fixed by #1336 I didn't see the bug when I pushed that.


Can't authorize my twitch account

Hi. Does anyone know why when I try verifying my twitch account, it doesn’t even let me press the authorize button? It does nothing, it's just stuck.

I have the same problem. Problems occur in versions 1.5.6 and 1.6.
I think the problem is that we do not have access to tl.com
tl server is down?

Yeah that could be the reason. Anyway, please let me know if you find a way to fix this.

Yeah that could be the reason. Anyway, please let me know if you find a way to fix that.

Just check the closed issues befor posting, please!
#367