Add e2e test for cleanup operation

This PR adds an e2e test that verifies cleanup is run against two pods in different racks but in the same data center. It also adds some verification logic to the scale up test to make sure cleanup runs since autoPilot is enabled for the test.

@allamand I had to add a make clean the CircleCI config. CircleCI was using the cached vendor directory from #88. Maybe it would be good to also cache Go.toml. If it changes, then purge cache contents. I would rather devote the time and effort to migrating over to Go modules.
@allamand can you please resume the build pipeline so e2e tests are run? Thanks 😄

@jsanda semas you are missing the new test file :
testdata/cassandracluster-1DC-no-autopilot.yaml: no such file or directory

@allamand thanks for pointing out. I just added/pushed it.

@jsanda just re-start tests

@jsanda did you find out why tests are failing ?

I think it is just a timing issue that can be easily fixed with some polling. I should be able to get this squared away in the next couple days.

I  just reviewed the failure. The test timed out waiting for the cluster to become ready. I pushed a commit to increase the memory for the Cassandra pods used in the test. The only thing I can think of is that the smaller amount of memory that I was using made the pods unstable and thus prevented the cluster from becoming ready.
The  test is passing for me against my dev k8s cluster. I am going to run it a couple more times.
@cscetbon or @allamand can you please start the e2e tests?

I have run the test several times. I am seeing intermittent failures. I just noticed this in the events from the CircleCI failure:
cassandra-e2e   2s          Warning   FailedScheduling          pod/cassandra-e2e-dc1-rack2-0                          0/1 nodes are available: 1 Insufficient cpu.

The test creates a four node cluster spread across two racks and runs cleanup on one node from each rack. I think that this is a good test scenario; however, it looks like I would be better off using a smaller cluster so that the test is more stable and reliable. I am going to update the test.
@allamand and/or @cscetbon can you document what kind of environment is used for CI? That would be helpful for myself as well as anyone else who might want to contribute e2e tests.

Hi John
Actually it is a minikube cluster created on a circleCI job virtual machine.
Sébastien
Le 24 août 2019 à 18:44, John Sanda <notifications<EMAIL_ADDRESS>a écrit :
I have run the test several times. I am seeing intermittent failures. I just noticed this in the events from the CircleCI failure:
cassandra-e2e   2s          Warning   FailedScheduling          pod/cassandra-e2e-dc1-rack2-0                          0/1 nodes are available: 1 Insufficient cpu.
The test creates a four node cluster spread across two racks and runs cleanup on one node from each rack. I think that this is a good test scenario; however, it looks like I would be better off using a smaller cluster so that the test is more stable and reliable. I am going to update the test.
@allamandhttps://github.com/allamand and/or @cscetbonhttps://github.com/cscetbon can you document what kind of environment is used for CI? That would be helpful for myself as well as anyone else who might want to contribute e2e tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Orange-OpenSource/cassandra-k8s-operator/pull/90?email_source=notifications&email_token=ACEKVYYBJE24ROAJMARTKYTQGFQPLA5CNFSM4IKGGECKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CDSLA#issuecomment-524564780, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACEKVY642SZTHVAAZNI77ELQGFQPLANCNFSM4IKGGECA.

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

I think have discovered another reason for some of the intermittent failures.
Here are the logs from my second Cassandra node:
INFO  [main] 2019-08-24 20:29:02,899 Server.java:156 - Starting listening for CQL clients on /<IP_ADDRESS>:9042 (unencrypted)...
INFO  [main] 2019-08-24 20:29:03,094 CassandraDaemon.java:556 - Not starting RPC server as requested. Use JMX (StorageService->startRPCServer()) or nodetool (enablethrift) to start it
INFO  [jolokia-1] 2019-08-24 20:29:58,411 CompactionManager.java:299 - No sstables to CLEANUP for system_distributed.view_build_status
INFO  [jolokia-1] 2019-08-24 20:29:58,593 CompactionManager.java:299 - No sstables to CLEANUP for system_distributed.parent_repair_history
INFO  [jolokia-1] 2019-08-24 20:29:58,633 CompactionManager.java:299 - No sstables to CLEANUP for system_distributed.repair_history
INFO  [jolokia-2] 2019-08-24 20:29:58,697 CompactionManager.java:299 - No sstables to CLEANUP for system_auth.resource_role_permissons_index
INFO  [jolokia-2] 2019-08-24 20:29:58,701 CompactionManager.java:299 - No sstables to CLEANUP for system_auth.role_members
INFO  [jolokia-2] 2019-08-24 20:29:58,707 CompactionManager.java:299 - No sstables to CLEANUP for system_auth.role_permissions
INFO  [jolokia-2] 2019-08-24 20:29:58,710 CompactionManager.java:299 - No sstables to CLEANUP for system_auth.roles
INFO  [jolokia-3] 2019-08-24 20:29:58,793 CompactionManager.java:299 - No sstables to CLEANUP for system_traces.sessions
INFO  [jolokia-3] 2019-08-24 20:29:58,795 CompactionManager.java:299 - No sstables to CLEANUP for system_traces.events

And checking the cluster status reports:
  status:
    cassandraRackStatus:
      dc1-rack1:
        cassandraLastAction:
          Name: Initializing
          endTime: "2019-08-24T20:28:05Z"
          status: Done
        phase: Running
        podLastOperation:
          Name: cleanup
          endTime: "2019-08-24T20:30:01Z"
          operatorName: cassandra-k8s-operator-7cf67f66bb-w576w
          podsOK:
          - cassandra-e2e-dc1-rack1-0
          startTime: "2019-08-24T20:29:57Z"
          status: Done
      dc1-rack2:
        cassandraLastAction:
          Name: Initializing
          endTime: "2019-08-24T20:29:37Z"
          status: Done
        phase: Running
        podLastOperation: {}
    lastClusterAction: Initializing
    lastClusterActionStatus: Done
    phase: Running
    seedlist:
    - cassandra-e2e-dc1-rack1-0.cassandra-e2e.cassandra-e2e
    - cassandra-e2e-dc1-rack2-0.cassandra-e2e.cassandra-e2e
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

The cleanup operation finished almost immediately, but it looks like rack2 is stuck in the running phase. I put a 30 minute sleep call in my test prior to doing any verification. It has been more than 15 minutes now and the status for rack2 has not changed.

And here is the end of the operator logs:
time="2019-08-24T20:29:37Z" level=info msg="[cassandra-e2e][dc1-rack2]: StatefulSet(Initializing): Replicas Number OK: ready[1]"
time="2019-08-24T20:29:37Z" level=info msg="Action Initializing is done!" cluster=cassandra-e2e
time="2019-08-24T20:29:57Z" level=info msg="Start operation" cluster=cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack1-0 rack=dc1-rack1
time="2019-08-24T20:29:57Z" level=info msg="Operation start" cluster=cassandra-e2e hostName=cassandra-e2e-dc1-rack1-0.cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack1-0 rack=dc1-rack1
time="2019-08-24T20:29:57Z" level=info msg="Execute the Jolokia Operation" cluster=cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack1-0 rack=dc1-rack1
time="2019-08-24T20:29:57Z" level=info msg="Start operation" cluster=cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack2-0 rack=dc1-rack2
time="2019-08-24T20:29:57Z" level=info msg="Operation start" cluster=cassandra-e2e hostName=cassandra-e2e-dc1-rack2-0.cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack2-0 rack=dc1-rack2
time="2019-08-24T20:29:57Z" level=info msg="Execute the Jolokia Operation" cluster=cassandra-e2e operation=Cleanup pod=cassandra-e2e-dc1-rack2-0 rack=dc1-rack2
time="2019-08-24T20:29:58Z" level=info msg="[cassandra-e2e-dc1-rack2-0.cassandra-e2e]: Cleanup of keyspace system_distributed"
time="2019-08-24T20:29:58Z" level=info msg="[cassandra-e2e-dc1-rack2-0.cassandra-e2e]: Cleanup of keyspace system_auth"
time="2019-08-24T20:29:58Z" level=info msg="[cassandra-e2e-dc1-rack2-0.cassandra-e2e]: Cleanup of keyspace system_traces"
time="2019-08-24T20:29:58Z" level=error msg="Issue when updating CassandraCluster" cluster=cassandra-e2e err="Operation cannot be fulfilled on cassandraclusters.db.orange.com \"cassandra-e2e\": the object has been modified; please apply your changes to the latest version and try again"
time="2019-08-24T20:29:58Z" level=info msg="[cassandra-e2e-dc1-rack1-0.cassandra-e2e]: Cleanup of keyspace system_distributed"
time="2019-08-24T20:30:00Z" level=info msg="[cassandra-e2e-dc1-rack1-0.cassandra-e2e]: Cleanup of keyspace system_auth"
time="2019-08-24T20:30:00Z" level=info msg="[cassandra-e2e-dc1-rack1-0.cassandra-e2e]: Cleanup of keyspace system_traces"
time="2019-08-24T20:30:00Z" level=error msg="Issue when updating CassandraCluster" cluster=cassandra-e2e err="Operation cannot be fulfilled on cassandraclusters.db.orange.com \"cassandra-e2e\": the object has been modified; please apply your changes to the latest version and try again"
time="2019-08-24T20:30:00Z" level=error msg="Issue when updating CassandraCluster" cluster=cassandra-e2e err="Operation cannot be fulfilled on cassandraclusters.db.orange.com \"cassandra-e2e\": the object has been modified; please apply your changes to the latest version and try again"

It looks like a race condition here. The cleanup finishes before the current reconciliation. When the operator goes to update the status, it no longer has the latest version. The update fails, the status does not change, and the test eventually times out and fails.

@jsanda weird, cause updating the status is done by retrying after getting a new version when it happens. It's needed as we use go routines and that the version they have expires.
What is the order of the operations you run in your test ?

What is the order of the operations you run in your test ?

