Feature/git blame layer

Given the functionality was almost there I decided to try my hands at a git blame layer. The idea being to emulate a little the vscode GitLens git blame functionality. What this adds is a git blame per line, when the user is resting on the line like the hover tool tip.
It renders inline if there is space otherwise it renders above the line in a tooltip like container.

EDIT: Removed the popup as this was in an awkward position (competing with the hover tooltip) instead the layer now renders the highlight on the given line if the space is too small it begins to truncate the blame summary if still too large it renders the summary in the earliest previous empty space (possibly overkill to have so many layers to try and preserve rendering on depending on screen space but as someone who works on a laptop it seemed worth the effort)
Outstanding:

[x] Tests
[x] Configuration: experimental flag, off by default, enabled: auto i.e. per new line after a wait of a configurable amount of time, manual i.e. triggered manually per line via a key binding

Very cool! 😄

Change looks good to me! Great work @Akin909 - really like the way you architected this functionality.
Minor feedback on the look - I'm wondering if it makes sense to right-align the blame text?

But I'm fine if that comes in separately, we can always tweak the styling later 👍

I enabled this a few days ago and it's working wonderfully.  I really like how it finds nearby whitespace to render into - much less invasive than a pop-up that obscures code, or a split that reduces available window width.
My one issue is that I use Oni with two vertical splits.  This doesn't leave much room, and most of the space available is taken up with the author and time, when for me the message is more useful.
Perhaps a future tweak would be some configuration as to the ordering of the fields?  Maybe that can already be done with "experimental.vcs.blame.mode" config option?  I haven't had chance to dive into the code to see what that does, though.


External LM rescoring decode script is getting killed

Following up on this #380 @vsl9 @borisgin @blisc Have followed the steps 1-3 here and everything went smooth. But launching python scripts/decode.py --logits=<path_to>/model_output.pickle --labels=<path_to>/librivox-train-clean-100.csv --lm=<path_to>/4-gram.binary  --vocab=open_seq2seq/test_utils/toy_speech_data/vocab.txt --alpha=2.0 --beta=1.5 --beam_width=512 --dump_all_beams_to=<path_to>/beams.txt with respective alpha beta and beam_width values just kills the script instantly for some unknown reason. My output looks something like this:
# empty preds: 0 Greedy WER = 0.0025 Killed
after running the script multiple times in eval mode. Do you think the beam_width value used here is an overkill for my memory? I am running on a single GPU instance of 12 GB memory. Your thoughts on this will help me. Thank you :+1:

Adding to the above steps is it required to run the step 4 also ? Since I can see that in run_lm_exp.sh it is iterating over the checkpoints and then taking in the beam_dumps obtained from step 3 which itself is failing in my case. Could you please explain what is happening under the hood while performing these steps ?

Have you have any success with smaller beam widths? You can also try removing the --dump_all_beams_to=BEAMS.txt parameter.
Step 2 uses a pretrained speech model to get the predicted character logits per time step for each sound file.
Step 3 uses the outputs of step 2 and first does greedy decoding, and then will run beam search decoding rescoring with the given n-gram LM. If you give a range of alpha and beta, it will run grid search over all values. Otherwise in most cases, it will just run beam search with the provided alpha and beta. It will also dump the most probable candidates for each sound file if dump_all_beams_to is provided.
Step 4 takes the candidates from step 3 and uses T-XL to rescore each candidate and outputs the most probable one (the most probable one is just a linear combination of the score from Step 3 and the output of T-XL).

@blisc I have tried smaller beam widths but still no luck :disappointed: I shall also try removing the --dump_all_beams_to option and let you know. As per your explanation of the different steps, if I were to now train my model on a completely different dataset it does not matter during training time whether I have enabled ctc_decoder_with_lm option in my model config. I shall still be able to do re-scoring using the above mentioned technique provided I have a trained model. Right?

You should not enable use_language_model during training. All of the current decoder params are deprecated.
Your trained model will be able to make use of the re-scoring and new decoder script.
The new decoder script will make use of all available CPU cores, perhaps your instance is killing your script due to high CPU or CPU memory usage? An alternative would be to use a cloud instance for steps 2 and 4 on the cloud instance and step 3 on a local machine.

scripts/decode.py doesn't use GPUs, it is CPU only. Insufficient system RAM might be the issue. Have you tried to decrease beam_width to very small value and then increase it gradually (like 2, 8, 16, 64, 128)? Or maybe there was a problem with the decoder's installation (scripts/install_decoders.sh).

Hi, Is there any update on this one? I am getting a similar issue when I run on 71k files of about 51 hours of data.

A small hack which I did was to run the files in smaller batches which dint caused any issue with the same beam width.


problem when installing rife

Hi, every time i try to git colne the repository it gives me the following error
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Can anyone help? thank y all for your precious time and i have to say to the developer/developers of this porject that they did an amazing work as i saw the samples

try git clone https://github.com/hzwer/arXiv2020-RIFE instead

This worked, thanks mate


PS v7 points to PS v6 docs

As per the below Screenshot from PSv7 there is still a pointer to PSv6 Docs

this should be changed prior to v7 becoming GA

There's a PR that changes this to https://aka.ms/powershell.


Fix tag typos

What type of PR is this?
/kind bug
/kind rule-update
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
Some rules currently use "mitre_defense_evation" tag instead of the correct tag of "mitre_defense_evasion". Other rules use the correct tag. Anything matching against these tags would currently need to check for both.
Which issue(s) this PR fixes:

Fixes #1142
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

"mitre_defense_evation" tag corrected to "mitre_defense_evasion"

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kaizhe
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

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

Welcome @sporkmonger! It looks like this is your first PR to falcosecurity/falco 🎉

LGTM label has been added.  Git tree hash: 8a41a4be852c497b402134318d7cb5369b70305f

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

Needs approval from an approver in each of these files:

rules/OWNERS [leodido]

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

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

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leodido]

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

Thanks a lot @sporkmonger


Add language support.

Now users can pass desired language to detect font loaded.
FontDetect.onFontLoaded(fontname, callback [, onFail: xxx, {msInterval: yyy, msTimeout: zzz, lang:'fa'}]);

This is an excellent idea! See the comments for some small changes (naming of variables, mostly, and a data check). Then we can merge this.

Hi Jennifer,
First of all, Happy New Year to you.
I made the fixes you mentioned in above comments. If everything is okay, please merge them.

Thanks, Ahmad; it looks like one line still needs to be changed.

I've change that line and also I've added eLang section in README,md


My thoughts on this project

Hey Andrea! Thanks for the merge on #2. To answer your question, yes I am currently using the plugin; I have incorporated it into a 3-service microservice sbt build. My opinions on the project? Beyond that I found it cool enough to start using...

I think it's a great idea. Something like this is absolutely necessary for building play/scala microservices while maintaining the benefits of type safety.
I'm struggling with how to generating model definitions that are shared between many API specs. For example I could have a users microservice and a companies microservice, with corresponding users.yaml and companies.yaml.  I want both User and Company to use a custom URN as an ID rather than just a Long or a String. However I can't see any way to define a URN in another swagger file (with its own package name) and then use it in my direct API swagger files. This could be because I'm new to swagger.
I think the codegen has a long way to go before actually matching some of the more obscure corners of the swagger spec. (e.g. models that extend "string" instead of "object")
I'm afraid that the one file with all the settings and defaults will become huge as number of configuration options proliferate. There's probably something we can do to simplify that when it becomes a problem.
I'm running into a large number of NPEs even when matching the swagger spec. I haven't been diligent about patching all of them. I'll try to do that moving forward.
I wonder what will happen when new play versions change their APIs? I wonder how the plugin will support the new syntax.

That exhausts most of my thoughts on the topic =)
As a follow-up, what are your plans for building and maintaining this plugin? What's your use-case?

Thanks a lot for sharing your thoughts!
Inheritance and "source merging" on Swagger spec are hot topics also for me!
About the first I've found that polymorphism is supported:
https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md
in section Models with Polymorphism Support
and it is great, in your use case you can define a URN definition and then use it in the rest of your yaml.
Unfortunately the second point is not covered at all from the specification, I've implemented a very rough "yaml source merging" just to avoid stupid errors in generated code, but I think that future work on this project will cover this point in some way.
On corner cases, err..., you are right, especially support for primitive swagger types in body and responses is totally uncovered at the moment, I've developed as a consequence of having to struggle with swagger for a project with short deadlines, so, I've started covering all my use cases.
Probably with a little bit of refactoring of the CodeGen file it will become even easier to implement and cover cases as soon as they are needed.
The new play API looks great! As soon as I have time to upgrade I will try to support it.
This plugin as you can see is under the unicredit umbrella and so we are going to use it in projects and to support it, this is only a starting point and I have colleagues that are going to use and develop with/on it.
At the moment the biggest use case is mine and is a 8 microservices infrastructure to support pricing evaluations, the plugin is used for generating both SPA Api and intra microservices communication too.


Send SOAP WebService Request (Content-Type and Xml Prefix questions)

sorry for the questions, but since i haven't found any serious AL forum yet and i'm struggeling converting C/SIDE to AL... This time it's about a SOAP WebService call from AL to AL, and i have two issues:
How to set the content type to "text/xml; charset=utf-8"? I tried content.GetHeaders and Add, but than i do have multiple content types. Without, i do receive a unsupported media error.
        Content.GetHeaders(Headers);
        Content.WriteFrom(CreateMySoapWebServiceXml);
         RequestMessage.SetRequestUri('http://febee32f3cb2:7047/NAV/WS/CRONUS%20AG/Codeunit/MyPublishedWebService');
        RequestMessage.Method('POST');
        RequestMessage.Content(Content);
        RequestMessage.GetHeaders(Headers);
        Headers.Add('SOAPAction',GetSoapServiceName + ':' + GetSoapMethodName);

        if Client.Send(RequestMessage,ResponseMessage) then begin
            // ....
        end;

The second question is about the prefixes "soap" for XML. In .NET i the CreateElement had an overload for CreateElement(Prefix,LocalName,NamespaceUri). The XmlElement.Create does only have LocalName and NamespaceUri as parameters.
Thanks in advance!

