Spark2 Client install failed

installed version
odp：<IP_ADDRESS>-50
odp-utils：<IP_ADDRESS>
ambari：<IP_ADDRESS>.0-16
The first question：
The /etc/spark2/conf directory was not generated during the installation process of Spark2 Client ！！！

The second question：
ranger-kms install failed，because ODP should have copied mysql-connector-java.jar to the/usr/odp/current/ranger kms/ews/webapp/lib/directory, but in reality, mysql-connector-java.jar was copied to/usr/odp/current/ranger kms/ews/webapp/lib, and lib became a file instead of a directory

@lucasbak Could you please take a look at the problem? Thank you.

@lucasbak Solutions to two problems

The solution to the first problem：
mkdir -p /etc/spark2/conf

The solution to the second problem：
mv /usr/odp/current/ranger-kms/ews/webapp/lib /usr/odp/current/ranger-kms/ews/webapp/lib_bak
mkdir /usr/odp/current/ranger-kms/ews/webapp/lib

Will you iterate these two issues into subsequent versions？

Hi @SGITLOGIN,
Thanks for the report, we also identified ranger-tagsync problem with postgresql connector.
Indeed the tree directory for connector should not contain webapp.
Will reproduce internally.
Best regards

@lucasbak Solutions to two problems

The solution to the first problem：
mkdir -p /etc/spark2/conf

The solution to the second problem：
mv /usr/odp/current/ranger-kms/ews/webapp/lib /usr/odp/current/ranger-kms/ews/webapp/lib_bak
mkdir /usr/odp/current/ranger-kms/ews/webapp/lib

Will you iterate these two issues into subsequent versions？

@SGITLOGIN ,
Yes, we will add also the fix for ranger-tagsync.

@SGITLOGIN
on which Operating system do you install the packages ?

CentOS 7.9

@SGITLOGIN
We will try to reproduce on centos 7.9

Okay, thank you very much

@lucasbak Could you please also install the Ranger KMS component when installing the cluster? My installation of the Ranger KMS component has also failed

@lucasbak
Phoenix Query Server startup failed！！！
Report no file error: /usr/odp/current/phoenix-server/bin/queryserver.py

@lucasbak
Atlas startup failed，Work hard to analyze the problem.

@lucasbak
I feel that ODP version <IP_ADDRESS>-50 has a lot of problems

@lucasbak
odp：<IP_ADDRESS>-50
odp-utils：<IP_ADDRESS>
ambari：<IP_ADDRESS>.0-16

@SGITLOGIN
Alright, will reproduce your installation and keep you up to date
Best regards

@lucasbak
There is another question. The installed odp version is <IP_ADDRESS>-50, but there is also a <IP_ADDRESS>-53 directory under the /usr/odp/ directory. Is this normal?

@SGITLOGIN.
This is not normal. Did you not mixed up your repository files ?
check in /etc/yum.repos.d/ files

@lucasbak
no，I suspect it was entered when installing the installation package.

@lucasbak
I installed it using Local repository.

We are currently deploying a new cluster
We will reproduce your install from the WebUI.
no worries ;-)

OK

@lucasbak
The Spark2 Thrift Server service started successfully, but after a while, it showed that the service was in a failed state.

Do you require spark2 instead of Spark3 ?

yes，The spark version currently used by our spark program code is 2.*

@SGITLOGIN ,
In your services you have TEZ but not Hive ?

@lucasbak

I tested Spark3 and there was no problem.
There is a problem with Spark2 thrift server service
我安装了tez和hive

@lucasbak Here are all the components I installed. When you install the cluster, all of the following components are installed.
Choose File System
HDFS
Choose Services
YARN + MapReduce2 Hive Tez Atlas Kafka Hbase Ranger Infra Solr Ranger KMS ZooKeeper Ambari Metrics Spark2 Zeppelin Notebook Flink

@SGITLOGIN
OK. Do you use mysql/mariadb for all services backend ?

@lucasbak
yes，mysql

Ok.
Currently reproducing every error internally and fix it. It may take time as we may need to rebuild RPMs

Ok

@SGITLOGIN

We have successfully reproduced and found solution for ranger-tagsync not installing/starting
We have successfully reproduced and found solution for ranger-kms starting
We have successfully reproduced and found solution for spark2-client install
We have successfully reproduced and found solution for atlas metadata server not starting
We have successfully reproduced and found solution for Phoenix Queryserver not starting

the new version for both ambari and odp stack should be ready next days
Thanks for your support :)

Ok，I have one more request.

After solving the above problems, please try to turn on kerberos in the cluster to see if there is any problem, because our company needs to turn on kerberos authentication, so thank you.

@lucasbak

@lucasbak
The yarn application log cannot be viewed and the error is as follows: "Logs are unavailable because Application Timeline Service seems unhealthy and could not connect to the JobHistory server."，Please analyze this issue too.

@lucasbak
Hi，spark3-shell execution error：Error: Missing application resource.
You said "It's a identified bug fixed in later version of ODP 1.2. Spark-shell is not rightly rendered"，Has this issue not been fixed yet?

@lucasbak
When the odp version is <IP_ADDRESS>-50, the hadoop-aliyun version is hadoop-aliyun-<IP_ADDRESS>.2.2.0-50.jar
When the odp version is <IP_ADDRESS>-134, the hadoop-aliyun version is hadoop-aliyun-<IP_ADDRESS>.2.1.0-134.jar
Questions are as follows:
When the odp version is <IP_ADDRESS>-134, put hadoop-aliyun-<IP_ADDRESS>.2.1.0-134.jar in the /usr/odp/current/spark3-client/jars directory. There will be no problem when spark accesses oss. .
When the odp version is <IP_ADDRESS>-50, hadoop-aliyun-<IP_ADDRESS>.2.2.0-50.jar is placed in the /usr/odp/current/spark3-client/jars directory, and spark will report an error when accessing oss.

@lucasbak
Hi, the path of the /usr/bin/find-spark-home soft connection should be /usr/odp/current/spark3-client/bin/find-spark-home, not /usr/odp/current/spark3/bin/find-spark-home

@SGITLOGIN ,
All issues taken in count and be shipped in the next build:

path of find-spark-home
spark-shell rendering

For Yarn logs we need to reproduce.
However about the hadoop-aliyun, as it is specific to your cluster, we need to discuss it first internally.  They are normally reserved for Support Customers.
Will keep you up to date when the build will be released :).
Best regards

@lucasbak
Ok，
But regarding the hadoop-aliyun package, I think you should also consider the situation where spark accesses hive tables (the underlying data is stored on oss), so the hadoop-aliyun package you provide should also be equipped with the spark version.

@lucasbak
Will the next version of ODP fix all the problems I mentioned in this issue?
When will the next version of ODP be released?

@SGITLOGIN
Alright. the next version of ODP <IP_ADDRESS> with all issues will be available before end of the week.
Will keep you up to date

@SGITLOGIN ,
For Logs, you can use Yarn ui V1 it will work.

@lucasbak
Sorry，I didn't understand what "Yarn ui V1" is，Can you give an example or take a screenshot？

@SGITLOGIN ,
For Logs, you can use Yarn ui V1 it will work.

@lucasbak
Sorry，I didn't understand what "Yarn ui V1" is，Can you give an example or take a screenshot？

@SGITLOGIN ,
For Logs, you can use Yarn ui V1 it will work.

@lucasbak
OK, thank you

@lucasbak
There are two more questions about HIVE that need to be reproduced here.

The HIVE log level setting is INFO, but when beeline goes to the command line, the log is displayed as DEBUG (new cluster).
HIVE is extremely slow when executing msck repair table or drop table (EXTERNAL Table, only 31 partitions).

@lucasbak
Hiveserver2 and Hivemetastore log levels are also DEBUG

@SGITLOGIN ,
as a workaround, try to create the /etc/hive/conf/logback.xml file with the content at https://github.com/clemlabprojects/ambari/blob/5598b04ff598d115af16c987a1ed3978cd46b7a8/ambari-server/src/main/resources/stacks/ODP/1.0/services/HIVE/package/templates/zookeeper-logback.xml.j2
replace zookeeper_log_level by INFO

@lucasbak
An error is always printed in the hive.out log：java.lang.Exception: null

@SGITLOGIN
can you show me the content of /etc/hive/conf/logback.xml ?
on our cluster we dont have any error

@lucasbak
I tried it and the log level has been changed to INFO.
error should be debug level logs.

@SGITLOGIN ,
as a workaround, try to create the /etc/hive/conf/logback.xml file with the content at https://github.com/clemlabprojects/ambari/blob/5598b04ff598d115af16c987a1ed3978cd46b7a8/ambari-server/src/main/resources/stacks/ODP/1.0/services/HIVE/package/templates/zookeeper-logback.xml.j2
replace zookeeper_log_level by INFO
restart hive service

@SGITLOGIN ,
In the fix, we sync log level on the hive > LOG LEVEL param so it will be done automatically.
It will be part of next ambari build to.
We will release ambari + odp before the en of the week

@lucasbak
Ok，
The problem just mentioned needs you to reproduce it here.
Question：""""HIVE is extremely slow when executing msck repair table or drop table (EXTERNAL Table, only 31 partitions).""""

@SGITLOGIN
Try again generally give being slow is linked to Hive debug level.
Hive is the same version as <IP_ADDRESS>

Try again without debug and keep us updated

How much partition do you have ?

30 partitions

@SGITLOGIN ,
We have just tested with 36 partition.
The INTO TABLE took less than 20 seconds
And the msck repair took 0.5 sec.
Your long response time may du to DEBUG, try to put de logback.xml file in all configuration folders. That's the solution we will provide in next build of Ambari coming before the end of the week.
Best regards

OK

@lucasbak
Hello，The solution to this problem is considered to be solved in the next version

