Sets color picker to fixed position

Description
In the context of a project I came across the following problem when using GeoStyler:
Color pickers in the "Symbolizer Editor" are not displayed completely, especially if single components of the editor are hidden or in almost any display of the color picker for stroke color settings:

By changing the CSS property of the position the color picker becomes accessible again at least for the user:

Pull request type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Dependency updates
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe)
[ ] I am unsure (we'll look into it together)

Do you introduce a breaking change?

[ ] Yes
[x] No
[ ] I am unsure (no worries, we'll find out)

Checklist

[x] I understand and agree that the changes in this PR will be licensed under the BSD 2-Clause License
[x] I have followed the guidelines for contributing
[x] The proposed change fits to the content of the code of conduct
[x] I have added or updated tests and documentation, and the test suite passes (run npm test locally)
[ ] I'm lost; why do I have to check so many boxes? Please help!

Thanks @mholthausen
Did you check if the colorpicker moves along with the window, if this is being dragged?
We also had a fix a while ago (https://github.com/geostyler/geostyler/pull/345), maybe these changes got lost. In case the fixed approach does not work with dragging, this might be of help.

Yes, it moves along with the "Symbolizer Editor" window.
I have tested it in the current versions of Chrome (87.0.4280.66) and Firefox (83.0):


Caller entry in log should not include path

Currently, when running the toolchain, the caller entry in the log is printed with the relative path to the module:
02:26:28 INF ../../../go/pkg/mod/github.com/coreruleset/crs-toolchain/v2@v2.0.0-20221119080758-c264fb6b6ed6/cmd/regex_format.go:132 > Formatting url-schemes.data component=cmd

regex_format.go:132 is enough, the path information is just noise.

This is fixed now.


Theme support

To enable theme support (for example bootstrap), this needs to be added in the initialization of the paert select2 object:
self.select2 = self.$element.select2({
...
theme: options.theme,
...
})...

This is line 22 in the current version.

Hi,
Any progress on that?

Hi, the component is very useful. Considering the theme support ... the fix I posted in the OP is working properly with bootstrap theme for example - it just passes on the theme parameter. Seems a valid fix just to be added this line of the code.
I can do a PR if you need ? ;)


Ore Gen

Describe the Bug
I am running the newest Version of Create Fabric on a Server and i get this error all the time which kills my RAM and crashes the Server... "Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!" ... I didnt change any spawn chances and the only thing that is close to the error i found is this old forge error https://github.com/Creators-of-Create/Create/issues/102 but so far i did see the stone variants and zinc ore so im not sure if it is actually a create bug... the only other mod that adds any stone variants is twigs (https://www.curseforge.com/minecraft/mc-mods/twigs)... I think it occurs when unloaded chunks are loaded again ore new chunks are loaded... Currently playing this modpack (https://www.curseforge.com/minecraft/modpacks/zentner-winterpack) so there u can find all other mods it could be related to...
Reproduction Steps

Create on a Server (didnt get it in SP so far)
Loading unloaded or loading new chunks

Expected Result
I dont think anything is really wrong with the generation itself except for the server to get an error and pretty much making it lagg and crash because of it...
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods
No response
Additional Context
No response

need the log

Its no real crash it just says "02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Work...
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Worker-Main-1/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:27] [Work...
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Worker-Main-3/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!
[02:04:29] [Work..."

full thing please. put it on a paste site.

there is nothing more than that the server doesnt really crash but it just laggs caus this error occurs

I need the full log to see your full mod list and any other errors that may have occurred.

i mean it is a server log and when it laggs there are no other errors and i posted the modpack where u can see all mods included above^^

what he means may be is the whole log/latest.log file ? (found   in your .minecraft folder)

yeah i'll send that tomorrow but im telling you that thing is causing extreme laggs and there are no other errors while it laggs

if there were any mod specific errors or crashes i would know on which modsite to ask .-.

maybe include the  and  config file  (server mods ..etc)?

https://gist.github.com/DerRentner/a1cc84df6076abc1683d5c0a7a3eec3f#file-latest-log
"[02:04:24] [Server thread/INFO]: [[Overworld] Rentner720: Teleported [Overworld] Rentner720 to 10000.500000, 300.000000, 10000.500000]
[02:04:25] [Worker-Main-2/ERROR]: Your ore spawn chances don't add up to 100! Ores won't spawn as you intend!"
as an example i tpd to an unloaded chunk and the error occured...
I think it is with never before loaded chunks and with unloaded chunks being loaded again but im not sure about the second one... Same in Singleplayer btw just testet it...

Still have no clue why the error happens and what causes it performance isnt as bad as it was a few days ago when the error occurs but it still spams the server log... and i still couldnt find anything like it except the previous mentioned error in the create forge version from a few years ago... And as i said before if u want to know what mods and config just look at this modpack https://www.curseforge.com/minecraft/modpacks/zentner-winterpack which i own and update and the error occurs with these excact mods and configs...

the error is from YUNG's Better Mineshafts

Looks like your config for it might be wrong. Try deleting it and letting it regenerate.
The error doesn't seem like it should cause lag though.

If you can get the server to crash again and send the log I'll look at it. But for now this doesn't seem like a Create issue, unless it's fixed when Create is removed.


[TIR] Flatten SeqStmt on construction

Previously, SeqStmt could be nested, making a distinction between the nested SeqStmt({SeqStmt({a,b}), c}) and the flat SeqStmt({a,b,c}), even though the two are semantically equivalent.  This also caused an issue with round-trips through TVMScript, which does not preserve this distinction.
This commit updates the SeqStmt constructor and the SeqStmt visitor in StmtMutator to flatten nested sequential statements provided.
This is part of changes described in https://github.com/apache/tvm/pull/14486, to improve round-trip failures that occur in lowering.

Sorry for the late response. Could you please rebase it again and let's merge it?

No worries (this has been on my back burner as well).  Main has been merged into the PR branch to resolve conflicts, and now running through CI.

@tvm-bot rerun

Thanks @Lunderberg for the PR :)


Support for LCLs (and maybe ECLs) in TMC messages?

It seems to be easy to get hold of a country's LCL in TMC Exchange format (ISO 14819-3). And in the same package (for Germany) I also got the ECL - but in Excel format which can easily be exported to CSV.
Could you add support to use those files to provide clear text messages for TMC?

Any specifications on TMC Exchange format? Nothing comes up on Google, and there's no mention of it in my copy of ISO 14819-3:2004. Is this in the 2013 revision? If so, where did you get a copy?
The ECL is already hardcoded in English in tmc_data.h. Translation could be possible and would seem to also require language-specific rules for the grammar to work.

I only found it mentioned in the terms and conditions for the German LCL/ECL - last paragraph. Google found this PDF which looks promising.
About the grammar. The German ECL uses 3 columns: "No quantifier", "Q=1" and "Q>1". And sentences have placeholder(s) for the numbers, e.g.:
"Accident, (L) Stationary traffic" / "An accident, (L) stationary traffic" / "(Q) accidents, (L) stationary traffic"
But there's also a generic all-purpose column reading "(Q) accident(s), (L) stationary traffic".
(L) gets replaced by the length in metres, e.g. "1 km"
(Q) gets replaced by the quantity
and then there are a few more such codes
There's some more information in that Excel file about extra content which might get sent via additional RDS groups and how that is encoded. You can just order the set from that link above. I got the mail right away, so it seems like nobody checks your data before handing out the precious data.

Thanks, great sources!

LCLs are now supported, experimentally, using the option --loctable "directory_with_loctable".

It borked for me with:
terminate called after throwing an instance of 'std::runtime_error'
  what():  not supported from ISO 8859-15 (Latin 9) to UTF-8
Aborted

Because the README.DAT was:
1;31/10/2014;;BASt;ISO 8859-15 (Latin 9);2;1

But I don't know how you could make something valid out of that. After changing it to ISO 8859-15, it didn't complain anymore. But I still don't get locations:
{"group":"3A","open_data_app":{"app_name":"RDS-TMC: ALERT-C","oda_group":"8A"},"pi":"0xD321","prog_type":"No PTY","tmc":{"system_info":{"is_encrypted":false,"is_on_alt_freqs":true,"location_table":1,"scope":["urban"]}},"tp":true}
{"group":"8A","pi":"0xD321","prog_type":"No PTY","tmc":{"message":{"description":"Queuing traffic.","direction":"single","event_codes":[108],"extent":"-2","location":34022}},"tp":true}
{"group":"8A","pi":"0xD321","prog_type":"No PTY","tmc":{"message":{"description":"Right lane closed. Roadworks.","direction":"single","event_codes":[501,701],"extent":"-1","location":10257}},"tp":true}

I was a bit too optimistic when I thought the encoding field would ever be a valid encoding name.. :)
Are you loading location table number 1? I should perhaps disable the try/catch statements so that all database parsing errors would crash the program. (I didn't test it on a German dataset myself, I had a Finnish one from 2009.)

How can I check which tables it loads? I just let it go crazy on the directory with the unpacked LCL data using the new -l parameter. Is there anything else I should check or configure?

It should now print an object called "location_table_info".

Hmm ... seems there's something wrong (it's printed twice, and judging from the time between the two lines, it's also parsed twice?):
{"location_table_info":{"ltn":1,"num_points":0,"num_roads":0,"num_names":30291}}
{"location_table_info":{"ltn":1,"num_points":0,"num_roads":0,"num_names":30291}}

It's reloaded every time sync is regained or something :) But this will be fixed in the future.
Hmm, seems like points and roads are not succesfully loaded. It could be that column names differ from those in my database. I need to request that German one for sure.

From what I can see, the column names are correct. Here are the headers and a few lines of data of those files:
NAMES.DAT (column names from locationdb.cc: NID, NAME)
CID;LID;NID;NAME;NCOMMENT
58;1;1;(Basketball-)Arena;
58;1;2;(Fußball-)-Arena;
58;1;3;(Fußball-)Arena;
58;1;4;(Fußball-)Stadion;
58;1;5;48;

ROADS.DAT (LCD, ROADNUMBER, RNID)
CID;TABCD;LCD;CLASS;TCD;STCD;ROADNUMBER;RNID;N1ID;N2ID;POL_LCD;PES_LEV
58;1;44;L;1;1;A448;26551;4409;4389;350;0
58;1;57;L;1;3;L140;;26166;6813;279;0
58;1;82;L;1;4;VG29;;30024;17246;14291;0
58;1;113;L;5;0;;2061;;;14292;0
58;1;118;L;1;3;L170;;25820;20715;576;0

SEGMENTS.DAT (ROA_LCD)
CID;TABCD;LCD;CLASS;TCD;STCD;ROADNUMBER;RNID;N1ID;N2ID;ROA_LCD;SEG_LCD;POL_LCD
58;1;34;L;3;0;B8;;6948;6813;50444;;260
58;1;411;L;3;0;A14;;29429;24782;51281;;268
58;1;1987;L;3;0;L75;;7477;11867;6982;;256
58;1;1990;L;3;0;L75;;11867;18902;6982;;256
58;1;3011;L;3;0;L28;;19352;19223;3009;;529

POINTS.DAT (TABCD, LCD, N1ID, XCOORD, YCOORD, ROA_LCD, SEG_LCD, RNID)
CID;TABCD;LCD;CLASS;TCD;STCD;JUNCTIONNUMBER;RNID;N1ID;N2ID;POL_LCD;OTH_LCD;SEG_LCD;ROA_LCD;INPOS;INNEG;OUTPOS;OUTNEG;PRESENTPOS;PRESENTNEG;DIVERSIONPOS;DIVERSIONNEG;XCOORD;YCOORD;INTERRUPTSROAD;URBAN
58;1;14;P;1;11;;;26528;;3730;;8998;;1;1;1;1;1;1;;;+00684525;+5192775;0;0
58;1;15;P;1;10;;;27953;;5385;;8998;;1;1;1;1;1;1;;;+00684120;+5203450;0;0
58;1;16;P;1;11;;;636;;742;;8998;;1;1;1;1;1;1;;;+00691620;+5213720;0;0
58;1;17;P;1;15;;;10222;;1389;;8998;;0;1;1;0;1;1;;;+00697525;+5219160;24935;0
58;1;18;P;1;11;;;26528;;3730;;9213;;1;0;0;1;1;1;;;+00684525;+5192775;0;0

POFFSETS.DAT (LCD, NEG_OFF_LCD, POS_OFF_LCD)
CID;TABCD;LCD;NEG_OFF_LCD;POS_OFF_LCD
58;1;14;39392;22
58;1;15;22;16
58;1;16;15;17
58;1;17;16;
58;1;18;;26283

The empty fields might have been a problem. I've set default values now.

Wohooo, that was it!
{"location_table_info":{"ltn":1,"num_points":35765,"num_roads":3820,"num_names":30292}}
{"location_table_info":{"ltn":1,"num_points":35765,"num_roads":3820,"num_names":30292}}

And:
{"group":"8A","pi":"0xD321","prog_type":"No PTY","tmc":{"message":{"coordinates":[[52.36730,13.46670]],"description":"Warning cleared.","direction":"single","event_codes":[1771],"road_number":"B96a"}},"tp":true}
{"group":"8A","pi":"0xD321","prog_type":"No PTY","tmc":{"message":{"coordinates":[[52.42030,13.52240]],"description":"Reopened.","direction":"single","event_codes":[467],"road_number":"A113"}},"tp":true}

Thanks a lot! :smiley:

Could you make it so that redsea still outputs the location ids, even though it has the location from the table lookup? Same for decrypted locations - it would be nice if it would still spit out the encrypted_location, too.

Sure why not, it should work now.

You're the best! Thank you very much! :+1:

By the way, I changed the way coordinates are printed, to disambiguate between latitude and longitude.

There doesn't seem to be a standard exchange format for ECLs. Closing this for now.


feat: support fuzzy-search, refactor code structure ✨

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


Fix ufw task according to Ansible 2.7.8 changes

Since Ansible 2.7.8 direction param is required: https://github.com/ansible/ansible/pull/50402/files#diff-476edcbbb72b9029f5b116b4c813c076R403

We are facing this same issue. Can this be merged ?

Builds for some platforms are failed. We need to fix them first.


Johanna/fixes apollo client upgrade

FRONTEND PULL REQUEST
Related Issue
Resolves a dependabot upgrade that needed code changes and fixes some weird behavior in the csv download logic
Changes Proposed

Upgrade apollo-client dependency
Refactor logic in the csv download to not depend on a custom wrapper to trigger lazy queries and use the lazyQuery method in apollo client and useEffect combo instead
Remove the useImperativeQuery wrapper that had typescript issues with the latest apollo client version and that was not strictly necessary for the csv download logic

Additional Information
All axe checks are passing
Testing
I have manually tested this in Dev5

Verify that the csv file downloads correctly with and without filter params

@emyl3 I would appreciate your review the most as you have worked with the results csv download component a lot!

looks like this fixes #5287 🎉
can you confirm and close after merging if this is the case?

@johanna-skylight sorry for the delay reviewing now!


How to generate mock for protocol includes macro

Protocol includes macro, the method is not generated to mock result file. Is there a way to resolve this situation ?
protocol PresentableListener: class {
    func run()
    #if DEBUG
    func showDebugMode()
    #endif
}

If generate mock for the above protocol, Mock class includes run method but showDebugMode method is not generated.

Can you mention what commandline you used to generate mocks? If you weren't using a commandline, can you mention which of the two parsers (sourcekit, swiftsyntax) was used?

@elsh
./mockolo  -s [some directories] -d ./Mock/MockResults.swift --header "@testable import mymodule"

I generated mockolo binary and use it like the above command.

See https://github.com/uber/mockolo/pull/82

@elsh
I confirmed to generate the mocks includes macro syntax, it works. Thanks for quickly fixing.


update t-digest algo in tex

@tdunning, line 62 was confusing me - can you confirm it should be j instead of i? Also, can you confirm the other changes as well?

Can you justify the changes?  Looks like you are correcting typos and such,
but it would help to have some commentary.
On Sun, Mar 15, 2015 at 3:00 PM, Cameron Davidson-Pilon <
<EMAIL_ADDRESS>wrote:

@tdunning https://github.com/tdunning, this line was confusing me - can
you confirm it should be j instead of i?
You can view, comment on, or merge this pull request online at:
https://github.com/tdunning/t-digest/pull/43
Commit Summary

update t-digest algo in tex

File Changes

M docs/t-digest-paper/histo.tex
https://github.com/tdunning/t-digest/pull/43/files#diff-0 (2)

Patch Links:

https://github.com/tdunning/t-digest/pull/43.patch
https://github.com/tdunning/t-digest/pull/43.diff

—
Reply to this email directly or view it on GitHub
https://github.com/tdunning/t-digest/pull/43.

Yes, they are just typo corrections, no new logic. I'll comment inline.


refactor: optimization of text selections

[x] restrain the interface for textSelectionRenderManager and textSelectionService

excellent code!


chore: update CODEOWNERS file

What does this PR do?
update codeowners file
What issues does this PR fix or reference?
https://github.com/eclipse/che/issues/22188
Is it tested? How?

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

@mkuznyetsov You commit needs a signoff (git commit --amend -s)

/retest


Translate Display format

Hello, is there any possibility to translate dateFormat option?

You can pass dateFormat to component, for example
dateFormat="YYYY/MM" or dateFormat="YYYY年MM月"

I'm using dateFormat = "MMM-YYYY" and the result is next

But the month is showed in English and I need translate it to Spanish


fix(docs): build demo

The demo was no longer included in the doc site since https://github.com/slidevjs/slidev/commit/4f5bb6820d47e6eaba8836a8a933ec29a8b3112e
check this out: https://sli.dev/demo/starter/7
And I've added PLAYWRIGHT_BROWSERS_PATH=0 env virable on netlify settings to prevent chromium executable not found error in a cached build. Just mentioning, not sure this project did this before.

seems chromium executable doesn"t exist still exists, and PLAYWRIGHT_BROWSERS_PATH=0 didn't work.🥲


Don't overwrite real fields when mutation argument is the same

Fixes #97
in #80 where passed in values from a mutation were returned in the payload if the field name is the same, this was overwritting real values whereas it should only be applied to fake values. Changing the order in which the fake and real objects are spread to construct the responses fixes this.

@alecrae Released as<EMAIL_ADDRESS>🎉


add ownCloud chart

This uses the same approach I've described in #177. @lachie83 I've held off on Ingress for now, I think I will work on improving these charts to support that in a future version.

Worked like a charm for me. Thanks!


add ETDRS grid tool

Context

This tool aims to implement the drawing capabilities of an ETDRS Grid to CS3D. An ETDRS Grid (Early Treatment Diabetic Retinopathy Study Grid) is a standardized grid used in ophthalmology to assess macular thickness and retinal changes. It divides the macula into three concentric regions: the central subfield (1 mm), the inner ring (3 mm), and the outer ring (6 mm), often further divided into quadrants. The grid facilitates consistent measurement and comparison of retinal areas, aiding in the diagnosis and monitoring of conditions like diabetic macular edema. It allows the customization of the diameter of the concentric rings and the angles of the quadrant lines.
Changes & Results

Testing

Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

[] I have run the yarn build:update-api to update the API documentation, and have
committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] "OS:
[] "Node version:
[] "Browser:

@anaisabel1909 can you define the example in examples-info.json ? It will not show up in the docs website if you don't do so.
just add the following:
      "etdrsGrid" : {
        "name": "ETDRS Grid Tool",
        "description": "Here we demonstrate how to use the ETDRS Grid tool. An ETDRS Grid (Early Treatment Diabetic Retinopathy Study Grid) is a standardized grid used in ophthalmology to assess macular thickness and retinal changes."
      },

https://github.com/cornerstonejs/cornerstone3D/blob/main/utils/ExampleRunner/example-info.json


Support more than 1 action on simulator

This code works:
    it('starts with video view on first launch', (done) => {
      global.simulator.deleteAndRelaunchApp(() => {
        expect(element(by.id('VideoView'))).toBeVisible();
        done();
      });
    });

    it('does not display video view on second launch', (done) => {
      global.simulator.reloadReactNativeApp(() => {
        expect(element(by.id('VideoView'))).toNotExist();
        done();
      });
    });

while this fails (prints error: _onTestResult is undefined on testFailed):
    it('starts with video screen on first launch only', (done) => {
      global.simulator.deleteAndRelaunchApp(() => {
        expect(element(by.id('VideoView'))).toBeVisible();
        global.simulator.reloadReactNativeApp(() => {
          expect(element(by.id('VideoView'))).toNotExist();
          done();
        });
      });
    });

I tracked the reason to this
Also, #57 would make this code much prettier

using async await instead of invocaction queue and callbacks will solve this.
https://github.com/wix/detox/issues/38

new async await api is no in master, check out the test project. upcoming detox version (5.0.0) breaks the api completely in favor of async await.
device actions are now async await as well, you can now do
    it('starts with video screen on first launch only', () => {
       await device.deleteAndRelaunchApp();
       await expect(element(by.id('VideoView'))).toBeVisible();
       await device.reloadReactNativeApp();
       await expect(element(by.id('VideoView'))).toNotExist();
    });


Adds cacheBustingEnabled setting to simple browser

This is a feature to add a toggle for the "cache busting" behaviour in the simple browser.
The feature request is here https://github.com/microsoft/vscode/issues/205105
Apologies in advance if this isn't the correct way to go about this, please feel free to disregard this PR if I've not done this correctly :)

