Add support for CORS

For the meme creator on .tech, I was linking to images hosted on spee.ch. However, security issues prevented publishing. From MDN:

As soon as you draw into a canvas any data that was loaded from another origin without CORS approval, the canvas becomes tainted. A tainted canvas is one which is no longer considered secure, and any attempts to retrieve image data back from the canvas will cause an exception to be thrown.

CORS doesn't allow multiple allowed origins, so the options are:

Send Access-Control-Allow-Origin: * and accept security downsides
Check if referrer is from [lbry.tech, lbry.io, lbry.fund, ???] and return Access-Control-Allow-Origin: <allowed_domain>.

@NetOperatorWibby can you confirm this is working as intended for you now?

@kauffj Just remembered this. It is not working as intended.
SecurityError: The operation is insecure.

This is only with linking images from spee.ch to the meme creator on the Playground. The spee.ch images linked on the community page on .tech work. Publishing with images not served from .tech itself creates the above error.

@NetOperatorWibby can you describe the steps to test this?
Alternately, can you verify that it's a problem for all browsers or specific browsers?


[WHISPER] '.txt' or other simple files don't show up on 'files' list of the chat

Fix in 1.8 if fix is easy, move to 1.9 if fix takes a lot more work.

Seems to work on my side, got some more details on how to reproduce?


[Docs Rewrite] Meta-Issue: Introduction section

This is a tracking issue to cover all work related to rewriting the "Introduction" section.
Tasks

[ ] Move "Ecosystem" to "Real World Usage" section
[x] Add "Quick Start" page that shows fast app setup with RSK
[ ] Move "Motivation", "Three Principles", and "Prior Art" to "Thinking in Redux" section (do we leave any of this content up front?)
[ ] Add some kind of a "comparison with other tools / use cases" page

I just have a couple quick questions regarding the action items for this:

Move "Ecosystem" to "Real World Usage" section

This would make the "Introduction" section pretty long, which might be more cumbersome for new users. The "Ecosystem" section has a lot of information that might not all be relevant for new users.

Add "Quick Start" page that shows fast app setup with RSK

Would we still want the "basic example" section? or would the "Quick Start" section replace that?

Move "Motivation", "Three Principles", and "Prior Art" to "Thinking in Redux" section

Would this new section go under the "Introduction" section? or would it be its own section altogether?

@bpas247 : not quite sure what you mean by that.  The point is to move "Ecosystem" out of the "Introduction" category (where it already is) and into a brand-new "Real World Usage" category (which currently does not exist).
I'm not sure whether it's worth keeping that tiny example directly in the "Getting Started" page.  I do think there's a different intent between that example and what I picture for a "Quick Start".  The "Basic Example" is supposed to show "here's the raw Redux API in its smallest form".  The "Quick Start" page would be "copy and paste this code that uses Redux Toolkit as the fastest way to get something meaningful working, and you can learn the details of how it actually works later".
"Thinking in Redux" would be another brand-new top-level category, completely separate from "Introduction".

The point is to move "Ecosystem" out of the "Introduction" category (where it already is) and into a brand-new "Real World Usage" category (which currently does not exist).

Okay, I was just confused since I thought you meant to move "Ecosystem" to the existing "Real World Usage" section, which is a sub-section of the "Learn Redux" section. Moving it into a new category makes more sense then.

Per the idea of a "Quick Start" page, see the feedback I just pasted into https://github.com/reduxjs/redux/issues/3592#issuecomment-570072854 .

I think this introduction section could be reworked.
Analysis
n.b: "I" will sometimes represent a new user.
Getting Started with Redux

Redux is a predictable state container for JavaScript apps.

If I don't know Redux, I don't know what it means.
Installation
I understand that you're promoting RTK but it feels weird that it comes before Redux. You install the toolkit, and then you're left with a package that you don't know how to use because it's actually a different library than the docs you're on.
Learn Redux
If I come to the documentation to learn Redux, I won't lose my time looking at a bunch of links that can lead anywhere. So I would be like "let's skip this section, I will keep reading the docs". And the next step is installation.
Installation
I already read this! Let's go to the next page.
Motivation
Good decision to move it, at this point I should already know why I want to use Redux.
Core Concepts
Knowing Redux I would expect to find those subsections: Store / State / Action / Reducer. Concepts need names.
Three Principles
This whole section announces principles that should be included in the core concepts.