@lucasbak When the odp version is <IP_ADDRESS>-50, the hadoop-aliyun version is hadoop-aliyun-<IP_ADDRESS>.2.2.0-50.jar When the odp version is <IP_ADDRESS>-134, the hadoop-aliyun version is hadoop-aliyun-<IP_ADDRESS>.2.1.0-134.jar
Questions are as follows: When the odp version is <IP_ADDRESS>-134, put hadoop-aliyun-<IP_ADDRESS>.2.1.0-134.jar in the /usr/odp/current/spark3-client/jars directory. There will be no problem when spark accesses oss. . When the odp version is <IP_ADDRESS>-50, hadoop-aliyun-<IP_ADDRESS>.2.2.0-50.jar is placed in the /usr/odp/current/spark3-client/jars directory, and spark will report an error when accessing oss.

@lucasbak
There is another problem. When installing the Zepplin component, the two parameters zeppelin.interpreter.exclude and zeppelin.interpreter.include must be configured to perform subsequent installation steps. However, after these two configuration items are set, the background log reports an error and says that they cannot be used at the same time. the service did not start normally and the page cannot be accessed.

@lucasbak  Hello
Can Spark2 and Spark3 be installed at the same time?
Can Hive's engine be set to spark?
Kerberos can be enabled for a cluster only for a certain component？

Hi @SGITLOGIN ,

Spark2 and Spark3 can not be installed at the same time, however you can install manually the rpm at the same time if you want to use both, you will need to configure one of it manually on the host you want to run the application from.The package creates symlinks between binaries and bin folder so you need to be careful.
For Hive on Spark you can try it but we do not support it. You should use Tez as in Hive 3 it is better optimized.
Kerberos must be enabled  globally and can not be disabled for some component, every service is installed and configured to work with Kerberos, what's the problem with Kerberos ?
For Zeppelin, we did not encoutered the problem, can you just let a blank space for the property ? the solution is to delete the property from configuration file

@lucasbak

After kerberos authentication is turned on, authentication is required to access yarn's 8088 port, but we do not need kerberos authentication for this part, just access it directly.
For Zeppelin, you should also encounter this problem in this version. The solution you mentioned later is to log in to the server and modify the configuration file, right?

Hi @SGITLOGIN
new versions are available :)
it contains all the fixes in this issue, and disable DEBUG mode by default in zookeeper client for HDFS, YARN, HIVE.
ODP：<IP_ADDRESS>-58
ODP-UTILS：<IP_ADDRESS>
AMBARI：<IP_ADDRESS>.0-23
Keep us up to date

OK

