s3 bucket

Approach
manually Configure

AWS MSK cluster backup into same AWS account

Prerequisites
1.Aws Account
2.Install Aws CLI
3.Require VPC, Subnet, Route table, Security Group
4.MSK cluster
5.Ec2 instance & install Java , Kafka
6.IAM role for client & backup
7.S3 bucket
8.MSK plugin
9.MSK connector
10.VPC Endpoint
Process

create S3 bucket in main aws account

Create IAM role for S3 bucket & attached policy for access object
3.Create MSK cluster provisioned attached VPC, subnet(different AZ), Security Group
broker- kafka.t3.small
Kafka version- 2.8.1(recommended)
4.Create Custom Plugin
download s3 sink connector-https://www.confluent.io/hub/confluentinc/kafka-connect-s3
and uploaded zip file into s3 bucket
MSK connect > custom plugin> s3 bucket
5.Create VPC endpoint
service name & type - com.amazonaws.us-east-1.s3 & Gateway
6.create Client Machine(EC2 Instance) with IAM role
instance type - t3a.small
AMI - Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type
connect Ec2 terminal> install Kafka > install AWS CLI >Install Java > create Topic
7.create connector
MSK connect> choose connector >existing plugin > add connector configure > IAM role for s3 bucket
8.send backup data to s3 bucket
create producer and add some massage
S3 bucket - MSK cluster data available in topic folder.

AWS MSK cluster backup into another AWS account.
1.create S3 bucket in account B and attached bucket policy.
2.Account A create IAM role for s3 bucket change trust policy for cross account access.

Restore data From S3 bucket to AWS MSK cluster into same AWS account.

downloaded s3 source connector-https://www.confluent.io/hub/confluentinc/kafka-connect-s3-source and uploaded into S3 bucket.
2.create Custom plugin
MSK connect > custom plugin> choose s3 bucket
3.create connector
MSK connect> choose connector >existing plugin > add connector configure > IAM role for s3 bucket
Note : connector getting fails

Description:
SonarQube is a static code analysis tool that helps identify bugs, vulnerabilities, and code smells in software projects. It provides detailed reports and insights to improve code quality and maintainability throughout the development lifecycle.Configure SonarQube in Azure Pipelines for automated code scanning, Install SonarQube, integrate it into your pipeline, and analyze code quality continuously to catch issues early and ensure high-quality code.
Approach:

sonarqube server install in ubuntu VM ware.
Java install
integration sonar to azure devops pipeline project.

Business value:
1.SonarQube improves code quality by identifying and addressing bugs, security vulnerabilities, and code smells.
2.It reduces technical debt by catching issues early in the development process, minimizing future maintenance efforts.
3.Enhanced security is achieved through early detection and remediation of vulnerabilities, reducing the risk of security breaches.
4.Early issue resolution with SonarQube saves costs that would otherwise be spent on post-release bug fixes.
Acceptance criteria :
1.SonarQube is successfully integrated into the Azure Pipelines.
2.Code analysis is performed automatically as part of the pipeline execution.
3.SonarQube generates detailed reports on code quality, security vulnerabilities, and bugs.
4.The reports provide actionable insights for developers to address identified issues.
5.The SonarQube dashboard displays accurate and up-to-date information on code health.
6.Continuous monitoring and improvement of code quality are ensured through scheduled pipeline executions.


Add "extension-css" option

It is the continuation of the merged extend-css into rustdoc.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Any news?

We generally don't add a configuration option for all rustc/rustdoc options, especially unstable ones. I think it's premature to add an entire Cargo.toml configuration option for this, and the best way to enable this functionality would probably be through RUSTDOCFLAGS similarly to how RUSTFLAGS are handled.

We can keep it open until it's in release version. However, wouldn't it shadow the feature to force people to use cargo flags instead of an option into Cargo.toml?

