Consider removing merge tool

The merge conflicts encountered are simple enough to resolve in the GitHub UI without using a merge tool.  It may be worth considering simplifying the activities to resolve the merge conflicts in that way.  This would not diminish the conceptual content of the activities, but would hopefully reduce excess overhead that seems to add confusion.
It is easy to imagine adding additional activities later that would introduce more significant merge conflicts that would benefit from use of a GUI tool.

I would agree with this thought. My experience with students and the merge tool was that some had issues getting it working, and most didn't see the benefit of using them (because the conflicts were simple). It would be useful to introduce the merge tool in an optional (or extra practice) section so they can see the directions but ignore until needed.


Rename the diffutils binary to diff,

in preparation for the future implementation of other binaries (cmp, sdiff and diff3)

what is your plan here? Create new binaries ?
What about doing the same as coreutils ? One main binaries (or individual programs)
and if you do ln -s diffutils diff or ln -s diffutils cmp, it will change the behavior of the command.

I was thinking of individual binaries, but I must admit I didn't look at how it's done for coreutils, and I suppose it makes sense to do something similar. I'll take a look later, in the meantime I'm leaving this PR open.

the main adv is the size of the binaries as Rust bins have a tendency to be bigger than C :)

Closing, as this is definitely being obsoleted by Gustavo's work in #88.


Unable to read meta-data for class org.springframework.ai.autoconfigure.bedrock.llama2.BedrockLlama2AutoConfiguration

Bug description
I'm developing an application that interacts with ChatGPT 3.5 and I'm using this library. Since yesterday the project doesn't start anymore because of this error:
java.lang.IllegalStateException: Unable to read meta-data for class org.springframework.ai.autoconfigure.bedrock.llama2.BedrockLlama2AutoConfiguration

My project configuration didn't change since the last time it used to work.
Environment
I'm using OpenAi 0.8.0-SNAPSHOT with Java SE 17.0.17. Rolling back to OpenAi 0.7.1-SNAPSHOT works fine.
The parent I am using is:
<parent>
	<groupId>org.springframework.boot</groupId>
	<artifactId>spring-boot-starter-parent</artifactId>
	<version>3.2.0</version>
	<relativePath/>
</parent>

The dependencies are:
<dependencies>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-web</artifactId>
	</dependency>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-tomcat</artifactId>
		<scope>provided</scope>
	</dependency>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-test</artifactId>
		<scope>test</scope>
		<exclusions>
			<exclusion>
				<groupId>junit</groupId>
				<artifactId>junit</artifactId>
			</exclusion>
			<exclusion>
				<groupId>org.skyscreamer</groupId>
				<artifactId>jsonassert</artifactId>
			</exclusion>
		</exclusions>
	</dependency>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-devtools</artifactId>
		<scope>runtime</scope>
		<optional>true</optional>
	</dependency>
	<dependency>
		<groupId>org.projectlombok</groupId>
		<artifactId>lombok</artifactId>
		<optional>true</optional>
	</dependency>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-data-mongodb</artifactId>
	</dependency>
	<dependency>
		<groupId>org.apache.httpcomponents</groupId>
		<artifactId>httpclient</artifactId>
		<version>4.3.2</version>
	</dependency>
	<dependency>
		<groupId>org.springframework.security</groupId>
		<artifactId>spring-security-core</artifactId>
		<version>6.2.0</version>
	</dependency>
	<dependency>
		<groupId>org.apache.commons</groupId>
		<artifactId>commons-lang3</artifactId>
	</dependency>
	<dependency>
		<groupId>org.json</groupId>
		<artifactId>json</artifactId>
		<version>20231013</version>
	</dependency>
	<dependency>
		<groupId>org.springdoc</groupId>
		<artifactId>springdoc-openapi-starter-webmvc-ui</artifactId>
		<version>2.3.0</version>
	</dependency>
	<dependency>
		<groupId>org.junit.jupiter</groupId>
		<artifactId>junit-jupiter</artifactId>
		<version>5.9.2</version>
		<scope>test</scope>
	</dependency>
	<dependency>
		<groupId>jakarta.annotation</groupId>
		<artifactId>jakarta.annotation-api</artifactId>
		<version>2.1.1</version>
	</dependency>
	<dependency>
		<groupId>org.springframework.ai</groupId>
		<artifactId>spring-ai-openai-spring-boot-starter</artifactId>
		<version>0.8.0-SNAPSHOT</version>
	</dependency>
            <dependency>
		<groupId>org.springframework</groupId>
		<artifactId>spring-web</artifactId>
	</dependency>
            <dependency>
		<groupId>org.apache.logging.log4j</groupId>
		<artifactId>log4j-api</artifactId>
	</dependency>
</dependencies>

The problem occurs when i try to launch the project using both java -jar and mvn spring-boot:run.
Expected behavior
The project starts properly.

Hi @StefanoDib , thanks for testing and reporting this.
I will check it shortly

@DEG-7 Not sure what you mean? could you pass source reference?

ah, got it. thanks @DEG-7
Indeed the Autoconfiguration.import has wrong definition. Apparently my IDE missed the name refactoring.

@StefanoDib it should be resolved now.
Let me know if other related issues pop-up.

@StefanoDib it should be resolved now. Let me know if other related issues pop-up.

Sadly a new issue popped-up. When performing a mvn clean install, i received this error:
package org.springframework.ai.client does not exists.

Importing OpenAiClient from org.springframework.ai.openai.client solves the problem, but i receive the same error on AiResponse which i can't find somewhere else.
I want to clarify that rolling back to 0.7.1-SNAPSHOT still works fine.
I hope that my bug reportings are helpful!

@StefanoDib it should be resolved now. Let me know if other related issues pop-up.

Sadly a new issue popped-up. When performing a mvn clean install, i received this error:
package org.springframework.ai.client does not exists.

Importing OpenAiClient from org.springframework.ai.openai.client, instead of AiClient, solves the problem, but i receive the same error on AiResponse which i can't find somewhere else. I want to clarify that rolling back to 0.7.1-SNAPSHOT still works fine. I hope that my bug reportings are helpful!

I just noticed that AiClient and AiResponse were renamed to ChatClient and ChatResponse. I quickly changed the references and the projects works fine.


Fix 👏 Google 👏 auth 👏

Steps to reproduce
Sign in with Google. Note that the token does not get stored.
Action items

[x] Try logging in to see if it was a one-off issue on that day
[x] If not, talk with Andre and walk through backend authentication

Working with Andre on this one today. Hopefully will get resolved.

Bug resolved, and SO MUCH MORE was built out for the MVP 💪


Added image classification experimental extension

Should we call this image labeling to keep it consistent with the naming in Firebase ML?

Please add a new line to lerna.json with this extension's path

Thanks. All comments addressed.

@jhuleatt any other concerns with this PR?

I don't have write access to the repo, could someone with write access please merge this PR?


Slider not working properly.

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information

Hey there @nikunjvaghasiya!
Thanks for opening an issue. Could you please edit your initial comment and fill out the issue template so the team can know what the problem is?

Please note that I am not affiliated with the GitHub docs team.

Hey there @nikunjvaghasiya!
Thanks for opening an issue. Could you please edit your initial comment and fill out the issue template so the team can know what the problem is?

Please note that I am not affiliated with the GitHub docs team.

This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!

This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!