Create the cluster
Wait for cluster to be ready
Set labels on pods to trigger cleanup
Do verification

It seems you're saying the reconciliation is not done and a cleanup is run, is that right ?

My previous comment was a bit confusing. From the logs I pasted, it is clear that dc1-rack2 is stuck in phase: Running even though the actual cleanup operation has already finished. The logs also show that status updates are failing, though I am not sure which one in particular. This does not happen all the time, hence the race condition.

Phase is running while there is no ongoing action on the cluster, that is normal.
Phase is pending when there are some pods not ready.
Sébastien
Le 25 août 2019 à 16:29, John Sanda <notifications<EMAIL_ADDRESS>a écrit :
What is the order of the operations you run in your test ?

Create the cluster
Wait for cluster to be ready
Set labels on pods to trigger cleanup
Do verification

It seems you're saying the reconciliation is not done and a cleanup is run, is that right ?
My previous comment was a bit confusing. From the logs I pasted, it is clear that dc1-rack2 is stuck in phase: Running even though the actual cleanup operation has already finished. The logs also show that status updates are failing, though I am not sure which one in particular. This does not happen all the time, hence the race condition.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Orange-OpenSource/cassandra-k8s-operator/pull/90?email_source=notifications&email_token=ACEKVY4Z2GBSXWBTORV4FEDQGKJMDA5CNFSM4IKGGECKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CUUUI#issuecomment-524634705, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACEKVY5FAR3IV43KU2EOXNTQGKJMDANCNFSM4IKGGECA.

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

@allamand Thanks for clarifying.
I still think that there is a problem though. Neither podLastOperation nor podsOK are set for dc1-rack2 even though we can see from the Cassandra logs that the cleanup operation already completed.

@jsanda Can you reproduce it on a local kind cluster ? If yes, I can investigate it as there is an existing issue I'm supposed to work on (pod operations).

This is better now, I think we can go with it ?

Yeah, I think it is ready now.
On Tue, Aug 27, 2019 at 6:12 AM Sébastien Allamand<EMAIL_ADDRESS>wrote:

This is better now, I think we can go with it ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Orange-OpenSource/cassandra-k8s-operator/pull/90?email_source=notifications&email_token=AABJBOJQJPRMBOECIUMB3KLQGT4ZFA5CNFSM4IKGGECKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HHREA#issuecomment-525236368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJBOJ2EANNZCB3FEHCSI3QGT4ZFANCNFSM4IKGGECA
.

--

John

@allamand can you please kick off the e2e tests.

/test

I noticed this in the CircleCI logs:

time="2019-08-29T17:25:41Z" level=info msg="failed to create or get service for metrics: Service "cassandra-k8s-operator-metrics" is invalid: [spec.ports[0].name: Invalid value: "metricsPort": a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is 'a-z0-9?'), spec.ports[0].port: Invalid value: 0: must be between 1 and 65535, inclusive]"

@allamand do you think that is the cause for failure?

I noticed this in the CircleCI logs:

time="2019-08-29T17:25:41Z" level=info msg="failed to create or get service for metrics: Service "cassandra-k8s-operator-metrics" is invalid: [spec.ports[0].name: Invalid value: "metricsPort": a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is 'a-z0-9?'), spec.ports[0].port: Invalid value: 0: must be between 1 and 65535, inclusive]"

@allamand do you think that is the cause for failure?

I'm not sure what happened, I trigger again tests and this was good this time.

@allamand can you restart the build and run the e2e tests? The latest failure looks like it was caused by a connection problem while downloading dependencies.
I have rebased on master. The changes on my end are done, pending review and passing tests.

@allamand Thanks for restarting the build. Can you please run the e2e tests.

yes sorry for delay

@allamand Any other changes needed for this?

@jsanda, it’s ok for me but I see @scetbon was asking some changes ?

@allamand can we give the e2e tests another go please :)

/tests


Do not pass NoneType as argument to ceph_crush_rule

With ansible-core 2.15 it is not possible to pass argument of unexpected
type, as otherwise module will fail with:
'None' is not a string and conversion is not allowed
With that we want to only get all existing crush rules, so we can simply
supply an empty string as a name argument, which would satisfy
requirements and have same behaviour for previous ansible versions.
Alternative approach would be to stop making name as a required
argument to the module and use empty string as default value
when info state is used.

@guits would it be possible to review this PR? It's blocking some progress over in the OpenStack world.

Reviews of this patch would be greatly appreciated, we are fast approaching a release deadline for OpenStack and this error is blocking ceph support in the OpenStack-Ansible project.


(feature) Added grid and did linting changes to README.md

This has been done using tables in markdown, there is no way as such to stylise/colorise or customise them so have gone with simple approach. This looks best in light mode as most icons are on the darker side.

cool, thanks for the feedback, let me try some more stuff in that case


feat(template): support tooltip for ENV entites (#366)

feat(template): support for selection list for ENV entites (#366)
Sample:
      {
        "name": "USESSL",
        "label": "use SSL",
        "value": "N",
        "values": {"Y": "Yes", "N": "No"},
        "hint": "generates a self-signed certificate"
      }

Sorry @twityde a bit busy right now, will try to review this (functionaly at first) next week.


Fix shooter bug

Fix bug: on shoot the old shooter is launched and a new one is created
Refactor function board.shootWasPressed() because it was becoming pretty big
extract Miley  to lib/shared/miley.js

looks good


[request] Supress extra History entries

Since installing Back To Close, I've noticed many "Close tab" entries in the "Show All History" window. Would it be possible to supress them? I tried unchecking "Show "Close tab" in history", but I still get duplicate entries for the URL, but ending with a #.

Hmm, that is a very good question actually. The code relies on sending you to a psudo-new-page kinda thing, so it knows that it already ran. I'll look into what i can do when I get time though. Thanks a lot for the request :D

By now I have literally thousands of these "Close tab" entries in my history, with the URL ending in #. I did a search and deleted them - which took over an hour - but it looks like sometimes they don't get the "Close tab" name, but the name of the page instead. So the history database is still unnecessarily bloated by these entries.
Just hoping you might find some time to add the feature to delete the psuedo-page from the history, when the tab is closed. Thanks!

Seems to be fixed, thanks!


only call event handlers if they are functions

We found a crach setting event handlers to undefined

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 77.77%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   91.74%   91.74%
=======================================
  Files           1        1
  Lines         763      763
=======================================
  Hits          700      700
  Misses         63       63

Impacted Files
Coverage Δ

rtcpeerconnection.js
91.74% <77.77%> (ø)
:arrow_up:

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 b2ff1f9...6a738e1. Read the comment docs.

whoops, not sure how I missed that... can you rebase please?

ping @fippo

E_TOO_MANY_NOTIFICATIONS. Thank you!

published as 1.1.5

thanks :)


Remove ymal files to start from scratch

@lee1043 had another thought - do we need the Makefile anymore if .circleci is gone?

@acordonez Great point. I do not have good understanding of purpose of the Makefile. If it is certain that the Makefile has been only used with circle ci, I agree we can remove it. Do you know how Makefile have been used in the workflow?

@lee1043  I searched for each of the targets in the Makefile (e.g. conda-rerender) in the repo and many of them don't show up outside the Makefile. The ones that do only show up in .circleci/config.yml. The CircleCI config also looks like the only place we use "make" commands in the repo. Based on that info, it looks like the Makefile is only used for the CircleCI workflows.

@acordonez thanks for investigating. In this PR, I removed circle ci related files and added github action workflow initiative. I agree it may be easier if we merge this to master before we ask Tom and Jason to step in. I will merge it when you approve the changes.

@lee1043 I don't see anything else that looks like it should be deleted.


Dashboard view of all users with totals by team

Is your feature request related to a problem? Please describe.
Look at Harold's output doc
Describe the solution you'd like
Describe alternatives you've considered
Additional context

done 2-29-2020


Restore edit functionality

Fixes #1083 .
Changes proposed in this PR:

Moved edit components on a new route ../asset/[did]/edit)
Adds tab for edit compute and edit metadata
restore edit metadata functionality
restore edit compute settings
secure edit route - onlyOwner

Just tested this for a recently published asset and the edit changes are not visible after returning to asset page after successfully edit action:

Although, if I try to edit the asset again, I can see the changes done in previous edit attempt.

can we hide compute settings if the asset is not compute? Not a big issue

@claudiaHash there was an issue with the sample file that was preventing aqua to index the updates (fixed) . Also after updating you need to wait for a few seconds to let aqua index the changes.  Can you do another test and see if it works for you now?

Can you do another test and see if it works for you now?

All good now!

Fixed setting initial value of sample file.
Also fixed subgraph so update history is ok. Don't see any more issues.


Profile the problem solving

The simplified european model by @gzclarence takes 5 minutes to build and solve. We need to profile it.
Some references:
https://www.youtube.com/watch?v=BFvpwC8hEWQ&ab_channel=TheJuliaProgrammingLanguage
https://www.youtube.com/watch?v=Okn_HKihWn8&ab_channel=TheJuliaProgrammingLanguage
https://docs.julialang.org/en/v1/manual/profile/

@gzclarence

The simplified european model by @gzclarence takes 5 minutes to build and solve. We need to profile it.
Some references: https://www.youtube.com/watch?v=BFvpwC8hEWQ&ab_channel=TheJuliaProgrammingLanguage https://www.youtube.com/watch?v=Okn_HKihWn8&ab_channel=TheJuliaProgrammingLanguage https://docs.julialang.org/en/v1/manual/profile/

Thanks a lot for the information!

@abelsiqueira I don't know if I can wait till tomorrow to find out... How's it going? 😶