This will likely require something along the lines of an RFC for dealing with rustdoc options in general in Cargo. There are many more options that want to be specified beyond just this one (e.g. https://github.com/rust-lang/cargo/issues/331).

oops

Ah I've since created a PR for RUSTDOCFLAGS at https://github.com/rust-lang/cargo/pull/2794 so I'm going to close this in favor of that, thanks for the PR though!

Great! Your solution is indeed better. Thanks @alexcrichton!


how to handle routes?

how did you do to handle the whole application routes? is all declared at main.js? it's so bigger.how to split by service module?
thx very much.

application routes, what do you mean?
If you're talking about the angular ui-router routes, there are only 2, & they're all here:
https://github.com/preciousDev/angularMaterial-webpack2-ocLazyLoad/blob/master/app-content/main/main.js
Does that answer your question?

You can always separate routes into different module routes like Angular2-4 does it.
Just move them into different files and require them in main.js

Just made a commit with those changes added in.
Just add a file with the extension of .routes.js in the each module folder, and put in the routes in the file. It will automatically get imported in


System is arming (or thinks it is arming) even with Critical warnings

PX4 1.7.3, installed on a Pixracer, using QGC v3.3.0.  The pixracer is sitting on my desk connected to QGC over USB.  I have a valid GPS fix.  I try to Arm and it seems to let me even with the following Critical warnings:

Is this right?

however, once i fixed the compass rotation problem (that was giving the "MAG SENSORS INCONSISTENT" warning), then the system properly prevents arming:

Working on a fix here - https://github.com/PX4/Firmware/tree/pr-commander_preflight

I think it´s not so bad to allow arming for stabilized flights and reject only e.g. auto mission or rtl that is directly dependant to the sensor´s errors

@taileron I agree, but it needs to be done explicitly and I'm not entirely sure how we'd want to go about that.
Some of these requirements we could determine from the system configuration. For example if the user has and RC or data link loss failsafe configured for RTL then at arming time the system could require a valid global position estimate and valid home position.

@dagar some errors disappear when the fc runs a minute but mostly it is necessary to reboot the system to get rid of conditions that could prevent arming.
so what´s about to have the possibility or do it automatic: repeat the preflight check after 40 ... 120 sec when temperatures and reference voltages are more stable and more gps satellites than directly after boot, deleting all previous preflight errors + nsh "commander check" with current sensor values


Updated structure

-Updated folder structure

I have corrected the paths, now the website is working fine

Again it's not working @divyaagrawal261. Take your time fix the issues and then create a pull request don't rush


Feature/widgets pom record support

Feature/widgets pom record support

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

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- Ginger/GingerCoreNET/Application Models/Learn/POM/PomLearnUtils.cs  1
- Ginger/GingerCore/Resources/GingerHTMLHelper.js  1

See the complete overview on Codacy

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

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- Ginger/GingerCoreNET/Application Models/Learn/POM/PomLearnUtils.cs  1
- Ginger/GingerCore/Platforms/PlatformsInfo/JavaPlatform.cs  10
- Ginger/GingerCore/Resources/GingerHTMLHelper.js  1

See the complete overview on Codacy

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

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- Ginger/GingerCoreNET/Application Models/Learn/POM/PomLearnUtils.cs  1
- Ginger/GingerCore/Platforms/PlatformsInfo/JavaPlatform.cs  10
- Ginger/GingerCore/Resources/GingerHTMLHelper.js  1

See the complete overview on Codacy


SpeechGPT: Empowering Large Language Models with Intrinsic Cross-Modal Conversational Abilities

https://docs.google.com/document/d/1CgFtGrU9Zoh-su_ApokhC-wn5pliiWVtbDd5Lo9FJVo/edit?usp=sharing


Migrate user authentication

@joannechen1223 probably authentication is not something we want to change at this point, especially because other services will create additional costs, which I wish to avoid when not needed

See #91 for related discussion (not critical)

Is this something we still need? What's the current state of affairs with authentication?

We are using Firebase as auth provider now. I think it's good to close this now since we are not planning to migrate to other provider. We can reopen if we need.


For each inference service, add methods to learn tokens-per-minute and requests-per-minute limits

We need be able to adjust TPM/RMP limits dynamically.
If too hard, these should be user settings on coop.

@zer0dss This naturally goes w/ price look-ups.


Move from github link to crates.io reference for minstant now that it exists.

Current dependencies on/for this PR:

main

PR #21  (this PR)

This comment was auto-generated by Graphite.


Add "header" for compressed items

Since your main goal was to use it with localStorage (similar to mine). It would be interesting to prepend on the compressed string a kind of header. Something along the lines of data URIs in CSS but less verbose. Example:
"lz;<encoded data>"

In that way it makes easier to identify if the data being used is compressed or not.

That breaks compatibility - far better for you to do it yourself if there's a possibility it's not compressed.

Fair enough, I've done it myself, I just thought it would be a good "enhancement". Regarding compatibility that would be an easy fix, just add a version flag and check against that, or add some global options for LZString, for instance.

It's cross-platform and cross-language compatibility - there's no version string in it, just raw compressed data (which is where the command line archive tools wrap the raw data with all that extra info) ;-)

just add a version flag and check against that

