Add docs for cattle detector in prebuilt.md file

Adding cattle detector to docs

Looks good, I added a text edit. @ethanwhite this is part of that conversation about docs building from main versus release. Should we wait until https://github.com/weecology/DeepForest/issues/746 is merged before we merge this? I think so, users might see the model and the model isn't ready until it has been

[ ] Uploaded to hugging face @henrykironde
[ ] #317 on hugging face is complete
[ ] A example of how to run is complete. @Mu-Magdy we will add this example right below each model once items 1 and 2 are complete.

I'm fine with waiting, but I also think that @henrykironde should have that sorted out soon enough that we don't need to wait on it. @henrykironde if you're having issues getting #746 to default to stable let me know on Slack and I can take a look.

I'm merging this. @Mu-Magdy your next step is to work with @henrykironde to get the model uploaded to hugging face and add an example on how to call it in the new interface.
https://huggingface.co/weecology
https://github.com/weecology/DeepForest/blob/5b2b5e2ae5f5aa523ce655572cdb5980de151d53/deepforest/utilities.py#L59


Create optional rules for prototype methods

I found your comment at explaining why these aren't available at the moment: https://github.com/mysticatea/eslint-plugin-es/pull/2#issuecomment-386864281. While it is true that you will get some false positives, many of the methods have unique enough names that most of the time you won't, and the rare cases that do can be fixed with an inline exception.
I suggest creating these rules and put them in separate rule groups so they are not enabled by default, but can be used when users are happy to deal with the small number of false positives.
We have a similar set of rules for Wikipedia at https://github.com/wikimedia/eslint-config-wikimedia/tree/master/language and would like to be able to use this library instead, but the prototype method rules are important to us and catch lots of issues.

If you only need to report by property name, I think you can use the following rule as a workaround.
https://eslint.org/docs/rules/no-restricted-properties


Implement RFC 47 (Serialise signature)

This change implements deterministic package and program signatures based on the contents and dependencies of the packages. Signatures are computed by hashing the serialised package ASTs with the BLAKE2 hash function. This hash function was chosen for its good speed and low collision rate.
The signature computation handles circular dependencies by computing signatures per package cycle instead of per package. Packages in the same group are discriminated by a group index.
In order to allow deterministic signatures, file parsing order is now always alphabetical inside of a package.
The compiler now outputs the package groups and dependencies when the -V3 or -V4 flags are enabled.
Signatures will be used for future work on separate package compilation in order to validate package identities.
Closes #2147.

appveyor failure:
c:\projects\ponyc\src\libponyc\pkg\program.c(7): fatal error C1083: Cannot open include file: 'blake2.h': No such file or directory

Looks like I forgot to make the relevant edits to wscript.


Add basic tagging

Content
This PR adds a new field tags, which will be a list of searchable tags that can be used to find the given parameter.
As an initial examples, I have added tags for the SurfaceFluxes.jl parameters.
In the API, these are supported by two new functions -

get_tagged_parameter_names: Returns a list of the parameters with a given tag.
get_tagged_parameter_values: Returns a list of name-value Pairs of the parameters with a given tag.

For string-matching, punctuation and capitalization is removed. This could be changed to use string distance instead - I am not sure what the needs are.
I have also added tests for get_tagged_parameter_values and get_tagged_parameter_names

I will be able to tag my favorite parameters!

@trontrytel I am planning on adding tags for most parameters once the basic interface has been agreed upon!

@trontrytel I am planning on adding tags for most parameters once the basic interface has been agreed upon!

Yes, this looks really cool. I think it will improve the readability a lot once fully implemented

2. I wasn't expecting any tags to be applied in this PR, perhaps leave this to a future one?

@odunbar What do you think of just adding the "SurfaceFluxes" tag to the relevant parameters?

@odunbar I have finally dealt with your last comments! I removed all of the tags from the default parameter file and renamed the tags field to tag.


Add test to copy command

Added some tests for copy command.
Slight modifications to copy command.

Codecov Report

Merging #108 (5cb7b93) into master (2aec74e) will increase coverage by 6.43%.
The diff coverage is 76.66%.

@@             Coverage Diff              @@
##             master     #108      +/-   ##
============================================
+ Coverage     59.79%   66.23%   +6.43%
- Complexity      530      584      +54
============================================
  Files            92       92
  Lines          2057     2070      +13
  Branches        245      253       +8
============================================
+ Hits           1230     1371     +141
+ Misses          752      613     -139
- Partials         75       86      +11

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/CopyCommand.java
79.06% <16.66%> (+79.06%)
:arrow_up:

...a/seedu/address/model/person/FormatPersonUtil.java
91.57% <91.66%> (+91.57%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
84.31% <0.00%> (+5.88%)
:arrow_up:

...c/main/java/seedu/address/model/module/Module.java
90.90% <0.00%> (+9.09%)
:arrow_up:

.../seedu/address/logic/parser/CopyCommandParser.java
94.11% <0.00%> (+94.11%)
:arrow_up:

Continue to review full report at Codecov.

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


Request: Typescript support

It would be great if js client could by type safe with typescript support. Otherwise we can just use the API.

Thanks for your feedback @homoky ! We will probably switch to a TypeScript-supported SDK in the future.
In the meantime you can also generate it from OpenAPI generator that includes support for various TS clients:

Typescript (AngularJS, Angular (2.x - 11.x), Aurelia, Axios, Fetch, Inversify, jQuery, Nestjs, Node, redux-query, Rxjs)

Thanks for your feedback @homoky ! We will probably switch to a TypeScript-supported SDK in the future.
In the meantime you can also generate it from OpenAPI generator that includes support for various TS clients:

Typescript (AngularJS, Angular (2.x - 11.x), Aurelia, Axios, Fetch, Inversify, jQuery, Nestjs, Node, redux-query, Rxjs)

Thanks for the info. It works great. We can keep this issue open for another users.


Updating OpenWebUI disables Whitelisted models & OpenAI API Key in Admin Settings

Bug Report
Description
Bug Summary:
Updating OpenWebUI resets Admin Settings which includes Whitelisted models and OpenAI API Key cofiguration. After each update manual configuration setting is required as a workaround.
Steps to Reproduce:

Update WebUI using the following command:
docker run --rm --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once open-webui
Navigate to Admin Settings to find Whitelisting and OpenAI API Key disabled.

Expected Behavior:
Admin Settings should persist through updates.
Actual Behavior:
Admin Settings do not persist through updates.
Environment

Operating System: macOS Sonoma
Browser (if applicable): Brave (Chrome)

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.

Logs and Screenshots
Browser Console Logs:
N/A
Docker Container Logs:
N/A
Screenshots (if applicable):
N/A
Installation Method
Terminal installation using docker commands (see above)
Additional Information
N/A
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Read these two guides to set it permanently:
https://docs.openwebui.com/tutorial/openai
https://docs.openwebui.com/tutorial/ollama

Thanks. I’ll set up ENV vars for OpenAI. How about whitelisting?

Thanks. I’ll set up ENV vars for OpenAI. How about whitelisting?

Oh, sweet. Thanks for the answer. It in itself is some good documentation for people searching in issues. Much appreciated!


EmrEtlRunner: uncompress enriched files when copying to HDFS

When combining the shred job with the output of stream enrich, files have to be gzipped by the s3 loader because lzo is not handled by shred (handling lzo files in the shredder could be an alternative solution).
This is #3525 waiting to happen all over again.

Good point!

handling lzo files in the shredder

This probably wouldn't work so well (as the LZO format we use with raw events is a bit non-standard)...


update where projects list goes

Documentation for projects list could use clarity on where the projects list goes (in the pelicanconf.py file).

Thank you @maneesha

:tada: This PR is included in version 5.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allow all versions of action

Hello,
I work in Telenor and we are using this action. I am wondering if it is possible to allow an action with any version.
I.e.
Our github-actions-allow-list.yml looks like:
actions:
  -<EMAIL_ADDRESS>  -<EMAIL_ADDRESS>  -<EMAIL_ADDRESS>
Is it also possible to allow an action like this?
  - OurPublicSlug/abc

Without having to provide the version? Or OurPublicSlug/abc@* (at star) to allow all?
Thanks, James.

@theztefan Would you know?

Is it also possible to allow an action like this?
  - OurPublicSlug/abc

Without having to provide the version? Or OurPublicSlug/abc@* (at star) to allow all?

@j4m350n, yes that is possible, and as you pointed out it needs to be OurPublicSlug/abc@* to work for all versions.
Only patterns documented under https://docs.github.com/en/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-and-reusable-workflows-to-run are possible.

Hey @j4m350n! As @stoe point out, technically, the feature (and therefore this Action) does allow * wildcard character which makes your request possible. Reference to wildcard matching
That being said, you would still want to check in and confirm your company policy allows this.


Update HackMaster_5E.html

Updating to have an NPC/Monster sheet,
Bug fix for butchery
Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[X ] Is this a bug fix?
[ X] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


fix(ts): Changes for inclusion in aztec3-packages

Description
Minor changes for including this package as a submodule in aztec3-packages. I'm pulling this branch of aztec3-circuits into aztec3-packages/circuits, and then symlinking the ts folder into aztec3-packages/yarn-project/circuits.
The one weird issue I hit was the following compilation error:

error TS4124: Compiler option 'module' of value 'nodenext' is unstable. Use nightly TypeScript to silence this error. Try updating with 'npm install -D typescript@next'.

I followed its suggestion to the letter and it worked, but it means having a different ts version for this project, and other projects in aztec3-packages that do have the same module resolution did not require it. I'd appreciate if someone else can test this if it happens on their machines (I'm on Ubuntu 22.04 and node 18.14.2).
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] There are no circuit changes, OR specifications in /specs have been updated.
[ ] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[ ] The branch has been rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.
[ ] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[ ] If existing code has been modified, such documentation has been added or updated.