There were various improvements (#315, #317, #319). The benchmark script is maybe not working, so I am benchmarking locally. The NLBE example from @gzclarence is not up-to-date with the current CSV requirements, so I haven't tested on it yet.

This has been done up to a reasonable point. With the changes since ~1-2 weeks ago, we have:
Old version:

Create graph and RPs: ~50s
Create constraints partitions: ~40x
Create model: ~500s

New version:

Create graph and RPs: < 1s
Create constraints partitinos: ~3.5s
Create model: ~35s

I don't know if we want to close this and open a new one to continue improving the model, or just change the priority.

With #407 and #408, we have the model creation down to 3-5 seconds. The dataframes version is more complicated but is faster. After #112 we can verify again how they scale, but I am guessing that the dataframes version will be better.


Update Readme to accurately reflect the project and criteria

The project README contains a lot of text makes sense when talking about individual open source projects, but makes less sense when we are talking about organizations. Examples:
https://github.com/todogroup/ospolandscape#new-entries
Projects must be open source and hosted on or mirrored to GitHub.
Projects with at least 300 GitHub stars that clearly fit in an existing category are generally included. Put the project in the single category where it best fits.

https://github.com/todogroup/ospolandscape#best-practices-badge
The interactive landscape displays the status (or non-existence) of a badge for each open-source project.

The updated readme should reflect the nature of this project, and make it clear what the criteria are for inclusion of an organization as an OSPO Adopter or a TODO Group Member. Some cases to consider:

How do we handle companies who previously adopted, but no longer are staffing, an OSPO?
How do we handle organizations for which we no longer have good contact information?

+1 I will go and see what we can do here, this obviously was lifted
language from the CNCF landscape
I do think in the future we could consider adding "projects" here,
potentially from the https://github.com/todogroup/awesome-oss-mgmt and make
that whole list interactive :o
On Tue, Mar 16, 2021 at 2:42 PM DuaneOBrien @.***>
wrote:

The project README contains a lot of text makes sense when talking about
individual open source projects, but makes less sense when we are talking
about organizations. Examples:
https://github.com/todogroup/ospolandscape#new-entries
Projects must be open source and hosted on or mirrored to GitHub.
Projects with at least 300 GitHub stars that clearly fit in an existing category are generally included. Put the project in the single category where it best fits.
https://github.com/todogroup/ospolandscape#best-practices-badge
The interactive landscape displays the status (or non-existence) of a badge for each open-source project.
The updated readme should reflect the nature of this project, and make it
clear what the criteria are for inclusion of an organization as an OSPO
Adopter or a TODO Group Member. Some cases to consider:

How do we handle companies who previously adopted, but no longer are
staffing, an OSPO?
How do we handle organizations for which we no longer have good
contact information?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/todogroup/ospolandscape/issues/17, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSINEBR77QIRJMV5IB3TTD67EJANCNFSM4ZJJH5KQ
.

--
Cheers,
Chris Aniszczyk
http://aniszczyk.org

I created https://github.com/todogroup/ospolandscape/issues/22 and https://github.com/todogroup/ospolandscape/issues/21 to deal with your points and https://github.com/todogroup/ospolandscape/pull/23 to specify what entries should be for adopters https://github.com/todogroup/ospolandscape/pull/23


[Package Request] Apache Maven

Description
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
Metadata

Homepage: https://maven.apache.org
Source: https://github.com/apache/maven
License: Apache-2.0
Platforms: Unix, Linux, Darwin, Windows

How to install
Download binaries.
https://maven.apache.org/download.cgi
apache-maven-3.9.9-bin.tar.gz
apache-maven-3.9.9-bin.tar.gz.sha512
https://maven.apache.org/install.html

https://github.com/aquaproj/aqua-renovate-config/pull/727

I'm not very familiar with Aqua. I use it through mise, and contrary to what I can see with other packages, there is no way to install apache/maven — even after these changes. Other packages work fine.

I know mise uses aqua-registry, but I'm not familiar with mise.
aqua-registry is the registry for aqua, not mise.
Could you ask mise community for help?
Maybe mise caches aqua-registry.
About aqua, we haven't released the new version of aqua-registry yet.
https://github.com/aquaproj/aqua-registry/releases

All right. Then I will wait for the release of the Aqua registry. I thought it was published right away, because I was able to install rfjakob/gocryptfs already, but when I tried Apache Maven I got this:
[x80486@uplink:~]$  mise use --global aqua:apache/maven --verbose
DEBUG ARGS: /home/x80486/.local/share/applications/mise use --global aqua:apache/maven --verbose
DEBUG config: ~/.config/mise/config.toml
DEBUG install_some_versions: aqua:apache/maven@latest
DEBUG GET Downloading https://mise-versions.jdx.dev/aqua-registry/apache/maven/registry.yaml to ~/.cache/mise/aqua-registry/pkgs/apache/maven/registry.yaml
DEBUG GET https://mise-versions.jdx.dev/aqua-registry/apache/maven/registry.yaml
DEBUG starting new connection: https://mise-versions.jdx.dev/
DEBUG GET https://mise-versions.jdx.dev/aqua-registry/apache/maven/registry.yaml 404 Not Found
Error:
   0: HTTP status client error (404 Not Found) for url (https://mise-versions.jdx.dev/aqua-registry/apache/maven/registry.yaml)

Location:
   src/http.rs:64

Version:
   2024.12.2 linux-x64 (d1b9749 2024-12-07)

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

And again, this may be an issue with mise, but I was going under the assumption that Apache Maven was available right away, similar to gocryptfs.

About aqua, we haven't released the new version of aqua-registry yet.

v4.270.0 is out. 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.270.0

there will be a delay for new tools added to the aqua registry of a few hours before they're in mise. You can avoid this by cloning the aqua registry

Thank you for your quick answer!
I'll update the document of aqua for mise users. 😄


pop ups in gamearena have not highest z-index

teammatehand and shametokens are displayed on top of pop ups

20446dd1f65cfff4da724d9e506edca8c9d300e2


Add owners and security contacts files

This adds owners and security contacts information.  Besides being
required by Kubernetes, this also will allow us to turn on the lgtm and
approve commands.

:tada: @spiffxp
cc @brancz @piosz
Added the SIG leads + people active in the project recently who are also current maintainers.  Can add more people later if need be.  If you're not on this list and you think you should be, file a PR once this merges.

lgtm (will wait for at least one more lgtm before merging I would say)

/lgtm

/lgtm


Task for control component

Hi,
trying to understand deeply the control module and so the control component, I would to know how many task are created when the control component is created and how they are managed. A task is created when the component start and the others when the component initializes the readers? And these task how are scheduled? They are in a thread pool or for this component not?
Thanks

Component
The cyber Component is divided to two types. one is event-base and another is timer-base. The control component is timer-base. The underlying implementation is still through a coroutine to perform tasks. You can adjust the priority in "cyber/conf/control_sched_classic.conf"
Reader
The reader in control module have no callback func, and do read in proc.
  chassis_reader_ =
      node_->CreateReader<Chassis>(chassis_reader_config, nullptr);   // callback is null
  ACHECK(chassis_reader_ != nullptr);

Therefore, these readers do not have any coroutine to execute it. If there is a callback func, then the callback func will called when the message is received, the function will be executed in an new coroutine.

There is a thread pool in Apollo to execute all the task? And what task does the scheduler class perform? what change between classic scheduler and choreography scheduler?

Simply say.

choreography have a pool but classic not.
They all set the scheduling order of tasks by setting the priority of the coroutine

You can choice only one of them.
By the way, classic is a subset of the choreography, because choreography have extra thread pool.

What is the difference between InnerThread and Task?

There are also thread used by apollo, and SetInnerThreadAttr will set cup set and cup affinity

InnerThread is thread
Task is coroutine

I understood that each class Processor instance is a thread, it is right? And these threads how start and run? Who schedule them?
What is the difference between an InnerThread and a 'processor thread'?

Processor instance is a thread, you can read more about go's GMP model,they are almost the same.
CreateProcessor create thread and bind to Processor, multi coroutine will run on Processor, and schedule by linux
InnerThread and a 'processor thread', there are the same, you can read more about coroutine

So, to sum it up. In apollo there are various threads, InnerThread and 'processor thread'. For example, an InnerThread is the TimingWheel that schedules all the timer components and sends to the 'processor threads' the task of the component, for example the Proc function of the control module. At the end the 'processor thread' schedules the tasks and run them. It is right?

Yes, you are right


Add missing word to message templates

This PR adds a missing word ('need') to the 3 matching message templates.
@sanisc

created again not as a fork but as a commit to the repo


Start 1.0.1

No review needed.

Coverage remained the same at 35.903% when pulling 7ff8a51ae7292d965af92c649a23d7350d785370 on start_1.0.1 into 5f3157ac758b92006d24c27b48ab7f57e1b67c5f on stable_1.0.


Fixed typo

Correcting the fonfigurations typo.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Apr 11 00:58:03 raspberrypi mopidy[22429]: INFO     [MainThread] mopidy.commands Starting Mopidy core
Apr 11 00:58:03 raspberrypi mopidy[22429]: INFO     [MainThread] mopidy.commands Starting Mopidy frontends: HttpFrontend, IrisFrontend, MpdFrontend
Apr 11 00:58:03 raspberrypi mopidy[22429]: INFO     [HttpFrontend-10] mopidy.http.actor HTTP server running at [::ffff:<IP_ADDRESS>]:6680
Apr 11 00:58:03 raspberrypi mopidy[22429]: INFO     [IrisFrontend-11] mopidy_iris.core Starting Iris 3.69.3
Apr 11 00:58:04 raspberrypi mopidy[22429]: INFO     [MainThread] mopidy_mpd.actor MPD server running at [::ffff:<IP_ADDRESS>]:6600
Apr 11 00:58:04 raspberrypi mopidy[22429]: INFO     [MainThread] mopidy.commands Starting GLib mainloop
Apr 11 00:58:05 raspberrypi mopidy[22429]: INFO     [MpdSession-13] mopidy_mpd.session New MPD connection from [::ffff:<IP_ADDRESS>]:33406
Apr 11 00:58:10 raspberrypi mopidy[22429]: INFO     [MpdSession-14] mopidy_mpd.session New MPD connection from [::ffff:<IP_ADDRESS>]:41438
Apr 11 00:58:15 raspberrypi mopidy[22429]: INFO     [MpdSession-15] mopidy_mpd.session New MPD connection from [::ffff:<IP_ADDRESS>]:41454

The authentification error appears during the boot procedure, as mentioned before, mopidy seems to try to connect to the server way before it has network access. So unfortunately no fix for me here.

Do you have a log showing your Mopidy Spotify issues? I cannot see anything in the above log.

I don't know enough about the project to know which logs exist or where I would find them, but if you tell me command I can check ;) I'll try to record another short video showing the problem.

Here is a short video of the mentioned error.

@AlvinSchiller You can delete the [core] and [logging] sections of the sample mopidy.conf. The former shouldn't be necessary since it's just the defaults, and the latter is wrong and causing an error at startup - it's harmless but it's unnecessary noise.
@jonaskor Yes, starting Mopidy before the network is ready doesn't work. There's a RPI OS config setting to wait for the network to be ready, I always suggest using it but if memory serves there is some issue with that here. However, once your network is ready and Mopidy starts properly I see no further errors.

After the manual mopidy restart, everything works fine.   My problem is only, that the restart is necessary after every boot of the system.

@jonaskor So just to confirm, you still can't play any Spotify tracks once you do the manual Mopidy restart?

After the manual mopidy restart, everything works fine. My problem is only, that the restart is necessary after every boot of the system.

Oh great! Sorry, I misinterpreted your earlier reply and thought it was always still broken.
Will enabling the wait for network setting in raspi-config work here @AlvinSchiller ? I have a vague memory of that setting causing a problem for some project because it messed up their logic to otherwise start a fallback WiFi access point. But maybe that was some other project, my memory is too bad....

Would that work?
https://pypi.org/project/Mopidy-WaitForInternet/

Looks like it would. Don't think I've ever seen that one. Of course won't help if you have any other services starting that need a working internet but maybe everyone else does it better than Mopidy.

@jonaskor I saw that you used the "autohotspot" features. I had a deeper look and identified a problem which might intensified your "login" problem. I made some changes and from my view its good to use now.
Would be awesome if you could test your case again.

Would that work?
https://pypi.org/project/Mopidy-WaitForInternet/

I didn't use this package for now, as my tests where successful, but will add it to the Spotify wiki entry.

Would that work?
https://pypi.org/project/Mopidy-WaitForInternet/

I didn't use this package for now, as my tests where successful and it might not fit every case. But will add it to the Spotify wiki entry.

It feels like a hack and takes advantage of Mopidy internals that could change. To me, a working network dependency is exactly the sort of thing that should be handled by systemd.

@jonaskor I saw that you used the "autohotspot" features. I had a deeper look and identified a problem which might intensified your "login" problem. I made some changes and from my view its good to use now. Would be awesome if you could test your case again.

This fixed things, awesome! Now the box connects to wifi within 20sec! Mopidy still needs another 3 to 4 minutes to connect to the server, but then everything works, no need for rescanning library or restarting mopidy anymore.  How cool is that! Thank you!
Since all the brain power already seems to be gathered here: any suggestions on how to speed up the connection time to the mopidy server? ;)

Mopidy still needs another 3 to 4 minutes to connect to the server,

Do you mean that Mopidy takes a long time from starting to becoming ready to use? That'll be the time it spends refreshing your Spotify playlists, I noticed in your log you had quite a lot (and immediately felt your pain).
The very latest (unreleased) version of Mopidy-Spotify is much improved in that respect and the refresh time is now hidden. I wasn't planning to do another pre-release that would include the fix since it'll be part of the upcoming Mopidy 4.0 release later this month. However, I've since learned/realised that this project (and maybe others) won't immediately be able to upgrade to Mopidy 4 because they need to remain on Debian Buster for reasons outside their control.
So long story short, I will see if I can easily backport the playlist refresh improvement since it's such a huge quality of life improvement.

Mopidy still needs another 3 to 4 minutes to connect to the server,

Do you mean that Mopidy takes a long time from starting to becoming ready to use? That'll be the time it spends refreshing your Spotify playlists, I noticed in your log you had quite a lot (and immediately felt your pain).
The very latest (unreleased) version of Mopidy-Spotify is much improved in that respect and the refresh time is now hidden. I wasn't planning to do another pre-release that would include the fix since it'll be part of the upcoming Mopidy 4.0 release later this month. However, I've since learned/realised that this project (and maybe others) won't immediately be able to upgrade to Mopidy 4 because they need to remain on Debian Bullseye for reasons outside their control.
So long story short, I will see if I can easily backport the playlist refresh improvement since it's such a huge quality of life improvement.

That would be so great!! Thank you for all your work, guys!

I published another Mopidy-Spotify pre-release including the playlist refreshing speedup.
sudo python3 -m pip install --break-system-packages Mopidy-Spotify==5.0.0a2

@AlvinSchiller this is the better version to use. It makes a considerable difference to startup time.

I published another Mopidy-Spotify pre-release including the playlist refreshing speedup.
sudo python3 -m pip install --break-system-packages Mopidy-Spotify==5.0.0a2

@AlvinSchiller this is the better version to use. It makes a considerable difference to startup time.

That was fast 🙂.
I will make the change to use it, asap 🙂👍

Version updated to 5.0.0a2.
@jonaskor if you by chance could verify this a last time, i think we would be ready to go :)