Hello Skordas,
Regarding Headers - I believe you can resolve the first issue by first calling Remove on the RequestMessage headers to remove the default Content-Type header value, and then call Add to replace it with yours.
I am not sure about your second issue.

hi, thank you vytjak. It worked 👍
Only prefix for Xml CreateElement missing. Current workaround is to write the xml in a text variable :(

Could you try
el := CreateElement(LocalName, NamespaceUri)
el.Add(XmlAttribute.CreateNamespaceDeclaration(NamespacePrefix, NamespaceUri))

I would add the namespace declaration at the top of the document and then use only CreateElement(LocalName, NamespaceUri) in all the places I want an element in that namespace.

hi atoader, thank you very much. I would have never used the XmlAttribute to do this, but it seems to work.
        Document := XmlDocument.Create;
        RootNode := XmlElement.Create('envelope','http://test').AsXmlNode;
        RootNode.AsXmlElement.Add(XmlAttribute.CreateNamespaceDeclaration('prefix','http://test'));
        Document.Add(RootNode);

        ChildNode := XmlElement.Create('child','http://test').AsXmlNode;
        RootNode.AsXmlElement.Add(ChildNode);

Result:

<prefix:envelope xmlns:prefix="http://test">
<prefix:child />
</prefix:envelope>

I am running into same issue as your question. What is the syntax for removing the headers on request message?


some notarizing warnings

Build with latest v17r6 beta on macOS 10.13.6
latest 4d-utility-build-application
[https://osxapps-ssl.itunes.apple.com/itunes-assets/Enigma113/v4/a9/2c/2b/a92c2b94-e384-8ee7-9d64-5927bb21569c/developer_log.json?accessKey=1571598785_1967464153845019211_VX%2BDy5HUQd3GkTXt30H0JpCy3IUVD7KW4A7OOKwqvUDHz8XnoXPjAqt3n%2BDZjzCHTl%2BKSpxwmCoMUYwsKMdl13CjRHlqfPmRu0RQBvovfPSQt7TBWoZn0tx0NbUtZ5ySgvQ%2FXlFjfRR%2FvsCRSsy0p1d%2FmLd%2FZFcmcW8n%2BXCTyLY%3D]
|
-- | --
logFormatVersion | 1
jobId | "174e6734-6930-4bc9-8976-73711fccf188"
status | "Accepted"
statusSummary | "Ready for distribution"
statusCode | 0
archiveFilename | "EXPOSE.zip"
uploadDate | "2019-10-18T13:07:35Z"
sha256 | "c9da43bd28759038561f00dacc191e24c8c1df5f35797cfa192d005ad728538d"
issues |
-- | --
0 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
1 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The signature algorithm used is too weak."
docUrl | null
architecture | "x86_64"
2 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "x86_64"
3 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The executable does not have the hardened runtime enabled."
docUrl | null
architecture | "x86_64"
4 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/InstallTool.app/Contents/MacOS/InstallTool"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
5 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/InstallTool.app/Contents/MacOS/InstallTool"
message | "The executable does not have the hardened runtime enabled."
docUrl | null
architecture | "x86_64"
6 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/Plugins/Event Kit.bundle/Contents/MacOS/Event Kit"
message | "The binary uses an SDK older than the 10.9 SDK."
docUrl | null
architecture | "x86_64"

OK got it, your sample is to sign the 4d.app only and not build apps/clients/servers
So I have to add the missing parts by myself :-)
But I get still one error, what is wrong ?
issues |
-- | --
0 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
code to sign inside your test method
$componentPath:=$path+New collection("";"Contents";"MacOS";"").join(Folder separator)
DOCUMENT LIST($componentPath;$componentPaths;Ignore invisible | Absolute path)
For ($i;1;Size of array($componentPaths))
If ($componentPaths{$i}#"Install@")
$componentPath:=$componentPaths{$i}
$statuses.push(codesign ($componentPath;$signingIdentity;$plist;$entitlements;$force))
End if
End for

rather than the code itself, there might be useful information in the $status collection.

Got this in debugger:

Got 2 more error entries:

If you like to try it with my app: http://www.node.de/n.zip
Thanks Armin

you might want to Google the exact error message in quotes.

Hi Miyako,
yes I've found it and think that I have to suppress out the --deep option during codesign for this.
Sure I and other developers can adjust the tool with try and error until it fits. I thought, that I inform you about my problems to get an enhanced version which works maybe also as a drop in component to sign build apps clients and server.
perhaps also with the xcrun stapler staple option or the app
You have maybe tested only with the 4d.app and not with compiled build apps, or my xcode 10.1 on 10.13.6 is to old.
Thanks Armin

Miyako, I don't get it running with your build tool.
The app report successful notarized, but there are issues inside:
If you like to try it with my app:
fresh build, but not signed
|
-- | --
logFormatVersion | 1
jobId | "b7c7aba2-2523-4c9f-a9dd-fee2141ce498"
status | "Accepted"
statusSummary | "Ready for distribution"
statusCode | 0
archiveFilename | "EXPOSE.zip"
uploadDate | "2019-10-21T12:07:00Z"
sha256 | "b69fdf6006ef330bf300736fa63b39dddeb4f532d8b9a19dce11a35feae54e1b"
ISSUES:
issues |
-- | --
0 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/EXPOSE"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
1 |
severity | "warning"
code | null
path | "EXPOSE.zip/EXPOSE.app/Contents/MacOS/InstallTool.app/Contents/MacOS/InstallTool"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"

Tried to sign 4D v17r6 4D.APP (latest build 17 R6 build 17R6.243126) and got
223 warnings, here are the first 15, maybe 4D v17r6 works different than v17r5
But I need to sign and notarize my v17r6 build apps/client/servers
Armin
P.S.: modified your code only at 3 lines:
line 25: $path:="OSX_11:Users:armindeeg:Desktop:4D v17 R6:Test:4D.app:"
line 220: $params.username:="xxxxx"  //account
line 221: $params.password:="xxxxx"  //location for app specific password
issues |
-- | --
0 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/MacOS/4D"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
1 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/M…tents/MacOS/InstallTool"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
2 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/M…tents/MacOS/InstallTool"
message | "The executable does not …rdened runtime enabled."
docUrl | null
architecture | "x86_64"
3 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…ces/php/Mac/php-fcgi-4d"
message | "The binary uses an SDK older than the 10.9 SDK."
docUrl | null
architecture | "x86_64"
4 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The binary is not signed."
docUrl | null
architecture | "i386"
5 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "i386"
6 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The binary is not signed."
docUrl | null
architecture | "x86_64"
7 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "x86_64"
8 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The binary is not signed."
docUrl | null
architecture | "x86_64h"
9 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…es/DWARF/TRMosaicLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "x86_64h"
10 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…ramework/TRMosaicLayout"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "i386"
11 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…ramework/TRMosaicLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "i386"
12 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…ramework/TRMosaicLayout"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
13 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…ramework/TRMosaicLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "x86_64"
14 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…tedCollectionViewLayout"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "i386"
15 |
severity | "warning"
code | null
path | "4D.dmg/4D.app/Contents/R…tedCollectionViewLayout"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "i386"

Miyako FYI,
I've tested the old build app utility from 20th june and this one works, no warnings except for an old plugin.
Something in the new version cause the warnings on the notarization result.
Armin

are you using the version newer than Oct. 8?
because there was a request from a user, to modify the code so that it does not throw "undefined" errors in compiled mode.
it was a bad idea, I reverted in Oct. 8.

Yes, I use the latest 7 days old version which shows the notarization warnings.
the old version from 20.6.2019 does not show these kind of warnings. If you like you can test it with my app, If posted a link top the n.zip some message before.
I've tested both the latest and the old from june in uncompiled mode

most of your warnings are about 4D for iOS, which should not exist in a typical final application.
also, earlier you mentioned about removing --deep.
if true, you are not using the component as it was designed.

no removing --deep had no effect
I think, I've found it.
the last call before the end if
//the app
$statuses.push(codesign ($path;$signingIdentity;$plist;$entitlements**;$noOptions**))
When I remove the last parameter and step into the first If (Count parameters>4) inside the codesign method, then the codes produces no warnings from apple notarization. But there are some checks for the now missing parameter 5

if there is a count parameters then it is not the latest version.
the whole point of the correction was to remove parameter counting.

I think the error originates from a wrong test path name
$componentPath:=$path+New collection("";"Contents";"MacOS";"InstallTool.app";"").join(Folder separator)
If (Test path name($componentPath)=Is a folder)
$statuses.push(codesign ($componentPath;$signingIdentity;$plist;$entitlements;$force))
End if

this was for a different user using the code for 17.x and 17 R (installer location is different)

Hi Miyako,
I thought I can get the latest version on this button ?

And Codesign has the parameter counting:

the topmost Count parameters is OK. the problem was with the ones down below.
keep in mind that the TEST method is updated too.
with the latest version, can you not notarize without modification (other than account info.) ?

Thanks Miyako,
we get closer to a solution:
now I get this warnings: (Event Kit has to be updated from me)
s |
-- | --
0 |
severity | "warning"
code | null
path | "EXPOSE.dmg/EXPOSE.app/Contents/Native Components/SQLServer.bundle/Contents/MacOS/SQLServer"
message | "The signature of the binary is invalid."
docUrl | null
architecture | "x86_64"
1 |
severity | "warning"
code | null
path | "EXPOSE.dmg/EXPOSE.app/Contents/Native Components/SQLServer.bundle/Contents/MacOS/SQLServer"
message | "The signature algorithm used is too weak."
docUrl | null
architecture | "x86_64"
2 |
severity | "warning"
code | null
path | "EXPOSE.dmg/EXPOSE.app/Contents/Native Components/SQLServer.bundle/Contents/MacOS/SQLServer"
message | "The signature does not include a secure timestamp."
docUrl | null
architecture | "x86_64"
3 |
severity | "warning"
code | null
path | "EXPOSE.dmg/EXPOSE.app/Contents/Plugins/Event Kit.bundle/Contents/MacOS/Event Kit"
message | "The binary uses an SDK older than the 10.9 SDK."
docUrl | null
architecture | "x86_64"

Changed on your test method is only
Account Info and path.
And now the altool method, does not return the ticket id inside $params like before.

the old code made a 2nd call immediately after uploading, but this could result in a success:false, because the call was too early.
so I removed
If ($status.RequestUUID#Null)
$params.RequestUUID:=$status.RequestUUID
//2nd call, get status
$status:=altool ($params)
End if

but I guess it was only necessary to remove the line
$status:=altool ($params)

I didn't reproduce the SQLServer issue.
https://osxapps-ssl.itunes.apple.com/itunes-assets/Enigma123/v4/d7/bd/b5/d7bdb5bd-2c89-b2e7-2c61-c8b659eca1ee/developer_log.json?accessKey=1571947244_7100595096977786776_FQRZIuEIF%2Fh4Cip4d6z7pFXZM9mBOLDonOCam435OTbP4g%2F0jjyZhUx4JdQt4hZCoHvNc6wf%2BtkZAw3iZuNwnyYWsT7HdLhWurhtmVCbEpoklG6tEAz9d1J%2B3dcq%2FGx8E5n3wgbk6IoVsdlAcXmhvleDjIcc1sPPGsOgpAYYh4g%3D

First I had the SQL Server issue, then the WebViewerSystem and then the CodeEditor
Don't know why, but I've added these 3 blocks to resolve it.
Now apple reports only the old event kit plugin, which is my next step.
Maybe it is my 10.13.6 with Xcode 10.1 ?
	  //sign with hardened runtime because this is an app
	$componentPath:=$path+New collection("";"Contents";"Native Components";"SQLServer.bundle";"Contents";"MacOS";"SQLServer").join(Folder separator)
	$statuses.push(codesign ($componentPath;$signingIdentity;$plist;$entitlements;$force))

	  //sign with hardened runtime because this is an app
	$componentPath:=$path+New collection("";"Contents";"Native Components";"WebViewerSystem.bundle";"Contents";"MacOS";"WebViewerSystem").join(Folder separator)
	$statuses.push(codesign ($componentPath;$signingIdentity;$plist;$entitlements;$force))

	  //sign with hardened runtime because this is an app
	$componentPath:=$path+New collection("";"Contents";"Native Components";"CodeEditor.bundle";"Contents";"MacOS";"CodeEditor").join(Folder separator)
	$statuses.push(codesign ($componentPath;$signingIdentity;$plist;$entitlements;$force))

Hi Miyako,
with xcode 10.3 it works fine on macOS 10.13.6
Here is a link how to install xcode 10.3 on High Sierra https://codewithchris.com/xcode-update/

With xcode 10.1 I get some warnings. So I think minimum xcode with command line tools is 10.3
Thank for your support Armin

thanks for sharing!


Please provide a signed APK

Could you please attach a signed APK to your releases? App bundles are non-trivial for the average user – and Play Store a no-go for the privacy-focused :wink:
Speaking of the latter: Applying for inclusion at F-Droid might be a good idea :smiley:

Ugh? Makes no sense to assign this to me, I cannot work on it :rofl:

Yeah, sorry, I was testing the waters with the CI system to publish app bundles to the stores, but it's true that it doesn't make much sense to upload it to releases here since you won't be able to install them by usual means. Now the releases should upload APKs instead of AABs :)
About publishing the app to F-Droid, I may take a look at it, thanks for suggesting it!

Thanks a lot! Meanwhile, in another universe… As long as there's an APK attached to new tags, it will be automatically updated (usually within 24h). And if you want to link there, here's a badge for that.
Should you need help getting your app to "F-Droid proper", I'll be there (disclosure: I'm one of the maintainers).


fedora: Remove use of interface multiqueue

What this PR does / why we need it:
The fedora preference is the only plain OS level preference shipped with interface multiqueue enabled. The only other preferences that enable this are rhel.8.dpdk, rhel.9.dpdk and rhel.9.realtime.
This is an issue as it essentially blocks vCPU hot plug when using the fedora preference, always requiring a restart to plug new vCPUs as sockets. To avoid this interface multiqueue is removed from the fedora preference.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

`preferredNetworkInterfaceMultiQueue` is no longer enabled by the `fedora` preference

/cherry-pick release-1.2
/cherry-pick release-1.1


Small typos in the presentation

Two small typos exist in the presentation at page:
https://eddiejaoude.github.io/opensource-deployment-presenation/#/1/8

INVOVLED instead of INVOLVED
Contibute instead of Contribute

I'm going to send a PR soon with these 2 typos fixed :)
BTW, the repo name itself contains a typo (presenation instead of presentation) but I think this cannot be fixed through a simple pull request.

PR merged, thank you 👍

BTW, the repo name itself contains a typo (presenation instead of presentation) but I think this cannot be fixed through a simple pull request.

OMG yes you are right!! I will fix it 🤓


FileOutputStream should use FileChannels

Java 7 rt.jar uses FileChannels for the implementation of old FileOutputStreams.

done


Project Isolation support

To apply the plugin to all Gradle projects, you only need to apply the plugin to the top-level build file as shown above

With regards to project isolation support (docs), this seems to be a bit of a problem. One project should not access another project.
https://github.com/Kotlin/kotlinx-kover/blob/e1f3fbc4232216bf55b3c43ca0ad193e639afd68/src/main/kotlin/kotlinx/kover/KoverPlugin.kt#L48-L50
Above, the root project is accessing other projects. I somewhat solve this problem by having separate plugins:
com.myPlugin.aggregator
com.myPlugin.subproject

com.myPlugin.subproject is applied to subprojects, and com.myPlugin.aggregator is responsible for aggregating the output from subprojects that apply com.myPlugin.subproject.
Excerpt from Square's herding elephants article on why this feature is important

Eliminate cross-project configuration (think: allprojects and subprojects) so that every module (or "project", to use Gradle terminology) could be configured independently from every other. This should improve the configuration phase of the build, since those APIs defeat configuration on demand; and it also sets us up to be compatible with a new experimental Gradle feature known as project isolation, which holds the promise of making slow Android Studio syncs a thing of the past.

Even though Project Isolation is experimental (and in most cases, not yet practical) - it's important that Gradle plugins (like Kover) design with Project Isolation in mind. For example, having separate plugins and only using allprojects/subprojects { } (if you must) in a dedicated .aggregator plugin. That way, when Gradle releases APIs to avoid the allprojects/subprojects { } APIs, the migration is trivial.
note: I'd definitely recommend reaching out to the Gradle team to see what they recommend here

Relates #19

Resolved in 0.7.0-Alpha


Replace lstrip() with removeprefix() to fix Ruff linter warning

This PR fixes the Ruff linter warning:
B005 Using `.strip()` with multi-character strings is misleading

I believe the intent of data.decode("utf-8").lstrip("data:") was to remove the prefix data:. However, lstrip() removes any combination of characters (a, d, t, :) from the beginning of the string. This could introduce potential bugs.
Ref: https://docs.python.org/3/library/stdtypes.html#str.lstrip
cc @ywang96

@simon-mo Could you please review my PR? It's short and straightforward.


Don't delete FileAccess when it is null

Fixes https://github.com/Zylann/voxelgame/issues/57#issuecomment-427369016
And other potentiall issues.

Thanks!


QLora with DeepSpeed support

System Info
peft: 0.12.1.dev0
accelerate: 0.33.0.dev0
transformers: 4.45.0.dev0
platform: ubuntu22.04 LTS
python 3.10.12
hardward: NVIDIA RTX2080TI * 4
Who can help?
No response
Information

[ ] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[ ] My own task or dataset (give details below)

Reproduction
https://github.com/pacman100/LLM-Workshop/tree/main/personal_copilot/training
I've been following this article to finetune a model.
run_peft.sh works on my machine but only use single GPU, so i want to use accelerate + deepspeed to split model into multiple GPUs to train larger model.
DeepSpeed with no quantization also works on my machine. But as long as i enabled quantization, it will raise an error:
ValueError: Model was not initialized with Zero-3 despite being configured for DeepSpeed Zero-3. Please re-initialize your model via Model.from_pretrained(...) or Model.from_config(...) after creating your TrainingArguments!
So my question is does QLora support deepspeed now, and if so, what is correct way to run it?
Expected behavior
Expect QLora + DeepSpeed will run on multiple GPUs without error.

btw, i found the same error while trying to run the scripts in examples/sft/run_peft_qlora_deepspeed_stage3.sh.
Do i need to upgrade some package version, or the error is caused by model(since i've changed the model from LLAMA-2-70B to codellama/CodeLlama-7b-Instruct-hf)

Another update, after i inspected the code that triggers this error:

i found transformer lib will not set zero3 when enabled quantization. Let me try to upgrade transformer lib

Nope that won't work, since i found the main branch of transformer also contains this code

it will only initialize deepspeed when quantized not configured

I found that was a wrong check introduced from transformer lib. reinstall these dependencies with newest release solved my problem.

I found that was a wrong check introduced from transformer lib. reinstall these dependencies with newest release solved my problem.

Glad that you found a solution. Could you be so kind to explain further how you solved it, which dependency needed to be updated?

I found that was a wrong check introduced from transformer lib.

Do you mean it's a bug in transformers?


flops in Conv2D is wrong

First, nice work. But I found something wrong when calculating flops in torch.nn.Conv2d, in count_hooks.py file, the out_w = y.size(2) // m.stride[0] is wrong, it must be out_w = y.size(2). The same as out_h.
So the flops result is less than standard ones.

Thanks for the correction. PR merged.


refactor: change url structure for sharing and getting public key

Fix for issue #100

@tskull01 thanks!


Update vite_preload_tag to emit one early hint per entrypoint

Description 📖
Update vite_preload_tag to emit one early hint per entrypoint
Avoids error like "too many 1xx informational responses"
Background 📜
I am trying this gem with caddy as reverse proxy
And visiting the deployed website returns 502, log shows "too many 1xx informational responses"
I found this issue is reported https://github.com/caddyserver/caddy/issues/5616
Which is caused by having too many 103 responses sent
The Fix 🔨
Update vite_preload_tag to emit one early hint per entrypoint (actually all sources input, but it's mainly used by vite_javascript_tag)
Screenshots 📷
N/A

Looks good, thanks Pikachu! 😃


Question about S2C_ActorControlSelf

I'm not a native English speaker so I have some issue on this:
"S2C_ActorControlSelf
Use any action with cooldown, and possibly make it to rollback.
Spamming NIN Ten(4975) is the best way to cause the game to rollback the action."
I'm not sure what is a "rollback" and what is "NIN Ten", so I don't know which ability to use in order for me to find my S2C_ActorControlSelf value, could anyone explain it a little bit more? Or just show me an ability icon that I should use for this.

Use Ten-Chi-Jin(天地人) in succession until this happens. You'll see that a Mudra action is cancelled.
https://user-images.githubusercontent.com/3614868/125471742-998f3c89-6cc4-4730-adb1-08215a32b2f1.mp4


Extract release scripts

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


Multiple attachments for a nested association

Hi! I have a model with some nested associations, and the last association can have multiple attachments uploaded with ActiveStorage. How do I adapt the  snippet in the README to this case? The example seems to be for a parent model with a single attachment, while I have multiple attachments with a nested association/model.
Thanks in advance!

I'm sorry, I don't know as I don't use ActiveStorage yet :) Please let me know if you find out.

Has this been solved? I have the same question for carrierwave

No, I haven't heard back. Looking at the docs, I can see that multiple attachments are basically attachments via has-many-through, so you might be able to do the same as for the singular version by iterating over the records in the association?

Oh wait, you were referring to carrierwave :) Seems you need to associate an array of file paths in that case, see: https://github.com/carrierwaveuploader/carrierwave/wiki/How-to:-"Upload"-from-a-local-file

The current active storage example in the readme didn't work for me- rails 5.2.
It uses ActiveStorage::Downloader but I received NameError: uninitialized constant ActiveStorage::Downloader
Here's a both has_one_attached and has_many_attached snippets for rails 5.2
# Rails 5.2, has_one_attached example
pirate.deep_clone include: :parrot do |original, kopy|
  if kopy.is_a?(Pirate) && original.avatar.attached?
    attachment = original.avatar
    kopy.avatar.attach \
      :io           => StringIO.new(attachment.download),
      :filename     => attachment.filename,
      :content_type => attachment.content_type
  end
end

# Rails 5.2, has_many_attached example
pirate.deep_clone include: :parrot do |original, kopy|
  if kopy.is_a?(Pirate) && original.crew_members_images.attached?
    original.crew_members_images.each do |attachment|
      kopy.crew_members_images.attach \
        :io           => StringIO.new(attachment.download),
        :filename     => attachment.filename,
        :content_type => attachment.content_type
    end
  end
end

Thanks for this, I've updated the readme!

I'm stuck with this problem too, where I have a multiple attachment for a nested association. Any inputs on how to go about it would help.
I have this association -

A building has many floors
A floor has many rooms
A room has many beds

Without ActiveStorage, I'm able to make a deep clone as below -
building.deep_clone include: [floors: [rooms: [:beds]]]
I have an ActiveStorage dependency of bed has_many_attached :sheets
The Readme describes the usage of ActiveStorage for parent model, but not for the nested models.
Could you please shed some light on how to go about it?
Thanks.

Hi,
As the readme states, a passed block will be evaluated for every copy created. That's why it's needed to check the class of the copy before doing stuff. So, in your case, you just need to check that the copied object is in fact a Bed.
building.deep_clone include: [floors: [rooms: [:beds]]] do |original, kopy|
  if kopy.is_a?(Bed) && original.sheets.attached?
     # ActiveStorage copy strategy for sheets
  end
end

Hi,
As the readme states, a passed block will be evaluated for every copy created. That's why it's needed to check the class of the copy before doing stuff. So, in your case, you just need to check that the copied object is in fact a Bed.
building.deep_clone include: { floors: { rooms: :beds } } do |original, kopy|
  if kopy.is_a?(Bed) && original.sheets.attached?
     # ActiveStorage copy strategy for sheets
  end
end

Thank you very much. I was able to get it to work.
Appreciate the quick response :)


can not see rom list.

i had launch server and saw the website, but i can not see rom list. why?

Thank you for giving a try.
Are you talking about launching server or local right? Do you run it on ubuntu or window? Can you copy the log from browser?

Thank you for giving a try.
Are you talking about launching server or local right? Do you run it on ubuntu or window? Can you copy the log from browser?
i'm on a local host on ubuntu.

it just output
handlers.go:115] Browser connected to overlord
handlers.go:287] Send sync [<IP_ADDRESS>] <IP_ADDRESS>
no any other info