@microsoft-github-policy-service agree

Closing as out of scope based on comment in https://github.com/microsoft/vscode/issues/205105


update blocks after undo and load

Add calls to update blocks after ctrl+z undo and after program load.  Math blocks (such as plus, minus, etc.) were not updating when they had value inputs.  Instead showed invalid string "..."
[#159514952]

I added changes as per @dougmartin's request.  Going to merge.


Default value of properties location

Please make it more clear that default values do not go in the properties block but rather in the constructor. This question has come up in multiple locations #114, slack, and twitter

I will include it in the docs


Split forms sass partial in subpartials

checkboxes, file-input, input-fields, radio-buttons, range, select and switches

Awesome, thanks!


Support milliseconds

Thanks for the great contribution to FastApi!
I was thinking it'd be a good idea to support milliseconds so that:

fractions of seconds can be used, and
it's the unit expiring information is stored https://redis.io/commands/expire#expires-and-persistence

My first take is that milliseconds should be used as the default for all rate limiting but to avoid breaking changes I'd be happy to add a flag for seconds vs. milliseconds. Please let me know what you think!

Good, thanks for that!

Thanks as well!!


how to get flag self position in os.Args

how to get flag self position in os.Args

@zhujintao Can you elaborate with an example ?

mask password field in command lineps -ef  --mysql-dsn=*********
flag := &cli.StringFlag{Name: "mysql-dsn", Usage: "mysql connect dsn, format: user:password@ip:port` `"}
	flag.Action = func(ctx context.Context, cli *cli.Command, s string) error {

		var pos int
		for _, name := range flag.Names() {
			findname := "--" + name + "=" + s
			pos = slices.Index(os.Args, s)
			if pos == -1 {
				pos = slices.Index(os.Args, findname)
			}
		}

                 // mask password args to ****
                 maskDsnPasswordForIndex(pos)

                 return nil
	}

@zhujintao No we dont have any mechanism for the feature you want. You could reconstruct the command line args based on all the flags currently set and mask specific stuff

ok,  can add method to get field position in command line?

If you'd like to add it I would be happy to review your PR.


Support for persistent 2.5

It would be nice to support the latest version of persistent 2.5 series.

Yes, that would be very nice indeed! As it is now, esqueleto has effectively been removed from Stackage because it's blocking other packages. :cry:

Any progress on this? Downstream is now starting to patch around this.

Now that lts-7.0 is out with GHC 8.0 we cannot switch to it solely because esqueleto. @meteficha Any chance you take 5 minutes and merge a PR that addresses this?

@meteficha was this project abandoned?

What's going on here? Looks like @vandenoever fixed it but didn't submit a PR to upstream Esqueleto?

@wyager I've created alternative PR #153 but I will be happy to close it in favor of more proper one

@wyager It was @tebello-thejane  who fixed it for my use-case with https://github.com/prowdsponsor/esqueleto/pull/150. I cannot say which is the better PR.

Maybe we should contact them at<EMAIL_ADDRESS>and ask if this is maintained and if not, someone could take over it?

Perhaps an issue at https://github.com/haskell-infra/hackage-trustees/issues ?

I suggest updating this ticket to be about persistent-2.6 and base-<IP_ADDRESS>, because we have a esqueleto-2.5.0 version now, but it still can't be use with lts-7.x because it's too old.

@nd2s the new maintainer's repository is here: https://github.com/bitemyapp/esqueleto


Give Alby users the opportunity to claim a Lightning Address through Alby

Alby allows to send tips to Twitter profiles when the profile owner published a Lightning Address in the profile. Currently there is only a very limited amount of services that allow to conveniently generate a LN Address (some examples)
Alby could integrate such a service to give more user the possibility to receive payments (e.g. tips on Twitter)
There are several options:
1.) Provide a full service consisting of LN address server + custodial node. That would allow Alby to give any user a LN address.
2.) Provide an own bridge server to an user's existing LN node.
3.) Integrate a "community-supported" LN address server to a user's existing LN node