single source of truth -> Store
read-only state -> State
pure functions -> Reducer

Note the ending phrase for Core Concepts:

This is basically the whole idea of Redux.

And for Three principles:

That's it! Now you know what Redux is all about.

It is redundant.
Prior Art
Again good decision to move it, I basically don't care about prior art, I just wanna use Redux.
Learning Resources
I already saw a section on learning Redux. I wasn't interested. And now you give me a zillion more links?!
Ecosystem
Again, more links ?!  I got my toolkit! Isn't it enough ? I'd better find something simpler than Redux... At this point, I might close the tab and go after a simpler solution.
Examples
At last I can see how to use Redux. But I didn't learn how to use it. Yes I could have clicked one of a thousand links, but the docs should teach me.
About the sandboxes, I find them super slow to load, not a great experience.
Proposition

What is Redux

Definition/TLDR of Motivation
What it looks like (basic example)
Comparison with other libraries could go there, be it just a link if it's too big

Installation
Core concepts

Store
State
Actions
Reducers

Where to go next

Official Tutorial
Examples
Learning Resources
Getting help

I know what is Redux. I know the core concepts. I installed the library. Now what ? I can follow the official tutorial, I can look at some examples, I can look up some online resources or find help on discord and whatnot.
Examples should be moved into their own section.
Learning resources and Ecosystem should be moved into the "Real wold usage" mentioned here.
Aside : It's another subject but for the tutorials I would link to the basic tutorial. It's down to earth and show me how to code the core concepts I've learned about.
The Essentials one is ultra scary. It begins by what's basically the Introduction Section. And then it's so big that it is slow to load. I've read a ton of Redux content, but this one I'm not sure I would.
That's a big comment. I hope this feedback is valuable and that you understand I respect the work done. If you think some things could indeed be done, let me know.

@sbaudray thanks, appreciate the feedback!  I'll try to look through those suggestions in more detail shortly.
Per the "Essentials is scary" and "point to the basic tutorial" comments: I get where you're coming from, but I'll have to disagree there.
The goal of the "Essentials" tutorial is to teach people how to be productive with Redux Toolkit, which is now our recommended default syntax for writing Redux logic, with a focus on "here's how to use it" instead of "here's how it works inside". But, to do that, they do still need to know things like what "actions", "reducers", and "immutability" are.  So, that first page provides a crash course in those terms so that the rest of the "write this code and it just works" content (hopefully) makes sense.  Agreed that it's a lot to go through to start, but we have had a number of very positive comments about the "Essentials" tutorial overall.
The "Basics" tutorial, on the other hand is A) very low-level; B) currently very-out-of-date; C) really doesn't help you build anything practical.  So I definitely don't want to point people to that now, and even after I get done rewriting it, I don't want to point to that as the default.
If you've got specific suggestions for how to shuffle or improve the "Essentials" content, I'm definitely interested, but it's going to stay as the default.

A few other quick thoughts:

I'd probably want to move "Learning Resources" and "Examples" underneath the "Tutorials" category
Generally agree with restructuring the "Getting Started" page
But Redux Toolkit needs to stay as the default
Dan originally wrote that "Core Concepts" thing as an SO answer or Reddit comment or something.  The original intent is to show that Redux is more of a set of principles and a pattern than a specific library.  Agree that it could probably be merged with "3 Principles". Not sure where that content should go, though - part of a rewritten "Basics" tutorial?  Somewhere else?

For the tutorial I will answer in  https://github.com/reduxjs/redux/issues/3594
Regarding the Core Concepts; it's my understanding that you want a tutorial centred documentation, so I would put them in the essentials where they basically already are.

@sbaudray : I don't think I'd agree with the statement "you want a tutorial centered documentation".
Per the https://documentation.divio.com/ page you linked in the other issue (which is excellent and something I've already been referring to frequently), tutorials are part of a good set of docs.  But, we also need references, usage guides, and explanations.
It's also worth having some of the same material in multiple places, so that people who might not look at a tutorial can still find it in an "explanation" area, etc.
The "Core Concepts" aspect is somewhere between "explanation" and "tutorial", conceptually.