@shou1156226, you can open Chrome console by pressing F12, then right click on any record in there and select "Save as...", or just expand the browser window to fit all text and print-screen it.


e2e & integration testing needed

Describe the bug
AWSSQS source lacks any kind of testing outside some basic unit tests -- that should be fixed
Expected behavior
we should have integration tests that run for every commit and accurately demonstrate if the source is working or not
To Reproduce

Submit PR to repo
Watch in sadness as there are no integration tests to run :cry:

Knative release version
latest

/reopen

/reopen


Can't find template "SignalR negotiate HTTP trigger" in "javascript"

···
PS C:\dev\Code\Playgrounds\serverless> func new --template "SignalR negotiate HTTP trigger" --name negotiate
Use the up/down arrow keys to select a template:SignalR negotiate HTTP trigger
Can't find template "SignalR negotiate HTTP trigger" in "javascript"
···
template do not support javascript but doc asked create a js fuycntion app at the begining

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

ID: 92ea301b-6db8-83db-9bed-4e94969f26dd
Version Independent ID: b5c14f79-1eb4-3a6e-0c50-e61c1dadacfb
Content: Tutorial: Authentication with Azure Functions - Azure SignalR Service
Content Source: articles/azure-signalr/signalr-tutorial-authenticate-azure-functions.md
Service: signalr
GitHub Login: @Y-Sindo
Microsoft Alias: zityang