Thanks a lot, very nice discusion and sites. Hey
Odesláno z aplikace Poštahttps://go.microsoft.com/fwlink/?LinkId=550986 pro Windows 10
Od<EMAIL_ADDRESS>Odesláno:čtvrtek 28. ledna 2021 20:32
Komu<EMAIL_ADDRESS>Kopie<EMAIL_ADDRESS>Předmět: Re: [github/docs] Slider not working properly. (#3230)
This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussionshttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgithub%2Fdocs%2Fdiscussions&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370859249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Z%2BOqO96se3wmuP20QDnPdsm60HC8dr2a7mvZnpPFZbs%3D&reserved=0!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgithub%2Fdocs%2Fissues%2F3230%23issuecomment-769321451&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370859249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lnAhP5%2FXrfAMfoWjRFIy4IrG2fQyl%2Fmx2uVFUaoanMw%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM4IGEEXZHZJSSAU2NO6NVDS4G3T7ANCNFSM4WVF4GFQ&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370869207|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=PzU%2BRP72cch4dDtfTUyYEAc%2FeHDlU3UHTV9yZPUCo7w%3D&reserved=0.

Thanks a lot, very nice discusion and sites. Hey
Odesláno z aplikace Poštahttps://go.microsoft.com/fwlink/?LinkId=550986 pro Windows 10
Od<EMAIL_ADDRESS>Odesláno:čtvrtek 28. ledna 2021 20:32
Komu<EMAIL_ADDRESS>Kopie<EMAIL_ADDRESS>Předmět: Re: [github/docs] Slider not working properly. (#3230)
This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussionshttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgithub%2Fdocs%2Fdiscussions&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370859249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Z%2BOqO96se3wmuP20QDnPdsm60HC8dr2a7mvZnpPFZbs%3D&reserved=0!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgithub%2Fdocs%2Fissues%2F3230%23issuecomment-769321451&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370859249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lnAhP5%2FXrfAMfoWjRFIy4IrG2fQyl%2Fmx2uVFUaoanMw%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM4IGEEXZHZJSSAU2NO6NVDS4G3T7ANCNFSM4WVF4GFQ&data=04|01||b1fc452adeb1404e08ec08d8c3c36b80|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637474591370869207|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=PzU%2BRP72cch4dDtfTUyYEAc%2FeHDlU3UHTV9yZPUCo7w%3D&reserved=0.


Fixes for #107, #129

Fix for #129

@luben @romix
Hi, could you please take a look at this? Thanks.

+1 both changes look good to me

Thanks @luben
Would it be possible to test the settings for a snapshot version?

I guess only @romix can test if it works as expected

Hi @ajaychandran
We just took over maintenance of the project and are now cleaning up tickets/pull requests. There have been multiple PR's doing the sbt upgrade - we picket #142 and also updated all dependencies... etc.
Could you create a new pr and only address #129 if this is still an issue pls?


Update to Jupyterlab 3.0

Also removes full screen functionality as I was not sure how to get base/js/dialog working and it was breaking the JupyterLab install. Use
jupyter labextension install<EMAIL_ADDRESS>to test.

Gentlest of bumps, anyone? Would love for merge rights to be more spread out too!

John Omernik forked and updated QGrid to Python JupyterLab 3+ and ipywidgets v8.0.
Here is the URL : https://github.com/JohnOmernik/qgrid


Apiv2 template question annotations and question_options

Fixes # .
Changes proposed in this PR:

add "annotations" to the template payload when show_phases=true
add "question_options" to the template payload when show_phases=true

Basically, I need the "example answers" and question options (if non textarea) for a more complete view/payload of the template

The test failures are unrelated and something I need to address. Will get this merged in and included in the upcoming 4.0.1 release


Generators not accepting fuel

Hi, I am on DNS Techpack version 7712, using advanced generators version <IP_ADDRESS>-mc1.7.10. Fuel types in NEI say that they will generate a certain amount in the turbine generator, but I cannot get the generator to fill up with the fuels. I tried connecting BC pipes, mekanism mechanical pipes, and thermal expansion portable tanks to the fluid input valve on both steam turbine generators and gas turbine generators, but I still cannot get the actual fuel to get into the generator. I believe this is because it isn't accepting it, but as I said I looked around in the .jar file and found the config file, and all the fuel types were there. What am I doing wrong?

Can you upload a screenshot of your setup?

Hi, my friend and I actually found the fix to the problem. Apparently the gas generators only accept Buildcraft Fuel (Gasoline). Even if this is not supposed to happen, this was fine by us as we had tons of oil to use. Anyways, great mod, looking towards future builds!


need clarification on Java requirement to use  SourceBuddy

Hi,
I am evaluating to sourcebuddy to dynamically create compile java classes. In our java environment only JRE is available . Please let me know  whether is there any requirement of JDK as well or only JRE is ok to use .
Thanks
Gaurav

Different installations may lack some of the Java features. I cannot tell what your installation supports, but most probably, you will need JDK. I also do not know why it is only JRE in your environment, but one reason may be that the people providing the environment do not want you to use tools like SourceBuddy.

Thanks for your reply. We ship our products to customer with the required
JRE  version only and due to security reasons and size of product
deliverable we can use JRE.as we don't want to use tools.jar available in
jdk ,we are looking some 3rd party libraries where javac is present to
compile generated classes at run time  .
Thanks
GAURAV
On Fri, 29 Dec 2023, 15:31 Peter Verhas, @.***> wrote:

Different installations may lack some of the Java features. I cannot tell
what your installation supports, but most probably, you will need JDK. I
also do not know why it is only JRE in your environment, but one reason may
be that the people providing the environment do not want you to use tools
like SourceBuddy.
—
Reply to this email directly, view it on GitHub
https://github.com/sourcebuddy/sourcebuddy/issues/5#issuecomment-1871896055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4TLPK653XYIE2RC3XPVPLYL2IIVAVCNFSM6AAAAABBFI5BYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRHA4TMMBVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

I've kept this issue open for a while to allow the original reporter to add any necessary comments.


Could not resolve "./api/index. js"

Reproduction
https://github.com/vin-ni/nuxt-pinia-bug
Steps to reproduce the bug

yarn install
yarn dev

Expected behavior
The server spins up and mounts pinia.
Actual behavior
It errors and logs: Could not resolve "./api/index. js"

Additional information
Node Version: 18.13.0
OS: MacOS Ventura
Device: Macbook Pro M1 2020
Not sure where to post this. If it is a vite error or a pinia error.
I already tried @nuxt/pinia 0.4.6, 0.4.5, 0.4.4, 0.4.3, 0.4.2 and node versions 19, 18, 16, 14

You also need to add pinia package: https://pinia.vuejs.org/ssr/nuxt.html#installation

@posva I get the same error if pinia is also installed. Updated the git repo with the pinia package as well.

You can find an example project at https://github.com/piniajs/example-nuxt-3, it should help you set up 😀

I get the same bug in the example project:

I set up the project correctly and it also works on my Intel Mac. But on the M1 it just doesn't work. I think it's really a bug.

Why isn't this considered a bug?

I also use an M1 and I cannot reproduce it so I think it's a configuration issue. That's why I moved your issue to the discussions at #1948 (also please don't open duplicates like that 😅).
Hopefully, someone would help you out with the problem you are facing 😃
Locking this thread to keep the discussion in one place.


Update support Laravel 6.0

It is currently not possible to upgrade from Laravel 5.8 to version 6.0 if this dependency is installed.
When the release is planned a new version that has support for Laravel 6.0?

https://github.com/laravel/framework/releases/tag/v6.0.0

@dlu92, https://github.com/jenssegers/laravel-mongodb/pull/1824 PR in work

@dlu92, support in 3.6.0

@jenssegers You can close this now :)


Braces Rule Adds Unexpected Spacing

The PHP version I'm using ($ php -v):
PHP 7.3.11 (cli) (built: Nov 11 2019 23:27:48) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies
PHP CS Fixer version I'm using ($ php-cs-fixer -V):
PHP CS Fixer 2.16.0 Yellow Bird by Fabien Potencier and Dariusz Ruminski
The different commands I used to run PHP CS Fixer:
php-cs-fixer fix ./path/myfile.php -vvv --rules="{\"braces\": true}"
php-cs-fixer fix ./path/myfile.php -vvv --rules="{\"braces\": {\"allow_single_line_closure\": false}}"
php-cs-fixer fix ./path/myfile.php -vvv --rules="{\"braces\": {\"allow_single_line_closure\": true}}"

PHP code sample:

before running PHP CS Fixer (no changes):

<?php
    $arr = ["1", "2", "3"];
    foreach($arr as $v) {
        echo $v;
    }
?>

with unexpected changes applied when running PHP CS Fixer:

<?php
    $arr = ["1", "2", "3"];
    foreach ($arr as $v) {
        echo $v;
    }
?>

with the changes you expected instead:

<?php
    $arr = ["1", "2", "3"];
    foreach($arr as $v) {
        echo $v;
    }
?>

PHP CS Fixer is adding a space between the foreach statement and the open parenthesis when the braces rule is turned on. Running either of the two commands listed below will result in no changes to the file, which is the expected behavior.
php-cs-fixer fix ./path/myfile.php -vvv --rules="{\"braces\": false}"
php-cs-fixer fix ./path/myfile.php -vvv --rules="{\"braces\": {}}"

Hi and thanks for reporting.
I think the change is good, however we know that it would be better if you would have more configuration options by splitting up the braces rule. Please see https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/823 for the discussion on this topic. Closing as it would be better to continue the discussion on one issue.


Tool tips for Digital buttons are incorrect.

Hover over input and tooltip says "Mode Input: Click to toggle high" whether it's input or not.  Check LA and direction as well.

Fixed in https://github.com/Digilent/waveforms-live/commit/fc57a1d9a31de7276c965f068d60519a6592978d


fixe case when from, to and value are 0

Summary
Handles case when from, to and value are 0 in Gauge control.
Solves
fixes #420

Awesome, thank you for both, PR and report

No worries. Great job with the library!


Differentiate between beta and GA credentials

Right now the code that looks for credentials (getServiceCreds) for a service in VCAP_SERVICES doesn't differentiate between beta and GA credentials, which means that even if you specify the correct local GA credentials, if the environment variable contains beta credentials, the incorrectly matched environment variable credentials will take precedence, preventing the code from working. getServiceCreds should also take a version from which it can determine if a GA service is being used and check the plan to avoid false matches.

I've fixed this in vcap_services, the library we use to get credentials from bluemix.


allow the whole blog to be one actor

I can think about many WordPress instances where not the bloggers but the blog as such are the most important thing most people want to follow. For example thing about a blog for your local soccer club. Sometimes "User A" might blog about the latest game, sometimes "User B", etc. But for me this doesn't matter. I don't want to follow all the individual bloggers and keep track if a new user starts to write blogs for my soccer club. I just want to follow the soccer club's blog and get all the news. In such a case it would be good to have a "meta actor" which is the whole blog I can follow and not only the authors as individual actors.

I agree. There are situations where bloggers prefer to maintain a collective identity without presenting themselves as individual authors. Is this possible?

I like the way Pterotype allows you to have<EMAIL_ADDRESS>+ set a profile pic and description for the fediverse so it appears as a user.

I'm for this, as well. Particularly on community sites that join the Indieweb.

I worked on this today and was able to find my blog via mastodon. If nobody is working on it i like to continue to test if the posts work and sumit a pull request

@terenc3 sure, that would be awesome!

I know a few people that would install this plugin if only this feature was available

I know a few people that would install this plugin if only this feature was available

Hi, any further plans on developing this feature? I think it would be really useful. Implementing this is sadly beyond my skills, but I can volunteer to test this. @terenc3 were you able to implement a working version of this feature?

Also, isn't this practically the same feature request as #1?

Yes, thats why this one is closed ;)
Yes, it is still planned as a feature!


RF intergration

BC power just died (as in spacetoad has switched to RF) so I thing that the cross to buildcraft should be deleted and I could try to get RF working

The Commented out classes are now safe to remove. Once done, this issue can be closed!

Yay :D

Going to close this shortly :)


CI-Hardening Executions

You can ignore this PR, it is to run CI over and over to catch flakes.

Abandoning this test


NIFI-12542 Refactor zendesk bundle to use updated APIs

Summary
Refactor tests and components in zendesk bundle to use updated APIs from NIFI-12452.
Additionally, makes use of newer List.of and Set.of for declaration of relationships and properties.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thank you for review & merge @exceptionfactory. 🎉
I wasn't sure whether additional Jira tickets are over the top. I'll open separate sub-tasks for any further adjustments. Thanks for pointing that out. 👍🏻


[FLINK-3830][build][WIP] POM Cleanup flink-scala

What is the purpose of the change
This PR changes the flink-scala pom to

not contain unused dependencies
contain all used dependencies

Brief change log
Verifying this change
mvn dependency:analyze
[INFO] — maven-dependency-plugin:2.10:analyze (default-cli) @ flink-scala_2.11 —
[WARNING] Used undeclared dependencies found:
[WARNING]     org.apache.flink:flink-metrics-core:jar:1.4-SNAPSHOT:compile
[WARNING]     org.apache.flink:flink-shaded-hadoop2:jar:1.4-SNAPSHOT:compile
[WARNING]     org.apache.flink:flink-test-utils-junit:jar:1.4-SNAPSHOT:test
[WARNING]     com.esotericsoftware.kryo:kryo:jar:2.24.0:compile
[WARNING]     org.apache.flink:flink-annotations:jar:1.4-SNAPSHOT:compile
[WARNING]     org.apache.commons:commons-lang3:jar:3.3.2:compile
[WARNING] Unused declared dependencies found:
[WARNING]     org.hamcrest:hamcrest-all:jar:1.3:test
[WARNING]     org.apache.flink:force-shading:jar:1.4-SNAPSHOT:compile
[WARNING]     org.powermock:powermock-module-junit4:jar:1.6.5:test
[WARNING]     com.google.code.findbugs:jsr305:jar:1.3.9:compile
[WARNING]     log4j:log4j:jar:1.2.17:test
[WARNING]     org.mockito:mockito-all:jar:1.10.19:test
[WARNING]     org.powermock:powermock-api-mockito:jar:1.6.5:test
[WARNING]     org.apache.flink:flink-test-utils_2.11:test-jar:tests:1.4-SNAPSHOT:test
[WARNING]     org.slf4j:slf4j-log4j12:jar:1.7.7:test