Note
If you are updating the submodule, please make sure you do it in its own special PR and avoid making changes to the submodule as a part of other PRs.
 For some reason, I can no longer hit that error. Apologies for the back and forth.


Progress on ldexp/frexp

The purpose of this PR is to complete frexp and ldexp, add tests, more coverage and handle arguments zero, inf and NaN.

Hi Matt (@mborland) I have a direct, maybe silly question. Can I use exponent manipulation around here?

takes a new biased value and converts it into the right bit pattern. Try:

I'm afraid the code you suggested fails all of the frexp/ldexp tests. I tried a bit of debug, but was not able to fix it easily locally. Maybe I have not comprehended the bias/offset interaction yet. Well I know I haven't, but the suggested code doesn't work.

takes a new biased value and converts it into the right bit pattern. Try:

I'm afraid the code you suggested fails all of the frexp/ldexp tests. I tried a bit of debug, but was not able to fix it easily locally. Maybe I have not comprehended the bias/offset interaction yet. Well I know I haven't, but the suggested code doesn't work.

I added print statements and this is the result:
Float: 1
Dec: 9.999995e-01
test_frexp_ldexp.cpp(180): test 'result_test_frexp_ldexp_is_ok' failed in function 'int main()'
Float: 0.553722
Dec: 5.537220e-01
test_frexp_ldexp.cpp(180): test 'result_test_frexp_ldexp_is_ok' failed in function 'int main()'
Float: 0.962466
Dec: 9.624655e-01
test_frexp_ldexp.cpp(180): test 'result_test_frexp_ldexp_is_ok' failed in function 'int main()'
Float: -0.579044
Dec: -5.790445e-01
test_frexp_ldexp.cpp(180): test 'result_test_frexp_ldexp_is_ok' failed in function 'int main()'
4 errors detected.

Editing the exponent would have less rounding steps.

Editing the exponent would have less rounding steps.

I must be a bit dull here, but could you spell-this-out for me. The printouts look good. I can't see what I'm missing.

Editing the exponent would have less rounding steps.

I must be a bit dull here, but could you spell-this-out for me. The printouts look good. I can't see what I'm missing.

I think skipping rounding steps is pushing you out of tolerance since decimal32 has higher precision than float. 1e-7 is dec32 epsilon so all of those would be a few epsilon off. I have the same issue comparing  functions to float since dec32 will have the extra digit.

Editing the exponent would have less rounding steps.

I must be a bit dull here, but could you spell-this-out for me. The printouts look good. I can't see what I'm missing.

I think skipping rounding steps is pushing you out of tolerance

Ah OK. Modifying the exponent is a kind of multiplicatoin. I need to round after that. Is there a way I could insert a rounding there? I have not looked into the rounding mechanisms yet. I'll need help on this one.

Editing the exponent would have less rounding steps.

I must be a bit dull here, but could you spell-this-out for me. The printouts look good. I can't see what I'm missing.

I think skipping rounding steps is pushing you out of tolerance

Ah OK. Modifying the exponent is a kind of multiplication. I need to round after that. Is there a way I could insert a rounding there? I have not looked into the rounding mechanisms yet. I'll need help on this one.

On second thought I don't think editing the exponent will work here. Is this still supposed to be num * 2^exp? Editing the exp would result in num * 10^exp which is how I implemented sclabn

I don't think editing the exponent will work here. Is this still supposed to be num * 2^exp?

Uhhh yes, of course. The radix is 10. Silly me.