it was npm dependency missing. the prompt is misleading

I get exactly the same error.

@waynebaby
Thanks for your feedback! We will investigate and update as appropriate.

The "SignalR negotiate HTTP trigger" template is only available to Node worker model V3 and not available to V4 yet. And now the default Node worker model used by function cli is changed to V4. Will update the doc to remove the use of template. If you use worker model V4, see the sample https://github.com/aspnet/AzureSignalR-samples/blob/main/samples/BidirectionChat/js/src/functions/negotiate.js here . If you want to use worker model V3, you could use command func new --model V3 --worker-runtime node --language javascript --template "SignalR negotiate HTTP trigger" --name negotiate to create a negotiate function.

The doc is updated.

It looks like this has been resolved and the doc has been updated. @waynebaby are you still getting this error?


[Task] Highlighting

Highlighting a given source code is a task format we have evaluated in the past. There is already an implementation for the old OpenPatch system. https://gitlab.com/openpatch/web-frontend/-/tree/master/formats/highlight. It uses draft.js and also supports keyboard interaction for highlighting.
The easiest way would be to copy most of the stuff and use draftjs as well. Unfortunately, draftjs was not updated since August 2020 and the issue count is rising. Thus, I do not know if it is future-proof. Maybe someone knows a better alternative system.
Additional links:

Old OpenPatch Version: https://openpatch.gitlab.io/web-frontend/?path=/story/format-highlight-renderer--with-dispatch
Research Paper about automatically evaluating this task format: https://dl.acm.org/doi/10.1145/3279720.3279729
Research Paper about using this task format: https://dl.acm.org/doi/10.1145/3304221.3319745

implemented in #458


[Feature] Support Yi-Large from 01.ai

What Would You Like to See with the Gateway?
01.ai is a chinese LLM provider with Yi-large being a 34B parameter model with capabilities close to GPT-4. Should like to see 01 as a provider in portkey-ai gateway
Context for your Request
No response
Your Twitter/LinkedIn
https://x.com/hargup13

Should also be a good first issue.

Looks like there is support for 01.AI models already https://github.com/Portkey-AI/gateway/blob/main/src/providers/lingyi/api.ts
Though the API keys I got from the waitlist don't work for lingyi and only work for the url api.01ww.xyz

@hargup we've decided to close this. You could use combo of provider + customHost to route your requests to the working URL (api.01ww.xyz). Provider would be lingyi.
Check out this doc for an example on how to do this: https://portkey.ai/docs/integrations/llms/byollm#2-initialize-portkey-with-your-custom-url


when add dimensions in istio-control/istio-discovery helm chart, some errors occurred while getting the prometheus metrics

version: 1.11.4
I deploy istio with helm. when i add dimensions in file(istio-1.11.4/manifests/charts/istio-control/istio-discovery/values.yaml):
telemetry:
  enabled: true
  v2:
    # For Null VM case now.
    # This also enables metadata exchange.
    enabled: true
    metadataExchange:
      # Indicates whether to enable WebAssembly runtime for metadata exchange filter.
      wasmEnabled: false
    # Indicate if prometheus stats filter is enabled or not
    prometheus:
      enabled: true
      # Indicates whether to enable WebAssembly runtime for stats filter.
      wasmEnabled: false
      # overrides stats EnvoyFilter configuration.
      configOverride:
        gateway:
          disable_host_header_fallback: true
          metrics:
            - dimensions:
                request_host: request.host
                request_method: request.method
                source_cluster: node.metadata['CLUSTER_ID']
              tags_to_remove:
                - connection_security_policy
                - destination_app
                - destination_canonical_revision
                - destination_canonical_service
                - destination_principal
                - destination_service_name
                - destination_service_namespace
                - destination_version
                - response_flags
                - source_app
                - source_canonical_revision
                - source_canonical_service
                - source_principal
                - source_version

when add "request_method: request.method" , the metrics in prometheus will be three "istio_requests_total" like this.

but istio_requests_total has no method field.

when remove "request_method: request.method", the metrics in prometheus will be only one "istio_requests_total"

You will need to add extra tags to the configuration as well, see step 2 here https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#enable-custom-metrics. Note you will need to restart your proxy in order to make extra tag to work.