This functionality has been added now but maybe we want to use this thread to discuss ways to improve the process and make it more visible to the users?


Display URL and Folder as Subtext

Information should be displayed next to each item that shows what folder it's in (if applicable).  This can be achieve using the parentId and url attributes in a BookmarkTreeNode.
This type of stuff exists in Spotlight:

Fixed with this commit:  https://github.com/jonnykry/bookmark-spotlight/commit/01f83034ada4b878fde45e87e5bc5d19375bb4a3


backend behind basic auth does not work - Request cannot be constructed from a URL that includes credentials

If i put the VRT backend behind a basic auth proxy, and configure the REACT_APP_API_URL like<EMAIL_ADDRESS>i get the following error in the ui:
Failed to execute 'fetch' on 'Window': Request cannot be constructed from a URL that includes credentials<EMAIL_ADDRESS>
Any way to workaround this?

@monotek I guess it's due to deprecation of basic auth in url
don't think you could workaround it as is without making it as a headers

How can i do it via headers?
Is there another ENV variable i could use?
Is there any documentation about it available?

@monotek it requires changes on frontend side, it's not implemented

Can you point out where in the Frontend?
Is there another way to protect the api?
The api tokens seem only to protect the project but not stuff like user creation.

@monotek all private API are already protected with auth
use company VPN to completely restrict access to public as well

Thats kind of unfortunate.
Would be nice auth via header could be implemented.
Or at least an option to disable user registration.

@monotek yeah, disabling self registration could be an feature together with allowing admin users to create new ones


reset first-guess ice/snow surface temperature to celsius2k

current behavior is for seaice solve4temp to start its iterative search with the last value of TICES.  In this version the model starts with celsius2k instead. The reason for the change is to simplify the adjoint. @mjlosch suggested that we try this edit.

@ifenty great!
Could you turn this into a "draft" PR? That way it's clear we are still working on this. I think you need to be author to do so, I don't see the button at my end.
Have you checked in a FWD/AD simulation that this change does not affect the result any more that any other numerical change? I would expect differences in the simulations of order <1% in variables like sea ice thickness, concentration, surface temperature, etc.
There are a few things to think about:

There is a place in seaice_reg_ridge.F where TICES is reset if the ice thickness is below a certain threshold. I am not sure how to handle this cleanly. One option would be to have a CPP flag (like SEAICE_RESET_TSURF or TICES) and apply the change of seaice_growth_adx also to seaice_growth, just within this CPP flag?
we could think of removing the pickup of TICES, if a flag like SEAICE_RESET_TSURF is defined.

