Feat/Add System/Zync optional bugsnag releaseStage

Right now there is no way to distinguish in Bugsnag which environment is producing bugs, because most environments uses RAILS_ENV production value.
This PR adds a new field with a new envvar to permit to diferenciate about different environments using same RAILS_ENV values.
Related to:
https://github.com/3scale/zync/pull/484
https://github.com/3scale/porta/pull/3123
/kind feature
/priority important-soon
/assign

/approve


[Snyk] Upgrade html-snapshots from 3.6.1 to 3.6.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade html-snapshots from 3.6.1 to 3.6.3.
: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 2 versions ahead of your current version.
The recommended version was released 2 days ago, on 2024-04-15.

Release notes

Package name: html-snapshots

3.6.3 -<EMAIL_ADDRESS>

3.6.2 -<EMAIL_ADDRESS>eslint 9+

3.6.1 -<EMAIL_ADDRESS>

    from html-snapshots GitHub release notes

Commit messages

Package name: html-snapshots

0f087e3 Merge pull request #689 from localnerve/rc-3.6.3
f43981b @ 3.6.3 -<EMAIL_ADDRESS>59acf4a Merge pull request #688 from localnerve/rc-3.6.2
e95600e @ 3.6.2 - update to eslint 9+
af65c6f @ 3.6.2 -<EMAIL_ADDRESS>b48abfd Merge pull request #687 from localnerve/rc-3.6.1-ex
d575ca5 fix: update examples to<EMAIL_ADDRESS>c66c771 Merge pull request #686 from localnerve/snyk-upgrade-290dbeab3d6f8d4062edb40c15b78365
f6af723 fix: upgrade html-snapshots from 3.5.0 to 3.6.0

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: 99.245%. remained the same
when pulling 861b4a36a9afadd0a4a01f18421e2d6493d4c4a5 on snyk-upgrade-31b09fc1185d3fa5e188bff37ecb060e
into d771cda3dc352014f251b2f46ae3562ea3d96c0c on master.


fetch: detect bad slice sizes early on the client side

Motivation
When reading server responses consisting of slices of hashes, such as EpochData, in case if the response has wrong length, it's possible to stop reading it early without consuming the whole stream.
Also, fetch.EpochData.AtxIDs slice size must be in line with types.EpochActiveSet, but this requirement has been violated at some point: #5779
Description
Validate slice sizes against the response size early in streaming mode without reading the whole slice.
Also, ensure that fetch.EpochData.AtxIDs slice size is in line with types.EpochActiveSet in common/types/activation.go
Test Plan
Make sure tests pass
TODO

[x] Merge spacemeshos/go-scale#83
[x] Release a new go-scale version
[x] Update deps

bors merge

bors merge


⚠ Bofrost.com has degraded performance

In e0669d6, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1073 ms

Resolved: Bofrost.com performance has improved in d5e2b35.


Small fix for running vmc on Windows.

Hello,
I recently updated our vmc fork to the latest upstream code and found that ruby vmc on Windows hung. It turned out to be a simple issue surrounding detecting the root path on Windows.
Thanks,
Luke

Hm I have to figure out a better way to do this request so you don't get more changes than you'd like.


Add a bot to manage issues and PRs?

You might consider adding fabric bot to handle issues and PRs. https://docs.opensource.microsoft.com/tools/fabricbot/learningFabricBot.html

For this repo, there isn't enough traffic to need it.


was wondering whether react webpack node can run on aws

Note: This is just a template, so feel free to use/remove the unnecessary things
Description

Type: Bug | Enhancement | Question
Related Issue: #abc

Bug
Expected Behavior
Actual Behavior
Steps to Reproduce

Enhancement
Reason to enhance/problem with existing solution
Suggested enhancement
Pros
Cons

Question
How to?

I have a project that I built with this boilerplate  currently up and running on Amazon AWS. Your question of how to is a bit vague, so I will just run down the steps I took. and provide a few links.
I set up an AWS account using the free tier. I didn't feel it was necessary to go with something like elastic beanstalk, so I used a pure EC2 instance.
Before you make our instances you need to create a security group, which specifies what ports are open on your server, and what if any or all IPs have access to them.  The Amazon docs can walk you through it nicely.
Then you should make sure you are in correct region (in the upper right hand corner), and and then pic Launch a new instance, and follow along with the setup wizard. I picked the Ubuntu Server 14.04 free tier, and most of the default options and I moved through the process. And then let it set it self up.
Once this was done I set up an elastic IP and paired it with my instance. This is important to do. because it gives you a dedicated IP for your virtual instance/IP. And make sure you pair it right away, because there is a charge for having unpaired elastic IPs.
Now it is time to connect. There are instructions on the instances page. I use SSH, with the key file that i generated in the creation process.
First install node. following the instructions
Next install mongo db following this instructions, there are a lot of them so make sure you follow the instructions for the correct version.
To get mongo running fully was a bit of a challenge, I was having some issuing with file permisions but the notes I have look like this. This should be everything, but if something doesn't work the error and answer is on stack overflow. Because thats how I got it working.
RUN MONGO TEST:
sudo service mongod start
sudo service mongod stop
START MONGOD:
sudo /usr/bin/mongod --dbpath /home/ubuntu/db/data
KEEP MONGO RUNNING:
sudo /usr/bin/mongod --dbpath /home/ubuntu/db/data --fork --logpath /var/log/mongodb.log
Now you will want to upload your files. open a section terminal window for this. I was using the secure copy command like this, with the hashed values representing your information.
scp -i #KEY#.pem -r  #SOURCE#  ubuntu@ec2-##-##-##-###.compute-1.amazonaws.com:#DEST#
I would suggest not using this method to copy your node modules, but instead to npm install directly on the server after your package.json is uploaded. Then everything should be good to go. npm start should get your project running, and you will be running at the elastic ip address.
If you don't want to use the Port value that you specified then you can set it to 80 and hit the pure IP address like this, with those hashes representing the port you were running on.
sudo  iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port ####
This works and is how I did it but I'm not actually sure if this is a best practice or not. Dev ops stuff is not what I do.
 If you want the keep the site running at all times you will need forever.  sudo npm install forever -g
And then my new npm script looks like this
"stayAlive": "cross-env NODE_ENV=production PORT=9000 forever start  server/index.js",
and then you should be good to go.
Hope this helps, The AWS docs are actually a really good resource, but if you have any more questions about something specifically just let me know.

What a champion!!! Hahah!

Thank you so much! Caranicas. I was having a long day when o asked that question. I ended up deploying it to a droplet with Ubuntu 14 node 6 pm2. If there is anything I can do to help you please let me know. I am an information scoundrel :)

@elitekode yeah happy to help. This boilerplate is awesome and has helped me a ton, so anytime I can  help pay it forward I like to. It helped me get my app up in 6 weeks and only have to focus on learning about react and redux, and node, without having to wire it all up.
@choonkending feel free to lift any or all of this for the AWS section of the read me, or if you'd like me to put something together, just let me know what other information you'd like me to add, and Ill write something up.

@caranicas Would be great to add an aws.md under /docs and link it from README. I think the information you provided is more than sufficient and a good starting point!

Just wanted to share my small input here regarding the ports of the app and the AWS instance.
Its actually not a very good practice to use the iptables to redirect incoming requests from port 80 to port XXXX
A better solution would be to use amazon's ELB - Load Balancer ability. Meaning set up an elb that will do this redirect. It will also allow you to monitor the number of requests and some more stuff. I'm just not sure if its totally free.
Another option is to set up an NginX on that instance that will do the redirection of ports.
Both of these options are considered safer and more valid because it also allows you the ability to add protection against attacks or maybe some filtering that not related to the app etc.

Thanks guys! I'm closing this issue for now, but feel free to re-open if necessary

its in the docs now, so totally.


Upstream changes from past few days

@tensorflow-jenkins: test this please

well, cmake is failing for unknown reasons, everything looks right.  Merging anyway since we're way behind on upstreaming, and everything else works.


Bug: can't show on RecyclerView views as anchors, or makes it scroll in other cases

I've noticed that if you set RecyclerView views as anchors, and I click on one of the bottom ones of the screen, it doesn't get shown.
This is when I use WRAP_CONTENT for width and height of the popup.
If I try to set width and height myself, I've noticed that it sometimes scrolls the RecyclerView.
Attached video and sample project to show issues:
MyApplication.zip
2019-08-01_11-31-43.zip
Please fix those issues.

Hi,

I've noticed that if you set RecyclerView views as anchors, and I click on one of the bottom ones of the screen, it doesn't get shown.
This is when I use WRAP_CONTENT for width and height of the popup.

Okay, I'll fix the problem. Check next release of this library.

If I try to set width and height myself, I've noticed that it sometimes scrolls the RecyclerView.

It may be due to the LayoutManager.
You can avoid that behavior by the following code:
layoutManager = object : GridLayoutManager(context, 3) {
    override fun requestChildRectangleOnScreen(
        parent: RecyclerView, child: View, rect: Rect, immediate: Boolean
    ): Boolean {
        return false
    }
}

What does "requestChildRectangleOnScreen" do? Why do I need to change it for the popup you have here, but it doesn't have any issues when I use a different solution (like ContextMenu) ?
Please try to have a fix that doesn't require this change.

See this:
https://stackoverflow.com/questions/29473977/popupmenu-click-causing-recyclerview-to-scroll
Anyway, the problem should be fixed by new layout logic in my latest release: v0.4.1. So you should no longer need this change.
Please check it.

ok thanks

But what does this function do?


iRODS user zone - create account short circuited by "Save Changes" button

If you Create an iRODS user account and then hit the "Save Changes" button, the account is created but Django does not retain the correct state for the iRODS account.
Re-opening the profile page will again show "Create an iRODS account" but the user will be unable to because the account was already created.

Issue discussed with @hyi, @pkdash

@mjstealey I am closing this issue since I believe I have verified with you that this worked after applying my fix. If you see any follow-up issues with this, feel free to reopen it or create a new one.


Update recipe: fix failing build for v1.1.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged) NA: last new version build failed
[x] Reset the build number to 0 (if the version changed) Yes
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


Add a jax.profiler.RootTraceContext API.

