dataset

ViP3D
├── mmdet3d/
├── plugin/
├── tools/
├── data/
│   ├── nuscenes/
│   │   ├── maps/
│   │   ├── samples/
│   │   ├── v1.0-trainval/
│   │   ├── lidarseg/
你好你好，请问一下你的数据集是下载的min吗？nuscenes文件夹下的lidarseg文件是从Nuscences-lidarseg下载的吗

It is nuScenes full dataset (1000 scenes). lidarseg is obtained from full dataset here:

It is nuScenes full dataset (1000 scenes). lidarseg is obtained from full dataset here:

THANKS FOR YOUR ANSWER!

hi, after extracting the full dataset it is like
/data/sets/nuscenes
samples	-	Sensor data for keyframes.
sweeps	-	Sensor data for intermediate frames.
maps	-	Folder for all map files: rasterized .png images and vectorized .json files.
v1.0-*	-	JSON tables that include all the meta data and annotations.
is  Lidarseg the same as sweeps or we need to download it from other source?

If running training without downloading lidarseg, what will happen?

If running training without downloading lidarseg, what will happen?

Can i use mini-dataset?


Sync error

Won't sync remote deck.
" Could not find a suitable TLS CA certificate bundle, invalid path: C:\Users\username\AppData\Local\Temp\tmpimflzkrmcacert.pem"

Still don't know what happened, but fixed by removing the deck sync and turning the addon on and off again...


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or a supporter signed this repo up for Open Collective. This pull request adds backers and sponsors from your Open Collective https://opencollective.com/rlsl ❤
It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets
P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).
Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

I went ahead and put the contributor image in even though you are not accepting contributions now. You can remove/readd later if you want.


Feature Request: !dadjoke needs to be able to search https://icanhazdadjoke.com/search

Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.09 KiB | 0 bytes/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
To https://github.com/LEXmono/q.git
94c0dd7..a61a1ce  master -> master


init incubator/status

Signed-off-by: Gregory Hill<EMAIL_ADDRESS>What this PR does / why we need it:
There are a number of open source status pages for monitoring / reporting service health, but currently there is no easy way to bootstrap these in a cloud environment. This chart introduces a generic wrapper into incubator that allows the installer to chose between (currently) one of three web services for performing this task.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

hey @gregdhill
Have you considered hosting this chart and adding it to helm hub?
https://github.com/helm/hub/blob/master/Repositories.md


list is not recognized as a class

class C(list):
    pass

codon run test.py
gives the following error message:
test_codon.py:1:1-33: error: class name 'list' is not defined

list is a type alias for List, and aliases are currently not working when inheriting classes. List should work as an interim measure until we fix this.

Fixed in #604.


Create README.md

100 days of code
Thanks for your participation in 100 days of code. These 100 days of coding will help you get a nice understanding with hands on approach towards solving problems. Stay determined, stay motivated and happy coding :)
📝Please make sure to follow these points

[ x] Created a separate folder with your name. eg brahmajeet
[ x] Made daily solution file of problem in format. eg DAY-1.py
[x ] I have uploaded my own solution.
[x ] My Pull Request title is in format < name > - < day >  eg  Brahmajeet-day-1
[x ] I will upload ALL MY SOLUTIONS in my folder ONLY.

Thank you!
Your part is over after your pull request is made. Your Pull Request will be merged soon if approved by maintainers. Happy contributing.

@soham117  later on while doing the checkouts  do [x] instead of [x ] or [ x]  (without spaces)

Alright !


Run against Erlang 19.3 & 18.3

also found out there is an erlang 18.3.4 which we can run against
made it a proper crossover matrix with all elixir versions against
all erlang versions - thank you travis sorry for the load :)

Dialyzer throws warnings/errors on the combination of elixir 1.4.2 and Erlang 18.3 - funnily I have a similiar problem over at benchee but with Erlang 18.2 I suppose.
lib/wallaby/browser.ex:795: The call _@2:'conditions'() requires that _@2 is of type atom() | tuple() not #{}

lib/wallaby/browser.ex:980: The call _@1:'host'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/browser.ex:982: The call _@4:'host'() requires that _@4 is of type atom() | tuple() not #{}

lib/wallaby/browser.ex:1121: The call _@1:'selector'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/browser.ex:1131: The call _@1:'selector'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/phantom/driver.ex:317: The call _@1:'session_url'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/phantom/server.ex:93: The call _@4:'base_url'() requires that _@4 is of type atom() | tuple() not #{}

lib/wallaby/phantom/server.ex:93: The call _@2:'awaiting_url'() requires that _@2 is of type atom() | tuple() not #{}

lib/wallaby/phantom/server.ex:109: The call _@1:'awaiting_url'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/query.ex:245: The call _@1:'result'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/query.ex:248: The call _@2:'result'() requires that _@2 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:63: The call _@19:'result'() requires that _@19 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:63: The call _@16:'result'() requires that _@16 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:63: The call _@15:'method'() requires that _@15 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:63: The call _@10:'result'() requires that _@10 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:63: The call _@7:'selector'() requires that _@7 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:75: The call _@1:'method'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:162: The call _@1:'conditions'() requires that _@1 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:168: The call _@6:'result'() requires that _@6 is of type atom() | tuple() not #{}

lib/wallaby/query/error_message.ex:171: The call _@11:'result'() requires that _@11 is of type atom() | tuple() not #{}

I try to solve it through more typespecs/structs over at benchee but that's just a guess.
@aaronrenner - any idea, you seem to know this stuff? :D

@PragTob I played around with the combination of Elixir 1.4.2 and Erlang 18.3 and I'm not having any luck either. Since the rest of the matrix passes, can we just exclude that combination?
I also just checked in some big build changes as a part of #198. What do you think about updating the Elixir and Erlang versions after that commit is merged?

If it makes your life easier, let's hold this merge until #198 is in to avoid merge conflicts on that big PR, they are easier to resolve over here :+1:
Regarding the exclusion, I might open an issue at elixir lang as it seems curious. I'll see if I can just skip the dialyzer part instead of the whole build

I would be really interested to hear the response if you open an issue at elixir lang too. Would you add a link to the issue here for posterity?

When I open the issue I link to both this here and my benchee PR :) I'll finish my work on a theory how to get it away on benchee and then hopefully get to it :)

^ Issue is there for the interested :) Yes, I'm bad at distilling it down to shorter titles.

I just claim that this is good to go now.


Clicking and dragging at boundary not deterministic

I'm having some very weird issues with nondeterministic behaviour when clicking and dragging at the boundary. Take a look at this video: https://youtu.be/3SKC4AJHXKk
Move 1 purple onto yellow, works ok
Move 2 purple off yellow, DOESN'T WORK
Move 3 purple onto yellow, works ok
Move 4 purple off yellow, works ok BUT WHY? SHOULD BE IDENTICAL TO MOVE 2
Moves 5, 6, 7, 8 work ok, all purple/red
Now to the bottom of the diagram
Move 9 red onto yellow, works ok
Move 10 red off yellow, DOESN'T WORK
Move 11 red onto yellow, works ok
Move 12 red off yellow, DOESN'T WORK (same as move 10)
Move 13 red onto yellow, works ok
Move 14 red off yellow, works ok BUT WHY? SHOULD BE IDENTICAL TO MOVES 10, 12
Move 15 yellow onto red, works ok
Move 15 yellow off red, DOESN'T WORK

Could it be an issue with the system not correctly detecting the drag at the "top" strand. (Doesn't explain the nondeterminism of course.)

filename_todo (14).zip
Here is the workspace.

I think that this is fixed now. It turns out it was deterministic, but the direction a homotopy was performed as the response to a horizontal drag was determined by checking if the drag was oriented upwards or downwards as makes sense for vertical drags.

Ahh right, I didn't think of that. So deterministic yet, but in a way which
was sensitive to the thermal entropy of my mouse as I attempt to move it
perfectly horizontally along the table :).
On Wed, Apr 21, 2021 at 7:11 PM Lukas Heidemann @.***>
wrote:

I think that this is fixed now. It turns out it was deterministic, but the
direction a homotopy was performed as the response to a horizontal drag was
determined by checking if the drag was oriented upwards or downwards as
makes sense for vertical drags.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/homotopy-io/homotopy-rs/issues/35#issuecomment-824258049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQ4OHXXQVLHGNWKWXZDP6LTJ4IMFANCNFSM43I5UIAQ
.

Unfortunately this issue still exists. Try creating a braid diagram and dragging a lower wire end left-and-slightly-up. It braids to the right.

9bfc110da4221ed4b99637b7c8144febcf8993f3 should have fixed this. The code that determines homotopies as well as attachments does deserve a proper cleanup though.


Handle large number of settlements better

In today's testing we had a lot of orders in the system which yielded at some point ~400 settlements. Currently the driver loop simulates all of them which can take a long time even when we do it in batches.
A better solution could be to order by objective value first and only simulate the first N (one batch) settlements. Only if all fail we continue to simulate.
Relevant logs are are from 2021-09-24 14:00 UTC staging solver mainnet. We can also try testing our system with a large amount of orders or rinkeby or xdai.

