Upgrade from V2 to V3 (alpha)

Hi decided today to upgrade from V2 to V3.0.0 alpha 3. But seem to be getting an error and I can't really see what the issue is?

My Code in sw.js is:
'use strict';

// Until all the browsers will give us the APIs to cache.
importScripts('/themes/assets/js/cache-polyfill.js');

// Load the Workbox library.
importScripts('/themes/assets/workbox-v3.0.0-alpha.3/workbox-sw.js');

/**
 * Create an instance of WorkboxSW.
 * Setting clientsClaims to true tells our service worker to take control as
 * soon as it's activated.
 *
 * Note: ignoreUrlParametersMatching is used to block out parameter string
 * URL's and default will ignore utm_-prefixed parameters. Default: [/^utm_/]
 */
 const workboxSW = new self.WorkboxSW({
   "clientsClaim": true,
   "skipWaiting": true,
   "directoryIndex": "/",
   "precacheChannelName": "precache-royal",
   "ignoreUrlParametersMatching": [/^utm_/]
  });

etc.

There was zero problems when running the latest version of V2. I am wondering if I need to change the code or not - or maybe there is another issue?
Thanks in advance.

Because it is a major version bump there are a number of changes, especially around workboxSW.
The best thing to do is checkout https://developers.google.com/web/tools/workbox/next/, especially have a quick glance at the code snippets in the Guides.
For an example, the short above snippet would now be:
'use strict';

// Until all the browsers will give us the APIs to cache.
importScripts('/themes/assets/js/cache-polyfill.js');

// Load the Workbox library.
importScripts('/themes/assets/workbox-v3.0.0-alpha.3/workbox-sw.js');

/**
 * Setting clientsClaims to true tells our service worker to take control as
 * soon as it's activated.
 */
self.workbox.skipWaiting();
self.workbox.clientsClaim();

 *
 * Note: ignoreUrlParametersMatching is used to block out parameter string
 * URL's and default will ignore utm_-prefixed parameters. Default: [/^utm_/]
 */
self.workbox.precaching.precacheAndRoute([], {
    directoryIndex: '/'
    ignoreUrlParametersMatching: [/^utm_/]
});

etc.

The one thing I do need to add in is support for the broadcasting of cache updates from precaching which I'll do later today and will look like:
self.workbox.precaching.precacheAndRoute([], {
    directoryIndex: '/'
    ignoreUrlParametersMatching: [/^utm_/],
    plugins: [
        new self.workbox.broadcastUpdae.Plugin({ channelName: 'precache-royal' }),
    ]
});

Interesting, thanks Matt.


root: disable usage of fsevents in jest

At least @freben and I have been having issues with extremely bad watch performance in tests. It manifests itself as hundreds of child processes spawned by the Jest main process, which use up a ton of CPU until the disappear 10-15s later. I've narrowed this down to only happening when using the fsevents module for file watching, but since that immediately calls out to the native MacOS APIs it's a lot trickier to continue debugging at that point.
We figured it's worth disabling fsevents in tests for now since this is a tricky issue to catch or even realize is happening.
This may be an issue that is specific to development on Spotify issued MacOS devices, but we're not quite sure what other options we have at this point 😅. From a bit of quick testing the performance seems alright with the node fallback API.
Also curious if anyone else has been seeing issues similar to this one.

Shipping this as it's still having impact, and expecting minimal if any negative impact on the development in this repo with this in place. Let's revisit in the future to see if we can get rid of the workaround.


Update balena-yocto-scripts digest to 34c8434

This PR contains the following updates:

Package
Update
Change

balena-yocto-scripts
digest
93f94ff -> 34c8434

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@resin-jenkins test this please


[FP]: CVE-2016-8735 on JSP Standard Tag Library (JSTL).

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:apache:tomcat:::::::: versions up to (excluding) 6.0.48
CVE
CVE-2016-8735
ODC Integration
{"label"=>"Docker"}
ODC Version
9.2.0
Description
Since the cpe where updated on 6/27/2024 3:23:35 PM (see: https://nvd.nist.gov/vuln/detail/CVE-2016-8735#VulnChangeHistorySection), we have encountered false positives with Apache Tomcat versions 9.0.90 and 10.1.25.
Can you please check this quickly?

False positive is not reproducible

also with the docker image<EMAIL_ADDRESS>is properly linked to cpe:2.3:a:apache:standard_taglibs:1.2.5:*:*:*:*:*:*:* and not showing false positive CVEs


install: move this section above get-started?

I like that Get Started is the first section in our docs, but It's 2nd page links to Installation for the user to go and figure out how to best install the tool. This may kind of break the continuity of get-started from the very beginning. Perhaps if we have Installation on top in the left side bar, most users will already have DVC installed by the time they get to the Get Started -> Initialize page.

From https://github.com/iterative/dvc.org/pull/734#issuecomment-546538772:

had to revert it back since it affected the way dvc.org/doc (main page) looks like. Before it was using Get Started index as a default one and it was crafted to look nice and it makes sense to start with get started :) Install index page is not ready to be a front page for the docs website. Need more work here.

Good point, https://dvc.org/doc/get-started has introductory notes to the entire docs. So maybe these should be moved into a docs/index.md to open as a docs landing page? And then move install above get-started.

yep, good idea, @jorgeorpinel ! Then we can make Agenda in the Get Started to be an index page of the Get Started itself.
Probably some changes to the engine are required to make it work.

it makes sense to start with get started :)

If the user clicks the "Get Started" button, then it will go to the get-started, no matter whether it is the first item on the menu or the second. However if he clicks the "DOC" link to go to the UG or Command Reference, then he still gets Get Started (expanded), which effectively hides the rest of the docs.


SplitView Pane does not render

Describe the bug
I started a new avalonia project and wanted to use the SplitView like I did in a previous project that used version 0.10.18. The new project is now on avalonia 11.1.3. However the SplitView does not render the side pane. It looks like the Style for the SplitView does not include the Pane as an element.
This is the visual tree in my old project

This is the visual tree of my new project

To Reproduce
Checkout my project repo and see that the pane does not render.
Expected behavior
No response
Avalonia version
11.1.3
OS
Windows
Additional context
No response

This project appears to have been migrated from 0.10.x. Please read the migration guide: https://docs.avaloniaui.net/docs/stay-up-to-date/upgrade-from-0.10
Theming has changed and you need to explicitly include a theme now as Avalonia no longer ships with one. New project templates reflect this. No theme = no visuals.


🔄 Synced file(s) with epfml/FeAI

Synced local file(s) with epfml/FeAI.

Changed files

Synced local directory mobile-browser-based-version/src/helpers/data_validation_script with remote directory mobile-browser-based-version/src/helpers/data_validation

This PR was created automatically by the repo-file-sync-action workflow run #1426434331

This is an example of the auto-sync, still need to figure out how to set up rules properly. For now it's just syncing mobile-browser-based-version/src/helpers/data_validation_script folder in a test branch between FeAI -> DeAI


Add Assistants methods to summarize and trim messages

Is your feature request related to a problem? Please describe.
A lengthy Assistant conversation will exceed token context limit. We need a way to trim the messages and/or summarize the conversation to be able to continue it.
Describe the solution you'd like

[ ] Add Langchain::Assistant#summarize_messages! method that summarizes the all of the messages. Need to research how to best summarize a conversation, and whether the summary should go into a prompt in a system message or as a role="user" message.
[ ] Add Langchain::Assistant#trim_messages!(token_offset:) to trim messages to free up a token offset. Research best ways to do this as well.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Zep DB is also summarizing chat histories after a certain time (definable by the user). they used a separate role for this called summary. So introducing a 4th role might help here.
Regarding the best way to summarize: I would set one as default but allow the user to customize the summarization-prompt.
I worked a lot with Sparse Priming Representations and for me it worked fine.
Another great method for summaries is Chain of Density.
Zep is moving from summaries towards "Facts". So they extract specific knowledge from the history and save it in a graph. Maybe that's an approach to consider as well.


[📑 Docs]: ADD 'server' definition to specification docs

What Dev Docs changes are you proposing?
The term server is referenced several times in our Spec under the Definitions section, but it is not yet defined in our Spec.

Let's add a 'server' definition in our Spec under the Definitions section
To ensure we find the most technically accurate definition for the term 'server' within the AsyncAPI spec, let's ask in one of our dedicated AsyncAPI slack channels, such as our #03_specification.
You will likely feel that you need to research and talk to several folks in our Slack channels until you find the best answer. It will help if you reference in your Slack questions this issue, so people can fully understand how to best help you.

How do I get started contributing to this ticket for AsyncAPI Docs?
 At AsyncAPI, we value Doc contributions as much as every other type of contribution. ❤
To get started as a Docs contributor:

Familiarize yourself with our project's Contribution Guide and our Code of Conduct.
Head over to our Docs GH Board here and bookmark it.
Leave a comment in the issue you're picking up and introduce yourself. This is also the perfect place to leave any questions you may have on getting started.
Open a PR and get started!