I'm starting to get a better understanding of the direction :)
Shouldn't Core Concepts belong to Understanding Redux > Thinking in Redux, and we could link to it from the Basic tutorial ?

@sbaudray : I'm actually wondering if we can combine the content from "Core Concepts" and "Three Principles" into a single page. If we did that, we could have ## Three Principles and ## Core Concepts as secondary headers.  I'm just not sure what the combined page title should be.

Core Concepts:

Imagine your app’s state is described as a plain object.
This object is like a “model” except that there are no setters...To change something in the state, you need to dispatch an action.
Finally, to tie state and actions together, we write a function called a reducer.

Three Principles:

The global state of your application is stored in an object tree within a single store.
The only way to change the state is to emit an action, an object describing what happened.
To specify how the state tree is transformed by actions, you write pure reducers.

The structure is actually the same, do we need them under secondary headers  ?

If there's a good way to consolidate and rewrite this content into one page, I'm up for that.

One thing I want to bring here that it's not related to the structure of the section, it's examples. To me, the problem manifests itself across all docs and tutorials but it gets an intro in "Core Concepts". There are multiple places where it's mentioned that actions in Redux are supposed to describe "what happened". The "Core Concepts" page itself states this rather clearly:

An action is a plain JavaScript object (notice how we don’t introduce any magic?) that describes what happened

However, right after that, it goes with examples that contradict the very thing that was just said: ADD_TODO, SET_VISIBILITY_FILTER, etc. None of these describe what happened. These are do-something commands and "glorified setters". I've seen effects of this in real-life projects where engineers following such examples think about actions as about commands. This leads to a logic pile-up in UI components with sequential dispatch calls that just tell the reducer what to do: set this, change that, clear this. I think README here goes in the right direction with its examples of 'counter/incremented' and 'counter/decremented' as at least an attempt of "what happened" style. The docs, however, use 'counter/increment' as a command again and so forth.
I think proper examples would promote a better understanding of "why redux" and "how to redux" and that it's not just a framework to change global variables in an implicit, non-direct way with 4 levels of abstraction for one set operation.

@edudar thanks for the feedback. FWIW, that is actually one of the many pages that need to be rewritten to reflect these newer principles :)
That said, in a lot of ways "actions are events that describe what happened" is an ideal, and one that's admittedly difficult to wrap your mind around.  That's part of why there were so many arguments in the early issues about "Is Redux CQRS? Is it Event Sourcing? Is it Flux?".
At some point I want to write a docs page about "how to mentally model actions" that would give some advice on this topic. To some extent I don't feel qualified to write that page :)  but someone's gotta do it.
Unfortunately, there's a ton of other stuff that's higher priority atm, so that won't be happening any time soon.


[docs] No search results for How can we apply CSS styles to nested elements inside the slot

Hi Team,
Could you please help us in applying the CSS to nested elements inside the slot.
Eg:

Render me in a slot