The CI failure seems like a mypy bug (the __init__ it's complaining about should be inherited from the C++ class, not from object); maybe you can silence it by using super()?

I'm not a huge fan of the name RootTraceContext but I don't have any better ideas.

I initially named it as StepTraceContext but didn't want to say "step" at the JAX level.

The CI failure seems like a mypy bug (the __init__ it's complaining about should be inherited from the C++ class, not from object); maybe you can silence it by using super()?

That works! Thanks.

Can you switch it to StepTraceContext? Even though it can be used for other purposes in JAX, and even though we leave training loop-type things up to Flax/Haiku/Trax/etc., the team believes it's a clearer name given that the profiler UI calls the units "steps".
I'm happy to merge it after that; sorry for letting the PR languish.

No problem. Changed the name. PTAL.


warning in FF

mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create

Duplicated from #141. Thanks for reporting @avdeev!


Micro SD problems

Hey, yes, another issue, my microsd doesnt work.
Board:
cyd2usb
Some CYDs the touch and SD SPI bus is shared, anyone figure this out yer?

Reset until it recognizes the sd

Doesnt work, Larry on BLOUGH discord told me it has to be implemented software side

Still not fixed, resetting doesnt help


TE: Not sending repeated mail for merged anomaly

cleaned up anomaly_function_relations table
not sending repeated email for a merged anomaly.

lgtm


Identify logger for Ionic Vue applications

What is logging?
Logging is the process of recording some detail about application behaviour and storing it in a persistent medium.
Simply put, it is the process of recording relevant data in a store. That data can be information about usage patterns, activities, and operations within an application, or server, etc.
Types
Logs can be of multiple types, each pertaining to a different use case-

Event logs- Record events taking place in an application or system and provide a trail to understand the activity of that system and better debug it.
Transaction logs- Database systems keep transaction logs that record changes made to the stored data and hence, provide recovery means if crashes and errors happen
Message logs- Textual communication between clients (users) in an app (chat app, games, etc), saved in logs.
Serve logs- Logs recorded and maintained by a server consisting of a list of activities it performed.

Why do we need logging?
Reasons why logging is important-

Helps to troubleshoot bugs- Logging makes it easier to identify and resolve bugs as logs provide an idea of why the application broke. Through logs, the developer can easily replicate the error by seeing the activity logged.
Improves monitoring in production environments- Logging information for apps in production can provide useful information in development as well as the business aspect. For instance, one can monitor the user's flow of using the app, peak user activity time through timestamps in logs, etc.
Makes debugging easier- The debugging process gets easier as the developer gets an overall view of what is happening where, through logs, cutting the debugging time.

References-

https://en.wikipedia.org/wiki/Logging_(software)
https://www.becomebetterprogrammer.com/why-does-writing-logs-is-more-important-than-what-you-think-in-software-development/

Log levels
Labels that indicate the severity of a log entry and hence, help in classifying its urgency are termed log levels. They serve on multiple grounds such as separating messages that are just informational from fatal ones, that describe a problem and controlling the application's volume of log output.
Log levels were initially developed in the 1980s by Syslog, a logging solution for the Sendmail project. The severity levels defined by the project later became a standard for logging.
Common log levels
Log levels vary depending on the programming language and framework one is using. Following are the common ones-

FATAL- The FATAL log level represents messages with the greatest severity. It usually means that something critical is broken, and the application cannot continue to do any more useful work without the fix. Examples of situations may be DB failure or running out of disk space on the server.

ERROR- The ERROR log level is used to represent error conditions in an application that prevent a specific operation from running but doesn't mean the application itself will stop working like in FATAL. Examples may include some services not working or some resources not loading.

WARN- The WARN log shows that something unexpected has occurred, yet the application will run as usual. It is mainly used to draw attention to issues that might turn into problems if not checked. Examples can be uncalled resource usage causing the app to slow down.

INFO- The INFO level logs simply state what happened in the application. They are used to indicate useful insights from the business perspective. Examples can be logging a successful job execution or status change.

DEBUG- The DEBUG level is used for logging messages that help developers to diagnose, troubleshoot, or test an application.

TRACE- The TRACE level tracks down the path of code execution. It is mainly used to understand the flow of the program and tackle issues like errors, crashes, etc.

Logging for front-end apps
Front-end applications have gone very complex with time, the developer has to manage state, API calls, visibility, platforms, browser support, etc thus, generating multiple opportunities for something to go wrong.
Need for logging

Logging on the front end gives a view of what's happening to the client, including error cases or untested issues.
In case of failure in production, the front-end dev won't get the full picture due to a lack of logging info, hence, making it challenging to debug and fix the issue.
Developers are dependent on browser logs and the reported errors for identifying problems.

References

https://thenewstack.io/why-frontend-developers-need-logs-too/

Findings on testing Node libraries
Tested on numerous popular logging libraries available for Node.js, such as Winston, log4js (log4js-node), and Morgan.
Node-based libraries won't be of any use as polyfills for core node modules like HTTP, path, OS, etc are not available in the browser or in the module bundler (webpack). Hence, won't work on the browser (client) environment.

Reference issue on winston js:
https://github.com/winstonjs/winston/issues/287
Another library that can be used for logging:
https://www.npmjs.com/package/bunyan
https://github.com/farpoint/meteor-winston-client

Reference issue on winston js: winstonjs/winston#287
Another library that can be used for logging: https://www.npmjs.com/package/bunyan https://github.com/farpoint/meteor-winston-client

Sir, the meteor-wintston-client required winston to be set up, hence, the problem again boils down to the inability to use node-based libraries. The same goes for bunyan.

Checkout libraries in below link:
https://www.npmjs.com/search?q=keywords%3ABrowser+logger
We should definitely check:
loglevelnext
https://www.npmjs.com/package/loglevelnext
This project originated as a fork of the much-loved loglevel module, but has diverged and has been rewritten, and now shares similarities only in functional intent.

 Will explore these.

Sending the logs to the server is a crucial feature. loglevel is quite popular library and could be the first choice but as the loglevel-plugin-remote is not maintained (last release in 2017 ) we chose to go with vue-logger-plugin
https://github.com/kutuluk/loglevel-plugin-remote

Initial implementation is done, and applied to Job Manager. Closing this as will have a separate ticket for server side implementation


Tabular: Added support for empty / useless data input

Issue #, if available:
Resolves #532
Description of changes:
Added support for empty / useless data input
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-537-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-537/1/index.html


Bump Marker v0.3.0 and update CI

Fixing the CI, is a problem for later me :)

I've created: https://github.com/oli-obk/ui_test/issues/177


Remove apostrophes from notebooks

To avoid unexpected glitches.

The RTD changes have already been tested in my fork, merging.


Put a basic project description in the README

The project description should include

[x] names and contact info of the team members
[x] description of what the project does
[x] inspiration for the project - why did we decide to do this?

@wecodewithmichaelmccloskey please review

The README looks good to me. The only thing we may wish to add is the user stories to the "Project Inspiration" section.

I added the user story segment from the final report, those stories were good and if anything they can be updated.


Sentance was missing a word

Added a correct word and updated the sentence to increase readability.

@pastperfect : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Thanks @pastperfect, good catch! Looks good, #sign-off


Added flag to checkout to update submodules when present.

Addresses #13
Want me to add an entry to CHANGELOG as well?

I needed to add a "prepare" script in order to have npm install directly from git, but it now works!
Sorry, ideally that would be another PR, but I thought these might be confusing in isolation.
Context: https://blog.jim-nielsen.com/2018/installing-and-building-an-npm-package-from-github/
To see what the prepare script does, run npm install in any project at each commit in this PR, and see how diff the folder looks in node_modules
# WITHOUT prepare script
$ npm install patcon/storybook-branch-switcher#9985ca6 --save-dev
$ ./node_modules/.bin/sb-branch-switcher
zsh: no such file or directory: ./node_modules/.bin/sb-branch-switcher
$ tree node_modules/storybook-branch-switcher
./node_modules/storybook-branch-switcher
├── LICENSE
├── README.md
├── manager.js
├── package.json
└── preview.js

# WITH prepare script
npm install patcon/storybook-branch-switcher#614c032 --save-dev
$ ./node_modules/.bin/sb-branch-switcher
😎 Your workspace looks good! ...
$ tree node_modules/storybook-branch-switcher
./node_modules/storybook-branch-switcher
├── LICENSE
├── README.md
├── dist
│   ├── cli.mjs
│   ├── cli.mjs.map
│   ├── index.d.mts
│   ├── index.d.ts
│   ├── index.js
│   ├── index.js.map
│   ├── index.mjs
│   ├── index.mjs.map
│   ├── manager.mjs
│   ├── manager.mjs.map
│   ├── preview.d.mts
│   ├── preview.d.ts
│   ├── preview.js
│   ├── preview.js.map
│   ├── preview.mjs
│   └── preview.mjs.map
├── manager.js
├── package.json
└── preview.js

2 directories, 21 files

Hm. I'm seeing some odd behavior. The git submodule init step might also be needed, for when a new submodule appears in .gitmodules between branches

Ok, added minor mention in the readme :)
This is ready for final review 🎉


Ignore  and  blocks

I've had a few instances where I've pasted something from buttfront.net or buttflare.com.  If someone's not careful, it could backfire on them.  Love the extension, but it should ignore <code> and <pre> blocks.

+1

My extension only replaces the exact string "the cloud" with "my butt" -- it does not replace "cloud" with "butt", however, some of the extensions forked from mine do. Please follow up with the owner of the repository of the extension you're using.


enable cross cluster workloadentry reading by default

cc @istio/release-managers-1-10
I want to propose enabling this by default in 1.10+
Reasons for:

We have strong coverage in integration tests
I'm aware of users trying this out (at least Google customers)

Reasons against:

Requires a permission for istio-reader introduced in 1.9, and we need to make sure upgrades are safe.

Requires a permission for istio-reader introduced in 1.9, and we need to make sure upgrades are safe.

Have we made sure its safe? Or do we have a plan/issue for doing this before we ship 1.10?

Or do we have a plan/issue for doing this before we ship 1.10?

It should be safe for 1.9->1.10, but I'm not sure about 1.8->1.10.
Can this verification come in the form of a manual test (probably by me) + bug bash line item? Or is there a good place where I can fit this into automation (cc @Monkeyanator)

Ideally I would say no but that is an unreasonable request I think. I would
feel fine with manual test. If 1.9 to 1.10.works then that's the main
thing, we don't support skip upgrade anyhow
On Wed, Apr 7, 2021, 1:31 PM Steven Landow @.***> wrote:

