output path

Is your feature request related to a problem? Please describe.
when running bin/console make-to <destination-path> <make-command>
./bin/console make-to /home/http/perso/prestashop/modules/vueseclatees/src/src/Command make:command
I was expecting for the output file to be at home/http/perso/prestashop/modules/vueseclatees/src/src/Command but it's on
home/http/perso/prestashop/modules/vueseclatees/src/src/Command/src/Command/BackgroundScrappingCommand.php
This means, I should write ./bin/console make-to /home/http/perso/prestashop/modules/vueseclatees/src/ make:command
Describe the solution you'd like
just the inforamtion on the doc :D

Ah yep exactly! You have to enter the project destination path. Entering the very final destination of the file is not conceivable to me since most of Symfony make commands (and the make commands I'll add in the future) alter/create multiple files in different locations. User can still arrange files afterwards as he wants to.
By the way, it's better to use this tool when the destination project is under version control so you can see/revert the changes that have occurred.
Anyway: indeed, everything will be clearer with the README... 😅

yep, nice explanation.

Should now be clearer with the new README!

I consider it as done.
Feel free to re-open it if you think it can be improved!


[NDSL] Microphysics port

Located at GEOS_GFDL_1M_InterfaceMod.F90:GFDL_1M_Run. Many subroutines. Everything under Run should be considered for port.
Parent: https://github.com/GEOS-ESM/SMT-Nebulae/issues/57

[ ] G002.4.1 is done
[ ] G002.4.2 is done
[ ] Subtasks further if needed
[ ] Port to GFDL_1M to pyMoist

Flowchart to track progress here

Deal with RHCRIT3D from evap/sublc loop not being computed


Set up Google Analytics

See https://docs.wagtail.io/en/v2.3/topics/writing_templates.html?highlight=preview#varying-output-between-preview-and-live for excluding google analytics from wagtail preview pages.

Nothing to test. Ready for deploy to production in the next release.


Website UI Design Guide

Create a style guide/branding guide for the Zarf product website (MUI)

[ ] - Typography
[ ] - Colors
[ ] - Icons
[ ] - Images

Website stories all moved to https://github.com/defenseunicorns/zarf-website


Massive conversions in opflow - lack of control for algorithm users

Opflow has several places where its conversion to matrix is gated via a massive param that defaults to False e.g here https://github.com/Qiskit/qiskit-aqua/blob/008337ec340946f5ef5872a60b5975096a6ec9bc/qiskit/aqua/operators/list_ops/list_op.py#L283
This is fine perhaps if directly working with opflow - however when coming from algorithms, such as VQE, such calls are inside the implementation that calls upon opflow such that the user sees ValueError getting raised but there is no way they can alter massive that the error suggests.
It maybe too much to expose such a param directly on these algorithms etc in Aqua - maybe having some global setting in opflow (or via Aqua using aqua globals) that allows control over such matrix conversion limits might be a more accessible solution that allows users to change this such that internal conversions can proceed (subject to memory etc which is the reason it was gated in the first place).

@woodsp-ibm , do we have an understanding about the priority of this issue?


spawn points still working from prev scans

so i finally logged on the map and stopped the scanning just so i could view the points which i noitced still change colors.. ive always been alittle confused on what the colors ment if someone could explain that to me as well as the spawn timers. example one says every hour from 3:25 to 18:25 or 50:01 to 05:01 what exactly does that mean

timers give you the timetable already like your samples, spawn point become active every houer from 3 minute and 25 second to 18 minute 25 second or 50 minute and 1 second to  next hour 5 minute 1 second. every spawn point will be active for 15 minutes.
green means active, when time running it change colour to yellow. orange-red means nearly time out. grey is inactive and blue close to become active.

Thank you that makes reading it so much easier. I found the cache folder on my pc. Any recommend programs to get to actually be able to read those files? I run Windows 10

I believe there was another migration, most of the spawns are all different timers


fixing reused OWL and other properties

some of the properties reused from OWL were broken by use of a different letter case, e.g. VersionIRI instead of versionIRI. This will break RDF

Thanks @nicholascar. Good catch. It seems this was indeed a few errors.
Since MOD1.4 is now archive, I will fixe directly the archived file... and verify its ok in MOD2.


Add immutable to Rollup.sol/BatchManager.sol to reduce SLOAD

What's wrong
#455

In terms of gas-saving, the most significant reduction is gas per batch rollback, which is from 4958 to 4354 (Rollback 249 batches is from 1234592 to 1084244 ).
That's because the paramMinGasLeft was a SLOAD but now a constant
https://github.com/thehubbleproject/hubble-contracts/blob/ddf6cb94fbb92dab9c1a3f253fcab26d6213c10b/contracts/rollup/BatchManager.sol#L85-L86


init grpc doc

started a doc page for grpc related things

Nice! We'll probably need to iterate on it over time given new developments and feedback, but this is good enough to merge now


Typography - link style

link style in blog is getting double underline
we would keep the blue underline and use Brown for inline link

Cleaned up the extra underlines in content in production and on this blog post on the test site so you can check.  Set inline link font to use Brown font.

inline link is 18px, slightly smaller than 20px Lyon so the x-height match!

underline looks a bit too close to the text, try make the underline perhaps 0.1 em further away form the text?

I forgot we have smaller text size for small viewport! Link style for S should also be smaller, 14px

Adjusted link text size for small viewport


Linux epoll event resubscribe optimization

Prior to this change, if ONE_SHOT is enabled, linux epoll based
asio wouldn't be subscribed for certain events after another
event was fired on the same FD.
The specific scenario was the following:

Register event E for READ/WRITE with ONE_SHOT.
E fires for READ and a message is placed on the message queue
for the TCPConnection actor.
TCPConnection actor eventually gets to processing this message
(after processing any other messages ahread of this one on the
queue) and then goes through the work of _event_notify. At
the end of _event_notify, _resubscribe_event is called and
epoll is told to resubscribe for READ and/or WRITE events as
required.

Normally, this wouldn't be an issue but the behavior we're seen
is that with ONE_SHOT, if a READ (or WRITE) event is fired, all
events for the FD are disabled. This means that in the above
scenario, when the READ event is fired, the WRITE is also
disabled along with the READ because of ONE_SHOT.
We could (and did) try adding a call to _resubscribe_event in
_event_notify before any processing is done to resubscribe
earlier but there were two problems with this. First, it still
meant that the other event was unsubscribed for the duration of
the time the asio event notification message was sitting on the
message queue of the TCPConnection actor. Second, it resulted in
a race condition and incorrect use of epoll where the TCPConnection
actor would ask epoll to resubscribe to either READ or WRITE when
the event had already fired and was waiting on the message queue.
For the READ event case, this is incorrect use of epoll because
the manual for epoll strongly indicates that when using ONE_SHOT
and Edge Triggering all data should be read from the socket before
it is resubcribed again.
The final design we settled upon is to move the readable/writeable
flags into the Event structure, split the resubscribe for READ
and WRITE events, and have epoll automagically resubscribe to the
untriggered event if ONE_SHOT is enabled. This ensures there are
no race conditions because the decision to resubscribe is based on
the the state of the readable/writeable flags on the event which is
always up to date based on the latest events that fired. It also
ensures that we resubscribe to the untriggered event as soon as
possible because the epoll asio thread takes care of it.

The event now holds the readable/writeable flags.
This is only safe because the asio thread will only
write to those flags if there's a subscription for an event.
In order to avoid two threads writing/reading to the new flags
at the same time, the resubscribe for reads and writes has been
split.
Additionally, the epoll code will now automagically resubscribe
to the un-triggered event in order to minimize the delay for when
an event is triggered for ONE_SHOT code so it behaves the same
as for kqueue ONE_SHOT where if an FD is subscribed with ONE_SHOT
for both read and write events and a read event fires and
is disabled because of ONE_SHOT, the write event is still left
enabled. This also greatly simplifies where/when resubscribes
need to occur in the TCPConnection actor.
Update kqueue code to also split readable/writeable resubscribe.

Side note. We've been running with this for 4-6 weeks now a Sendence (I think its been that long), without issue.

Also, just wanted to say thank you for the very thorough and detailed ticket description / commit message! :heart:

Makes sense. Thanks for your feedback on things and the suggested improvement.

That description was so good, by the time I read the code, I knew exactly what it did and what I was looking for. Looks good to me, thanks @dipinhora !


refactor(scripts): allow importing without extension

Current dependencies on/for this PR:

main

PR #175   👈

This stack of pull requests is managed by Graphite.


remove source from jsk_apc and jsk_common

May I ask why you want to remove the source entries?

If I understand correctly, this entry triggers
http://build.ros.org/job/Idev__jsk_apc__ubuntu_trusty_amd64/
This package is failing due to missing dependency (?? Maybe)
And we're resting on Travis , also contribute not to apply heave load on
ros buildfarm
2016年4月21日木曜日、Dirk<EMAIL_ADDRESS>
May I ask why you want to remove the source entries?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ros/rosdistro/pull/11183#issuecomment-212515450

--
◉ Kei Okada

Removing the entry prevent users to compile the latest code from source using e.g. rosinstall_generator. You can only opt-out of the devel jobs by setting test_commits: false within the source section (see REP 143). (While the REP says that the default value is already false the ROS build farm overrides the default to be true in order to provide devel jobs out-of-the-box.

I see, updated to use test_commits and test_pull_request

Please remove the test_pull_requests entries. Their default value is already false.

And the test_commits entry needs to be in alphabetical order.

I see, fixed


This test isn't passing.


how about LiteOS_Migration_Guide_keil.md

two docs based on DISCO-STM32F429 with keil
one is the LiteOS_Migration_Guide_keil.md, the other one is LiteOS_Migration_Guide_stm32f429_Keil.md
which is standard?

《LiteOS_Migration_Guide_keil.md》for common migration guide,《LiteOS_Migration_Guide_stm32f429_Keil.md》for device driver。


Add SDO acknowledgment for Sun image

Desired attribution is: "Courtesy of NASA/SDO and the AIA, EVE, and HMI science teams."

In #256


Manage part of files

When using Ansible/Chef/Puppet I try to strictly stick to package install, create config file and start/manage service. But sometimes it's very hard since you need to manage part of a file, ex add DNS to ifcfg-* files.
Ansible lineinfile is great for this and saved me multiple times (it's not perfect but so much better than all other sed solutions I seen...).
It would also be nice to improve on this design by allowing multiple lines instead of single lines.
Ansible blockinfile solves some of the multiple lines situations, but sadly some files ex /etc/environment don't support comments.
Very exciting to see where converge will be going 👍

Thanks for your feedback! We're adding this to our roadmap.


[BUG]/ Incosistent state of rating & favourite button

after pressing rating 4+ / favourite button when search button pressed, though the rating / favourite filter is removed, they are still being highlighted.
https://github.com/Anandsg/Hungry-hero/assets/127688631/97db6d7a-7683-4e66-9558-eecfc16f3f36

@Anandsg please assign it to me

please add hacktoberfest tag before merging


Doc change for cockroach init

Document the cockroach init command
Update 1.1 prod deployment docs

Revise workflow to use init command
Use includes wherever possible

Update 1.1 cockroach start docs
Use init command in 1.1 core feature demos
Update formatting on 1.1 local deployment docs
Make 1.1 build an app tutorials single-node only

Fixes #1288
Fixes #1718

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/806ad3d352bd4a0323eb1a4296e137b8f8595390/

@bdarnell, for now, I didn't change the "Start a Local Cluster" tutorials because revising them to focus more on single-node local deployment is a broader project. The risk of leaving the pages as-is, though, is that users might be surprised or confused that the workflow is different once they get to prod deployment. Thoughts?

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f5e06063f1b0ad623428022992069c056d80f046/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/80dbfb6e38702ab61bd35d5e8bbd9bcee8608b40/

Yeah, the updates to the "local cluster" docs can come in a separate change.

Reviewed 28 of 28 files at r1, 3 of 3 files at r2, 1 of 1 files at r3, 1 of 1 files at r4, 1 of 1 files at r5, 4 of 4 files at r6.
Review status: all files reviewed at latest revision, 7 unresolved discussions, all commit checks successful.

_includes/prod_deployment/insecure-requirements.md, line 1 at r6 (raw file):

- You must have SSH access to each machine with `root` or `sudo` privileges. This is necessary for distributing and starting CockroachDB binaries.

It's necessary for the instructions we use here, but it's not true in general. It's entirely possible to run cockroach without root/sudo permissions (that's what we do on our own test clusters). The only thing in our instructions that needs root is putting the binary in /usr/local/bin, which we only do because it's easier than giving detailed instructions about modifying your $PATH (alternatively, we could use ./cockroach in all the instructions so it doesn't need to go on your path. This is what I normally do)
The insecure requirements should have the same page.ssh_link trick as the secure ones.

_includes/prod_deployment/insecure-requirements.md, line 4 at r6 (raw file):

- Your network configuration must allow TCP communication on the following ports:
	- **26257** (`tcp:26257`) for intra-cluster and client-cluster communication

Repeating the port here is weird. What's the tcp:26257 syntax for?

_includes/prod_deployment/secure-generate-certificates.md, line 125 at r6 (raw file):

	~~~

    {{site.data.alerts.callout_success}}In later steps, you'll use the root user's certificate to run cockroach client commands from your local machine. If you might also want to run cockroach client commands directly on a node (e.g., for local debugging), you'll need to copy the root user's certificate and key to that node as well.{{site.data.alerts.end}}

Since the remaining steps all assume the node has a copy of the root cert, we should include the scp command for that here (but describe it as optional)

_includes/prod_deployment/secure-recommendations.md, line 4 at r6 (raw file):

- Decide how you want to access your Admin UI:
  - Only from specific IP addresses, which requires you to set firewall rules to allow communication on port `8080` *(documented on this page)*.

Is that supposed to be a link?

_includes/prod_deployment/secure-recommendations.md, line 5 at r6 (raw file):

- Decide how you want to access your Admin UI:
  - Only from specific IP addresses, which requires you to set firewall rules to allow communication on port `8080` *(documented on this page)*.
  - Using an SSH tunnel, which requires you to use `--http-host=localhost` when starting your nodes.

Is that required? That's unfortunate. We should file an issue about that if there's not one.

v1.1/deploy-cockroachdb-on-aws-insecure.md, line 21 at r6 (raw file):

## Requirements

You must have SSH access ([key pairs](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html)/[SSH login](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html)) to each machine with root or sudo privileges. This is necessary for distributing binaries and starting CockroachDB.

We should add the platform-specific links here to the See Also section (or as additional links in this section after the include)

v1.1/start-a-node.md, line 20 at r6 (raw file):

# Start a multi-node cluster:
$ cockroach start <flags, including --join>

This command should end with & so it goes into the background (otherwise you won't get another prompt to be able to run cockroach init)

Comments from Reviewable

Review status: all files reviewed at latest revision, 7 unresolved discussions, all commit checks successful.

_includes/prod_deployment/insecure-requirements.md, line 4 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Repeating the port here is weird. What's the tcp:26257 syntax for?

Don't remember why that was there. Removing.

_includes/prod_deployment/secure-generate-certificates.md, line 125 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Since the remaining steps all assume the node has a copy of the root cert, we should include the scp command for that here (but describe it as optional)

Which remaining steps require the root cert on the node? I think they all run client commands from the local machine?

_includes/prod_deployment/secure-recommendations.md, line 4 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Is that supposed to be a link?

No, I think it's meant to just call out that our tutorials go the route of opening the port via the firewall. I'll just remove that.

_includes/prod_deployment/secure-recommendations.md, line 5 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Is that required? That's unfortunate. We should file an issue about that if there's not one.

Checking with @mberhault.

v1.1/deploy-cockroachdb-on-aws-insecure.md, line 21 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
We should add the platform-specific links here to the See Also section (or as additional links in this section after the include)

Can you clarify which platform-specific links you mean?

v1.1/start-a-node.md, line 20 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
This command should end with & so it goes into the background (otherwise you won't get another prompt to be able to run cockroach init)

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cd4bdfea64820e81b038f2b2c624d35cc87ee96c/

Review status: 35 of 38 files reviewed at latest revision, 4 unresolved discussions, all commit checks successful.

_includes/prod_deployment/secure-generate-certificates.md, line 125 at r6 (raw file):
Previously, jseldess wrote…
Which remaining steps require the root cert on the node? I think they all run client commands from the local machine?

Oh, the insecure instructions say "ssh to any node" and run it there, but the secure versions say to run it locally. I missed that because I paid more attention to the insecure versions (since they come first alphabetically). This discrepancy between secure and insecure mode is strange and we should run client commands locally in both cases.

_includes/prod_deployment/secure-test-cluster.md, line 55 at r7 (raw file):

	~~~

6. Use **CTRL + D**, **CTRL + C**, or `\q` to exit the SQL shell.

On windows (if you're running this locally instead of sshing to any node), it's ctrl-z instead of ctrl-d (i know \q works anywhere, and i think ctrl-c does). But ctrl-d/ctrl-z is probably the most "normal" way to do this.

v1.1/deploy-cockroachdb-on-aws-insecure.md, line 21 at r6 (raw file):
Previously, jseldess wrote…
Can you clarify which platform-specific links you mean?

Sorry, I meant to delete/rewrite this comment. I meant that we should the page.ssh_link for the insecure docs too.

Comments from Reviewable

_includes/prod_deployment/insecure-requirements.md, line 1 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
It's necessary for the instructions we use here, but it's not true in general. It's entirely possible to run cockroach without root/sudo permissions (that's what we do on our own test clusters). The only thing in our instructions that needs root is putting the binary in /usr/local/bin, which we only do because it's easier than giving detailed instructions about modifying your $PATH (alternatively, we could use ./cockroach in all the instructions so it doesn't need to go on your path. This is what I normally do)
The insecure requirements should have the same page.ssh_link trick as the secure ones.

Removed that bit about root/sudo, and added the ssh_link to the insecure docs. Thanks for catching that.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8c12cdf42ccb369a47458a673f8d8a0e6e8a1848/

v1.1/deploy-cockroachdb-on-aws-insecure.md, line 21 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Sorry, I meant to delete/rewrite this comment. I meant that we should the page.ssh_link for the insecure docs too.

Done.

Comments from Reviewable

_includes/prod_deployment/secure-recommendations.md, line 5 at r6 (raw file):
Previously, jseldess wrote…
Checking with @mberhault.

Revised, with help from Marc.

Comments from Reviewable

Review status: 18 of 38 files reviewed at latest revision, 5 unresolved discussions, some commit checks pending.

_includes/prod_deployment/secure-test-cluster.md, line 55 at r7 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
On windows (if you're running this locally instead of sshing to any node), it's ctrl-z instead of ctrl-d (i know \q works anywhere, and i think ctrl-c does). But ctrl-d/ctrl-z is probably the most "normal" way to do this.

I'll go with just \q or ctrl-c, since they'll work everywhere.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/0b45fc405769479d951fef29e415972f9162dd8b/

_includes/prod_deployment/secure-generate-certificates.md, line 125 at r6 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Oh, the insecure instructions say "ssh to any node" and run it there, but the secure versions say to run it locally. I missed that because I paid more attention to the insecure versions (since they come first alphabetically). This discrepancy between secure and insecure mode is strange and we should run client commands locally in both cases.

Updated the insecure docs to run client commands locally.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f195da9db214a07387d05c5572b7cf58e3e180f2/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e60198ebcfc7407351e688732834ef1a3f234365/


It can't work well in Windows 11

I find that the line of Terminal is too long that the Windows icon is broken.

I found this would happen a while ago when I ran it from visual studio terminal but I never thought there would be a case where the terminal would be this long in normal use, I will look into this

When I use it in full screen, it looks like that （the picture I have put before）, and when it is not in full screen, it will be more terrible, like this:

I found that if I use cmd or powershell instead of pwsh7, it will be better.
like this:

and this:


Reintegrate skeleton-docker into repository

🗣 Description
This PR would reintegrate the cisagov/skeleton-docker skeleton into this repository.
This was done by adding the correct skeleton repository as a remote, pulling from its develop branch, and resolving any conflicts shown.
git remote add skeleton https://github.com/cisagov/skeleton-docker.git
git remote set-url --push skeleton no_push
git pull --allow-unrelated-histories skeleton develop
git status

After skeleton was merged, fixed pre-commit issues that showed up.

💭 Motivation and Context
When this project was created, it was not started using the skeleton tool This prevents the lineage GitHub Action from automatically generating PRs to ensure downstream repositories are kept up-to-date.

🧪 Testing
Automated tests pass.

📷 Screenshots (if appropriate)
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@zenine07 FYI, I made the DOCKER_USERNAME and DOCKER_PASSWORD secrets available to this repo.  That should help you out.

@dav3r Why do we need the multiplatform builds? Am I able to just disable that? I'm having a lot of issues getting it to work, but I'll keep trying.

I'm not really up-to-date on the Docker buildx stuff, but I think that we should build on those platforms unless there's a good reason not to.  @felddy or @jsf9k - can you offer any other thoughts here?

@dav3r Why do we need the multiplatform builds? Am I able to just disable that? I'm having a lot of issues getting it to work, but I'll keep trying.

I'm not really up-to-date on the Docker buildx stuff, but I think that we should build on those platforms unless there's a good reason not to. @felddy or @jsf9k - can you offer any other thoughts here?

The main reason I can think of is this is an internal application at the moment and know exactly what platform we're deploying it on. I can't see this being loaded on a Rasberry Pi or an IBM Main Frame.

Instead of committing src/AdminUI/src/assets/htmlhelp/de_search/0xu0036.json et al, not disable the JSON linting for htmlhelp like you did with .prettierignore?  I'd prefer to be consistent about whether we're going to lint the autogenerated html help stuff.

@jsf9k I had that idea too, but it didn't look like the check-json hook had the ability to ignore a directory.

Can we remove the now-empty files src/AdminUI/amplify/backend/backend-config.json and src/AdminUI/amplify/team-provider-info.json?

@jsf9k I believe those are already removed, I'm not seeing them anywhere.

Instead of committing src/AdminUI/src/assets/htmlhelp/de_search/0xu0036.json et al, not disable the JSON linting for htmlhelp like you did with .prettierignore?  I'd prefer to be consistent about whether we're going to lint the autogenerated html help stuff.

@jsf9k I had that idea too, but it didn't look like the check-json hook had the ability to ignore a directory.

Did you try adding an exclude line like we do here?

Can we remove the now-empty files src/AdminUI/amplify/backend/backend-config.json and src/AdminUI/amplify/team-provider-info.json?

@jsf9k I believe those are already removed, I'm not seeing them anywhere.

Interesting.  The diff under the "Files changed" tab of this PR lists it as an empty file instead of a deleted file.  I don't see it in the branch either, though, so I guess you are correct.  Withdrawn!

@zenine07 Did you try adding an exclude line like we do here?

@dav3r @jsf9k That did the trick, missed that. I actually had a new export of the help documents I needed to merge in, so I merged those and added the exclude to the checks that were failing. Once everything passes, I'll re-request your reviews.


Workspace name in terrakube can contain characters not supported in terraform cloud name block.

Feedback
Seems the workspace name in terraform can't contain spaces or slashes. I dont' know if a parsed name can be used. Tried the 'id' in the name field but this created a new workspace with the ID as the name.

Thank you for your feedback, I guess we can add some validation for the workspace name un the UI


Branch issue 21

fixes #21
Updated the User Guide for v1.1.
Can someone help to try to test by running npm run serve in the docs directory? Thanks!

Thank you @zsh-eng for the review! I have fixed and updated the changes in the commits above!


WIP - template panel context issues

As I've now encountered an issue myself where the #910 changes caused problems, possibly related to some of the others, probably I should try and fix them all up.
As a short reminder, after template based widgets came along, and before #942 landed, I tried to ensure the number of calls to pprint.pformat was kept to a minimum, as it is an expensive calculation (#933).
In doing so, the call changed from: try: ... pformat(value); except: ... to use force_text instead of pformat. This was, in hindsight, a mistake, mostly around usages of Form instances.
Because __str__ on a Form will by default render the form, it has a number of side-effects:

The repr won't get used if the rendering causes an SQL query to be triggered (ie: most forms!) (one I've now encountered)
The form instance can have full_clean called on it because the __str__ includes error printing (one I've now encountered)
Possibly subsequently prevents forms from rendering correctly at all? (#989)

In an ideal world, we could just change to repr (#725) instead of force_text, as this is similarly lightning fast. Instead, to err on the side of caution, I've opted for calling pprint.saferepr instead, which is protected against recursive data structures.
This has the benefit of still being faster than pformat (as far as I can tell) and avoids a certain class of problems the other options bring. But it's much slower than calling repr or force_text
directly.

Marking as WIP because there's a number of other issues (#989, #1024, #1053, #725) are related, and one option is just to undo the changes I made to avoid too many pformat calls. Also there's no tests ;)

Makes sense to me. Thanks!


proot-rs

This is a GSoC 2021 project. Once it is complete I will submit a PR to add it.
See: https://github.com/proot-me/proot-rs

Thant's great!


Running model failed: Invalid argument: Session was not created with a graph before Run()!

Hello, I`m have an error while testing plugin...
"Running model failed: Invalid argument: Session was not created with a graph before Run()!"

I fixed it using older version 1.4 of tensorflow to build model


[Cherry-pick][Enhancement] Reduce header_lock time in PrimaryKey Table (#6424)

In the gc process of primaryKey table, scanning RocksDB may take a lot of time, which will lead to long time to hold header_lock, reduce the holding time of header_lock
What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

starrocks_be_unittest succeeded.


v08 - fix ContinueAs data field assignment

Signed-off-by: spolti<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
What this PR does / why we need it:
Special notes for reviewers:
Additional information (if needed):

relates to https://github.com/serverlessworkflow/sdk-go/issues/70

interesting, I requested @lsytj0413  to re-review and it remove you @ricardozanini lol

/lgtm


Ruby's highlighting doesn't work on nested brackets in some cases

Version: v9.8.0
I found that highlighting for Ruby is not working within nested brackets in some cases.
I'm afraid similar issues might occur as well on other nested braces/parentheses etc.
not nested

nested

Thank you,

Can you confirm this is still an issue?  A jsfiddle reproducing would be great.
You can fork my template:
https://jsfiddle.net/ajoshguy/nagkqytv/18/

Awesome. :-)


Errors produced when navigating away from a page while a table is loading

Setup

Rancher version: 2.6.5
Browser type & version: Electron (Cypress)

Describe the bug
I have been developing Cypress-based end-to-end tests, which tend to click around faster than normal users.
When navigating away from a page which has a table, if the table is not done loading at click time, Javascript errors will be produced thereby failing the test.
To Reproduce
Ideally, follow reproduction instructions to get to the exact same environment I used (in AWS via Terraform).
At that point comment code in https://github.com/moio/scalability-tests/blob/20221003_300_pods_per_node/cypress/cypress/support/commands.js#L14-L15 and re-run the Cypress test.

@moio Please can you provide the console output including the errors, and also supply an issue title? At some point it would be worth migrating to the e2e framework the dashboard provides (which will be kept up to date with breaking changes)

@richard-cox you are totally right. As it may take me some time before I get back to you with the exact error, I am closing this issue and will reopen it when I have better data - no need to clutter your issues list in the meantime.
I also take your suggestion to look into the dashboard e2e tests at some point.
Thanks


Composer names

This is entirely just a nice-to-have idea, but it would be neat to list the name of the composer of each song (which can be retrieved from the official soundtracks, or other places). That could then be put in the song info portion or in a separate portion of the song data.

Please note that this repository for the plugin is not being maintained, and this issues page is not monitored. Issues should be brought up here: https://github.com/lmcintyre/OrchestrionPlugin
I would actually like to do this, but some tracks are missing composer data entirely, or it may be misattributed, which would cause people to just assume it's correct until new information comes out. Just a very time-consuming thing to do.


Crashes on server

Crash Report: https://pastebin.com/C4z01cJ6

I honestly have no idea why this crash is happening, I've never seen anything like it.
One fix you could try is using
Fabric Api 0.37.2+1.17
and
Fabric Loader 0.11.6


Add service providers to Context

Let's add a ServiceProvider which can be used to bulk register items into a Depository. The contract may look something like:
interface ServiceProvider {
    public function register(Depository $depository): void {}
    public function provides(string $class): bool {}
}

And then we add support in the Depository.
class Depository {
    public function addServiceProvider(ServiceProvider $provider): this {
        $provider->register($this);

        $this->providers[] = $provider;

        return $this;
    }
}

And also have auto-resolution support using the provides() method.

See pull request https://github.com/titon/framework/pull/69


Class 'App\User' not found if not using default 'App' namespace

Laravel Version: 5.5.5
Voyager Version: 1.0.0
PHP Version: PHP 7.0.22
Database Driver & Version: Mysql 5.7.19

Description:
Class 'App\User' not found generating optimized autoload files if not using default 'App' namespace
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover

  [Symfony\Component\Debug\Exception\FatalThrowableError]
  Class 'App\User' not found

Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

Installation failed, reverting ./composer.json to its original content.

Steps To Reproduce:

create L5.5 new fresh project

php artisan app:name MyNamespace

composer require tcg/voyager

This can be updated by editing the config, here is a relevant line of code.
https://github.com/the-control-group/voyager/blob/2c0f2713a34d1503a447ab50119e4515f25b0ad0/src/Commands/AdminCommand.php#L114

Change the setting like @CodeBradley said

Isn't it possible for Voyager to get the User model class from config/auth.php?

Yes, and we may choose to change that at some point, but for now @CodeBradley's comment is correct.


why is fao catalogue wms preview not shown

Description
record is
https://soilwise-he.containers.wur.nl/cat/collections/metadata:main/items/04111166-39d6-4d25-befe-14e8af3f0c91
getcapabilities is
https://data.apps.fao.org/map/gsrv/edit/pak_hih/wms?request=getcapabilities
it has a layer DHI
Environment

operating system:
Python version:
pycsw version:
source/distribution

[ ] git clone
[ ] DebianGIS/UbuntuGIS
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):

web server

[ ] Apache/mod_wsgi
[ ] CGI
[ ] other (please specify):

Steps to Reproduce
Additional Information

check https://github.com/geopython/pycsw/pull/1042

solved


[Question]: When will UIE support English Event Extraction?

请提出你的问题
I am wondering when UIE will support English Event Extraction.

This will be much appreciated. Thank you!!


Update dependencies

Webpack 5 changed how JSONs are imported, so I just decided to replace the service JSONs with TypeScript files. I think this is better anyway, for correctly detecting the types. I'll have to update the CLI as well.
I had to delete my whole node_modules folder and reinstall everything to make the build work.

Even after deleting node_modules I get A LOT of errors like this:

ERROR in ./node_modules/<EMAIL_ADDRESS>1:0-46
Module not found: Error: Can't resolve './setPrototypeOf' in '\universal-trakt-sync\node_modules@material-ui\core\node_modules@babel\runtime\helpers\esm'
Did you mean 'setPrototypeOf.js'?
BREAKING CHANGE: The request './setPrototypeOf' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '.mjs' file or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
<EMAIL_ADDRESS>3:0-60 50:2-11
<EMAIL_ADDRESS>1:0-36 1:0-36
<EMAIL_ADDRESS>175:0-47 175:0-47 176:0-26 176:0-26
@ ./src/modules/history/HistoryApp.tsx 2:0-46 55:39-48
@ ./src/modules/history/history.tsx 9:0-42 16:105-115

Those were the errors I was getting as well. Oh also make sure to delete
the package-lock.json or pnpm-lock.yaml file.

Are you ok with using pnpm instead of npm? The reason why I added package-lock.json to .gitignore is because I personally use pnpm (so does the CI), since it's faster and uses less space disk.

oh. right. I personally use Yarn. Which was why I initially got this error I think. I completely forgot about the yarn.lock-file. If you recommend pnpm, i'll be happy to test it out.

I'm down to switch to Yarn too, we just have to choose one and ensure that it's used everywhere.
I've never used Yarn, but the reason why I prefer pnpm over npm is because if you have, for example, 50 repos that all use the same package and same version, with npm it will create 50 copies of that package in each repo's node_modules, while with pnpm it will store all packages in a single central folder and then use symbolic links in each repo's node_modules, so you only end up with 1 copy of the package that is referenced across all repos.

It really just important whenever anyone updates the package.json, and since that is usually you I leave that decision to you. For anyone not updating package.json, npm, pnpm, and yarn would probably work anyways.

Ok, I'll keep pnpm then, since it's already using it, so no changes are needed.


INTLY-3044 apicurio product info

currently, for the product apicurio, we are displaying the display
name as apicurito. this is now incorrect and we should instead be
using api manager.
this change replaces the display name for apicurio with api
designer.
verification:

run yarn start:dev
open the main page of the solution explorer
ensure the apicurio service is now api designer
if running against a cluster, ensure the link still works as
expected

@pb82 @tiffanynolan Mind taking a look?

@aidenkeating API Designer or API Manager (because in the PR description its API Manager)? Otherwise LGTM.


Create a GitLab-based demo repo alongside the GitHub version

The demo repo for GitLab similarly should serve two purposes:

showing how the result will look like
running the CI pipeline on GitLab and making sure that everything works (e.g. using this)

open question is which GitLab instance it should be hosted on?

this could be useful https://github.com/jakob-fritz/github2lab_action


build error with butterknife8.8.1 on gradle 3.0.1

What went wrong:
A problem occurred configuring project ':app'.

Failed to notify project evaluation listener.
com.android.build.gradle.api.BaseVariant.getOutputs()Ljava/util/List;

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

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

This is fixed on master. You can use 9.0.0-SNAPSHOT for now.

thanks for reply, but it still build failed, not sure whether I've set the wrong config:
A problem occurred configuring root project 'AssistantVertu'.

Could not resolve all files for configuration ':classpath'.
Could not find com.jakewharton:butterknife-gradle-plugin:9.0.0-SNAPSHOT.
Searched in the following locations:
https://dl.google.com/dl/android/maven2/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/maven-metadata.xml
https://dl.google.com/dl/android/maven2/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.pom
https://dl.google.com/dl/android/maven2/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.jar
https://jcenter.bintray.com/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/maven-metadata.xml
https://jcenter.bintray.com/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.pom
https://jcenter.bintray.com/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.jar
http://maven.aliyun.com/nexus/content/groups/public/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/maven-metadata.xml
http://maven.aliyun.com/nexus/content/groups/public/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.pom
http://maven.aliyun.com/nexus/content/groups/public/com/jakewharton/butterknife-gradle-plugin/9.0.0-SNAPSHOT/butterknife-gradle-plugin-9.0.0-SNAPSHOT.jar
Required by:
project :

Try:

thanks for reply, but after I use 9.0.0-SNAPSHOT, it reports java.lang.NullPointerException


Write a Java program to find surface area of a cube

Description
Write a Java program to find surface area of a cube
Surface area of cube = 6 × Side^2
Side : 2

Surface area : 24

How to contribute

Save the solution in FindSurfaceAreaOfACube.java file
Add FindSurfaceAreaOfACube.java file in find-surface-area-of-a-cube folder

!assign


Fix node rules in plugin/n

I noticed that our node config was still referencing rules that are deprecated in eslint proper and moved to the n plugin.
I'm assuming these haven't been working as expected since the upgrade to eslint 8 so I'm not sure how much of a downstream impact they will have. Notably,

global-require is off by default, this turns it on
no-process-exit is on by default, this turns it off

If there have been no issues or comments against this in the past 18 months it may be worth considering removing these rules completely

If there have been no issues or comments against this in the past 18 months it may be worth considering removing these rules completely

We definitely fixed the no-process-exit errors last time we upgraded. The global-require may be deprecated, but I don't think it was removed so it was still being triggered on the eslint side.
Either way, I think this PR is fine. I'll merge and publish.

@jjspace FYI this is published.


Pixhawk ESC 1.6 does not boot up properly when fw flashed with CAN adapter

We are able to flash the vectorcontrol fw to the SV2470VC with the USB-CAN adapter from Ben without problems but when doing the same to the Pixhawk 1.6 ESC it does not work. The ESC keep reinitializing
and does not spin or give feedback.
However, when flashing the fw to the Pixhawk 1.6 ESC it works. (Except for the performance issues #12 )

I am unable to reproduce this issue—I use the CAN adapter exclusively during development and firmware always loads fine. What application firmware image did you load when you observed the restarting behaviour?

The issue is present on all fw:s (e.g. 544c8_gcc4_8_3_sverling) that get passed the flashing stage, i.e. #14

Please could you send through a log of the process from starting ui.py through to after the ESC has restarted a few times?

After updating the gui hash: 68e34de6 we are able to flash the fw in 68e34de6_gcc4_8_4_Ben to the Pixhawk ESC 1.6 with the CAN-Adapter

thanks for fixing @bendyer and verifying @CarlOlsson !


Flaky test: TestHttpProbe/returns_the_status_code_if_the_request_is_successful

Occurrences:

https://github.com/jesusprubio/up/actions/runs/9686542637/job/26729185707
https://github.com/jesusprubio/up/actions/runs/9686388900/job/26728671722

Hi, please check the following pull request:
https://github.com/jesusprubio/up/pull/55


Unable to publish message to RabbitMQ

Expected Behavior
I'm using the Dapr .NET sdk and using PublishAsync method to publish messages to rabbit MQ. I expect the message to be published without any issues. I'm using it in Kubernetes. The code can be found at Daprpubsub. The code is also attached herewith.[DaprPubsub.zip]https://github.com/dapr/dotnet-sdk/files/6820240/DaprPubsub.zip)
The configuration of the Rabbit MQ is perfect. The component definition is perfect. The dapr SDK is able to reach the rabbit MQ. In fact in the rabbitmq exchange, I was able to find an exchange created with the name of the topic name. There are
Actual Behavior
No Queue is getting created and Message is not present
Steps to Reproduce the Problem

Install Rabbit MQ in the Kubernetes cluster using Helm from https://charts.bitnami.com/bitnami
Update the component file with the amqp configuration.
apply the component in the same name space as that of code
Deploy the code.
Execute Kubectl get svc and get the Loadbalancer external IP of the service daprpub. The port will be 5045..
Assuming the external IP is something like localHost. Access the URL as http://localHost:5045/swagger. The swagger page will be displayed
In the Swagger UI access the Put in queue method. The method executes without any exception.

Thanks

Ant help in this regard will be greatly appreciated.

Attached is the log from application. Is there any help that can be offered
logs.txt

Did you also install Dapr onto the cluster beforehand? Your code is fine so I suspect there is something missing in your deployment. Your logs are for the applications so I would look at the app sidecar and dapr pods logs too.  I would look at the health of your cluster too.
Also, these references might be useful:
https://github.com/dapr/quickstarts/tree/master/hello-kubernetes and https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-deploy/

@jbw ,
I have attached the Dapr logs from Sidecar
Daprlogs.txt
here with. Yes I followed the above instructions only to deploy Dapr to K8s. I had deployed before hand itself

The logs don't contain anything for daprsub sidecar. If correctly configured you should see something like:
app is subscribed to the following topics: [topic name] through pubsub=pubsub" app_id=...
Your issue is with K8s so I would suggest looking at the example application in the links above and being able to observe the status of your cluster by inspecting logs, pods, etc using kubectl.
In the namespace dapr-system, there should be a dapr-dashboard deployment which you can port-forward into which might help also tools like Lens give a visual look into your cluster which can make it easier to inspect.

@jbw,
I have redeployed my application and did the steps once again. I'm not able to get the same working. I'm attaching the logs that I received.
applog.txt
dprSidecarlog.txt
As you told I have also port forwarded the dapr dashboard. In that, in the overview section Dapr Application sections, I see "daprpub" application. What else can I do firn what is wrong

@jbw any suggestions to resolve this issue

I've raised a PR on your repo to demonstrate. You can close this issue now. It's not a Dapr issue.

@VenkateshSrini @jbw - is there anything else to resolve here? This sounds like a general troubleshooting discussion and not a bug in the SDK.

@rynowak ,
Yes I have installed Dapr first then only the app.

Given the age of the issue, and the general nature of the question, I'm going to close this. If you still need help, feel free to reopen this issue or open a new one.


How to push commits to main branch without using pull requests?

I tried pushing my squashed commits after I pushed commits I want to join to the main branch, but the error message Required status check "continuous-integration/appveyor/pr" is expected. appeared and I failed.
I also tried pushing my commits that are reviewed by AppVeyor (of course those have the same commit id), but the same message appeared.
What do I need to do to push commits to the main branch without using pull requests?

Try directly commiting changes to main, without any merging strategy (just take your changes you may have done in a side branch and re-commit them in main manually). My last few commits were all direct and I had no problems pushing them.

Are you sure the status check allows collaborators to push commit directly?
You can directly push commits without passing the status check because you don't have Include administrators in Branch protection rule enabled, but collaborators can't.

Yikes. Try again now. Still requires linear history, but status checks are off.

Yeah, I can push my commits directly now.


Update performance docs for 16-bit depth format with no stencil buffer

Add content to explain potential issue with 16-bit depth buffer format sharing. There will be no stencil buffer created per Unity documentation
https://docs.unity3d.com/ScriptReference/RenderTexture-depth.html
Related issue:
https://github.com/microsoft/MixedRealityToolkit-Unity/issues/5970
Also cleaned up some spacing and newlines

Docs Build status updates of commit 331471e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/performance-recommendations-for-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/recommended-settings-for-unity.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Power Apps: Create seed data file

Done in Deploy workflow.
Data is available at https://github.com/OneWeekBreathe/Breathe/tree/main/data


#85

Dear Team,
The about us and contact us page is ready for the respective website just we need to add the respective data like(email, address, and phone number. I would Update the fonts for the site soon.
Requesting to provide the contact section details for the respective users.

Why have you made the top bar fixed?
Why there is a big gap between search bar and icons?
Where are you adding the contact info?

Why have you made the top bar fixed?
Why there is a big gap between search bar and icons?
Where are you adding the contact info?

Navbar: That looks good that's why but sir if you don't like it I will make that same as before.
I will check for that gap sir.
For any inconveniences if someone wants to connact, because in many websites it's good to show the team contact details. Other wise many people think low quality firm.

Conclusion: I will make the Navbar like previous and remove that gap, please confirm me for the contact details if you say I will remove that too.

Please make it the same as before
Over time we evolved to know what our needs are. We have added LinkedIn, facebook and insta id so that people can connect with us.

Please make it the same as before
Over time we evolved to know what our needs are. We have added LinkedIn, facebook and insta id so that people can connect with us.

Ohk sir, I will make it as before. With just About Us section


EF.Core 2.0  If model has non virtual complex type property  сonfigured with key "OwnsOne"

I modifed test project to use complext type in test
modelBuilder.Entity<Person>().OwnsOne(u => u.Widget);
    public class Person
    {
        [Key]
        public virtual Int64 Id { get; private set; }
        ...
        public  Widget Widget { get; set; }
        ...
    }

System.InvalidOperationException : The property 'Widget' on entity type 'Person' is being accessed using the 'Property' method, but is defined in the model as a navigation property. Use either the 'Reference' or 'Collection' method to access navigation properties.

I am not sure if this is related to your problem, but I got the same error message today. While searching for a solution, stumbled upon this issue. I solved my problem and I am posting my findings here in case someone else stumbles here also.
public class Person
    {
        public long Id { get; private set; }
        public  Widget Widget { get; set; }
    }

public class Context : DbContext
{
    ...
    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
          modelBuilder.Entity<Person>.OwnsOne(x => x.Widget);
    }
}

I was trying to optimize the SQL generated by EF, and wrote something like this :
context.Entry(Person).Property(x => x.Widget).IsModified = false;
According to the error I got, replacing "Property" with "Reference" solved my problem.
context.Entry(Person).Reference(x => x.Widget).IsModified = false;


Enhancement: Expose the faker instance

Summary
Hi, currently switching to PolyFactory from pydantic-factories.  🎉
Having access to the faker instance for generating data is useful, as was requested in https://github.com/litestar-org/polyfactory/issues/79 and implemented in https://github.com/litestar-org/polyfactory/pull/81
Thank you!
Basic Example
class MyFactory(ModelFactory[MyClass]):
    """Factory."""

    __model__ = MyClass

    optional_override1 = ModelFactory.get_faker().pystr

    complex_override = Use(lambda: f"{ModelFactory.get_faker().pystr()}/{ModelFactory.get_faker().pystr()}")

Drawbacks and Impact
No response
Unresolved questions
No response

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

You can already access the faker instance: MyFactory.__faker__. All factories are guaranteed to have a Faker instance as well. You can change the Faker instance by giving a different value for __faker__ as well.

Oh I feel like dunderscore properties would be considered "private" and maybe change unexpectedly.  But maybe it's just me.   I can work with MyFactory.__faker__.
Thank you

@lindycoder the dunderscore properties are not private and are part of the public API. The reason they're named as such is so that we can easily differentiate between them and the classmethods you may define to generate the value as documented here.


Cannot import ImageDataGenerator from tensorflow.keras GPU version

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04.6 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.1.0
Python version: 3.7.5
Bazel version (if compiling from source): None
GCC/Compiler version (if compiling from source): None
CUDA/cuDNN version: 10.1/7.3.1
GPU model and memory: GeForce RTX 2080Ti 10989MiB

Describe the current behavior
I am transfering from TensorFlow 1 to 2 and my codes are all running correct in TensorFlow 1.13 & 1.15. I met the problem when I try to import the ImageDataGenerator: no matter to use tf.keras.processing.image or tf.python.keras.processing.image.
Describe the expected behavior
In TensorFlow 1.13 & 1.15 and TensorFlow 2.0.0 CPU version, using from tensorflow.keras.preprocessing.image import ImageDataGenerator can import the ImageDataGenerator normally. But for TensorFlow 2.1.0 GPU version, it shows error even I add .python right after tensorflow. Here "CPU version" or "GPU version" means the hardware status of the PC I use.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
from tensorflow.keras.preprocessing.image import ImageDataGenerator # option 1
from tensorflow.python.keras.preprocessing.image import ImageDataGenerator # option 2
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
For now the only way I think it can work is to revise the content in "init.py" in somewhere within the TensorFlow package. But it will not be a good solution so I wonder if anyone can help me with this. Thanks.
2020-03-26 11:24:47.107325: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer.so.6'; dlerror: libnvinfer.so.6: cannot open shared object file: No such file or directory 2020-03-26 11:24:47.107424: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer_plugin.so.6'; dlerror: libnvinfer_plugin.so.6: cannot open shared object file: No such file or directory 2020-03-26 11:24:47.107442: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:30] Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly. Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/home/daiwei/.conda/envs/daiwei_tensorflow/lib/python3.7/site-packages/tensorflow/__init__.py", line 50, in __getattr__     module = self._load()   File "/home/daiwei/.conda/envs/daiwei_tensorflow/lib/python3.7/site-packages/tensorflow/__init__.py", line 44, in _load     module = _importlib.import_module(self.__name__)   File "/home/daiwei/.conda/envs/daiwei_tensorflow/lib/python3.7/importlib/__init__.py", line 127, in import_module     return _bootstrap._gcd_import(name[level:], package, level) ModuleNotFoundError: No module named 'tensorflow_core.keras'

@TMaysGGS, I have tried to reproduce the issue in google colab but i found no error. For your reference link of gist is here

@TMaysGGS, I have tried to reproduce the issue in google colab but i found no error. For your reference link of gist is here

Hi, @khimraj ,
Thank you for you reply. I tried it in Colab too and no error occured. Could it be a problem by me wrongly installing the denpendencies or the order I installed all the necessary packages?
And it is also weird that I can import tensorflow.keras in TensorFlow 2.0.0 CPU ver, but I have to import tensorflow.python.keras in TensorFlow 2.1.0 GPU ver. Since for now I do not have a third computer it is hard for me to prove where the problem is located... The functions I need to import are:
from tensorflow.keras.models import Model
from tensorflow.keras.layers import Input, Dense
from tensorflow.keras.optimizers import Adam
from tensorflow.keras.utils import plot_model, multi_gpu_model
and I have to change them to the codes below to successfully import the functions for tf 2.1.0 - gpu:
from tensorflow.python.keras.models import Model
from tensorflow.python.keras.layers import Input, Dense
from tensorflow.python.keras.optimizers import Adam
from tensorflow.python.keras.utils.vis_utils import plot_model
from tensorflow.python.keras.utils.multi_gpu_utils import multi_gpu_model

The problem seems to be partially solved. The "No module named 'keras_preprocessing" error is because when I install TensorFlow 2.1.0 a new version of Keras-Preprocessing package is installed also, and then after I use "pip uninstall keras-preprocessing=1.xx" to remove the old version, the new version of Keras-Preprocessing package is somehow damaged or deleted partially, which causes the module not found but can be imported. Thus the error I showed above should not be a bug of TensorFlow. I am sorry to bother.
Besides, the import restriction that I need to add ".python" when I try to import packages in tensorflow.keras (tensorflow.python.keras) cannot be reproduced in any other computer. I used one Windows PC with CPU only and another one with GPU Nvidia 1080 Ti, and using "from tensorflow.keras import xxx" is always working. So I wonder if this is a bug or something else, though it is not a severe problem. Now I just always use "tensorflow.python.keras" for consistency.
Now I am closing the issue and sorry again for bothering.


When will the next Aniyomi stable update be releasing ?? Please add aniyomi preview and beta features to stable version in this update ...🍀📌

Describe your suggested feature
The stable app hasn't been updated for hell 4 months 😖
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

Rejoice!


Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2022-05-12T18:11:56+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio_release-1.14
b75e9638e95858dfb55d7d09646f4558cedc4784
link
true
/test unit-tests_istio_release-1.14

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio_release-1.14

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.14
b75e9638e95858dfb55d7d09646f4558cedc4784
link
true
/test integ-pilot-multicluster_istio_release-1.14

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster_istio_release-1.14


Too many raw_bitcasts in SIMD code

What is the feature or code improvement you would like to do in Cranelift?
During translation from Wasm to CLIF, a combination of Wasm's v128 type and Cranelift's current type system forces us to add many raw_bitcast instructions between operations. For example, this Wasm code:
  (func (export "add-sub") (param v128 v128 v128) (result v128)
    (i16x8.add (i16x8.sub (local.get 0) (local.get 1))(local.get 2)))

Translates to this CLIF code:
function u0:4(i64 vmctx [%rdi], i8x16 [%xmm0], i8x16 [%xmm1], i64 fp [%rbp]) -> i8x16 [%xmm0], i64 fp [%rbp] system_v {
    ss0 = incoming_arg 16, offset -16

                                ebb0(v0: i64 [%rdi], v1: i8x16 [%xmm0], v2: i8x16 [%xmm1], v12: i64 [%rbp]):
[RexOp1pushq#50]                    x86_push v12
[RexOp1copysp#8089]                 copy_special %rsp -> %rbp
@00a6 [null_fpr#00,%xmm0]           v4 = raw_bitcast.i16x8 v1
@00a6 [Mp2vconst_optimized#5ef,%xmm2] v11 = vconst.i16x8 0x00
@00a6 [Mp2fa#5f9,%xmm2]             v5 = isub v11, v4
@00a6 [null_fpr#00,%xmm2]           v6 = raw_bitcast.i8x16 v5
@00aa [null_fpr#00,%xmm2]           v7 = raw_bitcast.i16x8 v6
@00aa [null_fpr#00,%xmm1]           v8 = raw_bitcast.i16x8 v2
@00aa [Mp2fa#5fd,%xmm2]             v9 = iadd v7, v8
@00aa [null_fpr#00,%xmm2]           v10 = raw_bitcast.i8x16 v9
@00ac [-]                           fallthrough ebb1(v10)

                                ebb1(v3: i8x16 [%xmm2]):
@00ac [Op2frmov#428]                regmove v3, %xmm2 -> %xmm0
[RexOp1popq#58,%rbp]                v13 = x86_pop.i64
@00ac [Op1ret#c3]                   return v3, v13
}

This issue is to discuss if and how to remove these extra bitcasts.
What is the value of adding this in Cranelift?
The extra raw_bitcasts emit no machine code but they are confusing when troubleshooting and add extra memory and processing overhead during compilation.
Do you have an implementation plan, and/or ideas for data structures or algorithms to use?
Some options:

add types to load and const: https://github.com/WebAssembly/simd/issues/125 was discussed in the Wasm SIMD Sync meeting (https://github.com/WebAssembly/simd/issues/121) and someone brought up that making load and const typed (e.g. f32x4.load) would allow compilers to attach the correct types to values and retain them through the less-strong v128 operations (e.g. xor). https://github.com/WebAssembly/simd/issues/125 discusses this from a performance point of view but that addition would solve this issue.

examine the DFG: another approach would be to look at the DFG to figure out the types of predecessors as mentioned in https://github.com/WebAssembly/simd/pull/1#issuecomment-295331508. This, however, would have to be extended for type signatures. Cranelift would have to look at the instructions in a function to figure out how the v128 parameters are used. In the function add-sub above, with signature (param v128 v128 v128), the addition and subtraction make this clear but some functions will make this analysis impossible.

add a V128 type to Cranelift: Cranelift's type system could be extended to include a V128 type in Cranelift's type system that would include all INxN, FNxN, and BNxN types. The instruction types would stay the same (e.g. iadd should still only accept integers) but type-checking could be relaxed to allow the V128 type to be used as one of its valid subtypes. This opens up a mechanism to get around the type-checking but arguably that already exists with raw_bitcast. Code that knows its types would remain as-is but Wasm-to-CLIF translated code could use the V128 a bit more naturally than the raw_bitcasts.

do nothing: I brought this up a long time ago when talking to @sunfishcode and that seemed the best thing to do then--I'm opening this issue to discuss whether that is still the case.

Have you considered alternative implementations? If so, how are they better or worse than your proposal?
See above.

It seems to me that the simplest fix is simply to remove all NxM types from CL's type system, where NxM == 128, and replace them with a single V128 type.  What benefit does having all these types bring us?  They are not useful for typechecking CLIF that is derived from wasm, since wasm allows free intermixing of the types.

(notes copied from #2303):
Disadvantages of using bitcasts:

they make the logic in this file [code_translator.rs] fragile: miss out a bitcast for any reason, and there is the risk of the system failing in the verifier.  At least for debug builds.

in the new backends, they potentially interfere with pattern matching on CLIF -- the patterns need to take into account the presence of bitcast nodes.

in the new backends, they get translated into machine-level vector-register-copy instructions, none of which are actually necessary.  We then depend on the register allocator to coalesce them all out.

they increase the total number of CLIF nodes that have to be processed, hence slowing down the compilation pipeline.  Also, the extra coalescing work generates a slowdown.

Replacing NxM with V128 would require a new variant of many instructions for every lane size. The current design allows using the same iadd instruction for every integer type both scalar and vector. It is also useful for typechecking CLIF derived from rust, as rust doesn't allow mixing vector types without an explicit transmute.

One longer-term way around that, once the old backend is no longer needed, that would be to abandon the DSL for defining CLIF instructions.  And instead define them using a simple Rust enum, in the same way that the new backends define target specific instructions.  And for the vector instructions, include a field of type
enum Laneage { I8X16, I16X8, I32X4, I64X2, F versions of the same, etc }

Currently many instructions are both scalar and vector instructions at the same time. For example iadd. Adding a Laneage argument would add unnecessary noise when using scalars only.


Check for null responses during cosmos updates to avoid NPE

cosmosDataAccessor.updateMetadata() can return null response if there is nothing to update, i.e. fields already have specified value. Check for null response during metadata updates to avoid NPE.

Codecov Report

Merging #2100 (c4fbfab) into master (7009ebe) will decrease coverage by 58.70%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #2100       +/-   ##
=============================================
- Coverage     73.84%   15.14%   -58.71%
+ Complexity    10064     2283     -7781
=============================================
  Files           721      721
  Lines         54721    54731       +10
  Branches       6763     6765        +2
=============================================
- Hits          40410     8289    -32121
- Misses        12168    45962    +33794
+ Partials       2143      480     -1663

Impacted Files
Coverage Δ

...ithub/ambry/cloud/azure/AzureBlobDataAccessor.java
0.00% <0.00%> (-67.80%)
:arrow_down:

...ithub/ambry/cloud/azure/AzureCloudDestination.java
0.00% <0.00%> (-72.78%)
:arrow_down:

...m/github/ambry/cloud/azure/CosmosDataAccessor.java
0.00% <0.00%> (-44.91%)
:arrow_down:

.../src/main/java/com/github/ambry/router/Router.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/com/github/ambry/store/Message.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/named/PutResult.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaMode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaName.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/rest/RestMethod.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/config/KMSConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 563 more

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 7009ebe...c4fbfab. Read the comment docs.


Tune codeql-analysis

Currently CodeQL is only triggered on the master branch. This is not useful for how we set up the Dogecoin Core repo.
Additionally changed the process to use the depends system (but not analyze that) and to skip over any doc changes.

only audit production code (no python)
trigger on *-maint and *-dev push
trigger on PR
remove useless autogenerated comments
skip doc changes
use depends system without analyzing it
cache depends

forgot to document removal of python checks (because that's dev tools, not production code)

forgot to document removal of python checks (because that's dev tools, not production code)
why should we not let it run over dev tools which at the end, should test the final result we produced?

why should we not let it run over dev tools which at the end, should test the final result we produced?

It will distract from issues with production code. No python code gets compiled into released binaries, so static analysis there is just not very impactful, imho, because it would basically be analyzing the test framework, not Dogecoin Core.

I just wonder about the python removal as I think such a tool should cover all code used for making the software product, but maybe it makes sense to just turn that on at a later point where we have great code coverage and some work done on the tests?

You can run a static analysis locally any time and propose fixes, but I'd recommend doing that on 1.21 and not on 1.14 and also once we're a bit further down the line, and then only for the Dogecoin-specific things we didn't clone from Bitcoin Core (fixes to generic Bitcoin Core code are better proposed upstream and then backported. Helps more people, does more good 🥰)

the installation of libboost-all-dev is is recommended if the installation of the other tools does not work - how do we account for that? is this note on the topic obsolete?

Where do you see that note? Because honestly, libboost-all-dev is not needed when using depends (no boost system lib is needed because it gets compiled from source and then detected by ./configure thx to --prefix=), and it's also not needed when doing compile with system libs, because you don't need all. Doing this is basically a shortcut to not have to think which boost libs to install.

how much faster is it with the -j4 flag? :)

It specifies the number of concurrent jobs... in this case 4. The net compile time increase varies, but it's "up to 4x" from -j1

@patricklodder Not sure it s working correctly: "1 analysis not found"
https://github.com/dogecoin/dogecoin/pull/2380/checks?check_run_id=3033566739

because there was no base branch before the PR
Should be good in future runs, also see https://github.com/dogecoin/dogecoin/security/code-scanning

I see. The security repo is private ... :(

Hmm makes sense to not have that public in raw form. I'll make issues for the ones that can be disclosed (at least 1 of 2, possibly both) - and both are with 3rd party code.


Flow: Add component for multi-tenant remote_write support

The Prometheus remote_write protocol doesn't have the notion of multi-tenancy itself. For this reason different backends offer use various methods to enable multi-tenancy, most often using an X-Scope-OrgID header, or labels with a special meaning.
When using a prometheus.remote_write component, the Prometheus queue_manager reads WAL segments sequentially and enqueues metrics opportunistically to be batched off as remote_write requests. This behaviour offers no fine-grained control at the request level. Our current suggestion to users is that they add an extra header to their endpoint block, but these per-endpoint headers are static, and we don't support write_relabel_config filtering in Flow yet.
The new component would act as a remote_write middleware, receiving metrics from upstream components, extracting a given label (say tenant), and batching timeseries grouped by this label value.
It would then send discrete remote_write requests for these batches while also adding the correct X-Scope-OrgID header for each one.
Notes

This was inspired by the conversation in grafana/agent#1821 and existing solutions like cortex-tenant.
I don't believe it would be easy to try and shoehorn this behaviour into the current prometheus.remote_write component.
Using this component would entail some performance penalty which should be measured and explicitly documented.

+1
Since there seems to be no progress - is there any alternative for dynamic (based on metric label) tenant headers?

Moving this proposal to active because of the amount of requests for it. @mattdurham let's discus it when you have time whether it's something we can bring in the remote_write component or the remote_queue one

I would like to see a possibility to add a component in Alloy the tenant information.
I have an alloy instance and several different components active - however I want to send metrics from one component to tenantA and the metrics from other components to tenantB.
Maybe in the component we can add a parameter like "tenant = tenantA" which is then forwarded to "prometheus.remotw_write" component and this component is able to if the component which is sending the metrics to is has the value set and the dynamically replaces it in remote_write for the relevant data,.
If an additional "label in the metrics should be the indicator where to send the metrics to we should make it possible to decide which label it is because a hardcoded "tenant" label may conflict with existing labels in metrics.

I wonder if we could use the proposed foreach block for such a feature. The foreach would create a new sub-pipeline for every member of an array. We would also need to have a new type of component which looks at all the metric samples, gets the tenant label, and outputs an array containing all tenant strings. That array could be what the foreach is iterating on, and each sub-pipeline could filter out the samples which don't apply for its tenant.


Empty logs should be removed

With the workers it would be easy to remove error logs if they are empty. This will reduce the number of small and unused empty log files. The cluster's filesystem will thank us for that ;)

The clusters filesystem would thank us but I'm unsure if we want that behaviour.
Maybe others could chime in.

Unless they cause problem, I would keep them. It is useful to know if the
file was created or not while debugging, even if it is an empty file.
Just my personal opinion, I just read the last comment as offline.
Le jeu. 2 févr. 2017 14:47, Mathieu Germain<EMAIL_ADDRESS>a
écrit :

The clusters filesystem would thank us but I'm unsure if we want that
behaviour.
Maybe others could chime in.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SMART-Lab/smartdispatch/issues/38#issuecomment-277059260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALC-wG54AYwYMNvbLY2PPSgHk5fvjBFks5rYjA9gaJpZM4CorRf
.

Ok, let's keep them. Anyway, it might change if we ever implement the database approach.


Restrict access for reviewer

Description of changes:

Add view_suveys, view_assigned_engagements, view_feedbacks roles to be used to restrict access to survey listing, engagement and feedback listing pages
Filter side nav according to role
Refactor user authorization in engagement form
separate engagement create and edit into different roues with different restrictions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1737 (1f84f09) into main (133b246) will increase coverage by 0.55%.
The diff coverage is 71.42%.

:exclamation: Current head 1f84f09 differs from pull request most recent head 819147f. Consider uploading reports for the commit 819147f to get more accurate results

@@            Coverage Diff             @@
##             main    #1737      +/-   ##
==========================================
+ Coverage   70.97%   71.53%   +0.55%
==========================================
  Files         374      370       -4
  Lines       11144    10968     -176
  Branches      865      823      -42
==========================================
- Hits         7910     7846      -64
+ Misses       3100     2991     -109
+ Partials      134      131       -3

Flag
Coverage Δ

metapi
78.56% <71.42%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

met-api/src/met_api/models/engagement.py
71.59% <0.00%> (+0.40%)
:arrow_up:

...b/src/components/engagement/form/ActionContext.tsx
55.88% <ø> (-2.16%)
:arrow_down:

...agement/form/EngagementFormTabs/EngagementForm.tsx
75.78% <ø> (-0.26%)
:arrow_down:

...mponents/engagement/form/EngagementFormWrapper.tsx
100.00% <ø> (ø)

met-web/src/components/layout/SideNav/SideNav.tsx
88.00% <ø> (ø)

met-api/src/met_api/services/engagement_service.py
69.86% <50.00%> (-0.28%)
:arrow_down:

met-api/src/met_api/utils/roles.py
100.00% <100.00%> (ø)

... and 8 files with indirect coverage changes


Add a resolver to generate the JSON data object as vuetable-2 needs it

The single page application that builds on top of the web service GraphQL API uses vuetable-2 to generate the master table view for a given data model. Include a GrapqhQL resolver for each model that delivers the JSON data object as vuetable-2 needs it.
For the restful example resolver see:

helper.js line 174
get_routes template from line 48

For the single page code generator see:

master table view

Done. #6ae09c
#16dc3f


Import, build and install SSMIS UPP Averaging Module at NCI

keyword_SSMIS_UPP_preprocess_satellite_average   |    by<EMAIL_ADDRESS>
Fiona discovered that the SSMIS dataset we receive from UKMO is different from what UKMO ultimately assimilates in their NWP systems. UKMO applies averaging to the data prior to assimilation using SSMIS UPP Averaging Module.
We are uncertain as to how to proceed with the SSMIS dataset and its ingestion into MARS. However in order to be ready for testing the SSMIS UPP Averaging module is downloaded, built and installed. These steps are described in this ticket.

Issue migrated from trac:349 at 2024-01-31 18:32:50 +1100

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>set owner to jtl548

<EMAIL_ADDRESS>commented

ticket/349/TicketSummary


ACTION REQUIRED: Changes to pulling Chainguard Images

Hey there Chainguard here.
We noticed that you are using Chainguard Images, thank you! We wanted to make you aware of an upcoming change that will impact your project.
Starting August 16, 2023 public users will no longer be able to pull images from our registry (cgr.dev/chainguard) by tags other than latest or latest-dev. Please see the announcement for more information.
You are currently using the following.
In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/charts/tornjak-frontend/values.yaml:

cgr.dev/chainguard/bash:5.2.15

In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/charts/spire-server/values.yaml:

cgr.dev/chainguard/bash:5.2.15

In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/charts/spire-agent/values.yaml:

cgr.dev/chainguard/wait-for-it:latest-20230517
cgr.dev/chainguard/bash:5.2.15

In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/charts/spire-agent/README.md:

cgr.dev/chainguard/wait-for-it:latest-20230517
cgr.dev/chainguard/bash:5.2.15

In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/charts/spiffe-oidc-discovery-provider/values.yaml:

cgr.dev/chainguard/bash:5.2.15

In https://github.com/spiffe/helm-charts/blob/a167ce68901a2b08d44367aa3a6da7612a64afc6/charts/spire/README.md:

cgr.dev/chainguard/wait-for-it:latest-20230517
cgr.dev/chainguard/bash:5.2.15

Our goal is to prevent your project from experiencing any disruptions. Please see the migration guide for options.
If there's more we can do to help please reply to this issue or email us at<EMAIL_ADDRESS>Thank you!

So, we need to switch to :latest@sha256xxxxx on all these...

Renewing the call for https://github.com/spiffe/helm-charts/pull/249

Thanks chainguard. I think the digestabot mentioned in the migration guide would work well here.

Discussed with @kfox1111 . digest-a-bot won't work for our use case as it assumes image and tag are together. For us they are separate configurables.

Hey, I work with Chainguard - I'm not sure what you mean by "separate configurables"? I'd love to come up with something that works for you if I can. Do you mean you need access to older tags?

Ah cool, that is useful!
I'll open an issue on digestabot.


Added video, link to website

After this, will add to AWS so the website will be live

Woah :O can't wait to see it live!
LGTM


Revamp OCM invitation workflow

This is part of a series of PRs for having OCM in production.
In particular, this is regarding the invitation workflow.
Improvements/changes in this PR:

Refactored OCM Invite manager
Updated /invite-accepted endpoint to the last OCM APIs spec (https://github.com/cs3org/OCM-API/pull/54)

Introduced mutual exchange of user information on invitation accept

Add errors as specified by the OCM and cs3apis specs (https://github.com/cs3org/OCM-API/pull/58, https://github.com/cs3org/cs3apis/pull/198)
Allow user to specify a description when generating an invitation token
Split old ocmd http service in two services (OCM and sciencemesh) -> Closes https://github.com/cs3org/reva/issues/3540

ocm services contain only the implementation of the OCM APIs (https://cs3org.github.io/OCM-API/docs.html)
sciencemesh is meant for reva clients (like web) for interacting with tokens and shares in OCM

Written integration tests for the invitation workflow (both grpc and http)

@michielbdejong from this point on we're on the new OCM endpoints, therefore you can start adapting the ownCloud/Nextcloud sciencemesh apps code according to https://github.com/cs3org/OCM-API/pull/54 and our discussion. I think we could tag a Reva version after you give a green light that the apps are OK.


get_status method for job

Is there one? I can't seem to find it and have been using job.state.status, which would break if state member was modified in any way in the future.
I can try to do the leg work of adding this in if you'd prefer.

Hi there! As a disclaimer, I'm not very active with the project any more so my advice here may be wrong.
I believe the correct way to do this is through the path you mention (job.state.status). Maintaining a reference to the state object and querying its status repeatedly would result in stale data (as you correctly point out). Instead, I think what you want to do is hold a reference to the job itself and, whenever you want to know the current state, get the current state and look at the status on that. That should survive any changes to the state as the job moves through its lifecycle.

#179

What I meant was that job.state.status seemed inferior to job.get_status() due to the latter better abstracting retrieving status from how status is stored/maintained. But since this code will likely be relatively static going forward I can understand how this really isn't necessary.
I completely misunderstood your comment the first time I read it. You're right, job.state.status works perfectly fine (for now). But again, since developments aren't planned this probably isn't very important.
I'm trying to develop a command line interface manager for dagobah jobs with slack notificatinos, so such functionality would be somewhat nice for my personal workflow. I'll likely make certain extensions/implementations, but it would probably be easier for me to do this on a fork of dagobah instead of modifying it here.


s3test doesn't run

I know this degradation happened at this commit https://github.com/akiradeveloper/akashic-storage/commit/665bfae76585b968cd5968167df5082f4963e551
I should fix this immediately
ERROR: test suite for <module 's3tests.functional' from '/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/s3tests/functional/init.py'>
Traceback (most recent call last):
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/nose/suite.py", line 209, in run
self.setUp()
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/nose/suite.py", line 315, in setupContext
try_run(context, names)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/nose/util.py", line 471, in try_run
return func()
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/s3tests/functional/init.py", line 352, in setup
nuke_prefixed_buckets(prefix=prefix)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/s3tests/functional/init.py", line 111, in nuke_prefixed_buckets
nuke_prefixed_buckets_on_conn(prefix, name, conn)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/s3tests/functional/init.py", line 63, in nuke_prefixed_buckets_on_conn
for bucket in conn.get_all_buckets():
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/boto/s3/connection.py", line 437, in get_all_buckets
response = self.make_request('GET', headers=headers)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/boto/s3/connection.py", line 665, in make_request
retry_handler=retry_handler
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/boto/connection.py", line 1071, in make_request
retry_handler=retry_handler)
File "/home/travis/build/akiradeveloper/akashic-storage/s3-tests/s3-tests-clone/virtualenv/local/lib/python2.7/site-packages/boto/connection.py", line 1030, in _mexe
raise ex
error: [Errno 111] Connection refused

The thing is the server isn't listening on the port! Wow and Why!
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:3306            <IP_ADDRESS>:*               LISTEN      988/mysqld
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      1031/sshd
tcp        0      0 <IP_ADDRESS>:5432          <IP_ADDRESS>:*               LISTEN      1228/postgres
tcp        0      0 <IP_ADDRESS>:48880      <IP_ADDRESS>:80      ESTABLISHED 3986/python
tcp        0      0 <IP_ADDRESS>:48885      <IP_ADDRESS>:80      ESTABLISHED 1374/python
tcp        0    208 <IP_ADDRESS>:22         <IP_ADDRESS>:56639   ESTABLISHED 1612/sshd: travis [
tcp        0      0 <IP_ADDRESS>:48188      <IP_ADDRESS>:80      ESTABLISHED 1373/python
tcp        0      0 <IP_ADDRESS>:48879      <IP_ADDRESS>:80      TIME_WAIT   -
tcp        0      0 <IP_ADDRESS>:58108      <IP_ADDRESS>:80      TIME_WAIT   -
tcp6       0      0 :::22                   :::*                    LISTEN      1031/sshd

I support it is server is immediately closed when  the program quits from App. So we need Await.ready there
Not sure why it was the commit turned into failure but the compactor thread running keeps the process from being killed? The commit purged compactor and there was a threadpool.


Replace uint with unsigned

As of PHP 7.4.0, uint is no longer guaranteed to be available on all
platforms.  Therefore we replace it with the portable unsigned.

Merged, after rebase.


about the dataset

Hello, @vevenom
Thanks for your impressive work of this project .
I`m working on my idea based on ScanNet-layout, and i need to annotate some custom pictures manually.
So I wonder if you can send me the tagging tools or just tell me the name of these tools ?
Thanks a lot .
HuiYao

Hi @Hui-Yao
Thank you for the nice words.
Unfortunately I cannot share this part of the code but it's a fairly simple procedure.
If you are looking to annotate 2D polygons you can do that with LabelMe for example. For the 3D annotations we actually just drew 2D masks of planar layout surfaces. Then, for each of the annotated 2D layout polygons, we estimate plane parameters from the contained planar layout surfaces by relying on the associated depth map and a RANSAC procedure. From there, you can calculate the pixelwise layout depth.

Thanks a lot. Wish luck in your research.


GH-244 - Extensible source support

Description

Provides ability to let project spec a sourceFormat object
Supports {{org}} {{repo}} {{pathname}} placeholders in pattern

Related Issue
Resolves: GH-244
Motivation and Context
See the GH issue.
How Has This Been Tested?
E2E for now. Once approach is agreed upon, will write tests.
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

I tried to strike a balance between changing very deep parts of Sidekick / Admin and simply bolting on something that cannot be maintained.
My hope is that this can work for XWalk / UE as well.

Supporting this makes sense to me, and I don’t see any immediate issues with this approach. However, @rofe might have a different perspective. It would also be good to get input from UE to confirm if this works for them.
One suggestion: instead of sourceFormat, perhaps something like contentSourceEditFormat would be more consistent with related fields like contentSourceUrl and contentSourceType.

One suggestion: instead of sourceFormat, perhaps something like contentSourceEditFormat would be more consistent with related fields like contentSourceUrl and contentSourceType.

I changed things to get closer to your comment above.
A couple notes:

The patterns exposed in sidekick/config.json are less verbose, so I did keep sourceFormat as the entry for a project. This should maintain the naming convention style of that file.
Putting two top-level properties in sidekick/config.json seemed heavy, so I did make sourceFormat an object with two properties.
Since contentSourceType already exists, and is markup in these scenarios, I was reluctant to change that property to what is provided by the project. I see markup being useful in the long run.
This PR introduces contentSourceLabel as the text that is used in the button. SP & GDrive button labels by comparison are calculated based on other details (fstab).
This PR introduces contentSourcePattern to better match the naming conventions of the project.
While the sidekick/config.json is an object with sub-props, I did flatten them down to better fit the style of the codebase. This makes null checks a bit cleaner.

Let me know what y'all think. Happy to adjust further.
The final sidekick/config.json looks like:
{
  "project": "DA Block Collection",
  "sourceFormat": {
    "label": "Document Authoring",
    "pattern": "https://da.live/edit#/{{org}}/{{repo}}{{pathname}}"
  }
}

My hope is that this can work for XWalk / UE as well.

I looked at some existing xwalk mountpoints and it looks like the pattern could be fulfilled. Letting @buuhuu confirm.

Wondering if the label ever need to be localized? If so, you could add an additional, optional labelI18n object, analog to the existing titleI18n allowing localization of custom button texts in the current schema.

@rofe @auniverseaway I think this will work with XWalk as well. Today we have a Sidekick overlay which just does
const { pathname } = window.location;
const editorUrl = `${contentSourceUrl}${pathname}?cmd=open`;

In the new format this would be
{
  "project": "abc",
  "sourceFormat": {
    "label": "Universal Editor",
    "pattern": "https://author-p1234-e5678.adobeaemcloud.com/bin/franklin.delivery/{{org}}/{{repo}}/main/{{pathname}}?cmd=open"
  }
}

We should not duplicate the {{contentSourceUrl}} if possible, same as we should not duplicate owner, repo, branch. Either we replace all patterns or none. If we say it is fine to duplicate these parameters in the config the proposal would even work without any parameter replacement iiuc.

@buuhuu,
If @rofe approves and it works for you, I think tokenizing {{contentSourceUrl}} makes sense. The goal is to put this property in the respective boilerplates and you don't have to change it project to project.
For an XWalk project, I show:
contentSourceUrl
https://author-p15404-e146221-cmstg.adobeaemcloud.com/bin/franklin.delivery/mhaack/my-aem-project/main

Edit URL
https://author-p15404-e146221-cmstg.adobeaemcloud.com/bin/franklin.delivery/mhaack/my-aem-project/main/index?cmd=open

Which means that should work well for UE.
DA / WordPress / Drupal / etc have different content and edit URLs.

The goal is to put this property in the respective boilerplates and you don't have to change it project to project

Can you elaborate on this? With hlx5 repo-less it cannot be in the boilerplate / it changes from project to project.

@buuhuu the reason for supporting variables is that this edit url format can stay fully generic and doesn't need to be changed from project to project.
@auniverseaway I approve :)

I think I accounted for all feedback and suggestions.
@rofe the only thing I didn't add was i18n for the label as it didn't seem like proper nouns would need to be localized: SharePoint, Google Drive, Universal Editor, WordPress, Document Authoring (as a brand name), etc. If you feel strongly we should add the support, let me know.
I modified the original comment with the updated spec, but here it is as well. If I can get thumbs on the final naming conventions I can work on tests and docs.
Thanks!
Sidekick spec
UE
{
  "project": "XWalk Block Collection",
  "editUrlFormat": {
    "label": "Universal Editor",
    "pattern": "{{contentSourceUrl}}{{pathname}}?cmd=open"
  }
}

DA
{
  "project": "DA Block Collection",
  "editUrlFormat": {
    "label": "Document Authoring",
    "pattern": "https://da.live/edit#/{{org}}/{{site}}{{pathname}}"
  }
}

@auniverseaway we'd also need to update the config schema. That makes me wonder if it wouldn't be easier to just add 2 top level properies instead of an object?

Tested it with https://main--my-aem-project--mhaack.aem.page/ for UE & Crosswalks, works nicely. cc @buuhuu

@rofe @dylandepass I think I've got all suggestions covered. I didn't see the schema in the codebase, so my assumption is that it's generated from the TS def?

I didn't see the schema in the codebase

At the moment, the schema needs to be updated manually here:
https://github.com/adobe/helix-website/blob/main/tools/sidekick/config.schema.json

@rofe updated: https://github.com/adobe/helix-website/pull/657

@auniverseaway I'll merge this into a branch to make sure all checks are passing before mergin to main.