So there will be one kind of optimization coming later, when we have optimized mul-by-int (see also #74). When that gets in, you can simply mul-by-integral-type when e2 is less than 2^32 or 2^64. But that can wait till later. I'll finish up the tests, zero, inf and NaN then.

Hi Matt (@mborland) So this one is mostly complete. I just need edge cases for ldexp
But I'm going to get this one in to develop sooner rather than later (even if I need to post-work on it). The reason is because I finally adapted the func-prototypes to the cmath-philosophy in your repo.
I was a little unsure about some of the exact prototype locations and class friendship of a template class tends to be a bit tricky. So we might have to review this.
Also, the friendship would not be needed if we added just a few public constant get-functions for the decimal components.

One of the cool things is, that when this cycles and gets pushed, the impls of ldexp, frexp, ilogb and pow will be (will have become) generic for all decimal types in the project.

I was a little unsure about some of the exact prototype locations. And the syntax for enable-if class friendship of a template class tends to be a bit tricky. So we might have to review this.

That never seems to work very well.

Also, the friendship would not be needed if we added just a few public constant get-functions for the decimal components.

That's true. My reasoning so far to not have public getters or setters is a regular type wouldn't have them, and I want the operation to be as seamless as a builtin type. frexp10 is kind of a cheating way I've gotten around this since it gives you the significand and exponent exactly. I should probably start writing documentation...

All true Matt. I went ahead and merged this. Even though it's not quite done.
Outstanding tasks:

I believe I can get rid of at least one class friendship even now.
Also I still need to handle edge-cases in ldexp.
I'm not sure about the exact locatoins/forms of the enable_if-ed prototypes. If I fumble around the architecture, I'll surely blow it and make it worse. I would ask you to review my protos on frexp, ldexp, ilogb, pow.
Of course there are a few other template forms of pow that we'll need, but I'll handle these in future PR(s).


list all tools available in the docs

Is your feature request related to a problem? Please describe.
Its unclear what tools are available. The only example is
"actions": {
    "payment_links": {
        "create": True,
    },
}

Describe the solution you'd like
A list of tools in the docs or a link to the relevant API docs where this might be located.
Describe alternatives you've considered
Searching other Stripe docs
Additional context
No response

Great feedback! We'll update the README


Feature

This PR adds sweet alert support, codeclimate, updates eslint and modifies front end using bootstrap. It also updates karma and README.md

Coverage remained the same at 100.0% when pulling 660c755fc064741de2706b03a6426fc646cc1d6b on feature into 99d2d06ae7fb98162f5784909d1d809c4c1d0ef3 on develop.

Coverage remained the same at 100.0% when pulling 722a6d27bb377d6a702ce217e3a701e19296ea85 on feature into 99d2d06ae7fb98162f5784909d1d809c4c1d0ef3 on develop.


Inconsistent Error Response Objects

Hi @Kexkey!
I noticed when testing invalid input, that the structure of the error response object is different depending on the type of error.
For example, the object returned for an "Invalid arguments" error (in this case amount = 0):
{
  "id": 1,
  "error": {
    "code": -32600,
    "message": "Invalid arguments",
    "data": {
      "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
      "amount": 0,
      "batcherId": 2
    }
  }
}

Compared to this response in the case of an invalid address:
{
  "id": 1,
  "error": {
    "message": {
      "result": null,
      "error": {
        "code": -32700,
        "message": "Invalid address",
        "data": {
          "address": "hjkfaklshfkjsabf7a48fga",
          "amount": 0.01115399,
          "batcherId": 2
        }
      }
    },
    "data": {
      "address": "hjkfaklshfkjsabf7a48fga",
      "amount": 0.01115399,
      "batcherId": 2
    }
  }
}

At the moment this makes parsing errors in the response a bit awkward, albeit a minor issue, particularly since we have our own validation which should catch invalid input before a request is made to batcher

You're right!  I'll fix that.
Explanation: the former is a validation done by the Batcher itself; the latter is an error response from Cyphernode.
Thanks!

The same problem appears in every call.  I fixed it, I'll push the fix in the dequeueandpay branch ... I'll let you know when it's there.  Thanks again!

I need more testing but I pushed the new stuff to the features/dequeueandpay branch.  Let me know what you think!  Thanks!

Thanks a lot @Kexkey! LGTM


feat: migrate to other lavalink API wrappers

hmm
Do we have more options for lavalink API Wrapper?


execfile has a dependency to the future / past module

at least for building by boa and conda we need future in the host requirement.
This includes past
We need a different way to get the result of
execfile('mslib/version.py')
in https://github.com/Open-MSS/MSS/blob/develop/setup.py#L33

We should probably get rid of setup.py entirely and replace it with only setup.cfg (if possible?), or better yet pyproject.toml. That would solve the execfile issue as well.

The reason of execfile there was not to have to enter the versions string again everywhere.
When doing a conda build I have to add the string again into the feedstock meta.yaml. This decreases the value of the entry in setup.py. But it is worth to have that mostly dependent on the __version__ entry
This may be a solution.
https://stackoverflow.com/questions/71193095/questions-on-pyproject-toml-vs-setup-py
describes version = {attr = "my_package.__version__"}
Currently pyproject.toml is an open issue on conda.
https://github.com/conda/conda/issues/12462

The reason of execfile there was not to have to enter the versions string again everywhere.

I understand that. The version directive in e.g. pyproject.toml works the other way around, it automatically sets version of the package so that we don't have to specify that more than once either.
We could even go further and never specify a version in our source code by using e.g. setuptools-scm. That would get rid of the duplication between version and git tags as well. I have no idea how all of that interacts with conda though.

github tag gives access to a  defined source snapshot and we need it on many places. Release, DOI, conda-forge build, etc
We are not on pypi but have to take care for dependent libraries as we were there.
There are currently a lot developed for packaging. There is not need to  tackle this for the next major.


Allow multiple backend migrations

Has some minor backwards incompatibilities in ms.create_migration, which could be avoided, however the next release already has a few such as removal of .state.

CI failure here is the same as https://github.com/diesel-rs/diesel/issues/3960

CI fixed


potential data loss message in sk logs

Steps to reproduce

Expected result
No such errors in logs
Actual result
WARN load_timeline{timeline=44f55a8653f12e2a6e7d4b1356190123}: timeline 44f55a8653f12e2a6e7d4b1356190123 potential data loss: flush_lsn by find_end_of_wal is less than either commit_lsn or peer_horizon_lsn from control file

Environment
stage
Logs, links

This is related to deletion issue. Apparently all such projects are deleted; directory on sk has no WAL, but controlfile, which causes the WARN. cc @petuhovskiy

So, from logs it is crystal clear compute is still alive when DELETE request comes in. Since we don't have explicit timeline creation, it creates new one. One more reason to have explicit creation...
On a related node, I also dislikeon_compute_disconnect bailing out due to timeline being canceled. Unless we have proper shutdown, we should tli users shutdown normally to avoid messy shared state.

As a hack, until we have explicit creation, we can keep deleted timeline in hash (till next restart) to prevent these warns and empty directories accumulation. @petuhovskiy WDYT?

I think I even had a code in #2329 which kept deleted timelines in hash :) We definitely can do this, and I would also prefer to store info about deleted tenants on disk.
I don't like explicit creation because it's hard to do it right, so let's start with keeping info about deleted timelines. cc @arssher

+1, and I'd propose to start with memory:

it is straightforward to implement, and definitely enough to fix orphaned directories/scary warn issue
it is straightforward to fix on overflow (just restart)

and I would also prefer to store info about deleted tenants on disk

Can you elaborate why? I dont get it why do we need to store some data for deleted tenants

Can you elaborate why? I dont get it why do we need to store some data for deleted tenants

Short answer: to be safe and ensure that once deleted tenant won't reappear.
Long answer:
We have a distributed system with a lot of services talking to each other and many points of failure. The task here is to synchronize the state between all services, where the state is Map<TenantTimelineId, Active | Deleted>. We have a single source of truth for this state, it's stored in the console database.
We want to know the state in each service (console, safekeeper, pageserver, compute, etc.), because we want to allocate and free up resources for timelines accordingly. If we forget about the deleted state in safekeeper, we can accidentally recreate the timeline and fail to free up the resources (this exact issue). The most reliable way to ensure that we don't forget about the deleted state is to persist data to disk. That's why I proposed to keep info about deleted tenants on the disk.
Generally speaking, we may want to know not only whether the timeline is Active or Deleted, but also keep track of safekeepers and pageservers configuration (which safekeepers/pageservers are assigned to this timeline currently). Console (control-plane) is still a single source of truth of that info, and there are two good ways to access that state:

Ask control-plane API every time to read the state (works best if control-plane is very reliable and HA)
Store a local copy of the global state everywhere (requires effort to build a reliable pipeline to replicate state from control-plane database to all storage services)

There are also other ways, but in most of them we cannot guarantee that the state will converge, and we will not need to manually fix inconsistency artifacts that can happen because of restarts, partial unavailability, network issues, etc.

we can accidentally recreate the timeline and fail to free up the resources (this exact issue)

It looks like the problem can be solved with explicit create action. In this case if someone reaches to you after and asks about deleted tenant it will be 404 or something like that

Fix with remembering deleted timelines until next restart was merged, this can be closed.


How to serve different home page for different domains?

I have three sites host on the mezzanine project. It goes well except that three domains goes to the same home.html template, which it's not what I want. What I need is routing requests to its own home template.
a.com -> home-a.html
b.com -> home-b.html
c.com -> home-c.html

You may try making home page a special page (see comments in your main urls.py) or using themes by site:
http://mezzanine.jupo.org/docs/multi-tenancy.html

Please use the mailing list for general help requests: https://groups.google.com/g/mezzanine-users


java.sql.SQLException: Column name pattern can not be NULL or empty.

In a Maven project i try to connect to a MySql database (version 5.7.19).
Instrumentation works, also Base.open() seems to run through. But when i try to perform a findAll() request i get the following error message:
org.javalite.activejdbc.InitException: java.sql.SQLException: Column name pattern can not be NULL or empty.
This is my database.properties for development:
development.driver=com.mysql.cj.jdbc.Driver
development.username=root
development.password=
development.url=jdbc:mysql://localhost/my_db

This is my test code:
Base.open();
List<Channel> channels = Channel.findAll();
System.out.println("channels size: " +channels.size());
Base.close();

What could be wrong here? Thank you!

I had this dependency:
<dependency>
   <groupId>mysql</groupId>
   <artifactId>mysql-connector-java</artifactId>
   <version>8.0.8-dmr</version>
</dependency>

Going back to version 5.1.38 does work. This seems to me quite a big step back. Which version of mysql-connector-java is the most recent one which works?

@rivella50 this is unlikely a bug in the framework. The Base simply calls JDBC. Try writing a simple JDBC program and execute select * from channels and see it it works. My guess, this is some mismatch in a way you declare a table, a version of MySQL and a version of the driver. ActiveJDBC is a pass-through framework. It is not trying to be 'smart' with data types.

Ok, thank you, Igor!


Add frustum

No extra Files Again.

Hope I have made up to all your requirement now.
Please Review.

You need to resolve the conflict. When done I'll merge as it looks good.

@ajpmaclean : Conflict Resolved.

Thanks


Fixes issue #9 - Judges 5 should have only 31 verses

English KJV Judges Chapter 5 has 32 verses instead of 31

Why has this not been merged?


Pin packaging to >= 20

Describe the bug
If the packaging library is 19.2 or older, this line under dtypes throws an error.
I tested with 20+ and it works just fine.
This has been experienced elsewhere as well.
I would suggest pinning the version to >= 20.0.

[x] I have checked that this issue has not already been reported.
[ ] I have confirmed this bug exists on the latest version of pandas.
[ ] (optional) I have confirmed this bug exists on the master branch of pandas.

Screenshots

closing, just saw #380 .

closing, just saw #380 .

thanks @ktroutman, will cut a bugfix release so that latest version has this fix

thanks @ktroutman, will cut a bugfix release so that latest version has this fix


add static-contact-dynamics example

This PR adds a new python example. The example computes the static contact dynamics with Solo12.

It seems like there is a problem with the example-robot-data dependency in the CI. Should I remove the dependency on example_robot_data and load the robot like in https://github.com/stack-of-tasks/pinocchio/blob/b4d7a8b6240f760e824cba06c9c93c95f594dd12/examples/meshcat-viewer-dae.py#L17-L22 ?
Also, I think I've put the example in the wrong line of the CMakeLists.txt. Should it be here https://github.com/stack-of-tasks/pinocchio/blob/b4d7a8b6240f760e824cba06c9c93c95f594dd12/examples/CMakeLists.txt#L71 ?

Yes, you should like the other examples, as example-robot-data depends on pinocchio.

Also, I think I've put the example in the wrong line of the CMakeLists.txt. Should it be here
https://github.com/stack-of-tasks/pinocchio/blob/b4d7a8b6240f760e824cba06c9c93c95f594dd12/examples/CMakeLists.txt#L71

Yes, indeed.

Happy to contribute, @jcarpent . When the time comes, let me know if you want me to rewrite the example to meet any notation criteria.


import scan fails with java rest API

Please use the following template when submitting issues:
Issue Template
Issue Type

[ ] Bug
[X] Enhancement

Description
i am using java code to import a scan report to DefectDojo via its rest API.
in the post json body, for the file parameter, i set it as string. but defectdojo rejected it with error "invalid format"
checked the parser, found they use code   json.load()  instead of json.loads()
if i changed the parser code to json.loads(), rest API importing can work, but i will fail to import via the web console.  seems i enter a dilemma.
so for the java rest api client, how to import a scan result?

use HttpEntity


Marshal error messages enhancement

This PR provides marshal/unmarshal error messages enhancement.
According to #671 errors were updated by the supported types list.

https://issues.apache.org/jira/browse/CASSGO-38


Troubles with Mac Os

I do not success on installing this plugin on my mac.
My book compile well on gitbook and on an ubuntu.
I have followed this tuto, with nmp installed thanks to brew.
vhuber@host% gitbook install
info: 8 plugins to install
info: No version specified, resolve plugin anchors
info: install plugin anchors from npm (gitbook-plugin-anchors) with version 0.4.0
<EMAIL_ADDRESS>node_modules/gitbook-plugin-anchors
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>info: >> plugin anchors installed with success
info: No version specified, resolve plugin include-highlight
info: install plugin include-highlight from npm (gitbook-plugin-include-highlight) with version 0.1.0
<EMAIL_ADDRESS>node_modules/gitbook-plugin-include-highlight
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>info: >> plugin include-highlight installed with success
info: No version specified, resolve plugin mathjax
info: install plugin mathjax from npm (gitbook-plugin-mathjax) with version 1.0.0
child_process.js:1162
    throw errnoException(err, 'spawn');
          ^
Error: spawn E2BIG
    at exports._errnoException (util.js:746:11)
    at ChildProcess.spawn (child_process.js:1162:11)
    at exports.spawn (child_process.js:995:9)
    at spawn (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/lib/utils/spawn.js:7:13)
    at runCmd_ (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/lib/utils/lifecycle.js:207:14)
    at runCmd (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/lib/utils/lifecycle.js:172:5)
    at runPackageLifecycle (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/lib/utils/lifecycle.js:134:3)
    at Array.<anonymous> (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/node_modules/slide/lib/bind-actor.js:15:8)
    at LOOP (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/node_modules/slide/lib/chain.js:15:14)
    at chain (/Users/vhuber/.gitbook/versions/2.2.0/node_modules/npm/node_modules/slide/lib/chain.js:20:5)

and my book.json
{
    "gitbook": "2.2.0",
    "plugins": ["anchors","include-highlight","mathjax","ga","richquotes","toc","expandable-chapters","unicodecss"],
    "pluginsConfig": {
        "ga": {
            "token": "UA-65761593-1"
        },
        "richquotes" : {
            "todos" : true,
            "fixme" : true
        }
    },
    "links": {
        "sidebar": {
            "Feel++": "http://www.feelpp.org/",
            "GitHub": "http://www.github.com/feelpp/feelpp"
        }
    }
}

Was anyone able to resolve this issue? A quick fix or hack or something? I'm getting this error and I need to use something to typeset math formula in Gitbook, and so far this plugin fails to install.

I'm having the same issue. Cannot install MathJax on MAC OSX.

I found if you use the beta version then it works fine on OSX. You use the term mathjax-beta instead of mathjax in your book.json. Not sure why the beta version works and the main release doesn't.

@GravityScore your way works only in gitbook install statge, when I run gitbook build it will still throw out an error:
Error: Error loading plugins: gitbook-plugin-mathjax-beta.

+1

Related to https://github.com/GitbookIO/gitbook-cli/issues/11


posix: rwlock: implement pthread_rwlockattr_setpshared()

Implement pthread_rwlockattr_setpshared() and pthread_rwlockattr_getpshared().
Both functions are required by the _POSIX_READER_WRITER_LOCKS Option as detailed in Section E.1 of IEEE-1003.1-2017.
The _POSIX_READER_WRITER_LOCKS Option is required for PSE51, PSE52, PSE53, and PSE54 conformance, and is otherwise mandatory for any POSIX conforming system as per Section A.2.1.3 of IEEE-1003-1.2017.

removed blank line (my autoformat seems to be broken atm 😢)

@jukkar - can you please re-approve

It looks like the 2d review period is up for this too.


Session Logging

Description of the new feature/enhancement

Option to enable session logging, by which all everything being displayed on the terminal will be saved to a test file. Putty, SecureCRT and other ssh clients normally have this feature and it is extremely useful for network admins who work with switches and firewalls.
Proposed technical implementation details (optional)

Right click the tab to have option to enable/disable session logging. once clicked, it should ask where the log file should be saved. and once enabled, everything on that terminal tab should be saved to the text file until the session ends or tab closed

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9700 for more discussion.
/dup #9700


musl is added for linux

This will replace glib with musl for Linux distribution of wave cli

@jordeu I have reported an issue with GraalVM team
https://github.com/oracle/graal/issues/7685

This looks broken

new issue created with GraalVM team for jdk21 https://github.com/oracle/graal/issues/7717

@munishchouhan , when you have the chance, can you look at this related question from the Graal team: https://github.com/oracle/graal/issues/7717#issuecomment-1790863882
thank you :-)