Or do we have a plan/issue for doing this before we ship 1.10?
It should be safe for 1.9->1.10, but I'm not sure about 1.8->1.10.
Can this verification come in the form of a manual test (probably by me) +
bug bash line item? Or is there a good place where I can fit this into
automation (cc @Monkeyanator https://github.com/Monkeyanator)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/32017#issuecomment-815242105, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPMXZE2VHY2XXYLRBDTHS6LNANCNFSM42ROWKYQ
.

Can you expand on why this would be an issue upgrading from 1.8? My understanding is that adding permissions should be fine?
I'd say we should at least manually verify whether this breaks skip-level upgrade from 1.8 (we don't support it but we should know if we're outright breaking it).
Assuming this completely breaks upgrade from 1.8 existing tests should catch it already, but I'm not sure the failure mode you have in mind?

I think before enable it by default, the below comment should be resolved.
// TODO only do this for non-remotes, can't guarantee CRDs in remotes (depends on https://github.com/istio/istio/pull/29824)


fix p2p peers

Changes proposed in this PR:

fix p2p peers

Code wise is fine, I need to update docs and write a network tutorial

ready for review


test trigger type

I'd like to add support for running app tests in a Spin environment. The test trigger type would invoke a new e.g. run_tests export, which could be an additional entrypoint on existing components.

What would the end goal of this be, supporting something like a spin test top level command?

Yes and as the harness for a suite of spin env tests.


run the intel  reinforcement on  mutiple node

i have build the nfs, intel mpi,and ssh connection,now,i  bash the setup.sh

the shell is stop here ....

Can you download checkpoint with reference implementation?  I try to execute this line and gsutil says this file is not there.  @pkanwar23

I used the following commands and it still works.  I don't have full detail about your issue.  But some suggestions:

Makesure gstuil is installed for python2 rather than python3
make sure ml_perf/checkpoint directory exists
check internet connection setting.  I need to set proxy to connect to the file repo.

gsutil -m cp -r gs://minigo-pub/ml_perf/checkpoint/9 .
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000000.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000001.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000002.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000003.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000004.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000005.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000006.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000007.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000008.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/work_dir/checkpoint...
Copying gs://minigo-pub/ml_perf/checkpoint/9/golden_chunks/000000-000009.tfrecord.zz...
Copying gs://minigo-pub/ml_perf/checkpoint/9/work_dir/model.ckpt-9383.data-00000-of-00001...
Copying gs://minigo-pub/ml_perf/checkpoint/9/work_dir/model.ckpt-9383.index...
Copying gs://minigo-pub/ml_perf/checkpoint/9/work_dir/model.ckpt-9383.meta...
\ [14/14 files][557.3 MiB/557.3 MiB] 100% Done 153.0 KiB/s ETA 00:00:00
Operation completed over 14 objects/557.3 MiB.

I am having an issue with that command also. The error I am getting:
CommandException: No URLs matched: gs://minigo-pub/ml_perf/checkpoint/9
CommandException: 1 file/object could not be transferred.

Google had reorgnized the directory to accomondate training v0.7 submission, thus the directory structure no longer compatible with previous submission code for v0.6.   The directory path for v0.6 checkpoint is in the following directories and may need to be downloaded manually.
$ gsutil list gs://minigo-pub/ml_perf/0.6/
gs://minigo-pub/ml_perf/0.6/checkpoint/
gs://minigo-pub/ml_perf/0.6/target/

The directory structure is no longer as you have it laid out. The current structure is:
gs://minigo-pub/ml_perf/0.6/checkpoint/
gs://minigo-pub/ml_perf/0.6/target/```

This is resulting in issues when trying to run it. The error I am getting is:

```Unable to open table file ml_perf/target/9/target: Failed precondition: ml_perf/target/9/target; Is a directory: perhaps your file is in a different file format and you need to use a different restore operator?```

It is passing `ml_perf/target/9/target` in `Dual_Network` as a `save_file`.


Requests containing UUID in standard form should be parsed

Reproduction steps

Start simple app logging correlation ID on localhost port 8000
send request with Correlation ID in standard form:

curl -v -H "X-Request-ID: $(uuidgen)" localhost:8000
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8000 (#0)
> GET / HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/7.64.1
> Accept: */*
> X-Request-ID: 611AEE7D-1206-4E03-A2A6-97C238D982FD

Actual result
Application logs following truncated Request ID: 611AEE7D-1206-4E03-A2A6-97C238D9
Expected result
Application should log non-truncated Request ID sent by application: 611AEE7D-1206-4E03-A2A6-97C238D982FD
Root cause
Library is not parsing Request ID in header:
https://github.com/snok/asgi-correlation-id/blob/c427439342ba4e1809cf4dcb9b3bb693bb156518/asgi_correlation_id/middleware.py#L46
Hence, in case of the UUID is valid but not in hex format is causing library to truncate  UUID incorrectly here:
https://github.com/snok/asgi-correlation-id/blob/c427439342ba4e1809cf4dcb9b3bb693bb156518/asgi_correlation_id/log_filters.py#L21

Hi @matusvalo, thanks for opening an issue!
As you point out, the request ID here is valid:
is_valid_uuid('611AEE7D-1206-4E03-A2A6-97C238D982FD')
Out[4]: True

Just so I don't misunderstand anything, are you proposing that we - when receiving a valid UUID, should transform it to a hex format like this?
UUID('611AEE7D-1206-4E03-A2A6-97C238D982FD').hex
Out[5]: '611aee7d12064e03a2a697c238d982fd'

The problem is that by default the UUID is truncated in logs because line
https://github.com/snok/asgi-correlation-id/blob/c427439342ba4e1809cf4dcb9b3bb693bb156518/asgi_correlation_id/log_filters.py#L21
expects UUID in hex format.

@sondrelg  I have created a PR which fixes this issue. I hope that the issue will be more clear after.


Rancher container logs

Hi,
I have been looking at docker logging driver features to ship logs to a fluentd instance.
What I am also trying to do is to add as much information as possible to the log message so that it will be easier to do some filtering at a later point.
For that reason, I am looking at adding rancher-defined labels to the message by defining the following options in the docker compose:
log_opt:
  labels: "io.rancher.stack_service.name,io.rancher.container.ip"

Is that supposed to work? Reading at https://docs.docker.com/engine/reference/logging/overview/ indicates that it should be possible.
Thanks,
Matteo

@m4ce we do support log driver configuration in our API, but not yet in our UI. Feel free to add your +1 here: #2935
Also, it is supported in rancher-compose. You would specify it thusly:
foo:
  image: nginx
  log_driver: json-file
  log_opt:
    labels: foo

Does that answer your questions sufficiently to close this issue?

@cjellick,
thanks for your answer!
Not quite, if I set the labels field to any rancher-defined labels (e.g. io.rancher.stack_service.name), the container fails to start.
In theory, docker should expose the labels (e.g. io.rancher.stack_service.name) in the JSON formatted log message in the extra field.
Right now, the only way I found to achieve that is to parse the container JSON log files via logstash and using the docker_metadata filter (https://github.com/tgermain/logstash-filter-docker_metadata) which adds envs and labels to the log message before shipping it to a central destination (e.g. Elasticsearch).
Cheers,
Matteo

@m4ce I understand what you're trying to do, but just haven't had the time to try it out myself to see if it'd even work with fluentd. I have never used fluentd and just need to find time to actually learn and try it out.

@m4ce Were you ever able to get this working as expected? I still haven't had time to try out fluentd, but I don't see any reason why this wouldn't work in Rancher.

@m4ce I don't see any reason why this wouldn't work. If you are unable to get this going in our latest release, please re-open.


DWN (Decentralized Web Node)

Is your feature request related to a problem? Please describe.
Expanding Identus capabilities through seamless connectivity with decentralized web nodes, enabling a versatile and distributed self-sovereign identity ecosystem.
Describe the solution you'd like
Integrating Identus agents with decentralized web nodes enhances the self-sovereign identity ecosystem by offering diverse features and functionality across multiple DID methods and verifiable credential formats. Our Users benefit from an enriched experience with expanded capabilities such as integrated payments, autonomous credential exchange based on defined ACLs and rules, and customizable interfaces and hooks. For example, machine learning and artificial intelligence are moving towards intelligent Identus agents. This versatile solution fosters a more resilient, distributed, and innovative identity management platform that caters to the evolving needs of the decentralized web.

[ ] #54
[ ] #55
[ ] #56
[ ] #57
[ ] #58
[ ] #59

Are you talking about this spec: https://identity.foundation/decentralized-web-node/spec/ ?

A Decentralized Web Node (DWN) is a data storage and message relay mechanism entities can use to locate public or private permissioned data related to a given Decentralized Identifier (DID). Decentralized Web Nodes are a mesh-like datastore construction that enable an entity to operate multiple nodes that sync to the same state across one another, enabling the owning entity to secure, manage, and transact their data with others without reliance on location or provider-specific infrastructure, interfaces, or routing mechanisms.

Wow... this sounds a lot like scuttlebutt ... If you wanna discuss this, we have about a decade worth of experience working with data that flows like this

@mixmix these are great points, I suggest we create a Github discussion to discuss it further.


Expand deprecation policy

Summary
This commit expands the deprecation policy to be a bit stricter and
clarify some edge cases that have arisen in recent releases. It adds
two sub-points to the previous deprecation policy:

A feature can't be deprecated until the alternative has been present
in a released version.
A deprecated feature can't be removed until it's been deprecated in
more than 1 release.

These two additional subpoint should clarify some ambiguity in the
current policy especially as we've had feedback on the current approach
to deprecation and typically have > 3 months between releases.
Details and comments

Looks good to me, typos aside.  I don't know if we want to do it now, but it'd be good to have a section on FutureWarning for instances where a line of code will continue to be valid, but its result will change as well.


Allow a "language" option to be passed.

To indicate HTML or Javascript for the checkCode() & fixCode() functions.
To Test
npm run lint and npm test

cc @Banno/ux


Regenerate aws-sdk SQS interface (v1.30.1)

New SQS client version released from aws-sdk-go-v2 - v1.30.1
See full changelog.

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

Comparison is base (26aed9c) 100.00% compared to head (ed8b586) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #80   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          427       427
=========================================
  Hits           427       427

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Full proxy support to configuration

For now, we have a parameter called 'http_proxy' to configure proxy when initializing the EventHub Client.
It's a dictionary object with the following keys:
keys: 'proxy_hostname' (str value) and 'proxy_port' (int value).
Additionally the following keys may also be present: 'username', 'password'.

This is done, we decide to keep the http_proxy kwargs.


update and add new generate_protos script in csharp examples

This update the generate_protos.bat script to the latest Grpc.Tools version.
It also adds a copy of the script for use in the hello-world-from-cli example, in order to generate code with the script for both examples.

Do these scripts do anything different? If not, can you put the output in a common directory, or if that doesn't work, can you have one script that generates both?

I think these could be changed to use a common directory, without having to have the packages restored in each one (using different tools to restore packages in each one).
By the way this is tied to the documentation change in https://github.com/grpc/grpc.github.io/pull/322/files/a329f4c42c6843da3e78fa8c9f4be643efecfaf1#r75013511

The quickstart also no longer references the bat script, and I'm now thinking that it's not worth it to have the generate_protos_script in the dotnet cli example as well, especially since that will often be used on OS X or linux.
I think the original one should still have its tools version updated though.

LGTM

test this please


Spark 3.0.0 Python image not being able to read using S3AFileSystem

Hi! I'm trying to run a pyspark (spark 3.0.0) job which runs a spark.read.json("s3a://bucket/path/to/data.json") in order to retrieve some data for processing, using image gcr.io/spark-operator/spark-py:v3.0.0 and I'm hitting a Class org.apache.hadoop.fs.s3a.S3AFileSystem not found wall:
Traceback (most recent call last):                                                                                │
│   File "/tmp/spark-a6de7139-1901-4d9e-921b-dc5359f227ae/hello_world.py", line 28, in <module>                                                                             │
│     df = spark.read.json("s3a://bucket/path/to/data.json")                                                                                │
│   File "/opt/spark/python/lib/pyspark.zip/pyspark/sql/readwriter.py", line 300, in json                                                                                │
│   File "/opt/spark/python/lib/py4j-0.10.9-src.zip/py4j/java_gateway.py", line 1305, in __call__                                                                           │
│   File "/opt/spark/python/lib/pyspark.zip/pyspark/sql/utils.py", line 131, in deco                                                                                │
│   File "/opt/spark/python/lib/py4j-0.10.9-src.zip/py4j/protocol.py", line 328, in get_return_value                                                                        │
│ py4j.protocol.Py4JJavaError: An error occurred while calling o58.json.                                                                                │
│ : java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.hadoop.fs.s3a.S3AFileSystem not found                                                    │
...

I tried creating a custom Spark image as follows:
FROM gcr.io/spark-operator/spark-py:v3.0.0

# add s3a connector
ADD https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-bundle/1.11.271/aws-java-sdk-bundle-1.11.271.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-aws/3.1.2/hadoop-aws-3.1.2.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk/1.11.823/aws-java-sdk-1.11.823.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-s3/1.11.823/aws-java-sdk-s3-1.11.823.jar $SPARK_HOME/jars

But it didn't work either.
Does anyone have a clue how can I start reading/writing files from S3 using Spark 3.0.0? Thanks!

Also tried the following docker image:
FROM gcr.io/spark-operator/spark-py:v3.0.0

# add s3a connector
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-aws/3.0.0/hadoop-aws-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-client/3.0.0/hadoop-client-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-common/3.0.0/hadoop-common-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-bundle/1.11.199/aws-java-sdk-bundle-1.11.199.jar $SPARK_HOME/jars
```
No success either :/

i am seeing this same issue in spark 2.4.5

I figured out how to do it:
Here’s a fork with the changes I made to the base docker image (just a few changes):
https://github.com/Coqueiro/spark/tree/branch-3.0-s3
I created a Makefile to aid distribution creation, but I basically just followed the official doc:
http://spark.apache.org/docs/latest/building-spark.html
Also, here’s the image, already built and pushed to Docker Hub:
https://hub.docker.com/repository/docker/coqueirotree/spark-py
It has Spark 3.0.0, Hadoop 3.2.0 and S3A support.

Also tried the following docker image:
FROM gcr.io/spark-operator/spark-py:v3.0.0

# add s3a connector
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-aws/3.0.0/hadoop-aws-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-client/3.0.0/hadoop-client-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-common/3.0.0/hadoop-common-3.0.0.jar $SPARK_HOME/jars
ADD https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-bundle/1.11.199/aws-java-sdk-bundle-1.11.199.jar $SPARK_HOME/jars

No success either :/

This actually fixed my issues. i think perhaps for me, maybe the files in the spark 3.0.1 release are corrupt or whenever i download them they are corrupt. (obviously i changed the files to 3.2.0 instead of 3.0.0


Send only data to client which user is allowed to see

Create some data (agenda items, motions, assignments, users, mediafiles).
Create a new group (keep all permissions deactivated)
Create a new user and add the new group.
Login as this new user in a new (private) tab.
Now go to search view (enter '/search/' or click on search button in navigation bar)
Enter a blank " ".

=> motions, users and mediafiles are visible!!! But user cannot open detail view of these search entries.
@normanjaeckel Any idea why not agenda items and assignments?
This is a serious security issue!

As discussed check motion and mediafile access_permissions.py:get_restricted_data. Users should already work.


Use a better strategy to direct calls to specific tracer implementation

Currently, there exists a single Tracer interface and implementation for both Amqp and Http method calls.
Split the single tracer to more specific implementations and direct calls accordingly.

@JonathanGiles Do you think we should consider having separate implementations in the same plugin package for tracing in HTTP and AMQP?
Currently, they are only distinguished with separate overloads.

Using this issue to investigate opentelemetry-sdk progress.

Closed via #6114


owmods-gui: init at 0.10.0

Description of changes
The GUI version of the mod manager for Outer Wilds Mod Loader.

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

I wanted to make this package be built from source, but it uses pnpm to create tauri's frontend, which is hard to do with the current Node.js build tools.

I wanted to make this package be built from source, but it uses pnpm to create tauri's frontend, which is hard to do with the current Node.js build tools.

I mean better because the .deb versions have analytics enabled while this won't

Closing to init this package in a different folder structure


Fix #417: Render Skeleton component in charts while data is loading to avoid layout shift.

See:

https://act-now-packages--pr461-mikelehen-chart-load-s1kw1ydm.web.app/storybook/index.html?path=/story/charts-metriclinechart--loading-delay
https://act-now-packages--pr461-mikelehen-chart-load-s1kw1ydm.web.app/storybook/index.html?path=/story/charts-metriclinethresholdchart--loading-delay
https://act-now-packages--pr461-mikelehen-chart-load-s1kw1ydm.web.app/storybook/index.html?path=/story/charts-metricserieschart--loading-delay
https://act-now-packages--pr461-mikelehen-chart-load-s1kw1ydm.web.app/storybook/index.html?path=/story/metrics-metricsparklines--loading-delay

👍  I'll play with centralizing our loading state color and tweaking the shade in another PR.


Knobs/replace datepicker

Also see: https://github.com/storybooks/storybook/pull/4244
This does the same on master

Merge when ready, thanks for the review @wuweiweiwu and @pksunkara 🙇


Modules not found error

It seems like installing dependencies are not working on both react-headless and react-next examples. I can't find node_modules folder after running yarn install or npm run install.
OS: MAC (M1)
Node: v18.16.0

I believe you run the yarn install from project's root directory.
You would need to switch to example directory and install the dependencies from there
cd ./examples/react-next
yarn install

or if you want to run from project root try:
yarn install:workspace

yarn start:react-next
# or
yarn start:react-headless

pls try and let us know if none of these helps.

cd ./examples/react-next
yarn install

This is exactly what I did.

By the way, there is a installing error like this:

I see you revert the version back to classic.
yarn set version classic

The repo is set for yarn v3
set you yarn version to yarn v3:
> yarn set version berry
> yarn install


Unable to connect to CompactLogix PLC

When using the code in "Getting Connected", I'm getting an error while attempting to read PLC properties.
My code
const { Controller } = require("ethernet-ip");

const PLC = new Controller();

// Controller.connect(IP_ADDR[, SLOT])
// NOTE: SLOT = 0 (default) - 0 if CompactLogix
PLC.connect("<IP_ADDRESS>", 0).then(() => {
    console.log(PLC.properties);
}).catch(err => console.log(err));

Error message
{ generalStatusCode: 8, extendedStatus: [] }

Environment
node --version
v8.5.0

PLC: CompactLogix 1769-L18ER-BB1B, V30.11

It looks like the issue is being caused by the readWallClock function not being supported by CompactLogix PLC's

Working on the patch now! Preciate the help in tracking this down!


How does fastreid.utils.registry work?

@L1aoXingyu Hi, I found that when building model and train set, they both end at calling fastreid.utils.Registry, I didn't understand how this function works. Can I train using my own dataset by modifying configs?

in fastreid.datasets.init.py：
from ...utils.registry import Registry：

DATASET_REGISTRY = Registry("DATASET")
DATASET_REGISTRY.doc = """
Registry for datasets
It must returns an instance of :class:Backbone.
"""

in  fastreid.modeling.meta_arch.build.py：
from ...utils.registry import Registry

META_ARCH_REGISTRY = Registry("META_ARCH")  # noqa F401 isort:skip
META_ARCH_REGISTRY.doc = """
Registry for meta-architectures, i.e. the whole model.
The registered object will be called with obj(cfg)
and expected to return a nn.Module object.
"""

You can refer partialreid project https://github.com/JDAI-CV/fast-reid/blob/3840f3f79a49a3544fc32509f897101d3634e574/projects/PartialReID/partialreid/partialbaseline.py#L12
In your own project, you can register a new dataset, meta_arch, backbone, and head, then call them by modifying configs.
The only thing you need to notice is importing all registered modules.

You can refer partialreid project
https://github.com/JDAI-CV/fast-reid/blob/3840f3f79a49a3544fc32509f897101d3634e574/projects/PartialReID/partialreid/partialbaseline.py#L12
In your own project, you can register a new dataset, meta_arch, backbone, and head, then call them by modifying configs.
The only thing you need to notice is importing all registered modules.

Thank you.


/bin/sh: 1: youtube-dl: not found

I have this running in docker, and its able to see my lidarr DB.
I get this message when it try's to download
/bin/sh: 1: youtube-dl: not found
How can I fix this?

That's resolved. but now it acts like its downloading the file, but its not  writing the files.

can you provide console output

The  yt-dlp by default is called like this and not youtube-dl. Maybe it would be a good idea to update https://github.com/dmzoneill/lidarr-youtube-downloader/blob/c00c4c649742551a31055b081ef8054d4e3cfffa/lidarr_youtube_downloader/lyd.py#L407 to use the "official" binary name? Then the renaming of the binary can also be removed and it makes it easier to use it locally via pip.


⚠ Bofrost.lu has degraded performance

In 9be757e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1042 ms

Resolved: Bofrost.lu performance has improved in 8682742 after 13 minutes.


Renew Error v2.1.9 :: challenge-mismatch

server-status Activity : Renew  in ~8 minutes
After that ~8 minutes the server-status Activity : Ongoing...
When the time for the next run is reached, it is starting  renewing:
Gives errors:
[md:debug] [pid 5516:tid 2264] md_acme_authz.c(215): ACME server authz: challenge 'pending' for apachelounge.com at https://acme-v02.api.letsencrypt.org/acme/authz-v3/767248432. Exact response was: {"identifier":{"type":"dns","value":"apachelounge.com"},"status":"pending","expires":"2019-10-21T00:08:59Z","challenges":[{"type":"http-01","status":"pending","url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/767248432/UCXiaw","token":"a5IoE8vdYqwm0_nDPDBoRzf-yQ98GRTeWTPUKp6z80w"},{"type":"dns-01","status":"pending","url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/767248432/CESIGA","token":"a5IoE8vdYqwm0_nDPDBoRzf-yQ98GRTeWTPUKp6z80w"},{"type":"tls-alpn-01","status":"pending","url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/767248432/bTtkDA","token":"a5IoE8vdYqwm0_nDPDBoRzf-yQ98GRTeWTPUKp6z80w"}]}
[md:debug] [pid 5516:tid 2264] md_acme_authz.c(355): (70023)This function has not been implemented on this platform: apachelounge.com: protocol 'acme-tls/1' not enabled for this domain.
[md:info] [pid 5516:tid 2264] (70023)This function has not been implemented on this platform: md[apachelounge.com] while[Setting up challenge 'tls-alpn-01' for domain apachelounge.com] detail[error setting up challenge 'tls-alpn-01', for domain apachelounge.com, looking for other option]
[md:error] [pid 5516:tid 2264] (22)Invalid argument: md[apachelounge.com] while[Setting up challenge 'tls-alpn-01' for domain apachelounge.com] problem[challenge-mismatch] detail[None of offered challenge types for domain apachelounge.com are supported. The server offered 'http-01 dns-01 tls-alpn-01' and available are: 'tls-alpn-01'.]
[md:debug] [pid 5516:tid 2264] md_result.c(254): (22)Invalid argument: md[apachelounge.com] while[Setting up challenge 'tls-alpn-01' for domain apachelounge.com] problem[challenge-mismatch] detail[None of offered challenge types for domain apachelounge.com are supported. The server offered 'http-01 dns-01 tls-alpn-01' and available are: 'tls-alpn-01'.]
[md:debug] [pid 5516:tid 2264] md_result.c(254): (22)Invalid argument: md[apachelounge.com] while[Setting up challenge 'tls-alpn-01' for domain apachelounge.com] problem[challenge-mismatch] detail[None of offered challenge types for domain apachelounge.com are supported. The server offered 'http-01 dns-01 tls-alpn-01' and available are: 'tls-alpn-01'.]
[md:debug] [pid 5516:tid 2264] md_reg.c(1068): (22)Invalid argument: apachelounge.com: staging done
[md:error] [pid 5516:tid 2264] (22)Invalid argument: AH10056: processing apachelounge.com: None of offered challenge types for domain apachelounge.com are supported. The server offered 'http-01 dns-01 tls-alpn-01' and available are: 'tls-alpn-01'.
[md:info] [pid 5516:tid 2264] AH10057: apachelounge.com: encountered error for the 1. time, next run in 3 seconds

MDMessageCmd gives a mail: errored apachelounge.com
And mod_md is repeating/trying again and again.
After stop/start Apache same trying loop.
serror-v219.log
staging.zip
I removed mod_md
Config:
Protocols h2 http/1.1 acme-tls/1
MDomain apachelounge.com www.apachelounge.com land10.nl..............
Listen 443
MDCertificateAgreement accepted
MDRenewMode Always
MDRenewWindow   79d
MDWarnWindow 80d
MDStapling on
MDNotifyCmd D:/servers/apacheS/bin/MDNotifyCmd.bat
MDMessageCmd D:/servers/apacheS/bin/MDMessageCmd.bat

There was no change regarding the challenge handling in recent versions that I am aware of.
The error says that it could not find a supported challenge for the domain apachelounge.com because it does not seem to support the acme-tls/1 protocol. Since this worked in the last weeks several times, I wonder if something changed.
I do not see the MDBaseServer configuration in the config above, for example.
As to the again and again: what do you propose should happen?

Nothing changed here, still the same Apache. Renew was working with v2.1.8
MDBaseServer was there
again and again : no problem for me. Was a worried about the limit Pending Authorizations, but that is 300.

This is strange:
This function has not been implemented on this platform: apachelounge.com: protocol 'acme-tls/1' not enabled for this domain.
and this one says it is enabled/available:
processing apachelounge.com: None of offered challenge types for domain apachelounge.com are supported. The server offered 'http-01 dns-01 tls-alpn-01' and available are: 'tls-alpn-01'.

Did you get the error mail every time or once an hour? (There is a rate limit on the notification call  at least there should be...).
Anyway, thanks for the data. I made a change in v2.1.10 that adds some more special handling for the base server setup you use. The support for the tls-alpn-01 challenges will now fall back to check the base server now and that should solve your issue.

Cannot recall the mail frequency, I deleted all.
Coming time I cannot test anymore mod_md.
I had  to switch to an other client because I must test the auto LE with the author of the SurgeMail server. I reported in #144 already that mod_md conflicts with other clients.


Move to a different release action

The way things were before we created a (pulished) release first, then
build and uploaded assets. This meant (particularly with OSX) the
release existed as "latest" for a long time without assets. This causes
issues for anyone that tries to install during this time, including some
test suites.
This new action allows you to create a Draft release, upload assets,
then publish it -- meaning it won't be visible until it's ready, solving
that problem.
Annoyingly, we had to fork the action to do it, as the best one our
there needed a fix and the maintainer is gone.

Example Release:

NOTE: It didn't use the section titles from our release.yaml config because it's not on main yet.


fix missing links, add careers page

Description

Fix missing links
Add Careers page

Issue number
https://github.com/palomachain/paloma/issues/

fixes https://github.com/VolumeFi/paloma/issues/171


A "json4s" dependency causes a build failure

Adding a org.json4s:json4s-jackson_2.11:3.2.11 dependency results in
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':packageDebug'.
> Duplicate files copied in APK decoder.properties
  	File 1: /Users/mojojojo/.gradle/caches/modules-2/files-2.1/org.scala-lang/scalap/2.11.0/4d1ef078a977e29c32d539fac2900ca56f17fb85/scalap-2.11.0.jar
  	File 2: /Users/mojojojo/.gradle/caches/modules-2/files-2.1/org.scala-lang/scalap/2.11.0/4d1ef078a977e29c32d539fac2900ca56f17fb85/scalap-2.11.0.jar

Hi,
Please add following code to your build.gradle and try again.
android {
  packagingOptions {
    exclude 'decoder.properties'
  }
}

Yes. I've worked around this by ending up with the following set up:
  packagingOptions {
    exclude 'META-INF/LICENSE'
    exclude 'META-INF/LICENSE.txt'
    exclude 'META-INF/NOTICE'
    exclude 'META-INF/NOTICE.txt'
    exclude 'decoder.properties'
    exclude 'rootdoc.txt'
  }

I just thought that it should be solved on the plugin level.

I just thought that it should be solved on the plugin level.

I agree with you. But this is official plugin's problem. See also: https://code.google.com/p/android/issues/detail?id=61573


Concerns about scoring expected outputs

Firstly, thank you for contributing tau-bench!
I ran:
python3 run.py --agent-strategy tool-calling --env retail --model gpt-4o --model-provider openai --user-model gpt-4o --user-model-provider openai --user-strategy llm --max-concurrency 10 --task-ids 2

And got a perfectly scored output:
🏆 Average reward: 1.0
📈 Pass^k
  k=1: 1.0

For a response that seems wrong. Digging deeper in the code, I see that it is being scored via this snippet in base.py:
        if len(self.task.outputs) > 0:
            # check outputs
            r_outputs = 1.0
            outputs = {}
            for output in self.task.outputs:
                found = False
                for action in self.actions:
                    if (
                        action.name == RESPOND_ACTION_NAME
                        and output.lower()
                        in action.kwargs["content"].lower().replace(",", "")
                    ):
                        found = True
                        break
                outputs[output] = found
                if not found:
                    r_outputs = 0.0
                    reward = 0.0
            info = RewardOutputInfo(r_outputs=r_outputs, outputs=outputs)

If I'm reading correctly, it's checking that the output.lower() (in this case, 10) appears somewhere in the response from the agent. In my case, the agent responded:
"content": "We currently have 12 different T-shirt options available in our online store. Here are some of the options:\n\n1. **Color:** Blue, **Size:** M, **Material:** Cotton, **Style:** Crew Neck\n2. **Color:** Purple, **Size:** XL, **Material:** Cotton, **Style:** Crew Neck\n3. **Color:** Red, **Size:** XXL, **Material:** Cotton, **Style:** Crew Neck\n4. **Color:** Black, **Size:** XXL, **Material:** Polyester, **Style:** V-Neck\n5. **Color:** Black, **Size:** S, **Material:** Polyester, **Style:** Crew Neck\n6. **Color:** Purple, **Size:** S, **Material:** Polyester, **Style:** V-Neck\n7. **Color:** Blue, **Size:** S, **Material:** Cotton, **Style:** V-Neck\n8. **Color:** Black, **Size:** XXL, **Material:** Cotton, **Style:** Crew Neck\n9. **Color:** Red, **Size:** L, **Material:** Cotton, **Style:** V-Neck\n10. **Color:** Black, **Size:** XL, **Material:** Cotton, **Style:** Crew Neck\n\nPlease note that availability may vary, and some options might not be in stock at the moment.",

It says there are 12 T-shirt options, but manages to pass the test case because it is enumerating a list up to 10. This seems problematic? Either the expected output (10) is wrong, or the way the scoring is being done is not very robust. On a similar train of thought, it seems to reward models that are more verbose, as the odds of hitting the correct output string increases.
I attached my output below, thank you!
tool-calling-gpt-4o-0.0_range_0--1_user-gpt-4o-llm_1025151105.json
cc @noahshinn @ysymyth

Yea agree. It's not the perfect semantic equality check that we want. I'm happy to add an llm check as an opt-in grading strategy, or open to feedback from you as well.


Fix #174: Cast error in cmsxform.c reported by GCC 8

For failed platforms I see only build host configuration errors:
configure: error: C compiler cannot create executables


Istiod appears to erroneously generate conflicting inbound listener

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
There are two services that result in a conflicting inbound listener error in istiod (discovery container).
service-a: an external facing api.
service-b: an internal api consumed by service-a.
Note: only service-a has a virtualservice and destination rule.
The error generated is here:
"message": "Conflicting inbound listener:3000. existing: service-b.demo.svc.cluster.local, incoming: service-a.demo.svc.cluster.local"

Not sure why only port is listed in the error with no pod ip as I find in other instances of this error reported online.
❯ kubectl get services
NAME                      TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)    AGE
service-a                ClusterIP   <IP_ADDRESS>         <none>        3000/TCP   3y290d
service-b                ClusterIP   <IP_ADDRESS>        <none>        3000/TCP   3y291d

❯ kubectl get ep
NAME                      ENDPOINTS         AGE
service-a                <IP_ADDRESS>:3000   3y290d
service-b                <IP_ADDRESS>:3000   3y291d

❯ kubectl get virtualservices
NAME            GATEWAYS                           HOSTS                                      AGE
service-a       ["demo/demo-gateway"]   ["api.demo.example.com"]     448d

❯ kubectl get destinationrules
NAME            HOST                                   AGE
service-a       service-a.demo.svc.cluster.local       448d

Service definitions:
❯ kubectl describe service service-a
Name:              service-a
Namespace:         demo
Labels:            app.kubernetes.io/managed-by=Helm
Annotations:       meta.helm.sh/release-name: service-a
                            meta.helm.sh/release-namespace: demo
Selector:          app=service-a
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                <IP_ADDRESS>
IPs:               <IP_ADDRESS>
Port:              http-web-api  3000/TCP
TargetPort:        3000/TCP
Endpoints:         <IP_ADDRESS>:3000
Session Affinity:  None
Events:            <none>

❯ kubectl describe service service-b
Name:              service-b
Namespace:         demo
Labels:            app.kubernetes.io/managed-by=Helm
Annotations:       meta.helm.sh/release-name: service-b
                   meta.helm.sh/release-namespace: demo
Selector:          app=service-b
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                <IP_ADDRESS>
IPs:               <IP_ADDRESS>
Port:              <unset>  3000/TCP
TargetPort:        3000/TCP
Endpoints:         <IP_ADDRESS>:3000
Session Affinity:  None
Events:            <none>

Virtual service definitions:
❯ kubectl describe virtualservice service-a
Name:         service-a
Namespace:    demo
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: service-a
                        meta.helm.sh/release-namespace: demo
API Version:  networking.istio.io/v1beta1
Kind:         VirtualService
Spec:
  Gateways:
    demo/demo-gateway
  Hosts:
    api.demo.example.com
  Http:
    Match:
      Uri:
        Prefix:  /
    Route:
      Destination:
        Host:  service-a
        Port:
          Number:  3000
Events:            <none>

Version
❯ istioctl version
client version: 1.17.2
control plane version: 1.19.3
data plane version: 1.19.3 (44 proxies)
❯ kubectl version --short
Client Version: v1.23.5
Server Version: v1.27.7-gke.1088000
WARNING: version difference between client (1.23) and server (1.27) exceeds the supported minor version skew of +/-1

Additional Information
No response

I don't think its erroneous, you have 2 services on the same port. The inbound proxy cannot identify which one to was the target of a given request. Listed as last bullet on https://istio.io/latest/docs/ops/deployment/requirements/#pod-requirements

Note it will mostly work, you just may have incorrect telemetry mostly

I have missed an important detail. The gateway is only configured for service-a to serve external requests. While service-b is consumed by service-a internally with the kubernetes service hostname of service-b.

Ah sorry, I missed the selector is different

Do you have any Sidecar resources?

@howardjohn I have a potential fix based on more info. Looking at the full log entry (it was split into multiple entries), the error is from the proxy container of service-c. This service has port 3000 declared on the pod but no k8s service configured (as it is not needed). It appears this is confusing istio discovery trying to add service-c to the mesh and resulting in this error. In fact the pod should have annotations to prevent side car injection as it is not needed for this service. I have now removed the port definition and will see if this fixes the issue before debugging further.

This error happens when at least two services defined for a proxy. Check the all the services with targetport 3000 in the same namespace

can you maybe send the output of istioctl x internal-debug instancesz? You can send over slack DM if you don't want to share that many details. istioctl bug-report may be useful as well

Sent over slack. Removing the port from the pod container did not help. Oddly the error is coming from a pod that has envoy proxy sidecar but no services with port 3000. All other k8s services on port 3000 are paired to a single pod.

This error happens when at least two services defined for a proxy. Check the all the services with targetport 3000 in the same namespace

There are multiple services on port 3000 in the namespace but each is linked to an independent set of pods (deployment set). Shouldn't be an issue.

Almost positive this is https://github.com/istio/istio/issues/45241 based on the instancesz I was sent offline.


Orca not reporting jvm_memory_used_bytes

Seeing a lot of other jvm metrics in there but not that one and we use that for the dashboards:
https://s.armory.io/P8uyr2JO

this bug still exists in spinnaker v1.26.3


⚠ RPC server - Figment Solana has degraded performance

In 5f50696, RPC server - Figment Solana ($FIGMENT_SOLANA_RPC_URL) experienced degraded performance:

HTTP code: 429
Response time: 305 ms

Resolved: RPC server - Figment Solana performance has improved in f6c752e.


dsqds

dsq
d
q
d

Thanks to @rlefevre for bringing these to my attention!

So sorry @evancz about those, makes me fear as I don't know how this happened 😨
Congrats for your work, best!

Do you have a cat? :joy_cat:

Or an infinite number of monkeys trying to write Shakespeare!

I am ashamed as none of these hypothesis are true 🙈
My unconscious wanted to contribute to elm maybe ;)!


token puzzle

PR-Codex overview
This PR focuses on implementing dynamic JWT token generation based on provided username and password.
Detailed summary

Updated the todo comment to reflect the task of implementing dynamic JWT token generation
Updated the checkstyle suppressions file to adjust the line number for the MagicNumber check in Token.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Oops, I failed. You can see the full log here (spent 13s)
+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 28481
+ echo '2.0-SNAPSHOT BUILD'
2.0-SNAPSHOT BUILD
+ date
Tue Sep 26 18:10:35 CEST 2023
+ uptime
 18:10:35 up 120 days, 10:22,  1 user,  load average: 19.74, 20.36, 20.45
+ cat
.rultor.yml in eo-cqrs/eo-cqrs-secrets doesn't allow eo-cqrs/ohip-java to use its assets (there are 7 friends), see http://doc.rultor.com/reference.html#assets
+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 2min)


getServerSideProps returns an empty object when using next/link and a middleware.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d3g9j0bpx2nsb4
AWS Region
us-east-1
Amplify Hosting feature
SSR
Frontend framework
Next.js
Next.js version
13.4.2
Next.js router
Pages Router
Describe the bug
I created a simple Next.js application. Inside I have some pages that use SSR (with getServerSideProps) and I have an empty middleware (it just returns NextResponse.next()).
The different pages are pretty simple, just containing a getServerSideProps and printing the content of that on the screen:
import type { InferGetServerSidePropsType } from 'next';
import Link from 'next/link';

type HomeProps = InferGetServerSidePropsType<typeof getServerSideProps>;

const Home = (props: HomeProps) => {
  return (

        <Link href="/">Home</Link>
        <Link href="/page1">Page 1</Link>
        <Link href="/page2">Page 2</Link>

Server Side Props

{JSON.stringify(props, null, 2)}

  );
};

export const getServerSideProps = () => {
  return {
    props: {
      page: 'Home',
    },
  };
};
export default Home;

The issue is than randomly when navigating through the links, getServerSideProps return an empty object. That behaviour can be seen on the following video and it appears to happen when we start navigating "too fast":
https://user-images.githubusercontent.com/58597410/261696699-dabb56c6-7069-43de-933c-89fe4ba2047a.mov
This only happens when we use next/link, a middleware file and getServerSideProps at the same time.
I created a minimal reproducible example on the following repository: https://github.com/FacundoSpira/amplify-nextlink-middleware-error
And the app is deployed here: https://main.d3g9j0bpx2nsb4.amplifyapp.com/
Expected behavior
The app should navigate correctly, regardless of how many times and how quickly I click on a link.
Reproduction steps

Clone the repository: https://github.com/FacundoSpira/amplify-nextlink-middleware-error
Deploy it to amplify
Navigate to the deployed URL and start navigating between the links. When navigating too quickly getServerSideProps will return an empty object.

Build Settings
No response
Log output
No response
Additional information
No response

Hi @FacundoSpira 👋 , thanks for raising this and for sharing detailed reproduction steps.
I was able to reproduce the behavior where getServerSideProps returned an empty object when quickly navigating through the links. I am investigating into this further and will keep you posted with any updates.

Hi @FacundoSpira 👋 , thanks for raising this and for sharing detailed reproduction steps.
I was able to reproduce the behavior where getServerSideProps returned an empty object when quickly navigating through the links. I am investigating into this further and will keep you posted with any updates.

Thanks! Glad you were able to reproduce it. Please let me know if there's anything we can help with.

Hey sir, is there any progress on this so far? I'm facing the same problem and I'm using next.js 13.4.13.

Hello @Jay2113, hope you are doing well.
Is there any update on the issue?
Thanks!

@FacundoSpira 👋 , apologies for the delayed response here. We have identified this as a bug and are actively working to mitigate it. I'll keep you posted with any updates.

We have deployed a fix for this issue.


Remove values that are empty arrays, such as cc: []

Without this, Mailgun was failing with this error when the message had a cc value like []:
'cc' parameter is not a valid address. please check documentation

@TylerRick Thank you for contribution!


Exclude Certain Entities from Lighting

would it be possible to add a component that excludes the entity it's on from being affected by lights?

Not possible currently, but I agree it's definitely needed.
Either some type of sprite specific light mask, or a way to use the z-index to order lights and sprites.


[ml] Rework of the optimization framework

This PR reworks the current optimization framework to make the regularization part of the optimization algorithm. Furthermore, it consolidates the LossFunction by defining a common interface for loss functions. The GenericLossFunction allows to construct loss function by specifying the outer loss function and the prediction function individually.
Additionally, this PR introduces some syntactic sugar which makes programming with broadcast variables easier.

This PR is the new PR for #740.

Will merge this PR, since there were no objections in the old PR #740.


v0.2.0 Not available on Hex

I tried to install this in my mix.deps and got this error
Because your app depends on firebase_admin ~> 0.2.0 which doesn't match any versions, version solving failed.

@briankariuki if you're still interested I've just published v0.2.0 to Hex

I just copied the code into my project.


About adding, modifying and deleting annotations.

About adding, modifying and deleting annotations
I found that Recaf has no feature about modifying annotations.
Why not add it?

This is something that will be supported in the 3X release. It's been added to the bytecode parser grammer: https://github.com/Col-E/Recaf/blob/dev3/recaf-assembler/src/main/antlr/me/coley/recaf/assemble/parser/Bytecode.g4#L139
The assembler supports editing fields and methods, editing class level definitions is all that remains in order to fully support annotation editing in 3X. It shouldn't be too hard to tweak the grammar to also support class definitions, most of the work will probably be in UI integrations. But it will be something that will get done.

LEF's 邮箱自动回复：请留下您的QQ，然后说清要办的事情我会定期查看邮箱。QQ1720766910--------------------------LEF-gangaDev 2018/12/26设置

Closing as 4.X is the only branch we're working on going forward. The assembler is capable of adding/removing annotations now.
For instance here's a class with an annotation:
.annotation TestAnnotation {
    number: 15,
    bogusNumber: NaN,
    charValue: 'c',
    subWithString: .annotation org/jetbrains/annotations/NotNull {
        value: "Hello, world!"
    },
    subWithEnum: .annotation EnumHolder {
        value: .enum net/fabricmc/api/EnvType CLIENT
    },
    subWithClass: .annotation ClassHolder {
        value: { java/lang/String }
    },
    stringArray: { "one", "two", "three" }
}
.super java/lang/Object
.class public super Example {

}

@TestAnnotation(
  number = 15,
  bogusNumber = NaN,
  subWithString = @NotNull("Hello world"),
  subWithEnum = @EnumHolder(EvnType.CLIENT),
  subWithClass = @ClassHolder(String.class),
  stringArray = [ "one", "two", "three" ]
)
public class Example {}


Externalizing authenticationendpoint is not working

Due to the changes introduced along with kernel 4.5.x upgrade, externalizing authenticationendoint is no longer works as expected.
Some causes,

Dependency update
changes introduced while fixing https://github.com/wso2/product-is/issues/6184 has a hard dependency to server at https://github.com/wso2/carbon-identity-framework/blob/v5.14.97/components/authentication-framework/org.wso2.carbon.identity.application.authentication.endpoint/src/main/webapp/basicauth.jsp#L63

Doc reference https://docs.wso2.com/display/IS580/Hosting+Authentication+Endpoint+on+a+Different+Server
Script https://github.com/wso2/samples-is/tree/master/host-endpoints-externally

Flow that have tested:

Login flow
Username recovery flow
Password recovery flow with email
Password recovery flow with challenge question
Ask password flow


[Bug] Revisit the use of kubectl wait to avoid flakiness

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ci
What happened + What you expected to happen
In KinD E2E tests, we use kubectl wait to block the process only when the system is not ready. However, it is not good to use kubectl wait --for=condition=Ready after deleting a resource.
[Example 1]
The test test_detached_actor kills GCS on the head pod and uses kubectl wait to make sure that the new head pod is ready. However, in my experiment, the head pod will need 60 seconds to crash after the GCS server is killed. The head pod is READY:1/1, STATUS: Running before the crash. Hence, kubectl wait cannot make sure the new head pod is ready.
https://github.com/ray-project/kuberay/blob/ea6e8d1e5d36690c2a3577361db124fad1389a00/tests/compatibility-test.py#L319-L327
[Example 2]
READY: 1/1 cannot imply STATUS: Running. Hence, sometimes kubectl wait --for=condition=ready will consider a pod with READY: 1/1, STATUS: Terminating to meet conditions. See the post "How can a pod have status ready and terminating?" for more details.

Link
INFO:kuberay_utils.utils:executing cmd: kubectl wait --for=condition=ready pod -l rayCluster=raycluster-compatibility-test --all --timeout=900s
pod/raycluster-external-redis-head-xvhcg condition met
pod/raycluster-external-redis-worker-small-group-r5s2s condition met
INFO:kuberay_utils.utils:executing cmd: kubectl get pods -A
NAMESPACE            NAME                                                 READY   STATUS        RESTARTS   AGE
default              raycluster-external-redis-head-xvhcg                 1/1     Running       0          37s
default              raycluster-external-redis-worker-small-group-jdsdd   0/1     Running       0          37s
default              raycluster-external-redis-worker-small-group-r5s2s   1/1     Terminating   0          37s

Link
INFO:kuberay_utils.utils:executing cmd: kubectl wait --for=condition=ready pod -l rayCluster=raycluster-compatibility-test --all --timeout=900s
pod/raycluster-external-redis-head-x97nr condition met
pod/raycluster-external-redis-worker-small-group-b66wg condition met
INFO:kuberay_utils.utils:executing cmd: kubectl get pods -A
NAMESPACE            NAME                                                 READY   STATUS        RESTARTS   AGE
default              raycluster-external-redis-head-x97nr                 1/1     Running       0          39s
default              raycluster-external-redis-worker-small-group-9mjgb   1/1     Running       0          39s
default              raycluster-external-redis-worker-small-group-b66wg   1/1     Terminating   0          39s

Reproduction script
RAY_IMAGE=rayproject/ray:2.0.0 python3 tests/compatibility-test.py RayFTTestCase.test_detached_actor 2>&1 | tee log
RAY_IMAGE=rayproject/ray:2.0.0 python3 tests/compatibility-test.py RayFTTestCase.test_kill_head 2>&1 | tee log

Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

We should remove all "kubectl wait" because the command does not know the expected state (e.g. how many Pods?) of RayCluster. In addition, https://github.com/ray-project/kuberay/issues/704 will also increase the instability.


WIP: Dummy PR to check maint-18.1.0 status

[!CAUTION]
Do not merge this PR.
This PR is being used to test verification and binary packaging jobs prior to creating 18.1.0 RC2. After testing, we'll close this without merging.

@github-actions crossbow submit --group verify-rc-source

@github-actions crossbow submit --group packaging

@github-actions crossbow submit verify-rc-source-integration-macos-amd64

Everything looks good except verify-rc-source-integration-macos-amd64. On my arm64 machine, the integration is failing so I'm going to hold off on creating the next RC until I understand what's going on.

verify-rc-source-integration-macos-amd64 is failing because JPype doesn't yet work on Python 3.13, see https://github.com/apache/arrow/pull/44395. Since the intention of that job is to test without conda, I think we can just let it fail for now and move forward with an RC.

Closing now that RC2 is up.


Issue with metrics reporting concept accuracy

Hi,
I read your wonderful paper on neuro-symbolic CL. It is an interesting domain. I am trying to setu your repository locally. However, I am facing issues just running it for the first time:
python start.py --version nesy --model cool --dataset shortcut-mnist --lr 0.3 --batch_size 32 --n_epochs 1 --buffer_size 500 --minibatch_size 32
However it leads to the following error
python-BaseException
Traceback (most recent call last):
  File "/volumes1/projects/NesyCL/utils/training.py", line 160, in evaluate
    perc_correct, distr, cc = custom_accuracy_concepts(concepts, reprs, dataset.NAME)
  File "/volumes1/projects/NesyCL/utils/metrics.py", line 51, in custom_accuracy_concepts
    torch.argmax(zs[1].view(-1,10), dim=-1).view(-1, 1)], dim=0)
IndexError: tuple index out of range

Essentially, one of the folllowing lines is creating the trouble.
https://github.com/ema-marconato/NeSy-CL/blob/main/utils/metrics.py#L37
https://github.com/ema-marconato/NeSy-CL/blob/main/utils/metrics.py#L49
Please let me know the fix. Thanks in advance.

Hey there, thank you for pointing out the error!
I think the error may be caused by some issues in the last merge before pushing the repo.
It will take me a few days to fix it, since I am very busy these days. I'll keep you updated.
Bests,
Emanuele

@ema-marconato  Thank you for the quick reply. The issue is mainly with the MNIST datasets. It seems to work for CLEVER dataset.
I also have couple of minor issues. I have raised separate requests for the same. Thanks in advance.


ImportError: cannot import name 'dist_model'

Thanks for sharing the pre-trained model.
I'm very interested in this work but are facing a problem when running the code.
Below is the error that occurs.
I'd really appreciate it if you could help me solve this problem.
Many thanks!
ImportError                               Traceback (most recent call last)
 in ()
9
10
---> 11 from utils import *
12
13 sys.path.append('models/')
/content/drive/My Drive/LenslessLearning-master/utils.py in ()
234 import sys
235 sys.path.append('/home/kristina/PerceptualSimilarity')
--> 236 from models import dist_model as dm
237 from admm_helper_functions_torch import *
238
ImportError: cannot import name 'dist_model'

it looks like it's just having issues finding paths to various packages. The code is still looking for a specific path on someone else's computer--try modifying line 235 to point to whichever directory you installed PerceptualSimilarity  and see if that helps? Maybe @monakhova could chime in and help out.

The package is from the Perceptual Similarity repo and calls the LPIPS loss.  You can find this here: https://github.com/richzhang/PerceptualSimilarity

Thanks! It works now.
Can I ask another question? I notice that in the admm_model.py, class ADMM_Net needs a parameter "h" for initialization. what should this "h" be if I'd like to retrain the models?
class ADMM_Net(nn.Module):
def init(self, batch_size, h, iterations, learning_options = {'learned_vars': []},
cuda_device = torch.device('cpu'), le_admm_s = False, denoise_model = []):
Thank you!

The package is from the Perceptual Similarity repo and calls the LPIPS loss. You can find this here: https://github.com/richzhang/PerceptualSimilarity

Thanks! It works now.
Can I ask another question? I notice that in the admm_model.py, class ADMM_Net needs a parameter "h" for initialization. what should this "h" be if I'd like to retrain the models?
class ADMM_Net(nn.Module):
def init(self, batch_size, h, iterations, learning_options = {'learned_vars': []},
cuda_device = torch.device('cpu'), le_admm_s = False, denoise_model = []):
Thank you!

it looks like it's just having issues finding paths to various packages. The code is still looking for a specific path on someone else's computer--try modifying line 235 to point to whichever directory you installed PerceptualSimilarity and see if that helps? Maybe @monakhova could chime in and help out.

Can I ask another question? I notice that in the admm_model.py, class ADMM_Net needs a parameter "h" for initialization. what should this "h" be if I'd like to retrain the models?
class ADMM_Net(nn.Module):
def init(self, batch_size, h, iterations, learning_options = {'learned_vars': []},
cuda_device = torch.device('cpu'), le_admm_s = False, denoise_model = []):
Thank you so much!

h is the point spread function of the imaging system.

h is the point spread function of the imaging system.

I notice in the DiffuserCam project, there's a mat file "example_psf.mat". Is this the same psf that should be used here?
Thank you so much!

The package is from the Perceptual Similarity repo and calls the LPIPS loss. You can find this here: https://github.com/richzhang/PerceptualSimilarity

Sorry, I don't know if I miss something, but I don't find 'dist_model' in directory 'models'. I'd really appreciate it if you could help me solve this problem.

The package is from the Perceptual Similarity repo and calls the LPIPS loss. You can find this here: https://github.com/richzhang/PerceptualSimilarity

Sorry, I don't know if I miss something, but I don't find 'dist_model' in directory 'models'. I'd really appreciate it if you could help me solve this problem.

Hi, I encountered exact the same issue :(
Actually, the PerceptualSimilarity repo does not have a directory named 'models', let alone the 'dist_model' file. Have anyone solved this? Thank you very much!

The latest repo of LPIPS has changed a lot. You can pull history repo ,here :https://github.com/richzhang/PerceptualSimilarity/releases/tag/1.0 .

The package is from the Perceptual Similarity repo and calls the LPIPS loss. You can find this here: https://github.com/richzhang/PerceptualSimilarity

Sorry, I don't know if I miss something, but I don't find 'dist_model' in directory 'models'. I'd really appreciate it if you could help me solve this problem.

The latest repo of LPIPS has changed a lot. You can pull history repo ,here :https://github.com/richzhang/PerceptualSimilarity/releases/tag/1.0 .


Allocate fewer objects when searching

A few changes to Crafty.map.search

Maximum of one array created per search
Possibility to provide 'output' array
Split filtererd/unfiltered search into two separate methods

Because of the last two points, I still need to update some of the docs/comments, but figured I'd check whether we wanted to change the api like this first.
(I also have a follow-up PR that simplifies a couple of the core 'Collision' methods in a similar way.)

Merging.  There is probably some follow-up work to make more internal uses of search pass in a results object.


Resize and intrinsic

In image augmentation phase the image is resized but nothing changed to its intrinsic matrix, will this affect the projection depth result?

The intrinsic matrix is changed in class ImageAug3D


Pipeline running error for 02c, missing permissions for the service account

I'm running the 02c, pipleine.run, and got the following error:
"message: "Failed to create pipeline job. Error: Service account<EMAIL_ADDRESS>does not have [storage.objects.get, storage.objects.create] IAM permission(s) to the bucket "learn-demo1". Please either copy the files to the Google Cloud Storage bucket owned by your project, or grant the required IAM permission(s) to the service account..""
It seems the service account does not have permission to the bucket, I've tried to change the role of the account from "Editor" to "owner" manually in the IAM section but it did not work.

I recieved the same error, it gave me these instructions:
From the console link above, or by going to https:/console.cloud.google.com and navigating to "IAM & Admin > IAM":
Locate the row for the service account listed above<EMAIL_ADDRESS>Under the inheritance column click the pencil icon to edit roles
In the fly over menu, under Assign roles select Add Another Role
Click the Select a role box and type Storage Object Admin, then select Storage Object Admin
Click Save
Rerun the list of services below and verify the role has been added.
I tried this and it didn't work.


Suggestions for new folders structure

I try to add one more example to import ecoinvent 2.2 and 3.1 from https://github.com/brightway-lca/brightway25/blob/main/notebooks/IO - importing Ecoinvent.ipynb but it doesn't seems to work on my machine.

Hello, hello! I updated the example in the repo and added a GitHub action to ensure all notebooks are valid JSON. If you want to add additional examples, please use the current repo structure as the basis. Thank you very much for your contribution!


license violation of crypto-js

It seems that you derivated this program from crypto-js that is under bds-3
It is a license violation to distribyte triplesec under mit without aknowledgement of crypto-js author...
Could you confirm and corrrect

Does Crypto-JS have a license?  If so, can you point me to it?

@maxtaco: https://code.google.com/archive/p/crypto-js/ on the right side of this page, you'll see License: New BSD License. If you dig a little in the recent commits, you'll find the one where he updated a link to this file, which is pretty clearly the 3-Clause BSD.

Thanks. I added the license in [here|https://github.com/keybase/triplesec/commit/c8c6133c1660cd9a5eb680b444535db4ebf757d4]. Reopen if you think this doesn't cover it.

@maxtaco, I can't reopen because I did not create the issue.
Unless you have a reason to keep this MIT, I think a better solution would be relicensing the whole library as BSD to match the origin license. From my perspective, the licenses are very similar other than the patent grant.
Having both licenses in this library makes it ambiguous what code/changes are subject to what licenses - if you really wanted to do that, it would be better to distribute it as a patchset or clearly delineated dependency tree that represented the boundary between the MIT code and the BSD code.
Considering the patent clause in BSD, users would have to be wary if you did not intend to issue a the explicit patent grant as it would mean if Keybase decided to patent Triplesec, users of this library could be in violation. I expect that would never happen, but perhaps it is reason enough to consider the relicensing.


Indices not moved to correct device in batched NMS

I'm trying to increase the points per side but when I go over 80 I get the following
Traceback (most recent call last):
  File "/home/louis/dev/cv/segment-anything/scripts/amg.py", line 267, in <module>
    main(args)
  File "/home/louis/dev/cv/segment-anything/scripts/amg.py", line 244, in main
    masks = generator.generate(image)
  File "/home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py", line 163, in generate
    mask_data = self._generate_masks(image)
  File "/home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py", line 206, in _generate_masks
    crop_data = self._process_crop(image, crop_box, layer_idx, orig_size)
  File "/home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py", line 251, in _process_crop
    keep_by_nms = batched_nms(
  File "/home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py", line 73, in batched_nms
    return _batched_nms_vanilla(boxes, scores, idxs, iou_threshold)
  File "/home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torch/jit/_trace.py", line 1220, in wrapper
    return fn(*args, **kwargs)
  File "/home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py", line 110, in _batched_nms_vanilla
    keep_mask[curr_indices[curr_keep_indices]] = True
RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)

I expect this means the curr_keep_indices need to be moved to the same device as the indexed keep_mask tensor.
If we breakpoint at line 251 in _process_crop of automatic_mask_generator.py
        # Remove duplicates within this crop.
        breakpoint()
        keep_by_nms = batched_nms(
            data["boxes"].float(),
            data["iou_preds"],
            torch.zeros(len(data["boxes"])),  # categories
            iou_threshold=self.box_nms_thresh,
        )
        data.filter(keep_by_nms)

Note torch.zeros(len(data["boxes"])),  # categories does not specify a device

and enter the debugger
> /home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py(253)_process_crop()
-> data["boxes"].float(),
(Pdb) n
> /home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py(254)_process_crop()
-> data["iou_preds"],
(Pdb) n
> /home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py(255)_process_crop()
-> torch.zeros(len(data["boxes"])),  # categories
(Pdb) n
> /home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py(256)_process_crop()
-> iou_threshold=self.box_nms_thresh,
(Pdb) n
> /home/louis/dev/cv/segment-anything/segment_anything/automatic_mask_generator.py(252)_process_crop()
-> keep_by_nms = batched_nms(
(Pdb) s
--Call--
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(44)batched_nms()
-> def batched_nms(
(Pdb) n
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(68)batched_nms()
-> if not torch.jit.is_scripting() and not torch.jit.is_tracing():
(Pdb) n
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(69)batched_nms()
-> _log_api_usage_once(batched_nms)
(Pdb) n
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(72)batched_nms()
-> if boxes.numel() > (4000 if boxes.device.type == "cpu" else 20000) and not torchvision._is_tracing():
(Pdb) n
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(73)batched_nms()
-> return _batched_nms_vanilla(boxes, scores, idxs, iou_threshold)

and print the devices of the variables being passed through batched_nms() to _batched_nms_vanilla():
> /home/louis/miniconda3/envs/sam/lib/python3.10/site-packages/torchvision/ops/boxes.py(73)batched_nms()
-> return _batched_nms_vanilla(boxes, scores, idxs, iou_threshold)
(Pdb) p boxes
tensor([[   0.,    0.,  968.,   45.],
        [   0.,    0.,  968.,   45.],
        [   0.,    0.,  968.,   45.],
        ...,
        [   3.,    0.,  995., 1332.],
        [   3.,    0.,  995., 1332.],
        [   0.,    4.,  995., 1332.]], device='cuda:0')
(Pdb) p scores
tensor([0.9919, 0.9900, 0.9894,  ..., 1.0067, 1.0069, 0.9800], device='cuda:0')
(Pdb) p idxs
tensor([0., 0., 0.,  ..., 0., 0., 0.])
(Pdb) p iou_threshold
0.7

We can confirm that the source of the error is the zeroes which we created without specifying a device, the boxes and scores are on CUDA.
To remedy it
torch.zeros_like(data["boxes"][:,0])

or
torch.zeros(len(data["boxes"]), device=data["boxes"].device)

but I think the first way is more elegant.
I expect the same edit should also be applied on line 360.
            torch.zeros(len(boxes)),  # categories

to
            torch.zeros_like(boxes[:,0]),  # categories

I've submitted a PR to fix this:

#41


Can't run a fresh project

After running deno run -A https://deno.land/x/entropy_cli/init.ts, I went to the created directory, and ran:
deno task dev

But then, the following problem arose:
error: Module not found "file:///home/x/entropy-test/core/src/server/server.module.ts".
    at file:///home/x/entropy_test/src/main.ts:1:30

[!WARNING]
The created folder does NOT contain any core/ directory, hence the error.

My details:
Linux: 5.15.144-1-MANJARO
deno: 1.39.2 (release, x86_64-unknown-linux-gnu)
v8: 12.0.267.8
typescript: 5.3.3

Thanks for reporting this bug, I published a fixed version 1.0.0-beta.16. The error was caused by a faulty import map that has been accidentally changed in the repository.
Now the installation process should run smoothly - however you may still encounter little bugs since the framework is still in the beta stage and it is under active development.
# latest framework version requires Deno 1.40
deno upgrade

deno run -A https://deno.land/x/entropy_cli/init.ts

I hope the CLI is more stable now and it will come out of beta soon 😅


Docs: Fixing a dead link for graphiql-cdn

I found a dead link on this README. It should be pointed one additional directory up to here.
It's a small fix, but I figured I'd post it for others that are looking for it 👍 .

Ty!