Version updated to 5.0.0a2. @jonaskor if you by chance could verify this a last time, i think we would be ready to go :)

Just installed the develop branch with the following command (in case anyone else wants to install it soon: cd; rm install-jukebox.sh; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/develop/scripts/installscripts/install-jukebox.sh; chmod +x install-jukebox.sh; GIT_BRANCH=develop bash ./install-jukebox.sh ).
And it works absolutely amazing! Thank you so much! Start up time of around 30-40 sec (on Raspberry Pi 4, Debian 32bit, Bullseye) until I am able to playback spotify songs and playlists! Awesome!


This documentation would be more useful if it had some examples.

For example, if you have a query with open bugs in it, and a lower and upper threshold is set to the defaults (of 0), when the gate will process correctly, and when it won't. I have a query with a bug in it, and I'm using the default values in the query deployment gate, but it's not failing as I would expect.
Currently this documentation is very short, just doesn't explain concepts well enough. What is the difference between the lower and upper threshold? In some parts of the document we refer to it as lower and upper, in others minimum and maximum. In what situations would changing the lower/minimum and upper/maximum values make sense?

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

ID: 6ccc264d-264f-b1e7-e5bf-eabe76ac36bc
Version Independent ID: 6e7213ee-23d6-2077-2df3-f5dec3c24d15
Content: Query Work Items task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/work-item-query.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Thank you for your feedback. The topic https://docs.microsoft.com/azure/devops/pipelines/release/deploy-using-approvals#configure-a-gate shows how to use the task, and explains a little more about the settings. Perhaps this will be useful. For questions related to the product rather than the documentation, you may also find the Developer Community website at https://developercommunity.visualstudio.com/spaces/21/index.html useful, where questions are tracked and answered by the product teams.


Feat: Limit plugin to vite build phase and run it at post stage.

Using enforce property of the vite-plugin interface to put the execution of the obfuscation after other vite plugins. Could resolve #144 if merged.

Ty!


Setup contributor guidelines, code of conduct, etc

Added and modified from the toolbox templates. Under the Code of conduct there's a contact email, is this still the same?

Make sure to refer to OpenActive apart from license.
hello [at] openactive.io for email.


Issue with snowflake_database_grant resource in Snowflake Terraform Provider when using a Data Share

Provider Version
Snowflake Terraform provider version: 0.62.0
Terraform Version
Terraform version: 1.3.4
Describe the bug
I am encountering an issue with the snowflake_database_grant resource in the Snowflake Terraform provider. Specifically, I have defined a resource to grant IMPORTED PRIVILEGES to a Snowflake role on a database that is created from a Data Share, using the following configuration:
However, when the IMPORTED PRIVILEGES grant is removed from the database outside of Terraform, and I run terraform plan, the plan reports that there are no changes to make, even though the Snowflake role loses the imported privileges that were originally granted via Terraform.
Expected behavior
The terraform plan should detect that the imported privileges have been removed from the database, and should report that the Snowflake role has lost those privileges.
Actual behavior
The terraform plan reports that there are no changes to make, even though the Snowflake role has lost the imported privileges that were originally granted via Terraform.
Code samples and commands
This is a sample of the database grant resource we have defined:
resource "snowflake_database_grant" "read" {
  for_each = toset(["IMPORTED PRIVILEGES", ])

  database_name = snowflake_database.this.name
  privilege     = each.key
  roles = [
    snowflake_role.read.name
  ]
  with_grant_option = false
}

Additional context
Steps to reproduce

Define a snowflake_database_grant resource in Terraform to grant IMPORTED PRIVILEGES to a Snowflake role on a database that is created from a Data Share.
Apply the Terraform configuration to create the grant in Snowflake.
Remove the IMPORTED PRIVILEGES grant from the database outside of Terraform.
Run terraform plan.

Please let me know if there is any additional information I can provide that would be helpful in resolving this issue. Thank you for your help!


load walking environment in UoE

If you'd like to do a skype call, I can demo the terrain code developed for walking the drc terrain.  Maybe it would be useful.

this is something much more basic. its just an environment for testing in sim


[WIP] Check for dirty records in save_inventory

Allow save inventory to skip starting a transaction if the record being saved was not actually changed by the provider's inventory data.
VMs and Storages still directly call update_attributes!.  At the moment, it doesn't seem like those object counts are limiting factors. If that changes, we can look at applying the same change there.