I added the label "work in progress" which has similar meaning as "draft" as far as I know.

Miraculously, resetting ticeInMult = celsius2k does not affect the AD gradient, but only the FD gradients (from 16 to 9 digits of agreement):
Y Y Y Y 16>16< 9 16 16 16 16 16 22 16 16 16 16 16 16 22 16 16 16 16 16 16 16 16 16 16 16 pass  offline_exf_seaice  (e=0, w=33, lfd=1, dop=1)
Y Y Y Y 16>16<16 10 10  6  6 16 16  6  6 16 22  5  5 22 22 22 22 pass  offline_exf_seaice.thsice

* There is a place in seaice_reg_ridge.F where TICES is reset if the ice thickness is below a certain threshold. I am not sure how to handle this cleanly. One option would be to have a CPP flag (like SEAICE_RESET_TSURF or TICES) and apply the change of seaice_growth_adx also to seaice_growth, just within this CPP flag?

I guess the larger question is do we need to carry around the ice/snow surface temperature outside of seaice_growth_adx? it doesn't play any role in seaice_reg_ridge (e.g., sea-ice viscosity is not a function of surface temperature) or anywhere else besides being a diagnostic variable.

Also, can you @mjlosch explain what is the difference between kind=isbyte and byte =isbyte ?

it's the same, but "byte" is deprecated.

if ticeMultIn is set to celsius2k as first-guess and is updated to the EBM temperature after solve4temp, do we even need both ticeMultIn and ticeMultOut? maybe just a single ticeMult that is updated in solve4temp?

I agree, but that's even independent of TICES.

I guess the larger question is do we need to carry around the ice/snow surface temperature outside of seaice_growth_adx? it doesn't play any role in seaice_reg_ridge (e.g., sea-ice viscosity is not a function of surface temperature) or anywhere else besides being a diagnostic variable.

There's still "seaice_growth.F" which requires (so far) that this field is available, and in "cost_test_ice.F", we also need this as a global field. That's why I suggested a CPP flag: if we use this new method, TICES doesn't need to be in the pickup. The it's only needed in the pickup, as a diagnostics (which could be done locally in seaice_growth_adx, although this implies a staggering in time with respect to HEFF, etc.) and in "cost_ice_test.F"

I guess the larger question is do we need to carry around the ice/snow surface temperature outside of seaice_growth_adx? it doesn't play any role in seaice_reg_ridge (e.g., sea-ice viscosity is not a function of surface temperature) or anywhere else besides being a diagnostic variable.

There's still "seaice_growth.F" which requires (so far) that this field is available, and in "cost_test_ice.F", we also need this as a global field. That's why I suggested a CPP flag: if we use this new method, TICES doesn't need to be in the pickup. The it's only needed in the pickup, as a diagnostics (which could be done locally in seaice_growth_adx, although this implies a staggering in time with respect to HEFF, etc.) and in "cost_ice_test.F"

@mjlosch Oh, yes. another reason to carry TICES is so that ice/snow surface temperature can be used as a cost term. We should just set TICES equal to ticeMultOut after solve4temp.

@ifenty I turned this into a draft to make it clear that we are still working on this. There are few things to sort out, some of the points are repeated from a previous post.

[ ] TICES is still used in seaice_growth_adx.F to decide if precipitation will be snow or rain. This happens before calling solve4temp (which would compute new surface temperature). We'll have to move this part of the code to after calling solve4temp if we really want to get rid of the dependency on TICES of the previous timestep.
[ ] There is a place in seaice_reg_ridge.F where TICES is reset if the ice thickness is below a certain threshold. I am not sure how to handle this cleanly. One option would be to have a CPP flag (like SEAICE_RESET_TSURF or SEAICE_RESET_TICES) and apply the change of seaice_growth_adx also to seaice_growth, just within this CPP flag?
[ ] we could think of removing the pickup of TICES, if a flag like SEAICE_RESET_TSURF is defined.
[ ] what are the effects/differences in a long run (order 1-10 years of simulation)? I assume that they are very small, but we should be able to quantify them. It would be great if @ifenty could explore this a little so that we can give some numbers or even a plot here.
[ ] Do we want to restrict these changes to seaice_growth_adx.F, or also add them to seaice_growth.F for consistency? This would have the advantage that we can cleanly remove resetting TICES in seaice_reg_ridge.F

I propose this:

we get replace ticeInMult and tIceOutMult by a single ticeMult = TICES in seaice_growth.F and seaice_growth_adx.F, then pass it to solve4temp, copy the result to TICES, and then diagnose TICES after seaice_growth (or at the end), but no longer in seaice_diagnostics_state.F (this will change the diagnostics of TICES, but not the results)
We add a flag SEAICE_RESET_TICES. If set, TICES is reset in seaice_growth_adx.F, including using TICES to decide over snow or rain, i.e. use the surface temperature of ice AFTER solve4temp (will change only offline_exf_seaice)
We also add this flag to seaice_growth.F (will change many results at some low level)
decide if SEAICE_RESET_TICES should be the default or if it should even be removed again. This will affect all setups out there that use seaice, but only very slightly, as we can probably show that the differences between resetting TICES or not are small. Alternatively, we could skip the SEAICE_RESET_TICES flag and immediately go for resetting TICES after make sure that the effects are small.
cleanup: remove resetting TICES according to HEFF in seaice_reg_ridge.F. and remove a lot of store directives.

The intended outcome is that we break the dependency of TICES across the time loop cycles, with minimal impact on the results; this will help move PR #468 forward. TICES is still there as a global diagnostics to be used in any cost function that we want to have. We keep it in the pickups for now (although not necessary, alternatively we could have a CPP flag SEAICE_TICES_IN_PICKUPS or so).
@jm-c what do you think about this plan?

@ifenty I just realised in a different context that TICES (copied to ticeMultIn -> TSURFin) is used in S/R seaice_solve4temp to set the albedo.
https://github.com/MITgcm/MITgcm/blob/a887215b1e0e90e76d67063756ad7a4fa9398f04/pkg/seaice/seaice_solve4temp.F#L247
https://github.com/MITgcm/MITgcm/blob/a887215b1e0e90e76d67063756ad7a4fa9398f04/pkg/seaice/seaice_solve4temp.F#L295-L301
This means that setting ticeMultIn = 0degC will not work as it will corrupt the albedo computations, and we still need TICES from the previous time step. If we want to proceed here we need to have some new ideas. What do you think?

@mjlosch I looked at the code and see the issue that you are raising. What if we allowed the albedo (and thereby the absorbedSW) to change within the iterations? We could start the iterations with the surface temperature set to 0 Celsius (melting condition) with its corresponding melting condition albedo. Then if the surface temperature in a later iteration changed to be  <0 C,  the albedo would change to its freezing condition value. from that iteration on, we would be in the same situation as if we had inherited the 'melting or freezing' condition information from the last iteration of TICES.
Perhaps another way of doing solving this problem is to have a single, trial iteration starting from T=0.  If the new T is < 0 then we can say that the surface albedo has to be from a freezing condition and then proceed with the iterations without allowing albedos to change.  Doing that would only make sense if the iterative temperature updates never switched directions (i.e., never went from 0, to <0, then back up to >=0).
What do you think?

@ifenty I also thought about including the albedos in the iterative loop. I foresee that this may jeopardise convergence as it adds (non-smooth) nonlinearity. Are you willing to test this?
This second option appears to much of a hack to me, but again, one can give it a try.

@mjlosch Sure, I can test it out. My intuition is that if we always start from a melting condition (Tsurf = 0C) then we'll be OK.

@ifenty should we pursue this PR any further, especially in the light of the dependence of the albedos on TICES?

@ifenty This is just a measure of the effect of incorrect albedo computations in this branch. I compared a pair of 3-year runs using this branch and the master branch. This branch has a slightly larger sea-ice concentration cost (by 4%) than the master branch.

@mjlosch Thank you for implementing this. As I mentioned in Monday's meeting, @ifenty and I are also implementing something to solve the albedo computation. See https://github.com/owang01/MITgcm/tree/tices_reset_in_seaice_growth_adx. A three-year forward run with our implementation has almost the same sea-ice concentration cost (increase by 0.04%) as the master branch.
The way how it is implemented is as follows. We start using dry albedo for the iterations. During the iterations, if the sea ice surface temperature (tsurfLoc) is ever warmer than melting temperature, we set a switch (tsurfabovemelt as a function of i,j) to TRUE. After the iterations, if the switch tsurfabovemelt == FALSE, we will continue using dry albedo. Otherwise, we use wet albedo and compute absorbedSW, IcePenetSW, and F_ia based on wet albedo. So the fluxes would be consistent with the albedo we are using.
We are also doing a pair of 28-year forward runs again the master branch to see how large sea-ice would differ.

For 28-year runs, the sea-ice concentration cost difference between this branch and master is < 1% . (As pointed out by Martin, sea-ice concentration cost may not be a good matrix for testing the implementation).
@mjlosch  https://github.com/owang01/MITgcm/tree/tices_reset_in_seaice_growth_adx has the latest modification to seaice_solve4temp.F we implemented.


Advance to "Support subqueries in from and join" commit.

Coverage increased (+0.2%) to 86.098% when pulling 4a8cc900ec026a304cd4463944f5854cf5fe62f5 on subqueries into fba38867d254d20715aa6e0446d9cadf81dbea26 on master.