🏷 Tag Alejandra Quetzalli in your AsyncAPI Doc PRs
Do you have a documentation contributor question and wonder how to tag Alejandra into your GitHub discussion or PR? Never fear!
Tag me in your AsyncAPI Doc PRs or GitHub Discussions via my GitHub handle, alequetzalli 🐙.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

hey there @osigida! great first issue! Do you have any interest in helping contribute to this issue as well? 😄

@alequetzalli I would love to, but not this time, as it is not clear what the intention was behind server term.

@osigida researching that out is the point of the issue you created 🙂

@alequetzalli Can I give this a try?

@alequetzalli Can I give this a try?

@nafees87n You can! Just to let you know tho, I saw @luphieanza express interest in it and he already started researching in the spec channel. You might want to team with him ♥✨✨

@nafees87n yeah we could do it together since we both have interest with this :grin:

@

@nafees87n yeah we could do it together since we both have an interest in this grin Have a look at this reference https://www.asyncapi.com/docs/specifications/v2.3.0 I found it when I try to research the spec channel.

@luphieanza Sure

@alequetzalli I want to PR this issue, but I need to make sure, that I just need to merge only v.2.3.0 or all those spec versions?

@alequetzalli I want to PR this issue, but I need to make sure, that I just need to merge only v.2.3.0 or all those spec versions?

@luphieanza  Good question! I would add the definition only to the latest spec version, v.2.3.0. Thank you for checking and let me know if that makes sense. 😄

you should not add new definition here https://github.com/asyncapi/website/pull/657/files but in https://github.com/asyncapi/spec/tree/master/spec where the original file is. website repo has only a copy of the spec that is modified by automation whenever change happens in https://github.com/asyncapi/spec/tree/master/spec

I see, thanks for your help @derberg I will do that for the revision.

I apologize @luphieanza, I should have remembered to add that instruction in the Description section! 😆
Thanks for the catch @derberg  ⭐

@alequetzalli you might want to close this issue.

Congratulations on this contribution, @luphieanza! A very worthy one ✨
LIVE:
https://www.asyncapi.com/docs/specifications/v2.4.0-2022-04-release.1#definitionsServer


Documentation issues

There are several documentation issues with PocketSVG when documentation issues are turned on in Xcode (as is the default in Cocoapods):

@arielelkin would you prefer to fix this yourself? I can also submit a quick pull request for it 👍

PRs are always welcome here 🙂, @noahsark769 . Go ahead and submit it and I'll work from it.

Opened #101, thanks!

fixed via https://github.com/pocketsvg/PocketSVG/pull/101


Update Get Started guide

@tadayosi @astefanutti @jamesnetherton I updated the Get Started guide but need someone to review it. I found issues with the standalone versions of Hawtio and we'll need to fix them before releasing the new documentation.

@alexkieling Awesome work, thanks!  A bit of feedback follows:

I introduced gatsby-remark-autolink-headers plugin so manual anchors like  aren't necessary. You can just link the sections like you do on GitHub.
https://github.com/hawtio/hawtio.github.io/blob/develop/gatsby-config.js#L29

We can drop support for older Karaf (lower than 4.x) and Jetty 8 for Hawtio v2. Jetty 9.x should be supported instead.

I noticed there's the section "Using a git clone" but let's restate it as "Run with a Spring Boot application" or something like that. It's also good to link it at the top. We may also push it to the 1st or 2nd in order, as Spring Boot support is one of our strong selling points :wink:


Is there a bug of hinge loss for binary classification(binary:hinge)?

I use binary:hinge as my objective function when training a binary classification task. The max_depth was set to 1. And I found the metrics(auc, logloss, error) keep the same during training process. Like
[509]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[510]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[511]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[512]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[513]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[514]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[515]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[516]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[517]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[518]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[519]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[520]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[521]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[522]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653
[523]	train-auc:0.5	train-logloss:10.6287	train-error:0.288653

I dumped the model in the end, and I found that there are many trees with the same structure and selected feature. And some trees has only one node.  Such as:

Is there a bug of hinge loss for binary classification(binary:hinge)? or Can some one give me some advice about the usage of hinge loss in xgboost.

You can find the hinge loss implementation in src/objective/hinge.cu.  It's not a particularly good obj for gradient boosting since it doesn't have hessian defined.  But other than that I don't see what's wrong in the implementation.  My guess for your issue is 1 - y * p < 0 with hinge defined as l(p) = max(0, 1 - y * p).


exfat/fat32 command to bxfat/bat32 (:shrek:)

Add meme version of exfat command

Yeah, this is epic.

no

no

Yes

Please allow the memeing of the exfat command, for Komet's sake of course 😉

#22 not as good as bsfat and bxfat

I would like to make these commands use the list cog just like .es. These meme commands should also be changed over to us the list cog.


Postal Telnet

How to perform postal test with telnet?
Hello guys, I'm trying to do a test via telnet, I don't know if that is possible.
What I'm trying to do is simulate email delivery via the command line.
telnet mypostal.com 25
EHLO mylocalserver.com
AUTH LOGIN
(username in base64)
(base64 user password)
I have the following response from the postal
SMTP << 235 Granted for (my username)
Following to test the message:
MAIL FROM<EMAIL_ADDRESS>(This domain is configured correctly in postal, SPF and DKIM)
RCPT TO<EMAIL_ADDRESS>DATE
Here I write what I want to test
(. to end)
.
Finally I get the following return message
SMTP << 530 From / Sender name is not valid
I've already consulted the following links here
https://github.com/postalhq/postal/issues/863
https://github.com/postalhq/postal/issues/728
None of them can solve the problem.
NOTE: Remembering that through an email client, I can send emails normally through the domain "mydomain.com"

This indicates that the credential you are using (i.e. the username) does not cover the domain you are using.
See also #863 and #728

Hello.
I read it, read it again and for sure I read the 2 topics again.
What I currently do is:
I'm going to the organization/server
There are dozens of domains already created, authenticated and functioning.
When I refer to domains created, authenticated and functioning, I mean that I created a credential on the SMTP server, on my EXIM server I can authenticate without problems and send emails through<EMAIL_ADDRESS>These emails are sent through an email client as a roundcube.
The problem is when I am going to connect via SMTP, I am not sure if I am doing it right.
I am inserting the user in org/server format and the password generated by the postal.
Both are available in the url (help/outgoing)
What am I missing?

The domain in the FROM address (mydomain.com in your example) must be in the same organization as the credential you're using. Do you have multiple organizations in your Postal setup?

I have exact same problem and no we don't have multiple organisations in our postal setup.
The problem is only with the telnet. PHP Mails etc are working fine.


Enable CustomFinancialModel to get costs from PySAM

The financial model must be consistent across all technologies, but the wave energy requires the CustomFinancialModel class. HOPP uses the SingleOwner financial model to get PV (and other tech) costs. Thus, when using CustomFinancialModel the PV costs are not available.
We need to update HOPP such that PySAM costs can be accessed when using the CustomFinancialModel class. This could be possibly done by inheriting from the SingleOwner class or by creating methods in CustomFinancialModel to access PySAM costs.

Addressed in https://github.com/jaredthomas68/HOPP/pull/2

Creates new method set_overnight_capital_cost() in PowerSource to add technology costs.
Modified set_overnight_capital_cost() for Battery class, includes energy_capital_cost and power_capital_cost

Ideally in the future we can pull ATB costs directly from an API or other method. There is an outdated ATB json in HOPP (2020), could potential update to most recent ATB but not sure if that's the best path.

@jaredthomas68 Can we close this if it was addressed in the PR mentioned above?


Fix detection of IPv6 addresses

Fixes brentsimmons/NetNewsWire#1382.
This will allow http:// without anything else, but that's better than not allowing IPv6 addresses.

Slightly better check; looks for a string of hex digits + colons between brackets (so it won't false-positive on just "http:"). The earlier check for "." should catch IPv6 URLs that end in IPv4 notation.


Fix typo in _CrtSetReportHook2 parameter name

@adr26 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@adr26 Thanks for the typo fix; merging.


guard in auth problem

Q
A

Bug?
no

New Feature?
no

Framework
Laravel

Framework version
5.5.y

Package version
2.0.0-alpha2

PHP version
7.1.y

config/auth.php
'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'TLXAdminUsers',
        ],

        'user' => [
            'driver' => 'jwt',
            'provider' => 'Users',
        ],

        'staff' => [
            'driver' => 'jwt',
            'provider' => 'Staff',
        ]
    ]

config/api.php
'auth' => [
        'jwt' => 'Dingo\Api\Auth\Provider\JWT'
    ],

Kernel.php
protected $routeMiddleware = [
        'api-auth' => \Dingo\Api\Http\Middleware\Auth::class,
        'bindings' => \Illuminate\Routing\Middleware\SubstituteBindings::class,
        'can' => \Illuminate\Auth\Middleware\Authorize::class,
        'guest' => \Studiomate\Http\Middleware\RedirectIfAuthenticated::class,
        'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class,

        'role' => \Laratrust\Middleware\LaratrustRole::class,
        'permission' => \Laratrust\Middleware\LaratrustPermission::class,
        'ability' => \Laratrust\Middleware\LaratrustAbility::class
    ];