You will need to add extra tags to the configuration as well, see step 2 here https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#enable-custom-metrics. Note you will need to restart your proxy in order to make extra tag to work.

thank you, it takes effect. i add annotations "sidecar.istio.io/extraStatTags: request_method" in gateway-ingress .
But there is one more question，I initially added it this way, but it didn't work。
- name: ISTIO_METAJSON_ANNOTATIONS
       value: |
          {"sidecar.istio.io/extraStatTags":"request_method"}

That is an undocumented approach, which I wouldn't be surprised if no longer working... It would be better to follow the doc, thanks!

I am going to close this issue since the question has been answered and solution works. Thanks!


Send contacts to publishing api

https://trello.com/c/JxKRVn6c/731-export-whitehall-contacts-to-publishing-api-medium

:+1:


🐛 Being able to match multiple items in jsonpath

Summary
This allows a jsonpatch to match multiple items and returns a list with jsonraw
Related issue(s)
Fixes #
https://github.com/open-cluster-management-io/work/issues/196

LGTM

/lgtm


UDP and SOAP

I want to connect to a remote device. The router of the network where the device is, only has 4370 port opened. How can I make sure the Class won't try to connect using port 80?
Thanks

You can be sure TAD-PHP tries to connect using port 80 because current version is designed to test if the device "is on-line" through a curl() call and it's supposed that the device has a webserver build-in (I had a device with webserver support in my last job).
So, if your device doesn't have a webserver built-in, TAD-PHP will refuse sending commands. I know this is a very annoying issue.
I have a new version but I don't have any device where to test it. In the meantime I won't commit changes until I can get a new device to run tests in a properly way.
Sorry,
Cobis


feat: add Edgeware EdgeEVM Mainnet

Issue: https://github.com/safe-global/safe-deployments/issues/269
ChainID: 2021
RPC endpoint: https://edgeware-evm.jelliedowl.net/
Block explorer: https://edgscan.live/

Thanks @moisses89 & @Uxio0 🙌


Revert "Kill bower"

Reverts daneden/animate.css#838

@jabranr I actually just realised something: we're not going to use the sass branch for v4 of Animate.css, so I'm reverting the change. Feel free to open another PR for master

@daneden No worries. I will open one for master.


On-finished 2.2.0 typings

@czechboy0 thank you your contributions.
please check this document http://definitelytyped.org/guides/contributing.html#tests

@vvakame Better? This is my first typing, so please bear with me :)

Needs fixing

Fixed, ready to be looked at, @vvakame

@czechboy0 cool! thanks mate.


feat(cli): add --cpu-prof flag

📝 Description
Add a --cpu-prof flag to panda, panda cssgen, panda codegen and panda debug commands This is useful for
debugging performance issues in panda itself. This will generate a panda-{command}-{timestamp}.cpuprofile file in
the current working directory, which can be opened in tools like Speedscope
This is mostly intended for maintainers or can be asked by maintainers to help debug issues.
💣 Is this a breaking change (Yes/No):
no

Can we this docs to the cli references doc


New version: OVRASTeam.OpenVR-AdvancedSettings version 5.5.0

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1056
Microsoft Reviewers: Open in CodeFlow

@Trenly the NIS installer is not setting some fields if you want to fix it =)
Name        : OpenVR Advanced Settings
Publisher   :
Version     :
ProductCode : OpenVRAdvancedSettings
Uninstall   : winget uninstall --id "OpenVRAdvancedSettings"

https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/pull/599


Move *.fish files to functions directory

See: https://github.com/jorgebucaran/fisher/issues/651

thank you!

thank you!


Adding ROCm support to run_pip_tests.sh (r2.3)

Adding this commit to the release branches

Can one of the admins verify this patch?


[RR Request]: Carapace 1.0

Open Source Project name
Carapace
What is your project?
A multi-shell completion library and binary.
It enables complex argument completion consistent across every major shell and provides over  and .
Version
1.0
Date
March 13, 2024
Description of breaking changes
Carapace consists of a pflag fork, a yaml spec, a shell lexer, a completion bridge and various scrapers.
It has grown to over 13 projects so it is a good time to move them to a separate organization account.
Since this includes a change in the package name they all got a major bump to 1.0.
Apart from that the library has been fairly stable for quite a while now which also contributes to this change.
GitHub Repo
https://github.com/carapace-sh/carapace-bin
Website
https://carapace.sh/
Link to changelog
https://carapace-sh.github.io/carapace-bin/release_notes/v1.0.html
Social media
https://mastodon.social/@carapace_sh/112090531275321447
Anything else to add?
No response

Congrats on being featured in the March Release Radar 🥳

Read the blog here
Feel free to retweet Mish's tweet featuring you

Congrats on being featured in the March Release Radar 🥳

Read the blog here
Feel free to retweet Mish's tweet featuring you


Improved the text for a front page of the wiki

Together with @ddworken we rewrote the introduction section a little bit.
@manuelvsousa for the Hugo syntax & the contents
@empijei for the overall look and other suggestions
Visually it looks like this:

@ddworken can you review the changes from the commit 554f849?


Why not frontend from flask

Why frontend  not handle from flask since it is used on backend.
I just want to clear about this

Was too lazy to set it up lol


TRIVIAL - override for CVE 2022 24765

This is override of git until git 2.35.2 is available via APK

tested on https://github.com/wandera/actions-test/runs/6004500345?check_suite_focus=true


chore: update RED4ext.SDK

Upgrade to latest RED4ext.SDK for patch 2.01.

▶ PR's need to hold back for a bit: ongoing work is still going on in RED4ext.SDK.

it was updated on master now


Primarily superficial wording changes

I stripped trailing whitespace because git was being annoying.
Most of these changes are extremely superficial - I commented on the changes with substance.

Thanks for the cleanups!

Note that I've given you contributor access (probably should have done that first) so you can push directly rather than have to fork and submit a pull request (but feel free to use pull requests if you actually want my review up anything up-front - happy to review after the fact though if that's a little simpler for you).


Add server_error connection hook

Problem Description
Server connection errors like the following are only logged into the console but ignored:
[info] <IP_ADDRESS>:38503: error establishing server connection: [Errno 103] Connect call failed (<IP_ADDRESS>', 443)

After a server_connect hook, we have no way to handle these as the connection is terminated and no server_disconnected/tcp_error hook is called. It would be nice to have an hook to give plugins a possibility to handle these.
Proposal
Add a ConnectionEvents hook which is called when a server error occurs. For consistency with the existent hooks, it could have the following signature:
def server_error(self, data: server_hooks.ServerConnectionHookData):
        # A server connection failed (error message in data.server.error)

Additional context
My workaround with the current API is to manually override ConnectionHandler.server_event (https://github.com/emanuele-f/PCAPdroid-mitm/commit/fd891b8e31defb594ef5e585d0b0c9d11465097c)

Yes, that sounds good to me! It makes sense to add an event hook for this.
Would you be willing to give the implementation a stab?
We should also ponder a bit on the event hook name, those are hard to change later. Some more ideas:

server_error: closest to existing terminology, but doesn't make it clear that this only refers to connection establishment errors
server_connect_error: a bit more verbose
server_connect_failed: alternative

I have no super strong opinions, @mitmproxy/devs any thoughts? Unique opportunity for bikeshedding. 😄  🚲🛖

Yes, that sounds good to me! It makes sense to add an event hook for this.

Great!

Would you be willing to give the implementation a stab?

I suspect this would require so much time wrt the actual value my contribution can bring, to understand the events logic and provide an acceptably clean implementation. I prefer to rely on you :)

I suspect this would require so much time wrt the actual value my contribution can bring, to understand the events logic and provide an acceptably clean implementation. I prefer to rely on you :)

Honestly your monkeypatching looks much more complex than what is needed :)
You can basically copy & adjust ServerConnectedHook (see code search). And then just
await self.handle_hook(server_hooks.ServerErrorHook(hook_data))
around here:
https://github.com/mitmproxy/mitmproxy/blob/c91685efeb995659a5dd8dfdbbb65be5c55f2ac0/mitmproxy/proxy/server.py#L190
No worries if you don't have the capacity for that, but I won't make any commitments w.r.t. a timeline.

All good. I appreciate you opening this issue, just letting you know I won't find the time to tackle it soon. :)

All good. I appreciate you opening this issue, just letting you know I
won't tackle it soon. :)
On Thu, 5 May 2022, 18:00 Emanuele Faranda, @.***>
wrote:

I guess you can implement this in 5 minutes. I won't just copy and paste
some code and provide a PR without understanding what it does. From what
I've seen during my patching, code is not linear as objects are passed from
one method of one class to another, which requires understanding the
abstractions used in this project. I'm not requesting your commitment, I've
just open a feature request as I think this is currently a blind spot for
plugins.
—
Reply to this email directly, view it on GitHub
https://github.com/mitmproxy/mitmproxy/issues/5308#issuecomment-1118741479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHY2PV7AH4LDJJWJSX5TMLVIPWCZANCNFSM5UYSCZ7Q
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

I'll work on this

I wonder if this approach can eventually allow retrying server connections, potentially to another server address & port?
Would it be possible to return some 'retry' indicator from the error hook, or alter some data structure?

Fixed in #6806


Stop running Bundler v1

What are you trying to accomplish?
Stop running Bundler v1 internally, and thus dropping all Bundler v1 specific code, without dropping support for providing updates for Bundler v1 lockfiles.
Anything you want to highlight for special attention from reviewers?
To do this, I adapted native helpers to pass an explicitly requirement on the locked version of Bundler to the resolver. With that in place, the end user behavior should still be the same. Ironically, the changes caused some trouble in Bundler 2. I think it should be possible to reconcile that, but for now I only changed helpers when locked bundler version is v1, and left helpers unchanged otherwise. It seemed also a plus to make this less risky to not change anything for Bundler v2.
Also, I'm pretty sure @jurre will ask about the following so I'll explain. There's some stuff that may change in edge cases. For example, if v1 lockfile uses multiple global sources (something considered insecure), Dependabot will now start splitting the gems in the lockfile by the source they come from. I'm not sure how Bundler 1 deals with that, and since Dependabot currently does not modify the BUNDLED WITH section in the lockfile, it may cause some trouble.
I think the above is acceptable given Bundler 1 is very old, and only particular cases like that may be affected, but generally updates should still work fine!
How will you know you've accomplished your goal?
Bundler v1 users can still get Dependabot PRs, and at the same time we can get rid of all the Bundler v1 specific code.
Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[ ] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