After the change:
[INFO] --- maven-dependency-plugin:2.10:analyze (default-cli) @ flink-scala_2.11 ---
[WARNING] Unused declared dependencies found:
[WARNING]    org.hamcrest:hamcrest-all:jar:1.3:test
[WARNING]    org.apache.flink:force-shading:jar:1.4-SNAPSHOT:compile
[WARNING]    org.powermock:powermock-module-junit4:jar:1.6.5:test
[WARNING]    com.google.code.findbugs:jsr305:jar:1.3.9:compile
[WARNING]    log4j:log4j:jar:1.2.17:test
[WARNING]    org.mockito:mockito-all:jar:1.10.19:test
[WARNING]    org.powermock:powermock-api-mockito:jar:1.6.5:test
[WARNING]    org.slf4j:slf4j-log4j12:jar:1.7.7:test

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes)

Documentation
none

We will have to redo this from scratch since too much time has passed.


change "Sirupsen/logrus" to "sirupsen/logrus" ?

can i add a new Pull Requests
chenge import "github.com/Sirupsen/logrus" to import "github.com/sirupsen/logrus"
Because the official is lowercase, and I want to customize it in my project. For add linenumber and filename in log.
(ps:  https://gist.github.com/hcwhan/c7b0cd986db2a63ab3fc05c6f55c64af)

Yes, feel free to create a pull-request :-)


for(var i:int=0,len:int=arr.lengthi<len;i++)

AS3: for(var i:int=0,len:int=arr.lengthi<len;i++)
=>
JS:for(var i=0,len:int=arr.lengthi<len;i++)

Please see the Readme under the Limitations section:
"Typed variable declarations cannot be all on one line"
Sorry about this, it was a bit difficult for me to parse these values with Regex parsing. But at some point hopefully I can resolve some of the limitations.

thanks


:loudspeaker: Feature preview for HTTP/2 and HTTP/3 one command away

Hello HTTPie users,
I am working on native support for HTTP/2 and HTTP/3 in urllib3 and I reached a point where I need testers.
So I am opening that issue to invite anyone willing to explore and report anomalies directly here. It would help with the final design of this implementation.
pip install httpie-next -U

# run twice! first is http/2 and second should be http/3
https GET www.cloudflare.com/img/nav/globe-lang-select-dark.svg

❓ So what gets installed
➡  The plugin httpie-next can remind you of httpie-http2 which is abandoned, in that case, this plugin is an excuse to install the patched urllib3 version and set up the QUIC capability cache layer.
➡ .config/httpie/httpie.quic.json is the QUIC capability cache layer persistence.
➡ In the future this (extra) won't be needed.
➡ h11, h2, and aioquic get installed. I have no plan to make one of them optional in this experiment.
⚠ Disclaimer!
➡ Installing this will undoubtfully alter your environment as most dependencies rely on urllib3, so you are warned! Also! You immediately relinquish your "right" to get active support from urllib3, requests, or HTTPie as it is an experimental version.
➡ Historically, urllib3 mostly lies on http.client package shipped within CPython, this patch completely detaches us from it.
➡ Understand that my modest piece of work (meaning patched urllib3) isn't meant to be reviewed or merged (ever). It would be hard on the maintainers to caution importing that many LOCs. For curious folks see https://github.com/urllib3/urllib3/pull/3030
So this is more for first hours enthusiastic users.
🥼 How to help?
➡ Install the extra, and report directly in this thread so that I can explore deeper and potentially work with better confidence for the next steps in urllib3. It is vital that some of you engage with this, as, this patch imports directly or indirectly more than 2.5k lines of code in urllib3!
Your report is most valuable if it contains at least:
> Python interpreter: e.g. 3.11
> Operating system: e.g. Windows/Mac/Linux
> Remote server: e.g. www.cloudflare.com
> How to reproduce: e.g. Made a POST request with a 120 MiB file and...

A +1 diff needs to be merged in HTTPie to accept HTTP/3 response. https://github.com/httpie/httpie/blob/30a6f73ec806393d897247b4c7268832de811ff7/httpie/models.py#L115-L116
~I will propose a PR.~ Proposed https://github.com/httpie/httpie/pull/1513
The plugin effectively patches the .version attr/property of wrapped HTTPResponse within httpie.models pending PR merge.

@Ousret great stuff, will play with it a report back

Now directly available through PyPI.
pip install httpie-next -U

Update: Since last time, a lot has happened.
See https://github.com/httpie/cli/pull/1531 if you want to test this in a more mature form.


Fix the translation of cofix to fix

This moves the head constructors's lazy of a cofixpoint definition to the toplevel of the fixpoint definition to avoid creating diverging functions in call-by-value semantics. See stedolan/malfunction#39 for an explanation of the problem with Coq's extraction which we mimicked.

What does this do on

CoInductive stream := Cons { head : nat; tail : stream }.

CoFixpoint repeat n :=
  mk n (repeat n).

?

I might be misreading this, but the change doesn't look correct to me. I think in the cases where remove_head_lazy fails to find a lazy to remove it should insert a force, e.g. to correctly compile the following:
CoFixpoint ones := {| head := 1; tail := ones |}.
CoFixpoint maybe_ones (b : bool) := if b then ones else {| head := 2; tail = maybe_ones b |}

maybe_ones should extract to:
let rec maybe_ones b = lazy (if b then force ones else lazy {head = 2; tail = maybe_ones b})

In general, the translation should be to wrap the entire body of a cofixpoint in lazy (force (...)), so that side-effects (i.e. nontermination) are delayed until the cofixpoint is inspected. force can then be pushed down, and if it reaches a lazy rewritten by force (lazy E) = E. If it doesn't reach a lazy, the force needs to remain present in the generated code.

I might be misreading this, but the change doesn't look correct to me. I think in the cases where remove_head_lazy fails to find a lazy to remove it should insert a force, e.g. to correctly compile the following:
CoFixpoint ones := {| head := 1; tail := ones |}.
CoFixpoint maybe_ones (b : bool) := if b then ones else {| head := 2; tail = maybe_ones b |}

maybe_ones should extract to:
let rec maybe_ones b = lazy (if b then force ones else lazy {head = 2; tail = maybe_ones b})

Shouldn't it rather become:
let rec ones := lazy (Cons[(S[O]) ones])
let rec maybe_ones b = lazy (if b then force ones else {head = 2; tail = maybe_ones b})

(Note the else branch does not have another lazy in front)

In general, the translation should be to wrap the entire body of a cofixpoint in lazy (force (...)), so that side-effects (i.e. nontermination) are delayed until the cofixpoint is inspected. force can then be pushed down, and if it reaches a lazy rewritten by force (lazy E) = E. If it doesn't reach a lazy, the force needs to remain present in the generated code.

Yes, I agree.
I'll push the new code I have first, which also handles going under defined constants as the guard does and then correct it.

I might be misreading this, but the change doesn't look correct to me. I think in the cases where remove_head_lazy fails to find a lazy to remove it should insert a force, e.g. to correctly compile the following:
CoFixpoint ones := {| head := 1; tail := ones |}.
CoFixpoint maybe_ones (b : bool) := if b then ones else {| head := 2; tail = maybe_ones b |}

maybe_ones should extract to:
let rec maybe_ones b = lazy (if b then force ones else lazy {head = 2; tail = maybe_ones b})

In general, the translation should be to wrap the entire body of a cofixpoint in lazy (force (...)), so that side-effects (i.e. nontermination) are delayed until the cofixpoint is inspected. force can then be pushed down, and if it reaches a lazy rewritten by force (lazy E) = E. If it doesn't reach a lazy, the force needs to remain present in the generated code.

With the latest definition in this branch I get:
Definition MetaCoq.TestSuite.erasure_live_test.maybe_ones.ones := let fix ones { struct 0 } :=
  lazy (Cons[(S[O]) ones]) in ones
Definition MetaCoq.TestSuite.erasure_live_test.maybe_ones.maybe_ones := let fix maybe_ones { struct 1 } :=
fun b =>
 lazy (match b with
 | true => force MetaCoq.TestSuite.erasure_live_test.maybe_ones.ones
 | false => Cons[(S[(S[O])]) (maybe_ones b)]
  end)

Which looks fine to me! Indeed the general moto should be "Use a lazy (force to delay side effects to the time the fixpoint body is actually forced.


update mappings and related documentation

https://github.com/orchestracities/anubis/blob/f867379c50793472e713c6a39b73c1e0a8eb8788/config/opa-service/policy.rego#L11
from the WAC spec

NOTE: HTTP Method and Access Mode Mapping
When the target of the HTTP request is the ACL resource, the operation can only be allowed with the acl:Control access mode.
Having acl:Control does not imply that the agent has acl:Read or acl:Write access to the resource itself, just to its corresponding ACL resource. For example, an agent with control access can disable their own write access (to prevent accidental over-writing of a resource by an application), but be able to change their access levels at a later point (since they retain acl:Control access).
The HTTP GET method request targeting a resource can only be allowed with the acl:Read access mode.
The HTTP POST can be used to create a new resource in a container or add information to existing resources (but not remove resources or its contents) with either acl:Append or acl:Write.
As the HTTP PUT method requests to create or replace the resource state, the acl:Write access mode would be required.
As the processing of HTTP PATCH method requests depends on the request semantics and content, acl:Append can allow requests using SPARQL 1.1 Update’s [SPARQL11-UPDATE] INSERT DATA operation but not DELETE DATA, whereas acl:Write would allow both operations.
As the HTTP DELETE method requests to remove a resource, the acl:Write access mode would be required.

linked to #9

acl:Control is only to authorize creation of policies for a resource. so this needs reworking in rego.


Link to the correct docs

Spotted this one when I wanted to check out the docs.

Feel free to ignore this PR if it was meant to be some kind of hidden advertisement for Fluxor 😃


Damage multipler

There will be a custom arrow slider that, when hit, amplifies the amount of health drain from a miss. It does not do any damage itself, instead opting to punish you for continuing to miss.

A "miss note" already exists. If the custom note will have the same effect as a normal miss this could be used.

A miss note already exists. If the custom note will have the same effect as a normal miss this could be used.

Nvm, it cannot be used, as "a normal miss" deals damage, while this one does not.