How can we apply the css to span with class redText inside a P tag which is a slot. It would be helpful if you can share some examples. I have already gone through your workarounds, but couldn't execute it.
Workaround 1 - Use Javascript To Style
(1) Access the slotted elements from javascript by using @queryAssignedElements (See https://lit.dev/docs/components/shadow-dom/#query-assigned-nodes)
(2) For each slotted element, parse its dom tree and style the child nodes using javascript (e.g. childelement.style.backgroundColor = '#ff0';)
Workaround 2 - Copy Slotted HTML to Another Div
(1) Access the slotted elements from javascript by using @queryAssignedElements (See https://lit.dev/docs/components/shadow-dom/#query-assigned-nodes)
(2) For every slotted element under consideration, copy-paste its outerHTML to another empty div, placed next to it.
(3) Since these initially empty divs are not from the slots, you can setup static css rules for them.
(4) Empty the slots after the copy pasting into the adjacent divs is complete.
Regards
Rajesh

This is a good question to ask in the Lit Discord channel.

applying the CSS to nested elements inside the slot

This isn't supported in CSS. You can only style slotted elements themselves using :slotted(...). So you have to write some code to do it...

How can we apply the css to span with class redText inside a P tag which is a slot. It would be helpful if you can share some examples.

Here is an example.
Do not use those workarounds, instead if you can't avoid the issue, I recommend copying a style into the parent scope and attempting to scope it so it applies narrowly.
static scopeStyles = css`
  element-name {
    /* whatever makes sense */
  }
`;

connectedCallback() {
  super.connectedCallback();
  const {scopeStyles} = this.constructor as typeof MyElement;
  const {adoptedStyleSheets} = this.getRootNode() as Document;
  if (!adoptedStyleSheets.includes(scopeStyles.styleSheet)) {
    adoptedStyleSheets.push(scopeStyles.styleSheet);
  }
}

Hi Steve,
Thank you so much for your detailed explanation and the example you shared. It clarified a lot of my doubts, and I appreciate the guidance.
I do have a couple of follow-up queries regarding this approach:

Could this approach have any potential performance implications on the component, especially if used extensively?
Is it acceptable to inject an entire component's CSS (around 30–40 lines) to style the slot elements using this method? Our primary use case involves form controls, and we want to ensure there are no significant limitations or drawbacks before proceeding.

Looking forward to hearing your thoughts. Thanks again for your help!
Best regards,
Rajesh
From: Steve Orvell @.>
Date: Wednesday, 20 November 2024 at 8:19 PM
To: lit/lit.dev @.>
Cc: Paidipati, Rajesh @.>, Author @.>
Subject: [External] Re: [lit/lit.dev] [docs] No search results for How can we apply CSS styles to nested elements inside the slot (Issue #1384)
External email. Inspect before opening any links or attachments.
This is a good question to ask in the Lit Discord channelhttps://urldefense.com/v3/__https://discord.com/invite/buildWithLit__;!!OrxsNty6D4my!6Qorahn5Od9CqGzhw1tidKuQ4eiB5Y64Zn_vay4thx8M_bDwQia-FFSuTgMbAcOHkMOua37qc6_yzI5q7AztvKMwLwTQHpyC$.
applying the CSS to nested elements inside the slot
This isn't supported in CSS. You can only style slotted elements themselves using :slotted(...). So you have to write some code to do it...
How can we apply the css to span with class redText inside a P tag which is a slot. It would be helpful if you can share some examples.
Here is an examplehttps://urldefense.com/v3/__https://lit.dev/playground/*gist=8c05aae25605e6dedbd2f2cdc6ec2a16__;Iw!!OrxsNty6D4my!6Qorahn5Od9CqGzhw1tidKuQ4eiB5Y64Zn_vay4thx8M_bDwQia-FFSuTgMbAcOHkMOua37qc6_yzI5q7AztvKMwL4wN54Z_$.
Do not use those workarounds, instead if you can't avoid the issue, I recommend copying a style into the parent scope and attempting to scope it so it applies narrowly.
static scopeStyles = css  element-name {     /* whatever makes sense */   };
connectedCallback() {
super.connectedCallback();
const {scopeStyles} = this.constructor as typeof MyElement;
const {adoptedStyleSheets} = this.getRootNode() as Document;
if (!adoptedStyleSheets.includes(scopeStyles.styleSheet)) {
adoptedStyleSheets.push(scopeStyles.styleSheet);
}
}
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/lit/lit.dev/issues/1384*issuecomment-2488785291__;Iw!!OrxsNty6D4my!6Qorahn5Od9CqGzhw1tidKuQ4eiB5Y64Zn_vay4thx8M_bDwQia-FFSuTgMbAcOHkMOua37qc6_yzI5q7AztvKMwL-dU-5ui$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BI2JMC5TNZYLHS4PNJNXAQD2BSOPFAVCNFSM6AAAAABSDU3U2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBYG44DKMRZGE__;!!OrxsNty6D4my!6Qorahn5Od9CqGzhw1tidKuQ4eiB5Y64Zn_vay4thx8M_bDwQia-FFSuTgMbAcOHkMOua37qc6_yzI5q7AztvKMwL0Iu0j9R$.
You are receiving this because you authored the thread.Message ID: @.***>

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.

www.accenture.com

Could this approach have any potential performance implications on the component, especially if used extensively?

I can't guarantee anything, but I wouldn't expect performance issues.

Is it acceptable to inject an entire component's CSS ... we want to ensure there are no significant limitations or drawbacks before proceeding

The main drawback is the need to avoid conflicting with user styling. A more general approach would be to provide a stylesheet along with your elements for users to apply themselves, but if your user base is limited, say to your company, the auto-injection approach may be reasonable.
I'd recommend trying to manually scope the styles to apply inside your elements as much as possible (the example showed a simple approach), and I would also recommend using an @layer to help control the cascade more easily.

Thanks Steve, appreciate your quick response and the insights you provided.
From: Steve Orvell @.>
Date: Thursday, 21 November 2024 at 4:25 AM
To: lit/lit.dev @.>
Cc: Paidipati, Rajesh @.>, Author @.>
Subject: [External] Re: [lit/lit.dev] [docs] No search results for How can we apply CSS styles to nested elements inside the slot (Issue #1384)
External email. Inspect before opening any links or attachments.

Could this approach have any potential performance implications on the component, especially if used extensively?

I can't guarantee anything, but I wouldn't expect performance issues.

Is it acceptable to inject an entire component's CSS ... we want to ensure there are no significant limitations or drawbacks before proceeding

The main drawback is the need to avoid conflicting with user styling. A more general approach would be to provide a stylesheet along with your elements for users to apply themselves, but if your user base is limited, say to your company, the auto-injection approach may be reasonable.
I'd recommend trying to manually scope the styles to apply inside your elements as much as possible (the example showed a simple approach), and I would also recommend using an @@.***__;!!OrxsNty6D4my!4a3-cdqq-sN4jQwlW7JqwB_yuWsNSF3-HZU-5rPUYn75yhirxK0sO9u1Om9w21NTHm3dVNn5qVL568aSCDtb_j5vqC_DMDTv$> to help control the cascade more easily.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/lit/lit.dev/issues/1384*issuecomment-2489698449__;Iw!!OrxsNty6D4my!4a3-cdqq-sN4jQwlW7JqwB_yuWsNSF3-HZU-5rPUYn75yhirxK0sO9u1Om9w21NTHm3dVNn5qVL568aSCDtb_j5vqDFawq0E$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BI2JMC5ALZULZYD4ZPNKCX32BUHMTAVCNFSM6AAAAABSDU3U2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGY4TQNBUHE__;!!OrxsNty6D4my!4a3-cdqq-sN4jQwlW7JqwB_yuWsNSF3-HZU-5rPUYn75yhirxK0sO9u1Om9w21NTHm3dVNn5qVL568aSCDtb_j5vqEj1BDeh$.
You are receiving this because you authored the thread.Message ID: @.***>

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.

www.accenture.com


[Codegen 129]: add emitObjectProp in parser primitives

Summary:

Part of #34872

Create a function emitObjectProp(name: string, optional: boolean) in parser-primitives.js. Factor out the code from Flow and TypeScript into that function. Use that function in the original call site.

Changelog:

[Internal][Changed]: Add emitObjectProp in parser primitives
Test Plan:

yarn test react-native-codegen

@rshest @cipolleschi , It seems the this PR was not merged correctly. So, I've opened a follow-up PR https://github.com/facebook/react-native/pull/37904

@tarunrajput I'm sorry for this. Thank you for the followup!


Made reach,push,pick-place env solvable

Originally, if env was randomized, it was basically unsolvable (The best strategy would be to randomly flail about, and hope to touch the _state_goal coordinate by luck).
Options to fix were:

Add info about _state_goal to observation
Keep _state_goal constant and instead have random_init impact the sawyer's starting position

I chose the first option. Specifically, the observation now includes a 3D vector that points from the end effector to _state_goal. @ryanjulian suggested just a euclidean distance, but as far as I can tell, that wouldn't provide enough information to solve the env in a stateless manner; the policy would have to guess and check for directionality. Hopefully my method doesn't count as goal conditioning.

Before merging #95 and #96 please, in the module wide docstring of each of these environments, please write a short message describing what the changes are that you have made to these environments.

@haydenshively can you add L2 distance instead of a 3-element vector?


Job title localization

About the PR

localizing job title. Replaced all uses of JobTitle with LocalizedJobTitle.
I have a problem!...
public string? LocalizedJobTitle = Loc.GetString(JobTitle) gives error that Field initializer cannot access non-static field, method, or property 'IdCardComponent.JobTitle'.CS0236. I don't know how to handle this... help me please, I want to localize this! 😭
Why / Balance

Technical details

Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl: to4no_fix

Strongest localization warrior 💪 💪 💪

Strongest localization warrior 💪 💪 💪

Start your day with game localization! 🥤

Everything is fixed and working

fixes https://github.com/space-wizards/space-station-14/issues/28791


How to develop a custom map with openlayers?

How to develop a custom map with openlayers?
There are some objects are moving on the map.
The base picture of map is 'CAD Dwg' files.
I can know the latitude and longitude of the map with 'GPS'.
I can know the latitude and longitude of the objects which is moving on the map with 'GPS'.
It should not be developed on the GPS API.
I can only get the latitude and longitude by GPS with hardware devices.
There are some questions to ask:
1、Is there similar js framework to use?
2、Is there similar demo to reference?
3、Is there similar algorithm to achieve?
Thinking with myself.
4、Should the map must use canvas to achieve? Is there other way?
5、Is it necessary to convert dwg to a picture,for example png,jpg?
6、How to set the coordinate system of map is better?
7、How to draw the dots on the map?
8、How to connect the dots be a line?
I haven't done anything like this.
Please master to give directions and help me.
Thank you very much,master.

This is an issue tracker, not a Q&A forum. Please start by looking at the examples, then look for questions that are already answered on Stack Overflow. If anything is still unclear, ask more specific questions - also on Stack Overflow.


WIP - Card storage

This is a start to implementing the store/unstore card features listed in #6

Not sure how the history of this branch went wrong so closed off in favour of a tidier branch.


Property bindings not working in templates with whitespaces or other combinations

In the quick tour property binding example, there is a component defined this way:
<dom-module id="name-tag">

  <template>

    This is {{owner}}'s name-tag element.
  </template>

</dom-module>

If the  tags are removed:
  <template>

    This is {{owner}}'s name-tag element.
  </template>

We would expect to have This is Daniel's name-tag element., but the content that is rendered is This is {{owner}}'s name-tag element..
The same happen trying other stuff, such as several properties, etc:
This is {{owner}}{{owner}}'s name-tag element.
This is {{owner}}-{{owner}}'s name-tag element.
Here is a test JSFiddle

According to the documentation:

String concatenation is not supported inside a tag, and the tag can’t contain any whitespace

So you must wrap the binding into a tag: This is {{owner}}'s name-tag element.

Er, right... I should've seen it, sorry.
Anyway, any plans to support this in the future?

AFAIK it is on the roadmap: https://www.polymer-project.org/1.0/docs/#binding-features

@timeu Thanks for the info!! I'm closing the issue then


support Scala 2.12.0

ping @bphelan

yes please

2.12.0-RC2 is now out

hi. anybody still maintaining this repo...?

http://repo1.maven.org/maven2/com/github/seratch/com/veact/scala-ssh_2.12/0.8.0-1/
https://github.com/seratch/scala-ssh/commit/c905116a18a4560d5225af9811ea0a63d6b8c6ab

hmm.... so should the Scala community build be tracking @seratch's fork instead of this repo, do you think?

@SethTisue I myself is willing to contribute to the community builds. I should work on my fork more seriously.

Hi,
A member of our team looked into the open pull requests for Scala 2.12.x and found some issues with them... I asked him to get back to the authors a few weeks back but it looks like he's been too busy.
Feel free to follow another fork.  We took over maintaining this because it hadn't been updated in almost two years.  We're still maintaining this here but things like Scala version updates aren't much of a priority to us and this is a busy time of year.
Cheers,
Ben

@seratch I had forgotten that the community build is already tracking @xuwei-k's fork, rather than this repo. your changes seem similar, so I'm not sure there's any benefit to switching?

@SethTisue I see. At the current moment, there is no strong reason to choose mine over Kenji's one.

Scala is up to 2.12.4 now and moreover sshj is up to 0.23.0 now, which includes support for 384-bit elliptic ecdsa keys used by some servers.  We have locally overridden the sshj dependency to 0.23.0 with no ill effects, and the various forks on github enabling scala-2.12 support seem to be simply adding the version number to the dependencies.  Would there be any chance to get a minimal 0.9 release with these updates?


Update Composer dependencies (2021-03-26-00-07)

Visual regression test passed!
View the visual regression test report


Added after priority to replace default authenticator.

The documentation needs to include the after priority in order to override the default authenticator.  Currently there is no clear indication of this and without it, coresecurity will override your changes.

@robbieaverill Updated =)


[Feature] when content overflow workarea, hide the content overflow

when content overflow workarea, hide the content overflow

@shuwenjunn
What is mean?

It will be very useful!
without overflow

with overflow

I finally got it using the globalCompositeOperation property!
On workarea object, I used the globalCompositeOperation: "source-in" and on all other objects globalCompositeOperation: "source-atop"


Touch cursor is not centered on target element

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
Circle cursor positioned over target element so it's top left corner is over target's center. It's behavior of the pointer-like cursor. E.g. the target is YouTube logo.

What is the expected behavior?
Touch cursor should be centered on target-element
How would you reproduce the current behavior (if this is a bug)?
Start test on a touch device
Provide the test code and the tested page URL (if applicable)
Tested page URL: https://youtube.com
Test code
fixture `Google`.page `https://youtube.com`;

test('test', async t => {
    await t
        .click('#koya_elem_2_1 > div._mihc > div > button > span')
        .wait(1000000000);
});

Specify your

operating system: Windows 10
testcafe version: 0.13.0-alpha3
node.js version: 7.5.0

Duplicate of https://github.com/DevExpress/testcafe/issues/739

My fault, I was misleading, initial-scale doesn't help with this one, cursor is still displaced with this meta. Something is wrong with pointerOffsetX and pointerOffsetY in cursor UI.


Clearer error message for URL without a hostname.

When I got the existing error message I had no idea what it meant.  A little digging in the code reveals that the problem was I provided a URL that did not contain a hostname, so aiohttp was unable to parse the hostname out of that URL.  Here is an alternate wording for the error message that I hope will lead the library user to understand what went wrong more quickly.

What do these changes do?

Are there changes in behavior for the user?

Related issue number

Checklist

[ ] I think the code is well written
[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes
[ ] Add yourself to CONTRIBUTORS.txt

The format is <Name> <Surname>.
Please keep alphabetical order, the file is sorted by names.

[ ] Add a new entry to CHANGES.rst

Choose any open position to avoid merge conflicts with other PRs.
Add a link to the issue you are fixing (if any) using #issue_number format at the end of changelog message. Use Pull Request number if there are no issues for PR or PR covers the issue only partially.

could you create PR against https://github.com/aio-libs/aiohttp


atime is not a Date object

Replace
var atime = Date.now();

by
var atime = new Date(Date.now());

Fixed.


Update UCX docs to call out Ubuntu 22.04 is not supported yet [skip ci]

Signed-off-by: Alessandro Bellina<EMAIL_ADDRESS>This adds a NOTE to the UCX section of the rapids-shuffle docs to call out that Ubuntu 22.04 isn't supported as of spark-rapids 23.02, but will be in the future.

build

build


i18n Support

Do you plan to support multiple languages? Its important that you offer a usable SDK for non-English speaking clients.

Hi Alex,
We do support multi languages for the SDK, it is based on the set up of the SumUp account you are using. I have changed your set up for the test account we've provided you. We will get in touch directly with your team for further information.
Many thanks,


Fabric slice expiring fails to to delete AL2S connection

A fabric slice that creates an aws dx connection using al2s can expire and is not able to delete the dx connection since it still in use.  This falls into the general problem of fabric control framework "leaking resources" ....  Fabric should have a way to retry post deleting a slice .... I know the team spoke about this. Just not sure if this has been taken care of or not.

In the current case, Network AM retries 3 times on failure to delete. If retry attempts also fail an audit process has been added which periodically attempts to clean up the leaked slivers every hour.
I need to check if AL2S handler has 3 retries in built or not.
Audit will be available in 1.7