Hello,
I tried the lastest version with:
ODP：<IP_ADDRESS>-58
ODP-UTILS：<IP_ADDRESS>
AMBARI：<IP_ADDRESS>.0-23
My POC server is running with Centos 7.9.
I use public repositories.
I saw some bugs.
First one bug is concerning Zookeeper, just after the install zookeeper can't start as the parameter admin.serverPort is not defined and by default it's 8080, the Ambari's port.
After changed it, all is fine.
Second bug is concerning Spark 2, the install and start is ok, excepted for Thrift server.
Last 4096 bytes of prelaunch.err :
/hadoop/yarn/local/usercache/spark/appcache/application_1707514685210_0003/container_e07_1707514685210_0003_01_000001/launch_container.sh: line 37: $PWD:$PWD/spark_conf:$PWD/spark_libs/:$HADOOP_CONF_DIR:/usr/odp/<IP_ADDRESS>-58/hadoop/:/usr/odp/<IP_ADDRESS>-58/hadoop/lib/:/usr/odp/current/hadoop-hdfs-client/:/usr/odp/current/hadoop-hdfs-client/lib/:/usr/odp/current/hadoop-yarn-client/:/usr/odp/current/hadoop-yarn-client/lib/:/usr/odp/current/hadoop-client/share/hadoop/common/lib/:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/lib/:$PWD/mr-framework/hadoop/share/hadoop/common/:$PWD/mr-framework/hadoop/share/hadoop/common/lib/:$PWD/mr-framework/hadoop/share/hadoop/yarn/:$PWD/mr-framework/hadoop/share/hadoop/yarn/lib/:$PWD/mr-framework/hadoop/share/hadoop/hdfs/:$PWD/mr-framework/hadoop/share/hadoop/hdfs/lib/:$PWD/mr-framework/hadoop/share/hadoop/tools/lib/*:/usr/odp/${odp.version}/hadoop/lib/hadoop-lzo-0.6.0.${odp.version}.jar:/etc/hadoop/conf/secure:$PWD/spark_conf/hadoop_conf: bad substitution
I noticed that the variable "${odp.version}" isn't populated correctly.
I looked for the variable in all configurations and changed it to "<IP_ADDRESS>-58".
I saw some paths with "/usr/hdp" too, I don't know if it can be an issue ?
I restarted the Thrift server, but after a while, the Thrift server stops.
Exception in thread "main" java.lang.ClassNotFoundException: java.lang.NoClassDefFoundError: org/apache/hadoop/hive/ql/metadata/HiveException when creating Hive client using classpath: file:/usr/odp/current/spark2-client/standalone-metastore/hive-metastore-<IP_ADDRESS>.2.2.0-58.jar
Please make sure that jars for your version of hive and hadoop are included in the paths passed to spark.sql.hive.metastore.jars.
Is Spark2 Thrift server service work ?
Another problem is with Spark3, I had this error:
Exception in thread "main" org.apache.spark.SparkException: Master must either be yarn or start with spark, mesos, k8s, or local
It appears that the property "spark.master" in "Advanced spark3-thrift-sparkconf" is not setted correctly, by default it's "{{spark_thrift_master}}", I changed it to "yarn" and I restarted the Thrift server.
New error:
24/02/10 08:35:07 ERROR FairSchedulableBuilder: Error while building the fair scheduler pools
java.io.FileNotFoundException: File does not exist: /usr/odp/current/spark3-thriftserver/conf/spark-thrift-fairscheduler.xml
I checked the file and it is there!
Last bug, I tried to install NiFi, but from the start it can't find the package. Is NiFi available ?
I see only this for NiFi:
nifi.noarch : nifi_1_2_2_0_58 Stack Link Virtual Package
nifi-registry.noarch : nifi_1_2_2_0_58-registry Stack Link Virtual Package
nifi-registry_1_2_2_0_58.noarch : Apache NiFi Registry is a complementary
nifi-toolkit.noarch : nifi_1_2_2_0_58-toolkit Stack Link Virtual Package
nifi_1_2_2_0_58-registry.noarch : Apache NiFi Registry is a complementary
nifi_1_2_2_0_58-toolkit.noarch : Apache NiFi is an easy to use, powerful, and
Thank you.

@SGITLOGIN
Did you succeed ?


Do not auto-discard drafts

At present, drafts are automatically discarded after 30 days to prevent them piling up. However, this is no longer needed. We should:

Stop auto-discarding drafts.
Remove this line from the drafts modal:

Drafts older than 30 days are automatically removed.

Remove this line from  /help/view-and-edit-your-message-drafts , and check whether any other documentation is affected.

Drafts are saved for 30 days.

CZO thread

@zulipbot  claim

@zulipbot claim

claim

@zulipbot claim


Pipeline Run Successful But Results not Visible

I ran this tool in my pipeline and have two methods to visualize results however none of them worked.

Published Artifacts:

Using SARIF SAST Scans Tab -- Nothing to see (sc attached)

Connecting Microsoft Defender for Cloud | DevOps security (preview) Azure Repos -- No visibility there as well.

Any suggestions?

Hello @mlaraibkhan, thank you for raising this support issue. Unfortunately, the Scans tab is not owned by Defender for DevOps and is a Microsoft DevLabs product. Our recommendation is to follow up with the Microsoft DevLabs team by providing direct feedback via the Azure DevOps Marketplace here: https://marketplace.visualstudio.com/items?itemName=sariftools.scans&ssr=false#qna

Hi @mlaraibkhan,
Can you also confirm that the msdo.sarif file in your artifacts has any results in it? It may be that you are not seeing any results because the tools did not find any problems in your repositories.

Hey,
I ran the test on a sample repository where I did find some issues, here's the sc, which indicates I have a few findings in msdo.sarif file.

@chrisnielsen-MS I also have the same issue in one of our pipelines, the artifact uploaded includes the correct file but not visible.
If I create a " - task: PublishBuildArtifacts@1" the file is visible in the Scans section.

Thank you for confirming @mlaraibkhan and thank you for the suggestion @cajohanikea -- @mlaraibkhan can you try adding the publish task and see if it shows up for you? If that still doesn't do it, I think following up with the Microsoft DevLabs team via my earlier link will be the best path forward.


keyup and keydown don't exist in typings file

The new keyup and keydown feature are missing in the Option Interface in the typings file, or am I missing something?

??? @JohannesKlauss

You can do something like this:
hotkeys('ctrl+a,alt+a+s', { keyup: true }, (evn, handler) => {
  // ....
});

But the {keyup: boolean} part is nowhere declared inside the declaration file for Typescript.

@JohannesKlauss thx!


Update interface for CSVLedgerEntity add() method

This PR goal is to clarify the returning type of the CSVLedgerEntity add() method.
Previously, the method returned an ID of the first created entry, but it should return the IDs of all created entries.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Flag
Coverage Δ

unittests
83.48% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

pyledger/storage_entity.py
96.41% <100.00%> (ø)


audit whether prerelease or not

[x] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew tests with your changes locally?

Closes https://github.com/Homebrew/brew/issues/7177
Check projects on GitHub whether pre-release or not.

Looks good! Do you have any prereleases you've found that I can use to test this?

Looks good! Do you have any prereleases you've found that I can use to test this?

I audited sysdig
The test was successful. I write the result below.
> brew audit sysdig
sysdig:
  * 0.26.5 is a GitHub prerelease
Error: 1 problem in 1 formula detected

Thanks so much again for your contribution!  You rock, @hyuraku!

Hi.
I am going to revert this change:
https://github.com/Homebrew/brew/pull/7205
It broke brew audit, for example brew audit octant --online fails with Error: Not Found.
This probably needs more testing.

@hyuraku Sorry we had to revert! Would you be able to look at addressing the mentioned issue and reopening a PR with fixes? Even if not: let me know, thanks!

@MikeMcQuaid
I would like to submit another PR about the issue whether GitHub prerelease or not.

Yes, please. Bugs happen, I think if we test it a little bit more before shipping this will be OK.


Add Contacts

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#42  👈
#41
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kanziw and the rest of your teammates on  Graphite

Merge activity

May 4, 2:05 PM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


Adds support for instrumenting the AWS SDK for Java V2

Issue #, if available:
#43
Description of changes:
Adds 2 new artifacts for instrumenting the AWS SDK for Java V2.
The aws-xray-recorder-sdk-aws-sdk-v2 artifact exposes a TracingInterceptor class. An instance of this class can be passed into any AWS SDK V2 service client when it is being built:
DynamoDbAsyncClient client =  DynamoDbAsyncClient.builder()
    .region(Region.US_WEST_2)
    .overrideConfiguration(ClientOverrideConfiguration.builder()
        .addExecutionInterceptor(new TracingInterceptor())
        .build()
    ).build();

The aws-xray-recorder-sdk-aws-sdk-v2-instrumentor artifact allows for easy instrumentation of all AWS SDK V2 service clients. When included as a dependency, the AWS SDK will automatically inject the TracingInterceptor into each service client.
Both artifacts will require version 2.2.0 of the aws-sdk-java artifact in order to run.
I haven't dealt with maven-managed dependencies much. Currently, neither artifact will work unless the AWS SDK V2 is also a dependency of the consuming package. This allows the customer to specify which version of the AWS SDK they wish to use. If testing shows Maven will prefer the version of an artifact that is closest to the root pom.xml (and gradle works similarly) then it might make sense to explicitly depend on the AWS SDK in the new artifacts as well.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

If I use Java SDK v2 only, I got the following error when I try to use  AWSXRayServletFilter
java.lang.NoClassDefFoundError: com/amazonaws/services/xray/model/GetSamplingRulesRequest
	at com.amazonaws.xray.strategy.sampling.pollers.RulePoller.pollRule(RulePoller.java:64)
	at com.amazonaws.xray.strategy.sampling.pollers.RulePoller.lambda$start$0(RulePoller.java:46)

According to dependency tree, the x-ray sdk relies on AWS SDK 1.x version
Can it be used using Java SDK v2 only?
P.S. I see there is a module xray under software.amazon.awssdk, what's its current status?


Issue18

I have implemented undetected-chromedriver.

I have only tested this new changes with etherscan and bscscan , and it was working fine
And It passed all the anti-bot tests on fingerprintjs

Let me know if you see any issue.

@dante11235 as for the errors it seems that it pops up when attempting to parse/scrape a table fails. no idea why it often pops up but seems like it doesn't damage functionality atm.


Discussion: SkoHub Vocabs Index Page

As already being started to discussed in #214 I'm opening the discussion here for the further design and functionality of the index page.
I'm copying over @acka47 arguments

+1 for following the approach in the screenshot of https://github.com/skohub-io/skohub-vocabs/issues/214#issuecomment-1340988196 for now. We should then put some general thought into this and adjust further.

I don't see the need to have the name of the software on such a prominent place like we have now.
It doesn't seem intuitive that the software name links to an overview of vocabularies in the same GitHub repo.

We should invite @kaena83 to the conversation as she has some experience with UX design.

and

One last thought.
Premises:

My general problem is with the list showing vocabularies from one specific GitHub repo. This seems arbitrary but might encourage people to publish all their vocabs from one repo which – from my point of view – should not become best practice.
We want to encourage people to set up their own –institutional or personal – SkoHub Vocabs instances.

I conclude with a question:
Shouldn't the overview page then show all vocabularies published via the specific SkoHub instance, regardless of the git repo they are residing in? (With a possibility to filter the list for organisations with a larger set of vocabs.)

regarding

I don't see the need to have the name of the software on such a prominent place like we have now.
It doesn't seem intuitive that the software name links to an overview of vocabularies in the same GitHub repo.

I totally agree. I think this will be more intuitive if we think of replacing "SkoHub Vocabs" with the name of the institution / project which hosts the vocabularies. With solving #188 and #185 it should be easy to change the name and therefore it will be more intuitive to click on it and get directed to an vocabs overview page.

Shouldn't the overview page then show all vocabularies published via the specific SkoHub instance, regardless of the git repo they are residing in? (With a possibility to filter the list for organisations with a larger set of vocabs.)

That sounds really interesting. Maybe this can also be thought of in context of #185. If the info about vocabularies that should be shown on a index page is given there, we could further list them.
In general I'm more in favor of thinking about what benefits that index page can add to SkoHub Vocabs instead of removing it. I think it is a nice feature to browse different vocabs without having to manually go to a different URL, but to navigate within the application. So this might be in line with your last raised question.

For BARTOC we need a machine-readable list of vocabularies published via a given Skohub instance to integrate data about its vocabularies with information in BARTOC. At the moment we have indexed six vocabularies in BARTOC with their Skohub URL but this data has been collected manually and sure there are more.
Apart from the technical solution this is about documentation. It should be made clear "Skohub" is a software and "SkoHub Vocabs" is just one instance. Maybe the index page could also link to other Skohub instances?


Feature/covid display

This is a mobile web application to check a list of metrics created with React and Redux.
The web app has several pages. One page with a list of items that could be filtered by some parameters like the country name. On another page for the item details, the detail page of the country case breaks down.

Thank you very much


[Question] Why this plugin dependents on plenary?

https://github.com/lewis6991/gitsigns.nvim/blob/6433129ce42257e20e6518a0c73ee7636b5a8b3d/lua/gitsigns.lua#L1-L4
It seems that plenary is overkill for gitsigns.nvim.

Plenary is just a library of lua functions, it's mostly used for plenary/job which is a critical dependency of the plugin. The other stuff is used pretty much because it is available and convenient. plenary/path also contains some useful stuff but it is a little under-developed at the moment so I do some of its functions manually.
Lua itself is simple and has a very lean standard library, nvim extends that a bit (see :help lua), but there are still many standard things that aren't included in which plenary.nvim fills the gap. I don't really see it as overkill, it simply saves me time having to duplicate lots of functions it has already implemented and tested.

Thanks for your explanation. I hope some convenient functions of plenary should be merged into nvim runtime as an official support.
In my option, plenary is unlike a library, it's just a patch.


⚠ CCS has degraded performance

In 44f4fc9, CCS (https://ccs.mitsubishimotorsid-mobileapp.com/v1/health) experienced degraded performance:

HTTP code: 200
Response time: 16118 ms

Resolved: CCS performance has improved in e1322ec after 1 minute.


'Answer Sets' Enhancement Request: Give user option to overwrite existing answer set or save as new

The existing sessions.py, "Answer Sets," feature allows DA users to save a new Answer Set. Good so far. But then when the user goes back to that same Answer Set and makes changes (or not) and wants to update the Answer Set to capture any changed or added data, the existing code saves the existing set as a separate Answer Set with the same title (same metadata: 'title'), resulting in multiple copies of the identical set name saved into the saved_interview_list. This feature enhancement request proposes to do the following:

If the Answer Set already exists (i.e., the same metadata: 'title' already exists in the saved interview list when the user goes to save the Answer Set), provide a radio button question (e.g., "Answer Set {metadata: 'title'} already exists. Would you like to overwrite the existing Answer Set, or else save your current answers as a new Answer Set with a different title?") allowing the user to choose what they'd like to do.

Specifically, the two options would be:

a. Completely overwrite/save over the existing Answer Set (or delete the existing set and then save the current one) with the current answer data;
b. Save the current Answer Set as a new set, and provide the user an area input question to enter the title of the current set, with the default value being the existing Answer Set title appended by a datetime stamp (e.g., "Jones v. Smith [2024-08-12]").
As a final matter, this request proposes to refactor the existing sessions.py and Answer Sets documentation to use separate terminology to more clearly define the "metadata: 'title'" of the Answer Set, and "answer_set_title" is proposed, as it avoids the 'filename' confusion with the "docassemble.AssemblyLine:al_saved_sessions_store.yml" file, which is already aggravated by other arguments and similar concepts like 'sessions,' 'interviews,' 'save_answers' vs. 'save_answer_set', "get_saved_interview_list" vs. "get_saved_answer_set_list," "load_interview_answers" vs. "load_answer_set."
In particular, it may help clear up confusion with four similar-sounding parameters in get_saved_interview_list:
filename_to_exclude (str, optional): The filename to exclude from the results. Defaults to "".
exclude_current_filename (bool, optional): Whether to exclude the current filename from the results. Defaults to True.
exclude_filenames (Optional[List[str]], optional): A list of filenames to exclude from the results. Defaults to None.
exclude_newly_started_sessions (bool, optional): Whether to exclude sessions that are still on "step 1". Defaults to False.

here is GPT-created code that definitely needs to be refactored and harmonized with sessions.py, but might be a helpful starting place.
`import datetime
from typing import Union, Set, List, Optional, Dict, Any
def save_interview_answers(
filename: str = al_session_store_default_filename,
variables_to_filter: Union[Set[str], List[str], None] = None,
metadata: Optional[Dict[str, Any]] = None,
metadata_key_name: str = "metadata",
original_interview_filename: Optional[str] = None,
source_filename: Optional[str] = None,
source_session: Optional[str] = None,
additional_variables_to_filter: Optional[Union[Set[str], List[str]]] = None,
overwrite: bool = False,
custom_title: Optional[str] = None,
) -> str:
"""
Saves or overwrites a session with a specified interview filename.
Args:
    filename (str, optional): The desired filename for the new session. Defaults to `al_session_store_default_filename`.
    variables_to_filter (Union[Set[str], List[str], None], optional): The "base" list or set of variables to filter out. Defaults to `al_sessions_variables_to_remove`.
    metadata (Optional[Dict[str, Any]], optional): Dictionary containing metadata. Defaults to an empty dictionary.
    metadata_key_name (str, optional): Key name for metadata storage. Defaults to "metadata".
    original_interview_filename (str, optional): Original filename of the interview. Defaults to None.
    source_filename (str, optional): Source filename to get session variables from. Defaults to None.
    source_session (str, optional): Session ID of the source file. Defaults to None.
    additional_variables_to_filter (Union[Set[str], List[str], None], optional): List or set of additional variables to filter out. Defaults to None.
    overwrite (bool, optional): Determines if the session should overwrite an existing session. Defaults to False.
    custom_title (Optional[str], optional): Custom title for the session. Defaults to None.

Returns:
    str: ID of the new session.
"""
# Avoid using mutable default parameter
if not variables_to_filter:
    variables_to_filter = al_sessions_variables_to_remove
if not additional_variables_to_filter:
    additional_variables_to_filter = []
if not metadata:
    metadata = {}

# Get session variables, from either the specified or current session
all_vars = get_filtered_session_variables(
    filename=source_filename,
    session_id=source_session,
    variables_to_filter=variables_to_filter,
    additional_variables_to_filter=additional_variables_to_filter,
)

try:
    metadata["steps"] = (
        all_variables(include_internal=True).get("_internal").get("steps", -1)
    )
except:
    metadata["steps"] = -1

if original_interview_filename:
    metadata["original_interview_filename"] = original_interview_filename
else:
    metadata["original_interview_filename"] = all_variables(special="metadata").get(
        "title", user_info().filename.replace(":", " ").replace(".", " ")
    )
metadata["answer_count"] = len(all_vars)

if overwrite:
    existing_sessions = get_saved_interview_list(filename=filename, user_id=user_info().id)
    for session in existing_sessions:
        if session.get("title") == (custom_title or existing_title):
            # Update session with new data
            set_session_variables(filename, session["key"], all_vars, overwrite=True)
            set_interview_metadata(filename, session["key"], metadata, metadata_key_name=metadata_key_name)
            print("Session updated successfully.")
            return session["key"]

# Create a new session
current_datetime = datetime.datetime.now().strftime("%Y-%m-%d %H:%M:%S")
new_title = custom_title or f"{existing_title} ({current_datetime})"
metadata["title"] = new_title

new_session_id = create_session(filename)

# Copy in the variables from the specified session
set_session_variables(filename, new_session_id, all_vars, overwrite=True)

# Add the metadata
set_interview_metadata(
    filename, new_session_id, metadata, metadata_key_name=metadata_key_name
)

# Make the title display as the subtitle on the "My interviews" page
if metadata.get("title"):
    try:
        set_session_variables(
            filename,
            new_session_id,
            {"_internal['subtitle']": metadata.get("title")},
            overwrite=True,
        )
    except:
        log(
            f"Unable to set internal interview subtitle for session {filename}:{new_session_id} with name {metadata.get('title')}"
        )

return new_session_id

Example usage
overwrite_decision = False  # Set to True to overwrite, False to save as a new session
custom_session_title = "Custom Interview Title"  # Optional custom title
save_interview_answers("Sample Interview Title", overwrite=overwrite_decision, custom_title=custom_session_title)
`


Finish TinyRange Benchmarks

Benchmarks

[ ] Network

[ ] Docker
[ ] Podman
[ ] TinyRange

[ ] Disk

[ ] Docker
[ ] Podman
[ ] TinyRange

[ ] CPU

[ ] Docker
[ ] Podman
[ ] TinyRange

[ ] Filesystem Creation

[ ] Docker
[ ] Podman
[ ] TinyRange

[x] Startup Time

[x] Docker
[x] Podman
[x] TinyRange

Hosts

[ ] Linux (Framework)
[ ] Linux (n100)
[ ] Windows (n100)
[ ] MacOS (Macbook Air M1)
[ ] Linux (Raspberry PI)

Wrote benchmarks for a paper under submission.
Will open source code once reviews come back.


Using lightweight charts with non time based bar with subsecond bar sizes

Question
hi - I tried to use lightweight charts with 5 min bars and it works great.
I then tried to use with bars that are not time based. In my case I tried to use it with volume bars where each bar has a volume of 400.
For reference, I'm pasting below the data I'm loading. I've pasted an example that works and an example that does not work.
While doing this, I noticed the following:

I can load non time based data
I think the lowest possible bar timestamp granularity is 1 second. In other words, I think there is a limitation that two bar timestamps cannot happen within the same second. When I try and load this type of data the chart window comes up but it's empty.

I'm trying to get confirmation my understanding is correct regarding the limitation.
And if my understanding is correct, is this a limitation in the TV lib or in the python lib.
Hope this makes sense
Code example
this works fine

,date,open,high,low,close,volume
0,2024-02-13 12:55:08.938028,4962.25,4963.25,4962.25,4962.75,400.0
1,2024-02-13 12:55:10.634011,4962.75,4963.25,4962.75,4963.25,400.0
2,2024-02-13 12:55:11.256009,4963.25,4964.0,4963.25,4964.0,400.0
3,2024-02-13 12:55:12.042010,4964.0,4964.25,4963.75,4963.75,400.0
4,2024-02-13 12:55:13.369017,4963.75,4964.0,4963.25,4963.25,400.0
5,2024-02-13 12:55:14.683019,4963.25,4963.25,4962.75,4963.0,400.0
6,2024-02-13 12:55:15.951015,4963.0,4963.75,4963.0,4963.5,400.0
7,2024-02-13 12:55:17.685001,4963.5,4964.25,4963.25,4964.25,400.0
8,2024-02-13 12:55:18.442006,4964.25,4965.0,4964.0,4965.0,400.0
9,2024-02-13 12:55:19.794010,4965.0,4965.25,4965.0,4965.0,400.0

this does not work (notice the first 2 lines start have a 08 seconds timestamp)

,date,open,high,low,close,volume
0,2024-02-13 12:55:08.938028,4962.25,4963.25,4962.25,4962.75,400.0
1,2024-02-13 12:55:08.634011,4962.75,4963.25,4962.75,4963.25,400.0
2,2024-02-13 12:55:11.256009,4963.25,4964.0,4963.25,4964.0,400.0
3,2024-02-13 12:55:12.042010,4964.0,4964.25,4963.75,4963.75,400.0
4,2024-02-13 12:55:13.369017,4963.75,4964.0,4963.25,4963.25,400.0
5,2024-02-13 12:55:14.683019,4963.25,4963.25,4962.75,4963.0,400.0
6,2024-02-13 12:55:15.951015,4963.0,4963.75,4963.0,4963.5,400.0
7,2024-02-13 12:55:17.685001,4963.5,4964.25,4963.25,4964.25,400.0
8,2024-02-13 12:55:18.442006,4964.25,4965.0,4964.0,4965.0,400.0
9,2024-02-13 12:55:19.794010,4965.0,4965.25,4965.0,4965.0,400.0

Awesome @pranavladkat  ! Thanks for the note and snippet, I'll check it out


check if strike user exists when user edits profile

fixed with https://github.com/neb-b/dono.at/commit/4eb5207d3b65fc5444b2429db13dfd8d5e6f79b2


"No framework found Gzip"

While manually integration getting linker command failed with exit code 1 (use -v to see invocation) "no framework found issue"
and on pod integration while import Gzip getting "No such module Gzip" issue.

I had this problem as well. You have to tell the app to build. After that the error went away. The framework has a problem somewhere in that it is not built yet.

You need to import GzipSwift I think.

I have the same problem, but I can't install it with pod

This issue was closed because it has been inactive for years since the last update and may be outdated. CocoaPods is no more supported for GzipSwift.


Refused to display in a frame because it set 'X-Frame-Options' to 'deny'

Describe the bug
Hello guys,
I get the following error in the chrome console when trying to connect to wetty:

Refused to display 'https://pfcloud.ddns.net:8080/' in a frame because it set 'X-Frame-Options' to 'deny'

I already got it to work when accessing it directly. However I need to run it as a reverse proxy with nginx.
I followed this guide you published: https://github.com/butlerx/wetty/blob/main/docs/nginx.md.
Additionally I also have this line in my nginx config, however I dont really know if it has something to do with the error:
        add_header Access-Control-Allow-Origin *;
To Reproduce
Steps to reproduce the behavior:

Go to https://pfcloud.ddns.net:8080/wetty and you should get get same error.
You will also get notified that this is a dangerous site. This is I think a side effect of the error as this didn´t occur when I accessed it directly and not through the reverse proxy.
Open the console and you should see the exact same error and some others in the console.

Expected behavior
Well my expectation was that it would work exactly as it does when not routing it through a reverse proxy.

After a bit more research I found a solution on this website:
https://devanswe.rs/nginx-problem-refused-to-display-url-in-a-frame-because-it-set-x-frame-options-to-deny/
Maybe this should be added as a possible error to the reverse proxy guide.

I eventually got it to work with this article.
Maybe this should be added to the nginx reverse proxy guide as a possible fix.


Yingjianw/additional safety rollout

First commit:

Add a flag to controll the rollout in case there are any performance degradation or bug for each api call (create, rename, drop, get) that can touch the parent child relation service. This flag can also be used in the long run if we see performance degradation as we have more parent child relationship created and we can quickly block certain actions.
Add a validation to make sure the parent name specified in the request actually exists in metacat
One bug fix on the rename side even though we are going to rewrite to use two phase commit idea in this pr https://github.com/Netflix/metacat/pull/600, which already handled this case. I have also added this case in our e2e test

More specifically the bug is:

Supposed that we have childName = 'c' and parentName = 'p', and let's ignore uuid and clone type for example.
Then we insert a new parent child relationship childName = 'nc' and parentName = 'p'
So for now we have two records:

'c' | 'p'

'nc' | 'p'

Then we rename 'c' to 'nc' because we always rename in parent child relationship first, and after the rename, the db will look something like

'nc' | 'p'

'nc' | 'p'

But it will fail later in the tableProxy as table 'nc' already and then if we revert back it will make all 2 records as 'c' | 'p'

Second commit

Add a validation during createTable to prevent creating a new record having the same name in the existing mysql db but uuid is different from that of the exiting one.

Third commit

Add a search endpoint for getParentsApi in case we need to block the get api and we can still have way to debug

Forth commit

Move out other parent child config out to keep all validation logic in the same place and also the config is general enough and doesn't need to be netflix specific

Fifth commit
Make all the flags to false by default

Thanks all, I will address the comments in the next PR.


Using with public_activity gem

I am using https://github.com/pokonski/public_activity on a number of models that I am protecting with acts_as_paranoid.  Right now when an associated record that is tracked is destroyed, it cannot be viewed in rendered activities because the polymorphic association checks for records that are not deleted, which is standard behavior with the gem.  I would like, however, to be able to override this behavior so that deleted records are included in the association.
I tried something like this:
class IdeaHistory < ActiveRecord::Base
    include PublicActivity::Renderable

    self.table_name = PublicActivity.config.table_name

    acts_as_paranoid

    # Define polymorphic association to the parent
    belongs_to :trackable, :polymorphic => true
    # Define ownership to a resource responsible for this activity
    belongs_to :owner, :polymorphic => true
    # Define ownership to a resource targeted by this activity
    belongs_to :recipient, :polymorphic => true, with_deleted: true
    belongs_to :recipient_including_deleted, :class_name => "Idea", :foreign_key => 'recipient_id', :with_deleted => true
    # Serialize parameters Hash
    serialize :parameters, Hash

    if ::ActiveRecord::VERSION::MAJOR < 4 || defined?(ProtectedAttributes)
      attr_accessible :key, :owner, :parameters, :recipient, :trackable
    end
end

where I hard coded the recipient to be one of my models but it did not work.  Do you have any idea how I can get public_activity and acts_as_paranoid to work well together?

So it seems there is a workaround for this issue ( chaps-io/public_activity#186 ), and I'm not sure there's anything we can do about it here.. so close.

The issue you reference @zzak is not a working work-around. Closed prematurely.

The issue you reference @zzak is not a working work-around. Closed prematurely.


[BAT] Drone

Coverage decreased (-3.8%) to 50.775% when pulling 60f50d61195cfffbcc6d0e55cef1f48ad2a515ac on wy65701436:drone into a90bef7de7e09fcef8dae80e1d0b95552575069a on vmware:drone.


Drop unused packages

Review packages and try to identify unused ones and remove them. Some examples:

google-measurement-protocol for Google Analytics - it should be removed from Saleor as it's been deprecated for a long time
django-versatileimagefield - it's not used in logic anymore, but it's still referred to in migrations. We should look into how it can be removed.
django-prices-openexchangerates

it's not usable in cloud so we can drop the package
drop to_local_currency function
mark all *localCurrency fields as deprecated and make them always return null (they're nullable already)

Added django-prices-openexchangerates to the list.

Added django-prices-vatlayer.


silero-vad v5

we must use v4 version of Silero because the latest one, v5,  changed the interface.  PR #115 was a hotfix.
This summarizes the benefits of v5 and the change of interface:
https://github.com/snakers4/silero-vad/issues/2#issuecomment-2195433115

so let's see if it works


✨(metabase) add maps data and notebook

Add maps for metropole and regions (level: department, epci, city) and creation notebook.

To take 'mixed EPCI' into account, DISTINCT is removed from requests and replaced by drop_duplicates for each region.


Strange model binding

$router->bind('profile', function ($user_name = null) {
    if(!$user_name)
    {
        $user_name = Auth::user()->user_name;
    }
    $user = \App\Models\User::where('user_name', $user_name)->first();
    return \ZaWeb\Profile\Models\Profile::where('user_id', $user->id)->first();
});

Controller:
    public function index(Profile $profile)
    {
        dd($profile->toArray());
    }

    public function show(Profile $profile)
    {
        dd($profile->toArray());

    }

Route /profile:
 [ ]
Route /profile/admin:
array:9 [▼
  "id" => "1"
  "phone" => null
  "user_id" => "1"
  "city_id" => "1"
  "vkcom" => null
  "attachment_id" => "1"
  "about" => "Site admin"
]

How can I fix this?

Ask on the forums. Also, you're code sample is incomplete

I think it's a bug of the framework. because this bind is not called if no url parameter user_name, although user_name = null

May this be another bug report about session data not being available in route bindings?

No, i'm tried to set default value $user_name = 'admin' and it's  not working


CI: also run GAMS on main and show in summary

A follow up to #94 : now that main also supports outputting DD files, make CI run GAMS on main output and compare the results in the summary table:
    Benchmark    Time (s)                  DD Diff     Accuracy      Correct    Additional
-------------  ----------  -----------------------  -----------  -----------  ------------
DemoS_001-all   3.1   3.1            OK         OK  100.0 100.0   119    119      0      0
DemoS_002-all   3.4   4.0      Diff (7)   Diff (7)  100.0 100.0   345    345      0      0
DemoS_007-all   6.4   7.1  Error runn… Error runn…   79.6  79.6  1772   1772     14     14

I haven't yet included a regression test that will fail if the diff is worse in the PR compared to main, because as discussed I'm not sure how accurate our method of counting number of lines in gdxdiff output is. But at least we can look at the table and get a visual indicator if things get much worse.

Great, thanks @siddharth-krishna ! Could you also rename dd diff gdx diff in the summary table?


feat: add support for ingress TLS and ingressClass

Hello!
First of all thanks for publishing your charts!
I would like to contribute and add support for TLS and ingressClass for the Ara ingress resource.
The structure changed a bit but defaults remain the same. Let me know if you have any question.
Fred

lgtm!
Can you bump the Chart Version to 0.2.0, then i'll merge.
thx for contributing!

Hi @Nold360, thx for the feedback. I've just updated the version as requested.


Generate RBAC based on the current config

Generate RBAC based on the current config, and in such a way that the code can be shared with the backend.

More context on this one.
At

I've been working a little with Wenlin on this today and my plan was, if there was more time, to build this incrementally with TDD in stages, e.g.

GVRs in, RBAC string templated out
GVRs in, RBAC structs out
GVRs and Namespaces in, scoped rbac generated based on some list of known namespaces in the case of excluded namespaces
means of getting GVRs from loaded dynamic data gatherers.
adding a command to spit this all out.

You are correct, I was imagining that it'd be possible to supply a list of namespaces that comes from kubectl get ns if the agent were running locally using the installers credentials.
I'm thinking that the first use of this is going to be a command in the agent, and if the agent, running in that command had access to the installers creds, it could get a list of all namespaces.
We might not be able to do this when using it from the platform side, however I think it's a feature worth adding here in the agent.


Check that cdm$condition_occurrence has condition_end_date

I noticed while working with other ddbb that some have cohort_end_date = NA, and the function was outputting empty tables. You could check that and do cohort_end_date = cohort_start_date in that case, the function then works fine.

@catalamarti @MimiYuchenGuo

so my point would be to add something like this:
condition_occurrence <- cdm$condition_occurrence %>%
  dplyr::mutate(condition_end_date = dplyr::if_else(is.na(.data$condition_end_date), .data$condition_start_date, .data$condition_end_date))

But is in the scope of this package?
@edward-burn @KimLopezGuell @MimiYuchenGuo
If we do that we should apply to other tables too


docs(rabbitmq): motivation for introduction of rabbitmq

There has been much discussion of message queues within Renku and it was decided that RabbitMQ should be used as the messaging solution. However, little was recorded regarding the specific motivation for introducing this component and the choice of which messaging solution to use.
This PR captures some of that discussion, albeit significantly disconnected from many of the discussions which took place on this topic, both in time and space.

probably need to change the folder to something other than 010, gateway refactor is already 010

@Panaetius I believe we can close this - with existing implementation of Redis streams it isn't necessary anymore?


feat(coverage): add coverage['100'] to istanbul provider

Description

Add support for passing 100: true for @vitest/coverage-istanbul
Close #3566

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[x] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[x] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

@AriPerkkio one of the tests timed out. Can you rerun it ?
Thanks.


[W-13520872] add API Experience Hub icon

ref: W-13520872
add an icon for API Experience Hub. Validate via local build.

@cheungaryk looks like there is a merge conflicts here.

@agansop fixed. Sorry about that


SIGNATURE VERIFICATION FAILED

Error Code:
110775B5D101FB36BC6C911BEB774491D9FF06E2: Key expired

In the morning I ran into the same problem, I solved it this way:
gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pgp.mit.edu

@Vertical-Card
I already reported this key expiration issue to upstream, and they're fixing it.

https://gitlab.torproject.org/tpo/tpa/team/-/issues/40299

gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pgp.mit.edu

actually it's recommend to use command below as workaround now:
gpg --homedir ~/.local/share/torbrowser/gnupg_homedir --keyserver hkps://keys.openpgp.org --refresh-keys 0x4E2C6E8793298290

How to workaround with this command?

Fixed in torbrowser-launcher 0.3.4


recursive loop detected in template string: {{mysql_root_password}}

this line causes an infinite loop while running the playbook
mysql_root_password: "{{mysql_root_password}}"

because inside the "all" file, the variable name is also mysql_root_password
I got around it by renaming the variable to custom_mysql_root_password

Thanks for the feedback @vesper8 . Good catch. Would you mind doing a pull request for this?

@vesper8 did not get any feedback so closing this thread.


libhdhomerun: 20220303 -> 20231020

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20221205 in filename of file in /nix/store/nc35b6lfcm8pjwv7wjh0j8wk8rbs6chy-libhdhomerun-20221205

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nc35b6lfcm8pjwv7wjh0j8wk8rbs6chy-libhdhomerun-20221205 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/56dbf4817d2015830223ab1a1a99a961a691b927.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nc35b6lfcm8pjwv7wjh0j8wk8rbs6chy-libhdhomerun-20221205
ls -la /nix/store/nc35b6lfcm8pjwv7wjh0j8wk8rbs6chy-libhdhomerun-20221205/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20230303 in filename of file in /nix/store/qrq67yf98q6gyjyc8mxcjvz6sr1wxrv1-libhdhomerun-20230303

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qrq67yf98q6gyjyc8mxcjvz6sr1wxrv1-libhdhomerun-20230303 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/c2ad4d88a1d586b980809cbcb19700328964d16a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qrq67yf98q6gyjyc8mxcjvz6sr1wxrv1-libhdhomerun-20230303
ls -la /nix/store/qrq67yf98q6gyjyc8mxcjvz6sr1wxrv1-libhdhomerun-20230303/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20230323 in filename of file in /nix/store/wvk429cqxvnjqvv1ggsr6x2pl5sab7j3-libhdhomerun-20230323

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wvk429cqxvnjqvv1ggsr6x2pl5sab7j3-libhdhomerun-20230323 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/35f94f057d92c1efd3fe17d0ca760ddeeada73af.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wvk429cqxvnjqvv1ggsr6x2pl5sab7j3-libhdhomerun-20230323
ls -la /nix/store/wvk429cqxvnjqvv1ggsr6x2pl5sab7j3-libhdhomerun-20230323/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20230505 in filename of file in /nix/store/9hmycz3zhj7q0rfnacfv4q76r37ys1zb-libhdhomerun-20230505

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9hmycz3zhj7q0rfnacfv4q76r37ys1zb-libhdhomerun-20230505 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/72504784217aa2a843c398ed1bdbeb132f729f6a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9hmycz3zhj7q0rfnacfv4q76r37ys1zb-libhdhomerun-20230505
ls -la /nix/store/9hmycz3zhj7q0rfnacfv4q76r37ys1zb-libhdhomerun-20230505/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20230719 in filename of file in /nix/store/8444b3gspwzzf1gf6pnsk126b8fsqk7h-libhdhomerun-20230719

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8444b3gspwzzf1gf6pnsk126b8fsqk7h-libhdhomerun-20230719 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/addc70859234a077589cbe4858991fe328ea9bc2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8444b3gspwzzf1gf6pnsk126b8fsqk7h-libhdhomerun-20230719
ls -la /nix/store/8444b3gspwzzf1gf6pnsk126b8fsqk7h-libhdhomerun-20230719/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20231020 in filename of file in /nix/store/78wm0b218dncq79p5hrp3hwqjp639id7-libhdhomerun-20231020

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/78wm0b218dncq79p5hrp3hwqjp639id7-libhdhomerun-20231020 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/45bdbc442208b88049fa18173d865d3fc818fd9d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/45bdbc442208b88049fa18173d865d3fc818fd9d#libhdhomerun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/78wm0b218dncq79p5hrp3hwqjp639id7-libhdhomerun-20231020
ls -la /nix/store/78wm0b218dncq79p5hrp3hwqjp639id7-libhdhomerun-20231020/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20231109 in filename of file in /nix/store/khqafzl7nmg3z5g45ivk9rc59ljqkyhk-libhdhomerun-20231109

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/khqafzl7nmg3z5g45ivk9rc59ljqkyhk-libhdhomerun-20231109 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/639e43d31c4557e96a8f8d8de9d4fdc45219f1a1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/639e43d31c4557e96a8f8d8de9d4fdc45219f1a1#libhdhomerun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/khqafzl7nmg3z5g45ivk9rc59ljqkyhk-libhdhomerun-20231109
ls -la /nix/store/khqafzl7nmg3z5g45ivk9rc59ljqkyhk-libhdhomerun-20231109/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libhdhomerun/versions.
meta.description for libhdhomerun is: Implements the libhdhomerun protocol for use with Silicondust HDHomeRun TV tuners
meta.homepage for libhdhomerun is: https://www.silicondust.com/support/linux
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20231214 in filename of file in /nix/store/5x6b0zwms29k2khvjxmzryvq2ba4nrpc-libhdhomerun-20231214

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
hdhomerun-config-gui
kodiPackages.pvr-hdhomerun
libhdhomerun
mythtv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5x6b0zwms29k2khvjxmzryvq2ba4nrpc-libhdhomerun-20231214 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libhdhomerun https://github.com/r-ryantm/nixpkgs/archive/897c2c62fa5daec7fe1336c3f3dd2279288aa56a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/897c2c62fa5daec7fe1336c3f3dd2279288aa56a#libhdhomerun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5x6b0zwms29k2khvjxmzryvq2ba4nrpc-libhdhomerun-20231214
ls -la /nix/store/5x6b0zwms29k2khvjxmzryvq2ba4nrpc-libhdhomerun-20231214/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @titanous for testing.

Looks unmaintained, please open a new PR for more attention...


KOGITO-8783: [SWF Editor] Create empty workflow on code lens

Hello,
Please review this PR which enables user to create empty workflow in a new workflow file by clicking on the code lens.
JIRA: https://issues.redhat.com/browse/KOGITO-8783

@Sara4994 Please update the snapshots because of the naming changes.


fix: incorrect level of envoy-gateway configmap vars

fix: incorrect level of envoy-gateway configmap vars
Signed-off-by: bitliu<EMAIL_ADDRESS>

Codecov Report

Merging #711 (132ba59) into main (7db9a40) will decrease coverage by 0.25%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #711      +/-   ##
==========================================
- Coverage   63.29%   63.03%   -0.26%
==========================================
  Files          47       47
  Lines        5806     5806
==========================================
- Hits         3675     3660      -15
- Misses       1902     1914      +12
- Partials      229      232       +3

Impacted Files
Coverage Δ

internal/envoygateway/config/decoder.go
70.00% <50.00%> (ø)

internal/provider/kubernetes/gatewayclass.go
71.73% <0.00%> (-3.63%)
:arrow_down:

internal/provider/kubernetes/gateway.go
48.18% <0.00%> (-3.42%)
:arrow_down:

internal/provider/kubernetes/tlsroute.go
62.11% <0.00%> (+2.64%)
:arrow_up:

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


[improvement] Implement "IPv6 Unavaliable" Error Code

This is an issue attempting to solve a real-world issue that I have encountered lately. The problem is described as follows:

To enable the ECH feature of browsers, one have to enable the built-in browser DoH resolver. But this will cause proxy clients to unable to sniff and hijack DNS requests as usual.
If TUN inbound is enabled and an IPv6 address is add to the TUN interface, even if the remote proxy server does not support IPv6, the browser will still attempt to send request to the resolved IPv6 address and will fail.
Under existing protocols, there is no way for the server to tell its clients that either it does not support IPv6 or an IPv6 request fails, thus browser's Happy Eyeball fallback cannot be triggered (by proxy client returning an ICMP unreadable response on TUN), causing connection failure.

To address this issue, I propose that an error code representing "IPv6 connection failure" to be added, so that proxy clients can properly trigger Happy Eyeballs when TUN inbound is used.
edit: context: https://github.com/SagerNet/sing-box/issues/932#issuecomment-1739071275

SagerNet/sing-box#932 (comment) is to reveal its impracticability, not to motivate someone to implement it.

This comment is exactly what motivated me to make such proposal, and I have made discussions with nekohasekai and Ian Moore with this. ECH has its value in at least adding an extra layer of safety against Deep Packet Inspection technology, and if this is something that cannot be implemented it will be a great pity.


drivers: sensor: hts221 and lsm6dsl compilation issue when sensor defined in board (I2C) and in test (SPI)

Describe the bug
While pushing PR #27013, Buildkite highlight a compilation issue in hts221 and lsm6dsl.
#27753 already fixes a similar issue with lis2dh (on stm32f3_disco).
Now it merged, and new issue raised up on disco_l475_iot1 with compilation of hts221 and lsm6dsl.
Both sensor are embedded in disco_l475_iot1 baord (on I2C), but ther is conflict with test which define the same sensor on SPI:
-> error: 'DT_N_S_soc_S_i2c40005800_S_lsm6dsl_6a_Pspi_max_frequency
To Reproduce
Steps to reproduce the behavior:

west build -p auto -b disco_l475_iot1 tests/drivers/build_all/ -- -DCONF_FILE=sensors_trigger_i_z.conf
See error

Expected behavior
Compilation successful
Logs and console output
FAILED: zephyr/drivers/sensor/lsm6dsl/CMakeFiles/drivers__sensor__lsm6dsl.dir/lsm6dsl_spi.c.obj
C:\gnuarmemb\bin\arm-none-eabi-gcc.exe -DBUILD_VERSION=v2.4.0-rc1-122-gb3ae394ac314 -DCORE_CM4 -DKERNEL -DSTM32L475xx -DUSE_FULL_LL_DRIVER -DUSE_HAL_DRIVER -D_FORTIFY_SOURCE=2 -D__PROGRAM_START -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I../include -Izephyr/include/generated -I../soc/arm/st_stm32/stm32l4 -I../drivers -I../soc/arm/st_stm32/common -I../subsys/testsuite/include -IC:/zephyr/zephyr_project/modules/hal/cmsis/CMSIS/Core/Include -IC:/zephyr/zephyr_project/modules/hal/st/sensor/stmemsc/iis3dhhc_STdC/driver -IC:/zephyr/zephyr_project/modules/hal/st/sensor/stmemsc/lis2mdl_STdC/driver -IC:/zephyr/zephyr_project/modules/hal/st/sensor/stmemsc/lsm6dso_STdC/driver -IC:/zephyr/zephyr_project/modules/hal/stm32/stm32cube/stm32l4xx/soc -IC:/zephyr/zephyr_project/modules/hal/stm32/stm32cube/stm32l4xx/drivers/include -IC:/zephyr/zephyr_project/modules/hal/stm32/stm32cube/stm32l4xx/drivers/include/Legacy -isystem ../lib/libc/minimal/include -isystem c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/9.2.1/include -isystem c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/9.2.1/include-fixed -Os -imacros C:/zephyr/zephyr_project/zephyr/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mcpu=cortex-m4 -mthumb -mabi=aapcs -imacros C:/zephyr/zephyr_project/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=C:/zephyr/zephyr_project/zephyr/tests/drivers/build_all=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/zephyr/zephyr_project/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/zephyr/zephyr_project=WEST_TOPDIR -ffunction-sections -fdata-sections -std=c99 -nostdinc -MD -MT zephyr/drivers/sensor/lsm6dsl/CMakeFiles/drivers__sensor__lsm6dsl.dir/lsm6dsl_spi.c.obj -MF zephyr\drivers\sensor\lsm6dsl\CMakeFiles\drivers__sensor__lsm6dsl.dir\lsm6dsl_spi.c.obj.d -o zephyr/drivers/sensor/lsm6dsl/CMakeFiles/drivers__sensor__lsm6dsl.dir/lsm6dsl_spi.c.obj   -c C:/zephyr/zephyr_project/zephyr/drivers/sensor/lsm6dsl/lsm6dsl_spi.c
In file included from ../soc/arm/st_stm32/stm32l4/soc.h:30,
from ../include/arch/arm/aarch32/cortex_m/cmsis.h:17,
from ../include/arch/arm/aarch32/syscall.h:29,
from ../include/arch/syscall.h:19,
from ../include/syscall.h:12,
from ../include/kernel_includes.h:36,
from ../include/kernel.h:17,
from ../include/init.h:11,
from ../include/device.h:22,
from ../include/drivers/spi.h:24,
from C:/zephyr/zephyr_project/zephyr/drivers/sensor/lsm6dsl/lsm6dsl_spi.c:13:
zephyr/include/generated/devicetree_unfixed.h:3865:32: error: 'DT_N_S_soc_S_i2c_40005800_S_lsm6dsl_6a_P_spi_max_frequency' undeclared here (not in a function); did you mean 'DT_N_S_soc_S_spi_40003c00_S_ism43362_1_P_spi_max_frequency'?
3865 | #define DT_N_INST_0_st_lsm6dsl DT_N_S_soc_S_i2c_40005800_S_lsm6dsl_6a
|                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../include/devicetree.h:1911:38: note: in definition of macro 'DT_CAT'
1911 | #define DT_CAT(node_id, prop_suffix) node_id##prop_suffix
|                                      ^~~~~~~
../include/devicetree.h:1448:34: note: in expansion of macro 'DT_PROP'
1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)
|                                  ^~~~~~~
../include/sys/util_internal.h:106:36: note: in expansion of macro 'DT_N_INST_0_st_lsm6dsl'
106 | #define UTIL_PRIMITIVE_CAT(a, ...) a##VA_ARGS
|                                    ^
../include/sys/util_internal.h:105:26: note: in expansion of macro 'UTIL_PRIMITIVE_CAT'
105 | #define UTIL_CAT(a, ...) UTIL_PRIMITIVE_CAT(a, VA_ARGS)
|                          ^~~~~~~~~~~~~~~~~~
../include/devicetree.h:297:31: note: in expansion of macro 'UTIL_CAT'
297 | #define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))
|                               ^~~~~~~~
../include/devicetree.h:1426:27: note: in expansion of macro 'DT_INST'
1426 | #define DT_DRV_INST(inst) DT_INST(inst, DT_DRV_COMPAT)
|                           ^~~~~~~
../include/devicetree.h:1448:42: note: in expansion of macro 'DT_DRV_INST'
1448 | #define DT_INST_PROP(inst, prop) DT_PROP(DT_DRV_INST(inst), prop)
|                                          ^~~~~~~~~~~
C:/zephyr/zephyr_project/zephyr/drivers/sensor/lsm6dsl/lsm6dsl_spi.c:30:15: note: in expansion of macro 'DT_INST_PROP'
30 |  .frequency = DT_INST_PROP(0, spi_max_frequency),
|               ^~~~~~~~~~~~
Environment (please complete the following information):

OS:  Linux and Windows
Toolchain Zephyr SDK
Commit SHA: 6c53e9331854a3485112685c47b77852f3576224

OK, I'm scheduling it for the next jira sprint (our internal sprint).
Thanks for reporting it!

@ABOSTM
It seems to me that this bug is only related to lsm6dsl, isn't it?

@avisconti ,
Looking at buildkite details of #27013, there is also an error for hts221.
I didn't look carefully the 1st time, and I think error was the same than lis2dh and lsm6dsl.
But in fact error is different for hts221. I submitted a new issue #28443
And I updated the title and description of this issue.


Fixes #2: Create CONTRIBUTING.md

Fixes #2

writing Persian in the online editor is hard, I had to make the commits dirty.
Please squash to not mess with the commit history.

Thank you!

No problem, glad it has been merged
On Apr 14, 2018 19:38, "Sajjad Hashemian"<EMAIL_ADDRESS>wrote:
Thank you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sijad/flarum-ext-persian/pull/4#issuecomment-381342062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkFCek17bvcHMUwkW5FPwQoQTTt1FHLks5toiYUgaJpZM4TVHMe
.


Validation is slow

I did some profiling and found a very simple speed improvement. I'll send a pull request.

Fixed in 268a9e1


[MM-28256] Cypress/E2E: Automate backlogs - Slash Commands > Statuses (4 test cases)

Summary
E2E testing for https://mattermost.atlassian.net/browse/MM-28256
Ticket Link
https://mattermost.atlassian.net/browse/MM-28256

/update-branch

@jfrerich is there any further change needed here to address the changes mentioned by Saturn above?

@jfrerich is there any further change needed here to address the changes mentioned by Saturn above?

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Heads up that as part of our efforts to move to a monorepo, we're closing out a number of older pull requests like this one to help streamline the effort.
If you'd like to preserve these changes -- even if you're not the original author! -- feel free to resubmit the pull request against the monorepo once it's ready. You can subscribe to https://github.com/mattermost/mattermost-server/issues/22420 for status updates on this effort.


Rest Updates

Knocking off a few easy issues to start.

[Current coverage][cc-pull] is 65.70%

Merging [#76][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.84%

@@             master        #76   diff @@
==========================================
  Files            14         14
  Lines           559        589    +30
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            372        387    +15
- Misses          140        153    +13
- Partials         47         49     +2

Powered by Codecov. Last updated by [21d0886...53ea5bf][cc-compare]
[cc-base-branch]: https://codecov.io/gh/snickers/snickers/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/snickers/snickers/compare/21d08866827ef9c0b33e820d876ee8a3a81fccf8...53ea5bf5a5ce80bf8f01c07b48122384780a104e?src=pr
[cc-pull]: https://codecov.io/gh/snickers/snickers/pull/76?src=pr

YES! Thanks @blainsmith!  🍻 🍻


Navbar Improvements on screen

The Nav bar shows a scroll in Mobile view which leads to bad UX.
Propose an effective solution and implement it.

[ ] Remove the scroll
[ ] Implement a solution that works on all screen sizes.

@aayusharora are you talking about the date panel ? if yes we can implement a carousel for this.

Yes @utkarshnath

@aayusharora I think we should use drop-down tabs or we should use tabs vertically instead of horizontally and show the content of each tab in form of list.

@anu-007 That can be one of the solutions but it should be with toggle, so that we can save vertical space in mobile

@aayusharora We can have the days as a bar and make the detailed view invisible, we can toggle the visibility whenever the user clicks any tab.
That would save us the space required and also provide a better UX.

@geekyd That will be fine but make sure we should have no scroll bars anywhere.

@aayusharora Here is the mock-up design of the navbar
Desktop View
**When the page loads for the first time**

When user clicks a navbar link

Mobile View
**When the page loads for the first time**

When user clicks a navbar link

Hey @geekyd Thanks !! Please send the PR. Assigning this to you than :)

Looks Nice :)


[libxml2] Pass version to rc via configured file

What does your PR fix?
This change fixes a build failure on mingw/Windows from issues with quoting/escaping the dotted version string when passing it to the resource compiler.

Which triplets are supported/not supported?

Does the upstream know this bug or fixed it?

There is no upstream bug. The CMakeLists.txt comes from vcpkg. That's why the include was missing.

FTR, upstream creates rcVersion.h here:
https://gitlab.gnome.org/GNOME/libxml2/-/blob/master/win32/configure.js#L283-294


[Testing] Fix stream's leaked goroutines

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
This is a sub-task of https://github.com/apache/skywalking/issues/9454 to fix leaked goroutines in the stream package
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I can finish it, can assign to me ?

Solve pr ref:https://github.com/apache/skywalking-banyandb/pull/214


Minecraft Bedrock server can't set view/max view distance above 32

Bug Report
System Information

Operating System (Including distribution name and version number)

Windows 11 23H2 Pro

AMP version and build date (Always use the version number, 'latest' is not valid!)

v2.4.4, built 17/05/2023 17:54

Which AMP release stream you're using (Mainline, Nightly or FastTrack)

Mainline

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms

What are you trying to do?

Set the view distance and max view distance to 96 (the max for bedrock)

What are you expecting to happen?

To see the server.properties file reflect the setting of 96 (rather than 32)

What is actually happening? ('Nothing' is not an acceptable answer!)

The server.properties file keeps reverting to 32 (I'm guessing a hard coded max due to using the same or similar template to Minecraft Java which I believe has a max view distance of 32). I do see the server.properties file reflect the change when I set to another value under 32 (such as 20) so it is correctly reflecting changes, it just isn't allowing the setting to go above 32. I am able to run this setting at 96 using the server.properties file when launching the bedrock server outside of AMP.

Reproduction
With a fresh Minecraft bedrock server instance in AMP, set the following settings:
-configuration > server settings > view distance to 96
-configuration > Performance and Limits > Max view distance to 96
-In the root game server files, verify server.properties has the value for "view-distance=96"

Configuration -> Limits -> Max View Distance also needs to be raised. This setting controls the limit for the setting in Configuration > Performance and Limits.

Thanks for the reply, but this issue still stands.
I mentioned in my original post that I set BOTH values to 96 and it does not raise the value.


Does not work on a real device

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/effects/touch-tracking
Great sample, but...
This sample is working fine on Android Emulator (Oreo), but does not on a real device. I use Xamarin Live Player and got the following error every time:
[LogEntry: Time=2018-09-27 4:12:26 PM -04:00, Level=Error, Title=Visualization Error, Message=Constructor on type 'InterpretedXamarin.Forms.RoutingEffect' not found. (MissingMethodException)]
Thanks!

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

ID: 908530d1-f21d-5532-c530-1727e3356b64
Version Independent ID: e01f2543-3b7d-0b60-8d79-c012feab83de
Content: Invoking Events from Effects - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/effects/touch-tracking.md
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Closed as a duplicate of #807


All example .ipynb files and code in the tutorial doesn't run

I have downloaded all requirements and tensortrade. When I run any of the example scripts or go through the tutorial, I run into the error that some package is missing or incorrect, e.g. DiscreteActions does not exist and wallet_tuples is not in Portfolio (it was changed to wallets). The list goes on.
To reproduce, download tensortrade, install requirements, try any of the example files or the tutorial.
It's quite difficult to understand how this library works without a single working example.

The project is currently undergoing many changes. The examples and documentations haven't been updated yet. Hopefully some of these issues will be fixed with the upcoming PR merges. For the time being, try finding more help via Discord discussions.


Setup vanilla Tailwind

@raulrpearson what do you think of extending this issue to also update react/next?


polish(nyz): polish atari envpool demo

Description
Related Issue
TODO
Check List

[ ] merge the latest version source branch/repo, and resolve all the conflicts
[ ] pass style check
[ ] pass all the tests

This PR will be updated in #746


fix: display conetent edge to edge

For reference android doc links:
https://developer.android.com/develop/ui/views/layout/edge-to-edge
https://developer.android.com/develop/ui/views/layout/immersive
https://developer.android.com/develop/ui/views/layout/display-cutout


[ENH]need old function!

Why was the original mode of 'generating a macro on the action bar' removed by the plugin? I need to place the GSE macro on the action bar and keep the key usable after paging.

Because Blizzard changed the rules and that method no longer functions.
A macro (on your action bar like you used to do) can no longer /click a GSE Sequence.  THats now called Macro Chaining by Blizzard and the GSE Sequence will cycle but fail silently.  This is all described in https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/wiki/GSE-3.2-and-The-War-Within-‐-Catchup But the situation is what you "need" to do is no longer an option.
The alternative is to KeyBind the GSE Sequence if you want to be able to use it.  This is also covered at https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/wiki/KeyBinding Along with tips for SkyRiding.


Detect DATE_TIME

Description
A Date/Time is a type of PII that can reveal significant personal details such as birth dates, activity timestamps, or historical records.
Detection Steps
A Date/Time typically follows formats like YYYY-MM-DD, DD-MM-YYYY, MM-DD-YYYY, or timestamps such as YYYY-MM-DD HH:MM:SS, and can include variations based on locale or format settings.

Looks good - nice that you included the MM-DD-YYYY format which gets used outside the US quite often

I think you would fall into issues with dates such as 8/5/2024 because there are no zeros before 8 and 5. times would have a similar issue as well. The pattern match technique would have to take into account those things as well.

Looks good, I'm curious if this should also account for a date spelled out, such as 'September 11th,  2024.' Not sure how often you'd run into it though, seems like you have the most common use cases covered.


Fixing a flaky unit test

NetflixOSS » eureka » eureka-pull-requests #302 FAILURE
Looks like there's a problem with this pull request

looks like the build system is having hiccups

NetflixOSS » eureka » eureka-pull-requests #305 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #306 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #324 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #326 FAILURE
Looks like there's a problem with this pull request


Add sample ads.properties file

Change-Id: I3e988d37954ea20c2b4dabdf99dfe4c43d506bde

I would suggest uncommenting the required lines and adding INSERT_ITEM. For example
api.googleads.clientId=INSERT_CLIENT_ID

There's technically no required fields though... anything can be configured in code or config file or both.
I also think that it's more helpful not to put placeholders in here. I don't think anyone would have questions about where to put the details. It just means that people need to remove these before they can use the template.


doc: Render lib.fixedPoints

Description of changes

Render lib.fixedPoints docs in the Nixpkgs manual.
Fix the formatting

Not in scope:

Improvements to the docs; please follow up with a PR.

except for lib.fix because I've done that one; will follow up after merge

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Have reviewed the output diff. This works. Merging so the real improvements can be made.


⚠ sandbox-api.piste.gouv.fr healthcheck has degraded performance

In 4c54558, sandbox-api.piste.gouv.fr healthcheck (https://sandbox-api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2779 ms

Resolved: sandbox-api.piste.gouv.fr healthcheck performance has improved in 6be9b85.


Create notstolencode

just do it else ill rickroll you

https://www.youtube.com/watch?v=6YDoowoYzOI


Added checks for configuration

Strategy type now needs type and factory_id attributes
Segment type now needs type and factory_id attributes

This resolves https://github.com/pheature-flags/pheature-flags/issues/197

👏🏽👏🏽👏🏽

You're welcome :)


Use sample ID on measurements

Include sample ID on the measurements query as discussed with Chris and Sai for their use on the SBH plugin.

Under review by @CarolusVitalis, check dependencies and changes made by the previous merge that may be deleted.


Improved logging

Closes #34.

[1] [09:42:04] ~/r/w/e/frontend-only logging > c run -- serve
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
     Running `/home/cecile/repos/wasmbl/target/debug/frontend-only serve`
[2021-06-01T09:42:17Z INFO  wasmbl] Building frontend package
[2021-06-01T09:42:17Z INFO  wasmbl] Running pre-build hook
    Finished dev [unoptimized + debuginfo] target(s) in 0.09s
[2021-06-01T09:42:17Z WARN  walrus::module] failed to parse `name` custom section Invalid name type (at offset 3267815)
[2021-06-01T09:42:17Z INFO  wasmbl] Running post-build hook
[2021-06-01T09:42:17Z INFO  wasmbl] Development server started: http://<IP_ADDRESS>:3000
[2021-06-01T09:42:17Z INFO  tide::server] Server listening on http://<IP_ADDRESS>:3000

Almost good!

Apparently we get the logs of all crates... so we have the "server listening" twice. We can simply remove ours.

There is a warning about walrus we should fix. I have no idea what it is.

We should consider if we actually want to display the logs of other crates like that. I think it is possible to disable. Maybe it's good to keep. I don't know... this is something to think about.

The "pre-build" log comes after the "build" log but then we see build logs. This makes no sense. Probably they are misplaced.


Refactor usage of exceptions in converters/connectors

These are the existing exceptions right now:

SpeckleException
ConversionNotSupportedException
ConversionException
UnitNotSupportedException
ValidationException

Connectors now use exclusively SpeckleException instead of a mix of that and conversionexceptions.
The only place where ConversionNotSupported is expected is within a RootObjectConverter.
ValidationException is thrown if we can verify the data is wrong BEFORE we can attempt conversion
ConversionException should be used for anything else.
We can expand the types more as we find more use-cases to unify.

Tested in ArcGIS:

[ ] SpeckleException
[X] ConversionNotSupportedException
[X] ConversionException
[X] UnitNotSupportedException
[ ] ValidationException


docs: addition of method documentation

Improves method documentation. (addresses #16)

Signed-off-by: Javier Delgado<EMAIL_ADDRESS>

@hachreak Could you take a look please? :smile:

:+1:

could you add tasks, ext inside docs/api.rst? :)

apart the small issue with tasks, the rest is LGTM.


Issues found when running for the first time on windows

Node libraries became broken due to incorrect pinning of versions.
The default sqlite db that ships with the app doesn't work out of the box.
IdP error screens are unhelpful.
IdP doesn't gracefully handle not understanding sessions between restarts.

IdP has persistent sessions now, point 4 isn't an issue.


/usr/local/opt/python3/bin/python3.6: bad interpreter: No such file or directory

Error as above, however I do have python3.8 and the readme indicates this is supported.
(venv) (base) Robins-MacBook:datasette robin$ ls /usr/local/opt/python3/bin/

.. pip3 python3 python3.8

Topline this fixed the same problem for me.
brew install<EMAIL_ADDRESS>ln -s<EMAIL_ADDRESS>/usr/local/opt/python/bin/python3.7
pip3 uninstall -y numpy
pip3 uninstall -y setuptools
pip3 install setuptools
pip3 install numpy
pip3 install datasette-publish-fly