Breaking changes?

Are there breaking changes listed anywhere for major version releases?

Changelog?
https://github.com/ReactTraining/history/blob/master/CHANGES.md

We currently keep things in the CHANGES.md file, but I'm planning on having more detailed release notes going forward on each release page (i.e. like this).

What’s the opposite of a “wild goose chase?” A “tame duck?”
I have CHANGELOG so burned into my brain that I didn’t see the next best thing: CHANGES. I do love release notes, though. Either way, thanks for the help!


ChatToolChoiceType enum is missing REQUIRED value

The OpenAI API allows to specify tool_choice: "required"
See https://platform.openai.com/docs/guides/function-calling/function-calling-behavior
The simple-openai enum offers only "none" and "auto"
public enum ChatToolChoiceType {

    @JsonProperty("none")
    NONE,

    @JsonProperty("auto")
    AUTO;

}

That feature was recently added and it will be part of the release 3.0.0
See: https://platform.openai.com/docs/changelog/apr-29th-2024

This issue will be resolved in 3.0.0.


Change page and search problem

Hello
I install laravel-datatables and now I works on page load but when I want to change page number or search I get this error:
http://i65.tinypic.com/15pkbgw.jpg
This is my controller code:
    public function getJSONTransactionDataTables()
    {
        return Datatables::of(Transaction::where('user_id', Auth::user()->id))->make(true);
    }

And for route:
Route::any('payment/datatables','PaymentController@getJSONTransactionDataTables');

I think I my problem is route.
How can I solve this problem.

Windows 7
PHP 7
Laravel 5.3
Laravel-Datatables 6.21

Try inspecting the ajax request using chrome dev tools / firebug to get a better hint of what was causing the issue.

Closing old issue. Please open a new one if needed. Thanks!


Not able to restore model ckpts

Dear Yin Cui,
First of all it is Great! to see fashionpedia model ckpts with different backbones and their performances have been shared in: https://github.com/tensorflow/tpu/tree/master/models/official/detection/projects/fashionpedia
However, when I was trying to load a model ckpt "SpineNet-143" using following code:
with tf.Session() as sess:
saver = tf.train.import_meta_graph('./spinenet-143/model.ckpt.meta')
saver.restore(sess,tf.train.latest_checkpoint('./spinenet-143/'))
i was getting following error:
"NotFoundError: Op type not registered 'LegacyParallelInterleaveDatasetV2' in binary running on 7d386b9416f5. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) tf.contrib.resampler should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed."
Could you please look into the issue and let us know as how we can load the model to test inference ?
Also it will be great if we can get frozen model (.pb format) similar to example given in "baseline_predictor_demo.ipynb"
Thanking you!
Regards,
Abhishek

Thanks! for sharing the model training and inference codes in the tensorflow/tpu github, however, model restoration issue still persisting, here is what error I'm getting when I'm just trying to restore model from spinenet-143 ckpt:
CODE used to restore:
saver = tf.train.Saver()
with tf.Session() as sess:
saver.restore(sess, './model_spinenet_143/model.ckpt')
ERROR:
NotFoundError: Restoring from checkpoint failed. This is most likely due to a Variable name or other graph key that is missing from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
root error(s) found.
(0) Not found: Key Variable not found in checkpoint
[[node save/RestoreV2 (defined at /usr/local/lib/python3.6/dist-packages/tensorflow_core/python/framework/ops.py:1748) ]]
I'm using tensorflow-gpu 1.15.0 version in colab, any hint as this error is occurring ?
Thanks

Above error is it due to the fact that I'm trying to load a pre-trained checkpoint that was trained on TPU on GPU ?

Setting --use_tpu=False should work on CPU and GPU.
For more about code release, please refer to this link

Able to run inferences with suggestions from @richardaecn, hence closing this issue


feat: support build lance java with rust release mode

Now the lance java package only support build with debug mode.
Add a propertiy to support build with release mode.
## release mode
mvn clean package -DskipTests -Drust.release.build=true

## debug mode(default)
mvn clean package -DskipTests

.github/workflows/java-publish.yml could you help take a look if this java publish pipeline would be broken?

.github/workflows/java-publish.yml could you help take a look if this java publish pipeline would be broken?
The default behavior of build rust was still debug mode.

But I review the configuration of java-publish.yml, the building on x86 platform was in debug mode.
I add this configuration for it.


Add pa11y-ci for automated accessibility tests

This is mostly a POC and it will need a lot more tweaking and some of my other PRs finished first, like #29208.

[x] Look into ignoring some classes known to fail in hideElements (*-success, etc) ("hideElements": "[class*=-success], [class*=-info]")
[ ] Maybe ignore examples from color contrast check?
[ ] See if we can use html reporter (https://github.com/pa11y/pa11y-reporter-html)
[ ] Find a way to use the HTML reporter but still log the results in CLI
[x] See if we can drop delay-cli
[x] Upload HTML report on CI
[ ] See if we can use npx maybe, since Chromium is a huge download

I've made some progress with this a few days ago. I added the HTML results to CI so one can download them and review them. The pa11-ci tests run only on Node.js 12 so you need to visit this action to get the results.
AFAICT we need to ignore some selectors that we know that will fail color contrast, and we can try fixing the remaining issues.
Any help is welcome. :)

I looked into this one more time and I think if we fix the following errors, only a few will be left:
Error: Not all th elements in this table have a scope attribute. These cells should contain a scope attribute to identify their association with td elements.

WCAG2AA.Principle1.Guideline1_3.1_3_1.H63.1

Error: This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.

WCAG2AA.Principle3.Guideline3_2.3_2_2.H32.2

Error: This select element does not have a name available to an accessibility API. Valid names are: label element, title undefined, aria-label undefined, aria-labelledby undefined.

WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.Select.Name

Error: This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.

WCAG2AA.Principle1.Guideline1_3.1_3_1.F68

anywhere we can actually see the exact bits failing? i can never make sense of those CI things (and currently the pa11y task seems to be failing due to some configuration thing?)

@patrickhlauke please follow the link above (Or in the future the Node.js 12.x Action) and you will see the archive with the results.

Error: Not all th elements in this table have a scope attribute. These cells should contain a scope attribute to identify their association with td elements.
WCAG2AA.Principle1.Guideline1_3.1_3_1.H63.1

that, i would argue, is a false positive. should be a warning at most, and in general isn't needed. but i guess adding scope="col" to those table headers won't do any harm either.

Error: This select element does not have a name available to an accessibility API. Valid names are: label element, title undefined, aria-label undefined, aria-labelledby undefined.
WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.Select.Name
Error: This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.
WCAG2AA.Principle1.Guideline1_3.1_3_1.F68

i think most of those are due to the still ongoing vagueness on whether or not placeholder counts as being a valid way to provide an accessible name. in some browsers, placeholder is used as a last resort accessible name (even when a value was chosen/entered in a form control). in some others, it's ignored/overridden as soon as a value is chosen/entered.
to be safe, all those cases where we just relied on placeholder to give an accessible name we should double-up with an aria-label.

For all those cases where the error is "Error: This form does not contain a submit button..." i'd suggest simply removing the <form> and </form> from the code samples. they give the wrong impression that it's a complete form, when it's only really showing a handful of form elements as examples.

btw happy to tackle the above things, but unsure if i should do it in this branch here, or a separate branch off of current master?

So, it seems we still get the FP about the duplicate ID constructor. Also, I don't see any changes when using axe vs htlm_cs.

Based on latest results and @patrickhlauke's comments and PR:

Should we ignore the missing legend test completely? Or maybe add an ID to those fieldsets and add them to the hideElements whitelist in Pa11y config file, and documenting the opinionated stuff?
Should we skip the #constructor ID too — temporarily, linking to upstream issue maybe? I can't find a duplicate ID either, so I guess that's a bug… However we had the same in axe or HTML_CodeSniffer, so I'm confused about this: do they share the same HTML parser or something?
the color contrast issues in "Theming" bother me: I'll try to get on this, scss-side.
I still have errors due to forms missing submits in Navbars example page, with this pattern: <form><input class="form-control" type="text" placeholder="Search" aria-label="Search"></form>, not sure how to proceed those. I guess they should match the "Navbar" component page examples, with a "Search" button aside. Let me try this.

@ffoodd

yes i'd ignore the <legend> thing
yes seems to be an error/bug. it IS odd that the error appears regardless of testing engine...is there perhaps something happening in the generated page which is then removed/modified AFTER pa11y runs before it becomes final output?
not sure we can avoid having some contrast issues with theming other than completely dropping certain tints/combinations. we could exclude from testing but add a note/callout to the page pointing out that naturally some of the tints do NOT pass contrast requirements and authors should use their best judgement about which to choose/when to use them?
as said in #30464 is, in my view, not a failure per se, should really be just a warning, and i COULD see an argument for this not being a problem for forms that only contain a single text/search input

I think our best way moving forward with pa11y-ci is to find a way to add a unique page class in body and ignore anything we think we should. I'll probably need some help with that, but I will try to tackle this in a separate PR. After this is done, we can ignore further things more easily.

@XhmikosR What do you mean by "a unique page class in body"?
@patrickhlauke About contrasts, I'll just submit a PR to try defining a 4.5 threshold for our color-contrast() function. It could lead to good things :)

Something like this, adapted for Hugo: https://github.com/twbs/blog/blob/e687b66fee2a4ebffed09c91279bb4f8a8c51fcf/_layouts/default.html#L23-L26

@ffoodd ah i now looked specifically at which color combos in theming fail, and yes...it's the edges where it flips from using black text to white text. so yes, changing the contrast algo to enforce 4.5:1 (what does it currently do? 3:1?) will solve it

It's defined as 3:1 for now. But it could have side effects in component, would require a few checks :)

Two things here:

I ignored the missing submit button test;
I effectively switched to aXe: after comparing to what I've done in Boosted, I realized that runners needed to be declared in defaults.

Aaand… We have (a lot) more failures :innocent:

@XhmikosR I can apply it again, I just followed @patrickhlauke recommendation there.

Alright, let's leave it as is for now. I still think the warning is useful to have so we should ignore it on a per-case basis. And currently we can't target only the examples, unfortunately.

FWIW we have a lot of headings hierarchy failures (easy to fix) and aXe seems a bit zealous about ARIA landmarks.

FWIW we have a lot of headings hierarchy failures (easy to fix) and aXe seems a bit zealous about ARIA landmarks.