Probably worth doing some realworld testing, but a green spec suite, both with bundler 1 and bundler 2, is reassuring!
Regarding spec changes, I only changed expectations when I considered the new behavior in Bundler 2 better. When it was not clear, I fixed things so that things still work as the work today.

Thanks David! Should we consider just dropping support for bundler v1 altogether instead?

I don't know but this is ready, so shouldn't be necessary to make that decision now if you don't want to!

I'm mostly thinking if we just drop support, we don't need to worry about potential edge-cases or patch up any issues we find with how this works against real world bundler 1 projects.

🤷♂ Up to you! I'm just proposing this because the previous times this was approach the number of users was still not small enough to justify a hard drop. Since the main annoyance of supporting Bundler v1 is maintaining a doubled code base, I figured we can fix the main annoyance and let users keep gradually moving on without disruption.

Maybe ship this and announce official Bundler v1 deprecation at the same time, announcing that while support is still there, internal changes my cause issues for some users that won't necessarily be addressed.

@amazimbe can you help deploy this?

Yes, I will.

@jurre I'm not able to deploy this without your approval. Please take a look when you get a chance.

To be entirely honest, I feel a little unsure about this change, David captured my reservations well in the PR body.
I would much rather we just push to stop supporting Bundler v1 altogether, rather than have potentially broken support out there. My worry is that, yes it might work for people using a single source, but the potential support burden from people who are using multiple sources seems not worth the risk. If we're not committed to fully supporting Bundler 1, and to be candid, I am not, I'd rather we just drop support entirely and communicate that clearly to our customers.
As mentioned, Bundler v1 is very old, usage is low, the upgrade path is really good these days. Why should we put ourselves in this awkward situation?
cc @jonjanego can we sync up soon-ish and decide if we can move forward with dropping support for Bundler v1, rather than having potentially incompatible support?
If we do decide we want to move forward with this change, we should IMO at the very least test the scenario where we're using multiple sources with Bundler 1 and see how this implementation handles that, so we can update our documentation to reflect the limitation if necessary.

No worries @jurre, I understand being careful, and that's precisely why I proposed this as a way to unblock dropping support, since it has been postponed a few times precisely to avoid disrupting users. But I do understand that this will still be disrupting.
How about this alternative approach:
If Dependabot finds a Bundler v1 lockfile, then it ignores all dependencies, except for Bundler itself, and proposes a PR to upgrade Bundler. Once the PR is merged, users can get PRs for the other dependencies again.

Let me talk to Jon about dropping support altogether, and let's also thoroughly test this approach on some real world v1 repo's.
I noticed some v2 fixtures with multiple sources actually use the v1 format, for example this one. I'm actually not quite sure what that means for our test suite here, but either way it'd be good to double check how this actually behaves. @amazimbe is going to run through some examples in a bit.

Awesome, let me know if you need help!

I was curious and I tried this, and I can confirm the behavior:

Dependabot will split sources in lockfile for security if used to upgrade a lockfile with merged source.
Bundler v1 will either merge them back (if run in non frozen mode), or fail (if run in frozen mode).

Note that this is not a new issue though, it already happened for 2.x lockfiles when Dependabot migrated to the version of Bundler that started splitting sources. See for example: https://github.com/dependabot/dependabot-core/issues/4095.
I think the best course of action would be what I proposed earlier:

If Dependabot finds a Bundler v1 lockfile, then it ignores all dependencies, except for Bundler itself, and proposes a PR to upgrade Bundler.
Once that PR is merged, users can get PRs for the other dependencies again.

I run this against a repo with :
bundler version 1.17.3
ruby 2.7.0
but it did not update the bundler version.

Yes, that's correct. Currently Dependabot never updates the Bundler version, and that's what will create issues here. Dependabot will upgrade the lockfile to "v2 format" but will keep "BUNDLED WITH 1.17.3" in it. And that will cause issues in edge cases like the multiple sources situation we were discussing.
Hence my suggestion of actually adding support in Dependabot for upgrading the version of Bundler in the lockfile. Then we can completely stop creating PRs for Bundler v1 lockfiles, except for upgrading the Bundler version itself, and once users merge that PR and upgrade to Bundler v2, they get their Dependabot PRs back.

Yes, that's correct. Currently Dependabot never updates the Bundler version, and that's what will create issues here. Dependabot will upgrade the lockfile to "v2 format" but will keep "BUNDLED WITH 1.17.3" in it. And that will cause issues in edge cases like the multiple sources situation we were discussing.
Hence my suggestion of actually adding support in Dependabot for upgrading the version of Bundler in the lockfile. Then we can completely stop creating PRs for Bundler v1 lockfiles, except for upgrading the Bundler version itself, and once users merge that PR and upgrade to Bundler v2, they get their Dependabot PRs back.

In my case the lockfile stays in v1 format

In my case the lockfile stays in v1 format

So, it proposes correct updates and does not update the format? Then that sounds perfect 😅. I have to admit I tried Bundler directly but not Dependabot as in this PR, so maybe you are right and this is fine after all!

In my case the lockfile stays in v1 format

So, it proposes correct updates and does not update the format? Then that sounds perfect 😅. I have to admit I tried Bundler directly but not Dependabot as in this PR, so maybe you are right and this is fine after all!

This is the log I get on the simple bundle v1 repo that I'm running this against

updater | 2024/07/10 11:32:49 INFO Starting job processing
  proxy | 2024/07/10 11:32:49 [007] POST http://host.docker.internal:50326/update_jobs/cli/update_dependency_list
{"data":{"dependencies":[{"name":"hola","requirements":[{"file":"Gemfile","groups":["default"],"requirement":"0.0.0","source":{"type":"rubygems","url":"https://amazimbe:XXX@rubygems.pkg.github.com/dsp-testing/"}}],"version":"0.0.0"},{"name":"irb","requirements":[{"file":"Gemfile","groups":["default"],"requirement":"\u003e= 0","source":null}],"version":"1.14.0"},{"name":"io-console","requirements":[],"version":"0.7.2"},{"name":"psych","requirements":[],"version":"5.1.2"},{"name":"rdoc","requirements":[],"version":"6.7.0"},{"name":"reline","requirements":[],"version":"0.5.9"},{"name":"stringio","requirements":[],"version":"3.1.1"}],"dependency_files":["/Gemfile","/Gemfile.lock"]},"type":"update_dependency_list"}
  proxy | 2024/07/10 11:32:49 [007] 200 http://host.docker.internal:50326/update_jobs/cli/update_dependency_list
{"data":{"metric":"updater.started","tags":{"operation":"update_all_versions"}},"type":"increment_metric"}
  proxy | 2024/07/10 11:32:49 [008] POST http://host.docker.internal:50326/update_jobs/cli/increment_metric
  proxy | 2024/07/10 11:32:49 [008] 200 http://host.docker.internal:50326/update_jobs/cli/increment_metric
updater | 2024/07/10 11:32:49 INFO Starting update job for dsp-testing/alfred-bundler1-test
updater | 2024/07/10 11:32:49 INFO Checking all dependencies for version updates...
updater | 2024/07/10 11:32:49 INFO Checking if hola 0.0.0 needs updating
  proxy | 2024/07/10 11:32:50 [010] GET https://rubygems.pkg.github.com:443/dsp-testing/versions
  proxy | 2024/07/10 11:32:50 [010] 200 https://rubygems.pkg.github.com:443/dsp-testing/versions
  proxy | 2024/07/10 11:32:50 [012] GET https://rubygems.pkg.github.com:443/dsp-testing/info/hola
  proxy | 2024/07/10 11:32:51 [012] 200 https://rubygems.pkg.github.com:443/dsp-testing/info/hola
updater | 2024/07/10 11:32:51 INFO Latest version is 0.0.0
updater | 2024/07/10 11:32:51 INFO No update needed for hola 0.0.0
updater | 2024/07/10 11:32:51 INFO Checking if irb 1.14.0 needs updating
  proxy | 2024/07/10 11:32:51 [014] GET https://rubygems.org:443/api/v1/versions/irb.json
  proxy | 2024/07/10 11:32:52 [014] 200 https://rubygems.org:443/api/v1/versions/irb.json
updater | 2024/07/10 11:32:52 INFO Filtered out 15 pre-release versions
updater | 2024/07/10 11:32:52 INFO Latest version is 1.14.0
updater | 2024/07/10 11:32:52 INFO No update needed for irb 1.14.0
updater | 2024/07/10 11:32:52 INFO Checking if io-console 0.7.2 needs updating
  proxy | 2024/07/10 11:32:52 [016] GET https://rubygems.org:443/api/v1/versions/io-console.json
  proxy | 2024/07/10 11:32:53 [016] 200 https://rubygems.org:443/api/v1/versions/io-console.json
updater | 2024/07/10 11:32:53 INFO Latest version is 0.7.2
updater | 2024/07/10 11:32:53 INFO No update needed for io-console 0.7.2
updater | 2024/07/10 11:32:53 INFO Checking if psych 5.1.2 needs updating
  proxy | 2024/07/10 11:32:53 [018] GET https://rubygems.org:443/api/v1/versions/psych.json
  proxy | 2024/07/10 11:32:53 [018] 200 https://rubygems.org:443/api/v1/versions/psych.json
updater | 2024/07/10 11:32:53 INFO Filtered out 26 pre-release versions
updater | 2024/07/10 11:32:53 INFO Latest version is 5.1.2
updater | 2024/07/10 11:32:53 INFO No update needed for psych 5.1.2
updater | 2024/07/10 11:32:53 INFO Checking if rdoc 6.7.0 needs updating
  proxy | 2024/07/10 11:32:53 [020] GET https://rubygems.org:443/api/v1/versions/rdoc.json
  proxy | 2024/07/10 11:32:54 [020] 200 https://rubygems.org:443/api/v1/versions/rdoc.json