Coverage increased (+0.2%) to 86.098% when pulling 4a8cc900ec026a304cd4463944f5854cf5fe62f5 on subqueries into fba38867d254d20715aa6e0446d9cadf81dbea26 on master.


when and run_once are reduplicative

ci check this

@tanshanshan Can you rebase this?

https://github.com/kubernetes-incubator/kubespray/pull/1694
I fix it in a new pr.
Sorry to trouble you


Multiple markdown replacements on same line don't work

If you have a markdown line like the following:

Test: more text
This should be changed into a list item and then bolded text.

The list item is created but the bolded text is not.
I seem to have found the error in this line:
lineText = this.quill.getText(this.quill.getIndex(line), lineText.length);

This does not pick up the rest of the line after the the list item substitution is made. Any way to get it to correctly pick up the rest of the lineText so it can continue with further substitutions?
Thanks a lot for any insights!

I was able to fix this by rewriting the lines for loop to the following:
lines.forEach((line, index) => {
            let lineText = line.domNode.textContent
            let lineIndex = this.quill.getIndex(line)
            let oldLineText = null

            while (oldLineText !== lineText) {
                oldLineText = lineText

                for (let match of this.matches) {
                    const matchedText = lineText.match(match.pattern)

                    if (matchedText) {
                        // NOTE: `code-block` is special (multi-line)
                        if (match.name === 'code-block') {
                            if (index + 1 === lines.length - 1) {
                                continue
                            }

                            const restOfLines = lines.slice(index + 1, lines.length)
                            const lastIndex = restOfLines.findIndex(l => l.domNode.textContent.match(match.pattern))
                            if (lastIndex === -1) {
                                continue
                            }

                            match.action(this.quill.getIndex(line), this.quill.getIndex(restOfLines[lastIndex]))
                            lines.splice(index, lastIndex + 1)

                            break
                        } else {
                            match.action(lineText, match.pattern, lineIndex)

                            let updatedLine = this.quill.getLine(lineIndex)[0]
                            lineText = updatedLine.domNode.textContent

                            break
                        }
                    }
                }
            }
        })