If the failures are about skipped levels, then...it's not a hard WCAG failure (see https://developer.paciellogroup.com/blog/2020/03/heading-off-confusion-when-do-headings-fail-wcag/)
As for landmarks, historically axe/deque have been indeed quite keen to see lack of landmarks as a hard failure, but again the reality is not quite as clear cut (will need to see specifically which things are being flagged though...admittedly, i'm only commenting based on past experience with these tools)

@patrickhlauke aXe is reporting multiple navigation landmarks as an error, specifying html > body > nav. Since they're properly labelled with aria-label, I don't think this should be considered as a failure…
Let us know if you have any time to browser this new report. I'll try to tackle a few things when I can, too.

axe is correct that we do have two <nav> elements with the same aria-label="Secondary navigation"> (the search bar at the top, and the TOC)

"Error: Heading levels should only increase by one" as note that's not actually a hard failure. should be a warning at best. we should ignore/exclude this particular test

"Error: All page content must be contained by landmarks"
that's best practice, not a hard failure (in fact, looking at https://dequeuniversity.com/rules/axe/3.5/region?application=axeAPI and also the above heading thing https://dequeuniversity.com/rules/axe/3.5/heading-order?application=axeAPI axe does call this WCAG Best practice rather than noting them as specific SC failures ... but it seems pa11y doesn't differentiate here and calls them errors regardless - wonder if there's some way to easily say "just error on hard failures, not best practices")

ditto "Error: Aside must not be contained in another landmark" - best practice, not failure

All right, I cleaned up the branch.
Notes:

I switched back to htmlcs; it's faster and doesn't have the landmarks FP
I haven't split the accessibility to a separate Action because it needs the doc built files
We could go further and run pa11ci for js/tests/visual; we already run these through the HTML validator, but maybe it's an overkill
I don't love that the results are not logged in CLI. I still need to see if I can find a way to have both
Finally, there are still some valid failures even with our current ignores, so perhaps we shouldn't land this until we sort these out in master. Not a lot, though, so that's something regarding v5.0 :)

i have a tiny bit of time this week (as I'm in-between jobs with a few days off) ... so shout if you need me to look at anything here (and maybe point me to what it is I should look at...I always lose track of where we're up to / where the logs are / etc)

@patrickhlauke the results are uploaded in the Docs Action. https://github.com/twbs/bootstrap/actions?query=workflow%3ADocs+branch%3Amaster-xmr-pa11y-ci Then you visit the failed action and you get the zip with the HTML results.

just did a run-through of the pa11y results. all the color contrast issues are legit, and gel with some of the problems i found manually last week while going over some of the v5 pages.
beyond that, i'd still say the following two rules can be ignored:

WCAG2AA.Principle3.Guideline3_2.3_2_2.H32.2 (forms without an explicit submit button)
WCAG2AA.Principle1.Guideline1_3.1_3_1.H71.NoLegend (fieldsets without a legend)

plus that one failure that appears to be a false positive about the duplicate id="constructor" which i just can't find when manually verifying the page

What's the status on this one? Still ongoing or closable?
Also, lol-ing at the dates here.

It's been a long walk, you know 😄
We'll need to rebase and check report. FYI I manages to make it green and required on Boosted so I really think we should keep going.

From my side these are the things to think about:

aXe or html_codesniffer; last time I tried aXe, we were flooded with issues that might have been FPs
I don't want the huge puppeteer (which in turn downloads Chromium) devDependency, ~143MB... Not sure how to work around this, we could probably move the needed packages in the Action that needs them, but it's not a perfect solution either
I can't seem to be able to find a way to display the CLI results and also redirect them at the same time

Is this PR still worth pursuing at this point, or do we need a fresh take on it?

There's no need for a fresh take in it, I can rebase it. We need to solve the TODO I have in the OP.


Refactor - Rich Formatting dropdown

Disconnect Rich Formatting dropdown options rendering from the specific Elements components (less styles to override)
Dramatically simplify Dropdown options rendering logic
Change how Dropdown symbols are exported (it's a TS namespace now)
Convert all related stylesheets to SCSS modules
No changes in visual presentations are expected


Generated images got oil painting style and is blurry

I trained the StyleGAN2 about 140k iterations(samples_per_gpu=3, px=1024), and visualized the training result. I found the generated images tend to be oil painting style and is a little blurry. What can I do to avoid these phenomenon?
Looking forward to your reply, thanks!

Training such high-resolution stylegan2 needs much training cost. I may suggest that you can use samples_per_gpu=4 and adopt 8 GPUs as the standard setting. Could you tell me more about the training details, e.g., the number of GPUs, current fid, and etc?

The number of GPUs is 8, samples_per_gpu=3, current FID50k is about 120, maybe there are some bugs in my implement...

I use my own implementation.

How many iterations have you trained your models for? Maybe I can share some results in our experiments to help you.

Thank you for your help! The current iteration is about 168k, loss_disc_fake_g is about 3.6(in the range of 1.8~2.4), loss_disc_real is 0.28(in the range of 0.1~0.7),  loss_disc_fake is about 0.4(in the range of 0.1~0.7), loss_path_regular is about 1.1(increasing while training), loss_r1_gp is about 2.4.

Thank you for your help! The current iteration is about 168k, loss_disc_fake_g is about 3.6(in the range of 1.8 to 2.4), loss_disc_real is 0.28(in the range of 0.1 to 0.7), loss_disc_fake is about 0.4(in the range of 0.1 to 0.7), loss_path_regular is about 1.1(increasing while training), loss_r1_gp is about 2.4.

I check out experiments and the fid in 16w iteration is 5.3657.
loss_disc_fake_g: about 1.5
loss_disc_fake: about 0.385

Thank you for your reply, I'll check my implementation.


use alertmanager pod address list in thanos config

Signed-off-by: marcolan018<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/24147

/retest

/retest

/retest


Remove index.json from the metadata folder

Is this issue ongoing? It seems that https://github.com/oracle/graalvm-reachability-metadata/pull/1 is not set to be associated with this issue.

Yes, it is still planned and the work will be continued in the near future.


Add support for swarm mode templating

Wire templating support of swarmkit for the engine, in order to be used through services 🐮 — #27995 updated swarmkit but did not wire it (and thus the package wasn't kept either).

[x] Tests
[ ] Documentations

Closes #28022
/cc @thaJeztah @stevvooe @aaronlehmann @icecrime
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

@AkihiroSuda doesn't need vendoring, it's already vendored (just wasn't used so the package was cleaned) — the vendor check is green :wink:

oh, sorry 😅

Thanks for carrying this!
I suspect we will run into some validation problems when passing through template syntax. It might be good to have a few tests that create services that flex these pipelines end to end.
Specific areas in order of sensitivity:

Mount source/target validated as path
Hostname may have aggressive validation
Env, although most just looks for an =

docker/swarmkit#1738 was merged

LGTM

LGTM

@vieux @vdemeester looks like we missed this in the changelog

https://github.com/docker/docker/issues/28022 is tracking the documentation part, so removing docs/revisit


add video logging functionality for evaluation episodes

This branch adds on option in the evaluation rollout to render videos of the environment add write them as a ndarray to a logger

This works for mt1 and mt50 environments and can be merged


How to build amazon chime sdk on Windows using VS code

I want to build the amazon chime sdk on windows using Visual Studio Code. Could you please provide the steps for the same.

Hello. VS Code is not really a build system, though it does integrate well with CMake, which we recommend to use when starting a project from scratch.

Hello
Tried to integrating using CMake but was not able to configure due to openssl libraries. For your reference I have added the screenshot

What platform are you running on? Have you installed openssl? If it is not in /usr/lib/ and /usr/include/, you need to set -DLWS_OPENSSL_LIBRARIES and -DLWS_OPENSSL_INCLUDE_DIRS as mentioned in README.

Running on windows and openssl is installed

Openssl may be installed, but it is probably not in the location checked by CMake. Please find the locations of libssl.so and set the values LWS_OPENSSL_LIBRARIES and LWS_OPENSSL_INCLUDE_DIRS

Closing due to age.


[NavigatorExperimental] Override Styles for NavigationHeader? Bottom Border

I have written a custom NavigationHeader component and applied my own unique styles. However, it seems some of the core react native styles are hardcoded to the component and cannot be overwritten. I.e. there is a thin border on the bottom that I can't seem to get rid of. I'm going after the effect where the header blends into the page content by having the same background color, however the line is messing up the experience.

What styles are you passing to NavigationHeader?
Passing something like <NavigationHeader style={{ borderBottomWidth: 0 }} />should work.

@ryankask wow, that did the trick! Thank you!


update(docs): add me to owners.

What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area docs
What this PR does / why we need it:
As privately discussed with @dwindsor, i am opening this PR to propose myself as a driverkit maintainer.
In the latest 2-3 months, i have been as active as possible, bringing to driverkit:

arm64 support
improved CI with integration tests
lots of bug fixes
lots of small and not-so-small refactorings
just (but imo this is the best part :D) ideas to play around

I am going to publicly propose myself during the next community call, then leave this open for a public discussion, for a week or so.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

update(docs): add fededp to owners.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 9358ae782b0a3dc9eda1307ab17436bcbb825e2f

:( @leodido i talked with David; as far as i know, he tried to contact you!

/unhold


Fix unfinished-comments being wrongly triggered after opening the dropdown of a review comment

Test URLs

Go to a PR with reviews, e.g. https://github.com/sindresorhus/refined-github/pull/4023
Open the dropdown menu of any review comment
Go to a different tab
The title of the previous tab should NOT say (Draft comment)

Can we have an explicit value check instead? field.value !== ''. Empty fields are never something we need to save

Empty fields are never something we need to save, even if they’ve been changed

True, but we still need the id check (or something equivalent) because those hidden textareas are not empty:

(Maybe the comment should make that clearer)

I noticed that the bug happens on any comment, not just reviews


CIV-9993 Hearing party MCI

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-9993
Change description

Added 2nd page for manage contact information. More details in the ticket
have to delete experts (yes/no etc) if the experts are removed, same as witnesses if not it causes CCD errors

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Please don't update branch because ccd guys are fixing the bug


fix(docs): Incorrect types in docs for helpers

Motivation/Description of the PR
Applicable helpers:

[ ] Webdriver

[ ] Puppeteer

[ ] Nightmare

[ ] REST

[ ] Appium

[ ] Protractor

[ ] TestCafe

Description of this PR, which problem it solves

A link to the corresponding issue (if applicable).

Type of change

[ ] Breaking changes
[ ] New functionality
[ ] Bug fix
[x] Documentation changes/updates
[ ] Hot fix
[ ] Markdown files fix - not related to source code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run ./runio docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- runio.js  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- runio.js  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- runio.js  1

See the complete overview on Codacy


Change order of sub-sidebar items of transport

I was trying to change the order of the sub-sidebar items of international/passenger/freight transport on beta, but encountered that that is not possible in the admin of ETmodel. There is a field to fill in the 'position' of the sub-sidebar item (see image below), but this does not seem to work! Do you know how to change this, @grdw or @antw ?

Is this possible, @antw and @grdw ? :wink:
The preferred order would be:

Passenger transport
Freight transport
International transport


Fix exception 'No message received'

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):

Bug Fix

Short description (up to few sentences):
Fix No message received exception in replication.
Detailed description:
Default server keep_alive_timeout is 3 seconds https://github.com/yandex/ClickHouse/blob/master/dbms/programs/server/config.xml#L88. But default Poco HTTPClientSession timeout is 8 seconds https://github.com/ClickHouse-Extras/poco/blob/d0271f990869b7f23dac4bb2ee0c127cf815f077/Net/include/Poco/Net/HTTPClientSession.h#L269. Server closes connection in three seconds, but client session tries to reconnect  after 8 seconds https://github.com/ClickHouse-Extras/poco/blob/d0271f990869b7f23dac4bb2ee0c127cf815f077/Net/src/HTTPClientSession.cpp#L403. If we make request in interval between (3, 8] seconds after previous we will try to write in CLOSE_WAIT socket and exception No message received will be thrown.
Closes: https://github.com/yandex/ClickHouse/issues/4047

Nice debug :) there is still a very small chance that connection will be in close wait if this check succeeds, time drift/vm pauses. Negligible to some degree :)