updater | 2024/07/10 11:32:54 INFO Filtered out 17 pre-release versions
updater | 2024/07/10 11:32:54 INFO Latest version is 6.7.0
updater | 2024/07/10 11:32:54 INFO No update needed for rdoc 6.7.0
updater | 2024/07/10 11:32:54 INFO Checking if reline 0.5.9 needs updating
  proxy | 2024/07/10 11:32:54 [022] GET https://rubygems.org:443/api/v1/versions/reline.json
  proxy | 2024/07/10 11:32:55 [022] 200 https://rubygems.org:443/api/v1/versions/reline.json
updater | 2024/07/10 11:32:55 INFO Filtered out 12 pre-release versions
updater | 2024/07/10 11:32:55 INFO Latest version is 0.5.9
updater | 2024/07/10 11:32:55 INFO No update needed for reline 0.5.9
updater | 2024/07/10 11:32:55 INFO Checking if stringio 3.1.1 needs updating
  proxy | 2024/07/10 11:32:55 [024] GET https://rubygems.org:443/api/v1/versions/stringio.json
  proxy | 2024/07/10 11:32:55 [024] 200 https://rubygems.org:443/api/v1/versions/stringio.json
updater | 2024/07/10 11:32:55 INFO Filtered out 2 pre-release versions
updater | 2024/07/10 11:32:55 INFO Latest version is 3.1.1
updater | 2024/07/10 11:32:55 INFO No update needed for stringio 3.1.1
{"data":{"base-commit-sha":"302b47a90f0477affd107e40e7ad0ce5d083c479"},"type":"mark_as_processed"}
  proxy | 2024/07/10 11:32:55 [025] PATCH http://host.docker.internal:50326/update_jobs/cli/mark_as_processed
  proxy | 2024/07/10 11:32:55 [025] 200 http://host.docker.internal:50326/update_jobs/cli/mark_as_processed
updater | 2024/07/10 11:32:55 INFO Finished job processing
  proxy | 2024/07/10 11:32:56 Skipping sending metrics because api endpoint is empty
  proxy | 2024/07/10 11:32:56 0/11 calls cached (0%)

To test it I pulled this branch locally and then run against my bundle v1 repo with multiple sources
script/dependabot update bundler dsp-testing/alfred-bundler1-test

Oh, but it seems that repo does not need any updates? Of course if Bundler won't create any PRs it won't change the lockfile format. I think we'd need to test on a repository that actually needs updates. I suggest downgrading some gem manually and committing the updated Gemfile/Gemfile.lock file, and then trying again.

Oh, but it seems that repo does not need any updates? Of course if Bundler won't create any PRs it won't change the lockfile format. I think we'd need to test on a repository that actually needs updates. I suggest downgrading some gem manually and committing the updated Gemfile/Gemfile.lock file, and then trying again.

I downgraded one gem and then run it again. It generated a pr but in the gemfile.lock the bundler format is still v1

Tagging @jurre and @deivid-rodriguez for final approvals. If this meets the bar, then @amazimbe can get it deployed.
Thanks.

@amazimbe can you share the before and after lockfiles from those updates where we can see the updated dependency but the format staying the same?

@amazimbe can you share the before and after lockfiles from those updates where we can see the updated dependency but the format staying the same?

 To avoid confusion, I'll summarise the current state of play in this comment.
Before running this CLI against my bundler v1 repo the Gemfile.lock was like this:
GEM
  remote: https://rubygems.org/
  remote<EMAIL_ADDRESS>  specs:
    connection_pool (2.4.1)
    hola (0.0.0)
    io-console (0.7.2)
    irb (1.14.0)
      rdoc (>= 4.0.0)
      reline (>= 0.4.2)
    psych (5.1.2)
      stringio
    rack (3.1.6)
    rack-protection (3.0.6)
      rack
    rdoc (6.7.0)
      psych (>= 4.0.0)
    redis (5.2.0)
      redis-client (>= 0.22.0)
    redis-client (0.22.2)
      connection_pool
    reline (0.5.9)
      io-console (~> 0.5)
    sidekiq (6.0.1)
      connection_pool (>= 2.2.2)
      rack (>= 2.0.0)
      rack-protection (>= 2.0.0)
      redis (>= 4.1.0)
    stringio (3.1.1)

PLATFORMS
  ruby

DEPENDENCIES
  hola (= 0.0.0)!
  irb
  sidekiq (= 6.0.1)

BUNDLED WITH
   1.17.3

After running this CLI against my  bundler v1 repo, the output contained:
GEM
    remote: https://rubygems.pkg.github.com/xxxx/
    specs:
       hola (0.0.0)

GEM
    remote: https://rubygems.org/
    specs:
    concurrent-ruby (1.3.3)
    connection_pool (2.4.1)
    io-console (0.7.2)
    irb (1.14.0)
        rdoc (>= 4.0.0)
        reline (>= 0.4.2)
    logger (1.6.0)
    psych (5.1.2)
        stringio
    rack (3.1.7)
    rdoc (6.7.0)
        psych (>= 4.0.0)
    redis-client (0.22.2)
        connection_pool
    reline (0.5.9)
        io-console (~> 0.5)
    sidekiq (7.3.0)
        concurrent-ruby (< 2)
        connection_pool (>= 2.3.0)
        logger
        rack (>= 2.2.4)
        redis-client (>= 0.22.2)
    stringio (3.1.1)

PLATFORMS
    ruby

DEPENDENCIES
    hola (= 0.0.0)!
    irb
    sidekiq (= 7.3.0)

BUNDLED WITH
    1.17.3

This is indeed in V2 format.
We then run bundle _1.17.3_ update in the v1 repo and the new Gemfile.lock reverted back to the original i.e.

GEM
  remote: https://rubygems.org/
  remote<EMAIL_ADDRESS>  specs:
    connection_pool (2.4.1)
    hola (0.0.0)
    io-console (0.7.2)
    irb (1.14.0)
      rdoc (>= 4.0.0)
      reline (>= 0.4.2)
    psych (5.1.2)
      stringio
    rack (3.1.7)
    rack-protection (3.0.6)
      rack
    rdoc (6.7.0)
      psych (>= 4.0.0)
    redis (5.2.0)
      redis-client (>= 0.22.0)
    redis-client (0.22.2)
      connection_pool
    reline (0.5.9)
      io-console (~> 0.5)
    sidekiq (6.0.1)
      connection_pool (>= 2.2.2)
      rack (>= 2.0.0)
      rack-protection (>= 2.0.0)
      redis (>= 4.1.0)
    stringio (3.1.1)

PLATFORMS
  ruby
  unknown

DEPENDENCIES
  hola (= 0.0.0)!
  irb
  sidekiq (= 6.0.1)

BUNDLED WITH
   1.17.3

To conclude, I believe we have 3 main options:

Remove support for bundler v1 completely as bundler v1 is more than 6 years old. But as @deivid-rodriguez mentioned earlier, this has been tried before but we haven't actually done it due to the number of v1 users still being significant.
As proposed by @deivid-rodriguez, make changes to Dependabot so that it only creates a PR to upgrade bundler if it encounters a bundler v1 lockfile. This would be like a forced bundler upgrade.
Merge this as is and document the flip flopping when users manually run bundle update to avoid confusion. From what I've seen, this would lose the updates made by dependabot every time bundle update is run so it could be confusing and perhaps ineffective.

On hold awaiting input from product about how we would like to proceed.

No longer relevant 🎉. Thanks all :)


Update ContentTransferEncoding.java

found eml files in the wild with "BASE64" encoding, so ignoring case makes sense, i think...

Thanks!

Released in 7.5.1. Sorry for the late release, I didn't realize this was still pending.

no problem at all! thx for your wonderful work!


Add ports

Is there any way to add ethernet ports to ROS in this container?

Hello!
Yep, you may use docker-compose config, for example:
version: "3"

services:

  routeros-6-42:
    image: evilfreelancer/docker-routeros:6.42.12
    restart: unless-stopped
    ports:
      - "12222:22"
      - "12223:23"
      - "18728:8728"
      - "18729:8729"
      ....list of additional ports....

Or pure docker way, and with -p prive to docker list of ports
docker run -d -p 2222:22 -p 8728:8728 -p 8729:8729 -p 5900:5900 -ti evilfreelancer/docker-routeros

Oh, sorry for the inaccuracy. I meant network interfaces, like ethernet 2, etc...

Hm, I think this is not possible for current solution, bacuse docker container has only one erhernet adapter.
Probably you may use network_mode: "host" in docker compose and container will see all available interfaces, then need to modify entrypoint.sh file and add required interfaces.

Could you please tell me login and entry point /bin/sh or /bin/bash?
and credentials would be helpfull too)

docker-compose exec routeros-6-42 bash
or
docker-compose exec routeros-6-42 sh
by default ROS has no login, you can login via telnet as admin user

Thx, i'll try)

I tried to add some interfaces, but get stuck.  I have an idea to add several bridgesm because host network has only one interface. Is it possible?

Yeah, you can add few networks to docker container (networks also mean network interfaces), probably best solution for this is rewriting entrypoint and docker compose file.
I've tried to create few intefaces for qemu inside docker container, but seems it's not so easy as I expected. My second idea is VDE switch http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking and connect qemu to docker interfaces via this switch, because I've checked TAP tunnels and seems it's not work.

I reached my goal by adding following lines to the entrypoint.sh
    -device e1000,netdev=net1 \     -netdev user,id=net1 \     -device e1000,netdev=net2 \     -netdev user,id=net2 \     -device e1000,netdev=net3 \     -netdev user,id=net3.
tried to add more, but startup take too long. idk hy so, but 4 interfaces is more than enough for me. Thank you for help. Issue can be closed)

So you just was needed few interfaces which not actually work? (Probably by test reasons)

Yes, but then i connected them to additional bridges

Can you please provide complete solution? (maybe via gist or somehow else)
I'll add it to this repo as alternative edition of docker image, because for right now this container is for test purposes only.

Sure. Here in is
https://gist.github.com/reinethernal/c5eb0c376714d21120369c07bc9be10e