@sachinrekhi
Thank you for reporting a bug with a great solution.
I will check in detail and fix it as soon as possible.
Sorry for inconvenience :(

@morishjs By the way, do you know why the following line appears in a lot of the matchers? I don't quite get what this is specifically avoiding?
if (text.match(/^([*_ \n]+)$/g)) return;

@sachinrekhi
For a bold formatting case, the following string will be converted to an empty string and then turning on bold formatting.
** ** => (empty string)

I am seriously considering removing it because I can't give anyone else compelling reason.

Got it! Thanks for the explanation.

@sachinrekhi
Thank you for contributing to this repository. I've fixed the error, so please make sure the program works as you expected.
Updated version is v0.1.3.


Tooltip for medals on Osekai Medals app triggering earlier than user hovers on medal

Not hovered:

Hovered:

this is because tippy is added to the div, not the img itself, should be an easy fix


Progress on the rewrite for older cards (Like the P40)

Was wondering what the current progress was on the rewrite and if this could be turned into some sort of tracker for it? optimizations for the P40 seems to be something many would like

I think V2 is in the works. Not sure if it will have support for P40 but then again, you have llama.cpp that is all FP32 and I can run Q5KM and Q6 quants on it. If you apply the peer access patch it even does direct transfers on linux. For nvlink it's faster than exllama. Some downsides in how it processes prompts but other than that, you can use it today.


Make selectable date range to be minimum 7 days

Why do we need this ?

We need the minimum date range to be 7 days because the data for less than 7 days is not retrospective or actionable.

Acceptance Criteria

[ ] Make minimum selectable date range to be 7 days

Further Comments / References

May I work on this issue?

@jayantbh  Hey can help me navigate which files to look into ?

Sure! You'll want to look into components/DateRangePicker to start with.

@jayantbh  can you assign this to me ?

Done! Go ahead!

@jayantbh  hey can you look into #428 as it solves this issue

Got it! The PR looks good! Approved.
We can go ahead.


Search gives unexpected results if item names contain dash character

Currently, dash character is defined as non-word character and it results into following search oddities:
$ knife node create mysql -d -z
Created node[mysql]
$ knife node create mysql-slave -d -z
Created node[mysql-slave]
$ knife search node 'name:mysql' -a name -z
2 items found

mysql:
  name: mysql

mysql-slave:
  name: mysql-slave

$ knife search node 'name:mysql?slave' -a name -z
0 items found

$ knife search node 'name:mysql-?lave' -a name -z
1 items found

mysql-slave:
  name: mysql-slave

:+1: We met same problem.

@sawanoboly simple fix is avialable in https://github.com/chef/chef-zero/pull/158, could you vote for that PR?

PR is now merged, thanks for the report and the fix.


'kubectl desc' shortcut for 'kubectl describe'

Kubernetes version (use kubectl version): 1.8
Feature Request to have kubectl describe to support the shorted form kubectl desc, in a similar way that you can kubectl get po instead of kubectl get pods.

You can use kubectl plugin as follows:
$ cat <<'EOL' >kubectl-desc
#!/bin/sh
exec kubectl describe $@
EOL
$ chmod +x kubectl-desc
$ sudo mv kubectl-desc /usr/local/bin/
$ kubectl desc po nginx

kubectl plugin was implemented in kubectl 1.12, so you need to upgrade kubectl. See https://kubernetes.io/docs/tasks/extend-kubectl/kubectl-plugins/ for more details.

/close

Thanks

Hi -- I think this would be something easy to implement, and regret this being rejected. The proposed solution via a plugin works, but needs to be done for each machine running kubectl.
Save our fingers!
F.

I agree @brunzefb, but you have to love the workaround @superbrothers is suggesting!


Build results for poky morty and meta-ros

I have tested bitbake core-image-ros-world on the current poky morty release with all machines in that yocto release. The exact build configurations are listed below. None of them failed with errors, and the builds only emitted some warnings.
When downloading sources, bitbake warns:
WARNING: libpng-native-1.6.24-r0 do_fetch: Failed to fetch URL http://distfiles.gentoo.org/distfiles/libpng-1.6.24.tar.xz, attempting MIRRORS if available
WARNING: python-urlgrabber-3.9.1-r0 do_fetch: Checksum mismatch for local file /home/lukas/dev/yoctoproject.org/poky/morty/build/downloads/urlgrabber-3.9.1.tar.gz
Cleaning and trying again.
WARNING: python-urlgrabber-3.9.1-r0 do_fetch: Renaming /home/lukas/dev/yoctoproject.org/poky/morty/build/downloads/urlgrabber-3.9.1.tar.gz to /home/lukas/dev/yoctoproject.org/poky/morty/build/downloads/urlgrabber-3.9.1.tar.gz_bad-checksum_63424f4e3675c8df474bd5bcac1f4790
WARNING: python-urlgrabber-3.9.1-r0 do_fetch: Checksum failure encountered with download of https://pypi.python.org/packages/source/u/urlgrabber/urlgrabber-3.9.1.tar.gz - will attempt other sources if available

Bitbake emits these eight warnings on all build configurations for the different machines:
WARNING: imu-transformer-0.2.1-r0 do_populate_lic: imu-transformer: No generic license file exists for: GPL in any provider
WARNING: ivcon-0.1.5-r0 do_populate_lic: ivcon: No generic license file exists for: GPL in any provider
WARNING: sphinxbase-0.8-r0 do_package_qa: QA Issue: sphinxbase rdepends on libasound, but it isn't a build dependency, missing alsa-lib in DEPENDS or PACKAGECONFIG? [build-deps]
WARNING: poco-1.7.4-r0 do_package: poco-1.7.4 was registered as shlib provider for libCppUnit.so.1, changing it to poco-cppunit-1.7.4 because it was built later
WARNING: velodyne-driver-1.2.0-r0 do_package_qa: QA Issue: /opt/ros/indigo/lib/velodyne_driver/vdump contained in package velodyne-driver requires /bin/bash, but no providers found in RDEPENDS_velodyne-driver? [file-rdeps]
WARNING: core-image-ros-world-1.0-r0 do_rootfs: The license listed GPL was not in the licenses collected for recipe imu-transformer
WARNING: core-image-ros-world-1.0-r0 do_rootfs: The license listed GPL was not in the licenses collected for recipe ivcon
WARNING: core-image-ros-world-1.0-r0 do_rootfs: [log_check] core-image-ros-world: found 2 warning messages in the logfile:
[log_check] WARNING: The license listed GPL was not in the licenses collected for recipe imu-transformer
[log_check] WARNING: The license listed GPL was not in the licenses collected for recipe ivcon

The warnings due to the meta-ros recipes are all tracked in the issue tracker, i.e., imu-transformer: #440, ivcon: #264, sphinxbase: #441, velodyne-driver: #442. The do_rootfs warnings are due to #264 and #440.
The bitbake build for the qemumips64 machine further emits this warning, which is unrelated to meta-ros:
---------- CONFIG_CPU_MIPSR2 -----------------
Config: CONFIG_CPU_MIPSR2
From: /home/lukas/dev/yoctoproject.org/poky/morty/build/tmp/work-shared/qemumips64/kernel-source/.kernel-meta/configs/standard/mti-malta64/bsp/mti-malta64/mti-malta64-common.cfg
Requested value:  # CONFIG_CPU_MIPSR2 is not set
Actual value:

Config 'CPU_MIPSR2' has the following conditionals:

Dependency values are:

The common build configuration is:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
[...]
DISTRO            = "poky"
DISTRO_VERSION    = "2.2"
[...]
meta
meta-poky
meta-yocto-bsp    = "morty:73454473d7c286c41ee697f74052fed03c79f9f5"
meta-oe
meta-python
meta-multimedia   = "morty:659d9d3f52bad33d7aa1c63e25681d193416d76e"
meta-ros          = "master:0a9f44d830f1c4fa560c5b8eabb02ff0706c9b00"

Build Configuration for qemux86:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""

Build Configuration for qemuarm:
NATIVELSBSTRING   = "universal"
MACHINE           = "qemuarm"
TUNE_FEATURES     = "arm armv5 thumb dsp"
TARGET_FPU        = "soft"

Build Configuration for qemuarm64:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "aarch64-poky-linux"
MACHINE           = "qemuarm64"
TUNE_FEATURES     = "aarch64"
TARGET_FPU        = ""

Build Configuration for qemumips:
NATIVELSBSTRING   = "Fedora-23"
TARGET_SYS        = "mips-poky-linux"
MACHINE           = "qemumips"
TUNE_FEATURES     = "o32 bigendian fpu-hard mips32r2"
TARGET_FPU        = ""

Build Configuration for qemumips64:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "mips64-poky-linux"
MACHINE           = "qemumips64"
TUNE_FEATURES     = "n64 bigendian fpu-hard"
TARGET_FPU        = ""

Build Configuration for qemuppc:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "powerpc-poky-linux"
MACHINE           = "qemuppc"
TUNE_FEATURES     = "m32 fpu-hard ppc7400 altivec"
TARGET_FPU        = ""

Build Configuration for qemux86-64:
NATIVELSBSTRING   = "Fedora-23"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "qemux86-64"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""

Build Configuration for beaglebone:
NATIVELSBSTRING   = "Fedora-23"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "beaglebone"
TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU        = "hard"

Build Configuration for genericx86:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i686-poky-linux"
MACHINE           = "genericx86"
TUNE_FEATURES     = "m32 core2"
TARGET_FPU        = ""

Build Configuration for genericx86-64:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "genericx86-64"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""

Build Configuration for mpc8315e-rdb:
NATIVELSBSTRING   = "Fedora-23"
TARGET_SYS        = "powerpc-poky-linux"
MACHINE           = "mpc8315e-rdb"
TUNE_FEATURES     = "m32 fpu-hard ppce300c3"
TARGET_FPU        = ""

Build Configuration for edgerouter:
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "mips64-poky-linux"
MACHINE           = "edgerouter"
TUNE_FEATURES     = "n64 bigendian fpu-hard"
TARGET_FPU        = ""

@bulwahn < I was hoping not to have to support OpenEmbedded releases prior to thud. If this is OK, please close this issue.

"Silence implies consent" (see http://wiki.c2.com/?SilenceImpliesConsent).


[Bug] Same code and enviroment A800 succeed but A10 failed

Checklist

[x] 1. I have searched related issues but cannot get the expected help.
[x] 2. The bug has not been fixed in the latest version.
[x] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.

Describe the bug

I use the same code and enviroment with different GPU(A10, A800), A800 succeed but A10 failed.
A800 didn't show the progress "Convert to turbomind format".
Reproduction
backend_config = TurbomindEngineConfig(dtype="float16", tp=1, session_len=4096)
gen_config = GenerationConfig(n=1,
top_p=1,
top_k=1,
temperature=0.0,
max_new_tokens=512,
do_sample=False,
random_seed=3407,
min_new_tokens=1,
stop_words=[self.tokenizer.eos_token,'<|im_end|>'],
skip_special_tokens=True)
model = pipeline(model_path="InternVL2_5-8B", backend_config=backend_config)
Environment
lmdeploy==0.6.4
transformers==4.46.3
timm==1.0.12
cuda 12.5
flash-attn-2.6.3
torch-2.4.0

Error traceback
/usr/local/lib/python3.10/dist-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
InternLM2ForCausalLM has generative capabilities, as `prepare_inputs_for_generation` is explicitly overwritten. However, it doesn't directly inherit from `GenerationMixin`. From 👉v4.50👈 onwards, `PreTrainedModel` will NOT inherit from `GenerationMixin`, and this model will lose the ability to call `generate` and other related functions.
  - If you're using `trust_remote_code=True`, you can get rid of this warning by loading the model with an auto class. See https://huggingface.co/docs/transformers/en/model_doc/auto#auto-classes
  - If you are the owner of the model architecture code, please modify your model class such that it inherits from `GenerationMixin` (after `PreTrainedModel`, otherwise you'll get an exception).
  - If you are not the owner of the model architecture class, please contact the model code owner to update it.
[TM][WARNING] [LlamaTritonModel] `max_context_token_num` is not set, default to 4096.
2024-12-17 11:09:38,325 - lmdeploy - WARNING - turbomind.py:231 - get 227 model params
[WARNING] gemm_config.in is not found; using default GEMM algo

Convert to turbomind format:   0%|          | 0/32 [00:00<?, ?it/s]
Convert to turbomind format:   6%|▋         | 2/32 [00:00<00:01, 18.66it/s]
Convert to turbomind format:  16%|█▌        | 5/32 [00:00<00:01, 20.17it/s]
Convert to turbomind format:  25%|██▌       | 8/32 [00:00<00:01, 21.11it/s]
Convert to turbomind format:  34%|███▍      | 11/32 [00:00<00:01, 17.78it/s]
Convert to turbomind format:  44%|████▍     | 14/32 [00:00<00:00, 19.13it/s]
Convert to turbomind format:  53%|█████▎    | 17/32 [00:00<00:00, 20.13it/s]
Convert to turbomind format:  62%|██████▎   | 20/32 [00:01<00:00, 15.02it/s]
Convert to turbomind format:  69%|██████▉   | 22/32 [00:01<00:00, 12.11it/s]
Convert to turbomind format:  78%|███████▊  | 25/32 [00:01<00:00, 14.35it/s]
Convert to turbomind format:  88%|████████▊ | 28/32 [00:01<00:00, 16.24it/s]
Convert to turbomind format:  97%|█████████▋| 31/32 [00:01<00:00, 17.76it/s]

terminate called after throwing an instance of 'std::runtime_error'
  what():  [TM][ERROR] pointer_mapping_ does not have information of ptr at 0x7dc2a6000. Assertion fail: /lmdeploy/src/turbomind/utils/allocator.h:284

Looks like OOM during warm-up. You may try to lower max_prefill_token_num or cache_max_entry_count on the A10.


Do not fail pageserver startup because of one broken index_part

This was one of the issues during production outage. This patch turns ? to match around error and an error message.
On the other side this approach allows for other bad thing to happen. Error does not get propagated to timeline registration code which leads to incorrect registration of broken timeline. Which is bad since initial sync for such timeline is skipped.
This part is reworked in on-demand patch so I think main contribution is the test, not the fix itself.

as a restoration attempt

I'm not sure what is the better option.
Option one is to try to correct the error. We can fetch list of files via s3 ls, but we still have only local metadata. It may be possible that other pageserver updated medatada with higher disk consistent lsn and we wont be able to check that. Theoretically this can lead to remote_consistent_lsn jumping backwards which is not that harmful, but still.
The other option is to mark it as broken and ask for human to investigate. Most likely it is a bug, not a real corruption. Leaving things as they are will help to investigate the issue.
I'm leaning towards second option, but it needs more changes that intersect with on-demand PR since RemoteIndex is completely removed there.


Deploy serverless function in development enviornment

Hi, is there a way to deploy serverless function without building all cvat images before?

Serverless functions are deplyoed independent of CVAT instance.
Please, follow the documentation: https://openvinotoolkit.github.io/cvat/docs/contributing/setup-additional-components/


The frame list shouldn't scroll sideways

This is a really minor one, but anyway.
Steps:

create some frames
start dragging a frame
move it towards the right

On Firefox at least (haven't tested elsewhere): the frames list scrolls slightly to the left (even though there's no scrollbar). As a result, the left border of the frames isn't visible anymore.

Released in v0.7.0


APP6D. Land equipment. incorrect icons

Could you please fix icons for Land equipment for APP6D
Actual result:

Expected:

Fixed in master branch, will update the unit generator in the next update.

thanks


TextRecognition iOS error

Hello, I'm getting "Input image must not be nil" on iOS. I'm using RNFS.TemporaryDirectoryPath, also tried RNFS.DocumentDirectoryPath. It's working using Android. Any idea? Should I add some permission or capability?

Ok, i found the problem. i should add file:// as a prefix for ios


How to upload res folder into Flash

How to upload res folder into Flash,It seems that folder is not supported by spiflashfs

Py exported to maixpy_spiffs_image.py exported to maixpy_spiffs_img and fired it into firmware Flash. Until then, we still use SD card to complete the function development.

python gen_spiffs_image.py ../../projects/maixpy_k210/config_defaults.mk

image.Image("/flash/res/icons/app_camera.bmp")


NO-JIRA: always set minAvailable on PDBs to 1

We are currently experiencing issues in CI when the autoscaler scales down the cluster and evicts pods from actively running mgmt clusters running prow jobs.  These mgmt clusters run SingleReplica to save on resources and can not tolerate being evicted without control plane downtime.  Depending on when this downtime occurs during the job, it frequently causes flakes.
Setting minAvailable to 1 on deployments that are required for smooth running of the KAS (etcd, kas itself, aggregated apiservers, and ingress to the kas) will prevent these pods from being evicted until the jobs complete.

/lgtm
/approve

/test e2e-aws


Update aws-core, http-client-spi, ... to 2.17.44

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.42 to 2.17.44.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #537.


Issues on versions > 0.36.4

Describe the bug
I received different functionality with the same miners using 0.36.4 vs. 0.36.5.
To Reproduce
Steps to reproduce the behavior:
Install pyasic 0.36.5 via
python3.8 -m pip install pyasic==0.36.5
Use pyasic in a script
Steps to reproduce the behavior:
Install pyasic 0.36.4 via
python3.8 -m pip install pyasic==0.36.4
Use pyasic in a script
Expected behavior
Gives back appropriate data from the api, 0.36.5 I would assume works with more miners than older versions, however my script stops on 0.36.5 with key error, whereas 0.36.4 the same script will save to a database data relative to other miners.
Desktop (please complete the following information):

OS: [e.g. iOS]
Ubuntu 18.04 using python3.8

Additional context
0.36.5 output:
/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/types/whatsminer/M5X/M56S.py:28: UserWarning: Unknown chip count for miner type M56S VH30, please open an issue on GitHub (https://github.com/UpstreamData/pyasic).
  warnings.warn(
/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/06/23 23:25:25](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0
Traceback (most recent call last):
  File "./main.py", line 33, in <module>
    miner_data = asyncio.run(get_miner(miner_ip))
  File "/usr/lib/python3.8/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 608, in run_until_complete
    return future.result()
  File "./main.py", line 24, in get_miner
    miner_data = await miner.get_data()
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/base.py", line 501, in get_data
    gathered_data = await self._get_data(allow_warning, data_to_get=data_to_get)
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/base.py", line 454, in _get_data
    miner_data[data_name] = await function(**args_to_send)
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/backends/bmminer.py", line 172, in get_fw_ver
    api_version = await self.api.version()
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py", line 86, in version
    return await self.send_command("version")
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/__init__.py", line 86, in send_command
    validation = self._validate_command_output(data)
  File "/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/__init__.py", line 246, in _validate_command_output
    elif data["STATUS"][0]["STATUS"] not in ("S", "I"):
KeyError: 0

0.36.4 output:
/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/types/whatsminer/M5X/M56S.py:28: UserWarning: Unknown chip count for miner type M56S VH30, please open an issue on GitHub (https://github.com/UpstreamData/pyasic).
  warnings.warn(
/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/06/23 23:26:52](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0
/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/06/23 23:26:56](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0

For some reason the data being returned from that specific miners API doesn't return the result status in the correct place.  I can try to handle for this, what type of miner is the one having the error (<IP_ADDRESS>)?
As an aside, pyasic is still very much in development, and breaking changes tend to happen a lot.  Semantic versioning information states that in 0.x.x versions, non backwards compatible API changes may also happen.  That being said, if you need it to be stable for any given environment, I highly recommend pinning your version to a specific version, such as pyasic==0.36.10.

I have tracked down to 2 miners that are having the issues, I've been able to incorporate 0.36.10 using exception handling on the miner.get_data() function.
2 miners in question:
Name: Antminer S19j Pro (104TH)AMCB07
Firmware version: <IP_ADDRESS>3
Name: Antminer S19 XPA113D
Firmware version: <IP_ADDRESS>1
The error I'm receiving for these two miners as follows:
/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/07/23 00:08:13](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0
Exception: 0 on <IP_ADDRESS>
/home/administrator/.local/lib/python3.8/site-packages/pyasic/miners/types/whatsminer/M5X/M56S.py:28: UserWarning: Unknown chip count for miner type M56S VH30, please open an issue on GitHub (https://github.com/UpstreamData/pyasic).
  warnings.warn(
/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/07/23 00:08:17](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0

Let me know any other debuggin information you need, this is on Ubuntu 18.04 with python3.8.0, Thanks.

Here's the call stack and local variables while debugging and stuck on .145:

Interesting.  That all looks basically correct.  Can you test a few things:

Does the miner type pyasic returns from get_miner match the real miner type?  You can call print(await pyasic.get_miner(IP)) to check this.  I'm not certain if something is off about the AMLogic CB or possibly they're different somehow.
What is the result of the version command with errors off, and maybe some other commands too for reference?  These can be acquired with print(await miner.api.send_command("version", ignore_errors=True)).  If you could do this with the "version" command and the "devdetails" command that would help.

Nah it's just returning {}

/home/administrator/.local/lib/python3.8/site-packages/pyasic/API/bmminer.py:72 in _x19_multicommand
[WARNING][07/07/23 00:49:33](root) - BMMinerAPI: <IP_ADDRESS> - ([Hidden] X19 Multicommand) - API Command Error 0
Exception: 0 on <IP_ADDRESS>
{}

I'm unsure what miner object you are talking about, here is how my code looks

async def scan_miners():
    network = MinerNetwork("<IP_ADDRESS>")
    miners = await network.scan_network_for_miners()
    ##print(miners)
    return miners

async def get_miner(miner_ip):
    miner = await MinerFactory().get_miner(miner_ip)
    try:
        miner_data = await miner.get_data()
        return miner_data
    except Exception as ex:
        print(f"Exception: {ex} on {miner_ip}")
        return {}
    ##print(miner_data)

if __name__ == "__main__":
    miners = asyncio.run(scan_miners())
    miner_ips = re.findall(r'\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b', format(miners))
    miners_data = []
    for miner_ip in miner_ips:
        ##print(asyncio.run(get_miner(miner_ip)))
        miner_data = asyncio.run(get_miner(miner_ip))
        if miner_data:
            miners_data.append(miner_data)

Here's a script that will test what I want to check:
import pyasic
import asyncio

NETWORK = pyasic.MinerNetwork("<IP_ADDRESS>")

ERR_MINERS = ["<IP_ADDRESS>", "<IP_ADDRESS>"]

async def main():
    print("[TEST]: SCAN & DATA")
    # test scanning and data
    miners = await NETWORK.scan_network_for_miners()
    await asyncio.gather(*[get_miner_data(m) for m in miners])
    await asyncio.gather(*[devdetails_and_version(m) for m in miners])

    print("[TEST]: DEVDETAILS & VERSION")
    # test erroring miners
    miners = await asyncio.gather(*[pyasic.get_miner(ip) for ip in ERR_MINERS])
    await asyncio.gather(*[get_miner_data(m) for m in miners])
    await asyncio.gather(*[devdetails_and_version(m) for m in miners])

async def get_miner_data(m: pyasic.AnyMiner):
    try:
        print(m, "[SUCCESS]:", await m.get_data())
    except Exception as e:
        print(m, "[ERROR]:", e)

async def devdetails_and_version(m: pyasic.AnyMiner):
    try:
        tasks = [m.api.send_command(cmd, ignore_errors=True) for cmd in ["devdetails", "version"]]
        print(m, "[SUCCESS]:", await asyncio.gather(*tasks))
    except Exception as e:
        print(m, "[ERROR]:", e)

if __name__ == '__main__':
    asyncio.run(main())

Apologies for the issue, we are utilizing a proprietary firmware that doesn't match the API call, closing issue.

That's no problem.  I can work on adding support for it if you want, but we would likely need to work more closely on gathering information.
You are also welcome to extend pyasic if you prefer, just create a class that inherits from BaseMiner.

Thank you @UpstreamData for the information, I believe we are going to pull our own version of Pyasic and incorporate our API into it, I greatly appreciate you giving me a leg up by recommending inheriting from BaseMiner.

No problem.  Feel free to hit me up if you have any questions or need help!

Hey this commit ended up solving my issues with this request/issue:
https://github.com/UpstreamData/pyasic/compare/master...Devinmara:pyasic_ml:master
From testing it appears to work with other miners still as well.

Re-opening.
Looked at the code, it looks good, but I think it should be -
if isinstance(data["STATUS"], dict):
I'll see if I can implement this tonight.

Sounds good man, i've been making modifications in my own branch but would love for this to be upstream so my codebase doesn't get as messy I can just keep updated pyasic :) thanks for your hard work!

Hey this commit ended up solving my issues with this request/issue: master...Devinmara:pyasic_ml:master From testing it appears to work with other miners still as well.

Done.  Pushing out version 0.38.1 with the changes.

working as expected.


Server builder plugin

Provide a scalable mechanism to add default services/functionality to servers without modifying include dependencies of existing files.

LGTM
Please resolve conflicts.


When our server goes away it should kill clients gracefully.

Currently clients disconnect cleanly, but a server-exit is less forgiving.  See also #3 .

Clients now timeout after 2 x $heartbeat seconds.


Last Check for today

Please also see if you can also integrate Choose Directory Prompt while entering the directory instead of asking the user to write the path


Issue with /docs/concepts/workloads/pods/init-containers/

This is a...

[ ] Feature Request
[ x ] Bug Report

Problem:
Init containers doc has not been updated for 1.6.  Examples still use 1.5 annotations and don't show the new syntax.
Proposed Solution:
Update examples for 1.6.
Filing this bug mostly so that I remember to submit a patch.
Page to Update:
http://kubernetes.io/...

https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#init-containers-in-use
This section should explicitly have an example showing the 1.6 version (init container field) in addition to the existing example for pre-1.6
It should also call them out explicitly.
@crimsonfaith91, Can you send a PR updating docs here?

@foxish sure! :)

/assign @crimsonfaith91

@jberkus I am working on this issue. Apart from changing to 1.6 syntax for YAML files, I am thinking about showing services.yaml, or give a link to it. Where should I find the YAML file?
Is the line i11:32 $ kubectl describe -f examples/init-container.yaml a typo?

@crimsonfaith91 not sure what you mean with services.yml?  Why would you need to show that?

@jberkus I apologize for getting back to you late.
I am working on updating: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#init-containers-in-use
In the tutorial, there are a code snippet:
$ kubectl create -f services.yaml   service "myservice" created   service "mydb" created
As it mentions about services.yaml, i am thinking whether we need to include it (or a link to it) for easy reference by readers. However, i am not sure where should i find one (or have to create my own).
Tell me if i should work on another section of the tutorial. Thanks!

Oh, yeah, I think you're right, we really need an example service.yaml file there because that's just confusing.  We'd have to create one from scratch, though, since that's just a dummy example.

I see. I will create services.yaml from scratch too.
I plan to include both 1.5 and 1.6 YAML files as there are clients using 1.5. Will it be fine?

I am able to create services.yaml and update the syntax of myapp.yaml to 1.6.
I will make a PR tomorrow. :)

Looks good to me.  Closing issue. Thanks so much!


SC4S failed to start because there is another container with same NAME

Was the issue replicated by support?
No
What is the sc4s version ?
Latest , but it doesn't aligned with version
Which operating system (including its version) are you using for hosting SC4S?
Linux Debian Based
Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S?
Docker / Podman
Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support?
No
Is the issue related to the environment of the customer or Software related issue?
No
Is it related to Data loss, please explain ?
Protocol? Hardware specs?
Yes because
Last chance index/Fallback index?
No index related
Is the issue related to local customization?
No
Do we have all the default indexes created?
Not index related
Describe the bug
From our company we manage several SC4S based on docker in different entities that we support.
Lately we have found in several of them that the SC4S system fails to lift, indicating error that there is already a SC4S container. When running the command systemctl start sc4s.service it fails indicating that there is already another container with the name SC4S.
The solution is to
docker container rm SC4S
systemctl start sc4s.service
This has always happened when due to power problems or CPD downtime, has caused the virtual machine has suffered an outage and therefore the container has not been deleted as when the sc4s service is stopped.
The solution we have found is to execute those commands, but we have also thought of putting the following line in the sc4s.service file
Adding this line before docker run
ExecStartPre=sh -c 'docker container rm SC4S || /bin/true'
[Unit]
Description=SC4S Container
Wants=NetworkManager.service network-online.target docker.service
After=NetworkManager.service network-online.target docker.service
Requires=docker.service

[Install]
WantedBy=multi-user.target

[Service]
Environment="SC4S_IMAGE=ghcr.io/splunk/splunk-connect-for-syslog/container3:latest"

# Required mount point for syslog-ng persist data (including disk buffer)
Environment="SC4S_PERSIST_MOUNT=splunk-sc4s-var:/var/lib/syslog-ng"

# Optional mount point for local overrides and configurations; see notes in docs
Environment="SC4S_LOCAL_MOUNT=/opt/sc4s/local:/etc/syslog-ng/conf.d/local:z"

# Optional mount point for local disk archive (EWMM output) files
Environment="SC4S_ARCHIVE_MOUNT=/opt/sc4s/archive:/var/lib/syslog-ng/archive:z"

# Map location of TLS custom TLS
Environment="SC4S_TLS_MOUNT=/opt/sc4s/tls:/etc/syslog-ng/tls:z"

TimeoutStartSec=0

ExecStartPre=/usr/bin/docker pull $SC4S_IMAGE

# Note: /usr/bin/bash will not be valid path for all OS
# when startup fails on running bash check if the path is correct
ExecStartPre=/usr/bin/bash -c "/usr/bin/systemctl set-environment SC4SHOST=$(hostname -s)"

ExecStartPre=sh -c 'docker container rm SC4S || /bin/true'
ExecStart=/usr/bin/docker run \
        -e "SC4S_CONTAINER_HOST=${SC4SHOST}" \
        -v "$SC4S_PERSIST_MOUNT" \
        -v "$SC4S_LOCAL_MOUNT" \
        -v "$SC4S_ARCHIVE_MOUNT" \
        -v "$SC4S_TLS_MOUNT" \
        --env-file=/opt/sc4s/env_file \
        --network host \
        --name SC4S \
        --rm $SC4S_IMAGE

Restart=on-abnormal

To Reproduce
Steps to reproduce the behavior:

Create a container with same name using docker run command or using sc4s.service (but poweroff without tools the VM)
Try to start / restart sc4s.service
Modify sc4s.service and add line before docker run

ExecStartPre=sh -c 'docker container rm SC4S || /bin/true'

See that container starts fine.

@guillerg86 thanks for reporting. Probably will be better use ExecStop and ExecStopPost instead of ExecStartPre, because you know when you using ExecStartPre during first run you will got an error about can't rm container that not exists, I think it's very strange.
Can you test it please:
ExecStop=/usr/bin/docker stop SC4S
ExecStopPost=/usr/bin/docker rm SC4S

@guillerg86 also probably we can use restart flag for docker run

The problem about this "ExecStop" is when VM or machine was stopped without executing stop (electrical outage, etc...) thats why I thought is better do on PRE with || /bin/true
If container doesn't exist, pipe will make continue the script.
I've tested this solution (execstartpre) on a 5 clients and works fine. If VM stops suddently or because an outage, it doesn't remove the container (on stop) but before executing docker run, the service will remove the existent container if exists.

@guillerg86 okay I will check with VM stop

Thanks!

The solution is excellent and can be added to main @ikheifets-splunk

It will be added to main with next release.


Added the Dark theme toggle

Please, go through these steps before you submit a PR.

[x] My Pod Leader knows I'm working on this Pull Request
[x] I've explained what the Pull Request is adding.
[x] I've explained why this is important.

Fixes issue #14
We have added a responsive dark theme toggle . It also supports the system default theme.
Screenshots:

Co-authored by @k-abirami

Hey, looks pretty good! The button just seems to be oddly positioned, can you fix that and I'll merge it!

Hey @akshgpt7 , I have changed the position of the toggle to the bottom of the page.

Works so well! Thanks for picking this up.


Add set_scale and set_offset to Rasterband

[X] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

bors r+


[presto] Using $(hostname -s) rather than ${HOSTNAME}

Recent change in the hostname implementation has required that we find short hostname using a different mechanism.  This patch makes that change.

/gcbrun

readonly PRESTO_MASTER_FQDN="$(/usr/share/google/get_metadata_value attributes/dataproc-master)"
@cjac - Can we change the variable name since value doesn't contain FQDN?

/gcbrun

/gcbrun


Datadog Cluster Agent warning about CronJob deprecation

batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob

Tested with cluster-agent 1.16.0 and Kubernetes v1.21.6.

As well as this:
policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

Please fix this, its spamming our log and as you might already know ... we have to pay for each log entry. its not nice to let your customers pay for problems you cause with your own software!

I'm having the same issue, and I'd gladly look for a way to use new API versions, but the problem is - I don't have deprecated resources in the cluster 🤔
$ k get poddisruptionbudgets.policy --all-namespaces -o json | jq '.items[].apiVersion'
"policy/v1"
$ k get cronjob --all-namespaces -o json | jq '.items[].apiVersion'
$ # No cronjobs in the cluster

Fixed in https://github.com/DataDog/datadog-agent/pull/11126

Hi! Although warnings should be silenced, there are still calls/logs to removed API made:

As this issue is still opened - are there any updates on this?
(GKE) Kubernetes Version: "1.26.10-gke.1101000"
Helm Release Version: "3.1.9"
Datadog Cluster Agent/Agent Version: "7.39.0"


CI against Ruby 2.2.8, 2.3.5, and 2.4.2

These Ruby versions are released.
https://www.ruby-lang.org/en/news/2017/09/14/ruby-2-4-2-released/
https://www.ruby-lang.org/en/news/2017/09/14/ruby-2-3-5-released/
https://www.ruby-lang.org/en/news/2017/09/14/ruby-2-2-8-released/

CI is broken. Do you mind to take a look in a different PR?


AppSource/New-AppSourceSubmission.ps1

When the Appsource Submission fails the scripts does not give an error. It only shows a line in the console that there was a failure.

Is it possible to add an error when then submission fails.
Or is there another way to catch this failure in our pipeline?

I found how to check it. Sorry for bothering you :)

I cannot even remember how - if you could add your solution (for other people to find) and close the issue?

new app version submission
$submission = New-AppSourceSubmission -authContext $authContext                           -productId $product.Id
-appFile $mainAppFilePath                           -libraryAppFiles $libraryFiles
-autoPromote `
-doNotWait
$submissionID = $submission.id
if ($submissionID.substate -eq "Failed") {
Write-Host  "##vso[task.LogIssue type=error;]Appsource submission $submission.id failed"
Write-Error "Appsource submission $submission.id failed"
}

This will tell you if the submission failed - not if the validation failed - right?