@blomquisg @Fryguy  so, problem with .changed? is that it doesn't work when using non standard attributes. That applies for Relationships, Ancestry and probably other special code. Also for after_update hooks. So for graph refresh I have these configurable and I've evaluated each use case, before I've switched it on.
So I think we should also makes this configurable, starting with evaluating possible big models:
these are top 15 sizes for a medium size OpenShift env:
CustomAttribute:  229909
ContainerEnvVar:  12302
ContainerImage:  9540
ContainerVolume:  5737
ContainerBuildPod:  2852
ContainerTemplateParameter:  2066
ContainerQuotaItem:  1968
ContainerCondition:  1884
SecurityContext:  1836
ContainerDefinition:  1836
ManageIQ::Providers::Kubernetes::ContainerManager::ContainerGroup:  1830
ContainerGroup:  1830
Container:  1806
ContainerReplicator:  1664
ContainerLimitItem:  984

I've check so far that CustomAttribute is ok. And ContainerImage is ok on 99%, the problematic setter is not used in refresh, so it should be ok.

@blomquisg I am getting great numbers with
From 46b905e2599aebf16b6f149c8f4ff72414ccce3b Mon Sep 17 00:00:00 2001
From: Ladislav Smola<EMAIL_ADDRESS>Date: Thu, 6 Apr 2017 12:28:30 +0200
Subject: [PATCH 1/2] Do not do blank transaction

Do not do blank transaction
---
 app/models/ems_refresh/save_inventory_helper.rb | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/app/models/ems_refresh/save_inventory_helper.rb b/app/models/ems_refresh/save_inventory_helper.rb
index ca73888..f694fbe 100644
--- a/app/models/ems_refresh/save_inventory_helper.rb
+++ b/app/models/ems_refresh/save_inventory_helper.rb
@@ -101,9 +101,7 @@ module EmsRefresh::SaveInventoryHelper

   def update_attributes!(ar_model, attributes, remove_keys)
     ar_model.assign_attributes(attributes.except(*remove_keys))
-    ar_model.with_transaction_returning_status do
-      ar_model.save! if ar_model.changed?
-    end
+    ar_model.save! if ar_model.changed?
   end

   def backup_keys(hash, keys)
--
2.7.4

removed 500k queries, for 250k records present, but that is the case when nothing gets updated
From bab528355f6abc42cbb49112c6f00eb821735c57 Mon Sep 17 00:00:00 2001
From: Ladislav Smola<EMAIL_ADDRESS>Date: Thu, 6 Apr 2017 12:51:22 +0200
Subject: [PATCH 2/2] Wrap updating in 1 big transaction

Wrap updating in 1 big transaction. Doing transaction per
update is expensive, since we do BEGIN, update, END, so 3 queries
per one update. With remote DB, this will make add a lot of
processing time.
---
 app/models/ems_refresh/save_inventory_helper.rb | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/app/models/ems_refresh/save_inventory_helper.rb b/app/models/ems_refresh/save_inventory_helper.rb
index f694fbe..89578e4 100644
--- a/app/models/ems_refresh/save_inventory_helper.rb
+++ b/app/models/ems_refresh/save_inventory_helper.rb
@@ -52,17 +52,21 @@ module EmsRefresh::SaveInventoryHelper
     record_index = TypedIndex.new(association, find_key)

     new_records = []
-    hashes.each do |h|
-      found = save_inventory_with_findkey(association, h.except(*remove_keys), deletes_index, new_records, record_index)
-      save_child_inventory(found, h, child_keys)
+    ActiveRecord::Base.transaction do
+      hashes.each do |h|
+        found = save_inventory_with_findkey(association, h.except(*remove_keys), deletes_index, new_records, record_index)
+        save_child_inventory(found, h, child_keys)
+      end
     end

     # Delete the items no longer found
-    deletes = deletes_index.values
-    unless deletes.blank?
-      type = association.proxy_association.reflection.name
-      _log.info("[#{type}] Deleting #{log_format_deletes(deletes)}")
-      disconnect ? deletes.each(&:disconnect_inv) : association.delete(deletes)
+    ActiveRecord::Base.transaction do
+      deletes = deletes_index.values
+      unless deletes.blank?
+        type = association.proxy_association.reflection.name
+        _log.info("[#{type}] Deleting #{log_format_deletes(deletes)}")
+        disconnect ? deletes.each(&:disconnect_inv) : association.delete(deletes)
+      end
     end

     # Add the new items
--
2.7.4

should be doing 1 query per update, instead of 3

@blomquisg I've done the changes in https://github.com/ManageIQ/manageiq/pull/14670

Closed in favor of https://github.com/ManageIQ/manageiq/pull/14670 which mostly includes these changes


AP-5394: Update SCA review and print

What
Link to story
Update the review_and_print and submitted_application pages:

hide the email row from client if it is empty
hide the emergency level of service and scope limits for SCA DF applications
hide the Emergency cost limit block for SCA DF applications
hide the separate representation block on the submitted_application page too.  It will _only_appear on the merits_report now

Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
The standards in the Git Workflow document on Confluence should be followed
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

Looks good.
Considering your CYA amendment to "hide the email row from client if it is empty", in general, should we also hide all other relevant CYA sections if they are empty? New ticket?


allow mounting in userlist file for pgbouncer

This allows setting up a file for auth_file, which I believe is required if you want to set stats_users for monitoring pgbouncer. You can already set auth_file and stats_users via values.yaml, this just adds the final piece.

@feikesteenbergen can you review this?

@feikesteenbergen can you review this?


Update yargs package version

In newer versions of Node, Yargs comes without index.js, preventing the CLI from running.
Node: v14.17.1
Yarn: v1.22.10

Okay, I just have the problem that yargs doesn't come with index.js when I install via Yarn.

Seems to settle for now
"resolutions": {
    "typeorm-seeding/yargs": "15.5.0-candidate.0"
},


Search function on new app doesn't seem to include applicant names, can we add that?

What fields are being indexed now and can we include the applicant name as was the case in the previous app?

@danblah Is this the main site search or the submission search on /submissions page?
Sent with GitHawk

Submissions page.


Add testing of upgrading of latest released chart version to CI

Motivation
It is important that new chart version don't introduce breaking changes that prevent upgrading a cluster from an older version to the newest version.
Modifications

Remove "basic" test scenario and replace it with "upgrade".

Add 2 upgrade scenarios for upgrading the PSP and TLS configurations

Upgrade installs the latest released chart version & produces 2 messages to a Pulsar topic

It upgrades the cluster and then consumes the 2 messages

Adds "metallb" for k8s loadbalancer support so that --wait will work with helm upgrade. Previous waiting for a deployment to complete never succeeded since the load balancer didn't get an IP. Installing metallb to kind solves that problem.

Verifying this change

[ ] Make sure that the change passes the CI checks.

Merging since this is needed for testing other PRs.


Question: Can we check for DNSSEC?

Hi,
I was wondering whether it's possible to check for the AD flag or similar to assert that a domain has DNSSEC enabled.
Cheers!

I am not actively working on it these days, but a PR is always welcome


Python Packaging Tools: Slap

I recently came across your post on Python Packaging Tools :ok_hand:. You may be interested in slap-cli.

Thanks for the hint, I will put it on my list of tools to look at!


Build framework as a 3rd-party lib

Pull the framework/ folder out, build it as a third party lib/jar
When other people write apps for PMCA, they'll just have to include that lib/jar in the build path, without having to copy the framework code.
(Optionally put that lib/jar in maven repository, so that it can be added as a maven/gradle/... dependency)
I can assist on this - Let me know if you want me to help

I'm planning to do this eventually. For the time being, i'm just investigating in the APIs and it's IMHO easier to have everything in one single project. Especially because I don't know yet in which form we will release this framework, whether we have to add a custom intermediate code layer for example.
The framework directory contains just some stubs for the Sony APIs. They are more or less auto-generated from the unpacked firmware.
So I would propose to wait a bit before we really release the framework.

Ok....
Do you need help in any specific item? Are you looking at the firmwares for a specific camera, or for all available cameras?

Mainly testing atm... I only have an a6000, it would be great if you could test everything on your camera, too.
The stubs come mainly from the nex6 which is one of the oldest cameras with android apps enabled (just after the nex5r). The features present in this camera should (hopefully) work on most newer cameras, too.

I had the Nex-6 (now sold) and tested successfully all functions of PMCADemo until v0.6...
I tried to compile some useful code from other camera apps but the whole implementation was too changeling for my code expertise, LOL
I am now waiting to get the A7 or A7II and hopefully all should work too...

Any development on the framework (library) side?

Sorry, been bit busy at work, didn't have much time to work on this
If you look at my fork, I've added code that makes it easier to browse and
dump the filesystem of your current camera (instead of just working on the
decompiled nex6). If you have an A7, share the jars?(I'll share mine later
tonight)
Think I have time to look at it in a few weeks when things quiet down
On Oct 20, 2015 6:13 AM, "lh8511"<EMAIL_ADDRESS>wrote:
Any development on the framework (library) side?
—
Reply to this email directly or view it on GitHub
https://github.com/ma1co/PMCADemo/issues/3#issuecomment-149510746.

Ok thanks,
Will check

@ngvincent
I still do not decided which version of A7 to get! Will be probably A7ii or simple A7.
Anyway I got a dump for A7s in my disk. What Jars do you want?
-What camera do you have?

Hi everyone, sorry for my late answer, I've been very busy in the last months and couldn't work on this.
In the last few days, I reverse engineered the USB communication between camera and browser plugin. I mean, nobdy wants to use IE :) I just pushed my results to the other repo.
Concerning the framework, my goal is to develop an abstraction layer with a nice scripting interface, so people can write their own scripts (probably JavaScript, since interpreters are easy to integrate) and have them interpreted on camera. That would lower the entry barrier for many people. What do you think?

Welcome ma1co.
A scripting interface would be very cool.