As Rycochet mentioned: that's not so simple because the current format is pure a raw compression string without any metadata. However, I just wrote a proposal for how one might want to approach a newer format in a backwards-compatible way. Have a look.

@JobLeonard That's more like it! 😃 👏


 So you don't need to read this issue and just Close the issue since this is Lettuce Github Issue, Thank you.

no u

First time, i meet lettuce, It's very fresh.
Then i marry with Lettuce ,then i eat him, and i cook him, then i'm do something very cool then he'sbecomes cute Lettuce,
Ai lob yu Lettuce.


Add Oscillator alters Wave/Harmonic/Detune/Keyprop/WaveType of existing oscillators

Pressing the "+" button to add an oscillator should not alter existing oscillator properties.   However, it does.

Fixed for 2.4.0


change FACTORIO_PATH/FCONF

Easy change path to config

This will break cross-usage with systemd as the environment file is not passed via bash and cannot use "variables in variables", as such I'm forced to specify the absolute path in a string rather than passing a variable.

It is working, verified

ok thx


Centreline.displacement does not allow selection of road_id

The Centreline.displacement does not allow selection of road_id, which means a point in mapped to the nearest line geometry element. There is often a need to force the point to map to a specific geometry element, e.g. around ramps.

Added in v1.14

Updated to allow a list of road_ids. See version 1.15.


Array : when minItems=1 is specified, the user should not be allowed to removed the array item from the UI

Prerequisites

[x ] I have read the documentation;

Description
The UI should honor Array minItems and maxItems.
Steps to Reproduce