@marcodelapierre sure

What's the need for Java 21? would staying on 20 solve the problem?

@pditommaso upgrade to 21 was advised by GraalVM team because they do not support 20 for native-image any more

Can a temporary workaround be using gclib static build instead of musl?

there is another option for building mostly static images
https://www.graalvm.org/22.0/reference-manual/native-image/StaticImages/#build-mostly-static-native-image

there is another option for building mostly static images
https://www.graalvm.org/22.0/reference-manual/native-image/StaticImages/#build-mostly-static-native-image

There still may be a problem here, as the "quasi-static" nature implies a dynamic linking to libc; hence we still need to make sure that we're using musl (preferably)  or static glibc.

@munishchouhan  referring to the static build issues with GraalVM 21 and Musl, how about testing the setup with a simple example, e.g. the one provided here by the GraalVM folks (see  static native example): https://www.graalvm.org/latest/reference-manual/native-image/guides/build-static-executables/

@munishchouhan after you are back to Spain, please take the chance to test on your local Linux environment

I tried testing it my local linux, but musl is not supported in AMR yet by native-image
https://www.graalvm.org/22.0/reference-manual/native-image/ARM64/
I tried using emulated ubuntu x86 but its very slow on mac

@pditommaso solved the test env issue
Now, I am using https://github.com/pditommaso/vagrant-with-quemu-provider for testing