@ma1co as someone that works as a designer and a front end designer that would be pretty awesome since javascript is one of the few languages i actually understand :+1:

hi @ma1co , I have tested the python code with a7s and it work great, also the apk install well !
Now i'd like to write an app to force 4k internal recording, I am trying to build an APK from your PMCADemo project, but i am not able. I don't know very well android programming. Please what i have to do to build the APK ?
At the moment i found Android Studio, with Android 2.3 Platform SDK, but something go wrong.
Please help me, thank's a lot

I've pulled out the stubs and I'm currently writing a new abstraction framework around them: OpenMemories-Framework.


Evaluation results not accurate?

Hi,
I've been trying to recreate your results from the Hybridnets paper. I've run the eval code on the 100k dataset but the results I'm getting are nowhere close to the actual results you presented in the paper. I'm sure I'm missing something here, could you please tell me what could possibly be going wrong here.
I think the root locations that I'm giving are inaccurate.

data root - raw images from the 100k dataset
label root - I saved separate json file for each image from the "bdd100k_labels_images_val.json" that I downloaded from the bdd100k dataset. So in total I saved 10,000 separate json (one for each image) into another folder named "val".
Road labels in Seg_list - I used the drivable masks
Lane labels in Seg_list - I used the lane masks

The output that I got after evaluation of 100 images:

The iou values are inconsistent with the ones mentioned in the paper, they are nowhere near them. I was also wondering why the precision is so low, is there a specific reason as to why there are so many false positives. I hope you can help me out, thanks.

This is what I got with 100 images. Are you sure you're using the same road and lane labels as us? You can uncomment some cv2.imwrite blocks in dataset.py to check if they're correctly set up.
Precision is low because we chose the confidence threshold where Recall is maximum to print out. It's reasonable that when confidence threshold is lower, you get more predictions (recall up) but they may not be correct (precision down).

Thanks a lot, I was indeed giving wrong mask location, I changed it to colormasks and now I'm getting the correct values. For the precision values, it should increase if I increase the confidence threshold right?

@luceeleven yeah, try python val.py --conf_thres 0.5 now


Bump resources for EKS-A CLI presubmit

2 vCPUs are better than 1.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


[BUG] Potential bug when do batch inference

Hi,
I tried to modify the code for batch inference but found one bug,
In the prepare_inputs_labels_for_multimodal if we provide attention_mask but not given labels, then when execute L187, the  local variable _new_labels referenced before assignment,
https://github.com/haotian-liu/LLaVA/blob/539d666848245a7075fb485cee5706e68e0489d2/llava/model/llava_arch.py#L187-L191
So I guess maybe we need to change the logic as L199-L202 did, that pad attention_mask just dependent on the new_input_embeds.shape[1] - input_ids.shape[1]
Best,

Hi, we have rewritten the multimodal processing function and this should be addressed. Also, I am trying to work on an efficient batch inference. Closing this and consolidating the discussion to https://github.com/haotian-liu/LLaVA/issues/754. Thanks.


more WARNING and deprecated

conda deactivate
conda remove --name EDSR36 --all -y
conda create -n EDSR36 -y python=3.6.4
conda activate EDSR36
conda init zsh
export PATH="$HOME/anaconda3/envs/EDSR36/bin:$PATH"
which pip python
pip install -r requirements.txt -i https://mirror.baidu.com/pypi/simple

python main.py --upscale --scale  4 --image  ../1-012.jpg --out xxx.npg
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/Users/51pwn/anaconda3/envs/EDSR36/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
python main.py --upscale --scale  4 --image  ../1-012.jpg --out  222.jpg
WARNING:tensorflow:From main.py:61: The name tf.ConfigProto is deprecated. Please use tf.compat.v1.ConfigProto instead.

WARNING:tensorflow:From /Users/51pwn/MyWork/51pwn4ai/EDSR_Tensorflow/run.py:221: The name tf.gfile.GFile is deprecated. Please use tf.io.gfile.GFile instead.

WARNING:tensorflow:From /Users/51pwn/MyWork/51pwn4ai/EDSR_Tensorflow/run.py:222: The name tf.GraphDef is deprecated. Please use tf.compat.v1.GraphDef instead.

WARNING:tensorflow:From /Users/51pwn/MyWork/51pwn4ai/EDSR_Tensorflow/run.py:296: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.

@Saafke


Why is meshopt_simplifyWithAttributes (silently) limited to 16 attributes?

The meshopt_simplifyWithAttributes seems to be limited to 16 attributes (i.e. 16 "floats") maximum. It will assert in the debug build, but corrupt the stack in a release build. That does not seem to be documented in the header.
But! I'm wondering why exactly 16 attributes. For a use case of say (float3 normal, float4 tangent, float2 uv, float4 blendWeights, float4 blendIndices), that is already 17 attributes. Could the limit be bumped up? There is kMaxAttributes which sounds like an easy change, just not sure if there are some negative effects of that.

Yeah the limit should be documented, I'll fix this.
If you'd like to change this locally / in your copy for testing, that seems completely fine. In the current state of the code this only marginally impacts one function; that function in theory could even be rewritten to not rely on stack space and the limit could be lifted altogether. However, this algorithm is in the state of much needed further development (which hopefully foreshadowing I will be able to dedicate some time to next year), so I'm reluctant to change this, or the limit, at the moment. The limit is 16 because it's about double what I tested :) (UV/normal/color combination)
In general right now due to how the metrics for the algorithm work (which I need to somehow fully rework - they're based on state of the art research from 1999, nothing new has come out since, but they are not actually good enough for complex reasons this margin can't contain), I think it's unreasonable to just put your entire vertex into the algorithm and hope it magically figures it out.
In my testing I found it becomes harder and harder to tune the weights and balance the impact of attributes vs geometry (something else I hope to try to figure out a better solution for) as you increase the number or complexity of attribute data. Even with UV + normal + color it was not obvious what the weights should be and how to guide the algorithm to be making obviously better decisions - again in part due to the fact that the metrics aren't final.
Additionally, the algorithm works best when you give it decorellated and interpolatable data. Someone even tried to change the normal representation in the past and had better results; so I'm very skeptical that for example giving the algorithm both normal and tangent data makes it better at all, and just normal plus maybe a tangent flip with a large weight would suffice.
Giving the algorithm bone indices and weights is going to backfire. The indices aren't interpolatable or stable and don't even have a meaningful distance metric. Vertices nearby will have a different index set, sometimes in a benign fashion - eg switching from ABCD to ABDE, or worse from ABCD to BACE, and this will not end well. I suspect that in terms of representative power, the blend weight/index representation above is about equal, maybe worse, to just two floats - single dominant bone index and its weight. It will still be unstable etc but will be a little more stable. Ideally you don't even want this - you probably want to skin the mesh to a different pose and feed the resulting vertex position as an attribute...
So basically right now I feel like it's really not practical to just feed everything as is and hope for the best.
Of course, if the metric and the implementation were more final, the limit would be fairly inconsequential, but I'm highlighting the fact that if right now you think you're bumping against the limit, you're probably actually not :) Let me know if that makes sense.

Oh, but again, I'd highly encourage experimenting with higher attribute counts and higher limits. If there's results that say "oh actually it's completely fine, here's the attribute set and weights and see it works great" then it would be a great motivation to bump the limit and maybe even rework the code to not carry a stack buffer proportional to the limit, it's just not obvious to me right now that it's necessary.

Yeah, all good points! I only initially was a bit puzzled until I realized to build in debug and hit the assert. Thanks for the in-depth explanations and for updating the docs.


CX Code_Injection @ core/apphandler.js [master]

Code_Injection issue exists @ core/apphandler.js in branch master
The application's function method receives and dynamically executes user-controlled code using eqn, at line 194 of core\apphandler.js. This could enable an attacker to inject and run arbitrary code.
The attacker can inject the executed code via user input, eqn, which is retrieved by the application in the function method, at line 194 of core\apphandler.js.
Severity: High
CWE:94
Vulnerability details and guidance
Checkmarx
Recommended Fix
Lines: 197 39