On the playground, (https://mozilla-services.github.io/react-jsonschema-form/) select Arrays.
Modify the JSON schema fragment as shown below:
 "type": "object", "properties": {  "listOfStrings": {    "type": "array",    "minItems": 1,    "title": "A list of strings",    "items": {      "type": "string",      "default": "bazinga"    }  }
Try deleting the items from the list of strings. You can delete all the items. You should not be able to delete items when the length reaches minItems.

However, you get validation error

This behavior sounds fair to me. Validation happens when you submit the form, except if you enabled the liveValidate feature then it's fair to have validation errors while fiddling with the form in real time.
Maybe users want to delete a bunch of stuff to reenter some others. Preventing removing items is more likely to create confusion and/or frustration in my own experience. What's important to me is that we get proper validation when the form is submitted, which works just fine here.

In my current app, we want the behavior of disabling the remove button when minItem is specified. Example when minItem=1 , delete button should be disabled when there is only on array item. Maybe there should one more configurable item in the UI configuration like disableminItemDelete:true. Let me know what do you think? and how to achieve this functionality

One option could be to use CSS to achieve that
hide the button when only one .array-item :
.array-item:nth-child(1):nth-last-child(1) .array-item-remove {
   display:none;
}

Actually, this was just one of the example. there are other instances where we have to disable add button when maxItem is specified. I was hoping as I framework, react-jsonschema-form should allow adding this functionality through UI configuration json. Let me know if this make sense from the framework perspective

I agree with @n1k0 -- rjsf doesn't try to prevent the user from entering nonvalidating information, and I don't think it should start here.

There are some drawbacks to this approach but you can use a fixed items with additionalItems. Drawbacks include not being able to remove the fixed items nor order them (i.e. items[0] will always be items[0]).
Example here.


Bump queue version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 28.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
888

Relevant Lines:
3093

💛  - Coveralls


fix: required={false} should work

Summary
Make sure setting required to false is working as expected.
Type

Bug

Summarise concisely:
Right now, if I set the required prop to explicitly false, it will be ignored and the field will be required. This PR fixes this issue

Codecov Report

Merging #464 (d4bc229) into main (b6a5a76) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #464   +/-   ##
=======================================
  Coverage   92.25%   92.25%
=======================================
  Files          26       26
  Lines         310      310
  Branches       37       37
=======================================
  Hits          286      286
  Misses         13       13
  Partials       11       11

Impacted Files
Coverage Δ

src/helpers/pickValidators.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d2020b2...d4bc229. Read the comment docs.


[SUPPORT]The file being written is in an invalid state. Probably caused by an error thrown previously. Current state: COLUMN

Describe the problem you faced
we are using flink compaction async.
sometimes, the same file group compact task will be distributed to different task manager even though the compaction plan distribute the compact task using keyby filegroupid(hudi-4397),
this will lead to the exception:
The file being written is in an invalid state. Probably caused by an error thrown previously. Current state: COLUMN
To Reproduce
Steps to reproduce the behavior:

job manager is killed and restart
2.all task managers register again
3.say task manager1 will be assigned different file group id compact task, which maybe distribute to task manager2 before task manager re-register

i noticed that, when task manager re-registered, the compact task will continue to run which started before this re-register happened
Environment Description

Hudi version : 0.11.0 + hudi-4397

flink version : 1.14.4

Running on Docker? (yes/no) : yes

@yuzhaojing @danny0405 : Can you folks follow up when you get a chance.

We have figured some reason in: https://issues.apache.org/jira/browse/HUDI-4880, can you help to validate with the fix ?

accept, thank you ~


gradio stucks on uploading the video

hi,
bro,your work is amazing ,but i met a problem

maybe try to downgrade to gradio==4.40.0?


add access property

resolves https://github.com/dbt-labs/dbt-docs/issues/381
Description
Adds access
no access defined

access: private

access: public

Checklist

[ ] I have read the contributing guide and understand what's expected of me
[ ] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

The issue specified to "display if available" but since we default to unprotected it is always available on models.  However, it won't show for other nodes.


Output channel Log (Window) does not appear until window reload for the first time

The log file is not present in the output pane or Developer: Open Log File..., I cannot investigate https://github.com/microsoft/vscode/issues/102107

Can you please check if this is same as - https://github.com/microsoft/vscode/issues/89559

@sandy081 Log (Window) is not in any of my 3 windows (2 are WSL Remote, 1 is Windows)

Yeah I can reproduce it too on stable, insiders & sources.
It seems reloading the window is showing the log.
After investigation, it seems file service is not returning a change event after log file got created. I wait until file exists and create the output channel after it is created.
https://github.com/microsoft/vscode/blob/0bbc57993bf2dc639d5bb415f5bceff2bc942ce4/src/vs/workbench/contrib/logs/common/logs.contribution.ts#L24-L89
@bpasero assigning to you.

@sandy081 running with --verbose there is literally no node.js file event coming in for the renderer log:
TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339
log.ts:173 TRACE [File Watcher (node.js)] [CHANGED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339/tasks.log
log.ts:173 TRACE [File Watcher (node.js)] [CHANGED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339/extensions.log
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [CHANGED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339/tasks.log
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [CHANGED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/output_1_20200711T075339/extensions.log
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/exthost1
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/exthost1
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/git.txt
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/microsoft-authentication.txt
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/github-authentication.txt
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/git.txt
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/microsoft-authentication.txt
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/github-authentication.txt
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/sharedprocess.log
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/telemetry.log
log.ts:173 TRACE [File Watcher (node.js)] [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/userDataSync.log
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/sharedprocess.log
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/telemetry.log
log.ts:173 TRACE [File Watcher (node.js)] >> normalized [ADDED] /Users/bpasero/Desktop/log-ws23344334333/logs/20200711T075338/userDataSync.log

If I just create the log after a timeout of 0 it appears, so maybe this file is created too soon for the watcher to get a hold of it:
setTimeout(async () => {
	const exists = await this.fileService.exists(file);
	if (exists) {
		outputChannelRegistry.registerChannel({ id, label, file, log: true });
		return;
	}
}, 0);

Moving back to you to decide if you want to add any workaround like that. Unfortunately it does not seem like node.js file watching gives me any API to know when the watcher is installed for good.

I will think about the workaround, but may I know why there is any change in file events from previous release to current release?

Workaround: Reloading Window shows the log.

Fixed it by reversing the order. Start watching and check for file existence. This avoids missing file event.
Reopening for candidate discussion.

I will think about the workaround, but may I know why there is any change in file events from previous release to current release?

Not that I am aware of.


docs: add mini.surround keybindings to readme

Thank you for this PR! However, those keymaps in the readme are auto-generated. I've updated the plugin spec so that they are now included in the readme.


hana::any_of()/if_() example code fails on the latest MSVC

Hey guys and gals, thank you for this awesome library!
I got a weird issue with hana::any_of() that I was even able to reproduce on godbolt: https://godbolt.org/z/6eaxaahYj
In short, even example code of hana::any_of() as described in the docs: https://www.boost.org/doc/libs/1_84_0/libs/hana/doc/html/group__group-_searchable.html#ga5f7ff0125c448983e1b96c3ffb84f646 fails on the latest MSVC, but compiles nice on (not so latest) gcc & clang.
I've encountered that using boost v1.84 from vcpkg baseline 898b728edc5e0d12b50015f9cd18247c4257a3eb, but I assume godbolt uses different baseline and maybe even version, and nonetheless it fails there too with exactly the same diagnosis:
boost/hana/eval_if.hpp(60): error C2446: ':': no conversion from 'const boost::hana::integral_constant<bool,false>' to 'const boost::hana::integral_constant<bool,true>'
boost/hana/eval_if.hpp(60): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
....

I tried /Zc:__cplusplus suggestion, but no luck...
My MSVC Version 17.9.6. cl.exe version
Microsoft (R) C/C++ Optimizing Compiler Version 19.39.33523 for x64

I'll very much appreciate suggestions how to fix that. I didn't expect such issue, honestly...

Same for hana::if_():

example https://www.boost.org/doc/libs/1_84_0/libs/hana/doc/html/group__group-_logical.html#gafd655d2222367131e7a63616e93dd080
result on MSVC  https://godbolt.org/z/cvejWKes6

eval_if() example works though: https://godbolt.org/z/rWvdvjPKv

I posted this as a potential bug in MSVC bug tracker and just got a reply from their compiler team, that it compiles with /Zc:ternary and indeed, it at least compiles: https://godbolt.org/z/sWeG3s3nv
I guess this concludes the ticket, so I'm closing it.


stm32h7:stm32h7x3xx_rcc - Fix Style

@anpaza - I  am Sorry this took so long and that you were dragged into this Nxstyle quagmire!
I did not push directly to your branch , because of a conversation Greg started on the dev mailing list about PR etiquette.
If these changes are Ok with you please merge them and I will merger the PR

@anpaza Any chance of you merging this?

Sorry, didn't understand you submitted a merge request.
Merged.

Haha, it doesn't pass nxstyle again.
What a mess.


Multiclass Semantic Segmentation using DeepLabV3+

Semantic segmentation with the goal to assign semantic labels to every pixel in an image is one of the fundamental topics in computer vision. Deep convolutional neural networks based on the Fully Convolutional Neural Network show striking improvement over systems relying on hand-crafted features on benchmark tasks. In this example, we would implement
the DeepLabV3+ model as proposed by the paper Encoder-Decoder with Atrous Separable Convolution for Semantic Image Segmentation for multi-class semantic segmentation.
Please find Colab Notebook here

Hi @fchollet can you please review this example?

Hi @fchollet thanks for the suggestions for improvement. I have updated the example as per your suggestions, can you please review?

Hi @fchollet I have updated the example as per your suggestions:

Added a brief description of the CIHP dataset.
Added a brief explanation of the inference and post-processing steps for visualization.
Changed AtrousSpatialPyramidPooling to DilatedSpatialPyramidPooling.

Can you please review?

Hi @fchollet , Added the generated files.

Upon closer review, I'd like to request one additional change (to be handled in a separate PR): please add a validation_data dataset in the call to fit(), and when visualizing the results, please use images from a validation or test set, rather than images from the training set. This is necessary to make sure that the model is capable of generalizing.

Upon closer review, I'd like to request one additional change (to be handled in a separate PR): please add a validation_data dataset in the call to fit(), and when visualizing the results, please use images from a validation or test set, rather than images from the training set. This is necessary to make sure that the model is capable of generalizing.

Hi @fchollet , I raised a new PR updating the example as per your suggestions. Please find it at https://github.com/keras-team/keras-io/pull/629


Fix project description "read more" button styling

What does this PR do and why?

makes "read more/less" button inline with the project description
improves responsiveness of project header

Screenshots or screen recordings

before
after

Acceptance checklist

[x] I have evaluted the Approval Guidelines for this PR.

@peripheralist 👋 lil clean up for you.

fabulous, love a good cleanup 😄
I just realized that i've been testing mobile dev on a small phone size for a while... which must be just behind a breakpoint, because for me the project header is always in a single column much more like your after. thanks for catching this!


Batch 2: ECR: Add AIA and PLIC interrupt controllers in MADT

Enable AIA and PLIC interrupt controllers in MADT.

The ECR is approved by ASWG on 05/18/2023. The approved version is here


Hard to stop GitHub auth dance

Attempt to sign in to GitHub via GHPRI, click Allow
Click Cancel

🐛 I now have to click twice No and once Cancel to stop the notification stream. I expected no extra clicks after step (2).
https://user-images.githubusercontent.com/22350/234018103-1757f6a7-7c07-4bab-b9c7-6dc41f8fd451.mov

3rd notification is my bug, 4th would be GHPR (@alexr00). Here's the PR for my side ^^^

Just verified this issue and seems okay, but I also noticed this:

Click to sign into github for an extension that needs it.

press cancel on the notification in vscode.

still go through the steps to authorize github in the browser and open the link that they give to open in vscode.

nothing happens :bug:. I get that nothing should change, but should there be a warning?

@andreamah what would you like to see in the warning in this case?

I'm not too sure. The state just leaves me sorta questioning whether the auth did anything I think. But looking at it again, I see that it doesn't do anything if it succeeds, so I guess silently failing also works?

I think I'd like air on the side of not annoying the user with yet another notification, so I think the silence is ok.


cloudapi: single uploadrequest

Change imageRequest to accept a single uploadRequest instead of
an array of uploadRequests.

Nice! Adding blocked until the related composer PR is merged (https://github.com/osbuild/osbuild-composer/pull/1267)

Thanks for a quick rebase and merge @Gundersanne :partying_face:


Add new service for querying compute systems' information

This PR adds a new service for use in querying compute systems for information. Currently only ComputeProcessorInfo is implemented to get processor count information. This can be expanded in the future as needed. Since the use case for this service is for ncproxy, this PR does not attempt to return processor count information for argons or containers themselves, only UVMs.
This PR additionally adds a test tool for using this service which is not meant to be used outside of dev testing.
Signed-off-by: Kathryn Baldauf<EMAIL_ADDRESS>

I would like to focus a bit on ensuring we have excellent commit/PR descriptions. Having information in the commit is especially important (rather than just the PR), so that it's present outside of GitHub. Some good information to think about when writing a commit description is:

Why do we need this change/why is this change important?
Overall architecture of the change
Any specific gotchas, edge cases, or implementation details that readers should be aware of
Any testing/analysis done

In this case your PR description has some of this, but the commit is empty. It would also be helpful to understand better why we need the change, and a high level sense of what the changes consist of.

I would like to focus a bit on ensuring we have excellent commit/PR descriptions. Having information in the commit is especially important (rather than just the PR), so that it's present outside of GitHub. Some good information to think about when writing a commit description is:

Why do we need this change/why is this change important?
Overall architecture of the change
Any specific gotchas, edge cases, or implementation details that readers should be aware of
Any testing/analysis done

In this case your PR description has some of this, but the commit is empty. It would also be helpful to understand better why we need the change, and a high level sense of what the changes consist of.

@kevpar I've updated the commit message to include details that you've mentioned. Let me know if there's any information you'd like included that I didn't add.

It would be great to have a test that starts Linux, Windows (process), Windows (hv-iso) containers and validates we get the correct result from them via QueryCompute.


[Question] Multi-Admin in Same fabric for Linux - Example/Documentation

Device#1 Ubuntu as commissioner using chip-tool #fabric1
Device#2 ESP32 Lightbulb endnode #fabric1
Device#3 Ubuntu - Please some one can help me to understand following,
is chip-tool can be used as multi-admin administrator? for Device#3
How to provision Device#3 in fabric1, command line argument to commissioning device#3 as administrator.

is chip-tool can be used as multi-admin administrator? for Device#3

Yes.  You can copy over the storage from Device #1 (so that the generated private keys are available, etc), and then run chip-tool on Device #3 with a non-default commissioner node id.
Device #1 would need to set up the right ACLs for this, of course.


Error running render-example.sh example script

While running one of the example scripts I am running into following issue:
./render-example.sh arch ../vgg16_weights.h5
Only using analogy loss
Using Theano backend.
Using gpu device 0: Tesla K80 (CNMeM is enabled with initial size: 90.0% of memory, CuDNN 3007)
Using brute-force model
Scale factor 0.25 "A" shape (1, 3, 116, 80) "B" shape (1, 3, 128, 89)
Building loss...
Precomputing static features...
Traceback (most recent call last):
File "/usr/local/bin/make_image_analogy.py", line 5, in
pkg_resources.run_script('neural-image-analogies==0.0.11', 'make_image_analogy.py')
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 528, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1401, in run_script
exec(script_code, namespace, namespace)
File "/usr/local/lib/python2.7/dist-packages/neural_image_analogies-0.0.11-py2.7.egg/EGG-INFO/scripts/make_image_analogy.py", line 27, in
File "build/bdist.linux-x86_64/egg/image_analogy/main.py", line 69, in main
File "build/bdist.linux-x86_64/egg/image_analogy/models/base.py", line 23, in build
File "build/bdist.linux-x86_64/egg/image_analogy/models/analogy.py", line 23, in build_loss
File "build/bdist.linux-x86_64/egg/image_analogy/models/base.py", line 53, in precompute_static_features
File "build/bdist.linux-x86_64/egg/image_analogy/models/base.py", line 61, in get_features
File "build/bdist.linux-x86_64/egg/image_analogy/models/base.py", line 72, in get_layer_output
AttributeError: 'Convolution2D' object has no attribute 'get_output'
Any idea what is wrong here. Any help would be really appreciated. Thanks

I solved this, apparently in Keras 1.0.2 get_output() is deprecated. Change the following code in model.base.py:
self._f_layer_outputs[name] = layer.get_output()
to
self._f_layer_outputs[name] = layer.output
worked for me.


AddValidationKeys missing

Hello,
It looks like this method might be missing in the latest release (3.0.1).  This is within the following file for v2.5.3:
IdentityServer4/src/IdentityServer4/src/Configuration/DependencyInjection/BuilderExtensions/Crypto.cs
Is this intentional?
Thanks

Yep - I think I removed it when we added support for multiple signing algorithms.
You can call AddValidationKey multiple times instead I think.

Thank you for the quick response, and this great project!


Mock C extension module: the case of Pyqt

I have not been able to successfully make shims for PyQt. (Some projects shim some of the pyqt submodules but not all of it.)
I imagine that the special case of pyqt (4 or 5) is sufficiently common for it to be useful for other people, hence the issue.
Is there anyone who has a good example of how to mock pyqt for readthedocs? Would it be in scope for readthedocs to handle pyqt?

I have thought about an extension that provided automatic mocking for common modules that require mocking. It's nothing I've ever bothered to write though. It would still require the user not install those dependencies first, which is where most users hit issues in the first place.
I've also thought maybe RTD should inspect dependencies and warn, but that's definitely a ways off our current roadmap.
To successfully mock out qt dependencies, make sure you aren't setting any qt dependencies via setup.py and/or requirements.txt. You should be able to mock out the modules normally, afaik.

Hi @SylvainCorlay! I wanted to check with you if you still have this issue? If you already solve it, can you please share your solution?
Besides, I found similar situation on these issues https://github.com/rtfd/readthedocs.org/issues/2387 and https://github.com/rtfd/readthedocs.org/issues/2511 that you may find useful.
I'm closing this issue since it's quite old and there was no updates. Please, feel free to reopen it if you consider.


[clarification]: Keyset pagination, what should happen when the order is not defined?

Specification
https://github.com/jakartaee/data/blob/main/spec/src/main/asciidoc/repository.asciidoc#restrictions-on-use-of-cursor-based-pagination
I need clarification on ...
At the specification, there is this point:

Sort criteria must be provided and should be minimal.

But what happens if the user does not inform any Sort element?
Using the same spec example:
@Repository
public interface Products extends CrudRepository<Product, Long> {
    CursoredPage<Product> findByNameLike(String namePattern, PageRequest<Product> pageRequest);
}

In this case, I will remove the Order method:
float priceMidpoint = 50.0f;
PageRequest<Product> pageRequest =
    //Order.by(_Product.price.asc(), _Product.id.asc()) removed, please, ignore if it will compile or not
PageRequest
             .pageSize(10)
             .afterKey(priceMidpoint, 0L);
CursoredPage<Product> moreExpensive =
        products.findByNameLike(pattern, pageRequest);

Additional information
No response

PageRequest<Product> pageRequest =
    //Order.by(_Product.price.asc(), _Product.id.asc()) removed, please, ignore if it will compile or not
PageRequest
             .pageSize(10)
             .afterKey(priceMidpoint, 0L);
CursoredPage<Product> moreExpensive =
        products.findByNameLike(pattern, pageRequest);

The example you gave is a user error for two reasons.
One reason is that it violates the rule from the specification that you cited:

Sort criteria must be provided and should be minimal.

The second reason is there is also a requirement for the size of the sort criteria to exactly match the number of key components of the cursor.  In your example, you have 2 key components supplied to afterKey but the size of the sort criteria is 0.
The example usage can be rejected on the basis of either of these.

Thanks, @njr-11; my question is, what exception should I throw?

IllegalStateException
UnsupportedOperationException
DataException
a Jakarta Data provider

I would recommend IllegalArugmentException because the user has supplied a PageRequest argument that is not appropriate for cursor-based pagination -- it has no Sorts and its number of key components does not match the amount of sort criteria.

I agree, that was my thought too.


Looking up elements via selectors is not supported by jqLite

Hi,
I'm seeing the following when using the library. Angular 1.6.3 app.
Error: [jqLite:nosel] Looking up elements via selectors is not supported by jqLite! See: http://docs.angularjs.org/api/angular.element
http://errors.angularjs.org/1.6.3/jqLite/nosel
at angular.js:66
at JQLite (angular.js:3188)
at compile (angular.js:8849)
at appendSpinnerTpl (angular-promise-buttons.js:116)
at Object.link (angular-promise-buttons.js:206)
at angular.js:1341
at angular.js:10413
at invokeLinkFn (angular.js:10419)
at nodeLinkFn (angular.js:9808)
at compositeLinkFn (angular.js:9048) ""
Any ideas why this would happen?

@johannesjo Thanks for getting back to me so quickly 🙂 I did not specify a custom BTN_SELECTOR anywhere. Should I be doing this?

That's weird. I'll check this once I'm back from lunch.

Thanks 🙏🏼

I tried to reproduce this issue with no luck. Can you maybe provide a plunkr doing that?


Implementing "Sibling Rivalry" Method from "Keeping Your Distance: Solving Sparse Reward Tasks Using Self-Balancing Shaped Rewards" Paper

🚀 Feature
I propose the implementation of the "Sibling Rivalry" method, as outlined in the paper "Keeping Your Distance: Solving Sparse Reward Tasks Using Self-Balancing Shaped Rewards." Link to GitHub: https://github.com/salesforce/sibling-rivalry
This method offers a novel approach to solving sparse reward tasks in reinforcement learning (RL) by utilizing self-balancing shaped rewards, particularly effective in goal-reaching tasks.
Motivation
While training a PPO agent to play the Battle City game, I've encountered a significant challenge: the agent more or less learns to eliminate enemy tanks but fails to protect the base, often resulting in suboptimal strategies like camping near the enemy spawn spot. I tried everything I could think of to make it defend the base, but it seems to default to camping or doing nothing. This behavior indicates that the agent is stuck in a local optima, focusing solely on tank destruction and neglecting the critical objective of base defense. Implementing the "Sibling Rivalry" method could potentially enable the agent to recognize situations where the base is in danger, encouraging it to learn strategies that involve defending the base rather than just attacking enemies. I hope that this method might help it to avoid this local optima and it might be the key to overcoming the current limitations in the agent's learning process.
Pitch
I suggest integrating the "Sibling Rivalry" method into the PPO algorithm. This would require adapting the code in base/learners/distance.py of the GitHub repository and integrating it into the PPO class as an option.
Alternatives
Currently, other methods like intrinsic curiosity models and reward relabeling strategies are used, but they often show limited performance in hard exploration scenarios. The "Sibling Rivalry" method outperforms these techniques, especially in diverse environments like 3D construction and navigation tasks.
Additional context
This issue has been moved from the DLR-RM/stable-baselines3 repository. Also, I know little about writing proper code and I do not have the technical skills to implement something so complex. I will give it a try anyways, but I'm probably better off with a simpler task like benchmarking it.
Checklist

[X] I have checked that there is no similar issue in the repo
[X] If I'm requesting a new feature, I have proposed alternatives

Original issue: https://github.com/DLR-RM/stable-baselines3/issues/1802


NumPy project endorses SPEC 6

After an extensive review and discussion with the maintainers and developer community, the NumPy Steering Council came to a consensus on endorsing SPEC 6.

Adding my +1

Sorry, happy with endorsing, I hadn't posted immediately, because I am not sure if there were any open discussions/opinions on this one.


Folder browse mode, quicker file operations.

Broken record here 👋🏽
*Aves really needs a folder browse mode.
Simple gallery, Pictures and F-Stop gallery has it.
This way files can be much faster organized than creating groups or categories by utilizing File Managers.
*Please make all files access permission or otherwise to speed up file operations. Deleting or moving files asking for folder access to each new directory is cumbersome and slow. The blue circle of death is what I call the percentage dialogue.
Please dev 🥺

ملاحظة جيدة

Aves is not a file manager.


Create support matrix

We should have a simple matrix for our KubeVirt-to-K8s version support. This repo seems like the logical place for it.
Context:
> We are confused if 0.58 supports k8s 1.25.
v0.58.0 has not been tested against k8s 1.25. It should work though, but if you need 'official' support statement, you probably need to switch to the latest KubeVirt v0.59.0.

It will be really helpful if you can provide the documentation that specifies the compatibility matrix for various versions.

Yeah, that is now missing. Agree, it would be useful to have such a matrix.
Originally posted by @vasiliy-ul in https://github.com/kubevirt/kubevirt/issues/8482#issuecomment-1477355609

On it.

Fabian's PR #9982 on kubevirt/kubevirt added version support and lifecycle information to docs/release.md.
I still think it would be useful to have a matrix in this repo that clearly shows the version's currently supported plotted against the supported k8s versions, but there would be overhead to keep it current.

Completed by #13