Graalvm is crashing, when I am trying to use Linux x86 using vagrant, i have tried Ubuntu and OL8 and also increased memory to 16 GB but still no luck
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fd6b37a8560, pid=13689, tid=13692
#
# JRE version: OpenJDK Runtime Environment GraalVM CE 21.0.1+12.1 (21.0.1+12) (build 21.0.1+12-jvmci-23.1-b19)
# Java VM: OpenJDK 64-Bit Server VM GraalVM CE 21.0.1+12.1 (21.0.1+12-jvmci-23.1-b19, mixed mode, sharing, tiered, jvmci, jvmci compiler, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# J 548 c1 java.lang.ClassLoader.checkName(Ljava/lang/String;)Z<EMAIL_ADDRESS>(37 bytes) @ 0x00007fd6b37a8560 [0x00007fd6b37a8560+0x0000000000000000]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to /home/vagrant/.gradle/daemon/8.4/core.13689)
#
# An error report file with more information is saved as:
# /home/vagrant/.gradle/daemon/8.4/hs_err_pid13689.log
[2.861s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://github.com/oracle/graal/issues
#

Related issues
https://github.com/oracle/graal/issues/4076
https://github.com/oracle/graal/issues/5814

@pditommaso @jordeu please review
This PR is working now
I was not passing the PLATFORM variable which was raising this error, because GHA was trying to build non static executable using musl library


removed IDEA GroovyDSL script, must be provided separately

See JENKINS-29668 and JENKINS-29669 for details.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Added SonarQube to Travis build

SonarQube is a linter which automatically analyses projects.

The result of these changes will be that new build analyses should go to https://sonarqube.com/organizations/space-wizards/projects . It might end up being worthwhile to make a dev branch to bundle changes upstream for checking, but that would be premature right now.


Turtle trading strategy added.

What have you changed and why?
Turtle trading strategy added. (https://www.investopedia.com/articles/trading/08/turtle-trading.asp)
Related Issues
Link related issues here.

Awesome results, it looks a great trending following strategy. Huge payoff.
+---------+--------+-----+------+--------+--------+----------+-----------+
|  PAIR   | TRADES | WIN | LOSS | % WIN  | PAYOFF |  PROFIT  |  VOLUME   |
+---------+--------+-----+------+--------+--------+----------+-----------+
| BTCUSDT |     11 |   4 |    7 | 36.4 % |  6.985 |  5589.10 | 128796.84 |
| ETHUSDT |     13 |   7 |    6 | 53.8 % |  2.662 |  4956.29 | 129456.71 |
+---------+--------+-----+------+--------+--------+----------+-----------+
|   TOTAL |     24 |  11 |   13 | 45.8 % |  4.644 | 10545.39 | 258253.55 |
+---------+--------+-----+------+--------+--------+----------+-----------+

--------------
START PORTFOLIO = 10000.00 USDT
FINAL PORTFOLIO = 20545.39 USDT
GROSS PROFIT    =  10545.388134 USDT (105.45%)
MARKET (B&H)    =  407.84%
MAX DRAWDOWN    =  -24.53 %
VOLUME          =  258253.55 USDT
COSTS (0.001*V) =  258.25 USDT (ESTIMATION)
--------------

Hi Rodrigo,
Do you have time to check the latest changes and commit if there is no problem?

Hi Rodrigo,
Do you have plan for new features?
"Roadmap
Include trailing stop tool
Stop Orders in backtesting"

Sure, I will create a clean roadmap.
I have some ideas, for example:

Support Futures Market (Long / Short)
Support other exchanges (Bitmex, FTX, etc)
Include a hyperopt (tunning parameters)
Include a live chart (display candles and orders in real-time)
Improve backtesting with new metrics (avg trades, avg time, sharp ration, etc).

I will create more issues to discuss these ideas.
Do you have some suggetions?

I created a roadmap for indicators: https://github.com/rodrigo-brito/ninjabot/issues/110

I will try to start with basic indicators. If you will start any of them:
Support Futures Market (Long / Short)
Support other exchanges (Bitmex, FTX, etc)
Include a hyperopt (tunning parameters)
Include a live chart (display candles and orders in real-time)
Improve backtesting with new metrics (avg trades, avg time, sharp ration, etc).
Just let me know if I can help.


NodeJS (v0.12.2) deprecated method replaced in indexOf.js

NodeJS v0.12.2 and possibly earlier versions have depreacted the .get() method on a buffer object.
This error is generated
.get() is deprecated. Access using array indexes instead.
Line 16 in indexOf.js has been changed to use the array method.
if (haystack[i+j] !== needle[j]) {
Untested in previous node versions

Thanks @Desmodue  :smile:
This has been fixed in 4ac00c206641644670113cee3dff506bd9b5ece6


[Navi21] test_lrn_test (Failed)

ROCm 4.2, OCL backend, Navi21, Full test: test_lrn_test (Failed).
WORKAROUND_ISSUE_1053 is used to avoid this error.

WORKAROUND_ISSUE_1053 used to avoid this error.

@junliume @JehandadKhan Can you please assign this?

@ce1adon could you take a look? Possibly related to #1054 ? not applicable to Navi21 for some reasons?

@ce1adon could you take a look? Possibly related to #1054 ? not applicable to Navi21 for some reasons?

https://ontrack-internal.amd.com/browse/SWDEV-289454?focusedCommentId=7514219&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-7514219
Previous comments show it's a compiler issue.

@junliume @ce1adon https://ontrack-internal.amd.com/browse/SWDEV-289454 was rejected. It seems that the relevant ticket is https://ontrack-internal.amd.com/browse/SWDEV-288205, which is in closed state now, but fixed Mainline build number of the compiler/runtime was not published there.

I recommend checking the issue with the most recent ROCm 4.3 release candidate, If the issue persists, then SWDEV-288205 can be reopened.

@xinlipn  I have tested a few times, and it seems that at least for the HIP backend, this workaround can be removed.


Proposal. Open a source file in it's original place (github, bitbucket etc)

Is your feature request related to a problem? Please describe.
The CodeChecker bug view mode doesn't show neither git blame info nor file history so it makes hard to report a bug for the code owner.
Describe the solution you would like
Open an external site where the file with a CodeChecker bug originates from. For example to open GitHub or BitBucket etc with the given file and line number.
 Site URL and line number templates can be taken from the  CodeChecker config file.
diff --git a/web/server/www/scripts/codecheckerviewer/BugViewer.js b/web/server/www/scripts/codecheckerviewer/BugViewer.js
index d14ff54f..65b00385 100644
--- a/web/server/www/scripts/codecheckerviewer/BugViewer.js
+++ b/web/server/www/scripts/codecheckerviewer/BugViewer.js
@@ -187,6 +187,15 @@ function (declare, domClass, dom, style, fx, Toggler, keys, on, query, Memory,
         that._lineDrawer(from, to);
       });

+      this.codeMirror.on("gutterClick", function(cm, n) {
+        var info = cm.lineInfo(n);
+        window.open(
+          "https://source.chromium.org/chromium/chromium/src/+/master:" +
+          that.filepath.innerHTML +
+          ";l=" +
+          (info.line + 1).toString());
+      });
+
       on(document, 'keydown', function (event) {
         if (event.ctrlKey && event.keyCode === 13) // Enter
           that.codeMirror.execCommand('findPersistentNext');

Additional context
With my fix applied just left-click on the line number on the left.

What do you think? Does it make sense?

@irishrover We are planning to integrate CodeChecker with git.
Our first plan is to set run name and version tag information based on git information at the CodeChecker store command (the run name will be the branch name and the version tag will be the latest commit hash).
Our second plan is to show git blame information alongside the file editor on the UI (show the commit hash and author who modified the line). I agree with you that it would be also a great feature to go to the source code repository and to see for example the commit our the source file there.
It's still under discussion in our side and I think our plan is to do this on the next major CodeChecker release: v6.13.0.


[KIE-790]  Build error on RuleUnit multiple OOPath lines

https://github.com/apache/incubator-kie-issues/issues/790

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests

for a full downstream build

for jenkins job: please add comment: Jenkins run fdb
for github actions job: add the label run_fdb

a compile downstream build please  add comment: Jenkins run cdb

an upstream build please add comment: Jenkins run upstream

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native

for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts

for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

DRL considers a new line is just WS, which is not used as a delimiter of the syntax.
So it was valid to parse
        /measurements[ $id: id == "color", $colorVal : val ]
	/sensors[ id == $id ]

as one constraint:
/measurements[ $id: id == "color", $colorVal : val ]/sensors[ id == $id ]

However, if we want to consider that they are 2 OOPath patterns, we need to use a new line as a delimiter. So this fix is exceptional.
As a fundamental fix, IMO, we need to introduce an explicit syntax to begin an OOPath. e.g. $/
For example)
        $/measurements[ $id: id == "color", $colorVal : val ]
	$/sensors[ id == $id ]

WDYT? @mariofusco

@tkobayas This is a problem that I discussed in the past also with @lucamolteni and @tarilabs and we never found a solution. I think yours is very clever and fixes an actual unexpected problem for many users, so I'm in favor for bringing it in.
For what regards having a proper oopath separator, actually we already have the ; which in my opinion is the most obvious one., so I wouldn't introduce any other. In essence if you write
/measurements[ $id: id == "color", $colorVal : val ]; // <-- note the semicolon at the end of this line
/sensors[ id == $id ]

it should already work. However I just searched our documentation to check if we're mentioning this and indeed I couldn't find any reference to it, so it would be nice to also add it to the docs.

Thank you, Mario! @mariofusco @lucamolteni Please review.

For what regards having a proper oopath separator, actually we already have the ;
...
However I just searched our documentation to check if we're mentioning this and indeed I couldn't find any reference to it, so it would be nice to also add it to the docs.

Oh, thanks. It worked! I filed https://github.com/apache/incubator-kie-issues/issues/803 and will work on it :)


Deleting individual events: It's weird that sometimes I get a confirmation prompt and sometimes I don't

This issue was raised by Cameron and Rickie in the process of developing and testing #1389.
Affects: Saved event targets with no result linked to them.
Issue
When I delete an individual event, I am not prompted for confirmation. When I click "Remove all targets", I am prompted. This feels oddly inconsistent, since removing the last target is the logical equivalent of clicking "Remove all".
I'm struggling to remember why we implemented it like this, and my best guess is that it had something to do with Winterhawks-specific constraints and tradeoffs. In any case, we can do better.
Acceptance criteria
Revision to Scenario 4 in 1389: Deleting an UNSAVED Event target with NO results linked to it
The way it works now: If there are no linked results, I can delete an unsaved event target with no confirmation prompt and no rationale prompt.
Desired change:

[ ] 1. I get the same confirmation prompt I get if I click "Remove all"

[ ] 2. Clicking "Cancel" or the "X" closes the prompt with no change.

[ ] 3. Clicking "OK" deletes the event target row.

Revision to Scenario 5 in 1389: Deleting a SAVED Event target with NO results linked to it.
The way it works now: I can delete a saved event target with no confirmation prompt and no rationale prompt.
Desired change:

[ ] 1. I get the same confirmation prompt I get if I click "Remove all"

[ ] 2. Clicking "Cancel" or the "X" closes the prompt with no change.

[ ] 3. Clicking "OK" deletes the event target row.

Housekeeping (where applicable)

[ ] Unit test/s written
[ ] i18n strings included
[ ] Is accessible to people using screen readers

@RickieT Just filed this, based on your feedback. Cameron asked that I put it in a separate ticket from 1389.
This is NOT a release blocker, but @camgnostic just want to bring this to your attention on the off chance that 1389 is giving you headaches and this is actually easier to implement.

Implementing this I ran into a problem:
if you delete a SAVED event target, you get a prompt (no rationale) and clicking okay deletes it.  Then when you hit save, a different prompt from another part of our rationale logic detects that targets have changed and prompts for a rationale.  The target has already been deleted at this point, so even if you hit cancel and close, the target remains deleted.  So do we want a rationale prompt for deleting a target without linked results?  If so, do we want the prompt when you initially click "delete" on a saved event target?  and then no prompt when you save the whole indicator form?
Prompt that I get clicking "save":

Tagging @jennyhavah as this is confusing

@camgnostic I think I may know how to work around the above wonkyness

Holy hell was that confusing. First I'll share my conclusions, and then explain how I got there. So in the case of an event indicator with linked results to ANY of its targets:

We DO prompt for a deletion rationale at the time you delete an individual event, regardless of whether or not that specific event is the one with the linked result.

If the specific event being deleted does NOT have linked results, we can use this wording in the rationale prompt: This action cannot be undone. For future reference, please provide a rationale for deleting this target.

If the specific event being deleted DOES have one or more linked results, we can use this wording in the rationale prompt:  This action cannot be undone. Any results assigned to this target will need to be reassigned. For future reference, please provide a rationale for deleting this target.

Even if no other changes are made after deleting event targets and I click “Save changes”, then at this point I would expect the yellow rationale prompt to show up even though it's meaningless and and then proceed to fail to save anything I type, because that’s ANOTHER bug we need to deal with. (I’ll file a separate ticket for that.)

And now the meandering thought process behind these conclusions, for the record.

Just to emphasize: This is a scenario where at least one event target has a result linked to it. Because as a general rule, we don't prompt for rationales when there are no results linked to ANY of the targets.

The event target you're deleting is not necessarily the one that had results linked to it.

Even if the specific event target was NOT the one with the linked results, it is still true that you're modifying the performance metrics of the indicator as a whole by deleting that target. So it makes sense to prompt for a rationale, regardless.

And SO, you ask, why not skip the confirmation prompt and just display that rationale prompt right as you're deleting the target, and not wait until you click Save changes? Good point!

The only risk I can think of is that if you’ve made any OTHER changes to the indicator prior to deleting the event target — such as updating the LoP target — you might mistakenly think that the deletion prompt covers all changes and not bother to click “Save changes” on the indicator as a whole.
However, I think that risk is outweighed by the risk of not capturing a rationale for the deletion at all, if we delay the prompt until you save changes to the indicator as a whole.
In fact, we have the exact same risk with the “Remove all targets” button — in that you could conceivably make other edits prior to clicking that button and lose those changes if you don’t click “Save changes” afterwards. But again, I think it’s outweighed by the risk of allowing that deletion to proceed with no prompt.

This ticket is no longer about "one weird little deferrable inconsistency" but more generally about tying up loose ends around event deletion. I've updated the title accordingly and -- after checking in with Cameron -- am moving it into This Release.

Moving this back to This Release while @KennyMonster works on the holistic "why are rationale prompts so wacky?" question

PASSED.

Prior to saving an event target, I am prompted for confirmation before deleting it. (No rationale, as expected.)

After saving event targets, before linking results, if I delete one event, I am prompted for confirmation before deleting it. (No rationale, as expected.) This is true both in the full-page and modal versions.


Problem with the calender

When i try to use the command export_ical this doesn't work, please could you help me.

Can you provide more information? What does it output? Is it that the link just doesn't work?


Could you please tell me how to get the mAP? THX!!!!!!!

I have trained on my own DS. But I have no idea how to get the map. Someone plz help me!!!!!!

https://medium.com/@jonathan_hui/map-mean-average-precision-for-object-detection-45c121a31173

https://medium.com/@jonathan_hui/map-mean-average-precision-for-object-detection-45c121a31173

I read your fork in morpheusthewhite@8c5307c before and cloned it. But I noticed that there are two documents named Annotation_imagenet and Annotation in C:\Faster-RCNN-TensorFlow-Python3.5\data\imagenet and I don't know which should I add my xml documents in.
Plz help me about that thx!!!

https://medium.com/@jonathan_hui/map-mean-average-precision-for-object-detection-45c121a31173

I read your fork in morpheusthewhite/Faster-RCNN-TensorFlow-Python3.5@8c5307c before and cloned it. But I noticed that there are two documents named Annotation_imagenet and Annotation in C:\Faster-RCNN-TensorFlow-Python3.5\data\imagenet and I don't know which should I add my xml documents in.
Plz help me about that thx!!!

You should put them in data/imagenet/Annotation_imagenet (I'll soon update the README)

https://medium.com/@jonathan_hui/map-mean-average-precision-for-object-detection-45c121a31173
this address is invaid, can you give another one? Thx

https://medium.com/@jonathan_hui/map-mean-average-precision-for-object-detection-45c121a31173
this address is invaid, can you give another one? Thx

It works for me


[FR] - Missing 1.25.1 Linux executable

External
Area
Other
Describe the feature you'd like
Even though the 1.25.1 was made some weeks ago, I couldn't find any Linux executable for this version (such as https://hydra.iohk.io/build/5563812). Any chance for an executable for this version to be provided?
Describe alternatives you've considered
Alternative would be just build from sources (I would like to avoid using docker).

You could extract the binary from an existing docker images or perhaps even use nessusio/cardano for example.
Also please have a look at #2360

I understand that these options are possible using docker, but then what's the point to link out an old executable on the cardano-node README? Will publishing these executables be discontinued?

The link correctly points to the "latest version of cardano-node and cardano-cli" built from master. If you want binaries for the latest tag (i.e. 1.25.1) you may have to build them - at least there isn't a download option that I'm aware of.

https://hydra.iohk.io/build/5446647/download/1/cardano-node-1.25.1-linux.tar.gz

No longer relevant


backend: query hub-auth (/device) to see if device is compliant with policy

@talwinder50 this endpoint is likely (not 100% certain yet) to be implemented in hub-auth and will be queried by edge-agent's http server during the WebAuthN registration ceremony.

This is not applicable now.


Fix title in metadata

Update the title tag from Karo v2 | ... to Karo | .... Basically remove v2.

Hi @sunnybeta , I would like to contribute to this. Feel free to assign it to me.


chore(ONYX-923): remove keyboard prop from edition text inputs

This PR resolves ONYX-923
Description

Remove the force numeric keyboard from Edition size and Edition number fields
Use default keyboard type

before
after

PR Checklist

[x] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

remove the force numeric keyboard from Edition size and Edition number fields -daria

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (remove the force numeric keyboard from Edition size and Edition number fields -daria)

  Generated by :no_entry_sign: dangerJS against c5506543ccfbc3e4a94af74e2e6f91553561f6e8


ARC-1723 - set createbranch pages inside jira

What's in this PR?
We have move the create-branch page to be part of the connect app routes "generalPages"
Why
This gives us access to JiraHost and the Connect API
How has this been tested?
Testing on stage and locally

I'm getting below error while running the flow

A scenario where user is auto-redirect to create branch page is also not working properly.

Looks good 👍


Denoms missing for some currencies

Summary of Bug

There are a few amounts that come from the API that don't include a denom. In order to correctly display the amounts the UI needs the coin.
Version

current
Steps to Reproduce

[x] totalShares in https://service-explorer.test.provenance.io/api/v2/validators/tpvaloper1tgq6cpu6hmsrvkvdu82j99tsxxw7qqajn843fe/commission
[x] supply in https://service-explorer.test.provenance.io/api/v2/assets/detail/cfigure
[x] balance in https://service-explorer.test.provenance.io/api/v2/assets/holders?count=10&id=nhash&page=1

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Worth noting that shares are not something expressed in coins… (aka nhash)


include full name for inclusive experience

Signed-off-by: Matt Cantu Snell<EMAIL_ADDRESS>

@Nebrethar I see there is a conflict in this -- is this something you're able to resolve?


Keep a way to opening a notebook with the default renderer without uninstalling the extension

Describe the bug
context
For being able to test this extension in a hosted hub, it's critical that I can switch back and forth between the MystJS renderer and a "normal" view with the default one, as was possible til 0.1.2.
If we notice problems with mystjs, right now we have no option but to entirely uninstall it and redeploy into production, which is a huge barrier.
I'm happy to tell students to occasionally switch to the old renderer manually if necessary, but having to redeploy makes it impractical to test/use the tool while it matures in a production environment.
Reproduce the bug
Once installed, mystjs takes over completely all notebook rendering.
List your environment
No response

Could you clarify your needs here? You shouldn't need to uninstall the extension to disable it: one can run jupyter labextension disable jupyterlab-mystjs.

The PR / discussion that introduced this is here:
https://github.com/executablebooks/jupyterlab-mystjs/pull/17#discussion_r1093567917
I wonder if it was a bit premature to fully take over the renderer. The terminal approach might be a bit much for students at the moment, I think there is a disable extension UI in Jupyter4.0?! Can't wait :)

Yup, our students don't control the startup of the environment itself, so the approach that was there in 0.1.2 was just about right. They could choose which to use, but it's too much for me in class to be telling them to basically reconfigure the server every time they log in.

I'm already pushing the limits of dog-fooding in a real-world course, I need to keep my focus on actually teaching a class :)

Though thanks @agoose77 for the labextension disable tip - I'd forgotten about it, and while not the answer I need for this particular scenario, it can be a good solution for other cases! Much appreciated.

@fperez so you need the ability to switch off the MyST renderer in some contexts during the same session? Could you elaborate on why you need this, is it just missing features?

Yup, precisely - the way it worked originally.
Right now if there's any bug/mismatch in this renderer compared to the default, escaping out is tricky. I'm using a real-world course to test this, so I need my students to very easily fall-back (within the same session they are working on) to the default renderer at any sign of trouble.

Are you using .ipynb notebooks, or jupytext-backed Markdown notebooks?

.ipynb notebooks for the most part.

OK. My take (not the only one that matters by any stretch of the imagination) is that the majority of our users at this stage should be using jupyter labextension disable ... to turn on/off the renderer. This is because we integrate much better with the rest of the JupyterLab tools in doing so. However, I can see that your use case is trickier because of this, so perhaps we can find a compromise; a second, mutually exclusive JupyterLab extension (shipped in this repo) that restores the old behaviour. This would be opt-in for you, so you can configure your binder image such that the old behaviour is the default.

Yup, I'm happy to do that - I have full control over my hub config so I can add any extension the team offers, as long as it has that functionality.
Thx!!

Other approaches could be:

to revert parts of the update, and keep the PR waiting in the wings while we improve the extension so that the fallback becomes less and less required?
Provide a setting to toggle the behaviour?

I think at this stage we are already have jupyterlab-mystjs and jupyterlab-myst -- my goal this week was to reduce myst extensions in the wild not add more. :)
I am not sure if (2) is easily possible, but would love to see settings start to emerge in this extension, so that could be a way to get into doing that!

@rowanc1 on terminology, in the JupyterLab context an "extension" is just a re-usable unit of code that integrates with the dependency injection system. We can ship multiple in the same package. I think we might be able to e.g. trigger a setting, but the user would also need to reload the page. I can see why that would be a poor UX if @fperez wants students to be able to do this multiple times in a session :/
I'll push a PR that we can bikeshed :)

Ok, awesome. Mostly trying to avoid having more pip/npm/conda packages out there. Looking forward to seeing what you come up with, thanks @agoose77. Let me know when I can help out!

BTW @rowanc1 is there a feeling that we'll use an organisation package name, e.g. @executablebooks/jupyterlab-mystjs?

TL;DR: I think we should stick with a flat namespace (no @ team) in the JS world.
We debated this a lot with the myst-to-html myst-to-jats naming conventions, different communities take different approaches to this. What I like about the 'flat' namespace is that there is no distinction between an official extension and a community extension, and that speaks a bit more to our values I think. I like that for things that should in-principle work together on equal footing (e.g. in prosemirror).
I think there is a different approach if there is a collection of packages that must all be installed together to work, this is the approach that we are taking for @myst-theme (and in @jupyterlab and many other tighter-knit packages).

@fperez, @agoose77 fixed this up in a PR, I want to get the HTML parsing working and then will aim to cut another release this afternoon!

#36

Fantastic, I'll push to our hub once it's on PyPI and will keep reporting.  I immensely appreciate the team's hard work, I'm very excited about working this semester with MyST with our students - thx @agoose77 for the responsiveness!


Installing a specific version of python

Hello
How are you?
Thanks for contributing to this project.
Now days, the default version of python3 on Google Colab is 3.10.
I am going to use python3.8 on Colab.
So I am going to install & use this condacolab.
How should & install I this condacolab for python3.8?

Hi @rose-jinyang, I have the same issue/task; have you solved it?
Thank you,
Sam.

Hey folks, currently published version only supports whatever condacolab runs on. However, the development version on main should support arbitrary Python runtimes, but this hasn't been tested widely yet and there are a few details that need to be polished.
If you want to give it a try, you can use:
!pip install https://github.com/conda-incubator/condacolab/archive/main.tar.gz

Let me know how it goes!

Hey folks, currently published version only supports whatever condacolab runs on. However, the development version on main should support arbitrary Python runtimes, but this hasn't been tested widely yet and there are a few details that need to be polished.
If you want to give it a try, you can use:
!pip install https://github.com/conda-incubator/condacolab/archive/main.tar.gz

Let me know how it goes!

So the command to specify a specific version of python is?
I found a fork before where you can specify the python version as follows
condacolab.install(
   environment_file="https://raw.githubusercontent.com/ssurbhi560/condacolab/07b92d827/environment.yaml",
   python_version="3.10",
   specs=["matplotlib", "numpy"],
   channels=["conda-forge", "bioconda"],
   pip_args=["blue"]
   extra_conda_args=["-yq"]
   )

But that doesn't work, the main branch I don't seem to see any demos and instructions for that, how do I specify a specific python version?

any news on how this works?

So if I'm using packages  that are only available on conda and require a specific python version, I can't use google colab?
If you can't install packages, what's the point of google colab?

Hey folks, currently published version only supports whatever condacolab runs on. However, the development version on main should support arbitrary Python runtimes, but this hasn't been tested widely yet and there are a few details that need to be polished.
If you want to give it a try, you can use:

!pip install https://github.com/conda-incubator/condacolab/archive/main.tar.gz

Let me know how it goes!

I have tried it, instal failed


User docs: get rid of "old table of contents"

Let's do a quick audit of https://chat.zulip.org/help/ so we can get rid of the "old table of contents" section - per https://chat.zulip.org/#narrow/stream/documentation/subject/user.20help/near/95296 , make sure everything is linked above first.

I can handle this issue, in fact I'm working on it right now.

https://github.com/zulip/zulip/pull/3146

Fixed via #3146!


Backend for Auto-scroll Issue and Total Count Card for Staff Capacity Pagination in facility details page

Bug Description:
Auto-scroll behavior and incorrect total count display for staff capacity pagination in the facility details page.
Steps to Reproduce:

Go to the facility details page.
Add or update staff capacity.
Observe auto-scroll behavior.
Check the total capacity card for incorrect count (shows current page only).

Expected Behavior:

Auto-scroll should stop at the staff capacity section instead of the page's top.
Total capacity card should display the total staff capacity across all pages.

Screenshots/Recordings:
https://github.com/user-attachments/assets/1b04ecb1-ef59-4638-a177-87a36a463853
Additional Context:
Fix reference Frontend: [Issue #9122]
Fix reference Frontend Pull Request: [PR #9275]

Closing in favor of https://github.com/ohcnetwork/care_fe/pull/9436


Import error import name import_string

when i am trying to install ratticDB i got this below error
Kindly help me to rectrify it
./manage.py syncdb --noinput
Traceback (most recent call last):
File "./manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/init.py", line 399, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/dist-packages/django/core/management/init.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(*args, **options.dict)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 284, in execute
self.validate()
File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 310, in validate
num_errors = get_validation_errors(s, app)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/validation.py", line 34, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line 196, in get_app_errors
self._populate()
File "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line 78, in _populate
self.load_app(app_name)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line 99, in load_app
models = import_module('%s.models' % app_name)
File "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in import_module
import(name)
File "/usr/local/lib/python2.7/dist-packages/two_factor/models.py", line 20, in
from .gateways import make_call, send_sms
File "/usr/local/lib/python2.7/dist-packages/two_factor/gateways/init.py", line 2, in
from django.utils.module_loading import import_string
ImportError: cannot import name import_string

This has nothing to do with the debug toolbar. You're using a version of django-two-factor-auth that's incompatible with your version of Django.


Prep work for release 0.1.7

Prep work for upcoming release.

Increment version number.
Verify python compatibility version.
Update CHANGELOG
Push to test pypi first.
Upon success, push to main pypi.

Development to Integration PR: https://github.com/cjcodeproj/medialibrary/pull/103
Integration to Main PR: https://github.com/cjcodeproj/medialibrary/pull/104

Release complete.
https://pypi.org/project/medialibrary/0.1.7/


Can't locate Bio/SeqIO.pm

Hi i am using MacOS Catalina, i am facing this error. i have tried through conda and CPAN to fix this. i am facing this error from last 2 weeks, Before this module was working . Can you guide me, How i can fix it.
Can't locate Bio/SeqIO.pm in @INC (you may need to install the Bio::SeqIO module) (@INC contains: /Users/padana/opt/anaconda3/lib/site_perl/5.26.2/darwin-thread-multi-2level /Users/padana/opt/anaconda3/lib/site_perl/5.26.2 /Users/padana/opt/anaconda3/lib/5.26.2/darwin-thread-multi-2level /Users/padana/opt/anaconda3/lib/5.26.2 .)

@ABDULLAHGUJJAR that looks like a Perl error. Are you after the Perl Repo. This module targets Raku (aka Perl6).


proposal: Add inspect stage to loki.process

Promtail's pipeline stages have been historically hard to debug; especially for pipelines that heavily depend on the extracted map of values, conditionally apply to only a subset of entries, or make use of more complex features such as templating. Flow's rendition of pipeline_stages in the loki.process component suffer from the same underlying issues.
I'd like to suggest that we introduce an inspect pass-through stage that does not alter incoming log entries or the shared extracted map.
The stage will make use of a LogQL stream selector and a sampling fraction to determine which log entries should be inspected. For entries selected for inspection, the stage would collect the log content, labels and the values in the shared extracted map and either log them, or append them to the parent loki.process component's DebugInfo.
So, given a user who's trying to understand what's going on in the following pipeline, they should be able to insert the inspect stage in any step of the process, reload the Flow config and be able to gain some understanding on how their processing stages work.
stage {
	regex {
		expression = "^(?s)(?P<time>\\S+?) (?P<stream>stdout|stderr) (?P<content>.*)$"
	}
}
stage {
	timestamp {
		source = "time"
		format = "RFC3339"
	}
}

/ *
stage {
        inspect {
                selector          = '{appLabel="mysql"} |~ ".*noisy error.*"'
                sampling_fraction = 0.1
        }
}
*/

stage {
	output {
		source = "content"
	}
}
stage {
	labels {
		values = { src = "stream" }
	}
}`

I created an issue to add live debugging support for the loki.process component. It should be able to provide insights on every stage without having to modify the pipeline.
@tpaschalis what do you think? Should we close this proposal?


Create entity list configurability POC

Need
For background and prior effort, see #35.
Approach

Add to existing list config functionality.
Start with HCA only (AnVIL will be addressed in a separate ticket).
Add a column config for each entity (currently projects, files and samples for HCA) that integrates with React Table's column config.
Don't worry about the polishing the UI; skinning will be handled in a separate ticket.

Definition of Done

Configuring entity columns drives corresponding table UI.
Storybook updated (stub configuration for any new components).


Issue/6549 fix issues with deploy or repair interval cron expressions

Description
closes https://github.com/inmanta/inmanta-core/issues/6549
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Failed to merge changes into iso6 due to merge conflict. Please open a pull request for these branches separately by cherry-picking the commit that was made on the branch master (git cherry-pick 23be8cf317c08517f0299d0519aadfd52cf6fba6).

Merged into branches master in 23be8cf317c08517f0299d0519aadfd52cf6fba6

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches by cherry-picking the relevant commit. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.

merged into iso6 with https://github.com/inmanta/inmanta-core/pull/6591


BUG: optimize.least_squares with method='trf' yields wrong result when initial guess is close to (lower) bound

Describe your issue.
When least_squares is called with method='trf' and the initial guess for a fit parameter is very close (<1e-10) to the lower bound, the optimization does not work and 1e-10 is returned as the "optimized" parameter. This is very likely due to the call of the function make_strictly_feasible in that case. In this function, the initial guess appears to be set to lower bound + 1e-10 if it is closer than 1e-10 to the lower bound.
Would it make sense to call make_strictly_feasible only when the initial guess is actually not feasible? This is checked a couple of lines earlier (with the function not_in_bounds).
Reproducing Code Example
import numpy as np
from scipy.optimize import least_squares

def chi2(x):
    return (x-1e-12)**2

print (least_squares(chi2, x0=1.1e-12, bounds=(0, np.inf)))

Error message
message: `gtol` termination condition is satisfied.
     success: True
      status: 1
         fun: [ 9.801e-21]
           x: [ 1.000e-10]
        cost: 4.802980050000001e-41
         jac: [[ 1.510e-08]]
        grad: [ 1.480e-28]
  optimality: 1.479868788609009e-38
 active_mask: [-1]
        nfev: 1
        njev: 1

SciPy/NumPy/Python version and system information
1.10.0 1.24.1 sys.version_info(major=3, minor=10, micro=6, releaselevel='final', serial=0)
blas_mkl_info:
  NOT AVAILABLE
blis_info:
  NOT AVAILABLE
openblas_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
    runtime_library_dirs = ['/usr/local/lib']
blas_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
    runtime_library_dirs = ['/usr/local/lib']
lapack_mkl_info:
  NOT AVAILABLE
openblas_lapack_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
    runtime_library_dirs = ['/usr/local/lib']
lapack_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
    runtime_library_dirs = ['/usr/local/lib']
Supported SIMD extensions in this NumPy install:
    baseline = SSE,SSE2,SSE3
    found = SSSE3,SSE41,POPCNT,SSE42,AVX,F16C,FMA3,AVX2
    not found = AVX512F,AVX512CD,AVX512_KNL,AVX512_KNM,AVX512_SKX,AVX512_CLX,AVX512_CNL,AVX512_ICL

Hi Adrian!
I agree that x0, not lb+1e-10, should be returned if x0 is a satisfactory solution. I tried removing that initial make_strictly_feasible (line 828 in least_squares.py) and, after that, trf that behavior (x: [ 1.1e-12 ]). As far as I can tell the initial make_strictly_feasible isn't needed because scipy already throws an error if the initial condition is out of bounds. I will make a PR with this change.

Thanks, @ellieLitwack!

I have opened this issue because the rstep set to 0 at least_square function in some specific cases result in a nan in this division: x0 * scale_inv / v**0.5 (optimize._lsq.trf.py line 234
https://github.com/scipy/scipy/issues/19309