Hi. I'm wondering if you may have considered this actually to be a bug in Poco? The Poco docs say nothing about only being able to send data over an HTTPClientSession object when the underlying socket is in a given state. In fact, I'd think this Poco class should be able to handle this situation, especially when using HTTP/1.1 keepalive persistent connections.  I say this because I've seen the same problem in a project I'm working on that uses Poco.


Deactivate unfixed warnings

This PR deactivates two kinds of warnings as they are unlikely to be fixed in code and may hide important warnings that are worth fixing:

Conversion: In general, I am hesitant in deactivating this warning due to double to int conversion bugs. However, we get a ton of these warnings due to BOOST_PYTHON_FUNCTION_OVERLOADS.
Multi-line comment: There are two sources (a) commented out macros that appear as multi-line comments and (b) Latex code.

This reduces our compiler warnings from at present 104 to 3.
The remaining warnings after this PR are:
In file included from ~/git/pinocchio/build/include/pinocchio/math/quaternion.hpp:11:0,
                 from ~/git/pinocchio/build/include/pinocchio/spatial/se3-tpl.hpp:12,
                 from ~/git/pinocchio/build/include/pinocchio/spatial/se3.hpp:44,
                 from ~/git/pinocchio/build/include/pinocchio/multibody/model.hpp:10,
                 from ~/git/pinocchio/build/include/pinocchio/algorithm/joint-configuration.hpp:8,
                 from ~/git/pinocchio/bindings/python/algorithm/expose-joints.cpp:6:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp: In static member function ‘static pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::ReturnType pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::run(pinocchio::internal::ComparisonOperators, const condition_type&, const condition_type&, const ThenType&, const ElseType&) [with condition_type = double; ThenType = double; ElseType = double]’:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp:71:7: warning: control reaches end of non-void function [-Wreturn-type]
       }
       ^
In file included from ~/git/pinocchio/build/include/pinocchio/spatial/explog.hpp:10:0,
                 from ~/git/pinocchio/build/include/pinocchio/bindings/python/spatial/explog.hpp:9,
                 from ~/git/pinocchio/bindings/python/spatial/expose-explog.cpp:6:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp: In static member function ‘static pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::ReturnType pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::run(pinocchio::internal::ComparisonOperators, const condition_type&, const condition_type&, const ThenType&, const ElseType&) [with condition_type = double; ThenType = double; ElseType = double]’:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp:71:7: warning: control reaches end of non-void function [-Wreturn-type]
       }
       ^
In file included from ~/git/pinocchio/build/include/pinocchio/math/quaternion.hpp:11:0,
                 from ~/git/pinocchio/build/include/pinocchio/spatial/se3-tpl.hpp:12,
                 from ~/git/pinocchio/build/include/pinocchio/spatial/se3.hpp:44,
                 from ~/git/pinocchio/build/include/pinocchio/bindings/python/spatial/se3.hpp:12,
                 from ~/git/pinocchio/bindings/python/spatial/expose-SE3.cpp:6:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp: In static member function ‘static pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::ReturnType pinocchio::internal::if_then_else_impl<condition_type, condition_type, ThenType, ElseType>::run(pinocchio::internal::ComparisonOperators, const condition_type&, const condition_type&, const ThenType&, const ElseType&) [with condition_type = double; ThenType = double; ElseType = double]’:
~/git/pinocchio/build/include/pinocchio/utils/static-if.hpp:71:7: warning: control reaches end of non-void function [-Wreturn-type]
       }
       ^

Issue from GitHub. This PR has been merged but has not been closed.

I had noticed the conversion warnings and I wanted to get rid of them. However, I had trouble with that,  naive approaches did not seem to work

I had noticed the conversion warnings from BOOST_PYTHON_FUNCTION_OVERLOADS and I wanted to get rid of them. However, I had trouble with that, naive approaches did not seem to work