Should also look at the gas estimation for settlements because isn't that a simulation internally too? So we might be simulating twice.

Should also look at the gas estimation for settlements because isn't that a simulation internally too? So we might be simulating twice.

It is. AFAIK eth_estimateGas does something similar to an eth_call under the hood.

I assume most solution candidate came from the baseline solver. Maybe we should keep only the n most promising solution candidates from each solver?

I think as part of this task we should also create some more metrics around how many runloops we perform per minute (even under pressure, I'd hope our goal can be close to 2 full rounds incl. settlement). During the Kaffeekränzchen we saw some runloops take up to 5 minutes. It might also make sense to record the average time to settlement for orders more accurately ("settling takes too long" is the most prominent empirical feedback we have been getting)
Martin was suggesting, that if we refactor the codebase, maybe we can do it in a way that gets closer to the envisioned decentralized world. In that world, each solver would likely just report a single solution to the "driver" containing their best merged version with already computed objective value. The driver may the request concrete calldata for the best solution (or tell the solver to do execution themselves).
Such a refactoring may also lay the foundation for no longer asking for binding quotes from DexAggregators unless we are sure we will try to execute the quote (cf. #828).

Should also look at the gas estimation for settlements because isn't that a simulation internally too? So we might be simulating twice.

Yes, and we are not batching those requests. Therefore, in todays session, while simulation was fast (~2s), it then took another 20s to pick the winning solution based on the gas estimates.


Stack Overflow Bags Don't Always Work

Are you experiencing an issue with...
shields.io
🐞 Description
Stack Overflow Bags Don't Always Work
Stack Overflow badges, when mounted on shields.io, work well. When applying them to GitHub, they sometimes stop working.
This problem seems to me to have to do with the number of requests, but I'm not sure.
I believe that, for those who participate in more than one community, the problem is even worse because the number of requests tends to be higher.
🔗 Link to the badge
Here's a screenshot of the badges on my GitHub profile:

Here the badges (maybe they work, maybe not):

💡 Possible Solution
I don't know if the API that shield.io is using is the same one that StackExchange launched, but here it is:
https://api.stackexchange.com/docs/reputation-on-users#ids=7753089&filter=default&site=stackoverflow&run=true
The current version seems to me to be v2.3.

This is a duplicate of https://github.com/badges/shields/issues/5415
For some reason we sometimes get a 400 back from stackexchange but it doesn't reproduce locally. We've speculated in the past it might be a rate limit issue, but we really don't do much traffic on this badge - certainly not enough to hit the documented rate limit of 30 requests per sec per server documented in https://api.stackexchange.com/docs/throttle It is a bit of a mystery


Do not recreate mux router for each incoming request

(*App).context, called in the HTTP handler on each request, creates a
URLBuilder, which involves calling Router(). This shows up in profiles a
hot spot because it involves compiling the regexps which define all the
routes. For efficiency, cache the router and return the same object each
time.
It appears to be safe to reuse the router because GetRoute is the only
method ever called on the returned router object.

Codecov Report

Merging #3683 (853e2e9) into main (edf5aa3) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3683      +/-   ##
==========================================
+ Coverage   56.58%   56.59%   +0.01%
==========================================
  Files         103      103
  Lines        7520     7522       +2
==========================================
+ Hits         4255     4257       +2
  Misses       2596     2596
  Partials      669      669

Impacted Files
Coverage Δ

...istribution/distribution/registry/api/v2/routes.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

This also avoids a lot of memory allocations involved in compiling the regexps. I have this change deployed and saw an immediate improvement in allocation/GC metrics (as well as a reduction in CPU usage).


recipe/build.sh: fix typo in cross-build script

Typo fix for the cross-build script. See also conda-forge/librsvg-feedstock#77, conda-forge/pango-feedstock#45, conda-forge/gtk3-feedstock#39.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[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.

@pkgw I think the blocking broken package was gettext, and that has now been fixed. You can probably kick the pango and librsvg builds now.

@ryanvolz Looks like the Python 3.6 build still failed. Do you happen to know if it's just that the 3.6 builds aren't getting updated anymore? gettext isn't Python-specific though so it wouldn't be that package, I think.

It looks like the only python=3.6 that was built with libffi=3.4 for linux-ppc64le was marked as broken (by virtue of unlucky timing, the only Python version affected that doesn't have a more recent build) and hasn't been rebuilt. Perhaps an oversight, because @isuruf has already closed all the Python rebuild PRs?

Fixed now

Thanks Isuru!

Great, thanks!


python310Packages.aurorapy: 0.2.7 -> 0.2.6

Description of changes
https://gitlab.com/energievalsabbia/aurorapy/-/compare/0.2.5...0.2.7?from_project_id=4400392

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/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 177261 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.aurora_abb_powerone
python310Packages.aurorapy
python39Packages.aurorapy


fix: set Input border color for accessibility

Overview
Updated the border-color of the Form Input component to $color-red-700.
PR Checklist

[ ] Related to Abstract designs:
[X] Related to JIRA ticket: LX-3974
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

Description
While working on this ticket, accessibility errors arose on the homepage. In order to address these accessibility issues, the validation text color was changed to $color-red-700. Thus, the color of the input border has been updated to match the text color.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

(whoops, wrong button)
@sylvanasantos before merging, you'll want to make a PR to the monolith with the alpha version of @codecademy/gamut published here. This looks totally reasonable from a dev perspective but I'm a little wary of changes to atoms since they're used in a lot of places.

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.18-alpha.0f4644.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5edfae390cd3c270794849ca--codecademy-styleguide.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.18-alpha.16e109.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5ee019be2096b0707d57126c--codecademy-styleguide.netlify.appDeploy Logs


[10.x] Add php artisan migrate:redo command

A lot of developers (myself included) often have to rollback and re-run the newly-created migration because we had a last-second decision that we need to add another column, or change the column structure.
Such command would help us save the time to run php artisan migrate:rollback --step=1 and php artisan migrate.
It also accepts ``--step` parameter, which defaults to 1 but can be set to any number.

Why don't you use php artisan migrate:fresh?

@driesvints as far as i've seen from the code, it wipes the whole database, instead of rolling back and reapplying 1 migration:
$this->components->task('Dropping all tables', fn () => $this->callSilent('db:wipe', array_filter([
            '--database' => $database,
            '--drop-views' => $this->option('drop-views'),
            '--drop-types' => $this->option('drop-types'),
            '--force' => true,
        ])) == 0);

ah, my bad. It's actually php artisan migrate:refresh --step=1 that does the same thing. Sorry !


greater number

to find greatest among three number
Proposed Changes
Add a short description here

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

Checklist

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

A new file was not to be created for this. Plus, your new file is not even a .py file.


An option to run a specific section would be great

Hello
I searched the tutorial and reference section but could not find anything about this.
I would like to be able to run a single section - meaning execute all 'parent' sections and don't execute the child sections.
My usecase is, that I setup the test data and test different things on the same setup. Once a test fails I need to fix that test, but if all sections are executed it is cumbersome to use breakpoints as most have to be skipped until the section of interest.
If there is a better test setup, please tell me.
Thank you!

Maybe it could be possible to make one test/section explicitly to be executed. I've tried to do this with add a tag, but it looks like that tags are only sampled at the highes level?

Yes ist seems that Tags are only applied to TEST_CASE but not SECTION, Tags would be a great way to implement my Request.

I agree.
Should not the definition of a 'test' be any block from within which you enter the codebase you're testing? So if you can run main(), object.do() or whatever in a SECTION then so too should you be able to isolate execution of that test.
I would actually argue that without this TDD is, by principle, not possible.

This has been a long standing and common (and understandable) request.
There are some problems with it that mean there is no ideal solution, but the basic principle of "only go into sections that I have specified" is possible - and indeed I have now implemented this on a locally branch and am testing it out!
The mechanism is via a new command line option, --section or -c. Each time you use this you can follow it with a section name, so for nested sections use multiple options. This is not terribly convenient for writing by hand (at least not with long section names), but at least gets us the first step of making it possible (and it turns out to be really useful for machine consumption - i.e. by test runner tools).
It doesn't currently support wildcards or tags - but I'll look at adding those later.
I'll be pushing - probably to a branch to begin with - soon.

This has shown up many times over the time, so I am linking some duplicates I found: #110, #276

Do we have an ETA for the release of this feature?

@ruipacheco Partial support is in, see current release notes, or CLI documentation.

While more could be done, I believe the feature that is in (with -c) is sufficient to close this ticket now (reopen if you disagree).


Can not resolve symbol MvpQueuingBasePresenter

In my project/build.gradle:
allprojects {
    repositories {
        google()
        jcenter()
        maven { url "https://oss.sonatype.org/content/repositories/snapshots/"}
    }
}

in my app/build.gradle:
   implementation 'com.hannesdorfmann.mosby3:mvi:3.1.1-SNAPSHOT'
    implementation 'com.hannesdorfmann.mosby3:mvp:3.1.1-SNAPSHOT'
    implementation 'com.hannesdorfmann.mosby3:viewstate:3.1.1-SNAPSHOT'
    implementation 'com.hannesdorfmann.mosby3:mvp-lce:3.1.1-SNAPSHOT'
    implementation 'com.hannesdorfmann.mosby3:mvp-nullobject-presenter:3.1.1-SNAPSHOT'

My presenter:
public class OfferDetailsPdfPresenterImplMvp extends MvpBasePresenter<OfferDetailsPdfMvp.View> implements OfferDetailsPdfMvp.Presenter<OfferDetailsPdfMvp.View> {
}

But I get compile error: Can not resolve symbol MvpQueuingBasePresenter

Sorry, the Readme is not up-to-date. You have to add this dependency :
com.hannesdorfmann.mosby3:mvp-queuing-presenter:3.1.0
Btw. You better use 3.1.0 (not SNAPSHOT). Also there is no need to include mvi if you are just doing mvp.


Enhancement: a dedicated config for libraries

Should have skipLibCheck: false in that config.
But let's wait till https://github.com/microsoft/TypeScript/issues/29118 lands in TypeScript so that the configuration won't be too complex.

It has been implemented in https://github.com/microsoft/TypeScript/pull/50403 and been released with TypeScript 5 😄

tsconfig.lib.json added in v0.5.0.
As for the skipLibCheck: false configuration, now that https://github.com/vuejs/core/pull/9261 has been merged, we'll add it when 3.4 stable is out and this package drops support for 3.3.

🤔 I'm still thinking about this issue.
https://majors.nullvoxpopuli.com/q?minors=on&old=&packages=vue
There are still about 2/5 Vue 3.x users are on version <= 3.3 as of today.
Should I discontinue support for Vue 3.3 now or wait till the percentage drops to something like 1/5? I'm a bit torn.

It's officially less than 1/5 of all Vue 3 downloads now.
I think we should do it.


import math library

Hello,
I would like to know if it's possible to import the "math" library in Python to use it while writing scripts via GMSafir?
Indeed, simply using "import math" in the script doesn't work.
Thanks for your help.
Kévin FRANCAZ INGENI

"import math", which is required for gmsafir.py, normally comes with your default python install. If not present, you need to install it with your python: python -m pip install math

I can indeed use the library via Python using the command 'import math', which shows that the library is properly installed. However, my question is about being able to use these functions in the gmsafir script (Edit script). In this case, how should I write the commands?
For example, if I want to calculate a point using the math function:
Point(1) = {math.cos(math.pi), math.sin(math.pi), 0, 1.0};
it doesn't work

the langage used in the GEO file is not python, it is a simple native langage defined by the Gmsh developers. You can find the built-in functions of this langage here: https://gmsh.info/doc/texinfo/gmsh.html#Built_002din-functions
I don't see Pi, but probably Acos(-1) is ok

Hello,
Thank you for your feedback, it's working much better now....
Have a great day!


Is this real-time behavior recognition?

I hope you can reply to this question?
thnaks

I don't think so ! Beacuse the weight of the resnet-34 is already 400M that is difficult to achieve real-time.

I run a resnet-50 on the webcam and got 8 fps on a GTX 1660 Ti.


Docker installation not working

Q
A

Bug report?
[ ]

Feature request?
[ ]

Support request?
[ ]

@cocolabssas please i really need your help so i've been trying to install the docker version for cocorico
but its not rendering properly, please any help

Hello @EmmaTheGr8est
Could you describe more precisely your problem?


NO-JIRA Fix CEL rules in the CRD

Some CEL rules seems to be wrong, using double single-quotes instead of double quotes.
e.g.
rule: 'self.platform.type == ''Azure'' ? self.services.exists(s, s.service
  == ''APIServer'' && s.servicePublishingStrategy.type == ''Route''
  && s.servicePublishingStrategy.route.hostname != '''') : true'

This PR change this strings to use real double quotes:
rule: 'self.platform.type == "Azure" ? self.services.exists(s, s.service
  == "APIServer" && s.servicePublishingStrategy.type == "Route"
  && s.servicePublishingStrategy.route.hostname  != "") : true'

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retest

/retest

/approve


Plugin access to octokit

Hey, I'm writing a plugin and would like to know if there's anyway I can access the underlying Danger octokit client for my own api calls. Or if this is recommended.
Thanks!

Hi @wilrnh, you could do that, since the Dangerfile is just a normal ruby file.
require 'octokit' # not sure if this is necessary
Octokit::Client.new(access_token: ENV['DANGER_GITHUB_API_TOKEN'])

Yeah @jeroenvisser101 is correct, still not figured out a the right way to expose the environment to plugins yet.

cool. thanks guys.


Adjust GetBoundingRect() for Inclusive end

Summary of the Pull Request
GetBoundingRect() has inclusive endpoints. I previously assumed end was exclusive so I drew the bounding rect wrong.
This also means that we should allow start and end to be the same. Which means that FailFastIf would get hit...

In what instance will start==end but the range not be degenerate? I don't like this one bit.

The prerequisite for this function is start and end are both inclusive. So, start==end really means end = start + 1 (end being exclusive after this conversion). Thus making the range non-degenerate.
Thus, we can simplify the FailFastIf to be start > end or end < start

we need types for exclusive and inclusive points and stuff

@msftbot merge this in -1 minutes


Support custom configuration file from external URL

This patch supports environmental variable POSTGRESQL_CONFIG_FILE to set custom configuration file.
Example usage
$ docker run -d --name postgresql_database \
   -e POSTGRESQL_CONFIG_URL=https://gist.githubusercontent.com/nak3/67788d11d66460f7fc41ed52719df4b1/raw/1195bab962b1ed3556328b524628a5865491651b/postgresql-download.conf \
   -e POSTGRESQL_USER=user -e POSTGRESQL_PASSWORD=pass -e POSTGRESQL_DATABASE=db -p 5432:5432 centos/postgresql-94-centos7

This command starts postgres with config by downloading from external location.

Other info

The current image has some mechanisms to configurations like discussed bz#1326525#c2.

Set the config through environment vars for entries that have already been made configurable
Setup dockerbuilds within OpenShift to rebuild an additional layer with your config changes.  You can use an image change trigger to automate this.
Mount in config using a volume

However, the method introduced by this patch is more useful way.

@bparees @mfojtik what do you guys think?

@mnagy i don't love this idea :-) what if the external URL will be inaccessible (we will have container in restart loop?). Also have great potential to allow middle-man attacks without verifying the checksum or signing the configuration. The security guy in my head is screaming no :-)

I can see the value for dev/debug usage.  But @mfojtik's points are spot on...probably better would be to make the postgres image into an s2i builder that can pick up configuration as the "source", similar to what we do with jenkins.  (so you can either use it as is, or you can easily apply your own configuration on top of it via s2i).

The S2I idea is interesting... It means you will be able to install your own custom configuration or populate the database using assemble/run.

you wouldn't want to populate the DB using this mechanism, because then you're using the container storage for your DB which is a Bad Idea[tm].

@bparees i can seed the DB in the run script when the storage is attached. The script can check if the DB is seeded or not and I can have the initial dump stored in the repo with configuration.

@mfojtik fair enough.  though you are bloating image sizes.  and it doesn't help w/ schema migration (if anything it might make schema migration more confusing since the user might update their image w/ the new schema, but when the image starts up it mounts the PV from the old instance and so it ignores the image db content since the volume is seeded)

@bparees i think it depends on the application... take the baseball example marketing use... they just need to insert the stadium data when mongodb start up :-) if the data already exists (iow. there is PV, this will be no-op). I'm saying this is just an example of how the S2I scripts can be used, not saying is the best example everyone should follow :)

@mfojtik yeah, i'm just worried about people picking up on it as a pattern.  i agree there can be some use cases.  In fact back when we were first starting this i argued that the DB images should be s2i images for pretty much that reason:  you might want to define the DB schema as part of your assemble script.  (I didn't consider loading data, but that's a small extension)

@bparees trello: https://trello.com/c/knDOVefH/914-make-database-images-s2i-compatible

I also don't think downloading something from internet is not the best idea.
On the other hand, people still can bind-mount the some script or configuration
into container instead (into precisely defined place). That is done e.g. in
docker-library/postgres or fedora-cloud/Fedora-Dockerfiles/postgres

@praiskup in openshift/kubernetes they can't unless they use ConfigMap which will take over the configuration directory entirely and there are no 'good tools' to manage them.
Also from the operations point of view, the Docker containers should contain (that also include configuration for the application/service that the given image provide), so having to bind-mount directory with custom configuration might defeat the purpose of having docker image contain (and allow users to get the same behavior without sharing the piece of configuration separately)....

Suppose I wanted to create an image that downloads the config from the net
anyway. How hard would it be if we made postgres into an s2i image?
On Tue, Apr 26, 2016, 16:01 Michal Fojtik<EMAIL_ADDRESS>wrote:

@praiskup https://github.com/praiskup in openshift/kubernetes they
can't unless they use ConfigMap which will take over the configuration
directory entirely and there are no 'good tools' to manage them.
Also from the operations point of view, the Docker containers should
contain (that also include configuration for the application/service that
the given image provide), so having to bind-mount directory with custom
configuration might defeat the purpose of having docker image contain (and
allow users to get the same behavior without sharing the piece of
configuration separately)....
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/openshift/postgresql/pull/106#issuecomment-214755008

if we made it an s2i image you could write a custom/override run script to pull config down from the internet when the image starts, if you really wanted to.

@bparees after some thinking it might make sense, but not from internet but from some local internal service which distribute configuration files... still possible to use run script for that.

Thank you for the discussion all. I agree so please feel free to close this request.

@nak3 I think you'll be able to fetch the configuration in the "run" script once we make the database images S2I compatible, but I don't know when that happen.

Oh, I hope it will be very soon ;) since all of current methods are pains in the neck for my testing...


Make TEXT columns filterable and groupable

Fix #34.
fetch_metadata already makes string columns filterable and groupable, but TEXT was not included as a string type.
We might want to PR this to upstream also.

Hm. TEXT type is meant to be huge text that doesn't make much sense to group of filter by user.
I mean maybe it's okay to fix as proposed right now. But better fix would be to return correct types from gitbase. Then for example repository name would be checked automatically but commit message not.

Here is the issue for gitbase: https://github.com/src-d/gitbase/issues/824
It doesn't look like this issue is very critical. I would better wait for fix in gitbase than hacking superset.


Does pyOCD have a mailing list?

I'd like to contribute, but I couldn't find any documentation on the matter. Is there any mailing list or groups that I could subscribe to to stay updated on discussions of pyOCD development?

We have mbed-devel mailing list where you could find some old discussions, but mostly just notifications from github.
Github might be the best place for this. The discussions are mostly here, in pull requests or issues.


Crash when highlighting text in console input box

Highlighting text in the console input box and then navigating through input history with the up/down keys leads to an inconsistent selection state and crashes.
To reproduce:

Type "a long line here" and press enter.
Type "line2" and press enter.
Press the up arrow twice to go back to "a long line here".
Select all with ctrl+A.
Press the down arrow to go to "line2". Notice that the selection does not reset.
Try typing any character and the game should crash.

This should be fixed in my PR.
Sombra reported this earlier this week on our Discord.

Is now fixed in master, will be included in next release.


feat(.cspell.json):  add words

I want to add these words.
words

word
definition

bbox
abbreviation of bounding box. example: https://github.com/tianweiy/CenterPoint/tree/master/det3d/core/bbox

bboxes
the plural form of bbox

PointPillars
3D detection model proposed in CVPR 2019

@Shin-kyoto Could you consider adding word-by-word so that we can judge faster? :bow:
Using https://github.com/tier4/autoware-spell-check-dict/actions/workflows/add-word.yaml would be your help.

@Shin-kyoto Could you consider adding word-by-word so that we can judge faster? bow Using https://github.com/tier4/autoware-spell-check-dict/actions/workflows/add-word.yaml would be your help.

Thank you for telling me that!
So I'll add words by workflow.

Close this PR because I'll add words by workflow.


Project Setup

Brief description:
This feature is used to test if a project can be created, deleted and the different project settings.
User spec:
https://github.com/CCTC-team/redcap_cypress/blob/redcap_val/user_requirement_specification/core/04_project_setup.spec
Feature link:
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.300 - REDUNDANT Edit Survey Responses.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.800 - Project Title.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.1000 - Project Copy.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in Development Mode.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.1200 - Delete Project.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.1300 - Enable %26 Disable Survey.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/B/Project Setup/B.6.4.1400 - Repeating Surveys.feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.1500 - Manage Survey User..feature
https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature
Pre review:

[x] Script(s) targets the correct feature sufficiently
[x] The user requirements are met

Post review:

[ ] Script(s) targets the correct feature sufficiently
[ ] Script(s) appropriately tests the feature

Script Pre-reviewed:

A.6.4.100 - User Create Projects

All tests pass except
A.6.4.600 - Events and Arms in Production - Test not passing.

A.6.4.400 - Draft Mode
Added steps to verify draft mode actions are reflected in the instrument (from PQ)


Add Language Info endpoint

Move queue endpoint

This change is

Codecov Report
Attention: 102 lines in your changes are missing coverage. Please review.

Comparison is base (04f977f) 70.95% compared to head (027027a) 70.58%.

Files
Patch %
Lines

src/Serval.Client/Client.g.cs
52.70%
71 Missing and 25 partials :warning:

...l.Translation/Controllers/TranslationController.cs
80.00%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #283      +/-   ##
==========================================
- Coverage   70.95%   70.58%   -0.38%
==========================================
  Files         138      141       +3
  Lines        6135     6319     +184
  Branches      981     1011      +30
==========================================
+ Hits         4353     4460     +107
- Misses       1335     1395      +60
- Partials      447      464      +17

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

src/Serval.Translation/Controllers/TranslationEnginesController.cs line 1051 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
Is the goal to ultimately reimplement something very much akin to this but that allows you to specify which queue? Or am I misunderstanding? Is it just that you want to be able to specify the queue on creation? I thought one of the rationales was that this could be used to probe queue loads before adding jobs (which just specifying a queue in buildOptions wouldn't allow you to do. If the plan is to rebuild this slightly differently, then I wonder if it's worth just doing that now in the same PR since the code will be relatively similar and not take much effort. If not, we should probably remove the corresponding code on the Machine side (?).

Oh, I see - nevermind!

src/Serval.Translation/Controllers/TranslationController.cs line 63 at r1 (raw file):

    [ProducesResponseType(typeof(void), StatusCodes.Status503ServiceUnavailable)]
    public async Task<ActionResult<LanguageInfoDto>> GetLanguageInfoAsync(
        [NotNull] string engineType,

Same as with queueDepth above. See this message from Damien on this topic during the initial queue depth PR: https://github.com/sillsdev/serval/pull/177#pullrequestreview-1674873160. This is why it inadvertently ended up being a POST request.

samples/EchoTranslationEngine/TranslationEngineServiceV1.cs line 303 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
Given that the Echo engine in general just spits back whatever you give in, would it be worth doing something more akin to that here. I get that it's a bit harder to echo this information since it needs to undergo transformation. If we do keep it this way, we should at least make sure this is documented since this is meant to be used for testing and someone might expect that the response language code, for example, is just the input (?).

Agreed - that makes more sense.

src/Serval.Translation/Controllers/TranslationController.cs line 63 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
Same as with queueDepth above. See this message from Damien on this topic during the initial queue depth PR: https://github.com/sillsdev/serval/pull/177#pullrequestreview-1674873160. This is why it inadvertently ended up being a POST request.

Can you copy the comment from that review here?  I don't know which one you are referring to.

This also resolves https://github.com/sillsdev/serval/issues/281.

src/Serval.Translation/Controllers/TranslationEnginesController.cs line 1051 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
I do still wonder if it's worth adding in that queue-specification in this PR if that is the ultimate intent.

I added the reference to https://github.com/sillsdev/serval/issues/281 above.

tests/Serval.ApiServer.IntegrationTests/TranslationEngineTests.cs line 1424 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
Why make a new client creation method instead of extending the previous one?

Am I able to?  The queue and the language info are now in a separate file TranslationController.cs because we needed a different endpoint.  I can merge the two files into one file called TranslationController.cs and redo all the "engines" endpoints - what do you  think is best?

src/Serval.Translation/Controllers/TranslationController.cs line 63 at r1 (raw file):
Previously, johnml1135 (John Lambert) wrote…
Can you copy the comment from that review here?  I don't know which one you are referring to.

URLs are often treated as case insensitive. In this case, just the engine type part of the URL will be case sensitive. Unfortunately, we never expected to use the engine types in a URL, so they can't easily be converted to Pascal case. We have a couple of options:

Change the engine type values to kebab case on all endpoints (breaking change). We convert to Pascal case for internal use or switch to using kebab case everywhere.
Change the engine type values to kebab case only on this endpoint. We convert to Pascal case for internal use.
Pass the engine type in the body or query string.
Require that engine types are case insensitive everywhere.

src/Serval.Translation/Controllers/TranslationController.cs line 63 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
URLs are often treated as case insensitive. In this case, just the engine type part of the URL will be case sensitive. Unfortunately, we never expected to use the engine types in a URL, so they can't easily be converted to Pascal case. We have a couple of options:

Change the engine type values to kebab case on all endpoints (breaking change). We convert to Pascal case for internal use or switch to using kebab case everywhere.
Change the engine type values to kebab case only on this endpoint. We convert to Pascal case for internal use.
Pass the engine type in the body or query string.
Require that engine types are case insensitive everywhere.

@ddaspit - what do you think?  I am inclined to do the case insensitive route...

src/Serval.Grpc/Protos/serval/translation/v1/engine.proto line 85 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
This should be named language to be consistent with the rest of the API.

Replaced in all locations in serval and machine.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 5 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I think I would prefer a different name. I don't think "resolved" is very clear in this context. Maybe something like InternalCode.

ISOLanguage?  ISO639_3Language?  InternationalLanguage?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 6 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
To be consistent with the rest of the API, you should use IsSupported.

All languages are supported - how about IsSupportedNatively?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 7 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I'm not sure what "common" means in this context. I think simply Name should be sufficient.

English, etc.  They are from the table here: https://github.com/facebookresearch/flores/blob/main/flores200/README.md

src/Serval.Translation/Controllers/TranslationController.cs line 6 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
This should be a translation engine types controller. The route would be api/v{version:apiVersion}/translation/engine-types.

Changed and file renamed.

src/Serval.Translation/Controllers/TranslationController.cs line 57 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I would rename the route to languages.

All "codes" renamed.

src/Serval.Translation/Controllers/TranslationController.cs line 64 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
This should be simply language.

done

tests/Serval.ApiServer.IntegrationTests/TranslationEngineTests.cs line 1424 at r1 (raw file):
Previously, johnml1135 (John Lambert) wrote…
Am I able to?  The queue and the language info are now in a separate file TranslationController.cs because we needed a different endpoint.  I can merge the two files into one file called TranslationController.cs and redo all the "engines" endpoints - what do you  think is best?

I see. No, I think your refactor makes sense.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 6 at r2 (raw file):
Previously, johnml1135 (John Lambert) wrote…
All languages are supported - how about IsSupportedNatively?

Where is IsSupported used elsewhere in the API? And to be clear, this flag just tells the user whether the language is one of NLLB's 200, right? That's what this means?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 6 at r2 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
Where is IsSupported used elsewhere in the API? And to be clear, this flag just tells the user whether the language is one of NLLB's 200, right? That's what this means?

Yes, it says if the language is in the NLLB200, and when MADLAD is supported, it will tell if it is in that model natively.  This can be used for determining if a language is supported for source text or if you can do direct inferencing on it.

tests/Serval.ApiServer.IntegrationTests/TranslationEngineTests.cs line 1424 at r1 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
I see. No, I think your refactor makes sense.

I will keep the refactor then and rename the file to TranslationEngineTypesController.cs (as per Damien's comment).

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 5 at r2 (raw file):
Previously, johnml1135 (John Lambert) wrote…
ISOLanguage?  ISO639_3Language?  InternationalLanguage?

ISOLanguageCode?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 6 at r2 (raw file):
Previously, Enkidu93 (Eli C. Lowry) wrote…
OK, yes, makes sense. I don't see an issue with something like IsSupportedNatively or IsSupportedByModel. If Damien just meant by IsSupported that you should give it a name with 'Is' in its name, then cool, but I do think just IsSupported might be confusing since we can support languages for which this is false in a sense - the model just doesn't have native support without fine-tuning. We can clarify in the docs of course, but it would be nice to have that meaning encoded in the name.

Done.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 5 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
ISOLanguageCode isn't really appropriate either. This refers to the token that is used by model to represent a language. For example, in the MADLAD-400 model the English token would be <2en>.

I'll switch to InternalCode.

@ddaspit I see you re-requested my review; was there something in particular you had in mind for me to look at?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 5 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I would also make this optional, since there might be engines where this is irrelevant.

Hmm - then the entire endpoint would be meaningless?  Would Smt engines have native support?

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 6 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
Yes, I was referring to the convention Is<name> for boolean variables. I would just go with IsNative. It conveys the same meaning, and it is better to be concise, especially in DTOs.

IsNative.  I like it.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 7 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I would make this optional.

Can I update to dotnet standard 2.1?  I want nullable types..

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 7 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
What do you want to update to .NET Standard 2.1? This assembly is a .NET 8 DLL, so it already supports nullable types.

I think I need to update the language support to "latest" and add "nullable" - https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/configure-language-version.  I don't need 2.1 - I was wrong.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 7 at r2 (raw file):
Previously, johnml1135 (John Lambert) wrote…
I think I need to update the language support to "latest" and add "nullable" - https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/configure-language-version.  I don't need 2.1 - I was wrong.

If we update to C# latest, we get 400+ warnings about nullable types.  What should we do?  Let's have a short meeting tomorrow.

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 5 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
The main use case for the endpoint is the IsNative property. The InternalCode is only relevant for pretrained multilingual NMT models. For SMT, I guess everything is native.

How about make IsNative an enum? IsNative: True|False|N/A

src/Serval.Translation/Contracts/TranslationInfoDto.cs line 7 at r2 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I'm confused. This is already a .NET 8 project, so the default C# language version is 12, which supports nullable types.

It's .NET 7.3 - I can show you what I am seeing.

src/Serval.Translation/Controllers/TranslationEngineTypesController.cs line 64 at r5 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
This should be language like everything else.

Done.

src/Serval.Translation/Controllers/TranslationEngineTypesController.cs line 57 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
The FLORES-200 codes are not ISO 639-3 codes. They are a combination of ISO 639-3 codes and ISO 15924 codes. They do not conform to any particular standard. Also, this is only applicable to the NMT engine type using NLLB.

Updated comment.

src/Serval.Translation/Models/Engine.cs line 14 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
It is not the responsibility of models to convert to pascal case. Models typically do not contain any logic. The controller is responsible for interpreting the inputs and mapping them to models that the application/service layer can understand.

I'll fix all.

src/Serval.Translation/Models/Engine.cs line 29 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
Use the CaseExtensions library to perform the conversion.

Done - nice find.

src/Serval.Translation/Models/LanguageInfo.cs line 9 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
It is not the responsibility of models to convert to pascal case. Models typically do not contain any logic. The controller is responsible for interpreting the inputs and mapping them to models that the application/service layer can understand.

Will fix all.

src/Serval.Translation/Models/Queue.cs line 7 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
It is not the responsibility of models to convert to pascal case. Models typically do not contain any logic. The controller is responsible for interpreting the inputs and mapping them to models that the application/service layer can understand.

Will fix all.

src/Serval.Translation/Models/LanguageInfo.cs line 9 at r6 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
I think you accidentally turned this into a field instead of a property.

GAAAAAAAHHHHH!  C# has so many subtle things that have big impacts!  Fixed.

src/Serval.Translation/Models/LanguageInfo.cs line 8 at r7 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
Is there an actual requirement for the language name from Scripture Forge? If not, we should just remove it. We don't need it and it will only make it more difficult to implement this in future engines.

Hmm.  I see what you mean.  I will kill it at the API level but keep the guts of it there.  If we do want it in the future it will be easy to add.  We can also grab data from the ethnologue or similar if needed.

tests/Serval.Translation.Tests/Services/EngineModelTests.cs line  at r7 (raw file):
Previously, ddaspit (Damien Daspit) wrote…
We don't need to unit test a library. You can delete this test fixture.

Your right - I forgot that I didn't need this anymore.


Implement lazy loading on components

Is your feature request related to a problem? Please describe.
GE page load time is a bit high for it's size. To reduce this, we can lazily load components that users don't see at first glance.
We can lazy load: Resources, History tab, Modify Permissions, Access tokens, Request headers, Response headers, Code snippets, Toolkit component and Adaptive cards tabs.
Describe the solution you'd like
Graph explorer that loads faster
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@Onokaev  what's the current page load avg time? And with this change, what's our projected page load time?

Our current average is 12-15 seconds according to the load time stats. We can slash this to 5-7 seconds.


[Bug]: Modifying settings.yml trough env variables in docker-compose not working

Installation Method
Docker ultra lite
The Problem
Hi, first thank you really much for your work, your project just drop out of the sky just in time we needed it haha
I'm writting you about modifying the settings of the app in the settings.yml file.
According to the documentation, to set the csrfDisabled parameter to false, I just need to put the line :
- SECURITY_CSRFDISABLED=false
in the environement part of my docker-compose.yml file, but every time the container build itself, this parameter is not taken in consideration and I need to modify manually this parameter in the settings.yml file.
Is there a special way to do so or maybe the name of the env variable for this parameter is not the good one ?
Wishing you a great day !
Version of Stirling-PDF
latest-ultra-lite
Last Working Version of Stirling-PDF
No response
Page Where the Problem Occurred
No response
Docker Configuration
services:
  stirling-pdf:
    restart: always
    image: frooodle/s-pdf:latest-ultra-lite
    ports:
      - '8080:8080'
    volumes:
      - ./trainingData:/usr/share/tessdata #Required for extra OCR languages
      - ./extraConfigs:/configs
      - ./customFiles:/customFiles/
      - ./logs:/logs/
    environment:
      - DOCKER_ENABLE_SECURITY=false
      - SECURITY_ENABLELOGIN=false
      - SECURITY_CSRFDISABLED=false
      - INSTALL_BOOK_AND_ADVANCED_HTML_OPS=false
      - LANGS=fr_FR
      - ALLOW_GOOGLE_VISIBILITY=false
      - APP_LOCALE=fr_FR
      - UI_APP_NAVBAR_NAME=navbar
      - SYSTEM_DEFAULTLOCALE=fr-FR
      - ENDPOINTS_TO_REMOVE=markdown-to-pdf,url-to-pdf

Relevant Log Output
No response
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

Seems there is a bug with the csrf disabling parameter specifically, will be fixed next release

to fix your trouble check this solution click
maybe this will solve your problem.


Get the version of dependency

Test with NPOI 2.1.3 https://www.nuget.org/packages/NPOI/2.1.3
The NPOI.OpenXml4Net.dll depend on ICSharpCode.SharpZipLib.dll with specific version <IP_ADDRESS>8.

If I replace the ICSharpCode.SharpZipLib with an old version, I will got an exception.
NPOI.POIXMLException ---> System.IO.FileNotFoundException: Could not load file or assembly 'ICSharpCode.SharpZipLib, Version=, Culture=neutral, PublicKeyToken=1b03e6acf1164f73' or one of its dependencies. The system cannot find the file specified.
Is it possible for you to detect the version of dependencies?

The assembly explorer belongs to https://www.jetbrains.com/help/resharper/Navigation_and_Search__Navigate_from_Here__Assembly_Explorer.html

I can get the assembly version from AssemblyName.FullName
 public void AssemblyTest()
        {
            string path = @"";
            DirectoryInfo directoryInfo=new DirectoryInfo(path);
            var pattern = "*.dll";
            var files = directoryInfo.GetFiles(pattern);
            var str1 = "ICSharpCode.SharpZipLib";

            int i = 0;
            foreach (var file in files)
            {
                AssemblyName assemblyName = AssemblyName.GetAssemblyName(file.FullName);
                var assembly = Assembly.Load(assemblyName);
                var dependencies = assembly.GetReferencedAssemblies();
                var filter1 = dependencies.Where(x => x.Name.Equals(str1)).ToList();
                if (filter1.Count > 0)
                {
                    i++;
                    Console.WriteLine(i);
                    Console.WriteLine(assembly.GetName());
                    foreach (var filter in filter1)
                    {
                        Console.WriteLine($"{filter.FullName}");
                        Console.WriteLine();
                    }
                }
            }
        }


test: add gamut-illustrations to test/styleguide alias configs

Overview

Adds gamut-illustrations to the test/styleguide alias configs

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6033cab76df84d49b2df81bd--gamut-preview.netlify.appDeploy Logs


Rename ALPHA into a more meaningful name

As discussed here we can use base_prediction or base_score or inital_prediction.

I am going to rename ALPHA with base_prediction.


Automated cherry pick of #3381: .circleci: yunionio/onecloud-ci: bump golang version to 1.13.3

Cherry pick of #3381 on release/2.11.
#3381: .circleci: yunionio/onecloud-ci: bump golang version to 1.13.3

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@f9ede8b). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #3383   +/-   ##
==============================================
  Coverage                ?   7.13%
==============================================
  Files                   ?     476
  Lines                   ?   77272
  Branches                ?       0
==============================================
  Hits                    ?    5514
  Misses                  ?   71294
  Partials                ?     464

Flag
Coverage Δ

#aFlag
7.13% <ø> (?)

Impacted Files
Coverage Δ

pkg/baremetal/utils/disktool/disktool.go
0% <ø> (ø)

pkg/appsrv/fetch.go
0% <ø> (ø)

pkg/multicloud/aws/loadbalancerbackendgroup.go
0% <ø> (ø)

pkg/compute/models/dbinstancejoints.go
0% <ø> (ø)

pkg/compute/models/dbinstance_databases.go
10% <ø> (ø)

pkg/util/s3auth/v4.go
82.99% <ø> (ø)

pkg/compute/models/snapshotpolicy.go
2.33% <ø> (ø)

pkg/multicloud/aws/loadbalancer.go
0% <ø> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0% <ø> (ø)

pkg/util/s3auth/interface.go
24.56% <ø> (ø)

... and 51 more

Continue to review full report at Codecov.

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

/lgtm

/approve


feat: new api order most_active. Rename popularity to hight rated

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

54 of 71 (76.06%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-23.7%) to 48.08%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/modules/hotScenes.ts
7
8
87.5%

src/entities/Place/routes/getPlaceMostActiveList.ts
26
29
89.66%

src/entities/Place/model.ts
1
14
7.14%

Totals

Change from base Build<PHONE_NUMBER>:
-23.7%

Covered Lines:
185

Relevant Lines:
268

💛  - Coveralls


Provide a way to make yum clean REPO_NAME optional

We're testing a bunch of cookbooks using kitchen and vagrant-cachier to cache yum, apt, rubygems and a few other packages.
However the yum clean operation that got added in version 3.6 is a bit of an inconvenience because it blows away all yum caches.
I'm happy to submit a PR to make that behaviour optional by specifying a yum_clean (?) parameter that defaults to true, but can be turned off if desired.
Thoughts?
/cc @someara (the original author who added that line of code)

either disable it by default, or make it optional with yum clean headers being used instead of yum clean all

feature added in abe430dd806bfc3df250a868526c186aa2326922

released in 3.8.0

Thanks a bunch


  Instead of using Windows Folder Auditing and the event log, it instead uses the NTFS Change Journal.  Currently it uses FSUTIL to query the journal, and parses the output into a list of dictionaries.  The it filters out what we don't need / want to see

Looks like this is conflicting, probably due to the pep8 changes that were made recently. Resolving the merge conflict is probably going to be a nightmare, so instead I recommend you copy the new win_pulsar.py out of your git repo to somewhere else, then do the git pull, and to resolve the conflicts you just copy your external copy back in and commit. That should resolve everything so we can merge.


Missing LICENSE prevents distribution

Hi,
I recently discovered that I could not distribute the product I'm working on, which uses Redis, because the project's LICENSE file is missing.
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license
Can anyone please add a LICENSE file to the repository?
Thanks

Good point! I wasn’t aware of this limitation regarding the missing LICENSE file. Was this an intentional decision for the repository, or might it have been overlooked?

Please take a look at this @shubham-cmyk @iamabhishek-dubey

@shubham-cmyk @iamabhishek-dubey Could you please share your perspective? As far as I can tell, this prevents anyone from using the Redis operator with these images. Instead, it seems one would need to build their own Redis images. Is that correct?


Make Various Levels

Being able to switch between levels is completed (thanks to Gavin Copley)

I did this by making it so that when you move a variable increases. When that variable is greater than another number you get switched into a new script with the second level. This way we can add an infinite amount of levels with enough time.


Added new FirstPromoter Integration

FirstPromoter allows a site to build a referral program and ask other members to promote your work to other people. Currently, to integrate FirstPromoter on a site, it needs steps from the guide here.
The new native integration with FirstPromoter makes it easy for as site to enable FirstPromoter referral program on their site, by only needing to add their FirstPromoter Tracking ID and enabling it

[x] Adds new FirstPromoter settings
[x] Update tests

@tpatel

it's prohibited to add new objects to the settings table.

That basically refers to the type of Setting value, which shouldn't be a JSON object anymore as we moved away from JSON stringified objects assigned to setting keys. This issue is a good reference when we undertook the Setting table cleanup and covers this :)

If it's something new I guess it's generally good to not update "frozen" apis

Yeah so settings getting new value has been the exception so far, afair primarily because the whole default-settings setup where we end up adding all new settings on Ghost startup and then the v2 API is setup to just pick and send all settings by default instead of having a proper include-list. Ghost Admin always explicitly asks for settings by group so new settings are not added in its response.

@tpatel

it's prohibited to add new objects to the settings table.

That basically refers to the type of Setting value, which shouldn't be a JSON object anymore as we moved away from JSON stringified objects assigned to setting keys. This issue is a good reference when we undertook the Setting table cleanup and covers this :)

If it's something new I guess it's generally good to not update "frozen" apis

Yeah so settings getting new value has been the exception so far, afair primarily because the whole default-settings setup where we end up adding all new settings on Ghost startup and then the v2 API is setup to just pick and send all settings by default instead of having a proper include-list. Ghost Admin always explicitly asks for settings by group so new settings are not added in its response.


jxlinfo: avoiding div by zero for blending

For blending frames, this triggers undefined behavior, because info.animation.tps_numerator is zero. We avoid that by not computing it for non-animation frames


implement low-diff shares counting (#2718 #2726)

Since it's the development branch I think we should merge this without incrementing to DB version 1.0.4 - Those who have to run the upgrade can do it manually again (re-set DB version to 1.0.2 and then run the script) or run the ALTER TABLE themselves.


Fix serveral recent new clang-format errors

There are more files that don't comply with clang format from 1eeda0f.

Thanks @Noshyaar added them to this commit

eedb390 introduces some more. :P

@Noshyaar added too


Whatever page?

Is possible to make installable whatever web app or only the webs that are in a catalogue?... for example a web app that I can create for myself

@jorgegarmilla Now, it's not possible but the feature has been planned. #12


Disable inline styles inside link

[x] add inLink function
[x] add unit tests to ensure transformation is not applied when current entity is link

fixes #14
fixes #31

Conflicts!

@mxstbr solved

🎉🎉

@Rosey ayoooo ❤


Map/dungeon desync between players

I have been experiencing on server an issue where 2 players will enter the same dungeon and basically load 2 different versions of it. I have personally experienced this on another server with my wife. the only common mod between the two packs that appears to touch mountain biome is jtv biomes, so i am beginning my investigation here. is there any possibility that JTV_B could cause this sort of occurrence?

While I don't know how that would be possible, it's certainly not impossible. I know that Forgotten Biomes messed up the Mountain caves on my server, but I looked at the code and didn't see anything that would have affected them.
All of the changes I make to the Mountains are right here:
https://github.com/thedefside/valheim-mods/blob/440458c93ee6be2fd1eac95eedae1fea86e8355f/jtv-biomes/JtvBiomes.cs#L111
It's just 2 lines that add a new location to the Zone Manager. You could try turning off the Mountains Locations in the config and see if that helps.

Ah sorry, I forgot I had posted this here.
I have determined that the issue was in fact caused by players who cloud save and players who legacy save mingling in the same locations.
The issue evaporated the moment they synced up their settings for character saves

Ah sorry, I forgot I had posted this here. I have determined that the issue was in fact caused by players who cloud save and players who legacy save mingling in the same locations. The issue evaporated the moment they synced up their settings for character saves

Ah, thanks for letting me know 👍


Add new reference to the Prompt2Model readme

Description
Adding a new paper to the Prompt2Model references to cite.
References
N/A
Blocked by
N/A

@neubig done!

Looks good, I approve but linting is failing!


Build(deps): Bump dotenv-webpack from 7.0.3 to 7.1.0 (#2560)

Pull request opened by the merge tool on behalf of #2560

Merged in 6c63518a644ccf1c916e2b93a1469bb5b0fd1491


Add tests support for CronJob

This is a feature request to add support for testing the CronJob resources just like existing Job resources.

So, what is the status of this one? I see that pr was opened some time ago and looks good (not sure about api version of cronjob, since 1.25 EoL is in 1 week). Will it be merged, or should I implement my custom helpers to work with cronjobs (need to test cronjob helm chart)


Jib 3.4.2 build fails

Environment:

Jib version: 3.4.2
Build tool: Gradle 8.7
OS: macos

When I run
./gradlew jibDockerBuild

It fails with
Caused by: java.lang.NoSuchMethodError: 'void org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.tar.TarArchiveEntry)'
        at com.google.cloud.tools.jib.tar.TarStreamBuilder.writeAsTarArchiveTo(TarStreamBuilder.java:52)
        at com.google.cloud.tools.jib.image.ImageTarball.dockerWriteTo(ImageTarball.java:166)
        at com.google.cloud.tools.jib.image.ImageTarball.writeTo(ImageTarball.java:84)
        at com.google.cloud.tools.jib.docker.CliDockerClient.load(CliDockerClient.java:195)

Workaround. It works when I set this in both root and gradle submodule build.gradle.kts
buildscript {
    dependencies {
        classpath("commons-codec:commons-codec:1.16.1")
    }
    configurations.all {
        resolutionStrategy {
            force("org.apache.commons:commons-compress:1.26.0")
            force("commons-codec:commons-codec:1.16.1")
        }
    }
}

Please make it work w/o workarounds

Facing the same issue also! I hope that will be fixed soon

Hey @artemptushkin, thanks for filing the issue and appreciate you sharing the workaround! As we try to learn more, would it be possible to see how your project's dependency tree looks without the explicit inclusion of org.apache.commons:commons-compress:1.26.0? Particularly curious if the dependency is being transitively brought in from another place.

Are there any updates?

We have the same issue in the jib-gradle-plugin. A gradlew buildEnvironment shows org.apache.commons:commons-compress:1.26.0 is requested by jib-gradle-plugin itself:
\--- com.google.cloud.tools:jib-gradle-plugin:3.4.2
     +--- com.google.http-client:google-http-client:1.42.2
     |    ...
     +--- com.google.http-client:google-http-client-apache-v2:1.42.2
     |    ...
     +--- com.google.auth:google-auth-library-oauth2-http:1.10.0
     |    ...
     +--- org.apache.commons:commons-compress:1.26.0

Other transitive dependencies request 1.21 but Gradle resolves the conflict with the newer version requested by jib-gradle-plugin. But the stacktrace shows it is the jib-gradle-plugin itself which breaks on this dependency, as can be seen in the first post.

@adenhartog thanks for the trace
My
|         |    +--- org.apache.commons:commons-compress:1.21

comes from
+--- org.springframework.boot:org.springframework.boot.gradle.plugin:**3.2.4**

Though no "commons-codec" in the trace for ./gradlew buildEnvironment

For comparison, we also have the spring-boot-gradle plugin but in our project. It requests 1.21 but gradle resolves it to 1.26.0 in our project:
          |    \--- org.springframework.boot:spring-boot-gradle-plugin:3.2.4
          |         +--- org.springframework.boot:spring-boot-buildpack-platform:3.2.4
          |         |    ...
          |         |    +--- org.apache.commons:commons-compress:1.21 -> 1.26.0 (*)

Other transitive dependencies request 1.21 but Gradle resolves the conflict with the newer version requested by jib-gradle-plugin.

For comparison, we also have the spring-boot-gradle plugin but in our project. It requests 1.21 but gradle resolves it to 1.26.0 in our project:

If your project is a multi-module one, then it's pretty common that ./gradlew buildEnvironment lies about how it resolved dependencies; it's a long-standing Gradle bug where dependencies declared in the parent project shamelessly and silently overrides dependencies of sub-projects, as opposed to what you see from ./gradlew buildEnv.
So, if you haven't done so, I recommend first that you should strictly follow these instructions for setting up your multi-module project. That is, declare all your plugins in the project root while not applying it and then selective apply plugins in sub-projects.

Sorry, I've fixed a wrong link above.

Here is a non multi-module project buildEnvironment (also spring-boot but not using the spring-boot gradle plugin), our compress comes from Jib and it also broke our jibBuildTar step after 3.4.2
+--- com.google.cloud.tools.jib:com.google.cloud.tools.jib.gradle.plugin:3.4.2
|    \--- com.google.cloud.tools:jib-gradle-plugin:3.4.2
|         +--- org.apache.commons:commons-compress:1.26.0

This is on Gradle (wrapper) 8.6, Java 21, and Linux (Fedora 38, but also failing in GitHub CI on ubuntu-latest).
It seems to be the same issue as reported above:
> Task :jibBuildTar FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jibBuildTar'.
> com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException: 'void org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.tar.TarArchiveEntry)'

Another thing, I saw the workaround is to enforce commons-codec version 1.16, in our project is at version 1.11 currently, which is also pulled in by jib
+--- com.google.cloud.tools.jib:com.google.cloud.tools.jib.gradle.plugin:3.4.2
|    \--- com.google.cloud.tools:jib-gradle-plugin:3.4.2
|         +--- com.google.http-client:google-http-client:1.42.2
|         |    +--- org.apache.httpcomponents:httpclient:4.5.13
|         |    |    +--- org.apache.httpcomponents:httpcore:4.4.13 -> 4.4.15
|         |    |    +--- commons-logging:commons-logging:1.2
|         |    |    \--- commons-codec:commons-codec:1.11

@chanseokoh Aligning the versions in de root project plugins block fixes the problem in our multi-module project. Good to know about this obscure Gradle issue/bug, thanks!

@adenhartog glad it fixed your project.
@mihalyr-prospect I think it must be that for one reason or another, your project is set up to "downgrade" the Apache commons compress 1.26.0. You should ensure that your build environment doesn't downgrade it. If you have to force it, do so. I can take a look if you have a reproducible sample, but I don't think Jib is doing anything wrong about it.

@chanseokoh  I shared above our buildEnvironment that shows that we use commons compress 1.26.0 that is only pulled in by jib and nothing should depend on it or "downgrade" it as far as I can see. Unfortunately, I don't have a sample as it is a private project and right now this isn't that important for us to debug this further. For now I just skip this update, it was supposed to be only a patch bump that broke our CI, we don't really need anything from the new version right now.

Is there a fix in the next release? or we should force the usage of commons-compress & commons-codec?
Anyway at the moment, we downgraded also to the previous version.

FWIW, there is nothing to fix in Jib. Jib asks to use the latest version of the libraries, but somehow your project is pulling an old version. Basically, it is your responsibility to correctly set up your project so that it doesn't happen. If your project is a multi-module one, make sure you follow https://github.com/GoogleContainerTools/jib/issues/4235#issuecomment-2057081017. Sometimes, you will have to manually resolve this kind of diamond dependency conflicts.

@chanseokoh no, that's not fully right, there is no "commons-codec:commons-codec" at all as you see I have to define it by myself. There are plenty of comments here, you could take a look if you can fix it, usually it's a case that we have to enforce a libraries version in the build classpath - it doesn't happen for other plugins

you can take any base spring boot project on 3.2.4

I am not the maintainer of this repo. I am contributing my own time to help the community. Please provide a reproducible sample if it is that easy to create.

I had some free time to look into why my build fails and in my case buildEnvironment  wasn't telling me the truth, because it did not include the dependencies from buildSrc
demo/buildSrc$ ../gradlew -q dependencies

Revealed this:
\--- org.testcontainers:postgresql -> 1.19.7
     \--- org.testcontainers:jdbc:1.19.7
          \--- org.testcontainers:database-commons:1.19.7
               \--- org.testcontainers:testcontainers:1.19.7
                    +--- junit:junit:4.13.2
                    |    \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
                    |         \--- org.hamcrest:hamcrest:2.2
                    +--- org.slf4j:slf4j-api:1.7.36 -> 2.0.12
                    +--- org.apache.commons:commons-compress:1.24.0

While running ./gradlew buildEnvironment was telling me that nothing uses commons-compress except jib and it is on version 1.26.0 which wasn't the case.

Okay, two dependencies:

commons-codec:commons-codec - no dependency at all, your trace confirms
commons-compress - wrong version, can we enforce or anything? gradle resolves the lower one it happens I know

@mihalyr-prospect there you go! As you saw, the cause is that Gradle pulls in an old version of some library in your build environment for one reason or another where ./gradlew buildEnv lies, which is a known issue. All you have to do is to resolve your diamond dependency conflict in your project in way or another. Glad you were able to fix it.

Moving the jib plugin version definition to the root of my multi-module project with apply false and using it at the subproject solved the issue for me as well.

Closing this issue as Jib is working as intended. Thanks everyone for the help!


Refine Arbitrage Bot to Meet Target Profit Milestone Criteria

After achieving prototyped arbitrage trade execution, the arbitrage bot should be refined and optimized in order to exceed the existing market maker contract's profit over a 7 day window. This will include technical optimizations (e.g., caching, laziness where possible), route discovery algorithm refinement, and other possible optimizations.
Note: Need clarification on the margin by which the arb bot must exceed the existing contract's profit.

@dowlandaiello any update on this one ?


What is the difference between ADJ & ADJe label in POS Tagging?

There are a number of labels generated by hazm,
what does an extra 'e' at the end of certain labels mean in this particular tagger??
in other words,
What is the difference between
ADJ & ADJe
N & Ne
ADV, ADVe
NUM, NUMe
PRO, PROe
etc etc

This e character indicates ezafe diacritic that is hidden in Persian text and hazm finds it. If you don't need this information just ignore it and use ADJe as ADJ.
More information about ezafe usecase:
A. Nourian, M. S. Rasooli, M. Imany, and H. Faili, “On the Importance of Ezafe Construction in Persian Parsing,” in The 53rd Annual Meeting of the Association for Computational Linguistics (ACL) and the 7h International Joint Conference on Natural Language Processing (IJCNLP), 2015.


Document patterns to build applications using Daml Finance

We should document the patterns used in the daml-finance-app to work with Daml Finance components.
I am specifically referring to

the factory pattern
writing the UI against interfaces rather than concrete template implementations

This will be easier once interface views + subscriptions are part of the official Daml doc.

I agree with "writing the UI against interfaces rather than concrete template implementations"

An additional pattern that should be explained here is to implement the Lifecycle interface as a side-contract rather than directly in the instrument

Client application architecture documented in https://github.com/digital-asset/daml-finance/pull/397

Factory Pattern issue --> https://github.com/digital-asset/daml-finance/issues/850


Harvest generator operating dates when they're within a year of one another

Overview
Closes #3340.
What problem does this address?
When generator operating dates are within a year of each other, keep the last observed date in the year. Then try to harvest these dates again. This fixes 38 of the 59 generators reported without an operational date in #3340. The others still have inconsistent datetimes that should not be harvested.
What did you change?
Added _gen_operating_date() method that mirrors _lat_long() method. Also actually fix the harvesting to apply changes made to special columns to the main harvesting process.
Testing
How did you make sure this worked? How can a reviewer verify this?
Run debug_harvesting.ipynb. Look at the generators highlighted in the issue and confirm that those with dates within a year of one another have been harvested with the last date kept.
# To-do list
- [ ] Do we want to extend this method to other operating dates such as `boiler_operating_date`?
- [ ] Ensure docs build, unit & integration tests, and test coverage pass locally with `make pytest-coverage` (otherwise the merge queue may reject your PR)
- [x] Update the [release notes](../docs/release_notes.rst): reference the PR and related issues.
- [x] Review the PR yourself and call out any questions or issues you have

I think turning this on for the other operating data columns makes sense if it's easy (which it seems like it should be).


Increase the interval between savings of Flower's state

This PR increases the time interval between savings of Flower's state. Each saving of Flower's state causes a complete re-write of the DB for storing Flower's state, so this interval must be sufficiently large to avoid overworking the CPU and the storage hardware.
This PR closes #258 and #301.
Note: Once this PR is merged. We need to switch the directory containing the DB file, flower, back to a spindle hard drive.

After one day of operation. The monitoring service is not consuming undue amount of CPU usage.
@yarikoptic I am merging this to the master now so that I can merge this change to https://github.com/datalad/datalad-registry/pull/306 in which I am modifying the Docker compose files. Additionally, we need arrange a time to to switch the directory containing the DB file, flower, back to a spindle hard drive.


Error while running locally on windows

When running on windows locally it is giving error as "The last dimension of the inputs to Dense should be defined. Found None."
Its working fine on Google Colab.
The error in file unetr_2d.py on line "encoded_patches = PatchEncoder(num_patches, projection_dim)(patches)"

Hi @saurabhsensai,
Thank you for reaching out and reporting this issue. It sounds like the TensorFlow version could indeed be the culprit here. Since it's working on Colab (with TensorFlow v2.15.0), ensuring you're using the same version locally might resolve the issue.

Great 😃. It actually solved the problem. Thank you very much.


467 - Process pseudo patient ID

Description
Fixes #467,

[x] read in pseudo patient id (particpant_id from dri-to-pixl) in the cli and add to database (pseudo_patient_id in Image table) if has been defined in the csv file (never define it in omop parquet input)
[x] CLI tests
[x]  in pixl_dcmd, when getting the Image entity, if it has a pseudo_patient_id then set the DICOM tag to use that, if not then update the database with the generated value from de-identification
[x]  pixl_dcmd tests

Type of change
Please delete options accordingly to the description.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Suggested Checklist

[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have passed on my local host device. (see further details at the CONTRIBUTING document)
[x] Make sure your branch is up-to-date with main branch. See CONTRIBUTING for a general example to syncronise your branch with the main branch.
[x] I have requested PR review to UCLH-Foundtry/arc-dev
[x] I have addressed and marked as resolved all the review comments in my PR.
[ ] Finally, I have selected squash and merge

Hi @stefpiatek and @p-j-smith Do you have any ideas on how to address the following issues? https://github.com/UCLH-Foundry/PIXL/actions/runs/10465931114/job/28981927756 ? Talk to you soon!

Do you have any ideas on how to address the following issues? https://github.com/UCLH-Foundry/PIXL/actions/runs/10465931114/job/28981927756 ?

Oh I think it might be related to the alembic migration that's needed to to add in the new column. There's some docs on adding a new migration

Thanks Stef for your comments. Let's catch up!

Getting there and the code you've written is of good quality 🎉
I think there's a bit of confusion over what we're asking for in terms of final outcomes so might be worth having a chat in person about my review comments.

Thank you, Paul and Stef, for your feedback and the productive pair programming sessions! Feel free to share any additional thoughts or suggestions. Thanks again, Miguel


Image Resize Plugin does not mark Editor Content as "dirty"

Informations
Firefox 64.0 on Mac OS.
How to reproduce the bug?

Go to https://alex-d.github.io/Trumbowyg/demos/plugins/resizimg.html
Open Javascript Console and type document.getElementById('editor');
Depending on screen resolution you'll see something like <div id="editor" style="margin: 1rem; height: 237.8px;" class="trumbowyg-editor" dir="ltr" contenteditable="true">
Now resize the image (make it smaller or larger)
Type document.getElementById('editor'); again
You'll see that the image height is unchanged (237.8px in this example), even though the image is actually smaller or larger on screen.

The problem is, if Trumbowyg were used in a real application and that application would have a "Save" button and the user would press it to save after a resize operation, then the old size would be saved. And the user would have no chance of noticing, because on-screen everything looks right. I suspect that the image resize operation doesn't mark the editor content as "dirty" or perhaps forgets to call some update/refresh command on Trumbowyg.

My workaround currently is to do $("#myeditor").trumbowyg('toggle') on save and then get the content of the editor. The toggle switches to HTML mode, which seems to trigger an update of the content. After uploading the content to the server, I toggle again to get back to rich text mode.

The cleaner way to force a content refresh is to call $('#editor').trumbowyg('execCmd', {cmd: 'syncCode'})

trumbowyg.$c.trigger('tbwchange'); is called. But I think that is something the editor should call, when it has changed. Here we need to signal an external change to the editor.

Yep, but it should call syncCode internally before tbwchange, and maybe the tbwchange should not be called anymore after that.

I agree and tried it with my application and it seems to work. Will create a pull request.

Is this fixed? I can reproduce the problem on the demo page with the steps described in the first post.
I have the same problem with the version 2.15.2 and a base64 image.


[5.1] Useless else

A few return are embedded into unnecessary else
Also for throw in \Illuminate\Encryption\EncryptionServiceProvider::register

Tests failing.

On that, trying to understand why. OK locally and with CircleCI..

Closing for now