HttpCLientFactory correct usage to pass credentials and get access token

Following Curl script successfully returns the token from the Server
curl  "https://staging.tcsgsp.in/Tax-Tool-Core/services/accessMgmt/generateToken" -H  "accept: application/json" -H  "content-type: application/json" -H  "username: ********" -H  "password: ******"
And the following script generates the document on the Server
curl  -X POST "https://staging.tcsgsp.in/Tax-Tool-Core/services/auth/ewbApi/generateEwayBillNoDataApi" -H "content-type: application/json" -H "Authorization: Bearer 5cea--4aad-a02c-7fbc" -H "clientCode: xxx" -H "Gstin: 05XYZXYZXXR" -d @ewaybill.txt
In Dotnet Core 3.1 following code is in startup.cs
services.AddHttpClient("Get AccessToken", client1 => {
client1.BaseAddress = new Uri("https://staging.tcsgsp.in/");
client1.DefaultRequestHeaders.Add("accept", "application/json");
client1.DefaultRequestHeaders.TryAddWithoutValidation("Content-Type", "application/json");
client1.DefaultRequestHeaders.Add("username", "***");
client1.DefaultRequestHeaders.Add("password", "");
In Controller following code is in place
var client1 = _httpClientFactory.CreateClient("Get AccessToken");
var result = await client1.GetAsync("Tax-Tool-Core/services/accessMgmt/generateToken");
if (result.IsSuccessStatusCode)
{
var content = await result.Content.ReadAsStringAsync();
// return JsonConvert.DeserializeObject(content);
}
return null;
The above code returns error and we do not get the token.
Also I could not find any documentation on how to pass the credentials to get back token and
in the next step how to pass the token to the Server along with the  text file in the body and get the generated document
Is it possible to get the above tasks done through HttpClientFactory or we need some other classes?
Can anyone throw some light?
Thanks in advance.
Eshwar

@scalablecory is this System.Net or ASP.NET?

pay me

@eshwar-crystal were you able to figure this out? It looks like you need to run Fiddler to check how your request differs. You're using POST in one example but GET with HttpClient, for instance.


FUSETOOLS2-67 - provide more precise Diagnostic range for unknown option

not covered cases:

multiline Camel URI
unknown option which is a substring of another parameter on the same
line

please note that it would be better to have Camel validation result
returning a more precise range directly instead of calculating on
Language Server side
Signed-off-by: Aurélien Pupier<EMAIL_ADDRESS>Pull Request informations
Rebase & Merge default requirements

Green build for master branch
Wait 24 hours after PR creation
Green job for PR
Approved PR

PR labels default process

READY_FOR_REVIEW  →  REVIEW_DONE  →  READY_FOR_MERGE

Tests

[ ] Are there Unit tests?
[ ] Are there Integration tests?
[ ] Do we need a new UI test?

PR workflow progress

[ ] Tagged with relevant PR labels
[ ] Green job for PR
[ ] PR was created more than 24 hours ago or All committers approved it
[ ] Green master branch build

before:

with this PR:


Empty string content value in mixins is removed

Input:
.MyMixin {
  content: "";
}
.MyClass::after {
  .MyMixin;
}

Expected Output: (correct in <IP_ADDRESS> nuget package)
.MyMixin {
  content: "";
}
.MyClass::after {
  content: "";
}

Actual Output: (1.5.2 nuget package, and master branch as of today)
.MyMixin {
  content: "";
}
.MyClass::after {
  content: ;
}

This results in the ::after being completely ignored by the browser as it has no content.
Interestingly, putting parentheses after the mixin (.MyMixin() {) results in the expected behavior in all three versions.
.MyClass::after {
  content: "";
}

Am currently having the same issue in the newest version, 1.6.3.

This issue can be closed, was fixed in #556


Upgrade guide from 8.x to 9.x

Is there any breaking changes on 8.x to 9.x. Should updating from ~8.x to ~9.x be fine? Or there are some cautions that need to be followed?

Should be fine to upgrade from 8.x to 9.x directly. I think the major bump was only due to php version constraint.
https://github.com/yajra/laravel-datatables/blob/9.0/CHANGELOG.md#v900---2019-02-27


Improve and add docs to time modalities

Times intervals can be given in different modalities (see here). We should improve the source code, add proper documentation, and remove redundancies from AnnubesEnv class.

Kamino closed and cloned this issue to neurogym/neurogym


Decrease logging level for all apache projects

I'm using the Apache HTTP Client libraries with the DITA OT and lately starting with DITA OT 3.3.1 my console started getting flooded with debug messages coming from the library:
   [gen-list] [DEBUG] http-outgoing-0 >> GET http://devel-new.sync.ro/webdav-qa/DITA/flowers/topics/introduction.xml HTTP/1.1
   [gen-list] [DEBUG] http-outgoing-0 >> Accept: application/xml,*/*
   [gen-list] [DEBUG] http-outgoing-0 >> Accept-Encoding: gzip

These too verbose messages seem to be stopped if for example in the "config\logback.xml" we set to INFO all org.apache packages:
  <logger name="org.apache" level="INFO"/>

or at least add a specific rule for the http client:
 <logger name="org.apache.http" level="INFO"/>

Could you send a PR for the latter?


[BUG] Message Input height not corresponding to message content

Description
The message input height increases when the text grows, but does not decrease when the text length reduces (i.e when user deletes text, or clears the message entirely)
Screenshots
Screencast from 15-10-23 11:42:23.webm
Additional information
No response
🥦 Browser
Mozilla Firefox
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
None

Hii @Dun-sin @mathiasayivor  , i can fix it . can you please assign this issue it to me.

Hii @Dun-sin @mathiasayivor , i can fix it . can you please assign this issue it to me.

Sure, thanks for wanting to contribute, Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck

@JatinPhogat according to the guideline your time is up and if there's no PR by the end of the day, you will be unassigned

Hii @Dun-sin. I can fix this, can you assign me this issue.

Hii @Dun-sin. I can fix this, can you assign me this issue.

Sure, thanks for wanting to contribute. Make sure to read the issue description carefully and ask if you have questions. Follow the rules here, or your PR won't be accepted and will be closed. Good luck!


Per policy logging

This changes real time enforcer to emit log messages for each policy, even if the resource was found to be in compliance.  This is useful for producing evidence that the enforcement was in effect.
The structure is similar to the previous, but the counts have been removed (since they'd always be 1):
{
  "log_id": "-p8cng8e3225g",
  "policy": "versioning",
  "asset_info": {
    "resource_type": "storage.buckets",
    "resource_name": "01c5c681-f172-432c-85fc-3fff7e17a1e6",
    "resource_location": "us",
    "project_id": "yo-cool-project-dog",
    "method_name": "storage.buckets.create",
    "operation_type": "write"
  },
  "violation": true,
  "remediated": true
}

If no violation is found, violation is false.  If there was no remediation, or if remediation failed, remediation is false.

This also contains some clean up of logging in the cases where an intermediate step throws an exception.


Federated issue tracking

Problem

Ken on server A created an issue to Lennon's repository on server B.
Mandy on server B is a contributor to Lennon's repository.
Oprah on server C is also a contributor to Lenonn's repository.
Who should have the permission to close the issue? And how?

@tantek has experience on Github bridging. And he has some insight about cross domain permission handling. He raised interesting point in the ActivityPub community group meeting tonight that lead me thinking of this problem. (I think @cwebber tried to raise the same point but I was too stupid to pick up.)
The same problem also applies to a PR. Do we handle it? Or do we omit it?

IMHO the only way is for the original server to do access control. What does giving a remote user contributor access to your repository mean in terms of federation? Possibly it could be as simple as federating an activity indicating that "I user Ken grant Oprah contributor rights to my repository". This has several effects:

Oprah's server knows to display a "close" button. When she clicks it, her server will send an activity to Ken's server, who checks if Oprah is a contributor. She is, so Ken's server allows closing the issue.
Mandy also gets the contributor right change and sees the label "contributor" next to Oprah's name

Since Ken controls the issue, Ken's server needs to tell the other subscribers that the issue was closed. ActivityPub already has the forwarding mechanism. Other servers should maybe only accept issue closing from Ken's server, since he is the only one who really can say (as the owner of the repository) if the issue is closed. Of course if Mandy has received previously a message that Oprah is a contributor, her server could decide to accept an issue close from Oprah directly.
Just some thoughts, and a vote to keep things simple and work as close as possible to ActivityPub without complexity of figuring out totally new things like ACL's.

As written in another issue, an entire community exists around decentralized issue tracking. As I am more or less actively working on a such a system, I am a bit biased regarding this topic. Also, I did not (yet) have a look at how other distributed issue trackers ("dits"), like git-issues handle access control, so I can only provide what we do (or are planning to do) in git-dit:
In the case of dits, issues can be freely transferred from one repository to another, so an issue does live in any repository mirroring issues anyway. If an issue is altered in some way (e.g. an assignee is set), the change is only local but can be transferred to another repo using a fetch or push. Obviously, this allows for concurrent conflicting changes. In git-dit, we solved this problem by providing a mechanism by which a maintainer can select or simply set the state which should be considered up-stream for each issue.
Mere consumers of an issue simply refrain from setting this marker, or, if they have another opinion, they can override the upstream state by providing their own, locally. In the end, the access control becomes a matter of what repository you consider "upstream" and what changes are allowed by the maintainer. For large repositories with lots of issues being reported or commented, this is obviously not an option for the maintainer. For their side, we thought about having repos with global push-access, which are guarded by hooks enforcing arbitrary policies (e.g. assignees and maintainers can update the upstream state of an issue, we also provide an example).
I think this choice ("leave the policy-making to the maintainers of a project") is the only sensible option both for dits as well as a federation. Anything else would mean prescribing an exact access model, and in the end an exact workflow and thus limiting the user's freedom.
As for PRs: you should have an agreed-upon upstream master. Anything else means a fork which should probably be regarded another project. In such a situation, you have one master onto which, either directly or via possibly multiple stages, patches/merge commits are applied. I would rather not want to see a specific description about who is allowed to perform such actions in a specification of the communication protocol, but rather defined messages for requesting merges which can be either granted or denied based on a maintainer-specified policy.

I think it's fairly simple. The repositories don't "belong" to a server, they belong to a person or an organization. If I have permissions for a repository as an entity, then I should have the same permissions regardless of the server(s) that is on.
I feel it may be more productive to consider a server as two things:

A cache for repositories (to be synchronized with other caches).
Authentication gatekeeper to confirm identities of users and organizations.

@coderkevin: That is a very interesting idea. But if that's the case, we'd run into namespace collision / reservation issue. Say a repository named "foobar/hello" has a copy on server A and a copy on server B. And another totally different person wants to create another different software in the name of "foobar/hello" on server C. Should we stop that from happening? And how?
Having centralized service for name (user and organization identities) reservation would create a single point of failure. But without one, there is no sensible way to prevent name collision. Also that would be vastly different from most SCM software implementation today. I fear that could simply stop the protocol from being adopted by existing parties and thus weaken the federation itself.

@jaywink: For PRs closing, I agree its much simpler, thus practical, to have downstream sending a "close" request to upstream and leave the actual closing to upstream. That way we can circumvent the whole permission altogether. @neithernut seems to have the same opinion on this, if I'm not mistaken.
@neithernut: Issue syncing across platform is new to me. I'd love to hear more of it.

the most important point to make is that most if the talk on this thread in describing decentralized behaviour; but the goal is federation here and not merely decentralization - a good deal more care must be taken to maintain sanity and robustness - tools that support decentralization but not true federation would need to be modified to support a non-hierarchical workflow or else they will not be useful to anyone implementing a truly federated complete solution, neither will the protocol if it is coupled to such tools

Who should have the permission to close the issue? And how?

whoever ken has authorizes as collaborators - ken does this by interracting directly with his home-server by adding the peer's canonical and unique user-id e.g<EMAIL_ADDRESS>- kens server only needs to auth oprah against oprahs-homeserver.net when she interacts with kens repo - in a federated network, any modifications to "kens" repo that oprah makes by interacting only with her home-server can not be guaranteed to propagate to kens actual repo on kens home-server, nor that kens home-server will honor the request, or accept its historical information as truth, nor could that be done atomically as is required to maintain sanity - kens home-server keeps the state of kens repos and it must be the only keeper of the state of kens repos - if oprah wants to modify the state of kens repo, she must interact directly with kens home-server so that it can be done atomically - the only exception here is the that code and issues can be under version control; so for that subset of actions, the sanity of atomicity being can be replaced with merge conflicts because those can be resolved manually by the user with standard tools - if you must mirror issues and PRs it is most sensible to simply have them be git repos like pagure and deal with merge conflicts manually; or else you must revert to denoting one as canonical master and losing federation
the idea of maintaining a repo on a foreign server by interacting only with your home-server is not terribly useful - frankly its pretty goofy - in the end, every such action is a fiction until the canonical host validates and accepts them, which may not be satisfiable because they were not done atomically - it is the same reason why git commits and pushes are atomic
"cross domain permission" should not be desirable - just do "cross domain auth" and keep repo permission on the host where the repo lives - the only thing that the standard needs to ensure is that all identities are canonical and unique across the network

Oprah's server knows to display a "close" button. When she clicks it, her server will send an activity to Ken's server, who checks if Oprah is a contributor. She is, so Ken's server allows closing the issue.

again, that would be a terrible way to implement - oprah should not need to keep kens code on her home-server in order to collaborate on kens instance - oprah simply interacts with kens instance on kens home-server - kens home-server only needs to auth oprah against her home-server when she interacts with kens home-server

As for PRs: you should have an agreed-upon upstream master. Anything else means a fork which should probably be regarded another project.

another terrible implementation - completely at odds with the notion of federation - federation is antithetical to hierarchy - it simply is not possible nor desirable to denote one instance as having precedence over any other - if you implement that you do not have federation - git does not have a concept of a fork - there is just replica A and replica B - "forks" are an entirely logical and optional distinction; and therefore each server is free to implement that fiction any way they like (or ignore it) - all that is required for a pull request is a destination repo and branch and a patch to apply - any hierarchical distinction plays no role in that process

If I have permissions for a repository as an entity, then I should have the same permissions regardless of the server(s) that is on.

im not sure how to address that - realistically speaking, a repository absolutely "belongs" to a server - not in any logical sense, but in the strictest practical sense - the user who logically owns the repo may well have never been in the same room with that server, much less be the true owner of the hardware - just to put that into context, assuming all repos are freely licensed, it is the actual legal owner of the physical server box who actually legally owns all of the data on it - period - the software license grants that - not even the copyright holder has any claim to it - i.e. if you clone my repo from my server to your server, i do not have any permission on your server unless you grant it explicitly, and i should not - that is just a fact of reality - no protocol can speak to that, especially not when it is federated

in the pagure model issues are just git repos - that inherently makes it federated - new issues and issue comments then are just a git commits that can be handled in exactly the same way as a pull request against the code repo - as no external tooling would be required for that it seems the simplest razor solution - it can be argued that the protocol should not assume the implementation but we are talking about git forges and pull requests are an intrinsic feature that needs to be specified anyways - even if not implemented as a git repo on a particular server, making a patch file of the issue in order to fake a pull request seems like very simple adaptor - in any case it would be highly desirable that entire issue sets can be completely migrated from one inter-operating git forges to another

@bill-auger: So if we do federate issues and comments, can we pass along some meta data to facilitate issue hashing / patching of this sort?

@bill-auger

i think more could be done that merely notifying the issue tracker that some interesting has happened - in the pagure model issues are just git repos - that inherently makes it federated - new issues and issue comments then are just a git commits that can be handled in exactly the same way as a pull request against the code repo

This would actually also work for git-dit. For other dits, I'm not so sure...
Anyway, if we pursue such a solution, the "receiving" or "following" service must either perform a fetch, e.g. of a specified reference, or we need a stable way to reconstruct a commit with exactly the same hash. I think this is what @yookoala just noted. The former is obviously easier to do.

@neithernut: I don't think we should force the implementation to support certain notion of comment / issue management (unless there is substantial supports from the stackholders, which would be the ones who develop Git service software). I'd propose to allow for additional information in the protocol that make space for underlying implementation for additional security / redundancy.

@yookoala

I don't think we should force the implementations to support certain notion of comment / issue management

I agree. I just wanted to point out the implications of such a decision.

I'd propose to allow for additional information in the protocol that make space for underlying implementation for additional security / redundancy.

In this case, the question is what data should be provided by a service, either as part of a notification or when queried. This could be, for example:

A description of the issue
Arbitrary metadata (this easily gets tricky)
Messages/comments attached to an issue

as i said im my email i am becoming concerned already that the discussions are still continuing here at such a prolific pace and at such an early stage - its not even clear that everyone interested is in the know yet - now that the mailing list is formed and new people have joined, the main discussions should be moved there - people who are not on the mailing list yet can still read the discussions on the web - if the discussions happen in both venues things will get very confused and possibly segregated

at the very least, anyone joining now has a lot of catching up to do - and its only the 2nd day

@yookoala

we'd run into namespace collision / reservation issue. Say a repository named "foobar/hello" has a copy on server A and a copy on server B.

There's a well-defined precedent here, DNS. I think it's probably important for any federated system to not rely on one specific server for anything, right? Each user on the system can have a published public encryption key (or keys) that they manage themselves and only they have the private keys for. Then, each repository is associated with one or more users, and only responds to requests that are signed with one of the users' private keys. That request can be distributed to other nodes on the federation, and could even be stored as an artifact of the history.

@coderkevin
Well, with

The repositories don't "belong" to a server, they belong to a person or an organization.

you proposed that a repository is rooted not on a server but the "name" of a person or organization. This implies the collision/reservation issue because you now have to reserve names across  the federation.
As for DNS, a person or organization may not own a domain name. It's actually quite rare for the persons to own a domain name. So you end up having names and organizations "managed" under the domain name of a service. You could make use of things like OpenID but I suspect that's not what you had in mind.
I think having a repository rooted on a service with a given domain name is not that big of a deal, if "upstream" has to move for some reason, followers may need to have their repos point at the new upstream, but this is not a problem imo. It's rare and such "re-pointing" functionality would be provided by any reasonable implementation. Even if we don't specify a notification for moves, services could hack something using a HTML 301 status code.

Well, I wasn't exactly talking about using domains for organization names. But you're right that one would have to reserve such a name across the federation. I wonder if we could use what we've learned from the DNS system. Perhaps there can be a small constellation of servers which share a consensus of a name directory. Names of organizations and users, and the associations between them...Oh and maybe the public keys for the users as well.

"names" must be canonical and unique across the federation - that is not to say fred42 must be unique because every identity should be coupled to a home-server - so fred42's actual ID is<EMAIL_ADDRESS>-  the "name" fred42 only needs to be unique on freds-home-server.net

fred42 only needs to be unique on freds-home-server.net

What happens when freds-home-server.net goes down? Or if the domain expires? Wouldn't this still have a single point of failure? Who will be the authority if that one single point of failure ceases to exist?

if fred's home-server goes down then fred (and fred alone) has a minor problem - if fred has previously neglected to backup his data and credentials, the fred, has a bigger problem - yet the network lives on unfettered
i think you are assuming that fred's home-server is most likely to be operated by some person other than fred himself - which leads people to ludicrous suggestions like the one in #10 where it was suggested that the protocol should somehow try to prevent servers from shutting down; in order to protect users who are not in control of their own data on that server - the very promise of federation is to give users full control over their own data by running their own server in federation with the larger network of inter-operable nodes

I have mocked up some draft vocabulary based on the discussions in these issues, and I think the inclusion of "Mirrors" as a concept for the Repository actor can prevent some of this problem. However, you are still at the mercy of Fred actually putting up mirrors and announcing them.

"you" are never at freds mercy - fred decides when and where to publish fred's code and when to delete it - fred is not obligated to do anything; and no other person is necessarily interested in his actions - if "you" think fred's code is worth preserving more than fred does, then it is "you" who should clone and backup fred's code in case he unplugs his computer

i still confused why all this discussion is still happening on github - the mailing list was setup this morning - it would be most helpful to have all discussions in a single venue

because no one knows where the mailing list is and it's not publicly visible
On Thu, Jun 7, 2018, 8:16 PM bill auger<EMAIL_ADDRESS>wrote:

i still confused why all this discussion is still happening on github -
the mailing list was setup this morning - it would be most helpful to have
all discussions in a single venue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/git-federation/gitpub/issues/11#issuecomment-395605439,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAORV1E-RtxBuLqN364BgK65aJc_ezr9ks5t6cJSgaJpZM4Uc_hv
.

it was not setup properly this morning - everything is working properly now
the address is:
<EMAIL_ADDRESS>this is the link to the archives:
https://framalistes.org/sympa/arc/git-federation

One of the reasons we PSYCers (who did a federated chat system in the 90s, then decided to drop federation) was that there was no satisfactory way to ensure that an incoming TLS connection is legitimately speaking for a certain domain name. Your server is presented a certificate from the other side and has to autonomously figure out whether it is trustworthy — nobody has figured out a way to interactively engage some user to make an educated decision. Most servers in the XMPP federation do not check certificates, for example — so anyone who wants to tear down entire issue trackers can write a bot that fakes a legitimate contributor's user@host credentials and recursively deletes all data. You can probably come up with worse scenarios — I just mention the first that came to my head.
To solve the problem of X.509's untrustworthiness you can try to throw DNSSEC and DANE at it, which means that less people even have the competence to set up their own servers. Most devs won't run their own servers anyway, so they need to register with somebody else's server who then exercises a certain degree of power on them — In history, federation has always been a slippery slope towards centralization.
For a truly distributed authentication that has no authority-bearing servers you'll want to authorize people by the means of public key crypto, as has been suggested already in this thread. If you take this route, then you typically need custom software on the user's machine (git commit -S might be helpful). Or there may be a solution involving HTTP client certificates to log into as many servers as necessary.
From our perspective the next logical step is to organize the routing according to those public keys, removing the dependency on servers all together. Git was invented to be server-free and it should actually be possible to pursue that path.
Also I recommend not to repeat XMPP's mistake of using user@host notation, as it will first create user expectation that those addresses also work for email and then produce SPAM on all protocols using that notation. Better to use a custom URL syntax.

very good points @symlynX
i should clarify that the user@host notation is not a "mistake" precisely, it is standard URI syntax for when you want some resource to be accessible in a standard way by some generic client - HTTP, FTP, SIP, and countless others have used it for that purpose - with that said, it is true that in this case, this is strictly an ID and not playing the role of a URI

ActivityPub examples use https://host/user/  as id (Mastodon displays it as @user@host) — though the only requirement is that it must be a publicly dereferencable URI. FWIW, Matrix uses @user:host specifically to avoid confusion with emails.

but again, in this case, this is strictly an ID and not playing the role of a URI and never needs to be passed in a URL - it can be any globally unique string - even unicode

@symlynX: I think our federation need to support current git services. And most, if not all, of them uses identity locals to the instance server. That means there is no true distributed authentication in the eco-system.
I think our protocol, if possible, might allow true distributed authentication in long run. We might also solve issue for repositories migration with global identities. But even at that stage, I don't think it will be enforced.

I think we should use an approach like Mastodon for short hand reference. The user ID in the protocol would best be the HTTPS URL to the user page.

it would be most helpful to keep discussion on topic - the topic of this thred is "issue tracking"
there is a dedicated thread for discussions of "identity and authentication"
https://github.com/git-federation/gitpub/issues/7

Maybe worth looking into prior art: there is this very interesting protocol used by Hubzilla that was specifically designed for such purposes: https://project.hubzilla.org/help/en/developer/zot_protocol#What_is_Zot_

ActivityPub examples use https://host/user/ as id (Mastodon displays it as @user@host) — though the only requirement is that it must be a publicly dereferencable URI. FWIW, Matrix uses @user:host specifically to avoid confusion with emails.

I would strongly avoid writing anything into the protocol related to Mastodon custom way of using ActivityPub. There is nothing in ActivityPub related to "user@host" ID's. ActivityPub ID's are always URI's.
Server implementers are free to show their users a friendly name (like Mastodon does), but it should not be a part of the protocol.
(will post this to mailing list too, bill ;))

Another thing to consider with using IRI's is that you can have a canonical link that is sent over ActivityPub only, which is not necessarily human-friendly (ex: example.com/user/canonical/{GUID}). But as an application allow a convenient shorthand link for human interactions (ex: "Hey my profile is example.com/user/{my username}"). This permits applications to choose better systems for managing user identities.
A problem with any solution that bakes in username as a unique id is that it is unnecessarily restricting 2 out of 3 parts of identity. I don't recall where I read it, but if I remember right the 3 parts of identity were broken down something along these lines:

Logical - What determines an identity joined against other data (ex: a primary key in users table)
Behavioral - What behaviors is the identity permitted and how to authenticate said identity (ex: authn and authz)
Social - What changes can the identity make online to reflect the user's desired real-world identity (ex: name changes, account migration)

So it would be nice to use a solution that does not forbid the separation between the Logical and Social aspects of identity.

Yes, I also like to have  such separation here (as changing in Social aspect
had broken things with Logical aspect a lot of times before)
--
Regards
Gilhad"
So it would be nice to use a solution that does not forbid the separation
between the Logical and Social aspects of identity.
"

Hi, just my 2 cents: I'm surprised to see issue tracking here because it seems to me not tightly related to git or software development in general. I think an ActivityPub extension for issue tracking only would be better and keep "GitPub" for git related things like pull requests. If one wants to implement both federated pull request and issue tracking he could follow GitPub for the first and the general extension for issue tracking.
Pro: git based, other VCS based apps and other apps not related to software development would use the same ActivityPub extension for issue tracking.

@alxlg: Thanks for the opinion.
IMO, in a federated ecosystem, we are exploring how to support feature that needs by most federated instances (i.e. the software of those instances). Issue tracking is a part of most of them. So I think we bound to discuss it anyway. Whether to put it into the spec, or not, is another issue. In fact, many people did ask for such feature in previous discussion.
But even if this is specified in the result specification, since how and what to implement in the spec is always optional, a feature like "issue tracking" is not forced to the software that do not need it.

@yookoala maybe I should rephrase: issue tracking is not only about software development / version control systems so it should take into account more use cases. I think it would be better to have "IssuePub" for issue tracking and "SourcePub" for activities about coding like pull requests and forks.
P.S. I sent my previous reply to mailing list to but it seems it wasn't approved by moderators.

@yookoala I just hope issue tracking spec will be generic enough and not bound to version control system use case

alxlg -
most every aspect of the feature set has been discussed in detail on the mailing list if you are interested to read it - one of the longest discussions was about being as generally applicable as possible (the threads: "Is it really about git?" and "Generalization, of issues and in general,")

@bill-auger As I said I sent my reply to mailing list but it wasn't approved by moderators, so I can't join the discussion there

alxlg -
you can read everything though - the URL is in the README of this repo

@alxlg: I think it is nice to have a generic issue tracking abstraction so it is not bound to any VCS. The real question is how.
In the current discussion, there is no concret suggestion as to how issue tracking should be dealt with. The discussion is still about principles and scope.
If you have idea on how the protocol should look like, please give us your thought here. Thanks.

Maybe also worth looking into this:
https://github.com/sit-fyi/issue-tracking
(while not federated per-se it's decentralized nature should make federation sync issues much easier)


Use the padding only under iOS especially if it is only for iPhone 5.

Without these changes the 10px padding occurs on my Sony Xperia Z5 when starting the VR in Portrait mode and it won't go away. So just use it on iOS if it is only for iPhone 5

Just saw that on my iPhone 6 Plus the behaivour is the same as on the Sony Xperia Z5... also have the padding there... is there a possibility to diff between iPhone 5 and iPhone 6 so we can only use the padding on the iPhone 5?

We can differentiate, but this seems like an overly specific hack. Could you provide a screenshot of the problem you're seeing?

hmm... I would like to, but somehow now I can't manage to reproduce it...
don't know why it works now... but if it do it is fine :D so we can forget my last comment.

Please close then!
On Mon, Oct 10, 2016 at 1:54 AM cnspaha<EMAIL_ADDRESS>wrote:

hmm... I would like to, but somehow now I can't manage to reproduce it...
don't know why it works now... but if it do it is fine :D so we can forget
my last comment.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/borismus/webvr-polyfill/pull/155#issuecomment-252564595,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQ8gKkRns7BItDpCLZvPFbNAaC8WOSgks5qyf0tgaJpZM4KIibM
.

The issue still exists. I'm working with A-Frame in embedded mode and changing the orientation of the device will produce a 10px thick border on the right and bottom. I'm using an iPhone 7.

I'm still seeing this padding issue as well on lots of modern Android devices: Pixel, Pixel XL, 5X, 6P, etc. One key point is that this only happens when presenting to VR from portrait mode (otherwise the onResize_() function which adds the padding doesn't get called).  Here is screenshot of the issue on a nexus 5X:

I added a artificial red border to highlight the issue which is the padding added at the bottom and right sides. You can also notice in the screen shot that the back and settings buttons are abnormally large.


Cannot create LIST partition on data type other than INT

Hi @michaljuhas
I am now doing 'S04-P01-Practice'. However, I got error when I want to create a LIST partition. Here is my code and the error message. Could you please help?
CREATE TABLE `sample_staff`.`invoice_partitioned` AS SELECT * FROM `sample_staff`.`invoice`;
ALTER TABLE invoice_partitioned ADD COLUMN department_code VARCHAR(35);
ALTER TABLE `sample_staff`.`invoice_partitioned`  REMOVE PARTITIONING ;

UPDATE invoice_partitioned,
    department_employee_rel,
    department
SET
    invoice_partitioned.department_code = department.code
WHERE
    invoice_partitioned.employee_id = department_employee_rel.employee_id
        AND department_employee_rel.department_id = department.id
        AND invoice_partitioned.invoiced_date BETWEEN department_employee_rel.from_date AND department_employee_rel.to_date
;

ALTER TABLE invoice_partitioned
partition BY LIST(department_code) (
partition CS	values in ("CS"),
partition	DEV	values in ("DEV"),
partition	FIN	values in ("FIN"),
partition	HR	values in ("HR"),
partition	MKT	values in ("MKT"),
partition	PROD	values in ("PROD"),
partition	QA	values in ("QA"),
partition	RES	values in ("RES"),
partition	SAL	values in ("SAL")
)
;

Error message: Error Code: 1697. VALUES value for partition 'CS' must have type INT

I even add the partition for the null value, but it does not work.
ALTER TABLE invoice_partitioned
partition BY LIST(department_code) (
partition CS	values in ('CS'),
partition DEV	values in ('DEV'),
partition	FIN	values in ('FIN'),
partition	HR	values in ('HR'),
partition	MKT	values in ('MKT'),
partition	PROD	values in ('PROD'),
partition	QA	values in ('QA'),
partition	RES	values in ('RES'),
partition	SAL	values in ('SAL'),
PARTITION NUL values in (null)
)
;

I think it should work but unfortunately it has not worked. So instead, I add another INT column to make it work.
ALTER TABLE invoice_partitioned ADD COLUMN department_id INT;

UPDATE invoice_partitioned,
    department_employee_rel
SET
    invoice_partitioned.department_id = department_employee_rel.department_id
WHERE
    invoice_partitioned.employee_id = department_employee_rel.employee_id
        AND invoice_partitioned.invoiced_date BETWEEN department_employee_rel.from_date AND department_employee_rel.to_date
;

ALTER TABLE invoice_partitioned
partition BY LIST(department_id) (
partition	CS	values in (	1	),
partition	DEV	values in (	2	),
partition	FIN	values in (	3	),
partition	HR	values in (	4	),
partition	MKT	values in (	5	),
partition	PROD	values in (	6	),
partition	QA	values in (	7	),
partition	RES	values in (	8	),
partition	SAL	values in (	9	),
partition NUL values in (null)
)
;


added optional start parameter, enabling pagination

This pull requests adds an optional starting index for google requests. You can set the number of results by which you want your query to be offset. To use it, change syntax from:
google ('node.js best practices',  callback)

to:
google ('node.js best practices',  10, callback)

Is there any way to rerun the Travis build? I'm not sure that the failure was related to my changes.

Here are my local test results:

google()
✓ should return search results (1405ms)
when resultsPerPage is set
✓ should return search results (625ms)
when timeSpan is set
✓ each time-based query should return search results (463ms)
when nextText and lang are set
✓ should return next page search results (1694ms)

Paging is already supported. What's the use case for not wanting to start on the first page?

My use-case is an application running on multiple instances which needs to add a batch of results to a database independent of the state of other instances, and independent of the application lifecycle on a single instance.
Making the paging an optional parameter with a few lines of code made a lot more sense to me than having to build state management around the module. This change makes it easy to check a database for the index of the last page retrieved from Google, and run the next query from there.
As an aside, it is easier to use the module without abusing it if you do a deeper (multi-page) search over a longer period of time instead of paging on a loop.

As an aside, it is easier to use the module without abusing it if you do a deeper (multi-page) search over a longer period of time instead of paging on a loop.

This is an excellent point. Ok, I'll incorporate this... I think that I wanna refactor the module...

I'll accept the PR, but first, please add a test. Something as simple as searching for something with the new parameter and checking for results.

Great! Test added.

Thanks, published :)


Feature request: better memory management for PlayerUnitEvents

Hi, incredible library, thankyou. I'm leveraging PlayerUnitEvents extensively because my map has an extremely large number of units and a need for high optimization.
Usually, when I register a PlayerUnitEvent, I expect to unregister it as soon as the registering object is either disposed of or garbage collected. Currently I can't do this with PlayerUnitEvents.Unregister, because as far as I can tell that will also unregister any other registering object that registered against the same event and integer ID. I don't have a clear idea how this could be resolved.
Happy to clarify if need be.

Hm, I'm a bit confused here. I am aware that there are some issues with overlapping registrations for the same event, but I don't understand your issue?
Registrations are done either as a global trigger, or as a filter on some type id, typically unit type. There should never be a case of needing to unregister anything because of a single object (unit) being disposed of. Unregistering only makes sense if every instance of that unit type is gone from the map, though frankly I think you're better off just leaving them registered since it won't really make an impact on memory or performance to leave them there.
In fact, Lua's garbage collection works strangely in WC3, in that it does a huge sweep all at once for all players. It is not constantly cleaning memory, and if anything you'd rather avoid to trigger this sweep at all, since it'll typically cause a notable lag spike and just generally doesn't help performance in the long term. By constantly registering and unregistering events, you'd hit the memory threshold to cause a sweep earlier, which is probably not what you want.

Though not really what your issue was about, I've now improved the death handling for buffs in https://github.com/Orden4/WCSharp/commit/1d6345f9b7e3cc8a211ed9288b1a5fea4152f054

On reflection, I think your advice here is good and you're right that just leaving them registered is the better move. Thank you.


feat: [WIP] Implement Java binding

This pull request is still under development and addresses the interconnection between Java and Rust using JNI for both write and read paths. Here's a summary of the progress:
Write Path:

Code currently implements sending data from Java to Rust through JNI.
arrow_c in java and arrow ffi in rust are used for efficient data serialization and transfer.
Resource management ensures proper release on both sides, preventing memory leaks.

Read Path:
Development for the read path (data flow from Rust to Java) is ongoing within this PR.
The same approach with Arrow and JNI will be utilized for consistency and performance.
Next Steps:

Continuous development and testing on both write and read paths.
Open to feedback and suggestions on design and implementation for all aspects.

Highlights:

This PR establishes a single source for building a complete Java-Rust communication channel using JNI, which will have a better compatibility for integration with Java projects still running on java 8 such as Presto, Spark and hive/hadoop .
Arrow integration ensures optimized data handling and minimizes data copies.
Careful resource management prevents memory leaks and improves overall stability.

Hi @eddyxu,
I integrated a mvn plugin to build rust project in maven,  you can run mvn clean package  to generate the jar with a native library embedded.
Then you can find jar atlance/java/target/lance-0.1-SNAPSHOT.jar

The structure of the jar is simple
jar tf target/lance-0.1-SNAPSHOT.jar
META-INF/MANIFEST.MF
META-INF/
nativelib/
nativelib/darwin-aarch64/
com/
com/lancedb/
com/lancedb/lance/
META-INF/maven/
META-INF/maven/com.lancedb/
META-INF/maven/com.lancedb/lance/
nativelib/darwin-aarch64/liblance_jni.dylib
com/lancedb/lance/Dataset.class
META-INF/maven/com.lancedb/lance/pom.xml
META-INF/maven/com.lancedb/lance/pom.properties

I only added one target platform "darwin-aarch64" for macos on arm. (I will figure out how to add more target platform later)
It will also run the test in both Rust and Java project.
By the way, I also removed quite a few redundant code.

@beinan @LuQQiu thanks for working on this. Please let us know what else we can help to move this forward. We are excited to have a Java SDK!


Getting errors with favicons

NOTE: Before you start, the following should be completed.

Read tutorial to understand the usage and the correct effect of functional design.
Make sure no similar issue(including closed ones) exists.
Try to find the answer on Jekyll Forum and StackOverflow.

Description
Hello, I customized favicon following this tutorial. I successfully changed the favicon but the server kept spitting error messages. The error message appears when I try to access my blog with my iPhone 11 Pro with safari browser after tapping the share button.
Operations you have already tried
manually added copies of apple-touch-icon-precomposed.png, apple-touch-icon.png and favicon.ico into the root of the blog. Error messages are gone but it doesn't seem right. I have two copies of favicon.ico (and other files) inside /assets/img/favicons and / (root of the blog).
Just to make sure I am following the tutorial correctly, am I supposed to add generated favicons into /assets/img/favicons or /_site/assets/img/favicons?
Removed custom favicons and checked if the error doesn't appear with the default favicon. Error persists.
EDIT 2: After googling, I found an article saying that I need to insert the generated code into the <head> tag. Since I am using Chirpy Starter, I do not have access to _layout/default.html. I can manually create _layout/default.html but I wish there was a better way.
Following html code is generated by realfavicongenerator.net:
<link rel="apple-touch-icon" sizes="180x180" href="/assets/img/favicons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/assets/img/favicons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/assets/img/favicons/favicon-16x16.png">
<link rel="manifest" href="/assets/img/favicons/site.webmanifest">
<link rel="mask-icon" href="/assets/img/favicons/safari-pinned-tab.svg" color="#5bbad5">
<link rel="shortcut icon" href="/assets/img/favicons/favicon.ico">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="msapplication-config" content="/assets/img/favicons/browserconfig.xml">
<meta name="theme-color" content="#ffffff">

Logs/Screenshots
[2023-03-18 12:35:00] ERROR `/apple-touch-icon-precomposed.png' not found.
[2023-03-18 12:35:00] ERROR `/favicon.ico' not found.
[2023-03-18 12:35:00] ERROR `/apple-touch-icon.png' not found.

EDIT: trivial typo
EDIT 2:

Hi!
You should not user the html code that was generated by realfavicongenerator.net. Only use the images in the zip-file.
I put the two files favicon.ico and apple-touch-icon.png into the folder favicons (which should be inside the folder img, inside folder assets, in the root directory). After a fresh install I had to create the two folders img and favicons. In the _config.yml you can see the default path to the favicons are /asset/img/favicons/. No other actions were needed to get the favicons working. Still worked in production after deployment.
There is a known problem with Safar in iOS when it comes to the favicon and the share button. Here you can read about the problem with the hard cache that is preventing the favicon from updating. Unfortunately there is nothing we can do about it. It's up to Apple to fix the problem with the long caching of the favicon.

Thanks for the feedback @JorgenIvarsson!
LIke you said, there's nothing much I can do to get rid of the error messages. I just gave up on it. Thank you for clarifying the location to put favicon.ico. It helped me a lot.


Change to support new codes.ohio.gov website

This tool's code needs to be updated because Ohio recently changed the technology that the  codes.ohio.gov website is built upon.

Fixed with the latest version uploaded today.


Last minute renaming

Maybe rename core to sce and common to ps4 (or core)

Still unsure

Yea ... see https://github.com/ps4dev/ps4sdk/issues/12


initial friendlier sql post without images

Let's wait to merge this until we are ready to publish!
Happy to take any feedback!
We are also waiting to decide if the images in the google doc should be included in the post.

Thanks for those linting rules! All set now. The only thing I didn't agree with was no ! in a header, but ah well... I followed the rule!

Awesome feedback folks. Thank you for going over it in depth, and for the conceptual improvements as well!


SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED error in Python 11

In Python 11, accessing data on certain sites appears to not be possible with a basic requests call:
>>> import requests
>>> # Same issue with https://opendata.baltimorecity.gov/egis/rest/services/Hosted/911_Calls_For_Service_2017_csv/FeatureServer/
>>> url = "https://xmaps.indy.gov/arcgis/rest/services/OpenData/OpenData_NonSpatial/MapServer/5/"
>>> r = requests.get(url)
Traceback (most recent call last):
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\urllib3\connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\urllib3\connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\urllib3\connectionpool.py", line 1042, in _validate_conn
    conn.connect()
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\urllib3\connection.py", line 414, in connect
    self.sock = ssl_wrap_socket(
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\requests\api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\requests\api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\requests\sessions.py", line 587, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\requests\sessions.py", line 701, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\matth\.conda\envs\opd-py3.11\Lib\site-packages\requests\adapters.py", line 563, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='xmaps.indy.gov', port=443): Max retries exceeded with url: /arcgis/rest/services/OpenData/OpenData_NonSpatial/MapServer/5/ (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:992)')))

If using conda: how to install Python 3.11 with conda (not available through the main channel yet): https://stackoverflow.com/questions/74959226/how-to-pick-python-3-11-as-a-conda-environment-in-vs-code
I have seen this solution suggested: https://stackoverflow.com/a/71646353/9922439. The question I have is does this make the request in a comparable way to Python 3.10 or is it something different and perhaps we should be concerned that there is a security concern.
I have also seen the suggestion to downgrade the cryptography package: https://pyquestions.com/ssl-error-unsafe-legacy-renegotiation-disabled. Not sure if that is a workable solution if someone is using an environment where other installed packages use requests.

Ended up implementing OP_LEGACY_SERVER_CONNECT option in stackoverflow answer. Decided this was secure enough because Python 3.10 connects to these sites and it's documented by openssl:
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_options.html
SSL_OP_LEGACY_SERVER_CONNECT: Allow legacy insecure renegotiation between OpenSSL and unpatched servers only: this option is currently set by default. See the SECURE RENEGOTIATION section for more details.


v1.9: Cilium is broken due to a kernel complexity issue when using Kind and a recent kernel

Bug report
With recent kernels (it's the case with at least kernel 5.10), when using Kind, Cilium is broken on v1.9 due to a kernel complexity issue. The default options as suggested in the kind installation page instruct to disable host services (--set hostServices.enabled=false) as this is not supported with Kind.
As PR #14951, marked for backport to v1.9, removes this limitation,  the installation documentation for Kind should be updated to instruct to instead enable host services which allows to bypass the kernel complexity issue.

I think this is a duplicate of https://github.com/cilium/cilium/issues/14726, no?

I would like to take up this issue.

The fix for this complexity issue has been backported to v1.9 and will be released as part of v1.9.9.


fitBounds  do not works on a circle

c: Circle;

this.c = circle([ data.lat, data.lon ], { radius: data.radius , color: data.color });

const circleStart = {
  id: data.id,
  name: data.name,
  enabled: true,
  layer: this.c
};

this.fitBounds = this.c.getBounds();   <<<<  KO

The specific issue you're running into here is that this.c.getBounds() doesn't work until after the circle is added to the map. You'd have to register a listener on the layer add event and then call fitBounds in there. Something like this:
this.c.on('add', () => { this.fitBounds = this.c.getBounds(); });

You may run into a warning about changes after change detection because the callback gets invoked during the change detection that added the layer... so, a quick solution for that is to inject the ChangeDetectorRef and manually trigger change detection:
this.c.on('add', () => { this.fitBounds = this.c.getBounds(); });
this.changeDetector.detectChanges();

thanks @reblace your solution works!!


docs: kick-off 1.17.1-dev.

Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

dupe of https://github.com/envoyproxy/envoy/pull/14824 need fix some CI scripts altogether.

@lizan Thanks!


Dicom network protocol support

Is there any plan support dicom network ?

but this does not support transferring dicom file


Workspace edit integration test failing

  1 failing
  1) vscode API - workspace
       WorkspaceEdit fails when creating then writing to file if file is open in the editor and is not empty #146964:

      AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected

+ 'SOME TEXTHello Here And There'
- 'SOME TEXT'
            ^
      + expected - actual

      -SOME TEXTHello Here And There
      +SOME TEXT

      at Context.<anonymous> (extensions/vscode-api-tests/src/singlefolder-tests/workspace.test.ts:1031:10)

https://dev.azure.com/vscode/VSCode/_build/results?buildId=68646&view=logs&j=9833cdaa-2e92-5f8d-56a8-239fd18fd628&t=ff2af1d7-3e77-5c9b-1266-059963f765ca&l=394

Haven't seen this ever since. Closing


Failed to get service principle with app id

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad sp show
Errors:
400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 654, in execute
    raise ex
cli/core/commands/__init__.py, ln 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
...
python3.6/site-packages/msrestazure/azure_active_directory.py, ln 486, in get_msi_token
    result.raise_for_status()
python3.6/site-packages/requests/models.py, ln 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ad sp show --id {} --query {}

Expected Behavior
Environment Summary
Linux-4.15.0-1089-azure-x86_64-with-debian-stretch-sid
Python 3.6.10
Installer: DEB

azure-cli 2.8.0

Additional Context

add to S173

Duplicate of #11749


does not work with GIMP 2.10.38

does not work with GIMP 2.10.38,  doesn't show up in filter menu ...

It's definitely working with GIMP 2.10.38
The issue is probably one of two things:
1
The plug-in isn't installed correctly:

Open GIMP and go to: GIMP > Edit > Preferences > Folders > Plug-ins
Ensure the Plug-in is actually in a listed folder.
Ensure the Plug-in is correctly extracted to an appropriate folder.

If you downloaded the .zip release, the Plug-in must be extracted. GIMP Plug-ins require a certain structure and won't be recognized if that structure isn't met. The script (gimp_upscale.py) must be in a parent folder of the same name, like this:
plug-ins
|
└── gimp_upscale
    |
    └── gimp_upscale.py

2
GIMP isn't configured with Python support.

Try opening: Filters > Python-Fu > Console
If you can access that option then Python is working.
If you can't access that options, then you may need to reinstall GIMP and ensure Python-Fu is selected during setup.
If you're running the Linux version of GIMP, you may need to take additional steps so Python-Fu works.


[SPARK-38342][CORE] Clean up deprecated api usage of Ivy

What changes were proposed in this pull request?
This pr use Ivy.retrieve(ModuleRevisionId, RetrieveOptions) instead of  deprecated Ivy.retrieve(ModuleRevisionId, String, RetrieveOptions) to  clean up deprecation compilation warning.
The refactor way refer to the Implementation of  RetrieveEngine#retrieve method as follows:
    @Deprecated
    public int retrieve(ModuleRevisionId mrid, String destFilePattern, RetrieveOptions options)
            throws IOException {
        RetrieveOptions retrieveOptions = new RetrieveOptions(options);
        retrieveOptions.setDestArtifactPattern(destFilePattern);

        RetrieveReport result = retrieve(mrid, retrieveOptions);
        return result.getNbrArtifactsCopied();
    }

Why are the changes needed?
Clean up deprecated api usage.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA

+CC @xkrogen

Merged to master


Use ES5 functions instead of arrow functions

Fixes #1

Thanks for the commit, but what is it trying to accomplish exactly? I mean what is the problem with using arrow functions? it is supported since node version 0.11 which was released in early 2013 I think.
If you're trying to use it in an earlier version, we can accept this and also we would need to change the Array#find method, since it is also a part of `ES6.

But I also don't see any harm in it.
Thanks for the commit :+1:

It was to use in a browser with browserify!

Ah! okay... I also updated the NPM. Let me know if you run into any issues :)


Poor Documentation for Scenarios

Hi,
First of all, what a great project, especially for the automation of Azure Stack HCI. As a retired PowerShell MVP, I love the work.
I would like to bring attention to some of the documentation issues. I am sure that when you are used to the project, you don't notice UX issues. However, it's very difficult to understand how to run Scenarios. The entire documentation is geared towards the Hydration phase and preparation, but then there is no / or minimal information on how to run Scenarios. There are LabConfig files, but they seem to represent config differences rather than the main LabConfig files and that is not clear. There is no indication that scenarios should be run on the DC server. So, the warming-up part is very easy to understand, but the Scenario part remains a mystery. I think the main reason might be that the scenarios were made by other people/teams.
I was able to deploy Azure Stack HCI after reading the documentation here, as the docs were not helpful:
https://learn.microsoft.com/en-us/azure-stack/hci/deploy/tutorial-private-forest
I think you should add more explanation for beginners who want to try this lab.
As I said, now that I understand the logic of the project, installing/reinstalling scenarios is very easy for me. It saves a lot of time. Thanks again.
Yusuf

Hi @yusufozturk I can certainly see your point and appreciate your feedback. not speaking on behalf of Jaromir here. There is a kind of gap but if you understand how to use the scenario files things get clear.
Jaromir and me recently had a talk about how community calls could help to make this amazing project even better and more accessible while also trying to get some work off for Jaromir. My idea what to restructure some parts and avoid duplicates, because code changes happen and over the course there are different iterations and versions of steps that do no longer align with the lastest code, plus it is not feasible for Jaromir to update them one by one.
If you haven't yet feel free to join the Azure Slack HCI community to broaden the ideas about this.

I did create introduction hands on labs here: https://github.com/DellGEOS/AzureStackHOLs. Does it help?


[python3] Install the debug version of the files *_d.pyd

Fixes #28130. Install the debug version files *_d.pyd for python3.
It should be noted that the tools/ directory of vcpkg is intended to provide some programs for other ports to use during the build process, rather than debug binaries.
But because Python has some difficulty separating tools from extension modules, FindPython fails when Python components are slightly mismatched. So here port python3 as one of the rare cases, add the debug version of the _d.pyd file for it.
This PR will be put on hold for a while for everyone to review.

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks!


Passing additional API-Key to window.WebChat.renderWebChat

We have a working Bot that uses the DirectLine AppService Extensions v3. So the following pseudo-code works perfectly fine:
const secret = <Directline Secret>;
const userId = "dl_test";

const { token } = fetch("https://<our-domain>.azurewebsites.net/.bot/v3/directline/tokens/generate",
        { headers: {
                    authorization: "Bearer ${secret}"
                    },
                    method: "POST",
                    body: JSON.stringify({
                        user: {
                            id: userId
                        }
                    })
        }
        );

window.WebChat.renderWebChat(
    {
    directLine: await window.WebChat.createDirectLineAppServiceExtension({
        domain: 'https://<our-domain>.azurewebsites.net/.bot/v3/directline',
        token
    }),
    userID: userId,
    username: "Test User"
    },
    document.getElementById('webchat')
);

Note that in reality we are not exposing our secret in the frontend, this is just for illustration.
Now we want to access the chatbot through our API-Gateway. For this we need to pass an additional header in the requests. For the token generation this works just fine. But how do we pass an additional header in the window.WebChat.renderWebChat component? The end result should be something like this:
const secret = <Directline Secret>;
const userId = "dl_test";

const { token } = fetch("https://<our-gateway-domain>/tokens/generate",
        { headers: {
                    authorization: "Bearer ${secret}",
                    apikey: <Our API Key>   # <---- this works
                    },
                    method: "POST",
                    body: JSON.stringify({
                        user: {
                            id: userId
                        }
                    })
        }
        );

window.WebChat.renderWebChat(
    {
    directLine: await window.WebChat.createDirectLineAppServiceExtension({
        domain: 'https://<our-gateway-domain>',
        token
    }),
    userID: userId,
    username: "Test User",
    apikey: <Our API Key> # <---- this does not work
    },
    document.getElementById('webchat')
);

Do we have to re-write one or more of the components? I looked in the samples but did not see anything similar.

You will need to fork out the DirectLineJS repo which includes the DL ASE chat adapter. Then, modify it to add a new HTTP header, and pass the new chat adapter back to Web Chat via the directLine prop.

Ah, thanks! We will take a look and direct any additional questions to the DirectLine Repo.

Hello,
will it be possible to make this request a feature? this is a typical use case in the Azure architecture where we expose services through APIM or an API gateway that requires an additional secret to be passed in the request header.


fixing workspace dependencies; config values

Fixes some configuration values for the default endpoints the helium_gateway should call to in order to receive the remote entropy data as well as the default (mainnet) endpoint for submitting beacon reports to.
Also fixes compiler warnings for dependencies related to the workspace dependency (inheritance) refactor causing conflicts with the versions of dependencies in use by the primary (/src) code directory for the project. Since the main /src is not a workspace member, this was causing issues when the compiler was trying to determine the main project's dependency versions from the workspace.dependencies section of the Cargo.toml. Maybe worth refactoring the main /src directory to be a helium_gateway or similar workspace member and then reverting this change but to duplicating the dependency entries in the root Cargo.toml file her to quickly unblock.

Not sure what to make of this now; I have both successfully and not successfully built the project with the main dependencies inherited from the workspace.dependencies key.


Option to disable the Blips

Suggested by dtrail on 5mods:

Nice one! Thx.
But isn't there any option to disable the blips?

Added in ae88d1f3b42162f8f0f3bc01cd9488502f632423


Expose HTTP Writer As Available Writer

Please expose a basic HTTP writer. It should be configurable for host, port, method and optionally for security. A templating option should also be provided. As a start a basic JSON, or CSV format can be provided with package before supporting templating.
It'll be very useful for many currently non-supporting tools, e.g. SumoLogic. Also custom app can easily be built to consume metrics.

There is already an HttpOutputWriter. It is not directly configureable, but it can be reused to write a simple Java class for whatever format you need. See for example LibratoWriter2. Yes, this requires writing code and not just configuration (but I tend to think that configuration is just code that you cannot easily unit test).
If you are interested in providing a more flexible approach, feel free to submit a pull request!

@gehel has  plan to implement this?

No, I have no plan on implementing this. I usually don't write new OutputWriters for which I don't have a use case personally, as I would probably get the constraints wrong (and I don't have all that much free time). That being said, I'm happy to accept pull requests!


docs: Improve Trusted Publishers security section

It seems the compromise that the example refers to is token compromise: make that explicit.

cc @woodruffw who wrote most of it

Indeed! Thank you for clarifying that, LGTM!


wip: Continuing #7212

Motivation

Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OV91Xaad85x7AG
→ https://go/builds/bui_OV92m9Cu7am3Ze
→ https://go/builds/bui_OV92R8RLMDZU1F

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OVROax8aWrSto1
→ https://go/builds/bui_OVROt6gqV8Icd4
→ https://go/builds/bui_OVRP6fKAC2KZzS

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OVmT67QidBJY7N
→ https://go/builds/bui_OVmTQiJAlxAGCE
→ https://go/builds/bui_OVmTLtTkHu0BPI

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OW7zFDrRo32afK
→ https://go/builds/bui_OW7z6ub4DzL6Tc
→ https://go/builds/bui_OW7zFG2q6Ch1Ia

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OXdgn8qvJBUfmd
→ https://go/builds/bui_OXdgxhl658CrhY
→ https://go/builds/bui_OXdgF8KCH7gWbV

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OY8AAtGB71kmNU
→ https://go/builds/bui_OY8ArxE4AGg0ZH
→ https://go/builds/bui_OY8ApSumPgr9Vl

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OYAcaD1sFlRhJ7
→ https://go/builds/bui_OYAct2iKLW539v
→ https://go/builds/bui_OYAch83QipXub0

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OYV7nIGbAj7Mwv
→ https://go/builds/bui_OYV71ZbDddp4sd
→ https://go/builds/bui_OYV70tM6OzJQOg

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OYVCgXFwZCCigG
→ https://go/builds/bui_OYVCamH7szMxVx
→ https://go/builds/bui_OYVCZpDHmIDUL7

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OYWBBePffgScGO
→ https://go/builds/bui_OYWBFlDb1M8qA2
→ https://go/builds/bui_OYWB0NnVviU72R

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_OYWozYs2YVLwSp
→ https://go/builds/bui_OYWoxo9pvNM58Z
→ https://go/builds/bui_OYWo6njMh3shkB


mkcloud: move PV+VG setup into setuphost

this is only needed once per host and not for every mkcloud run

:+1:


Update webpack.config.js

i was just starting using react throughout your guide but I got couple of small issues which I resolved in the pull request

Closing out old PR


MGDOBR-222: fix manager start with disabled rhoas (pt.2)

MGDOBR-222
Please make sure that your PR meets the following requirements:

[x] Your code is properly formatted according to this configuration
[x] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[x] All new functionality is tested
[x] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

Description
This is the cleaner and final solution to the bug.
Major changes

RhoasClient and dependent beans are now produced using Producer methods, that take into account the value of the feature flag.
Properties are read programmatically by the Producer methods only when the feature flag is enabled and passed to the beans via constructor, instead of using @ConfigProperty. This permits empty properties without errors if the feature flag is disabled.
Added tests for all the possible scenarios: "feature flag disabled", "feature flag enabled", "feature flag enabled with missing properties" and "default feature flag value (no explicit property set)" with related test profiles that allow to spot unwanted configuration errors.

@robpblake @r00ta @danielezonca @lucamolteni just to be clear: I introduced this "feature flag" to enable RHOAS via opt-in in #196 and I explained why in this comment.
We later realized it wasn't working as expected, because even if the flag was false, the absence of some RHOAS properties was crashing the manager (the exact behavior I was trying to avoid with the introduction of the flag).
The purpose of this PR is to fix the problem with a cleaner design and no need for setting dummy property values (like the quick fix in #213). Imho the effort with test profiles will be worth also in the future for other scenarios where we need to test different configurations.
In any case, this flag is temporary. It will be removed when the RHOAS integration will become mandatory (now it is not because the created topic is ignored) and we figure out how to test locally. Nothing more than this.

@robpblake @r00ta @danielezonca @lucamolteni just to be clear: I introduced this "feature flag" to enable RHOAS via opt-in in #196 and I explained why in this comment.
We later realized it wasn't working as expected, because even if the flag was false, the absence of some RHOAS properties was crashing the manager (the exact behavior I was trying to avoid with the introduction of the flag).
The purpose of this PR is to fix the problem with a cleaner design and no need for setting dummy property values (like the quick fix in #213). Imho the effort with test profiles will be worth also in the future for other scenarios where we need to test different configurations.
In any case, this flag is temporary. It will be removed when the RHOAS integration will become mandatory (now it is not because the created topic is ignored) and we figure out how to test locally. Nothing more than this.

@kostola OK, thanks for the explanation.
Can I ask you to make sure that the JIRA task we have to remove the feature flag has a complete list of everything here that needs to be cleaned up. Just in-case you're not the person that works on that task.
There are a couple of other comments on the PR that I think would help to clarify next steps on this work.
cheers,
Rob

JIRA task we have to remove the feature flag

The cleanup task is MGDOBR-225


Where can I find the examples for HoG

Nvidia TX2:
Ubuntu:

Problem description:
Hello there,
#129 & #128 have issused the HoG examples.
Anybody can provide it？

Hi @hejinIzhanghao
Currently we have no HOG examples in ACL.
I'd suggest you take a look at the fixtures in the validation tests.
https://github.com/ARM-software/ComputeLibrary/blob/master/tests/validation/fixtures/HOGDescriptorFixture.h
https://github.com/ARM-software/ComputeLibrary/blob/master/tests/validation/fixtures/HOGDetectorFixture.h
https://github.com/ARM-software/ComputeLibrary/blob/master/tests/validation/fixtures/HOGMultiDetectionFixture.h
This might help you to gain a better understanding on how to use these functions and configure them properly.
Hope this helps.


[Enhancement] Add Edit Connection screen

Problem: Currently there is no option to change the connection after creating it. requiring you to delete it and recreate it.
Suggestion: add the ability to edit the connection before or after connecting to the cluster.
While connected, it might be in read-only mode. if not connected you will be able to change/edit it.

duplicated issue


Designing Data-Intensive Applications

asgfasdf

notes

I've reached page 2.

I've reached page 10.


[Display news: Gallery view] Gallery view of News page has 1 column in 576px screen resolution, instead of 2 columns

Environment: macOS High Sierra 10.13, Google Chrome 81.0.4044.129 (64-bit)
Reproducable: always
Build found: commit 07bfeb2
Preconditions:

https://ita-social-projects.github.io/GreenCityClient/#/news is opened.
Eco news page is opened, Gallery view is selected.

Steps to reproduce:

Change screen resolution to 576px.

Actual result:
1 column is displayed with 576px screen resolution.
Expected result:
2 columns are displayed with 576px screen resolution.
User story: #459

https://github.com/ita-social-projects/GreenCity/issues/999
Only list view is present.


Editing a Sign Results Removes All Text Previously on the Sign

If you shift right click to edit a sign it removes the text on the sign meaning you need to rewrite everything on the sign.
This is on a 1.16.1 server with the mod installed on the server.

Thanks for the bug report! It seems like some behavior has changed in the client that affects this. It might require a client-side mod to fix.
I'm still looking into it!

Issue is fixed with the latest release (0.6.1). However, you need to install the mod on both the client and server to fix this issue.


Issue with k8s.io/docs/admin/high-availability/

This is a...

[ ] Feature Request
[ ] Bug Report

Problem:
Followed the steps from https://kubernetes.io/docs/admin/high-availability/
Was able to see 2 Container etcd-server came up
While running cluster health command from Master Node-1/2
kubectl exec etcd-server-kuber-poc-app1 etcdctl cluster-health
member 8e9e05c52164694d is healthy: got healthy result from http://<IP_ADDRESS>:2379
cluster is healthy
But From Master Node 1/2  see this error
kubectl exec etcd-server-kuber-poc-app2 etcdctl cluster-health
Error:  client: etcd cluster is unavailable or misconfigured
error #0: client: endpoint http://<IP_ADDRESS>:4001 exceeded header timeout
error #1: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused
cluster may be unhealthy: failed to list members
Please advise on this error
Proposed Solution:
Page to Update:
http://kubernetes.io/...

kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2", GitCommit:"bdaeafa71f6c7c04636251031f93464384d54963", GitTreeState:"clean", BuildDate:"2017-10-24T19:38:10Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"f38e43b221d08850172a9a4ea785a86a3ffa3b3a", GitTreeState:"clean", BuildDate:"2017-10-11T23:16:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Docker Version 17.10.0-ce
Kubernates Version v1.8.1
CentOS Version CentOS Linux release 7.4.1708 (Core)

@kumarganesh2814 :wave: This issue sounds more like a request for support and less like an issue specifically for docs. You can bring your question to the #kubernetes-users channel in Kubernetes slack. You can also search resources like Stack Overflow for answers to similar questions.
If after seeking support you discover an issue with documentation, please feel free to reopen this issue.

2017-11-14 03:14:56.774499 I | discovery: cluster status check: error connecting to https://discovery.etcd.io, retrying in 18h12m16s

I see this error from logs of etcd pods any advise for this error
I put this into slack but no reply also dont see concreate answer to this issue anywhere
Best Regards
Ganesh

@kumarganesh2814 It looks like your second etcd instance failed to start or respond. You may want to try etcd documentation or fourm.

@tengqm
Thanks Man. For Pointer
I rebooted my VM and now I see state as below
NAMESPACE       NAME                                        READY     STATUS             RESTARTS   AGE
default         default-http-backend-66b447d9cf-h2rmp       1/1       Running            1          1d
default         etcd-server-kuber-poc-app1                  1/1       Running            1          1d
default         etcd-server-kuber-poc-app2                  0/1       CrashLoopBackOff   45         1d
default         ro-dashboard-59c9c54bd9-v9gwr               0/1       CrashLoopBackOff   42         12d
ingress-nginx   default-http-backend-66b447d9cf-s7zqp       1/1       Running            1          1d
ingress-nginx   nginx-ingress-controller-59fbff6875-jw686   0/1       CrashLoopBackOff   41         5d
kube-system     etcd-kuber-poc-app1                         1/1       Running            4          12d
kube-system     kube-apiserver-kuber-poc-app1               1/1       Running            3          12d
kube-system     kube-controller-manager-kuber-poc-app1      1/1       Running            2          12d
kube-system     kube-dns-545bc4bfd4-mm5zg                   1/3       CrashLoopBackOff   103        15d
kube-system     kube-flannel-ds-26shx                       1/1       Running            1          1d
kube-system     kube-flannel-ds-qn84v                       1/1       Running            1          15d
kube-system     kube-flannel-ds-zlrq7                       1/1       Running            4          15d
kube-system     kube-proxy-mwcdp                            1/1       Running            1          1d
kube-system     kube-proxy-w9mwl                            1/1       Running            1          15d
kube-system     kube-proxy-z8l8j                            1/1       Running            3          15d
kube-system     kube-scheduler-kuber-poc-app1               1/1       Running            3          12d
tomcat          default-http-backend-66b447d9cf-g8dk6       1/1       Running            1          1d
tomcat          tomcat-b7b984958-gqfxw                      1/1       Running            1          6h
tomcat          tomcat-b7b984958-gwpfq                      1/1       Running            1          6h

Error for kube-dns
failed to "StartContainer" for "dnsmasq" with CrashLoopBackOff

All Issues are resolved now I am running with 2 etcd-server but I see error like
2017-11-14 14:43:15.428194 I | discovery: cluster status check: error connecting to https://discovery.etcd.io, retrying in 2m8s


Raise useful error if no DatabaseCleaner strategies are loaded

Summary
Raise useful error if no DatabaseCleaner strategies are loaded
Details
When #before_js is called on a Strategy, bail out if DatabaseCleaner.cleaners is empty.
Motivation and Context
This fixes #491.
How Has This Been Tested?
I added a spec and made it pass.
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

I can re-review this by monday/tuesday. If you think it's still relevant (Just been off for a while).


Update mongodb-compass-beta to 1.8.0-beta.1

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution.


Replace containerd cri with just containerd

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Functionality in containerd/cri is being pulled into containerd. CI workflow should now use containerd directly.
Which issue(s) this PR fixes:
Partial # 613
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

/assign @yujuhong

Looks like a flake…, let's try a retest.

Making it a draft till I iron out some issues.

see: https://github.com/containerd/containerd/pull/4380
containerd is on by default now in github actions so either have to stop the service containerd or run two containerd's at the same time..

containerd is on by default now in github actions so either have to stop the service containerd or run two containerd's at the same time..

Thanks @mikebrow for the heads up. I ran into this issue and updated the changes to fix the build.

@saschagrunert Thanks for the review. It is still a WIP as have to resolve some more issues with the Windows build. Will let you know when it is good to go.

Good to review again now.

Thanks for the reviews @saschagrunert @mikebrow

/approve


Fixes GA on admin/prod

What's this PR do?
tell us, what have you changed?
How should this be reviewed?
tell us, how can we review, to test that this works
Any background context you want to provide?
what else?
Relevant tickets
Fixes #
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love.

Okie dokie.


How to have more than one pager on the custom page

Background: I have customize Content page by introducing a  custom module.
Right now I have an obstacle to have tow pagers on the page at the header and at the footer of my content page. Strangely, Orchard allows only one pager on the page. Adding two   @Display(Model.Pager) does not help.
Code:
@Display(Model.Pager)
 <fieldset class="contentItems bulk-items">
@Display(Model.ContentItems)
</fieldset>
@Display(Model.Pager)

Thanks for the help in advance.

We do it on the Projection Widget. You can optionally pass some prefix on the pager shape so the links don't collide. And on the server you can get each page values independently.
Can you check what we did there?

I have limited experience with Orchard. Could you elaborate your answer a little bit ?

I have found this

            @Html.SelectOption((int)Model.Pager.PageSize, 0, T("All").ToString())
            @foreach(int size in pageSizes.OrderBy(p => p)) {
                @Html.SelectOption((int)Model.Pager.PageSize, size, size.ToString())
            }

But it is just allow to select size but I need functional footer and header pager.

DId this and it works:
var pagerShape1 = Shape.Pager(pager).TotalItemCount(maxPagedCount > 0 ? maxPagedCount : query.Count());
            var pagerShape2 = Shape.Pager(pager).TotalItemCount(maxPagedCount > 0 ? maxPagedCount : query.Count());
            var pageOfContentItems = query.Slice(pager.GetStartIndex(), pager.PageSize).ToList();

			var list = Shape.List();
			list.AddRange(pageOfContentItems.Select(ci => _contentManager.BuildDisplay(ci, "SummaryAdmin")));

			var viewModel = Shape.ViewModel()
				.ContentItems(list)
				.Pager1(pagerShape1)
                .Pager2(pagerShape2)
                .Options(model.Options)
				.TypeDisplayName(model.TypeDisplayName ?? "");

    @Display(Model.Pager1)
    <fieldset class="contentItems bulk-items">
    @Display(Model.ContentItems)
    </fieldset>
    @Display(Model.Pager2)


Fix to fetch the correct prev minor release for e2e tests

Issue #, if available:
When workload cluster creation with previous eksa-version e2e test is run against release branch, the test incorrectly fetches 2 minor versions below the current release branch. For ex., when run against release-0.17 it fetches 15.x eks-a version while the correct previous version should be 16.x.This change fixes the logic to fetch the right latest minor version when run against both main and release branches.
Description of changes:
Testing (if applicable):
Ran the e2e test locally against both main and release branch.
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/cherrypick release-0.17


.NET is not a language

.NET is listed as a language, it should be listed as a platform (the same way JVM is listed as a platform and Java or Scala  as languages)

unsubscribe
On Tue, Jun 19, 2018 at 6:21 PM totano<EMAIL_ADDRESS>wrote:

.NET is listed as a language, it should be listed as a platform (the same
way JVM is listed as a platform and Java or Scala as languages)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/awesome/issues/1337, or mute the thread
https://github.com/notifications/unsubscribe-auth/ALidQcMUWX-jyeTtn2bMNMyDxszjBl54ks5t-PPbgaJpZM4UtcSs
.

@app-lie : please see https://stackoverflow.com/questions/11043374/how-to-unwatch-multiple-repos-easily-on-github .


Question normalize operation

The operation https://github.com/YuanGongND/ast/blob/102f0477099f83e04f6f2b30a498464b78bbaf46/src/dataloader.py#L191 for normalizing should be divided by the standard deviation, not the variance?

Hi there,
It is *2, not **2. We just normalized the input with smaller std.
If you don't use our AudioSet pretrained model, it is fine to use 0 mean and 1 std (i.e., fbank = (fbank - self.norm_mean) / (self.norm_std)). Otherwise please keep the normalization consistent with us.
-Yuan

Hi there,
It is *2, not **2. We just normalized the input with smaller std.
If you don't use our AudioSet pretrained model, it is fine to use 0 mean and 1 std (i.e., fbank = (fbank - self.norm_mean) / (self.norm_std)). Otherwise please keep the normalization consistent with us.
-Yuan
Thank you!


ui [nfc]: Comment with TODO(#95) where we need dark-theme colors

This PR marks several places where we don't yet have enough direction to make a v1 of dark-theme support. In these places, I was unable to find an appropriate dark-theme color by looking at the web app and the Figma (as it is now).
Once we fill these in, it hopefully won't be too long until we have that v1 of dark theme. 🙂
Then some time after that, we'll hopefully have an updated Figma with a dark-theme variant of all the UI pieces. We'll examine that closely and fix places that aren't following it, including places that were wrong because we were following web. (As Vlad says on CZO, "Colors in web might be different from mobile.")

Thanks for the review! Revision pushed.
In this commit:
subscription_list [nfc]: Factor out helper for dividing line

I made the helper a static field on the class, instead of a variable in the build method.

Thanks! Looks good — merging.


Support check-in policies

There is no opportunity to create a check-in policy.
I have created a check-in policy via Visual Studio, but it is ignored in Rider. Check-in finishes successfully without any complaint.

Hi @julia-vaseva,
Check-in policies are something we have scheduled to work on soon. I can keep you updated on the progress here.
Thanks,
-Leah


feat: real image dataset support

Note: This is a draft PR for discussion
This PR adds support for real image datasets in the stress test.
I just added a method dataset_images(dataset_path: str, num_docs: int = 100) in helper.py . This method reads a given directory and yields all found images (gif/png/jpg). I am using the state variable to store the scandir iterator so that progress is kept between calls.
Questions:

I am not closing the ScandirIterator as it is hard to say when we are done processing the dataset? I guess it should be okay here, but its not really clean.
Maybe we should unify the dataset and random document generator functions? I mean that both have the same method with an optional dataset path. If the path is empty we generate random documents, if its not empty we try to process the dataset.

Missing:

Documentation in readme
We need the same for text datasets

Actually for the text based datasets the formats will change all the time, so we probably cant have a unified method to access the datasets (second question above), but we need specific methods for specific datasets

I am not closing the ScandirIterator as it is hard to say when we are done processing the dataset? I guess it should be okay here, but its not really clean.

Should be okay for now.

The PR looks nice! Let's test it today on end-to-end remote with terraform


deselecNode doesn't take suppressEvents parameter

According to the docs the api function deselectNode is supposed to take a second parameter, suppressEvents, it does not. The other select/deselect api functions have this parameter, only deselectNode that doesn't.

saw that it was already a pull request for this one, #552

:+1:
Hi, Yes, suppress events doesn't work at the moment. Fix would be great :)
Thanks for the awesome grid :)

suppressEvents is no longer supported, stop listening for the event if you no longer want it


Support IE8 TextNode

Supports text in IE8, fixes https://github.com/google/incremental-dom/issues/69#issuecomment-133910391.
The old code tried setting node.__incrementalDOMData = new NodeData(), which will throw for TextNodes. The new code will detect the legacy environment, and never set. Unfortunately, it means that we can't cache the TextData object (so we'll recreate it every patch).

Closing with https://github.com/google/incremental-dom/issues/69#issuecomment-139355384.


WIP: kick off production users list with MayaData and Weaveworks

Hi @dholbach, we at Apester use scope in production https://apester.com

Let's land this for now and then do consecutive PRs for new users of Scope.


Optimize  Deck

just an idea but instead of just the  maginify glasss how about a word too. It took me like 10 mins to figure out how to optimize the deck but besides that it works great... Thanks Man  See Pic

Added in latest version.


feat : Render adaptive card behind feature toggle

Description of changes made

Feature toggle for adaptive cards
Rendering adaptive card
Unit test case coverage

Associated issue number/tracking link
SPARK-94093
SPARK-97152
Reviewers
@adamweeks

Thank you so much for adding this feature. It looks really great.
With this being such a large PR touching so much of the code base, we'd prefer the commits be rebased and broken down into sections of work for easier review.
My starting suggestion would be commits like:

feat(package): add adaptivecards package
feat(r-c-adaptive-card): add adaptive card component
feat(r-c-activity-iteam): add support for adaptive card posts
feat(r-c-utils): add adaptive card utilities
feat(widget-message): load adaptive card features

When doing commits this way, it gives a better picture of the story of the feature and makes it easier for the team to review commit by commit.
Really impressive work on the feature though, it touches a lot of areas in the code and follows all of the existing coding style.

Finished another round. Please rebase on master instead of adding a merge commit.
The commit of "feat(upstream):Merge Upstream Changes" will generate a "merge" feature in the CHANGELOG.

Finished another round. Please rebase on master instead of adding a merge commit.
The commit of "feat(upstream):Merge Upstream Changes" will generate a "merge" feature in the CHANGELOG.

Rebased the master


:recycle: feat(beta): Use package.json as solc source of truth

Description
Improve evmts example by using package.json as source of truth for solc
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #238

PR #239

PR #240

PR #241   👈

This comment was auto-generated by Graphite.