I did spent a significant amount of time trying to get rid off them "properly" but none of the usual suspects (casting, appending type specifiers, etc.) worked :-(. If you have an idea for a better solution, let's fix them proper and re-activate the warning.

I had noticed the conversion warnings from BOOST_PYTHON_FUNCTION_OVERLOADS and I wanted to get rid of them. However, I had trouble with that, naive approaches did not seem to work

I did spent a significant amount of time trying to get rid off them "properly" but none of the usual suspects (casting, appending type specifiers, etc.) worked :-(. If you have an idea for a better solution, let's fix them proper and re-activate the warning.

Same here. Tried but failed. Weird. I fear this warning may come from inside boost, and there may be nothing we can do about it. And I haven't found anything on the internet about it either. The only "better" solution I can think of is to locally ignore the warning putting #pragma around each instance of BOOST_PYTHON_FUNCTION_OVERLOADS, but I'm not even sure it can actually be considered "better".

I had noticed the conversion warnings from BOOST_PYTHON_FUNCTION_OVERLOADS and I wanted to get rid of them. However, I had trouble with that, naive approaches did not seem to work

I did spent a significant amount of time trying to get rid off them "properly" but none of the usual suspects (casting, appending type specifiers, etc.) worked :-(. If you have an idea for a better solution, let's fix them proper and re-activate the warning.

Same here. Tried but failed. Weird. I fear this warning may come from inside boost, and there may be nothing we can do about it. And I haven't found anything on the internet about it either. The only "better" solution I can think of is to locally ignore the warning putting #pragma around each instance of BOOST_PYTHON_FUNCTION_OVERLOADS, but I'm not even sure it can actually be considered "better".

I spent some time investigating this, and as I recall there is no issue on the caller side, it's just the boost macro implementation that seems to be problematic.
I think that @gabrielebndn's proposal of using #pragma is the way to go in this specific case, the same way one would use -isystem to silence system header warnings.

@wxmerkt, I now see that your -Wno-conversion is limited to the Python wrappings. In this case it's good, as Python bindings contain hardly any function code, and I think there is no point wasting more time on this.


Implement word deletion

Allow to delete complete words by pressing ctrl + backspace or ctrl + delete.
Repro

Go to https://svedit.vercel.app/
Click at the end of the first text in the website (Svedit title)
After entering edit mode, press ctrl + backspace
Missing feature: it deletes only 1 character and not the whole word

Expected behavior

Go to https://svedit.vercel.app/
Click at the end of the first text in the website (Svedit title)
After entering edit mode, press ctrl + backspace
it deletes the whole word

Right, that's not yet implemented. Just to be sure, the expectation is that the text at the current line is deleted right?
There's just a challenge here in the case of Svedit, as our internal model does not know about lines (and where lines break), so if you typed a paragraph and hit ctrl+backspace, it would be easy to remove the whole text until you find a newline character for instance. But it would be hard to delete the text of the current line (as it is rendered).
Do you think it would it be an acceptable compromise to delete the current word (instead of the current line) on ctrl+backspace?

Ctrl + Backspace is more common for deleting the previous word.
Whereas Cmd + Backspace is more commonly used to delete up to the beginning of the current line. Which actually feels a bit weird in "prose". It makes sense when there's a closed "unit of meaning" per line (e.g. in a code editor), but when a paragraph is broken over several lines, it doesn't feel right.
I would then rather expect to delete until the next sentence fragment (separated by e.g. ;,.: \n)
These are the common shortcuts in Word/ iA Writer/ Pages / VS Code/ etc.

Action
Mac
Windows

Delete previous word
Option + Backspace OR: Ctrl + Backspace
Ctrl + Backspace

Delete to start of line
Cmd + Backspace
Home, then Shift + Home, then Backspace (???)

Delete next word
Option + Delete OR: Fn + Option + Backspace
Ctrl + Delete

Delete to end of Block
Ctrl + K
Shift + End, then Delete


#defaultsTo should be varg, not value, varg

ArgumentAcceptingOptionSpec#defaultsTo(v,varg) prevents me from adding the defaults as a String[] value
Thus this,
parser.accepts("some-values").withRequiredArgs().defaultTo( SOME_ARRAY );
won't compile.

Sounds reasonable -- though I am leaning toward offering both defaultsTo(V, V...) and defaultsTo(V[]), to disallow at compile time the pathological defaultsTo() with no args.
Note also that this doesn't help with primitive arrays:
OptionSpec<Integer> c = parser.accepts("c").withRequiredArg().ofType(Integer.class).defaultsTo(new int[] { 1, 2 });

(Thanks, Java. 8^| )
Would offering both defaultsTo(V, V...) and defaultsTo(V[]) suit your needs?

Sure thing. Trying to deconstruct an array to fit into (V,V...) is darn ugly.

Right on. I'll roll this in shortly.

Resolved in 4.2. Thanks for pointing this out!


Error: The method 'instantiateImageCodec' isn't defined for the class 'PaintingBinding'.

Appears on:
robertmainzer@Roberts-MacBook-Air remonon_app % flutter --version
Flutter 3.16.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 78666c8dc5 (2 weeks ago) • 2023-12-19 16:14:14 -0800
Engine • revision 3f3e560236
Tools • Dart 3.2.3 • DevTools 2.28.4

Flutter build logs:
Launching lib/main.dart on iPhone 15 Pro in debug mode...
Running Xcode build...
Xcode build done.                                           33.5s
Failed to build iOS app
Error (Xcode): ../../.pub-cache/hosted/pub.dev/flutter_gif-0.0.4/lib/flutter_gif.dart:236:8: Error: The method 'instantiateImageCodec' isn't defined for the class 'PaintingBinding'.

Could not build the application for the simulator.
Error launching application on iPhone 15 Pro.

For anyone interested, I fixed it myself and published flutter_gif_plus.


Regrading  website animations

hi i am Ram #gssoc24
i want to add some animations in your website which looks good and User interactive
tech stack to be used
-AOS.js
-ityped.js
etc

Hey there @RamakrushnaBiswal . If it's framer motion then only we can plan something

@ashutosh-rath02 yh sir

Sure @RamakrushnaBiswal please work on it and give me a preview video first and time you will require to finish this.

@ashutosh-rath02 ok sir

Stale

Hello @RamakrushnaBiswal! Your issue #88 has been closed. Thank you for your contribution!


apfm1000 can't be scraped

The wiki says "This system scrapes metadata for the “apfm1000” group"
I can scrape some apfm1000 roms individually, but not the entire system.
The ES scraper dialog doesn't include APF M1000 as an option - it's the only system missing from the big list of systems with checkboxes.

apfm1000 system is not known by Screenscraper which is probably the global scraper you are using.
Only HFSDB and TheGamesDB are supported.


@react-maps/world fix: svg viewBox update

viewBox size is incorrect for the world map.
Currently it looks like this:

After the change:

Btw, you already fixed it before with this commit: https://github.com/shubhexists/react-maps/commit/29a2c92f226762e18f001d3033bc52549034f766
but then overrode it with this one: https://github.com/shubhexists/react-maps/commit/00fbe063aa738940155468471f781be874594c00 when you moved viewBox size to constants

Hi @ajgoralczyk , Thanks a lot. I will just make this update.
Thanks for your time

The view ports are corrected in @react-map/world @1.0.9.
Thanks


Property for middleware

How to send some parameter to middleware?
For example, I have two pages: all_pages and all_users.
They initializaded with middleware. In the middleware, you need to check if the user object has permission. The problem is that for different pages you need to check different permissions. And you will have to create many similar types of middleware. It would be wonderful to have the ability to transfer to the middleware the resolution that should be checked:
// pages/all_pages.veu
export default {
  name: 'all_pages',
  middleware: ['check_access?permission=edit_pages'],
}

// pages/all_users.veu
export default {
  name: 'all_users',
  middleware: ['check_access?permission=edit_users'],
}

// middleware/check_access.js
export default function ({ store, error, params }) {
  if (!store.state.currentUser.permissions.find(p => p === params.permission) {
    return error(/* ... */)
  }
}

It's really useful example when we can use meta variables for routes. Unfortunately, meta fields not supported by Nuxt.
In my project, I also have some scenarios when meta fields excellent solutions because some logic depends exactly on the page, but not the state. That's why vuex not so good solutions in this case.
For example. All pages have menu component, that why this component placed at the layout, but not every page. Now I want to make this menu a little different at a couple of pages. It's really easy with meta variables and really overhead with new custom layouts.
@pi0, @Atinux, guys, what do you think about it?
p.s. Sorry for my English.

Hi @cawa-93 @KonstantinVlasov
You can already check some params from the matched route directly, which is even better than meta or middleware params.
See my demonstration: https://glitch.com/edit/#!/nuxt-midd-properties?
Example: https://nuxt-midd-properties.glitch.me/
You pages could look like this:
// pages/all_pages.vue
export default {
  middleware: ['check_access'],
  permissions: ['edit_pages']
}


Add CMake support

Fixes #9

First of all, thanks for your attempt to add CMake support.
However, before accepting the PR I have a few remarks.

I don't know much about CMake, but looking at CMakeLists.txt, I get the impression that it is quite Windows specific. The goal for SQLite3MultipleCiphers is to be platform-independent. That is, I would certainly prefer if the CMake support would work on other platforms as Windows, too. Would you be able to address this aspect? If not now, maybe later in the future?

Before making the first release I intend to remove the pthreads4w component (and most likely the test applications depending on it). Why? SQLite3MultipleCiphers itself does not depend on pthreads4w, and pthreads4w is Windows-only. I added it only for testing the multi-threading behaviour, especially shared cache mode (a feature which is deprecated and should be discouraged to be used according to the SQLite developers). That is, the file CMakeLists.txt will have to be adjusted before making the release.

Sorry for the poor infomation for this PR.
"CMake support" is not correct for this PR, maybe "a prototype of supporting cmake" is much better. Currently, it's just convertions of the current VS solutions and it need to be add more work on it for other platfrom & build tool supports.
Curently, I just test it on windows for VS2010 and VS2019.

I don't know much about CMake, but looking at CMakeLists.txt, I get the impression that it is quite Windows specific. The goal for SQLite3MultipleCiphers is to be platform-independent. That is, I would certainly prefer if the CMake support would work on other platforms as Windows, too. Would you be able to address this aspect? If not now, maybe later in the future?
CMake has cross platfrom support. It can generat makefile for Linux too. Actualy I should combine both the makefiles and VS solution into the CMakeList.txt, but currently its much like only for generating MSVC solutions. Unfortunately, my poor Linux knowledge limiting me to finished that job. It should be a easy task, such as adding platfrom specified build tool args for certain platform.

Before making the first release I intend to remove the pthreads4w component (and most likely the test applications depending on it). Why? SQLite3MultipleCiphers itself does not depend on pthreads4w, and pthreads4w is Windows-only. I added it only for testing the multi-threading behaviour, especially shared cache mode (a feature which is deprecated and should be discouraged to be used according to the SQLite developers). That is, the file CMakeLists.txt will have to be adjusted before making the release.
In my opinion, whatever changes is going to make to this project, moving to CMake always a good idea. Editing a single or couple cmake files is much easier than editing makefiles and tons of VS solutions for differnt VS version. If currently pthreads4w is windows only, we can just adding something like if(WIN32) ...pthreads4w stuff... end()  to only add this project for windows.

Sorry for the poor infomation for this PR.
"CMake support" is not correct for this PR, maybe "a prototype of supporting cmake" is much better. Currently, it's just convertions of the current VS solutions and it need to be add more work on it for other platform & build tool supports.

Starting with support for Windows only, is fine with me. However, the final goal should be to support all relevant major platforms (i.e. Windows, Linux, OSX).

Currently, I just test it on windows for VS2010 and VS2019.

For development I use mainly VS2019, but I'm able to test with VS2010, VS2015, and VS2017 as well. Additionally, I test with MinGW64 occasionally.

CMake is designd for cross platfrom. Actually I should combine both the makefiles and VS solution into the CMakeList.txt, but currently its much like only for generating MSVC solutions. Unfortunately, my poor Linux knowledge limiting me to finished that job. It should be a easy task, such as adding platform specified build tool args for certain platform.

Well, since I'm not acquainted with CMake, I hope other developers will then become encouraged to contribute to the CMake build support.

In my opinion, whatever changes is going to make to this project, moving to CMake always a good idea. Editing a single or couple cmake files is much easier than editing makefiles and tons of VS solutions for differnt VS version.

Hm, I use premake5 to generate the build files for VS and MinGW/gcc. So regenerating the build files after some changes is typically a matter of a few seconds only.

If currently pthreads4w is windows only, we can just adding something like if(WIN32) ...pthreads4w stuff... end() to only add this project for windows.

As said I intend to remove pthreads4w from the repository. If there is a demand I might set up a separate repository for testing the component.

Hm, I use premake5 to generate the build files for VS and MinGW/gcc. So regenerating the build files after some changes is typically a matter of a few seconds only.

Hm, not notice there already a build system. Maybe a build guide is more important. Users can easily to conver the project into what they need.
However, maybe CMake is more famous? opencv, CEF, vcpkg are using cmake. I think a binaries with a CMakeList.txt witch use to manage the binaries for externel projects as a release is easier to use.

Maybe a build guide is more important. Users can easily to conver the project into what they need.

Yes, a build guide has still to be written. Its lack is one of the reasons I haven't made an official release yet.

However, maybe CMake is more famous? opencv, CEF, vcpkg are using cmake.

I know that CMake is almost ubiquitous nowadays. However, when I started to develop open source some 15 years ago, it was extremely cumbersome to use, and I began to use bakefile (the build system of wxWidgets back then) and switched to premake later on.
Adding CMake support to this project is certainly a good idea. Most likely that would make integration of this component into the vcpkg world etc easier. However, that requires platform-independency.

I think a binaries with a CMakeList.txt witch use to manage the binaries for externel projects as a release is easier to use.

Again, I'm certainly not against adding CMake support. In the contrary. However, I would prefer that you eliminate at least most if not all of the add_compile_options section (because it is not only platform-specific but also compiler-specific), before I merge the PR. Thanks in advance for your efforts.

FWIW, there are two ways to support CMake in a project:

Build the project itself with CMake.
Allow other CMake-based projects to consume easily your project, as a CMake dependency.

If you're happy with premake, there's no reason to change it, and only do #2.
That's what Boost does for example: it builds using its own b2 build system,
which generates as a build product the CMake files for upstream consumption.

Thanks for your comments, @ddevienne.

FWIW, there are two ways to support CMake in a project:

Build the project itself with CMake.
Allow other CMake-based projects to consume easily your project, as a CMake dependency.

If you're happy with premake, there's no reason to change it, and only do (2).
That's what Boost does for example: it builds using its own b2 build system,
which generates as a build product the CMake files for upstream consumption.

At least at the moment I don't intend to replace the premake based build system. However, adding some sort of CMake support is certainly a good idea, since CMake is in widespread use. Within the premake project there are efforts to add CMake as a supported build file format. That is, maybe premake will support generating CMake files in the not too far future.


Error: when start the Exporter

Here below is my version details:
Redis:
C:\Users>redis-cli -v
redis-cli 3.0.504
Python :
C:\Users>python
Python 3.10.0 (tags/v3.10.0:b494f59, Oct  4 2021, 19:00:18) [MSC v.1929 64 bit (AMD64)] on win32
How I am starting in my windows environment:
Step 1: C:\Users>pip install rq-exporter
Requirement already satisfied: rq-exporter in c:\program files\python310\lib\site-packages (1.9.0)
Requirement already satisfied: redis>=3.5.3 in c:\program files\python310\lib\site-packages (from rq-exporter) (4.0.1)
Requirement already satisfied: rq>=1.8.0 in c:\program files\python310\lib\site-packages (from rq-exporter) (1.10.0)
Requirement already satisfied: prometheus-client>=0.8.0 in c:\program files\python310\lib\site-packages (from rq-exporter) (0.12.0)
Requirement already satisfied: deprecated in c:\program files\python310\lib\site-packages (from redis>=3.5.3->rq-exporter) (1.2.13)
Requirement already satisfied: click>=5.0.0 in c:\program files\python310\lib\site-packages (from rq>=1.8.0->rq-exporter) (8.0.3)
Requirement already satisfied: colorama in c:\program files\python310\lib\site-packages (from click>=5.0.0->rq>=1.8.0->rq-exporter) (0.4.4)
Requirement already satisfied: wrapt<2,>=1.10 in c:\program files\python310\lib\site-packages (from deprecated->redis>=3.5.3->rq-exporter) (1.13.3)
Step 2: Starting the exporter:
C:\Users>rq-exporter
C:\Program Files\Python310\lib\site-packages\redis\connection.py:72: UserWarning: redis-py works best with hiredis. Please consider installing
warnings.warn(msg)
[2021-11-19 15:01:26] [rq_exporter] [ERROR]: Incorrect RQ class location
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\site-packages\rq_exporter_main_.py", line 241, in main
REGISTRY.register(RQCollector(connection, worker_class, queue_class))
File "C:\Program Files\Python310\lib\site-packages\prometheus_client\registry.py", line 26, in register
names = self._get_names(collector)
File "C:\Program Files\Python310\lib\site-packages\prometheus_client\registry.py", line 66, in _get_names
for metric in desc_func():
File "C:\Program Files\Python310\lib\site-packages\rq_exporter\collector.py", line 55, in collect
for worker in get_workers_stats(self.worker_class):
File "C:\Program Files\Python310\lib\site-packages\rq_exporter\utils.py", line 70, in get_workers_stats
workers = worker_class.all()
File "C:\Program Files\Python310\lib\site-packages\rq\worker.py", line 123, in all
worker_keys = get_keys(queue=queue, connection=connection)
File "C:\Program Files\Python310\lib\site-packages\rq\worker_registration.py", line 47, in get_keys
return {as_text(key) for key in redis.smembers(redis_key)}
File "C:\Program Files\Python310\lib\site-packages\redis\commands\core.py", line 1769, in smembers
return self.execute_command('SMEMBERS', name)
File "C:\Program Files\Python310\lib\site-packages\redis\client.py", line 1067, in execute_command
conn = self.connection or pool.get_connection(command_name, **options)
File "C:\Program Files\Python310\lib\site-packages\redis\connection.py", line 1177, in get_connection
connection.connect()
File "C:\Program Files\Python310\lib\site-packages\redis\sentinel.py", line 45, in connect
self.connect_to(self.connection_pool.get_master_address())
File "C:\Program Files\Python310\lib\site-packages\redis\sentinel.py", line 113, in get_master_address
master_address = self.sentinel_manager.discover_master(
File "C:\Program Files\Python310\lib\site-packages\redis\sentinel.py", line 234, in discover_master
masters = sentinel.sentinel_masters()
AttributeError: 'Redis' object has no attribute 'sentinel_masters'
This is the error I am facing. Guide me where I did wrong or any pre-requisite thing I need to incomplete?

Hi,
Sorry about this, it seems that we have introduced a bug in the last version v1.9.0, please use the latest version v1.9.1 that was just published.
Please feel free to re-open this issue if you still have problems after trying the latest version.
Thank you.

@mdawar It's working fine on my windows machine.  Thank you for the response.
But, I am unable to install the RQ-exporter python package in my AWS-EC2 Linux box.
ubuntu@ip-xxx-xx-xx-xxx:/$ pip install rq-exporter==1.9.1
Collecting rq-exporter==1.9.1
Could not find a version that satisfies the requirement rq-exporter==1.9.1 (from versions: )
No matching distribution found for rq-exporter==1.9.1
ubuntu@ip-xxx-xx-xx-xxx:/$ python --version
Python 2.7.17
ubuntu@ip-xxx-xx-xx-xxx:/$ python3 --version
Python 3.6.9
ubuntu@ip-xxx-xx-xx-xxx:/$

@mdawar It's working fine on my windows machine. Thank you for the response.
But, I am unable to install the RQ-exporter python package in my AWS-EC2 Linux box.
ubuntu@ip-xxx-xx-xx-xxx:/$ pip install rq-exporter==1.9.1 Collecting rq-exporter==1.9.1 Could not find a version that satisfies the requirement rq-exporter==1.9.1 (from versions: ) No matching distribution found for rq-exporter==1.9.1
ubuntu@ip-xxx-xx-xx-xxx:/$ python --version Python 2.7.17
ubuntu@ip-xxx-xx-xx-xxx:/$ python3 --version Python 3.6.9
ubuntu@ip-xxx-xx-xx-xxx:/$

This problem could be related to caching.
Can you please try installing using a direct link to the wheel file:
pip install https://files.pythonhosted.org/packages/c1/73/d17738ae5fa7f1197736eee30537411ce5c64a80b118545b4ecdfa231c50/rq_exporter-1.9.1-py3-none-any.whl

If you're wondering, I got the link from the Download Files tab on Pypi.
This is temporary of course, when you try later it should be working fine.

@mdawar
Hi, I am getting a different error this time.
ubuntu@ip-xxx-xx-xx-xxx:/$ pip install https://files.pythonhosted.org/packages/c1/73/d17738ae5fa7f1197736eee30537411ce5c64a80b118545b4ecdfa231c50/rq_exporter-1.9.1-py3-none-any.whl
rq_exporter-1.9.1-py3-none-any.whl is not a supported wheel on this platform.

@mdawar
Hi, I am getting a different error this time.
ubuntu@ip-xxx-xx-xx-xxx:/$ pip install https://files.pythonhosted.org/packages/c1/73/d17738ae5fa7f1197736eee30537411ce5c64a80b118545b4ecdfa231c50/rq_exporter-1.9.1-py3-none-any.whl rq_exporter-1.9.1-py3-none-any.whl is not a supported wheel on this platform.

I have resolved this issue. In my Linux box, the default python version is 2.7 so that's why RQ-exporter is not installed with pip.
so I have changed the python version to 3.7. then it got worked with the previous command "pip install rq-exporter"
Thanks for your patience @mdawar. Really appreciated.

@mdawar Now my exporter is working fine.
But on the collected metrics page, worker metrics and jobs metrics are not showing.  What do I need to get those metrics well?
I have one running queue in my Redis?
Kindly help me. I am new to the Redis things and Prometheus monitoring...

@OjerDev Did you enqueue any jobs?
Please check out the Development section on the README, there's a full example of the exporter with scripts that enqueue jobs and workers that process them, also you can find the full Prometheus and Grafana dashboard setup, take a look at the docker-compose.yml file and the docker-compose directory.
You can start a full local development environment with docker-compose up.

@mdawar  Currently, I am not enqueueing any job.. And i have been told not to use docker developmenmt for this whole setup. so from the start, i am running this package manually.
And another thing, i have one custom queue running in my Redis and i need that queue stats only.  i have only the queue name and nothing more.
To achieve this one i need your guidance please..
Adding that, i have done the setup of prometheus and grafana. its working correctly.

@OjerDev As I remember, you need to enqueue jobs to start seeing the metrics, and in this setup you cannot get the historical queue stats, you only get the current queue metrics only and that's due to how rq provides this data.
It doesn't matter if you're using Docker or not, I was telling you to check the docker-compose setup just to see how things are configured, you can still use all of these configurations without Docker.
Also if you want realtime and accurate stats about the job queue, then this not the right tool for the job, Prometheus scrapes the exporter depending on the configured interval, so anything happening between those scrapes will be missed.

@mdawar Thanks for clarifying my doubt. Getting the current queue metrics is fine for me.  I have checked the custom scripts file in the path and I can see how you are configured and used the custom scripts in the docker-compose.yml file.
Are there any usage instructions for how to use these custom scripts in our exporter?

@mdawar Thanks for clarifying my doubt. Getting the current queue metrics is fine for me. I have checked the custom scripts file in the path and I can see how you are configured and used the custom scripts in the docker-compose.yml file.
Are there any usage instructions for how to use these custom scripts in our exporter?

Actually you don't use any of these scripts.
Let me clarify a couple of things, you don't need to add any extra code to be able to use this exporter, this exporter must be configured to connect to the Redis instance you're using for rq, that's it.
So you just use rq as you would without this exporter, this exporter runs as a separate service to provide the job/queue metrics for Prometheus to collect them, that's the only purpose of this exporter, and then it's up to you how you use these metrics and display them or create alerts or whatever.
I have provided an example Grafana dashboard to display these metrics but it's in no means a complete solution, it's just provided as an example.


-Fix tail

Description
Tail has been broken in the recent CLI changes. Pretty trivial (imo) oversight, adding the proper hierarchy in.
GitHub Issues
Fixes #546

Coverage remained the same at 80.762% when pulling edd0ad1d1afe1458c4ab6c402eb25ffa05a7a48c on narfman0:master into 60cd82436b9a352cd8aca8491b5f9202af3e0406 on Miserlou:master.

gahhh


Any way to force OmniSharp to always use .NET Framework 3.5 instead of 4?

Most of my work is in Unity3D, and I often get intellisense errors because OmniSharp is using .NET Framework 4 for intellisense, and Unity3D always uses .NET Framework 3.5.  This can be very problematic in some cases where I lose all intellisense for certain packages.  Is there a way I can compile OmniSharp such that it uses 3.5 instead of 4?

This is out of OmniSharp-vim scope, it falls under the server domain: Omnisharp-roslyn


mkctf-cli: command not found

Followed installation instructions to the tee and added ~/bin to $PATH. Installation of mkctf along with all dependencies installed without errors.
Issue:

mkctf-cli command not found
mkctf-* appears to be a broken link

Thank you! Just fixed a small but important typo in the README.md (see this commit).
Tell me if it solves your problem.
Regards

Yep, its working now. Thanks!


feat(helm): ✨ otel collector and metric templates and other changes

add templates for otel collector and otel collector metrics
single helper file for basic templates
single valid notes.txt
alertmanager api from env var

Signed-off-by: Prashant Shahi<EMAIL_ADDRESS>

@prashant-shahi Is it tested?

yes, it is tested manually.. and also CI lint and test passed

Cool :+1:

This is part of helm chart release signoz-0.0.6.
@pranay01 requesting for shipped love..


Upgrade Ruby version to 3.2.0

We should be using the latest version of Ruby possible. This branch should be tested before merging, as per https://docs.publishing.service.gov.uk/manual/ruby.html#update-ruby-version-in-the-relevant-repos. Trello card: https://trello.com/c/e5BZBWyK/3075-bump-platform-reliability-repos-ruby-versions-to-v3xx-5

I ran a Terraform plan using this branch on integration and it ran successfully - see the console output