Code (Line #197):
			output: mathjs.eval(req.body.eqn)

Code (Line #39):
	exec('ping -c 2 ' + req.body.address, function (err, stdout, stderr) {

Issue still exists.
SUMMARY
Issue has 2 vulnerability/vulnerabilities left to be fixed (Please scroll to the top for more information)

Issue still exists.
SUMMARY
Issue has 2 vulnerability/vulnerabilities left to be fixed (Please scroll to the top for more information)

Issue still exists.
SUMMARY
Issue has 2 vulnerability/vulnerabilities left to be fixed (Please scroll to the top for more information)

Issue still exists.
SUMMARY
Issue has 2 vulnerability/vulnerabilities left to be fixed (Please scroll to the top for more information)


Pagination

Hello and thank you for such a great library, two questions — is this project intended for use as documentation builder or can one build blog with it?
If it is possible to build static blog with Ivy, then i should ask if pagination can be implemented?

https://mulholland.xyz/docs/ivy/faq.html#can-i-build-a-blog-using-ivy
Text:
Sure, but you'll have to write some code to do it.
Ivy is actually a stripped-down version of an older static website generator that I tinkered with for years called Malt, which was fully blog-capable. One of the lessons I learned along the way is that it's pretty much impossible to build a simple, elegant, general-purpose static-website-plus-blog engine — it just ends up being a WordPress-style rat's nest of options and switches.
It's actually quite easy to build a blog on top of Ivy by adding a simple plugin to assemble indexes, etc. — at least, it's easy to do it for one specific site. I've certainly thought about building a general-purpose blog plugin, but it inevitably turns into its own mini rat's nest of options and switches all over again.
I don't have any personal use for a blog so I probably never will get around to working on the problem again, but if anyone else wants to try they're welcome to take a look at Malt for inspiration.

Thank you for detailed answer.

Thanks @KricketK. Sorry about the slow response @asyncee. Ivy is optimised for building simple sites but you could take a look at the indexing and pagination code in Malt and consider adapting it for your own use.


Update framework to 8.13.2

About this PR
📦 Updates org.elasticsearch.test:framework from 8.13.1 to 8.13.2
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.elasticsearch.test", artifactId = "framework" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.elasticsearch.test", artifactId = "framework" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #337.

Superseded by #343.


_posts/0000-01-02-jdm85.md

The following vulnerabilities are fixed with an upgrade:

https://snyk.io/vuln/SNYK-RUBY-RUBYZIP-469156

_posts/0000-01-02-jdm85.md


dummy

A dummy PR to test CI

?

Found the bug we were looking for

Found the bug we were looking for

(https://github.com/Granulate/gprofiler/pull/147)


fix: Start using all required fields from allOf (box/box-codegen#551)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

3 of 34 (8.82%)  changed or added relevant lines in 5 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.04%) to 69.934%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Box.Sdk.Gen/Schemas/FolderFull/FolderFullPermissionsField.cs
0
3
0.0%

Box.Sdk.Gen/Schemas/IntegrationMapping/IntegrationMapping.cs
0
6
0.0%

Box.Sdk.Gen/Schemas/IntegrationMappingBase/IntegrationMappingBase.cs
0
9
0.0%

Box.Sdk.Gen/Schemas/FileFull/FileFullPermissionsField.cs
0
13
0.0%

Files with Coverage Reduction
New Missed Lines
%

Box.Sdk.Gen/Schemas/FolderFull/FolderFullPermissionsField.cs
1
0.0%

Box.Sdk.Gen/Schemas/FileFull/FileFullPermissionsField.cs
1
0.0%

Box.Sdk.Gen/Schemas/IntegrationMappingBase/IntegrationMappingBase.cs
1
0.0%

Box.Sdk.Gen/Schemas/IntegrationMapping/IntegrationMapping.cs
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.04%

Covered Lines:
6940

Relevant Lines:
9914

💛  - Coveralls


Drop circleci, add githb actions and refators

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area falco-chart
What this PR does / why we need it:

add dependabot config
move to a charts directory to make it more clean
drop circleci config
add github actions workflows for testing and release

bonus point: it will push the oci chart to the github registry as well :)
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] CHANGELOG.md updated

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

Needs approval from an approver in each of these files:

OWNERS [cpanato]

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

as a follow up we can sign the chart with gpg, but will require someone to create the keys

/assign @leogr @LucaGuerra
also will need someone with admin access in circleci to remove the job from there

looks like falco-exporter failed, checking

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

77496ae testing

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.

also, the release might failed when we merge this because it see those charts as new charts. But after we merge this i will follow up to make sure everything will work
i did some tests in a sample repo and that works, and got the same issues as here

for the falco-exporter maybe we ignore that for now and i will test asap we merge this

now it is fixed :)

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

Needs approval from an approver in each of these files:

OWNERS [Issif,cpanato]

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

LGTM label has been added.  Git tree hash: 10ddc154b31b8ddd96ea954c17e1db5fde288121


Initial import

Initial import of existing web component, plus test scripts and a dev environment.
Tested like:

yarn test - Runs the basic unit tests written
yarn build - Builds two versions of the lib; one cjs version for use with a bundler, and one iife version for direct loading using a script tag
yarn dev - Run storybook, which includes stories for testing out the web component

Todo:

[ ]  License
[ ]  Port old build routine from dev-docs
[ ]  Npm publish script + dist files
[ ]  Some integration tests?
[ ] Add remaining params to storybook

Love to see it 🤩 I think both the project structure and the exectuion is great. Nice idea to have a storybook we can use to test, the only question is what room URL to use I guess 🤔

Love to see it 🤩 I think both the project structure and the exectuion is great. Nice idea to have a storybook we can use to test, the only question is what room URL to use I guess 🤔

Yea, that is the question. Either Ill make it a regular param in the story, or allow something like yarn dev <roomname>

Lovely!

Worked well for me, I was able to run a storybook via STORYBOOK_ROOM=<roomUrl> yarn dev, setting different parameters works as well (apart from the ones that aren't added yet).
Would it be possible to have a way to trigger commands e.g. toggleCamera() from storybook as well?


Update version info

I did put 6.x, since I thought these docs would be released together with 6.x so it would fit. A more generic text would probably would be helpful to not update the page on every release. But I can also create more pull requests for the other branches.

Reading this, it seems to be OK since it is stated to be an example from the time of writing. Hence we can leave it as it is or apply this patch and it should be fine.
On July 9, 2018 6:05:54 PM GMT+02:00, Per Pascal Seeland<EMAIL_ADDRESS>wrote:

I did put 6.x, since I thought these docs would be released together
with 6.x so it would fit. A more generic text would probably would be
helpful to not update the page on every release. But I can also create
more pull requests for the other branches.

Ok, makes sense.
@pascalseeland Thanks for the patch!


Fixed "Error: SVC is not permitted on this architecture"

The error
Error: SVC is not permitted on this architecture

will appear when using newer arm-none-eabi-gcc. Setting -march=armv6s-m will fix it.

Yes. This was a GCC change after we stopped using this repo.


Loading submodules' content in VSCode web

It would be helpful if the web version of VSCode also loads the (content of the) submodules of Github repos.
Currently, VSCode web only recognizes submodule and displays an empty "dummy" folder for each submodule.

Duplicate of https://github.com/microsoft/vscode-remote-repositories-github/issues/291


Show properties window for shared projects

Customer scenario
Opening the properties page of a C# or VB Shared Projects, opens the AppDesigner and displays an error.
Bugs this fixes:
Fixes: #833
Fixes: #1325
Workarounds, if any
You can change properties by opening the Properties Window tool window itself and selecting the Shared Project in Solution Explorer.
Risk
Low
Performance impact
None
Is this a regression from a previous update?
Yes
Root cause analysis:
Shared Projects and .NET Core share the same code base. A component was incorrectly marked as applying to all "C#" and "VB" projects, when it really only applied to C#/VB projects that support the Application Designer.
With this change, shared projects revert to their VS 2015 behavior which is to display the Project Properties tool window.
How was the bug found?
Customer via VS Feedback.
Dev Notes
Show the properties window instead of the AppDesigner for shared projects to be consistent with what we did in VS 2015.
CPS uses the presence of any property pages to decided whether to show AppDesigner or not.

tag @dotnet/project-system
@adrianvmsft, this also fixes your bug.

Tagging @MattGertz  for approval.

Regression; approving to take to Shiproom.

Shiproom Approved to merge via 378323


Playwright.Keyboard

Before I dive in and try to push Keyboard features, anybody else work on this? I'd hate to duplicate effort. Also, if theres any pointers or suggestions, this would be a good way to track it.

It's a good question and request.
I had some trouble figuring out how I wanted to structure things when introducing Accessibility as a sub-resource of Page. The OO patterns in the other implementations don't translate seamlessly into our module/functional world.
Sometime after adding Accessibility, I added Locator. I'm pretty happy with that result. In particular:

Locator is its own, standalone module (which is also true for Accessibility).
Page.locator/2 returns an instance of Locator, with selectors scoped to the provided page.

I'd like to go back and make the Accessibility API be like Locator, while still scoping the module under the Page namespace (Accessibility is logically part of Page, while Locator might be associated with other resources).
I suggest that Keyboard should be a module under Page (there's already a placeholder file there) and be modeled after Locator.

Oh, to the "anybody else work on this?" question, not yet. Happy to have more of your contributions, @dbrody :)


l99 example setup - fix mazak machine reference

bb: The example setup does watch one device in the mazak agent
ob: Yeah, it is in the config, however, when I open Grafana, it is blank (no machines). Maybe I miss some steps …

@bburns where and what is the problem here?
https://github.com/Ladder99/ladder99/blob/fc96345058b35d11d16ce8455404a27c2ac64521/setups/example/setup.yaml#L65
https://github.com/Ladder99/setup-demo/blob/main/setup.yaml
https://github.com/Ladder99/setup-test/blob/main/setup.yaml

Maybe there is no problem at all, maybe there was an issue my config. :thinking: All MTC demo agents from Mazak work as expected now.

User issue.

That mazak might have been off at the time - I made a note in the docs that can happen -

The dashboard will show the LIVE status of a Mazak CNC machine, as provided by Mazak (note: the machine may be OFF at certain times of the day) -

That mazak might have been off at the time - I added a note in the docs -

The dashboard will show the LIVE status of a Mazak CNC machine, as provided by Mazak (note: the machine may be OFF at certain times of the day) -


Implement "Tournaments" tab

Tournaments are not a big thing atm, and the current client's implementation is the worst thing ever. Not going to do this for now.


Pull Request

Git workshop pull request

Done!

But it showing whole HTML changed in review including other users' commits

Closing this issue as your name was added in another PR.


changed task helper to actually get all the tasks when get_tasks is run

This PR fixes the command get_tasks. It is returning one task, which doesn't make sense because the word tasks is plural, i.e. not one task, all the tasks from the tasks family should be returned.  I need this PR to be merged in order for this viv-task-dev PR to get merged which will then allow me to resolve this MP4 PR which is needed for this issue
Details:

I need this merged in order for the get_tasks! command to work properly in viv-task-dev according to the readme line 36. So it follow that we shouldn't need to pass in a task name, only a task family name (dir name) into the command.
Watch out:

pyhooks api breaking change (breaks old pyhooks versions)

I'm concerned that something might depend on this non working as intended command, but I searched around and didn't see usage.
Documentation:

None needed, fixing existing code.
Testing:

manual test instructions: Copy the taskhelper.py file into a task container and run python scripts/taskhelper.py avoid_shutdown get_tasks
I tested on a couple task in mp4. That data is sensitive and I won't put it here, but it returns all the tasks as expected.

Testing: I installed viv-task-dev and had it use the code from this branch. tasks! abc inside the container printed all tasks instead of just one (note that I did still have to pass a task name but fixing that will be a different PR).

@tbroadley fixing that is in this PR if you want to approve since you have this in context :) https://github.com/METR/viv-task-dev/pull/26


nohup $atom_path etc...etc..

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Crash on launch with error
/usr/bin/atom: line 86: 1983389 Trace/breakpoint trap   (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[1983389:0321/185955.067741:FATAL:electron_main_delegate.cc(254)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

Steps to Reproduce
run atom
Expected behavior:
It would launch with no errors such as.
/usr/bin/atom: line 86: 1983389 Trace/breakpoint trap   (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[1983389:0321/185955.067741:FATAL:electron_main_delegate.cc(254)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

Actual behavior:
it does not launch and produces the error.
/usr/bin/atom: line 86: 1983389 Trace/breakpoint trap   (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[1983389:0321/185955.067741:FATAL:electron_main_delegate.cc(254)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

Reproduces how often:
Every time.
Versions
apm 2.6.4
atom 1.58.0
os Garuda Linux aka arch.
Kernel 5.16.14-zen1-1-zen
python 3.10.2
npm 6.14.9
Additional Information
Have run shotgunned fixes from about 15 different 'similar' issues. Reinstalled, removed, rebooted, cleared and cleaned, installed on an entirely blank version of the same os. No joy.
also of note: I am not running it as root.
Running it like
sudo atom --no-sandbox

works.
also of note running in safe gives me the error.
/usr/bin/atom: line 86: 2005894 Illegal instruction     (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1

(electron9:2006168): Gtk-WARNING **: 19:30:28.295: Theme parsing error: gtk-dark.css:5822:26: '-shadow' is not a valid color name

(electron9:2006168): Gtk-WARNING **: 19:30:28.295: Theme parsing error: gtk-dark.css:5825:14: not a number

(electron9:2006168): Gtk-WARNING **: 19:30:28.295: Theme parsing error: gtk-dark.css:5826:13: not a number

(electron9:2006168): Gtk-WARNING **: 19:30:28.295: Theme parsing error: gtk-dark.css:5827:11: Expected a length
204 No Content
2022-03-21 19:30:27 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

Unexpected crash report id length
Failed to get crash dump id.
Report Id:

Is atom just having a problem with my theme?

Have tried changing themes to several different ones including default and nothing. No idea if that is the problem, but I see the words to I might as well try right? XD

have you tried running atom in safe mode? atom --safe ?

For anyone else with the same issue, running atom with the --no-sandbox flag works (workaround found here, and there's other fix suggestions in that thread)


Reduce latency with DXGI 1.3 GetFrameLatencyWaitableObject

Summary of the Pull Request
Reduce input lag, especially with selection, by using IDXGISwapChain2::GetFrameLatencyWaitableObject.
I hope that it's visible on these GIFs:
Before:

After:

References
I used the documenation from:
https://docs.microsoft.com/en-us/windows/uwp/gaming/reduce-latency-with-dxgi-1-3-swap-chains
From https://docs.microsoft.com/en-us/windows/win32/direct3ddxgi/dxgi-1-3-improvements:

The following functionality has been added in Microsoft DirectX Graphics Infrastructure (DXGI) 1.3, which is included starting in Windows 8.1.

PR Checklist

[ ] Closes #xxx
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
Before, during rendering:

render frame
call Present on swap chain:

blocks until it can present
meanwhile, selection/text in terminal might have changed, but we're still using the frame that we rendered before blocking
presents

After, during rendering:

block until we can present
render frame with latest data
call Present on swap chain:
present without blocking

Validation Steps Performed

Okay this looks incredible. I'm wondering if there are any other perf gains beyond just input latency that this gets us 🤔
Before I even get to reviewing this, let's make sure we get the expert on this one:
@msftbot make sure @miniksa signs off on this

Okay actually spoke with @miniksa offline - he's OOF today, but he mentioned that this probably needs a fallback for Windows 7, since the DirectX renderer is also used by the WpfControl, which works back to win 7.
I don't know how that would work, but he'll provide more details tomorrow if needed.
He also mentioned that you must be some sort of crazy mind reader, because he had the exact same thought last night as he was trying to fall asleep, and he's on to you 🕵

Wow!! This looks amazing
Offhand, I’m wondering if this is part of the DX Platform update that was backported to Windows 7!
If not, we may need version guards. Parts of this project, including the renderer, have to maintain Win7 compatibility :(
If you already have version guards, sorry, I haven’t looked at the code :smile:

At this point, MS no longer officially supports Win7. As an MS project, I think it would be ok to break compatibility. However, as I mentioned above, we can just use software rendering as the fallback if it fails to render.

The WPF control is a MSFT project that Visual Studio depends on, and they need to work on Windows 7, I'm gonna say it's not okay to break back-compat for them

I added version guards for windows 7. I can remove them later if they are not needed. But I did not test them on windows 7 because I don't have windows 7.


[Snyk] Upgrade supertest from 6.3.0 to 6.3.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade supertest from 6.3.0 to 6.3.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 23 days ago, on 2022-10-24.

Release notes

Package name: supertest

6.3.1 - 2022-10-24
fix: bump superagent (closes #798)  25122e6

v6.3.0...v6.3.1

6.3.0 - 2022-10-04
fix: lint package.json, added files array  20adbc1
Merge pull request #793 from lamweili/feat/http2  22b89b6
Merge pull request #795 from lamweili/code-coverage  a225e95
Merge pull request #794 from lamweili/migrate-cov  fa129dc
test(#767): 100% code coverage  9c5bd92
ci: migrated code coverage from coveralls to codecov  46e6feb
feat: supports http2  da57804
Merge pull request #767 from alexandre-abrioux/expect-stacktrace  e064b5a
Merge pull request #774 from jmccure/update-promise-example-readme  ba4b43b
Merge pull request #792 from lamweili/refactor/test  b8c2e29
ci: added ci  da1e842
refactor(test): do not hardcode any ports, use ephemeral ports  8847310
refactor(test): do not have both s and server, renamed to server for consistency  c1c4402
test: 100% test coverage  8bf4c14
refactor(TestAgent): removed the host param when creating Test object  1c8930d
feat(TestAgent): decoupled TestAgent and superagent's Agent to support more than ca, key, cert 5e23869
fix(TestAgent): attach cookies to agent after plugin is used  6d9b9cb
Update promise example to work with Mocha  5862fe6
fix: add stacktrace to failed expect function call  3dba4e9
test: add failing test  b24da85

v6.2.4...v6.3.0

    from supertest GitHub release notes

Commit messages

Package name: supertest

ca353dd 6.3.1
25122e6 fix: bump superagent (closes #798)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Coverage remained the same at 85.625% when pulling 5286c038afd4f4c88c798460397aeac35a808fd2 on snyk-upgrade-30e9568e0792213d33704d3026e76bd8 into 15264fa85051e862007f9a87177d922212c3a64e on main.


Books Slug Change

Need to change the Books navigation slug from "cracking-open" to "books". But before we make the change we should add a 301 redirect.

[x] 301 Redirect
[x] Change "cracking-open" slug to "books"

@asc313x heads up that I changed the slug for /cracking-open to /books and altered the htaccess file for the 301 redirect. These are not pushed to GitHub so avoid changing them on the web server.


Add functionality to utility commands

The empty class we call Utility commands now needs to have functionality added to each slash command.
Utility Commands

/update -> updates a record (Gimpy)
/delete -> deletes a record (Skye)
/reset -> resets the db, deleting all channels (Skye)
/insert -> img, message etc. (Skye)
/join -> joins two tables together (Gimpy)

~Delayed due to being unable to interact with the database at this time.~

Done with #82 .


FlattenRegionStreamHashImageFilter post merge stuff

Description
see #711
check if flatten work with compressed textures
In 24th example right after loading texture I've applied flatten filter, and used output image for the rest of program - displaying works; hashing passes (content hash for output image from CFlattenRegionsImageFilter is not set - we get zero hash instead - works fine after recalculating content hash).
Tested against Block Compression (BC1,BC3,BC7)
TODO list:

[x] remove unused variables
[x] ICPUBuffer to corresponding span
[x] move code from assert
[x] check if flatten work with compressed textures
[x] zero-lenght hash
[x] iota -> custom iterator

where definition of ValueIterator should be located?

where the definition of ValueIterator should be located?

if you just need an iterator that goes over integers from S to S+N there's https://en.cppreference.com/w/cpp/ranges/iota_view

Why do I see my own changes again?

I still see my own changes, start a new branch from my HEAD, cherry pick your commits and learn to pull/merge properly.

I still see my own changes, start a new branch from my HEAD, cherry pick your commits and learn to pull/merge properly.

fixed this branch instead


Test Case projects which aren't Linked Projects

There are some Test Cases which have as their project, a project which isn't an official CCP-WSI Linked Project.
Ideally, we should be get in contact with the relevant project owner and ask if we can add it as a CCP-WSI Linked Project however there isn't time for the for the first release.
A project has to be in the catalogue for it to be selected as meta data for a Test Case. So for projects that aren't official Linked Projects, I'm adding them so they can appear in the Test Case Metadata but not publishing them so they don't appear in the projects catalogue. The problem with this, is that where the project appears in the Test Case meta data it contains a link to the project page in the project catalogue. There is no easy way of changing this just for this use case. So, as the project isn't published, if you click on the link to the project provided by the test case metadata it returns a 404.
This needs a better work around or fix but I think a 404 is ok for the first release of the prototype.

It will have to stay like the for the 2nd release too.


fix incorrect  up direction class - document scroll position

Pull fix for computing scrollTop position.
See https://github.com/angular-ui/ui-select/pull/989

Related to https://github.com/angular-ui/ui-select/pull/1212