I want to use 'staff' guard and 'user' guard in 'dingo auth' with 'jwt' on the route.
However, 'dingo auth' using 'jwt' seems to be able to use only the defaults defined in config / auth.php.
Is there a way to use 'staff' guard and 'user' guard on a route?
I know how to use 'auth:staff' on middleware by defining
'auth' => Illuminate\Auth\Middleware\Authenticate::class'

on routeMiddleware, This is also a problem because of an 500 error not 401 error.

Have you solved your problem?

wait

I make a middlleware=auth.jwt , when use staff guard , config set the api.provider = staff.
in auth.jwt middleware
Config::set("auth.guards.api.provider","staff");
in routes api
 $api->group(['middleware' => ['api.auth',"auth.jwt"]], function ($api) {});
dingo api default guards is api。

$api->group(['middleware' => ["auth.jwt",'api.auth']], function ($api) {});

I will have a look at it.


Fix utc date time for end of the year cut off

fixes #371

add test case with selected 5 ls5_fc_albers datasets which exposes the tst issue
fix tst issue
revert accidental docker-compose port changes
add pytz as a python library

Thanks for looking into this Pin!
Ideally we keep using the self.grouping_time_zone on SummaryStore so that we have one consistent variable for time zone (rather than a new separate global), but given that things are already inconsistent this isn’t making it worse. Can do it in a future PR if desired.

Yes, i have raised an issue to refactor  this, see issue #381


Which object types are protected by Defender for Office?

In conjunction with OfficeDocs-O365ServiceDescriptions/#764 I'm currently wondering if users actually need to be Exchange Online recipients to be protected by Defender for Office.
For example, if a user is only licensed for Microsoft 365 Apps and SharePoint Online, but not Exchange Online, to solely be able to work with Office files stored on OneDrive and SharePoint, they're only a user in regards of Exchange, they're no recipient. As such, they can be neither included in nor excluded from Safe Links policies when configuring those in the browser, as the "users" lists just allow to select recipients, not users. This matches the current documentation, which only refers to "mailboxes, mail users, or mail contacts".
Interestingly, when configuring policies by using PowerShell, also users and not just recipients can be included or excluded by stating their full UserPrincipalName, but that doesn't necessarily mean they're protected eventually.
Although the licensing parts of documentation always speak of users, all the configuration parts almost exclusively speak of recipients, which would be two different things in the end, at least from a technical perspective.

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

ID: 8112b7a9-8f21-18b3-03da-f8c02b05f239
Version Independent ID: a441f1d1-5844-ecb9-ba44-95b94714e4e8
Content: Complete Safe Links overview for Microsoft Defender for Office 365 - Office 365
Content Source: microsoft-365/security/office-365-security/safe-links.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@chrisda Please help us in resolving this issue. Thanks

@DMoenks, Safe Links or Safe Attachments protection requires a Microsoft Defender for Office 365 Plan 1 or Plan 2 license.
So what exactly is the ask here for this topic?

The question is not regarding licensing for Defender for Office, as the license need for that product would rather be the topic of the other issue I linked above. The question is, if users need to be Exchange Online recipients to actually be protected by Defender for Office from a technical perspective or if it's sufficient if they're Exchange Online users.
The example I provided above (licensed for Microsoft 365 Apps and SharePoint Online, but not for Exchange Online), would end up in the affected user account to be an Exchange Online user, not a recipient. So, even if that user account was licensed for Defender for Office by any means, would it actually be protected by Defender for Office or not?
As the documentation mentions recipients over and over, I would suspect the answer to be No, but I couldn't such an answer anywhere in the documentation. If the answer would be No, there might be customers having user accounts they deem protected, which aren't actually protected at all...

You should open a support ticket and ask. Report back here with any improvements to the documentation (the Safe Links or Safe Attachments topics, not the Service Description).

@DMoenks Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Typo + cardinality in documentation of domain model

Bug Report
Describe the Bug
(https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/docs/developer/architecture/diagrams/domain-model.png)
Typo: permitions ==> permissions  for Policy

add text making clear that more than one policy can be part of the contract definition (written in text, but in figure it is not clear)

Thanks for filing this. This diagram is out-of-date and probably should be replaced by just referencing the code (or generating a UML diagram from some tool).
To be precise, a ContractDefinition does not contain a multiplicity of policies, it references exactly two policies, an access control policy and a contract policy (this is noted in the class attributes in the diagram).

Next time I will label it correctly, thank you!
It would be a pity to remove the diagram, it was showing exactly the dependencies I was looking for. But perhaps a link to a specification with such a diagram would be good as well.


Update serialization tests for PL v0.30.0_rc changes

Before submitting
Please complete the following checklist when submitting a PR:

[ ] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[ ] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[ ] Ensure that the test suite passes, by running make test.

[ ] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[ ] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:

feel free to delete the test that used to be a Tensor and is now a Hamiltonian if it's causing headaches 😬

feel free to delete the test that used to be a Tensor and is now a Hamiltonian if it's causing headaches grimacing

All good. This change just needs to get merged into v0.30, and then onto master so that we can build and push the wheels for TestPyPI, so that the plugin test matrix can use it (phew).


Error: stack level too deep

brew doctor output
Error: stack level too deep
Please report this issue:
  https://docs.brew.sh/Troubleshooting
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:70:in `block in global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `global_deps_for'
...

Verification

[ ] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 3.6.12-17-g4abca3f
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4abca3fa1fe227389ebcace239ee219ec2c8da5b
Last commit: gpg: Signature made Tue Nov 22 04:13:00 2022 EST
gpg:                using RSA key 4AEE18F83AFDEB23
gpg: Good signature from "GitHub (web-flow commit signing<EMAIL_ADDRESS>[full]
2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: cda648379ec2486595f7f078f56c62c052f99335
Core tap last commit: gpg: Signature made Wed Nov 23 19:24:17 2022 EST
gpg:                using RSA key A43413FAF66A860AE649C28282D7D104050B0F0F
gpg: Can't check signature: No public key
6 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 2
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8_1/bin/ruby
CPU: dual-core 64-bit merom
Clang: N/A
Git: 2.38.1 => /home/linuxbrew/.linuxbrew/bin/git
Curl: 7.68.0 => /bin/curl
Kernel: Linux 5.4.0-132-generic x86_64 GNU/Linux
OS: Ubuntu 20.04.5 LTS (focal)
Host glibc: 2.31
/usr/bin/gcc: 9.4.0
Error: stack level too deep
Please report this issue:
  https://docs.brew.sh/Troubleshooting
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:70:in `block in global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
...

What were you trying to do (and why)?
brew update
What happened (include all command output)?
Error: stack level too deep
Please report this issue:
  https://docs.brew.sh/Troubleshooting
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:70:in `block in global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:70:in `block in global_deps_for'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `flat_map'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/dependency_collector.rb:69:in `global_deps_for'

What did you expect to happen?
brew commands to work as expected.
Step-by-step reproduction instructions (by running brew commands)
brew update

Appears to be a duplicate of https://github.com/Homebrew/brew/issues/14081 but the suggestion of brew update-reset does not resolve it for me.

The full log from a brew upgrade is too long to put in the issue so I've attached it here.
log.txt

I'm running into the exact same issue.  I've tracked this down and it should be fixed now.

What was the fix? @Bo98

What was the fix?

It was Homebrew/homebrew-core#116590.

Yes, sorry - I should have linked that.
We have checks in place to prevent this from happening, but they were not visible enough so human error meant it was missed. I am addressing that now.


Gh 1070: Merge develop

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: t92549:white_check_mark: p013570:white_check_mark: GCHQDeveloper314:x: GafferGaffer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


PR test for regression testing

Docs Build status updates of commit 8a780b8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

api/overview/azure/activedirectory.md
:white_check_mark:Succeeded
View