I've added yet another entrypoint by your gist
https://github.com/EvilFreelancer/docker-routeros/blob/master/entrypoint_with_four_interfaces.sh
All next releases will be with this file


Vue-ts fails in pipelines and fresh modules install with error: Search string not found: "/supportedTSExtensions = .*(?=;)/"

Vue - Official extension or vue-tsc version
Vue tsc 2.1.10
VSCode version
1.95.3 (user setup)
Vue version
3.3.4
TypeScript version
5.0.2
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 1.30 GB / 15.70 GB
Binaries:
    Node: 18.20.5 - ~\AppData\Local\Volta\tools\image\node\18.20.5\node.EXE
    Yarn: 1.22.22 - ~\AppData\Local\Volta\tools\image\yarn\1.22.22\bin\yarn.CMD
    npm: 10.8.2 - ~\AppData\Local\Volta\tools\image\node\18.20.5\npm.CMD

package.json dependencies
{
  "dependencies": {
    "@jamescoyle/vue-icon": "^0.1.2",
    "@mapbox/togeojson": "^0.16.2",
    "@mdi/font": "^7.4.47",
    "@mdi/js": "^7.4.47",
    "@remixicon/vue": "^4.2.0",
    "@tanstack/vue-query": "^5.12.2",
    "@tanstack/vue-query-devtools": "^5.13.3",
    "axios": "^1.7.2",
    "circle-to-polygon": "^2.2.0",
    "element-plus": "^2.7.6",
    "jwt-decode": "^4.0.0",
    "keycloak-js": "^25.0.0",
    "leaflet": "1.9.4",
    "leaflet-draw": "1.0.2",
    "leaflet-geosearch": "^4.0.0",
    "leaflet.vectorgrid": "^1.3.0",
    "lodash": "^4.17.21",
    "moment": "^2.30.1",
    "pinia": "^2.1.7",
    "pinia-plugin-persistedstate": "^3.2.1",
    "pubsub-js": "^1.9.4",
    "remixicon": "^4.2.0",
    "swiper": "^10.3.0",
    "tokml": "^0.4.0",
    "uuid": "^9.0.1",
    "vue": "^3.3.4",
    "vue-router": "4"
  },
  "devDependencies": {
    "@tailwindcss/typography": "^0.5.13",
    "@types/axios": "^0.14.0",
    "@types/circle-to-polygon": "^2.2.3",
    "@types/jwt-decode": "^3.1.0",
    "@types/keycloak-js": "^3.4.1",
    "@types/leaflet": "^1.9.12",
    "@types/leaflet-draw": "^1.0.11",
    "@types/moment": "^2.13.0",
    "@types/pubsub-js": "^1.8.6",
    "@types/uuid": "^9.0.8",
    "@vitejs/plugin-vue": "^4.2.3",
    "autoprefixer": "^10.4.15",
    "concurrently": "^8.2.2",
    "husky": "^9.0.11",
    "postcss": "^8.4.29",
    "prettier": "3.3.0",
    "sass": "^1.66.1",
    "tailwindcss": "^3.3.3",
    "typescript": "^5.0.2",
    "unplugin-auto-import": "^0.16.6",
    "unplugin-element-plus": "^0.8.0",
    "unplugin-vue-components": "^0.25.2",
    "vite": "^4.4.5",
    "vitest": "^1.6.0",
    "vue-tsc": "^2.1.10"
  }
}

Steps to reproduce
This is a vue 3 project. With these present in my package json
"lint": "vue-tsc",
"lint:watch": "vue-tsc --watch",

Run yarn lint. It doesn't lint the files. It just breaks with error
What is expected?
Files should be linted. Errors should be returned if files with wrong types or typescript errors exist.
What is actually happening?
Script breaks
Script breaks
```powershell
✓ src/utility/functions/tests/validator.test.ts (1)
   ✓ Email validation

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  13:27:04
   Duration  677ms (transform 103ms, setup 0ms, collect 130ms, tests 4ms, environment 0ms, prepare 173ms)

><EMAIL_ADDRESS>build:css
> tailwindcss -i ./src/assets/scss/tailwind/tailwind.css -o ./src/assets/scss/tailwind/tailwind-purged.css -m

Rebuilding...

Done in 995ms.

><EMAIL_ADDRESS>lint
> vue-tsc

C:\Users\user\Documents\_project\fix-yarn\node_modules\vue-tsc\index.js:34
            throw err;
            ^
Search string not found: "/supportedTSExtensions = .*(?=;)/"
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v20.14.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

### Link to minimal reproduction

_No response_

### Any additional comments?

It seems some recent updates is causing this. My pipelines would usually run successfully and linting with vue-tsc in pre commit hook also worked. Now it fails all of a sudden.
For existing projects, no issue. For new fresh node module installations (including pipelines), it breaks

Duplicate of #5018


Update fails on macOS when installing rvc-beta

HI,
Thanks for the project.
I have an issue with the update script. It fails on installing rvc-beta:
Building wheels for collected packages: torchcrepe, rvc-beta
  Building wheel for torchcrepe (setup.py) ... done
  Created wheel for torchcrepe: filename=torchcrepe-0.0.20-py3-none-any.whl size=72326242 sha256=81f13868868e84507f420b02c8722c6fca47a65b45adf65b500a6c92d82b3b5b
  Stored in directory: /private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-ephem-wheel-cache-aly64qkb/wheels/4a/7c/9f/170aad22b22218ca80febc6cf9f321b105adfed5c6930233fe
  Building wheel for rvc-beta (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for rvc-beta (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [30 lines of output]
      Traceback (most recent call last):
        File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
          return _build_backend().build_wheel(wheel_directory, config_settings,
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/api.py", line 57, in build_wheel
          return WheelBuilder.make_in(
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 88, in make_in
          wb.build(target_dir=directory)
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 124, in build
          self._copy_module(zip_file)
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 235, in _copy_module
          to_add = self.find_files_to_add()
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 200, in find_files_to_add
          if self.is_excluded(
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 143, in is_excluded
          if exclude_path.as_posix() in self.find_excluded_files(fmt=self.format):
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 111, in find_excluded_files
          vcs_ignored_files = set(vcs.get_ignored_files()) if vcs else set()
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/vcs/git.py", line 340, in get_ignored_files
          output = self.run(*args)
        File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/vcs/git.py", line 373, in run
          subprocess.check_output(
        File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/subprocess.py", line 421, in check_output
          return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
        File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/subprocess.py", line 526, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['git', '--git-dir', '/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-install-pvdanmj5/rvc-beta_5aa98684fc0f4a95a0f6ca810d0759d9/.git', '--work-tree', '/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-install-pvdanmj5/rvc-beta_5aa98684fc0f4a95a0f6ca810d0759d9', 'ls-files', '--others', '-i', '--exclude-standard']' returned non-zero exit status 128.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for rvc-beta
Successfully built torchcrepe
Failed to build rvc-beta
ERROR: Could not build wheels for rvc-beta, which is required to install pyproject.toml-based projects
Failed to install RVC dependencies

Done!

Thanks for reporting!
The rest of the project should be functional even if RVC failed.
Also, the error seems quite arbitrary. Perhaps updating again might make it
succeed this time (main part is for pip install -r requirements_rvc.txt
within conda to be ran again).
On Thu, Aug 10, 2023, 1:46 PM Gábor Librecz @.***>
wrote:

HI,
Thanks for the project.
I have an issue with the update script. It fails on installing rvc-beta:
Building wheels for collected packages: torchcrepe, rvc-beta
Building wheel for torchcrepe (setup.py) ... done
Created wheel for torchcrepe: filename=torchcrepe-0.0.20-py3-none-any.whl size=72326242 sha256=81f13868868e84507f420b02c8722c6fca47a65b45adf65b500a6c92d82b3b5b
Stored in directory: /private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-ephem-wheel-cache-aly64qkb/wheels/4a/7c/9f/170aad22b22218ca80febc6cf9f321b105adfed5c6930233fe
Building wheel for rvc-beta (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for rvc-beta (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [30 lines of output]
Traceback (most recent call last):
File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
main()
File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
return _build_backend().build_wheel(wheel_directory, config_settings,
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/api.py", line 57, in build_wheel
return WheelBuilder.make_in(
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 88, in make_in
wb.build(target_dir=directory)
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 124, in build
self._copy_module(zip_file)
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/wheel.py", line 235, in _copy_module
to_add = self.find_files_to_add()
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 200, in find_files_to_add
if self.is_excluded(
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 143, in is_excluded
if exclude_path.as_posix() in self.find_excluded_files(fmt=self.format):
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/masonry/builders/builder.py", line 111, in find_excluded_files
vcs_ignored_files = set(vcs.get_ignored_files()) if vcs else set()
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/vcs/git.py", line 340, in get_ignored_files
output = self.run(*args)
File "/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-build-env-n56ce437/overlay/lib/python3.10/site-packages/poetry/core/vcs/git.py", line 373, in run
subprocess.check_output(
File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/subprocess.py", line 421, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/Users/kuglee/Downloads/one-click-installers-tts-6.0/installer_files/env/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', '--git-dir', '/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-install-pvdanmj5/rvc-beta_5aa98684fc0f4a95a0f6ca810d0759d9/.git', '--work-tree', '/private/var/folders/3z/sn1s5sd168579mqdhyvyq3gh0000gn/T/pip-install-pvdanmj5/rvc-beta_5aa98684fc0f4a95a0f6ca810d0759d9', 'ls-files', '--others', '-i', '--exclude-standard']' returned non-zero exit status 128.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for rvc-beta
Successfully built torchcrepe
Failed to build rvc-beta
ERROR: Could not build wheels for rvc-beta, which is required to install pyproject.toml-based projects
Failed to install RVC dependencies
Done!
—
Reply to this email directly, view it on GitHub
https://github.com/rsxdalv/tts-generation-webui/issues/122, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTRXI5BT6TYIWNL4GT2JCDXUS3WPANCNFSM6AAAAAA3LJW7WI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank!
Tried to run within conda but got the same error:
pip install -r tts-generation-webui/requirements_rvc.txt

As you said the rest is working fine. I didn't want to use that anyway.