[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8a780b8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

api/overview/azure/activedirectory.md
:white_check_mark:Succeeded
View

[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8a780b8:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\e1tx-s, target branch: master, target branch commit: 0d3ef991f9d85aedfdc58d483d27fcae515333fb, source commit: 8a780b8d83a8f76bde640a5085359eaa87c1926d.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


fix: PR#88 – Update Gemfile(revise Liquid path)

The path /home/runner/work/blog/blog/RalphHightower/liquid does not exist.
Error: The process '/opt/hostedtoolcache/Ruby/3.3.4/x64/bin/bundle' failed with exit code 13


Using RIAS plugin with images loaded immediately

Hi,
I'm are using Lazysizes with the RIAS plugin to load images from the ReSRC service. Works really smooth!
But when there is an image that's always present in the head, like an article cover or something, I would like to load it immediately, not checking if it's in the viewport. Just use the RIAS plugin to set the correct height and width etc.
Is that in any way possible? What are your thoughts on this?

You could use the lazySizes.loader.unveil method. This would look something like this:
[].slice.call(document.querySelector('.header img.lazyload, img.loadimmediate').forEach(lazySizes.loader.unveil);

A little lazier way would be to simply add the class lazypreload, but this only kicks in after the window is loaded.

Great suggestion! I'm going to implement this. Thank you :)
One question: why do you use [].slice.call() around the document.queryselector? I assume this is necessary, but I've not seen this used before?

This kind of a workaround to transform a nodelist into an array. This only works with list, so I should have used querySelectorAll instead of querySelector. http://stackoverflow.com/questions/2125714/explanation-of-slice-call-in-javascript
In case you use jQuery, you can also do:
$('.header img.lazyload, img.loadimmediate').get().forEach(lazySizes.loader.unveil);

//or
$('.header img.lazyload, img.loadimmediate').each(function(){
    lazySizes.loader.unveil(this);
});

Allright, thanks for clearing that up. And thanks for the quick replies!


Support Django 1.11

@slurms thanks!

All good :+1:, would it be possible to make a pypi release too?

Will do


NOT FOUND exception on subsequent runs

Output:
$ flo run
Traceback (most recent call last):
  File "/usr/local/bin/flo", line 14, in <module>
    run_subcommand(args)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/__init__.py", line 48, in run_subcommand
    command.execute(**args.__dict__)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/run.py", line 58, in execute
    self.inner_execute(task_id, start_at, skip, only, force)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/run.py", line 48, in inner_execute
    self.task_graph.run_all_out_of_sync(mock_run=mock_run)
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 402, in run_all_out_of_sync
    self._run_helper(self.get_out_of_sync_tasks(), do_run_func, mock_run)
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 373, in _run_helper
    self.logger.info(self.duration_message(starting_tasks))
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 336, in duration_message
    for task in self.iter_tasks(tasks):
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 106, in iter_tasks
    raise Exception("NOT FOUND %s" % ([t.id for t in horizon], ))
Exception: NOT FOUND [u'massage/poi/output']

Flo seems to get itself "out of sync" somehow:

The ones that are not found can change, but usually are ones near the bottom of my yaml file
Removing .flo and running fresh works fine. It only errors on subsequent runs.

Further:
$ grep massage/poi/output .flo/*
grep: .flo/archive: Is a directory
.flo/duration.csv:massage/poi/output,14.938328981399536
.flo/state.csv:config:massage/poi/output,f9b89a4c69de3782a97dee9d31973b1654904e8d
.flo/state.csv:massage/poi/output,3f176f19882306396675a4c4a0c3c4d168cf8c46

Also, I'm actively editing/enhancing my yaml file so that could be partly related.

It just happened to me again. This time it was after I added a line to an existing "depends" list.
Removing the entry from duration did nothing.
Deleting all lines in state.csv that related to the task and its added dependent works around the problem. i.e. seems to be related to state.csv and dependencies. The tasks that get exceptioned are not necessarily the ones causing the problem.

Here's another example:
I have a task defined like this:
---
creates: a/output
depends:
  - a/src
  - b/output
  - c/output
command: make a

Where all occurrences of src and output represent a directory.
Now I edit an SQL file inside a/src and get an error:
$ flo run
Traceback (most recent call last):
  File "/usr/local/bin/flo", line 14, in <module>
    run_subcommand(args)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/__init__.py", line 48, in run_subcommand
    command.execute(**args.__dict__)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/run.py", line 58, in execute
    self.inner_execute(task_id, start_at, skip, only, force)
  File "/usr/local/lib/python2.7/dist-packages/flo/commands/run.py", line 48, in inner_execute
    self.task_graph.run_all_out_of_sync(mock_run=mock_run)
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 402, in run_all_out_of_sync
    self._run_helper(self.get_out_of_sync_tasks(), do_run_func, mock_run)
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 373, in _run_helper
    self.logger.info(self.duration_message(starting_tasks))
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 336, in duration_message
    for task in self.iter_tasks(tasks):
  File "/usr/local/lib/python2.7/dist-packages/flo/tasks/graph.py", line 106, in iter_tasks
    raise Exception("NOT FOUND %s" % ([t.id for t in horizon], ))
Exception: NOT FOUND [u'd/output', u'e/output']

Both d and e are tasks that depend on a.
Editing .flo/state.csv manually and removing the line starting with a/output, fixes it.

It would seem that there's probably some logic error in this code:
        source_tasks = tasks or self.get_source_tasks()
        distances = {}
        horizon = list(source_tasks)
        done, horizon_set = set(), set(source_tasks)
        source_tasks = set(source_tasks)
        while horizon:
            # before popping task off the horizon list, make sure all
            # of its dependencies have been completed
            found = False
            for task in horizon:
                if (
                    task in source_tasks or
                    not task.upstream_tasks.difference(done)
                ):
                    found = True
                    break

I can't get my head around what exactly it's doing yet, however I find it strange to see a for task in horizon inside a while horizon loop.
@deanmalmgren I don't suppose you'd help stamp out this bug? Unfortunately I hit it pretty much every time I change anything in a dependency directory.

One final (I think) update for now: this problem only seemed to start once my flo.yaml got larger. i.e. I built up 10+ tasks and some dependencies initially with no problems. So I have a suspicion that it might have started once my dependency depth reached 2 (i.e. tasks relying on tasks relying on tasks).

@rarkins Sorry for the slow response. I've been onsite with a client the last two days and didn't get a chance to help out. If you have a chance to send along the output of flo archive, I can try and take a look at what's going on.
Its hard for me to debug without a bit more information.
Thanks,
Dean

Hi @deanmalmgren: never any need to apologise when supporting open source!
It looks like flo archive sucks up all the data with it? Actually the directory names are even sensitive, let alone the contents. I guess if my troubleshooting and code exploration so far is not enough then I'll need to find a way to reproduce it with a dummy data set.

Hmmm.. Yeah, it would be good if we can reproduce with a separate flo.yaml then. Maybe throw it in a gist or something?

I'm not sure if/how I can do it, but will try to build it up sometime.


Write in port serial

Greeting
What should I do if I want to write something in the serial port?
Everything in the library is great ♥
Thanks

😨Sorry for that, I forgot add write method to this libaray. I will add this methond now! Please wait a moment

I have updated Write API and doc in pub packages. Now you can write something in the serial port.
This function has been tested in STM32 board.

Thanks for following up


Run in both OS

Hii Flutter Team,
I m Akshay Pujari From India I Make an Small Mobile App Using Flutter in Android Studio and Run on Android Device It seen's fine,
But now I want to Run Same App in IOS Device Using Android Studio so how can i run in my app in IOS
Device Please Help me
System Info.
OS : I Have Windows 10

@ragasubekti is correct; you unfortunately do require a Mac to compile and run for iOS:

To develop Flutter apps for iOS, you need a Mac with Xcode 9.0 or newer

https://flutter.io/setup-macos/#install-xcode


Bug on Freebie Points

There is a issue on freebies points, I'll just put the steps to reproduce it.

Open a new sheet
Put any quantity of points on any Discipline
Toggle Freebie Mode
Put 2 points on the same Discipline added early
Remove the the freebie from that Discipline clicking on the first dot (not the last one)

You will end up with extra 7 points, and it can be repeated undefined.

Thanks for opening, I'll get to it!


Upgrade to<EMAIL_ADDRESS>

Fixes #157

Thanks for the PR! Are the linting issues from your fix or because of a rustfmt / clippy update?

They all seem unrelated.

Alright, I'll fix them later then. Thanks again for the PR!


[ZEPPELIN-287] Adds proper standard output capturing to FlinkInterpreter

The FlinkInterpreter only captures output to Console and, thus, misses all output which goes to System.out. Some of Flink's functions, such as DataSet[T].print(), print their results to System.out. Consequently Zeppelin's interpreter misses this output. This PR fixes this behaviour by redirecting System.out and by setting System.out as the PrintStream for Console.

Looks good to me


Unable to download Facebook private video

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.03.14. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.03.14

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl - v "https://www.facebook.com/yousef.leaue.65/videos/143454699809423/" --username **** --password ****
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.facebook.com/yousef.leaue.65/
videos/143454699809423/', '--username', 'PRIVATE', '--password', 'PRIVATE']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2018.03.14
[debug] Python version 3.4.4 (CPython) - Windows-2012ServerR2-6.3.9600
[debug] exe versions: ffmpeg N-90313-gb173e03536, ffprobe N-90313-gb173e03536
[debug] Proxy map: {}
[facebook] Downloading login page
[facebook] Logging in
[facebook]<PHONE_NUMBER>09423: Downloading webpage
[facebook]<PHONE_NUMBER>09423: Downloading webpage
ERROR: Cannot parse data; please report this issue on https://yt-dl.org/bug . Ma
ke sure you are using the latest version; type  youtube-dl -U  to update. Be sur
e to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph71axfm2\bu
ild\youtube_dl\YoutubeDL.py", line 785, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph71axfm2\bu
ild\youtube_dl\extractor\common.py", line 440, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph71axfm2\bu
ild\youtube_dl\extractor\facebook.py", line 422, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmph71axfm2\bu
ild\youtube_dl\extractor\facebook.py", line 337, in _extract_from_url
youtube_dl.utils.ExtractorError: Cannot parse data; please report this issue on
https://yt-dl.org/bug . Make sure you are using the latest version; type  youtub
e-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and inclu
de its complete output.
...
<end of log>

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
The problem is when i want to download a private video from facebook but its not working anymore, i tried to download a public video without logging in but it worked, please take a look at the log.

Could you please give me an specific time till it get fixed?

No ETA.


fix selector

fix bug in selector, the new unit test will not pass without this fix. (stuck on the Select() call)

Coverage increased (+0.2%) to 65.452% when pulling 75f505a028a2987e555fed6fb49e7abae3a49be9 on yiminc:fix_selector into 9ec7b2a3e47d1b625b4d25cc39d7442d440189e9 on uber-go:master.


Panic recovery

When a panic is raised in an handler, server doesn't catch and manage this panic to return a status 500 (Internal Server Error) response. Instead, it returns nothing to the client. This is demonstrated with this code:
package main

import (
	"github.com/gin-gonic/gin"
	"github.com/long2ice/swagin"
	"github.com/long2ice/swagin/router"
	"github.com/long2ice/swagin/swagger"
)

func main() {
	app := swagin.New(swagger.New("SwaGin", "Swagger + Gin = SwaGin", "0.1.0"))
	app.GET("/", test)
	if err := app.Run(); err != nil {
		panic(err)
	}
}

var test = router.New(
	&Test{},
	router.Summary("Test query"),
	router.Description("Test query model"),
)

type Test struct{}

func (t *Test) Handler(ctx *gin.Context) {
	panic("test")
}

This can be fixed adding a recovery handler to the Gin engine. This handler will trap the panic and return appropriate response to client.

Just use app.Use(recovery())


Expose the Pointer trait as public

This PR makes the following changes:

Mark Pointer as public.  This is necessary for the crates that implement data structures which expose Atomic-like API (e.g. store() and compare_and_swap()).
I'm thinking of concurrent ART as a use case.  It's basically the infinite array of Atomic<T>, where initially everything is just Atomic::null().  Basically, I'd like to expose Art::store<P: Pointer<T>>(index: usize, value: P).

Add #![deny(missing_docs, warnings, missing_debug_implementations)], which is generally a good thing.

@stjepang I couldn't think of that :)  I changed it to #![warn(missing_docs, missing_debug_implementations)].

@stjepang I'm happy with from_usize and into_usize.  I initially thought from_raw and into_raw, but they probably have a connotation with raw pointers.

@Vtec234, any thoughts on this rename?

Based on two approvals, I'm merging it.  Thanks!


feat: upgrade to Patternfly v5

I used @patternfly/pf-codemods to upgrade most of the things, then fixed errors and some warnings. And upgraded some tables. In the next iteration I will ged rid of the rest deprecated components, mainly Selects and Dropdowns.

Thanks @tadayosi for careful review - I admit, I simply assumed Matej did the best.

@tadayosi thanks for the review I will comment.

Thanks @tadayosi for careful review - I admit, I simply assumed Matej did the best.

Well I did:), or at least I tried diven that time and space ;)

finished review. at this point I'd like to request changes, as the way you changed around the curried callback functions is alarming and suspected that it breaks the code. please check them again.

Thanks for the review, as I mentioned you're right, I missed curried signatures of the functions. It also discovered other thing, and that is that are unit test suite could be better too.


How are the RSSI Values created?

I was trying to dig through the code as I am using this as a low cost sensor for some RF research to figure out what the outputted value represents. The best guess I have is that its an RCPI 8bit between 0-220 (as comments I found indicated min values were 90 and max were 220) but I am not sure if that mapping is correct.
Any information about the exact details would be helpful.

In receiver.cpp you can see the analogRead function which reads the RSSI value.
The below link explains the returned value 😃
https://www.arduino.cc/en/Tutorial/AnalogInput

Okay, so if I am understanding this correctly: mapping 0-1023 from 90 to 220 or 0 to 100. Therefore 90 would equal 0 Volts and 220 should equal 5V or 100%.

The RSSI min/max output range isn't from 0 to 5v, but more like 0.5 to 1.2.  Hence the min and max calibration values are only ~90 to ~220.
The 0 to 100 conversion you see in the code is to normalise Rx modules on the same scale. It then makes it easy to see a 2% difference, which is the threshold for switching between the Rx modules.


Deploys in ap-southeast-4 fail with transform error

Describe the bug
Deploying to ap-southeast-4 fails with:
Fragment returned by transform AWS::Serverless-2016-10-31 is null. Rollback requested by user.

Steps To Reproduce
Steps to reproduce the behavior:

Follow the quick start guide in the readme (create config.json and deploy it via CLI to ap-southeast-4), or run this command:

aws cloudformation create-stack \
  --region ap-southeast-4 \
  --output text \
  --stack-name buildkite \
  --template-url "https://s3.amazonaws.com/buildkite-aws-stack/v6.28.0/aws-stack.yml" \
  --capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM CAPABILITY_AUTO_EXPAND \
  --parameters "[{\"ParameterKey\":\"BuildkiteAgentToken\",\"ParameterValue\":\"TokenGoesHere\"},{\"ParameterKey\":\"KeyName\",\"ParameterValue\":\"default\"},{\"ParameterKey\":\"ImageId\",\"ParameterValue\":\"\"}]"

Navigate to the CloudFormation dashboard
Deploy fails with above error

Expected behavior
Deployment succeeds
Actual behaviour
Deployment failed: "ROLLBACK_COMPLETE":
Fragment returned by transform AWS::Serverless-2016-10-31 is null. Rollback requested by user.

Stack parameters (please complete the following information):

AWS Region: ap-southeast-4
Version: latest (6.30.0)

Additional context
Not sure what resources are missing in ap-southeast-4 that causes this issue, quite unfamiliar with CloudFormation templates.

Thanks @J-tt, that's annoying. This is the first we've heard of this. It seems maybe that AWS::Serverless-2016-10-31 transform might not be functioning in ap-southeast-4. This could be because it is not fully supported there, or one of the services it interacts with. Have you raised this in a ticket with AWS?

Hi @DrJosh9000 I haven't raised it with AWS, as I'm not 100% sure what the root cause is.
I'll look at filing this issue over at https://github.com/aws/serverless-application-model as well

@J-tt I did a bit of digging and https://docs.aws.amazon.com/general/latest/gr/serverlessrepo.html which we use to distribute the autoscaler  isn't supported in Melbourne yet. 😞
You can modify the stack to work around this but it is certainly not ideal, so we will raise it with AWS to add our 👍🏻 to getting it deployed there 🤞🏻 cc @DrJosh9000


Update to gradle version 4.9

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


Possible Memory Leak?

16 Mar 19:42:11 - info: Reloading watcher...
(node) warning: possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit.

I'm using the Phoenix Framework with Elixir which in it's most recent release included brunch to automatically build static assets. I was playing around with the config and restarting the Phoenix server quickly when I got this message. Should I be concerned?

Here is the stack trace:
Trace
  at Socket.addListener (events.js:179:15)
  at Socket.Readable.on (_stream_readable.js:671:33)
  at bindWatcherEvents (/home/elbow/Prospace/juice/node_modules/brunch/lib/watch.js:567:21)
  at /home/elbow/Prospace/juice/node_modules/brunch/lib/watch.js:636:11
  at /home/elbow/Prospace/juice/node_modules/brunch/lib/watch.js:527:18
  at /home/elbow/Prospace/juice/node_modules/brunch/lib/watch.js:178:14
  at /home/elbow/Prospace/juice/node_modules/brunch/node_modules/async-each/index.js:24:44
  at /home/elbow/Prospace/juice/node_modules/brunch/lib/watch.js:165:16
  at FSReqWrap.cb [as oncomplete] (fs.js:228:19)

It probably isn't problematic (in fact, I think recent versions of node have dropped this EventEmitter warning), but I don't really understand the circumstances under which you made this happen. Brunch restarts its internal processes upon a config or package.json change, so I was guessing that if you do that enough times you can end up binding too many listeners to the the watcher's events, but part of the logic there is to close the prior watcher instance.
If you can provide clearer steps to reproduce it would be helpful.

I am using Phoenix Framework which is starting brunch each time it starts up. I restarted the Phoenix server process (which also restarts brunch) repeatedly in quick succession and got this error message. That's really all that was going on at the time. Rapid server restarts.

If it happens again I will be sure to better document the exact circumstances of the occurrence. Sorry for being so vague.

I just tried to reproduce this by touching the config file repeatedly while watch was running, but brunch was able to restart the watcher dozens of times without triggering the event emitter warning.
Closing for now.


Shell integration: Explore decorations in xterm.js

This would let us show decorations in the buffer, now that we understand more about it https://github.com/xtermjs/xterm.js/issues/1852

Can i say i hate this feature? I really do, it covers up the prompt and doesn't add anything of value (i can select things myself, thank you very much)

@pitust it's off by default, don't turn it on if you don't like it

@pitust shell integration is off by default, but if you have that turned on the decorations will appear. It shouldn't be covering up the prompt, that would be a bug. It's been under heavy development the last 2 weeks and has been in a not so great state because of that.
You can turn off the decorations currently by setting this:
  "terminal.integrated.shellIntegration.commandIconDefault": "",
  "terminal.integrated.shellIntegration.commandIconError": "",
  "terminal.integrated.shellIntegration.commandIcon": "",

This will likely change though as that's not that easy to figure out.

Created https://github.com/microsoft/vscode/issues/143737 to follow this up


Validating the DID address

I have found that
did:dxp:yvjnYLNujCX5qfow3qMCgf/Yl9kobOEqzgwiChyIFGb1GM8AZOeWxsuj7TQk7Aic5EJdzuhevwqW8tDGaMz6yY8YIu5lgbwYihHn
is still matched with
^did:(dxp:|sov:)([a-zA-Z0-9]){21,22}([/][a-zA-Z0-9:]+|)$
is that a bug?

Hi jjhesk. This is accepted as the crucial part of the DID is ([a-zA-Z0-9]){21,22}. What comes after the slash / can be any arbitrary alphanumeric string. Might change this in the future and make it more restrictive. Closing the issue for the meantime. Thanks!


Prefer to not use the global registry

Projects which import Prometheus sometimes need to use their own registerers. This PR is an example implementation which would allow that to happen.
What I have not yet done:

I haven't tested this locally.
I haven't implemented this for all service discovery components. But if you confirm that the approach makes sense, I could do it for the rest of them too.

A few unknowns:

What is a good way of testing this change?
Do I need to add any unit tests?
Is it ok that SD components will panic if more than one tries to use the default registerer? This is a breaking change.
Is it ok that some metrics won't be visible now if components aren't setup in the config? E.g. if a SD component is not used, there won't be metrics for it. This is a breaking change.

Closes #12549

Do I need to add any unit tests?

On the face of it, no.  There are existing tests checking metrics.

Is it ok that SD components will panic if more than one tries to use the default registerer? This is a breaking change.

I didn't understand this question.

Is it ok that some metrics won't be visible now if components aren't setup in the config? E.g. if a SD component is not used, there won't be metrics for it. This is a breaking change.

That sounds OK to me.

Is it ok that SD components will panic if more than one tries to use the default registerer? This is a breaking change.

I didn't understand this question.

I guess this can only happen if the Prometheus code is used as a library (because Prometheus itself would never use multiple instances of the same SD). In the former case, I think panic'ing is even better than silently sharing the same metrics. (So it's a "breaking change" only for those that use Prometheus code as a library? Would be good indeed if you could clarify what you mean by "breaking change" here.)

Is it ok that some metrics won't be visible now if components aren't setup in the config? E.g. if a SD component is not used, there won't be metrics for it. This is a breaking change.

That sounds OK to me.

I think it's even better than before. Seeing tons of metrics for all the SD methods that I'm never going to use is annoying. Note that we explicitly allow changes in the exported metrics without bumping the major version. See https://prometheus.io/docs/prometheus/latest/stability/#api-stability-guarantees (“Things considered unstable […]: The metrics in the /metrics endpoint of Prometheus itself”).
I think this is an incremental improvement, and the same idea could be pushed further incrementally until we don't use the global registry anymore directly.
@roidelapluie we didn't really get to this during the bug scrub. If you have any objections, please make them known. Otherwise, I think @ptodev should finalize this PR. The aforementioned further increments can be done later at will.

Is it ok that SD components will panic if more than one tries to use the default registerer? This is a breaking change.

I didn't understand this question.

I guess this can only happen if the Prometheus code is used as a library (because Prometheus itself would never use multiple instances of the same SD). In the former case, I think panic'ing is even better than silently sharing the same metrics. (So it's a "breaking change" only for those that use Prometheus code as a library? Would be good indeed if you could clarify what you mean by "breaking change" here.)

This clarification is correct - it is only a "breaking change" for those that use Prometheus code as a library. For those folks, it won't be possible to use multiple instances of the same SD component with the global registry anymore, because the SD components no longer register their metrics using an init() function. As far as I can tell there is no advantage to using global metrics and an init() function, but I want to highlight this here since it's technically a breaking change.

Thank you for the feedback, @bboreham and @beorn7 ! Since there are no objections to the idea of moving away from the global registry, I polished the PR and it is now ready for review.

Situations where a SD might get recreated, in which case the metrics will get registered again to the same reistry, causing a failure.

If that ever happens legitimately, then we needed to come up with a way to un-register. Or use this pattern (but is a bit frowned upon). For now, I would expect that this case doesn't happen.

Places where we are not setting a registerer in DiscovererOptions. In that case the registerer would be nil, and the metrics registration would fail.

A pattern used at some places is to allow a nil registerer and treat it as "I don't want any metrics to get registered". I.e. you simply have to guard the Register call by a if reg != nil { ... }. That's actually quite convenient if you want to use the library in a test or something, where you aren't interested in the metrics, and instead of passing in a dummy registry, you can just say nil.

And BTW, I chatted with @roidelapluie . Generally, he likes what you are doing here. So let's brush up final things here (like the nil registerer case discussed above), and then I can do the final code review.

Situations where a SD might get recreated, in which case the metrics will get registered again to the same reistry, causing a failure.

If that ever happens legitimately, then we needed to come up with a way to un-register. Or use this pattern (but is a bit frowned upon). For now, I would expect that this case doesn't happen.

Unfortunately I just realised there is a situation where we could indeed register the same metric twice. It would happen during a config reload. I see this error when trying a reload locally:
ts=2023-09-20T11:15:41.195Z caller=manager.go:319 level=error component="discovery manager scrape" msg="Cannot create service discovery" err="failed to register metric: duplicate metrics collector registration attempted" type=file config=prometheus

I think a nice way to solve this is to have the discovery.Manager manage metric registration and unregistration. I pushed a commit which implements this for Consul SD. Would you mind taking a look and letting me know if this would be ok please?
The bad thing about unregistration is that metrics will be cleared each time there is a config reload (e.g. counters would start from 0). However, I think this is the expected behaviour - there are other places in the code which do delete series with certain labels when config is reloaded (e.g. the stop() function for the scrape pool).

Places where we are not setting a registerer in DiscovererOptions. In that case the registerer would be nil, and the metrics registration would fail.

A pattern used at some places is to allow a nil registerer and treat it as "I don't want any metrics to get registered". I.e. you simply have to guard the Register call by a if reg != nil { ... }. That's actually quite convenient if you want to use the library in a test or something, where you aren't interested in the metrics, and instead of passing in a dummy registry, you can just say nil.

The first time I worked on this PR, I did actually implement it this way - if a nil registerer was passed to a SD, then it was ignored with no error. However, later I changed it to always requiring a registerer to be present. I like this approach more even in tests, because it helped me catch certain errors. Would you mind if we continue treating a nil registerer as an error please?
I just realised the current implementation will probably panic if a nil Registerer is passed to an SD. I could change it to returning an error instead of panicking?

All good points. First the simple answers:

Offering a "metrics no-op mode" when nil is passed in as a Registerer is a convenience feature for those using the Prometheus code as a library. We should ask them what they want. And I guess you are their representative here. If you think you don't need it, that's fine.
If you want to enforce passing in a non-nil Registerer, I think it is fine to panic because it can be seen as a programming error rather than something that happens based on user input or other external circumstances. But you should clearly document that a nil Registerer will cause a panic.
Unregistering metrics and starting counters from zero upon config reloads is probably fine. Depending on the situation, it might even be desired (for example if the used labels change due to the config reload – you don't want unused metrics to hang around).

I'll comment on the double registration problem as a follow-up to the separate comment above.

@beorn7, thank you so much for the help with this PR! It is a very big one, so I am going to close it and will instead open two PRs in its place - one for the scrape package, and another for the SD.
The PR for the scrape package is open for review - please feel free to take a look at #12958
I hope that by having the changes in two PRs they will be easier to review and easier to test.


[6.0🍒] Use new noncopyable infrastructure

cherry-pick of https://github.com/apple/swift/pull/72276 that just missed the creation of the 6.0 branch.
relies on friend PR https://github.com/apple/llvm-project/pull/8420

https://github.com/apple/llvm-project/pull/8420
@swift-ci test


[CSM-363, CSM-364] Fix bugs in JSON import/export (version for 0.5 branch)

Copy of https://github.com/input-output-hk/cardano-sl/pull/1152 for to provide fix for 0.5 release

@flyingleafe can you rebase on top of master?

@domenkozar the same PR but to master is here: https://github.com/input-output-hk/cardano-sl/pull/1152
or did I misunderstood what do you want me to do?

Sorry about the confusion, you're right :) I think we'll just have to wait for https://github.com/travis-ci/travis-build/pull/1112 to be merged first.

@flyingleafe please make a PR which merges it to master. You should use -s ours I suppose.

@flyingleafe ping

@flyingleafe ping, it's quite important as it blocks everyone else who commits to 0.5.

@flyingleafe ping

@gromakovsky how about https://github.com/input-output-hk/cardano-sl/pull/1152?

Yes, but these commits are not in master. See this guide: https://serokell.slack.com/archives/G3JSNBZDY/p1498916165937939

8d3b70a3f should be parent of master but it's not.
gromak ~/Work/cardano-sl (cardano-sl-0.5|…) % git branch --contains 8d3b70a3f                                                                                141 :(
* cardano-sl-0.5

The easiest way to resolve it is to do git merge 8d3b70a3f -s ours from master.

@gromakovsky the thing is that master is protected, so I cannot do it in such an easy way. I, of course, can make another PR and trigger CI and so on, but it seems like it would be much easier if some developer with rights merge it to master directly that way ;)

@flyingleafe I can do it in this particular case because we started this discussion already and because we have problems with CI anyway.
But in general workflow is that after your commits appear in release branch, you are responsible for making sure they will appear in master.

It won't take more than a minute to make a PR.
Other people may be not sure whether it's ok to merge with -s ours. Even if there is a twin PR, it can be the case that you suddenly realized something new during migration to the release branch. Or there is another reason not to use -s ours. Moreover, other people shouldn't check whether there are some changes in release branch which can be merged with -s ours.
So you should notify someone else about it.
That being said, if you ask someone explicitly to merge your commits, it's a bit distractive, but if you make a PR, it's a regular flow. Someone will approve and merge it later. If you really don't want to wait or load CI, you can make a PR and ask someone to merge it w/o passing checks (which is fine when there are no changes). But again, it should be done when PR is ready, because sometimes it's inconvenient for others to stop their work, switch to another branch, merge, etc.

Ok, done, but that's exceptional case.


WOTS layer-> Migrate to flex trits

#541 switched the state to flex_trits.
Due to sponge dependency, some WOTS API parameters are still trits_t.
See TODOs in mam/v2/wots.c.


Update Deltaglider.netkan

Closing in favour of c0a6e219ec06205b58a7667f16c2c03611810cb9 , which I'm about to test. :)


Fields are repeated in JSON Schema completions

Not sure who is at fault (the schema or the plugin):

Schema looks fine so not sure what's up.

Must be a bug in the plugin, I don't have this problem in PyCharm.


Train a model based on the assigned classes

Also need to show model evaluation metrics (accuracy f1 etc) so that the user knows how accurate the model is expected to be.


Link to Dat Desktop in README.md is incorrect.

Just noticed that the link to the Dat Desktop application provided in the readme (see:  https://github.com/datproject/dat#desktop-applications) points to an anchor that doesn't exist, on a page without the relevant information.
Currently: https://docs.datproject.org/install#desktop-application
Should be: https://github.com/datproject/dat-desktop ?

Good catch. Would you be up for submitting a pull request with the change? 😁

Yep, no worries!

Thank you!


Documentation: How to use ssh connection

Hi,
thank you very much for starting this nice package.
Could you please provide one example that shows how to execute the commands on a remote host? I've tried to set host='ssh://user@ip', unfortunately without success (the host runs docker and is accessible, validated via docker-py). Connecting to the local machine seems to work.
client = DockerClient(
    config=client_config,
    context=None,
    debug=None,
    host='ssh://user@ip',
    log_level=None,
    tls=None,
    tlscacert=None,
    tlscert=None,
    tlskey=None,
    tlsverify=None,
    client_config=None,
    compose_files=[],
)
client.info()
ValidationError: 53 validation errors for SystemInfo
ID
  field required (type=value_error.missing)
Containers
  field required (type=value_error.missing)
ContainersRunning
  field required (type=value_error.missing)
ContainersPaused
  field required (type=value_error.missing)
ContainersStopped
  field required (type=value_error.missing)
Images
  field required (type=value_error.missing)
Driver
  field required (type=value_error.missing)
DriverStatus
  field required (type=value_error.missing)
DockerRootDir
  field required (type=value_error.missing)
Plugins
  field required (type=value_error.missing)
MemoryLimit
  field required (type=value_error.missing)
SwapLimit
  field required (type=value_error.missing)
KernelMemory
  field required (type=value_error.missing)
CpuCfsPeriod
  field required (type=value_error.missing)
CpuCfsQuota
  field required (type=value_error.missing)
CPUShares
  field required (type=value_error.missing)
CPUSet
  field required (type=value_error.missing)
PidsLimit
  field required (type=value_error.missing)
OomKillDisable
  field required (type=value_error.missing)
IPv4Forwarding
  field required (type=value_error.missing)
BridgeNfIptables
  field required (type=value_error.missing)
BridgeNfIp6tables
  field required (type=value_error.missing)
Debug
  field required (type=value_error.missing)
NFd
  field required (type=value_error.missing)
NGoroutines
  field required (type=value_error.missing)
SystemTime
  field required (type=value_error.missing)
LoggingDriver
  field required (type=value_error.missing)
CgroupDriver
  field required (type=value_error.missing)
NEventsListener
  field required (type=value_error.missing)
KernelVersion
  field required (type=value_error.missing)
OperatingSystem
  field required (type=value_error.missing)
OSType
  field required (type=value_error.missing)
Architecture
  field required (type=value_error.missing)
NCPU
  field required (type=value_error.missing)
MemTotal
  field required (type=value_error.missing)
IndexServerAddress
  field required (type=value_error.missing)
RegistryConfig
  field required (type=value_error.missing)
HttpProxy
  field required (type=value_error.missing)
HttpsProxy
  field required (type=value_error.missing)
NoProxy
  field required (type=value_error.missing)
Name
  field required (type=value_error.missing)
Labels
  field required (type=value_error.missing)
ExperimentalBuild
  field required (type=value_error.missing)
ServerVersion
  field required (type=value_error.missing)
Runtimes
  field required (type=value_error.missing)
DefaultRuntime
  field required (type=value_error.missing)
Swarm
  field required (type=value_error.missing)
LiveRestoreEnabled
  field required (type=value_error.missing)
Isolation
  field required (type=value_error.missing)
InitBinary
  field required (type=value_error.missing)
ContainerdCommit
  field required (type=value_error.missing)
RuncCommit
  field required (type=value_error.missing)
InitCommit
  field required (type=value_error.missing)

Hello! I have to admit that it's strange and could be more documented. Here it what I do to get the containers of a server in my company:
In [1]: from python_on_whales import DockerClient

In [2]: docker =<EMAIL_ADDRESS>
In [3]: docker.ps()
Out[3]:
[<python_on_whales.components.container.cli_wrapper.Container at 0x7f18a29410a0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941340>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941040>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a29412e0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941610>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e280>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e5e0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e5b0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207ef70>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207eaf0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e9d0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207ea90>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e310>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e430>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a1476280>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a1476a90>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a14764f0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a14760d0>]

Hi  gabrieldemarmiesse,
I managed to get it running. The problem was a malformed $PATH (os.environ), such that ssh could not by launched. This problem was not present with docker-py, I guess paramiko found a way somehow.
Not I can run .ps() or .info() and ssh is invoked. The problem is now, that after I restart python and I run a solution based solely on python-on-whales instead of docker-py, I am not able to unlock my private key. Any idea how I can unlock the keyfile (like running ssh-add)?
from python_on_whales import docker, DockerClient

client =<EMAIL_ADDRESS>client.ps()

The docker command executed was `/usr/bin/docker --host<EMAIL_ADDRESS>container list -q --no-trunc`.
It returned with code 1
The content of stdout is ''
The content of stderr is 'error during connect: Get http://docker/v1.24/containers/json: command [ssh -l user -- xxx.xxx.xxx.xxx docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=Permission denied, please try again.
Permission denied, please try again.
<EMAIL_ADDRESS>Permission denied (publickey,password).

Can you run
/usr/bin/docker --host<EMAIL_ADDRESS>container list

From your command line?

It works, however only if I run ssh-add in the same shell before executing the docker command:
/usr/bin/docker --host<EMAIL_ADDRESS>container list -a
CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS                     PORTS     NAMES
0d9be03b17f5   debian         "bash"                   8 seconds ago   Exited (0) 6 seconds ago             nice_meitner
74d6c142d27d   e1b5b7b06862   "/bin/sh -c 'mkdir -…"   22 hours ago    Exited (0) 22 hours ago              interesting_pike
129ca9a96f0c   24682118fcbf   "/bin/sh -c '#(nop) …"   22 hours ago    Created                              elegant_sammet
3162d82a2cbe   730cce28d0c8   "/bin/sh -c 'apt-get…"   22 hours ago    Exited (0) 22 hours ago              laughing_pascal
ef37c788fb0f   6bba76b56108   "/bin/sh -c 'apt-get…"   22 hours ago    Exited (0) 22 hours ago              hopeful_bohr
22aefb133d5c   6e3fa18e7bf7   "/bin/sh -c '#(nop) …"   22 hours ago    Created                              strange_carver
07b19b09fc77   9b5e75b69a4f   "/bin/sh -c '#(nop) …"   22 hours ago    Created                              hungry_sanderson

Without ssh-add, I get
error during connect: Get http://docker/v1.24/containers/json?all=1: command [ssh -l user -- xxx.xxx.xxx.xxx docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Permission denied, please try again.
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Permission denied, please try again.
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
<EMAIL_ADDRESS>Permission denied (publickey,password).

If you do the ssh-add before running python, does it work with python-on-whales (python-on-whales just calls the CLI, so all steps you use to make the CLI work, you should do them too with python-on-whales)

If I run ssh-add first, and then start python from the same shell, it works.
However, it would be more optimal to invoke ssh-add from within python, such that I can run an complex app (which imports python-on-whales) without the need to mess around with additional command calls before starting the app. Paramiko gives access to ssh agents. However, since ssh is handled entirely by docker here, I am not sure about how to combine paramiko and python-on-whales.

Paramiko has a very strange relation with the ssh binary. Some configs are ignored in paramiko and valid when using the command line. The settings are quite different too. This let to a lot of frustration from users in docker-py "it works from the command line, but not in docker-py, what is going on?".
Python-on-whales took the decision to rely on the docker binary entirely, which means that paramiko will not be useful here. You would need to call subprocess.call("ssh-add ..."). This has the benefit that users only need to know how to setup their ssh from the CLI. But it also means that paramiko will be useless.
The issues that made me take this decision:
https://github.com/docker/docker-py/issues/2289
https://github.com/docker/docker-py/issues/2398
https://github.com/docker/docker-py/issues/2416

I see, thank you very much for your support.
With your help I know managed to get it running:
from python_on_whales import docker, DockerClient
import pexpect
import os
import getpass
agent = pexpect.run('ssh-agent')
agent = [x.strip('\r\n ') for x in agent.decode('UTF-8').split(';')]
os.environ['SSH_AUTH_SOCK'] = agent[0].split('=')[-1]
os.environ['SSH_AGENT_PID'] = agent[2].split('=')[-1]

child = pexpect.spawn('ssh-add')
child.expect('Enter passphrase for .*')
child.sendline(getpass.getpass())

client =<EMAIL_ADDRESS>client.info()

Because I need to supply a password, subprocess.call did not worked for me. Using the module pexpect however was sufficient and now I can access a remote host over ssh.
Thank you!

Hello! I have to admit that it's strange and could be more documented. Here it what I do to get the containers of a server in my company:
In [1]: from python_on_whales import DockerClient

In [2]: docker =<EMAIL_ADDRESS>
In [3]: docker.ps()
Out[3]:
[<python_on_whales.components.container.cli_wrapper.Container at 0x7f18a29410a0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941340>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941040>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a29412e0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a2941610>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e280>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e5e0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e5b0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207ef70>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207eaf0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e9d0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207ea90>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e310>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a207e430>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a1476280>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a1476a90>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a14764f0>,
 <python_on_whales.components.container.cli_wrapper.Container at 0x7f18a14760d0>]

Maybe the bug doesn't come from the ssh, but from docker.info()?

I believe this means that your SSH keys are on your PC? I am using windows(local pc) and the docker I want to connect to is on a VPS. On the VPS, I've set the SSH keys but I have disabled password authentication, how do I use the password with the SSH ?

Hi @Smyja ! Do you manage to contact your server with the docker command line? Can you do something like:
docker --host<EMAIL_ADDRESS>container list

This would be a first step to make python-on-whales working over ssh.
Since python-on-whales is just a wrapper around the docker CLI, try to make the CLI work first. It's easier to debug.

Hi @Smyja ! Do you manage to contact your server with the docker command line? Can you do something like:
docker --host<EMAIL_ADDRESS>container list

This would be a first step to make python-on-whales working over ssh.
Since python-on-whales is just a wrapper around the docker CLI, try to make the CLI work first. It's easier to debug.

I get this error.
error during connect: Get http://docker/v1.24/containers/json: command [ssh -l root -- xxx.xx.xx.xx docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=Permission denied, please try again.
My docker version is 20.10.7


Update using-codecommit-with-sso.md

@bbsahoobyndr

Can we submit PR from feature branch and delete Develop
Change the title and remove : "Windows"   and call it : "AWS CodeCommit using AWS SSO"
For Step 6 , use codecommit:// instead of https for cloning


Support ESNI on All of Cloudflare-Enabled Sites

@DitFranXX commented on Mon Feb 11 2019

This is Feature Request, CC: https://blog.cloudflare.com/encrypted-sni/ https://encryptedsni.com/
All of CF-Enabled domain enabled ESNI as default. also Firefox has ESNI Implements which can be enabled by set network.security.esni.enabled to true (But it is not work with ADGuard with HTTPS Filtering because Site cert is Adguard Personal CA instead Cloudflare's cert.)
May this is issue of something called CoreLibs .

Steps to reproduce

Access any cloudflare enabled domain with /cdn-cgi/trace path
Access https://encryptedsni.com/

Expected behavior

sni=encrypted
SNI section has green check mark.

Actual behavior

sni=plaintext
SNI section has red X mark.

Your environment

ALL of HTTPS Filtering-able enviroment(Window, Mac, and Android)

@DitFranXX
We actually have another issue about it, but most likely we will have to split it into smaller tasks: #553
Supporting the CloudFlare draft implementation would be a good first step.

It's been 7 months. CoreLibs now 1.5. High priority, And milestone is targeting 1.4. When this feature implemented?

@DitFranXX
The milestone was set to v2.0, I don't know why in the GH history it shows v1.4.
The first pre-requisite is to start supporting DNS filtering and DNS encryption in desktop AdGuard products which is a huge task by itself. We cannot rely on plain DNS in ESNI.
Only after that, we can start working on ESNI. The problem is that the work on the ESNI specification draft is still a work-in-progress, and it seems that supporting the draft version by Firefox and Cloudflare does not make much sense now.

Closing as duplicate of #1565 which is already done


SetUserSSHPublicKeysPlugin incorrect path for Windows Administrator user

Hello,
SetUserSSHPublicKeysPlugin is always populating ~/.ssh/authorized_keys with public key (if provided).
but this path is incorrect for Administrative users.
as explained here: https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_keymanagement#administrative-user
authorized keys for Administrator user should be stored in C:\ProgramData\ssh\administrators_authorized_keys, not in C:\Users\username\.ssh\authorized_keys.
this bug results in inability to connect using ssh key authentication as Administrator even when correct public key was provided to SetUserSSHPublicKeysPlugin.

I think we need a new key for cloud-init config that will contain a list of SSH keys to add to this file.
Or maybe if the user is in the Administrators group, Cloudbase-Init should append their keys directly to C:\ProgramData\ssh\administrators_authorized_keys instead of creating C:\Users\username\.ssh\authorized_keys.


Bluetooth: controller: split: Fix aborting of connection req PDU

Fix the initiator so that connection request PDU is not abort
mid-air by preemption by the overalapping first connection
event.
If the connection establishment is in progress, then the
first connection event trying to abort the initiator will
wait the connection request to be transmited completely.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

@cvinayak can you fix CI?


[PLT-6656] Splitting LHS in subcomponents

Summary
Split the LHS into subcompnents, mainly a channel component to use to show each channel.
The next step is to convert the sidebar.jsx to a redux PureComponent.
Ticket Link
PLT-6656 (It doesn't fix the entire issue)
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Added or updated unit tests (required for all new features)
[x] Touches critical sections of the codebase (It touches the channels sidebar)

Not needed, contained in #422


[New Port Request] Clipper2

Library name: Clipper2
Library description:
A Polygon Clipping and Offsetting library (in C++, C# & Delphi)
Clipper2 is a major update of my original Clipper library which I'm now calling Clipper1.
Clipper1 was written over 10 years ago and still works very well, but Clipper2 is better in just about every way.
Source repository URL:
Project homepage (if different from the source repository):
https://github.com/AngusJohnson/Clipper2

Looking forward to this port.

I wonder if it can be used as a drop-in replacement, or if clipper and clipper2 can be installed/used side by side.

I wonder if it can be used as a drop-in replacement, or if clipper and clipper2 can be installed/used side by side.

It's not a drop in replacement, however the API is very similar. You can use them side by side without any issues. We do this currently in our project. I'd suggest leaving in the Clipper1 port and adding the Clipper2 as a new port.


Create Kruskal's_Algorithm.py

Kruskal’s algorithm to find the minimum cost spanning tree uses the greedy approach. The Greedy Choice is to pick the smallest weight edge that does not cause a cycle in the MST constructed so far.
Time Complexity: O(ElogE) or O(ElogV), Sorting of edges takes O(ELogE) time. After sorting, we iterate through all edges and apply the find-union algorithm. The find and union operations can take at most O(LogV) time. So overall complexity is O(ELogE + ELogV) time. The value of E can be at most O(V2), so O(LogV) is O(LogE) the same. Therefore, the overall time complexity is O(ElogE) or O(ElogV)
Auxiliary Space: O(V + E), where V is the number of vertices and E is the number of edges in the graph

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[x] New algorithm
[x] Optimization in previous algorithms
[x] Code style update
[x] Refactor
[x] Documentation
[x] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hi @Purvesh77,
This is the correct one?

@ming-tsai If U are able to merge it
Then Merge it else,I will not understanding it automatically closing PR.

Hi @Purvesh77,
Ok, please wait the reviewer check the pull request.

@ming-tsai What was the issue?

@Purvesh77 I don't know, but I just re-open it.